Method and apparatus for transmitting and receiving a wireless signal in a wireless communication system

Abstract

In the present invention, a device performs a procedure for setting a first path related to a direct connection to a network, and while the device is in an RRC (radio resource control) connection state in which the first path is set, a sidelink message for adding a second path related to an indirect connection to the network is transmitted to another device set as a relay device between the network and the device. Based on the fact that the other device is not in an RRC connection state, the random access process of the other device is triggered by the transmission of the sidelink message of the device.

Description

Technical Field

[0001] The present invention relates to a wireless communication system, and more specifically, to a method and apparatus for transmitting and receiving wireless signals.

Background Art

[0002] A wireless communication system is a multiple access system that shares available system resources (such as bandwidth, transmission power, etc.) to assist communication with multiple users. Examples of multiple access systems include CDMA (code division multiple access) systems, FDMA (frequency division multiple access) systems, TDMA (time division multiple access) systems, OFDMA (orthogonal frequency division multiple access) systems, SC-FDMA (single carrier frequency division multiple access) systems, MC-FDMA (multi carrier frequency division multiple access) systems, and the like.

[0003] Sidelink (SL) refers to a communication method in which a direct link is established between terminals (User Equipment, UE) to directly exchange voice or data between the terminals without going through a base station (Base Station, BS). SL is one solution to solve the burden on the base station due to the rapidly increasing data traffic.

[0004] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, infrastructure, and other things through wired or wireless communication. V2X is classified into four types such as V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication is provided by the PC5 interface and / or the Uu interface.

[0005] On the other hand, as more communication devices require larger communication capacities, the need for improved mobile broadband communication compared to existing radio access technologies (RATs) is emerging. As a result, the design of communication systems considering services or terminals sensitive to reliability and latency is being discussed. The next-generation radio access technology considering enhanced mobile broadband communication, massive MTC, URLLC (Ultra-Reliable and Low Latency Communication), etc. is called new radio access technology (new radio) or NR (new radio). V2X (vehicle-to-everything) communication can also be supported in NR.

[0006] FIG. 1 is a diagram for explaining a comparison between V2X communication based on RAT before NR and V2X communication based on NR.

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

[0008] For example, CAM includes dynamic state information of a vehicle such as direction and speed, static vehicle data such as dimensions, basic vehicle information such as external lighting status, and route details. For example, a terminal can broadcast CAM, and the delay of CAM is less than 100 ms. For example, when an emergency situation such as a vehicle failure or accident occurs, the terminal can generate and send DENM to other terminals. For example, all vehicles within the transmission range of the terminal can receive CAM and / or DENM. In this case, DENM has a higher priority than CAM.

[0009] Subsequently, various V2X scenarios have been defined in NR in relation to V2X communication. For example, various V2X scenarios include vehicle platooning, advanced driving, extended sensors, remote driving, etc.

[0010] For example, based on vehicle platooning, vehicles dynamically form a group and move together. For example, in order to perform platoon operations based on vehicle platooning, the vehicles belonging to the above group receive periodic data from the leading vehicle. For example, the vehicles belonging to the above group can use the periodic data to reduce or increase the inter-vehicle distance.

[0011] For example, based on enhanced driving, a vehicle is semi-automated or fully automated. Each vehicle can adjust trajectories or maneuvers based on data obtained from local sensors of neighboring vehicles and / or neighboring logical entities. For example, each vehicle can share driving intentions with neighboring vehicles with each other.

[0012] For example, based on extended sensors, raw data, processed data, or live video data obtained by local sensors can be exchanged between vehicles, logical entities, pedestrian terminals, and / or V2X application servers with each other. Therefore, for example, a vehicle can recognize an environment that is better than the environment that can be sensed using its own sensors.

[0013] For example, based on remote driving, for a person who cannot drive or a remote vehicle located in a dangerous environment, a remote driver or a V2X application can operate or control the remote vehicle. For example, when the route can be predicted like in public transportation, cloud computing-based driving is used for the operation or control of the remote vehicle. For example, access to a cloud-based back-end service platform is considered for remote driving.

[0014] On the other hand, solutions for specifying service requirements for various V2X scenarios such as platooning vehicles, enhanced driving, extended sensors, remote driving, etc. are being discussed in V2X communication based on NR. SUMMARY OF THE INVENTION PROBLEMS TO BE SOLVED BY THE INVENTION

[0015] An object of the present invention is to provide a method and an apparatus therefor for accurately and efficiently performing a wireless signal transmission / reception procedure.

[0016] The technical problems to be achieved in the present invention are not limited to the above technical problems, and other technical problems not mentioned will be clearly understandable to those with ordinary knowledge in the technical field to which the present invention belongs from the following description.

Means for Solving the Problems

[0017] According to one aspect of the present invention, in a wireless communication system, a method for a first UE (user equipment) to set a multi-radio communication path includes executing a procedure for setting a first path related to a direct connection to a network, and while the first UE is in an RRC (radio resource control) connection state in which the first path is set, transmitting a sidelink message for adding a second path related to an indirect connection to the network to a second UE set as a relay UE between the network and the first UE. Based on the fact that the second UE is not in an RRC connection state, the random access process of the second UE is triggered by the transmission of the sidelink message of the first UE.

[0018] Preferably, the second UE that is not in an RRC connection state performs the random access process to request an RRC connection to the network.

[0019] Preferably, the first UE requests the second UE to perform the random access process.

[0020] Preferably, based on the second UE being RRC-connected to the network, the second path related to the indirect connection to the network is set.

[0021] Preferably, the first UE is configured with the first path related to the direct connection to the network and the second path related to the indirect connection to the network.

[0022] Preferably, the sidelink message is directly transmitted to the second UE via the sidelink interface between the first UE and the second UE.

[0023] Preferably, the sidelink message includes information indicating that the sidelink message is related to the multi-path configuration of the first UE.

[0024] Preferably, the first UE receives, via the first path, an RRC reconfiguration message from the network that includes information for additionally configuring the second path on the first path.

[0025] Preferably, the sidelink message is transmitted based on the RRC reconfiguration message.

[0026] Preferably, based on the additional configuration of the second path on the first path, the first UE transmits an RRC reconfiguration complete message to the network via the first path or the second path.

[0027] Preferably, the first UE operates as a remote UE on the second path related to the indirect connection.

[0028] According to another aspect of the present invention, there is provided a computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform the above-described method.

[0029] According to another aspect of the present invention, there is provided a UE configured to perform the above method.

[0030] According to another aspect of the present invention, there is provided an apparatus for controlling a UE configured to perform the above method. [Advantages of the Invention]

[0031] According to the present invention, wireless signal transmission and reception procedures can be performed accurately and efficiently.

[0032] The effects that can be obtained from various examples of the present disclosure, and other effects not mentioned, will be clearly derived and understood by those having ordinary knowledge in the technical field to which the present invention pertains from the following description. [Brief Description of the Drawings]

[0033]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Mode for Carrying Out the Invention

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

[0035] For background technology, terms, definitions, and abbreviations related to this invention, the following documents can be referred to.

[0036] 3GPP (Registered Trademark) LTE

[0037] - 3GPP TS 36.211: Physical channels and modulation

[0038] - 3GPP TS 36.212: Multiplexing and channel coding

[0039] - 3GPP TS 36.213: Physical layer procedures

[0040] - 3GPP TS 36.214: Physical layer; Measurements

[0041] - 3GPP TS 36.300: Overall description

[0042] - 3GPP TS 36.304: User Equipment (UE) procedures in idle mode

[0043] - 3GPP TS 36.314: Layer 2 - Measurements

[0044] - 3GPP TS 36.321: Medium Access Control (MAC) protocol

[0045] - 3GPP TS 36.322: Radio Link Control (RLC) protocol

[0046] - 3GPP TS 36.323: Packet Data Convergence Protocol (PDCP)

[0047] - 3GPP TS 36.331: Radio Resource Control (RRC) protocol

[0048] 3GPP NR

[0049] - 3GPP TS 38.211: Physical channels and modulation

[0050] - 3GPP TS 38.212: Multiplexing and channel coding

[0051] - 3GPP TS 38.213: Physical layer procedures for control

[0052] - 3GPP TS 38.214: Physical layer procedures for data

[0053] - 3GPP TS 38.215: Physical layer measurements

[0054] - 3GPP TS 38.300: Overall description

[0055] - 3GPP TS 38.304: User Equipment (UE) procedures in idle mode and in RRC inactive state

[0056] - 3GPP TS 38.321: Medium Access Control (MAC) protocol

[0057] - 3GPP TS 38.322: Radio Link Control (RLC) protocol

[0058] - 3GPP TS 38.323: Packet Data Convergence Protocol (PDCP)

[0059] - 3GPP TS 38.331: Radio Resource Control (RRC) protocol

[0060] - 3GPP TS 37.324: Service Data Adaptation Protocol (SDAP)

[0061] - 3GPP TS 37.340: Multi-connectivity; Overall description

[0062] Sidelink (SL) refers to a communication method that directly establishes a link between terminals (User Equipment, UE) and enables direct communication of voice or data between terminals without going through a base station (Base Station, BS). Sidelink is a solution to relieve the burden on the base station caused by rapidly increasing data traffic.

[0063] V2X (vehicle-to-everything) means a communication technology that exchanges information with other vehicles, pedestrians, infrastructure, etc. through wireless communication. V2X is classified into four types such as V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication is provided by the PC5 interface and / or the Uu interface.

[0064] On the other hand, as more communication devices require larger communication capacities, there is a growing need for improved mobile broadband communication compared to existing radio access technologies (RAT). As a result, communication systems considering services or terminals sensitive to reliability and latency are being discussed. Next-generation radio access technologies considering such improved mobile broadband communication, massive MTC, URLLC (Ultra-Reliable and Low Latency Communication), etc. are called new radio access technology (new radio) or NR (new radio). V2X (vehicle-to-everything) communication can also be supported in NR.

[0065] The following technologies can be used in various radio access systems such as CDMA (Code Division Multiple Access), FDMA (Frequency Division Multiple Access), TDMA (Time Division Multiple Access), OFDMA (Orthogonal Frequency Division Multiple Access), SC-FDMA (Single Carrier Frequency Division Multiple Access). CDMA can be implemented by radio technologies such as UTRA (Universal Terrestrial Radio Access) and CDMA2000. TDMA can be implemented by radio 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 by radio technologies such as IEEE802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE802-20, E-UTRA (Evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e and provides 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 part of E-UMTS (Evolved UMTS) that uses E-UTRA, adopts OFDMA in the downlink, and adopts SC-FDMA in the uplink. LTE-A (Advanced) is an evolution of 3GPP LTE.

[0066] 5G NR is a technology that follows LTE-A and is a new clean-slate mobile communication system with characteristics such as high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, such as low-frequency bands below 1 GHz, intermediate-frequency bands from 1 GHz to 10 GHz, and high-frequency (millimeter-wave) bands above 24 GHz.

[0067] For a clearer explanation, the description will focus on LTE-A or 5G NR, but the technical idea according to an embodiment of the present invention is not limited to these.

[0068] FIG. 2 shows the structure of an LTE system according to an embodiment of the present invention. This is also called an E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network), or an LTE (Long Term Evolution) / LTE-A system.

[0069] Referring to FIG. 2, the E-UTRAN includes a base station 20 that provides a control plane and a user plane to a terminal 10. The terminal 10 can be fixed or mobile and is also called by terms such as MS (mobile station), UT (user terminal), SS (Subscriber station), MT (mobile terminal), and wireless device. Generally, the base station 20 is a fixed station that communicates with the terminal 10 and is also called by applications such as eNB (evolved NodE-B), BTS (base transceiver system), and AP (access point).

[0070] The base stations 20 are connected to each other by an X2 interface. The base station 20 is connected to the EPC (evolved Packet core, 30) by an S1 interface, more specifically, connected to the MME (mobility management entity) by S1-MME and to the S-GW (Serving gateway) via S1-U.

[0071] EPC30 consists of an MME, an S-GW, and a P-GW (Packet data network-gateway). The MME has access information of the terminal and information regarding the capabilities of the terminal, and such information is mainly used for the mobility management of the terminal. The S-GW is a gateway with the E-UTRAN as an endpoint, and the P-GW is a gateway with the PDN (Packet Date Network) as an endpoint.

[0072] The radio interface protocol layers between the terminal and the network are classified into a first layer (L1), a second layer (L2), and a third layer (L3) based on the lower three layers of the well-known Open System Interconnection (OSI) reference model in a communication system. Among them, the physical layer belonging to the first layer provides an information transmission service using physical channels, and the RRC (Radio Resource Control) layer belonging to the third layer controls radio resources between the terminal and the network. For this purpose, the RRC layer exchanges RRC messages between the terminal and the base station.

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

[0074] Referring to Figure 3, the NG-RAN (Next Generation-Radio Access Network) includes a gNB (next generation-Node BF cell) and / or an eNB that provide user plane and control plane protocol termination to the terminal. The case of including only the gNB is illustrated in Figure 7. The gNB and the eNB are connected to each other by an Xn interface. The gNB and the eNB are connected to the 5th generation core network (5G Core Network: 5GC) by an NG interface. More specifically, the AMF (access and mobility management function) is connected by an NG-C interface, and the UPF (user plane function) is connected by an NG-U interface.

[0075] FIG. 4 shows the structure of the NR radio frame.

[0076] Referring to FIG. 4, in NR, radio frames are used for uplink and downlink transmissions. The radio frame has a length of 10 ms and is defined by two 5 ms half-frames (HF). Each half-frame contains five 1 ms sub-frames (SF). A sub-frame is divided into one or more slots, and the number of slots in a sub-frame depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM(A) symbols with a cyclic prefix (CP).

[0077] When normal CP is used, each slot contains 14 symbols. When extended CP is used, each slot contains 12 symbols. Here, the symbols include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or DFT-s-OFDM symbols).

[0078] Table 1 illustrates the number of symbols per slot (N slot symbol ), the number of slots per frame (N frame,u slot ), and the number of slots per sub-frame (N subframe,u slot ) according to the SCS setting (μ) when normal CP is used.

[0079]

Table 1

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

[0081]

Table 2

[0082] In the NR system, the OFDM(A) numerology (e.g., SCS, CP length, etc.) can be set to be different among a plurality of cells merged into one terminal. As a result, the (absolute time) intervals of time resources (e.g., subframes, slots or TTIs) (collectively referred to as TUs (Time Unit) for convenience) composed of the same number of symbols are set to be different among the merged cells.

[0083] In NR, a number of numerologies or SCSs are supported to support various 5G services. For example, when the SCS is 15 kHz, a wide area in a traditional cellular band is supported, and when the SCS is 30 kHz / 60 kHz, dense-urban, lower latency and wider carrier bandwidth are supported. When the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz is supported to overcome phase noise.

[0084] The NR frequency band is defined by two types of frequency ranges. The two types of frequency ranges are FR1 and FR2. The numerical values of the frequency ranges are changeable. For example, the two types of frequency ranges are as shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 means "sub 6GHz range", FR2 means "above 6GHz range", and is also called millimeter wave (mmW).

[0085]

Table 3

[0086] As described above, the numerical values of the frequency range of the NR system can be changed. For example, FR1 includes a band from 410 MHz to 7125 MHz as shown in Table 4 below. That is, FR1 includes a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included within FR1 includes an unlicensed band. The unlicensed band is used for various applications, for example, it is used for communication for vehicles (e.g., autonomous driving).

[0087] [Table 4]

[0088] Figure 5 is a diagram showing the slot structure of an NR frame.

[0089] Referring to Figure 5, a slot includes a plurality of symbols in the time domain. For example, in the case of normal CP, one slot includes 14 symbols, while in the case of extended CP, one slot includes 12 symbols. Or in the case of normal CP, one slot includes 7 symbols, while in the case of extended CP, one slot includes 6 symbols.

[0090] A carrier wave includes a plurality of sub-carriers in the frequency domain. An RB (Resource Block) is defined as a plurality (e.g., 12) of consecutive sub-carriers in the frequency domain. A BWP is defined as a plurality of consecutive (P)RBs ((Physical) Resource Block) in the frequency domain and corresponds to one numerology (e.g., SCS, CP length, etc.). A carrier wave includes a maximum of N (e.g., 5) BWPs. Data communication is performed on the activated BWP. Each element is referred to as a resource element (RE) in the resource grid, and one complex symbol can be mapped.

[0091] On one hand, the wireless interface between terminals or the wireless interface between a terminal and a network is composed of an L1 layer, an L2 layer, and an L3 layer. In various embodiments of the present invention, the L1 layer means the physical layer. The L2 layer means, for example, any one of a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer. The L3 layer means, for example, an RRC layer.

[0092] Hereinafter, V2X or SL (sidelink) communication will be described.

[0093] FIG. 6 shows a radio protocol architecture for SL communication. More specifically, FIG. 6(a) shows the user plane protocol stack of NR, and FIG. 6(b) shows the control plane protocol stack of NR.

[0094] Hereinafter, the sidelink synchronization signal (SLSS) and synchronization information will be described.

[0095] The SLSS includes a PSSS (Primary Sidelink Synchronization Signal) and an SSSS (Secondary Sidelink Synchronization Signal) as an SL-specific sequence. The PSSS is called S-PSS (Sidelink Primary Synchronization Signal), and the SSSS is called S-SSS (Sidelink Secondary Synchronization Signal). For example, length-127 M-sequences are used for S-PSS, and length-127 Gold sequences are used for S-SSS. For example, a terminal detects the first signal and acquires synchronization using S-PSS. For example, a terminal acquires fine synchronization and detects a synchronization signal ID using S-PSS and S-SSS.

[0096] The Physical Sidelink Broadcast Channel (PSBCH) is a (broadcast) channel on which the basic (system) information that a terminal should know first before SL signal transmission and reception is transmitted. For example, the basic information includes information about SLSS, Duplex Mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, information about resource pools, the type of application related to SLSS, subframe offset, broadcast information, etc. For example, in order to evaluate the performance of the PSBCH in NR V2X, the payload size of the PSBCH is 56 bits including a 24-bit CRC.

[0097] S-PSS, S-SSS, and PSBCH are included in a block format (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter referred to as S-SSB (Sidelink-Synchronization Signal Block)) that supports periodic transmission. The S-SSB has the same numerology (i.e., SCS and CP length) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) within a carrier, and the transmission bandwidth is within a pre-set SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB is 11 Resource Blocks (RBs). For example, the PSBCH spans 11 RBs. Also, the frequency position of the S-SSB is pre-set. Therefore, the terminal does not need to perform hypothesis detection in terms of frequency to discover the S-SSB in a carrier.

[0098] On the one hand, in the NR SL system, a plurality of numerologies having different SCSs and / or CP lengths are supported. At this time, as the SCS increases, the length of the time resource for the transmitting terminal to transmit the S-SSB becomes shorter. As a result, the coverage of the S-SSB decreases. Therefore, in order to ensure the coverage of the S-SSB, the transmitting terminal transmits one or more S-SSBs to the receiving terminal within one S-SSB transmission period according to the SCS. For example, the number of S-SSBs transmitted by the transmitting terminal to the receiving terminal within one S-SSB transmission period is pre-configured or configured for the transmitting terminal. For example, the S-SSB transmission period is 160 ms. For example, a 160-ms S-SSB transmission period is supported for all SCSs.

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

[0100] For example, when the SCS is 60 kHz in FR2, the transmitting terminal transmits one, two, four, eight, sixteen, or thirty-two S-SSBs to the receiving terminal within one S-SSB transmission period. For example, when the SCS is 120 kHz in FR2, the transmitting terminal transmits one, two, four, eight, sixteen, thirty-two, or sixty-four S-SSBs to the receiving terminal within one S-SSB transmission period.

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

[0102] FIG. 7 shows a terminal performing V2X or SL communication.

[0103] Referring to FIG. 7, in V2X or SL communication, the term "terminal" mainly means the user's terminal. However, when network equipment such as a base station transmits and receives signals according to the communication method between terminals, the base station may also be regarded as a kind of terminal. For example, terminal 1 is the first device 100, and terminal 2 is the second device 200.

[0104] For example, terminal 1 selects a resource unit corresponding to a specific resource within a resource pool that means a set of a series of resources. Also, terminal 1 transmits an SL signal using the resource unit. For example, terminal 2, which is a receiving terminal, has a resource pool set in which it can transmit a signal to terminal 1, and detects the signal of terminal 1 within the resource pool.

[0105] Here, when the terminal 1 is within the connection range of the base station, the base station notifies the terminal 1 of the resource pool. On the other hand, when the terminal 1 is outside the connection range of the base station, another terminal notifies the terminal 1 of the resource pool, or the terminal 1 uses a preset resource pool.

[0106] Generally, a resource pool consists of a plurality of resource units, and each terminal selects one or more resource units to use for its own SL signal transmission.

[0107] FIG. 8 shows resource units for V2X or SL communication.

[0108] Referring to FIG. 8, the entire frequency resource of the resource pool is divided into NF, and the entire time resource of the resource pool is divided into NT. Therefore, a total of NF*NT resource units are defined within the resource pool. FIG. 8 shows an example where the resource pool is repeated with a period of NT subframes.

[0109] As shown in FIG. 8, one resource unit (e.g., Unit #0) is shown periodically repeated. Alternatively, in order to obtain the effect of diversity in the time or frequency dimension, the index of the physical resource unit to which one logical resource unit is mapped may change in a pattern predetermined by time. In this resource unit structure, the resource pool means a set of resource units available for transmission by a terminal attempting to transmit an SL signal.

[0110] The resource pool can be subdivided into several types. For example, according to the content of the SL signal transmitted from each resource pool, the resource pool can be classified as follows.

[0111] (1) Scheduling Assignment (SA) is a signal that contains information such as the location of resources used by a transmitting terminal for transmitting on the SL data channel, the Modulation and Coding Scheme (MCS) or Multiple Input Multiple Output (MIMO) transmission mode required for demodulating other data channels, and Timing Advance (TA). SA can also be multiplexed and transmitted together with SL data on the same resource unit. In this case, the SA resource pool means the resource pool on which SA is multiplexed and transmitted together with SL data. SA is also called the SL control channel.

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

[0113] (3) The discovery channel is the resource pool for a transmitting terminal to transmit information such as its own ID, enabling the transmitting terminal to be discovered by adjacent terminals.

[0114] Even when the content of the aforementioned SL signal is the same, different resource pools can be used according to the attributes of the SL signal transmission and reception. As an example, even for the same SL data channel or discovery message, depending on the SL signal transmission timing determination method (for example, whether it is transmitted at the reception time of the synchronization reference signal, or transmitted by applying a certain timing advance to the reception time), the resource allocation method (for example, whether the base station designates the transmission resources of individual signals to individual transmission terminals, or whether individual transmission terminals themselves select individual signal transmission resources within the resource pool), the signal format (for example, the number of symbols occupied by each SL signal in one subframe, or the number of subframes used for the transmission of one SL signal), the signal strength from the base station, the transmission power strength of the SL terminal, etc., it may be divided into different resource pools.

[0115] SL DRX (sidelink discontinuous reception)

[0116] SL supports SL DRX for unicast, groupcast, and broadcast. Define similar parameters (on-duration, inactivity-timer, retransmission-timer, cycle) for Uu for SL to determine the SL active time for SL DRX. During the SL active time, the terminal performs SCI monitoring for data reception (for example: two-stage SCI of PSCCH and PSSCH). During the SL DRX inactive time, the terminal may skip SCI monitoring for data reception.

[0117] The actual parameters supported for each cast type (unicast, groupcast, broadcast) are specified in the following subsections.

[0118] The SL active time of the RX terminal includes the time during which an applicable SL on-duration timer, SL inactivity timer, or SL retransmission timer is running (for one of unicast, groupcast, or broadcast). Also, the slots associated with the known periodic transmissions of the TX terminal and the time when the terminal expects a CSI report associated with a CSI request (for unicast) are considered the SL active time of the RX terminal.

[0119] The TX terminal maintains a timer set corresponding to the SL DRX timer of the RX terminal for each source / destination L2 ID pair for unicast or each destination L2 ID for groupcast / broadcast. If there is data to be transmitted to one or more RX terminals with SL DRX set, the TX terminal selects resources considering the active time of the RX terminal determined by the timer maintained at itself.

[0120] In the case of unicast, SL DRX is set for each pair of source L2 ID and destination L2 ID.

[0121] The terminal maintains an SL DRX timer set for each direction for each pair of source L2 ID and destination L2 ID. For a source / destination L2 ID pair, the SL DRX setting for one direction can be negotiated between terminals in the AS hierarchy. In the case of the SL DRX setting for each direction where one terminal is the TX terminal and the other is the RX terminal:

[0122] - The RX terminal can send assistance information including the desired on-duration timer, SL DRX start offset, and SL DRX period to the TX terminal, and all 2TX terminals can use this to determine the SL DRX setting for the RX terminal.

[0123] Regardless of whether support information is provided or not, a TX terminal in RRC_IDLE / RRC_INACTIVE / OOC, or a TX terminal in RRC_CONNECTED that uses mode 2 resource allocation determines the SL DRX setting for the RX terminal. For a TX terminal in RRC_CONNECTED that uses mode 1 resource allocation, the SL DRX setting for the RX terminal is determined by the serving base station of the TX terminal.

[0124] - The TX terminal sends the RX terminal the SL DRX setting used by the RX terminal.

[0125] - The RX terminal accepts or rejects the SL DRX setting.

[0126] The basic SL DRX configuration for groupcast / broadcast is used for the DCR message.

[0127] When the TX terminal is in RRC_CONNECTED, the TX terminal reports the received support information to the serving base station, and when it receives the SL DRX setting with a dedicated RRC signal at the base station, it sends the SL DRX setting to the RX terminal. When the RX terminal is in RRC_CONNECTED, the RX terminal reports the received SL DRX setting to its serving base station, for example, for the alignment of the Uu setting and the SL DRX setting.

[0128] The SL on-duration timer, SL inactivity timer, SL HARQ RTT timer, and SL HARQ retransmission timer are supported for unicast. The SL HARQ RTT timer and SL HARQ retransmission timer are maintained for each SL process at the RX terminal. When the SCI indicates two or more transmission resources, in addition to the (pre)-set value for each of these timers, the SL HARQ RTT timer value is derived from the retransmission resource timing.

[0129] The SL DRX MAC CE is introduced for SL DRX operation with unicast only.

[0130] For groupcast / broadcast, SL DRX is commonly configured among multiple terminals based on the QoS profile and the destination L2 ID. Multiple SL DRX configurations can be supported for each groupcast / broadcast.

[0131] For groupcast, the SL on-duration timer, SL inactivity timer, SL HARQ RTT timer, and SL retransmission timer are supported. For broadcast, only the SL on-duration timer is supported. The SL DRX period, SL on-duration, and (applicable only to groupcast) SL inactivity timer are configured for each QoS profile. The start offset and slot offset of the SL DRX period are determined according to the destination L2 ID. The (applicable only to groupcast) SL HARQ RTT timer and the (applicable only to groupcast) SL HARQ retransmission timer are not configured for each QoS profile or destination L2 ID. In the case of groupcast, the RX terminal maintains an SL inactivity timer for each destination L2 ID and selects the maximum SL inactivity timer value when multiple SL inactivity timer values associated with different QoS profiles are configured for that L2 ID. In the case of groupcast and broadcast, when multiple QoS profiles are configured for each destination L2 ID, the RX terminal maintains a single SL DRX period (selected as the minimum SL DRX period of all QoS profiles of that L2 ID) and a single SL on-duration (selected as the maximum SL on-duration of all QoS profiles of that L2 ID) for that L2 ID.

[0132] In the case of groupcast, the SL HARQ RTT timer and the SL retransmission timer are maintained at the RX terminal for each SL process. The SL HARQ RTT timer may be set to different values from each other so as to support both HARQ enabled transmission and HARQ disabled transmission.

[0133] A common basic SL DRX setting between groupcast and broadcast is used for QoS profiles that are not mapped to non-default SL DRX settings.

[0134] TX terminals and RX terminals within the coverage of RRC_IDLE / RRC_INACTIVE obtain their SL DRX settings in the SIB. (TX or RX) terminals in RRC_CONNECTED obtain the SL DRX settings in the SIB or from dedicated RRC signals during handover. In the case of out-of-coverage, the SL DRX settings are obtained by pre-configuration.

[0135] In the case of groupcast, when a TX terminal receives new data with the same destination L2 ID, it resumes its timer corresponding to the SL inactivity timer for the destination L2 ID (used for determining the allowed transmission time).

[0136] The TX profile is introduced to ensure compatibility for groupcast and broadcast transmissions between terminals that support / do not support the SL DRX function. The TX profile is provided from the upper layer to the AS layer and identifies one or more SL function groups. The TX terminal assumes SL DRX for the RX terminal only when the relevant TX profile corresponds to SL DRX support. The RX terminal determines that SL DRX is used when there is a relevant TX profile corresponding to SL DRX support for all destination L2 IDs of interest.

[0137] For unicast, groupcast, and broadcast, alignment of Uu DRX and SL DRX for RRC_CONNECTED terminals is supported. Alignment of Uu DRX and SL DRX is supported for the same terminal. Also, in mode 1 scheduling, alignment of the Uu DRX of the TX terminal and the SL DRX of the RX terminal is supported.

[0138] Alignment is performed with overall or partial time overlap between Uu DRX and SL DRX. For the SL RX terminal in RRC_CONNECTED, alignment is performed at the base station.

[0139] The SL DRX function that controls the SCI (i.e., one-stage SCI and two-stage SCI) monitoring activities of the terminal for unicast, groupcast, and broadcast is set by RRC to the MAC entity. When using the SL DRX operation, the MAC entity also needs to monitor the SCI (i.e., one-stage SCI and two-stage SCI) according to the requirements in other sections of the present invention.

[0140] RRC sets the following parameters to control the SL DRX operation.

[0141] - sl-drx-onDurationTimer: Duration at the start of the SL DRX cycle

[0142] - sl-drx-SlotOffset: Delay time before the start of sl-drx-onDurationTimer

[0143] - sl-drx-InactivityTimer (except for broadcast transmissions): Period after the first slot of receiving an SCI (i.e., one-stage SCI and two-stage SCI) indicating a new SL transmission to the MAC entity

[0144] - sl-drx-RetransmissionTimer (per SL process except for broadcast transmissions): Maximum period until receiving an SL retransmission

[0145] - sl-drx-StartOffset: The slot at which the SL DRX cycle starts

[0146] - sl-drx-Cycle: SL DRX cycle

[0147] - sl-drx-HARQ-RTT-Timer (per SL process excluding broadcast transmission): The minimum period before the MAC entity anticipates an SL HARQ retransmission

[0148] When SL DRX is configured, the active time includes the following times.

[0149] - The time when the sl-drx-onDurationTimer or sl-drx-InactivityTimer runs, or

[0150] - The time when the sl-drx-RetransmissionTimer runs, or

[0151] - When no SL-CSI report MAC CE is received, the sl-LatencyBoundCSI-Report interval set by RRC, or

[0152] - When an SL-CSI report MAC CE is received, the time between the SL-CSI report request transmission and the SL-SCI report MAC CE reception, or

[0153] - The slots related to the known periodic transmissions of the terminal transmitting SL-SCH data.

[0154] When one or more SL DRXs are configured, the MAC entity performs the following.

[0155] 1> When multiple SL DRX periods mapped to multiple SL-QoS-Profile of destination Layer-2 ID and interest cast type are related to group cast and broadcast:

[0156] 2> Among multiple SL DRX periods mapped to multiple SL-QoS-Profile related to destination Layer-2 ID, select the sl-drx-Cycle with the shortest length.

[0157] 2> Among multiple SL DRX onduration timers mapped to multiple SL-QoS-Profile related to destination Layer-2 ID, select the sl-drx-onDurationTimer with the longest length.

[0158] 1> When the sl-drx-HARQ-RTT-Timer expires:

[0159] 2> If the data of the SL process is not successfully decoded or the HARQ feedback (i.e., negative acknowledgment) is not unicast according to the UL / SL priority:

[0160] 3> After the sl-drx-HARQ-RTT-Timer expires, start the sl-drx-RetransmissionTimer for the SL process in the first slot.

[0161] When the cast type is group cast or broadcast as instructed by the upper layer, sl-drx-StartOffset and sl-drx-SlotOffset are derived from the following formula.

[0162] sl-drx-StartOffset (ms) = Destination Layer-2 ID modulo sl-drx-Cycle (ms).

[0163] sl-drx-SlotOffset (ms) = Destination Layer-2 ID modulo sl-drx-onDurationTimer (ms).

[0164] 1> When the SL DRX cycle is used and [(DFN Х 10) + subframe number] modulo (sl-drx-Cycle) = sl-drx-StartOffset:

[0165] 2> Start sl-drx-onDurationTimer after sl-drx-SlotOffset from the subframe start.

[0166] 1> When SL DRX is the active time:

[0167] 2> Monitor the SCI (i.e., one-stage SCI and two-stage SCI) in this SL DRX.

[0168] 2> When the SCI indicates a new SL transmission:

[0169] 3> When the source Layer-1 ID of the SCI is equal to the 8 LSBs of the intended destination Layer-2 ID, the destination Layer-1 ID of the SCI is equal to the 8 LSBs of the intended source Layer-2 ID, and the cast type indicator of the SCI is set to unicast:

[0170] 4> Start or resume sl-drx-InactivityTimer for the source Layer-2 ID and destination Layer-2 ID pair after the first slot of the SCI reception.

[0171] 3> When the destination Layer-1 ID of the SCI (i.e., two-stage SCI) is equal to the 8 LSBs of the intended destination Layer-1 ID and the cast type indicator of the SCI is set to groupcast:

[0172] 4> Select the sl-drx-InactivityTimer with the longest length among the multiple SL DRX inactivity timers mapped to the multiple SL-QoS-Profile of the destination Layer-2 ID related to the destination Layer-1 ID of the SCI.

[0173] 4> After the first slot of SCI reception, start or resume the sl-drx-InactivityTimer for the destination Layer-2 ID.

[0174] 2> If the SCI indicates an SL transmission:

[0175] 3> If no PSFCH resource is configured for the SL grant related to the SCI:

[0176] 4> Start the sl-drx-HARQ-RTT-Timer for the SL process in the slot after the transmission of the PSSCH (i.e., the currently received PSSCH) is completed.

[0177] 3> If a PSFCH resource is configured for the SL grant related to the SCI:

[0178] 4> When HARQ feedback is activated by the SCI and the cast type indicator of the SCI is set to unicast; or, 4> When HARQ feedback is activated by the SCI, the cast type indicator of the SCI is set to groupcast, and positive-negative acknowledgment is selected;

[0179] 5> After the transmission of the PSFCH for transmitting the SL HARQ feedback is completed, start the sl-drx-HARQ-RTT-Timer for the SL process in the first slot. Or

[0180] 5> When the SL HARQ feedback is not transmitted according to the UL / SL priority, after the PSFCH resource for the SL HARQ feedback is terminated, start the sl-drx-HARQ-RTT-Timer for that SL process in the first slot.

[0181] 4> When HARQ feedback is activated in the SCI, the cast type indicator of the SCI is set to group cast, and only negative-only acknowledgment is selected;

[0182] 5> After the PSFCH transmission for transmitting the SL HARQ feedback is completed, start the sl-drx-HARQ-RTT-Timer for that SL process in the first slot. Or

[0183] 5> When the SL HARQ feedback is not transmitted according to the UL / SL priority, after the PSFCH resource for the SL HARQ feedback is terminated, start the sl-drx-HARQ-RTT-Timer for that SL process in the first slot. Or

[0184] 5> When the SL HARQ feedback is an affirmative acknowledgment, after the PSFCH resource for the SL HARQ feedback is terminated, start the sl-drx-HARQ-RTT-Timer for that SL process in the first slot.

[0185] 4> When the SCI deactivates the HARQ feedback and the resources for one or more retransmission opportunities are not scheduled by the SCI:

[0186] 5> Start the sl-drx-HARQ-RTT-Timer for that SL process in the slot after the PSFCH resource is terminated.

[0187] 4> If HARQ feedback is deactivated in the SCI and resources for one or more retransmission opportunities are scheduled by the SCI:

[0188] 5> Start the sl-drx-HARQ-RTT-Timer for that SL process in the slot after the transmission of the PSSCH (i.e., the currently received PSSCH) has ended.

[0189] Reference: When the SCI indicates the next retransmission resource, the sl-drx-HARQ-RTT-Timer is derived from the retransmission resource timing (i.e., the very next retransmission resource indicated by the SCI). The terminal uses the configured sl-drx-HARQ-RTT-Timer when the SCI does not indicate the next transmission resource.

[0190] 3> Abort the sl-drx-RetransmissionTimer for that SL process.

[0191] 1> If an SL DRX command MAC CE for a unicast source Layer-2 ID and destination Layer-2 ID pair is received:

[0192] 2> Abort the sl-drx-onDurationTimer for the unicast source Layer-2 ID and destination Layer-2 ID pair.

[0193] 2> Abort the sl-drx-InactivityTimer for the unicast source Layer-2 ID and destination Layer-2 ID pair.

[0194] Inter-UE Coordination (IUC)

[0195] The SL terminal assists in inter-UE coordination (IUC) in mode 2. Here, terminal-A sends information about resources to terminal-B, and terminal-B uses this for resource (re)selection. The following inter-UE coordination methods are supported.

[0196] - IUC mode 1. The adjustment information transmitted from terminal - A to terminal - B indicates the preferred and / or non - preferred resources for the transmission of terminal - B.

[0197] - IUC mode 2. The adjustment information transmitted from terminal - A to terminal - B indicates the existence of expected / potential resource collisions for the resources indicated by the SCI of terminal - B.

[0198] In mode 1, the IUC can be triggered by an explicit request from terminal - B or the state of terminal - A. Terminal - A determines a set of resources reserved by other terminals or a set of slots that are not expected to receive SL from terminal - B when terminal - A is the intended receiver of terminal - B and terminal - A operates in half - duplex mode. Terminal - A either uses this resource as the non - preferred resource set or excludes this resource to determine the preferred resource set, and transmits the preferred / non - preferred resources to terminal - B. The resources of terminal - B for (re)selection may be based on the detection result of terminal - B (if available) and the adjustment information received at terminal - A, or may be based only on the adjustment information received at terminal - A. In the case of mode 1, the IUC can be transmitted using MAC CE and two - stage SCI or MAC CE only. The explicit request and report for the IUC are supported in unicast mode.

[0199] In mode 2, terminal - A determines the resources that are reserved by other terminals and are identified as completely / partially overlapping with the resources indicated by the SCI of terminal - B at terminal - A, or the slots that are not expected to receive SL in that slot by half - duplex operation when terminal - A is the intended receiver of terminal - B, as the expected / potential collision resources within the resources indicated by the SCI of terminal - B. Terminal - B determines the resources to re - select using the collision resources and excludes the collision resources from the re - selected resources. In the case of mode 2, the IUC is transmitted using PSFCH.

[0200] The procedure for transmitting the adjustment request (SL-IUC Req) between SL terminals is used to trigger the transmission of adjustment information between SL terminals of the peer UE.

[0201] The procedure for reporting the adjustment information (SL-IUC Info) between SL terminals is used to provide the adjustment information between terminals to the peer UE.

[0202] - sl-LatencyBoundIUC-Report is maintained for each PC5-RRC connection.

[0203] The MAC entity maintains sl-IUC-ReportTimer for each pair of source Layer-2 ID and destination Layer-2 ID corresponding to the PC5-RRC connection. The sl-IUC-ReportTimer is used for the SL-IUC information reporting terminal to comply with the delay requirement notified by the IUC-Information triggering terminal. The value of the sl-IUC-ReportTimer is the same as the delay requirement for the SL-IUC information of sl-LatencyBoundIUC-Report set in RRC.

[0204] The MAC entity performs the following for each pair of source Layer-2 ID and destination Layer-2 ID corresponding to the PC5-RRC connection set in the upper layer.

[0205] 1> When the SL-IUC information report is triggered by the SL-IUC request MAC CE (and / or SCI) and has not been cancelled:

[0206] 2> When the sl-IUC-ReportTimer is not running for the triggered SL-IUC information report:

[0207] 3> Start the sl-IUC-ReportTimer.

[0208] 2> When the sl-IUC-ReportTimer has expired for the triggered SL-IUC information report:

[0209] 3> Cancel the triggered SL-IUC information report.

[0210] 2> Otherwise, if the MAC entity has the SL resources assigned to a new transmission and, as a result of logical channel prioritization, the SL-SCH resources can accommodate the SL-IUC information MAC CE and its subheader:

[0211] 3> As defined in 6.1.3.35, instruct to generate the adjustment information MAC CE between SL terminals in the multiplexing and assembly procedures.

[0212] 3> Abort the sl-IUC-ReportTimer for the triggered SL-IUC information report.

[0213] 3> Cancel the triggered SL-IUC information report.

[0214] Figure 9 shows the adjustment information MAC CE between terminals.

[0215] The adjustment information MAC CE between terminals is identified by a MAC subheader having the LCID specified in Table 5.

[0216]

Table 5

[0217] The priority of the adjustment information MAC CE between terminals is fixed at "1". The adjustment information MAC CE between terminals has a variable size and includes the following fields.

[0218] - RT: This field is the code point value of the SCI format 2-C resourceSetType field and indicates the resource set type, i.e., the preferred resource set or the non-preferred resource set.

[0219] - RSL: This field is the code point value of the SCI format 2-C referenceSlotLocation field, indicating the position of the reference slot. The length of this field is 17 bits. If the length of the referenceSlotLocation field in SCI format 2-C is shorter than 17 bits, this field contains the referenceSlotLocation field using the LSB bits.

[0220] - LSIi: This field is the code point value of the SCI format 2-C lowestIndices field, indicating the lowest subchannel index for the first resource position of each TRIV. LSI0 indicates the lowest subchannel index for the first resource position of TRIV within the first resource combination, and LSI1 indicates the lowest subchannel index for the first resource position of TRIV within the second resource combination. The length of this field is 5 bits. If the length of the lowestIndices field in SCI format 2-C is shorter than 5 bits, this field contains the lowestIndices field using the LSB bits.

[0221] - RCi: This field is the code point value of the SCI format 2-C resourceCombination field, indicating the resource combination. RC0 indicates the first resource combination, and RC1 indicates the second resource combination. [The maximum number of resource combinations included is 8.] The length of this field is 26 bits. If the length of the resourceCombination field in SCI format 2-C is shorter than 26 bits, this field contains the resourceCombination field using the LSB bits.

[0222] - First resource locationi-1: This field is the code point value of the SCI format 2-C firstResourceLocation field and indicates the first resource location. First Resource location0 indicates the first resource location of the second resource combination, and First Resource location1 indicates the first resource location of the third resource combination. The length of the field is 13 bits. If the length of the firstResourceLocation field in SCI format 2-C is shorter than 13 bits, this field includes the firstResourceLocation field using the LSB bit.

[0223] - R: Reserved bit, set to 0.

[0224] Figure 10 shows the adjustment request MAC CE between terminals.

[0225] The adjustment request MAC CE between terminals is identified by a MAC sub-header with the LCID specified in Table 5. The priority of the adjustment request MAC CE between terminals is fixed at "1". The adjustment request MAC CE between terminals has a variable size and includes the following fields.

[0226] - RT: This field is the code point value of the SCI format 2-C resourceSetType field and indicates the resource set type, i.e., the preferred resource set or the non-preferred resource set.

[0227] - RP: This field is the code point value of the SCI format 2-C resourceReservationPeriod field and indicates the resource reservation period. The length of the field is 4 bits. If the length of the resourceReservationPeriod field in SCI format 2-C is shorter than 4 bits, this field includes the resourceReservationPeriod field using the LSB bit.

[0228] - Priority: This field is the code point value of the SCI format 2-C priority field, indicating the priority. The length of the field is 3 bits.

[0229] - RSWL: This field is the code point value of the SCI format 2-C resourceSelectionWindowLocation field, indicating the position of the resource selection window. The length of the field is 34 bits. If the length of the resourceSelectionWindowLocation field in SCI format 2-C is shorter than 34 bits, this field contains the resourceSelectionWindowLocation field using the LSB bits.

[0230] - Number of Subchannel: This field is the code point value of the SCI format 2-C numberOfSubchannel field, indicating the number of subchannels. The length of the field is 5 bits. If the length of the numberOfSubchannel field in SCI format 2-C is shorter than 5 bits, this field contains the numberOfSubchannel field using the LSB bits.

[0231] - R: Reserved bit, set to 0.

[0232] SL relay

[0233] The SL relay was introduced to support the 5G ProSe terminal-network relay (U2N relay) function that provides network connection to the U2N remote terminal. Both L2 and L3 U2N relay architectures are supported. The L3 U2N relay architecture is transparent to the serving RAN of the U2N relay terminal except for SL resource control.

[0234] Relay Discovery: An AS function that activates UE-to-Network Relay Discovery between 5G ProSe terminals that use NR technology and do not go through network nodes.

[0235] U2N Relay Terminal: A terminal that provides a function to assist in network connection to U2N remote terminals.

[0236] U2N Remote Terminal: A terminal that communicates with the network through a U2N relay terminal.

[0237] Upstream: The direction from the IAB topology towards the parent node.

[0238] Uu Relay RLC Channel: An RLC channel between the L2 U2N relay terminal and the base station, which is used to transmit packets via Uu for relay between the L2 terminal and the network.

[0239] The U2N relay terminal needs to be in the RRC_CONNECTED state to relay unicast data.

[0240] For L2 U2N relay operation, the following combinations of RRC states are supported.

[0241] - Only when both the U2N relay terminal and the U2N remote terminal are in the RRC CONNECTED state can they send and receive relayed unicast data.

[0242] - When all U2N remote terminals connected to the U2N relay terminal are in RRC_INACTIVE or RRC_IDLE, the U2N relay terminal can be in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED.

[0243] In the case of L2 U2N relay, the U2N remote terminal is set to use only resource allocation mode 2 for the data to be relayed.

[0244] A single unicast link is established between one L2 U2N relay terminal and one L2 U2N remote terminal. The traffic of the U2N remote terminal and the traffic of the U2N relay terminal via a given U2N relay terminal need to be separated into different Uu RLC channels on Uu.

[0245] Protocol stack of SL relay

[0246] Figure 11 shows (a) the user plane protocol stack and (b) the control plane protocol stack of the L2 terminal - network relay.

[0247] The protocol stacks for the user plane and control plane of the L2 U2N relay architecture are shown in Figures 11(a) and (b). The SRAP sub - array is placed on the RLC sub - layer for both CP and UP in both the PC5 interface and the Uu interface. Uu SDAP, PDCP, and RRC are terminated between the L2 U2N remote terminal and the base station, while SRAP, RLC, MAC, and PHY are terminated at each hop (i.e., the link between the L2 U2N remote terminal and the L2 U2N relay terminal and the link between the L2 U2N relay terminal and the base station).

[0248] In the case of the L2 U2N relay, the SRAP sub - layer over the PC5 hop is for bearer mapping only. The SRAP sub - layer does not exist on the PC5 hop for relaying the messages of the L2 U2N remote terminal in BCCH and PCCH. In the case of the L2 U2N remote terminal messages of SRB0, the SRAP sub - layer does not exist on the PC5 hop, but the SRAP sub - layer exists on the Uu hop for both DL and UL.

[0249] In the case of the L2 U2N relay, uplink:

[0250] - The Uu SRAP sublayer assists in the UL bearer mapping between the receiving PC5 relay RLC channel and the transmitting Uu relay RLC channel for relay via the L2 U2N relay terminal Uu interface. In the case of uplink relay traffic, other end-to-end RBs (SRB or DRB) of the same remote terminal and / or other terminals of other remote terminals are multiplexed via the same Uu relay RLC channel.

[0251] - The Uu SRAP sublayer assists in identifying the L2 U2N remote terminal for UL traffic. The ID information of the L2 U2N remote terminal Uu radio bearer and the local remote terminal ID are included in the UL Uu SRAP header so that the base station can correlate the received packets with the specific PDCP entity associated with the correct Uu radio bearer of the remote terminal.

[0252] - The PC5 SRAP sublayer of the L2 U2N remote terminal assists in the UL bearer mapping between the remote terminal Uu radio bearer and the transmitting PC5 relay RLC channel.

[0253] For the L2 U2N relay, in the downlink:

[0254] - The Uu SRAP sublayer assists in the DL bearer mapping at the base station to map the radio bearers (SRB, DRB) between the terminals of the remote terminal to the Uu relay RLC channel via the relay terminal Uu interface. The Uu SRAP sublayer assists in the DL bearer mapping and data multiplexing between multiple radio bearers (SRB or DRB) of the L2 U2N remote terminal and / or other L2 U2N remote terminals and one Uu Relay RLC channel via the relay terminal Uu interface.

[0255] - The Uu SRAP sublayer assists in identifying remote terminals for DL traffic. The ID information of the remote terminal Uu radio bearer and the local remote terminal ID are included in the Uu SRAP header by the base station in the DL so that the relay terminal maps the packets received in the remote terminal Uu radio bearer to the associated PC5 Relay RLC channel.

[0256] - The PC5 SRAP sublayer of the relay terminal assists in DL bearer mapping between the received Uu Relay RLC channel and the transmitted PC5 Relay RLC channel.

[0257] - The PC5 SRAP sublayer of the remote terminal correlates the received packets to the specific PDCP entity associated with the correct Uu radio bearer of the remote terminal based on the ID information contained in the Uu SRAP header.

[0258] The local remote terminal ID is included in both the PC5 SRAP header and the Uu SRAP header. The local remote terminal ID used for the SRAP header by the base station is set in the L2 U2N relay terminal. The remote terminal obtains the local remote ID from the base station by Uu RRC messages including RRCSetup, RRCReconfiguration, RRCResume, and RRCReestablishment. Uu DRB and Uu SRB are mapped to other PC5 relay RLC channels and Uu relay RLC channels in both the PC5 hop and the Uu hop.

[0259] The base station is responsible for preventing collisions in the use of the local remote terminal ID. The base station can update the local remote terminal ID by transmitting the updated local remote ID to the relay terminal by the RRCReconfiguration message. The serving base station can perform local remote terminal ID updates independently of the procedure for updating the PC5 unicast link L2 ID.

[0260] FIG. 12 shows a protocol stack of discovery messages for relay between a terminal and a network.

[0261] For U2N relay discovery, discovery models of Model A and Model B are supported. The protocol stack used for discovery is shown in FIG. 12.

[0262] The U2N remote terminal can send a relay discovery message and can monitor the SL for relay discovery messages while in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED. The network can broadcast a threshold, which is used to determine whether the U2N remote terminal can send a Relay discovery solicitation message to the U2N relay terminal.

[0263] The U2N relay terminal can send a relay discovery message and can monitor the SL for relay discovery messages while in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED. The network can broadcast the maximum Uu RSRP threshold, the minimum Uu RSRP threshold, or both, which are used to determine whether the U2N relay terminal can send a relay discovery message to the U2N remote terminal.

[0264] The network can provide relay discovery settings using broadcast or dedicated signaling for relay discovery. Also, the U2N remote terminal and the U2N relay terminal can use pre-configurations for relay discovery.

[0265] For relay discovery, a resource pool used for NR SL communication may be employed, or the network can configure a resource pool dedicated to relay discovery. The resource pool dedicated to relay discovery and the resource pool for NR SL communication can be configured simultaneously through system information, dedicated signaling, and / or pre-configuration. Whether a resource pool dedicated to relay discovery is configured depends on the implementation of the network. If a resource pool dedicated to relay discovery is configured, only the resource pool dedicated to relay discovery is used for relay discovery. If only the resource pool for NR SL communication is configured, all configured transmission resource pools can be used for relay discovery and SL communication.

[0266] In the case of a U2N remote terminal connected to the network by a U2N relay terminal (including both within and outside the coverage), only resource allocation mode 2 is used for transmitting discovery messages.

[0267] Relay discovery re-uses the NR SL resource allocation principle for U2N relay terminals within the coverage and the NR SL resource allocation principle for all U2N remote terminals both within and outside the coverage.

[0268] SL power control for transmitting relay discovery messages is performed in the same way as NR SL communication.

[0269] PDCP layer encryption or integrity protection is not applied to relay discovery messages.

[0270] The terminal determines whether the base station supports relay discovery, non-relay discovery, or both through SIB12.

[0271] Relay selection / reselection

[0272] The U2N remote terminal performs radio measurements at the PC5 interface and uses this together with upper layer criteria for U2N relay selection and reselection. If there is no unicast PC5 connection between the U2N relay terminal and the U2N remote terminal, the U2N remote terminal evaluates whether the PC5 link quality to the U2N relay terminal meets the relay selection criteria using SD-RSRP measurements.

[0273] For relay reselection, if there is data transmission from the U2N relay terminal to the U2N remote terminal, the U2N remote terminal uses SL-RSRP measurements for the serving U2N relay terminal for relay reselection trigger evaluation. If there is no data transmission from the U2N relay terminal to the U2N remote terminal, whether to use SL-RSRP or SD-RSRP for relay reselection trigger evaluation depends on the implementation of the terminal.

[0274] If the PC5 link quality measured by the U2N remote terminal for the U2N relay terminal exceeds a set threshold (pre-set or provided by the base station), the U2N remote terminal considers the U2N relay terminal suitable from the radio criteria aspect. The U2N remote terminal searches for appropriate U2N relay terminal candidates that meet all AS layer and upper layer criteria (see TS 23.304[xx]). If there are multiple appropriate U2N relay terminals, selecting one of them depends on the implementation of the U2N remote terminal. For L2 U2N relay (re)selection, the PLMN ID and cell ID can be used as additional AS criteria.

[0275] In the following cases, the U2N remote terminal triggers U2N relay selection.

[0276] - When the direct Uu signal strength of the current serving cell of the U2N remote terminal is lower than the set signal strength threshold.

[0277] - When instructed by the upper layer of the U2N remote terminal.

[0278] In the following cases, the U2N remote terminal triggers U2N relay reselection.

[0279] - When the PC5 signal strength of the current U2N relay terminal is lower than the (pre-set) signal strength threshold.

[0280] - When the U2N relay terminal notifies cell (re)selection, handover or Uu RLF by the PC5-RRC signal.

[0281] - When the remote terminal receives a PC5-S link release message from the U2N relay terminal.

[0282] - When the U2N remote terminal detects PC5 RLF.

[0283] - When instructed by the upper layer.

[0284] For the L2 U2N remote terminal and the L3 U2N remote terminal in RRC_IDLE / INACTIVE, the cell (re)selection procedure and the relay (re)selection procedure are performed independently. If both a suitable cell and a suitable U2N relay terminal are available, the terminal implementation selects either the cell or the U2N relay terminal. The L3 U2N remote terminal can select a cell and a U2N relay terminal simultaneously, which varies depending on the implementation of the L3 U2N remote terminal.

[0285] For the L2 and L3 U2N relay terminals in RRC_IDLE / INACTIVE, when the U2N relay terminal selects a new cell, a PC5-RRC message is used to notify the connected remote terminal. The PC5-RRC message is also used to notify the connected L2 or L3 U2N remote terminal when the L2 / L3 U2N relay terminal performs a handover or detects Uu RLF. When receiving the PC5 RRC message for notification, whether to release or maintain the unicast PC5 link depends on the implementation of the U2N remote terminal. If the U2N remote terminal decides to release the unicast PC5 link, it can trigger the L2 release procedure and perform relay reselection.

[0286] Control plane procedure for L2 U2N relay

[0287] 1) RRC Connection Management

[0288] The U2N remote terminal needs to configure its PDU session / DRB with the network before transmitting user plane data.

[0289] Before the U2N remote terminal configures the Uu RRC connection with the network via the U2N relay terminal, the NR V2X PC5 unicast link setup procedure is reused to set up a secure unicast link between the U2N remote terminal and the U2N relay terminal.

[0290] The Uu configuration procedure for relay between the L2 terminal and the network is applied to the configuration of the Uu SRB1 / SRB2 and DRB of the U2N remote terminal.

[0291] Figure 13 shows the L2 U2N remote terminal connection setup procedure. The following high-level connection setup procedure in Figure 13 is applicable to the L2 U2N relay.

[0292] 1. The U2N remote terminal and the U2N relay terminal perform a discovery procedure and configure the PC5-RRC connection using the NR V2X procedure.

[0293] 2. The U2N remote terminal uses the specified PC5 relay RLC channel settings to send the first RRC message (i.e., RRC Setup Request) for its connection settings with the base station by the relay terminal. When the U2N relay terminal is not in RRC_CONNECTED, it needs to perform its connection settings when receiving a message on the specified PC5 relay RLC channel. During the RRC connection setup procedure of the relay terminal, the base station can set up the Uu relay RLC channel that relays SRB0 for the U2N relay terminal. The base station responds to the U2N remote terminal with an RRC Setup message. The RRC Setup message is sent to the U2N remote terminal using the SRB0 relay channel via Uu and the specified PC5 relay RLC channel via PC5.

[0294] 3. The base station and the U2N relay terminal perform a relay channel setup procedure via Uu. According to the settings from the base station, the U2N relay / remote terminal sets up the PC5 relay RLC channel for relaying SRB1 to the U2N remote / relay terminal via PC5.

[0295] 4. The RRC Setup Complete message is sent from the U2N remote terminal to the base station by the U2N relay terminal using the SRB1 relay channel via PC5 and the SRB1 relay channel set for the U2N relay terminal via Uu. Thereafter, the U2N remote terminal is RRC-connected via Uu.

[0296] 5. The U2N remote terminal and the base station set up security through the Uu procedure, and the security message is relayed by the U2N relay terminal.

[0297] 6. The base station sends an RRCReconfiguration message to the U2N remote terminal via the U2N relay terminal to configure the SRB2 / DRB for relay purposes. The U2N remote terminal sends an RRCReconfigurationComplete message to the base station via the U2N relay terminal as a response. Also, the base station further configures the Uu relay RLC channel between the base station and the U2N relay terminal, and configures the PC5 relay RLC channel between the U2N relay terminal and the U2N remote terminal for relay traffic.

[0298] 2) Radio Link Failure

[0299] When the U2N remote terminal in RRC_CONNECTED is connected to the base station by the U2N relay terminal, it suspends the Uu RLM.

[0300] The U2N relay terminal declares a radio link failure (RLF) according to the same criteria.

[0301] After the RLF is declared, the U2N relay terminal performs the following operations.

[0302] - A PC5-RRC message is used to send an instruction to the U2N remote terminal connected to the U2N relay terminal, which triggers an RRC connection reconfiguration for the U2N remote terminal.

[0303] When detecting the PC5 RLF, the U2N remote terminal triggers a connection reconfiguration.

[0304] 3) RRC Connection Reconfiguration

[0305] The U2N remote terminal performs the following operations during the RRC connection reconfiguration procedure.

[0306] - If only an appropriate cell is available, the U2N remote terminal starts the RRC reconfiguration procedure for the appropriate cell.

[0307] - When only a suitable U2N relay terminal is available, the U2N remote terminal starts an RRC reconfiguration procedure for the serving cell of the suitable relay terminal as appropriate.

[0308] - When both a suitable cell and a suitable relay are available, the U2N remote terminal selects one of the two to start the RRC reconfiguration procedure according to the implementation.

[0309] 4) RRC connection resume

[0310] The RRC connection resume mechanism is applied to the U2N remote terminal.

[0311] 5) System information

[0312] U2N remote terminals within the coverage can obtain all necessary SIBs via the Uu interface regardless of the PC5 connection with the relay terminal. The U2N remote terminal may receive system information from the relay terminal after the PC5 connection with the U2N relay terminal is established.

[0313] U2N remote terminals in the RRC_CONNECTED state can request SIBs from the U2N relay terminal using the on-demand SIB framework. U2N remote terminals in the RRC_IDLE or RRC_INACTIVE state can inform the U2N relay terminal of the SIB types requested by the PC5-RRC message. Subsequently, the U2N relay terminal triggers the on-demand SI / SIB acquisition procedure according to its own RRC state (if necessary) and sends the SI / SIBs obtained by the PC5-RRC to the U2N remote terminal.

[0314] The SIBs used by an RRC_IDLE or RRC_INACTIVE U2N remote terminal (for example, for the purpose of a relay) can be requested by the U2N remote terminal (from the U2N relay terminal or the network). In the case of the SIBs requested by the U2N remote terminal from the U2N relay terminal, if there is an update to the requested SIBs, the U2N relay terminal will re-transmit them. In the case of an RRC_CONNECTED U2N remote terminal, it is the responsibility of the network to send the updated SIBs to the U2N remote terminal during an update. When the U2N remote terminal enters the RRC_CONNECTED state, it releases the SI request with the U2N relay terminal.

[0315] In the case of SIB1 transmission, both the request-based transmission (i.e., the SIB1 request of the U2N remote terminal) and the unrequested transmission to the U2N remote terminal are supported by the U2N relay terminal, and its use is implemented by the U2N relay terminal. When SIB1 is changed, the U2N relay terminal always transmits SIB1 to the U2N remote terminal in the RRC_IDLE or RRC_INACTIVE state.

[0316] For an L2 U2N remote terminal in the RRC_IDLE or RRC_INACTIVE state, short messages via the Uu interface are not transmitted from the L2 U2N relay terminal to the L2 U2N remote terminal. The L2 U2N relay terminal can transmit the PWS SIB to the L2 U2N remote terminal connected to it.

[0317] RAN sharing is supported by the L2 U2N relay terminal. In particular, the L2 U2N relay terminal can transmit information related to cell access by means of a discovery message before setting up a PC5-RRC connection.

[0318] 6) Paging

[0319] When both the U2N relay terminal and the U2N remote terminal are in the RRC IDLE or RRC INACTIVE state, the U2N relay terminal monitors the paging occasions of the U2N remote terminal connected to it. If the U2N relay terminal needs to monitor paging for the U2N remote terminal, the U2N relay terminal must monitor all the POs of the U2N remote terminal.

[0320] When the U2N relay terminal is in the RRC CONNECTED state and the U2N remote terminal is in the RRC_IDLE or RRC_INACTIVE state, there are two options for paging transmission.

[0321] - If a CORESET and a paging search space are configured in the active DL BWP of the U2N relay terminal, the U2N relay terminal monitors the POs of the U2N remote terminal connected to it.

[0322] - The paging transmission of the U2N remote terminal can be carried out by a dedicated RRC message from the base station to the U2N relay terminal. The dedicated RRC message for transmitting remote terminal paging to the RRC_CONNECTED relay terminal contains one or more remote terminal IDs (5G-S-TMSI or I-RNTI).

[0323] Which of the two options described above is used depends on the implementation of the network. When a paging search space is configured for the RRC CONNECTED U2N relay terminal, it is possible to determine whether to monitor the POs for the U2N remote terminal based on the PC5-RRC signal received by the U2N remote terminal.

[0324] The U2N remote terminal in RRC_IDLE requests the U2N relay terminal to perform PO monitoring by providing the 5G-S-TMSI (configured at the upper layer) and the terminal-specific DRX cycle. The U2N remote terminal in RRC_INACTIVE provides the minimum value of the two terminal-specific DRX cycles (configured at the upper layer and set by the RAN), the 5G-S-TMSI, and the I-RNTI to the U2N relay terminal for PO monitoring. The L2 U2N relay terminal can inform the base station of the remote terminal information (i.e., 5G-S-TMSI / I-RNTI) via the SidelinkUEInformationNR message for paging transmission purposes. The U2N relay terminal receives the paging message, verifies the 5G-S-TSMI / I-RNTI, and transmits the relevant paging record to the remote terminal accordingly.

[0325] The U2N relay terminal can transmit paging to the U2N remote terminal via PC5 using unicast signaling.

[0326] 7) Access Control

[0327] The U2N remote terminal performs unified access control (UAC). The U2N relay terminal in RRC-CONNECTED does not perform UAC on the data of the U2N remote terminal.

[0328] 8) Mobility Registration Update and RAN Area Update

[0329] When the L2 U2N remote terminal is connected to the L2 U2N relay terminal, it performs a mobility registration update / RNAU based on the serving cell of the L2 U2N relay terminal. If the serving cell of the L2 U2N remote terminal in the RRC_IDLE or RRC_INACTIVE state is changed (due to cell change by the U2N relay terminal) and the new serving cell is outside the configured RNA / TA of the U2N remote terminal, it starts the mobility registration update / RNAU procedure.

[0330] Service continuity for L2 U2N relay

[0331] 1) Switching from an indirect path to a direct path

[0332] Figure 14 shows the procedure for the U2N remote terminal to switch directly to the Uu cell.

[0333] For the service continuity of the L2 U2N relay, when the U2N remote terminal switches to the direct path, the following procedure is performed.

[0334] 1. The Uu measurement setup and measurement reporting signaling procedures are performed to evaluate both the relay link measurement and the Uu link measurement. When the configured measurement reporting criteria are met, the measurement results of the U2N remote terminal are reported. The SL relay measurement report should include at least the source L2 ID of the U2N relay terminal, the serving cell ID (i.e., NCGI), and the SL measurement quantity information. The SL measurement quantity is the SL-RSRP of the serving U2N relay terminal, and if SL-RSRP is not available, SD-RSRP is used.

[0335] 2. The base station decides to switch the U2N remote terminal to the direct Uu path.

[0336] 3. The base station sends an RRCReconfiguration message to the U2N remote terminal. After receiving the RRCReconfiguration message from the base station, the U2N remote terminal aborts the UP and CP transmissions by the U2N relay terminal.

[0337] 4. The U2N remote terminal performs random access in synchronization with the base station.

[0338] 5. The terminal (i.e., the previous-stage U2N remote terminal) uses the settings provided in the RRCReconfiguration message to send RRCReconfigurationComplete to the base station via the direct path. From this stage, the terminal (i.e., the previous-stage U2N remote terminal) uses the RRC connection via the direct path to the base station.

[0339] 6. The base station sends an RRCReconfiguration message to the U2N relay terminal to reconfigure the connection between the U2N relay terminal and the base station. The RRCReconfiguration message to the U2N relay terminal is sent at any time after three steps by the implementation of the base station (e.g., to release the Uu and PC5 relay RLC channel settings for relaying and the bearer mapping settings between PC5 RLC and Uu RLC).

[0340] 7. The U2N relay terminal or the U2N remote terminal initiates PC5 unicast link release (PC5-S). The timing of link release depends on the implementation of the terminal. When the base station receives RRC Reconfiguration in step 6, the U2N relay terminal performs PC5 connection reconfiguration to release the PC5 relay RLC channel for relaying, or when the base station receives RRCReconfiguration in step 3, the terminal (i.e., the previous U2N remote terminal) performs PC5 connection reconfiguration to release the PC5 relay RLC channel.

[0341] 8. The data path is switched from the indirect path to the direct path between the terminal (i.e., the previous U2N remote terminal) and the base station. During the path switch, DL / UL lossless transmission is performed according to the PDCP data recovery procedure.

[0342] Reference: The 8th step can be performed at any time after the 4th step. The 8th step is independent of the 6th and 7th steps.

[0343] 2) Switching from the direct path to the indirect path

[0344] Figure 15 shows the procedure for the U2N remote terminal to switch to the indirect path.

[0345] The base station can select a U2N relay terminal in any RRC state, such as RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED, as the target U2N relay terminal for the direct-indirect path switch.

[0346] For the service continuity of the L2 U2N remote terminal, when the L2 U2N remote terminal is switched to the indirect path by a U2N relay terminal in the RRC_CONNECTED state, the following procedure is performed.

[0347] 1. After the U2N remote terminal measures / finds candidate U2N relay terminals, it reports one or more candidate U2N relay terminals and Uu measurement values.

[0348] - The terminal can appropriately filter the U2N relay terminals according to the relay selection criteria before reporting. The terminal only needs to report the U2N relay terminal candidates that meet the upper layer criteria.

[0349] - The report includes at least the U2N relay terminal ID, the serving cell ID of the U2N relay terminal, and the SL measurement quantity information. The SL measurement quantity is the SL-RSRP of the candidate U2N relay terminal, and when the SL-RSRP is not available, the SD-RSRP is used.

[0350] 2. The base station decides to switch the U2N remote terminal to the target U2N relay terminal. Thereafter, the base station sends an RRCReconfiguration message to the target U2N relay terminal. This includes at least the local ID and L2 ID of the remote terminal, Uu and PC5 relay RLC channel settings for relaying, and bearer mapping settings.

[0351] 3. The base station sends an RRCReconfiguration message to the U2N remote terminal. The content of the RRCReconfiguration message includes at least the U2N relay terminal ID, PC5 relay RLC channel settings for relay traffic, and the radio bearers between related endpoints. After receiving the RRCReconfiguration message from the base station, the U2N remote terminal aborts UP and CP transmissions via Uu.

[0352] 4. The U2N remote terminal sets up a PC5 connection with the target U2N relay terminal.

[0353] 5. The U2N remote terminal sends an RRCReconfigurationComplete message to the base station via the relay terminal to complete the path switching procedure.

[0354] 6. The data path is switched from a direct path to an indirect path between the U2N remote terminal and the base station.

[0355] When the U2N relay terminal selected for direct-indirect path switching is in RRC_IDLE or RRC_INACTIVE, after receiving the path switching command, the U2N remote terminal sets up a PC5 link with the U2N relay terminal and sends an RRCReconfigurationComplete message through the U2N relay terminal. In that case, the U2N relay terminal is switched to the RRC_CONNECTED state. In FIG. 15, the U2N remote terminal procedure for switching to the indirect path is also applicable when the U2N relay terminal selected for direct-indirect path switching is in RRC_IDLE or RRC_INACTIVE, but the four steps must be performed before the two steps.

[0356] SL discovery

[0357] The terminal can perform NR SL discovery while inside or outside coverage for non-relay operation.

[0358] The relay discovery mechanism (excluding the transmission of discovery messages based on U2N relay-specific thresholds) is also applicable to SL discovery.

[0359] Addition of indirect path to direct radio base

[0360] According to the prior art, when a terminal-network relay (U2N relay) function is set up between the relay terminal and the remote terminal, the relay terminal provides network connection to the U2N remote terminal. In this case, the remote terminal is not directly connected to the network while maintaining an indirect connection based on the U2N relay function.

[0361] On the other hand, it is advantageous for the remote terminal to maintain not only an indirect connection based on both PC5 and Uu, but also a direct connection only through Uu to support multi-path (MP) operation. The remote terminal with MP operation set can select one or both of the connections for data transmission to the network for more stable transmission and / or higher throughput.

[0362] In the case of MP operation, the remote terminal needs to set up an indirect connection while having a direct connection. However, according to the prior art, setting up an indirect connection based on a direct connection is not supported.

[0363] The method for executing data transmission of the terminal includes the following steps.

[0364] The remote terminal directly sets up an RRC connection with the base station and directly sets up a secondary connection by means of the RRC connection.

[0365] The base station determines the multi-path configuration. Figures 16 to 18 show an example of the additional procedure of U2N of the Uu base station.

[0366] - Referring to Figure 16 (Alt 1-1), the remote terminal can directly report the measurement information for the relay terminal to the base station.

[0367] - Referring to Figure 17 (Alt 1-2), the remote terminal can report the PC5-RRC connection setup based on the SL terminal information.

[0368] - Referring to Figure 18 (Alt 1-3), the relay terminal can report the PC5-RRC connection setup based on the SL terminal information. When the relay terminal is in the RRC_IDLE or RRC_INACTIVE state, the Uu RRC connection setup of the relay terminal is performed first.

[0369] When the relay terminal is in the RRC_IDLE or RRC_INACTIVE state, the Uu RRC connection setup of the relay terminal is performed first.

[0370] - Alt 2-1: The RRC connection setup of the relay terminal is performed based on paging.

[0371] In the case of an RRC_INACTIVE terminal, the base station can send paging to the RRC_INACTIVE terminal. The terminal ID in the paging message is the resume ID or the source / destination ID.

[0372] In the case of an RRC_IDLE terminal, the base station can send paging to the RRC_IDLE terminal. The terminal ID in the paging message is the source / destination ID.

[0373] Alternatively, paging can be requested from the core network (CN). It is necessary to define a method for the CN or the base station to find the s-TMSI of the relay terminal.

[0374] - Alt 2-2: The RRC connection setup of the relay terminal is performed by the remote terminal. The remote terminal can request the relay terminal to perform the RRC connection setup with the base station. The said request can be sent when the base station instructs the remote terminal to perform the RRC connection setup of the relay terminal. When the conventional method is reused, the remote terminal sends an RRC request message to the relay terminal, but the terminal may already be in the RRC connected state. The said request is sent by SL RRC.

[0375] - Alt 2-3: The RRC connection setup of the relay terminal is performed by SIB / capability. When the base station configures a multi-path and the remote / relay terminal supports the multi-path, the relay terminal starts the RRC connection setup. The base station configures a multi-path at the relay terminal and / or the remote terminal by SIB or a dedicated RRC signal. Based on this configuration, the relay terminal starts the RRC connection setup.

[0376] The addition of the U2N connection is performed by the RRC reconfiguration procedure.

[0377] The base station can recognize the PC5-RRC connection between the Layer2-IDs of the relay terminal and the remote terminal based on Alt 1-2 or Alt 1-3, etc.

[0378] The method for executing data transmission and reception of the terminal includes the following steps.

[0379] 1. The remote terminal performs random access, performs network and RRC connection setup, and can also perform PC5 discovery and PC5-RRC connection setup with the relay terminal as follows.

[0380] A. While the RRC connection is terminated and there is no U2N relay connection, the remote terminal in RRC_IDLE or RRC_INACTIVE selects a cell, performs random access in the cell, and then directly transmits the first RRC message (i.e., RRCSetupRequest or RRCResumeRequest) in UL for RRC connection setup with the base station. The base station directly responds to the remote terminal in DL with an RRCSetup or RRCResume message.

[0381] Upon receiving the RRCSetup or RRCResume message, the terminal transmits an RRCSetupComplete or RRCResumeComplete message to the base station. Thereafter, the base station can transmit a SecurityModeCommand message to the terminal for AS security activation between the terminal and the base station. After RRC connection setup and AS security activation, the base station transmits the first RRCReconfiguration message to the terminal to configure radio parameters and a direct data bearer for the terminal.

[0382] B. On the other hand, the U2N remote terminal and the U2N relay terminal perform a discovery procedure and use the NR V2X procedure to set up a PC5-RRC connection. Thereafter, the U2N remote terminal can configure the first SL DRX setting and transmit it to the U2N relay terminal by means of an RRCReconfigurationSidelink message for the PC5-RRC connection, or vice versa.

[0383] The present invention can assist all procedures for RRC connection establishment, PC5 discovery, and PC5-RRC connection establishment. For example, RRC connection establishment can precede PC5 discovery and PC5-RRC connection establishment. Alternatively, PC5 discovery and PC5-RRC connection establishment can precede RRC connection establishment. Alternatively, the terminal can perform PC5 discovery, RRC connection establishment, and then PC5-RRC connection establishment in sequence according to the implementation of the terminal.

[0384] 2. The remote terminal is set by the network to derive the NR SL measurement results of the serving L2 relay terminal or candidate L2 U2N relay terminal related to the measurement object set in measObjectRelay.

[0385] 3. The remote terminal can receive measurement settings in the RRCReconfiguration message. When the terminal receives measConfig in the RRCReconfiguration message, the terminal performs measurements as follows for each measId included in measIdListh in VarMeasConfig and starts the measurement reporting procedure.

[0386] A. When measObject is related to an L2 U2N relay terminal, the remote terminal performs the corresponding measurement related to the candidate relay terminal at the frequency indicated by the related measObject. When performing the measurement, the terminal filters the measurement results based on layer 3 filtering before using them for report criterion evaluation or measurement reporting for the measurement quantity of each candidate L2 U2N relay terminal.

[0387] B. For the measurement quantity of each L2 U2N relay terminal to be derived, the remote terminal performs the following.

[0388] - Derive the measurement quantity based on the DMRS as shown in TS 38.215 of the L2 U2N relay terminal related to the NR SL frequency indicated by the related measObjectRelay. Also,

[0389] - Apply layer 3 filtering.

[0390] C. When the measObject is related to an L2 U2N relay terminal:

[0391] - When eventY1-Relay is set in the reportConfig; or

[0392] - When the reportConfig includes a reportType set to periodical:

[0393] The remote terminal shall consider all L2 U2N relay terminals detected at the relevant frequency as applicable to this measId.

[0394] Table 6 describes the events for measurement report triggering.

[0395]

Table 6-1

Table 6-2

Table 6-3

Table 6-4

[0396] In the state where the D.VarMeasReportList does not contain the measurement report item for this measId (the first L2 U2N relay terminal triggers the event), when reportType is set to eventTriggered, and the item conditions applicable to this event, that is, the event corresponding to the eventId of the said reportConfig in VarMeasConfig, are satisfied for all measurements after layer 3 filtering performed during the timeToTrigger defined for this event in VarMeasConfig for one or more applicable L2 U2N relay terminals, the remote terminal shall do the following.

[0397] - Include the measurement report item in the VarMeasReportList for this measId.

[0398] - Set the numberOfReportsSent defined in the VarMeasReportList for this measId to 0.

[0399] - Include the L2 U2N relay terminals related to the relaysTriggeredList defined in the VarMeasReportList for this measId.

[0400] - Start the measurement report procedure as follows.

[0401] Otherwise, when reportType is set to eventTriggered, and the item conditions applicable to this event, that is, the event corresponding to the eventId of the said reportConfig in VarMeasConfig, are satisfied for all measurements after layer 3 filtering performed during the timeToTrigger defined for this event in VarMeasConfig for one or more applicable L2 U2N relay terminals not included in the relaysTriggeredList (subsequent L2 U2N relay terminals trigger the event), the remote terminal shall do the following.

[0402] - Set the numberOfReportsSent defined in the VarMeasReportList for this measId to 0.

[0403] - Include the L2 U2N relay terminal in the relaysTriggeredList defined in the VarMeasReportList for this measId.

[0404] - Start the measurement reporting procedure as follows.

[0405] E. Otherwise, if the reportType is set to eventTriggered and the detachment condition applicable to this event is met for all measurements after layer 3 filtering performed during the timeToTrigger defined for this event in the VarMeasConfig, for one or more of the L2 U2N relay terminals included in the relaysTriggeredList defined in the VarMeasReportList for this measId, the remote terminal shall do the following.

[0406] - Remove the relevant L2 U2N relay terminal from the relaysTriggeredList defined in the VarMeasReportList for this measId.

[0407] - If reportOnLeave is set to true for the said reporting setting, start the measurement reporting procedure as follows.

[0408] - If the relaysTriggeredList defined in the VarMeasReportList for this measId is empty: remove the measurement report items in the VarMeasReportList for this measId; if the periodic reporting timer for this measId is running, stop it;

[0409] When F.reportType is set to periodical and the (first) measurement result is available:

[0410] - If reportAmount exceeds 1: Immediately after the amount to be reported becomes available for the NR SpCell or, if the terminal is an L2 U2N remote terminal, for the serving L2 U2N relay terminal, the terminal starts the measurement reporting procedure as shown in 5.5.5.

[0411] - Otherwise (i.e., if reportAmount is 1): Immediately after the amount to be reported becomes available for the NR SpCell and the strongest cell among the cells, or for the NR SpCell and the strongest L2 U2N relay terminal among the applicable L2 U2N relay terminals, the terminal starts the measurement reporting procedure as shown in 5.5.5; or, immediately after the amount to be reported becomes available for the serving L2 U2N relay terminal and the strongest cell among the applicable cells (if the terminal is an L2 U2N remote terminal), the terminal starts the measurement reporting procedure as in the next step.

[0412] 4. In the previous step, when starting the measurement reporting procedure, for the measId for which the measurement reporting procedure was triggered, the terminal sets the measResults in the MeasurementReport message as follows, and then the remote terminal sends the MeasurementReport message to the network via the SRB.

[0413] A. If the terminal is connected to the L2 U2N relay terminal by a PC5-RRC connection (i.e., if the terminal is an L2 U2N remote terminal), the terminal needs to set sl-MeasResultServingRelay to include the SL-RSRP of the serving L2 U2N relay terminal.

[0414] - If there is no data transmission from the serving L2 U2N relay terminal to the L2 U2N remote terminal, when setting sl-MeasResultServingRelay of the serving L2 U2N relay terminal, whether to use SL-RSRP or SD-RSRP depends on the implementation of the terminal.

[0415] B. When there is one or more applicable neighboring cells to report:

[0416] - When reportType is set to eventTriggered or periodical and the measurement report is related to the candidate L2 U2N relay terminal, the terminal needs to set sl-MeasResultCandRelay to up to maxReportCells to include the best candidate L2 U2N relay terminal as follows.

[0417] When reportType is set to eventTriggered: The terminal must include the L2 U2N relay terminals included in relaysTriggeredList as defined within VarMeasReportList for this measId.

[0418] Otherwise, the terminal must include the applicable L2 U2N relay terminals for which new measurement results have become available after the last periodic report, or after the measurement has been started or reset.

[0419] - For each L2 U2N relay terminal included in sl-MeasResultsCandRelay, the terminal must include sl-RelayUEIdentity. For each included L2 U2N relay terminal, the terminal must include the layer 3 filtered measurement results according to reportConfig for this measId.

[0420] When the measObject associated with this measId is associated with the L2 U2N relay terminal, the terminal must set the measResult to include the quantity indicated by the reportQuantityRelay in the associated reportConfigRelay in descending order of the sorting quantity, with the best L2 U2N relay terminal included first.

[0421] For the candidate L2 U2N relay terminal, the terminal regards yN-Threshold2-Relay as the sorting quantity.

[0422] For the candidate L2 U2N relay terminal, the terminal regards reportQuantityRelay as the sorting quantity.

[0423] Table 7 describes the SL-MeasResultsSLRelay information element.

[0424]

Table 7

[0425] After the PC5-RRC connection is established by the PC5 unicast link configuration, the remote terminal and the relay terminal can trigger the SL terminal capability transmission procedure to exchange their respective terminal capabilities. In this procedure, the remote terminal sends a UECapabilityEnquirySidelink message requesting the relay terminal's MP capability to the relay terminal, and the relay terminal sends a UECapabilityInformationSidelink message including the MP capability to the remote terminal. Thereafter, the relay terminal sends a UECapabilityEnquirySidelink message requesting the remote terminal's MP capability to the remote terminal, and the remote terminal sends a UECapabilityInformationSidelink message including the MP capability to the relay terminal.

[0426] The MP capability of the terminal includes one or more of the following.

[0427] - Whether the terminal supports multi-path operation as a remote terminal and / or a relay terminal

[0428] - The SL / UL / DL frequency carriers / bands that the terminal supports for MP operation for transmission and / or reception

[0429] - The combination of the SL carrier / band and the UL carrier / band that the terminal supports for MP operation for its own transmission

[0430] - The combination of the SL carrier / band and the DL carrier / band that the terminal supports for MP operation for its own reception

[0431] The relay terminal confirms that both the relay terminal and the remote terminal support MP capabilities based on the exchange of the above-mentioned SL terminal capabilities. When the remote terminal is in RRC_CONNECTED, the relay terminal that is not in RRC_CONNECTED can initiate the RRC connection setup procedure.

[0432] 6. If the remote terminal and the relay terminal support MP operation in the DL / UL carriers of the serving cell and the SL carriers where SL transmission and / or SL reception are performed between the remote terminal and the relay terminal, or if the serving cell supports SL resources for SL transmission / reception and / or MP operation (e.g., according to the resource pool setting of system information or dedicated signals), the relay terminal either initiates the RRC connection setup or the relay terminal sends a first SL message to the remote terminal to indicate the RRC state of the relay terminal or whether the relay terminal is in RRC_CONNECTED.

[0433] A. The first SL message includes one or more of the following.

[0434] - The PCell cell ID of the relay terminal.

[0435] - The PLMN ID of the registered PLMN of the relay terminal.

[0436] - The tracking area code of the tracking area registered by the relay terminal for the PCell.

[0437] B. When receiving the first SL message, the remote terminal performs any one or more of the following steps.

[0438] - If the cell indicated by the relay terminal is different from the serving cell where the remote terminal camps on, the remote terminal reselects the indicated cell according to the cell reselection procedure, or the remote terminal aborts the multi-path operation setting with the relay terminal. If the remote terminal cannot reselect the indicated cell according to the cell reselection procedure, the remote terminal aborts the multi-path operation setting with the relay terminal.

[0439] - If the tracking area indicated by the relay terminal is different from the tracking area where the remote terminal is registered, the remote terminal triggers a tracking area update procedure to register in the tracking area indicated by the relay terminal, or the remote terminal aborts the multi-path operation setting with the relay terminal. For example, if the remote terminal cannot register in the tracking area indicated by the relay terminal due to the failure of the tracking area update procedure or other related NAS procedures, the remote terminal aborts the multi-path operation setting with the relay terminal.

[0440] - If the PLMN indicated by the relay terminal is different from the PLMN where the remote terminal is registered, the remote terminal reselects the PLMN indicated by the relay terminal and registers in the indicated PLMN, or the remote terminal aborts the multi-path operation setting with the relay terminal. For example, if the remote terminal cannot register in the PLNN indicated by the relay terminal due to the failure of the PLMN registration procedure or other related NAS procedures, the remote terminal aborts the multi-path operation setting with the relay terminal.

[0441] C. The first SL message is a RemoteUEInformationSidelink message, a UEAssistanceInformationSidelink message, an RRCReconfigurationSidelink message, or an RRCReconfigurationCompleteSidelink message.

[0442] 7. When the remote terminal directly enters RRC_CONNECTED by RRC connection setup (i.e., by RACH procedure), when the remote terminal sets up a PC5-RRC connection by PC5 unicast link setup, and when the remote terminal and the relay terminal support MP operation in the DL / UL carrier and the SL carrier of the serving cell where SL transmission and / or SL reception between the remote terminal and the relay terminal are performed, or when the serving cell supports SL resources for SL transmission / reception and / or MP operation (e.g., by resource pool setup of system information or dedicated signal base):

[0443] A. (When receiving the first SL message) The remote terminal can request the relay terminal to transmit a second SL message and start RRC connection setup for entering RRC_CONNECTED. The second SL message includes one or more of the following.

[0444] - Request for multi-path operation or request for RRC connection setup of the relay terminal for multi-path

[0445] If this request is included, the relay terminal triggers RRC connection setup.

[0446] - RRC state of the remote terminal or whether the remote terminal is in the RRC_CONNECTED state

[0447] - Cell ID of the serving cell where the remote terminal camps on.

[0448] - PLMN ID of the registered PLMN of the remote terminal.

[0449] - Tracking area code of the tracking area where the remote terminal is registered in the PCell.

[0450] At this stage, (based on the first SL message) the remote terminal requests the relay terminal to start RRC connection setup when one or more of the following conditions are met.

[0451] - When the relay terminal is not in the RRC_CONNECTED state

[0452] - When the relay terminal camps on the same cell where the remote terminal has camped on

[0453] - When the relay terminal camps on the cell corresponding to the best cell of the remote terminal, that is, among the multiple cells measured by the remote terminal, the cell with the best cell quality

[0454] - When the remote terminal measures the cell indicated by the relay terminal and the measurement result of the cell indicated by the relay terminal exceeds the threshold set by the network (SIB or dedicated signal)

[0455] In this case, regardless of whether the cell is the highest-ranked cell in terms of cell quality among all candidate cells, if the cell is suitable, the remote terminal performs cell reselection to the said cell

[0456] - When the remote terminal reselects the cell indicated by the relay terminal (for example, when the indicated cell is not the barred cell of the remote terminal / or when the indicated cell is an appropriate cell of the remote terminal)

[0457] - After the remote terminal receives the first SL message, as a result of the cell reselection procedure, when the cell indicated by the relay terminal is successfully reselected

[0458] - When the relay terminal is registered in the same tracking area as the tracking area where the remote terminal is registered

[0459] - When the remote terminal can register in the tracking area indicated by the relay terminal (for example, when the said tracking area is not in the prohibited tracking area list of the remote terminal, or when the said tracking area does not correspond to the tracking area that could not be registered by the tracking area update of the remote terminal)

[0460] - When the remote terminal successfully registers in the tracking area indicated by the relay terminal after receiving the first SL message.

[0461] - When the relay terminal is registered in the same PLMN as the PLMN in which the remote terminal is registered.

[0462] - When the remote terminal can register in the PLMN indicated by the relay terminal (for example, when the PLMN is not in the prohibited PLMN list of the remote terminal or when the PLMN does not correspond to the PLMN in which the remote terminal could not register).

[0463] - When the remote terminal successfully registers in the PLMN indicated by the relay terminal after receiving the first SL message.

[0464] In the above-described stage, if any one or more of the above conditions are not satisfied, the remote terminal does not request the relay terminal to start RRC connection setup and aborts the MP operation with the relay terminal.

[0465] B. When receiving the second SL message (and / or after transmitting the first SL message), the relay terminal transmits an RRCSetupRequest message or an RRCResumeRequest message to the base station to start the RRC connection setup procedure if any one or more of the following conditions are satisfied.

[0466] - When the relay terminal is not in the RRC_CONNECTED state

[0467] - When the relay terminal camps on the same cell as the cell on which the remote terminal camps (i.e., the cell indicated by the remote terminal).

[0468] - When the remote terminal camps on the cell corresponding to the best cell of the relay terminal, that is, the cell having the best cell quality among the plurality of cells measured by the relay terminal.

[0469] - When the relay terminal measures the cell indicated by the remote terminal and the measurement result of the cell indicated by the remote terminal exceeds the threshold value set by the network (SIB or dedicated signal).

[0470] In this case, regardless of whether the cell occupies the highest rank in terms of cell quality among all candidate cells, if the cell is appropriate, the relay terminal performs cell reselection on the cell.

[0471] - When the relay terminal can reselect the cell indicated by the remote terminal (for example, when the indicated cell is not the blocked cell of the remote terminal / or when the indicated cell is an appropriate cell of the remote terminal)

[0472] - After the relay terminal receives the second SL message, when it successfully reselects the cell indicated by the remote terminal as a result of the cell reselection procedure.

[0473] - When the remote terminal is registered in the same tracking area as the tracking area where the relay terminal is registered.

[0474] - When the relay terminal can register in the tracking area indicated by the remote terminal (for example, when the tracking area is not in the relay terminal's prohibited tracking area list or when the tracking area does not correspond to the tracking area that could not be registered by the relay terminal's tracking area update).

[0475] - After the relay terminal receives the second SL message, when it successfully registers in the tracking area indicated by the remote terminal.

[0476] - When the remote terminal is registered in the same PLMN as the PLMN where the relay terminal is registered.

[0477] - When the relay terminal can register in the PLMN indicated by the remote terminal (for example, when the PLMN is not in the relay terminal's prohibited PLMN list or when the PLMN does not correspond to the PLMN that the relay terminal could not register).

[0478] - After the relay terminal receives the second SL message and successfully registers with the PLMN instructed by the remote terminal.

[0479] In the above-described stage, if any one or more of the above conditions are not satisfied, the relay terminal aborts the RRC connection setup or the relay terminal does not start the RRC connection setup. The relay also aborts the MP operation with the relay terminal.

[0480] - When the second SL message requesting multi-path operation or RRC connection setup is the RRCReconfigurationSidelink message sent by the remote terminal,

[0481] If the RRC connection setup of the relay terminal is not successfully completed, the relay terminal sends an RRCReconfigurationFailureSidelink message to the remote terminal.

[0482] The RRCReconfigurationFailureSidelink message may include a failure cause indicating "RRC connection setup failure".

[0483] Upon receiving the RRCReconfigurationFailureSidelink message, the remote terminal aborts the MP operation with the relay terminal and reselects another relay terminal.

[0484] Otherwise, if the RRC connection setup of the relay terminal is successfully completed, the relay terminal sends an RRCReconfigurationCompleteSidelink message to the remote terminal. The RRCReconfigurationCompleteSidelink message includes one or more of the following.

[0485] Whether the RRC connection setup of the relay terminal is successfully completed.

[0486] The PCell cell ID of the relay terminal.

[0487] The PLMN ID of the PLMN registered by the relay terminal.

[0488] The tracking area code of the tracking area in which the relay terminal is registered with the PCell.

[0489] C. In the above-described stage, the first SL message and / or the second SL message is a RemoteUEInformationSidelink message, a UEAssistanceInformationSidelink message, an RRCReconfigurationSidelink message, or an RRCReconfigurationCompleteSidelink message.

[0490] 8. When the relay terminal sends an SL message and reports to the remote terminal that the RRC connection setup of the relay terminal has been successfully completed, the relay terminal may instruct the remote terminal with one or more of the following by the SL message.

[0491] - The PCell cell ID of the relay terminal.

[0492] - The PLMN ID of the PLMN registered by the relay terminal.

[0493] - The tracking area code of the tracking area in which the relay terminal is registered with the PCell.

[0494] A. When the relay terminal and the remote terminal are set to different serving cells, different tracking areas and / or different PLMNs from each other, the remote terminal and / or the relay terminal notify the base station of one or more different serving cells, different tracking areas and / or different PLMNs from each other by, for example, the SidelinkUEInformationNR message.

[0495] B. The SL message is a RemoteUEInformationSidelink message, a UEAssistanceInformationSidelink message, an RRCReconfigurationSidelink message, or an RRCReconfigurationCompleteSidelink message.

[0496] 9. After RRC connection setup and PC5 - RRC connection setup, the relay terminal and / or the remote terminal perform SL terminal information for the NR sidelink communication procedure in which the terminal transmits the SidelinkUEInformationNR message to the base station.

[0497] The terminal configures the content of the SidelinkUEInformationNR message as follows.

[0498] A. When sl - NonRelayDiscovery is included in a specific SIB (e.g., SIB12) and is configured by the upper layer to receive NR SL non - relay discovery knowledge, or when sl - L2U2N - Relay is included in a specific SIB (e.g., SIB12) and is configured by the upper layer to receive NR SL L2 U2N relay discovery knowledge, or when sl - L3U2N - RelayDiscovery is included in a specific SIB (e.g., SIB12) and is configured by the upper layer to receive NR SL L3 U2N relay discovery knowledge, or when an indication for multi - path support is included in a specific SIB (e.g., SIB12) and is configured by the upper layer to receive NR SL U2N relay discovery knowledge:

[0499] - The terminal includes sl - RxInterestedFreqListDisc and configures it to the frequencies for NR SL relay discovery knowledge reception.

[0500] - When the terminal acts as an L2 U2N remote terminal or the terminal performs multi-path operation as a remote terminal, the terminal includes sl-SourceIdentity-RemoteUE and sets it to the source ID set at the upper layer for NR SL L2 U2N relay communication transmission.

[0501] B. When sl-NonRelayDiscovery is included in a specific SIB (e.g., SIB12) and is set by the upper layer to transmit NR SL non-relay discovery public knowledge, or when sl-L2U2N-Relay is included in a specific SIB (e.g., SIB12) and is set by the upper layer to transmit NR SL L2 U2N relay discovery public knowledge, or when sl-L3U2N-RelayDiscovery is included in a specific SIB (e.g., SIB12) and is set by the upper layer to transmit NR SL L3 U2N relay discovery public knowledge, or when an instruction for multi-path support is included in a specific SIB (e.g., SIB12) and is set by the upper layer to transmit NR SL U2N relay discovery public knowledge, the terminal includes sl-TxResourceReqListDis and, for each destination for which it requests the network to allocate NR SL discovery public knowledge resources, (if necessary) sets its fields as follows:

[0502] - Set sl-DestinationIdentityDisc to the destination ID set at the upper layer for NR SL discovery public knowledge transmission.

[0503] - When the terminal operates as an L2 U2N relay terminal, the terminal sets sl-SourceIdentity-RelayUE to the source ID set at the upper layer for NR SL L2 U2N relay discovery public knowledge transmission.

[0504] - Set sl-CastTypeDisc to the cast type of the related destination ID set at the upper layer for NR SL discovery public knowledge transmission.

[0505] - Set sl-InterestedFreqListDisc to indicate the relevant destination frequencies for NR SL discovery public transmission.

[0506] - Set sl-TypeTxSyncListDisc to the current synchronization reference type used in the relevant sl-InterestedFreqList for NR SL discovery public transmission.

[0507] - Set sl-DiscoveryType to the current discovery type of the relevant destination ID set at the upper layer for NR SL discovery public transmission.

[0508] C. When set by the upper layer to transmit NR SL L2 U2N relay communication and the terminal operates as an L2 U2N relay terminal for multi-path, the relay terminal shall do the following.

[0509] - Include sl-TxResourceReqL2U2N-Relay in sl-TxResourceReqListCommRelay and set this field as follows for each destination that requests (if necessary) the network to allocate NR SL L2 U2N relay communication resources.

[0510] - Set sl-DestinationIdentityL2U2N to the destination ID set at the upper layer for NR SL L2 U2N relay communication transmission.

[0511] - Set sl-TxInterestedFreqListL2U2N to indicate the relevant destination frequencies for NR SL L2 U2N relay communication transmission.

[0512] - Set the sl-TypeTxSyncListL2U2N to the current synchronization reference type used in the sl-InterestedFreqListL2U2N associated with NR SL L2 U2N relay communication transmission.

[0513] - Set the sl-LocalID-Request to request the local ID for the L2 U2N remote terminal.

[0514] - Set the sl-PagingIdentity-RemoteUE to the paging terminal ID received at the peer L2 U2N remote terminal.

[0515] - Set the sl-CapabilityInformationSidelink to include the UECapabilityInformationSidelink message (if present) received at the peer terminal.

[0516] - Include ue-Type and set this to the relay UE.

[0517] - Include multi-path support / request indication.

[0518] - Include an indication of the RRC state of the remote terminal or whether the remote terminal is in RRC_CONNECTED.

[0519] - Include the cell ID of the PCell for the remote terminal.

[0520] - Include the PLMN ID of the PLMN registered for the remote terminal.

[0521] - Include the tracking area code of the tracking area where the remote terminal is registered with the PCell.

[0522] D. NR sidelink L2 U2N relay communication is configured by the upper layer to be transmitted. If there is an L2 U2N relay terminal selected by the terminal for multi-path, the remote terminal shall perform the following.

[0523] - Include sl-TxResourceReqL2U2N-Relay in sl-TxResourceReqListCommRelay and, if necessary, set its fields as follows to request the network to allocate NR SL L2 U2N relay communication resources.

[0524] - Set sl-TxInterestedFreqListL2U2N to indicate the frequencies of the destinations relevant for NR SL L2 U2N relay communication transmission.

[0525] - Set sl-TypeTxSyncListL2U2N to the current synchronization reference type used in the relevant sl-InterestedFreqListL2U2N for NR SL L2 U2N relay communication transmission.

[0526] - If there is a terminal CapabilityInformationSidelink message received at the peer terminal, set sl-CapabilityInformationSidelink to include this.

[0527] - Include ue-Type and set it to remoteUE.

[0528] - Include multi-path support / request indication.

[0529] - Include an indication of the RRC state of the relay terminal or whether the relay terminal is in RRC_CONNECTED.

[0530] - Include the PCell cell ID of the relay terminal.

[0531] - Include the PLMN ID of the registered PLMN of the relay terminal.

[0532] - Include the tracking area code of the tracking area in which the relay terminal is registered with the PCell.

[0533] When configured by the upper layer to send E.NR SL L3 U2N relay communication, the relay terminal or the remote terminal shall perform the following.

[0534] - Include sl-TxResourceReqL3U2N-Relay in sl-TxResourceReqListCommRelay and, for each destination (if required) for which the network is requested to allocate NR SL L3 U2N relay communication resources, configure the fields thereof as follows:

[0535] - Set sl-DestinationIdentity to the destination ID configured by the upper layer for NR SL L3 U2N relay communication transmission.

[0536] - Set sl-CastType to the cast type of the associated destination ID configured by the upper layer for NR SL L3 U2N relay communication transmission.

[0537] - If the associated two-way SL DRB is configured by the configuration by RRCReconfigurationSidelink, set sl-RLC-ModeIndication to include the RLC mode of the SL QoS flow of the associated RLC mode and optionally the QoS profile.

[0538] - Set sl-QoS-InfoList to include the QoS profile of the SL QoS flow of the associated destination configured by the upper layer for NR SL L3 U2N relay communication transmission.

[0539] - Set sl-TxInterestedFreqList to indicate the frequency of the associated destination for NR SL L3 U2N relay communication transmission.

[0540] - Set the sl-TypeTxSyncList to the current synchronization reference type used in the sl-InterestedFreqList for NR SL L3 U2N relay communication transmission.

[0541] - When the UECapabilityInformationSidelink message is received from the peer terminal, set the sl-CapabilityInformationSidelink to include it.

[0542] - Include the ue-Type and set it to relayUE if the terminal operates as an NR SL L3 U2N relay terminal, or set it to remoteUE otherwise.

[0543] - Include the multi-path support / request indication.

[0544] - Include an indication of the RRC state of the relay terminal or whether the relay terminal is in RRC_CONNECTED.

[0545] - Include an indication of the RRC state of the remote terminal or whether the remote terminal is in RRC_CONNECTED.

[0546] - When the terminal operates as an NR SL U2N remote terminal:

[0547] Include the cell ID of the PCell for the relay terminal.

[0548] Include the PLMN ID of the registered PLMN for the relay terminal.

[0549] Include the tracking area code of the tracking area registered by the relay terminal for the PCell.

[0550] - When the terminal operates as an NR SL U2N relay terminal:

[0551] Include the cell ID of the PCell for the remote terminal.

[0552] It includes the PLMN ID of the PLMN registered for the remote terminal.

[0553] It includes the tracking area code of the tracking area registered for the remote terminal with respect to the PCell.

[0554] 10. When receiving a report from a remote terminal and / or a relay terminal (e.g., a MeasurementReport message (Alt 1-1 in Figure 16) and / or a SidelinkUEInformationNR message of the remote terminal (Alt 1-2 in Figure 17) and / or a SidelinkUEInformationNR message of the relay terminal (Alt 1-3 in Figure 18)), the base station determines whether to add an indirect path via the relay terminal for the remote terminal.

[0555] When the relay terminal is not in RRC_CONNECTED, the base station can request, for example, via the remote terminal, the relay terminal to start RRC connection setup. For example, the base station can send the SL message and request the remote terminal to request the relay terminal to start RRC connection setup.

[0556] Alternatively, when the relay terminal is not in the RRC_CONNECTED state, the base station can page the relay terminal as follows.

[0557] A. When the relay terminal is in RRC_INACTIVE (or RRC_IDLE), the base station sends a paging indication and / or a paging message to page the relay terminal. When the relay terminal is in RRC_IDLE, the base station can transmit the terminal ID of the relay terminal and request the core network (CN) node (e.g., AMF) to page the relay terminal. When requesting, the CN node sends a paging message to the relay terminal by the base station. The request to the CN node includes the source ID or destination ID of the relay terminal.

[0558] B. Alternatively, when the relay terminal is in RRC_INACTIVE (or RRC_IDLE), the base station can send an RRCReconfiguration message containing a paging message in dedicatedPagingDeliver to the remote terminal to page the relay terminal.

[0559] - When the remote terminal receives the message, for example, it starts transmitting a Uu message in SL and sends a paging message to the relay terminal. The relay terminal receives the paging message from the remote terminal. In this case, the paging message contains a PagingCause indicating "multi-path" or "relay" without a terminal ID. When the relay terminal receives a paging message from the remote terminal in SL, the relay terminal starts RRC connection setup.

[0560] C. The paging indication and / or paging message contains a terminal ID of the relay terminal (e.g., C-RNTI, ResumeIdentity, s-TMSI, or a source ID or destination ID belonging to the relay terminal) and a PagingCause indicating "multi-path" or "U2N relay connection".

[0561] D. After receiving the paging indication and / or paging message, if the relay terminal is not in RRC_CONNECTED and the paging indication and / or paging message contains a terminal ID belonging to the relay terminal, the relay terminal starts an RRC connection setup procedure in the cell of the base station and enters RRC_CONNECTED.

[0562] 11. If the relay terminal and the remote terminal are not set in the same cell or not registered in the same tracking area and / or the same PLMN, the base station can perform a handover for the relay terminal and / or the remote terminal to move the relay terminal and / or the remote terminal to the same cell, the same tracking area, and / or the same PLMN.

[0563] 12. When both the relay terminal and the remote terminal are in the RRC_CONNECTED state and the base station decides whether to add an indirect path via the relay terminal for the remote terminal according to the previous stage, the base station transmits, for example, an RRCReconfiguration message to each of the relay terminal and the remote terminal to configure an indirect path via the relay terminal for the remote terminal.

[0564] - If sl-L2RelayUEConfig is included in the RRCReconfiguration message, the relay terminal performs the setting procedure for the L2 U2N relay terminal and (re)configures zero, one or more indirect bearers and zero, one or more split bearers.

[0565] - If sl-L2RemoteUEConfig is included in the RRCReconfiguration message, the remote terminal performs the setting procedure for the L2 U2N remote terminal and (re)configures zero, one or more direct bearers and zero, one or more split bearers.

[0566] - The indirect bearer or split bearer includes the setting of the Uu relay RLC channel.

[0567] - An indirect link composed of a Uu link and an SL is set for the indirect bearer.

[0568] - The direct bearer is set by a link that exclusively passes through the Uu.

[0569] - Both an indirect link and a direct link are set for the split bearer. The base station can select one or both of the indirect link and the direct link for downstream data transmission to the remote terminal, while the remote terminal can select one or both of the indirect link and the direct link for upstream data transmission to the base station.

[0570] When the disclosed invention is utilized, particularly when the terminal can support the U2N relay function via SL, the remote terminal can, according to the invention, select one or both of SL transmission and UL transmission, or one or both of SL reception and DL reception.

[0571] The present invention is advantageous in that the system can appropriately apply multi-path operation including direct links and indirect links via U2N relays. In the prior art, there was no mechanism for providing SL relays for multi-path operation.

[0572] FIG. 19 shows a method by which a first UE sets a plurality of radio paths in an embodiment of the present invention.

[0573] Referring to FIG. 19, the first UE performs a procedure for setting a first path related to a direct connection to the network (1905).

[0574] While the first UE is in the RRC (radio resource control) connected state where the first path is set, the first UE transmits an SL message for adding a second path related to an indirect connection to the network to a second UE that is set as a relay UE between the network and the first UE (1910).

[0575] Based on the fact that the second UE is not in the RRC connected state, the random access procedure of the second UE is triggered by the SL message transmission of the first UE.

[0576] The second UE that is not in the RRC connected state performs a random access procedure to request an RRC connection to the network.

[0577] The first UE requests the second UE to perform a random access procedure.

[0578] Based on the fact that the second UE is RRC connected to the network, a second path related to an indirect connection to the network is set.

[0579] For the first UE, a first path related to a direct connection to the network and a second path related to an indirect connection to the network are set.

[0580] The SL message is directly transmitted to the second UE via the SL interface between the first UE and the second UE.

[0581] The SL message includes information indicating that the SL message is related to the multi-path setting of the first UE.

[0582] The first UE receives an RRC reconfiguration message including information for setting a second path in addition to the first path from the network via the first path.

[0583] The SL message is transmitted based on the RRC reconfiguration message.

[0584] Based on the setting of the second path in addition to the first path, the first UE transmits an RRC reconfiguration complete message to the network via the first path or the second path.

[0585] The first UE operates as a remote UE on the second path related to the indirect connection.

[0586] Without limitation, the various descriptions, functions, procedures, proposals, methods, and / or flowcharts of the present invention disclosed in this specification can be applied to various fields that require wireless communication / connection between devices (e.g., 5G).

[0587] Hereinafter, a more specific description will be given with reference to the drawings. In the following figures / descriptions, the same reference numerals exemplify the same or corresponding hardware blocks, software blocks, or functional blocks unless otherwise specifically mentioned.

[0588] FIG. 20 illustrates a communication system applicable to the present invention.

[0589] Referring to FIG. 20, the communication system 1 to which the present invention is applied includes a wireless device, a base station, and a network. Here, the wireless device means a device that communicates using a wireless access technology (for example, 5G NR (New RAT), LTE (Long Term Evolution)), and is also referred to as a communication / wireless / 5G device. Without being limited thereto, the wireless devices include a robot 100a, vehicles 100b-1, 100b-2, an XR (Extended Reality) device 100c, a hand-held device 100d, a home appliance 100e, an IoT (Internet of Thing) device 100f, and an AI device / server 400. For example, the vehicles include vehicles equipped with a wireless communication function, autonomous driving vehicles, vehicles capable of vehicle-to-vehicle communication, etc. Here, the vehicles include UAVs (Unmanned Aerial Vehicles) (for example, drones). The XR device includes an AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) device, and is embodied in the form of an HMD (Head-Mounted Device), a HUD (Head-Up Display) provided in a vehicle, a TV, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. The hand-held devices include smartphones, smart pads, wearable devices (for example, smartwatches, smart glasses), computers (for example, notebook computers, etc.). The home appliances include TVs, refrigerators, washing machines, etc. The IoT devices include sensors, smart meters, etc. For example, the base station and the network are also embodied in the wireless device, and a specific wireless device 200a can also operate as a base station / network node for other wireless devices.

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

[0591] Wireless communications / connections 150a, 150b, and 150c are performed between wireless devices 100a to 100f / base station 200 and between base stations 200 / 200. Here, the wireless communications / connections are uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), and inter-base station communication 150c (e.g., performed by various radio access technologies such as relay and IAB (Integrated Access Backhaul) (e.g., 5G NR)). Through wireless communications / connections 150a, 150b, and 150c, wireless devices and base stations / wireless devices, and base stations and base stations can send / receive wireless signals to / from each other. For example, wireless communications / connections 150a, 150b, and 150c can send / receive signals via various physical channels. For this purpose, based on various proposals of the present invention, any one of a setting process of various configuration information for sending / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and a resource allocation process is performed.

[0592] FIG. 21 illustrates a wireless device applicable to the present invention.

[0593] Referring to FIG. 21, the first wireless device 100 and the second wireless device 200 transmit and receive wireless signals by various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device 100, the second wireless device 200} corresponds to {the wireless device 100x, the base station 200} in FIG. 20 and / or {the wireless device 100x, the wireless device 100x}.

[0594] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and further includes one or more transceivers 106 and / or one or more antennas 108. The processor 102 controls the memory 104 and / or the transceiver 106 and is configured to implement the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification. For example, after the processor 102 processes the information in the memory 104 to generate a first piece of information / signal, the transceiver 106 transmits a wireless signal including the first piece of information / signal. Also, after the processor 102 receives a wireless signal including a second piece of information / signal by the transceiver 106, the information obtained from the signal processing of the second piece of information / signal is stored in the memory 104. The memory 104 is connected to the processor 102 and stores various information related to the operation of the processor 102. For example, the memory 104 stores software code that performs some or all of the processes controlled by the processor 102 or performs the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification. Here, the processor 102 and the memory 104 are part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). The transceiver 106 is connected to the processor 102 and transmits and / or receives wireless signals through one or more antennas 108. The transceiver 106 includes a transmitter and / or a receiver. The transceiver 106 can also be used interchangeably with an RF (radio Frequency) unit. In the present invention, the wireless device can also mean a communication modem / circuit / chip.

[0595] Specifically, the UE includes a processor 102 and a memory 104 that are coupled to the RF transceiver. The memory 104 includes at least one program capable of performing operations related to the embodiments shown in FIGS. 11 to 27.

[0596] Alternatively, a chipset including the processor 102 and the memory 104 is configured. In this case, the chipset includes at least one processor and at least one memory that is operably coupled to the at least one processor and causes the at least one processor to operate when executed.

[0597] The second wireless device 200 includes one or more processors 202 and one or more memories 204, and further includes one or more transceivers 206 and / or one or more antennas 208. The processor 202 controls the memory 204 and / or the transceiver 206 and is configured to implement the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification. For example, after the processor 202 processes the information in the memory 204 to generate third information / signal, the transceiver 206 transmits a wireless signal including the third information / signal. Also, after the processor 202 receives a wireless signal including fourth information / signal by the transceiver 206, the information obtained from the signal processing of the fourth information / signal is stored in the memory 204. The memory 204 is coupled to the processor 202 and stores various information related to the operation of the processor 202. For example, the memory 204 stores software code for performing some or all of the processes controlled by the processor 202 or for performing the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification. Here, the processor 202 and the memory 204 are part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). The transceiver 206 is coupled to the processor 202 and transmits and / or receives wireless signals via one or more antennas 208. The transceiver 206 includes a transmitter and / or a receiver. The transceiver 206 can also be used interchangeably with an RF unit. In the present invention, the wireless device also means a communication modem / circuit / chip.

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

[0599] One or more processors 102, 202 are also referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors 102, 202 are implemented by hardware, firmware, software, or a combination thereof. As an example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) are included in one or more processors 102, 202. The descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification are implemented using firmware or software, and the firmware or software is implemented to include modules, procedures, functions, and the like. The firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification is included in one or more processors 102, 202, or stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification are implemented using firmware or software in the form of code, instruction, and / or set of instructions.

[0600] One or more memories 104, 204 are connected to one or more processors 102, 202 and store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories 104, 204 are composed of 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 are located inside and / or outside the one or more processors 102, 202. Also, the one or more memories 104, 204 are connected to the one or more processors 102, 202 by various technologies such as wired or wireless connections.

[0601] One or more transceivers 106, 206 transmit user data, control information, radio signals / channels, etc. mentioned in this specification in the form of methods and / or flowcharts, etc. to one or more other devices. One or more transceivers 106, 206 receive user data, control information, radio signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods, and / or flowcharts, etc. disclosed in this specification from one or more other devices. For example, one or more transceivers 106, 206 are connected to one or more processors 102, 202 and transmit and receive radio signals. For example, one or more processors 102, 202 control one or more transceivers 106, 206 to transmit user data, control information, or radio signals to one or more other devices. Also, one or more processors 102, 202 control one or more transceivers 106, 206 to receive user data, control information, or radio signals from one or more other devices. One or more transceivers 106, 206 are connected to one or more antennas 108, 208, and one or more transceivers 106, 206 are configured to transmit and receive user data, control information, radio signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods, and / or flowcharts, etc. disclosed in this specification by one or more antennas 108, 208. In this specification, one or more antennas are multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 convert received radio signals / channels, etc. from RF band signals to baseband signals (Convert) in order to process received user data, control information, radio signals / channels, etc. using one or more processors 102, 202. One or more transceivers 106, 206 convert user data, control information, radio signals / channels, etc. processed using one or more processors 102, 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106, 206 include (analog) oscillators and / or filters.

[0602] Figure 22 illustrates another example of a wireless device to which this invention is applied. The wireless device can be embodied in various forms depending on usage examples / services (see Figure 20).

[0603] Referring to FIG. 22, the wireless devices 100 and 200 correspond to the wireless devices 100 and 200 in FIG. 21 and are composed of various elements, components, units / parts, and / or modules. For example, the wireless devices 100 and 200 include a communication unit 110, a control unit 120, a memory unit 130, and additional elements 140. The communication unit includes a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 includes one or more processors 102 and 202 and / or one or more memories 104 and 204 in FIG. 21. For example, the transceiver 114 includes one or more transceivers 106 and 206 and / or one or more antennas 108 and 208 in FIG. 21. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional elements 140 and controls various operations of the wireless device. For example, the control unit 120 controls the electrical / mechanical operations of the wireless device based on programs / codes / instructions / information stored in the memory unit 130. Also, the control unit 120 transmits the information stored in the memory unit 130 to the outside (e.g., other communication devices) through a wireless / wired interface by the communication unit 110, or stores the information received from the outside (e.g., other communication devices) through a wireless / wired interface by the communication unit 110 in the memory unit 130.

[0604] The additional elements 140 are variously configured depending on the type of wireless device. For example, the additional elements 140 include any one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computer unit. Without being limited thereto, the wireless device is embodied in the form of a robot (FIGS. 20, 100a), a vehicle (FIGS. 20, 100b-1, 100b-2), an XR device (FIGS. 20, 100c), a portable device (FIGS. 20, 100d), a household appliance (FIGS. 20, 100e), an IoT device (FIGS. 20, 100f), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (FIGS. 20, 400), a base station (FIGS. 20, 200), and a network node, etc. The wireless device is movable depending on the usage example / service or is used at a fixed location.

[0605] In FIG. 22, various elements, components, units / parts, and / or modules within the wireless devices 100 and 200 are all connected to each other by a wired interface, or at least some of them are wirelessly connected by the communication unit 110. For example, within the wireless devices 100 and 200, the control unit 120 and the communication unit 110 are wired-connected, and the control unit 120 and the first units (e.g., 130, 140) are wirelessly connected by the communication unit 110. Also, each element, component, unit / part, and / or module within the wireless devices 100 and 200 further includes one or more elements. For example, the control unit 120 is composed of one or more sets of processors. For example, the control unit 120 is composed of a set including a communication control processor, an application processor, an ECU (Electronic Control Unit), a graphics processing processor, a memory control processor, and the like. As another example, the memory unit 130 is composed of a RAM (Random Access Memory), a DRAM (Dynamic RAM), a ROM (Read Only Memory), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0606] FIG. 23 illustrates a vehicle or an autonomous driving vehicle to which the present invention is applied. The vehicle or the autonomous driving vehicle is embodied as a mobile robot, a vehicle, a train, an aerial vehicle (AV), a ship, or the like.

[0607] Referring to FIG. 23, the vehicle or the autonomous driving vehicle 100 includes 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 is part of the communication unit 110. Each of the blocks 110 / 130 / 140a to 140d corresponds to the blocks 110 / 130 / 140 in FIG. 21.

[0608] The communication unit 110 transmits and receives signals (such as data, control signals, etc.) to and from external devices such as other vehicles, base stations (e.g., base stations, roadside units, etc.), and servers. The control unit 120 controls elements of the vehicle or the autonomous driving vehicle 100 to perform various operations. The control unit 120 includes an ECU (Electronic Control Unit). The driving unit 140a causes the vehicle or the autonomous driving vehicle 100 to travel on the ground. The driving unit 140a includes an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit 140b supplies power to the vehicle or the autonomous driving vehicle 100 and includes a wired / wireless charging circuit, a battery, etc. The sensor unit 140c can obtain vehicle state, surrounding environment information, user information, etc. The sensor unit 140c includes an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight sensing 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 implements technologies such as maintaining the lane during driving, automatically adjusting the speed like an adaptive cruise control, automatically driving along a predetermined route, and automatically setting and driving along a route when a destination is set.

[0609] As an example, the communication unit 110 receives map data, traffic information data, etc. from an external server. The autonomous driving unit 140d generates an autonomous driving route and a drive plan based on the obtained data. The control unit 120 controls the drive unit 140a so that the vehicle or the autonomous driving vehicle 100 moves along the autonomous driving route according to the drive plan (for example, speed / direction adjustment). The communication unit 110 periodically obtains the latest traffic information data from the external server during autonomous driving and also obtains the surrounding traffic information data from the surrounding vehicles. Further, the sensor unit 140c obtains the vehicle state and the surrounding environment information during autonomous driving. The autonomous driving unit 140d updates the autonomous driving route and the drive plan based on the newly obtained data / information. The communication unit 110 transmits information regarding the vehicle position, the autonomous driving route, the drive plan, etc. to the external server. The external server can predict the traffic information data in advance using AI technology, etc. based on the information collected from the vehicle or the autonomous driving vehicle and provide the predicted traffic information data to the vehicle or the autonomous driving vehicle.

[0610] Here, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification includes not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology is an example of LPWAN (Low Power Wide Area Network) technology, and is implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-mentioned names. Further or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification communicates based on LTE-M technology. At this time, as an example, LTE-M technology is an example of LPWAN technology, and is also called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology is implemented in any of various standards such as 1) LTE CAT0, 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-mentioned names. Further or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification includes any of ZigBee (registered trademark), Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-mentioned names. As an example, ZigBee (registered trademark) technology generates PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE802.15.4, and is called by various names.

[0611] The embodiments described above combine the components and features of the present invention in a predetermined form. Each component or feature is considered optional unless otherwise explicitly stated. Each component or feature can be implemented in a form that does not combine with other components or features, or some components and / or features can be combined to form embodiments of the present invention. The order of operations described in the embodiments of the present invention may be changed. Some components and features of one embodiment may be included in other embodiments, or may replace the corresponding components or features of other embodiments. It is obvious that claims that are not in an explicit citation relationship in the claims can be combined to form embodiments, or included as new claims by amendments after filing.

[0612] In this specification, the embodiments of this invention are mainly described centering on the signal transmission and reception relationship between the terminal and the base station. Such a transmission and reception relationship can be similarly / identically extended to the signal transmission and reception between the terminal and the relay or between the base station and the relay. The specific operations assumed to be performed by the 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 the terminal in a network composed of a plurality of network nodes including the base station can be performed by the base station or other network nodes other than the base station. The base station may be referred to by terms such as fixed station, Node b, eNode b (eNB), access point, etc. Also, the terminal may be referred to by terms such as UE (User Equipment), MS (Mobile Station), MSS (Mobile Subscriber Station), etc.

[0613] Embodiments according to the present invention are implemented by various means, such as hardware, firmware, software, or combinations thereof. In the case of implementation by hardware, an embodiment of the present invention is 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.

[0614] In the case of implementation by firmware or software, an embodiment of the present invention is implemented in the form of modules, procedures, functions, etc. that perform the functions or operations described above. The software code is stored in a memory and driven by a processor. The memory unit is provided inside or outside the processor and exchanges data with the processor by various known means.

[0615] It is obvious to those skilled in the art that the present invention can be embodied in other specific forms without departing from the features of the present invention. Therefore, the above detailed description should not be construed as restrictive in all aspects and should be considered as exemplary. The scope of the present invention must be determined by a reasonable interpretation of the appended claims, and all changes within the equivalent scope of the present invention are included in the scope of the present invention.

Industrial Applicability

[0616] The present invention can be applied to terminals, base stations, or other devices in a wireless mobile communication system.

Claims

1. In a wireless communication system, a method for a first UE (user equipment) to set a multi-hop wireless communication path, comprising: performing a procedure for setting a first path related to a direct connection to a network, and while the first UE is in an RRC (radio resource control) connection state in which the first path is set, transmitting a sidelink message to a second UE set as a relay UE between the network and the first UE to add a second path related to an indirect connection to the network, wherein, based on the fact that the second UE is not in an RRC connection state, a random access procedure of the second UE is triggered by the transmission of the sidelink message of the first UE.

2. The method according to claim 1, wherein the second UE not in an RRC connection state performs the random access procedure to request an RRC connection to the network.

3. The method according to claim 1, wherein the first UE requests the second UE to perform the random access procedure.

4. The method according to claim 1, wherein based on the second UE being RRC-connected to the network, the second path related to the indirect connection to the network is set.

5. The method according to claim 1, wherein the first UE is set with the first path related to the direct connection to the network and the second path related to the indirect connection to the network.

6. The method according to claim 1, wherein the sidelink message is directly transmitted to the second UE via a sidelink interface between the first UE and the second UE.

7. The method according to claim 1, wherein the sidelink message includes information indicating that the sidelink message is related to the multi-path setting of the first UE.

8. The method according to claim 1, further comprising receiving, via the first path, an RRC reconfiguration message including information for additionally setting the second path to the first path from the network.

9. The method according to claim 8, wherein the sidelink message is transmitted based on the RRC reconfiguration message.

10. The method according to claim 8, further comprising transmitting an RRC reconfiguration complete message to the network via the first path or the second path based on the second path being additionally configured in the first path.

11. The method according to claim 1, wherein the first UE operates as a remote UE in the second path related to the indirect connection.

12. A computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform the method according to claim 1.

13. An apparatus for wireless communication, a memory configured to store instructions, and a processor configured to execute the instructions to perform operations, wherein the operations performed by the processor include executing a procedure for setting a first path related to a direct connection to a network, and transmitting a sidelink message for adding a second path related to an indirect connection to the network to another apparatus configured as a relay apparatus between the network and the apparatus while the apparatus is in an RRC (radio resource control) connection state in which the first path is set, wherein the random access procedure of the other apparatus is triggered by the transmission of the sidelink message of the apparatus based on the other apparatus not being in an RRC connection state.

14. The apparatus according to claim 13, wherein the apparatus is an ASIC (application-specific integrated circuit) or a digital signal processor.

15. The apparatus according to claim 13, wherein the apparatus is a UE (user equipment) operating in a wireless communication system based on 3GPP (registered trademark) (3rd generation partnership project).

Images