Apparatus and method for supporting vehicle-to-everything communication in a wireless communication system

Abstract

The present disclosure relates to a fifth-generation (5G) or pre-5G communication system that supports data transmission rates higher than those of a fourth-generation (4G) communication system, such as Long-Term Evolution (LTE). The present disclosure provides an apparatus and method for supporting vehicle-to-everything (V2X) communication in a wireless communication system. The method for operating a first terminal in a wireless communication system provided by the present invention includes the following processes: receiving, in a Radio Resource Control (RRC) idle mode or an RRC inactive mode, first system information for vehicle-to-everything (V2X) sidelink communication from a first base station; if the first system information includes sidelink configuration information, establishing a first sidelink radio bearer (SLRB) based on the sidelink configuration information; performing V2X sidelink communication with a second terminal via the first SLRB; transitioning to an RRC connected mode; and performing V2X sidelink communication with the second terminal via the first SLRB until an RRC reconfiguration message is received from the first base station.

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication systems, and more particularly, to apparatuses and methods for supporting vehicle-to-everything (V2X) communication in wireless communication systems. Background Art

[0002] To meet the increasing wireless data traffic demands since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "beyond 4G network" communication systems or "post-long term evolution (post-LTE)" systems.

[0003] To achieve higher data rates, 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 60 GHz band). To reduce the propagation loss of radio waves and increase the transmission distance in the millimeter wave band, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technologies in 5G communication systems have been discussed.

[0004] In addition, in 5G communication systems, developments of system network improvements are being carried out based on advanced small cells, cloud radio access network (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multi-point (CoMP), receiver interference cancellation, etc.

[0005] In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superimposed coding (SWSC) as advanced coding modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access technologies have been developed.

[0006] In 5G systems, vehicle-to-everything (V2X) technology is being considered. To support V2X operations in a new radio (NR) system separate from V2X operations in a traditional LTE system, detailed processes to meet the new requirements of the NR system are being discussed. Summary of the Invention

[0007] [Technical Problem]

[0008] Based on the above discussion, the present disclosure provides apparatuses and methods for effectively supporting vehicle-to-everything (V2X) communication in wireless communication systems.

[0009] [Technical Solution]

[0010] According to an aspect of the present disclosure, a method for operating a first UE in a wireless communication system includes: receiving, in a radio resource control (RRC) idle mode or an RRC inactive mode, first system information for vehicle-to-everything (V2X) sidelink communication from a first BS; when the sidelink configuration information is included in the first system information, establishing a first sidelink bearer (sidelink radio bearer (SLRB)) based on the sidelink configuration information; performing V2X sidelink communication with a second UE via the first SLRB; transitioning to an RRC connected mode; and performing V2X sidelink communication with the second UE via the first SLRB before receiving an RRC reconfiguration message from the first BS.

[0011] According to another aspect of the present disclosure, a first UE in a wireless communication system includes: a transceiver and at least one processor, wherein the at least one processor is configured to: receive, in a radio resource control (RRC) idle mode or an RRC inactive mode, first system information for vehicle-to-everything (V2X) sidelink communication from a first BS; when the sidelink configuration information is included in the first system information, establish a first sidelink bearer (sidelink radio bearer (SLRB)) based on the sidelink configuration information; perform V2X sidelink communication with a second UE via the first SLRB; transition to an RRC connected mode; and perform V2X sidelink communication with the second UE via the first SLRB before receiving an RRC reconfiguration message from the first BS.

[0012] [Advantages of the Invention]

[0013] The apparatus and method according to various embodiments of the present disclosure can effectively support vehicle-to-everything (V2X) communication in a wireless communication system.

[0014] The advantages obtainable from the present disclosure may not be limited to the above effects, and other effects not mentioned can be clearly understood by those of ordinary skill in the art to which the present disclosure pertains through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 An example of a wireless communication system according to various embodiments of the present disclosure is shown.

[0016] Figure 2 An example of a wireless protocol structure of a wireless communication system according to various embodiments of the present disclosure is shown.

[0017] Figure 3 An example of a structure of a wireless communication system according to various embodiments of the present disclosure is shown.

[0018] Figure 4 An example of a wireless protocol structure of a wireless communication system according to various embodiments of the present disclosure is shown.

[0019] Figure 5 Shows an example of vehicle-to-everything (V2X) communication in a wireless communication system according to various embodiments of the present disclosure.

[0020] Figure 6 Shows an example of the following processes in a wireless communication system according to various embodiments of the present disclosure: the process of a UE switching from a radio resource control (RRC) connected mode (RRC_CONNECTED) with a long-term evolution (LTE) base station (next-generation evolved node B (ng-eNB)) connected to a 5G core network (5GC) to an RRC inactive mode (RRC_INACTIVE); and the process of a UE in the RRC inactive mode performing new radio (NR) V2X sidelink communication.

[0021] Figure 7 Shows an example of the following processes in a wireless communication system according to various embodiments of the present disclosure: the process of a UE switching from an RRC connected mode (RRC_CONNECTED) with an LTE eNB (ng-eNB) connected to a 5GC to an RRC idle mode (RRC_IDLE); and the process of a UE in the RRC idle mode performing NR V2X sidelink communication.

[0022] Figure 8 Shows an example of the following processes in a wireless communication system according to various embodiments of the present disclosure: the process of a UE switching from an RRC connected mode (RRC_CONNECTED) with a next-generation node B (gNB) of NR connected to a 5GC to an RRC inactive mode (RRC_INACTIVE); and the process of a UE in the RRC inactive mode performing LTE V2X sidelink communication.

[0023] Figure 9 Shows an example of the following processes in a wireless communication system according to various embodiments of the present disclosure: an example of the process of a UE switching from an RRC connected mode (RRC_CONNECTED) with an NR gNB connected to a 5GC to an RRC idle mode (RRC_IDLE); and the process of a UE in the RRC idle mode performing LTE V2X sidelink communication.

[0024] Figure 10 Shows an example of the following processes in a wireless communication system according to various embodiments of the present disclosure: the process of a UE switching from an RRC connected mode (RRC_CONNECTED) with an LTE eNB (ng-eNB) connected to a 5GC to an RRC inactive mode (RRC_INACTIVE); and the process of a UE in the RRC inactive mode performing NR V2X sidelink communication.

[0025] Figure 11 Shows an example of the following processes in a wireless communication system according to various embodiments of the present disclosure: the process of a UE switching from the RRC connected mode (RRC_CONNECTED) with an LTE eNB (ng-eNB) connected to the 5GC to the RRC idle mode (RRC_IDLE); and the process of a UE in the RRC idle mode performing NR V2X sidelink communication.

[0026] Figure 12 Shows an example of the following processes in a wireless communication system according to various embodiments of the present disclosure: the process of a UE switching from the RRC connected mode (RRC_CONNECTED) with an NR gNB connected to the 5GC to the RRC inactive mode (RRC_IDLE); and the process of a UE in the RRC inactive mode performing LTE V2X sidelink communication.

[0027] Figure 13 Shows an example of the following processes in a wireless communication system according to various embodiments of the present disclosure: the process of a UE switching from the RRC connected mode (RRC_CONNECTED) with an NR gNB connected to the 5GC to the RRC idle mode (RRC_IDLE), and the process of a UE in the RRC idle mode performing LTE V2X sidelink communication.

[0028] Figure 14 Shows an example of the following processes in a wireless communication system according to various embodiments of the present disclosure: the process of managing an established sidelink radio bearer (SLRB) when a UE supporting NR V2X sidelink communication establishes an sidelink bearer (SLRB) in the RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE) and switches to the RRC connected mode (RRC_CONNECTED) with an LTE eNB during NR V2X sidelink communication.

[0029] Figure 15 Shows an example of the following processes in a wireless communication system according to various embodiments of the present disclosure: the process of managing an established sidelink radio bearer (SLRB) when a UE supporting NR V2X sidelink communication establishes an sidelink bearer (SLRB) in the RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE) and switches to the RRC connected mode (RRC_CONNECTED) with an NR gNB during NR V2X sidelink communication.

[0030] Figure 16Shows an example of the following process in a wireless communication system according to various embodiments of the present disclosure: When a UE supporting NR V2X sidelink communication establishes a sidelink bearer (sidelink radio bearer (SLRB)) in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE) and switches to RRC connected mode (RRC_CONNECTED) with an LTE eNB during NR V2X sidelink communication, the process of managing the established SLRB.

[0031] Figure 17 Shows an example of the following process in a wireless communication system according to various embodiments of the present disclosure: When a UE supporting NR V2X sidelink communication establishes a sidelink bearer (sidelink radio bearer (SLRB)) in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE) and switches to RRC connected mode (RRC_CONNECTED) with an NR eNB during NR V2X sidelink communication, the process of managing the established SLRB.

[0032] Figure 18 Shows an example of the structure of a UE in a wireless communication system according to various embodiments of the present disclosure.

[0033] Figure 19 Shows an example of the structure of a BS in a wireless communication system according to various embodiments of the present disclosure. Detailed embodiments

[0034] The terms used in the present disclosure are only for describing specific embodiments and are not intended to limit the present disclosure. Unless otherwise defined in the context, singular expressions may include plural expressions. Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by those skilled in the art to which the present disclosure pertains. These terms defined in a commonly used dictionary may be interpreted as having the same meaning as the context in the relevant field, and will not be interpreted as having an ideal or overly formal meaning unless clearly defined in the present disclosure. In some cases, even terms defined in the present disclosure should not be construed as excluding embodiments of the present disclosure.

[0035] Hereinafter, various embodiments of the present disclosure will be described based on a hardware approach. However, various embodiments of the present disclosure include technologies using both hardware and software, and thus various embodiments of the present disclosure do not exclude the software perspective.

[0036] The present disclosure describes a technology for effectively supporting vehicle-to-everything (V2X) in a wireless communication system.

[0037] As used in the specification, for convenience, terms related to signals, terms related to channels, terms related to control information, terms related to network entities, terms related to device components, etc. are used illustratively. Therefore, the present disclosure is not limited to the terms used hereinafter, and other terms having equivalent technical meanings related to the subject matter may be used.

[0038] In addition, various embodiments of the present disclosure will be described using terms used in some communication standards (e.g., the 3rd Generation Partnership Project (3GPP)), but this is for illustrative purposes only. Various embodiments of the present disclosure can also be easily modified and applied to other communication systems.

[0039] Figure 1 An example of a wireless communication system according to various embodiments of the present disclosure is shown.

[0040] Specifically, Figure 1 The structure of a Long Term Evolution (LTE) system according to an embodiment of the present disclosure is shown.

[0041] Referring to Figure 1 , the radio access network of the LTE system includes next-generation base stations (evolved Node B, eNB, Node B, or base station) 105, 110, 115, and 120, a mobility management entity (MME) 125, and a serving gateway (S-GW) 130. The user equipment 135 (UE or terminal) accesses an external network through the eNBs 105, 110, 115, and 120 and the S-GW 130.

[0042] In Figure 1 , the eNBs 105, 110, 115, and 120 may correspond to conventional Node Bs of a Universal Mobile Telecommunications System (UMTS). The eNB may be connected to the UE 135 through a radio channel and may play a more complex role than a conventional Node B. In the LTE system, all user services including real-time services such as Internet Protocol-based voice or Voice over IP (VoIP) can be provided through a shared channel. Therefore, a device for collecting and scheduling status information (such as the buffer status, available transmission power status, and channel status of the UE) that needs to be served by the eNBs 105, 110, 115, and 120 is required.

[0043] An eNB can generally control multiple cells. For example, to achieve a transmission rate of 100 Mbps, the LTE system uses Orthogonal Frequency Division Multiplexing (OFDM) as a radio access technology in a 20 MHz bandwidth, for instance. Additionally, an Adaptive Modulation and Coding (AMC) scheme that determines the modulation scheme and channel coding rate based on the UE's channel state can be applied. The S-GW 130 is a device for providing data bearers and can generate or remove data bearers under the control of the MME 125. The MME is a device for performing the UE's mobility management functions and various control functions and can be connected to multiple eNBs.

[0044] Figure 2 An example of the radio protocol structure of a wireless communication system according to various embodiments of the present disclosure is shown.

[0045] Specifically, Figure 2 The radio protocol structure in an LTE system according to an embodiment of the present disclosure is shown.

[0046] Referring to Figure 2 , the radio protocol of the LTE system may include Packet Data Convergence Protocol (PDCP) 205 and 240, Radio Link Control (RLC) 210 and 235, and Medium Access Control (MAC) 215 and 230 in the UE and the eNB, respectively.

[0047] The PDCP 205 and 240 can perform operations of Internet Protocol (IP) header compression / reconstruction. The main functions of the PDCP 205 and 240 can be described as follows.

[0048] - Header compression and decompression function: (Header compression and decompression: only Robust Header Compression (ROHC))

[0049] - User data transmission function (transmission of user data)

[0050] - Sequential transmission function (sequentially transmit higher layer PDUs during the PDCP reconstruction process for RLC AM)

[0051] - Reordering function (for split bearers in dual connectivity (only RLC AM supported): routing of PDCP PDUs for transmission and reordering of PDCP PDUs for reception)

[0052] - Duplicate detection function (during the PDCP reconstruction process for RLC AM, perform duplicate detection on lower layer Service Data Units (SDUs))

[0053] - Retransmission function (for split bearers in DC, retransmit PDCP SDUs during handover; and for RLC AM, retransmit PDCP PDUs during the PDCP data recovery process)

[0054] - Encryption and decryption functions (Encryption and decryption)

[0055] - Timer-based SDU deletion function (Timer-based SDU discard in the uplink)

[0056] Radio Link Control (RLC) 210 and 235 can perform Automatic Repeat reQuest (ARQ) operations by configuring the Packet Data Unit (PDU) of the Packet Data Convergence Protocol (PDCP) to an appropriate size. The main functions of RLC 210 and 235 can be described as follows.

[0057] - Data transmission function (Transmission of high-layer PDUs)

[0058] - ARQ function (Error correction via ARQ (only for AM data transmission))

[0059] - Concatenation, segmentation, and reassembly functions (Concatenation, segmentation, and reassembly of RLC SDUs (only for UM and AM data transmission))

[0060] - Resegmentation function (Resegmentation of RLC data PDUs (only for AM data transmission))

[0061] - Reordering function (Reordering of RLC data PDUs (only for (Unacknowledged Mode) UM and (Acknowledged Mode) AM data transmission))

[0062] - Duplicate detection function (Duplicate detection (only for UM and AM data transmission))

[0063] - Error detection function (Protocol error detection (only for AM data transmission))

[0064] - RLC SDU deletion function (RLC SDU discard (only for UM and AM data transmission))

[0065] - RLC reconstruction function (RLC reconstruction)

[0066] MAC 215 and 230 are connected to each RLC layer device included in a UE, and perform operations of multiplexing the RLC PDU into the MAC PDU and demultiplexing the RLC PDU from the MAC PDU. The main functions of MAC 215 and 230 can be described as follows.

[0067] - Mapping function (Mapping between logical channels and transport channels)

[0068] - Multiplexing and demultiplexing functions (multiplexing MAC SDUs belonging to one or different logical channels into transport blocks (TBs) transmitted to the physical layer via a transport channel, or demultiplexing the MAC SDUs from the TBs transmitted from the physical layer via a transport channel)

[0069] - Scheduling information reporting function (scheduling information reporting)

[0070] - HARQ function (error correction via HARQ)

[0071] - Logical channel priority control function (priority handling among the logical channels of a UE)

[0072] - UE priority control function (handling the priority among UEs by means of dynamic scheduling)

[0073] - Multimedia Broadcast Multicast Service (MBMS) service identification function (MBMS service identification)

[0074] - Transmission format selection function (transmission format selection)

[0075] - Padding function (padding)

[0076] The physical layer (PHY) 220 and 225 perform operations of channel encoding and modulating the high-layer data to generate OFDM symbols and transmitting the OFDM symbols via a radio channel, or demodulating and channel decoding the OFDM symbols received via a radio channel and transmitting the demodulated and channel-decoded OFDM symbols to the high layer.

[0077] Figure 3 Shows an example of the structure of a wireless communication system according to various embodiments of the present disclosure.

[0078] Specifically, Figure 3 Shows the structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

[0079] Reference Figure 3 , the radio access network of a next-generation mobile communication system (New Radio, NR, 5th generation or 5G) may include a next-generation base station (New Radio Node B, NR gNB or NR base station) 310, and a next-generation radio core network (New Radio Core Network or NR CN) 305. The next-generation radio user terminal 315 (New Radio User Equipment, NR UE or NR terminal) may access an external network via the NR gNB 310 or the NR CN 305.

[0080] In Figure 3Among them, the NR gNB 310 may correspond to the evolved Node B (eNB) in a traditional LTE system. The NR gNB can be connected to the NR UE 315 via a wireless channel and can provide better services than traditional Node Bs. In the next-generation mobile communication system, all user services can be provided through shared channels. Therefore, there is a need for a device for collecting and scheduling status information (such as the buffer status, available transmit power status, and channel status of the UE) to be served by the NR gNB 310. One NR gNB 310 can control multiple cells. Compared with the current LTE, in the next-generation mobile communication system, a bandwidth greater than or equal to the current maximum bandwidth can be applied to achieve ultra-high-speed data transmission. Additionally, based on orthogonal frequency division multiplexing (OFDM) as the radio access technology, beamforming technology can also be used. Additionally, an adaptive modulation and coding (AMC) scheme for determining the modulation scheme and channel coding rate corresponding to the channel state of the NR UE can be applied.

[0081] The NR CN 305 can perform functions supporting mobility, configuring bearers, and configured QoS. The NR CN 305 is a device that performs various control functions and the mobility management function of the UE and can be connected to multiple NR gNBs. Additionally, the next-generation mobile communication system can be linked to the traditional LTE system, and the NR CN 305 can be connected to the MME 325 via a network interface. The MME 325 can be connected to the eNB 330, which is a traditional base station.

[0082] Figure 4 An example of the radio protocol structure of a wireless communication system according to various embodiments of the present disclosure is shown.

[0083] Specifically, Figure 4 An example of the radio protocol structure of the next-generation mobile communication system according to an embodiment of the present disclosure is shown.

[0084] Referring to Figure 4 , the radio protocol of the next-generation mobile communication system may include the NR service data adaptation protocol (SDAP) 401 and 445, NR PDCP 405 and 440, NR RLC 410 and 435, NR MAC 415 and 430, and NR PHY 420 and 425 in the UE and the NR gNB.

[0085] The main functions of the NR SDAP 401 and 445 may include some of the following functions.

[0086] - User data transmission function (transmission of user-plane data)

[0087] - Mapping function of QoS flows and data bearers for uplink and downlink (mapping between QoS flows for DL and UL and DRBs)

[0088] - Tagging function for QoS flow IDs in the uplink and downlink (tagging the QoS flow identifier (ID) in downlink (DL) packets and uplink (UL) packets)

[0089] - Mapping function of reflected QoS flows to data bearers for uplink SDAP PDUs (mapping of reflected QoS flows of UL SDAP PDUs to DRBs)

[0090] For the SDAP layer device, the UE can receive configurations via Radio Resource Control (RRC) messages, which indicate whether to use the header of the SDAP layer device or the functions of the SDAP layer device for each PDCP layer device, each bearer, or each logical channel. When the SDAP header is configured, the UE can indicate the update or reconfiguration of the mapping information between uplink and downlink QoS flows and data bearers through a 1-bit non-access stratum (NAS) Quality of Service (QoS) reflection configuration indicator (NAS reflected QoS) and a 1-bit access stratum (AS) QoS reflection configuration indicator (AS reflected QoS) of the SDAP header. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority or scheduling information to support seamless services.

[0091] The main functions of NR PDCP 405 and 440 may include some of the following functions.

[0092] - Header compression and decompression function: (Header compression and decompression: only Robust Header Compression (ROHC))

[0093] - User data transfer function (transfer of user data)

[0094] - Sequential transfer function (sequential transfer of higher layer PDUs)

[0095] - Unordered transfer function (unordered transfer of higher layer PDUs)

[0096] - Reordering function (reordering of received PDCP PDUs)

[0097] - Duplicate detection function (duplicate detection of lower layer SDUs)

[0098] - Retransmission function (retransmission of PDCP SDUs)

[0099] - Encryption and decryption function (encryption and decryption)

[0100] - Timer-based SDU deletion function (timer-based SDU discard in the uplink)

[0101] In the above example, the reordering function of the NR PDCP device is a function of reordering in sequence the PDCP PDUs received from the lower layer based on the PDCP sequence number (SN). The reordering function of the NR PDCP device may include the function of sending the reordered data in sequence to the upper layer, the function of directly sending the recorded data without considering the order, the function of recording the PDCP PDUs lost due to reordering, the function of reporting the status of the lost PDCP PDUs to the sending end, and the function of requesting retransmission of the lost PDCP PDUs.

[0102] The main functions of NR RLC 410 and 435 may include some of the following functions.

[0103] - Data transfer function (transmission of upper layer PDUs)

[0104] - Sequential transfer function (sequential transfer of upper layer PDUs)

[0105] - Unordered transfer function (unordered transfer of upper layer PDUs)

[0106] - ARQ function (error correction by ARQ)

[0107] - Concatenation, segmentation, and reassembly function (concatenation, segmentation, and reassembly of RLC SDUs)

[0108] - Resegmentation function (resegmentation of RLC data PDUs)

[0109] - Reordering function (reordering of RLC data PDUs)

[0110] - Duplicate detection function (duplicate detection)

[0111] - Error detection function (protocol error detection)

[0112] - RLC SDU deletion function (RLC SDU discard)

[0113] - RLC reconstruction function (RLC reconstruction)

[0114] In the above description, the sequential transfer function (sequential transfer) of the NR RLC 410 and 435 devices may be a function of sequentially transferring the RLC SDUs received from the lower layer to the upper layer. When an RLC SDU is divided into multiple RLC SDUs and received, the sequential transfer function (sequential transfer) of the NR RLC 410 and 435 devices may include the function of reassembling and then sending the RLC SDUs.

[0115] The sequential transfer function (in-sequence delivery) of the NR RLC 410 and 435 devices may include the functions of reordering the received RLC PDUs based on the RLC sequence number (SN) or PDCP SN, recording the RLC PDUs lost due to reordering, reporting the status of the lost RLC PDUs to the transmitting end, and requesting retransmission of the lost RLC PDUs.

[0116] The sequential transfer function (in-sequence delivery) of the NR RLC 410 and 435 devices may include the following functions: If there are lost RLC SDUs, only the RLC SDUs before the lost RLC SDUs are delivered to the upper layer in sequence. Additionally, the sequential transfer function (in-sequence delivery) of the NR RLC devices may include the following function: If a pre-determined timer expires, even if there are lost RLC SDUs, all the RLC SDUs received before the expiration of the pre-determined timer are delivered to the upper layer in sequence. Additionally, the sequential transfer function (in-sequence delivery) of the NR RLC 410 and 435 devices may include the following function: If a pre-determined timer expires, even if there are lost RLC SDUs, all the RLC SDUs received up to now are delivered to the upper layer in sequence.

[0117] The NR RLC 410 and 435 devices may process the received RLC PDUs in sequence regardless of the sequence number order (unordered delivery), and deliver the RLC PDUs to the NR PDCP 405 and 440 devices.

[0118] When receiving fragments, the NR RLC 410 and 435 devices may receive the fragments stored in or to be received in the buffer, reconfigure these fragments into a complete RLC PDU, and then deliver the RLC PDU to the NR PDCP device.

[0119] The NR RLC 410 and 435 layers may not include the concatenation function, and this function may be performed by the NR MAC layer, or may be replaced by the multiplexing function of the NR RLC 410 and 435 layers.

[0120] In the above description, the out-of-order transfer function (out-of-order transfer) of the NR RLC 410 and 435 devices may be a function of transferring the RLC SDUs received from the lower layer to the upper layer in sequence regardless of order. When an RLC SDU is divided into multiple RLC SDUs and received, the out-of-order transfer function (out-of-order transfer) of the NR RLC 410 and 435 devices may include the function of reassembling and then sending the RLC SDU. The out-of-order transfer function (out-of-order transfer) of the NR RLC 410 and 435 devices may include the function of storing the RLC SN or PDCP SN of the received RLC PDU, reordering it, and recording the lost RLC PDUs.

[0121] The NR MAC 415 and 430 may be connected to multiple NR RLC 410 and 435 layer devices configured in a UE, and the main functions of the NR MAC 415 and 430 may include some of the following functions.

[0122] - Mapping function (mapping between logical channels and transport channels)

[0123] - Multiplexing / demultiplexing function (multiplexing / demultiplexing of MAC SDUs)

[0124] - Scheduling information reporting function (scheduling information reporting)

[0125] - HARQ function (error correction via HARQ)

[0126] - Logical channel priority control function (priority handling between logical channels of a UE)

[0127] - UE priority control function (handling priorities between UEs via dynamic scheduling)

[0128] - MBMS service identification function (MBMS service identification)

[0129] - Transmission format selection function (transmission format selection)

[0130] - Padding function (padding)

[0131] The NR PHY layer 420 and 425 may perform operations of channel encoding and modulating the upper layer data to generate OFDM symbols and sending the OFDM symbols through a radio channel, or operations of demodulating and channel decoding the OFDM symbols received through the radio channel and sending the demodulated and channel decoded OFDM symbols to the upper layer.

[0132] Figure 5 An example of vehicle-to-everything (V2X) communication in a wireless communication system according to various embodiments of the present disclosure is shown.

[0133] Specifically, Figure 5 V2X communication in a next-generation mobile communication system according to an embodiment of the present disclosure is shown.

[0134] Vehicle-to-everything (V2X) according to an embodiment of the present disclosure inclusively indicates communication technologies through vehicles and all interfaces, and according to its form and the presence of components therein, there are vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), and vehicle-to-network (V2N).

[0135] Referring to Figure 5 , the (ng)-eNB / gNB 501 may include at least one in-vehicle UE 505 and 510 and pedestrian portable UE 515 located within a V2X-enabled cell 502. At this time, V2X may be supported through the Uu interface (UTMS air interface) and / or the PC5 (LTE-V2X or 5G-V2X) interface. According to an embodiment, when V2X is supported through the Uu interface, the in-vehicle UEs 505 and 510 may perform V2X cellular communication with the (ng)-eNB / gNB 501 through the uplink / downlink (UL / DL) 530 and 535 between the in-vehicle UE and the (ng)-eNB / gNB, or the pedestrian UE 515 may perform V2X cellular communication through the uplink / downlink (UL / DL) 540 between the pedestrian UE and the (ng)-eNB / gNB. When V2X is supported through the PC5 interface, V2X sidelink (SL) communication may be performed through the link (sidelink (SL)) 520 and 525 between UEs. According to an embodiment, the in-vehicle UE 505 present within the coverage range of the (ng)-eNB / gNB (within the coverage range of E-UTRA / NR) may transmit V2X packets to other in-vehicle UEs 510 and 545 and / or pedestrian portable UEs 515 and 555 through the sidelink (SL) 520, 550, 525, and 560 serving as a transmission channel, and receive V2X packets from the UEs. The V2X packets may be transmitted and received in a broadcast transmission type and / or a unicast and / or multicast transmission type.

[0136] A UE supporting V2X sidelink communication can send and receive V2X packets through a resource allocation mode (scheduled resource allocation or UE autonomous resource selection). Scheduled resource allocation (mode 1 and / or mode 3) is a mode where the (ng)-eNB / gNB allocates resources for sidelink transmission to an RRC-connected UE using a dedicated scheduling scheme. The (ng)-eNB / gNB can manage sidelink resources in this mode, which can efficiently manage interference and / or manage a resource pool (dynamic allocation or semi-persistent transmission). When an RRC-connected UE has data to send to another UE, the UE can send information indicating that the UE has data to send to another UE to the (ng)-eNB / gNB via an RRC message or a MAC control element (CE). According to an embodiment, the SidelinkUEInformation message or the UEAssistanceInformation message can be used as an RRC message, and a buffered status report MAC CE in a new format (including at least an indicator indicating a buffered status report via V2X communication and information about the size of the data buffered for sidelink communication) can be used as a MAC CE.

[0137] UE autonomous resource selection (mode 2 and / or mode 4) is a mode where the (ng)-eNB / gNB provides sidelink resource information / pool to a UE supporting V2X sidelink communication via system information and / or an RRC message, and the UE selects resources according to a predetermined rule. According to an embodiment, the (ng)-eNB / gNB can signal the SIB21 (SystemInformationBlockType21), SIB26, or a new SIBx to be defined for NR V2X UEs to the UE and provide sidelink resource information. According to an embodiment, as an RRC message, the (ng)-eNB / gNB can signal an RRC connection reconfiguration message (RRCConnectionReconfiguration message) and / or a connection resume message (RRCResume message) to the UE and provide sidelink resource information. Additionally, UE autonomous resource selection can assist the UE in selecting resources for the sidelink via a PC5-RRC message and / or a MAC CE, or allocate resources for sidelink transmission to other UEs through direct / indirect scheduling. That is, the UE autonomous resource selection mode can indicate one or more of the following information.

[0138] - The UE autonomously selects sidelink resources for transmission

[0139] - The UE assists in selecting sidelink resources for other UEs.

[0140] - The UE is configured by an NR-configured grant for sidelink transmission.

[0141] - Sidelink transmission by a UE to schedule other UEs.

[0142] The method for a UE to select resources may include area mapping, sensing-based resource selection, random selection, and configured grant-based resource selection.

[0143] A UE supporting V2X sidelink communication may transmit and receive V2X packets based on a preconfigured resource pool (preconfigured resources) included in SL-V2X-preconfiguration as an information element (IE). According to an embodiment, when for a predetermined reason, even if the UE is within the coverage of an (ng)-eNB / gNB, the UE cannot perform 2X sidelink communication based on scheduled resource allocation and / or UE autonomous resource selection mode, the UE may perform V2X sidelink communication through the sidelink transmission / reception resource pool preconfigured in SL-V2X-preconfiguration as an IE. Additionally, an in-vehicle UE 545 (outside the coverage of E-UTRA / NR) may perform V2X sidelink communication with another in-vehicle UE 565 or a portable UE 555 based on the preconfigured resources of the sidelink (preconfigured resources) through sidelinks (SLs) 570 and 575 as transmission channels.

[0144] The LTE V2X SL communication system is designed for basic safety services. That is, UEs supporting LTE V2X SL communication are designed to provide basic safety services to all neighboring UEs supporting LTE V2X SL communication through a broadcast transmission scheme. Therefore, it is not required for a UE to perform a process of establishing a separate session with another specific UE or an SL connection process (sidelink connection establishment process).

[0145] However, in next-generation mobile communication (NR), the V2X SL communication system may be designed to provide not only basic safety services but also various improved services (e.g., autonomous driving service, platooning service, remote driving service, and in-vehicle infotainment). Therefore, the NR V2X SL communication system may be designed to support unicast and / or multicast transmission types as well as the broadcast transmission type.

[0146] In the following, Figures 6 to 13 Embodiments of obtaining system information for supporting vehicle communication in a next-generation mobile communication system are shown.

[0147] Figure 6An example of a process in a wireless communication system according to various embodiments of the present disclosure is shown: a process in which a UE switches from a radio resource control (RRC) connected mode (RRC_CONNECTED) to an RRC inactive mode (RRC_INACTIVE) with respect to a long-term evolution (LTE) BS (next-generation evolved Node B (ng-eNB)) connected to a 5G core network (5GC); and a process in which a UE in the RRC inactive mode performs new radio (NR) V2X sidelink communication.

[0148] UEs 601 and 602 according to embodiments of the present disclosure may refer to vehicle-mounted UEs or pedestrian UEs. UEs 601 and 602 may support V2X sidelink communication via one or more radio access technologies (RATs). According to an embodiment, UEs 601 and 602 may support only LTE V2X sidelink communication or only NR V2X sidelink communication, or may support both LTE V2X sidelink communication and NR V2X sidelink communication. The LTE eNB 603 according to embodiments of the present disclosure may periodically broadcast system information related to LTE V2X sidelink configuration information and / or system information related to NR V2X sidelink configuration information.

[0149] When the UE 601 according to an embodiment of the present disclosure is configured to simultaneously transmit NR V2X sidelink communication and LTE V2X sidelink communication, if the UE does not obtain NR V2X sidelink communication configuration information and LTE V2X sidelink communication configuration information from a cell simultaneously, the UE may camp on one of a cell that only provides NR V2X sidelink communication configuration information or a cell that only provides LTE V2X sidelink communication configuration information. When in the state that the UE 601 camps on the first cell 603 that only provides NR V2X sidelink communication configuration information or LTE V2X sidelink communication configuration information, when at least one second cell 604 is detected to meet the cell selection condition (S criterion) for configuring V2V sidelink communication, it can be determined whether the UE 601 is within the coverage of at least one second cell 604 that provides LTE V2X sidelink communication configuration information or NR V2X sidelink communication configuration information that the first cell 603 cannot provide. When it is determined that the UE 601 is within the coverage of the second cell 604, the UE 601 may obtain system information including V2X sidelink communication configuration information only from the second cell 604 without performing cell selection / reselection on the detected second cell 604. The V2X sidelink communication configuration information included in the system information obtained from the second cell 604 is LTE V2X sidelink communication configuration information or NR V2X sidelink communication configuration information that the first cell 603 that only provides NR V2X sidelink communication configuration information or LTE V2X sidelink communication configuration information cannot provide. When the UE 601 is not within the coverage of the second cell 604, that is, when the UE 601 is out of coverage (OOC) of the second cell 604, the UE 601 may use pre-configuration.

[0150] Reference Figure 6 , in operation 610, the UE 601 may transmit data to and receive data from the LTE eNB 603 connected to the 5GC in the RRC connected mode (RRC_CONNECTED).

[0151] When there is no data transmission / reception for a predetermined reason or within a predetermined time, in operation 615, the LTE eNB 603 cannot send an RRC connection release message (RRCConnectionRelease message) including non-active configuration information (RRC-InactiveConfig).

[0152] In operation 620, the UE 601 that receives the RRC connection release message may switch to the RRC inactive mode (RRC_INACTIVE).

[0153] In operation 625, the UE 601 in RRC Inactive mode may discover a suitable LTE cell 603 through a cell selection process or a cell reselection process, and camp on the discovered cell to obtain system information. According to an embodiment, the system information may be one or more SIBx, including MIB1 (Master Information Block Type 1), SIB1, SIB2, SIB3, SIB4, SIB5, SIB21, SIB26, and / or NR V2X sidelink configuration information defined / introduced for NR V2X sidelink communication. The cell on which the UE camps may be referred to as a serving cell (SCell) or a primary cell (PCell).

[0154] According to various embodiments of the present disclosure, in operation 625, the UE 601 may be configured to perform LTE V2X sidelink communication, and may select or reselect a suitable LTE cell and obtain the required system information including LTE V2X sidelink configuration information. The UE 601 may perform LTE V2X sidelink communication based on the obtained LTE V2X sidelink configuration information.

[0155] According to various embodiments of the present disclosure, in operation 625, the UE 601 is configured to perform both LTE V2X sidelink communication and NR V2X sidelink communication, but may select or reselect a suitable LTE cell and obtain system information including only the required LTE V2X sidelink configuration information. The UE 601 may perform LTE V2X sidelink communication based on the obtained LTE V2X sidelink configuration information. Specifically, in operation 625, when it is indicated that there is an SIBx described by a scheduling information list (SchedulingInfoList) in the SIB1 (SystemInformationBlockType1) received from a cell (Scell or PCell), the UE 601 in the RRC inactive mode may obtain the SIBx. Alternatively, when a valid SIBx is not stored, the UE 601 may obtain the SIBx. When the LTE eNB 603 broadcasts the SIBx, the SIBx selectively includes s1-V2X-ConfigCommon. The sl-V2X-ConfigCommon may include at least one of the following: v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, threshSS-TxPrioritization, anchorCarrierFreqList, offsetDFN, cbr-CommonTxConfigList, cbr-pssch-TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR. Additionally, the SIBx may include sidelink bearers of the PC5 QoS profile (sidelink radio bearer (SLRB) configuration information. According to an embodiment, the sidelink bearer configuration information of one or more PC5 QoS profiles may include mapping information of one SLRB and / or PDCP / RLC / logical channel (LCH) configuration information. Alternatively, the sidelink bearer configuration information of one PC5 QoS profile may include mapping information of one or more SLRBs and / or PDCP / RLC / LCH configuration information.The PC5 QoS profile can be at least one of the following: packet filtering information (PFI), range and / or required transmission rate (required data rate), or PC5 QoS parameters / characteristics of the PC5 5G QoS identifier (PQI) (see [Table 1]).

[0156] The following [Table 1] indicates the standardized mapping of PQI to QoS characteristics.

[0157] [Table 1]

[0158]

[0159]

[0160] In operation 630, packets for transmitting NR V2X sidelink communication or the arrival of packets for transmitting NR V2X sidelink communication can be generated and configured to perform NR V2X sidelink communication. Additionally, it can be indicated to perform NR V2X sidelink communication in a specific frequency.

[0161] According to various embodiments of the present disclosure, operation 630 can be performed in operation 625.

[0162] In operation 635, a higher layer device can configure the PC5 QoS profile (e.g., PQI) in the packet and transmit the packet and its PC5 QoS profile to an access stratum (AS) device. When there is no indication in operation 630 to perform NR V2X sidelink communication in a specific frequency, an indication can be made in operation 635.

[0163] In operation 640, the AS device can determine whether the sidelink bearer configuration information of the PC5 QoS profile in the packet received in operation 635 exists in the SIBx received in operation 625. According to an embodiment, the AS device can identify whether a sidelink bearer identifier or its sidelink bearer mapped to the PC5 QoS profile (e.g., PQI and / or range) is configured. According to an embodiment, this is because the LTE eNB may not include the sidelink bearer configuration information of the PC5 QoS profile due to limitations on the SIBx size. The sidelink bearer configuration information of the PC5 QoS profile can be broadcast through the SIBx regardless of the frequency, or can be broadcast separately for each frequency. When the sidelink bearer configuration information is broadcast for each frequency, it can be determined whether the sidelink bearer configuration information of the PC5 QoS profile in the frequency indicated by the above operation exists in the received SIBx.

[0164] In operation 645, the AS device may determine whether the specific frequency indicated by the higher layer device in operation 630 or operation 635 is within the coverage area, or whether the specific frequency is included in SIBx.

[0165] In operation 650, the AS device may determine whether the specific frequency includes resource information for transmitting NR V2X sidelink communication. Additionally, it may be determined whether the sensed result in the corresponding resource information is available. The resource information according to this embodiment may refer to a regularly used transmission resource pool (e.g., v2x-CommTxPoolNormal, v2x-CommTxPoolNormalCommon) or an exceptionally used transmission resource pool (e.g., v2x-CommTxPoolExceptional).

[0166] When operations 640, 645, or 650 are not satisfied, in operation 655, UE 601 may obtain the system information broadcast by NR gNB 604. The system information may refer to the system information including the NR V2X sidelink communication configuration information. When there is no neighboring LTE cell that satisfies operations 640, 645, or 650, UE 60I may perform a cell selection / reselection process and obtain the system information. The system information may be the system information including the NR sidelink communication configuration information that satisfies the above operations. The embodiments of the present disclosure propose a method by which UE 601 resides in an LTE cell, obtains the system information only from an NR cell, and uses the information included in the system information without finally selecting / reselecting an NR cell. That is, since UE 601 does not finally perform inter-RAT cell selection / reselection, the RRC inactive mode may be maintained in operation 656. Additionally, UE 601 may obtain only the system information including the NR V2X sidelink communication configuration information broadcast by a second LTE cell rather than the first LTE cell in which UE currently resides to perform NR sidelink communication without intra-RAT cell selection / reselection. For example, when there is a second LTE cell that shares the NR V2X sidelink communication configuration information and the LTE V2X sidelink communication configuration information at a certain frequency, UE 601 may obtain the NR V2X sidelink communication configuration information only from the second LTE cell operating at the corresponding frequency. The corresponding frequency may be the frequency indicated in operation 630 for performing NR V2X sidelink communication.

[0167] In operation 660, the UE 601 may perform NR V2X sidelink communication (send an NR V2X sidelink packet) with another UE 602 based on the system information received in operation 655. When operation 640, operation 645, or operation 650 is not satisfied, the cell selection / reselection process (that is, operation 655) is not performed; and operation 660 may be performed using pre-configuration while maintaining the RRC inactive mode in operation 656. According to an embodiment, the UE 601 may perform NR V2X sidelink communication with another UE 602 through one of the transmission resource pool lists (for example, v2x-CommTxPoolList) included in the SL-V2X-preconfiguration. Alternatively, when operation 640, operation 645, or operation 650 is not satisfied because the cell selection / reselection process has been performed but a suitable LTE cell or NR cell has not been found, the UE 601 may perform operation 660 using pre-configuration while maintaining the RRC inactive mode in operation 656.

[0168] Figure 7 An example of a process in a wireless communication system according to various embodiments of the present disclosure is shown: a process in which a UE switches from an RRC connection mode (RRC_CONNECTED) with an LTE eNB (ng-eNB) connected to a 5GC to an RRC idle mode (RRC_IDLE); and a process in which a UE in the RRC idle mode performs NR V2X sidelink communication.

[0169] The UE 701 according to an embodiment of the present disclosure may refer to a vehicle-mounted UE or a pedestrian UE. The UE 701 may support V2X sidelink communication through one or more radio access technologies (RATs). According to an embodiment, the UE may support only LTE V2X sidelink communication or only NR V2X sidelink communication, or may support both LTE V2X sidelink communication and NR V2X sidelink communication. The LTE eNB 703 according to an embodiment of the present disclosure may periodically broadcast system information related to LTE V2X sidelink configuration information and / or system information related to NR V2X sidelink configuration information.

[0170] When the UE 701 according to an embodiment of the present disclosure is configured to simultaneously transmit NR V2X sidelink communication and LTE V2X sidelink communication, if the UE does not obtain NR V2X sidelink communication configuration information and LTE V2X sidelink communication configuration information from a cell simultaneously, the UE may camp on one of the cells that only provide NR V2X sidelink communication configuration information or the cells that only provide LTE V2X sidelink communication configuration information. When in the state that the UE 701 camps on the first cell 703 that only provides NR V2X sidelink communication configuration information or LTE V2X sidelink communication configuration information, when at least one second cell 704 is detected to meet the cell selection condition (S criterion) for configuring the frequency of V2V sidelink communication, it can be determined whether the UE 701 is within the coverage of at least one second cell 704 that provides LTE V2X sidelink communication configuration information or NR V2X sidelink communication configuration information that the first cell 703 cannot provide. When it is determined that the UE 701 is within the coverage of the second cell 704, the UE 701 may obtain the system information including V2X sidelink communication configuration information only from the second cell 704 without performing cell selection / reselection on the detected second cell 704. The V2X sidelink communication configuration information included in the system information obtained from the second cell 704 is the LTE V2X sidelink communication configuration information or NR V2X sidelink communication configuration information that the first cell 703 that only provides NR V2X sidelink communication configuration information or LTE V2X sidelink communication configuration information cannot provide. When the UE 701 is not within the coverage of the second cell 704, that is, when the UE 701 is out-of-coverage (OOC) of the second cell 704, the UE 701 may use pre-configuration.

[0171] Reference Figure 7 , in operation 710, the UE 701 may send and receive data from the LTE eNB 703 connected to the 5GC in the RRC connected mode (RRC_CONNECTED).

[0172] When there is no data sent / received for a predetermined reason or within a predetermined time, in operation 715, the LTE eNB 703 may send an RRC connection release message (RRCConnectionRelease message) that does not include inactive configuration information (RRC-InactiveConfig).

[0173] In operation 720, the UE 701 that receives the RRC connection release message may switch to the RRC idle mode (RRC_IDLE).

[0174] In operation 725, the UE 701 in the RRC idle mode can discover a suitable LTE cell 703 through a cell selection process or a cell reselection process, and camp on the discovered cell to obtain system information. According to an embodiment, the system information can be one or more SIBx, including MIB1, SIB1, SIB2, SIB3, SIB4, SIB5, SIB21, SIB26, and / or NR V2X sidelink configuration information defined / introduced for NR V2X sidelink communication. The cell on which the UE camps can be referred to as a serving cell (SCell) or a primary cell (PCell).

[0175] According to various embodiments of the present disclosure, in operation 725, the UE 701 can be configured to perform LTE V2X sidelink communication, and can select or reselect a suitable LTE cell and obtain system information including the required LTE V2X sidelink configuration information. The UE 701 can perform LTE V2X sidelink communication based on the obtained LTE V2X sidelink configuration information.

[0176] According to various embodiments of the present disclosure, in operation 725, the UE 701 is configured to perform both LTE V2X sidelink communication and NR V2X sidelink communication, but can select or reselect a suitable LTE cell and obtain system information including only the required LTE V2X sidelink configuration information. The UE 701 can perform LTE V2X sidelink communication based on the obtained LTE V2X sidelink configuration information.

[0177] Specifically, in operation 725, when it is indicated that there is a SIBx described by a scheduling information list (SchedulingInfoList) in SIB1 (System Information Block Type 1) received from a cell (Scell or PCell), the UE 701 in RRC idle mode can obtain the SIBx. Alternatively, when there is no valid SIBx stored, the UE 701 can obtain the SIBx. When the LTE eNB 703 broadcasts the SIBx, the SIBx selectively includes s1-V2X-ConfigCommon. The sl-V2X-ConfigCommon may include at least one of the following: v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, threshSS-TxPrioritization, anchorCarrierFreqList, offsetDFN, cbr-CommonTxConfigList, cbr-pssch-TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR. Additionally, the SIBx may include side-link bearers of PC5 QoS profiles (side-link radio bearer (SLRB) configuration information). According to an embodiment, the side-link bearer configuration information of one or more PC5 QoS profiles may include mapping information of one SLRB and / or PDCP / RLC / LCH configuration information. Alternatively, the side-link bearer configuration information of one PC5 QoS profile may include mapping information of one or more SLRBs and / or PDCP / RLC / logical channel (LCH) configuration information. The PC5 QoS profile may be at least one of the following: packet filtering information (PFI), range and / or required transmission rate (required data rate), or PC5 5G QoS identifier (PQI) of PC5 QoS parameters / characteristics (see [Table 1]).

[0178] In operation 730, a packet for transmitting NR V2X sidelink communication or an arrival of a packet for transmitting NR V2X sidelink communication may be generated and configured to perform NR V2X sidelink communication. Additionally, it may be indicated to perform NR V2X sidelink communication in a specific frequency.

[0179] According to various embodiments of the present disclosure, operation 730 may be performed in operation 725. In operation 735, a higher layer device may configure a PC5 QoS profile (e.g., PQI) in the packet and transmit the packet and its PC5 QoS profile to an access stratum (AS) device. When there is no indication to perform NR V2X sidelink communication in a specific frequency in operation 730, an indication may be made in operation 735.

[0180] In operation 740, the AS device may determine whether sidelink bearer configuration information of the PC5 QoS profile in the packet received in operation 735 exists in the SIBx received in operation 725. According to an embodiment, the AS device may identify whether a sidelink bearer identifier or its sidelink bearer mapped to the PC5 QoS profile (e.g., PQI and / or range) is configured. According to an embodiment, this is because the LTE eNB 703 may not include sidelink bearer configuration information of the PC5 QoS profile due to limitations on the SIBx size. The sidelink bearer configuration information of the PC5 QoS profile may be broadcast through the SIBx regardless of the frequency, or may be broadcast separately for each frequency. When the sidelink bearer configuration information is broadcast for each frequency, it may be determined whether the sidelink bearer configuration information of the PC5 QoS profile in the frequency indicated by the above operation exists in the received SIBx.

[0181] In operation 745, the AS device may determine whether the specific frequency indicated by the higher layer device in operation 730 or operation 735 is within coverage, or whether the specific frequency is included in the SIBx.

[0182] In operation 750, it may be determined whether resource information for transmitting NR V2X sidelink communication is included in a specific frequency. Additionally, it may be determined whether the result sensed in the corresponding resource information is available. The resource information according to this embodiment may refer to a normally used transmission resource pool (e.g., v2x-CommTxPoolNormal, v2x-CommTxPoolNormalCommon) or an exceptionally used transmission resource pool (e.g., v2x-CommTxPoolExceptional).

[0183] When the operations 740, 745, or 750 are not satisfied, in operation 755, the UE 701 may perform a cell selection process or a cell reselection process. When a suitable NR cell 704 is finally selected / reselected through the cell selection process or the cell reselection process, in operation 760, the UE 701 may enter the RRC idle mode.

[0184] When the operations 740, 745, or 750 are not satisfied, in operation 755, the UE 701 may only obtain the system information broadcast by the NR cell 704 without performing cell selection / reselection for the NR cell 704. The system information may refer to the system information including the NR V2X sidelink communication configuration information. The system information may be the system information including the NR sidelink communication configuration information that satisfies the above operations. An embodiment of the present disclosure proposes a method by which the UE 701 camps on the LTE cell 703, only obtains the system information from the NR cell 704, and uses the information included in the system information without finally selecting / reselecting the NR cell 704. That is to say, the UE 701 may not finally perform inter-RAT cell selection / reselection.

[0185] In addition, the UE 701 may only obtain the system information including the NR V2X sidelink communication configuration information broadcast by the second LTE cell rather than the first LTE cell on which the UE currently camps, so as to perform NR sidelink communication without intra-RAT cell selection / reselection. For example, when there is a second LTE cell that shares the NR V2X sidelink communication configuration information and the LTE V2X sidelink communication configuration information at a frequency, the UE 701 may only obtain the NR V2X sidelink communication configuration information from the second LTE cell operating at the corresponding frequency. The corresponding frequency may be the frequency indicated in operation 730 for performing NR V2X sidelink communication.

[0186] In operation 765, the UE 701 may obtain the system information broadcast by the selected / reselected NR cell 704. When the NR cell 704 performs broadcasting periodically, the UE 701 may obtain the system information broadcast by the NR cell 704 according to the corresponding period of the NR cell 704. When the NR cell 704 signals the system information according to the required type, the UE may request the corresponding system information from the NR gNB and obtain the system information. According to an embodiment, in the random access process with the NR cell BS 704, the UE 701 may send a request and obtain the system information through a preamble (msg1) or through an RRC system information request message (RRCSystemInfoRequest message, msg3). According to an embodiment, the system information may be the system information including the NR V2X sidelink communication configuration information that satisfies the above operations.

[0187] In operation 770, the UE 701 may perform NR V2X sidelink communication (transmit an NR V2X sidelink packet) with another UE 702 based on the system information received in operation 765. Alternatively, when operations 740, 745, or 750 are not satisfied because a cell selection / reselection process has been performed but a suitable LTE cell or NR cell has not been found, pre-configuration may be used to perform operation 770. According to an embodiment, the UE 701 may perform NR V2X sidelink communication with another UE 702 through one of the transmission resource pool lists (e.g., v2x-CommTxPoolList) included in the SL-V2X-preconfiguration. Alternatively, the UE 701 may use pre-configuration to perform operation 770 without a cell selection / reselection process (that is, without operation 755).

[0188] Figure 8 Examples of processes in a wireless communication system according to various embodiments of the present disclosure are shown: a process in which a UE switches from a radio resource control (RRC) connected mode (RRC_CONNECTED) with an NR next-generation node B (gNB) connected to a 5G core network (5GC) to an RRC inactive mode (RRC_INACTIVE); and a process in which a UE in the RRC inactive mode performs LTE V2X sidelink communication.

[0189] The UE 801 according to an embodiment of the present disclosure may refer to a vehicle-mounted UE or a pedestrian UE. The UE may support V2X sidelink communication through one or more radio access technologies (RATs). According to an embodiment, the UE may support only LTE V2X sidelink communication or only NR V2X sidelink communication, or may support both LTE V2X sidelink communication and NR V2X sidelink communication. The NR gNB according to an embodiment of the present disclosure may broadcast system information related to LTE V2X sidelink configuration information and / or system information related to NR V2X sidelink configuration information periodically or according to a required type.

[0190] When the UE 801 according to an embodiment of the present disclosure is configured to simultaneously transmit NR V2X sidelink communication and LTE V2X sidelink communication, if the UE does not obtain the NR V2X sidelink communication configuration information and the LTE V2X sidelink communication configuration information from a cell simultaneously, the UE may camp on one of the cells that provide only the NR V2X sidelink communication configuration information or the cells that provide only the LTE V2X sidelink communication configuration information. When in the state that the UE 801 camps on the first cell 803 that provides only the NR V2X sidelink communication configuration information or the LTE V2X sidelink communication configuration information, when at least one detected second cell 804 satisfies the cell selection condition (S criterion) for configuring the V2V sidelink communication frequency, it can be determined whether the UE 801 is within the coverage of at least one second cell 804 that provides the LTE V2X sidelink communication configuration information or the NR V2X sidelink communication configuration information that the first cell 803 cannot provide. When it is determined that the UE 801 is within the coverage of the second cell 804, the UE 801 may obtain the system information including the V2X sidelink communication configuration information only from the second cell 804 without performing cell selection / reselection on the detected second cell 804. The V2X sidelink communication configuration information included in the system information obtained from the second cell 804 is the LTE V2X sidelink communication configuration information or the NR V2X sidelink communication configuration information that the first cell 803 that provides only the NR V2X sidelink communication configuration information or the LTE V2X sidelink communication configuration information cannot provide. When the UE801 is not within the coverage of the second cell 804, that is, when the UE 801 is out of coverage (OOC) of the second cell 804, the UE 801 may use the pre-configuration.

[0191] Reference Figure 8 , in operation 810, the UE 801 may transmit data to and receive data from the NR gNB 803 connected to the 5GC in the RRC connected mode (RRC_CONNECTED).

[0192] When there is no data transmission / reception for a predetermined reason or within a predetermined time, in operation 815, the NR gNB803 may send an RRC connection release message (RRCConnectionRelease message) including the suspend configuration information (suspendConfig).

[0193] In operation 820, the UE 801 that receives the RRC connection release message may switch to the RRC inactive mode (RRC_INACTIVE).

[0194] In operation 825, the UE 801 in RRC Inactive mode may discover a suitable NR cell 803 through a cell selection process or a cell reselection process, and camp on the discovered cell to obtain system information. According to an embodiment, the system information may be one or more SIBy, including MIB1 (Master Information Block Type 1), SIB1, SIB2, SIB3, SIB4, SIB5, and LTE V2X sidelink configuration information defined / introduced for LTE V2X sidelink communication. The cell on which the UE camps may be referred to as a serving cell (SCell) or a primary cell (PCell).

[0195] According to various embodiments of the present disclosure, in operation 825, the UE 801 may be configured to perform NR V2X sidelink communication, and may select or reselect a suitable NR cell and obtain system information including the required NR V2X sidelink configuration information. The UE 801 may perform NR V2X sidelink communication based on the obtained NR V2X sidelink configuration information.

[0196] According to various embodiments of the present disclosure, in operation 825, the UE 801 is configured to perform both LTE V2X sidelink communication and NR V2X sidelink communication. The UE 801 may select or reselect a suitable NR cell and obtain system information including only the required NR V2X sidelink configuration information. The UE 801 may perform NR V2X sidelink communication based on the obtained NR V2X sidelink configuration information.

[0197] Specifically, in operation 825, when it is indicated that there is SIBy described in the system information scheduling information list (si-SchedulingInfo) in SIB1 (System Information Block Type 1) received from a cell (Scell or PCell), the UE 801 in RRC inactive mode can acquire SIBy. Alternatively, when there is no valid SIBy stored, the UE 801 can acquire SIBy. When the NR gNB 803 broadcasts SIBy, SIBy selectively includes s1-V2X-ConfigCommon. s1-V2X-ConfigCommon can include at least one of the following: v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, threshSS-TxPrioritization, anchorCarrierFreqList, offsetDFN, cbr-CommonTxConfigList, cbr-pssch-TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR.

[0198] In operation 830, a packet for transmitting LTE V2X sidelink communication can be generated, or a packet for transmitting LTE V2X sidelink communication arrives, and it can be configured to perform LTE V2X sidelink communication. Additionally, an indication to perform LTE V2X sidelink communication at a specific frequency can be indicated.

[0199] According to various embodiments of the present disclosure, operation 830 can be performed in operation 825.

[0200] In operation 835, the AS device can determine whether the specific frequency indicated by the higher layer device in operation 830 is within the coverage area, or whether the specific frequency is included in SIBy.

[0201] In operation 840, the AS device may determine whether the resource information for transmitting LTE V2X sidelink communication is included in a specific frequency. Additionally, it may be determined whether the sensed result in the corresponding resource information is available. The resource information according to this embodiment may refer to a regularly used transmission resource pool (e.g., v2x-CommTxPoolNormal, v2x-CommTxPoolNormalCommon) or an exceptionally used transmission resource pool (e.g., v2x-CommTxPoolExceptional).

[0202] When operation 835 or operation 840 is not satisfied, in operation 845, the UE may obtain the system information broadcast by the LTE eNB 804. The system information may be the system information including the LTE V2X sidelink communication configuration information that satisfies the above operations. According to an embodiment, the system information may be SIB21 or SIB26. When there is no neighboring NR cell that satisfies operation 835 or operation 840 based on the cell selection / reselection process, the UE 801 may obtain the system information. An embodiment of the present disclosure proposes a method by which the UE 801 resides in an NR cell, obtains only the system information from the LTE cell, and uses the information included in the system information without finally selecting / reselecting an LTE cell. That is, since the UE 801 does not finally perform inter-RAT cell selection / reselection, the RRC inactive mode may be maintained in operation 846. Additionally, the UE 801 may obtain only the system information including the LTE V2X sidelink communication configuration information broadcast by the second NR cell rather than the first NR cell in which the UE currently resides to perform LTE sidelink communication without intra-RAT cell selection / reselection. For example, when there is a second NR cell that shares the NR V2X sidelink communication configuration information and the LTE V2X sidelink communication configuration information at one frequency, the UE 801 may obtain the LTE V2X sidelink communication configuration information only from the second NR cell operating at the corresponding frequency. The corresponding frequency may be the frequency indicated in operation 830 for performing LTE V2X sidelink communication.

[0203] In operation 850, the UE 801 may perform LTE V2X sidelink communication (transmit LTE V2X sidelink packets) with another UE 802 based on the system information received in operation 845. When operation 835 or operation 840 is not satisfied, the cell selection / reselection process is not performed (that is, operation 845 is not performed), and operation 850 may be performed using pre-configuration while maintaining the RRC inactive mode in operation 846. According to an embodiment, the UE 801 may perform LTE V2X sidelink communication with another UE 802 through one of the transmission resource pool lists (e.g., v2x-CommTxPoolList) included in the SL-V2X-preconfiguration. Alternatively, when operation 835 or operation 840 is not satisfied because the cell selection / reselection process has been performed but a suitable LTE cell or NR cell has not been found, the UE 801 may perform operation 850 using pre-configuration while maintaining the RRC inactive mode in operation 846.

[0204] Figure 9 An example of a process in a wireless communication system according to various embodiments of the present disclosure is shown: an example of a process in which a UE switches from an RRC connection mode (RRC_CONNECTED) to an RRC idle mode (RRC_IDLE) with an NR gNB connected to a 5GC; and a process in which a UE in the RRC idle mode performs LTE V2X sidelink communication.

[0205] The UE 901 according to an embodiment of the present disclosure may refer to a vehicle-mounted UE or a pedestrian UE. The UE 901 may support V2X sidelink communication through one or more radio access technologies (RAT). According to an embodiment, the UE may support only LTE V2X sidelink communication or only NR V2X sidelink communication, or may support both LTE V2X sidelink communication and NR V2X sidelink communication. The NR gNB 903 according to an embodiment of the present disclosure may broadcast system information related to LTE V2X sidelink configuration information and / or system information related to NR V2X sidelink configuration information periodically or according to a required type.

[0206] When the UE 901 according to an embodiment of the present disclosure is configured to simultaneously transmit NR V2X sidelink communication and LTE V2X sidelink communication, if the UE does not obtain the NR V2X sidelink communication configuration information and the LTE V2X sidelink communication configuration information from a cell simultaneously, the UE may camp on one of the cells that only provide the NR V2X sidelink communication configuration information or the cells that only provide the LTE V2X sidelink communication configuration information. When in the state that the UE 901 camps on the first cell 903 that only provides the NR V2X sidelink communication configuration information or the LTE V2X sidelink communication configuration information, when at least one second cell 904 that satisfies the cell selection condition (S criterion) for configuring the V2V sidelink communication is detected, it can be determined whether the UE 901 is within the coverage of at least one second cell 904 that provides the LTE V2X sidelink communication configuration information or the NR V2X sidelink communication configuration information that the first cell 903 cannot provide. When it is determined that the UE 901 is within the coverage of the second cell 904, the UE 901 may obtain the system information including the V2X sidelink communication configuration information only from the second cell 904 without performing cell selection / reselection on the detected second cell 904. The V2X sidelink communication configuration information included in the system information obtained from the second cell 904 is the LTE V2X sidelink communication configuration information or the NR V2X sidelink communication configuration information that the first cell 903 that only provides the NR V2X sidelink communication configuration information or the LTE V2X sidelink communication configuration information cannot provide. When the UE 901 is not within the coverage of the second cell 904, that is, when the UE 901 is out of coverage (OOC) of the second cell 904, the UE 901 may use to.

[0207] Reference Figure 9 , in operation 910, the UE 901 may transmit data to and receive data from the NR gNB 903 connected to the 5GC in the RRC connected mode (RRC_CONNECTED).

[0208] When there is no data transmission / reception for a predetermined reason or within a predetermined time, in operation 915, the BS 903 may send an RRC release message (RRCRelease message) including suspend configuration information (suspendConfig).

[0209] In operation 920, the UE 901 that receives the RRC connection release message may switch to the RRC idle mode (RRC_IDLE).

[0210] In operation 925, a UE 901 in RRC idle mode may discover a suitable NR cell 903 through a cell selection process or a cell reselection process and camp on the discovered cell to obtain system information. According to an embodiment, the system information may be one or more SIBy, including MIB1, SIB1, SIB2, SIB3, SIB4, SIB5, and LTE V2X sidelink configuration information defined / introduced for LTE V2X sidelink communication. The cell on which the UE camps may be referred to as a serving cell (SCell) or a primary cell (PCell).

[0211] According to various embodiments of the present disclosure, in operation 925, the UE 901 may be configured to perform NR V2X sidelink communication, and may select or reselect a suitable NR cell and obtain system information including the required NR V2X sidelink configuration information. The UE 901 may perform NR V2X sidelink communication based on the obtained NR V2X sidelink configuration information.

[0212] According to various embodiments of the present disclosure, in operation 925, the UE 901 is configured to perform both LTE V2X sidelink communication and NR V2X sidelink communication. The UE 901 may select or reselect a suitable NR cell and obtain system information including only the required NR V2X sidelink configuration information. The UE 901 may perform NR V2X sidelink communication based on the obtained NR V2X sidelink configuration information.

[0213] Specifically, in operation 925, when it is indicated that there is SIBy described in the system information scheduling information list (si-SchedulingInfo) in the SIB1 (System Information Block Type 1) received from a cell (Scell or PCell), the UE 901 in RRC inactive mode can obtain SIBy. Alternatively, when there is no valid SIBy stored, the UE 901 can obtain SIBy. When the NR gNB 903 broadcasts SIBy, SIBy selectively includes s1-V2X-ConfigCommon. s1-V2X-ConfigCommon can include at least one of the following: v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, threshSS-TxPrioritization, anchorCarrierFreqList, offsetDFN, cbr-CommonTxConfigList, cbr-pssch-TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR.

[0214] In operation 930, a packet for transmitting LTE V2X sidelink communication can be generated, or a packet for transmitting LTE V2X sidelink communication arrives, and it can be configured to perform LTE V2X sidelink communication. Additionally, an indication can be made to perform LTE V2X sidelink communication at a specific frequency.

[0215] According to various embodiments of the present disclosure, operation 930 can be performed in operation 925.

[0216] In operation 935, the AS device can determine whether the specific frequency indicated by the higher layer device in operation 930 is within the coverage area, or whether the specific frequency is included in SIBy.

[0217] In operation 940, the AS device may determine whether the resource information for transmitting LTE V2X sidelink communication is included in a specific frequency. Additionally, it may be determined whether the sensed result in the corresponding resource information is available. The resource information according to this embodiment may refer to a regularly used transmission resource pool (e.g., v2x-CommTxPoolNormal, v2x-CommTxPoolNormalCommon) or an exceptionally used transmission resource pool (e.g., v2x-CommTxPoolExceptional).

[0218] When operation 935 or operation 940 is not satisfied, in operation 945, a cell selection process or a cell reselection process may be performed. When a suitable LTE cell 904 is finally selected / reselected through the cell selection process or the cell reselection process, in operation 950, the UE 901 may enter the RRC idle mode.

[0219] When operation 940 or operation 945 is not satisfied, in operation 945, the UE 901 may only obtain the system information broadcast by the LTE cell 904 without selecting / reselecting the LTE cell 904. The system information may refer to the system information including the LTE V2X sidelink communication configuration information. The system information may be the system information including the LTE sidelink communication configuration information that satisfies the above operations. The embodiments of the present disclosure propose a method by which the UE 901 resides in the NR cell 903, only obtains the system information from the LTE cell 904, and uses the information included in the system information without finally selecting / reselecting the LTE cell 904. That is, the UE 901 may ultimately not perform inter-RAT cell selection / reselection.

[0220] Additionally, the UE 901 may only obtain the system information including the LTE V2X sidelink communication configuration information broadcast by a second NR cell rather than the first NR cell where the UE currently resides to perform LTE sidelink communication without intra-RAT cell selection / reselection. For example, when there is a second NR cell that shares the NR V2X sidelink communication configuration information and the LTE V2X sidelink communication configuration information at a frequency, the UE 901 may only obtain the LTE V2X sidelink communication configuration information from the second NR cell operating at the corresponding frequency. The corresponding frequency may be the frequency indicated in operation 930 for performing LTE V2X sidelink communication.

[0221] In operation 955, the UE 901 may obtain system information broadcast by the selected / reselected LTE eNB 904. The system information may be system information including LTE V2X sidelink communication configuration information that satisfies the above operations. According to an embodiment, the system information may be SIB21 or SIB26. When there is no neighboring NR cell that satisfies operation 935 or operation 940 based on the cell selection / reselection process, the UE 901 may obtain the system information.

[0222] In operation 960, the UE 901 may perform LTE V2X sidelink communication (send LTE V2X sidelink packets) with another UE 902 based on the system information received in operation 955. Alternatively, when operation 940 is not satisfied because the cell selection / reselection process has been performed but no suitable LTE cell or NR cell has been found, pre-configuration may be used to perform operation 960. According to an embodiment, the UE 901 may perform LTE V2X sidelink communication with another UE 902 through one of the transmission resource pool lists (e.g., v2x-CommTxPoolList) included in the SL-V2X-preconfiguration. Alternatively, operation 960 may be performed using pre-configuration without the cell selection / reselection process (i.e., without operation 945).

[0223] Figure 10 Examples of the following processes in a wireless communication system according to various embodiments of the present disclosure are shown: a process in which a UE switches from a Radio Resource Control (RRC) connected mode (RRC_CONNECTED) to an RRC inactive mode (RRC_INACTIVE) with an LTE eNB (ng-eNB) connected to a 5GC; and a process in which a UE in the RRC inactive mode performs NR V2X sidelink communication.

[0224] The UE 1001 according to an embodiment of the present disclosure may refer to a vehicle-mounted UE or a pedestrian UE. The UE 1001 may support V2X sidelink communication through one or more Radio Access Technologies (RATs). According to an embodiment, the UE may support only LTE V2X sidelink communication or only NR V2X sidelink communication, or may support both LTE V2X sidelink communication and NR V2X sidelink communication. The LTE eNB 1003 according to an embodiment of the present disclosure may periodically broadcast system information related to LTE V2X sidelink configuration information and / or system information related to NR V2X sidelink configuration information.

[0225] Reference Figure 10, in operation 1010, the UE 1001 can send and receive data from the LTE eNB 1003 connected to the 5GC in the RRC connected mode (RRC_CONNECTED).

[0226] When the UE 1001 does not send / receive data for a predetermined reason or within a predetermined time, in operation 1015, the LTE eNB 1003 can send an RRC connection release message (RRCConnectionRelease message) including inactive configuration information (RRC-InactiveConfig).

[0227] In operation 1020, the UE 1001 that receives the RRC connection release message can switch to the RRC inactive mode (RRC_INACTIVE).

[0228] In operation 1025, the UE 1001 in the RRC inactive mode can discover a suitable LTE cell 1003 through a cell selection process or a cell reselection process and camp on the discovered cell to obtain system information. According to an embodiment, the system information can be one or more SIBx, including MIB1, SIB1, SIB2, SIB3, SIB4, SIB5, SIB21, SIB26, and / or NR V2X sidelink configuration information defined / introduced for NR V2X sidelink communication. The cell on which the UE camps can be referred to as a serving cell (SCell) or a primary cell (PCell).

[0229] According to various embodiments of the present disclosure, in operation 1025, the UE 1001 can be configured to perform LTE V2X sidelink communication, and can select or reselect a suitable LTE cell and obtain system information including the required LTE V2X sidelink configuration information. The UE 1001 can perform LTE V2X sidelink communication based on the obtained LTE V2X sidelink configuration information.

[0230] According to various embodiments of the present disclosure, in operation 1025, although the UE 1001 is configured to perform both LTE V2X sidelink communication and NR V2X sidelink communication, the UE 1001 can select or reselect a suitable LTE cell and obtain system information including only the required LTE V2X sidelink configuration information. The UE 1001 can perform LTE V2X sidelink communication based on the obtained LTE V2X sidelink configuration information.

[0231] Specifically, in operation 1025, when it is indicated that there is SIBx described in the SchedulingInfoList in SIB1 (System Information Block Type 1) received from a cell (Scell or PCell), the UE 1001 in RRC Inactive mode may acquire SIBx. Alternatively, when there is no valid SIBx stored, the UE 1001 may acquire SIBx. When the LTE eNB 1003 broadcasts SIBx, SIBx selectively includes s1-V2X-ConfigCommon. The s1-V2X-ConfigCommon may include at least one of the following: v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, threshSS-TxPrioritization, anchorCarrierFreqList, offsetDFN, cbr-CommonTxConfigList, cbr-pssch-TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR. Additionally, SIBx may include the sidelink bearer of the PC5 QoS profile (sidelink radio bearer (SLRB) configuration information). According to an embodiment, the sidelink bearer configuration information of one or more PC5 QoS profiles may include the mapping information of one SLRB and / or PDCP / RLC / LCH configuration information. Alternatively, the sidelink bearer configuration information of one PC5 QoS profile may include the mapping information of one or more SLRBs and / or PDCP / RLC / logical channel (LCH) configuration information. The PC5 QoS profile may be at least one of the following: packet filtering information (PFI), range and / or required transmission rate (required data rate), or the PC5 QoS parameters / characteristics of the PC5 5G QoS identifier (PQI) (see [Table 1]).

[0232] In operation 1030, the higher layer device may configure the AS device to receive NR V2X sidelink communication packets. Additionally, the higher layer device may indicate to receive NR V2X sidelink communication at a specific frequency.

[0233] According to various embodiments of the present disclosure, operation 1030 may be performed in operation 1025.

[0234] In operation 1035, the higher layer device may be configured to receive a PC5 QoS profile (PQI according to an embodiment) in an NR V2X sidelink communication packet and transmit its PC5 QoS profile to the AS device. When there is no indication in operation 1030 to perform NR V2X sidelink communication in a specific frequency, an indication may be made in operation 1035.

[0235] In operation 1040, the AS device may determine whether sidelink bearer configuration information of the PC5 QoS profile to be received in operation 1030 exists in the SIBx received in operation 1025. According to an embodiment, the AS device may identify whether a sidelink bearer identifier or its sidelink bearer mapped to the PC5 QoS profile (e.g., PQI and / or range) is configured. According to an embodiment, this is because the LTE eNB may not include sidelink bearer configuration information of the PC5 QoS profile due to limitations on the size of the SIBx. The sidelink bearer configuration information of the PC5 QoS profile may be broadcast through the SIBx regardless of the frequency, or may be broadcast separately for each frequency. When the sidelink bearer configuration information is broadcast for each frequency, it may be determined whether the sidelink bearer configuration information of the PC5 QoS profile in the frequency indicated by the above operation exists in the received SIBx.

[0236] In operation 1045, the AS device may determine whether the specific frequency indicated by the higher layer device in operation 1030 or operation 1035 is within the coverage area, or whether the specific frequency is included in the SIBx.

[0237] In operation 1050, the AS device may determine whether resource information for receiving NR V2X sidelink communication packets is included in a specific frequency. The resource information according to the present embodiment may refer to a conventionally used reception resource pool (e.g., commRxPool).

[0238] When operations 1040, 1045, or 1050 are not satisfied, in operation 1055, the UE may obtain the system information broadcast by the NR gNB 1004. The system information may refer to the system information including the NR V2X sidelink communication configuration information that satisfies the above operations. When there is no neighboring LTE cell that satisfies operations 1040, 1045, or 1050, the UE 1001 may perform a cell selection / reselection process and obtain the system information. An embodiment of the present disclosure proposes a method by which the UE 1001 resides in an LTE cell, obtains the system information only from an NR cell, and uses the information included in the system information, without finally selecting / reselecting an NR cell. That is, since the UE 1001 does not finally perform inter-RAT cell selection / reselection, the RRC inactive mode may be maintained in operation 1056. Additionally, the UE 1001 may obtain only the system information including the NR V2X sidelink communication configuration information broadcast by a second LTE cell rather than the first LTE cell in which the UE 1001 currently resides, to perform NR sidelink communication without intra-RAT cell selection / reselection. For example, when there is a second LTE cell that shares the NR V2X sidelink communication configuration information and the LTE V2X sidelink communication configuration information at a frequency, the UE 1001 may obtain the NR V2X sidelink communication configuration information only from the second LTE cell operating at the corresponding frequency. The corresponding frequency may be the frequency indicated in operation 1030 for performing NR V2X sidelink communication.

[0239] In operation 1060, the UE 1001 may receive the NR V2X sidelink communication sent by another UE 1002 based on the system information received in operation 1055. According to an embodiment, the sidelink control information and / or the corresponding data may be monitored in the reception resource pool (commRxPool) indicated by the system information. When operations 1040, 1045, or 1050 are not satisfied, operation 1055 is not performed; and operation 1060 may be performed using pre-configuration while maintaining the RRC inactive mode in operation 1056. According to an embodiment, the UE 1001 may receive the NR V2X sidelink communication sent by another UE 1002 through the reception resource pool included in the SL-V2X-preconfiguration (e.g., preconfigComm in the SL-preconfiguration). Alternatively, when operations 1040, 1045, or 1050 are not satisfied because a cell selection / reselection process has been performed but no suitable LTE cell or NR cell has been found, operation 1060 may be performed using pre-configuration while maintaining the RRC inactive mode in operation 1056.

[0240] Figure 11An example of a process in a wireless communication system according to various embodiments of the present disclosure is shown: a process in which a UE switches from a Radio Resource Control (RRC) connected mode (RRC_CONNECTED) to an RRC idle mode (RRC_IDLE) with respect to an LTE eNB (ng-eNB) connected to a 5G Core (5GC); and a process in which a UE in the RRC idle mode performs NR V2X sidelink communication.

[0241] A UE 1101 according to an embodiment of the present disclosure may refer to a vehicle-mounted UE or a pedestrian UE. The UE 1101 may support V2X sidelink communication through one or more Radio Access Technologies (RATs). According to an embodiment, the UE may support only LTE V2X sidelink communication or only NR V2X sidelink communication, or may support both LTE V2X sidelink communication and NR V2X sidelink communication. An LTE eNB 1103 according to an embodiment of the present disclosure may periodically broadcast system information related to LTE V2X sidelink configuration information and / or system information related to NR V2X sidelink configuration information.

[0242] Reference Figure 11 , in operation 1110, the UE 1101 may send and receive data from / to an LTE eNB 1103 connected to a 5GC in an RRC connected mode (RRC_CONNECTED).

[0243] When the UE 1101 does not send / receive data for a predetermined reason or within a predetermined time, in operation 1115, the LTE eNB 1103 may send an RRC connection release message (RRCConnectionRelease message) that does not include inactive configuration information (RRC-InactiveConfig).

[0244] In operation 1120, the UE 1101 that has received the RRC connection release message may switch to an RRC idle mode (RRC_IDLE).

[0245] In operation 1125, the UE 1101 in the RRC idle mode may discover a suitable LTE cell 1103 through a cell selection process or a cell reselection process and camp on the discovered cell to obtain system information. According to an embodiment, the system information may be one or more System Information Blocks (SIBx), including Master Information Block 1 (MIB1), SIB1, SIB2, SIB3, SIB4, SIB5, SIB21, SIB26, and / or NR V2X sidelink configuration information defined / introduced for NR V2X sidelink communication. The cell on which the UE camps may be referred to as a serving cell (SCell) or a primary cell (PCell).

[0246] According to various embodiments of the present disclosure, in operation 1125, the UE 1101 may be configured to perform LTE V2X sidelink communication, and may select or reselect a suitable LTE cell and obtain the required system information including LTE V2X sidelink configuration information. The UE 1101 may perform LTE V2X sidelink communication based on the obtained LTE V2X sidelink configuration information.

[0247] According to various embodiments of the present disclosure, in operation 1125, the UE 1101 is configured to perform both LTE V2X sidelink communication and NR V2X sidelink communication, but may select or reselect a suitable LTE cell and obtain the system information including only the required LTE V2X sidelink configuration information. The UE 1101 may perform LTE V2X sidelink communication based on the obtained LTE V2X sidelink configuration information.

[0248] Specifically, in operation 1125, when it is indicated that there is SIBx described by a scheduling information list (SchedulingInfoList) in SIB1 (System Information Block Type 1) received from a cell (Scell or PCell), the UE 1101 in RRC inactive mode may acquire SIBx. Alternatively, when there is no valid SIBx stored, the UE 1101 may acquire SIBx. When the LTE eNB 1103 broadcasts SIBx, SIBx selectively includes s1-V2X-ConfigCommon. s1-V2X-ConfigCommon may include at least one of the following: v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, threshSS-TxPrioritization, anchorCarrierFreqList, offsetDFN, cbr-CommonTxConfigList, cbr-pssch-TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR. Additionally, SIBx may include side-link bearers of PC5 QoS profiles (side-link radio bearer (SLRB) configuration information). According to an embodiment, the side-link bearer configuration information of one or more PC5 QoS profiles may include mapping information of one SLRB and / or PDCP / RLC / LCH configuration information. Alternatively, the side-link bearer configuration information of one PC5 QoS profile may include mapping information of one or more SLRBs and / or PDCP / RLC / logical channel (LCH) configuration information. The PC5 QoS profile may be at least one of the following: packet filtering information (PFI), range, and / or required transmission rate (required data rate), or PC5 QoS parameters / characteristics of a PC5 5G QoS identifier (PQI) (see [Table 1]).

[0249] In operation 1130, the higher layer device may configure the AS device to receive NR V2X side-link communication packets. Additionally, the higher layer device may indicate to receive NR V2X side-link communication at a specific frequency.

[0250] According to various embodiments of the present disclosure, operation 1130 may be performed in operation 1125.

[0251] In operation 1135, the higher layer device may be configured to receive a PC5 QoS profile (PQI according to an embodiment) in an NR V2X sidelink communication packet and transmit its PC5 QoS profile to the AS device. When there is no indication in operation 1130 indicating reception of NR V2X sidelink communication at a specific frequency, an indication may be made in operation 1135.

[0252] In operation 1140, the AS device may determine whether sidelink bearer configuration information of the PC5 QoS profile received in operation 1130 exists in the SIBx received in operation 1125. According to an embodiment, the AS device may identify whether a sidelink bearer identifier or its sidelink bearer mapped to the PC5 QoS profile (e.g., PQI and / or range) is configured. According to an embodiment, this is because the LTE eNB may not include sidelink bearer configuration information of the PC5 QoS profile due to limitations on the SIBx size. The sidelink bearer configuration information of the PC5 QoS profile may be broadcast via the SIBx regardless of frequency, or may be broadcast separately for each frequency. When the sidelink bearer configuration information is broadcast for each frequency, it may be determined whether the sidelink bearer configuration information of the PC5 QoS profile in the frequency indicated by the above operation exists in the received SIBx.

[0253] In operation 1145, the AS device may determine whether the specific frequency indicated by the higher layer device in operation 1130 or operation 1135 is within coverage, or whether the specific frequency is included in the SIBx.

[0254] In operation 1150, the AS device may determine whether resource information for receiving NR V2X sidelink communication is included in a specific frequency. The resource information according to the present embodiment may refer to a commonly used reception resource pool (e.g., commRxPool).

[0255] When operations 1140, 1145, or 1150 are not satisfied, in operation 1155, a cell selection process or a cell reselection process may be performed. When a suitable NR cell 1104 is finally selected / reselected through the cell selection process or the cell reselection process, in operation 1160, the UE 1101 may enter the RRC idle mode.

[0256] When operation 1150 or operation 1145 is not satisfied, in operation 1155, UE 1101 may obtain only the system information broadcast by NR cell 1104 without performing selection / reselection of NR cell 1104. The system information may refer to the system information including the NR V2X sidelink communication configuration information. The system information may be the system information including the NR sidelink communication configuration information that satisfies the above operations. An embodiment of the present disclosure proposes a method by which UE 1101 camps on LTE cell 1103, obtains only the system information from NR cell 1104, and uses the information included in the system information without finally selecting / reslecting NR cell 1104. That is to say, UE 1101 may not finally perform inter-RAT cell selection / reselection.

[0257] In addition, UE 1101 may obtain only the system information including the NR V2X sidelink communication configuration information broadcast by a second LTE cell other than the first LTE cell on which the UE currently camps to perform NR sidelink communication without intra-RAT cell selection / reselection. For example, when there is a second LTE cell sharing the NR V2X sidelink communication configuration information and the LTE V2X sidelink communication configuration information at a frequency, UE 1101 may obtain the NR V2X sidelink communication configuration information only from the second LTE cell operating at the corresponding frequency. The corresponding frequency may be the frequency indicated in operation 1130 to perform NR V2X sidelink communication.

[0258] In operation 1165, UE 1101 may obtain the system information broadcast by the selected / reslected NR cell 1104. When NR cell 1104 performs broadcast periodically, UE 1101 may obtain the system information according to the corresponding period. When NR cell 1104 signals the system information according to the required type, the UE may request the corresponding system information from NR cell BS 1104 and obtain the system information. According to an embodiment, UE 1101 may send a request and obtain the system information through a preamble (msg1) or through an RRC system information request message (RRC SystemInfoRequest message, msg3) during the random access procedure with the LTE eNB. The system information may refer to the system information including the NR V2X sidelink communication configuration information that satisfies the above operations.

[0259] In operation 1170, the UE may receive NR V2X sidelink communication sent by another UE 1102 based on system information. According to an embodiment, sidelink control information and / or corresponding data thereto may be monitored in a reception resource pool (commRxPool) indicated by the system information. Alternatively, when operations 1140, 1145, or 1150 are not satisfied because a cell selection / reselection process has been performed but no suitable LTE cell or NR cell has been found, pre-configuration may be used to perform operation 1170. According to an embodiment, the UE 1101 may receive NR V2X sidelink communication sent by another UE 1102 through a reception resource pool included in SL-V2X-preconfiguration (e.g., preconfigComm in the SL-preconfiguration). Alternatively, when operations 1140, 1145, or 1150 are not satisfied, pre-configuration may be used to perform operation 1170 without operation 1155.

[0260] Figure 12 Examples of processes in a wireless communication system according to various embodiments of the present disclosure are shown: a process in which a UE switches from a Radio Resource Control (RRC) connected mode (RRC_CONNECTED) to an RRC inactive mode (RRC_IDLE) with an NR gNB connected to a 5GC; and a process in which a UE in the RRC inactive mode performs LTE V2X sidelink communication.

[0261] The UE 1201 according to an embodiment of the present disclosure may refer to a vehicle-mounted UE or a pedestrian UE. The UE 1201 may support V2X sidelink communication through one or more Radio Access Technologies (RATs). According to an embodiment, the UE may support only LTE V2X sidelink communication or only NR V2X sidelink communication, or may support both LTE V2X sidelink communication and NR V2X sidelink communication. The NR gNB according to an embodiment of the present disclosure may broadcast system information related to LTE V2X sidelink configuration information and / or system information related to NR V2X sidelink configuration information periodically or according to a required type.

[0262] Reference Figure 12 In operation 1210, the UE 1201 may, in an RRC connected mode (RRC_CONNECTED), send data to and receive data from an NR gNB 1203 connected to a 5GC.

[0263] When the UE 1201 does not send / receive data for a predetermined reason or within a predetermined time, in operation 1215, the NR gNB 1203 may send an RRC connection release message (RRCConnectionRelease message) including suspend configuration information (suspendConfig).

[0264] In operation 1220, the UE 1201 that receives the RRC connection release message may switch to the RRC inactive mode (RRC_INACTIVE).

[0265] In operation 1225, the UE 1201 in the RRC inactive mode may discover a suitable NR cell 1203 through a cell selection process or a cell reselection process and camp on the discovered cell to obtain system information. According to an embodiment, the system information may be one or more SIBy, including MIB1, SIB1, SIB2, SIB3, SIB4, SIB5, and LTE V2X sidelink configuration information defined / introduced for LTE V2X sidelink communication. The cell on which the UE camps may be referred to as a serving cell (SCell) or a primary cell (PCell).

[0266] According to various embodiments of the present disclosure, in operation 1225, the UE 1201 may be configured to perform NR V2X sidelink communication, and may select or reselect a suitable NR cell and obtain system information including the required NR V2X sidelink configuration information. The UE 1201 may perform NR V2X sidelink communication based on the obtained NR V2X sidelink configuration information.

[0267] According to various embodiments of the present disclosure, in operation 1225, when the UE 1201 is configured to perform both LTE V2X sidelink communication and NR V2X sidelink communication, the UE 1201 may select or reselect a suitable NR cell and obtain system information including only the required NR V2X sidelink configuration information. The UE 1201 may perform NR V2X sidelink communication based on the obtained NR V2X sidelink configuration information.

[0268] Specifically, in operation 1225, when it is indicated that there is SIBy described in the system information scheduling information list (si-SchedulingInfo) in SIB1 (System Information Block Type 1) received from a cell (Scell or PCell), the UE 1201 in RRC inactive mode can obtain SIBy. Alternatively, when there is no valid SIBy stored, the UE 1201 can obtain SIBy. When the NR gNB 1203 broadcasts SIBy, SIBy selectively includes s1-V2X-ConfigCommon. s1-V2X-ConfigCommon can include at least one of the following: v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, threshSS-TxPrioritization, anchorCarrierFreqList, offsetDFN, cbr-CommonTxConfigList, cbr-pssch-TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR.

[0269] In operation 1230, a higher layer device can configure the AS device to receive LTE V2X sidelink communication. Additionally, an indication of receiving LTE V2X sidelink communication in a specific frequency can be indicated.

[0270] According to various embodiments of the present disclosure, operation 1230 can be performed in operation 1225.

[0271] In operation 1235, the AS device can determine whether the specific frequency indicated by the higher layer device in operation 1230 is within the coverage area, or whether the specific frequency is included in SIBy.

[0272] In operation 1240, the AS device can determine whether the resource information for receiving LTE V2X sidelink communication is included in the specific frequency. The resource information according to this embodiment can refer to a receiving resource pool for regular use (e.g., commRxPool).

[0273] When operation 1235 or operation 1240 is not satisfied, in operation 1245, the UE may obtain the system information broadcast by the LTE eNB 1204. The system information may refer to the system information including the LTE sidelink communication configuration information that satisfies the above operations. According to an embodiment, the system information may be SIB21 or SIB26. When there is no neighboring NR cell that satisfies operation 1235 or operation 1240 based on the cell selection / reselection process, the UE 1201 may obtain the system information. An embodiment of the present disclosure proposes a method by which the UE camps on an NR cell, obtains the system information only from an LTE cell, and uses the information included in the system information, without finally selecting / reselecting an LTE cell. That is, since the UE 1201 does not finally perform inter-RAT cell selection / reselection, the RRC inactive mode may be maintained in operation 1246.

[0274] In addition, the UE 1201 may obtain only the system information including the LTE V2X sidelink communication configuration information broadcast by a second NR cell rather than the first NR cell on which the UE currently camps, so as to perform LTE sidelink communication without intra-RAT cell selection / reselection. For example, when there is a second NR cell that shares the NR V2X sidelink communication configuration information and the LTE V2X sidelink communication configuration information at one frequency, the UE 1201 may obtain the LTE V2X sidelink communication configuration information only from the second NR cell operating at the corresponding frequency. The corresponding frequency may be the frequency indicated in operation 1230 to perform LTE V2X sidelink communication.

[0275] In operation 1250, the UE 1201 may receive the LTE V2X sidelink communication sent by another UE 1202 based on the system information received in operation 1245. According to an embodiment, the sidelink control information and / or the corresponding data may be monitored in the receive resource pool (commRxPool) indicated by the system information. Alternatively, when operation 1235 or operation 1240 is not satisfied, operation 1245 is not performed, and pre-configuration may be used to perform operation 1250 while maintaining the RRC inactive mode in operation 1246. According to an embodiment, the UE 1201 may receive the LTE V2X sidelink communication sent by another UE 1202 through the receive resource pool (for example, preconfigComm in the SL-preconfiguration) included in the SL-V2X-preconfiguration. Alternatively, when operation 1235 or operation 1240 is not satisfied because the cell selection / reselection process is performed but no suitable LTE cell or NR cell is found, pre-configuration may be used to perform operation 1250 while maintaining the RRC inactive mode in operation 1246.

[0276] Figure 13 An example of the following processes of a wireless communication system according to various embodiments of the present disclosure is shown: a process in which a UE switches from the RRC connected mode (RRC_CONNECTED) to the RRC idle mode (RRC_IDLE) with an NR gNB connected to the 5GC, and a process in which a UE in the RRC idle mode performs LTE V2X sidelink communication.

[0277] The UE 1301 according to an embodiment of the present disclosure may refer to a vehicle-mounted UE or a pedestrian UE. The UE 1301 may support V2X sidelink communication through one or more radio access technologies (RATs). According to an embodiment, the UE may support only LTE V2X sidelink communication or only NR V2X sidelink communication, or may support both LTE V2X sidelink communication and NR V2X sidelink communication. The NR gNB according to an embodiment of the present disclosure may broadcast system information related to LTE V2X sidelink configuration information and / or system information related to NR V2X sidelink configuration information periodically or according to a required type.

[0278] Refer to Figure 13 , in operation 1310, the UE 1301 may send data to and receive data from the NR gNB 1303 connected to the 5GC in the RRC connected mode (RRC_CONNECTED).

[0279] When there is no data transmission / reception for a predetermined reason or within a predetermined time, in operation 1315, the UE 1301 may send an RRC release message (RRCRelease message) that does not include suspend configuration information (suspendConfig).

[0280] In operation 1320, the UE 1301 that has received the RRC connection release message may switch to the RRC idle mode (RRC_IDLE).

[0281] In operation 1325, the UE 1301 in the RRC idle mode may discover a suitable NR cell 1303 through a cell selection process or a cell reselection process, and camp on the discovered cell to obtain system information. According to an embodiment, the system information may be one or more SIBy, including MIB1, SIB1, SIB2, SIB3, SIB4, SIB5, and LTE V2X sidelink configuration information defined / introduced for LTE V2X sidelink communication. The cell on which the UE camps may be referred to as a serving cell (SCell) or a primary cell (PCell).

[0282] Specifically, in operation 1325, when it is indicated that there is SIBy described in the system information scheduling information list (si-SchedulingInfo) in SIB1 (System Information Block Type 1) received from a cell (Scell or PCell), the UE 1301 in RRC inactive mode can acquire SIBy. Alternatively, when a valid SIBy is not stored, the UE 1301 can acquire SIBy. When the NR gNB 1303 broadcasts SIBy, SIBy selectively includes s1-V2X-ConfigCommon. s1-V2X-ConfigCommon can include at least one of the following: v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, threshSS-TxPrioritization, anchorCarrierFreqList, offsetDFN, cbr-CommonTxConfigList, cbr-pssch-TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR.

[0283] In operation 1330, the higher layer device can configure the AS device to receive LTE V2X sidelink communication. Additionally, the higher layer device can indicate to the AS device to receive LTE V2X sidelink communication at a specific frequency.

[0284] According to various embodiments of the present disclosure, in operation 1335, the higher layer device can configure the AS device to receive NR V2X sidelink communication. The higher layer device can indicate to the AS device to perform NR V2X sidelink communication at a specific frequency.

[0285] According to various embodiments of the present disclosure, when the NR V2X sidelink configuration information required by the UE 1301 in RRC idle mode exists in the system information acquired in operation 1325, the UE 1301 can perform NR V2X sidelink communication based on the NR V2X sidelink configuration information.

[0286] In operation 1335, the AS device may determine whether the specific frequency indicated by the higher-layer device in operation 1330 is within the coverage area, or whether the specific frequency is included in the SIBy.

[0287] In operation 1340, the AS device may determine whether the resource information for receiving LTE V2X sidelink communication is included in the specific frequency. The resource information according to the present embodiment may refer to a conventionally used reception resource pool (e.g., commRxPool).

[0288] When operation 1335 or operation 1340 is not satisfied, in operation 1345, a cell selection process or a cell reselection process may be executed. When a suitable LTE cell 1304 is finally selected / reselected through the cell selection process or the cell reselection process, in operation 1350, the UE 1301 may enter the RRC idle mode.

[0289] In operation 1355, the UE 1301 may obtain the system information broadcast by the selected / reselected LTE eNB 1304. The system information may refer to the system information including the LTE V2X sidelink communication configuration information that satisfies the above operations.

[0290] In operation 1360, the UE 1301 may receive an LTE V2X sidelink communication packet sent by another UE 1302 based on the system information received in operation 1355. According to an embodiment, the sidelink control information and / or the corresponding data may be monitored in the reception resource pool (commRxPool) indicated by the system information. Alternatively, when operation 1335 or operation 1340 is not satisfied because a suitable LTE cell or NR cell is not found due to the execution of the cell selection / reselection process, operation 1360 may be performed using pre-configuration. According to an embodiment, the UE 1301 may receive an NR V2X sidelink communication sent by another UE 1302 through the reception resource pool included in the SL-V2X-preconfiguration (e.g., preconfigComm in the SL-preconfiguration). Alternatively, when operation 1340 is not satisfied because a suitable LTE cell or NR cell is not found due to the execution of the cell selection / reselection process, operation 1360 may be performed using pre-configuration.

[0291] In the following, Figures 14 to 17 Embodiments for managing sidelink bearers to support V2X communication in a next-generation mobile communication system are shown.

[0292] Figure 14An example of a process in a wireless communication system according to various embodiments of the present disclosure is shown: a process of managing an established SLRB when a UE supporting NR V2X sidelink communication establishes a sidelink bearer (sidelink radio bearer (SLRB)) in the RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE) and switches to the RRC connected mode (RRC_CONNECTED) with an LTE eNB during NR V2X sidelink communication.

[0293] The UE 1401 according to an embodiment of the present disclosure may refer to a vehicle-mounted UE or a pedestrian UE. The UE 1401 may support LTE V2X sidelink communication and / or NR V2X sidelink communication. The LTE eNB 1403 according to an embodiment of the present disclosure may periodically broadcast or signal system information related to LTE V2X sidelink configuration information or system information related to NR V2X sidelink configuration information.

[0294] Reference Figure 14 Referring to, in operation 1405, the UE 1401 capable of performing NR V2X sidelink communication may pre-configure SLRB configuration information of a PC5 QoS profile from the core network. At this time, the SLRB configuration information may be pre-configured for all available PC5 QoS profiles. According to an embodiment, the pre-configured SLRB configuration information may include, for example, mappings of PC5 QoS profiles, PDCP / RLC / LCH, PFI, PQI to the SLRB, etc.

[0295] In operation 1410, the UE 1401 does not establish an RRC connection with the LTE eNB 1403, and thus may be in the RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE).

[0296] In operation 1415, the UE 1401 in the RRC idle mode or RRC inactive mode may discover a suitable LTE cell 1403 through a cell selection process or a cell reselection process and camp on the discovered cell to obtain system information. According to an embodiment, the system information may be one or more SIBx, including MIB1, SIB1, SIB2, SIB3, SIB4, SIB5, SIB21, SIB26, and / or NR V2X sidelink configuration information defined / introduced for NR V2X sidelink communication. The cell on which the UE camps may be referred to as a serving cell (SCell) or a primary cell (PCell).

[0297] Specifically, in operation 1415, when it is indicated that there is SIBx described by a scheduling information list (SchedulingInfoList) in SIB1 (System Information Block Type 1) received from a cell (Scell or PCell), UE 1401 in RRC idle mode or RRC inactive mode can obtain SIBx. Alternatively, when there is no valid SIBx stored, UE 1401 can obtain SIBx. When LTE eNB 1403 broadcasts SIBx, SIBx selectively includes s1-V2X-ConfigCommon. sl-V2X-ConfigCommon can include at least one of the following: v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, threshSS-TxPrioritization, anchorCarrierFreqList, offsetDFN, cbr-CommonTxConfigList, cbr-pssch-TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR. Additionally, SIBx can include sidelink bearer (sidelink radio bearer (SLRB)) configuration information of a PC5 QoS profile. According to an embodiment, the sidelink bearer configuration information of one or more PC5 QoS profiles can include mapping information of one SLRB and / or PDCP / RLC / LCH configuration information. Alternatively, the sidelink bearer configuration information of one PC5 QoS profile can include mapping information of one or more SLRBs and / or PDCP / RLC / logical channel (LCH) configuration information. The PC5 QoS profile can be at least one of the following: packet filtering information (PFI), range and / or required transmission rate (required data rate), or PC5 QoS parameters / characteristics of a PC5 5G QoS identifier (PQI) (see [Table 1]).

[0298] In operation 1420, a packet for transmitting NR V2X sidelink communication or the arrival of a packet for transmitting NR V2X sidelink communication may be generated and configured to perform NR V2X sidelink communication. Additionally, an indication to perform communication in a specific frequency may be made.

[0299] In operation 1425, a higher layer device may configure a PC5 QoS profile (PQI according to an embodiment) and transmit the packet and its PC5 QoS profile to an AS device.

[0300] In operation 1430, the AS device may determine whether the sidelink bearer configuration information of the PC5 QoS profile in the packet received in operation 1425 exists in the SIBx received in operation 1415.

[0301] When the sidelink bearer configuration information of the PC5 QoS profile in the packet received in operation 1425 exists in the SIBx received in operation 1415, in operation 1435, the AS device may establish an SLRB. When the information is not included in the SIBx, the AS device may establish an SLRB based on the information preconfigured in operation 1405.

[0302] In operation 1440, UE 1401 may perform NR V2X sidelink communication with another UE 1402 through the SLRB established in operation 1435. The NR V2X sidelink communication may be performed through broadcast, multicast, or unicast.

[0303] In operation 1445, a UE 1401 in RRC idle mode may send an RRC connection request message (RRCConnectionRequest message) to an LTE eNB to perform an RRC connection establishment procedure with the LTE eNB 1403. In operation 1450, the LTE eNB may send an RRC connection setup message (RRCConnectionSetup message) to the UE in RRC idle mode. The UE 1401 that receives the RRC connection setup message may apply the configuration information included in the message and then transition to RRC connected mode in operation 1451. The UE 1401 may continuously perform NR V2X sidelink communication with another UE 1402 via the SLRB established in operation 1435 based on the system information obtained in operation 1415. In operation 1455, the UE 1401 may send an RRC connection setup complete message (RRCConnectionSetupComplete message) to the LTE eNB. The RRC connection setup complete message may include QoS information related to the SLRB established and used in RRC idle mode. According to an embodiment, the RRC connection setup complete message may include at least one of the following information related to the SLRB established and used in RRC idle mode.

[0304] - PC5 QoS profile

[0305] According to an embodiment, one or more PC5 QoS flow identifiers (PFIs) and / or one or more PC5 5QIs (PQIs)

[0306] - One or more destination information

[0307] - Broadcast type based on each destination (e.g., whether the SLRB established and used in RRC idle mode is for unicast, broadcast, or multicast)

[0308] - Broadcast type based on each destination (e.g., whether the SLRB established and used in RRC idle mode is for unicast, broadcast, or multicast)

[0309] - Indicator or SLRB identifier indicating whether to continuously use the SLRB established and used in RRC idle mode

[0310] - SLRB mapping information of the PC5 QoS flow (e.g., mapping of PFI to SLRB and mapping of QoS profile to SLRB)

[0311] In operation 1445, a UE 1401 in RRC inactive mode may send an RRC connection resume request message (RRCConnectionResumeRequest message) to an LTE eNB to perform an RRC connection resume procedure with the LTE eNB 1403. In operation 1450, the LTE eNB may send an RRC connection resume message (RRCConnectionResume message) to the UE in RRC inactive mode. The UE 1401 that receives the RRC connection resume message may apply the configuration information included in the message and then transition to RRC connected mode in operation 1451. The UE 1401 may continuously perform NR V2X sidelink communication with another UE 1402 through the SLRB established in operation 1435 based on the system information obtained in operation 1415. In operation 1455, the UE1401 may send an RRC connection resume complete message (RRCConnectionResumeComplete message) to the LTE eNB. The RRC connection resume complete message may include QoS information related to the SLRB established and used in RRC inactive mode. According to an embodiment, at least one of the following information related to the SLRB established and used in RRC inactive mode may be included.

[0312] - PC5 QoS profile

[0313] According to an embodiment, one or more PC5 QoS flow identifiers (PFIs) and / or one or more PC5 5QIs (PQIs)

[0314] - One or more destination information items

[0315] - Broadcast type based on each destination (e.g., the SLRB established and used in RRC idle mode is for unicast, broadcast, or multicast)

[0316] - An indicator or SLRB identifier indicating whether to continuously use the SLRB established and used in RRC idle mode

[0317] - SLRB mapping information of PC5 QoS flows (e.g., mapping of PFI to SLRB and mapping of QoS profile to SLRB)

[0318] In operation 1460, the UE 1401 in the RRC connected mode may send a Sidelink UE Information message to the LTE eNB. Operation 1460 may be performed when the QoS information is not included in the RRC connection establishment complete message or the RRC connection resume complete message in operation 1455. The Sidelink UE message may include QoS information related to the SLRB established and used in the RRC idle mode or the RRC inactive mode. According to an embodiment, at least one of the following information related to the SLRB established and used in the RRC idle mode or the RRC inactive mode may be included.

[0319] - PC5 QoS profile

[0320] According to an embodiment, one or more PC5 QoS flow identifiers (PFIs) and / or one or more PC5 5QIs (PQIs)

[0321] - One or more destination information

[0322] - Broadcast type based on each destination (e.g., whether the SLRB established and used in the RRC idle mode is for unicast, broadcast, or multicast)

[0323] - An indicator or SLRB identifier indicating whether the SLRB established and used in the RRC idle mode is continuously used

[0324] - SLRB mapping information of the PC5 QoS flow (e.g., mapping of PFI to SLRB and mapping of QoS profile to SLRB)

[0325] In operation 1465, the LTE eNB may insert at least one of the following information into the RRC connection reconfiguration message and send the RRC connection reconfiguration message to the UE in the RRC connected mode.

[0326] - SLRB configuration information related to the QoS information included in operation 1455 or operation 1460

[0327] - An indicator (indication) indicating whether the SLRB configuration information established and used in the RRC idle mode or the RRC inactive mode is continuously used

[0328] - Resource mode (mode 3 or mode 4)

[0329] - Resource pool configuration information according to the resource mode

[0330] In operation 1467, the UE 1401 may determine whether to continuously use the SLRB established and used in the RRC idle mode or the RRC inactive mode based on the message received in operation 1465. According to an embodiment, when an indicator indicating continuous use is inserted into the RRC Connection Reconfiguration message, or when information identical to the SLRB established and used in the RRC idle mode or the RRC inactive mode is included, the UE 1401 in the RRC connected mode may perform NR V2X communication with another UE 1402 by continuously using the regularly used SLRB. When the SLRB configuration information not established in the RRC idle mode or the RRC inactive mode is included, the UE 1401 in the RRC connected mode may newly establish an SLRB and perform NR V2X communication with another UE 1402. When the UE 1401 newly establishes an SLRB and performs unicast communication with another UE 1402, the UE 1401 may send a PC5 RRC message including the new SLRB configuration information to the other UE 1402.

[0331] In operation 1470, the UE 1401 may send an RRC Connection Reconfiguration Complete message to the LTE eNB, and in operation 1475, perform NR V2X sidelink communication (send NR V2X sidelink packets) with another UE 1402.

[0332] When the UE that transmits and receives data in the RRC connected mode has no data to transmit / receive for a predetermined reason or within a predetermined time, in operation 1480, the LTE eNB may switch the UE to the RRC idle mode (RRC_IDEL) or the RRC inactive mode (RRC_INACTIVE) by sending an RRC Connection Release message (RRCConnectionRelease message). This message may include an indicator or information element indicating whether to continuously use or release the SLRB used in the RRC connected mode. The UE 1401 in the RRC idle mode or the RRC inactive mode may determine whether to continuously use or release the SLRB used with another UE 1402 based on the information included in the RRC Connection Release message, or determine whether to newly establish an SLRB based on the system information to perform NR V2X sidelink communication with another UE 1402. When the UE 1401 needs to change or release the SLRB regularly used with another UE 1402 or newly establish an SLRB, if the UE is performing unicast communication with another UE 1402, the UE 1401 may send a PC5 RRC message including the new SLRB configuration information to the other UE 1402.

[0333] In operation 1451, the UE 1401 may transition from the RRC idle mode or the RRC inactive mode to the RRC connected mode and then release all SLRBs established and used in the RRC idle mode or the RRC inactive mode.

[0334] Figure 15 An example of a process in a wireless communication system according to various embodiments of the present disclosure is shown: a process of managing an established side link radio bearer (SLRB) when a UE supporting NR V2X side link communication establishes a side link bearer (SLRB) in the RRC idle mode (RRC_IDLE) or the RRC inactive mode (RRC_INACTIVE) and switches to the RRC connected mode (RRC_CONNECTED) with an NR gNB during NR V2X side link communication.

[0335] The UE 1501 according to an embodiment of the present disclosure may refer to a vehicle-mounted UE or a pedestrian UE. The UE 1501 may support LTE V2X side link communication and / or NR V2X side link communication. The NR gNB according to an embodiment of the present disclosure may signal system information related to LTE V2X side link configuration information or system information related to NR V2X side link configuration information.

[0336] Reference Figure 15 , in operation 1505, the UE 1501 capable of performing NR V2X side link communication may pre-configure SLRB configuration information of a PC5 QoS profile from the core network. At this time, the SLRB configuration information may be pre-configured for all available PC5 QoS profiles. According to an embodiment, the pre-configured SLRB configuration information may include, for example, a mapping of the PC5 QoS profile, PDCP / RLC / LCH, PFI, and PQI to the SLRB, etc.

[0337] In operation 1510, the UE 1501 does not establish an RRC connection with the NR gNB 1503 and thus may be in the RRC idle mode (RRC_IDLE) or the RRC inactive mode (RRC_INACTIVE).

[0338] In operation 1515, a UE 1501 in RRC idle mode or RRC inactive mode can discover a suitable NR cell 1503 through a cell selection process or a cell reselection process, and camp on the discovered cell to obtain system information. According to an embodiment, the system information can be one or more SIBx, including MIB1, SIB1, SIB2, SIB3, SIB4, SIB5, and / or NR V2X sidelink configuration information defined / introduced for NR V2X sidelink communication. The cell on which the UE camps can be referred to as a serving cell (SCell) or a primary cell (PCell).

[0339] Specifically, in operation 1515, when it is indicated that there is a SIBx described by a scheduling information list (SchedulingInfoList) in SIB1 (System Information Block Type 1) received from a cell (Scell or PCell), the UE 1501 in RRC idle mode or RRC inactive mode can obtain the SIBx. Alternatively, when a valid SIBx is not stored, the UE 1501 can obtain the SIBx. When the NR gNB 1503 broadcasts the SIBx, the SIBx selectively includes s1-V2X-ConfigCommon. The sl-V2X-ConfigCommon can include at least one of the following: v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, threshSS-TxPrioritization, anchorCarrierFreqList, offsetDFN, cbr-CommonTxConfigList, cbr-pssch-TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR. Additionally, the SIBx can include sidelink bearer (sidelink radio bearer (SLRB)) configuration information of the PC5 QoS profile. According to an embodiment, the sidelink bearer configuration information of one or more PC5 QoS profiles can include mapping information of one SLRB and / or PDCP / RLC / LCH configuration information. Alternatively, the sidelink bearer configuration information of one PC5 QoS profile can include mapping information of one or more SLRBs and / or PDCP / RLC / LCH configuration information. The PC5 QoS profile can be at least one of the following: packet filtering information (PFI), range and / or required transmission rate (required data rate), or PC5 QoS parameters / characteristics of the PC5 5G QoS identifier (PQI) (see [Table 1]).

[0340] In operation 1520, a packet for transmitting NR V2X sidelink communication or the arrival of a packet for transmitting NR V2X sidelink communication may be generated and configured to perform NR V2X sidelink communication. Additionally, an indication to perform communication in a specific frequency may be made.

[0341] In operation 1525, the higher layer device may configure a PC5 QoS profile (PQI according to the embodiment) and transmit the packet and its PC5 QoS profile to the AS device.

[0342] In operation 1530, the AS device may determine whether the sidelink bearer configuration information of the PC5 QoS profile in the packet received in operation 1525 exists in the SIBx received in operation 1515.

[0343] In operation 1535, when the sidelink bearer configuration information of the PC5 QoS profile in the packet received in operation 1525 exists in the SIBx received in operation 1515, the AS device may establish an SLRB. When this information is not included in the SIBx, the SLRB may be established based on the information pre-configured in operation 1505.

[0344] In operation 1540, UE 1501 may continuously perform NR V2X sidelink communication with another UE1502 through the SLRB established in operation 1535. The NR V2X sidelink communication may be performed through broadcast, multicast, or unicast.

[0345] In operation 1545, the UE 1501 in RRC idle mode may send an RRC connection establishment request message (RRCSetupRequest message) to the NR gNB to perform an RRC connection establishment procedure with the NR gNB 1503. In operation 1550, the NRgNB may send an RRC connection establishment message (RRCSetup message) to the UE in RRC idle mode. The UE 1501 that receives the RRC connection establishment message may apply the configuration information included in the message and then switch to the RRC connected mode in operation 1551. The UE 1501 may continuously perform NR V2X sidelink communication with another UE1502 through the SLRB established in operation 1535 based on the system information obtained in operation 1515. In operation 1555, the UE 1501 may send an RRC connection establishment complete message (RRCSetupComplete message) to the NR gNB. The RRC connection establishment complete message may include QoS information related to the SLRB established and used in the RRC idle mode. According to the embodiment, the RRC connection establishment complete message may include at least one of the following information related to the SLRB established and used in the RRC idle mode.

[0346] - PC5 QoS profile

[0347] According to an embodiment, one or more PC5 QoS flow identifiers (PFIs) and / or one or more PC5 5QIs (PQIs)

[0348] - One or more destination information

[0349] - Broadcast type based on each destination (e.g., whether the SLRB established and used in RRC idle mode is for unicast, broadcast, or multicast)

[0350] - Broadcast type based on each destination (e.g., whether the SLRB established and used in RRC idle mode is for unicast, broadcast, or multicast)

[0351] - Indicator or SLRB identifier indicating whether to continuously use the SLRB established and used in RRC idle mode

[0352] - SLRB mapping information of PC5 QoS flow (e.g., mapping of PFI to SLRB and mapping of QoS profile to SLRB)

[0353] In operation 1545, the UE 1501 in RRC inactive mode may send an RRC resume request message (RRCResumeRequest message) to the NR gNB to perform an RRC connection resume procedure with the NR gNB 1503. In operation 1550, the NR gNB may send an RRC resume message (RRCResume message) to the UE in RRC inactive mode. The UE 1501 that receives the RRC resume message may apply the configuration information included in the message and then transition to RRC connected mode in operation 1551. The UE 1501 may continuously perform NR V2X sidelink communication with another UE 1502 through the SLRB established in operation 1535 based on the system information obtained in operation 1515. In operation 1555, the UE 1501 may send an RRC resume complete message (RRCResumeComplete message) to the NR gNB. The RRC resume complete message may include QoS information related to the SLRB established and used in RRC inactive mode. According to an embodiment, at least one of the following information related to the SLRB established and used in RRC inactive mode may be included.

[0354] - PC5 QoS profile

[0355] According to an embodiment, one or more PC5 QoS flow identifiers (PFIs) and / or one or more PC5 5QIs (PQIs)

[0356] - One or more destination information

[0357] - Broadcast type based on each destination (e.g., whether the SLRB established and used in RRC idle mode is for unicast, broadcast, or multicast)

[0358] - An indicator or SLRB identifier indicating whether the SLRB established and used in RRC idle mode is continuously used

[0359] - Mapping information of PC5 QoS flows (e.g., mapping of PFI to SLRB and mapping of QoS profile to SLRB)

[0360] In operation 1560, the UE 1501 in RRC connected mode may send a Sidelink UE Information message to the NR gNB. Operation 1560 may be performed when the QoS information is not included in the RRC setup complete message or the RRC resume complete message in operation 1555. The Sidelink UE message may include QoS information related to the SLRB established and used in RRC idle mode or RRC inactive mode. According to an embodiment, at least one of the following information related to the SLRB established and used in RRC idle mode or RRC inactive mode may be included.

[0361] - PC5 QoS profile

[0362] According to an embodiment, one or more PC5 QoS flow identifiers (PFIs) and / or one or more PC5 5QIs (PQIs)

[0363] - One or more destination information

[0364] - Broadcast type based on each destination (e.g., whether the SLRB established and used in RRC idle mode is for unicast, broadcast, or multicast)

[0365] - An indicator or SLRB identifier indicating whether the SLRB established and used in RRC idle mode is continuously used

[0366] - SLRB mapping information of PC5 QoS flows (e.g., mapping of PFI to SLRB and mapping of QoS profile to SLRB)

[0367] In operation 1565, the NR gNB may insert at least one of the following information into the RRC Reconfiguration message and send the RRC Reconfiguration message to the UE in RRC connected mode.

[0368] - SLRB configuration information related to the QoS information included in operation 1555 or operation 1560

[0369] - An indicator (indication) indicating whether to continuously use the SLRB configuration information established and used in RRC idle mode or RRC inactive mode

[0370] - Resource mode (mode 1 or mode 2)

[0371] - Resource pool configuration information according to the resource mode

[0372] In operation 1567, UE 1501 may determine whether to continuously use the SLRB established and used in RRC idle mode or RRC inactive mode based on the message received in operation 1565. According to an embodiment, when the indicator indicating continuous use is inserted into the RRC Reconfiguration message, or when the information including the same SLRB established and used in RRC idle mode or RRC inactive mode is included, the UE 1501 in RRC connected mode may perform NR V2X communication with another UE 1502 by continuously using the commonly used SLRB. When the SLRB configuration information not established in RRC idle mode or RRC inactive mode is included, the UE 1501 in RRC connected mode may newly establish an SLRB and perform NR V2X communication with another UE 1502. When UE 1501 newly establishes an SLRB and performs unicast communication with another UE 1502, UE 1501 may send a PC5 RRC message including the new SLRB configuration information to another UE 1502.

[0373] In operation 1570, UE 1501 may send an RRC Reconfiguration Complete message to the NR gNB, and in operation 1575, perform NR V2X sidelink communication (send NR V2X sidelink packets) with another UE 1502.

[0374] When a UE that sends and receives data in the UE connected mode has no data to send / receive for a predetermined reason or within a predetermined time, in operation 1580, the NR gNB may switch the UE to the RRC idle mode (RRC_IDEL) or the RRC inactive mode (RRC_INACTIVE) by sending an RRC release message (RRCRelease message). This message may include an indicator or information element indicating whether to continuously use or release the SLRB used in the RRC connected mode. The UE 1501 in the RRC idle mode or the RRC inactive mode may determine whether to continuously use or release the SLRB used with another UE 1502 based on the information included in the RRC connection release message, or determine whether to newly establish an SLRB to perform NR V2X sidelink communication with another UE 1502 based on the system information. When the UE 1501 needs to change or release the SLRB conventionally used with another UE 1502 or newly establish an SLRB, if the UE is performing unicast communication with another UE 1502, the UE 1501 may send a PC5 RRC message including the new SLRB configuration information to the other UE 1502.

[0375] In operation 1551, the UE 1501 may transition from the RRC idle mode or the RRC inactive mode to the RRC connected mode and then release all SLRBs established and used in the RRC idle mode or the RRC inactive mode.

[0376] Figure 16 An example of a process in a wireless communication system according to various embodiments of the present disclosure is shown: a process of managing an established sidelink radio bearer (SLRB) when a UE supporting NR V2X sidelink communication establishes a sidelink bearer (SLRB) in the RRC idle mode (RRC_IDLE) or the RRC inactive mode (RRC_INACTIVE) and switches to the RRC connected mode (RRC_CONNECTED) with an LTE eNB during NR V2X sidelink communication.

[0377] The UE 1601 according to an embodiment of the present disclosure may refer to a vehicle-mounted UE or a pedestrian UE. The UE 1601 may support LTEV2X sidelink communication and / or NR V2X sidelink communication. The LTE eNB according to an embodiment of the present disclosure may periodically broadcast or signal system information related to LTE V2X sidelink configuration information or system information related to NR V2X sidelink configuration information.

[0378] Reference Figure 16, in operation 1605, a UE 1601 capable of performing NR V2X sidelink communication may pre-configure SLRB configuration information of a PC5 QoS profile from the core network. At this time, the SLRB configuration information may be pre-configured for all available PC5 QoS profiles. According to an embodiment, the pre-configured SLRB configuration information may include, for example, the mapping of a PC5 QoS profile, PDCP / RLC / LCH, PFI, PQI to an SLRB, etc.

[0379] In operation 1610, the UE 1601 does not establish an RRC connection with the LTE eNB 1603, and thus may be in the RRC idle mode (RRC_IDLE) or the RRC inactive mode (RRC_INACTIVE).

[0380] In operation 1615, the UE 1601 in the RRC idle mode or the RRC inactive mode may discover a suitable LTE cell 1603 through a cell selection process or a cell reselection process, and camp on the discovered cell to obtain system information. According to an embodiment, the system information may be one or more SIBx, including MIB1, SIB1, SIB2, SIB3, SIB4, SIB5, SIB21, SIB26, and / or NR V2X sidelink configuration information defined / introduced for NR V2X sidelink communication. The cell on which the UE camps may be referred to as a serving cell (SCell) or a primary cell (PCell).

[0381] Specifically, in operation 1615, when it is indicated that there is SIBx described by a scheduling information list (SchedulingInfoList) in SIB1 (System Information Block Type 1) received from a cell (Scell or PCell), the UE 1601 in RRC idle mode or RRC inactive mode can obtain SIBx. Alternatively, when there is no valid SIBx stored, the UE 1601 can obtain SIBx. When the LTE eNB 1603 broadcasts SIBx, SIBx selectively includes s1-V2X-ConfigCommon. s1-V2X-ConfigCommon can include at least one of the following: v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, threshSS-TxPrioritization, anchorCarrierFreqList, offsetDFN, cbr-CommonTxConfigList, cbr-pssch-TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR. Additionally, SIBx can include sidelink bearer (sidelink radio bearer (SLRB)) configuration information of a PC5 QoS profile. According to an embodiment, the sidelink bearer configuration information of one or more PC5 QoS profiles can include mapping information of one SLRB and / or PDCP / RLC / LCH configuration information. Alternatively, the sidelink bearer configuration information of one PC5 QoS profile can include mapping information of one or more SLRBs and / or PDCP / RLC / LCH configuration information. The PC5 QoS profile can be at least one of the following: packet filtering information (PFI), range and / or required transmission rate (required data rate), or PC5 QoS parameters / characteristics of a PC5 5G QoS identifier (PQI) (see [Table 1]).

[0382] In operation 1620, a higher layer device can configure an AS device to receive NR V2X sidelink communication packets. An indication can be made to receive the communication at a specific frequency.

[0383] In operation 1625, the higher layer device may configure the PC5 QoS profile (PQI according to the embodiment) in the packets to be received and transmit the configured PC5 QoS profile to the AS device. When there is no indication in operation 1620 indicating the reception of NR V2X sidelink communication packets in a specific frequency, such an indication may be made in operation 1625.

[0384] In operation 1630, the AS device may determine whether the sidelink bearer configuration information of the PC5 QoS profile in the packets received in operation 1625 exists in the SIBx received in operation 1615.

[0385] When the sidelink bearer configuration information of the PC5 QoS profile in the packets to be received exists in the SIBx received in operation 1615, in operation 1635, the AS device may establish an SLRB. When the information is not included in the SIBx, the SLRB may be established based on the information preconfigured in operation 1605.

[0386] In operation 1640, UE 1601 may perform NR V2X sidelink communication with another UE 1602 through the SLRB established in operation 1635. The NR V2X sidelink communication may be performed through broadcast, multicast, or unicast.

[0387] In operation 1645, the UE 1601 in RRC idle mode may send an RRC connection request message (RRCConnectionRequest message) to the LTE eNB to perform an RRC connection establishment procedure with the LTE eNB 1603. In operation 1650, the LTE eNB may send an RRC connection setup message (RRCConnectionSetup message) to the UE in RRC idle mode. The UE 1601 that receives the RRC connection setup message may apply the configuration information included in the message and then switch to the RRC connected mode in operation 1651. UE 1601 may continuously perform NR V2X sidelink communication with another UE 1602 through the SLRB established in operation 1635 based on the system information obtained in operation 1615. In operation 1655, UE 1601 may send an RRC connection setup complete message (RRCConnectionSetupComplete message) to the LTE eNB. The RRC connection setup complete message may include QoS information related to the SLRB established and used in RRC idle mode. According to the embodiment, the RRC connection setup complete message may include at least one of the following information related to the SLRB established and used in RRC idle mode.

[0388] - PC5 QoS Profile

[0389] According to an embodiment, one or more PC5 QoS flow identifiers (PFIs) and / or one or more PC5 5QIs (PQIs)

[0390] - One or more destination information

[0391] - Broadcast type based on each destination (e.g., whether the SLRB established and used in the RRC idle mode is for unicast, broadcast, or multicast)

[0392] - Broadcast type based on each destination (e.g., whether the SLRB established and used in the RRC idle mode is for unicast, broadcast, or multicast)

[0393] - An indicator or SLRB identifier indicating whether to continuously use the SLRB established and used in the RRC idle mode

[0394] - SLRB mapping information of the PC5 QoS flow (e.g., mapping of PFI to SLRB and mapping of QoS profile to SLRB)

[0395] In operation 1645, the UE 1601 in the RRC inactive mode may send an RRC connection resume request message (RRCConnectionResumeRequest message) to the LTE eNB to perform an RRC connection resume procedure (RRC connection resume procedure) with the LTE eNB 1603. In operation 1650, the LTE eNB may send an RRC connection resume message (RRCConnectionResume message) to the UE in the RRC inactive mode. The UE 1601 that receives the RRC connection resume message may apply the configuration information included in the message and then switch to the RRC connected mode in operation 1651. The UE 1601 may perform NR V2X sidelink communication with another UE 1602 through the SLRB established in operation 1635 based on the system information obtained in operation 1615. In operation 1655, the UE 1601 may send an RRC connection resume complete message (RRCConnectionResumeComplete message) to the LTE eNB. The RRC connection resume complete message may include QoS information related to the SLRB established and used in the RRC inactive mode. According to an embodiment, at least one of the following information related to the SLRB established and used in the RRC inactive mode may be included.

[0396] - PC5 QoS Profile

[0397] According to an embodiment, one or more PC5 QoS flow identifiers (PFIs) and / or one or more PC5 5QIs (PQIs)

[0398] - One or more destination information

[0399] - Broadcast type based on each destination (e.g., whether the SLRB established and used in RRC idle mode is for unicast, broadcast, or multicast)

[0400] - An indicator or SLRB identifier indicating whether the SLRB established and used in RRC idle mode is continuously used

[0401] - SLRB mapping information of the PC5 QoS flow (e.g., mapping of PFI to SLRB and mapping of QoS profile to SLRB)

[0402] In operation 1660, the UE 1601 in RRC connected mode may send a Sidelink UE Information message to the LTE eNB. Operation 1660 may be performed when the QoS information is not included in the RRC connection establishment complete message or the RRC connection resume complete message in operation 1655. The Sidelink UE message may include QoS information related to the SLRB established and used in RRC idle mode or RRC inactive mode. According to an embodiment, at least one of the following information related to the SLRB established and used in RRC idle mode or RRC inactive mode may be included.

[0403] - PC5 QoS profile

[0404] According to an embodiment, one or more PC5 QoS flow identifiers (PFIs) and / or one or more PC5 5QIs (PQIs)

[0405] - One or more destination information

[0406] - Broadcast type based on each destination (e.g., whether the SLRB established and used in RRC idle mode is for unicast, broadcast, or multicast)

[0407] - An indicator or SLRB identifier indicating whether the SLRB established and used in RRC idle mode is continuously used

[0408] - SLRB mapping information of the PC5 QoS flow (e.g., mapping of PFI to SLRB and mapping of QoS profile to SLRB)

[0409] In operation 1665, the LTE eNB may insert at least one of the following information into the RRC connection reconfiguration message and send the RRC connection reconfiguration message to the UE in the RRC connected mode.

[0410] - SLRB configuration information related to the QoS information included in operation 1655 or operation 1660

[0411] - An indicator (indication) indicating whether to continuously use the SLRB configuration information established and used in the RRC idle mode or the RRC inactive mode

[0412] - Resource mode (mode 3 or mode 4)

[0413] - Resource pool configuration information according to the resource mode

[0414] In operation 1667, the UE 1601 may determine whether to continuously use the SLRB established and used in the RRC idle mode or the RRC inactive mode based on the message received in operation 1665. According to an embodiment, when an indicator indicating continuous use is inserted into the RRC connection reconfiguration (RRCConnectionReconfiguration) message, or when information indicating that the SLRB established and used in the RRC idle mode or the RRC inactive mode is the same is included, the UE 1601 in the RRC connected mode may perform NR V2X communication with another UE 1602 by continuously using the regularly used SLRB. When the SLRB configuration information not established in the RRC idle mode or the RRC inactive mode is included, the UE 1601 in the RRC connected mode may newly establish an SLRB and perform NR V2X communication with another UE 1602. When the UE 1601 newly establishes an SLRB and performs unicast communication with another UE 1602, the UE 1601 may send a PC5 RRC message including the new SLRB configuration information to the other UE 1602.

[0415] In operation 1670, the UE 1601 may send an RRC connection reconfiguration complete (RRCConnectionReconfigurationComplete) message to the LTE eNB, and in operation 1675, perform NR V2X sidelink communication (send NR V2X sidelink packets) with another UE 1602.

[0416] When a UE that sends and receives data in the UE connected mode has no data to send / receive for a predetermined reason or within a predetermined time, in operation 1680, the LTE eNB may switch the UE to the RRC idle mode (RRC_IDEL) or the RRC inactive mode (RRC_INACTIVE) by sending an RRC connection release message (RRCConnectionRelease message). This message may include an indicator or information element indicating whether to continuously use or release the SLRB used in the RRC connected mode. The UE 1601 in the RRC idle mode or the RRC inactive mode may determine whether to continuously use or release the SLRB used with another UE 1602 based on the information included in the RRC connection release message, or determine whether to newly establish an SLRB based on the system information to perform NR V2X sidelink communication with another UE 1602. When the UE 1601 needs to change or release the SLRB conventionally used with another UE 1602 or newly establish an SLRB, if the UE is performing unicast communication with another UE 1602, the UE 1601 may send a PC5 RRC message including the new SLRB configuration information to the other UE 1602.

[0417] In operation 1651, the UE 1601 may transition from the RRC idle mode or the RRC inactive mode to the RRC connected mode, and then release all the SLRBs established and used in the RRC idle mode or the RRC inactive mode.

[0418] Figure 17 An example of a process in a wireless communication system according to various embodiments of the present disclosure is shown: a process of managing an established sidelink radio bearer (SLRB) when a UE supporting NR V2X sidelink communication establishes a sidelink bearer (SLRB) in the RRC idle mode (RRC_IDLE) or the RRC inactive mode (RRC_INACTIVE) and switches to the RRC connected mode (RRC_CONNECTED) with an NR eNB during NR V2X sidelink communication.

[0419] The UE 1701 according to an embodiment of the present disclosure may refer to a vehicle-mounted UE or a pedestrian UE. The UE 1701 may support LTEV2X sidelink communication and / or NR V2X sidelink communication. The NR gNB according to an embodiment of the present disclosure may periodically broadcast or signal system information related to LTE V2X sidelink configuration information or system information related to NR V2X sidelink configuration information.

[0420] Reference Figure 17, in operation 1705, a UE 1701 capable of performing NR V2X sidelink communication may pre-configure SLRB configuration information of a PC5 QoS profile from the core network. At this time, the SLRB configuration information may be pre-configured for all available PC5 QoS profiles. According to an embodiment, the pre-configured SLRB configuration information may include, for example, the mapping of a PC5 QoS profile, PDCP / RLC / LCH, PFI, PQI to an SLRB, etc.

[0421] In operation 1710, the UE 1701 does not establish an RRC connection with the NR gNB 1703, and thus may be in the RRC idle mode (RRC_IDLE) or the RRC inactive mode (RRC_INACTIVE).

[0422] In operation 1715, the UE 1701 in the RRC idle mode or the RRC inactive mode may discover a suitable NR cell 1703 through a cell selection process or a cell reselection process, and camp on the discovered cell to obtain system information. According to an embodiment, the system information may be one or more SIBx, including MIB1, SIB1, SIB2, SIB3, SIB4, SIB5, SIB6, or NR V2X sidelink configuration information defined / introduced for NR V2X sidelink communication. The cell on which the UE camps may be referred to as a serving cell (SCell) or a primary cell (PCell).

[0423] Specifically, in operation 1715, when it is indicated that there is SIBx described in the SchedulingInfoList in SIB1 (System Information Block Type 1) received from a cell (Scell or PCell), the UE 1701 in RRC idle mode or RRC inactive mode can acquire SIBx. Alternatively, when a valid SIBx is not stored, the UE 1701 can acquire SIBx. When the NR gNB 1703 broadcasts SIBx, SIBx selectively includes s1-V2X-ConfigCommon. s1-V2X-ConfigCommon can include at least one of the following: v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, threshSS-TxPrioritization, anchorCarrierFreqList, offsetDFN, cbr-CommonTxConfigList, cbr-pssch-TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR. Additionally, SIBx can include sidelink bearer (sidelink radio bearer (SLRB)) configuration information of the PC5 QoS profile. According to an embodiment, the sidelink bearer configuration information of one or more PC5 QoS profiles can include mapping information of one SLRB and / or PDCP / RLC / LCH configuration information. Alternatively, the sidelink bearer configuration information of one PC5 QoS profile can include mapping information of one or more SLRBs and / or PDCP / RLC / LCH configuration information. The PC5 QoS profile can be at least one of the following: packet filtering information (PFI), range and / or required transmission rate (required data rate), or PC5 5G QoS identifier (PQI) PC5 QoS parameters / characteristics (see [Table 1]).

[0424] In operation 1720, the higher layer device can configure the AS device to receive NR V2X sidelink communication packets. An indication can be made to receive the communication at a specific frequency.

[0425] In operation 1725, a higher layer device may configure a PC5 QoS profile (PQI according to an embodiment) in the packets to be received and transmit the configured PC5 QoS profile to the AS device. When there is no indication in operation 1720 indicating receipt of NR V2X sidelink communication at a specific frequency, an indication may be made in operation 1725.

[0426] In operation 1730, the AS device may determine whether sidelink bearer configuration information of the PC5 QoS profile in the packets received in operation 1725 exists in the SIBx received in operation 1715.

[0427] When the sidelink bearer configuration information of the PC5 QoS profile in the packets to be received exists in the SIBx received in operation 1715, in operation 1735, the AS device may establish an SLRB. When the information is not included in the SIBx, the SLRB may be established based on the preconfigured information in operation 1705.

[0428] In operation 1740, UE 1701 may perform NR V2X sidelink communication with another UE 1702 through the SLRB established in operation 1735. The NR V2X sidelink communication may be performed through broadcast, multicast, or unicast.

[0429] In operation 1745, a UE 1701 in RRC idle mode may send an RRC connection establishment request message (RRCSetupRequest message) to the NR gNB to perform an RRC connection establishment procedure with the NR gNB 1703. In operation 1750, the NR gNB may send an RRC connection establishment message (RRCSetup message) to the UE in RRC idle mode. The UE 1701 that receives the RRC connection establishment message may apply the configuration information included in the message and then transition to RRC connected mode in operation 1751. UE 1701 may continuously perform NR V2X sidelink communication with another UE 1702 through the SLRB established in operation 1735 based on the system information obtained in operation 1715. In operation 1755, UE 1701 may send an RRC connection establishment complete message (RRCSetupComplete message) to the NR gNB. The RRC connection establishment complete message may include QoS information related to the SLRB established and used in RRC idle mode. According to an embodiment, the RRC connection establishment complete message may include at least one of the following information related to the SLRB established and used in RRC idle mode.

[0430] - PC5 QoS profile

[0431] One or more PC5 QoS flow identifiers (PFIs) and / or one or more PC5 5QIs (PQIs)

[0432] - One or more destination information

[0433] - Broadcast type based on each destination (e.g., whether the SLRB established and used in RRC idle mode is for unicast, broadcast, or multicast)

[0434] - Broadcast type based on each destination (e.g., whether the SLRB established and used in RRC idle mode is for unicast, broadcast, or multicast)

[0435] - Indicator or SLRB identifier indicating whether the SLRB established and used in RRC idle mode is continuously used

[0436] - SLRB mapping information of PC5 QoS flow (e.g., mapping of PFI to SLRB and mapping of QoS profile to SLRB)

[0437] In operation 1745, the UE 1701 in RRC inactive mode may send an RRC resume request message (RRCResumeRequest message) to the NR gNB to perform an RRC connection resume procedure (RRC connection resume procedure) with the NR gNB 1703. In operation 1750, the NR gNB may send an RRC resume message (RRCResume message) to the UE in RRC inactive mode. The UE 1701 that receives the RRC connection resume message may apply the configuration information included in the message and then switch to the RRC connected mode in operation 1751. The UE 1701 may continuously perform NR V2X sidelink communication with another UE 1702 through the SLRB established in operation 1735 based on the system information obtained in operation 1715. In operation 1755, the UE 1701 may send an RRC resume complete message (RRCResumeComplete message) to the NR gNB. The RRC resume complete message may include QoS information related to the SLRB established and used in RRC inactive mode. According to an embodiment, at least one of the following information related to the SLRB established and used in RRC inactive mode may be included.

[0438] - PC5 QoS profile

[0439] One or more PC5 QoS flow identifiers (PFIs) and / or one or more PC5 5QIs (PQIs)

[0440] - One or more destination information

[0441] - The broadcast type based on each destination (for example, whether the SLRB established and used in the RRC idle mode is for unicast, broadcast, or multicast)

[0442] - An indicator or SLRB identifier indicating whether to continuously use the SLRB established and used in the RRC idle mode

[0443] - SLRB mapping information for PC5 QoS flows (for example, the mapping from PFI to SLRB and the mapping from QoS profile to SLRB)

[0444] In operation 1760, the UE 1701 in the RRC connected mode may send a Sidelink UE Information message to the NR gNB. Operation 1760 may be performed when the QoS information is not included in the RRC establishment complete message or the RRC resume complete message in operation 1755. The Sidelink UE message may include QoS information related to the SLRB established and used in the RRC idle mode or the RRC inactive mode. According to an embodiment, at least one of the following information related to the SLRB established and used in the RRC idle mode or the RRC inactive mode may be included.

[0445] - PC5 QoS profile

[0446] According to an embodiment, one or more PC5 QoS flow identifiers (PFIs) and / or one or more PC5 5QIs (PQIs)

[0447] - One or more destination information

[0448] - The broadcast type based on each destination (for example, whether the SLRB established and used in the RRC idle mode is for unicast, broadcast, or multicast)

[0449] - An indicator or SLRB identifier indicating whether to continuously use the SLRB established and used in the RRC idle mode

[0450] - SLRB mapping information for PC5 QoS flows (for example, the mapping from PFI to SLRB and the mapping from QoS profile to SLRB)

[0451] In operation 1765, the NR gNB may insert at least one of the following information into the RRC Reconfiguration message and send the RRC Reconfiguration message to the UE in the RRC connected mode.

[0452] - SLRB configuration information related to the QoS information included in operation 1755 or operation 1760

[0453] - An indicator (indication) indicating whether to continuously use the SLRB configuration information established and used in the RRC idle mode or the RRC inactive mode

[0454] - Resource mode (mode 3 or mode 4)

[0455] - Resource pool configuration information according to the resource mode

[0456] In operation 1767, UE 1701 may determine whether to continuously use the SLRB established and used in the RRC idle mode or the RRC inactive mode based on the message received in operation 1765. According to an embodiment, when an indicator indicating continuous use is inserted into the RRC reconfiguration (RRCReconfiguration) message, or when information identical to the SLRB established and used in the RRC idle mode or the RRC inactive mode is included, the UE 1701 in the RRC connected mode may perform NR V2X communication with another UE 1702 by continuously using the regularly used SLRB. When the SLRB configuration information not established in the RRC idle mode or the RRC inactive mode is included, the UE 1701 in the RRC connected mode may newly establish an SLRB and perform NR V2X communication with another UE 1702. When the UE 1701 newly establishes an SLRB and performs unicast communication with another UE 1702, the UE 1701 may send a PC5 RRC message including the new SLRB configuration information to the other UE 1702.

[0457] In operation 1770, UE 1701 may send an RRC reconfiguration complete (RRCReconfigurationComplete) message to the NR gNB, and in operation 1775, perform NR V2X sidelink communication (send NR V2X sidelink packets) with another UE 1702.

[0458] When a UE that sends and receives data in the UE connected mode has no data to send / receive for a predetermined reason or within a predetermined time, in operation 1780, the NR gNB may switch the UE to the RRC idle mode (RRC_IDEL) or the RRC inactive mode (RRC_INACTIVE) by sending an RRC release message (RRCRelease message). The message may include an indicator or information element indicating whether to continuously use or release the SLRB used in the RRC connected mode. The UE 1701 in the RRC idle mode or the RRC inactive mode may determine whether to continuously use or release the SLRB used with another UE 1702 based on the information included in the RRC connection release message, or determine whether to newly establish an SLRB to perform NR V2X sidelink communication with another UE 1702 based on the system information. When the UE 1701 needs to change or release the SLRB conventionally used with another UE 1702 or newly establish an SLRB, if the UE is performing unicast communication with another UE 1702, the UE 1701 may send a PC5 RRC message including the new SLRB configuration information to the other UE 1702.

[0459] In operation 1751, the UE 1701 may transition from the RRC idle mode or the RRC inactive mode to the RRC connected mode, and then release all the SLRBs established and used in the RRC idle mode or the RRC inactive mode.

[0460] Figure 18 An example of the structure of a UE in a wireless communication system according to various embodiments of the present disclosure is shown.

[0461] Reference Figure 18 , the UE according to various embodiments of the present disclosure may include a radio frequency (RF) processing unit 1810, a baseband processing unit 1820, a storage unit 1830, and a controller 1840.

[0462] The RF processor 1810 according to an embodiment of the present disclosure may perform functions of transmitting and receiving signals through a radio channel, such as band conversion or amplification of signals. That is, the RF processing unit 1810 may up-convert the baseband signal provided from the baseband processing unit 1820 into an RF band signal, transmit the RF band signal through an antenna, and down-convert the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit 1810 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc.

[0463] Although Figure 18 only one antenna is shown, the UE may include multiple antennas.

[0464] The RF processing unit 1810 may include multiple RF chains. Additionally, the RF processing unit 1810 may perform beamforming. For beamforming, the RF processing unit 1810 may control the phase and magnitude of each signal transmitted / received through multiple antennas or antenna elements. Additionally, the RF processing unit 1810 may perform multiple-input multiple-output (MIMO) and receive multiple layers during MIMO operations. The RF processing unit 1810 may appropriately configure multiple antennas or antenna elements under the control of the controller 1840 to perform receive beam scanning or control the receive beam direction and beam width such that the receive beam is coordinated with the transmit beam.

[0465] The baseband processing unit 1820 may perform the conversion function between baseband signals and bitstreams according to the physical layer standard of the system. For example, in data transmission, the baseband processing unit 1820 may encode and modulate the transmit bitstream to generate complex symbols. In data reception, the baseband processing unit 1820 may reconstruct the received bitstream by demodulating and decoding the baseband signal provided by the RF processing unit 1810. For example, in an orthogonal frequency division multiplexing (OFDM) scheme, when transmitting data, the baseband processing unit 1820 may encode and modulate the transmit bitstream to generate complex symbols, map the complex symbols to subcarriers, and then configure OFDM symbols through an inverse fast Fourier transform (IFFT) operation or cyclic prefix (CP) insertion. Additionally, in data reception, the baseband processing unit 1820 may separate the baseband signal provided by the RF processing unit 1810 in units of OFDM symbols, reconstruct the signal mapped to subcarriers through a fast Fourier transform (FFT) operation, and then reconstruct the received bitstream through demodulation and decoding.

[0466] As described above, the baseband processing unit 1820 and the RF processing unit 1810 may transmit and receive signals. Therefore, the baseband processing unit 1820 and the RF processing unit 1810 may be referred to as transmitters, receivers, transceivers, or communication units. Additionally, at least one of the baseband processing unit 1820 and the RF processing unit 1810 may include multiple communication modules to support multiple different radio access technologies. Additionally, at least one of the baseband processing unit 1820 and the RF processing unit 1810 may include different communication modules to process signals in different frequency bands. For example, different radio access technologies may include LTE networks, NR networks, etc. Additionally, different frequency bands may include super high frequency (SHF) (e.g., 2.2 GHz and 2 GHz) bands and millimeter (mm) wave (e.g., 60 GHz) bands.

[0467] The storage unit 1830 may store data such as basic programs, application programs, and configuration information for UE operations. The storage unit 1830 may provide the stored data according to the request of the controller 1840.

[0468] The controller 1840 may control the overall operation of the UE. For example, the controller 1840 may transmit and receive signals through the baseband processing unit 1820 and the RF processing unit 1810. In addition, the controller 1840 may record data in the storage unit 1830 and read data. To this end, the controller 1840 may include at least one processor. For example, the controller 1840 may include a communication processor (CP) that performs communication control and an application processor (AP) that controls a higher layer (such as an application).

[0469] Figure 19 An example of the structure of a BS in a wireless communication system according to various embodiments of the present disclosure is shown.

[0470] A BS according to an embodiment of the present disclosure may include one or more transmit-receive points (TRPs).

[0471] Reference Figure 19 , a BS according to various embodiments of the present disclosure may include an RF processing unit 1910, a baseband processing unit 1920, a backhaul communication unit 1930, a storage unit 1940, and a controller 1950.

[0472] The RF processing unit 1910 may perform functions of transmitting and receiving signals through a radio channel, such as frequency band conversion and amplification of signals. That is, the RF processing unit 1910 may up-convert a baseband signal provided from the baseband processing unit 1920 into an RF band signal, transmit the RF band signal through an antenna, and then down-convert the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit 1910 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC. The RF processing unit 1910 may include at least one transceiver.

[0473] Although Figure 19 only one antenna is shown, the BS may include multiple antennas.

[0474] The RF processing unit 1910 may include multiple RF chains. In addition, the RF processing unit 1910 may perform beamforming. For beamforming, the RF processing unit 1910 may control the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. The RF processing unit 1910 may perform a downlink MIMO operation by transmitting one or more layers.

[0475] The baseband processing unit 1920 can perform the conversion function between baseband signals and bitstreams according to the physical layer standard of the first radio access technology. For example, in data transmission, the baseband processing unit 1920 can encode and modulate the transmitted bitstream to generate complex symbols. In data reception, the baseband processing unit 1920 can reconstruct the received bitstream by demodulating and decoding the baseband signal provided by the RF processing unit 1910. For example, in the OFDM scheme, when transmitting data, the baseband processing unit 1920 can encode and modulate the transmitted bitstream to generate complex symbols, map the complex symbols to subcarriers, and then configure OFDM symbols through IFFT operations and CP insertion. Additionally, when receiving data, the baseband processing unit 1920 can separate the baseband signal provided by the RF processing unit 1910 in units of OFDM symbols, reconstruct the signal mapped to subcarriers through FFT operations, and then reconstruct the received bitstream through demodulation and decoding. As described above, the baseband processing unit 1920 and the RF processing unit 1910 can transmit and receive signals.

[0476] Therefore, the baseband processing unit 1920 and the RF processing unit 1910 can be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0477] The communication unit 1930 can provide an interface for communicating with other nodes within the network. That is, the communication unit 1930 can convert the bitstream sent from the master BS to another node (e.g., the secondary BS, the core network, etc.) into a physical signal, and can convert the physical signal received from another node into a bitstream.

[0478] The storage unit 1940 can store data such as basic programs, application programs, configuration information, etc. for the operation of the master BS. In particular, the storage unit 1940 can store information about the UEs bearers allocated to the access and the measurement results reported by the accessed UEs. Additionally, the storage unit 1940 can store information related to determining whether to provide multiple connections to the UEs or to stop the connections. Additionally, the storage unit 1940 can provide the stored data according to the request of the controller 1950.

[0479] The controller 1950 can control the overall operation of the master BS. For example, the controller 1950 can send and receive signals through the baseband processing unit 1920 and the RF processing unit 1910 or through the communication unit 1930. Additionally, the controller 1950 can record data in the storage unit 1940 and read data. To this end, the controller 1950 can include at least one processor.

[0480] The method according to each embodiment described in the claims or this disclosure specification can be implemented by hardware, software, or a combination of hardware and software.

[0481] When the method is implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors within the electronic device. At least one program may include instructions that cause the electronic device to execute the method according to various embodiments of the present disclosure as defined by the appended claims and / or disclosed herein.

[0482] The program (software module or software) may be stored in non-volatile memory, including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage devices, compact disc-ROM (CD-ROM), digital versatile disc (DVD), or other types of optical storage devices, or magnetic tape cartridges. Alternatively, any combination of some or all of them may form the memory for storing the program. Additionally, multiple such memories may be included in the electronic device.

[0483] Additionally, the program may be stored in an attachable storage device that can access the electronic device through a communication network such as the Internet, intranet, local area network (LAN), wide area LAN (WLAN), and storage area network (SAN), or a combination thereof. Such a storage device may access the electronic device via an external port. Additionally, a separate storage device on the communication network may access the portable electronic device.

[0484] In the above detailed embodiments of the present disclosure, elements included in the present disclosure are expressed in the singular or plural according to the presented detailed embodiments. However, for ease of description, the singular or plural form is appropriately selected for the presented situations, and the present disclosure is not limited to the singular or plural expression of these elements. Therefore, elements expressed in the plural may also include a single element, or elements expressed in the singular may also include multiple elements.

[0485] Although specific embodiments have been described in the detailed description of the present disclosure, various modifications and changes can be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be defined by the embodiments, but should be defined by the appended claims and their equivalents.

[0486] Industrial Applicability

[0487] An apparatus and method according to various embodiments of the present disclosure can effectively support vehicle-to-everything (V2X) communication in a wireless communication system.

Claims

1. A method performed by a first user equipment (UE) in a wireless communication system, the method comprising: When the first UE camps on a first cell, receiving, in a Radio Resource Control (RRC) idle mode or an RRC inactive mode, first system information from the first cell, the first system information including a first sidelink communication configuration; When the first UE is configured by an upper layer to perform sidelink communication for a frequency, identifying whether information about the frequency for the sidelink communication is included in the first system information; When the information about the frequency for the sidelink communication is not included in the first system information, receiving second system information from a second cell, the second system information including a second sidelink communication configuration; and Performing the sidelink communication based on the second system information.

2. The method according to claim 1, further comprising: When the second system information includes sidelink radio bearer (SLRB) configuration information, establishing an SLRB by applying the SLRB configuration information.

3. The method according to claim 1, wherein, The first UE is configured to perform both first sidelink communication and second sidelink communication.

4. The method according to claim 1, when the second sidelink communication configuration is not included in the second system information, performing the sidelink communication based on a pre-configured sidelink communication configuration.

5. A first user equipment (UE) in a wireless communication system, the first UE comprising: A transceiver; A memory storing one or more computer programs; And One or more processors communicatively connected to the transceiver and the memory, Wherein the one or more computer programs include computer-executable instructions that, when executed by the one or more processors alone or in combination, cause the first UE to: When the first UE camps on a first cell, receive, in a Radio Resource Control (RRC) idle mode or an RRC inactive mode, first system information from the first cell, the first system information including a first sidelink communication configuration, When the first UE is configured by an upper layer to perform sidelink communication for a frequency, identify whether information about the frequency for the sidelink communication is included in the first system information, When the information about the frequency for the sidelink communication is not included in the first system information, receive second system information from a second cell, the second system information including a second sidelink communication configuration; and Perform the sidelink communication based on the second system information.

6. The first UE according to claim 5, wherein, When the computer-executable instructions are executed by the one or more processors alone or in combination, they further cause the first UE to: When the second system information includes sidelink radio bearer (SLRB) configuration information, establish an SLRB by applying the SLRB configuration information.

7. The first UE according to claim 5, wherein The first UE is configured to perform both first sidelink communication and second sidelink communication.

8. The first UE according to claim 5, wherein In the case where the second sidelink communication configuration is not included in the second system information, perform the sidelink communication based on a pre-configured sidelink communication configuration.

Images