Method of operating relay UE related to configuration of UE-to-UE relay connection in wireless communication system

Abstract

According to an embodiment, a method of operating a user equipment (UE) related to a configuration of a UE-to-UE relay connection in a wireless communication system comprises the steps of: receiving a first sidelink radio resource control (SL RRC) message from a source remote UE; establishing an SL connection with the source remote UE; after establishing the SL connection with the source remote UE, sending a second SL RRC message to the target remote UE; establishing an SL connection with the target remote UE; and transmitting a message for the SL connection sent by the source remote UE to the target remote UE after the SL connection is established with the target remote UE.

Description

Technical Field

[0001] The following description relates to wireless communication systems, and more particularly, to methods and apparatus for establishing a connection between a source remote user equipment (UE) and a target remote UE for UE-to-UE relay operations. Background Art

[0002] Wireless communication systems employ various radio access technologies (RATs) such as Long Term Evolution (LTE), Advanced LTE (LTE-A), and Wireless Fidelity (WiFi). The fifth generation (5G) is also included in the RATs. The three key areas of demand for 5G are (1) enhanced mobile broadband (eMBB), (2) massive machine type communications (mMTC), and (3) ultra-reliable low latency communications (URLLC). Some use cases may require multiple dimensions for optimization, while other use cases may focus on only one key performance indicator (KPI). 5G supports these various use cases in a flexible and reliable manner.

[0003] eMBB goes far beyond basic mobile Internet access and covers rich interactive work, media and entertainment applications in the cloud or augmented reality (AR). Data is one of the key drivers of 5G, and in the 5G era, dedicated voice services may not be seen for the first time. In 5G, it is expected that voice will be processed as an application using only the data connectivity provided by the communication system. The main driving force for the increase in traffic is the increase in the number of applications requiring high data rates and the increase in content size. As more and more devices are connected to the Internet, streaming services (audio and video), interactive video and mobile Internet connections will continue to be widely used. Many of these applications require always-on connections to push real-time information and notifications to users. Cloud storage and applications for mobile communication platforms are increasing rapidly. This applies to both work and entertainment. Cloud storage is a specific use case that drives the growth of uplink data rates. 5G will also be used for remote work in the cloud, which requires much lower end-to-end latency when done with a tactile interface to maintain a good user experience. Entertainment (e.g., cloud games and video streaming) is another key driver for increasing demand for mobile broadband capabilities. Entertainment will be critical for smartphones and tablets everywhere, including high-mobility environments such as trains, cars and airplanes. Another use case is augmented reality (AR) for entertainment and information search, which requires very little latency and a large amount of real-time data.

[0004] One of the most anticipated 5G use cases is the ability to actively connect embedded sensors in every field (i.e., mMTC). It is expected that there will be 20.4 billion potential Internet of Things (IoT) devices by 2020. In industrial IoT, 5G is one of the areas that will play a key role in enabling smart cities, asset tracking, smart utilities, agriculture, and secure infrastructure.

[0005] URLLC includes services that will revolutionize industries using ultra-reliable / available low-latency links, such as remote control of critical infrastructure and autonomous vehicles. The levels of reliability and latency are critical for smart grid control, industrial automation, robotics, drone control and coordination, etc.

[0006] Now, a number of use cases will be described in detail.

[0007] 5G can complement fiber-to-the-home (FTTH) and cable-based broadband (or cable data service interface specification (DOCSIS)) as a means of delivering streams with data rates ranging from hundreds of megabits per second to gigabits per second. Such high speeds are required for virtual reality (VR) and AR, as well as TV broadcasts with resolutions of 4K or higher (6K, 8K, or higher). VR and AR applications mainly include immersive sports events. Specific applications may require special network configurations. For example, for VR games, gaming companies may have to integrate core servers with network operators' edge network servers in order to minimize latency.

[0008] The automotive industry is expected to become a very important new driver of 5G, with many use cases for mobile communications in vehicles. For example, entertainment for passengers requires both high-capacity and high-mobility mobile broadband, because future users will expect to always have a high-quality connection, regardless of their location and speed. Other use cases in the automotive industry are AR dashboards. These dashboards display superimposed information on what the driver is seeing through the front window, identify objects in the dark, and inform the driver of the distance and movement of objects. In the future, wireless modules will enable communication between the vehicles themselves, information exchange between the vehicle and the supporting infrastructure, and information exchange between the vehicle and other connected devices (for example, devices carried by pedestrians). Safety systems can guide drivers to take alternative courses of action to enable them to drive more safely and reduce the risk of accidents. The next stage will be remotely controlled or autonomous vehicles. This requires very reliable and very fast communication between different autonomous vehicles and between vehicles and infrastructure. In the future, autonomous vehicles will perform all driving activities while the driver focuses on the elusive traffic anomalies of the vehicle itself. The technical requirements for autonomous vehicles require ultra-low latency and ultra-high reliability, thereby increasing traffic safety to a level that cannot be achieved by humans.

[0009] Smart cities and smart homes, often referred to as smart societies, will be embedded with dense wireless sensor networks. Distributed networks of smart sensors will confirm the cost and energy efficiency maintenance conditions of a city or home. A similar setup can be made for each home, where temperature sensors, window and heating controls, burglar alarms, and home appliances are all connected wirelessly. Many of these sensors are typically characterized by low data rates, low power, and low cost, but real-time high-definition (HD) video may be required, for example, in some types of surveillance installations.

[0010] The consumption and distribution of energy, including heat or gas, is becoming highly decentralized, creating a need for automatic control of very decentralized sensor networks. Smart grids interconnect these sensors using digital information and communication technologies to collect and act on information. This information can include information about the behavior of suppliers and consumers, enabling smart grids to improve the efficiency, reliability, economic viability, and sustainability of production of fuels such as electricity in an automated manner. Smart grids can be viewed as another sensor network with less latency.

[0011] The health sector has many applications that can benefit from mobile communications. Communication systems enable telemedicine, which provides clinical care at a distance. It helps to eliminate distance barriers and improve access to medical services that are often not consistently available in remote rural communities. It can also be used to save lives in critical care and emergency situations. Wireless sensor networks based on mobile communications can provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

[0012] Wireless and mobile communications are becoming increasingly important for industrial applications. Wires are expensive to install and maintain, and the possibility of replacing cables with reconfigurable wireless links is an attractive opportunity for many industries. However, to achieve this, wireless connections need to operate with latency, reliability, and capacity close to cables, and to be easier to manage. Low latency and very low error probability are new requirements that 5G needs to address.

[0013] Finally, logistics and freight tracking are important use cases for mobile communications to enable tracking of inventory and packages wherever they are located using location-based information systems. Logistics and freight tracking use cases typically require lower data speeds, but wide coverage and reliable location information.

[0014] A wireless communication system is a multiple-access system that supports communication for multiple users by sharing available system resources (bandwidth, transmit power, etc.) Examples of multiple-access systems include CDMA systems, FDMA systems, TDMA systems, OFDMA systems, SC-FDMA systems, and MC-FDMA systems.

[0015] Sidelink (SL) refers to a communication scheme in which a direct link is established between a user equipment (UE) and the UEs and the UEs directly exchange voice or data without intervention of a base station (BS). SL is considered a solution to alleviate the rapidly growing data traffic constraints of the BS.

[0016] Vehicle-to-everything (V2X) is a communication technology in which a vehicle exchanges information with another vehicle, pedestrians, and infrastructure through wired / wireless communications. V2X can be divided into four types: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). V2X communication can be provided via a PC5 interface and / or a Uu interface.

[0017] As more and more communication devices require greater communication capacity, enhanced mobile broadband communication relative to existing RATs is needed. Therefore, communication systems that take into account services or UEs that are sensitive to reliability and latency are being discussed. The next generation RAT that takes into account eMBB, MTC, and URLLC is called new RAT or NR. In NR, V2X communication can also be supported.

[0018] Figure 1 2 is a diagram illustrating a comparison between V2X communication based on a RAT prior to NR and V2X communication based on NR.

[0019] For V2X communication, the technology of providing security services based on V2X messages such as Basic Security Message (BSM), Collaborative Awareness Message (CAM) and Decentralized Environment Notification Message (DENM) is mainly discussed in the pre-NR RAT. V2X messages may include location information, dynamic information and attribute information. For example, a UE may send a CAM of a periodic message type and / or a DENM of an event-triggered type to another UE.

[0020] For example, CAM may include basic vehicle information, including dynamic status information such as direction and speed, vehicle static data such as size, external lighting status, path details, etc. For example, UE may broadcast CAM, and the waiting time of CAM may be less than 100ms. For example, when an unexpected event such as vehicle damage or accident occurs, UE may generate DENM and send DENM to another UE. For example, all vehicles within the transmission range of UE may receive CAM and / or DENM. In this case, DENM may have a higher priority than CAM.

[0021] Regarding V2X communication, various V2X scenarios are proposed in NR. For example, V2X scenarios include vehicle platooning, advanced driving, extended sensors, and remote driving.

[0022] For example, vehicles can be dynamically grouped and driven together based on vehicle platooning. For example, to perform platooning operations based on vehicle platooning, vehicles in a group can receive periodic data from a leading vehicle. For example, vehicles in a group can widen or narrow their gaps based on the periodic data.

[0023] For example, based on advanced driving, the vehicles can be semi-autonomous or fully autonomous. For example, each vehicle can adjust trajectory or maneuver based on data obtained from nearby vehicles and / or nearby logical entities. For example, each vehicle can also share driving intent with nearby vehicles.

[0024] For example, based on the extended sensor, raw or processed data or real-time video data obtained by local sensors can be exchanged between vehicles, logical entities, pedestrian terminals and / or V2X application servers. Therefore, the vehicle can perceive a high-level environment relative to the environment that can be perceived by the vehicle's sensors.

[0025] For example, based on remote driving, remote drivers or V2X applications can operate or control remote vehicles on behalf of people who are unable to drive or are in dangerous environments. For example, cloud-based driving can be used to operate or control remote vehicles when the path can be predicted as in public transportation. For example, access to a cloud-based backend service platform can also be used for remote driving.

[0026] In NR-based V2X communications, schemes for specifying service requirements for various V2X scenarios including vehicle platooning, advanced driving, extended sensors, and remote driving are discussed. Summary of the invention

[0027] Technical issues

[0028] The present disclosure aims to provide a method and apparatus for establishing a connection between a source remote user equipment UE and a target remote UE for UE-to-UE relay operation.

[0029] Technical Solution

[0030] In an embodiment, the present invention provides an operation method of a relay UE related to connection establishment from a user equipment (UE) to a UE relay in a wireless communication system. The method may include the following steps: receiving a first side link radio resource control (SL RRC) message from a source remote UE by the relay UE; establishing a side link (SL) connection with the source remote UE by the relay UE; after establishing the SL connection with the source remote UE, sending a second SLRRC message to a target remote UE by the relay UE; establishing a SL connection with the target remote UE by the relay UE; and after establishing the SL connection with the target remote UE, forwarding a message for the SL connection sent by the source remote UE to the target remote UE by the relay UE.

[0031] In an embodiment, the present invention provides a relay UE in a wireless communication system. The relay UE may include: at least one processor; and at least one computer memory, the at least one computer memory being capable of being operatively connected to the at least one processor and configured to store instructions, the instructions causing the at least one processor to perform operations when executed. The operations may include: receiving a first SL RRC message from a source remote UE; establishing a SL connection with the source remote UE; after establishing the SL connection with the source remote UE, sending a second SL RRC message to a target remote UE; establishing a SL connection with the target remote UE; and after establishing the SL connection with the target remote UE, forwarding to the target remote UE a message for the SL connection sent by the source remote UE.

[0032] In an embodiment, a non-volatile computer-readable storage medium is provided herein, and the non-volatile computer-readable storage medium is configured to store at least one computer program including instructions, and the instructions, when executed by at least one processor, cause the at least one processor to perform operations for a relay UE. The operations may include: receiving a first SL RRC message from a source remote UE; establishing a SL connection with the source remote UE; after establishing the SL connection with the source remote UE, sending a second SL RRC message to a target remote UE; establishing a SL connection with the target remote UE; and after establishing the SL connection with the target remote UE, forwarding to the target remote UE a message for the SL connection sent by the source remote UE.

[0033] The first SL RRC message may include identifier (ID) information about the target remote UE.

[0034] The second SL RRC message may include ID information about the source remote UE.

[0035] The target remote UE may be one of a plurality of UEs establishing a SL connection with the source remote UE.

[0036] The ID information about the target remote UE may be a layer 2 (L2) ID of the target remote UE.

[0037] The first SL RRC message may be a RRCReconfigurationSidelink message.

[0038] The ID information about the source remote UE may be an L2 ID of the source remote UE.

[0039] The second SL RRC message may be a RRCReconfigurationSidelink message.

[0040] The second SL RRC message may include information indicating a SL connection for a UE-to-UE relay operation.

[0041] The relay UE may communicate with at least one of another UE, a UE associated with an autonomous vehicle, a base station, or a network.

[0042] Beneficial Effects

[0043] According to an embodiment of the present disclosure, configuration for UE-to-UE (U2U) relay operation may be performed in steps. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The accompanying drawings, which are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this application, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure. In the drawings:

[0045] Figure 1 is a diagram for illustrating a comparison between vehicle-to-everything (V2X) communication based on a pre-new radio (NR) access technology (RAT) and NR-based V2X communication.

[0046] Figure 2 The structure of a Long Term Evolution (LTE) system according to an embodiment of the present disclosure is illustrated.

[0047] Figure 3 The radio protocol architecture of the user plane and the control plane according to the embodiments of the present disclosure is illustrated.

[0048] Figure 4 A structure of a New Radio (NR) system according to an embodiment of the present disclosure is illustrated.

[0049] Figure 5The functional split between the next generation radio access network (NG-RAN) and the fifth generation core network (5GC) according to an embodiment of the present disclosure is illustrated.

[0050] Figure 6 The structure of a radio frame of NR to which the embodiment is applicable is illustrated.

[0051] Figure 7 The structure of a time slot in an NR frame according to an embodiment of the present disclosure is illustrated.

[0052] Figure 8 A radio protocol architecture for side link (SL) communication according to an embodiment of the present disclosure is illustrated.

[0053] Fig. 9 A radio protocol architecture for SL communication according to an embodiment of the present disclosure is illustrated.

[0054] Fig.10 A synchronization source or synchronization reference of V2X according to an embodiment of the present disclosure is illustrated.

[0055] Fig.11 A process in which a user equipment (UE) performs V2X or SL communication according to a transmission mode according to an embodiment of the present disclosure is illustrated.

[0056] Fig.12 A process in which a UE performs a path switching according to an embodiment of the present disclosure is illustrated.

[0057] Fig.13 Direct to indirect path switching is illustrated.

[0058] Figures 14 to 18 are diagrams for explaining the embodiment; and

[0059] Figures 19 to 25 The diagrams are for explaining various devices to which the embodiments are applied. DETAILED DESCRIPTION

[0060] In various embodiments of the present disclosure, " / " and "," should be interpreted as "and / or". For example, "A / B" may mean "A and / or B". In addition, "A, B" may mean "A and / or B". In addition, "A / B / C" may mean "at least one of A, B and / or C". In addition, "A, B, C" may mean "at least one of A, B and / or C".

[0061] In various embodiments of the present disclosure, "or" should be interpreted as "and / or". For example, "A or B" may include "only A", "only B", or "both A and B". In other words, "or" should be interpreted as "additionally or alternatively".

[0062] The technology described herein can be used for various wireless access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. CDMA can be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as a radio technology such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rate for GSM Evolution (EDGE). OFDMA can be implemented as a radio technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Evolved UTRA (E-UTRA), etc. IEEE802.16m is an evolution of IEEE 802.16e, providing backward compatibility with IRRR 802.16e-based systems. UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using Evolved UTRA (E-UTRA). 3GPP LTE adopts OFDMA for downlink (DL) and SC-FDMA for uplink (UL). LTE Advanced (LTE-A) is an evolution of 3GPP LTE.

[0063] The successor to LTE-A - the 5th generation (5G) new radio access technology (NR) is a new clean-state mobile communication system characterized by high performance, low latency and high availability. 5G NR can use all available spectrum resources, including low frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high frequency (millimeter) bands of 24 GHz or above.

[0064] Although the following description is mainly given in the context of LTE-A or 5G NR for the sake of clarity, the technical ideas of the embodiments of the present disclosure are not limited thereto.

[0065] Figure 2 The structure of the LTE system according to the embodiment of the present disclosure is illustrated. This may also be referred to as an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) or an LTE / LTE-A system.

[0066] Reference Figure 2, E-UTRAN includes an evolved Node B (eNB) 20 that provides a control plane and a user plane to UE 10. UE 10 may be fixed or mobile, and may also be referred to as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), or a wireless device. eNB 20 is a fixed station that communicates with UE 10, and may also be referred to as a base station (BS), a base transceiver system (BTS), or an access point.

[0067] The eNBs 20 may be connected to each other via an X2 interface. The eNBs 20 are connected to an Evolved Packet Core (EPC) 39 via an S1 interface. More specifically, the eNBs 20 are connected to a Mobility Management Entity (MME) via an S1-MME interface, and to a Serving Gateway (S-GW) via an S1-U interface.

[0068] The EPC 30 includes an MME, an S-GW, and a packet data network gateway (P-GW). The MME has access information or capability information about the UE, which is mainly used for mobility management of the UE. The S-GW is a gateway with the E-UTRAN as an endpoint, and the P-GW is a gateway with a packet data network (PDN) as an endpoint.

[0069] Based on the lowest three layers of the open system interconnection (OSI) reference model known in communication systems, the radio protocol stack between the UE and the network can be divided into layer 1 (L1), layer 2 (L2), and layer 3 (L3). These layers are defined in pairs between the UE and the evolved UTRAN (E-UTRAN) for data transmission via the Uu interface. The physical (PHY) layer at L1 provides information transfer services on physical channels. The radio resource control (RRC) layer at L3 is used to control radio resources between the UE and the network. For this purpose, the RRC layer exchanges RRC messages between the UE and the eNB.

[0070] Figure 3 (a) in FIG. 1 illustrates a user plane radio protocol architecture according to an embodiment of the present disclosure.

[0071] Figure 3 (b) in FIG. 1 illustrates a control plane radio protocol architecture according to an embodiment of the present disclosure. The user plane is a protocol stack for user data transmission, and the control plane is a protocol stack for control signal transmission.

[0072] Reference Figure 3 (a) and Figure 3In (b), the PHY layer provides information transfer services to its higher layer on the physical channel. The PHY layer is connected to the medium access control (MAC) layer through a transport channel, and data is transferred between the MAC layer and the PHY layer on the transport channel. The transport channel is divided according to the characteristics used to send data via the radio interface.

[0073] Data is transmitted on a physical channel between different PHY layers (ie, the PHY layers of a transmitter and a receiver). The physical channel may be modulated by orthogonal frequency division multiplexing (OFDM) and uses time and frequency as radio resources.

[0074] The MAC layer provides services to the higher layer, Radio Link Control (RLC), on logical channels. The MAC layer provides the function of mapping from multiple logical channels to multiple transport channels. In addition, the MAC layer provides a logical channel multiplexing function by mapping multiple logical channels to a single transport channel. The MAC sublayer provides data transmission services on logical channels.

[0075] The RLC layer performs concatenation, segmentation, and reassembly of RLC service data units (SDUs). To guarantee various quality of service (QoS) requirements for each radio bearer (RB), the RLC layer provides three operation modes—transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). AM RLC provides error correction through automatic repeat request (ARQ).

[0076] The RRC layer is defined only in the control plane, and controls logical channels, transport channels, and physical channels in relation to configuration, reconfiguration, and release of RBs. RBs refer to logical paths for data transmission between UEs and networks provided by L1 (PHY layer) and L2 (MAC layer, RLC layer, and Packet Data Convergence Protocol (PDCP) layer).

[0077] The user plane functions of the PDCP layer include user data transmission, header compression and encryption. The control plane functions of the PDCP layer include control plane data transmission and encryption / integrity protection.

[0078] RB establishment is equivalent to the process of defining radio protocol layers and channel characteristics and configuring specific parameters and operation methods in order to provide specific services. RB can be divided into two types - signaling radio bearer (SRB) and data radio bearer (DRB). SRB is used as a path for sending RRC messages on the control plane, while DRB is used as a path for sending user data on the user plane.

[0079] Once an RRC connection is established between the RRC layer of the UE and the RRC layer of the E-UTRAN, the UE is in the RRC_CONNECTED state, otherwise the UE is in the RRC_IDLE state. In NR, the RRC_INACTIVE state is additionally defined. A UE in the RRC_INACTIVE state can maintain a connection with the core network while releasing the connection from the eNB.

[0080] The DL transport channels that carry data from the network to the UE include a broadcast channel (BCH) on which system information is sent and a DL shared channel (DL SCH) on which user traffic or control messages are sent. Traffic or control messages for DL ​​multicast or broadcast services may be sent on a DL-SCH or a DL multicast channel (DL MCH). The UL transport channels that carry data from the UE to the network include a random access channel (RACH) on which initial control messages are sent and a UL shared channel (UL SCH) on which user traffic or control messages are sent.

[0081] Logical channels above and mapped to the transport channels include a Broadcast Control Channel (BCCH), a Paging Control Channel (PCCH), a Common Control Channel (CCCH), a Multicast Control Channel (MCCH), and a Multicast Traffic Channel (MTCH).

[0082] A physical channel includes multiple OFDM symbols in the time domain multiplied by multiple subcarriers in the frequency domain. A subframe includes multiple OFDM symbols in the time domain. An RB is a resource allocation unit defined by multiple OFDM symbols multiplied by multiple subcarriers. In addition, each subframe may use a specific subcarrier of a specific OFDM symbol (e.g., the first OFDM symbol) in the corresponding subframe for a physical DL control channel (PDCCH), i.e., an L1 / L2 control channel. A transmission time interval (TTI) is a unit time for subframe transmission.

[0083] Figure 4 The structure of the NR system according to an embodiment of the present disclosure is illustrated.

[0084] Reference Figure 4 , the next generation radio access network (NG-RAN) may include next generation Node Bs (gNBs) and / or eNBs that provide user plane and control plane protocol terminations to the UE. Figure 4 In the figure, for example, NG-RAN is shown as including only gNB. gNB and eNB are connected to each other via Xn interface. gNB and eNB are connected to 5G core network (5GC) via NG interface. More specifically, gNB and eNB are connected to access and mobility management function (AMF) via NG-C interface, and to user plane function (UPF) via NG-U interface.

[0085] Figure 5 The functional division between NG-RAN and 5GC according to an embodiment of the present disclosure is illustrated.

[0086] Reference Figure 5 , gNB can provide functions including inter-cell radio resource management (RRM), radio admission control, measurement configuration and provision, and dynamic resource allocation. AMF can provide functions such as non-access stratum (NAS) security and idle state mobility processing. UPF can provide functions including mobility anchoring and protocol data unit (PDU) processing. Session management function (SMF) can provide functions including UE Internet Protocol (IP) address allocation and PDU session control.

[0087] Figure 6 The radio frame structure in NR to which the embodiments of the present disclosure are applicable is illustrated.

[0088] Reference Figure 6 , a radio frame can be used for UL transmission and DL transmission in NR. The length of a radio frame is 10ms and can be defined by two 5ms half frames. HF may include five 1ms subframes. A subframe may be divided into one or more slots, and the number of slots in a SF may be determined according to a subcarrier spacing (SCS). Each slot may include 12 or 14 OFDM (A) symbols depending on a cyclic prefix (CP).

[0089] In the case of normal CP (NCP), each time slot may include 14 symbols, and in the case of extended CP (ECP), each time slot may include 12 symbols. Herein, a symbol may be an OFDM symbol (or CP-OFDM symbol) or an SC-FDMA symbol (or DFT-s-OFDM symbol).

[0090] Table 1 below lists the number of symbols N per time slot according to the SCS configuration μ in the NCP case 时隙 符号 , the number of time slots per frame N 帧,u 时隙 And the number of time slots N in each subframe 子帧,u 时隙 .

[0091] [Table 1]

[0092] <![CDATA[SCS(15×2 u )]]> <![CDATA[N 时隙 符号 ]]> <![CDATA[N 帧,u 时隙 ]]> <![CDATA[N 子帧,u 时隙 ]]> 15KHz(u=0) 14 10 1 30KHz(u=1) 14 20 2 60KHz(u=2) 14 40 4 120KHz(u=3) 14 80 8 240KHz(u=4) 14 160 16

[0093] The following Table 2 lists the number of symbols per time slot, the number of time slots per frame, and the number of time slots per subframe according to SCS in the ECP case.

[0094] [Table 2]

[0095] SCS(15×2^u) <![CDATA[N 时隙 符号 ]]> <![CDATA[N 帧,u 时隙 ]]> <![CDATA[N 子帧,u 时隙 ]]> 60KHz(u=2) 12 40 4

[0096] In the NR system, different OFDM(A) parameter sets (e.g., SCS, CP length, etc.) may be configured for multiple cells aggregated for one UE. Therefore, the (absolute time) duration of a time resource (e.g., a subframe, a time slot, or a TTI) (collectively referred to as a time unit (TU) for convenience) including the same number of symbols may be configured to be different for the aggregated cells.

[0097] In NR, various parameter sets or SCS can be supported to support various 5G services. For example, with 15kHz SCS, wide areas in traditional cellular bands can be supported, while with 30kHz / 60kHz SCS, dense urban areas, lower latency and wide carrier bandwidth can be supported. With 60kHz or higher SCS, bandwidths greater than 24.25GHz can be supported to overcome phase noise.

[0098] The NR frequency band may be defined by two types of frequency ranges FR1 and FR2. The values ​​in each frequency range may vary. For example, two types of frequency ranges may be given in Table 3. In the NR system, FR1 may be a "range below 6 GHz" and FR2 may be a "range above 6 GHz" known as millimeter wave (mmW).

[0099] [Table 3]

[0100] Frequency range specification Corresponding frequency range Subcarrier Spacing (SCS) FR1 450MHz–6000MHz 15, 30, 60kHz FR2 24250MHz–52600MHz 60, 120, 240kHz

[0101] As mentioned above, in the NR system, the values ​​in the frequency range can be changed. For example, as listed in Table 4, the range of FR1 can be from 410 MHz to 7125 MHz. That is, FR1 can include frequency bands of 6 GHz (or 5850, 5900, and 5925 MHz) or above. For example, frequency bands of 6 GHz (or 5850, 5900, and 5925 MHz) or above can include unlicensed frequency bands. Unlicensed frequency bands can be used for various purposes, for example, vehicle communications (e.g., autonomous driving).

[0102] [Table 4]

[0103] Frequency range specification Corresponding frequency range Subcarrier Spacing (SCS) FR1 410MHz–7125MHz 15, 30, 60kHz FR2 24250MHz–52600MHz 60, 120, 240kHz

[0104] Figure 7 The time slot structure in the NR frame according to an embodiment of the present disclosure is illustrated.

[0105] Reference Figure 7, a time slot includes multiple symbols in the time domain. For example, a time slot may include 14 symbols in the NCP case and 12 symbols in the ECP case. Alternatively, a time slot may include 7 symbols in the NCP case and 6 symbols in the ECP case.

[0106] A carrier includes multiple subcarriers in the frequency domain. An RB can be defined by multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) can be defined by multiple consecutive (physical) RBs ((P)RBs) in the frequency domain and corresponds to a parameter set (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed in an activated BWP. Each element can be referred to as a resource element (RE) in a resource grid, and a complex symbol can be mapped to an RE.

[0107] The radio interface between UEs or the radio interface between UE and the network may include L1, L2 and L3. In various embodiments of the present disclosure, L1 may refer to a PHY layer. For example, L2 may refer to at least one of a MAC layer, an RLC layer, a PDCH layer or an SDAP layer. For example, L3 may refer to an RRC layer.

[0108] Now, a description will be given of the side link (SL) communication.

[0109] Figure 8 The radio protocol architecture for SL communication according to an embodiment of the present disclosure is illustrated. Specifically, Figure 8 (a) in FIG. 1 illustrates a user plane protocol stack in LTE, and Figure 8 (b) in FIG. 1 illustrates an example of the control plane protocol stack in LTE.

[0110] Fig. 9 The radio protocol architecture for SL communication according to an embodiment of the present disclosure is illustrated. Specifically, Fig. 9 (a) in FIG. 1 illustrates an example of a user plane protocol stack in NR, and Fig. 9 (b) in FIG. 4 illustrates the control plane protocol stack in NR.

[0111] Fig.10 A synchronization source or synchronization reference of V2X according to an embodiment of the present disclosure is illustrated.

[0112] refer to Fig.10In V2X, the UE can synchronize directly with the Global Navigation Satellite System (GNSS). Alternatively, the UE can synchronize indirectly with the GNSS through another UE (in or out of network coverage). If GNSS is configured as the synchronization source, the UE can calculate the direct frame number (DFN) and subframe number based on the Coordinated Universal Time (UTC) and the configured (preconfigured) DFN offset.

[0113] Alternatively, the UE may be synchronized directly with the BS or may be synchronized with another UE that is synchronized with the BS in time / frequency. For example, the BS may be an eNB or a gNB. For example, when the UE is within network coverage, the UE may receive synchronization information provided by the BS and may be synchronized directly with the BS. Next, the UE may provide synchronization information to another neighboring UE. If the timing of the BS is configured as a synchronization reference, the UE may follow the cell associated with the corresponding frequency (when the UE is within the cell coverage on the frequency) or the primary cell or serving cell (when the UE is not within the cell coverage on the frequency) for synchronization and DL measurements.

[0114] The BS (e.g., serving cell) may provide a synchronization configuration of a carrier for V2X / SL communication. In this case, the UE may comply with the synchronization configuration received from the BS. If the UE fails to detect any cell in the carrier for V2X / SL communication and fails to receive a synchronization configuration from the serving cell, the UE may comply with the preset synchronization configuration.

[0115] Alternatively, the UE may synchronize with another UE that fails to directly or indirectly acquire synchronization information from the BS or GNSS. The synchronization source and preference may be preconfigured for the UE. Alternatively, the synchronization source and preference may be configured via a control message provided by the BS.

[0116] The SL synchronization source may be associated with the synchronization priority. For example, the relationship between the synchronization source and the synchronization priority may be defined as shown in Table 14 or Table 15. Table 5 or Table 6 is only an example, and the relationship between the synchronization source and the synchronization priority may be defined in various ways.

[0117] [Table 5]

[0118] Priority GNSS-based synchronization BS-based synchronization (eNB / gNB-based synchronization) P0 Global Navigation Satellite System Base Station P1 All UEs synchronize directly with GNSS All UEs synchronize directly with the BS P2 All UEs are synchronized indirectly with GNSS All UEs are synchronized with the BS indirectly P3 All other UEs Global Navigation Satellite System P4 not applicable All UEs synchronize directly with GNSS P5 not applicable All UEs are synchronized indirectly with GNSS P6 not applicable All other UEs

[0119] [Table 6]

[0120]

[0121] In Table 5 or Table 6, P0 may represent the highest priority and P6 may represent the lowest priority. In Table 5 or Table 6, the BS may include at least one of a gNB or an eNB.

[0122] It can be (pre)configured whether GNSS-based synchronization or eNB / gNB-based synchronization is used. In single carrier operation, the UE can derive its transmission timing from the available synchronization reference with the highest priority.

[0123] Hereinafter, a side link synchronization signal (SLSS) and synchronization information will be described.

[0124] As a SL specific sequence, the SLSS may include a primary side link synchronization signal (PSSS) and a secondary side link synchronization signal (SSSS). The PSSS may be referred to as a side link primary synchronization signal (S-PSS), and the SSSS may be referred to as a side link secondary synchronization signal (S-SSS). For example, an M sequence of length 127 may be used for the S-PSS, and a gold sequence of length 127 may be used for the S-SSS. For example, the UE may use the S-PSS to detect an initial signal and obtain synchronization. In addition, the UE may use the S-PSS and the S-SSS to obtain detailed synchronization and detect a synchronization signal ID.

[0125] The physical sidelink broadcast channel (PSBCH) may be a (broadcast) channel for sending default (system) information that the UE needs to know first before sending and receiving SL signals. For example, the default information may include information related to SLSS, duplex mode (DM), time division duplex (TDD) UL / DL configuration, information related to resource pools, application types related to SLSS, subframe offsets, broadcast information, etc. For example, to evaluate the PSBCH performance in NR V2X, the payload size of the PSBCH may be 56 bits, including a 24-bit CRC.

[0126] S-PSS, S-SSS, and PSBCH may be included in a block format (e.g., SL synchronization signal (SS) / PSBCH block) that supports periodic transmission (hereinafter, the SLSS / PSBCH block is referred to as a sidelink synchronization signal block (S-SSB)). The S-SSB may have the same parameter set (i.e., SCS and CP length) as the physical sidelink control channel (PSCCH) / physical sidelink shared channel (PSSCH) on the carrier, and the transmission bandwidth may exist within a configured (or preconfigured) SL BWP. For example, the S-SSB may have a bandwidth of 11 RBs. For example, the PSBCH may span 11 RBs. In addition, the frequency position of the S-SSB may be configured (preconfigured). Therefore, the UE does not need to perform hypothetical detection of the frequency to discover the S-SSB on the carrier.

[0127] The NR SL system can support multiple parameter sets with different SCSs and / or different CP lengths. In this case, as the SCS increases, the length of the time resources used by the transmitting UE to send the S-SSB can be reduced. Therefore, the coverage of the S-SSB may be reduced. Therefore, in order to ensure the coverage of the S-SSB, the transmitting UE can send one or more S-SSBs to the receiving UE within an S-SSB transmission period based on the SCS. For example, the number of S-SSBs sent by the transmitting UE to the receiving UE within one S-SSB transmission period can be pre-configured or configured for the transmitting UE. For example, the S-SSB transmission period can be 160ms. For example, an S-SSB transmission period of 160ms can be supported for all SCSs.

[0128] For example, when the SCS in FR1 is 15kHz, the transmitting UE can send one or two S-SSBs to the receiving UE in one S-SSB transmission period. For example, when the SCS in FR1 is 30kHz, the transmitting UE can send one or two S-SSBs to the receiving UE in one S-SSB transmission period. For example, when the SCS in FR1 is 60kHz, the transmitting UE can send one, two, or four S-SSBs to the receiving UE in one S-SSB transmission period.

[0129] Fig.11 A process of performing V2X or SL communication by a UE according to a transmission mode according to an embodiment of the present disclosure is illustrated. Fig.11 The embodiments of the present disclosure may be combined with various embodiments of the present disclosure. In various embodiments of the present disclosure, the transmission mode may be referred to as a mode or a resource allocation mode. For the convenience of the following description, the transmission mode in LTE may be referred to as an LTE transmission mode, and the transmission mode in NR may be referred to as an NR resource allocation mode.

[0130] For example, Fig.11 (a) illustrates UE operation associated with LTE transmission mode 1 or LTE transmission mode 3. Or, for example, Fig.11 (a) illustrates UE operations related to NR resource allocation mode 1. For example, LTE transmission mode 1 can be applied to general SL communication, and LTE transmission mode 3 can be applied to V2X communication.

[0131] For example, Fig.11 (b) illustrates UE operation associated with LTE transmission mode 2 or LTE transmission mode 4. Or, for example, Fig.11 (b) illustrates UE operations associated with NR resource allocation mode 2.

[0132] refer to Fig.11(a), in LTE transmission mode 1, LTE transmission mode 3, or NR resource allocation mode 1, the BS may schedule SL resources to be used by the UE for SL transmission. For example, in step S8000, the BS may send information related to SL resources and / or information related to UE resources to the first UE. For example, the UL resources may include PUCCH resources and / or PUSCH resources. For example, the UL resources may be resources for reporting SL HARQ feedback to the BS.

[0133] For example, the first UE may receive information related to dynamic grant (DG) resources and / or information related to configuration grant (CG) resources from the BS. For example, the CG resources may include CG type 1 resources or CG type 2 resources. In the present specification, the DG resources may be resources that the BS configures / allocates to the first UE in downlink control information (DCI). In the present specification, the CG resources may be (periodic) resources that the BS configures / allocates to the first UE in the DCI and / or RRC message. For example, for CG type 1 resources, the BS may send an RRC message including information related to the CG resources to the first UE. For example, for CG type 2 resources, the BS may send an RRC message including information related to the CG resources to the first UE, and the BS may send a DCI for activation or release of the CG resources to the first UE.

[0134] In step S8010, the first UE may send a PSCCH (e.g., sidelink control information (SCI) or a first-level SCI) to the second UE based on resource scheduling. In step S8020, the first UE may send a PSSCH related to the PSCCH to the second UE (e.g., a second-level SCI, a MAC PDU, data, etc.). In step S8030, the first UE may receive a PSFCH related to the PSCCH / PSSCH from the second UE. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second UE via the PSFCH. In step S8040, the first UE may send / report HARQ feedback information to the BS via the PUCCH or PUSCH. For example, the HARQ feedback information reported to the BS may include information generated by the first UE based on the HARQ feedback information received from the second UE. For example, the HARQ feedback information reported to the BS may include information generated by the first UE according to a preset rule. For example, the DCI may be a DCI for scheduling of the SL. For example, the format of the DCI may include DCI format 3_0 or DCI format 3_1. Table 7 shows an example of DCI for scheduling of SL.

[0135] [Table 7]

[0136]

[0137]

[0138] refer to Fig.11 (b), in LTE transmission mode 2, LTE transmission mode 4 or NR resource allocation mode 2, the UE may determine the SL transmission resources within the SL resources configured by the BS / network or the pre-configured SL resources. For example, the configured SL resources or the pre-configured SL resources may be a resource pool. For example, the UE may select or schedule resources for SL transmission by itself. For example, the UE may perform SL communication by selecting resources by itself within the configured resource pool. For example, the UE may perform a sensing and resource (re)selection process to select resources by itself within a selection window. For example, sensing may be performed in units of subchannels. For example, in step S8010, a first UE that selects resources in a resource pool may use the resources to send a PSCCH (e.g., sidelink control information (SCI) or a first-level SCI) to a second UE. In step S8020, the first UE may send a PSSCH (e.g., a second-level SCI, a MAC PDU, data, etc.) related to the PSCCH to the second UE. In step S8030, the first UE may receive a PSFCH related to the PSCCH / PSSCH from the second UE.

[0139] refer to Fig.11 (a) or Fig.11 (b), for example, the first UE may send SCI to the second UE on the PSCCH. Or, for example, the first UE may send two consecutive SCIs (e.g., two-level SCIs) to the second UE on the PSCCH and / or PSSCH. In this case, the second UE may decode two consecutive SCIs (e.g., two-level SCIs) to receive the PSSCH from the first UE. In this specification, the SCI sent on the PSCCH may be referred to as the first SCI, the first-level SCI, or the first-level SCI format, and the SCI sent on the PSSCH may be referred to as the second SCI, the second SCI, or the second-level SCI format. For example, the first-level SCI format may include SCI format 1-A, and the second-level SCI format may include SCI format 2-A and / or SCI format 2-B. Table 8 shows an example of a first-level SCI format.

[0140] [Table 8]

[0141]

[0142]

[0143] Table 9 shows an exemplary second level SCI format.

[0144] [Table 9]

[0145]

[0146]

[0147] Reference Fig.11 (a) or Fig.11 (b) in the reference Fig.11 (a) or Fig.11 In (b), in step S8030, the first UE may receive the PSFCH based on Table 10. For example, the first UE and the second UE may determine the PSFCH resources based on Table 10, and the second UE may send HARQ feedback to the first UE on the PSFCH resources.

[0148] [Table 10]

[0149]

[0150]

[0151] Reference Fig.11 In (a), in step S8040, the first UE may send SL HARQ feedback to the BS via PUCCH and / or PUSCH based on Table 11.

[0152] [Table 11]

[0153]

[0154]

[0155] Table 12 below shows details of selection and reselection of SL relay UE defined in 3GPP TS 36.331. The content of Table 12 is used as the prior art of the present disclosure, and the relevant necessary details can be found in 3GPP TS 36.331.

[0156] [Table 12]

[0157]

[0158]

[0159] Fig.12 The connection management and the process of switching from direct to indirect path captured in the TR document (3GPP TR 38.836) related to Rel-17 NR SL are shown. The remote UE needs to establish its own PDU session / DRB with the network before user plane data transmission.

[0160] Before the remote UE establishes a Uu RRC connection with the network through the relay UE, the PC5 unicast link establishment procedure in the PC5-RRC aspect of Rel-16 NR V2X can be reused to establish a secure unicast link for L2 UE to network relay between the remote UE and the relay UE.

[0161] For both in-coverage and out-of-coverage, when the remote UE initiates the first RRC message for establishing a connection with the gNB, the PC5 L2 configuration for transmission between the remote UE and the UE to network relay UE can be based on the RLC / MAC configuration defined in the standard. The establishment of Uu SRB1 / SRB2 and DRBs for the remote UE follows the conventional Uu configuration procedure for L2 UE to network relay.

[0162] Fig.12 The high-level connection establishment procedure shown in is applied to L2 UE to network relay.

[0163] In operation S1200 , the remote UE and the relay UE may perform a discovery procedure, and in operation S1201 , establish a PC5-RRC connection based on an existing Rel-16 procedure.

[0164] In operation S1202, the remote UE may send a first RRC message (i.e., an RRC setup request (RRCSetupRequest)) for connection establishment with the gNB through the relay UE by using the default L2 configuration of PC5. The gNB responds to the remote UE with an RRC setup (RRCSetup) message (S1203). The transmission of the RRCSetup to the remote UE uses the default configuration of PC5. When the relay UE is not started in RRC_CONNECTED, the relay UE needs to perform its own connection setup after receiving a message about the default L2 configuration of PC5. In this operation, the details of the relay UE sending the RRCSetupRequest / RRCSetup message to the remote UE can be discussed in stage WI.

[0165] In operation S1204, the gNB and the relay UE perform a relay channel setup procedure via Uu. According to the configuration of the gNB, the relay / remote UE establishes an RLC channel for relaying SRB1 with the remote UE via PC5. In this operation, a relay channel for SRB1 is prepared.

[0166] In operation S1205, a remote UE SRB1 message (e.g., RRC Setup Complete message) is sent to the gNB via the relay UE using the SRB1 relay channel via PC5. The remote UE performs an RRC connection via Uu.

[0167] In operation S1206, the remote UE and the gNB configure security according to conventional procedures, and send a security message through the relay UE.

[0168] In operation S1210, the gNB configures an additional RLC channel between the gNB and the relay UE for service relay. According to the configuration of the gNB, the relay / remote UE configures an RLC channel between the remote UE and the relay UE for service relay. The gNB sends an RRC reconfiguration (RRCReconfiguration) to the remote UE through the relay UE to configure the relay SRB2 / DRB. The remote UE responds to the gNB sending an RRC reconfiguration completion (RRCReconfigurationComplete) through the relay UE.

[0169] For L2 UE to network relay except the connection establishment procedure:

[0170] -RRC reconfiguration and RRC disconnection procedures can reuse the traditional RRC procedures, where the message content / configuration design is left to phase WI.

[0171] -RRC connection reconfiguration and RRC connection recovery procedures can reuse existing RRC procedures as a baseline by considering the above L2 UE to network relay connection establishment procedure to handle the relay specific parts along with the message content / configuration design. The message content / configuration can be defined later.

[0172] Fig.13 Direct to indirect path switching is illustrated. For service continuity of L2 UE to network relay, when remote UE switches to indirect relay UE, Fig.13 process.

[0173] Reference Fig.13 In operation S1301, the remote UE measures / discovers candidate relay UEs and then reports one or more candidate relay UEs. The remote UE may filter out appropriate relay UEs that meet higher layer criteria during reporting. The report may include the ID and SL RSRP information of the relay UE, in which case the PC5 measurement details may be determined later.

[0174] In operation S1302, the gNB determines to switch to a target relay UE and optionally sends a target (re)configuration to the relay UE.

[0175] In operation S1304, the RRC reconfiguration message for the remote UE may include the ID of the target relay UE, the target Uu, and the PC5 configuration.

[0176] In operation S1305 , when the connection is not established, the remote UE establishes a PC5 connection with the target relay UE.

[0177] In operation S1306, the remote UE feeds back RRCReconfigurationComplete to the gNB via the target path by using the target configuration provided in RRCReconfiguration.

[0178] In operation S1307 , the data path is switched.

[0179] [Table 13]

[0180]

[0181]

[0182] Table 14 below corresponds to “New Rel-18 WID regarding NR sidelink relay enhancement”, which corresponds to the prior art of the present disclosure.

[0183] [Table 14]

[0184]

[0185] In UE-to-UE relay operation, in order to establish a sidelink (SL) connection between the source remote UE and the target BS (target gNB), the following three SL connections may need to be established.

[0186] -SL connection between source remote UE and relay UE.

[0187] -SL connection between relay UE and target remote UE.

[0188] -SL connection between source remote UE and target remote UE via an indirect link through a relay UE.

[0189] Hereinafter, a process of establishing a connection between a source remote UE and a target remote UE during a UE-to-UE relay operation will be described.

[0190] In an embodiment, the relay UE receives a first side link radio resource control (SL RRC) message from the source remote UE, and the relay UE may establish a SL connection with the source remote UE.

[0191] After establishing a SL connection with the source remote UE, the relay UE may send a second SL RRC message to the target remote UE. The relay UE may establish a SL connection with the target remote UE. After establishing a SL connection with the target remote UE, the relay UE may forward a message for the SL connection sent by the source remote UE to the target remote UE.

[0192] In other words, the connection configuration between the source remote UE and the target remote UE for UE-to-UE relay operation can be implemented as follows: The source remote UE and the relay UE establish a SL connection, the relay UE and the target remote UE establish a SL connection, and then the source remote UE and the target remote UE establish a SL connection.

[0193] The first SL RRC message may include information about the ID of the target remote UE. This is because the target remote UE may be one of multiple UEs that establish a SL connection with the source remote UE. In other words, a single relay UE may connect one source remote UE to multiple target remote UEs. Therefore, when the source remote UE establishes a SL connection, the relay UE may provide the ID of the target remote UE. The ID of the target remote UE (L2) may be included in the SL RRC message (e.g., RRCReconfigurationSidelink). The information about the ID of the target remote UE is the layer 2 ID (L2 ID) of the target remote UE, and the first SL RRC message may be an RRCReconfigurationSidelink message.

[0194] In addition, the second SL RRC message may include information about the ID of the source remote UE. The information about the ID of the source remote UE may be a layer 2 ID (L2 ID) of the source remote UE, and the second SL RRC message may be an RRCReconfigurationSidelink message. The second SL RRC message may include information indicating a SL connection for UE-to-UE relay operation.

[0195] Fig.15 The connection configuration between the source remote UE and the target remote UE for the above-mentioned UE-to-UE relay operation is illustrated.

[0196] Reference Fig.15 In step S1501 and step S1501-1, a SL connection is established between the source remote UE and the relay UE. Before this process, the source remote UE may have selected the relay UE.

[0197] In step S1501, when the relay UE receives a SL RRC message (first SLRRC message) related to the SL connection from the source remote UE, the relay UE can implicitly know which target remote UE the source remote UE expects to connect with by using the L2 ID of the source remote UE. This can be inferred because it is assumed that the source remote UE notifies the source remote UE of the target remote UE ID it expects to connect with through a PC5-S message in a higher layer message before the source remote UE selects the relay UE. It is assumed that the reason why the source remote UE establishes a SL connection with the relay UE is due to information reported by the relay UE indicating that the relay UE is able to connect with the target remote UE. After completing the SL connection with the source remote UE, the relay UE can attempt to establish a SL connection with the target BS.

[0198] Alternatively, since a single relay UE can connect one source remote UE to multiple target remote UEs, the source remote UE can provide the ID of the target remote UE when establishing the SL connection. In this case, the target remote UE (L2) ID can be included in the SL RRC message (e.g., RRCReconfigurationSidelink). Alternatively, after the source remote UE and the relay UE establish the SL connection, the source remote UE can notify the relay UE via a separate message (PC5-S or PC5-RRC) of the target remote UE ID to which the remote UE expects to connect. In this case, the source remote UE can indicate that the SL connection is for UE-to-UE relay operation.

[0199] In step S1501-1, after receiving the RRCReconfigurationSidelink message including the target remote UE (L2) ID, the relay UE reports the target remote UE ID to its higher layer and may forward the RRCReconfigurationCompleteSidelink message to the source remote UE.

[0200] In addition, when the RRCReconfigurationSidelink message sent by the source remote UE includes the target remote UE (L2) ID, when the target remote UE (L2) ID is received through a separate PC5-RRC message after the SL connection is established, or when a SL RRC message indicating that the SL connection is used for UE-to-UE relay operation is received, the SL connection establishment between the relay UE and the target remote UE is triggered.

[0201] In addition, when the source remote UE and the relay UE establish a SL connection, the relay UE may assign a local ( / time) ID to the source remote UE. The local ( / time) ID may be sent via a PC5-RRC ( / PC5-S) message. Alternatively, the relay UE may assign a local ( / time) ID after completing the SL connection with the target remote UE. In this case, the local ID may be assigned after step S1502 described below.

[0202] The local ID assigned from the relay UE to the source remote UE is a value for the target remote UE, and after the source remote UE receives the value, the source remote UE includes the local ID in a message sent to the target remote UE.

[0203] In step S1502 and step S1502-1, once the SL connection between the source remote UE and the relay UE is completed, the relay UE performs a SL connection with the target remote UE. In step S1502, the relay UE may send a SL RRC message (a first SL RRC message) (e.g., RRCReconfigurationSidelink) to the target remote UE. In this case, the relay UE may include the ID of the source remote UE (L2) in the SL RRC message (e.g., RRCReconfigurationSidelink). Alternatively, the relay UE may indicate that the SL connection is for UE-to-UE relay operation.

[0204] In step S1502-1, when the relay UE receives a message indicating that the SL connection is completed (e.g., RRCReconfigurationCompleteSidelink) from the target remote UE, the relay UE may need to notify the source remote UE. This can be done through PC5-S / SL-RRC messages.

[0205] In step S1501, if a local ID is not assigned, the relay UE may assign a local ID to the source remote UE after establishing a SL connection with the target remote UE. The local ID is used for the target remote UE. This value may be sent via an SL-S (SL-RRC) message, or may be sent via an RRCReconfigurationSidelink and / or RRCReconfigurationCompleteSidelink message.

[0206] A relay UE that has a SL connection with a source remote UE may assign a local ID to a target remote UE. The local ID is for the source remote UE.

[0207] The local ID assigned by the relay UE to the source UE and the local ID assigned to the target remote UE may be the same or different. Although the values ​​represented by each local ID are different for the source remote UE and the target remote UE, since these values ​​can be distinguished by L2 ID from the perspective of the relay UE, it is considered that using the same value for the local ID still allows distinction.

[0208] The relay UE may notify the target remote UE of the local ID value assigned to the source remote UE. In addition, the relay UE may notify the source remote UE of the local ID value assigned to the target remote UE (i.e., the local ID value assigned to itself by the other party from the perspective of the source remote UE and the target remote UE).

[0209] In step S1503 and step S1503 - 1 , the source remote UE may indirectly send a message for the SL connection with the target remote UE through the relay UE.

[0210] In a typical SL connection operation (1 hop), SL-SRB0 is used to send PC5-S messages for unicast (e.g., DCR), and SL-SRB1 is used for PC5-S security configuration. SL-SRB2 is used to send PC5-S messages (e.g., DCA) after PC5-S security configuration, and SL-SRB3 is used for PC5-RRC transmission.

[0211] After the source remote UE and the target remote UE each establish a SL connection with the relay UE, and then control signals are sent between the source remote UE and the target remote UE through typical SL-SRB0, SL-SRB 1, SL-SRB 2 and / or SL-SRB 3, there may be confusion for the remote UE and the relay UE that receive and send these signals due to the previously established connection. Therefore, for the signal sent by the source remote UE to the target BS to establish a connection with the target BS, a separate bearer may need to be configured to forward the signal to the target BS through the adaptation layer of the relay UE.

[0212] For example, SL-RLC0, SL-RLC1, SL-RLC2, and SL-RLC3 bearers may be configured separately. The SL-RLC0 bearer may correspond to a single-hop SL-SRB0, SL-SRB1, SL-SRB2, and SL-SRB3, and may be used during SL configuration between a source UE and a target UE. The corresponding bearers pass through the adaptation layer of the relay UE.

[0213] If the source remote UE is assigned a local ID (which is a local ID for the target remote UE), when the source remote UE sends a message to the target remote UE through the relay, the source remote UE may include the local ID for the target remote UE. Fig.16In the case shown, the adaptation layer of the relay UE may use the local ID to determine to which target remote UE the message should be forwarded.

[0214] On the other hand, when the target remote UE sends a message to the source remote UE through the relay, the target remote UE may include a local ID for the source remote UE. The adaptation layer of the relay UE may use the local ID to determine to which source remote UE the message should be forwarded.

[0215] When the source remote UE sends a message to the target remote UE via the relay, the source remote UE may include the assigned local ID (the local ID of the source remote UE) in the header of the adaptation layer. The relay UE may then forward this value to the target remote UE. This is because the target remote UE does not know the physical L2 ID of the source remote UE and needs to determine which source remote UE to receive data from. However, this can potentially be determined by a higher layer.

[0216] With regard to the above-mentioned explanation, the relay UE may include: at least one processor; and at least one computer memory, which may be operatively connected to the at least one processor and configured to store instructions, which, when executed, cause the at least one processor to perform operations. The operations may include: receiving a first SL RRC message from a source remote UE; establishing a SL connection with the source remote UE; after establishing a SL connection with the source remote UE, sending a second SL RRC message to a target remote UE; establishing a SL connection with the target remote UE; and after establishing a SL connection with the target remote UE, forwarding to the target remote UE a message for the SL connection sent by the source remote UE.

[0217] In addition, a non-volatile computer-readable storage medium is provided, which is configured to store at least one computer program including instructions, and the instructions, when executed by at least one processor, cause the at least one processor to perform operations for a remote UE. The operations may include: receiving a first SL RRC message from a source remote UE; establishing a SL connection with the source remote UE; after establishing the SL connection with the source remote UE, sending a second SL RRC message to a target remote UE; establishing a SL connection with the target remote UE; and after establishing the SL connection with the target remote UE, forwarding to the target remote UE a message for the SL connection sent by the source remote UE.

[0218] When the source remote UE and the relay UE establish a SL connection, and when the source remote UE sends a message to the relay UE for the SL connection with the target remote UE, the SL connection between the relay UE and the target remote UE is triggered. Fig.17A method is described in which a relay UE forwards a message received from a source remote UE for a SL connection with a target remote UE to complete the SL connection between the source remote UE and the target remote UE.

[0219] In step S1701 and step S1701-1, the source remote UE and the relay UE establish a SL connection. Details of the SL connection and / or local ID assignment can be found in Fig.15 Although the relay UE has not established a SL connection with the target remote UE, if the relay UE knows which target remote UE the source remote UE intends to establish a SL connection with, the relay UE can pre-assign a local ID.

[0220] In step S1702, once the source remote UE completes the SL connection with the selected relay UE, the source remote UE sends an RRCReconfigurationSidelink message to the relay UE to establish a SL connection with the target remote UE. The DST L2 ID of the MAC / PHY layer of the message needs to be the relay UE. However, the L2 ID of the target remote UE can be included in the header of the adaptation layer. This allows the relay UE to determine the final destination of the message.

[0221] Additionally / alternatively, the RRCReconfigurationSidelink message that needs to be sent to the target remote UE may be sent via a newly defined bearer, such as Fig.15 In addition, when the relay UE receives an RRCReconfigurationSidelink message including the ID of the target remote UE from the source remote UE or an RRCReconfigurationSidelink message sent through a newly defined bearer for UE-to-UE relay operation, a SL connection with the target remote UE may be triggered.

[0222] The source remote UE may include the assigned local ID for the target remote UE in the header of the adaptation layer of the signal for establishing the RRC connection. In other words, the header of the adaptation layer of the RRCReconfigurationSidelink message sent to establish the SL connection with the target remote UE may include the local ID.

[0223] In step S1703 and step S1703-1, when the SL connection between the relay UE and the target remote UE is triggered, the relay UE establishes a SL connection with the target remote UE. Once the SL connection between the relay UE and the target remote UE is completed, the relay UE forwards the RRCReconfigurationSidelink message received from the source remote UE and stored by the relay UE to the target remote UE. In this case, the local ID for the target remote UE used by the source remote UE when sending the RRCReconfigurationSidelink message can be removed before forwarding. Conversely, the local ID of the source remote UE can be included when forwarding the message. The target remote UE can use the local ID to identify the source remote UE. After receiving the local ID, the target remote UE sends an RRCReconfigurationCompleteSidelink message to the source remote UE via the relay UE.

[0224] Will refer to Fig.18 A method for applying a local ID is described. The relay UE may configure a local ID (local ID M or local ID N) for a target remote UE to the source remote UE. The relay UE may also configure a local ID (local ID A) for the source remote UE to the target remote UE.

[0225] When the source remote UE sends data to the target remote UE1 through the relay UE, the source remote UE may include the local ID (M) of the target remote UE in the data (eg, adaptation layer) sent to the relay UE.

[0226] The relay UE removes the local ID (M) of the target remote UE1 included by the source remote UE, and includes the local ID (A) of the source remote UE before transmitting data to the target remote UE1 (local ID exchange).

[0227] When the target remote UE receives the message, the target remote UE may determine from which source remote UE the data is transmitted based on the local ID (A) of the source remote UE exchanged by the relay UE.

[0228] The same principle can be applied when the target remote UE sends data to the source remote UE.

[0229] Examples of communication systems suitable for the present disclosure

[0230] The various descriptions, functions, processes, proposals, methods and / or operational flowcharts of the present disclosure described in this document may be applied to, without limitation, various fields requiring wireless communication / connection between devices (e.g., 5G).

[0231] Hereinafter, a description will be given in more detail with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise described, the same reference numerals may represent the same or corresponding hardware blocks, software blocks or functional blocks.

[0232] Fig.19 A communication system 1 applied to the present disclosure is illustrated.

[0233] Reference Fig.19 , the communication system 1 applied to the present disclosure includes a wireless device, a BS, and a network. Herein, a wireless device refers to a device that performs communication using a RAT (e.g., 5G NR or LTE), and may be referred to as a communication / radio / 5G device. The wireless device may include, but is not limited to, a robot 100a, a vehicle 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing inter-vehicle communication. Herein, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) installed in a vehicle, a television, a smart phone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, and the like. Handheld devices may include smart phones, smart boards, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebooks). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, a BS and a network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS / network node relative to other wireless devices.

[0234] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI ​​server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without passing through the BS / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., V2V / V2X communication). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.

[0235] Wireless communication / connection 150a, 150b or 150c can be established between wireless devices 100a to 100f / BS200 or BS200 / BS200. Herein, wireless communication / connection can be established through various RATs (e.g., 5G NR) such as UL / DL communication 150a, side link communication 150b (or D2D communication) or inter-BS communication (e.g., relay, integrated access backhaul (IAB)). The wireless device and the BS / wireless device can send / receive radio signals to each other through wireless communication / connection 150a and 150b. For example, wireless communication / connection 150a and 150b can send / receive signals through various physical channels. To this end, various configuration information configuration processes for sending / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping) and at least a part of the resource allocation process can be performed based on various proposals of the present disclosure.

[0236] Examples of wireless devices suitable for the present disclosure

[0237] Fig. 20 A wireless device suitable for use with the present disclosure is illustrated.

[0238] Reference Fig. 20 , the first wireless device 100 and the second wireless device 200 may transmit radio signals through various RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} may correspond to Fig.19 {wireless device 100x and BS200} and / or {wireless device 100x and wireless device 100x} in.

[0239] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then transmit a radio signal including the first information / signals through the transceiver 106. The processor 102 may receive a radio signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104. The memory 104 may be connected to the processor 102, and may store various information related to the operation of the processor 102. For example, the memory 104 may store software codes including commands for executing part or all of the processing controlled by the processor 102 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. Herein, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals through one or more antennas 108. Each of the transceivers 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with (one or more) radio frequency (RF) units. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0240] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then transmit a radio signal including the third information / signals through the transceiver 206. The processor 202 may receive a radio signal including fourth information / signals through the transceiver 106, and then store information obtained by processing the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202, and may store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including commands for executing part or all of the processing controlled by the processor 202 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. Herein, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals through one or more antennas 208. Each of the transceivers 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0241] Hereinafter, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by one or more processors 102 and 202 without limitation. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operational flow diagrams disclosed herein. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flows disclosed herein. One or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flow diagrams disclosed herein, and provide the generated signal to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206 and obtain the PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flow diagrams disclosed herein.

[0242] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. Firmware or software may be used to implement the description, function, process, proposal, method, and / or operational flow chart disclosed herein, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to perform the description, function, process, proposal, method, and / or operational flow chart disclosed herein may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 so as to be driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods and / or operational flows disclosed herein may be implemented using firmware or software in the form of codes, commands and / or command sets.

[0243] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions and / or commands. One or more memories 104 and 204 may be composed of read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard drive, register, cache memory, computer-readable storage medium and / or a combination thereof. One or more memories 104 and 204 may be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 by respective technologies such as wired or wireless connections.

[0244] One or more transceivers 106 and 206 can send the user data, control information and / or radio signal / channel mentioned in the method and / or operation flow chart of this article to one or more other devices. One or more transceivers 106 and 206 can receive the user data, control information and / or radio signal / channel mentioned in the description, function, process, proposal, method and / or operation flow chart disclosed in this article from one or more other devices. For example, one or more transceivers 106 and 206 can be connected to one or more processors 102 and 202, and send and receive radio signals. For example, one or more processors 102 and 202 can perform control so that one or more transceivers 106 and 206 can send user data, control information or radio signal to one or more other devices. One or more processors 102 and 202 can perform control so that one or more transceivers 106 and 206 can receive user data, control information or radio signal from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to send and receive user data, control information, and / or radio signals / channels mentioned in the description, functions, processes, proposals, methods, and / or operation flow charts disclosed herein through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert received radio signals / channels, etc. from RF band signals into baseband signals so as to process received user data, control information, radio signals / channels, etc. using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc. processed using one or more processors 102 and 202 from baseband signals into RF band signals. To this end, one or more of the transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0245] Examples of vehicles or autonomous vehicles suitable for the present disclosure

[0246] Fig.21 The vehicle or autonomous driving vehicle applied to the present disclosure is illustrated. The vehicle or autonomous driving vehicle can be realized by a mobile robot, a car, a train, a manned / unmanned aerial vehicle (AV), a ship, etc.

[0247] Reference Fig.21The vehicle or autonomous driving vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a driving unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 may be configured as a part of the communication unit 110.

[0248] The communication unit 110 may send signals (e.g., data and control signals) to and receive signals from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or autonomous driving vehicle 100. The control unit 120 may include an ECU. The drive unit 140a may enable the vehicle or autonomous driving vehicle 100 to travel on a road. The drive unit 140a may include an engine, a motor, a powertrain, wheels, brakes, a steering device, and the like. The power supply unit 140b may supply power to the vehicle or autonomous driving vehicle 100 and include a wired / wireless charging circuit, a battery, and the like. The sensor unit 140c may acquire vehicle status, surrounding environment information, user information, and the like. The sensor unit 140c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward / reverse sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement a technology for maintaining a lane on which the vehicle is driving, a technology for automatically adjusting a speed such as an adaptive cruise control, a technology for autonomous driving along a determined path, a technology for driving by automatically setting a path when a destination is set, and the like.

[0249] For example, the communication unit 110 may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d may generate an autonomous driving path and a driving plan from the obtained data. The control unit 120 may control the drive unit 140a so that the vehicle or the autonomous driving vehicle 100 may move along the autonomous driving path according to the driving plan (e.g., speed / direction control). In autonomous driving, the communication unit 110 may obtain the latest traffic information data from the external server irregularly / regularly, and may obtain surrounding traffic information data from neighboring vehicles. In autonomous driving, the sensor unit 140c may obtain vehicle status and / or surrounding environment information. The autonomous driving unit 140d may update the autonomous driving path and driving plan based on the newly obtained data / information. The communication unit 110 may transmit information about the vehicle position, autonomous driving path, and / or driving plan to an external server. The external server may predict traffic information data based on information collected from the vehicle or autonomous driving vehicle, using AI technology, etc., and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0250] Examples of Vehicles and AR / VR Applicable to the Disclosure

[0251] Fig. 22 The vehicle applied to the present disclosure is exemplified. The vehicle can be implemented as a transportation tool, an aircraft, a ship, etc.

[0252] Reference Fig. 22 , the vehicle 100 may include a communication unit 110, a control unit 120, a storage unit 130, an I / O unit 140a, and a positioning unit 140b.

[0253] The communication unit 110 may send signals (e.g., data and control signals) to and receive signals from external devices such as other vehicles or BSs. The control unit 120 may perform various operations by controlling the constituent elements of the vehicle 100. The storage unit 130 may store data / parameters / programs / codes / commands for supporting various functions of the vehicle 100. The I / O unit 140a may output AR / VR objects based on the information in the storage unit 130. The I / O unit 140a may include a HUD. The positioning unit 140b may obtain information about the location of the vehicle 100. The location information may include information about the absolute position of the vehicle 100, information about the position of the vehicle 100 in the driving lane, acceleration information, and information about the position of the vehicle 100 relative to neighboring vehicles. The positioning unit 140b may include a GPS and various sensors.

[0254] As an example, the communication unit 110 of the vehicle 100 may receive map information and traffic information from an external server, and store the received information in the storage unit 130. The positioning unit 140b may obtain vehicle location information through GPS and various sensors, and store the obtained information in the storage unit 130. The control unit 120 may generate a virtual object based on the map information, traffic information, and vehicle location information, and the I / O unit 140a may display the generated virtual object in a window (1410 and 1420) in the vehicle. The control unit 120 may determine whether the vehicle 100 is driving normally in the driving lane based on the vehicle location information. If the vehicle 100 leaves the driving lane abnormally, the control unit 120 may display a warning on a window in the vehicle through the I / O unit 140a. In addition, the control unit 120 may broadcast a warning message about driving abnormality to neighboring vehicles through the communication unit 110. Depending on the situation, the control unit 120 may send the vehicle location information and information about driving / vehicle abnormality to a relevant organization.

[0255] Examples of XR Devices Suitable for the Present Disclosure

[0256] Fig.23 The XR device applied to the present disclosure is illustrated. The XR device can be implemented by HMD, HUD installed in a vehicle, TV, smart phone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc.

[0257] Reference Fig.23 , the XR device 100a may include a communication unit 110, a control unit 120, a storage unit 130, an I / O unit 140a, a sensor unit 140b, and a power supply unit 140c.

[0258] The communication unit 110 may send signals (e.g., media data and control signals) to and receive signals from external devices such as other wireless devices, handheld devices, or media servers. The media data may include video, images, and sounds. The control unit 120 may perform various operations by controlling the constituent elements of the XR device 100a. For example, the control unit 120 may be configured to control and / or perform processes such as video / image acquisition, (video / image) encoding, and metadata generation and processing. The storage unit 130 may store data / parameters / programs / codes / commands required to drive the XR device 100a / generate an XR object. The I / O unit 140a may obtain control information and data from the outside and output the generated XR object. The I / O unit 140a may include a camera, a microphone, a user input unit, a display unit, a speaker, and / or a tactile module. The sensor unit 140b may obtain the XR device status, surrounding environment information, user information, and the like. The sensor unit 140b may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone, and / or a radar. The power supply unit 140c may supply power to the XR device 100a and include a wired / wireless charging circuit, a battery, and the like.

[0259] For example, the storage unit 130 of the XR device 100a may include information (e.g., data) required to generate an XR object (e.g., an AR / VR / MR object). The I / O unit 140a may receive a command for manipulating the XR device 100a from a user, and the control unit 120 may drive the XR device 100a according to the user's drive command. For example, when a user desires to watch a movie or news through the XR device 100a, the control unit 120 sends content request information to another device (e.g., a handheld device 100b) or a media server through the communication unit 110. The communication unit 110 may download / stream content such as a movie or news from another device (e.g., a handheld device 100b) or a media server to the storage unit 130. The control unit 120 may control and / or perform processes such as video / image acquisition, (video / image) encoding, and metadata generation / processing for content, and generate / output an XR object based on information about the surrounding space or real objects obtained through the I / O unit 140a / sensor unit 140b.

[0260] The XR device 100a may be wirelessly connected to the handheld device 100b through the communication unit 110, and the operation of the XR device 100a may be controlled by the handheld device 100b. For example, the handheld device 100b may operate as a controller of the XR device 100a. To this end, the XR device 100a may obtain information about the 3D position of the handheld device 100b, generate and output an XR object corresponding to the handheld device 100b.

[0261] Examples of robots suitable for the present disclosure

[0262] Fig.24 The robot applied to the present disclosure is exemplified. According to the purpose or field of use, the robot can be divided into industrial robots, medical robots, household robots, military robots, etc.

[0263] Reference Fig.24 , the robot 100 may include a communication unit 110, a control unit 120, a storage unit 130, an I / O unit 140a, a sensor unit 140b, and a driving unit 140c.

[0264] The communication unit 110 may send signals (e.g., drive information and control signals) to and receive signals from external devices such as other wireless devices, other robots, or control servers. The control unit 120 may perform various operations by controlling the constituent elements of the robot 100. The storage unit 130 may store data / parameters / programs / codes / commands for supporting various functions of the robot 100. The I / O unit 140a may obtain information from the outside of the robot 100 and output the information to the outside of the robot 100. The I / O unit 140a may include a camera, a microphone, a user input unit, a display unit, a speaker, and / or a tactile module. The sensor unit 140b may obtain internal information, surrounding environment information, user information, etc. of the robot 100. The sensor unit 140b may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyroscope sensor, an inertial sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone, a radar, etc. The drive unit 140c may perform various physical operations such as moving a robot joint. In addition, the driving unit 140c may enable the robot 100 to travel or fly on a road. The driving unit 140c may include an actuator, a motor, wheels, brakes, propellers, and the like.

[0265] Examples of AI devices to which the present disclosure is applied

[0266] Fig.25The AI ​​device applied to the present disclosure is illustrated. The AI ​​device can be implemented by a fixed device or a mobile device such as a TV, a projector, a smart phone, a PC, a notebook, a digital broadcast terminal, a tablet PC, a wearable device, a set-top box (STB), a radio, a washing machine, a refrigerator, a digital signage, a robot, a vehicle, etc.

[0267] Reference Fig.25 , the AI ​​device 100 may include a communication unit 110, a control unit 120, a storage unit 130, an I / O unit 140a / 140b, a learning processor unit 140c, and a sensor unit 140d.

[0268] The communication unit 110 can use wired / wireless communication technology to / from other AI devices (e.g., Fig.19 100x, 200, or 400) or AI servers (e.g. Fig.19 400) sends / receives wired / radio signals (e.g., sensor information, user input, learning model, or control signal). To this end, the communication unit 110 can send information in the storage unit 130 to an external device, and send a signal received from an external device to the storage unit 130.

[0269] The control unit 120 may determine at least one feasible operation of the AI ​​device 100 based on information determined or generated using a data analysis algorithm or a machine learning algorithm. The control unit 120 may perform an operation determined by controlling the constituent elements of the AI ​​device 100. For example, the control unit 120 may request, search, receive, or use data of the learning processor unit 140c or the storage unit 130, and control the constituent elements of the AI ​​device 100 to perform a predicted operation or an operation determined to be preferred among at least one feasible operation. The control unit 120 may collect historical information including the operation content of the AI ​​device 100 and the user's operation feedback, and store the collected information in the storage unit 130 or the learning processor unit 140c, or send the collected information to a server such as an AI server ( Fig.19 The collected historical information can be used to update the learning model.

[0270] The storage unit 130 may store data for supporting various functions of the AI ​​device 100. For example, the storage unit 130 may store data obtained from the input unit 140a, data obtained from the communication unit 110, output data of the learning processor unit 140c, and data obtained from the sensor unit 140. The storage unit 130 may store control information and / or software codes required to operate / drive the control unit 120.

[0271] The input unit 140a may acquire various types of data from outside the AI ​​device 100. For example, the input unit 140a may acquire learning data for model learning and input data to which the learning model will be applied. The input unit 140a may include a camera, a microphone, and / or a user input unit. The output unit 140b may generate an output related to visual, auditory, or tactile sensations. The output unit 140b may include a display unit, a speaker, and / or a tactile module. The sensor unit 140 may use various sensors to obtain at least one of the internal information of the AI ​​device 100, the surrounding environment information of the AI ​​device 100, and the user information. The sensor unit 140 may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a light sensor, a microphone, and / or a radar.

[0272] The learning processor unit 140c can use the learning data to learn a model including an artificial neural network. The learning processor unit 140c can communicate with the AI ​​server ( Fig.19 The learning processor unit 140c may perform AI processing together with the learning processor unit 400 of FIG. 400. The learning processor unit 140c may process information received from an external device through the communication unit 110 and / or information stored in the storage unit 130. In addition, the output value of the learning processor unit 140c may be sent to an external device through the communication unit 110 and may be stored in the storage unit 130.

[0273] Industrial Applicability

[0274] The above-mentioned embodiments of the present disclosure are applicable to various mobile communication systems.

Claims

1. A method for operating a relay UE associated with establishing a connection from a user equipment UE to a UE relay in a wireless communication system, the method comprising the following steps: receiving, by the relay UE, a first sidelink radio resource control (SL) RRC message from a source remote UE; The relay UE establishes a side link SL connection with the source remote UE; After establishing the SL connection with the source remote UE, the relay UE sends a second SL RRC message to the target remote UE; The relay UE establishes a SL connection with the target remote UE; and After establishing the SL connection with the target remote UE, the relay UE forwards the message for the SL connection sent by the source remote UE to the target remote UE.

2. The method according to claim 1, wherein: The first SL RRC message includes identifier ID information about the target remote UE.

3. The method according to claim 1, wherein: The second SL RRC message includes identifier ID information about the source remote UE.

4. The method according to claim 2, wherein: The target remote UE is one of multiple UEs that establish a SL connection with the source remote UE.

5. The method according to claim 2, wherein: The ID information about the target remote UE is a layer 2 L2 ID of the target remote UE.

6. The method according to claim 1, wherein: The first SL RRC message is an RRCReconfigurationSidelink message.

7. The method according to claim 3, wherein: The ID information about the source remote UE is a layer 2 L2 ID of the source remote UE.

8. The method according to claim 3, wherein: The second SL RRC message is an RRCReconfigurationSidelink message.

9. The method according to claim 8, wherein: The second SL RRC message includes information indicating a SL connection for a UE-to-UE relay operation.

10. A relay user equipment UE in a wireless communication system, the relay UE comprising: at least one processor; as well as At least one computer memory operatively connectable to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations comprising: receiving a first sidelink radio resource control (SL) RRC message from a source remote UE; Establishing a side link SL connection with the source remote UE; After establishing the SL connection with the source remote UE, sending a second SL RRC message to the target remote UE; Establishing a SL connection with the target remote UE; and After establishing the SL connection with the target remote UE, forwarding the message for the SL connection sent by the source remote UE to the target remote UE.

11. The relay UE according to claim 10, wherein: The relay UE communicates with at least one of another UE, a UE associated with an autonomous vehicle, a base station, or a network.

12. A non-volatile computer-readable storage medium, the non-volatile computer-readable storage medium being configured to store at least one computer program comprising instructions, the instructions, when executed by at least one processor, causing the at least one processor to perform operations for a relay user equipment UE, the operations comprising: receiving a first sidelink radio resource control (SL) RRC message from a source remote UE; Establishing a side link SL connection with the source remote UE; After establishing the SL connection with the source remote UE, sending a second SL RRC message to the target remote UE; Establishing a SL connection with the target remote UE; and After establishing the SL connection with the target remote UE, forwarding the message for the SL connection sent by the source remote UE to the target remote UE.

Images