Apparatus and method for allocating resources in a wireless communication system

Abstract

The disclosure relates to a communication technology for combining IoT technology with a 5G communication system to support a higher data transmission rate than a 4G system and a system for the communication technology. The disclosure can be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, health care, digital education, retail businesses, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. The disclosure relates to a method and apparatus for processing sidelink resource allocation in a V2X system. According to various embodiments of the disclosure, in a wireless communication system, a terminal can include at least one transceiver and at least one processor coupled to the at least one transceiver. The at least one processor can be configured to: acquire aggregation maximum bit rate (AMBR) information about a PC5 unicast link for sidelink communication of the terminal; provide the AMBR information to a base station; receive information about resources for the sidelink communication that have been allocated based on the AMBR information from the base station; and transmit data after the sidelink communication to another terminal based on the resources.

Description

TECHNICAL FIELD

[0001] The disclosure relates generally to a wireless communication system, and more particularly, to an apparatus and method for allocating resources in a wireless communication system. BACKGROUND

[0002] To meet the demand for wireless data traffic soaring since deployment of 4G communication systems, efforts have been made to develop an improved 5G or pre-5G communication system. Therefore, the 5G or 5G pre communication system is also called a 'Beyond 4G Network' or a 'Post LTE System'. The 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60GHz bands, so as to accomplish higher data rates. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed for use in 5G communication systems. In addition, in 5G communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, a technology for coordination between cells, a cooperative multi-cell transmission, cooperative multi-cell reception, interference mitigation, mobile networks based on a super-wideband, a dynamic spectrum sharing technology, a heterogeneous network, a 5G network slicing technology, a 5G security technology, and the like. In the 5G system, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), a non-orthogonal multiple access demodulation (NOMA), and a sparse code multiple access (SCMA) as an advanced access technology have been developed.

[0003] The Internet, which is a human centered connectivity network where humans generate and consume information, is now evolving to the Internet of Things (IoT) where distributed entities, such as things, exchange and process information without human intervention. The Internet of Everything (IoE), which is a combination of the IoT technology and the Big Data processing technology through connection with a cloud server, has emerged as a new paradigm for the IoT. As technology elements, such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology", and "security technology" have been demanded for IoT implementation, a sensor network, a Machine-to-Machine (M2M) communication, Machine Type Communication (MTC), and the like have been researched. Such an IoT environment can provide intelligent Internet technology services that create a new value through collection and analysis of data generated from connected things. The IoT can be applied to a variety of fields including smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances, and advanced medical services through convergence and combination between existing Information Technology (IT) and various industrial applications.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as a sensor network, MTC, and M2M communication can be implemented by beamforming, MIMO, and array antennas. Application of a cloud Radio Access Network (RAN) as the above-described Big Data processing technology can also be considered as an example of convergence between the 5G technology and the IoT technology.

[0005] Research has been conducted on communication using vehicles between a vehicle and another vehicle, between a vehicle and a terminal, or between a vehicle and a structure (hereinafter, referred to as vehicle-to-everything (V2X)) in a 5G communication system, and it is expected that various services can be provided to users by using V2X. SUMMARY

[0006] TECHNICAL PROBLEM

[0007] Based on the above description, the disclosure provides an apparatus and method for processing a sidelink transmission resource allocation in a wireless communication system.

[0008] In addition, the disclosure provides an apparatus and method of allocating resources in view of a PC5 unicast link aggregated maximum bit rate (AMBR).

[0009] In addition, the disclosure provides an apparatus and method for configuring a sidelink bearer (SLRB) per packet in a wireless communication system.

[0010] In addition, the disclosure provides an apparatus and method of managing a packet type in order to quickly process a packet in a wireless communication system.

[0011] In addition, the disclosure provides an apparatus and method of allocating resources for aperiodic traffic in a wireless communication system in a semi-persistent manner.

[0012] According to various embodiments of the disclosure, an operation method of a terminal in a wireless communication system can include determining a "PC5 unicast link aggregated maximum bit rate" (hereinafter, referred to as "PC5-LINK-AMBR") with respect to a sidelink, transmitting information about the PC5-LINK-AMBR to a base station, receiving a sidelink radio resource based on a PC5-LINK-AMBR allocated from the base station, and transmitting sidelink data by using the allocated sidelink radio resource.

[0013] According to various embodiments of the disclosure, a terminal in a wireless communication system includes a transceiver and at least one processor connected to the transceiver. The at least one processor can be configured to determine a PC5-LINK-AMBR regarding a sidelink, transfer information about the PC5-LINK-AMBR to a base station, receive a sidelink radio resource based on a PC5-LINK-AMBR allocated from the base station, and transmit sidelink data by using the allocated sidelink radio resource.

[0014] According to various embodiments of the disclosure, in a wireless communication system, an operation method of a base station can include obtaining PC5 unicast link aggregation maximum bit rate (AMBR) information regarding sidelink communication for a terminal, allocating a resource for the sidelink communication for the terminal based on the AMBR information, and transmitting information about the allocated resource to the terminal.

[0015] According to various embodiments of the disclosure, in a wireless communication system, an operation method of a terminal can include obtaining PC5 unicast link aggregation maximum bit rate (AMBR) information regarding sidelink communication for the terminal, providing the AMBR information to a base station, receiving information about a resource for the sidelink communication that has been allocated based on the AMBR information from the base station, and transmitting data subsequent to the sidelink communication to another terminal based on the resource.

[0016] According to various embodiments of the disclosure, in a wireless communication system, an operation method of a base station can include receiving a signal for requesting a sidelink radio bearer (SLRB) configuration from a terminal, obtaining packet type information regarding a sidelink flow of the terminal from the signal, generating SLRB configuration information regarding a packet type of the sidelink flow based on the packet type information, and transmitting the SLRB configuration information to the terminal, wherein the packet type is at least one of an IP packet, a non-IP packet, a PC5-S signaling, and a PC5 radio resource control (RRC) signaling.

[0017] According to various embodiments of the disclosure, in a wireless communication system, an operation method of a terminal can include generating a sidelink flow for sidelink communication of the terminal, determining a packet type of the sidelink flow, and identifying a sidelink radio bearer (SLRB) configuration corresponding to the packet type, wherein the identifying of the SLRB configuration includes: when the terminal is in a radio resource control (RRC) CONNECTED, receiving information about the SLRB configuration corresponding to the packet type from a base station, when the terminal is in an RRC INACTIVE or an RRC IDLE, receiving configuration information including an SRLB configuration for each packet and identifying the SLRB configuration corresponding to the packet type from the configuration information, and when the terminal is out of coverage, identifying the SLRB configuration corresponding to the packet type from pre-configured information including an SRLB configuration for each packet.

[0018] According to various embodiments of the disclosure, in a wireless communication system, an operation method of a first terminal can include generating a sidelink flow for sidelink communication between the first terminal and a second terminal, and transmitting, to the second terminal, sidelink-related information indicating a packet type of the sidelink flow, wherein the packet type is identified based on at least one of an identifier of the sidelink flow of a service data adaptation protocol (SDAP) layer of the first terminal, sidelink radio bearer (SLRB) information mapped to the sidelink flow of the first terminal, or a service data unit (SDU) type of a packet data convergence protocol (PDCP) layer of the first terminal.

[0019] According to various embodiments of the disclosure, in a wireless communication system, a base station can include at least one transceiver and at least one processor coupled to the at least one transceiver, wherein the at least one processor is configured to acquire aggregate maximum bit rate (AMBR) information about a PC5 unicast link for sidelink communication of a terminal, allocate resources for the sidelink communication of the terminal based on the AMBR information, and transmit information about the allocated resources to the terminal.

[0020] According to various embodiments of the disclosure, in a wireless communication system, a terminal can include at least one transceiver and at least one processor coupled to the at least one transceiver, wherein the at least one processor is configured to acquire aggregate maximum bit rate (AMBR) information about a PC5 unicast link for sidelink communication of the terminal, provide the AMBR information to a base station, receive, from the base station, information about resources for the sidelink communication that have been allocated based on the AMBR information, and transmit data subsequent to the sidelink communication to another terminal based on the resources.

[0021] According to various embodiments of the disclosure, a base station can include at least one transceiver and at least one processor coupled to the at least one transceiver, wherein the at least one processor is configured to receive, from a terminal, a signal for requesting sidelink radio bearer (SLRB) configuration, acquire, from the signal, packet type information about a sidelink flow of the terminal, generate SLRB configuration information about a packet type of the sidelink flow based on the packet type information, and transmit the SLRB configuration information to the terminal, wherein the packet type is at least one of an IP packet, a non-IP packet, PC5-S signaling, and PC5 radio resource control (RRC) signaling.

[0022] According to various embodiments of the disclosure, in a wireless communication system, a base station can include at least one transceiver and at least one processor coupled to the at least one transceiver, wherein the at least one processor is configured to generate a sidelink flow for sidelink communication of a terminal, determine a packet type of the sidelink flow, and identify a sidelink radio bearer (SLRB) configuration corresponding to the packet type, wherein, to identify the SLRB configuration, the at least one processor is configured to receive information on the SLRB configuration corresponding to the packet type from the base station when the terminal is in a radio resource control (RRC) CONNECTED, receive configuration information including SLRB configurations for respective packets and identify the SLRB configuration corresponding to the packet type from the configuration information when the terminal is in an RRC INACTIVE or an RRC IDLE, and identify the SLRB configuration corresponding to the packet type from pre-configuration information including SLRB configurations for respective packets when the terminal is out of coverage.

[0023] According to various embodiments of the disclosure, in a wireless communication system, a first terminal can include at least one transceiver and at least one processor coupled to the at least one transceiver, wherein the at least one processor is configured to generate a sidelink flow for sidelink communication between the first terminal and a second terminal, and transmit, to the second terminal, sidelink-related information indicating a packet type of the sidelink flow, wherein the packet type is identified based on at least one of: an identifier of the sidelink flow of a service data adaptation protocol (SDAP) layer of the first terminal; sidelink radio bearer (SLRB) information mapped to the sidelink flow of the first terminal; or a service data unit (SDU) type of a packet data convergence protocol (PDCP) layer of the first terminal.

[0024] According to various embodiments of the disclosure, a sidelink operation method performed by a terminal in a wireless communication system can include receiving a sidelink signal, obtaining sidelink control information (SCI) of the sidelink signal, and obtaining a medium access control (MAC) packet data unit (PDU) of the sidelink signal, wherein the SCI includes a propagation type indicator, first source identifier information, and first destination identifier information, and the propagation type indicator indicates one of a broadcast, a groupcast, and a unicast, and wherein a header of the MAC PDU includes second source identifier information and second destination identifier information.

[0025] According to various embodiments of the present disclosure, a sidelink operation method performed by a terminal in a wireless communication system can include generating a medium access control (MAC) packet data unit (PDU) of a sidelink signal, generating the sidelink signal including sidelink control information (SCI) for the sidelink signal based on the MAC PDU, and transmitting the sidelink signal, wherein the SCI includes a propagation type indicator, first source identifier information, and first destination identifier information, the propagation type indicator indicates one of a broadcast, a groupcast, and a unicast, and a header of the MAC PDU includes second source identifier information and second destination identifier information.

[0026] According to various embodiments of the present disclosure, a sidelink operation method performed by a base station in a wireless communication system can include receiving a resource request signal from a terminal, identifying a PC5-LINK aggregate maximum bit rate (AMBR) corresponding to a unicast link of the terminal from quality of service (QoS) information obtained from a core network entity, and transmitting resource information allocated based on the PC5-LINK AMBR to the terminal.

[0027] Advantageous Effects of Invention

[0028] Devices and methods according to various embodiments of the present disclosure support a scheme for processing required data amounts for respective unicast links so that a direct communication system between terminals can efficiently support various services having different required data amounts.

[0029] Devices and methods according to various embodiments of the present disclosure provide information required for a wireless end to process a packet so that a receiving terminal can process a packet as quickly as possible.

[0030] Advantageous effects obtainable from the present disclosure are not limited to those mentioned above, and other advantageous effects which are not mentioned will become apparent to those skilled in the art from the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0031] Figure 1 A wireless communication system according to various embodiments of the present disclosure is illustrated;

[0032] Figure 2 A configuration of a base station in a wireless communication system according to various embodiments of the present disclosure is illustrated;

[0033] Figure 3 A configuration of a terminal in a wireless communication system according to various embodiments of the present disclosure is illustrated;

[0034] Figure 4 A configuration of a communication unit in a wireless communication system according to various embodiments of the present disclosure is illustrated;

[0035] Figure 5A structure of a wireless time-frequency resource of a wireless communication system according to various embodiments of the disclosure is illustrated;

[0036] Figures 6a to 6d An example of a sidelink communication scenario in a wireless communication system according to various embodiments of the disclosure is illustrated;

[0037] Figure 7a and Figure 7b An example of a transmission method of a sidelink communication in a wireless communication system according to various embodiments of the disclosure is illustrated;

[0038] Figures 8a to 8e A signal flow between a terminal and a base station for unicast-based sidelink radio resource allocation according to various embodiments of the disclosure is illustrated;

[0039] Figure 9 A base station operation for unicast-based sidelink radio resource allocation according to various embodiments of the disclosure is illustrated;

[0040] Figures 10a to 10c A signal flow between a terminal and a base station for sidelink radio bearer (SLRB) configuration per packet type according to various embodiments of the disclosure is illustrated;

[0041] Figures 11a to 11b A base station operation for sidelink radio bearer establishment per packet type according to various embodiments of the disclosure is illustrated;

[0042] Figure 12 A signal flow between terminals for sidelink radio bearer establishment per packet type according to various embodiments of the disclosure is illustrated;

[0043] Figures 13a to 13d An example of packet filtering according to various embodiments of the disclosure is illustrated. DETAILED DESCRIPTION

[0044] The terms used in the present disclosure are merely used to describe particular embodiments, and are not intended to limit the present disclosure. A singular expression can include a plural expression, unless they are clearly different in the context. Unless otherwise defined, all terms used in the present disclosure, including technical terms and scientific terms, have the same meaning as understood by one of ordinary skill in the art to which the present disclosure belongs. Terms such as terms defined in a general dictionary can be interpreted as having the same meaning as the contextual meaning in the relevant technical field, and are not interpreted as having ideal or excessively formal meanings, unless otherwise defined in the present disclosure. In some cases, even the terms defined in the present disclosure should not be interpreted to exclude embodiments of the present disclosure.

[0045] Hereinafter, various embodiments of the disclosure will be described based on a software-based approach. However, various embodiments of the disclosure include a technology using both hardware and software, and thus various embodiments of the disclosure can not exclude the software perspective.

[0046] Hereinafter, the disclosure relates to an apparatus and method for resource allocation in a wireless communication system. In particular, the disclosure is configured to perform resource allocation for a terminal in sidelink communication between terminals, and relates to a method and apparatus for operating and allocating wireless resources for unicast-based sidelink communication.

[0047] In the following description, for the convenience of description, terms referring to a signal, terms referring to a channel, terms referring to control information, terms referring to a network entity, and terms referring to elements of an apparatus are exemplified. Accordingly, the terms used in the disclosure are not limited, and other terms referring to objects having equivalent technical meanings can be used.

[0048] In the following description, "physical channel" and "signal" can be used interchangeably with "data" or "control signal". For example, "Physical Downlink Shared Channel (PDSCH)" is a term of a physical channel through which data is transmitted, but "PDSCH" can also be used to refer to data. That is, in the disclosure, the expression "transmitting a physical channel" can be equally interpreted as the expression "transmitting data or a signal through a physical channel".

[0049] Hereinafter, in the disclosure, "higher layer signaling" refers to a signal transmission method for transmitting from a base station to a terminal using a downlink data channel of a physical layer or transmitting from a terminal to a base station using an uplink data channel of a physical layer. The higher layer signaling can be understood as Radio Resource Control (RRC) signaling or Medium Access Control (MAC) Control Element (CE) signaling.

[0050] In addition, in the disclosure, in order to determine whether a specific condition is satisfied or fulfilled, the expressions "greater than" or "less than" can be used, but this is only an example of description, and does not exclude the case of "equal to or greater than" or "equal to or less than". The condition described as "equal to or greater than" can be replaced with "greater than", the condition described as "equal to or less than" can be replaced with "less than", and the condition described as "equal to or greater than and less than" can be replaced with "greater than and equal to or less than".

[0051] In addition, the disclosure describes embodiments using terms used in some communication standards (for example, the Third Generation Partnership Project (3GPP)), but this is only an example for description. Embodiments of the disclosure can be easily modified and applied to other communication systems.

[0052] Figure 1 A wireless communication system according to various embodiments of the disclosure is shown.Figure 1 A base station 110, a terminal 120, and a terminal 130 are shown as parts of nodes using a wireless channel in a wireless communication system. Figure 1 Only one base station is shown, but other base stations identical or similar to the base station 110 can also be included.

[0053] The base station 110 is a network infrastructure for providing a wireless access to the terminals 120 and 130. The base station 110 includes a coverage area defined as a predetermined geographic area based on a distance over which a signal can be transmitted. In addition to the base station, the base station 110 can be referred to as an "access point (AP)", an "eNodeB (eNB)", a "fifth generation node (5g node)", a "next generation node B (gNB)", a "wireless point", a "transmission / reception point (TRP)", or other terms having equivalent technical meanings.

[0054] Each of the terminals 120 and 130 is a device for a user to use and performs communication with the base station 110 through a wireless channel. A link from the base station 110 to the terminal 120 or the terminal 130 is referred to as a downlink (DL), and a link from the terminal 120 or the terminal 130 to the base station 110 is referred to as an uplink (UL). In addition, the terminals 120 and 130 can communicate with each other through a wireless channel. Here, a link between the terminals 120 and 130 is referred to as a sidelink, and the sidelink can be used interchangeably with a PC5 interface. In some cases, at least one of the terminals 120 and 130 can operate without user involvement. That is, at least one of the terminals 120 and 130 is a device for performing machine type communication (MTC) and cannot be carried by a user. In addition to the terminal, each of the terminals 120 and 130 can be referred to as a "user equipment (UE)", a "mobile station", a "subscriber station", or a "remote terminal", a "wireless terminal", a "user device", or other terms having equivalent technical meanings.

[0055] The base station 110, the terminal 120, and the terminal 130 can transmit or receive a wireless signal in a millimeter wave band (e.g., 28 GHz, 30 GHz, 38 GHz, and 60 GHz). Here, in order to improve channel gain, the base station 110, the terminal 120, and the terminal 130 can perform beamforming. Here, beamforming can include transmission beamforming and reception beamforming. That is, the base station 110, the terminal 120, and the terminal 130 can impart directionality to a transmission signal or a reception signal. For this purpose, the base station 110 and the terminal 120 and 130 can select a serving beam 112, 113, 121, and 131 through a beam search or a beam management procedure. After the serving beam 112, 113, 121, and 131 is selected, subsequent communication is performed through a resource in a quasi co-location (QCL) relationship with a resource in which the serving beam 112, 113, 121, and 131 is transmitted.

[0056] A first antenna port and a second antenna port can be referred to as being in a QCL relationship if a large-scale property of a channel through which a symbol on the first antenna port is conveyed can be inferred from a channel through which a symbol on the second antenna port is conveyed. For example, the large-scale property of the channel can include at least one of a delay spread, a Doppler spread, a Doppler shift, an average gain, an average delay, and a spatial receiver parameter.

[0057] Figure 1 The terminal 120 and the terminal 130 illustrated in FIG. 1 can support vehicle communication. In the case of vehicle communication, in the LTE system, standardization of a V2X technology has been completed based on a device-to-device (D2D) communication structure in 3GPP Release 14 and Release 15, and efforts are being made to develop a V2X technology based on 5G NR. The NR V2X is expected to support unicast communication, groupcast (or multicast) communication, and broadcast communication between terminals. In addition, unlike the LTE V2X, which aims to transmit and receive basic safety information required for vehicle road travel, the NR V2X aims to provide more advanced services such as platooning, advanced driving, extended sensors, and remote driving.

[0058] The V2X services can be classified into basic safety services and advanced services. The basic safety services can include detailed services such as left turn awareness service, preceding vehicle collision warning service, emergency vehicle approaching awareness service, preceding obstacle warning service, and intersection traffic light information service, and a cooperative awareness message (CAM) service or basic safety message (BSM) service, and can transmit and receive V2X information using a broadcast, unicast, or groupcast transmission method. The advanced services need a method capable of transmitting and receiving V2X information using unicast and groupcast transmission methods in addition to the broadcast transmission method in order to enable transmission and reception of V2X information within a specific vehicle group or between two vehicles, and further enhance quality of service (QoS) requirements than the basic safety services. The advanced services can include detailed services such as platooning service, autonomous driving service, remote control driving service, and extended sensor-based V2X service.

[0059] Hereinafter, a "sidelink (SL)" refers to a signal transmission / reception path between terminals, and can be used interchangeably with a PC5 interface. Hereinafter, a base station is an entity that performs resource allocation to a terminal, and can support V2X communication and general cellular communication, or can support only V2X communication. That is, the base station can be an NR base station (e.g., gNB), an LTE base station (e.g., eNB), or a roadside unit (RSU). In addition to general user equipment and mobile stations, the terminal can include a vehicle supporting vehicle-to-vehicle (V2V) communication, a vehicle or a pedestrian phone (e.g., a smart phone) supporting vehicle-to-pedestrian (V2P) communication, a vehicle supporting vehicle-to-network (V2N) communication, a vehicle supporting vehicle-to-infrastructure (V2I) communication, an RSU equipped with a terminal function, an RSU equipped with a base station function, and an RSU equipped with some base station functions and some terminal functions. In addition, "V2X terminal" used in the following description can be referred to as a "terminal." That is, the terminal can be used as a V2X terminal related to V2X communication.

[0060] The base station and the terminal are connected through a Uu interface. Uplink (UL) refers to a wireless link through which the terminal transmits data or a control signal to the base station, and downlink (DL) refers to a wireless link through which the base station transmits data or a control signal to the terminal.

[0061] Figure 2 A configuration of a base station in a wireless communication system according to various embodiments of the disclosure is illustrated. Figure 2 The configuration illustrated in FIG. 1 can be understood as a configuration of the base station 110. The term "unit" or the term with the suffix "-er" and "-or" used in the following description refers to a unit for processing at least one function or operation, and can be implemented by hardware, software, or a combination of hardware and software.

[0062] Referring toFigure 2 The base station 110 includes a wireless communication unit 210, a backhaul communication unit 220, a storage unit 230, and a controller 240.

[0063] The wireless communication unit 210 performs a function for transmitting or receiving a signal through a wireless channel. For example, the wireless communication unit 210 performs a conversion function between a baseband signal and a bit string according to a physical layer standard of a system. For example, in performing data transmission, the wireless communication unit 210 generates complex symbols by encoding and modulating a transmission bit string. Also, in performing data reception, the wireless communication unit 210 reconstructs a received bit string by demodulating and decoding a baseband signal.

[0064] Also, the wireless communication unit 210 up-converts a baseband signal into a radio frequency (RF) band signal and then transmits the signal through an antenna, and down-converts an RF band signal received through the antenna into a baseband signal. To this end, the wireless communication unit 210 can include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. Also, the wireless communication unit 210 can include a plurality of transmission / reception paths. Further, the wireless communication unit 210 can include at least one antenna array configured by a plurality of antenna elements.

[0065] In terms of hardware, the wireless communication unit 210 can include a digital unit and an analog unit, and the analog unit can include a plurality of sub-units according to an operation power, an operation frequency, etc. The digital unit can be implemented by at least one processor (e.g., a digital signal processor (DSP)).

[0066] The wireless communication unit 210 transmits or receives a signal as described above. Accordingly, all or a part of the wireless communication unit 210 can be referred to as a "transmitter", a "receiver", a "transmitter / receiver", or a "transceiver". Also, in the following description, transmission or reception performed through a wireless channel can include processing performed by the wireless communication unit 210 as described above.

[0067] The backhaul communication unit 220 provides an interface for performing communication with other nodes in a network. That is, the backhaul communication unit 220 converts a bit string transmitted from the base station 110 to another node (e.g., another access node, another base station, an upper node, and a core network) into a physical signal, and converts a physical signal received from another node into a bit string.

[0068] The storage 230 stores data such as a basic program about an operation of the base station 110, an application program, or configuration information. The storage 230 can include a volatile memory, a non-volatile memory, or a combination of the volatile memory and the non-volatile memory. Then, the storage 230 provides the stored data on a request of the controller 240.

[0069] The controller 240 controls overall operations of the base station 110. For example, the controller 240 transmits or receives a signal through the wireless communication unit 210 or the backhaul communication unit 220. Also, the controller 240 records or reads data in or from the memory 230. Also, the controller 240 can perform a function of a protocol stack required in a communication standard. According to another example of implementation, the protocol stack can be included in the wireless communication unit 210. To this end, the controller 240 can include at least one processor. According to an embodiment, the controller 240 can control the base station 110 to perform operations according to embodiments which will be described later.

[0070] Figure 3 A configuration of a terminal in a wireless communication system according to various embodiments of the disclosure is illustrated. Figure 3 The configuration illustrated in FIG. 1 can be understood as a configuration of the terminal 120. The term "unit" or the term with the suffix "-er" at the end used in the following refers to a unit processing at least one function or operation, and can be implemented by hardware, software, or a combination of hardware and software.

[0071] Referring to Figure 3 The terminal 120 includes a communication unit 310, a memory 320, and a controller 330.

[0072] The communication unit 310 performs a function for transmitting or receiving a signal through a wireless channel. For example, the communication unit 310 performs a conversion function between a baseband signal and a bit string according to a physical layer standard of a system. For example, in performing data transmission, the communication unit 310 generates complex symbols by encoding and modulating a transmission bit string. Also, in performing data reception, the communication unit 310 reconstructs a received bit string by demodulating and decoding a baseband signal. Also, the communication unit 310 up-converts a baseband signal into an RF band signal and transmits the signal through an antenna, and down-converts an RF band signal received through an antenna into a baseband signal. For example, the communication unit 310 can include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC.

[0073] Also, the communication unit 310 can include a plurality of transmission / reception paths. Further, the communication unit 310 can include at least one antenna array including a plurality of antenna elements. In terms of hardware, the communication unit 310 can include a digital circuit and an analog circuit (e.g., a radio frequency integrated circuit (RFIC)). Here, the digital circuit and the analog circuit can be implemented in one package. Also, the communication unit 310 can include a plurality of RF chains. Further, the communication unit 310 can perform beamforming.

[0074] The communication unit 310 transmits or receives a signal as described above. Therefore, all or a part of the communication unit 310 can be referred to as a "transmitter", a "receiver", or a "transceiver". In addition, in the following description, transmission or reception performed through a wireless channel can include performing processing performed by the communication unit 310 as described above.

[0075] The memory 320 stores data such as a basic program on the operation of the terminal 120, an application program, or configuration information. The memory 320 can include a volatile memory, a non-volatile memory, or a combination of a volatile memory and a non-volatile memory. Then, the memory 320 provides the stored data at the request of the controller 330.

[0076] The controller 330 controls the overall operation of the terminal 120. For example, the controller 330 transmits or receives a signal through the communication unit 310. In addition, the controller 330 records or reads data in or from the memory 320. In addition, the controller 330 can perform the function of a protocol stack required for a communication standard. For this purpose, the controller 330 can include at least one processor or microprocessor, or can be a part of a processor. In addition, a part of the communication unit 310 and the controller 330 can be referred to as a communication processor (CP). According to an embodiment, the controller 330 can control the terminal 120 to perform operations according to embodiments that will be described later.

[0077] Figure 4 A configuration of a communication unit in a wireless communication system according to various embodiments of the disclosure is illustrated. Figure 4 An example of a detailed configuration of the wireless communication unit 210 of Figure 2 or the communication unit 310 of Figure 3 is illustrated. Specifically, Figure 4 An element for performing beamforming as a part of the wireless communication unit 210 of Figure 2 or as a part of the communication unit 310 of Figure 3 is illustrated.

[0078] Referring to Figure 4 , the wireless communication unit 210 or the communication unit 310 includes an encoding and modulation unit 402, a digital beamformer 404, a plurality of transmission paths 406-1 to 406-N, and an analog beamformer 408.

[0079] The encoding and modulation unit 402 performs channel encoding. To perform channel encoding, at least one of a low-density parity-check (LDPC) code, a convolutional code, and a polar code can be used. The encoding and modulation unit 402 generates modulation symbols by performing constellation mapping.

[0080] The digital beamformer 404 performs beamforming of digital signals (e.g., modulated symbols). To this end, the digital beamformer 404 multiplies the modulated symbols by beamforming weights. Here, the amplitude and phase of the signals are changed using the beamforming weights, and the beamforming weights can be referred to as a "precoding matrix," a "precoder," or the like. The digital beamformer 404 outputs the digitally beamformed modulated symbols via a plurality of transmission paths 406-1 through 406-N. Here, the modulated symbols can be multiplexed according to a multiple-input multiple-output (MIMO) transmission scheme, or can be provided via the plurality of transmission paths 406-1 through 406-N.

[0081] The plurality of transmission paths 406-1 through 406-N converts the digitally beamformed digital signals into analog signals. To this end, the plurality of transmission paths 406-1 through 406-N can each include an inverse fast Fourier transform (IFFT) operation unit, a cyclic prefix (CP) inserter, a DAC, and an up-converter. The CP inserter is used for an orthogonal frequency division multiplexing (OFDM) scheme, and can not be included when another physical layer scheme (e.g., filter bank multi-carrier (FBMC)) is applied. That is, the plurality of transmission paths 406-1 through 406-N provide independent signal processing processes to a plurality of streams generated through digital beamforming. However, according to an embodiment, some elements of the plurality of transmission paths 406-1 through 406-N can be used in common.

[0082] The analog beamformer 408 performs beamforming of analog signals. To this end, the digital beamformer 404 multiplies the analog symbols by beamforming weights. Here, the amplitude and phase of the signals are changed using the beamforming weights. In particular, the analog beamformer 440 can be variously configured according to a connection structure between the plurality of transmission paths 406-1 through 406-N and antennas. For example, each of the plurality of transmission paths 406-1 through 406-N can be connected to one antenna array. As another example, the plurality of transmission paths 406-1 through 406-N can be connected to one antenna array. As another example, the plurality of transmission paths 406-1 through 406-N can be adaptively connected to one antenna array, or can be connected to two or more antenna arrays.

[0083] Figure 5 A structure of a radio time-frequency resource of a wireless communication system according to various embodiments of the disclosure is illustrated.

[0084] Reference Figure 5In the wireless resource domain, the horizontal axis represents the time domain and the vertical axis represents the frequency domain. The minimum transmission unit in the time domain is the OFDM symbol or the DFT-S-OFDM symbol, and Nsymb OFDM symbols or DFT-S-OFDM symbols 530 are included in one slot 505. Unlike the slot, the length of a subframe in the NR system can be defined as 1.0 ms, and the length of a radio frame 500 can be defined as 10 ms. The minimum transmission unit in the frequency domain is the subcarrier, and the bandwidth of the entire system transmission band can include a total of NBW subcarriers 525. Specific values such as Nsymb and NBW can be applied differently according to the system.

[0085] The basic unit of the time-frequency resource domain is a resource element (RE) 510 that can be indicated by the OFDM symbol index, the DFT-S-OFDM symbol index, and the subcarrier index. A resource block (RB) 515 can be defined by NRB consecutive subcarriers 520 in the frequency domain. In general, the minimum transmission unit of data is the RB unit, and in general, in the NR system, Nsymb = 14 and NRB = 12.

[0086] Figure 5 The structure of the wireless time-frequency resource shown in FIG. 1 can be applied to the Uu interface. In addition, the structure of the wireless time-frequency resource shown in FIG. 1 can be applied to the sidelink in a similar manner. Figure 5 The structure of the wireless time-frequency resource shown in FIG. 1 can be applied to the Uu interface. In addition, the structure of the wireless time-frequency resource shown in FIG. 1 can be applied to the sidelink in a similar manner.

[0087] Figures 6a to 6d An example of a scenario of sidelink communication in a wireless communication system according to various embodiments of the disclosure is shown.

[0088] Figure 6a An in-coverage scenario in which the sidelink terminals 620a and 620b are located within the coverage of the base station 610 is shown. The sidelink terminals 620a and 620b can receive data and control information from the base station 610 through the downlink (DL), or can transmit data and control information to the base station through the uplink (UL). Here, the data and control information can be used for sidelink communication, or can be used for general cellular communication rather than sidelink communication. In addition, in Figure 6a In FIG. 6, the sidelink terminals 620a and 620b can transmit and receive data and control information about sidelink communication through the sidelink.

[0089] Figure 6bPartially covered in which a first terminal 620a among the sidelink terminals is located within the coverage of the base station 610 and in which a second terminal 620b is located outside the coverage of the base station 610 is shown. The first terminal 620a located within the coverage of the base station 610 can receive data and control information from the base station through the DL or can transmit data and control information to the base station through the UL. The second terminal 620b located outside the coverage of the base station 610 cannot receive data and control information from the base station through the DL and cannot transmit data and control information to the base station through the UL. The second terminal 620b can transmit and receive data and control information about the sidelink communication to and from the first terminal 610a through the sidelink.

[0090] Figure 6c An example in which the sidelink terminals (e.g., the first terminal 610a and the second terminal 620b) are located outside the coverage of the base station 610 is shown. Accordingly, the first terminal 620a and the second terminal 620b cannot receive data and control information from the base station through the DL and cannot transmit data and control information to the base station through the UL. The first terminal 620a and the second terminal 620b can transmit and receive data and control information about the sidelink communication through the sidelink.

[0091] Figure 6d An example in which the first terminal 620a and the second terminal 620b performing the sidelink communication are connected (e.g., an RRC connected state) or camped on (e.g., an RRC connected release state, i.e., an RRC idle state) different base stations (a first base station 610a and a second base station 610b) from each other is shown. Here, the first terminal 620a can be a sidelink transmission terminal and the second terminal 620b can be a sidelink reception terminal. Alternatively, the first terminal 620a can be a sidelink reception terminal and the second terminal 620b can be a sidelink transmission terminal. The first terminal 620a can receive a system information block (SIB) dedicated for the sidelink from the base station 610a to which the first terminal itself has accessed (or on which the first terminal itself camps) and the second terminal 620b can receive a SIB dedicated for the sidelink from another base station 610b to which the second terminal itself has accessed (or on which the second terminal itself camps). Here, the information about the SIB dedicated for the sidelink received by the first terminal 620a can be different from the information about the SIB dedicated for the sidelink received by the second terminal 620b. Accordingly, it is necessary to unify the information in order to perform the sidelink communication between the terminals located in different cells.

[0092] Although it has been described for convenience that the first terminal 620a and the second terminal 620b are located in the coverage of the base station 610 and the first terminal 620a and the second terminal 620b are located outside the coverage of the base station 610, the present disclosure is not limited thereto. For example, the first terminal 620a and the second terminal 620b can be located in the coverage of the base station 610 and the first terminal 620a and the second terminal 620b can be located outside the coverage of the base station 610. Figures 6a to 6dAn example of a sidelink system configured with two terminals (e.g., the first terminal 610a and the second terminal 620b) is described in the example of FIG. 6, but the disclosure is not limited thereto and can be applied to a sidelink system in which three or more terminals participate. In addition, UL or DL between the base station 610 and the sidelink terminal can be referred to as a "Uu interface," and a sidelink between the sidelink terminals can be referred to as a "PC-5 interface." In the following description, UL, DL, Uu interface, sidelink, and PC-5 can be used interchangeably with each other.

[0093] Further, in the disclosure, a terminal can refer to a vehicle supporting vehicle-to-vehicle (V2V) communication, a vehicle supporting vehicle-to-pedestrian (V2P) communication, or a pedestrian phone (e.g., a smartphone), a vehicle supporting vehicle-to-network (V2N) communication, or a vehicle supporting vehicle-to-infrastructure (V2I) communication. In addition, in the disclosure, a terminal can refer to a roadside unit (RSU) equipped with a terminal function, an RSU equipped with a base station function, or an RSU equipped with some base station functions and some terminal functions.

[0094] Figure 7a and Figure 7b An example of a transmission method of sidelink communication in a wireless communication system according to various embodiments of the disclosure is illustrated. Figure 7a A unicast method is illustrated, and Figure 7b A groupcast method is illustrated.

[0095] As Figure 7a illustrated in FIG. 7, the transmitting terminal 720a and the receiving terminal 720b can perform one-to-one communication. Figure 7a The transmission method illustrated in FIG. 7 can be referred to as "unicast communication." As Figure 7b illustrated in FIG. 7, the transmitting terminal 720a or 720d and the receiving terminal 720b, 720c, 720e, 720f, and 720g can perform one-to-many communication. Figure 7b The transmission method illustrated in FIG. 7 can be referred to as "groupcast communication" or "multicast communication." In Figure 7b , the first terminal 720a, the second terminal 720b, and the third terminal 720c can configure one group, and the terminals (the first terminal 720a, the second terminal 720b, and the third terminal 720c) in the group can perform groupcast communication. The fourth terminal 720d, the fifth terminal 720e, the sixth terminal 720f, and the seventh terminal 720g can configure another group, and the terminals (the fourth terminal 720d, the fifth terminal 720e, the sixth terminal 720f, and the seventh terminal 720g) in the group can perform groupcast communication. The terminals can perform groupcast communication within the group to which they belong, and can perform unicast, groupcast, or broadcast communication with at least one other terminal belonging to a different group. Although Figure 7bTwo groups are shown in FIG. 1, but the disclosure is not limited thereto and can be applied to a case in which a larger number of groups are configured.

[0096] Further, although not shown in Figure 7a or Figure 7b Broadcast communication can be performed by the sidelink terminals. The broadcast communication refers to a method in which all sidelink terminals receive data and control information transmitted by the sidelink transmission terminal through the sidelink. For example, if the first terminal 720a is a transmission terminal in Figure 7b , the remaining terminals 720b, 720c, 720d, 720e, 720f, and 720g can receive data and control information transmitted by the first terminal 720a.

[0097] The sidelink unicast communication, the sidelink groupcast communication, and the sidelink broadcast communication described above can be supported by an in-coverage scenario, a partial coverage scenario, or an out-of-coverage scenario.

[0098] In the case of the NR sidelink, unlike the LTE sidelink, it can be considered to support a transmission scheme in which a vehicle terminal transmits data to only one specific terminal through unicast communication and a transmission scheme in which a vehicle terminal transmits data to a plurality of specific terminals through groupcast communication. For example, the unicast technology and the groupcast technology can be usefully applied to the case of a service scenario in which two or more vehicles are connected to a single network and move together in a group, such as a platoon. Specifically, the unicast communication can be used by a lead terminal in a group connected through a platoon to control one specific terminal, and the groupcast communication can be used by the lead terminal to control a group including a plurality of specific terminals at the same time.

[0099] The base station or the terminal can perform resource allocation for sidelink communication, that is, V2X. The resource allocation for sidelink transmission can be performed within a resource pool defined in the time domain and the frequency domain. The resource pool can be configured within a bandwidth part (BWP) in the frequency domain. Specifically, resource allocation can be made using the following methods.

[0100] (1) Mode 1 resource allocation - scheduled resource allocation

[0101] The scheduling resource allocation is a method in which a base station allocates resources for sidelink transmission to an RRC connected terminal in a dedicated scheduling method. The base station can allocate resources to a terminal within a coverage. The base station can transmit resource allocation information to a transmitting terminal for sidelink transmission. That is, the base station can schedule resources for sidelink transmission and transmit the scheduling result to the terminal. The scheduling resource allocation method can be effective for interference management and resource pool management (dynamic allocation and / or semi-persistent transmission) because the base station is able to manage resources for sidelink. If a terminal in an RRC connected mode has data to be transmitted to other terminals, the terminal can transmit information indicating that there is data to be transmitted to other terminals to the base station by using an RRC message or a MAC control element (hereinafter, CE). For example, the RRC message transmitted by the terminal to the base station can be a sidelink terminal information message (sidelinkUEInformation) or a terminal assistance information message (UEAssistanceInformation), and the MAC CE can correspond to a buffer status report (BSR) MAC CE including at least one of an indicator indicating a BSR for V2X communication and information about the size of data buffered for sidelink communication, a scheduling request (SR), etc.

[0102] (2) Mode 2 resource allocation - UE autonomous resource selection

[0103] Second, the UE autonomous resource selection is a method of providing a terminal with a sidelink transmission / reception resource pool for V2X through system information, an RRC message (e.g., an RRCReconfiguration message or a PC5-RRC message), or pre-configured information, and the terminal selects a resource pool and a resource according to a predetermined rule. The UE autonomous resource selection can correspond to one or more of the following resource allocation methods.

[0104] > The UE autonomously selects a sidelink resource for transmission.

[0105] > The UE assists sidelink resource selection for other terminals.

[0106] > The UE is configured with an NR configured grant for sidelink transmission.

[0107] > The UE can schedule sidelink transmission of other terminals.

[0108] The resource selection method of the terminal can include zone mapping, sensing-based resource selection, and random selection.

[0109] - In addition, even if the terminal is located within the coverage of the base station, resource allocation or resource selection can not be performed according to the scheduled resource allocation or the UE autonomous resource selection mode. Here, the terminal can perform V2X sidelink communication through a pre-configured sidelink transmission / reception resource pool or a sidelink transmission / reception resource pool configured for an exceptional situation (exceptional resource pool).

[0110] - In addition, if the terminal for V2X communication is located outside the coverage of the base station, the terminal can perform V2X sidelink communication through a pre-configured sidelink transmission / reception resource pool.

[0111] A sidelink radio bearer (SLRB) configuration for transmitting a sidelink flow or packet and the SLRB can be mapped to a SL logical channel (LC), and the SL logical channel can be mapped to a SL logical channel group (LCG). The SLRB configuration and the SLRB can be distinguished according to a combination of a source index, a destination index, a type of propagation, a quality of service (QoS) flow identifier (QFI) / ProSe flow identifier (PFI), or a PC5 flow identifier (PFI), and a priority.

[0112] 1. PC5-LINK-AMBR operation scheme

[0113] A direct communication system between terminals through a sidelink can support data transmission / reception through a guaranteed bit rate (GBR) QoS flow, a non-guaranteed bit rate (non-GBR) QoS flow, and a delay-critical GBR QoS flow. With respect to the GBR QoS flow, the base station or the terminal can handle sidelink radio resource allocation based on a guaranteed flow bit rate (GFBR) and a maximum flow bit rate (MFBR). With respect to the non-GBR QoS flow, the base station or the terminal can handle sidelink radio resource allocation based on a UE PC5 aggregation maximum bit rate (UE-PC5-AMBR) and a PC5 LINK aggregation maximum bit rate (PC5-LINK-AMBR). With respect to the delay-critical GBR QoS flow, the base station or the terminal can handle sidelink radio resource allocation based on the UE-PC5-AMBR, or can handle sidelink radio resource allocation based on an aggregation maximum bit rate (AMBR) for the delay-critical GBR QoS flow. The case where the base station handles sidelink radio resource allocation corresponds to the case of mode 1 resource allocation, and the case where the terminal handles sidelink radio resource allocation corresponds to the case of mode 2 resource allocation. In other words, in mode 1 resource allocation, the base station can perform radio resource allocation for sidelink transmission of the terminal. In mode 2 resource allocation, the terminal can perform radio resource allocation for sidelink transmission.

[0114] The PC5-LINK-AMBR can be configured to have the same value for each PC5 unicast link and operate. Thus, an operation can be performed so that the sum of data rates of each PC5 flow belonging to the PC5 unicast link A is the same as the sum of data rates of each PC5 flow belonging to the PC5 unicast link B. The PC5 unicast link can be configured so that the V2X application of the terminal will use a unicast type of sidelink communication, and when a PC5 flow configured for transmission of packets generated in the V2X application is mapped to the PC5 flow and managed by the terminal. The PC5-LINK-AMBR of the PC5 unicast link can be configured in the terminal itself, can be configured in the V2X application server, or can be configured in an entity managing the terminal subscription, and the terminal can store the PC5-LINK-AMBR.

[0115] In mode 2 resource allocation, the terminal can store PC5-LINK-AMBR information for each PC5 unicast link. When a packet to be transmitted for a random unicast PC5 flow is generated, the terminal can determine the PC5 unicast link corresponding to the PC5 flow in order to obtain a resource for packet transmission, and can check (i.e., identify) the PC5-LINK-AMBR for the unicast link. The terminal can allocate a resource for packet transmission based on the PC5-LINK-AMBR. For example, the terminal can allocate a resource for packet transmission at a level not exceeding the PC5-LINK-AMBR.

[0116] In mode 1 resource allocation, the base station can receive a request for allocation of a resource for transmission of a packet belonging to a random unicast PC5 flow from the terminal. The base station can check (i.e., identify) a PC5 unicast link corresponding to the PC5 flow and a PC5-LINK-AMBR for the link in order to allocate a resource for packet transmission. The base station can allocate a resource for packet transmission based on the PC5-LINK-AMBR. For example, the base station can allocate a resource for packet transmission to the terminal at a level not exceeding the PC5-LINK-AMBR. Here, in order for the base station to identify the PC5-LINK-AMBR for the PC5 unicast link, the base station needs to know the PC5 unicast link to which the PC5 flow of the terminal is mapped and the PC5-LINK-AMBR information for the corresponding PC5 unicast link. Next, a scheme in which the base station acquires the PC5 unicast link of the terminal and the PC5-LINK-AMBR information for the corresponding PC5 unicast link will be described with reference to various embodiments.

[0117] Figures 8a to 8e A signal flow between a terminal and a base station for unicast-based sidelink radio resource allocation according to various embodiments of the disclosure is illustrated. Figures 8a to 8cAn embodiment in which the base station acquires PC5-LINK-AMBR information when a unicast stream is generated and unicast link information to which the unicast stream is mapped is updated is shown. Figure 8d and 8e An embodiment in which the base station acquires PC5-LINK-AMBR information when a unicast stream is deleted and unicast link information to which the unicast stream is mapped is updated is shown.

[0118] In Figure 8a In the present disclosure, a scheme for obtaining PC5-LINK-AMBR information based on a SLRB configuration request is described. Referring to Figure 8a In operation 801, the terminal can identify a sidelink stream. The sidelink stream can be used for service management (e.g., quality of service (QoS) management) through sidelink communication. One or more sidelink streams can correspond to one PC5 unicast link. The sidelink stream can be referred to as a PC5 stream, a PC5 QoS stream, or a sidelink QoS stream. The terminal can determine that a sidelink stream is generated. The terminal can identify the generated sidelink stream. For example, the terminal can identify a newly generated sidelink stream, i.e., a new stream. Also, for example, the terminal can identify a sidelink stream that needs to be reconfigured in response to a state of the terminal becoming RRC_CONNECTED.

[0119] In operation 803, the terminal can identify a PC5 unicast link. The PC5 unicast link can be used for managing sidelink communication of a unicast type. The PC5 unicast link can be mapped to one or more sidelink streams. The PC5 unicast link can be referred to as a PC5 link, a sidelink unicast link, or the like. The terminal can identify a PC5 unicast link mapped to a sidelink stream.

[0120] In operation 805, the terminal can identify a PC5-LINK-AMBR. The terminal can identify the PC5-LINK-AMBR based on at least one of a sidelink stream and a PC5 unicast link. That is, the terminal can manage information about the sidelink stream and the PC5 unicast link. The terminal can identify a PC5-LINK-AMBR of a PC5 unicast link to which the sidelink stream is mapped.

[0121] In operation 807, the terminal can transmit a signal for requesting sidelink radio bearer (SLRB) configuration information (hereinafter, an SLRB configuration request signal). The terminal can transmit the SLRB configuration request signal in order to configure SLRB information, thereby enabling transmission and reception of a packet corresponding to a sidelink stream. When the terminal and the base station are in an RRC CONNECTED state, the terminal can transmit the SLRB configuration request signal to the base station.

[0122] According to various embodiments, the terminal can transmit, to the base station, sidelink flow information and PC5 unicast link information mapped thereto at the same time as requesting SLRB configuration information about the sidelink flow. The terminal can include information about the sidelink flow and PC5 unicast link information mapped to the sidelink flow in configuration request information. For example, the SLRB configuration request signal can include at least one of a destination identifier, a source identifier, an identifier of a sidelink flow (hereinafter, a sidelink flow identifier), a QoS profile of the sidelink flow (the profile can correspond to a 5G QoS indicator (5QI)), PC5 5QI (PQI), or a QoS requirement), an identifier of a PC5 unicast link (hereinafter, a PC5 unicast link identifier), and a PC5-LINK-AMBR for the PC5 unicast link. According to an embodiment, if it is determined that the terminal has previously transmitted the PC5-LINK-AMBR to the base station and the value has not changed, the terminal can transmit the SLRB configuration request signal to the base station without the PC5-LINK-AMBR. That is, the PC5-LINK-AMBR for the PC5 unicast link mapped to the sidelink flow can be omitted from the SLRB configuration request signal.

[0123] The SLRB configuration request signal can include one or more sidelink flows and information about a PC5 unicast link mapped to each sidelink flow. Here, at least one sidelink flow can be mapped to one PC5 unicast link.

[0124] In operation 809, the base station can transmit SLRB configuration information to the terminal. The base station can transmit the SLRB configuration information to the terminal in response to the request performed in operation 807. The SLRB configuration information can include at least one of an SLRB identifier mapped to a sidelink flow, radio parameter information about the SLRB (for example, at least one of a service data adaptation protocol (SDAP) configuration, a packet data convergence protocol (PDCP) configuration, a radio link control (RLC) configuration, a medium access control (MAC) configuration, and a physical (PHY) configuration), a logical channel identifier, and a logical channel identifier group.

[0125] In operation 811, the base station can manage PC5-LINK-AMBR information. The base station can manage the PC5-LINK-AMBR information based on the SLRB configuration request signal received from the terminal. Here, the PC5-LINK-AMBR information can refer to information about a relationship between a sidelink flow, an SLRB, a logical channel, a PC5 unicast link, and an AMBR of the PC5 unicast link of the terminal. The base station can update the SLRB configuration about the sidelink flow and the PC5-LINK-AMBR information. If the base station receives at least one of the sidelink flow, the PC5 unicast link mapped to the sidelink flow, or the PC5-LINK-AMBR from the terminal, the base station can manage the sidelink flow, the PC5 unicast link, the SLRB, the logical channel, and the PC5-LINK-AMBR mapping information thereon. This information can be used when the terminal requests a sidelink resource allocation to the base station.

[0126] In operation 813, the terminal can transmit a signal (hereinafter, a sidelink resource request signal) requesting a resource for a sidelink to the base station. The terminal can request the base station to allocate a resource for transmission of a packet belonging to a sidelink flow. The sidelink resource request signal can include at least one of a destination identifier, a source identifier, a logical channel identifier, and buffer status information.

[0127] In operation 815, the base station can transmit resource allocation information to the terminal. When the sidelink resource request signal is received from the terminal, the base station can perform sidelink resource allocation based on at least one of the destination identifier, the source identifier, and the logical channel identifier, and the information (e.g., SLRB configuration and PC5-LINK-AMBR information) managed in operation 811. That is, the base station can perform scheduling. The base station can determine that the request is a resource request for a sidelink unicast link, and can determine an identifier of a corresponding PC5 unicast link. The base station can determine a sidelink resource to be allocated to the terminal based on a PC5-LINK-AMBR corresponding to the PC5 unicast link. When it is determined to allocate the sidelink resource, the base station can transmit allocation information about the sidelink resource, i.e., sidelink resource allocation information, to the terminal.

[0128] In Figure 8b , a scheme for obtaining PC5-LINK-AMBR information based on a sidelink resource request is described. Referring to Figure 8b In operation 821, the terminal can identify a sidelink flow. The terminal can determine that a sidelink flow is generated. The terminal can identify the generated sidelink flow. The sidelink flow can include a new flow or a sidelink flow that needs to be reconfigured due to a state of the terminal becoming in RRC_CONNECTED. Since operation 821 corresponds to operation 801 of Figure 8a , the same or similar description thereof can be omitted.

[0129] In operation 823, the terminal can identify the PC5 unicast link. The terminal can identify the PC5 unicast link mapped to the sidelink flow.

[0130] In operation 825, the terminal can identify the PC5-LINK-AMBR. The terminal can identify the PC5-LINK-AMBR based on at least one of the sidelink flow or the PC5 unicast link. That is, the terminal can manage information about the sidelink flow and the PC5 unicast link. Here, the terminal can identify the PC5-LINK-AMBR of the PC5 unicast link to which the sidelink flow is mapped.

[0131] In operation 827, the terminal can transmit a signal (hereinafter, SLRB configuration request signal) for requesting sidelink radio bearer (SLRB) configuration information. The terminal can transmit the SLRB configuration request signal in order to configure SLRB information, thereby enabling to transmit and receive a packet corresponding to the sidelink flow. The terminal can transmit the SLRB configuration request signal to the base station when the terminal and the base station are in an RRC CONNECTED state. The SLRB configuration request signal can include at least one of a destination identifier, a source identifier, a sidelink flow identifier, and a QoS profile of the sidelink flow (the profile can correspond to 5QI, PQI, or QoS requirement). The SLRB configuration request signal can include a plurality of pieces of sidelink flow information.

[0132] In operation 829, the base station can transmit SLRB configuration information to the terminal. The base station can transmit the SLRB configuration information to the terminal in response to the request performed in operation 827. The SLRB configuration information can include at least one of an SLRB identifier mapped to the sidelink flow, radio parameter information about the SLRB (for example, at least one of SDAP configuration, PDCP configuration, RLC configuration, MAC configuration, and PHY configuration), a logical channel identifier, and a logical channel identifier group.

[0133] In operation 831, the terminal can transmit a signal (hereinafter, sidelink resource request signal) for requesting a resource for a sidelink to the base station. The terminal can request the base station to allocate a resource for transmission of a packet belonging to the sidelink flow.

[0134] According to various embodiments, the terminal can transmit PC5 unicast link information mapped to a sidelink flow together with a sidelink resource request signal. That is, the terminal can transmit, to the base station, a sidelink resource request signal including information about a PC5 unicast link mapped to a sidelink flow and information about an AMBR of the PC5 unicast link. The sidelink resource request signal can include at least one of a destination identifier, a source identifier, a logical channel identifier, buffer status information, a PC5 unicast link identifier, and a PC5-LINK-AMBR. According to an embodiment, if it is determined that the terminal has previously transmitted a PC5-LINK-AMBR for a PC5 unicast link mapped to a sidelink flow to the base station and the value has not changed, the PC5-LINK-AMBR can be omitted from the sidelink resource request signal.

[0135] In operation 833, the base station can manage PC5-LINK-AMBR information. The base station can manage the PC5-LINK-AMBR information based on the sidelink resource request signal received from the terminal. Here, the PC5-LINK-AMBR information can refer to information about the relationship between a sidelink flow, an SLRB, a logical channel, a PC5 unicast link, and an AMBR of the PC5 unicast link of the terminal. In addition, the base station can update a sidelink flow, a PC5 unicast link mapped thereto, and PC5-LINK-AMBR information. The base station can manage a destination identifier, a sidelink flow, a unicast link, an SLRB, a logical channel, and PC5-LINK-AMBR mapping information thereon.

[0136] In operation 835, the base station can transmit resource allocation information to the terminal. The base station can perform sidelink resource allocation based on at least one piece of information among a destination identifier, a source identifier, and a logical channel identifier included in the sidelink resource request signal of the terminal and information (e.g., PC5-LINK-AMBR information) managed in operation 833. That is, the base station can perform scheduling. The base station can determine that the request is a resource request for a sidelink unicast link and can determine an identifier of a corresponding PC5 unicast link. The base station can determine a sidelink resource to be allocated to the terminal based on a PC5-LINK-AMBR corresponding to the PC5 unicast link. When it is determined to allocate a sidelink resource, the base station can transmit sidelink resource allocation information to the terminal.

[0137] In addition, in operation 835, the base station can transmit, to the terminal, information about a PC5 unicast link mapped to a sidelink flow and information about an AMBR of the PC5 unicast link. Figure 8bIn the middle, the identification of the PC5-LINK-AMBR in operation 825 is shown to be performed after the SLRB configuration request in operation 827, but the disclosure is not limited thereto. According to an embodiment, the terminal can identify the PC5-LINK-AMBR corresponding to the unicast link before transmitting the sidelink resource request signal after receiving the SLRB configuration information (i.e., after operation 829), and can include the corresponding PC5-LINK-ABMR in the sidelink resource request signal in order to transmit the sidelink resource request signal to the base station.

[0138] With Figure 8b Unlike, as another embodiment of the disclosure, the identifier of the PC5 unicast link and the PC5-LINK-AMBR information can be separated and transmitted. When transmitting the SLRB configuration request signal in operation 827, the terminal can transmit the PC5-LINK-AMBR information to be applied to each sidelink unicast link. In addition, the sidelink resource request signal of operation 831 can include the PC5 unicast link identifier information in addition to at least one of the destination identifier, the source identifier, the logical channel identifier, and the buffer status information. Based on the sidelink flow, the SLRB, and the logical channel information including the PC5-LINK-AMBR in operation 827 and the destination identifier, the source identifier, the logical channel identifier, and the PC5 unicast link identifier information in operation 831, the base station can determine that the request is a resource request for the PC5 unicast link, and can determine the identifier of the sidelink unicast link. The base station can determine the sidelink resource to be allocated to the terminal based on the PC5-LINK-AMBR corresponding to the unicast link. When determining to allocate the sidelink resource, the base station can transmit the sidelink resource allocation information to the terminal.

[0139] In Figure 8c , a PC5-LINK-AMBR information acquisition scheme based on QoS information is described. When the terminal performs service registration, the core network entity can manage the QoS profile, the subscription profile, etc. of the terminal. Here, the core network entity is an entity for QoS management of the terminal, and can be a network entity in charge of a policy and control function (PCF) or a network entity connected with a network entity in charge of the PCF to perform QoS management (e.g., a network entity in charge of an access and mobility management function (AMF) or a network entity in charge of a session management function (SMF)). Here, according to an embodiment of the disclosure, the QoS profile of the terminal can include information used when the terminal transmits / receives a service through a sidelink, and can include PC5-LINK-AMBR information about a sidelink unicast link.

[0140] Referring to Figure 8cIn operation 841, the core network entity can transmit QoS information to the base station. Here, the QoS information can be information related to a QoS profile of a sidelink of the terminal. The core network entity can transfer the sidelink-related QoS profile information of the terminal to the base station serving the terminal. The QoS information can include a PC5-LINK-AMBR for a sidelink unicast link.

[0141] In operation 843, the base station can manage PC5-LINK-AMBR information. The base station can manage the PC5-LINK-AMBR information based on the QoS information received from the core network entity. Here, the PC5-LINK-AMBR information can refer to information about a relationship between a sidelink flow of the terminal, an SLRB, a logical channel, a PC5 unicast link, and an AMBR of the PC5 unicast link. The base station can update the PC5-LINK-AMBR information for the sidelink unicast link of the terminal.

[0142] In operation 845, the terminal can identify a sidelink flow. The terminal can determine that a sidelink flow is generated. The terminal can identify the generated sidelink flow. The sidelink flow can include a new flow or a sidelink flow that needs to be reconfigured because the state of the terminal becomes in RRC_CONNECTED.

[0143] In operation 847, the terminal can identify a PC5 unicast link. The terminal can identify a PC5 unicast link mapped to the sidelink flow.

[0144] In operation 849, the terminal can identify a PC5-LINK-AMBR. The terminal can identify the PC5-LINK-AMBR based on at least one of the sidelink flow and the PC5 unicast link. The terminal can manage information about the sidelink flow and the PC5 unicast link. The terminal can identify the PC5-LINK-AMBR of the PC5 unicast link to which the sidelink flow is mapped.

[0145] In operation 851, the terminal can transmit a link management message to the core network entity. The link management message according to various embodiments can include information related to a PC5 unicast link or a sidelink flow of the terminal which is necessary for managing QoS of the sidelink of the terminal. That is, the terminal can transmit sidelink flow information and information about a PC5 unicast link mapped to the sidelink flow to the core network entity. According to various embodiments, the link management message can include information about at least one of a sidelink flow identifier, a PC5 unicast link identifier, and a PC5-LINK-AMBR corresponding to the PC5 unicast link. According to an embodiment, if it is determined that the terminal has previously transmitted a PC5-LINK-AMBR for a PC5 unicast link mapped to a sidelink flow to the core network entity and the value thereof has not changed, the PC5-LINK-AMBR can be omitted from the link management message. The link management message can include one or more sidelink flows and information about a PC5 unicast link corresponding to each sidelink flow. Here, at least one sidelink flow can be mapped to one PC5 unicast link.

[0146] In operation 853, the core network entity can update QoS information. The core network entity can update QoS information about a sidelink of the terminal based on the link management message received in operation 851. The core network entity can transmit sidelink QoS profile information to the base station. The transmitted QoS profile information can include information about at least one of sidelink flow identifier information of the terminal, PC5 unicast link information mapped to the sidelink flow, and a PC5-LINK-AMBR for the PC5 unicast link. According to an embodiment, if it is determined that a PC5-LINK-AMBR for a PC5 unicast link mapped to a sidelink flow has been previously transmitted by the core network to the base station and the value thereof has not changed, the PC5-LINK-AMBR can be omitted from the signaling in operation 853.

[0147] In operation 855, the base station can manage PC5-LINK-AMBR information. The base station can manage PC5-LINK-AMBR information based on the QoS information received from the core network entity. Here, the PC5-LINK-AMBR information can refer to information about a relationship between a sidelink flow of the terminal, an SLRB, a logical channel, a PC5 unicast link, and a PC5-LINK-AMBR of the PC5 unicast link. The base station can update information about a sidelink flow of the terminal, a PC5 unicast link (e.g., a PC5 unicast link to which the sidelink flow is mapped), and a PC5-LINK-AMBR mapped to the PC5 unicast link (or the sidelink flow).

[0148] In operation 857, the terminal can transmit a signal (hereinafter, SLRB configuration request signal) for requesting sidelink radio bearer (SLRB) configuration information. The terminal can transmit the SLRB configuration request signal in order to configure SLRB information so as to enable transmission and reception of a packet corresponding to a sidelink flow. The terminal can transmit the SLRB configuration request signal to the base station when the terminal is in an RRC connected state with the base station. The SLRB configuration request signal can include at least one of a destination identifier, a source identifier, a sidelink flow identifier, and a QoS profile of a sidelink flow (the profile can correspond to 5QI, PQI, or QoS requirements). The SLRB configuration request signal can include information about one or more sidelink flows.

[0149] In operation 859, the base station can transmit SLRB configuration information to the terminal. The base station can transmit the SLRB configuration information to the terminal in response to the request performed in operation 857. The SLRB configuration information can include at least one of an SLRB identifier mapped to a sidelink flow, radio parameter information (for example, at least one of SDAP configuration, PDCP configuration, RLC configuration, MAC configuration, and PHY configuration) about the SLRB, a logical channel identifier, and a logical channel identifier group.

[0150] In operation 861, the terminal can transmit a signal (hereinafter, sidelink resource request signal) for requesting a resource for a sidelink to the base station. The terminal can request the base station to allocate a resource for transmission of a packet belonging to a sidelink flow. The sidelink resource request signal can include at least one piece of information among a destination identifier, a source identifier, a logical channel identifier, and buffer status information.

[0151] In operation 863, the base station can transmit resource allocation information to the terminal. When receiving the sidelink resource request signal from the terminal, the base station can determine that the request is a resource request for a PC5 unicast link, and can determine a corresponding PC5 sidelink unicast link identifier based on at least one piece of information among a destination identifier, a source identifier, and a logical channel identifier, and information (for example, PC5-LINK-AMBR information) managed in operation 855. The base station can determine a sidelink resource to be allocated to the terminal based on a PC5-LINK-AMBR corresponding to the PC5 unicast link. When determining to perform sidelink resource allocation, the base station can transmit allocation information about a sidelink resource, that is, sidelink resource allocation information, to the terminal.

[0152] Figure 8cOperations 857 and 859 are shown to be performed after operations 851 to 855, but the disclosure is not limited thereto. Operations 851 to 855 are performed in parallel (e.g., simultaneously) with the execution time point of operations 857 to 859, or the execution time point of operations 857 to 859 can precede the execution time point of operations 851 to 855. In other words, the procedure for managing the PC5-LINK-AMBR through the signaling between the terminal and the core network entity can be performed not only before the SLRB configuration procedure but also after the SLRB configuration procedure.

[0153] In Figure 8d In the above-described embodiments, a scheme for obtaining PC5-LINK-AMBR information based on SLRB update is described. Referring to Figure 8d In operation 871, the terminal can determine to delete a sidelink flow. For example, the terminal can determine that at least one sidelink flow that is pre-configured based on information of a V2X application is no longer needed. The terminal can determine to delete the at least one sidelink flow.

[0154] In operation 873, the terminal can transmit a message for SLRB update (hereinafter, SLRB update message). The terminal can determine an identifier of a sidelink flow to be deleted and an identifier of a PC5 unicast link mapped to the sidelink flow. The terminal can transmit, to the base station, the SLRB update message including information on the identifier of the sidelink flow and information on the identifier of the unicast link. The SLRB update message can include at least one of a sidelink flow identifier determined to be deleted, a sidelink unicast link identifier, a destination identifier, and a source identifier. According to an embodiment, when the sidelink flow identifier is mapped to one sidelink unicast link identifier, the transmission of the sidelink unicast link identifier can be omitted. The SLRB update message can include the sidelink flow identifier determined to be deleted and PC5-LINK-AMBR information mapped to the sidelink unicast link identifier.

[0155] In operation 875, the base station can transmit an SLRB update confirmation message. The base station can transmit the SLRB update confirmation message to the terminal as a response to the SLRB update message. The SLRB update confirmation message can include at least one of the sidelink flow identifier, the sidelink unicast link identifier, the destination identifier, and the source identifier included in the SLRB update signaling of operation 873.

[0156] In Operation 877, the base station can manage PC5-LINK-AMBR information. The base station can manage PC5-LINK-AMBR information based on SLRB update messages received from the terminal. The base station can update information about secondary link flows, PC5 unicast links (e.g., PC5 unicast links to which secondary link flows are mapped), and PC5-LINK-AMBRs mapped to PC5 unicast links (or secondary link flows).

[0157] exist Figure 8d The embodiments for managing PC5-LINK-AMBR after the deletion of a secondary link stream have been described, but various embodiments of this disclosure are not limited thereto. According to the embodiments, even when updating the PC5-LINK-AMBR value for a secondary link unicast link without considering the deletion of the secondary link stream, it is possible to use... Figure 8d Operations 873 to 877 in the process. Here, the SLRB update signaling of operation 873 may include at least one of the following: secondary link flow identifier, secondary link unicast link identifier, PC5-LINK-AMBR, destination identifier, and source identifier.

[0158] exist Figure 8e This document describes a scheme for obtaining PC5-LINK-AMBR information based on secondary link flow updates. When a terminal performs service registration, the core network entity can manage the terminal's QoS profile, subscription profile, etc. Here, the core network entity is the entity used for QoS management of the terminal, and can be the network entity responsible for Policy and Control Function (PCF) or a network entity connected to the network entity responsible for PCF to perform QoS management (e.g., the network entity responsible for Session Management Function (SMF)).

[0159] Reference Figure 8e In operation 881, the terminal may determine to delete a secondary link flow. The terminal may determine that at least one secondary link flow that was pre-configured based on information from a V2X application is no longer needed. The terminal may determine to delete that at least one secondary link flow.

[0160] In operation 883, the terminal can transmit a message for updating a sidelink flow (hereinafter, a sidelink flow update message). The terminal can determine an identifier of a sidelink flow to be deleted and an identifier of a PC5 unicast link mapped to the sidelink flow. The terminal can transmit, to the base station, an SLRB update message including information on the identifier of the sidelink flow and information on the identifier of the unicast link. The SLRB update message can include at least one of the sidelink flow identifier determined to be deleted, the sidelink unicast link identifier, the destination identifier, and the source identifier. According to an embodiment, when the sidelink flow identifier is mapped to one sidelink unicast link identifier, the transmission of the sidelink unicast link identifier can be omitted. The SLRB update message can include the sidelink flow identifier determined to be deleted and PC5-LINK-AMBR information mapped to the sidelink unicast link identifier.

[0161] In operation 885, the core network entity can update QoS information. The core network entity can update the QoS information on the sidelink of the terminal based on the sidelink flow update message received in operation 883. The core network entity can transmit QoS information update signaling to the base station. The QoS information update signaling can include at least one of the sidelink flow identifier, the sidelink unicast link identifier, the destination identifier, and the source identifier included in the sidelink flow update message of operation 883.

[0162] In operation 887, the base station can manage PC5-LINK-AMBR information. The base station can manage the PC5-LINK-AMBR information based on the QoS information received from the core network entity. Here, the PC5-LINK-AMBR information can refer to information on the relationship between the sidelink flow, the SLRB, the logical channel, the PC5 unicast link, and the PC5-LINK-AMBR of the PC5 unicast link of the terminal. The base station can update information on the sidelink flow, the PC5 unicast link (e.g., the PC5 unicast link to which the sidelink flow is mapped), and the PC5-LINK-AMBR mapped to the PC5 unicast link (or the sidelink flow).

[0163] In Figure 8e , embodiments of managing PC5-LINK-AMBR after deleting a sidelink flow have been described, but various embodiments of the disclosure are not limited thereto. According to an embodiment, operations 883 to 887 in the procedure of Figure 8e may be used even in a case where the PC5-LINK-AMBR value for the sidelink unicast link is updated without considering sidelink flow deletion. Here, the signaling of operations 883 and 885 can include at least one of the sidelink flow identifier, the sidelink unicast link identifier, and the PC5-LINK-AMBR.

[0164] Figure 9Base station operations for unicast-based sidelink radio resource allocation according to various embodiments of the disclosure are shown. The base station shows Figure 1 a base station 110.

[0165] Referring to Figure 9 In operation 901, the base station can obtain PC5-LINK-AMBR information. The base station can obtain PC5-LINK-AMBR information about a PC5 unicast flow of a terminal. According to an embodiment, the PC5-LINK-AMBR information can be derived from a signal transmitted from the terminal. For example, the signal can be a SLRB configuration request signal, a sidelink resource request signal, or a SLRB update message. In addition, according to an embodiment, the PC5-LINK-AMBR information can be derived from a message transmitted from a core network entity. For example, the message can be a message for updating a QoS profile of a sidelink of the terminal.

[0166] A signal transmitted from an entity to a terminal or a core network in order to obtain PC5-LINK-AMBR information can include at least one of a sidelink flow identifier of a terminal, a PC5 unicast link identifier to which the sidelink flow identifier is mapped, and PC5-LINK-AMBR information corresponding to the PC5 unicast link. For example, the terminal A can configure PC5-LINK-AMBR 1 (AMBR for a sidelink unicast link 1) and PC5-LINK-AMBR 2 (AMBR for a sidelink unicast link 2). The terminal A can transmit information about at least one of a sidelink flow identifier and a sidelink unicast link identifier mapped to PC5-LINK-AMBR 1 and PC5-LINK-AMBR 2, respectively, to a base station or a core network entity by using a procedure of Figures 8a to 8c

[0167] In operation 903, the base station can manage sidelink-related information about a terminal. According to various embodiments of the disclosure, the sidelink-related information can include at least one piece of information among a destination identifier, a source identifier, a sidelink flow identifier, a PC5 unicast link identifier, a PC5-LINK-AMBR, a SLRB identifier, a logical channel identifier, and a logical channel group identifier of the terminal. In addition, the base station can manage a destination identifier, a source identifier, a sidelink flow identifier, a SLRB identifier, a logical channel identifier, a logical channel group identifier, and PC5-LINK-AMBR information mapped to a PC5 unicast link identifier.

[0168] ​In operation 905, the base station can receive a sidelink resource request. The base station can receive a request for a sidelink radio resource from the terminal. The request for the sidelink radio resource of the terminal can correspond to a case where the SL-BSR is received. The SL-BSR transmitted by the terminal can include at least one of a destination address, a logical channel identifier, a logical channel group identifier, and buffer status information.

[0169] In operation 907, the base station can identify the PC5 unicast link of the terminal. The base station can determine the sidelink unicast link information of the terminal mapped to at least one piece of information included in the SL-BSR among the sidelink-related information managed in operation 903, based on at least one piece of information among the destination address, the logical channel identifier, and the logical channel group identifier included in the SL-BSR.

[0170] The base station can determine whether the PC5 unicast link corresponding to the resource request satisfies the limit according to the PC5-LINK-AMBR. That is, the base station can determine whether to perform sidelink resource allocation requested by the terminal based on the buffer status information included in the SL-BSR of the terminal and the PC5-LINK-AMBR of the PC5 unicast link. According to an embodiment, if it is determined that the transmission rate of the PC5 unicast link does not exceed the PC5-LINK-AMBR when the base station performs allocation of a resource allocated based on the buffer status information of the terminal, the base station can determine to allocate a resource to the PC5 unicast link requested by the terminal. The base station can allocate a resource to a logical channel corresponding to the PC5 unicast link. On the other hand, if it is determined that the transmission rate of the PC5 unicast link exceeds the PC5-LINK-AMBR, the base station can determine to delay resource allocation for a logical channel corresponding to the PC5 unicast link requested by the terminal or not to perform resource allocation therefor. Hereinafter, the operation of the base station will be described on the assumption that resource allocation is performed.

[0171] In operation 909, the base station can allocate a sidelink resource. The base station can perform resource allocation for a logical channel requested by the terminal. In addition, as described above, the base station can not perform resource allocation based on the PC5-LINK-AMBR. In this case, operation 909 of FIG. 9 can be omitted. Figure 9

[0172] The above-described operations of the base station have been described on the assumption that the terminal transmits the SL-BSR. Figures 8a to 9 ​Embodiment: If the base station and the terminal know the sidelink flow identifier or information corresponding to the sidelink flow identifier (e.g., the SLRB identifier or the logical channel identifier in the above embodiment), the PC5 unicast link identifier mapped thereto can be distinguished. For example, assume that the PC5 unicast link identifier 1 is mapped to the sidelink flow identifier 1, and the PC5 unicast link identifier 1 is mapped to the sidelink flow identifier 2. After the base station receives the mapping information between the sidelink flow identifier and the PC5 unicast link identifier, if the sidelink resource allocation request signal transmitted by the terminal includes the sidelink flow identifier 1, the logical channel identifier corresponding to the sidelink flow identifier 1, or the SLRB identifier corresponding to the sidelink flow identifier 1, the base station can acquire the PC5-LINK-AMBR corresponding to the PC5 flow identifier 1. The base station can process the sidelink resource allocation request based on the PC5-LINK-AMBR corresponding to the PC5 unicast link identifier 1. Alternatively, if the PC5 unicast link identifier 1 is included in the sidelink resource allocation request signal transmitted by the terminal, the base station can acquire the PC5-LINK-AMBR corresponding to the PC5 flow identifier 1. The base station can process the sidelink resource allocation request based on the PC5-LINK-AMBR corresponding to the PC5 flow identifier 1.

[0173] As another embodiment, a case in which the base station cannot distinguish the PC5 unicast link identifier only by using the sidelink flow identifier information can be considered. For example, assume that the PC5 unicast link identifier 1 is mapped to the sidelink flow identifier 1, and the PC5 unicast link identifier 1 is mapped to the sidelink flow identifier 1. After the base station receives the mapping information, if the sidelink resource allocation request signal transmitted by the terminal includes the sidelink flow identifier 1, the SLRB identifier corresponding to the sidelink flow identifier 1, the logical channel identifier corresponding to the sidelink flow identifier 1, the base station cannot know whether the request for sidelink resource allocation should be processed based on the PC5-LINK-AMBR corresponding to the PC5 unicast link identifier 1 or based on the PC5-LINK-AMBR corresponding to the PC5 unicast link identifier 2. In this case, according to an embodiment, the sidelink resource allocation request signal can include the sidelink flow identifier, information corresponding to the sidelink flow identifier (which can correspond to the logical channel identifier or the SLRB identifier), and the PC5 unicast link identifier mapped to the corresponding sidelink flow (or logical channel SLRB). According to another embodiment, separate identifier information that enables the sidelink flow identifier to be distinguished from the PC5 unicast link identifier mapped thereto can be defined. This separate identifier information can be included in the sidelink resource allocation request signal transmitted by the terminal to the base station.

[0174] 2. SLRB configuration scheme per packet group of sidelink flows

[0175] In a case where data transmission / reception is made through a Uu interface between a terminal and a base station, the base station can acquire information on whether a packet to be transmitted by the terminal or a packet to be received by the terminal is an IP packet or a non-IP packet through information exchange with a core network. In a case where data transmission / reception is made through a sidelink interface of a terminal, the base station can acquire information on whether a packet to be transmitted or received by the terminal is an IP packet or a non-IP packet through information exchange with the terminal. For example, if the terminal determines that a sidelink flow for IP packet transmission and a sidelink flow for non-IP packet transmission should be configured separately, and a sidelink radio bearer (SLRB) for each flow should be configured, the terminal can request the base station for separate SLRB configurations corresponding to the sidelink flow for the IP packet and the sidelink flow for the non-IP packet, respectively. If the base station receives a separate SLRB configuration request for the sidelink flow corresponding to the IP packet and the sidelink flow corresponding to the non-IP packet from the terminal, the base station can configure separate SLRBs for the sidelink flow corresponding to the IP packet and the sidelink flow corresponding to the non-IP packet according to the request of the terminal.

[0176] As another embodiment, when PC5-S signaling is transmitted and received between terminals, if the terminal determines that a sidelink flow for transmitting or receiving the PC5-S signaling should be configured separately, and a separate SLRB should be configured for the flow, the terminal can report to the base station that the sidelink flow for the PC5-S signaling needs a separate SLRB configuration. The base station can configure a separate SLRB for the flow for the PC5-S signaling according to the request of the terminal.

[0177] As another embodiment, when PC5-RRC signaling is transmitted and received between terminals, the terminal can determine that a sidelink flow for transmitting or receiving the PC5-RRC signaling should be configured separately, and a separate SLRB should be configured for the flow. The terminal can report to the base station that the sidelink flow for the PC5-RRC signaling needs a separate SLRB configuration. The base station can configure a separate SLRB for the flow for the PC5-RRC signaling according to the request of the terminal.

[0178] Hereinafter, a scheme for configuring an SLRB for each sidelink packet type will be described with reference to FIG. 10. Here, the sidelink packet type can include at least one of an IP packet, a non-IP packet, PC5-S signaling, and PC5-RRC signaling. For the sidelink communication of FIG. 10, at least one of unicast, groupcast, and broadcast can be used.

[0179] Figures 10a to 10c A signal flow between a terminal and a base station for sidelink radio bearer (SLRB) configuration for each packet type according to various embodiments of the disclosure is illustrated.

[0180] In Figure 10aIn the middle, embodiments in which a terminal in an RRC_CONNECTED state configures an SLRB for each packet type are described. Referring to Figure 10a In operation 1001, the terminal can identify a sidelink flow. The terminal can determine that a sidelink flow is generated. The terminal can identify the generated sidelink flow. For example, the terminal can identify a newly generated sidelink flow, i.e., a new flow. Also, for example, when the state of the terminal becomes RRC_CONNECTED, the terminal can identify a sidelink flow that needs to be reconfigured.

[0181] In operation 1003, the terminal can transmit information about the sidelink flow and information about the packet type to the base station. The terminal can determine the packet type of the identified sidelink flow. The packet type can include at least one of an IP packet, a non-IP packet, PC5-S signaling, and PC5-RRC signaling. The terminal can obtain information about the packet type. According to various embodiments, the terminal can transmit an SLRB configuration request for the sidelink flow to the base station. The SLRB configuration request can include information about the sidelink flow and information about the packet type. For example, the SLRB configuration request can include at least one of a destination identifier, a source identifier, a sidelink flow identifier, and a packet type identifier.

[0182] The packet type identifier is an indicator indicating the packet type and can be included in the SLRB configuration request when requesting a separate radio bearer configuration for the packet type. The packet type identifier can be included in the SLRB configuration request even when a radio bearer configuration that has been previously configured for the same packet type as the packet type is requested. For example, when SLRB1 configured for sidelink flow 1 corresponding to an IP packet type and sidelink flow 2 corresponding to an IP packet type is generated in operation 1001, the terminal can report the packet type identifier for the purpose of requesting the base station to configure SLRB1 that has been configured for the same IP packet type for sidelink flow 2 or to configure a new SLRB corresponding to the IP packet type for sidelink flow 2. Meanwhile, the signaling used in operation 1003 can include a SidelinkUEInformation message, a UEAssistanceInformation message, or a newly defined RRC message.

[0183] In operation 1005, the base station can configure SLRB configuration information based on the packet type. The base station can identify the packet type of the sidelink flow for which the terminal requests the SLRB configuration. The base station can identify the packet type of the sidelink flow based on the signaling of operation 1003. The base station can configure SLRB configuration information about the packet type.

[0184] Also, according to embodiments, unlike as Figure 10aIf the signaling of operation 1003 does not include the packet type of the sidelink flow for which the terminal requests the SLRB configuration, the base station can configure the SLRB for the sidelink flow regardless of the packet type, if different from that shown in the middle. On the other hand, if the packet type of the sidelink flow for which the terminal requests the SLRB configuration is included in the signaling of operation 1003, the base station can configure the SLRB for the sidelink flow based on the packet type. The base station can configure the SLRB configured for the same packet type as the packet type in the sidelink flow. For example, when the SLRB1 configured for the sidelink flow 1 corresponding to the IP packet type and the sidelink flow 2 corresponding to the IP packet type are generated in operation 1001, if the base station receives the sidelink flow 2 and the information indicating the IP packet type, the base station can determine to configure the SLRB1 for the sidelink flow 2 or to configure a new SLRB2 corresponding to the IP packet type for the sidelink flow 2.

[0185] In operation 1007, the base station can transmit the SLRB configuration information to the terminal. The base station can transfer the SLRB configuration information about the sidelink flow to the terminal. The SLRB configuration information of operation 1007 can include at least one of the SLRB ID and the SLRB configuration parameter.

[0186] In operation 1009, the terminal can identify the SLRB configuration information. Here, the SLRB configuration information can be the SLRB configuration information about the sidelink flow of operation 1001. In addition, the SLRB configuration information can be the SLRB configuration information about the packet type indicated through the signaling in operation 1003.

[0187] In Figure 10b In the middle, an embodiment in which the terminal in the RRC_IDLE or RRC_INACTIVE state configures the SLRB for each packet type is described.

[0188] Referring to Figure 10b In operation 1021, the terminal can identify the sidelink flow. The terminal can determine that the sidelink flow is generated. The terminal can identify the generated sidelink flow. For example, the terminal can identify the newly generated sidelink flow, i.e., a new flow. In addition, for example, the terminal can identify the sidelink flow that needs to be reconfigured when the state of the terminal becomes the RRC_IDLE or RRC_INACTIVE.

[0189] In operation 1023, the terminal can determine the packet type of the sidelink flow. The terminal can obtain information about the packet type. The packet type can include at least one of an IP packet, a non-IP packet, PC5-S signaling, and PC5-RRC signaling. Figure 10a Unlike, the terminal in the RRC_IDLE or RRC_INACTIVE state can not transmit information about the packet type to the base station.

[0190] In operation 1025, the base station can configure SLRB configuration information for each packet type. The base station can configure SLRB configuration information corresponding to each packet type. For example, assuming that the packet types include at least one of IP, non-IP, PC5-S, and PC5-RRC, the base station can independently configure SLRB configuration information corresponding to each of IP, non-IP, PC5-S, and PC5-RRC.

[0191] In operation 1027, the base station can transmit SLRB configuration information for each packet type to the terminal. The SLRB configuration request can include at least one of a destination identifier, a QoS profile identifier, an SLRB ID, an SLRB configuration parameter, and a packet type identifier. The SLRB configuration information can be configured and transmitted for each packet type identifier. In addition, when the base station does not support separate SLRB configuration for each packet type, the packet type identifier can be omitted from the SLRB configuration information. The signaling of operation 1027 can be transmitted so that a terminal in an RRC_IDLE or RRC_INACTIVE state can receive the signaling. For example, the signaling of operation 1027 can include a V2X system information block (SIB).

[0192] In operation 1029, the terminal can identify SLRB configuration information corresponding to a packet type. If it is determined that the SLRB configuration information received in operation 1027 includes information for each packet type, the terminal can identify corresponding SLRB configuration information based on the packet type of the sidelink flow in operation 1023. In other words, the terminal can identify SLRB configuration information corresponding to the packet type of operation 1023 from among the received SLRB configuration information for each packet. For example, when the packet type determined in operation 1023 is PC5-S, and when SLRB information for non-IP, SLRB information for PC5-S, and SLRB information for PC5-RRC are received in operation 1207, the terminal can identify the SLRB information for PC5-S.

[0193] On the other hand, unlike what is shown in FIG. 10B, when it is determined that the SLRB configuration information does not include information for each packet type, the terminal can determine corresponding SLRB configuration information based on at least one of the QoS profile identifier and the destination identifier of the sidelink flow regardless of the packet type of the sidelink flow determined in operation 1023. Figure 10b

[0194] In operation 1031, the terminal can determine the SLRB configuration information based on at least one of the QoS profile identifier and the destination identifier of the sidelink flow. For example, when the packet type of the sidelink flow determined in operation 1023 is PC5-S, and when SLRB information for non-IP, SLRB information for PC5-S, and SLRB information for PC5-RRC are received in operation 1027, the terminal can determine the SLRB information for PC5-S based on at least one of the QoS profile identifier and the destination identifier of the sidelink flow. Figure 10b ​In the middle, operations 1025 to 1027 are shown to be performed after operations 1021 to 1023, but the disclosure is not limited thereto. Operations 1025 to 1027 can be performed before or in parallel with operations 1021 to 1023. That is, the operations performed by the terminal and the operations performed by the base station can be performed separately.

[0195] In Figure 10c In the middle, an embodiment in which a terminal in an OUT-OF-COVERAGE state configures an SLRB for each packet type is described.

[0196] In operation 1041, the terminal can identify a sidelink flow. The terminal can determine that a sidelink flow is generated. The terminal can identify the generated sidelink flow. For example, the terminal can identify a newly generated sidelink flow, i.e., a new flow. Also, for example, when the state of the terminal becomes OUT-OF-COVERAGE, the terminal can identify a sidelink flow that needs to be reconfigured.

[0197] In operation 1043, the terminal can determine a packet type of the sidelink flow in operation 1043. The terminal can obtain information on the packet type. The packet type can include at least one of an IP packet, a non-IP packet, PC5-S signaling, and PC5-RRC signaling. Figure 10a Unlike this, the terminal in the OUT-OF-COVERAGE can not transmit information on the packet type to the base station.

[0198] In operation 1045, the terminal can acquire SLRB configuration information based on pre-configuration. Unlike Figure 10c Separately from the process of, the terminal can receive pre-configuration for an SLRB before being changed to OUT-OF-COVERAGE. The terminal can obtain pre-configured SLRB configuration information. The pre-configured SLRB configuration information can include at least one of a destination identifier, a QoS profile identifier, an SLRB ID, an SLRB configuration parameter, and a packet type identifier. The SLRB configuration information can be configured for each packet type identifier. When the system does not support separate SLRB configuration for each packet type, the packet type identifier can be omitted from the pre-configured SLRB configuration information.

[0199] In operation 1047, the terminal can identify SLRB configuration information corresponding to the packet type. When it is determined that the preconfigured SLRB configuration information includes information for each packet type, the terminal can identify the corresponding SLRB configuration information based on the packet type of the sidelink flow in operation 1043. In other words, the terminal can identify the SLRB configuration information corresponding to the packet type of operation 1023 from among the received preconfigured SLRB configuration information for each packet. For example, when the packet type determined in operation 1023 is PC5-RRC, and SLRB information for IP, SLRB information for non-IP, SLRB information for PC5-S, and SLRB information for PC5-RRC are preconfigured, the terminal can identify the SLRB information for PC5-RRC.

[0200] On the other hand, unlike the above-described Figure 10c When it is determined that the SLRB configuration information does not include information for each packet type, the terminal can determine the corresponding SLRB configuration information based on at least one of the QoS profile identifier and the destination identifier of the sidelink flow, regardless of the packet type determined in operation 1043.

[0201] Figures 11a to 11b A base station operation for configuration of a sidelink radio bearer for each packet type according to various embodiments of the disclosure is illustrated.

[0202] In Figure 11a In operation 1101, the base station can receive an SLRB configuration request from terminal 1. The SLRB configuration request information can include at least one of a destination identifier, a source identifier, a QoS profile, a sidelink flow identifier, and packet type information identifier. Figure 11a .

[0203] In operation 1101, the base station can receive an SLRB configuration request from terminal 1. The SLRB configuration request information can include at least one of a destination identifier, a source identifier, a QoS profile, a sidelink flow identifier, and packet type information identifier.

[0204] In operation 1103, the base station can identify the packet type. The base station can determine that the SLRB configuration request signaling of the terminal includes a sidelink flow and packet type information thereon. The base station can identify the packet type of the sidelink flow for which the SLRB configuration is requested based on the packet type information included in the SLRB configuration request.

[0205] In operation 1105, the base station can determine whether to support SLRB configuration for each packet type. If the SLRB configuration for each packet type is supported, the base station can perform operation 1107. When the SLRB configuration for each packet type is not supported, the base station can perform operation 1109.

[0206] In operation 1107, the base station can transmit SLRB configuration corresponding to the packet type. The base station can configure SLRB configuration information according to the packet type of the sidelink flow requested by the terminal, and transmit the SLRB configuration information to the terminal. For example, when it is determined that the packet type for which the terminal requests the SLRB configuration is an IP packet, the base station can configure an SLRB corresponding to the IP packet independently of an SLRB corresponding to other packet types (at least one of non-IP, PC5-S, and PC5-RRC). For another example, when it is determined that the packet type for which the terminal requests the SLRB configuration is a non-IP packet, the base station can configure an SLRB corresponding to the non-IP packet independently of an SLRB corresponding to other packet types (at least one of IP, PC5-S, and PC5-RRC). The base station can transmit the configured SLRB configuration to the terminal.

[0207] According to an embodiment, if it is determined that an SLRB corresponding to the same packet type as that of the sidelink flow has been configured and the configured SLRB is allowed to be configured for the sidelink flow, the base station can provide the terminal with information on the configured SLRB for the sidelink flow. Here, the signaling transmitted by the base station to the terminal can include at least pre-configured SLRB identifier information. According to another embodiment, if the base station determines to configure a new SLRB for the sidelink flow regardless of whether the SLRB is configured according to the packet type of the sidelink flow, the base station can provide the terminal with information on the new SLRB configuration for the sidelink flow. Here, the signaling transmitted by the base station to the terminal can include at least one new SLRB identifier and SLRB configuration parameters.

[0208] In operation 1109, the base station can configure SLRB configuration information on the sidelink flow requested by the terminal, and can transmit the SLRB configuration information to the terminal in operation 1109. Here, the SLRB configuration information can be configured without regard to each packet type. According to an embodiment, if it is determined that the already-configured SLRB is allowed to be configured for the sidelink flow, the base station can provide the terminal with information on the configured SLRB for the sidelink flow. Here, the signaling transmitted by the base station to the terminal can include at least pre-configured SLRB identifier information. According to another embodiment, when it is determined to configure a new SLRB for the sidelink flow, the base station can provide the terminal with information on the new SLRB configuration for the sidelink flow.

[0209] In Figure 11b In operation 1109, the base station can configure SLRB configuration information on the sidelink flow requested by the terminal, and can transmit the SLRB configuration information to the terminal in operation 1109. Here, the SLRB configuration information can be configured without regard to each packet type. According to an embodiment, if it is determined that the already-configured SLRB is allowed to be configured for the sidelink flow, the base station can provide the terminal with information on the configured SLRB for the sidelink flow. Here, the signaling transmitted by the base station to the terminal can include at least pre-configured SLRB identifier information. According to another embodiment, when it is determined to configure a new SLRB for the sidelink flow, the base station can provide the terminal with information on the new SLRB configuration for the sidelink flow.

[0210] Referring to Figure 11b In operation 1121, the base station can determine to support sidelink communication. For example, the sidelink communication can include NR V2X communication.

[0211] In operation 1123, the base station can determine whether SLRB configuration for each packet type is supported. If the SLRB configuration for each packet type is supported, the base station can perform operation 1125. If the SLRB configuration for each packet type is not supported, the base station can perform operation 1127.

[0212] In operation 1125, the base station can transmit SLRB configuration for each packet type. The base station can configure SLRB configuration information for each packet type of the sidelink flow and transmit the SLRB configuration information. The signaling transmitted by the base station can include at least one of a destination address, a QoS profile, an SLRB identifier, an SLRB configuration parameter, and a sidelink packet type identifier. According to various embodiments, the base station can configure the SLRB configuration information according to the packet type identifier. For example, the base station can configure at least one piece of SLRB configuration information about IP packets. For another example, the base station can configure at least one piece of SLRB configuration information about non-IP packets. For another example, the base station can configure at least one piece of SLRB configuration information about PC5-S packets. For another example, the base station can configure at least one piece of SLRB configuration information about PC5-RRC packets. In operation 1125, signaling for transmitting SLRB configuration for each packet type can be transmitted to enable a terminal in an RRC_IDLE or RRC_INACTIVE state to receive the signaling. For example, the signaling can include a V2X system information block (SIB).

[0213] In operation 1127, the base station can configure SLRB configuration information and can transmit the configured SLRB configuration information to the terminal. The signaling transmitted by the base station can include at least one of a destination address, a QoS profile, an SLRB identifier, and an SLRB configuration parameter. That is, since the SLRB configuration for each packet type is not supported, the packet type identifier can be omitted. Signaling for use by the base station to transmit the SLRB configuration information can be transmitted to enable a terminal in an RRC_IDLE or RRC_INACTIVE state to receive the signaling. For example, the signaling can include a V2X SIB.

[0214] Figure 11a An SLRB configuration scheme of a base station for a terminal in an RRC_CONNECTED state is shown, and Figure 11bA SLRB configuration scheme of a base station for a terminal in an RRC_IDLE or RRC_INACTIVE state is shown. On the other hand, a terminal located out of coverage, i.e., an OUT-OF-COVERAGE terminal, can be pre-configured to configure a SLRB for each packet type. The base station or a core network entity can transmit a pre-configuration for a SLRB before the state of the terminal becomes an OUT-OF-COVERAGE state.

[0215] Figure 12 A signal flow between terminals for a sidelink radio bearer configuration for each packet type according to various embodiments of the disclosure is shown. A case where a first terminal and a second terminal perform sidelink communication through a PC5 unicast link is described.

[0216] Referring to Figure 12 In operation 1201, the first terminal can determine to perform unicast-based sidelink communication. Specifically, the first terminal can perform sidelink communication with the second terminal. Here, the first terminal can determine to perform transmission or reception of a sidelink packet with the second terminal based on a PC5 unicast link.

[0217] In operation 1203, the first terminal and the second terminal can exchange PC5 unicast link-related information. For example, the first terminal can transmit PC5 unicast link-related information of the first terminal to the second terminal. Also, as an example, the second terminal can transmit PC5 unicast link-related information of the second terminal to the first terminal. According to various embodiments, the PC5 unicast link-related information can include at least one of information on a sidelink flow for sidelink communication between the first terminal and the second terminal and SLRB information on the sidelink flow. The first terminal can exchange at least one of sidelink flow information and SLRB information to be used for sidelink unicast communication with the second terminal with the second terminal. If it is determined that the first terminal and the second terminal can support SLRB configuration for each packet type, the information exchanged in operation 1203 can include packet type information corresponding to the sidelink flow and the SLRB.

[0218] In operation 1205, the second terminal can obtain at least one of sidelink flow information and SLRB information to be used for sidelink unicast communication with the first terminal. If it is determined that the first terminal and the second terminal can support SLRB configuration for each packet type, the second terminal can determine packet type information corresponding to a sidelink flow and an SLRB. The second terminal can determine a packet type corresponding to a sidelink flow and an SLRB. The corresponding packet type information corresponding to the SLRB can be used to determine a corresponding packet type used when the first terminal and the second terminal receive a unicast packet, and to transmit the packet to a corresponding packet type processor. For example, the first terminal or the second terminal can transmit a packet received through an SLRB and a flow corresponding to an IP packet type to an IP packet processor. For another example, the first terminal or the second terminal can transmit a packet received through an SLRB and a flow corresponding to a non-IP packet type to a non-IP packet processor.

[0219] SLRB configuration according to a packet type (e.g., non-IP packet and IP packet) can be the same as or different from each other. For example, a case where different SLRB configurations are required according to a packet type can correspond to a header compression (e.g., robust header compression (ROHC)) configuration. For an IP packet, a header compression configuration can be applied. For a non-IP packet, a header compression configuration can not be applied. When the type of a packet to be transmitted or received by a terminal is a non-IP packet, an SLRB should be configured so that a header compression configuration is not applied thereto. When the type of a packet to be transmitted or received by a terminal is an IP packet, an SLRB should be configured so that a header compression configuration should or should not be applied thereto.

[0220] As an embodiment of SLRB configuration according to packet type (e.g., non-IP packet, IP packet, etc.), packet type information can be defined as one of QoS profile parameters of a service flow. Here, the QoS profile parameters can include at least one of PQI index, resource type (GBR, non-GBR, or delay critical GBR), priority, packet delay budget (PDB), packet error rate, maximum data burst volume, average window, and packet type (IP or non-IP). The QoS profile parameters can be configured for a base station and a terminal. In the case of an RRC_CONNECTED terminal, the terminal can report a QoS profile of a service flow corresponding to a packet type to the base station. Signaling for reporting the QoS profile of the service flow can include, for example, at least one of a SidelinkUEInformation message and a UEAssistanceInformation message. The base station can obtain information on the packet type from the QoS profile of the service flow. The base station can determine the packet type of the QoS profile and provide SLRB configuration according to the packet type to the terminal through an RRC dedicated message. For example, if it is determined that the packet type is a non-IP packet, the SLRB configuration can include not applying header compression. For example, if it is determined that the packet type is an IP packet, the SLRB configuration can include not applying or applying header compression. In the case of an RRC_IDLE terminal or an RRC_INACTIVE terminal, the base station can provide SLRB configuration for a QoS profile to the terminal through a system information (SI) message. The SLRB configuration can provide a list of parameters according to the packet type of the QoS profile. The terminal can acquire the SLRB configuration for the QoS profile of a service flow corresponding to the packet type through system information. In the case of an OUT-OF-COVERAGE terminal, pre-configured SLRB configuration can provide a list of parameters according to the packet type of the QoS profile. The terminal can acquire the SLRB configuration for the QoS profile of a service flow corresponding to the packet type.

[0221] As another embodiment of SLRB configuration according to packet type (e.g., non-IP packet, IP packet, etc.), packet type information can be defined as one of QoS profile parameters of a service flow. That is, a PQI index of a QoS profile corresponding to a packet type can be configured. For example, PQI indexes 1 to 5 can be configured for a non-IP packet type, and PQI indexes 6 to 10 can be configured for an IP packet type. Here, the PQI index values described as an example are only one embodiment, and the example does not limit various embodiments of the disclosure. Needless to say, the PQI indexes corresponding to each packet type can be selected according to system operation. Packet type information mapped to the PQI index of the QoS profile can be configured for a base station and a terminal. In the case of an RRC_CONNECTED terminal, the terminal can report a PQI index of a service flow corresponding to a packet type to the base station. Signaling for reporting the PQI index of the service flow can include, for example, at least one of a SidelinkUEInformation message and a UEAssistanceInformation message. The base station can obtain information on a packet type from the PQI index. The base station can determine a packet type of a QoS profile corresponding to the PQI index and provide SLRB configuration according to the packet type to the terminal through an RRC dedicated message. For example, when it is determined that the packet type is a non-IP packet, the SLRB configuration can include not applying header compression. For example, if it is determined that the packet type is an IP packet, the SLRB configuration can include not applying or applying header compression. In the case of an RRC_IDLE terminal or an RRC_INACTIVE terminal, the base station can provide the SLRB configuration for a QoS profile corresponding to the PQI index to the terminal through a system information (SI) message. The SLRB configuration can provide a list of parameters according to the packet type of the PQI index of the QoS profile. The terminal can obtain the SLRB configuration for the PQI index of a service flow corresponding to a packet type through a system information (SI) message. In the case of an OUT-OF-COVERAGE terminal, a pre-configured SLRB configuration can provide a list of parameters according to the packet type of the PQI index of the QoS profile. The terminal can acquire the SLRB configuration for the PQI index of a service flow corresponding to a packet type.

[0222] As another embodiment of the SLRB configuration according to the packet type (e.g., non-IP packet, IP packet, etc.), the packet type information can be defined as one of LAYER-2 IDs. That is, a range of LAYER-2 IDs corresponding to the packet type can be distinguished. For example, for the non-IP packet type, a range of LAYER-2 IDs from 1 to 1000 can be configured, and for the IP packet type, a range of LAYER-2 IDs from 1001 to 2000 can be configured. Here, the LAYER-2 ID range described as an example is only one embodiment, and the example does not limit various embodiments of the disclosure. Needless to say, the LAYER-2 ID corresponding to each packet type can be selected according to system operation. The packet type information mapped to the LAYER-2 ID can be configured for the base station and the terminal. In the case of the RRC_CONNECTED terminal, the terminal can report the LAYER-2 ID of the service flow corresponding to the packet type to the base station. The signaling for reporting the LAYER-2 ID of the service flow can include, for example, at least one of the SidelinkUEInformation message and the UEAssistanceInformation message. The base station can obtain information on the packet type from the LAYER-2 ID. The base station can determine the packet type of the QoS profile corresponding to the LAYER-2 ID and provide the SLRB configuration according to the packet type to the terminal through the RRC dedicated message. For example, when it is determined that the packet type is a non-IP packet, the SLRB configuration can include not applying header compression. For example, if it is determined that the packet type is an IP packet, the SLRB configuration can include not applying or applying header compression. In the case of the RRC_IDLE terminal or the RRC_INACTIVE terminal, the base station can provide the SLRB configuration for the QoS profile corresponding to the LAYER-2 ID to the terminal through the system information (SI) message. The SLRB configuration can provide a list of parameters according to the packet type of the QoS profile. The terminal can acquire the SLRB configuration for the LAYER-2 ID of the service flow corresponding to the packet type through the system information (SI) message. In the case of the OUT-OF-COVERAGE terminal, the pre-configured SLRB configuration can provide a list of parameters according to the packet type of the LAYER-2 ID. The terminal can acquire the SLRB configuration for the LAYER-2 ID of the service flow corresponding to the packet type.

[0223] As another embodiment of SLRB configuration according to packet type (e.g., non-IP packet, IP packet, etc.), an SLRB configuration parameter that should be configured according to packet type can be defined to be configured by the terminal itself. In the case where there is no SLRB configuration parameter that needs to be configured according to packet type, the terminal can apply SLRB configuration signaling of the base station or be based on a pre-configured SLRB configuration. In the case where there is an SLRB configuration parameter that needs to be configured according to packet type, the terminal itself can configure the parameter without applying SLRB configuration signaling of the base station or being based on a pre-configured SLRB configuration. That is, a parameter to be configured according to packet type can not be provided to the terminal through RRC dedicated signaling, system information signaling, or pre-configuration of the base station. When performing a procedure of configuring SLRB configuration for a sidelink flow, the terminal can configure SLRB configuration provided by the base station or through pre-configuration, and the terminal itself can configure an SLRB configuration parameter to be applied to a packet type corresponding to the SLRB. For example, SLRB configuration provided by the base station or through pre-configuration can include PDCP configuration (e.g., PDCP-config), and the PDCP configuration (e.g., PDCP-config) can not include a header compression parameter. The terminal can configure the PDCP configuration (e.g., PDCP-config) provided by the base station or through pre-configuration, and can configure header compression based on packet type. When the packet type is a non-IP packet, the terminal can not configure a header compression parameter (here, if the header compression parameter is not configured, the terminal can configure the header compression parameter to "not used" or "NULL (invalid)"). When the packet type is an IP packet, the terminal can configure the header compression parameter to "not used / NULL" (not to apply header compression) or configure a header compression profile (e.g., ROHC profile and maximum context identification (CID) (maxCID)) to be applied.

[0224] As an embodiment, in the case of sidelink unicast, SLRB configuration according to packet type configured by the terminal itself can be transmitted to the counterpart terminal through sidelink SLRB configuration signaling (e.g., a sidelink access layer layer configuration message). Here, SLRB configuration according to packet type configured by the terminal itself can include a header compression parameter.

[0225] 3. Packet filtering scheme for receiving terminal

[0226] At least one of the destination identifier, the source identifier, and the propagation type, or a combination thereof, can be included in signaling transmitted by the transmitting terminal over a sidelink control channel (e.g., a physical sidelink control channel (PSCCH)) or a sidelink data channel (e.g., a physical sidelink shared channel (PSSCH)). Sidelink control information (SCI) transmitted over the sidelink control channel or the sidelink data channel can include at least one of the destination identifier, the source identifier, and the propagation type. A header of a MAC PDU transmitted over the sidelink control channel can include at least one of the destination identifier, the source identifier, and the propagation type. The receiving terminal can determine the destination identifier, the source identifier, and the propagation type information of the packet using the SCI transmitted over the sidelink control channel or the sidelink data channel. The receiving terminal can determine the destination identifier, the source identifier, and the propagation type information of the packet using the header of the MAC PDU transmitted over the sidelink data channel. The receiving terminal can determine whether the packet corresponds to the receiving terminal based on at least one of the destination identifier, the source identifier, and the propagation type of the sidelink control channel or the sidelink data channel. In addition, the receiving terminal can transmit the packet determined to correspond to the receiving terminal (i.e., a decoded MAC PDU) to a higher layer. For example, after determining whether the packet corresponds to the receiving terminal, the HARQ entity can transfer the packet determined to correspond to the receiving terminal to a de-assembly and demultiplexing entity as a next entity. Thereafter, the de-assembly and demultiplexing entity can transfer the packet to the higher layer. In addition, the receiving terminal can discard the packet determined not to correspond to the receiving terminal without transferring the packet to the higher layer. In addition, according to some embodiments, if the system is configured such that the receiving terminal can determine that the destination of the corresponding packet is the receiving terminal itself through at least one of the destination identifier, the source identifier, and the propagation type that can be transmitted through the SCI of the sidelink control channel or the sidelink data channel, the header of the MAC PDU transmitted over the sidelink data channel can not include at least one of the destination identifier, the source identifier, and the propagation type of the packet. In addition, according to some embodiments, the system is configured such that the receiving terminal can determine that the destination of the corresponding packet is the receiving terminal itself by combining at least one of the destination identifier, the source identifier, and the propagation type that can be transmitted through the SCI of the sidelink control channel or the sidelink data channel with at least one of the destination identifier, the source identifier, and the propagation type included in the header of the MAC PDU of the sidelink data channel.The above various embodiments are advantageous in that the buffer and processing capacity of the receiving terminal are efficiently used and the delay of packet processing is reduced, compared to a scheme in which the receiving terminal has to transfer a packet whose destination is not the receiving terminal itself to a higher layer and determine whether to perform packet discard in the higher layer, by providing a scheme in which the receiving terminal can perform an operation of determining that the destination of the corresponding packet is the receiving terminal itself in a lower layer.

[0227] Hereinafter, various schemes capable of determining a packet type identifier will be described with reference to FIG. 13. The packet type identifier processing scheme enables the receiving terminal to quickly determine the packet type and quickly perform packet processing. The packet type identifier can include at least one of an IP packet, a non-IP packet, and a PC5-S packet.

[0228] Figures 13a to 13d An example of packet filtering according to various embodiments of the disclosure is illustrated.

[0229] In Figure 13a Embodiments in which packet filtering is performed in the PDCP layer are described. Referring to Figure 13a , the V2X layer of the transmitting terminal can determine a packet type identifier corresponding to a sidelink flow or a sidelink packet. The packet type identifier can include at least one of an IP packet, a non-IP packet, and a PC5-S. When the packet type identifier is PC5-S, the sidelink flow can be omitted, and each packet can be managed as a sidelink packet. The V2X layer can transfer information of the packet and the packet type identifier to the PDCP layer. The PDCP layer of the transmitting terminal can configure the packet type identifier corresponding to the packet as a service data unit (SDU) type and transmit the packet type identifier to a lower layer (e.g., an RLC layer, a MAC layer, a PHY layer). When a packet is received from the lower layer, the PDCP layer of the receiving terminal can determine the packet type identifier configured as the SDU type. The PDCP layer can transfer the packet and the packet type identifier information to the V2X layer. The V2X layer of the receiving terminal can determine the packet type based on the packet type identifier information and can transmit the packet to a corresponding packet processor. For example, the V2X layer of the receiving terminal can transfer a packet corresponding to an IP packet type to an IP packet processor, a packet corresponding to a non-IP packet type to a non-IP packet processor, and a packet corresponding to a PC5-S packet type to a PC5-S processor, respectively.

[0230] In Figure 13aIn the case of the sidelink unicast in the example of FIG. 11, the V2X layer of the transmitting terminal can determine the packet type identifier of the sidelink flow of the PC5 unicast link. The V2X layer of the transmitting terminal can transfer the packet and the packet type information to the PDCP layer, and the PDCP layer can configure the packet type information identifier as an SDU type. The PDCP layer of the receiving terminal can determine the packet type information of the SDU type of the packet configured to be received from a lower layer, and can transfer the packet and the packet type identifier to the V2X layer. The V2X layer of the receiving terminal can transmit the sidelink flow and the corresponding packet of the sidelink unicast link to the corresponding packet processor based on the packet type identifier information.

[0231] In the case of the sidelink groupcast in the example of FIG. 12, the V2X layer of the transmitting terminal can determine the packet type identifier of the sidelink flow. The V2X layer of the transmitting terminal can transfer the packet and the packet type information to the PDCP layer. The PDCP layer of the transmitting terminal can configure the packet type information identifier as an SDU type. The PDCP layer of the receiving terminal can determine the packet type information of the SDU type of the packet configured to be received from a lower layer, and can transfer the packet and the packet type identifier to the V2X layer. The V2X layer of the receiving terminal can transmit the packet according to the groupcast to the packet processor corresponding to the packet type based on the packet type identifier information. Figure 13a In the case of the sidelink groupcast in the example of FIG. 12, the V2X layer of the transmitting terminal can determine the packet type identifier of the sidelink flow. The V2X layer of the transmitting terminal can transfer the packet and the packet type information to the PDCP layer. The PDCP layer of the transmitting terminal can configure the packet type information identifier as an SDU type. The PDCP layer of the receiving terminal can determine the packet type information of the SDU type of the packet configured to be received from a lower layer, and can transfer the packet and the packet type identifier to the V2X layer. The V2X layer of the receiving terminal can transmit the packet according to the groupcast to the packet processor corresponding to the packet type based on the packet type identifier information.

[0232] Figure 13a In the example of FIG. 13, the packet according to the sidelink broadcast can be processed in the same or similar manner as in the case of the sidelink groupcast.

[0233] In the example of FIG. 14, an embodiment in which packet filtering is performed in the SDAP layer is described. Referring to FIG. 14, a terminal supporting sidelink communication can individually manage the sidelink flow identifier of each packet type so as to determine the packet type based on the sidelink flow identifier when packet reception occurs. That is, the sidelink flow identifier can be associated with a specific packet type. The packet type can include at least one of IP, non-IP, and PC5-S. Figure 13b Figure 13b

[0234] ​​​The V2X layer of the transmitting terminal can determine a packet type identifier corresponding to the sidelink flow or the sidelink packet. The packet type identifier can include at least one of an IP packet, a non-IP packet, and a PC5-S. The V2X layer of the transmitting terminal can select one sidelink flow identifier from a sidelink flow identifier pool corresponding to the packet type based on packet type-flow identifier mapping information (e.g., information in [Table 1]) and can configure a flow identifier for a sidelink flow corresponding to the packet type. The V2X layer of the transmitting terminal can transfer the packet and the selected flow identifier information to the SDAP layer. The SDAP layer can configure the flow identifier in the SDAP header. The SDAP layer can transfer the packet to a lower layer (e.g., a PDCP layer, an RLC layer, a MAC layer, or a PHY layer).

[0235] When a packet is received from a lower layer, the SDAP layer of the receiving terminal can transmit the flow identifier information of the SDAP header together with the packet to the V2X layer. The V2X layer can determine packet type information corresponding to the flow identifier based on packet type-flow identifier mapping information (e.g., information in [Table 1]) and can transfer the packet to a corresponding packet processor. For example, the V2X layer of the receiving terminal can transfer a packet corresponding to an IP packet type to an IP packet processor, a packet corresponding to a non-IP packet type to a non-IP packet processor, and a packet corresponding to a PC5-S packet type to a PC5-S processor, respectively.

[0236] [Table 1] illustrates an operation example of the packet type-flow identifier mapping information (i.e., the sidelink flow identifier pool for each packet type) described above in Figure 13b [Table 1], for example. The number of sidelink flows can be configured according to the size of the flow ID field of the SDAP header.

[0237] [Table 1]

[0238] Packet type Sidelink flow identifier IP 1..N Non-IP N+1..M PC5-S M+1 Reserved L..L+X

[0239] In Figure 13bIn the example of a secondary link unicast, the V2X layer of the sending terminal can determine the packet type identifier of the secondary link flow of the PC5 unicast link. The V2X layer can select a flow identifier from the flow identifier pool corresponding to the packet type information shown in [Table 1], and can transmit the packet and flow identifier information to the SDAP layer. The SDAP layer can configure the flow identifier in the SDAP header and can transmit the packet to the lower layer. The SDAP layer of the receiving terminal can determine the flow identifier information configured in the SDAP header of the packet received from the lower layer, and can transmit the packet and flow identifier information to the V2X layer. The V2X layer of the receiving terminal can determine the packet type information corresponding to the flow identifier information based on [Table 1], and can transmit the corresponding packets of the secondary link flow and the secondary link unicast link to the corresponding packet processor.

[0240] exist Figure 13b In the example of secondary link multicast, the V2X layer of the sending terminal can determine the packet type identifier of the secondary link flow. The V2X layer of the sending terminal can select a flow identifier from the flow identifier pool corresponding to the packet type information shown in [Table 1], and can transmit the packet and flow identifier information to the SDAP layer. The SDAP layer of the sending terminal can configure the flow identifier information in the SDAP header and transmit the packet to the lower layer. The SDAP layer of the receiving terminal can determine the flow identifier information configured in the SDAP header of the packet received from the lower layer, and can transmit the packet and flow identifier information to the V2X layer. The V2X layer of the receiving terminal can determine the packet type information corresponding to the flow identifier information based on [Table 1], and can transmit the packets of the secondary link flow to the corresponding packet processor.

[0241] exist Figure 13b In the example, packets broadcast according to the secondary link can be handled in the same or similar way as secondary link multicast.

[0242] exist Figure 13c This document describes an embodiment of performing packet filtering in the SDAP and PDCP layers. (See also...) Figure 13c, the V2X layer of the transmitting terminal can determine a packet type identifier corresponding to the sidelink flow or the sidelink packet. The packet type identifier can include at least one of an IP packet, a non-IP packet, and a PC5-S. When the packet type identifier is the PC5-S, the sidelink flow can be omitted, and each packet can be managed as a sidelink packet. The V2X layer of the transmitting terminal can configure an identifier for the sidelink flow. The V2X layer of the transmitting terminal can transmit the packet, the packet type identifier, and the sidelink flow identifier information to the AS layer. The access stratum (AS) layer can denote at least one of, for example, an SDAP layer, a PDCP layer, and a MAC layer. The SDAP layer of the transmitting terminal can configure the sidelink flow identifier in an SDAP header of the packet and transmit the packet to the PDCP layer. The PDCP layer of the transmitting terminal can configure the packet type identifier corresponding to the packet as an SDU type and transmit the packet type identifier to a lower layer. When the packet is received from the lower layer, the PDCP layer of the receiving terminal can determine the packet type identifier configured as the SDU type. The PDCP layer can transfer the packet type identifier information to the V2X layer. The PDCP layer of the receiving terminal can transfer the packet to the SDAP layer. The SDAP layer of the receiving terminal can determine the flow identifier configured in the SDAP header of the packet and can transfer the packet and the flow identifier information to the V2X layer. The V2X layer of the receiving terminal can determine the packet type and the flow information based on the packet type identifier and the flow identifier information and can transmit the packet to a corresponding packet processor. For example, the V2X layer of the receiving terminal can transfer the packet corresponding to the IP packet type to an IP packet processor, transfer the packet corresponding to the non-IP packet type to a non-IP packet processor, and transfer the packet corresponding to the PC5-S packet type to a PC5-S processor, respectively.

[0243] In Figure 13cIn the example of a secondary link unicast, the V2X layer of the sending terminal can determine the packet type identifier of the secondary link flow of the PC5 unicast link and can configure the identifier of the secondary link flow. The V2X layer of the sending terminal can transmit packet, packet type identifier, and flow identifier information to the AS layer. The AS layer can represent at least one of, for example, the SDAP layer, PDCP layer, and MAC layer. The SDAP layer of the sending terminal can configure the flow identifier in the SDAP header and transmit the packet to the PDCP layer. The PDCP layer of the sending terminal can configure the packet type identifier as SDU type and send the packet to the lower layer. The PDCP layer of the receiving terminal can determine the packet type information of the SDU type of the packet configured to be received from the lower layer and can transmit the packet type identifier to the V2X layer. The PDCP layer of the receiving terminal can transmit the packet to the SDAP layer. The SDAP layer of the receiving terminal can determine the flow identifier information configured in the SDAP header of the packet and can transmit the packet and flow identifier information to the V2X layer. The V2X layer of the receiving terminal can transmit the corresponding packets of the secondary link stream and the secondary link unicast link to the corresponding packet processor based on the packet type identifier and flow identifier information.

[0244] exist Figure 13c In the example of secondary link multicast, the sending terminal's V2X layer can determine the packet type identifier for the secondary link flow and configure the flow identifier. The sending terminal's V2X layer can then transmit the packet, packet type information, and flow identifier information to the AS layer. The sending terminal's SDAP layer can configure the flow identifier in the packet's SDAP header and can transmit the packet to the PDCP layer. The sending terminal's PDCP layer can configure the packet type identifier as an SDU type. The receiving terminal's PDCP layer can determine the packet type information of the SDU type of the packet configured to be received from a lower layer and can transmit the packet type identifier to the V2X layer. The receiving terminal's PDCP layer can then transmit the packet to the SDAP layer. The receiving terminal's SDAP layer can determine the flow identifier information configured in the packet's SDAP header and can transmit the packet and flow identifier information to the V2X layer. Based on the packet type identifier information, the receiving terminal's V2X layer can transmit the multicast packet to the packet processor corresponding to the packet type.

[0245] exist Figure 13c In the example, packets broadcast based on the secondary link can be handled in the same or similar way as in the case of secondary link multicast.

[0246] exist Figure 13d This document describes an embodiment of performing packet filtering based on the mapping between the secondary link stream and the SLRB. (See also...) Figure 13dIn the case of the sidelink unicast, two terminals can exchange packet type information and SLRB configuration information about a sidelink flow between them. In addition, both terminals can perform packet transmission or reception through the SLRB of the configured sidelink flow. For example, as shown in Figure 12 the process of exchanging SLRB configuration information and packet type information between two terminals performing packet transmission or reception based on sidelink unicast can be performed.

[0247] When a packet to be transmitted through the configured unicast flow occurs, the V2X layer of the transmitting terminal can transmit the packet and a flow identifier of the packet to the SDAP layer. The SDAP layer of the transmitting terminal can determine the SLRB mapped to the flow identifier of the packet, and can transfer the packet to a lower layer (e.g., a PDCP layer, an RLC layer, a MAC layer, or a PHY layer). The lower layer of the transmitting terminal can transfer the packet through the SLRB. The receiving terminal can receive the packet for the SLRB, and the SDAP layer of the receiving terminal can determine a flow identifier mapped to the SLRB for which the packet is received. The SDAP layer of the receiving terminal can transfer the packet and the flow identifier information to the V2X layer. The V2X layer of the receiving terminal can determine packet type information based on the flow identifier information of the packet. Since the packet type information corresponding to the sidelink flow and the packet type information corresponding to the SLRB and the SLRB are exchanged between the two terminals (the transmitting terminal and the receiving terminal), the V2X layer of the receiving terminal can determine the packet type based on the flow identifier information. The V2X layer of the receiving terminal can transfer the corresponding packet of the sidelink flow and the sidelink unicast link to the corresponding packet processor.

[0248] Figure 13d Embodiments thereof can be difficult to apply to a sidelink groupcast or a sidelink broadcast which has a limitation in exchanging a sidelink flow identifier, SLRB information, and corresponding packet type information between target terminals.

[0249] In the case of the sidelink unicast according to other embodiments of the disclosure, a sidelink flow configured between two terminals and a PC5 unicast link identifier to which the sidelink flow is mapped can be mapped to packet type information. For example, unicast link identifier 1 can be mapped to at least one sidelink flow corresponding to an IP packet type, and unicast link identifier 2 can be mapped to at least one sidelink flow corresponding to a non-IP packet type. One or more sidelink unicast links corresponding to the IP packet type can be configured. One or more sidelink unicast links corresponding to the non-IP packet type can be configured. When a SLRB configuration procedure for unicast is performed between two terminals to perform sidelink unicast-based packet transmission or reception, packet type information about a sidelink flow or packet type information about a sidelink unicast link and a sidelink flow can be exchanged. When a packet to be transmitted by a transmitting terminal occurs, the V2X layer of the transmitting terminal can map a flow for packet transmission to a unicast link of a corresponding packet type based on the packet type. The V2X layer of the receiving terminal can determine a packet type of a packet based on packet type information of a unicast flow to which a flow for which the packet reception occurs is mapped. The V2X layer of the receiving terminal can transfer the packet to a corresponding packet processor. In addition to the operation of the V2X layer of each of the transmitting terminal and the receiving terminal, the operation of the SDAP layer and the PDCP layer of each of the transmitting terminal and the receiving terminal can be performed as follows. The SDAP layer of the transmitting terminal can map a corresponding SLRB to a flow identifier of a packet, and the SDAP layer of the receiving terminal can obtain a flow identifier from a SLRB through which a packet for the same is received. As another embodiment, the SDAP layer of the transmitting terminal can configure a flow identification in an SDAP header, and the SDAP layer of the receiving terminal can obtain a flow identifier configured in the SDAP header. The PDCP layer of the transmitting terminal can configure packet type information received from an upper layer as an SDU type, and the PDCP layer of the receiving terminal can transfer the packet type information configured as the SDU type to the upper layer.

[0250] Next, operations of the transmitting terminal and the receiving terminal according to each propagation type will be described.

[0251] The V2X layer of the transmitting terminal can determine a propagation type of a packet corresponding to a sidelink packet or a sidelink flow. The propagation type can include at least one of unicast, groupcast, and broadcast. The V2X layer can transfer at least one of a sidelink flow identifier corresponding to the packet, packet and packet type information, a destination identifier, a source identifier, and the propagation type to the AS layer. The AS layer can include at least one of, for example, an SDAP layer, a PDCP layer, and a MAC layer. The SDAP layer of the transmitting terminal can map a corresponding SLRB to a flow identifier of the packet. When an SDAP header is configurable in the SDAP layer, the flow identifier can be configured in the SDAP header. The SDAP layer of the transmitting terminal can transfer the packet to the PDCP layer. The PDCP layer of the transmitting terminal can determine packet type information of the packet. The PDCP layer of the transmitting terminal can determine a packet type of the packet and configure an SDU type based on the packet type. That is, the PDCP layer of the transmitting terminal can configure the packet type information identifier as the SDU type. The PDCP layer of the transmitting terminal can transfer the packet to a lower layer (e.g., an RLC layer, a MAC layer, or a PHY layer). If configuration of a destination identifier and a source identifier is allowed in a MAC header, the MAC layer in the lower layer of the PDCP layer can configure the destination identifier and the source identifier of the packet in the MAC header. If configuration of a propagation type is allowed in the MAC header, the MAC layer of the transmitting terminal can include the propagation type information in the MAC header. The propagation type information can be used when it is determined that the propagation type corresponding to the packet cannot be distinguished based on the destination identifier and the source identifier. The destination identifier and the source identifier of the MAC header can be used when it is determined that the destination corresponding to the packet cannot be distinguished based on SCI transmitted through a sidelink control channel. If the propagation type information is allowed to be configured in the SCI transmittable through the sidelink control channel, the transmitting terminal can include the propagation type information in the SCI. The transmitting terminal can transmit the SCI including the propagation type information to the receiving terminal. If the destination identifier and the source identifier are allowed to be configured in the SCI transmittable through the sidelink control channel, the transmitting terminal can include the destination identifier and the source identifier in the SCI. The transmitting terminal can transmit the SCI including the destination identifier information and the source identifier information to the receiving terminal.

[0252] The reception terminal can receive SCI through a sidelink control channel and determine whether the propagation type information is included therein. If the propagation type information is included in the SCI, the reception terminal can determine the propagation type of the corresponding packet. The reception terminal can determine whether the destination identifier information and the source identifier information are included in the SCI. If the SCI includes the destination identifier information and the source identifier information, the reception terminal can determine the destination identifier and the source identifier of the corresponding packet. According to an embodiment, the reception terminal can distinguish the propagation type through the destination identifier and the source identifier. Based on the destination identifier, the source identifier, and the propagation type information of the SCI, the reception terminal can determine whether the corresponding packet is related to the reception terminal itself. If it is determined that the packet is not related to the reception terminal itself, the reception terminal can discard the packet. If it is determined that the packet is related to the reception terminal itself, the reception terminal can transmit the packet to a higher layer. If the destination identifier and the source identifier are allowed to be configured in the MAC PDU header, the MAC layer of the reception terminal can determine the destination identifier and the source identifier of the MAC header. If the propagation type is allowed to be configured in the MAC PDU header, the MAC layer of the reception terminal can determine the propagation type information of the MAC header. The MAC layer of the reception terminal can determine whether the corresponding packet is related to the reception terminal itself through at least one of the destination identifier, the source identifier, and the propagation type. If it is determined that the packet is related to the reception terminal itself, the reception terminal can transmit the packet to a higher layer. If it is determined that the packet is not related to the reception terminal itself, the reception terminal can discard the packet. If the SDU type is configured, the PDCP layer of the reception terminal can determine the packet type identifier from the SDU type information. The packet type information can be transmitted to a higher layer. The SDAP layer of the reception terminal can determine the flow information from the packet transmitted to the SLRB. If the SDAP header is configured, the SDAP layer of the reception terminal can determine the flow identifier information from the SDAP header. The flow information can be transmitted to a higher layer (e.g., a V2X layer).

[0253] The V2X layer corresponding to the higher layer of the reception terminal can determine that the corresponding packet has a transmission type based on the flow identifier and the packet type identifier. According to an embodiment, the V2X layer of the reception terminal can determine a PC5 unicast link based on the flow identifier and the packet type identifier, and can determine that the corresponding packet is a unicast packet. The PC5 unicast link can be mapped to at least one of the flow identifier and the packet type identifier. The V2X layer of the reception terminal can transfer the packet to a corresponding packet type processor. According to an embodiment, the V2X layer of the reception terminal can determine that the corresponding packet is a sidelink groupcast packet based on the flow identifier and the packet type identifier. The V2X layer of the reception terminal can transfer the packet to a corresponding packet type processor. In addition, according to an embodiment, the V2X layer of the reception terminal can determine that the corresponding packet is a sidelink broadcast packet based on the flow identifier and the packet type identifier. The V2X layer of the reception terminal can transfer the packet to a corresponding packet type processor.

[0254] 4. Semi-persistent sidelink resource allocation scheme for aperiodic traffic

[0255] In the case of mode 1 resource allocation, the terminal can report information about a sidelink flow or a sidelink packet to the base station in order to receive a sidelink resource allocation from the base station. The information about the sidelink flow or the sidelink packet can include information about a traffic pattern of periodically occurring sidelink traffic. The sidelink traffic pattern information can include at least one piece of information among a packet size, a transmission period, and a transmission offset. Instead of a dynamic resource allocation method of receiving a sidelink resource allocation request from the terminal and allocating a sidelink resource based on a traffic pattern for a resource allocation request for periodically occurring sidelink traffic, the base station can perform a sidelink resource allocation for the terminal by using a semi-persistent resource allocation method even without a sidelink resource allocation request from the terminal. Here, the semi-persistent resource allocation method can correspond to at least one of semi-persistent scheduling (SPS), configured grant type 1, and configured grant type 2.

[0256] Traffic generated from a V2X application suitable for an advanced autonomous driving service tends to require less latency and higher reliability. When traffic of a V2X application requiring less latency and higher reliability is not periodically occurring, a method in which the terminal transmits a sidelink resource allocation request and the base station dynamically allocates a resource related thereto can be used in order to transmit traffic generated in the V2X application. However, a dynamic sidelink resource allocation method is highly unlikely to be suitable for traffic transmission of a V2X application requiring less latency and higher reliability. Therefore, a method of allowing the terminal to use a semi-persistent sidelink resource allocated for periodically occurring traffic for use of periodically occurring traffic requiring less latency and higher reliability.

[0257] A first scheme for supporting semi-persistent resource allocation for aperiodic traffic usage according to various embodiments of the disclosure is as follows.

[0258] The terminal can report QoS profile information of a sidelink flow corresponding to aperiodic traffic to the base station. RRC signaling for the terminal to report a sidelink flow corresponding to aperiodic traffic and QoS profile information related thereto can include at least one of a sidelink UE information message, a UE assistance information message, and a new RRC dedicated message. The QoS profile of the sidelink flow can correspond to at least one of QoS requirements corresponding to aperiodic traffic (5QI) and PQI requiring less latency and high reliability. If it is determined that aperiodic traffic requires high reliability and less latency, the base station can determine to apply semi-persistent sidelink resource allocation to the sidelink flow based on the QoS profile of the sidelink flow received from the terminal. The base station can transmit semi-persistent sidelink resource allocation information for the sidelink flow to the terminal. The information transmitted by the base station to the terminal can include at least one of a sidelink flow identifier, a SLRB identifier, a logical channel identifier, and semi-persistent sidelink resource allocation information. The terminal can determine semi-persistent sidelink resource allocation for the sidelink flow.

[0259] A second scheme for supporting semi-persistent resource allocation for aperiodic traffic usage according to various embodiments of the disclosure is as follows.

[0260] The terminal can report the base station of sidelink traffic information needed to process a semi-persistent resource allocation used for sidelink traffic transmission. The information reported by the terminal to the base station can include at least one of sidelink flow information, sidelink traffic pattern information that can be periodically transmitted, and sidelink traffic pattern information that can be aperiodically transmitted. For example, the information reported by the terminal to the base station can be configured as shown in [Table 2]. When receiving the information in [Table 2] from the terminal, the base station can determine whether a sidelink flow has a sidelink traffic pattern that can be periodically transmitted or a sidelink traffic pattern that can be aperiodically transmitted. In addition, the base station can determine whether to configure sidelink resource allocation information for the sidelink flow in a semi-persistent manner based on the traffic pattern information. When the base station determines to perform sidelink resource allocation for the sidelink flow in a semi-persistent manner, the base station can provide semi-persistent sidelink resource allocation information to the terminal. The information transmitted by the base station to the terminal can include at least one of a sidelink flow identifier, an SLRB identifier, a logical channel identifier, and semi-persistent sidelink resource allocation information. The semi-persistent sidelink resource allocation information provided by the base station to the terminal can be configured separately for each of the periodically transmittable sidelink traffic and the aperiodically transmittable sidelink traffic or configured to be shared with each other. In the latter case, that is, when the resource allocation information is shared between the periodic sidelink traffic and the aperiodic sidelink traffic, the resource allocation information can include at least one of sidelink flow identifier information, an SLRB identifier, and a logical channel identifier that will use the same semi-persistent sidelink resource. The terminal can determine the semi-persistent sidelink resource allocation for the sidelink flow.

[0261] [Table 2]

[0262]

[0263] According to an embodiment, an operation method of a base station can include obtaining aggregate maximum bit rate (AMBR) information about a PC5 unicast link for sidelink communication of a terminal, allocating a resource for the sidelink communication of the terminal based on the AMBR information, and transmitting information about the allocated resource to the terminal.

[0264] According to an embodiment, the method can further include receiving, from the terminal, a signal for requesting a sidelink radio bearer (SLRB) configuration, and transmitting the SLRB configuration to the terminal, wherein the signal includes a flow for the sidelink communication; a PC5 unicast link mapped to the flow; and AMBR information about the PC5 unicast link.

[0265] According to an embodiment, the method can further include receiving, from the terminal, a signal for requesting a resource for the sidelink communication, wherein the signal includes a flow for the sidelink communication; a PC5 unicast link mapped to the flow; and AMBR information about the PC5 unicast link.

[0266] According to an embodiment, the method can further include receiving, from the terminal, a first signal for requesting a sidelink radio bearer (SLRB) configuration, transmitting the SLRB configuration to the terminal, and receiving, from the terminal, a second signal for requesting a resource for sidelink communication, wherein the first signal includes AMBR information for each PC5 unicast link, and the second signal includes an identifier of the PC5 unicast link.

[0267] According to an embodiment, the method can further include receiving, from the core network entity, QoS information of the terminal, wherein the QoS information of the terminal includes a flow for sidelink communication, a PC5 unicast link mapped to the flow, and AMBR information about the PC5 unicast link.

[0268] According to an embodiment, an operation method of a terminal in a wireless communication system can include obtaining aggregation maximum bit rate (AMBR) information about a PC5 unicast link for sidelink communication of the terminal, providing the AMBR information to a base station, receiving, from the base station, information about a resource for the sidelink communication that has been allocated based on the AMBR information, and transmitting data subsequent to the sidelink communication to another terminal based on the resource.

[0269] According to an embodiment, an operation method of a base station can include receiving, from a terminal, a signal for requesting a sidelink radio bearer (SLRB) configuration, obtaining, from the signal, packet type information about a sidelink flow of the terminal, generating SLRB configuration information about a packet type of the sidelink flow based on the packet type information, and transmitting the SLRB configuration information to the terminal, wherein the packet type is at least one of an IP packet, a non-IP packet, PC5-S signaling, and PC5 radio resource control (RRC) signaling.

[0270] According to an embodiment, an operation method of a terminal in a wireless communication system can include generating a sidelink flow for sidelink communication of the terminal, determining a packet type of the sidelink flow, and identifying a sidelink radio bearer (SLRB) configuration corresponding to the packet type, wherein the identifying of the SLRB configuration includes receiving, from a base station, information about the SLRB configuration corresponding to the packet type when the terminal is in a radio resource control (RRC) CONNECTED, receiving configuration information including an SRLB configuration for each packet and identifying the SLRB configuration corresponding to the packet type from the configuration information when the terminal is in an RRC INACTIVE or an RRC IDLE, and identifying the SLRB configuration corresponding to the packet type from pre-configuration information including an SRLB configuration for each packet when the terminal is out of coverage.

[0271] According to an embodiment, a method for operating a first terminal in a wireless communication system can include generating a sidelink flow for sidelink communication between the first terminal and a second terminal, and transmitting, to the second terminal, sidelink-related information indicating a packet type of the sidelink flow, wherein the packet type is identified based on at least one of an identifier of the sidelink flow of a service data adaptation protocol (SDAP) layer of the first terminal, sidelink radio bearer (SLRB) information mapped to the sidelink flow of the first terminal, or a service data unit (SDU) type of a packet data convergence protocol (PDCP) layer of the first terminal.

[0272] According to an embodiment, the sidelink-related information can include at least one of an identifier of the sidelink flow, the SLRB information, and an identifier of the packet type.

[0273] According to an embodiment, a base station in a wireless communication system can include at least one transceiver and at least one processor coupled to the at least one transceiver, wherein the at least one processor is configured to acquire aggregate maximum bit rate (AMBR) information about a PC5 unicast link for sidelink communication of a terminal, allocate resources for the sidelink communication of the terminal based on the AMBR information, and transmit information about the allocated resources to the terminal.

[0274] According to an embodiment, the at least one processor can be further configured to receive, from the terminal, a signal for requesting a sidelink radio bearer (SLRB) configuration, and transmit the SLRB configuration to the terminal, wherein the signal includes a flow for the sidelink communication, a PC5 unicast link mapped to the flow, and the AMBR information about the PC5 unicast link.

[0275] According to an embodiment, the at least one processor can be further configured to receive, from the terminal, a signal for requesting resources for the sidelink communication, wherein the signal includes a flow for the sidelink communication, a PC5 unicast link mapped to the flow, and the AMBR information about the PC5 unicast link.

[0276] According to an embodiment, the at least one processor can be further configured to receive, from the terminal, a first signal for requesting a sidelink radio bearer (SLRB) configuration, transmit the SLRB configuration to the terminal, and receive, from the terminal, a second signal for requesting resources for the sidelink communication, wherein the first signal includes AMBR information for each PC5 unicast link, and the second signal includes an identifier of the PC5 unicast link.

[0277] According to an embodiment, the at least one processor can be further configured to receive, from the core network entity, QoS information of the terminal, wherein the QoS information of the terminal includes: a flow for the sidelink communication; a PC5 unicast link mapped to the flow; and AMBR information about the PC5 unicast link.

[0278] According to an embodiment, a terminal can include at least one transceiver and at least one processor coupled to the at least one transceiver, wherein the at least one processor is configured to acquire aggregated maximum bit rate (AMBR) information about a PC5 unicast link for a sidelink communication of the terminal, provide the AMBR information to a base station, receive, from the base station, information about a resource for the sidelink communication that has been allocated based on the AMBR information, and transmit data after the sidelink communication to another terminal based on the resource.

[0279] According to an embodiment, a base station can include at least one transceiver and at least one processor coupled to the at least one transceiver, wherein the at least one processor is configured to: receive, from a terminal, a signal for requesting a sidelink radio bearer (SLRB) configuration, acquire, from the signal, packet type information about a sidelink flow of the terminal, generate SLRB configuration information about a packet type of the sidelink flow based on the packet type information, and transmit the SLRB configuration information to the terminal, wherein the packet type is at least one of an IP packet, a non-IP packet, a PC5-S signaling, and a PC5 radio resource control (RRC) signaling.

[0280] According to an embodiment, a base station can include at least one transceiver and at least one processor coupled to the at least one transceiver, wherein the at least one processor is configured to: generate a sidelink flow for a sidelink communication of a terminal, determine a packet type of the sidelink flow, and identify a sidelink radio bearer (SLRB) configuration corresponding to the packet type, wherein, to identify the SLRB configuration, the at least one processor is configured to: when the terminal is in a radio resource control (RRC) CONNECTED, receive, from the base station, information about the SLRB configuration corresponding to the packet type, when the terminal is in an RRC INACTIVE or an RRC IDLE, receive configuration information including an SLRB configuration for each packet and identify the SLRB configuration corresponding to the packet type from the configuration information, and when the terminal is out of coverage, identify the SLRB configuration corresponding to the packet type from pre-configuration information including an SLRB configuration for each packet.

[0281] According to an embodiment, a first terminal can include at least one transceiver and at least one processor coupled to the at least one transceiver, wherein the at least one processor is configured to: generate a sidelink flow for sidelink communication between the first terminal and a second terminal; and transmit, to the second terminal, sidelink-related information indicating a packet type of the sidelink flow, wherein the packet type is identified based on at least one of: an identifier of the sidelink flow of a service data adaptation protocol (SDAP) layer of the first terminal; sidelink radio bearer (SLRB) information mapped to the sidelink flow of the first terminal; or a service data unit (SDU) type of a packet data convergence protocol (PDCP) layer of the first terminal.

[0282] According to an embodiment, the sidelink-related information can include at least one of an identifier of the sidelink flow, SLRB information, and an identifier of the packet type.

[0283] The method according to various embodiments described in the claims or specification of the present disclosure can be implemented in hardware, software, or a combination of hardware and software.

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

[0285] The programs (software modules or software) can be stored in non-volatile memory including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile disc (DVD), or other types of optical storage device or magnetic cassette. Alternatively, any combination of some or all of them can form a memory in which the program is stored. In addition, a plurality of such memories can be included in the electronic device.

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

[0287] In the above detailed embodiments of the disclosure, elements disclosed in the disclosure are expressed in singular or plural according to the proposed specific embodiments. However, for the convenience of description, the singular form or the plural form is appropriately selected according to the situation presented, and the disclosure is not limited by the elements expressed in singular or plural. Therefore, the elements expressed in plural can also include a single element, or the elements expressed in singular can also include a plurality of elements.

[0288] Although specific embodiments have been described in the detailed description of the disclosure, various modifications and changes can be made thereto without departing from the scope of the disclosure. Therefore, the scope of the disclosure should not be understood as being limited to the embodiments, but should be defined by the appended claims and equivalents thereof.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: receiving a sidelink signal; obtaining sidelink control information (SCI) of the sidelink signal, wherein the SCI includes first identifier information and a transmission type indicator indicating one of a broadcast, a groupcast, or a unicast; obtaining a medium access control (MAC) protocol data unit (PDU) of the sidelink signal, wherein a header of the MAC PDU includes second identifier information; identifying a transmission type of the sidelink signal based on the transmission type indicator; determining whether to deliver the MAC PDU of the sidelink signal based on the identified transmission type, the first identifier information, and the second identifier information; delivering the MAC PDU of the sidelink signal to a first next entity; obtaining a packet data convergence protocol (PDCP) PDU of the sidelink signal and a service data adaptation protocol (SDAP) header of the sidelink signal; identifying a service data unit (SDU) type indicator of the PDCP PDU and a flow indicator of the SDAP header; and delivering the PDCP PDU of the sidelink signal to a second next entity according to the SDU type indicator and the flow indicator, wherein the SDU type indicator and the flow indicator indicate an internet protocol (IP) packet, a non-IP packet, or a proximity services sidelink (PC5-S). 2.The method of claim 1, wherein the first identifier information includes at least one of first source identifier information or first destination identifier information, and wherein the second identifier information includes at least one of second source identifier information or second destination identifier information. 3.The method of claim 1, wherein the first identifier information includes first source identifier information and first destination identifier information, and wherein the second identifier information includes second source identifier information and second destination identifier information. 4.A terminal in a wireless communication system, the terminal comprising: a transceiver; and a controller coupled to the transceiver and configured to: receive a sidelink signal; obtain sidelink control information (SCI) of the sidelink signal, wherein the SCI includes first identifier information and a transmission type indicator indicating one of a broadcast, a groupcast, or a unicast; obtain a medium access control (MAC) protocol data unit (PDU) of the sidelink signal, wherein a header of the MAC PDU includes second identifier information; identify a transmission type of the sidelink signal based on the transmission type indicator; determine whether to deliver the MAC PDU of the sidelink signal based on the identified transmission type, the first identifier information, and the second identifier information; deliver the MAC PDU of the sidelink signal to a first next entity; obtain a packet data convergence protocol (PDCP) PDU of the sidelink signal and a service data adaptation protocol (SDAP) header of the sidelink signal; identify a service data unit (SDU) type indicator of the PDCP PDU and a flow indicator of the SDAP header; and deliver the PDCP PDU of the sidelink signal to a second next entity according to the SDU type indicator and the flow indicator, wherein the SDU type indicator and the flow indicator indicate an internet protocol (IP) packet, a non-IP packet, or a proximity services sidelink (PC5-S). identify a service data unit, SDU, type indicator of the PDCP PDU and a flow indicator of the SDAP header; and deliver, to a second next entity, the PDCP PDU of the sidelink signal according to the SDU type indicator and the flow indicator, wherein the SDU type indicator and the flow indicator indicate an Internet Protocol, IP, packet, a non-IP packet, or a Proximity Communication Interface 5, PC5-S.

5. The terminal of claim 4, wherein the first identifier information includes at least one of first source identifier information or first destination identifier information, and wherein the second identifier information includes at least one of second source identifier information or second destination identifier information.

6. The terminal of claim 4, wherein the first identifier information includes first source identifier information and first destination identifier information, and wherein the second identifier information includes second source identifier information and second destination identifier information.

Images