WO2020050601A1 - Method and apparatus for requesting resource for device-to-device communication in wireless communication system supporting vehicle communication - Google Patents

Abstract

The present invention provides a method, performed by a terminal using a sidelink, for requesting a resource in a wireless communication system. In this case, the method, performed by the terminal, for requesting a resource comprises the steps of: receiving a parameter for a BSR on the basis of a base station type set to be connected to the terminal; transmitting, to the base station, the BSR in a format of the base station type on the basis of the received parameter; receiving, from the base station, at least one of resource allocation information of a first type sidelink and resource allocation information of a second type sidelink on the basis of the BSR; and performing sidelink communication on the basis of the received resource allocation information. In addition, for example, a terminal for requesting a resource may be provided.

Description

Method and apparatus for requesting resources for communication between terminals in a wireless communication system supporting vehicle communication

The present invention relates to a method and apparatus for requesting resources for communication between vehicles in a network or vehicle (or terminal) in a wireless communication system supporting vehicle communication (V2X).

The present invention relates to a method and apparatus for requesting resources for providing high-reliability / low-latency transmission in a New Radio (NR) system.

The International Telecommunication Union (ITU) is developing the International Mobile Telecommunication (IMT) framework and standards, and is currently in the process of discussing 5G (5G) communication through a program called "IMT for 2020 and beyond." .

In order to meet the requirements set forth in "IMT for 2020 and beyond", the 3rd Generation Partnership Project (3GPP) New Radio (3GPP) system is based on time-frequency, considering various scenarios, service requirements, and potential system compatibility. It is discussed in the direction of supporting various numerologies for resource unit criteria.

In addition, V2X communication may mean a communication method of exchanging or sharing information such as a traffic situation while communicating with a road infrastructure and other vehicles while driving. V2X is a vehicle-to-vehicle (V2V), which means LTE / NR-based communication between vehicles, and a vehicle-to-pedestrian (V2P), which means LTE / NR-based communication between vehicles and terminals carried by individuals. It may include a vehicle-to-infrastructure / network (V2I / N), which means LTE / NR-based communication between roadside units / networks. At this time, a roadside unit (RSU) may be a transport infrastructure entity implemented by a base station or a fixed terminal. For example, it may be an entity that transmits a speed notification to a vehicle. In addition, based on the performance requirements to support V2X through 5G systems, such as autonomous driving and vehicle remote control, specific technologies additionally required for LTE and NR systems, which are radio access technologies (RAT) within 5G systems, are being discussed. .

In the following, a new NR sidelink resource request method based on the resource allocation method of the NR system is proposed to introduce a transmission method between vehicles in the NR system.

The present invention can provide a method of configuring a format of NR SL BSR MAC CE.

The present invention can provide a method of performing a resource request procedure based on a type of a base station connected to a terminal.

The present invention can provide a method of performing a resource request procedure based on a terminal operation mode.

The present invention can provide a terminal and a base station device using the NR SL BSR MAC CE format.

The present invention can provide a terminal and a base station device performing a resource request procedure based on a base station type.

The present invention can provide a terminal and a base station device that performs a resource request procedure based on a terminal operation mode.

The present invention can provide a method for a terminal using a side link in a wireless communication system to perform a resource request. At this time, the method for the terminal to perform the resource request is a step of receiving a parameter for the BSR based on the base station type established with the terminal, transmitting the BSR to the base station in the format for the base station type based on the received parameters, BSR And receiving one or more of resource allocation information of the first type sidelink and resource allocation information of the second type sidelink from the base station based on the base station, and performing sidelink communication based on the received resource allocation information. can do.

The features briefly summarized above with respect to the present disclosure are merely illustrative aspects of the detailed description of the present disclosure described below, and do not limit the scope of the present disclosure.

According to the present disclosure, a method of configuring a format of an NR SL BSR MAC CE in consideration of NR SL (Sidelink) can be provided.

According to the present disclosure, a method of performing a resource request procedure based on a type of a base station connected to a terminal can be provided.

According to the present disclosure, a method of performing a resource request procedure based on a terminal operation mode can be provided.

The present invention is not limited to the above-described effects, and other effects not mentioned will be clearly understood by those skilled in the art from the following description.

1 is a view showing a wireless communication system to which the present disclosure can be applied.

2 is a view showing a V2X link to which the present disclosure can be applied.

3 is a diagram for explaining a V2X scenario to which the present disclosure can be applied.

FIG. 4 is a diagram illustrating a scenario in which V2X operation is performed using both sidelink and communication with a base station to which the present disclosure can be applied.

5 is a D2D communication scenario to which the present disclosure can be applied.

6 is a D2D communication scenario to which the present disclosure can be applied.

7 is a diagram showing an operation based on a base station scheduling mode and a terminal autonomous determination mode to which the present disclosure can be applied.

8 is a view showing a new numerology to which the present disclosure can be applied.

9 is a diagram showing the structure of an LTE SL BSR to which the present disclosure can be applied.

10 is a diagram showing the structure of an LTE SL BSR to which the present disclosure can be applied.

11 is a view showing the structure of an NR SL BSR to which the present disclosure can be applied.

12 is a diagram showing a resource request procedure based on an LTE base station to which the present disclosure can be applied.

13 is a diagram showing a resource request procedure based on an NR base station to which the present disclosure can be applied.

14 is a view showing a resource request procedure based on dual connectivity to which the present disclosure can be applied.

15 is a diagram showing a resource request procedure based on dual connectivity to which the present disclosure can be applied.

16 is a diagram illustrating a resource request procedure based on a terminal operation mode to which the present disclosure can be applied.

17 is a diagram illustrating a resource request procedure based on a terminal operation mode to which the present disclosure can be applied.

18 is a flowchart of a communication method to which the present disclosure can be applied.

19 is a view showing the configuration of a base station apparatus and a terminal apparatus to which the present disclosure can be applied.

Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art to which the present disclosure pertains can easily carry out the embodiments. However, the present disclosure can be implemented in many different forms and is not limited to the embodiments described herein.

In describing the embodiments of the present disclosure, when it is determined that a detailed description of a known configuration or function may obscure the subject matter of the present disclosure, detailed description thereof will be omitted. In the drawings, parts irrelevant to the description of the present disclosure are omitted, and similar reference numerals are used for similar parts.

In the present disclosure, when a component is said to be "connected", "coupled" or "connected" with another component, this is not only a direct connection relationship, but also an indirect connection relationship in which another component exists in the middle. It may also include. Also, when a component is said to "include" or "have" another component, this means that other components may be further included instead of excluding other components unless specifically stated to the contrary. .

In the present disclosure, terms such as first and second are used only for the purpose of distinguishing one component from other components, and do not limit the order or importance of components, etc., unless otherwise specified. Accordingly, within the scope of the present disclosure, the first component in one embodiment may be referred to as the second component in other embodiments, and likewise the second component in one embodiment may be the first component in another embodiment It can also be called.

In the present disclosure, the components that are distinguished from each other are for clarifying each feature, and the components are not necessarily separated. That is, a plurality of components may be integrated to be composed of one hardware or software unit, or one component may be distributed to be composed of a plurality of hardware or software units. Accordingly, such integrated or distributed embodiments are included within the scope of the present disclosure, unless otherwise stated.

In the present disclosure, components described in various embodiments are not necessarily essential components, and some may be optional components. Accordingly, an embodiment comprised of a subset of components described in one embodiment is also included in the scope of the present disclosure. Also, embodiments that include other elements in addition to the elements described in various embodiments are included in the scope of the present disclosure.

In addition, this specification is described for a wireless communication network, the work performed in the wireless communication network is performed in the process of controlling the network and transmitting data in a system (for example, a base station) that is in charge of the wireless communication network, or The operation can be performed at the terminal coupled to the network.

That is, it is apparent that various operations performed for communication with a terminal in a network composed of a plurality of network nodes including a base station can be performed by a base station or other network nodes other than the base station. The term 'base station (BS)' may be replaced by terms such as a fixed station, a Node B, an eNodeB (eNB), a gNodeB (gNB), or an access point (AP). Also, 'terminal' may be replaced with terms such as user equipment (UE), mobile station (MS), mobile subscriber station (MSS), subscriber station (SS), and non-AP STA (non-AP STA). You can.

In the present disclosure, transmitting or receiving a channel includes transmitting or receiving information or a signal through the corresponding channel. For example, transmitting a control channel means transmitting control information or a signal through the control channel. Similarly, transmitting a data channel means transmitting data information or a signal through the data channel.

In the following description, the term NR system is used for the purpose of distinguishing a system to which various examples of the present disclosure are applied from an existing system, but the scope of the present disclosure is not limited by these terms.

For example, the NR system supports various subcarrier spacing (SCS) considering various scenarios, service requirements, and potential system compatibility. In addition, NR systems are designed to overcome poor channel environments such as high path-loss, phase-noise and frequency offset occurring on a high carrier frequency. It can support the transmission of the physical signal / channel through the beam of. Through this, the NR system can support applications such as enhanced Mobile Broadband (eMBB), Massive Machine Type Communications (mMTC) / ultra Machine Type Communications (uMTC), and Ultra Reliable and Low Latency Communications (URLLC). However, although the term NR system in this specification is used as an example of a wireless communication system, the term NR system itself is not limited to the above-described features.

In addition, as an example, 5G mobile communication technology may be defined. At this time, as an example, 5G mobile communication technology may be defined to include not only the NR system described above, but also a new version of the LTE-Advanced (Long Term Evolution-Advanced) pro system developed with the NR system. That is, 5G mobile communication may be a technology that operates in consideration of backward compatibility with a previous LTE system as well as a newly defined NR system.

For example, the sidelink field of 5G may include both a sidelink in an LTE system and a sidelink in an NR system. At this time, the side link field may be an essential field for improving performance through ultra-high reliability and ultra-low delay, and grafting new and diverse services.

1 is a view showing a wireless communication system to which the present invention is applied.

1 may be a network structure of Next Generation Radio Access Network (NG-RAN) or Evolved-Universal Mobile Telecommunications System (E-UMTS). The NG-RAN or E-UMTS system may include a Long Term Evolution (LTE), an Advanced (LTE-A) system, or may include a fifth generation mobile communication network, a new radio (NR), and the like.

Referring to FIG. 1, a base station (BS) and a user equipment (UE) 12 in a wireless communication system 10 may wirelessly transmit and receive data. Also, the wireless communication system 10 may support device-to-device (D2D) communication. In the following, the concept of the terminal device used by the general user, such as a smartphone, and the terminal device mounted in the vehicle may be included for the above-described terminal.

In addition, as an example, in the wireless communication system 10, the base station 11 may provide a communication service to a terminal existing in the coverage of the base station through a specific frequency band. Coverage serviced by a base station can also be expressed in terms of a site. A site may include a number of areas 15a, 15b, 15c, which may be called sectors. Each sector included in the site may be identified based on different identifiers. Each sector 15a, 15b, 15c may be a partial area covered by the base station 11.

In addition, as an example, the base station 11 generally refers to a station (station) that communicates with the terminal 12, eNodeB (evolved-NodeB), BTS (Base Transceiver System), access point (Access Point), femto base station ( Femto eNodeB), a home base station (HeNodeB: Home eNodeB), a relay (relay), a remote radio head (RRH: Remote Radio Head), DU (Distributed Unit), etc.

The terminal 12 may be fixed or mobile, and a mobile station (MS), a mobile terminal (MT), a user terminal (UT), a subscriber station (SS), a wireless device (PDA), a personal digital assistant (PDA) , Wireless modem, and handheld device.

In addition, the base station 11 may be called in various terms such as megacell, macrocell, microcell, picocell, femtocell according to the size of the coverage provided by the base station. The cell may be used as a term indicating all or part of a frequency band provided by the base station, coverage of the base station, or base station.

Hereinafter, a downlink (DL) means a communication or communication path from the base station 11 to the terminal 12, and an uplink (UL) communicates from the terminal 12 to the base station 11 or It means the communication path. In the downlink, the transmitter may be part of the base station 11, and the receiver may be part of the terminal 12. In the uplink, the transmitter may be part of the terminal 12 and the receiver may be part of the base station 11.

Meanwhile, there are no restrictions on the multiple access technique applied to the wireless communication system 10. For example, Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier-FDMA (SC-FDMA), OFDM-FDMA , OFDM-TDMA, OFDM-CDMA can be used in a variety of multiple access techniques. In addition, a time division duplex (TDD) method transmitted using different times or a frequency division duplex (FDD) method transmitted using different frequencies may be used for uplink transmission and downlink transmission.

In this case, as an example, Table 1 below may be a definition for each term in relation to the above-described V2X.

[Table 1]

In addition, as an example, the abbreviations related to the configuration described below may be as shown in Table 2.

[Table 2]

Links used in V2X (Downlink (DL), Uplink (UL), Sidelink (SL))

In a communication system supporting V2X, downlink (DL), uplink (UL), and sidelink (SL) communication may be possible. As an example, FIG. 2 is a view showing a link considered in V2X. In this case, referring to FIG. 2, a communication system supporting V2X can support only a PC5 link, which is a link between a UE and a UE defined in D2D (ProSe). The PC5 link means an interface defined between the terminal and the terminal, and may be defined as a sidelink (SL) in the wireless access layer. Side link means a link in a wireless access layer for direct communication between a vehicle for vehicle communication and a vehicle, but is not limited to the above.

In addition, FIG. 3 may be a V2X operation scenario using communication with a terminal (or vehicle) and a base station. As an example, referring to FIG. 3, a communication system supporting V2X may only support a Uu link, which is a link between a base station and a UE, and / or a radio access network and a UE. The Uu link may include uplink (UL), which is a path through which a terminal transmits a signal to a base station, and downlink (DL), which is a path through which a base station transmits a signal to a terminal.

In addition, as an example, terms necessary for V2X may be defined as Table 1 and Table 2 described above. In this case, as an example, D2D (Device to Device) may mean communication between terminals. In addition, ProSe may mean a proximity service to a terminal performing D2D communication. In addition, the sidelink (SL) may be the above-described sidelink, and the Sidelink Control Information (SCI) may refer to the control information related to the above-described sidelink transmitted through the above-described sidelink. Further, a PSSCH (Physical Sidelink Shared Channel) may be a channel through which data is transmitted through the sidelink, and a PSCCH (Physical Sidelink Control Channel) may be a channel through which control information is transmitted through the sidelink. In addition, PSBCH (Physical Sidelink Broadcast Channel) is a channel for transmitting a signal through a sidelink in a broadcast manner, and system information may be transmitted. In addition, the PSDCH (Physical Sidelink Discovery Channel) may be a channel used for a signal discovery as a discovery channel.

In addition, V2V may mean communication between vehicles, V2P may be communication between vehicles and pedestrians, and V2I / N may mean communication between a vehicle and an infrastructure / network. This will be described later.

In this case, as an example, in relation to V2X, the terminal described below may be a vehicle. In the following, for convenience of description, the terminal is referred to as a unit, but the terminal may be a vehicle supporting V2X function. Further, as an example, the terminal may refer to a device capable of performing communication with a sidelink and a base station, and is not limited to the above-described embodiment. However, hereinafter, it is referred to as a terminal for convenience of description.

In addition, FIG. 4 may be a scenario for performing a V2X operation using both the above-described sidelink and base station communication.

4A and 4B, in the side link interface, both the PC5 link and the Uu link described above may be considered, including a Road Side Unit (RSU) operating in a UE format. 4A is a case in which a base station transmits a downlink signal to a plurality of vehicles, and FIG. 4B is a case in which a terminal (UE, RSU) transmits a sidelink signal to a plurality of vehicles.

For example, D2D communication may mean communication that directly transmits and receives data between terminals. In the following, it is assumed that the terminal (or vehicle) supports D2D communication. In addition, D2D communication may be replaced by an expression such as Proximity based Service (ProSe) or ProSe-D2D communication. The use of the term ProSe for D2D communication means that the meaning of transmitting and receiving data directly between terminals is not changed, but the meaning of the proximity-based service can be added.

D2D communication is a discovery procedure for communication between terminals in network coverage (in-coverage) or out-of-coverage, and direct communication (transmission and reception of control data and / or traffic data between terminals) direct communication). In this case, as an example, a terminal transmitting a signal based on D2D communication may be a transmitting terminal (Tx UE). Also, a terminal that receives a signal based on D2D communication may be a receiving terminal (Rx UE). At this time, the transmitting terminal may transmit a discovery signal, and the receiving terminal may receive the discovery signal. The role of the transmitting terminal and the receiving terminal may be changed. The signal transmitted by the transmitting terminal may be received by two or more receiving terminals. Here, the above-described discovery procedure and direct communication procedure may be performed independently of each other.

The D2D communication described above can be used for various purposes. For example, D2D communication within network coverage based on commercial frequency may be used for at least one or more of public safety, traffic network service, ultra-low latency service, and commercial purpose service. , It is not limited to the above-described embodiment. In addition, as an example, when based on a dedicated traffic network frequency, D2D communication through a corresponding frequency may be used only for traffic network communication and traffic safety regardless of network coverage.

In a cellular system, when UEs in close proximity perform D2D communication, the load of the base station can be distributed. In addition, when D2D communication is performed by terminals that are close to each other, the terminals transmit data at a relatively short distance, so that the power consumption and transmission latency of the terminal may be reduced. In addition, as an example, since the existing cellular-based communication and the D2D communication use the same resource from the overall system point of view, it is possible to improve frequency utilization efficiency when they are not spatially overlapped.

D2D communication scenario (or V2X communication scenario)

D2D communication (or V2X communication) may be divided into network coverage (base station coverage) (In-coverage, IC) communication and network coverage out-of-coverage (OCC) communication. In this case, the IC may be communication between terminals located in network coverage. In addition, the OCC may be communication between terminals located outside the network coverage.

As another example, D2D communication (or V2X communication) may be divided into communication between a terminal located within network coverage and a terminal located outside network coverage.

As an example, FIG. 5 may be a scenario for D2D communication (or V2X communication). In this case, referring to FIG. 5, since the first terminals V2X UE1 and 510 and the second terminals V2X UE2 and 520 are located within the network coverage, communication with the base station may be possible. That is, the first terminal 510 and the second terminal 520 may perform data transmission and reception for a vehicle communication service through a base station (Uu interface). That is, the first terminal 510 and the second terminal 520 may exchange data for a vehicle communication service with each other through UL data transmission and DL data reception. On the other hand, as an example, the third terminal (V2X UE3, 530) and the fourth terminal (V2X UE4,540) may be located outside the network coverage. In this case, when the third terminal 530 and the fourth terminal 540 are in a position where communication between the first terminal 510 and the second terminal 520 is not possible, the third terminal 530 and the fourth terminal 540 cannot exchange data for a vehicle communication service with the first terminal 510 and the second terminal. That is, a terminal in a location where a physical signal cannot reach may not be able to communicate with other terminals, base stations, servers, and the like.

For example, a case in which the fourth terminal 540 outside the network coverage needs to access the network for a vehicle communication service or a commercial service may be considered. At this time, if D2D communication is possible with the RSU (Road Side Unit 560) existing within the network service range through D2D communication, the RSU performs a relay function, so that the fourth terminal 540 outside the network coverage communicates with the base station through an indirect path. Data can be transmitted and received. In this case, as an example, the RSU 560 may be a UE type for a sidelink interface. Also, it may be a UE type for the Uu interface. Alternatively, in the sidelink interface, the UE type, but the radio interface between the RSU 560 and the base station may be defined as another interface for radio backhaul. The above-described wireless backhaul may be applied to messages and procedures used in wired backhaul between base stations defined in LTE and / or NR systems. Alternatively, the above-described wireless backhaul adds an adaptation layer to the message of the above-described RLC and / or PDCP layer in the above-described wireless backhaul based on the functions of the RLC and PDCP layers defined in the existing LTE and / or NR systems. It is also possible to define and operate a new message for transmitting and receiving between the lower layer, the adaptive layer. However, the RSU 560 may be of other types and is not limited to the above-described embodiment. That is, the RSU 560 serves as a relay so that the fourth terminal 540 can transmit vehicle communication service data to the RSU 560 through the side link SL. The RSU 560 may transmit the vehicle communication service data to the base station 550 using uplink (UL) transmission through the Uu interface. Thereafter, the first terminal 510 and the second terminal 520 from the base station 550 may receive vehicle communication service data of the fourth terminal 540. That is, the terminal located outside the network coverage may perform data transmission to terminals within the network coverage through a relay terminal such as an RSU and a base station of the relay terminal.

As another example, FIG. 6 is a diagram illustrating a D2D communication scenario. At this time, referring to FIG. 6, the fourth terminal V2X UE4, 640 may transmit data to the RSU 660 as described above. In this case, as an example, the data may be vehicle communication service data as described above. In the above-described case, the third terminal (V2X UE3, 630) may be a terminal capable of sidelink communication with the RSU 660, although it exists in a position where communication with the fourth terminal 640 is impossible. At this time, the third terminal 630 also needs to check the data of the fourth terminal 640. In more detail, since the V2X service is sensitive to delay time, the RSU 660 is configured to transmit data received from the fourth terminal 660 to the base station 650 through the Uu interface (LTE or NR uplink). In addition to the preparation, there is a need to perform preparations for passing data through the sidelink. That is, the RSU 660 may transmit data to the base station 650, and data transmission may be performed through sidelink communication to reduce a delay time that occurs while it is transmitted to the RSU 660 again. For example, the RSU 660 may operate in a mode controlled by a base station or a terminal autonomous determination mode, which will be described later. At this time, when the RSU 660 operates in a mode controlled by the base station, data received from the fourth terminal 640 is determined to be included in buffer status reporting (BSR) for transmission in LTE or NR, and at the same time. It may be determined as data to be included in the link (SL) BSR. That is, the vehicle communication service data received from the above-mentioned fourth terminal 640 is transmitted to the PDCP / RLC layer in the RB (radio bearer) of the LTE side, and the same information is transmitted to the PDCP / RLC layer in the RB of the sidelink side. You can.

At this time, PPPP (ProSe Priority per Packet) of data delivered to the sidelink side RB may maintain the priority of the received packet. For example, when there is no sidelink-side RB mapped to the priority of the received packet, the RSU 660 may configure a new RB supporting priority and transmit the packet by itself, limited to the above-described embodiment Does not work.

In addition, although referred to as D2D communication in the above, it may be V2X communication, and the above-described contents may be equally applied. However, the above-mentioned bar is referred to as D2D communication for convenience of description, but is not limited to the above-mentioned.

Base station scheduling mode / terminal autonomous decision mode (mode 3 / mode 4)

For example, in the present disclosure, an operation mode may be defined according to a resource allocation method for control information and data transmission for V2X communication or direct link (e.g. D2D, ProSe, or SL) communication.

For example, in the base station resource scheduling mode (eNodeB resource scheduling mode, mode 3), a base station or a relay node schedules resources used by a terminal to transmit V2X (or direct link) control information and / or data. Mode. Through this, the terminal may transmit V2X (or direct link) control information and / or data, and this mode may be the base station resource scheduling mode.

As an example, FIG. 7A may indicate a base station scheduling mode.

Referring to (a) of FIG. 7, the base station 710 may transmit system information for V2X sidelink communication to terminals 710 and 720 through a System Information Block (SIB). For example, the base station 710 may provide information related to V2X communication to the terminals 710 and 720 through a system information block including information related to V2X service and communication. The system information block may be SIB 21 and / or SIB 22. At this time, as an example, based on the received information, the terminals 710 and 720 may transmit information for V2X sidelink communication to other terminals. Further, as an example, when the terminal is in the RRC connected (RRC Connected) state, the base station 710 may transmit an RRC connection reconfiguration (RRC connection reconfiguration) message to the terminals 710 and 720 as shown in FIG. 7 (a). At this time, information for V2X sidelink communication may be transmitted in the RRC connection reconfiguration message. In addition, as an example, in the case of an out-of-coverage (OCC) in which the terminal does not exist in the base station coverage, the terminal cannot receive the above-described system information or RRC connection reset message, and related information through V2X sidelink communication from another terminal Can listen.

Meanwhile, as an example, the terminal may request a resource from the base station and receive resource allocation information from the base station. Referring to FIG. 7 (a), when data to be transmitted by the terminal 710 to the other terminal through the sidelink exists, the terminal 710 transmits a scheduling request (SR) to the base station 710 to present Provides UL grant information capable of receiving a message for reporting the buffer status information of the terminal, and based on the above-described uplink Grunt, the terminal buffers the amount and type of data to be transmitted through the sidelink. A status report message is transmitted to the base station 710 through an uplink. Based on the above-described report information, the base station 710 sidelinks scheduling information for resources to be used for data transmission through downlink control information (DCI) including sidelink grant (SL grant) information. Direct link) to the transmitting terminal (UE A, 720). Accordingly, the sidelink (or direct link) transmitting terminal 720 may transmit sidelink (or direct link) control information (SCI) and data to the sidelink (or direct link) receiving terminal (UE B, 730). . On the other hand, the sidelink (or direct link) receiving terminal (UE B, 730) may receive sidelink (or direct link) data based on the sidelink (or direct link) control information (SCI), the above-described implementation It is not limited to examples.

In addition, referring to (b) of FIG. 7, the UE autonomous resource selection mode (Mode 4) enables the UE to select resources used by the UE to transmit control information and data, and these resources The selection may be determined by a terminal sensing in a resource pool (ie, a set of resource candidates). Through this, the terminal can transmit control information and data, and this mode may be a terminal autonomous resource selection mode.

For example, the sidelink (or direct link) transmitting terminal (UE A, 740) is the sidelink (or direct link) receiving terminal (UE B, 750) from the resource of their choice, the sidelink (or direct link) control information and Data can be transferred. In this case, the side link (or direct link) receiving terminal 750 may receive side link (or direct link) data based on the side link (or direct link) control information.

In this case, as an example, the above-described base station resource scheduling mode may be referred to as mode 1 (mode 1) in side link (or direct link) communication for D2D or the like. In addition, the above-described base station resource scheduling mode may be referred to as mode 3 (Mode 3) in sidelink communication for V2X and the like. In addition, the terminal autonomous resource selection mode may be referred to as mode 2 in sidelink (or direct link) communication for D2D or the like. In addition, the terminal autonomous resource selection mode may be referred to as mode 4 in sidelink communication for V2X or the like. However, this is only one embodiment, and is not limited to the above-described name. That is, the same object and the same operation can be viewed in the same mode.

In addition, in the following description, V2X communication is described as a reference for convenience of description, but is not limited thereto. For example, the present invention may be equally applied to communication based on a direct link such as D2D, ProSe, etc., and is not limited to the above-described embodiment.

In addition, as an example, the UE may be considered to be within a reception range in a carrier used for V2X side link communication whenever a cell of the corresponding carrier is detected according to a specific criterion. Here, the criteria for detecting the cell of the above-described carrier is when a synchronization signal transmitted from a specific base station is received within the above-described carrier frequency band. At this time, the terminal authorized for V2X sidelink communication is within the coverage (region where network service is available) at the frequency used for V2X sidelink communication, or the V2X sidelink configuration is configured for the frequency through system information received from the base station. If it is confirmed that it is provided (including when the terminal is out of coverage at that frequency), the terminal uses the aforementioned scheduled resource allocation or terminal autonomous resource selection according to the base station configuration. If the terminal receives the system information block related to the V2X sidelink communication transmitted by the base station, but the information for configuring the V2X sidelink is not included in the above-described system information block, the terminal determines that V2X sidelink transmission and reception is necessary. At this point, an RRC message requesting a V2X service may be transmitted to the base station. If the terminal is out of coverage of the frequency used for V2X side link communication, and the base station does not provide a V2X side link configuration for that frequency, the terminal can use a full set of transmission and reception resources preconfigured in the terminal. That is, it may be based on the terminal autonomous decision mode.

At this time, as an example, in the base station scheduling mode, the terminal may request a transmission resource from the base station to transmit data, as described above. At this time, as an example, the base station transmits V2X-specific configuration information as shown in Table 3, and for this purpose, a signaling procedure (eg, RRC connection reconfiguration message) in a radio resource control (RRC) layer is performed. Can be used.

[Table 3]

In addition, as an example, a terminal autonomous determination mode (mode 4) may be considered. In this case, detailed configuration information for the transmission resource pool in mode 4 may be configured in the same manner as Table 3 above, which is detailed configuration information for the transmission resource pool for mode 3. At this time, in mode 4, a plurality of transmission resource pool information may be provided in a list form (SL-CommTxPoolListV2X). In addition, if necessary, the base station may transmit an RRC connection reconfiguration message to configure a new transmission resource pool operable in mode 4 or release some of the previously configured transmission resource pools, and is not limited to the above-described embodiment. In addition, the terminal may select itself some resources to be used for actual V2X data transmission among the resources in the transmission resource pool, and the base station may transmit reference parameter information, which is the basis for the terminal to make the selection, to the terminal.

For example, in mode 4, the base station may provide the information shown in Table 3 to the terminal through the RRC connection reconfiguration message similar to mode 3.

As another example, the UE in RRC IDLE mode in mode 4 may receive a system information block (referred to as V2X service related system information) including information related to a vehicle communication service from a base station. At this time, the terminal may configure the transmission resource pool itself based on the received system block information. In this case, as an example, the V2X service related system information block may be SIB 21 or SIB 22.

At this time, SIB 21 may include a variety of configuration information for V2X sidelink communication. For example, SIB 21 may include V2X common configuration information (V2X-ConfigCommon). Here, the common configuration information may include at least one or more of the information disclosed in Table 4 below. That is, information for V2X sidelink communication may be included.

[Table 4]

In addition, as an example, additional information that is not included in SIB 21 as information for V2X sidelink communication may be included in SIB 22. In this case, as an example, SIB 22 may include the same carrier information as SIB 21. When SIB21 and SIB22 include the same carrier information, SIB22 may include carrier configuration information not included in SIB21.

As another example, SIB21 and SIB22 may include different carrier information. When SIB21 and SIB22 include different carrier configuration information, each SIB may include different carrier configuration information. In this case, as an example, the information included in the above-described SIB 22 may include information shown in Table 5 below.

[Table 5]

In addition, as an example, when the base station does not provide reference parameter information through the system information block as described above, it may be considered that the terminal is in the RRC IDLE mode, or the terminal is located outside the network coverage. That is, when it is impossible to receive the reference parameter information from the base station, the terminal may perform a resource selection operation in the transmission resource pool using the parameter information stored in the internal memory. For example, the pre-configuration information of V2X may include information signaled through SIB 21 and SIB 22 as shown in Tables 4 and 5 described above. That is, the terminal may store the above-described information as parameter information in the internal memory as predetermined information. In addition, other information for the terminal to perform V2X sidelink communication may be further included, and is not limited to the above-described embodiment.

 In addition, as an example, the reference parameter information or the parameter information stored in the terminal is not only information signaled through SIB21 and SIB22, but also RSRP (reference signal received power) of a physical sidelink shared channel (PSSCH) required when selecting a resource in a transmission resource pool. It may include information about the reference value based on. At this time, RSRP may correspond to the energy level of the signal in the V2X system.

In addition, the reference parameter information or the parameter information stored in the terminal may include transmission profile (Tx profile) information for determining a sidelink transmission format. As an example, “v2x-TxProfileList” indicates a transmission format used as a Tx profile pointer index for each Tx profile. For each entry, a value of “REL14” indicates that the terminal will use a “Release 14” compatible format to send V2X packets. In addition, as an example, the “REL15” value may indicate that the terminal will use the “Release 15” format to transmit the corresponding V2X packet, and is not limited to the above-described embodiment.

In addition, the reference parameter information or the parameter information stored in the terminal may include information related to the PPPP value, and the above-described information may be used to determine priority for data.

In this case, as an example, a terminal operating in mode 4 may select a resource by itself through at least one of the above-described SIB 21, SIB22, and pre-configuration information. In this case, as an example, the concept of a zone may be used when a terminal selects a resource by itself. Zones can be configured or pre-configured by the base station, which, once configured (or pre-configured), will be divided into geographic regions using a single fixed reference point (i.e., geographic coordinates (0, 0)), length and width. In addition, a divided area may be defined as a zone. The terminal may determine the zone ID using the length and width of each zone, the number of zones, a single fixed reference point, and the geographical coordinates of the current location of the terminal. At this time, the zone may be configured both inside and outside the network coverage. When the terminal is within network coverage, the length and width of each zone and the number of zones may be provided to the terminal by the base station. On the other hand, if the terminal is out of network coverage, the terminal may use pre-configured zone information.

Based on the mapping relationship between the transmission resource and the zone, the terminal can select the V2X sidelink resource pool for the zone where the terminal is located. Thereafter, the UE may select a sidelink resource by performing sensing based on the selected resource pool. Sensing is a resource selection mechanism, and the terminal selects / reselects some specific sidelink resources and reserves transmission resources based on the sensing result. Up to two transmission resource reservation processes are allowed to the terminal, and at this time, the transmission resource reservation process is performed in parallel. However, at this time, the UE can perform only a single resource selection for V2X sidelink transmission.

On the other hand, as an example, the mode 3 and mode 4 terminals may have different methods for determining the sidelink transmission format according to the terminal version, and the method for determining the sidelink transmission format based on the terminal version is described below.

Operation according to the functions supported by the terminal

V2X terminal may support different functions according to the terminal version. For example, the terminal may operate in consideration of backward compatibility with the previous version while supporting a new function as the version is changed. As an example, a V2X terminal operating based on the first version (e.g. Release 14) may be considered. Also, as an example, a V2X terminal operating based on the second version (e.g. Release 15) may be considered. At this time, the V2X terminal operating based on the second version is a new function compared to the first version, and may support carrier aggregation (CA). At this time, carrier aggregation may mean that the terminal uses a plurality of carriers. For example, a carrier or a serving cell that a V2X terminal supporting a sidelink can be used as a sidelink (that is, a V2X service is possible through SIB, and a carrier or serving that provides at least one transmission resource pool information or reception resource pool information) Cell) may be considered. At this time, the V2X terminal supporting the sidelink can simultaneously transmit and receive data through the identified carrier or serving cells, and in this case, it can be said that the corresponding V2X terminal supports the sidelink CA.

Also, as an example, when a V2X terminal supporting a sidelink has at least two or more serving cells available as a sidelink, it is confirmed that the serving cell is confirmed while providing V2X carrier configuration information that can be used in each serving cell. If data can be transmitted and received at the same time, it can be said that the corresponding V2X terminal supports sidelink CA.

At this time, the sidelink CA can be supported by both V2X terminals in coverage and V2X terminals out of coverage. When selecting a carrier, the UE may select multiple carriers based on a Channel Busy Ratio (CBR) value and a PPPP value of a V2X message to be transmitted. The UE supporting the sidelink CA can perform packet duplication for transmitting the duplicated packets through different carriers. At this time, the PPPR value of each V2X message may be used as a criterion for activating / deactivating packet replication. The PPPR reflects the requirement for the reliability of the data packet, and is defined as a parameter that can be divided into 8 steps having values of 0 to 7 or 1 to 8. At this time, the difference in reliability of each step may be set to 10 times. For example, a requirement of 10% error rate may be assigned to a PPPR value of 8, a requirement of 1% error rate to a PPPR value, and a requirement of 0.1% error rate to a PPPR value of 6, or the like.

As another example, the V2X terminal operating based on the second version may support a new transmission format as a new function compared to the first version. For example, a new transport format may be used to support advanced V2X services such as vehicle cluster driving and remote driving. At this time, the second version V2X terminal supports a maximum data transmission rate using a high level modulation scheme and channel coding (Modulation and Coding Scheme, MCS), and can improve V2X performance.

In more detail, the second version V2X terminal may further support carrier aggregation and a new transport format in addition to the first version V2X terminal. In this case, as an example, there is a need to coexist for different version terminals in relation to the first version and the second version. That is, even a new version terminal may need to be compatible or coexist with the previous terminal. In this case, as an example, the second version (e.g. Release 15) may be a later version than the first version (e.g. Release 14). That is, the terminal corresponding to the late version may consider backward compatibility for coexistence with the previous version. In addition, as an example, the above-described first version and the second version are only one example, and in other versions (eg Release 16), there is a need to ensure backward compatibility with previous versions as described above, and the above-described implementation It is not limited to examples.

Meanwhile, in the case of a V2X terminal, a V2X service that is directly related to the driver's life may be considered, such as preventing collisions between vehicles and informing hazards of a driving route in advance. Therefore, as described above, the message for the V2X service needs to be received by all terminals regardless of the release of the terminal.

At this time, as an example, as described above, when the second version (eg Release 15) V2X terminal applies a new transmission format, the first version (eg Release 14) V2X terminal does not use the new transmission format. The version terminal may not receive the message. Accordingly, a problem that terminals supporting different versions (or releases) may not coexist may occur, and a transmission profile (Tx profile) may be used to solve this problem, which will be described below.

In this case, as an example, the second version (e.g. Release 15) V2X terminal may use a transmission profile (Tx profile) in consideration of compatibility with the first version (e.g. Release 14) V2X terminal. At this time, the terminal may determine the transmission format for the V2X message through the index value indicated by the transmission profile. More specifically, a transmission profile can be applied to each V2X message transmitted through the PC5 interface. In this case, the application layer may determine the index value of the transmission profile according to the priority of each message. For example, in the case of V2X messages related to safety, it is necessary for all terminals to receive V2X messages regardless of the terminal version (or release). Accordingly, the application layer may configure a transmission profile for the first version so that the terminal applies the first version (e.g. Release 14) transport format. On the other hand, in the case of a message for a service that is applied only between terminals of a higher version (e.g. cluster driving, remote driving), the first version terminal does not need to receive the above-described V2X message. Therefore, the second version V2X terminal can use the new transmission format, support the maximum data transmission rate, and improve V2X performance. At this time, the application layer of the terminal may configure a transmission profile so that the terminal applies a transmission format based on the second version. For example, in the transmission profile, an index value may be used to indicate that the first version (e.g. Release 14) transmission format or the second version (Release 15) transmission format is used. In this case, “Tx profile 1” may mean a transmission format based on the first version. Also, “Tx profile 2” may mean a transmission format based on the second version. The transmission profile may provide information on a transmission format used based on the service type. In addition, as an example, the transmission profile is not limited to the above-described first version and second version, and when another version exists or is applied, an index value for indicating this may be additionally defined. That is, the transmission profile may be information for indicating a transmission format used for message transmission, and is not limited to the above-described embodiment.

Based on the above, when “Tx profile 1” is provided for each V2X message to be transmitted based on the transmission profile, one MCS value is set using an MCS table for the first version, It can be applied to transmission. On the other hand, when “Tx profile 2” is provided based on the transmission profile, one MCS value may be set using an MCS table for the second version, and transmission may be performed using rate matching. In this case, as an example, selecting one MCS value from among values in the MCS table may vary depending on the terminal implementation, and is not limited to the above-described embodiment.

However, as an example, a case in which multiple V2X messages are multiplexed in one MAC PDU may be considered. At this time, the determination of the transmission format for the above-described MAC PDU transmission may follow the transmission profile of the V2X message for the highest priority, and is not limited to the above-described embodiment. That is, based on the above, the terminal can always transmit the V2X message through the PC5 interface after determining the transmission format according to the transmission profile.

In addition, as an example, the transmission format of the first version (e.g. Release 14) terminal can be applied only one. More specifically, as described above, since the first version is an older version than the second version, the terminal based on the second version must operate in consideration of compatibility with the terminal based on the first version, but the first version terminal Since the service for the terminal based on the 2 version is not provided, there is no need to consider this. Accordingly, when the base station instructs to apply a specific MCS value, the UE can determine a transmission format according to the MCS value. On the other hand, if the base station does not instruct to apply a specific MCS value, the terminal may select and apply one of the values corresponding to the MCS range based on the first version, and is not limited to the above-described embodiment.

On the other hand, as an example, various different services required for the next generation mobile communication system (eg, tangible content, mobile hologram display, smart home service, etc.) are eMBB (enhanced Mobile Broadband), URLLC (Ultra-Reliable and Low Latency Communications). And a service type of at least one of mMTC (massive machine type communication). At this time, the requirements required to support the three types of services described above may have different criteria even in the same requirements. For example, in the case of the eMBB service, the requirement items for latency may have different reliability for each channel through which data matching various types and purposes is transmitted. For example, for data having different QoS, there may be various criteria such as an error degree of reliability of 1%, 0.01%, or 0.001%, respectively. The eMBB service has a requirement criterion that the delay time that occurs during unidirectional communication between layer 2 in the terminal and layer 2 in the base station should not exceed 4 ms, based on the above reliability, whereas in the case of URLLC, 0.5 in the same environment. There is a requirement criterion not to exceed ms.

In order to satisfy the requirements of different requirements, a unit of radio resources defined as time / frequency / space, which is the most basic unit, can have a great influence. In the case of the delay time as in the above example, when defining one radio resource, the larger the amount of the time resource, the longer the delay time. In particular, in the case of a time resource unit that transmits a single MAC PDU, such as TTI, it is a necessary time for data transmission, and thus, when designing a frame structure for physical channels and radio resources, the length of the TTI may have a great influence on the delay time.

At this time, based on the above, a numerical value (or value) operated in a wireless communication system may be referred to as a numerology. Hereinafter, based on the above, a numerical value for a time and / or frequency resource unit criterion for transmission time interval (TTI) and / or wireless communication is referred to as a neuromerology.

On the other hand, in the NR (New Radio) system being discussed as one of the next generation mobile communication system, a frame structure including at least two different numerology may be applied.

At this time, as an example, Figure 8 is a view showing a radio resource that is different from each other different neurology. In this case, the OFDM symbol interval and the subcarrier bandwidth may be configured differently for each pneumatics, and the TTI length may also be configured differently. At this time, the length of the OFDM symbol interval between numerology may always have a relationship of 2n (n is a natural number) times. However, as an example, in the case of TTI, an example of a relationship of 2n (where n is a natural number) is shown in FIG. 8, but other relationships are also possible. For example, it may be redefined as part of the section defined by the TTI described above.

In this case, as an example, the new technology may be variously configured to satisfy various services and requirements of the NR system. Referring to Table 9 below, numerology may be defined based on subcarrier spacing (SCS), CP length, and the number of OFDM symbols per slot used in an orthogonal frequency division multiplexing (OFDM) system. The above-described values may be provided to the terminal through higher layer parameters DL-BWP-mu and DL-BWP-cp (DL) and UL-BWP-mu and UL-BWP-cp (UL).

In addition, as an example, in Table 6 below, when 2 is 2 and the subcarrier spacing is 60 kHz, normal CP and extended CP may be applied, and only normal CP may be applied in other bands.

[Table 6]

At this time, the normal slot (Normal slot) can be defined as a basic time unit used to basically transmit one data and control information in the NR system. The length of the normal slot may basically consist of the number of 14 OFDM symbols. In addition, unlike the slot, the subframe has an absolute time length corresponding to 1 ms in the NR system and can be used as a reference time for the length of another time interval. At this time, for coexistence or compatibility (backward compatibility) of the LTE and NR systems, a time period such as a subframe of LTE may be required for the NR standard, and is not limited to the above-described embodiment.

NR Sidelink BSR (NR SL BSR)

The NR sidelink BSR may be a procedure for providing information on the amount of data to be transmitted from the MAC entity to the sidelink to the gNB. In this case, as an example, the RRC may configure parameters necessary for the BSR procedure and control the BSR procedure. For example, parameters such as Table 7 below may be configured in the RRC to control the BSR. In this case, as an example, based on Table 7 below, the BSR may be reported for each LCG (Local Channel Group). In this case, “periodicBSR-TimerSL” in Table 7 below may be a timer for periodic BSR transmission. In addition, “retxBSR-TimerSL” may be a timer for BSR retransmission when resource allocation for the BSR is not received.

[Table 7]

More specifically, each logical channel (hereinafter referred to as LC) may be assigned to any LCG by the UE. At this time, when the data packet to be transmitted to the sidelink is transmitted from the upper layer (application), the UE generates a new LC based on QFI (QoS (Quality of Service) Flow Identity) in the data packet, or data through the previously generated LC. Packets can be sent. In this case, as an example, the base station may configure QFI value (s) corresponding to a specific LCG. Accordingly, the terminal may be configured to include the LCs containing the QFI value in the LCG corresponding to the QFI value. That is, the terminal may be configured to include each logical channel in the corresponding LCG based on the QFI indicating the flow in consideration of QoS. In this case, as an example, the maximum number of LCGs may be 8. In addition, the MAC entity of the terminal may calculate the amount of data of each LC according to the transmittable data calculation method defined in the RLC layer and the PDCP layer, and determine the amount of sidelink data that can be transmitted based on this. At this time, the calculation of the amount of transmittable data defined by the RLC layer and the PDCP layer may include data stored in the buffer in the layers and data changed in format for transmission to another layer.

In addition, as an example, 5QI (5G QoS Indicator) value may be defined as shown in Table 8. Referring to Table 8, 5QI values may be set for each resource type. At this time, the resource type may be divided into a GBR (Guaranteed Bit Rate) in which bandwidth is guaranteed and a non-GBR in which bandwidth is not guaranteed. The 5QI value may be assigned based on the service provided, and each 5QI value may have a different priority. Here, when the 5QI is mapped to the QFI, if the 5QI value is less than 64, which is the range of the QFI value, for the Non-GBR (Non-Guaranteed Bit Rate) QoS Flow, the 5QI value can be directly mapped to the QFI value. However, when the 5QI value is out of the range of the QFI value, dynamic allocation may be used. More specifically, a device including a function of mapping QoS flows to QFI values within a network may be considered. In this case, when a protocol data unit (PDU) session of a user plane is activated, 5QI having a value of 64 or more may be dynamically allocated and set as a specific QFI value. Therefore, the same 5QI may be mapped to different QFI values whenever the above-described PDU session is activated.

[Table 8]

On the other hand, as an example, the above-described QoS parameter can use a QFI (QoS Flow ID) value mapped based on 5QI values of Table 9 below among 5QI values defined in Table 8 below. That is, the OFI value mapped based on 5QI values may be used in connection with the V2X sidelink. In this case, as an example, a VFI (V2X QoS flow indicator) value based on Table 9 below may be used. More specifically, VFI may be a value set in consideration of the QoS of the V2X sidelink. At this time, the VFI index may be set separately from the QFI index. For example, VFI may be set to an index having a value of 1 to 8 based on Table 9 below. As another example, VFI may be set to an index having a value of 1 to 16, but is not limited to the above-described embodiment. Hereinafter, for convenience of description, an embodiment will be described based on QFI, but may be replaced with VFI. That is, a value corresponding to each LCG may be QFI or VFI, and is not limited to the above-described embodiment.

[Table 9]

In this case, as an example, based on the above, the BSR may be triggered based on the following conditions.

For example, ID information allocated only to a specific terminal may be configured to receive resource allocation information from a base station to a V2X terminal operating based on mode 3. In this case, as an example, based on V2X mode 3, “SL-V-RNTI” may be configured as ID information in the terminal. In this case, when “SL-V-RNTI” is configured in the terminal as ID information, the BSR may be triggered based on Table 10 below. More specifically, as a case where “SL-V-RNTI” is configured in a terminal, an LC for one destination is included in an arbitrary LCG, and triggers a BSR when there is new sidelink data that can be transmitted in the LC. You can. In addition, when the “SL-V-RNTI” is configured in the terminal and the new sidelink data that can be transmitted has a higher data priority than the transmittable sidelinks in all LCs having the same destination, the BSR is triggered. You can. In addition, as an example, when the SL-V-RNTI ”is configured in the terminal and there is no sidelink data that can be transmitted in all LCs in all LCGs having the same destination, the BSR may be triggered.

Table 10

In this case, as an example, in the case of Table 10, a regular side link BSR (Regular SL BSR) transmission procedure may be performed. In addition, as an example, an uplink resource is allocated, and the number of padding bits is equal to or greater than the sum of the lengths of the BSR MAC CE and subheaders including information about one LCG in one destination. In a large case, a padding sidelink BSR (Padding SL BSR) may be triggered.

In addition, as an example, when “retxBSR-TimerSL” expires and uplink data exists in at least one LC included in any LCG, a regular sidelink BSR may be triggered. In addition, as an example, when “periodicBSR-TimerSL” expires, a periodic sidelink BSR (Periodic SL BSR) may be triggered.

As an example, a case where the regular sidelink BSR and periodic sidelink BSR is triggered may be considered. In this case, if the MAC grant can be generated including all LCGs of all destinations including sidelink data that can be transmitted, the number of allowable bits of an uplink grant is transmitted to all destinations that include sidelink data that can be transmitted. The NR SL BSR MAC CE format including information on LCGs may be configured and reported. On the other hand, if it is not possible to generate a MAC PDU including all LCGs of all destinations including sidelink data that can be transmitted, the number of transmission grant bits of an uplink grant can be configured and reported as a SL Truncated BSR format. At this time, the information included in the SL Truncated BSR may be configured to include as many LCGs as possible in consideration of the number of allowed bits of the uplink grand, and is not limited to the above-described embodiment.

Meanwhile, a case in which the padded BSR is triggered may be considered. At this time, if the number of padding bits can generate a MAC PDU including all LCGs of all destinations including transmittable sidelink data, LCGs of all destinations including transmittable sidelink data The NR SL BSR MAC CE format including information may be configured and reported.

On the other hand, if the number of padding bits cannot generate a MAC PDU including all LCGs of all destinations including transmittable sidelink data, the SL Truncated BSR format can be configured and reported. In this case, as an example, the information included in the SL Truncated BSR may allow as many LCGs to be included as possible in consideration of the number of allowable bits of the uplink grant.

NR SL BSR MAC CE format

The NR SL BSR MAC CE format and the LTE SL BSR MAC CE format may be different. In this case, as an example, FIGS. 9 and 10 may be a format for LTE SL BSR MAC CE. In this case, FIG. 9 may be a case where N is an even number in relation to the LTE SL BSR MAC CE format. At this time, as an example, referring to FIG. 9, the destination index may be 4 bits. At this time, the maximum supported LCG may be 4, and the LCG field length may be 2 bits. In addition, the buffer size information (Buffer Size) may be defined as 6 bits. Therefore, information on the buffer size level can be used as an index corresponding to 6 bits. In addition, as an example, in LTE SL BSR MAC CE, a value corresponding to each LCG may be PPPP. On the other hand, in the following NR SL BSR MAC CE, a value corresponding to each LCG may be QFI.

In addition, as an example, as shown in FIG. 9, information corresponding to two destination indexes and two LCGs may be included in 3 Octet. Therefore, when N is even, it may be configured as shown in FIG. On the other hand, if N is odd, the remaining bits after the buffer size information as shown in FIG. 10 may remain as R (Reserved) bits, which is not limited to the above-described embodiment.

On the other hand, as described above, in the case where the NR SL BSR is triggered, the NR SL BSR MAC CE format may be configured and reported. In this case, as an example, in the method of configuring the SL BSR MAC CE format, as described above, in a new system (e.g. NR), a long BSR MAC CE format may be defined as a format having a variable length. At this time, as an example, in the new system, the LCG may be increased to 8 (4 existing). At this time, in the NR system, there is a need to support finer QoS in response to the LCG, so it can be set to eight more than the existing system (e.g. LTE). As described above, when the LCG is increased, if information about all LCGs is included, the length of the BSR MAC CE is increased, and the amount of resources required for the base station to receive the BSR can be increased. Therefore, since it can be a burden to the base station, it can be defined as a format having a variable length as a Long BSR MAC CE format. Meanwhile, as an example, as described above, in the existing system (e.g. LTE), BSR MAC CE is configured by always including information on all LCGs. That is, in the new system (e.g. NR), as the LCG is increased to 8, the BSR MAC CE format can be defined to have a variable length, and is not limited to the above-described embodiment.

In addition, as an example, NR SL BSR MAC CE may be as shown in FIG. 11. In more detail, referring to FIG. 11, a field indicating a 5-bit destination in the NR SL BSR MAC CE may be located. At this time, the field indicating the destination may be a destination index. At this time, as described above, in the existing system (e.g. LTE), the field indicating the destination may be 4 bits. On the other hand, a field indicating a 5-bit destination in the NR SL BSR MAC CE may be located. In this case, as an example, the value of the destination index may have a correspondence to the L2-destination ID defined by 24 bits. For example, the terminal may configure a correspondence relationship between the above-described destination index and L2-destination ID and report it to the base station through an RRC message. At this time, as an example, in the existing system, it could be used to distinguish a service in relation to an L2-destination ID. However, in the new system, it is necessary to distinguish and instruct not only services related to L2-destination ID, but also information about unicast, broadcast, and group. Therefore, the field indicating the destination may be set to 5 bits differently from the existing one so as to correspond to the information as described above. In this case, as an example, in relation to the destination index and L2-destination ID correspondence reported as described above, the L2-destination ID may include a list for broadcasting and group casting. In this case, as an example, the list for broadcasting and group casting may include K L2-destnation IDs. In addition, the L2-destination ID may include a list for unicast. In this case, as an example, the list for unicast may include M L2-destination IDs. That is, the L2-destination ID may include a list for broadcast and group casting and a list for unicast. In this case, as an example, the above-described K and M are natural numbers and may be 32 or less. At this time, the correspondence between the destination index and the aforementioned lists may have a correspondence in ascending order from the first of the L2-destination ID list for broadcasting and groupcasting. Subsequently, after the last value of the broadcasting and groupcasting list, a corresponding relationship may be in ascending order from the first of the L2-destination ID list for unicast, and is not limited to the above-described embodiment. In addition, in one error, in the NR SL BSR MAC CE, the LCG field may be 3 bits. Also, in the NR SL BSR MAC CE, the buffer size information field may be 8 bits.

In this case, as an example, in the NR SL BSR MAC CE in relation to the NR sidelink, the QFI value may be equally applied to the NR sidelink in relation to QoS of the base station and the terminal. Therefore, as described above, since the LCG can correspond to the QFI, in the NR SL BSR MAC CE with respect to the NR sidelink, the LCG can also be set to eight.

That is, through the above, it is possible to provide buffer status information for one destination and one LCG through 16 bits. At this time, as an example, the maximum transmittable destination and the LCG may be as shown in FIG. 11. That is, N destinations and LCG information may be configured based on “2N Oct”, and is not limited to the above-described embodiment. Here, since the above-described N value may include buffer status information for up to 8 LCGs for each of 32 destinations, the maximum N value may be 256. If there are no destinations and LCGs where data is present, the N value can be zero. At this time, the NR SL BSR can be transmitted by including only the MAC subheader indicating that the NR SL BSR is the corresponding. The MAC subheader for the NR SL BSR may be configured by including 6 bits of an LCID indicating that it is an NR SL BSR and an 8 bit L field indicating the length of the corresponding MAC CE.

Further, as an example, an index corresponding to an 8-bit buffer size (BS) field used in the NR SL BSR MAC CE format may be as shown in Table 11 below. At this time, the BS is 8 bits, and a total of 256 indices may correspond, and may correspond to respective BS values, and is not limited to the above-described embodiment.

[Table 11]

In addition, as an example, when configuring the NR SL BSR MAC CE as shown in FIG. 11, the “R” bit does not remain in the LTE SL BSR MAC CE as shown in FIGS. 9 and 10 based on the “Octet” unit. There may be an effect that it can be set, and this can increase resource efficiency.

At this time, as an example, the following embodiments will be described based on the above-described NR SL BSR MAC CE format and LTE SL BSR MAC CE format. That is, the following embodiments may be applied in consideration of using different BSR formats, and the following embodiments may operate based on the above-described format.

Example

The following describes a radio resource request method for a terminal to transmit / receive data through a side link in an NR system. At this time, as an example, in the following embodiment, the terminal may enable sidelink communication for a plurality of RATs (radio access technology). In this case, when the terminal performs sidelink transmission or reception of a data packet through a specific RAT, the terminal performs a sidelink transmission or reception operation through another RAT before transmission or reception of the above-described data packet is all completed. Can not. For example, the terminal may perform data transmission and reception through the LTE sidelink and the NR sidelink, and the resource request procedure for this will be described below. More specifically, the terminal needs to support both the LTE sidelink and the NR sidelink, and it may be possible to operate based on any one. At this time, when the terminal is connected to either an LTE base station or an NR base station as one base station, and operates based on a sidelink different from the connected system, a resource request procedure may be required, which will be described below.

Example 1 (when both LTE and NR are configured in mode 3)

For example, the terminal may operate in the base station scheduling mode (mode 3) based on the above. At this time, the terminal may receive information about scheduling from the LTE base station. In addition, the terminal may receive information about scheduling from the NR base station.

In more detail, the UE may configure buffer status information for all currently operating V2X services to a base station that has an RRC connection established, and transmit buffer status information (BSR) to the base station. At this time, the base station receiving the above-described BSR can divide the resources to be allocated to the LTE sidelink and the resources to be allocated to the NR sidelink based on the received BSR information, and generate a sidelink grant and transmit it to the terminal.

Example 1-1 (Resource Request Procedure by LTE Base Station)

For example, it is possible to consider a case in which the UE has an RRC connection established with an LTE base station (e.g. ng-eNB) or an LTE base station has dual connectivity (DC) as a master base station. In this case, as an example, the terminal may simultaneously use radio resources provided by a plurality of base stations through a dual connection. In a dual connection, a master base station and a secondary base station can be determined. For example, the master base station may be an LTE base station, and the secondary base station may be an NR base station (e.g. gNB). Further, as an example, the master base station may be an NR base station, and the secondary base station may be an LTE base station, but various combinations are possible without being limited to the above-described embodiment.

On the other hand, if the LTE base station in the above-described case is the master base station (or the terminal is RRC connection establishment with the LTE base station), it is possible to provide buffer data information for all V2X services using the LTE SL BSR format. At this time, as described above, the value corresponding to the LCG in the LTE SL BSR MAC CE format may be a PPPP value rather than QFI or VFI. Accordingly, the base station can provide the corresponding terminal with PPPP values corresponding to each of the four LCGs in the form of a list. Next, after receiving the BSR, the base station can check the V2X service corresponding to the LCG in the received BSR message, and then determine which RAT resource to allocate among the LTE resource pool or the NR resource pool. At this time, the base station may consider at least one of a service type according to a frequency band of the LTE / NR resource pool and a loading situation for a radio resource. It is also possible to further consider other situations, and is not limited to the above-described embodiment. At this time, the base station may transmit resource allocation information for LTE and resource allocation information for NR using DCI in the PDCCH of LTE in the form of sidelink grants. That is, the LTE base station may provide one or more of resource allocation information for LTE and resource allocation information for NR to the terminal. At this time, when the LTE base station configures DCI (Downlink Control Information) for radio resource allocation for the NR sidelink, DCI reuses all or part of the DCI configuration used when the NR base station allocates the NR sidelink radio resource. It can be, and is not limited to the above-described embodiment. At this time, the above-mentioned information includes time / frequency resource allocation-related index or resource range information, information to be transmitted through SCI when the transmitting terminal transmits a sidelink, BWP (BandWidth Part) information, QFI or VFI information, and Modulation and Coding Scheme) information. Also, other information may be further included, and is not limited to the above-described embodiment. Next, the terminal may transmit V2X data through the LTE sidelink and / or the NR sidelink based on the sidelink grant.

More specifically, FIG. 12 is a diagram illustrating a method of providing resource allocation information to a terminal based on an LTE base station (ng-eNB).

In this case, referring to FIG. 8, the LTE base station (ng-eNB, 1220) and the NR base station (gNB, 1230) may share information about the resource pool. That is, the LTE base station 1220 may receive information about the NR resource pool from the NR base station 1230. Thereafter, the LTE base station 1220 may provide the UEs 1210 with parameter information related to the sidelink BSR, such as PPPP values corresponding to the LCG. Thereafter, since the terminal 1210 is connected to the LTE base station 1220, the buffer state information may be transmitted to the LTE base station 1220 based on the LTE SL BSR. That is, the terminal 1210 may transmit buffer state information to the LTE base station 1220 based on the LTE SL BSR MAC CE format. Thereafter, the terminal 1210 may receive information on the sidelink grant from the LTE base station 1220. In this case, as an example, as described above, the sidelink grant may include any one or more of resource allocation information for LTE and resource allocation information for NR, as described above. Thereafter, the terminal 1210 may transmit V2X data through the LTE sidelink and / or the NR sidelink based on the information received from the LTE base station 1220.

Example 1-2 (resource request procedure by NR base station)

As another example, it is possible to consider a case in which the UE has an RRC connection setup with an NR base station (gNB) or a DC setup with the NR base station as a master base station. At this time, the terminal may provide buffer data information for all V2X services based on the NR SL BSR format.

More specifically, the base station may provide the corresponding terminal with QFI or VFI values corresponding to each of 8 LCGs in a list form. At this time, as described above, in the NR SL BSR MAC CE format, 8 LCGs may be set, and a QFI or VFI value may correspond to each LCG. At this time, the base station may provide the QFI or VFI value to the terminal in the form of a list. Thereafter, the terminal may report the BSR to the base station based on the NR SL BSR MAC CE format. After confirming the V2X service corresponding to the LCG in the received BSR message, the base station can determine which RAT resource to allocate among the LTE resource pool and / or the NR resource pool. Thereafter, the base station may consider a service type and a load situation for a radio resource according to the frequency band of the LTE resource pool and / or the NR resource pool based on the above. The base station transmits resource allocation information for LTE and resource allocation information for NR using DCI in the PDCCH of NR in the form of sidelink grants.

In this case, when the NR base station configures DCI for radio resource allocation for the LTE sidelink, DCI may reuse all or part of the DCI configuration used when the LTE base station allocates the LTE sidelink radio resource. It is not limited to one embodiment.

As another example, when the NR base station configures DCI for radio resource allocation for the LTE sidelink based on the difference between the PDCCH format of LTE and the PDCCH format of NR, the NR base station allocates the NR sidelink radio resource. Radio resource allocation information for the LTE sidelink may be included based on the DCI used. For example, except for the configuration of some fields irrelevant to the LTE sidelink in DCI used when the NR base station allocates the NR sidelink radio resource, the radio resource allocation information for the LTE sidelink is based on the remaining fields. As may be included, the DCI configuration used when the LTE base station allocates LTE sidelink radio resources may not be reused in whole or in part. However, the above is only one example, and may be configured in other ways, and is not limited to the above-described embodiment.

More specifically, FIG. 13 is a diagram illustrating a method of providing resource allocation information to a terminal based on an NR base station (gNB).

13, the NR base station (gNB, 1220) and the LTE base station (ng-eNB, 1230) may share information about the resource pool. That is, the NR base station 1220 may receive information on the LTE resource pool from the LTE base station 1230. Thereafter, the NR base station 1220 may provide the UEs 1210 with parameter information related to the sidelink BSR, such as QFI or VFI values corresponding to the LCG. Thereafter, since the terminal 1210 is connected to the NR base station 1220, the buffer state information may be transmitted to the NR base station 1220 based on the NR SL BSR. That is, the terminal 1210 may transmit buffer status information to the NR base station 1220 based on the NR SL BSR MAC CE format. Thereafter, the terminal 1210 may receive information on the sidelink grant from the NR base station 1220. In this case, as an example, as described above, the sidelink grant may include any one or more of resource allocation information for LTE and resource allocation information for NR, as described above. Thereafter, the terminal 1210 may transmit V2X data through the LTE sidelink and / or the NR sidelink based on the information received from the NR base station 1220.

Example 1-3 (resource request procedure in case of double connection)

As another example, a case in which a terminal and an LTE or NR base station have dual connectivity (hereinafter referred to as DC) set as a master base station may be considered. That is, the terminal can receive resource allocation from each base station. In this case, as an example, the terminal may provide buffer data information for some V2X services to the LTE base station using the LTE SL BSR format. In addition, the terminal may provide buffer data information for the remaining V2X services to the NR base station except for some of the above-described V2X services (buffer data information for the V2X service provided to the LTE base station) using the NR SL BSR format.

In this case, as an example, the UE may acquire relevant parameter information from the LTE base station and / or the NR base station through an RRC message such as an RRC connection reconfiguration procedure. More specifically, in case of performing LCG mapping based on QoS, the base station may not correspond to one BSR for all services. That is, the base station may provide a PPPP value corresponding to each of the four LCGs for LTE SL BSR in a list form for a service to be provided through the LTE sidelink. On the other hand, the base station may provide a QFI or VFI value corresponding to each of 8 LCGs in a list form for configuring a NR SL BSR for a service to be provided through an NR sidelink.

Also, as an example, the base station may not select only one for all services. At this time, the base station may provide parameter information for LTE sidelink and NR sidelink for a specific service. That is, for a specific service, both a PPPP value list for LTE SL BSR and a QFI or VFI value for NR SL BSR can be provided. At this time, the terminal may perform the specific service described above through the LTE sidelink and the NR sidelink. Meanwhile, as an example, the specific service described above may be a safety service. In more detail, in a case where safety is important, such as V2X, the safety-related service can be provided to both the LTE sidelink and the NR sidelink, and is not limited to the above-described embodiment. For the safety service, simultaneous transmission and reception through LTE sidelink and NR sidelink may also be possible. This is in accordance with the wireless communication capability (capability) of the terminal and can inform the base station through RRC signaling whether simultaneous transmission and reception of the aforementioned LTE and NR sidelinks is possible.

In addition, as an example, triggering for LTE SL BSR transmission may be performed when data corresponding to the above-described PPPP is included in a specific PDCP and / or RLC. In addition, triggering for NR SL BSR transmission may be performed when data corresponding to the above-described QFI or VFI is included in a specific PDCP and / or RLC. That is, the SL BSR for each RAT type can be operated independently.

Based on the above, the setting value and operation for the PUCCH resource and the BSR-related timers for transmitting a scheduling request (SR) corresponding to SL BSR for each RAT type may be independently set.

More specifically, FIG. 14 is a diagram illustrating a method that is independently operated based on dual connectivity. Referring to FIG. 14, the UE (UE, 1410) may acquire relevant parameter information from the LTE base station (ng-eNB, 1430) and / or the NR base station (gNB, 1420). As an example, as described above, the terminal 1410 may receive a PPPP value corresponding to each of four LCGs for LTE SL BSR in a list form. In addition, the terminal 1410 may be provided with QFI values corresponding to each of 8 LCGs in a list form for NR SL BSR configuration. That is, the terminal may receive parameters for LTE SL BSR and / or parameters for NR SL BSR.

Thereafter, the terminal 1410 may transmit the NR SL BSR to the NR base station 1420 based on the NR SL BSR format, and transmit the LTE SL BSR to the LTE base station 1430 based on the LTE SL BSR format. Thereafter, the terminal 1410 may receive sidelink grant information from each base station and perform NR sidelink and / or LTE sidelink communication based on this.

In addition, as an example, the R2 to transmit a data packet generated in the application layer through a transmission profile (Tx profile) or the like in the V2X application layer may be designated. At this time, as described above, version information applied to the terminal may be indicated through the transmission profile. In addition, as an example, RAT (LTE / NR) may be indicated through the transmission profile as described above, and is not limited to the above-described embodiment. Accordingly, the application layer may designate a corresponding data packet (PPPP or QFI) as a QoS parameter corresponding to the designated RAT. That is, the terminal may configure BSR format and information based on RAT information and QoS parameter information. At this time, as described above, each base station receiving the BSR checks for the V2X service corresponding to the LCG in the received BSR message, and then the LTE base station can perform resource allocation for the LTE resource pool. In addition, the NR base station can perform resource allocation for the NR resource pool. At this time, the base station may transmit the sidelink grant to the terminal based on the advanced resource allocation information, as described above. The terminal may transmit V2X data through LTE and / or NR sidelink according to the received sidelink grant.

In this case, as an example, FIG. 15 is a diagram illustrating a method of operating by designating an RAT based on a transmission profile.

15, RAT (LTE / NR) may be indicated as described above through a transmission profile. At this time, the application layer may designate a corresponding data packet (PPPP or QFI) as a QoS parameter corresponding to the designated RAT. For example, FIG. 15 (a) may be a case where an NR is indicated based on a transmission profile. At this time, the terminal 1510 may receive a data packet designated as QFI, and transmit the NR SL BSR to the base station based on this. Thereafter, the terminal 1510 may receive the sidelink grant and operate based on the NR sidelink.

Also, as an example, FIG. 15 (b) may be a case in which LTE is indicated based on a transmission profile. At this time, the terminal 1510 may receive a data packet designated as PPPP, and based on this, the LTE SL BSR may be transmitted to the base station. Thereafter, the terminal 1510 may receive the sidelink grant and operate based on the LTE sidelink.

Example 2 (when the transmission mode is different for each RAT)

The V2X transmission mode of the terminal may be set differently for each RAT. More specifically, the UE can basically set the same transmission mode for each RAT. However, the terminal may set different transmission modes for each RAT according to the configuration method.

For example, the terminal is set to mode 3 through an RRC message for LTE, and parameters corresponding thereto may be configured. On the other hand, the terminal may be set to mode 4 for NR. Also, the terminal may not include setting information for NR. In addition, the terminal may operate by setting the terminal itself to mode 4 through a system information block including information for transmitting and receiving an NR V2X sidelink received through an LTE or NR base station.

In this case, as an example, since LTE coverage and NR base stations have different coverage and different shaded areas, it may not be able to operate in the same mode in all RATs.

That is, when the LTE base station or the NR base station is capable of resource management for all V2X RATs, the same mode may be set for all RATs. On the other hand, since an LTE base station or an NR base station may only support V2X operation for a corresponding RAT, different transmission modes may be set for each RAT. Accordingly, the resource request method will be described below in consideration of the above.

Example 2-1 (LTE-Mode 3, NR-Mode 4)

For example, when the UE is configured to RRC connection with the LTE base station or when the LTE base station is configured for dual connectivity (dual connectivity: DC) to the master base station, buffers for some V2X services using the LTE SL BSR format Data information can be provided. In this case, the base station may provide the corresponding terminal with PPPP values corresponding to each of the four LCGs in the form of a list. In this case, as an example, data for PPPP that does not correspond to the aforementioned LCG may not be included in the LTE SL BSR. As described above, the terminal may recognize that data not included in the LTE SL BSR is transmitted through NR mode 4. Further, as an example, a QFI value that can be transmitted through NR mode 4 may be provided as a list separately from PPPP corresponding to LCG. At this time, only data packets corresponding to values in the QFI list may be transmitted through NR mode 4. At this time, as an example, since LTE and NR have different QoS indication schemes, data that can be transmitted through NR mode 4 may be separately indicated through a QFI list.

In addition, as an example, the R2 to transmit a data packet generated in the above-described application layer may be designated through a transmission profile or the like in the V2X application layer. Therefore, the above-described application layer can designate a corresponding data packet (PPPP or QFI) as a QoS parameter corresponding to the designated RAT, so that the UE can configure BSR format and information based on the RAT information and QoS parameter information.

At this time, Figure 16 is a view showing a resource allocation method based on the above-described embodiment 2-1. In this case, as an example, the BSR triggering and operation operation may be as described above. The terminal 1610 may provide buffer data information to LCGs having a corresponding relationship with the PPPP value described above using the LTE SL BSR format to the LTE base station 1620. At this time, the LTE base station 1620 performs resource allocation for the LTE sidelink through the LTE SL BSR described above, and the terminal can use the LTE sidelink based on this. Meanwhile, as an example, resource allocation for an NR sidelink may be included in a system information block previously received from a base station or an RRC message in an RRC connection reconfiguration procedure. At this time, the terminal can perform NR sidelink transmission by selecting a resource by itself based on transmission / reception resource pool information and related parameters for the NR sidelink included in the above, and is not limited to the above-described embodiment.

Example 2-2 (LTE-Mode 4, NR-Mode 3)

When an RRC connection is established with an NR base station or when the NR base station has dual connectivity (hereinafter referred to as DC) as a master base station, NR SL BSR format is used to provide buffer data information for some V2X services. You can.

In this case, as an example, the base station may provide the corresponding UE with QFI values corresponding to each of 8 LCGs in a list form. For example, data for QFI that does not correspond to the above-described LCG is not included in the NR SL BSR, and the UE can recognize that the corresponding data is transmitted through LTE mode 4.

As another example, the base station may provide PPPP values that can be transmitted through LTE mode 4 as a list separately from QFI corresponding to the LCG. At this time, only data packets corresponding to values in the above-described QFI list may be transmitted through LTE mode 4. That is, as described above, since the LTE and the NR have different QoS indication systems, a PPPP list for LTE mode 4 can be provided to prevent confusion.

As another example, a V2X application layer may designate an RAT to transmit a data packet generated by the application layer through a transmission profile. That is, the application layer may designate a corresponding data packet (PPPP or QFI) as a QoS parameter corresponding to the designated RAT. Therefore, the terminal can configure the BSR format and information based on the RAT information and QoS parameter information described above.

At this time, Figure 17 is a view showing a resource allocation method based on the above-described embodiment 2-2. In this case, as an example, the BSR triggering and operation operation may be as described above. The terminal 1710 may provide buffer data information to the NR base station 1720 using the NR SL BSR format for LCGs corresponding to the QFI value described above. At this time, the NR base station 1720 performs resource allocation for the NR sidelink through the NR SL BSR described above, and the terminal can use the NR sidelink based on this. Meanwhile, as an example, resource allocation for the LTE sidelink may be included in a system information block previously received from a base station or an RRC message in an RRC connection reconfiguration procedure. At this time, the terminal can perform the LTE sidelink transmission by selecting a resource by itself based on transmission / reception resource pool information and related parameters for the LTE sidelink included in the above, and is not limited to the above-described embodiment.

18 is a diagram illustrating a method for a terminal to request a resource according to the present disclosure.

Referring to FIG. 18, the terminal may receive a parameter for the BSR based on the type of base station established with the terminal. (S1810) At this time, as described in FIGS. 1 to 17, the terminal is an LTE base station or an NR base station. And RRC connection can be established. In addition, as an example, the terminal may be the LTE base station is double-connected to the master base station or the NR base station is double-connected to the master base station, as described above. In this case, as an example, the base station type may be an LTE base station or an NR base station. As described above, when an RRC connection is established to an LTE base station or dually connected to a master base station, the terminal may receive PPPP values corresponding to each of the four LCGs from the LTE base station in a list form. In addition, as an example, when an RRC connection is established to an NR base station or dually connected to a master base station, the terminal may receive QFI values corresponding to each of the 8 LCGs from the NR base station in a list form.

Next, the terminal may transmit the BSR to the base station in a format for the base station type based on the received parameters. (S1820) At this time, as described in FIGS. 1 to 17, in the case of the LTE base station, LTE SL BSR format Based on the BSR may be transmitted, in the case of an NR base station, the BSR may be transmitted based on the NR SL BSR format, as described above. Next, the UE may receive one or more of resource allocation information of the first type sidelink and resource allocation information of the second type sidelink from the base station based on the BSR. (S1830) At this time, FIGS. 1 to 17 As described above, the first type sidelink may be an LTE sidelink, and the second type sidelink may be an NR sidelink. That is, the terminal can receive at least one or more of the resource allocation information for the LTE sidelink and the NR sidelink from the base station, as described above.

Thereafter, the terminal may perform sidelink communication based on the received resource allocation information, as described above (S1840).

19 is a view showing the configuration of a base station apparatus and a terminal apparatus according to the present disclosure.

The base station apparatus 1900 may include a processor 1920, an antenna unit 1912, a transceiver 1914, and a memory 1916.

The processor 1920 performs baseband-related signal processing, and may include an upper layer processor 1930 and a physical layer processor 1940. The upper layer processor 1930 may process operations of a medium access control (MAC) layer, a radio resource control (RRC) layer, or more. The physical layer processor 1940 may process operations of a physical (PHY) layer (eg, uplink reception signal processing, downlink transmission signal processing, sidelink transmission signal processing, and sidelink reception signal processing). . In addition to performing baseband-related signal processing, the processor 1920 may control overall operation of the base station apparatus 1900.

The antenna unit 1912 may include one or more physical antennas, and when a plurality of antennas are included, may support MIMO (Multiple Input Multiple Output) transmission and reception. The transceiver 1914 may include a radio frequency (RF) transmitter and an RF receiver. The memory 1916 may store information processed by the processor 1920, software related to the operation of the base station apparatus 1900, an operating system, and applications, and may include components such as a buffer.

The terminal device 1950 may include a processor 1970, an antenna unit 1962, a transceiver 1964, and a memory 1966.

The processor 1970 performs baseband-related signal processing, and may include an upper layer processing unit 1980 and a physical layer processing unit 1990. The upper layer processing unit 1980 may process operations of the MAC layer, the RRC layer, or higher layers. The physical layer processing unit 1990 may process operations of the PHY layer (eg, downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, and sidelink reception signal processing). In addition to performing baseband-related signal processing, the processor 1970 may control overall operations of the terminal device 1950.

The antenna unit 1962 may include one or more physical antennas, and if a plurality of antennas are included, MIMO transmission and reception may be supported. The transceiver 1964 may include an RF transmitter and an RF receiver. The memory 1966 may store information processed by the processor 1970, software related to an operation of the terminal device 1950, an operating system, an application, and may include components such as a buffer.

The processor 1970 of the terminal device 1950 may be set to implement the operation of the terminal in the embodiments described in the present invention.

In this case, as an example, the processor 1970 of the terminal device 1950 may receive parameter information for the BSR from the base station device 1900 through the transceiver 1964. At this time, the base station apparatus 1900 may be an LTE base station or an NR base station as described above, as described above. Further, the processor 1950 of the terminal device 1950 may report the BSR to the base station device 1900 through the transceiver 1964, and receive sidelink resource allocation information based on this, as described above. The processor 1970 of the terminal device 1950 may perform sidelink communication based on the received resource allocation information, as described above.

Meanwhile, the processor 1920 of the base station apparatus 1900 may transmit a parameter for the BSR to the terminal apparatus 1950 through the transceiver 1914 as described above. In addition, the processor 1920 of the base station apparatus 1900 may receive the BSR from the terminal apparatus 1950 through the transceiver 1914, and may transmit sidelink resource allocation information based on this, as described above.

In addition, in the operation of the base station apparatus 1900 and the terminal apparatus 1950, the matters described in the examples of the present invention may be applied in the same way, and duplicate description will be omitted.

Exemplary methods of the present disclosure are expressed as a series of operations for clarity of description, but are not intended to limit the order in which the steps are performed, and each step may be performed simultaneously or in a different order if necessary. In order to implement the method according to the present disclosure, the steps illustrated may include other steps in addition, other steps may be included in addition to the remaining steps, or other additional steps may be included in addition to some steps.

The various embodiments of the present disclosure are not intended to list all possible combinations, but are intended to describe representative aspects of the present disclosure, and the details described in various embodiments may be applied independently or in combination of two or more.

Further, various embodiments of the present disclosure may be implemented by hardware, firmware, software, or a combination thereof. For hardware implementations, one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), General Purpose It may be implemented by a general processor, a controller, a microcontroller, a microprocessor, and the like.

The scope of the present disclosure includes software or machine-executable instructions (eg, operating systems, applications, firmware, programs, etc.) that cause actions according to the methods of various embodiments to be executed on a device or computer, and such software or Instructions include a non-transitory computer-readable medium that is stored and executable on a device or computer.

The present invention can be applied to various systems.

Claims (1)

1. In a method for performing a resource request by a terminal using a side link in a wireless communication system,

   Receiving a parameter for a buffer status report (BSR) based on the base station type established for connection with the terminal;

   Transmitting the BSR to a base station in a format for the base station type based on the received parameter;

   Receiving one or more of resource allocation information of a first type sidelink and resource allocation information of a second type sidelink from the base station based on the BSR; And

   And performing sidelink communication based on the received resource allocation information.

Images