Method and apparatus for performing vehicle communication in wireless communication system

Abstract

A method for a terminal to perform sidelink communication in a wireless communication system may include: a step of acquiring system information containing sidelink communication setting information; a step of establishing a Sidelink Radio Bearer (SLRB) based on the system information; a step of performing sidelink communication based on the established SLRB; and a step of performing an RRC connection with a base station based on the established SLRB.

Description

Technology Field

[0001] The present disclosure relates to a method and apparatus for performing vehicle communication in a wireless communication system, and specifically to a method and apparatus for controlling PC5 QoS parameters for a non-standardized PQI for vehicle communication. Background Technology

[0002] To meet the demand for wireless data traffic, which is increasing explosively due to the commercialization of 4G communication systems and the growth of multimedia services, improved 5G communication systems or pre-5G communication systems are being developed. For this reason, 5G communication systems or pre-5G communication systems are referred to as systems beyond 4G networks or systems after LTE systems.

[0003] To increase data transmission rates, 5G communication systems are being considered for implementation in the mmWave band (e.g., the 60 GHz band). To mitigate path loss and increase transmission distance in the mmWave band, beamforming, massive MIMO, full Dimensional MIMO (FD-MIMO), array antenna, analog beamforming, and large-scale antenna technologies are being discussed for 5G communication systems.

[0004] In addition, to improve the network performance of the system, technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation are being developed in 5G communication systems. Furthermore, in 5G systems, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed.

[0005] Meanwhile, the Internet is evolving from a human-centered network where humans generate and consume information into an IoT (Internet of Things) network that processes information by exchanging it among distributed components, such as objects. IoE (Internet of Everything) technology, which combines IoT with Big Data processing techniques via connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required; consequently, technologies such as sensor networks, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are currently being researched to facilitate the connection of objects. In an IoT environment, intelligent IT services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT technologies with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0006] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, Machine to Machine (M2M), and Machine Type Communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. The application of cloud RAN as a big data processing technology, as previously described, can also be considered an example of the convergence of 5G and IoT technologies. The problem to be solved

[0007] One embodiment of the present disclosure may provide a method and apparatus for providing services more effectively. means of solving the problem

[0008] A method for a terminal to perform sidelink communication in a wireless communication system according to one embodiment of the present disclosure may include: a step of obtaining system information including sidelink communication setting information; a step of establishing a Sidelink Radio Bearer (SLRB) based on the system information; a step of performing sidelink communication based on the established SLRB; and a step of performing an RRC connection with a base station based on the established SLRB. Effects of the invention

[0009] According to one embodiment of the present disclosure, services can be provided more effectively. Brief explanation of the drawing

[0010] FIG. 1a is a drawing illustrating the structure of an LTE system according to one embodiment of the present disclosure. FIG. 1b is a diagram illustrating a wireless protocol structure in an LTE system according to one embodiment of the present disclosure. FIG. 1c is a drawing illustrating the structure of a next-generation mobile communication system according to one embodiment of the present disclosure. FIG. 1d is a diagram illustrating the wireless protocol structure of a next-generation mobile communication system according to one embodiment of the present disclosure. FIG. 1e is a diagram illustrating V2X communication of a next-generation mobile communication system according to one embodiment of the present disclosure. FIG. 1f is a flowchart illustrating a method for connecting a terminal performing NR V2X sidelink communication to an LTE base station according to one embodiment of the present disclosure. FIG. 1g is a flowchart illustrating a method for connecting a terminal performing NR V2X sidelink communication to an NR base station according to one embodiment of the present disclosure. FIG. 1h is a flowchart illustrating a method for connecting a terminal performing NR V2X sidelink communication to an NR base station according to one embodiment of the present disclosure. FIG. 1i illustrates the structure of a terminal according to one embodiment of the present disclosure. FIG. 1j illustrates the structure of a base station in one embodiment of the present disclosure. Specific details for implementing the invention

[0011] The operating principle of the present invention will be described in detail below with reference to the attached drawings. In describing the present invention below, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the invention. Furthermore, the terms described below are defined considering their functions in the present invention, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0012] In the following description of the present invention, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions may unnecessarily obscure the essence of the invention. Embodiments of the present invention will be described below with reference to the attached drawings.

[0013] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0014] For convenience of explanation, the present invention uses terms and names defined in the 3GPP LTE (3rd Generation Partnership Project Long Term Evolution) standard. However, the present invention is not limited by the above terms and names and can be applied equally to systems conforming to other standards. In the present invention, eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as eNB may represent a gNB.

[0015] FIG. 1a is a drawing illustrating the structure of an LTE system according to one embodiment of the present disclosure.

[0016] Referring to FIG. 1a, the wireless access network of the LTE system may be composed of a next-generation base station (Evolved Node B, hereinafter ENB, Node B or base station) (1a-05, 1a-10, 1a-15, 1a-20), an MME (1a-25, Mobility Management Entity), and an S-GW (1a-30, Serving-Gateway). A user terminal (User Equipment, hereinafter UE or terminal) (1a-35) can connect to an external network through the ENB (1a-05 to 1a-20) and the S-GW (1a-30).

[0017] In FIG. 1a, the ENB (1a-05 to 1a-20) can correspond to the existing Node B of the UMTS (Universal Mobile Telecommunication System) system. The ENB is connected to the UE (1a-35) via a wireless channel and can perform more complex roles than the existing Node B. In an LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) via the Internet Protocol, can be serviced through a shared channel. Therefore, a device is required to collect status information such as the buffer status, available transmission power status, and channel status of the UEs to perform scheduling, and this can be handled by the ENB (1a-05 to 1a-20).

[0018] A single ENB can typically control multiple cells. For example, to achieve a transmission speed of 100 Mbps, an LTE system may use Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as a wireless access technology in a bandwidth of, for example, 20 MHz. Additionally, an Adaptive Modulation & Coding (hereinafter referred to as AMC) method may be applied to determine the modulation scheme and channel coding rate according to the channel conditions of the terminal.

[0019] The S-GW (1a-30) is a device that provides data bearers and can create or remove data bearers under the control of the MME (1a-25). The MME is a device that is responsible for various control functions as well as mobility management functions for terminals and can be connected to multiple base stations.

[0020] FIG. 1b is a diagram illustrating a wireless protocol structure in an LTE system according to one embodiment of the present disclosure.

[0021] Referring to FIG. 1b, the wireless protocol of the LTE system may consist of PDCP (Packet Data Convergence Protocol 1b-05, 1b-40), RLC (Radio Link Control 1b-10, 1b-35), and MAC (Medium Access Control 1b-15, 1b-30) at the terminal and ENB, respectively. PDCP (Packet Data Convergence Protocol) (1b-05, 1b-40) can be responsible for operations such as IP header compression / decompression. The main functions of PDCP can be summarized as follows.

[0022] - Header compression and decompression features (ROHC only)

[0023] - User data transfer function (Transfer of user data)

[0024] - In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM

[0025] - Reordering Function - Reordering Function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

[0026] - Duplicate detection function (Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)

[0027] - Retransmission Function - Retransmission Function (Retransmission of PDCP SDUs at handover for split bearers in DC and, for split bearers in DC, of ​​PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

[0028] - Encryption and decryption functions (Ciphering and deciphering)

[0029] - Timer-based SDU discard in uplink.

[0030] Radio Link Control (hereinafter referred to as RLC) (1b-10, 1b-35) can perform ARQ operations, etc., by reconfiguring PDCP Packet Data Units (PDUs) to an appropriate size. The main functions of RLC can be summarized as follows.

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

[0032] - ARQ function (Error correction through ARQ (only for AM data transfer))

[0033] - Concatenation, segmentation, and reassembly of RLC SDUs (only for UM and AM data transfer)

[0034] - Re-segmentation of RLC data PDUs (only for AM data transfer)

[0035] - Reordering of RLC data PDUs (only for UM and AM data transfer)

[0036] - Duplicate detection (only for UM and AM data transfer)

[0037] - Error detection function (for AM data transfer only) (Protocol error detection (only for AM data transfer))

[0038] - RLC SDU discard (only for UM and AM data transfer)

[0039] RLC re-establishment function

[0040] MAC (1b-15, 1b-30) is connected to multiple RLC layer devices configured in a terminal and can perform operations to multiplex RLC PDUs into MAC PDUs and demultiplex RLC PDUs from MAC PDUs. The main functions of MAC can be summarized as follows.

[0041] - Mapping function between logical channels and transport channels

[0042] - Multiplexing and demultiplexing of MAC PDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels

[0043] - Scheduling information reporting function

[0044] - Error correction through HARQ

[0045] - Priority handling between logical channels of one UE

[0046] - Inter-terminal - Priority handling between UEs by means of dynamic scheduling

[0047] - MBMS service identification function

[0048] - Transport format selection function

[0049] - Padding

[0050] The physical layer (1b-20, 1b-25) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0051] FIG. 1c is a drawing illustrating the structure of a next-generation mobile communication system according to one embodiment of the present disclosure.

[0052] Referring to FIG. 1c, as illustrated, the wireless access network of a next-generation mobile communication system (hereinafter NR or 2g) may be composed of a next-generation base station (New Radio Node B, hereinafter NR gNB or NR base station) (1c-10) and an NR CN (1c-05, New Radio Core Network). A user terminal (New Radio User Equipment, hereinafter NR UE or terminal) (1c-15) can connect to an external network through the NR gNB (1c-10) and the NR CN (1c-05).

[0053] In FIG. 1c, the NR gNB (1c-10) can correspond to the eNB (Evolved Node B) of the existing LTE system. The NR gNB is connected to the NR UE (1c-15) via a wireless channel and can provide superior service compared to the existing Node B. In the next-generation mobile communication system, all user traffic can be serviced through a shared channel. Therefore, a device is required to collect state information such as the buffer status, available transmission power status, and channel status of the UEs to perform scheduling, and this can be handled by the NR NB (1c-10). A single NR gNB can typically control multiple cells. In the next-generation mobile communication system, to achieve ultra-high-speed data transmission compared to current LTE, it can have a maximum bandwidth greater than the existing maximum bandwidth, and Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) can be used as a wireless access technology, and additional beamforming technology can be incorporated. In addition, an Adaptive Modulation & Coding (hereinafter referred to as AMC) scheme that determines the modulation scheme and channel coding rate according to the channel conditions of the terminal may be applied.

[0054] The NR CN (1c-05) can perform functions such as mobility support, bearer configuration, and QoS configuration. The NR CN is a device responsible for various control functions as well as mobility management functions for terminals, and is connected to multiple base stations. In addition, the next-generation mobile communication system can be interoperable with existing LTE systems, and the NR CN is connected to the MME (1c-25) via a network interface. The MME can be connected to the existing base station eNB (1c-30).

[0055] FIG. 1d is a diagram illustrating the wireless protocol structure of a next-generation mobile communication system according to one embodiment of the present disclosure.

[0056] Referring to Fig. 1d, the wireless protocol of the next-generation mobile communication system consists of NR SDAP (1d-01, 1d-45), NR PDCP (1d-05, 1d-40), NR RLC (1d-10, 1d-35), and NR MAC (1d-15, 1d-30) at the terminal and the NR base station, respectively.

[0057] The main functions of NR SDAP(1d-01, 1d-45) may include some of the following functions.

[0058] - User data transfer function (transfer of user plane data)

[0059] - Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink

[0060] - Marking QoS flow ID in both DL and UL packets for uplink and downlink

[0061] - Function to map reflective QoS flow to data bearers for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0062] For SDAP layer devices, the terminal may receive a setting via RRC (Radio Resource Control) messages regarding whether to use the SDAP layer device header or the SDAP layer device functions for each PDCP layer device, bearer, or logical channel. If the SDAP header is configured, the terminal may instruct the terminal to update or reset the mapping information for the uplink and downlink QoS flows and data bearers using the 1-bit NAS (Non-Access Stratum) QoS reflective QoS indicator and the 1-bit AS (Access Stratum) QoS reflective QoS indicator in the SDAP header. The SDAP header may include QoS flow ID information representing QoS. QoS information may be used for data processing priorities, scheduling information, etc., to support seamless service.

[0063] The main functions of NR PDCP (1d-05, 1d-40) may include some of the following functions.

[0064] - Header compression and decompression features (ROHC only)

[0065] - User data transfer function (Transfer of user data)

[0066] - In-sequence delivery of upper layer PDUs

[0067] - Out-of-sequence delivery of upper layer PDUs

[0068] - PDCP PDU reordering for reception

[0069] - Duplicate detection of lower layer SDUs

[0070] - Retransmission of PDCP SDUs

[0071] - Encryption and decryption functions (Ciphering and deciphering)

[0072] - Timer-based SDU discard in uplink.

[0073] In the above description, the reordering function of the NR PDCP device may refer to a function that reorders PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number). The reordering function of the NR PDCP device may include a function of transmitting data to an upper layer in the reordered order, a function of transmitting immediately without considering the order, a function of recording lost PDCP PDUs by reordering, a function of reporting the status of lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of lost PDCP PDUs.

[0074] The main functions of NR RLC(1d-10, 1d-35) may include some of the following functions.

[0075] - Data transfer function of upper layer PDUs

[0076] - In-sequence delivery of upper layer PDUs

[0077] - Out-of-sequence delivery of upper layer PDUs

[0078] Error Correction through ARQ

[0079] - Concatenation, segmentation and reassembly of RLC SDUs

[0080] - Re-segmentation of RLC data PDUs

[0081] - Reordering of RLC data PDUs

[0082] - Duplicate detection

[0083] - Error detection function (Protocol error detection)

[0084] - RLC SDU discard function

[0085] RLC re-establishment function

[0086] In the above description, the in-sequence delivery function of the NR RLC (1d-10, 1d-35) device may mean a function of delivering RLC SDUs received from a lower layer to an upper layer in sequence. If a single RLC SDU is originally received divided into multiple RLC SDUs, the in-sequence delivery function of the NR RLC (1d-10, 1d-35) device may include a function of reassembling and delivering them.

[0087] The sequential delivery function of the NR RLC (1d-10, 1d-35) device may include a function to rearrange the received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number), a function to record the lost RLC PDUs by rearranging the order, a function to report the status of the lost RLC PDUs to the transmitting side, and a function to request retransmission of the lost RLC PDUs.

[0088] The sequential delivery function of the NR RLC (1d-10, 1d-35) device may include a function to deliver only the RLC SDUs prior to the lost RLC SDU in order to the upper layer if there is a lost RLC SDU. Additionally, the sequential delivery function of the NR RLC (1d-10, 1d-35) device may include a function to deliver all RLC SDUs received before the timer started in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU, and may include a function to deliver all RLC SDUs received up to now in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU.

[0089] The NR RLC(1d-10, 1d-35) device may process RLC PDUs in the order they are received and deliver them to the PDCP device out of sequence, regardless of the sequence number, and in the case of segments, may receive segments stored in a buffer or to be received later and deliver them to the NR PDCP(1d-05, 1d-40) device.

[0090] When the (1d-10, 1d-35) device receives a segment, it may receive segments stored in a buffer or to be received later, reconstruct them into a single complete RLC PDU, and then transmit it to the NR PDCP (1d-05, 1d-40) device. The NR RLC layer may not include a concatenation function and may perform the function in the NR MAC layer or replace it with the multiplexing function of the NR MAC layer.

[0091] In the above description, the out-of-sequence delivery function of the NR RLC device may refer to the function of delivering RLC SDUs received from a lower layer directly to an upper layer regardless of order. The out-of-sequence delivery function of the NR RLC device may include the function of reassembling and delivering RLC SDUs when a single RLC SDU is received divided into multiple RLC SDUs. The out-of-sequence delivery function of the NR RLC device may include the function of storing the RLC SN or PDCP SN of the received RLC PDUs, sorting the order, and recording the lost RLC PDUs.

[0092] The NR MAC (1d-15, 1d-30) can be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC may include some of the following functions.

[0093] - Mapping function between logical channels and transport channels

[0094] - Multiplexing and demultiplexing of MAC SDUs

[0095] - Scheduling information reporting function

[0096] - Error correction through HARQ

[0097] - Priority handling between logical channels of one UE

[0098] - Priority handling between UEs by means of dynamic scheduling

[0099] - MBMS service identification function

[0100] - Transport format selection function

[0101] - Padding

[0102] The NR PHY layer (1d-20, 1d-25) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0103] FIG. 1e is a diagram illustrating V2X communication of a next-generation mobile communication system according to one embodiment of the present disclosure.

[0104] According to one embodiment of the present disclosure, V2X (vehicle-to-everything) is a general term for communication technology through a vehicle and all interfaces, and depending on the form and components constituting the communication, it includes V2V (vehicle-to-vehicle), V2I (vehicle-to-intrastructure), V2P (vehicle-to-pedestrian), V2N (vehicle-to-network), etc.

[0105] Referring to FIG. 1e, a base station (1e-01) may include at least one vehicle terminal (1e-05, 1e-10) and a pedestrian handheld terminal (1e-15) located within a cell (1e-02) that supports V2X. V2X can be supported via a Uu interface and / or a PC5 interface. When V2X is supported via a Uu interface, for example, the vehicle terminal (1e-05, 1e-10) may perform cellular communication with the base station (1e-01) using an uplink (UL) / downlink (DL), 1e-30, 1e-35 between the vehicle terminal and the base station, or the pedestrian handheld terminal (1e-15) may perform cellular communication using an uplink (UL) / downlink (DL), 1e-40 between the pedestrian terminal and the base station.

[0106] Additionally, if V2X is supported through the PC5 interface, V2X sidelink (SL) communication can be performed using a terminal-to-terminal link (Sidelink (SL), 1e-20, 1e-25). For example, a vehicle terminal (1e-05) in the coverage of a base station (in coverage of E-UTRA / NR) can transmit and receive V2X packets with other vehicle terminals (1e-10, 1e-45) and / or pedestrian handheld terminals (1e-15, 1e-55) through a transmission channel, the sidelink (SL, 1e-20, 1e-50, 1e-25, 1e-60). The V2X packets can be transmitted and received in a broadcast transmission type and / or a unicast and / or a groupcast transmission type.

[0107] A terminal supporting V2X sidelink communication can transmit 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 in which a base station allocates resources used for sidelink transmission to an RRC connected mode terminal using a dedicated scheduling method. Since this resource allocation mode allows the base station to manage sidelink resources, it can be efficient for interference management and / or resource pool management (dynamic allocation, semi-persistence transmission). When an RRC connected mode terminal has data to transmit to other terminal(s), it can notify the base station that there is data to transmit to other terminal(s) using an RRC message or a MAC Control Element (hereinafter CE). For example, RRC messages such as SidelinkUEInformation and UEAssistanceInformation messages may be used, and MAC CEs such as a buffer status report MAC CE in a new format (including at least an indicator indicating that it is a buffer status report for V2X communication and information about the size of the data buffered for sidelink communication) may be used.

[0108] UE autonomous resource selection (mode 2 and / or mode 4) is a mode in which a base station provides sidelink resource information / pools to a terminal supporting V2X sidelink communication via system information and / or RRC messages, and the terminal selects resources according to defined rules. For example, the base station may provide sidelink resource information to the terminal by signaling SIB21, SIB26, or SIBx, which will be newly defined for NR V2X terminals. As for RRC messages, for example, the base station may provide sidelink resource information by signaling the terminal an RRC connection reconfiguration message (RRCReconfiguration message) and / or a connection resumption message (RRCResume message). Additionally, UE autonomous resource selection may assist other terminal(s) in selecting resources used for the sidelink via PC5-RRC messages and / or MAC CE, or may allocate resources used for sidelink transmission directly or indirectly through scheduling. In other words, the UE autonomous resource selection mode may refer to one or more of the following.

[0109] - UE autonomously selects sidelink resource for transmission

[0110] - UE assists sidelink resource selection for other UEs

[0111] - A UE configured with NR is configured grant for sidelink transmission

[0112] - UE schedules sidelink transmission of other UEs

[0113] Resource selection methods for the terminal may include zone mapping, sensing-based resource selection, random selection, and configured grant-based resource selection.

[0114] A terminal supporting V2X sidelink communication can transmit and receive V2X packets based on a pre-configured resource pool (Preconfiguration resource) included in the Information Element (hereinafter IE) SL-V2X-Preconfiguration. For example, even if a terminal is within the coverage of a base station, if it cannot perform V2X sidelink communication based on scheduled resource allocation and / or UE autonomous resource selection modes for a certain reason, the terminal can perform V2X sidelink communication through a sidelink transmission and reception resource pool pre-configured in the IE SL-V2X-Preconfiguration. Additionally, a vehicle terminal (1e-45) out of coverage of the base station (out-of-coverage of E-UTRA / NR) can perform V2X sidelink communication with another vehicle terminal (1e-65) or pedestrian handheld terminal (1e-55) through a sidelink (SL, 1e-70, 1e-75), which is a transmission channel, based on the aforementioned sidelink preconfiguration resources.

[0115] LTE V2X SL communication was designed with basic safety services as its primary goal. In other words, terminals supporting LTE V2X SL communication were designed to provide basic safety services to all surrounding terminals supporting LTE V2X SL communication via a broadcast transmission type. Therefore, there was no need for a terminal to perform the process of establishing a session separately with another specific terminal or to perform the sidelink connection establishment procedure.

[0116] However, within next-generation mobile communication (NR), V2X SL communication can be designed to provide not only basic safety services but also various enhanced services (e.g., autonomous driving services, platooning services, remote driving services, in-vehicle infotainment). Therefore, NR V2X SL communication can be designed to support not only broadcast transmission types but also unicast and / or groupcast transmission types.

[0117] FIG. 1f is a flowchart illustrating a method for connecting a terminal performing NR V2X sidelink communication to an LTE base station according to one embodiment of the present disclosure.

[0118] Specifically, referring to FIG. 1f, this is a diagram illustrating a method of reporting the established SLRB to an LTE base station when a terminal supporting NR V2X sidelink communication establishes a Sidelink Radio Bearer (hereinafter SLRB) in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE) and switches to RRC connected mode (RRC_CONNECTED) with an LTE base station while performing NR V2X sidelink communication.

[0119] A terminal according to one embodiment of the present disclosure may refer to a vehicle terminal or a pedestrian terminal. The terminal may support LTE V2X sidelink communication or NR V2X sidelink communication. An LTE base station according to one 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.

[0120] Referring to FIG. 1f, a terminal (1f-01) capable of NR V2X sidelink communication can receive parameters used for NR sidelink communication from a core network in advance (1f-05). The information in advance can be referred to as SL-PreConfigurationNR. SL-PreConfigurationNR may include a frequency list used for sidelink communication (sl-PreconfigFreqInfoList), an anchor carrier frequency list for each wireless connection (sl-PreconfigNR-AnchorCarrierFreqList, sl-PreconfigEUTRA-AnchorCarrierFreqList), sidelink radio bearer configuration information used for sidelink communication (sl-RadioBearerPreConfigList), and sidelink RLC bearer configuration information (sl-RLC-BearerPreConfigList). sl-RadioBearerPReConfigList may include mapping information for PC5 QoS Profiles for each SLRB.

[0121] The terminal (1f-01) may be in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE) as it does not establish an RRC connection with the base station (1f-03) (1f-10).

[0122] A terminal (1f-01) in RRC idle mode or RRC disabled mode can find a suitable LTE cell and camp on it through a cell selection procedure or a cell re-selection procedure to obtain system information (1f-15). For example, the system information may refer to one or more SIBx that are defined / introduced for NR V2X sidelink communication and contain NR V2X sidelink configuration information, such as MIB1, SIB1, SIB2, SIB3, SIB4, SIB5, SIB21, SIB26. The cell camped on may be referred to as a Serving cell (hereinafter SCell) or a Primary cell (hereinafter PCell).

[0123] Specifically, if the SIB1 (SystemInformationBlockType1) received from the cell (Scell ​​or PCell) (1f-03) in step 1f-15 indicates that the aforementioned SIBx exists via the SchedulingInfoList, the RRC idle mode or RRC disabled mode terminal can acquire the SIBx. Alternatively, if a valid SIBx is not stored, the terminal (1f-01) can acquire the SIBx. When the base station (1f-03) broadcasts the SIBx, the SIBx may optionally include sl-V2X-ConfigCommon. For example, sl-V2X-ConfigCommon may include at least one of 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, threshS-RSSI-CBR. Additionally, SIBx may include sidelink radio bearer configuration information (sl-RadioBearerConfigList) and sidelink RLC bearer configuration information (sl-RLC-BearerConfigList) used for sidelink communication. Each sl-RadioBearerConfig may include one or more SL-QoS-Profiles. Each SL-QoS-Profile may include at least one of the following parameters.

[0124] - PQI Information

[0125] - Standardized PQI value

[0126] - Non-standardized PQI value

[0127] - Non-standardized QoS parameter values. Examples may include sl-ResourceType, sl-PriorityLevel, sl-PacketDelayBudget, sl-PacketErrorRate, sl-AveragingWindow, sl-MaxDataDataBurstVolume, etc.

[0128] - An indicator that determines whether to report non-standardized QoS parameter values ​​for non-standardized PQI values

[0129] - An indicator to apply GFBR (Guaranteed Flow Bit Rate) for Unicast

[0130] - An indicator to apply MFBR (Maximum Flow Bit Rate) for unicast

[0131] - Range value for groupcast

[0132] The terminal and the base station may know each other the mapping information between the Standardized PQI and QoS characteristics (see [Table 1]). Additionally, if the base station includes the above Non-standardized PQI values, the terminal and the base station may know each other the mapping information between the Non-standardized PQI and QoS characteristics.

[0133] [Table 1]: Standardized PQI to QoS characteristics mapping

[0134]

[0135] In step 1f-20, a packet for transmitting NR V2X sidelink communication may be generated or arrived and configured to perform NR V2X sidelink communication. It may also be instructed to perform NR V2X sidelink communication at a specific frequency.

[0136] In step 1f-25, upper layer devices can set PC5 QoS Profile(s) (e.g., PQI) for a packet and pass the packet and the PC5 QoS Profile(s) for it to the AS layer device.

[0137] In step 1f-30, the AS layer device can determine whether sidelink bearer configuration information for the PC5 QoS Profile(s) for the packet received in step 1f-25 is in the SIBx received in step 1f-15.

[0138] In step 1f-35, if the sidelink bearer configuration information for the PC5 QoS Profile(s) for the packet received in step 1f-25 is included in the SIBx received in step 1f-15, the terminal (1f-01) can establish an SLRB. If the above information is not included in the SIBx, the terminal (1f-01) may establish an SLRB or perform a procedure to establish / restart an RRC connection with the base station based on the information pre-configured in step 1f-05.

[0139] In step 1f-40, the terminal (1f-01) can perform NR V2X sidelink communication with another terminal (1f-02) through the SLRB established in step 1f-35. NR V2X sidelink communication can be performed via broadcast, groupcast, or unicast.

[0140] In step 1f-45, the RRC idle mode terminal may transmit an RRC connection establishment request message to the base station (1f-03) to perform an RRC connection establishment procedure with the base station (1f-03). In step 1f-50, the base station (1f-03) may transmit an RRC connection setup message to the RRC idle mode terminal (1f-01). Upon receiving the RRC connection setup message, the terminal (1f-01) may transition to the RRC connection mode (1f-51) after applying the setup information included in the message. Then, the terminal (1f-01) may transmit an RRC connection setup completion message (1f-55) to the base station (1f-03). The RRC connection setup completion message may include QoS information related to the SLRB(s) established and used in the RRC idle mode. For example, the RRC connection setup completion message may include at least one of the following information related to the SLRB(s) established and used in RRC idle mode.

[0141] - One or more destination identities

[0142] - Cast type based on individual destination (e.g., whether SLRB(s) established and used in RRC idle mode were used for unicast, broadcast, or groupcast)

[0143] - QoS profile information for one or more QoS flows. For example, each QoS flow identifier (sl-QoS-FlowIdentity) and sl-QoS-Profile information for it may be included. In this case, if a non-standardized PQI value is included in SIBx in the sl-QoS-Profile, the terminal may include only the non-standardized PQI value and not include specific QoS parameters for the non-standardized PQI.

[0144] - An indicator or SLRB identifier indicating whether to continue using the SLRB established and used in RRC idle mode.

[0145] - List of sidelink transmission frequencies of interest (sl-TxInterestedFreqList)

[0146] - An indicator or SLRB identifier indicating whether to continue using the SLRB established and used in RRC idle mode.

[0147] In step 1f-45, the RRC disabled mode terminal (1f-01) may transmit an RRC connection resume request message (RRCConnectionResumeRequest message) to the base station (1f-03) to perform an RRC connection resume procedure with the base station (1f-03). In step 1f-50, the base station (1f-03) may transmit an RRC connection resume message (RRCConnectionResume message) to the RRC disabled mode terminal (1f-01). Upon receiving the RRC connection resume message, the terminal (1f-01) may transition to an RRC connection mode (1f-51) after applying the configuration information included in the message. Then, the terminal (1f-01) may transmit an RRC connection resume completion message (RRCConnectionResumeComplete message) (1f-55) to the base station (1f-03). The RRC connection resumption completion message may include QoS information related to the SLRB(s) established and used in RRC disabled mode. For example, it may include at least one of the following information related to the SLRB(s) established and used in RRC disabled mode.

[0148] - One or more destination identities

[0149] - Cast type based on individual destination (e.g., whether SLRB(s) established and used in RRC disabled mode were used for unicast, broadcast, or groupcast)

[0150] - QoS profile information for one or more QoS flows. For example, each QoS flow identifier (sl-QoS-FlowIdentity) and sl-QoS-Profile information for it may be included. In this case, if a non-standardized PQI value is included in SIBx in the sl-QoS-Profile, the terminal may include only the non-standardized PQI value and not include specific QoS parameters for the non-standardized PQI.

[0151] - Indicator or SLRB identifier for whether to continue using the SLRB established and used in RRC disabled mode

[0152] - List of sidelink transmission frequencies of interest (sl-TxInterestedFreqList)

[0153] - Indicator or SLRB identifier for whether to continue using the SLRB established and used in RRC disabled mode

[0154] In step 1f-60, the RRC connection mode terminal (1f-01) may transmit a Sidelink Terminal Information message to the base station (1f-03). In step 1f-55, if the aforementioned QoS information is not included in the RRC connection setup completion message or the RRC connection resumption completion message, step 1f-60 may be performed. The Sidelink Terminal Information message may include QoS information related to the SLRB(s) established and used in RRC idle mode or RRC disabled mode. For example, the Sidelink Terminal Information message may include at least one of the following information related to the SLRB(s) established and used in RRC idle mode or RRC disabled mode.

[0155] - One or more destination identities

[0156] - Cast type based on individual destination (e.g., whether SLRB(s) established and used in RRC disabled mode were used for unicast, broadcast, or groupcast)

[0157] - QoS profile information for one or more QoS flows. For example, each QoS flow identifier (sl-QoS-FlowIdentity) and sl-QoS-Profile information for it may be included. In this case, if a non-standardized PQI value is included in SIBx in the sl-QoS-Profile, the terminal may include only the non-standardized PQI value and not include specific QoS parameters for the non-standardized PQI.

[0158] - Indicator or SLRB identifier for whether to continue using the SLRB established and used in RRC disabled mode

[0159] - List of sidelink transmission frequencies of interest (sl-TxInterestedFreqList)

[0160] - Indicator or SLRB identifier for whether to continue using the SLRB established and used in RRC disabled mode

[0161] In step 1f-65, the base station (1f-03) may transmit an RRC Connection Reconfiguration message to an RRC connection mode terminal (1f-01) including at least one of the following information.

[0162] - SLRB configuration information related to QoS information included in step 1f-55 or 1f-60

[0163] - Indicator for whether to continue using SLRB configuration information established in RRC idle mode or RRC disabled mode

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

[0165] - Resource pool configuration information based on resource mode

[0166] In step 1f-67, based on the message received in step 1f-65, the terminal (1f-01) can determine whether to continue using the SLRB established and used in RRC idle mode or RRC disabled mode. For example, if the RRCConnectionReconfiguration message contains an indicator that it is acceptable to continue using it, or if it contains the same information as the SLRB established and used in RRC idle mode or RRC disabled mode, the RRC connected mode terminal (1f-01) can continue using the previously used SLRB to perform NR V2X communication with another terminal (1f-02). If the message received in step 1f-65 contains SLRB configuration information that was not established in RRC idle mode or RRC disabled mode, the RRC connected mode terminal can establish a new SLRB and perform NR V2X communication with another terminal (1f-02). If terminal (1f-01) establishes a new SLRB and is performing unicast communication with another terminal (1f-02), terminal (1f-01) can send a PC5 RRC message containing new SLRB setup information to the other terminal (1f-02).

[0167] In step 1f-70, the terminal (1f-01) can send an RRCConnectionReconfigurationComplete message to the base station (1f-03) and perform NR V2X SL with another terminal (1f-02) (1f-75).

[0168] In step 1f-80, if a terminal (1f-01) transmitting and receiving data in RRC connection mode does not transmit or receive data for a certain reason or for a certain period of time, the base station (1f-03) may transmit an RRC connection release message (RRCConnectionRelease message) to cause the terminal (1f-01) to switch to RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE). The message may include a timer value or an element of SLRB setting information that allows continued use, indicating whether the SLRB used in RRC connection mode can be continued or released. Upon receiving the message, the terminal (1f-01) that has transitioned to RRC idle mode or RRC inactive mode may determine whether to continue using or release the SLRB used with another terminal (1f-02) based on the information included in the RRC connection release message. If a timer value is included in the message, the terminal (1f-01) may start the timer and apply the information included in the RRC connection release message. That is, the terminal (1f-01) may not apply the SLRB setting information included in the system information.

[0169] FIG. 1g is a flowchart illustrating a method for connecting a terminal performing NR V2X sidelink communication to an NR base station according to one embodiment of the present disclosure.

[0170] Specifically, referring to FIG. 1g, a method is shown for reporting the established SLRB to the NR base station when a terminal supporting NR V2X sidelink communication establishes a Sidelink Radio Bearer (hereinafter SLRB) in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE) and switches to RRC connected mode (RRC_CONNECTED) with the NR base station while performing NR V2X sidelink communication.

[0171] A terminal according to one embodiment of the present disclosure may refer to a vehicle terminal or a pedestrian terminal. The terminal may support LTE V2X sidelink communication or NR V2X sidelink communication. An NR base station according to one embodiment of the present disclosure may periodically broadcast system information related to LTE V2X sidelink configuration information or system information related to NR V2X sidelink configuration information, or signal in an on-demand manner.

[0172] Referring to FIG. 1g, a terminal (1g-01) capable of NR V2X sidelink communication can receive parameters used for NR sidelink communication from a core network in advance (1g-05). The information in advance can be referred to as SL-PreConfigurationNR. SL-PreConfigurationNR may include a frequency list used for sidelink communication (sl-PreconfigFreqInfoList), an anchor carrier frequency list for each wireless connection (sl-PreconfigNR-AnchorCarrierFreqList, sl-PreconfigEUTRA-AnchorCarrierFreqList), sidelink radio bearer configuration information used for sidelink communication (sl-RadioBearerPreConfigList), and sidelink RLC bearer configuration information (sl-RLC-BearerPreConfigList). sl-RadioBearerPReConfigList may include mapping information for PC5 QoS Profiles for each SLRB.

[0173] The terminal (1g-01) may be in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE) as it does not establish an RRC connection with the base station (1g-03) (1g-10).

[0174] A terminal (1g-01) in RRC idle mode or RRC disabled mode can find a suitable NR cell and camp on it through a cell selection procedure or a cell re-selection procedure to obtain system information (1g-15). For example, the system information may refer to one or more SIBx that are defined / introduced for NR V2X sidelink communication and contain NR V2X sidelink configuration information, such as MIB1, SIB1, SIB2, SIB3, SIB4, SIB5, SIB21, SIB26. The cell camped on may be referred to as a Serving cell (hereinafter SCell) or a Primary cell (hereinafter PCell).

[0175] Specifically, in step 1g-15, if the SIB1 (SystemInformationBlockType1) received from the cell (Scell ​​or PCell) (1g-03) indicates through the SchedulingInfoList that the aforementioned SIBx exists, the RRC idle mode or RRC disabled mode terminal (1g-01) can acquire the SIBx. Alternatively, if a valid SIBx is not stored, the terminal (1g-01) can acquire the SIBx. When the base station (1g-03) broadcasts the SIBx, the SIBx may optionally include sl-V2X-ConfigCommon. sl-V2X-ConfigCommon may include at least one of 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 sidelink radio bearer configuration information (sl-RadioBearerConfigList) and sidelink RLC bearer configuration information (sl-RLC-BearerConfigList) used for sidelink communication. Each sl-RadioBearerConfig may include one or more SL-QoS-Profiles. Each SL-QoS-Profile may include at least one of the following parameters.

[0176] - PQI Information

[0177] - Standardized PQI value

[0178] - Non-standardized PQI value

[0179] - Non-standardized QoS parameter values. Examples may include sl-ResourceType, sl-PriorityLevel, sl-PacketDelayBudget, sl-PacketErrorRate, sl-AveragingWindow, sl-MaxDataDataBurstVolume, etc.

[0180] - An indicator that determines whether to report non-standardized QoS parameter values ​​for non-standardized PQI values

[0181] - Indicator to apply GFBR (Guaranteed Flow Bit Rate) for Unicast

[0182] - An indicator to apply MFBR (Maximum Flow Bit Rate) for unicast

[0183] - Range value for groupcast

[0184] The mapping information between the standardized PQI and QoS characteristics (see [Table 2]) may be known to the terminal (1g-01) and the base station (1g-03). Additionally, if the base station (1g-03) includes non-standardized PQI values, the terminal (1g-01) and the base station (1g-03) may be known to each other.

[0185] [Table 2]: Standardized PQI to QoS characteristics mapping

[0186]

[0187] In the 1g-20 stage, a packet for transmitting NR V2X sidelink communication may be generated or arrived and configured to perform NR V2X sidelink communication. It may also be instructed to perform NR V2X sidelink communication at a specific frequency.

[0188] In the 1g-25 stage, upper layer devices can set PC5 QoS Profile(s) (e.g., PQI) for a packet and transmit the packet and the PC5 QoS Profile(s) for it to the AS layer device.

[0189] In step 1g-30, the AS layer device can determine whether sidelink bearer configuration information for PC5 QoS Profile(s) for the packet received in step 1g-25 is in the SIBx received in step 1g-15.

[0190] In step 1g-35, if the sidelink bearer configuration information for the PC5 QoS Profile(s) for the packet received in step 1g-25 is included in the SIBx received in step 1g-15, the SLRB may be established. If the information is not included in the SIBx, the SLRB may be established based on the information pre-configured in step 1g-05, or a procedure to establish / restart the RRC connection with the base station (1g-03) may be performed.

[0191] In step 1g-40, the terminal (1g-01) can perform NR V2X sidelink communication with another terminal (1g-02) through the SLRB established in step 1g-35. NR V2X sidelink communication can be performed via broadcast, groupcast, or unicast.

[0192] In step 1g-45, the RRC idle mode terminal (1g-01) may transmit an RRC connection establishment request message (RRCSetupRequest message) to the base station (1g-03) to perform an RRC connection establishment procedure with the base station (1g-03). In step 1g-50, the base station (1g-03) may transmit an RRC connection establishment message (RRCSetup message) to the RRC idle mode terminal (1g-01). Upon receiving the RRC connection establishment message, the terminal (1g-01) may transition to an RRC connection mode (1g-51) after applying the configuration information included in the message. Then, the terminal (1g-01) may transmit an RRC connection establishment completion message (RRCSetupComplete message) to the base station (1g-03) (1g-55). The above RRC connection setup completion message may include QoS information related to the SLRB(s) established and used in RRC idle mode. For example, the RRC connection setup completion message may include at least one of the following information related to the SLRB(s) established and used in RRC idle mode.

[0193] - One or more destination identities

[0194] - Cast type based on individual destination (e.g., whether SLRB(s) established and used in RRC idle mode were used for unicast, broadcast, or groupcast)

[0195] - QoS profile information for one or more QoS flows. For example, each QoS flow identifier (sl-QoS-FlowIdentity) and sl-QoS-Profile information for it may be included. In this case, if a non-standardized PQI value is included in SIBx in the sl-QoS-Profile, the terminal may include only the non-standardized PQI value and not include specific QoS parameters for the non-standardized PQI.

[0196] - An indicator or SLRB identifier indicating whether to continue using the SLRB established and used in RRC idle mode.

[0197] - List of sidelink transmission frequencies of interest (sl-TxInterestedFreqList)

[0198] - An indicator or SLRB identifier indicating whether to continue using the SLRB established and used in RRC idle mode.

[0199] In step 1g-45, the RRC disabled mode terminal (1g-01) may transmit an RRC connection resume request message (RRCResumeRequest message or RRCResumeRequest1 message) to the base station (1g-03) to perform an RRC connection resume procedure with the base station (1g-03). In step 1g-50, the base station (1g-03) may transmit an RRC connection resume message (RRCResume message) to the RRC disabled mode terminal (1g-01). Upon receiving the RRC connection resume message, the terminal (1g-01) may transition to an RRC connection mode (1g-51) after applying the configuration information included in the message. Then, the terminal (1g-01) may transmit an RRC connection resume completion message (RRCResumeComplete message) to the base station (1g-03) (1g-55). The RRC connection resumption completion message may include QoS information related to the SLRB(s) established and used in RRC disabled mode. For example, the RRC connection resumption completion message may include at least one of the following information related to the SLRB(s) established and used in RRC disabled mode.

[0200] - One or more destination identities

[0201] - Cast type based on individual destination (e.g., whether SLRB(s) established and used in RRC disabled mode were used for unicast, broadcast, or groupcast)

[0202] - QoS profile information for one or more QoS flows. For example, each QoS flow identifier (sl-QoS-FlowIdentity) and sl-QoS-Profile information for it may be included. In this case, if a non-standardized PQI value is included in SIBx in the sl-QoS-Profile, the terminal may include only the non-standardized PQI value and not include specific QoS parameters for the non-standardized PQI.

[0203] - Indicator or SLRB identifier for whether to continue using the SLRB established and used in RRC disabled mode

[0204] - List of sidelink transmission frequencies of interest (sl-TxInterestedFreqList)

[0205] - Indicator or SLRB identifier for whether to continue using the SLRB established and used in RRC disabled mode

[0206] In step 1g-60, the RRC connection mode terminal (1g-01) may transmit a Sidelink Terminal Information message to the base station (1g-03). In step 1g-55, if the aforementioned QoS information is not included in the RRC connection setup completion message or the RRC connection resumption completion message, step 1g-60 may be performed. The Sidelink Terminal Information message may include QoS information related to the SLRB(s) established and used in RRC idle mode or RRC disabled mode. For example, the Sidelink Terminal Information message may include at least one of the following information related to the SLRB(s) established and used in RRC idle mode or RRC disabled mode.

[0207] - One or more destination identities

[0208] - Cast type based on individual destination (e.g., whether SLRB(s) established and used in RRC disabled mode were used for unicast, broadcast, or groupcast)

[0209] - QoS profile information for one or more QoS flows. For example, each QoS flow identifier (sl-QoS-FlowIdentity) and sl-QoS-Profile information for it may be included. In this case, if a non-standardized PQI value is included in SIBx in the sl-QoS-Profile, the terminal may include only the non-standardized PQI value and not include specific QoS parameters for the non-standardized PQI.

[0210] - Indicator or SLRB identifier for whether to continue using the SLRB established and used in RRC disabled mode

[0211] - List of sidelink transmission frequencies of interest (sl-TxInterestedFreqList)

[0212] - Indicator or SLRB identifier for whether to continue using the SLRB established and used in RRC disabled mode

[0213] In step 1g-65, the base station (1g-03) may transmit an RRC connection mode terminal (1g-01) including at least one of the following information in an RRCReconfiguration message.

[0214] - SLRB setting information related to QoS information included in step 1g-55 or step 1g-60

[0215] - Indicator for whether to continue using SLRB configuration information established in RRC idle mode or RRC disabled mode

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

[0217] - Resource pool configuration information based on resource mode

[0218] In step 1g-67, based on the message received in step 1g-65, the terminal (1g-01) can determine whether to continue using the SLRB established and used in RRC idle mode or RRC disabled mode. For example, if an indicator indicating that it may continue to be used is included in the RRCReconfiguration message, or if the same information as the SLRB established and used in RRC idle mode or RRC disabled mode is included, the RRC connected mode terminal can continue using the previously used SLRB to perform NR V2X communication with another terminal (1g-02). If SLRB configuration information that was not established in RRC idle mode or RRC disabled mode is included in the message received in step 1g-65, the RRC connected mode terminal can establish a new SLRB and perform NR V2X communication with another terminal (1g-02). If terminal (1g-01) establishes a new SLRB and is performing unicast communication with another terminal (1g-02), terminal (1g-01) can send a PC5 RRC message containing new SLRB configuration information to the other terminal (1g-02).

[0219] In step 1g-70, the terminal (1g-01) can transmit an RRCReconfigurationComplete message to the base station (1g-03) and perform NR V2X SL with another terminal (1g-02) (1g-75).

[0220] In step 1g-80, if a terminal (1g-01) transmitting and receiving data in RRC connection mode does not transmit or receive data for a certain reason or for a certain period of time, the base station (1g-03) may transmit an RRC connection release message (RRCnRelease message) to cause the terminal (1g-01) to switch to RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE). The message may include a timer value or an element of SLRB setting information that allows continued use, indicating whether the SLRB used in RRC connection mode can be continued or released. Upon receiving the message, the terminal (1g-01) that has transitioned to RRC idle mode or RRC inactive mode may determine whether to continue using or release the SLRB used with another terminal (1g-02) based on the information included in the RRC connection release message. If the message includes a timer value, the terminal (1g-01) may start the timer and apply the information included in the RRC connection release message. That is, the terminal (1g-01) may not apply the SLRB setting information included in the system information.

[0221] FIG. 1h is a flowchart illustrating a method for connecting a terminal performing NR V2X sidelink communication to an NR base station according to one embodiment of the present disclosure.

[0222] Specifically, referring to FIG. 1h, this is a diagram illustrating the operation of a terminal that reports the established SLRB to an NR base station when the terminal supporting NR V2X sidelink communication establishes a Sidelink Radio Bearer (hereinafter SLRB) in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE) and switches to RRC connected mode (RRC_CONNECTED) with an NR base station while performing NR V2X sidelink communication.

[0223] Referring to FIG. 1h, a terminal supporting NR V2X sidelink communication may be in RRC idle mode (RRC_IDLE) or RRC disabled mode (RRC_INACTIVE) (1h-05)

[0224] In step 1h-10, the terminal may obtain system information containing V2X sidelink communication configuration information through a cell selection or cell re-selection procedure. The system information may include SLRB configuration information containing SL QoS Profile(s). The SL QoS Profile(s) may include at least one of the following information.

[0225] - PQI Information

[0226] - Standardized PQI value

[0227] - Non-standardized PQI value

[0228] - Non-standardized QoS parameter values. Examples may include sl-ResourceType, sl-PriorityLevel, sl-PacketDelayBudget, sl-PacketErrorRate, sl-AveragingWindow, sl-MaxDataDataBurstVolume, etc.

[0229] - An indicator that determines whether to report non-standardized QoS parameter values ​​for non-standardized PQI values

[0230] - Indicator to apply GFBR (Guaranteed Flow Bit Rate) for Unicast

[0231] - An indicator to apply MFBR (Maximum Flow Bit Rate) for unicast

[0232] - Range value for groupcast

[0233] In steps 1h-15, the terminal may receive service data or a request for transmitting NR V2X sidelink communication from a V2X application device. If there is no PC5 QoS Flow matching the service data or request, the terminal may determine PC5 QoS parameters and generate a PC5 QoS Flow.

[0234] In step 1h-20, the terminal can determine whether SLRB setting information for the PC5 QoS profile is in the system information for the PC5 QoS Flow generated above.

[0235] In step 1h-25, the terminal can perform an RRC connection establishment procedure or an RRC connection resumption procedure with the base station.

[0236] In step 1h-30, the terminal can establish an RRC connection with the base station and transition to RRC connection mode (RRC_CONNECTED).

[0237] In step 1h-35, the terminal may send an RRC message to the base station to request SLRB setup information. The RRC message may be one of an RRC connection setup complete message, an RRC connection resumption complete message, or a sidelink terminal information message.

[0238] In step 1h-40, the terminal can establish one or more SLRBs to perform V2X sidelink communication.

[0239] In step 1h-45, the terminal can perform an RRC connection establishment procedure or an RRC connection resumption procedure with the base station.

[0240] In step 1h-50, the terminal can establish an RRC connection with the base station and transition to RRC connection mode (RRC_CONNECTED).

[0241] In step 1h-55, the terminal can determine whether the established SLRB is based on standardized PQI in step 1h-40.

[0242] In steps 1h-60, the terminal may transmit an RRC message containing a standardized PQI. The RRC message may be one of an RRC connection establishment completion message, an RRC connection resumption completion message, or a sidelink terminal information message. At this time, the terminal may include standardized PQI values ​​in the message for each cast type, destination, and QoS flow.

[0243] In step 1h-65, the terminal can determine whether non-standardized PQI values ​​are included in the system information or whether the system information includes an indicator that indicates whether non-standardized QoS parameters do not need to be reported.

[0244] In step 1h-70, the terminal may transmit an RRC message containing a non-standardized PQI. The RRC message may be one of an RRC connection establishment completion message, an RRC connection resumption completion message, or a sidelink terminal information message. At this time, the terminal may include non-standardized PQI values ​​for each cast type, destination, and QoS flow in the message.

[0245] In step 1h-75, the terminal may transmit an RRC message containing non-standardized QoS parameters. Non-standardized QoS parameters may refer to at least one of sl-ResourceType, sl-PriorityLevel, sl-PacketDelayBudget, sl-PacketErrorRate, sl-AveragingWindow, and sl-MaxDataDataBurstVolume. The RRC message may be one of an RRC connection establishment completion message, an RRC connection resumption completion message, or a sidelink terminal information message. In this case, the terminal may include the non-standardized QoS parameters in the message according to cast type, destination, and QoS flow.

[0246] FIG. 1i illustrates the structure of a terminal according to one embodiment of the present disclosure.

[0247] The terminal may include a radio frequency (RF) processing unit (1i-10), a baseband processing unit (1i-20), a storage unit (1i-30), and a control unit (1i-40).

[0248] An RF processing unit (1i-10) according to one embodiment of the present disclosure can perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1i-10) can up-convert a baseband signal provided by a baseband processing unit (1i-20) into an RF band signal and transmit it through an antenna, and down-convert an RF band signal received through an antenna into a baseband signal. For example, the RF processing unit (1i-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc.

[0249] In FIG. 1i, only one antenna is shown, but the terminal may include multiple antennas.

[0250] Additionally, the RF processing unit (1i-10) may include multiple RF chains. Furthermore, the RF processing unit (1i-10) may perform beamforming. For beamforming, the RF processing unit (1i-10) may adjust the phase and magnitude of each of the signals transmitted and received through multiple antennas or antenna elements. Additionally, the RF processing unit (1i-10) may perform MIMO (Multiple-Input Multiple-Output) and may receive multiple layers when performing MIMO operation. The RF processing unit (1i-10) may perform receiving beam sweeping by appropriately setting multiple antennas or antenna elements according to the control of the control unit (1i-40), or adjust the direction and beam width of the receiving beam so that the receiving beam is coordinated with the transmitting beam.

[0251] The baseband processing unit (1i-20) can perform conversion functions between baseband signals and bit sequences according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (1i-20) can generate complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (1i-20) can restore the received bit sequence through demodulation and decoding of the baseband signal provided by the RF processing unit (1i-10). For example, in the case of following the orthogonal frequency division multiplexing (OFDM) method, when transmitting data, the baseband processing unit (1i-20) can generate complex symbols by encoding and modulating the transmitted bit sequence, map the complex symbols to subcarriers, and then construct OFDM symbols through inverse fast Fourier transform (IFFT) operations and cyclic prefix (CP) insertion. Additionally, upon receiving data, the baseband processing unit (1i-20) can divide the baseband signal provided by the RF processing unit (1i-10) into OFDM symbol units, restore the signals mapped to subcarriers through a fast Fourier transform (FFT) operation, and then restore the received bit sequence through demodulation and decoding.

[0252] The baseband processing unit (1i-20) and the RF processing unit (1i-10) can transmit and receive signals as described above. Accordingly, the baseband processing unit (1i-20) and the RF processing unit (1i-10) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, or a communication unit. Furthermore, at least one of the baseband processing unit (1i-20) and the RF processing unit (1i-10) may include a plurality of communication modules to support a plurality of different wireless access technologies. Additionally, at least one of the baseband processing unit (1i-20) and the RF processing unit (1i-10) may include different communication modules to process signals of different frequency bands. For example, different wireless access technologies may include LTE networks, NR networks, etc. In addition, different frequency bands may include super high frequency (SHF) bands (e.g., 2.2 GHz, 2 GHz) and millimeter wave (e.g., 60 GHz) bands.

[0253] The storage unit (1i-30) can store data such as basic programs, application programs, and setting information for the operation of the terminal. The storage unit (1i-30) can provide the stored data upon a request from the control unit (1i-40).

[0254] The control unit (1i-40) can control the overall operations of the terminal. For example, the control unit (1i-40) can transmit and receive signals through the baseband processing unit (1i-20) and the RF processing unit (1i-10). Additionally, the control unit (1i-40) can write and read data to and from the storage unit (1i-40). To this end, the control unit (1i-40) may include at least one processor. For example, the control unit (1i-40) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as applications.

[0255] FIG. 1j illustrates the structure of a base station in one embodiment of the present disclosure.

[0256] A base station according to one embodiment of the present disclosure may include one or more transmission reception points (TRPs).

[0257] A base station according to one embodiment of the present disclosure may include an RF processing unit (1j-10), a baseband processing unit (1j-20), a backhaul communication unit (1j-30), a storage unit (1j-40), and a control unit (1j-50).

[0258] The RF processing unit (1j-10) can perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1j-10) can up-convert a baseband signal provided by the baseband processing unit (1j-20) into an RF band signal and transmit it through an antenna, and down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1j-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.

[0259] In Fig. 1j, only one antenna is shown, but the base station may include multiple antennas.

[0260] Additionally, the RF processing unit (1j-10) may include a plurality of RF chains. Furthermore, the RF processing unit (1j-10) may perform beamforming. For beamforming, the RF processing unit (1j-10) may adjust the phase and magnitude of each of the signals transmitted and received through a plurality of antennas or antenna elements. The RF processing unit (1j-10) may perform down-MIMO operation by transmitting one or more layers.

[0261] The baseband processing unit (1j-20) can perform a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (1j-20) can generate complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (1j-20) can restore the received bit sequence through demodulation and decoding of the baseband signal provided by the RF processing unit (1j-10). For example, in the case of following the OFDM method, when transmitting data, the baseband processing unit (1j-20) can generate complex symbols by encoding and modulating the transmitted bit sequence, map the complex symbols to subcarriers, and then construct OFDM symbols through IFFT operation and CP insertion. Additionally, upon receiving data, the baseband processing unit (1j-20) can divide the baseband signal provided by the RF processing unit (1j-10) into OFDM symbol units, restore the signals mapped to subcarriers through FFT operations, and then restore the received bit sequence through demodulation and decoding. The baseband processing unit (1j-20) and the RF processing unit (1j-10) can transmit and receive signals as described above.

[0262] Accordingly, the baseband processing unit (1j-20) and the RF processing unit (1j-10) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, a communication unit, or a wireless communication unit.

[0263] The communication unit (1j-30) can provide an interface for communicating with other nodes within the network. That is, the communication unit (1j-30) can convert a bit sequence transmitted from the main base station to other nodes, such as an auxiliary base station or a core network, into a physical signal, and can convert a physical signal received from other nodes into a bit sequence.

[0264] The storage unit (1j-40) can store data such as basic programs, application programs, and configuration information for the operation of the main station. In particular, the storage unit (1j-40) can store information regarding bearers assigned to connected terminals, measurement results reported from connected terminals, etc. Additionally, the storage unit (1j-40) can store information that serves as a criterion for determining whether to provide or disconnect multiple connections to the terminals. Furthermore, the storage unit (1j-40) can provide the stored data upon a request from the control unit (1j-50).

[0265] The control unit (1j-50) can control the overall operations of the main station. For example, the control unit (1j-50) can transmit and receive signals through the baseband processing unit (1j-20) and the RF processing unit (1j-10) or through the communication unit (1j-30). Additionally, the control unit (1j-50) can write and read data to and from the storage unit (1j-40). To this end, the control unit (1j-50) may include at least one processor.

[0266] Methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0267] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of this disclosure.

[0268] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0269] Additionally, the above program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

[0270] In the specific embodiments of the present disclosure described above, the components included in the invention are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, or even if a component is expressed in the singular form, it may be composed of a plural form.

[0271] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

Claim 1 A method for a terminal to perform sidelink communication in a wireless communication system, comprising: receiving system information including PQI information from a base station; wherein the PQI information includes an indicator indicating whether non-standardized PQI and non-standardized QoS parameters do not need to be reported; establishing a Sidelink Radio Bearer (SLRB) based on the system information; performing the sidelink communication based on the established SLRB; initiating a Radio Resource Control (RRC) connection procedure with the base station; identifying whether the indicator indicating whether non-standardized QoS parameters do not need to be reported is included in the system information when the established SLRB is based on the non-standardized PQI; and transmitting an RRC message to the base station including the non-standardized PQI associated with at least one non-standardized QoS characteristic when the indicator indicating whether non-standardized QoS parameters do not need to be reported is included in the system information. Claim 2 The method of claim 1, wherein the system information includes at least one QoS Profile, and the at least one QoS Profile includes at least one of the PQI information, an indicator indicating to apply GFBR (Guaranteed Flow Bit Rate), an indicator indicating to apply MFBR (Maximum Flow Bit Rate), or a Range. Claim 3 The method of claim 1, wherein the PQI information further comprises at least one of Standardized PQI or Non-standardized QoS parameters. Claim 4 A method according to claim 3, wherein, if the established SLRB is based on the Standardized PQI, the RRC message includes the Standardized PQI. Claim 5 delete Claim 6 In a terminal performing sidelink communication in a wireless communication system, a memory for storing at least one command; A terminal comprising at least one processor, wherein the at least one processor executes the at least one command to cause the terminal to: receive system information including PQI information from a base station, wherein the PQI information includes an indicator indicating whether non-standardized PQI and non-standardized QoS parameters do not need to be reported, establish a Sidelink Radio Bearer (SLRB) based on the system information, perform the sidelink communication based on the established SLRB, initiate a Radio Resource Control (RRC) connection procedure with the base station, identify whether the indicator indicating whether non-standardized QoS parameters do not need to be reported is included in the system information when the established SLRB is based on the non-standardized PQI, and, when the indicator indicating whether non-standardized QoS parameters do not need to be reported is included in the system information, transmit an RRC message to the base station containing the non-standardized PQI associated with at least one non-standardized QoS characteristic. Claim 7 A terminal according to claim 6, wherein the system information includes at least one QoS Profile, and the at least one QoS Profile includes at least one of the PQI information, an indicator indicating to apply GFBR (Guaranteed Flow Bit Rate), an indicator indicating to apply MFBR (Maximum Flow Bit Rate), or a Range. Claim 8 A terminal according to claim 6, wherein the PQI information further comprises at least one of Standardized PQI or Non-standardized QoS parameters. Claim 9 In claim 8, if the established SLRB is based on the Standardized PQI, the RRC message is a terminal including the Standardized PQI. Claim 10 delete Claim 11 A method performed by a base station in a wireless communication system, comprising the steps of: transmitting system information including PQI information to a terminal; wherein the PQI information includes an indicator indicating whether non-standardized PQI and non-standardized QoS parameters do not need to be reported; wherein a Sidelink Radio Bearer (SLRB) is established at the terminal based on the system information, sidelink communication is performed at the terminal based on the established SLRB, and a Radio Resource Control (RRC) connection procedure is initiated at the terminal with the base station; wherein, if the established SLRB is based on the non-standardized PQI, the terminal identifies whether the indicator indicating whether non-standardized QoS parameters do not need to be reported is included in the system information; and wherein, if the indicator indicating whether non-standardized QoS parameters do not need to be reported is included in the system information, the terminal receives an RRC message including the non-standardized PQI associated with at least one non-standardized QoS characteristic from the terminal. Claim 12 In a base station of a wireless communication system, a memory that stores at least one command; A base station comprising at least one processor, wherein the at least one processor executes the at least one command to cause the base station to: transmit system information including PQI information to a terminal, wherein the PQI information includes an indicator indicating whether non-standardized PQI and non-standardized QoS parameters do not need to be reported, wherein a Sidelink Radio Bearer (SLRB) is established at the terminal based on the system information, wherein sidelink communication is performed at the terminal based on the established SLRB, wherein a Radio Resource Control (RRC) connection procedure with the base station is initiated at the terminal, wherein if the established SLRB is based on the non-standardized PQI, the terminal identifies whether the indicator indicating whether non-standardized QoS parameters do not need to be reported is included in the system information, and wherein if the indicator indicating whether non-standardized QoS parameters do not need to be reported is included in the system information, the base station receives an RRC message from the terminal containing the non-standardized PQI associated with at least one non-standardized QoS characteristic.

Images