KR20210055225A - Method and apparatus for performing vehicle communication in wireless communication system - Google Patents

Abstract

A method for allowing a terminal to perform sidelink communication in a wireless communication system comprises the following steps of: obtaining system information including sidelink communication setting information; establishing a sidelink radio bearer (SLRB) based on the system information; performing the sidelink communication based on the established SLRB; and performing RRC connection with a base station based on the established SLRB. Therefore, the present invention can effectively provide a service.

Description

Method and device for performing vehicle communication in wireless communication system {METHOD AND APPARATUS FOR PERFORMING VEHICLE COMMUNICATION IN WIRELESS COMMUNICATION SYSTEM}

The present disclosure relates to a method and apparatus for performing vehicle communication in a wireless communication system, and more particularly, to a method and apparatus for controlling a PC5 QoS parameter for a non-standardized PQI for vehicle communication.

In order to meet the demand for wireless data traffic, which is explosively increasing due to the commercialization of 4G communication systems and the increase in multimedia services, an improved 5G communication system or pre-5G communication system is being developed. For this reason, the 5G communication system or the pre-5G communication system is called a communication system after a 4G network (Beyond 4G Network) or a system after an LTE system (Post LTE).

In order to increase the data rate, the 5G communication system is being considered for implementation in an ultra-high frequency (mmWave) band (eg, a 60 gigabyte (60 GHz) band). In order to mitigate the path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, 5G communication systems include beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO). ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed.

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

Meanwhile, the Internet is evolving from a human-centered network in which humans create and consume information, to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. IoE (Internet of Everything) technology, which combines IoT technology with big data processing technology through connection with cloud servers, etc., is also emerging. In order to implement IoT, technological elements such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, and security technology are required. , M2M), and MTC (Machine Type Communication) technologies are being studied. In the IoT environment, intelligent IT (Internet Technology) services that create new value in human life by collecting and analyzing data generated from connected objects can be provided. IoT is the field of smart home, smart building, smart city, smart car or connected car, smart grid, healthcare, smart home appliance, advanced medical service, etc. through the convergence and combination of existing IT (information technology) technology and various industries. Can be applied to.

Accordingly, various attempts have been made to apply a 5G communication system to an IoT network. For example, technologies such as sensor network, machine to machine (M2M), and machine type communication (MTC) are implemented by techniques such as beamforming, MIMO, and array antenna. There is. The application of a cloud radio access network (cloud RAN) as the big data processing technology described above can be said as an example of the convergence of 5G technology and IoT technology.

An embodiment of the present disclosure may provide a method and an apparatus for more effectively providing a service.

According to an embodiment of the present disclosure, a method of performing sidelink communication by a terminal in a wireless communication system includes: obtaining system information including sidelink communication setting information; Establishing a Sidelink Radio Bearer (SLRB) based on the system information; Performing the sidelink communication based on the established SLRB; And performing RRC connection with the base station based on the established SLRB.

According to an embodiment of the present disclosure, a service can be more effectively provided.

1A is a diagram illustrating a structure of an LTE system according to an embodiment of the present disclosure.
1B is a diagram illustrating a radio protocol structure in an LTE system according to an embodiment of the present disclosure.
1C is a diagram showing the structure of a next-generation mobile communication system according to an embodiment of the present disclosure.
1D is a diagram illustrating a radio protocol structure of a next-generation mobile communication system according to an embodiment of the present disclosure.
1E is a diagram illustrating V2X communication in a next-generation mobile communication system according to an embodiment of the present disclosure.
1F is a flowchart illustrating a method of connecting a terminal performing NR V2X sidelink communication with an LTE base station according to an embodiment of the present disclosure.
1G is a flowchart illustrating a method of connecting a terminal performing NR V2X sidelink communication with an NR base station according to an embodiment of the present disclosure.
1H is a flowchart illustrating a method of connecting a terminal performing NR V2X sidelink communication with an NR base station according to an embodiment of the present disclosure.
1I is a diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.
1J shows a structure of a base station according to an embodiment of the present disclosure.

With reference to the accompanying drawings will be described in detail the operating principle of the present invention. In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, a detailed description thereof will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to the intention or custom of users or operators. Therefore, the definition should be made based on the contents throughout the present specification.

In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, a detailed description thereof will be omitted. Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

A term for identifying an access node used in the following description, a term for network entities, a term for messages, a term for an interface between network objects, a term for various identification information And the like are illustrated for convenience of description. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having an equivalent technical meaning may be used.

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

1A is a diagram illustrating a structure of an LTE system according to an embodiment of the present disclosure.

Referring to Figure 1a, the radio access network of the LTE system is a next-generation base station (Evolved Node B, hereinafter ENB, Node B or base station) (1a-05, 1a-10, 1a-15, 1a-20) and MME (1a- 25, Mobility Management Entity) and S-GW (1a-30, Serving-Gateway). User Equipment (hereinafter referred to as UE or terminal) 1a-35 may access an external network through ENBs 1a-05 to 1a-20 and S-GW 1a-30.

In FIG. 1A, ENBs 1a-05 to 1a-20 may correspond to an existing Node B of a Universal Mobile Telecommunication System (UMTS) system. The ENB is connected to the UEs 1a-35 through a radio channel and can perform a more complex role than the existing Node B. In the LTE system, all user traffic including real-time services such as VoIP (Voice over IP) through the Internet protocol can be serviced through a shared channel. Accordingly, there is a need for a device for scheduling by collecting state information such as a buffer state, an available transmit power state, and a channel state of the UEs, and the ENBs 1a-05 to 1a-20 may be in charge of this.

One ENB can typically control multiple cells. For example, in order to implement a transmission rate of 100 Mbps, the LTE system may use, for example, an orthogonal frequency division multiplexing (OFDM) in a 20 MHz bandwidth as a radio access technology. In addition, an adaptive modulation and coding method (hereinafter referred to as AMC) for determining a modulation scheme and a channel coding rate according to a channel state of the terminal may be applied.

The S-GW 1a-30 is a device that provides a data bearer, and may create or remove a data bearer under the control of the MME 1a-25. The MME is a device responsible for various control functions as well as a mobility management function for a terminal, and can be connected to a plurality of base stations.

1B is a diagram illustrating a radio protocol structure in an LTE system according to an embodiment of the present disclosure.

Referring to Figure 1b, the radio protocol of the LTE system is PDCP (Packet Data Convergence Protocol 1b-05, 1b-40), RLC (Radio Link Control 1b-10, 1b-35), MAC (Medium Access Control 1b-15, 1b-30). PDCP (Packet Data Convergence Protocol) (1b-05, 1b-40) may be in charge of operations such as IP header compression/restore. The main functions of PDCP can be summarized as follows.

-Header compression and decompression (ROHC only)

-Transfer of user data

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

-Sequence rearrangement function-For split bearer in sequence rearrangement function (DC (for RLC AM only): PDCP PDU routing for transmission and PDCP PDU rearrangement for reception) (For split bearers in DC (only support for RLC AM) : PDCP PDU routing for transmission and PDCP PDU reordering for reception)

-Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM

-Retransmission function-Retransmission function (retransmission of PDCP SDU in handover for split bearer in DC and retransmission of PDCP PDU in PDCP data-recovery procedure for RLC AM) (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

-Encryption and decryption function (Ciphering and deciphering)

-Timer-based SDU discard in uplink.

Radio Link Control (hereinafter referred to as RLC) (1b-10, 1b-35) may perform an ARQ operation or the like by reconfiguring a PDCP packet data unit (PDU) to an appropriate size. The main functions of RLC can be summarized as follows.

-Data transmission function (Transfer of upper layer PDUs)

-ARQ function (Error Correction through ARQ (only for AM data transfer))

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

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

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

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

-Protocol error detection (only for AM data transfer)

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

-RLC re-establishment

The MACs 1b-15 and 1b-30 are connected to several RLC layer devices configured in one terminal, and may perform an operation of multiplexing RLC PDUs to MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC can be summarized as follows.

-Mapping between logical channels and transport channels

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

-Scheduling information reporting

-Error correction through HARQ

-Priority handling between logical channels of one UE

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

-MBMS service identification

-Transport format selection

-Padding function

The physical layer (1b-20, 1b-25) channel-codes and modulates upper layer data, converts it into OFDM symbols, and transmits it to the radio channel, or demodulates OFDM symbols received through the radio channel and decodes the channel and transmits it to the upper layer. You can perform the operation that you do.

1C is a diagram showing the structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

Referring to Figure 1c, as shown, the radio access network of the next-generation mobile communication system (hereinafter NR or 2g) is a next-generation base station (New Radio Node B, hereinafter NR gNB or NR base station) (1c-10) and NR CN (1c). -05, New Radio Core Network). The user terminal (New Radio User Equipment, hereinafter NR UE or terminal) 1c-15 may access an external network through the NR gNB 1c-10 and NR CN 1c-05.

In FIG. 1C, the NR gNB 1c-10 may correspond to an Evolved Node B (eNB) of an existing LTE system. The NR gNB is connected to the NR UE 1c-15 through a radio channel and can provide a service superior to that of the existing Node B. In a next-generation mobile communication system, all user traffic can be serviced through a shared channel. Accordingly, there is a need for an apparatus for scheduling by collecting state information such as a buffer state, an available transmit power state, and a channel state of the UEs, and the NR NB 1c-10 may be in charge of this. One NR gNB can typically control multiple cells. In the next-generation mobile communication system, in order to implement ultra-high-speed data transmission compared to the current LTE, it can have more than the existing maximum bandwidth, and additionally beamforming by using Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology. Technology can be applied. In addition, an adaptive modulation and coding method (hereinafter referred to as AMC) for determining a modulation scheme and a channel coding rate according to a channel state of the terminal may be applied.

The NR CN (1c-05) may 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 a mobility management function for a terminal, and is connected to a plurality of base stations. In addition, the next-generation mobile communication system can be interlocked with the existing LTE system, and the NR CN is connected to the MME (1c-25) through a network interface. The MME may be connected to the eNB (1c-30), which is an existing base station.

1D is a diagram illustrating a radio protocol structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

Referring to Figure 1d, the radio protocol of the next-generation mobile communication system is NR SDAP (1d-01, 1d-45), NR PDCP (1d-05, 1d-40), NR RLC (1d-10) in the terminal and the NR base station, respectively. , 1d-35), and NR MACs (1d-15, 1d-30).

The main functions of the NR SDAPs 1d-01 and 1d-45 may include some of the following functions.

-Transfer of user plane data

-Mapping between a QoS flow and a DRB for both DL and UL for uplink and downlink

-Marking QoS flow ID for uplink and downlink (marking QoS flow ID in both DL and UL packets)

-A function of mapping a reflective QoS flow to a data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

For SDAP layer devices, the UE can be configured with an RRC (Radio Resource Control) message to set whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device for each PDCP layer device, for each bearer, or for each logical channel. have. When the SDAP header is set, the terminal uses a non-access stratum (NAS) QoS reflection setting 1-bit indicator (NAS reflective QoS) and an access stratum (AS) QoS reflection setting 1-bit indicator (AS reflective QoS) of the SDAP header. It can be instructed to update or reconfigure mapping information for the uplink and downlink QoS flows and data bearers. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used as data processing priority, scheduling information, etc. to support smooth service.

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

-Header compression and decompression (ROHC only)

-Transfer of user data

-In-sequence delivery of upper layer PDUs

-Out-of-sequence delivery of upper layer PDUs

-PDCP PDU reordering for reception

-Duplicate detection of lower layer SDUs

-Retransmission of PDCP SDUs

-Encryption and decryption function (Ciphering and deciphering)

-Timer-based SDU discard in uplink.

In the above description, the reordering function of the NR PDCP device may mean a function of reordering PDCP PDUs received from a lower layer in order based on a PDCP sequence number (SN). The order rearrangement function of the NR PDCP device may include a function of delivering data to an upper layer in the order of rearrangement, and may include a function of immediately delivering data without considering the order, and the order of the PDCP PDUs lost by rearranging the order. A function of recording may be included, a function of reporting a status of lost PDCP PDUs to a transmitting side may be included, and a function of requesting retransmission of lost PDCP PDUs may be included.

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

-Transfer of upper layer PDUs

-In-sequence delivery of upper layer PDUs

-Out-of-sequence delivery of upper layer PDUs

-Error Correction through ARQ

-Concatenation, segmentation and reassembly of RLC SDUs

-Re-segmentation of RLC data PDUs

-Reordering of RLC data PDUs

-Duplicate detection

-Protocol error detection

-RLC SDU discard function

-RLC re-establishment

In the above description, in-sequence delivery of the NR RLC (1d-10, 1d-35) device may mean a function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. When one RLC SDU is originally divided into several RLC SDUs and received, the sequential delivery function of the NR RLC (1d-10, 1d-35) device may include a function of reassembling and delivering the same.

The sequential delivery function of the NR RLC (1d-10, 1d-35) device may include a function of rearranging the received RLC PDUs based on an RLC sequence number (SN) or a PDCP sequence number (SN). It may include a function to record the lost RLC PDUs by rearrangement, and may include a function to report the status of the lost RLC PDUs to the sender, and a function to request retransmission of the lost RLC PDUs. Can include.

The sequential delivery function of the NR RLC (1d-10, 1d-35) device may include a function of sequentially delivering only RLC SDUs prior to the lost RLC SDU to a higher layer when there is a lost RLC SDU. . In addition, the sequential delivery function of the NR RLC (1d-10, 1d-35) device is a function of sequentially delivering all RLC SDUs received before the timer starts if a predetermined timer expires even if there is a lost RLC SDU. And, even if there is a lost RLC SDU, if a predetermined timer has expired, it may include a function of sequentially delivering all RLC SDUs received so far to an upper layer.

The NR RLC (1d-10, 1d-35) device processes RLC PDUs in the order in which they are received regardless of the sequence number (Out-of sequence delivery) to the PDCP device regardless of the order (Out-of sequence delivery). -of sequence delivery) may be delivered. In the case of a segment, segments stored in a buffer or to be received in the future may be received and delivered to the NR PDCP (1d-05, 1d-40) devices.

(1d-10, 1d-35) When the device receives a segment, it receives the segments stored in the buffer or to be received in the future, reconstructs it into one complete RLC PDU, and then reconfigures it into one complete RLC PDU, and then NR PDCP (1d-05, 1d-40) can be delivered to the device. The NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or may be replaced with a multiplexing function of the NR MAC layer.

In the above description, out-of-sequence delivery of the NR RLC device may mean a function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of an order. The non-sequential delivery function of the NR RLC device may include a function of re-assembling and delivering when one RLC SDU is originally divided into multiple RLC SDUs and received. The non-sequential delivery function of the NR RLC device may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs, arranging the order, and recording the lost RLC PDUs.

The NR MACs 1d-15 and 1d-30 may be connected to several NR RLC layer devices configured in one terminal, and the main functions of the NR MAC may include some of the following functions.

-Mapping between logical channels and transport channels

-Multiplexing and demultiplexing of MAC SDUs (Multiplexing/demultiplexing of MAC SDUs)

-Scheduling information reporting

-Error correction through HARQ

-Priority handling between logical channels of one UE

-Priority handling between UEs by means of dynamic scheduling

-MBMS service identification

-Transport format selection

-Padding function

The NR PHY layer (1d-20, 1d-25) channel-codes and modulates upper layer data, makes it into OFDM symbols, and transmits it to the radio channel, or demodulates and channel-decodes OFDM symbols received through the radio channel to the upper layer. You can perform the transfer operation.

1E is a diagram illustrating V2X communication in a next-generation mobile communication system according to an embodiment of the present disclosure.

V2X (vehicle-to-everything) according to an embodiment of the present disclosure collectively refers to a communication technology through a vehicle and all interfaces, and according to the shape and communication components, V2V (vehicle-to-vehicle) , Vehicle-to-intrastructure (V2I), vehicle-to-pedestrian (V2P), and vehicle-to-network (V2N).

Referring to FIG. 1E, the base station 1e-01 includes at least one vehicle terminal 1e-05, 1e-10 and a pedestrian portable terminal 1e-15 located in a cell 1e-02 supporting V2X. can do. V2X can be supported through the Uu interface and/or the PC5 interface. When supporting V2X through the Uu interface, as an example, the vehicle terminals 1e-05 and 1e-10 have an uplink (UL)/Downlink (DL) between the base station 1e-01 and the vehicle terminal-base station, 1e-30, 1e-35) to perform cellular communication, or the pedestrian portable terminal (1e-15) to perform cellular communication using the uplink and downlink (UL/DL, 1e-40) between the pedestrian terminal and the base station. I can.

In addition, when V2X is supported through the PC5 interface, V2X sidelink (SL) communication may be performed using a terminal-to-terminal link (Sidelink (SL), 1e-20, 1e-25). As an example, the vehicle terminal 1e-05 present in the coverage of the base station (in coverage of E-UTRA/NR) is the other vehicle terminals 1e-10 and 1e-45 and/or the pedestrian portable terminal 1e-15, 1e-55) and sidelinks (SL, 1e-20, 1e-50, 1e-25, 1e-60), which are transport channels, can transmit and receive V2X packets. The V2X packet may be transmitted and received in a broadcast transmission type and/or a unicast and/or groupcast transmission type.

A terminal supporting V2X sidelink communication may transmit and receive V2X packets through a resource allocation mode (scheduled resource allocation or UE autnomous 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 in a dedicated scheduling scheme. This resource allocation mode can be efficient for interference management and/or management of a resource pool (dynamic allocation, semi-persistence transmission) because the base station can manage sidelink resources. When there is data to be transmitted to other terminal(s), the RRC connected mode terminal may inform the base station of the existence of data to be transmitted to the other terminal(s) by using an RRC message or a MAC control element (CE). As an example, the RRC message may be a SidelinkUEInformation, UEAssistanceInformation message, etc., and the MAC CE of a new format (including at least an indicator indicating that it is a buffer status report for V2X communication and information on the data size buffered for sidelink communication) Buffer status report MAC CE, etc. can be used.

In the UE autonomous resource selection (mode 2 and/or mode 4), the base station provides sidelink resource information/pool as system information and/or RRC message to the terminal supporting V2X sidelink communication, and the terminal provides the resource according to the set rule. This is the mode to select. As an example, the base station may provide sidelink resource information to the terminal by signaling SIBx to be newly defined for SIB21, SIB26, or NR V2X terminal. As an RRC message, for example, the base station may provide sidelink resource information by signaling an RRC connection reconfiguration message (RRCReconfiguration message) and/or a connection resumption message (RRCResume message) to the terminal to the terminal. In addition, UE autonomous resource selection helps the terminal to select the resource used for the sidelink through PC5-RRC message and/or MAC CE to other terminal(s), or transmits the sidelink through scheduling directly or indirectly. It is also possible to allocate resources used for. That is, the UE autonomous resource selection mode may refer to one or more of the following.

- UE autonomously selects sidelink resource for transmission

- UE assists sidelink resource selection for other UEs (UE assists sidelink resource selection for other UEs)

- UE configured with NR configures a grant for sidelink transmission (UE configured with NR is configured grant for sidelink transmission)

- UE schedules sidelink transmission of other UEs (UE schedules sidelink transmission of other UEs)

The terminal resource selection method may include zone mapping, sensing-based resource selection, random selection, configured grant-based resource selection, and the like.

A terminal supporting V2X sidelink communication may transmit and receive V2X packets based on a preset resource pool (Preconfiguration resource) included in SL-V2X-Preconfiguration, which is an information element (IE). For example, even if the terminal exists in the coverage of the base station, if the V2X sidelink communication cannot be performed based on the scheduled resource allocation and/or the UE autonomous resource selection mode for a certain reason, the terminal is preset in the IE, SL-V2X-Preconfiguration. (preconfigured) V2X sidelink communication can be performed through the sidelink transmission/reception resource pool. In addition, the vehicle terminal 1e-45 out of the coverage of the base station (out-of-coverage of E-UTRA/NR) is a side that is a transmission channel with the other vehicle terminal 1e-65 or the pedestrian portable terminal 1e-55. V2X sidelink communication may be performed based on the above-described sidelink preconfiguration resource through links (SL, 1e-70, 1e-75).

LTE V2X SL communication was designed with the main goal of basic safety service. That is, a terminal supporting LTE V2X SL communication is designed to provide basic safety services to all neighboring terminals supporting LTE V2X SL communication through a broadcast transmission type. Therefore, there is no need for a terminal to perform a process of establishing a session separately from another specific terminal or to perform a sidelink connection establishment procedure.

However, within the next-generation mobile communication (NR), V2X SL communication can be designed to provide not only basic safety services but also various and improved services (eg, autonomous driving service, platnooning service, remote driving service, in-vehicle infotainment). Therefore, in the case of NR V2X SL communication, it may be designed to support not only a broadcast transmission type but also a unicast and/or groupcast transmission type.

1F is a flowchart illustrating a method of connecting a terminal performing NR V2X sidelink communication with an LTE base station according to an embodiment of the present disclosure.

Specifically, referring to FIG.1f, a terminal supporting NR V2X sidelink communication establishes a sidelink radio bearer (SLRB) in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE) to NR V2X. A diagram showing a method of reporting an established SLRB to an LTE base station when switching to an RRC connection mode (RRC_CONNECTED) with an LTE base station while performing sidelink communication.

A terminal according to an 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. The LTE base station 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.

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

The terminal 1f-01 may be in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE) because the RRC connection with the base station 1f-03 is not established (1f-10).

The terminal 1f-01 in the RRC idle mode or the RRC inactive mode can obtain system information by searching for a suitable LTE cell and camping on through a cell selection procedure or a cell reselection procedure (1f -15). As an example, the system information is defined/introduced for MIB1, SIB1, SIB2, SIB3, SIB4, SIB5, SIB21, SIB26 or NR V2X sidelink communication to mean one or more SIBx including NR V2X sidelink configuration information. I can. The camp-on cell may be referred to as a serving cell (SCell) or a primary cell (PCell).

Specifically, if the above-described SIBx exists in the SIB1 (SystemInformationBlockType1) received from the cell (Scell or PCell) (1f-03) in step 1f-15 through the scheduling information list (SchedulingInfoList), RRC idle mode or RRC The inactive mode terminal may acquire SIBx. Or, if the SIBx in a valid state is not stored, the terminal 1f-01 may acquire the SIBx. When the base station 1f-03 broadcasts SIBx, the SIBx may optionally include sl-V2X-ConfigCommon. For example, sl-V2X-ConfigCommon contains v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, thresh-List, and offset-CarrixTxTxSync, At least one of cbr-pssch-TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR may be included. Additionally, the 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.

-PQI information

-Standardized PQI value

-Non-standardized PQI value

-Non-standardized QoS parameter values. For example, sl-ResourceType, sl-PriorityLevel, sl-PacketDelayBudget, sl-PacketErrorRate, sl-AveragingWindow, sl-MaxDataDataBurstVolume, and the like may be included.

-Indicator indicating whether to report non-standardized QoS parameter values for non-standardized PQI values

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

-Indicator indicating to apply MFBR (Maximum Flow Bit Rate) for Unicast

-Range value for Groupcast

Mapping information of standardized PQI and QoS characteristics (refer to [Table 1]) may be known to each other between the UE and the base station. In addition, when the base station includes the non-standardized PQI value, the terminal and the base station may know each other about mapping information of the non-standardized PQI and QoS characteristics.

[Table 1]: Standardized PQI to QoS characteristics mapping

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

In step 1f-25, the upper layer devices may set the PC5 QoS Profile(s) (for example, PQI) for the packet, and transmit the packet and the PC5 QoS Profile(s) for the packet to the AS layer device.

In step 1f-30, the AS layer device may 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.

In steps 1f-35, if the sidelink bearer configuration information for the PC5 QoS Profile(s) for the packet received in steps 1f-25 is included in the SIBx received in steps 1f-15, the terminal (1f-01) Can establish an SLRB. If the information is not included in the SIBx, the terminal 1f-01 may establish an SLRB or perform a procedure of establishing/resuming an RRC connection with the base station based on the information previously set in step 1f-05. .

In step 1f-40, the terminal 1f-01 may perform NR V2X sidelink communication with the other terminal 1f-02 through the SLRB established in steps 1f-35. NR V2X sidelink communication may be performed through broadcast, groupcast, or unicast.

In steps 1f-45, the RRC idle mode terminal transmits an RRC connection request message to the base station 1f-03 to perform an RRC connection establishment procedure with the base station 1f-03. I can. 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 configuration message, the terminal 1f-01 may transition to the RRC connection mode (1f-51) after applying the configuration information included in the message. In addition, the terminal 1f-01 may transmit (1f-55) an RRC connection setup complete message to the base station 1f-03. The RRC connection establishment completion message may include QoS information related to the SLRB(s) established and used in the RRC idle mode. As an example, the RRC connection establishment completion message may include at least one of the following information related to the SLRB(s) established and used in the RRC idle mode.

- One or more destinationIdentity

- Cast type according to individual destination (for example, whether SLRB(s) established and used in RRC idle mode was used in unicast, broadcast, or groupcast)

- QoS profile information for one or more QoS flows. As an example, each QoS flow identifier (sl-QoS-FlowIdentity) and sl-QoS-Profile information for it may be included. At this time, when the non-standardized PQI value is included in the SIBx in the sl-QoS-Profile, the UE may include only the non-standardized PQI value and may not include a specific QoS parameter for the non-standardized PQI.

- Indicator or SLRB identifier of whether to continue to use the SLRB established and used in RRC idle mode

- Interested sidelink transmission frequency list (sl-TxInterestedFreqList)

- Indicator or SLRB identifier of whether to continue to use the SLRB established and used in RRC idle mode

In steps 1f-45, the RRC deactivation mode terminal 1f-01 transmits an RRC connection resume request message to the base station 1f-03 to perform an RRC connection resume procedure. -03). In step 1f-50, the base station 1f-03 may transmit an RRC connection resume message to the RRC deactivation mode terminal 1f-01. After receiving the RRC connection resumption message, the terminal 1f-01 may transition to the RRC connection mode (1f-51) after applying the configuration information included in the message. In addition, the terminal 1f-01 may transmit (1f-55) an RRC connection resume complete message 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 the RRC deactivation mode. For example, it may include at least one of the following information related to the SLRB(s) established and used in the RRC deactivation mode.

-One or more destinationIdentity

-Cast type according to individual destination (for example, whether the SLRB(s) established and used in RRC deactivation mode was used in unicast, broadcast, or groupcast)

-QoS profile information for one or more QoS flows. As an example, each QoS flow identifier (sl-QoS-FlowIdentity) and sl-QoS-Profile information for it may be included. At this time, when the non-standardized PQI value is included in the SIBx in the sl-QoS-Profile, the UE may include only the non-standardized PQI value and may not include a specific QoS parameter for the non-standardized PQI.

-Indicator or SLRB identifier indicating whether to continue to use the SLRB established and used in RRC deactivation mode

-Interested sidelink transmission frequency list (sl-TxInterestedFreqList)

-Indicator or SLRB identifier indicating whether to continue to use the SLRB established and used in RRC deactivation mode

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 steps 1f-55, if the above-described QoS information is not included in the RRC connection establishment completion message or the RRC connection resumption completion message, steps 1f-60 may be performed. The sidelink terminal information message may include QoS information related to the SLRB(s) established and used in the RRC idle mode or the RRC inactive mode. As an example, the sidelink terminal information message may include at least one of the following information related to the SLRB(s) established and used in the RRC idle mode or the RRC deactivated mode.

- One or more destinationIdentity

- Cast type according to individual destination (for example, whether SLRB(s) established and used in RRC deactivation mode was used in unicast, broadcast, or groupcast)

- QoS profile information for one or more QoS flows. As an example, each QoS flow identifier (sl-QoS-FlowIdentity) and sl-QoS-Profile information for it may be included. At this time, when the non-standardized PQI value is included in the SIBx in the sl-QoS-Profile, the UE may include only the non-standardized PQI value and may not include a specific QoS parameter for the non-standardized PQI.

- Indicator or SLRB identifier of whether to continue to use the SLRB established and used in RRC deactivation mode

- Interested sidelink transmission frequency list (sl-TxInterestedFreqList)

- Indicator or SLRB identifier of whether to continue to use the SLRB established and used in RRC deactivation mode

In steps 1f-65, the base station 1f-03 may transmit to the RRC connection mode terminal 1f-01 including at least one of the following information in the RRCConnectionReconfiguration message.

-SLRB setting information related to QoS information included in steps 1f-55 or 1f-60

-Indicator of whether to continue to use SLRB setting information established and used in RRC idle mode or RRC inactive mode

-Resource mode (mode 3 or mode 4)

-Resource pool setting information according to resource mode

In steps 1f-67, based on the message received in steps 1f-65, the terminal 1f-01 may determine whether to continue to use the SLRB established and used in the RRC idle mode or the RRC inactive mode. As an example, if an indicator indicating that it can continue to be used is included in the RRCConnectionReconfiguration message or the same information as the SLRB established and used in the RRC idle mode or RRC deactivation mode is included, the RRC connection mode terminal 1f-01 is previously used. It is possible to perform NR V2X communication with another terminal (1f-02) by continuing to use the old SLRB. If the message received in steps 1f-65 includes SLRB configuration information that was not established in the RRC idle mode or RRC inactive mode, the RRC connected mode terminal newly establishes an SLRB to communicate NR V2X with another terminal (1f-02). You can do it. If the terminal 1f-01 newly established the SLRB and was performing unicast communication with the other terminal 1f-02, the terminal 1f-01 sends the new SLRB configuration information to the other terminal 1f-02. Included PC5 RRC message can be transmitted.

In steps 1f-70, the terminal 1f-01 transmits an RRCConnectionReconfigurationComplete message to the base station 1f-03, and performs NR V2X SL with the other terminal 1f-02 (1f-75).

In steps 1f-80, if the terminal 1f-01 transmitting and receiving data in the RRC connection mode does not transmit or receive data for a predetermined reason or for a predetermined time, the base station 1f-03 sends an RRC connection release message. By transmitting, the terminal 1f-01 may be switched to an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE). The message may include a timer value indicating whether the SLRB used in the RRC connection mode can be continuously used or released, or an SLRB configuration information element that can be used continuously. The terminal (1f-01) that has received the message and transitioned to the RRC idle mode or the RRC inactive mode can continue to use or release the SLRB used with the other terminal (1f-02) based on the information included in the RRC connection release message. Can judge. If the timer value is included in the message, the terminal 1f-01 may drive the timer and apply the information included in the RRC connection release message. That is, the terminal 1f-01 may not apply the SLRB configuration information included in the system information.

1G is a flowchart illustrating a method of connecting a terminal performing NR V2X sidelink communication with an NR base station according to an embodiment of the present disclosure.

Specifically, referring to FIG.1G, a terminal supporting NR V2X sidelink communication establishes a sidelink bearer (hereinafter, SLRB) in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE) to NR V2X side When switching to the RRC connection mode (RRC_CONNECTED) with the NR base station while performing link communication, it shows a method of reporting the established SLRB to the NR base station.

A terminal according to an 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. The NR base station according to an 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 may signal in an on-demand form. have.

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

The terminal 1g-01 may be in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE) because the RRC connection with the base station 1g-03 is not established (1g-10).

The terminal (1g-01) in the RRC idle mode or the RRC inactive mode can obtain system information by searching for a suitable NR cell and camping on through a cell selection procedure or a cell reselection procedure (1g -15). As an example, the system information is defined/introduced for MIB1, SIB1, SIB2, SIB3, SIB4, SIB5, SIB21, SIB26 or NR V2X sidelink communication to mean one or more SIBx including NR V2X sidelink configuration information. I can. The camp-on cell may be referred to as a serving cell (SCell) or a primary cell (PCell).

Specifically, in step 1g-15, if it is indicated that the above-described SIBx exists in the SIB1 (SystemInformationBlockType1) received from the cell (Scell or PCell) (1g-03) through a scheduling information list (SchedulingInfoList), the RRC is idle. The mode or RRC deactivation mode terminal 1g-01 may acquire SIBx. Or, if the SIBx in a valid state is not stored, the terminal 1g-01 may acquire the SIBx. When the base station 1g-03 broadcasts SIBx, the SIBx may optionally include sl-V2X-ConfigCommon. sl-V2X-ConfigCommon includes: v2x-CommRxPool, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolExceptional, v2x-SyncConfig, v2x-InterFreqInfoList, v2x-ResourceSelectionConfig, zoneConfig, typeTxSync, threshSS-TxPrioList, cbrqbrps, offset-TxPrio At least one of TxConfigList, v2x-packetDuplicationConfig, syncFreqList, slss-TxMultiFreq, v2x-FreqSelectionConfigList, and threshS-RSSI-CBR may be included. Additionally, the 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.

-PQI information

-Standardized PQI value

-Non-standardized PQI value

-Non-standardized QoS parameter values. For example, sl-ResourceType, sl-PriorityLevel, sl-PacketDelayBudget, sl-PacketErrorRate, sl-AveragingWindow, sl-MaxDataDataBurstVolume, and the like may be included.

-Indicator indicating whether to report non-standardized QoS parameter values for non-standardized PQI values

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

-Indicator indicating to apply MFBR (Maximum Flow Bit Rate) for Unicast

-Range value for Groupcast

The mapping information of the standardized PQI and QoS characteristics (refer to [Table 2]) may be known to each other between the terminal 1g-01 and the base station 1g-03. In addition, when the base station 1g-03 includes a non-standardized PQI value, the terminal 1g-01 and the base station 1g-03 may know each other about mapping information of the non-standardized PQI and QoS characteristics.

[Table 2]: Standardized PQI to QoS characteristics mapping

In step 1g-20, a packet for transmitting NR V2X sidelink communication may be generated or arrived, and may be configured to perform NR V2X sidelink communication. And it may be instructed to perform NR V2X sidelink communication at a specific frequency.

In step 1g-25, the upper layer devices may set the PC5 QoS Profile(s) (for example, PQI) for the packet, and transmit the packet and the PC5 QoS Profile(s) for the packet to the AS layer device.

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

In steps 1g-35, when the sidelink bearer configuration information for the PC5 QoS Profile(s) for the packet received in steps 1g-25 is included in the SIBx received in step 1g-15, the SLRB may be established. have. If the information is not included in the SIBx, the SLRB may be established based on the information previously set in step 1g-05, or a procedure for establishing/resuming an RRC connection with the base station 1g-03 may be performed.

In step 1g-40, the terminal 1g-01 may perform NR V2X sidelink communication with the other terminal 1g-02 through the SLRB established in step 1g-35. NR V2X sidelink communication may be performed through broadcast, groupcast, or unicast.

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

- One or more destinationIdentity

- Cast type according to individual destination (for example, whether SLRB(s) established and used in RRC idle mode was used in unicast, broadcast, or groupcast)

- QoS profile information for one or more QoS flows. As an example, each QoS flow identifier (sl-QoS-FlowIdentity) and sl-QoS-Profile information for it may be included. At this time, when the non-standardized PQI value is included in the SIBx in the sl-QoS-Profile, the UE may include only the non-standardized PQI value and may not include a specific QoS parameter for the non-standardized PQI.

- Indicator or SLRB identifier of whether to continue to use the SLRB established and used in RRC idle mode

- Interested sidelink transmission frequency list (sl-TxInterestedFreqList)

- Indicator or SLRB identifier of whether to continue to use the SLRB established and used in RRC idle mode

In steps 1g-45, the RRC deactivation mode terminal (1g-01) sends an RRC connection resume request message (RRCResumeRequest message or RRCResumeRequest1 message) to perform an RRC connection resume procedure with the base station (1g-03). It can be transmitted to the base station (1g-03). In step 1g-50, the base station 1g-03 may transmit an RRC connection resume message to the RRC deactivation mode terminal 1g-01. After receiving the RRC connection resumption message, the terminal 1g-01 may transition to the RRC connection mode (1g-51) after applying the configuration information included in the message. In addition, the terminal 1g-01 may transmit (1g-55) an RRC connection resumption complete message to the base station 1g-03. The RRC connection resumption completion message may include QoS information related to the SLRB(s) established and used in the RRC deactivation mode. As an 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 the RRC deactivation mode.

- One or more destinationIdentity

- Cast type according to individual destination (for example, whether SLRB(s) established and used in RRC deactivation mode was used in unicast, broadcast, or groupcast)

- QoS profile information for one or more QoS flows. As an example, each QoS flow identifier (sl-QoS-FlowIdentity) and sl-QoS-Profile information for it may be included. At this time, when the non-standardized PQI value is included in the SIBx in the sl-QoS-Profile, the UE may include only the non-standardized PQI value and may not include a specific QoS parameter for the non-standardized PQI.

- Indicator or SLRB identifier of whether to continue to use the SLRB established and used in RRC deactivation mode

- Interested sidelink transmission frequency list (sl-TxInterestedFreqList)

- Indicator or SLRB identifier of whether to continue to use the SLRB established and used in RRC deactivation mode

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 steps 1g-55, if the above-described QoS information is not included in the RRC connection establishment completion message or the RRC connection resumption completion message, steps 1g-60 may be performed. The sidelink terminal information message may include QoS information related to the SLRB(s) established and used in the RRC idle mode or the RRC inactive mode. As an example, the sidelink terminal information message may include at least one of the following information related to the SLRB(s) established and used in the RRC idle mode or the RRC deactivated mode.

- One or more destinationIdentity

- Cast type according to individual destination (for example, whether SLRB(s) established and used in RRC deactivation mode was used in unicast, broadcast, or groupcast)

- QoS profile information for one or more QoS flows. As an example, each QoS flow identifier (sl-QoS-FlowIdentity) and sl-QoS-Profile information for it may be included. At this time, when the non-standardized PQI value is included in the SIBx in the sl-QoS-Profile, the UE may include only the non-standardized PQI value and may not include a specific QoS parameter for the non-standardized PQI.

- Indicator or SLRB identifier of whether to continue to use the SLRB established and used in RRC deactivation mode

- Interested sidelink transmission frequency list (sl-TxInterestedFreqList)

- Indicator or SLRB identifier of whether to continue to use the SLRB established and used in RRC deactivation mode

In steps 1g-65, the base station 1g-03 may transmit to the RRC connection mode terminal 1g-01 including at least one of the following information in the RRCReconfiguration message.

-SLRB setting information related to QoS information included in steps 1g-55 or 1g-60

-Indicator of whether to continue to use SLRB setting information established and used in RRC idle mode or RRC inactive mode

-Resource mode (mode 3 or mode 4)

-Resource pool setting information according to resource mode

In steps 1g-67, based on the message received in steps 1g-65, the terminal 1g-01 may determine whether to continue to use the SLRB established and used in the RRC idle mode or the RRC inactive mode. As an example, if an indicator indicating that it can continue to be used is included in the RRCReconfiguration message or the same information as the SLRB established and used in the RRC idle mode or RRC inactive mode is included, the RRC connected mode terminal continues to use the previously used SLRB. Thus, it is possible to perform NR V2X communication with the other terminal (1g-02). If SLRB configuration information not established in RRC idle mode or RRC deactivation mode is included in the message received in steps 1g-65, the RRC connected mode terminal newly establishes an SLRB to communicate NR V2X with another terminal (1g-02). You can do it. If the terminal 1g-01 newly established the SLRB and was performing unicast communication with the other terminal 1g-02, the terminal 1g-01 sends the new SLRB configuration information to the other terminal 1g-02. Included PC5 RRC message can be transmitted.

In steps 1g-70, the terminal 1g-01 transmits an RRCReconfigurationComplete message to the base station 1g-03, and performs NR V2X SL with another terminal 1g-02 (1g-75).

In steps 1g-80, if the terminal 1g-01 transmitting and receiving data in the RRC connected mode does not transmit or receive data for a predetermined reason or for a predetermined time, the base station 1g-03 sends an RRC connection release message. By transmitting, the terminal 1g-01 may be switched to an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE). The message may include a timer value indicating whether the SLRB used in the RRC connection mode can be continuously used or released, or an SLRB configuration information element that can be used continuously. The terminal (1g-01) that has received the message and transitioned to the RRC idle mode or RRC inactive mode can continue to use or release the SLRB used with the other terminal (1g-02) based on the information included in the RRC connection release message. Can judge. If the message includes a timer value, the terminal 1g-01 may drive the timer and apply the information included in the RRC connection release message. That is, the terminal 1g-01 may not apply the SLRB configuration information included in the system information.

1H is a flowchart illustrating a method of connecting a terminal performing NR V2X sidelink communication with an NR base station according to an embodiment of the present disclosure.

Specifically, referring to FIG.1H, a terminal supporting NR V2X sidelink communication establishes a sidelink bearer (hereinafter SLRB) in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE) to NR V2X side This is a diagram for explaining an operation of a terminal reporting an established SLRB to an NR base station when switching to an RRC connection mode (RRC_CONNECTED) with an NR base station while performing link communication.

1H, a terminal supporting NR V2X sidelink communication may be in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE) (1h-05).

In step 1h-10, the UE may obtain system information including V2X sidelink communication configuration information through a cell selection or cell reselection procedure. System information may include SLRB configuration information including SL QoS Profile(s). SL QoS Profile(s) may include at least one of the following information.

-PQI information

-Standardized PQI value

-Non-standardized PQI value

-Non-standardized QoS parameter values. For example, sl-ResourceType, sl-PriorityLevel, sl-PacketDelayBudget, sl-PacketErrorRate, sl-AveragingWindow, sl-MaxDataDataBurstVolume, and the like may be included.

-Indicator indicating whether to report non-standardized QoS parameter values for non-standardized PQI values

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

-Indicator indicating to apply MFBR (Maximum Flow Bit Rate) for Unicast

-Range value for Groupcast

In step 1h-15, the terminal may receive an instruction for service data or a request for NR V2X sidelink communication transmission from the V2X application device. When there is no PC5 QoS flow matching the service data or request, the terminal may create a PC5 QoS flow by determining the PC5 QoS parameter.

In steps 1h-20, the UE may determine whether the SLRB configuration information for the PC5 QoS profile exists in the system information for the generated PC5 QoS Flow.

In step 1h-25, the UE may perform an RRC connection setup procedure or an RRC connection resumption procedure with the base station.

In steps 1h-30, the UE may transition to the RRC connection mode (RRC_CONNECTED) by establishing an RRC connection with the base station.

In steps 1h-35, the terminal may transmit an RRC message to request SLRB configuration information from the base station. 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.

In step 1h-40, the terminal may perform V2X sidelink communication by establishing one or a plurality of SLRBs.

In steps 1h-45, the UE may perform an RRC connection setup procedure or an RRC connection resumption procedure with the base station.

In step 1h-50, the terminal may transition to the RRC connection mode (RRC_CONNECTED) by establishing an RRC connection with the base station.

In steps 1h-55, in steps 1h-40, the UE may determine whether the established SLRB is based on standardized PQI.

In steps 1h-60, the UE may transmit an RRC message including standardized PQI. 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. In this case, the UE may include a standardized PQI value for each cast type, destination, and QoS flow in the message.

In steps 1h-65, the UE may determine whether a non-standardized PQI value is included in the system information or an indicator indicating whether non-standardized QoS parameters need not be reported is included in the system information.

In steps 1h-70, the UE may transmit an RRC message including a non-standardized PQI. 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. In this case, the UE may include a cast type, destination, QoS flow, and non-standardized PQI value in the message.

In steps 1h-75, the UE may transmit an RRC message including non-standardized QoS parameters. The non-standardized QoS parameters may mean at least one parameter of sl-ResourceType, sl-PriorityLevel, sl-PacketDelayBudget, sl-PacketErrorRate, sl-AveragingWindow, and sl-MaxDataDataBurstVolume. 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. In this case, the UE may include the non-standardized QoS parameters for each cast type, destination, and QoS flow in the message.

1I is a diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.

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.

The RF processing unit 1i-10 according to an embodiment of the present disclosure may perform a function for transmitting and receiving a signal through a wireless channel, such as band conversion and amplification of a signal. That is, the RF processing unit 1i-10 up-converts the baseband signal provided from the baseband processing unit 1i-20 to an RF band signal, and then transmits it through an antenna, and transmits the RF band signal received through the antenna to the baseband signal. Can be down-converted to a 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 convertor (DAC), an analog to digital convertor (ADC), and the like. have.

In FIG. 1I, only one antenna is shown, but the terminal may include a plurality of antennas.

In addition, the RF processing unit 1i-10 may include a plurality of RF chains. Furthermore, the RF processing unit 1i-10 may perform beamforming. For beamforming, the RF processing unit 1i-10 may adjust a phase and a magnitude of each of signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processing unit 1i-10 may perform multiple-input multiple-output (MIMO), and may receive multiple layers when performing a MIMO operation. The RF processing unit 1i-10 performs reception beam sweeping by appropriately setting a plurality of antennas or antenna elements under the control of the control unit 1i-40, or You can adjust the width.

The baseband processing unit 1i-20 may perform a function of converting between a baseband signal and a bit stream according to a physical layer standard of a system. For example, when transmitting data, the baseband processing unit 1i-20 may generate complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit 1i-20 may restore a received bit stream through demodulation and decoding of the baseband signal provided from the RF processing unit 1i-10. For example, in the case of the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processor 1i-20 generates complex symbols by encoding and modulating a transmission bit stream, and mapping the complex symbols to subcarriers. Thereafter, OFDM symbols may be configured through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processing unit 1i-20 divides the baseband signal provided from the RF processing unit 1i-10 in units of OFDM symbols, and is mapped to subcarriers through a fast Fourier transform (FFT) operation. After restoring the signals, the received bit stream may be restored through demodulation and decoding.

The baseband processing unit 1i-20 and the RF processing unit 1i-10 may 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 transmission unit, a reception unit, a transmission/reception 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. In addition, 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 radio access technologies may include an LTE network, an NR network, and the like. In addition, different frequency bands may include a super high frequency (SHF) (eg, 2.2gHz, 2ghz) band, and a millimeter wave (eg, 60GHz) band.

The storage unit 1i-30 may store data such as a basic program, an application program, and setting information for the operation of the terminal. The storage unit 1i-30 may provide stored data according to the request of the control unit 1i-40.

The controller 1i-40 may control overall operations of the terminal. For example, the control unit 1i-40 may transmit and receive signals through the baseband processing unit 1i-20 and the RF processing unit 1i-10. Also, the control unit 1i-40 may write and read data in the storage unit 1i-40. To this end, the control unit 1i-40 may include at least one processor. For example, the controller 1i-40 may include a communication processor (CP) that controls communication and an application processor (AP) that controls an upper layer such as an application program.

1J shows a structure of a base station according to an embodiment of the present disclosure.

A base station according to an embodiment of the present disclosure may include one or more transmission reception points (TRP).

A base station according to an embodiment of the present disclosure includes 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. Can include.

The RF processing unit 1j-10 may perform a function for transmitting and receiving a signal through a wireless channel, such as band conversion and amplification of a signal. That is, the RF processing unit 1j-10 up-converts the baseband signal provided from the baseband processing unit 1j-20 to an RF band signal, and then transmits it through an antenna, and transmits the RF band signal received through the antenna to the baseband signal. It can be downconverted to a 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, and the like.

In FIG. 1J, only one antenna is shown, but the base station may include a plurality of antennas.

In addition, 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 a phase and a magnitude of each of signals transmitted and received through a plurality of antennas or antenna elements. The RF processing unit 1j-10 may perform a downlink MIMO operation by transmitting one or more layers.

The baseband processing unit 1j-20 may perform a function of converting between a baseband signal and a bit string according to a physical layer standard of the first wireless access technology. For example, when transmitting data, the baseband processing unit 1j-20 may generate complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit 1j-20 may restore a received bit stream through demodulation and decoding of the baseband signal provided from the RF processing unit 1j-10. For example, in the case of the OFDM scheme, when transmitting data, the baseband processing unit 1j-20 generates complex symbols by encoding and modulating a transmission bit stream, mapping the complex symbols to subcarriers, and then performing an IFFT operation and OFDM symbols can be configured through CP insertion. In addition, when receiving data, the baseband processing unit 1j-20 divides the baseband signal provided from the RF processing unit 1j-10 in units of OFDM symbols, and restores the signals mapped to the subcarriers through FFT operation. , Demodulation and decoding, it is possible to restore the received bit stream. The baseband processing unit 1j-20 and the RF processing unit 1j-10 may transmit and receive signals as described above.

Accordingly, the baseband processing unit 1j-20 and the RF processing unit 1j-10 may be referred to as a transmission unit, a reception unit, a transmission/reception unit, a communication unit, or a wireless communication unit.

The communication unit 1j-30 may provide an interface for performing communication with other nodes in the network. That is, the communication unit 1j-30 converts a bit stream transmitted from the main station to another node, for example, an auxiliary base station, a core network, etc., into a physical signal, and converts a physical signal received from another node into a bit stream. can do.

The storage unit 1j-40 may store data such as a basic program, an application program, and setting information for the operation of the main station. In particular, the storage unit 1j-40 may store information on bearers allocated to the connected terminal, measurement results reported from the connected terminal, and the like. In addition, the storage unit 1j-40 may store information that is a criterion for determining whether to provide or stop providing multiple connections to the terminal. Also, the storage unit 1j-40 may provide stored data according to a request of the control unit 1j-50.

The controller 1j-50 may control overall operations of the main station. For example, the control unit 1j-50 may 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. Also, the control unit 1j-50 may write and read data in the storage unit 1j-40. To this end, the control unit 1j-50 may include at least one processor.

The methods according to the embodiments described in the claims or the specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (device). The one or more programs include instructions for causing the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

These programs (software modules, software) include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (EEPROM: Electrically Erasable Programmable Read Only Memory), magnetic disc storage device, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other types of It may be stored in an optical storage device or a magnetic cassette. Alternatively, it may be stored in a memory composed of a combination of some or all of them. In addition, a plurality of configuration memories may be included.

In addition, the program is through a communication network composed of a communication network such as the Internet, an intranet, a local area network (LAN), a wide LAN (WLAN), or a storage area network (SAN), or a combination thereof. It may be stored in an accessible storage device. Such a storage device may access a device performing an embodiment of the present disclosure through an external port. In addition, a separate storage device on the communication network may access a device performing an embodiment of the present disclosure.

In the specific embodiments of the present disclosure described above, the constituent elements included in the invention are expressed in the singular or plural according to the presented specific embodiment. However, the singular or plural expression is selected appropriately for the situation presented for convenience of explanation, and the present disclosure is not limited to the singular or plural constituent elements, and even constituent elements expressed in plural are composed of the singular or singular. Even the expressed constituent elements may be composed of pluralities.

Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure is limited to the described embodiments and should not be determined, and should be determined by the scope of the claims and equivalents as well as the scope of the claims to be described later.

Claims (1)

In a method for a terminal to perform sidelink communication in a wireless communication system,
Obtaining system information including sidelink communication setting information;
Establishing a Sidelink Radio Bearer (SLRB) based on the system information;
Performing the sidelink communication based on the established SLRB; And
Including, performing an RRC connection with a base station based on the established SLRB.

Images