Patent Description:
Various systems have been developed for processing of wireless data such as the fourth-generation (<NUM>) communication system (e.g., Long Term Evolution (LTE) communication system or LTE-Advanced (LTE-A) communication system) and the fifthgeneration (<NUM>) communication system (e.g., New Radio (NR) communication system), which uses a frequency band higher than the frequency band of the <NUM> communication system. The <NUM> communication system supports Enhanced Mobile Broadband (eMBB) communications, Ultra-Reliable and Low-Latency communications (URLLC), massive Machine Type Communications (mMTC), and the like.

The <NUM> communication system and <NUM> communication system support Vehicle-to-Everything (V2X) communications. The V2X communications supported in a cellular communication system, such as the <NUM> communication system, the <NUM> communication system, and the like, may be referred to as "Cellular-V2X (C-V2X) communications. " The V2X communications (e.g., C-V2X communications) may include Vehicle-to-Vehicle (V2V) communications, Vehicle-to-Infrastructure (V2I) communications, Vehicle-to-Pedestrian (V2P) communication, Vehicle-to-Network (V2N) communication, and the like.

In the cellular communication system, the V2X communications (e.g., C-V2X communications) may be performed based on "sidelink" communication technologies (e.g., Proximity-based Services (ProSe) communication technology, Device-to-Device (D2D) communication technology, or the like). For example, sidelink channels for vehicles participating in V2V communications may be established, and communications between the vehicles may be performed using the sidelink channels.

The sidelink communications may be performed using sidelink resources. However, a method of configuring the sidelink resources is not yet explicitly defined in the 3GPP LTE or NR specifications. Therefore, a method for configuring the sidelink resources is required to be defined.

<CIT> discloses methods, systems, and devices for wireless communication. A base station may communicate with a user equipment (UE) using frequency resources (e.g., subcarriers) with scalable channel spacing and time resources (e.g., slots) with variable slot durations. The individual slots may include multiple symbols, and each symbol may be allocated for communication in a specific link direction (e.g., uplink, downlink, or sidelink). For UEs configured to operate in a half-duplex mode, the base station may allocate sufficient time for the UE to transition between uplink and downlink configurations. In other cases, for carrier aggregation, the base station may coordinate with the UE to prevent conflicting communications (e.g., simultaneous uplink and downlink transmissions). UEs or other devices may communicate directly with one another in a device-to-device configuration using the same or a similar scheme to allow for half-duplex devices to transition between sending and receiving.

Accordingly, exemplary embodiments of the present disclosure provide an apparatus and a method for configuring sidelink resources.

According to the exemplary embodiments of the present disclosure, an operation method of a base station in a communication system may include generating time division duplex (TDD)-uplink-downlink configuration (TDD-UL-DL-configuration) common information, the TDD-UL-DL-configuration common information that includes information regarding a DL-UL transmission period, a DL pattern indicating DL resources, a UL pattern indicating UL resources, and a sidelink (SL) pattern indicating SL resources; and transmitting to a user equipment (UE) system information including the TDD-UL-DL-configuration common information, wherein the DL resources, the UL resources, and the SL resources are included in the DL-UL transmission period, and resources other than the DL resources, the UL resources, and the SL resources among all resources included in the DL-UL transmission period are flexible resources.

The SL pattern may include at least one of information that indicates a number of consecutive SL slots in the DL-UL transmission period, information that indicates a number of consecutive SL symbols located before a starting SL slot among the consecutive SL slots, information that indicates a number of consecutive SL symbols located after an ending SL slot among the consecutive SL slots, an index of the starting SL slot, and an index of the ending SL slot. The SL pattern may be used to reconfigure one or more UL resources among the UL resources configured by the UL pattern to SL resources used for SL communication.

The operation method may further include generating TDD-UL-DL-configuration dedicated information including a slot pattern that indicates resources used for SL communication among the flexible resources; and transmitting to the UE a radio resource control (RRC) message including the TDD-UL-DL-configuration dedicated information. The slot pattern may include at least one of a slot index, information indicating that all symbols included in a slot indicated by the slot index are SL symbols, information that indicates a number of consecutive SL symbols among all the symbols included in the slot indicated by the slot index, an index of a starting SL symbol among the consecutive SL symbols, and an index of an ending SL symbol among the consecutive SL symbols.

The operation method may further include generating a downlink control information (DCI) including a slot format indicator (SFI) indicating resources used for SL communication among the flexible resources; and transmitting the DCI to the UE through a physical downlink control channel (PDCCH).

Furthermore, according to the exemplary embodiments of the present disclosure, an operation method of a first user equipment (UE) in a communication system may include receiving from a base station system information including time division duplex (TDD)-uplink-downlink configuration (TDD-UL-DL-configuration) common information; and identifying information regarding a DL-UL transmission period, a DL pattern indicating DL resources, a UL pattern indicating UL resources, and a sidelink (SL) pattern indicating SL resources, which are included in the TDD-UL-DL-configuration common information. The DL resources, the UL resources, and the SL resources are included in the DL-UL transmission period, and resources other than the DL resources, the UL resources, and the SL resources among all resources included in the DL-UL transmission period are flexible resources.

The operation method may further include receiving from the base station a radio resource control (RRC) message including TDD-UL-DL-configuration dedicated information; identifying from the TDD-UL-DL-configuration dedicated information a slot pattern indicating resources used for SL communication among the flexible resources; and performing DL communication, UL communication, or the SL communication using resources configured by the TDD-UL-DL-configuration common information and the TDD-UL-DL-configuration dedicated information.

The slot pattern may include at least one of a slot index, information that indicates that all symbols included in a slot indicated by the slot index are SL symbols, information that indicates a number of consecutive SL symbols among all the symbols included in the slot indicated by the slot index, an index of a starting SL symbol among the consecutive SL symbols, and an index of an ending SL symbol among the consecutive SL symbols.

The performing of the SL communication may further include transmitting to a second UE a sidelink control information (SCI) including information that indicates the SL resources configured by the TDD-UL-DL-configuration common information and the TDD-UL-DL-configuration dedicated information; and performing the SL communication with the second UE using the SL resources indicated by the SCI.

The operation method may further include receiving a downlink control information (DCI) from the base station; identifying from the DCI a slot format indicator (SFI) that indicates resources used for SL communication among the flexible resources; and performing DL communication, UL communication, or the SL communication using resources configured by the TDD-UL-DL-configuration common information and the SFI.

Furthermore, according to the exemplary embodiments of the present disclosure, a base station in a communication system may include a processor, a transceiver operated by the processor, and a memory configured to store at least one instruction executable by the processor. Additionally, when executed by the processor, the at least one instruction may be configured to generate time division duplex (TDD)-uplink-downlink configuration (TDD-UL-DL-configuration) common information, the TDD-UL-DL-configuration common information including information regarding a DL-UL transmission period, a DL pattern indicating DL resources, a UL pattern indicating UL resources, and a sidelink (SL) pattern indicating SL resources; and transmit to a user equipment (UE) system information including the TDD-UL-DL-configuration common information. The DL resources, the UL resources, and the SL resources are included in the DL-UL transmission period, and resources other than the DL resources, the UL resources, and the SL resources among all resources included in the DL-UL transmission period are flexible resources.

The at least one instruction may be further configured to generate TDD-UL-DL-configuration dedicated information including a slot pattern that indicates resources used for SL communication among the flexible resources; and transmit to the UE a radio resource control (RRC) message including the TDD-UL-DL-configuration dedicated information. The slot pattern may include at least one of a slot index, information that indicates that all symbols included in a slot indicated by the slot index are SL symbols, information that indicates a number of consecutive SL symbols among all the symbols included in the slot indicated by the slot index, an index of a starting SL symbol among the consecutive SL symbols, and an index of an ending SL symbol among the consecutive SL symbols.

The at least one instruction may be further configured to generate a downlink control information (DCI) including a slot format indicator (SFI) that indicates resources used for SL communication among the flexible resources; and transmit the DCI to the UE through a physical downlink control channel (PDCCH).

Furthermore, according to the exemplary embodiments of the present disclosure, a first user equipment (UE) in a communication system may include a processor, a transceiver operated by the processor, and a memory configured to store at least one instruction executable by the processor. When executed by the processor, the at least one instruction may be configured to receive from a base station system information including time division duplex (TDD)-uplink-downlink configuration (TDD-UL-DL-configuration) common information; and identify information regarding a DL-UL transmission period, a DL pattern indicating DL resources, a UL pattern indicating UL resources, and a sidelink (SL) pattern indicating SL resources, which are included in the TDD-UL-DL-configuration common information.

The DL resources, the UL resources, and the SL resources are included in the DL-UL transmission period, and resources other than the DL resources, the UL resources, and the SL resources among all resources included in the DL-UL transmission period are flexible resources. The SL pattern may include at least one of information that indicates a number of consecutive SL slots in the DL-UL transmission period, information that indicates a number of consecutive SL symbols located before a starting SL slot among the consecutive SL slots, information that indicates a number of consecutive SL symbols located after an ending SL slot among the consecutive SL slots, an index of the starting SL slot, and an index of the ending SL slot. The SL pattern may be used to reconfigure one or more UL resources among the UL resources configured by the UL pattern to SL resources used for SL communication.

The at least one instruction may be further configured to receive from the base station a radio resource control (RRC) message including TDD-UL-DL-configuration dedicated information; identify from the TDD-UL-DL-configuration dedicated information a slot pattern that indicates resources used for SL communication among the flexible resources; and perform DL communication, UL communication, or the SL communication by using resources configured by the TDD-UL-DL-configuration common information and the TDD-UL-DL-configuration dedicated information.

The at least one instruction may be further configured to receive a downlink control information (DCI) from the base station; identify from the DCI a slot format indicator (SFI) that indicates resources used for SL communication among the flexible resources; and perform DL communication, UL communication, or the SL communication using resources configured by the TDD-UL-DL-configuration common information and the SFI.

The at least one instruction may be further configured to transmit to a second UE a sidelink control information (SCI) including information indicating the SL resources configured by the TDD-UL-DL-configuration common information and the SFI; and perform the SL communication with the second UE by using the SL resources indicated by the SCI.

According to the exemplary embodiments of the present disclosure, sidelink (SL) resources may be configured using at least one of the time division duplex-uplink-downlink-configuration (TDD-UL-DL-configuration) common information, the TDD-UL-DL-configuration dedicated information, and the downlink control information (DCI). The user equipment (UE) may be configured to perform sidelink communication with another UE using the SL resources. Alternatively, the SL resources may be configured by the UE, and the UE may be configured to transmit sidelink control information (SCI) including information that indicates the SL resources to another UE. The UE may be configured to perform the sidelink communication with another UE using the SL resources indicated by the SCI. Therefore, the sidelink communication may be efficiently performed, and the performance of the communication system may be improved.

Exemplary embodiments of the present disclosure will become more apparent by describing in detail exemplary embodiments of the present disclosure with reference to the accompanying drawings, in which:.

It should be understood that the above-referenced drawings are not necessarily to scale, presenting a somewhat simplified representation of various features illustrative of the basic principles of the disclosure. The specific design features of the present disclosure, including, for example, specific dimensions, orientations, locations, and shapes, will be determined in part by the particular intended application and use environment.

Exemplary embodiments of the present disclosure are disclosed herein. However, specific structural and functional details disclosed herein are merely representative for purposes of describing exemplary embodiments of the present disclosure. Thus, exemplary embodiments of the present disclosure may be embodied in many alternate forms and should not be construed as limited to exemplary embodiments of the present disclosure set forth herein.

Accordingly, while the present disclosure is capable of various modifications and alternative forms, specific exemplary embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that there is no intent to limit the present disclosure to the particular forms disclosed, but on the contrary, the present disclosure is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure. Like numbers refer to like elements throughout the description of the figures.

Other words used to describe the relationship between elements should be interpreted in a like fashion (i.e., "between" versus "directly between," "adjacent" versus "directly adjacent," etc.).

The terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting of the present disclosure. It will be further understood that the terms "comprises," "comprising," "includes" and/or "including," when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this present disclosure belongs.

It is understood that the term "vehicle" or "vehicular" or other similar term as used herein is inclusive of motor vehicles in general such as passenger automobiles including sports utility vehicles (SUV), buses, trucks, various commercial vehicles, watercraft including a variety of boats and ships, aircraft, and the like, and includes hybrid vehicles, electric vehicles, plug-in hybrid electric vehicles, hydrogen-powered vehicles and other alternative fuel vehicles (e.g., fuels derived from resources other than petroleum). As referred to herein, a hybrid vehicle is a vehicle that has two or more sources of power, for example both gasoline-powered and electric-powered vehicles.

Additionally, it is understood that one or more of the below methods, or aspects thereof, may be executed by at least one control unit. The term "control unit" or controller may refer to a hardware device that includes a memory and a processor. The memory is configured to store program instructions, and the processor is specifically programmed to execute the program instructions to perform one or more processes which are described further below. The control unit may control operation of units, modules, parts, or the like, as described herein. Moreover, it is understood that the below methods may be executed by an apparatus (e.g., communication node) comprising the control unit in conjunction with one or more other components, as would be appreciated by a person of ordinary skill in the art.

Furthermore, the control unit of the present disclosure may be embodied as non-transitory computer readable media containing executable program instructions executed by a processor, controller or the like. Examples of the computer readable mediums include, but are not limited to, ROM, RAM, compact disc (CD)-ROMs, magnetic tapes, floppy disks, flash drives, smart cards and optical data storage devices. The computer readable recording medium can also be distributed throughout a computer network so that the program instructions are stored and executed in a distributed fashion, e.g., by a telematics server or a Controller Area Network (CAN).

Unless specifically stated or obvious from context, as used herein, the term "about" is understood as within a range of normal tolerance in the art, for example within <NUM> standard deviations of the mean. "About" can be understood as within <NUM>%, <NUM>%, <NUM>%, <NUM>%, <NUM>%, <NUM>%, <NUM>%, <NUM>%, <NUM>%, <NUM>%, <NUM>%, <NUM>%, <NUM>%, or <NUM>% of the stated value. Unless otherwise clear from the context, all numerical values provided herein are modified by the term "about.

Hereinafter, exemplary embodiments of the present disclosure will be described in greater detail with reference to the accompanying drawings. In order to facilitate general understanding in describing the present disclosure, the same components in the drawings are denoted with the same reference signs, and repeated description thereof will be omitted.

<FIG> is a conceptual diagram illustrating V2X communication scenarios. As shown in <FIG>, the V2X communications may include Vehicle-to-Vehicle (V2V) communications, Vehicle-to-Infrastructure (V2I) communications, Vehicle-to-Pedestrian (V2P) communications, Vehicle-to-Network (V2N) communications, and the like. The V2X communications may be supported by a cellular communication system (e.g., a cellular communication system <NUM>), and the V2X communications supported by the cellular communication system <NUM> may be referred to as "Cellular-V2X (C-V2X) communications. " Here, the cellular communication system <NUM> may include the <NUM> communication system (e.g., LTE communication system or LTE-A communication system), the <NUM> communication system (e.g., NR communication system), and the like.

The V2V communications may include communications between a first vehicle <NUM> (e.g., a communication node located within the vehicle <NUM>) and a second vehicle <NUM> (e.g., a communication node located within the vehicle <NUM>). Various driving information such as velocity, heading, time, position, and the like may be exchanged between the vehicles <NUM> and <NUM> via the V2V communications. For example, autonomous driving (e.g., platooning) may be supported based on the driving information exchanged via the V2V communications. The V2V communications supported in the cellular communication system <NUM> may be performed based on "sidelink" communication technologies (e.g., ProSe and D2D communication technologies, and the like). In particular, the communications between the vehicles <NUM> and <NUM> may be performed using at least one sidelink channel established between the vehicles <NUM> and <NUM>.

The V2I communications may include communications between the first vehicle <NUM> (e.g., the communication node located within the vehicle <NUM>) and an infrastructure (e.g., road side unit (RSU)) <NUM> located on a roadside. The infrastructure <NUM> may also include a traffic light or a street light which is located on the roadside. For example, when the V2I communications are performed, the communications may be performed between the communication node located within the first vehicle <NUM> and a communication node located in a traffic light. Traffic information, driving information, and the like may be exchanged between the first vehicle <NUM> and the infrastructure <NUM> via the V2I communications. The V2I communications supported in the cellular communication system <NUM> may also be performed based on sidelink communication technologies (e.g., ProSe and D2D communication technologies, and the like). In particular, the communications between the vehicle <NUM> and the infrastructure <NUM> may be performed using at least one sidelink channel established between the vehicle <NUM> and the infrastructure <NUM>.

The V2P communications may include communications between the first vehicle <NUM> (e.g., the communication node located within the vehicle <NUM>) and a person <NUM> (e.g., a communication node carried by the person <NUM>). The driving information of the first vehicle <NUM> and movement information of the person <NUM> such as velocity, heading, time, position, and the like may be exchanged between the vehicle <NUM> and the person <NUM> via the V2P communications. The communication node located within the vehicle <NUM> or the communication node carried by the person <NUM> may be configured to generate an alarm indicating a danger by detecting a dangerous situation based on the obtained driving information and movement information. The V2P communications supported in the cellular communication system <NUM> may be performed based on sidelink communication technologies (e.g., ProSe and D2D communication technologies, and the like). In particular, the communications between the communication node located within the vehicle <NUM> and the communication node carried by the person <NUM> may be performed using at least one sidelink channel established between the communication nodes.

The V2N communications may be communications between the first vehicle <NUM> (e.g., the communication node located within the vehicle <NUM>) and a server connected via the cellular communication system <NUM>. The V2N communications may be performed based on the <NUM> communication technology (e.g., LTE or LTE-A) or the <NUM> communication technology (e.g., NR). Additionally, the V2N communications may be performed based on a Wireless Access in Vehicular Environments (WAVE) communication technology or a Wireless Local Area Network (WLAN) communication technology which is defined in Institute of Electrical and Electronics Engineers (IEEE) <NUM>, or a Wireless Personal Area Network (WPAN) communication technology defined in IEEE <NUM>.

Meanwhile, the cellular communication system <NUM> supporting the V2X communications may be configured as follows.

<FIG> is a conceptual diagram illustrating embodiments of a cellular communication system. As shown in <FIG>, a cellular communication system may include an access network, a core network, and the like. The access network may include a base station <NUM>, a relay <NUM>, User Equipment (UEs) <NUM> through <NUM>, and the like. The UEs <NUM> through <NUM> may include communication nodes located within the vehicles <NUM> and <NUM> of <FIG>, the communication node located in the infrastructure <NUM> of <FIG>, the communication node carried by the person <NUM> of <FIG>, and the like. When the cellular communication system supports the <NUM> communication technology, the core network may include a serving gateway (S-GW) <NUM>, a packet data network (PDN) gateway (P-GW) <NUM>, a mobility management entity (MME) <NUM>, and the like.

When the cellular communication system supports the <NUM> communication technology, the core network may include a user plane function (UPF) <NUM>, a session management function (SMF) <NUM>, an access and mobility management function (AMF) <NUM>, and the like. Alternatively, when the cellular communication system operates in a Non-Stand Alone (NSA) mode, the core network constituted by the S-GW <NUM>, the P-GW <NUM>, and the MME <NUM> may support the <NUM> communication technology as well as the <NUM> communication technology, or the core network constituted by the UPF <NUM>, the SMF <NUM>, and the AMF <NUM> may support the <NUM> communication technology as well as the <NUM> communication technology.

In addition, when the cellular communication system supports a network slicing technique, the core network may be divided into a plurality of logical network slices. For example, a network slice supporting V2X communications (e.g., a V2V network slice, a V2I network slice, a V2P network slice, a V2N network slice, etc.) may be configured, and the V2X communications may be supported through the V2X network slice configured in the core network.

The communication nodes (e.g., base station, relay, UE, S-GW, P-GW, MME, UPF, SMF, AMF, etc.) comprising the cellular communication system may be configured to perform communications using at least one communication technology among a code division multiple access (CDMA) technology, a time division multiple access (TDMA) technology, a frequency division multiple access (FDMA) technology, an orthogonal frequency division multiplexing (OFDM) technology, a filtered OFDM technology, an orthogonal frequency division multiple access (OFDMA) technology, a single carrier FDMA (SC-FDMA) technology, a non-orthogonal multiple access (NOMA) technology, a generalized frequency division multiplexing (GFDM) technology, a filter bank multi-carrier (FBMC) technology, a universal filtered multi-carrier (UFMC) technology, and a space division multiple access (SDMA) technology.

The communication nodes (e.g., base station, relay, UE, S-GW, P-GW, MME, UPF, SMF, AMF, etc.) comprising the cellular communication system may be configured as follows.

<FIG> is a conceptual diagram illustrating embodiments of a communication node constituting a cellular communication system. As shown in <FIG>, a communication node <NUM> may include at least one processor <NUM>, a memory <NUM>, and a transceiver <NUM> connected to a network for performing communications. Additionally, the communication node <NUM> may further include an input interface device <NUM>, an output interface device <NUM>, a storage device <NUM>, and the like. Each component included in the communication node <NUM> may be configured to communicate with each other as connected via a bus <NUM>.

However, each of the components included in the communication node <NUM> may be connected to the processor <NUM> via a separate interface or a separate bus rather than the common bus <NUM>. For example, the processor <NUM> may be connected to at least one of the memory <NUM>, the transceiver <NUM>, the input interface device <NUM>, the output interface device <NUM>, and the storage device <NUM> via a dedicated interface.

The processor <NUM> may be configured to execute at least one instruction stored in at least one of the memory <NUM> and the storage device <NUM>. The processor <NUM> may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which methods in accordance with exemplary embodiments of the present disclosure are performed. Each of the memory <NUM> and the storage device <NUM> may include at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory <NUM> may include at least one of read-only memory (ROM) and random access memory (RAM).

Referring again to <FIG>, in the communication system, the base station <NUM> may form a macro cell or a small cell, and may be connected to the core network via an ideal backhaul or a non-ideal backhaul. The base station <NUM> may be configured to transmit signals received from the core network to the UEs <NUM> through <NUM> and the relay <NUM>, and transmit signals received from the UEs <NUM> through <NUM> and the relay <NUM> to the core network. The UEs <NUM>, <NUM>, <NUM>, <NUM> and <NUM> may belong to cell coverage of the base station <NUM>. The UEs <NUM>, <NUM>, <NUM>, <NUM> and <NUM> may be connected to the base station <NUM> by performing a connection establishment procedure with the base station <NUM>. The UEs <NUM>, <NUM>, <NUM>, <NUM> and <NUM> may be configured to communicate with the base station <NUM> after being connected to the base station <NUM>.

The relay <NUM> may be connected to the base station <NUM> and may be configured to relay communications between the base station <NUM> and the UEs <NUM> and <NUM>. In other words, the relay <NUM> may be configured to transmit signals received from the base station <NUM> to the UEs <NUM> and <NUM>, and transmit signals received from the UEs <NUM> and <NUM> to the base station <NUM>. The UE <NUM> may belong to both of the cell coverage of the base station <NUM> and the cell coverage of the relay <NUM>, and the UE <NUM> may belong to the cell coverage of the relay <NUM>. In other words, the UE <NUM> may be located outside the cell coverage of the base station <NUM>. The UEs <NUM> and <NUM> may be connected to the relay <NUM> by performing a connection establishment procedure with the relay <NUM>. The UEs <NUM> and <NUM> may be configured to communicate with the relay <NUM> after being connected to the relay <NUM>.

The base station <NUM> and the relay <NUM> may support multiple-input, multiple-output (MIMO) technologies (e.g., single user (SU)-MIMO, multi-user (MU)-MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) communication technologies, carrier aggregation (CA) communication technologies, unlicensed band communication technologies (e.g., Licensed Assisted Access (LAA), enhanced LAA (eLAA), etc.), sidelink communication technologies (e.g., ProSe communication technology, D2D communication technology), or the like. The UEs <NUM>, <NUM>, <NUM> and <NUM> may be configured to perform operations that correspond to the base station <NUM> and operations supported by the base station <NUM>. The UEs <NUM> and <NUM> may be configured to perform operations that correspond to the relays <NUM> and operations supported by the relays <NUM>.

Particularly, the base station <NUM> may be referred to as a Node B (NB), an evolved Node B (eNB), a base transceiver station (BTS), a radio remote head (RRH), a transmission reception point (TRP), a radio unit (RU), a roadside unit (RSU), a radio transceiver, an access point, an access node, or the like. The relay <NUM> may be referred to as a small base station, a relay node, or the like. Each of the UEs <NUM> through <NUM> may be referred to as a terminal, an access terminal, a mobile terminal, a station, a subscriber station, a mobile station, a portable subscriber station a subscriber station, a node, a device, an on-broad unit (OBU), or the like.

Meanwhile, the communications between the UEs <NUM> and <NUM> may be performed based on the sidelink communication technique. The sidelink communications may be performed based on a one-to-one scheme or a one-to-many scheme. When V2V communications are performed using the sidelink communication technique, the UE <NUM> may be the communication node located within the first vehicle <NUM> of <FIG> and the UE <NUM> may be the communication node located within the second vehicle <NUM> of <FIG>. When V2I communications are performed using the sidelink communication technique, the UE <NUM> may be the communication node located within first vehicle <NUM> of <FIG> and the UE <NUM> may be the communication node located within the infrastructure <NUM> of <FIG>. When V2P communications are performed using the sidelink communication technique, the UE <NUM> may be the communication node located within first vehicle <NUM> of <FIG> and the UE <NUM> may be the communication node carried by the person <NUM> of <FIG>.

The scenarios to which the sidelink communications are applied may be classified as shown below in Table <NUM> according to the positions of the UEs (e.g., the UEs <NUM> and <NUM>) participating in the sidelink communications. For example, the scenario for the sidelink communications between the UEs <NUM> and <NUM> shown in <FIG> may be a sidelink communication scenario C.

Meanwhile, a user plane protocol stack of the UEs (e.g., the UEs <NUM> and <NUM>) performing sidelink communications may be configured as follows.

<FIG> is a block diagram illustrating exemplary embodiments of a user plane protocol stack of an UE performing sidelink communication. As shown in <FIG>, a left UE may be the UE <NUM> shown in <FIG> and a right UE may be the UE <NUM> shown in <FIG>. The scenario for the sidelink communications between the UEs <NUM> and <NUM> may be one of the sidelink communication scenarios A through D of Table <NUM>. The user plane protocol stack of each of the UEs <NUM> and <NUM> may include a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer.

The sidelink communications between the UEs <NUM> and <NUM> may be performed using a PC5 interface (e.g., PC5-U interface). A layer-<NUM> identifier (ID) (e.g., a source layer-<NUM> ID, a destination layer-<NUM> ID) may be used for the sidelink communications and the layer <NUM>-ID may be an ID configured for the V2X communications (e.g., V2X service). Also, in the sidelink communications, a hybrid automatic repeat request (HARQ) feedback operation may be supported, and an RLC acknowledged mode (RLC AM) or an RLC unacknowledged mode (RLC UM) may be supported.

Meanwhile, a control plane protocol stack of the UEs (e.g., the UEs <NUM> and <NUM>) performing sidelink communications may be configured as follows.

<FIG> is a block diagram illustrating a first exemplary embodiment of a control plane protocol stack of an UE performing sidelink communication, and <FIG> is a block diagram illustrating a second exemplary embodiment of a control plane protocol stack of an UE performing sidelink communication. As shown in <FIG>, a left UE may be the UE <NUM> shown in <FIG> and a right UE may be the UE <NUM> shown in <FIG>. The scenario for the sidelink communications between the UEs <NUM> and <NUM> may be one of the sidelink communication scenarios A through D of Table <NUM>. The control plane protocol stack illustrated in <FIG> may be a control plane protocol stack for transmission and reception of broadcast information (e.g., Physical Sidelink Broadcast Channel (PSBCH)).

The control plane protocol stack shown in <FIG> may include a PHY layer, a MAC layer, an RLC layer, and a radio resource control (RRC) layer. The sidelink communications between the UEs <NUM> and <NUM> may be performed using a PC5 interface (e.g., PC5-C interface). The control plane protocol stack shown in <FIG> may be a control plane protocol stack for one-to-one sidelink communication. The control plane protocol stack shown in <FIG> may include a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and a PC5 signaling protocol layer.

Meanwhile, channels used in the sidelink communications between the UEs <NUM> and <NUM> may include a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH). The PSSCH may be used for transmitting and receiving sidelink data and may be configured in the UE (e.g., UE <NUM> or <NUM>) by a higher layer signaling. The PSCCH may be used for transmitting and receiving sidelink control information (SCI) and may also be configured in the UE (e.g., UE <NUM> or <NUM>) by a higher layer signaling.

The PSDCH may be used for a discovery procedure. For example, a discovery signal may be transmitted over the PSDCH. The PSBCH may be used for transmitting and receiving broadcast information (e.g., system information). Additionally, a demodulation reference signal (DM-RS), a synchronization signal, or the like may be used in the sidelink communications between the UEs <NUM> and <NUM>.

Meanwhile, a sidelink transmission mode (TM) may be classified into sidelink TMs <NUM> to <NUM> as shown below in Table <NUM>.

When the sidelink TM <NUM> or <NUM> is supported, each of the UEs <NUM> and <NUM> may be configured to perform sidelink communications using a resource pool configured by the base station <NUM>. The resource pool may be configured for each of the sidelink control information and the sidelink data. The resource pool for the sidelink control information may be configured based on an RRC signaling procedure (e.g., a dedicated RRC signaling procedure, a broadcast RRC signaling procedure, etc.). The resource pool used for reception of the sidelink control information may be configured by a broadcast RRC signaling procedure. When the sidelink TM <NUM> is supported, the resource pool used for transmission of the sidelink control information may be configured by a dedicated RRC signaling procedure.

In particular, the sidelink control information may be transmitted via resources scheduled by the base station <NUM> within the resource pool configured by the dedicated RRC signaling procedure. When the sidelink TM <NUM> is supported, the resource pool used for transmission of the sidelink control information may be configured by a dedicated RRC signaling procedure or a broadcast RRC signaling procedure. The sidelink control information may be transmitted through resources selected autonomously by the UE (e.g., UE <NUM> or <NUM>) within the resource pool configured by the dedicated RRC signaling procedure or the broadcast RRC signaling procedure.

When the sidelink TM <NUM> is supported, the resource pool for transmitting and receiving sidelink data may not be configured. In particular, the sidelink data may be transmitted and received via resources scheduled by the base station <NUM>. When the sidelink TM <NUM> is supported, the resource pool for transmitting and receiving sidelink data may be configured by a dedicated RRC signaling procedure or a broadcast RRC signaling procedure. The sidelink data may be transmitted and received through resources selected autonomously by the UE (e.g., UE <NUM> or <NUM>) within the resource pool configured by the dedicated RRC signaling procedure or the broadcast RRC signaling procedure.

Further, sidelink resource configuration methods will be described. Even when a method (e.g., transmission or reception of a signal) to be performed at a first communication node among communication nodes is described, a corresponding second communication node may be configured to perform a method (e.g., reception or transmission of the signal) corresponding to the method performed at the first communication node. In other words, when an operation of a UE #<NUM> (e.g., first vehicle) is described, a corresponding UE #<NUM> (e.g., second vehicle) may be configured to perform an operation that corresponds to the operation of the UE #<NUM>. Conversely, when an operation of the UE #<NUM> (e.g., second vehicle) is described, the corresponding UE #<NUM> (e.g., first vehicle) may be configured to perform an operation that corresponds to the operation of the UE #<NUM>. In the exemplary embodiments described below, the operation of the vehicle may be the operation of the communication node located within the vehicle.

In the communication system, downlink (DL) resources, uplink (UL) resources, and sidelink (SL) resources may be configured. The DL resources may be used for DL communication between the base station and the UE (e.g., vehicle). The UL resources may be used for UL communication between the base station and the UE (e.g., vehicle). The SL resources may be used for SL communication between the UEs (e.g., vehicles). The DL resources, UL resources, and SL resources may be configured as follows.

<FIG> is a conceptual diagram illustrating a first exemplary embodiment of a DL-UL transmission period including DL resources, UL resources, and SL resources in a communication system. As shown in <FIG>, a DL-UL transmission period may be configured, and DL resources and UL resources may be configured within the DL-UL transmission period. Additionally, SL resources may be additionally configured within the DL-UL transmission period. In particular, the DL-UL transmission period may be referred to as a DL-SL-UL transmission period. A resource that is not configured as a DL resource, a UL resource, or an SL resource within the DL-UL transmission period may be configured as a flexible (FL) resource, and the FL resource may be overridden to a DL resource, a UL resource, or an SL resource.

The length (e.g., periodicity) of the DL-UL transmission period may be about <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM>. In other words, the DL-UL transmission period may be repeated every about <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> in the time axis. For example, a plurality of DL-UL transmission periods may be configured consecutively in the time axis, and DL resources, UL resources, and SL resources may be configured identically across the plurality of DL-UL transmission periods.

The DL resources may be indicated by a DL pattern described in Table <NUM> below. Particularly, a DL slot may be a slot consisting only of DL symbols, and a DL symbol may be used for DL communication.

The UL resources may be indicated by a UL pattern described in Table <NUM> below. Particularly, a UL slot may be a slot consisting only of UL symbols, and a UL symbol may be used for UL communication.

The SL resources may be indicated by an SL pattern described in Table <NUM> below. Particularly, an SL slot may be a slot consisting only of SL symbols, and an SL symbol may be used for SL communication. When a plurality of SL periods used for SL communication are present within one DL-UL transmission period, a plurality of SL patterns may be configured. For example, when there are an SL period #<NUM> and an SL period #<NUM> within one DL-UL transmission period, an SL pattern #<NUM> indicating the SL period #<NUM> may be configured and an SL pattern #<NUM> indicating the SL period #<NUM> may be configured.

A method of signaling information indicating the DL resources, the UL resources, and the SL resources shown in <FIG> may be configured follows.

<FIG> is a sequence chart illustrating a first exemplary embodiment of a resource configuration information signaling method in a communication system. As shown in <FIG>, a communication system may include a base station and a UE. The base station may be the base station <NUM> shown in <FIG>, and the UE may be one of the UEs <NUM> to <NUM> shown in <FIG>. The base station and the UE may be configured to be the same as or similar to the communication node <NUM> shown in <FIG>. The UE may support the protocol stacks shown in <FIG>.

The base station may be configured to generate TDD-UL-DL-configuration common information (e.g., 'TDD-UL-DL-ConfigCommon') (S800). The TDD-UL-DL-configuration common information may include information indicating a subcarrier spacing and a TDD-UL-DL-pattern #<NUM>. In addition, the TDD-UL-DL-configuration common information may further include a TDD-UL-DL-pattern #<NUM>. The TDD-UL-DL-pattern #<NUM> may be optionally used.

The TDD-UL-DL-pattern #<NUM> may include information indicating a periodicity (e.g., length) of a DL-UL transmission period, a DL pattern described in Table <NUM>, and a UL pattern described in Table <NUM>. Additionally, the TDD-UL-DL-pattern #<NUM> may further include an SL pattern described in Table <NUM>. Some parameters in the SL pattern may be included in the TDD-UL-DL-pattern #<NUM>. For example, (IS-SSLOT and IS-ESLOT), (IS-SSLOT and NS-SLOT) or (IS-ESLOT and NS- SLOT) may be included in TDD-UL-DL-pattern #<NUM>, and at least one of NS-SSYM and NS-ESYM may be further included in TDD-UL-DL-pattern #<NUM> when there are consecutive SL symbols.

When the TDD-UL-DL-configuration common information includes the TDD-UL-DL-pattern #<NUM>, the TDD-UL-DL-pattern #<NUM> may include at least one of a DL pattern described in Table <NUM>, a UL pattern described in Table <NUM>, and an SL pattern described in Table <NUM>. Additionally, the TDD-UL-DL-pattern #<NUM> may further include information indicating a periodicity (e.g., length) of a DL-UL transmission period. The DL pattern, the UL pattern, and the SL pattern included in the TDD-UL-DL-pattern #<NUM> may be different from the DL pattern, the UL pattern, and the SL pattern included in the TDD-UL-DL-pattern #<NUM>, respectively.

When the TDD-UL-DL-configuration common information includes the TDD-UL-DL-pattern #<NUM> and the TDD-UL-DL-pattern #<NUM>, a DL-UL transmission period #<NUM> according to the TDD-UL-DL-pattern #<NUM> and a DL-UL transmission period #<NUM> according to the TDD-UL-DL-pattern #<NUM> may be configured in the time axis. The DL-UL transmission period #<NUM> may be continuous with the DL-UL transmission period #<NUM>. In other words, the (DL-UL transmission period #<NUM> + DL-UL transmission period #<NUM>) may be periodically repeated in the time axis, and the length of (DL-UL transmission period #<NUM> + DL-UL transmission period #<NUM>) may be equal to or less than about <NUM>.

The base station may be configured to transmit system information (e.g., system information block (SIB)) including the TDD-UL-DL-configuration common information (S810). The UE may be configured to receive the system information from the base station, and identify the TDD-UL-DL-configuration common information included in the system information (S820). Accordingly, the UE may be configured to identify the DL-UL transmission period based on the TDD-UL-DL-configuration common information, and identify at least one of the DL resources, the UL resources, and the SL resources within the DL-UL transmission period. In particular, the UE may perform DL communication with the base station using the DL resources, perform UL communication with the base station using the UL resources, and perform SL communication with other UE(s) using the SL resources.

The base station may further be configured to generate TDD-UL-DL-configuration dedicated information (e.g., 'TDD-UL-DL-ConfigDedicated') when necessary (S830). The TDD-UL-DL-configuration dedicated information may be used to reconfigure a FL resource (e.g., FL slot or FL symbol) configured by the TDD-UL-DL-configuration common information to a DL resource (e.g., DL slot or DL symbol), a UL resource (e.g., UL slot or UL symbol) or an SL resource (e.g., SL slot or SL symbol). The TDD-UL-DL-configuration dedicated information may include a slot pattern described in Table <NUM> below. For example, the TDD-UL-DL-configuration dedicated information may include one or more parameters from among the parameters listed in Table <NUM> below.

A slot configured by the TDD-UL-DL-configuration dedicated information may be as follows.

<FIG> is a conceptual diagram illustrating a first exemplary embodiment of a slot configured by TDD-UL-DL-configuration dedicated information in a communication system. As shown in <FIG>, symbols included in one slot may be configured as DL symbols, UL symbols, or SL symbols according to the TDD-UL-DL-configuration dedicated information. In particular, one slot may not include an FL symbol.

<FIG> is a conceptual diagram illustrating a second exemplary embodiment of a slot configured by TDD-UL-DL-configuration dedicated information in a communication system. As shown in <FIG>, symbols included in one slot may be configured as DL symbols, UL symbols, or SL symbols according to the TDD-UL-DL-configuration dedicated information. Among the symbols included in one slot, a symbol that is not configured as a DL symbol, a UL symbol, or an SL symbol may be an FL symbol.

Referring again to <FIG>, the base station may be configured to transmit an RRC message including the TDD-UL-DL-configuration dedicated information to the UE (S840). The RRC message including the TDD-UL-DL-configuration dedicated information may be a cell-specific RRC message or a UE-specific RRC message. The UE may be configured to receive the RRC message from the base station and identify the TDD-UL-DL-configuration dedicated information included in the RRC message (S850). Accordingly, the UE may be configured to identify at least one of the DL resources, the UL resources, and the SL resources configured by the TDD-UL-DL-configuration common information and the TDD-UL-DL-configuration dedicated information. In particular, the UE may perform DL communication with the base station using the DL resources, perform UL communication with the base station using the UL resources, and perform SL communication with other UE(s) using the SL resources.

On the other hand, a resource (e.g., a DL resource, a UL resource, a SL resource) configured by the TDD-UL-DL-configuration common information or the (TDD-UL-DL-configuration common information + TDD-UL-DL-configuration dedicated information) may be reconfigured by a slot format indicator (SFI). For example, an SFI may be used to reconfigure a FL resource configured by the TDD-UL-DL-configuration common information or the (TDD-UL-DL-configuration common information + TDD-UL-DL-configuration dedicated information) to a DL symbol, a UL symbol, or an SL symbol. The SFI may be configured as shown in Table <NUM> below. The SFI may not be limited to examples shown in Table <NUM> below, and may be variously configured. In Table <NUM>, 'D' may indicate a DL symbol, 'U' may indicate a UL symbol, 'S' may indicate an SL symbol, and 'F' may indicate an FL symbol.

The base station may be configured to generate a downlink control information (DCI) including an SFI (S860). The DCI including the SFI may be a DCI format 2_0. The base station may be configured to transmit the DCI including the SFI to the UE through a physical downlink control channel (PDCCH) (S870). The UE may be configured to receive the DCI from the base station and identify the SFI included in the DCI (S880). Accordingly, the UE may be configured to identify one or more of the DL resources, the UL resources, and the SL resources configured by (TDD-UL-DL-configuration common information + DCI) or (TDD-UL-DL-configuration common information + TDD-UL-DL-configuration dedicated information + DCI). In particular, the UE may be configured to perform DL communication with the base station using the DL resources, perform UL communication with the base station using the UL resources, and perform SL communication with other UE(s) using the SL resources.

Meanwhile, UL resources may be used as SL resources in the communication system. In particular, the base station may be configured to transmit to the UE information (hereinafter referred to as an 'SL reconfiguration pattern') that indicates an UL resource used as an SL resource among the UL resources. For example, the base station may be configured to generate TDD-UL-DL-configuration common information including information that indicates a subcarrier spacing and a pattern #<NUM>. The TDD-UL-DL-configuration common information may further include a pattern #<NUM>. Each of the pattern #<NUM> and the pattern #<NUM> may include a DL pattern described in Table <NUM> and a UL pattern described in Table <NUM>. Additionally, each of the pattern #<NUM> and the pattern #<NUM> may further include an SL reconfiguration pattern described in Table <NUM> below. The SL reconfiguration pattern may include one or more of parameters described in Table <NUM> (N'S-SLOT, N'S-SSYM, N'S-ESYM, I'S-SSLOT, I'S-ESLOT).

Therefore, some UL resources among the UL resources belonging to the UL period configured by the UL pattern may be reconfigured to SL resources by the SL reconfiguration pattern. The SL resources reconfigured by the SL reconfiguration pattern may be as follows.

<FIG> is a conceptual diagram illustrating a second exemplary embodiment of a DL-UL transmission period including DL resources, UL resources, and SL resources in a communication system. As shown in <FIG>, a DL-UL transmission period may be configured, and a DL period and a UL period may be configured within the DL-UL transmission period. The DL period may be configured by a DL pattern included in the TDD-UL-DL-configuration common information, and the UL period may be configured by a UL pattern included in the TDD-UL-DL-configuration common information.

Additionally, some UL resources in the UL period may be reconfigured to SL resources by an SL reconfiguration pattern included in the TDD-UL-DL-configuration common information. Thus, when the TDD-UL-DL-configuration common information is received from the base station, the UE may be configured to identify one or more of the DL resources, the UL resources, and the SL resources indicated by the TDD-UL-DL-configuration common information, and perform DL communication, UL communication, or SL communication using the corresponding resources.

Alternatively, the SL reconfiguration pattern may be included in the TDD-UL-DL-configuration dedicated information instead of the TDD-UL-DL-configuration common information. In particular, some UL resources among the UL resources belonging to the UL period configured by the TDD-UL-DL-configuration common information may be reconfigured to SL resources by the SL reconfiguration pattern included in the TDD-UL-DL configuration dedicated information. Therefore, when the TDD-UL-DL-configuration common information and the TDD-UL-DL-configuration dedicated information are received from the base station, the UE may be configured to identify the DL resources and the UL resources indicated by the TDD-UL-DL-configuration common information, and identify the UL resources to be reconfigured to the SL resources by the TDD-UL-DL-configuration dedicated information among the UL resources indicated by the TDD-UL-DL-configuration common information. The UE may be configured to perform DL communication, UL communication, or SL communication using the resources configured by the UL-DL-configuration common information and the UL-DL-configuration dedicated information.

Alternatively, the SL reconfiguration pattern may be included in a DCI instead of the TDD-UL-DL-configuration common information and TDD-UL-DL-configuration dedicated information. In particular, some resources among the UL resources belonging to the UL period configured by the TDD-UL-DL-configuration common information or the (TDD-UL-DL-configuration common information + TDD-UL-DL-configuration dedicated information) may be reconfigured to SL resources by the SL reconfiguration pattern included in the DCI.

Therefore, when the TDD-UL-DL-configuration common information and/or the TDD-UL-DL-configuration dedicated information is received from the base station, the UE may be configured to identify the DL resources or the UL resources indicated by the TDD-UL-DL-configuration common information and/or the TDD-UL-DL-configuration dedicated information. Thereafter, when the DCI including the SL reconfiguration pattern is received from the base station, the UE may be configured to identify the UL resources to be reconfigured by the DCI to the SL resources among the UL resources indicated by the TDD-UL-DL-configuration common information and/or the TDD-UL-DL-configuration dedicated information. The UE may be configured to perform DL communication, UL communication, or SL communication using the resources configured by the (UL-DL-configuration common information + DCI) or the (UL-DL-configuration common information + UL-DL-configuration dedicated information + DCI).

Meanwhile, SL resources may be configured by the UE, and the sidelink communication may be performed using the SL resources configured by the UE.

<FIG> is a sequence chart illustrating a first exemplary embodiment of a sidelink communication method in a communication system. As shown in <FIG>, a communication system may include a UE #<NUM> and a UE #<NUM>. For example, the UE #<NUM> may be the UE <NUM> shown in <FIG> and the UE #<NUM> may be the <NUM> shown in <FIG>. Each of the UE #<NUM> and the UE #<NUM> may be connected to a base station and may be located within coverage of the base station. Alternatively, the UE #<NUM> may be located outside the coverage of the base station. The UE #<NUM> and the UE #<NUM> may be configured to be the same as or similar to the communication node <NUM> shown in <FIG>. The UE #<NUM> and the UE #<NUM> may support the protocol stacks shown in <FIG>.

The UE #<NUM> may reconfigure UL resources configured through at least one of the TDD-UL-DL-configuration common information, the TDD-UL-DL-configuration dedicated information, and the DCI to SL resources (S1200). In addition, the UE #<NUM> may reconfigure FL resources configured through at least one of the TDD-UL-DL-configuration common information, the TDD-UL-DL-configuration dedicated information, and the DCI to SL resources. The UE #<NUM> may be configured to generate a sidelink control information (SCI) including SL resource information that indicates the reconfigured SL resources (S1210). The SL resource information may include one or more of parameters listed in Table <NUM> below.

UL symbols included in a specific slot may be overridden to be SL symbols by the SL resource information as follows.

<FIG> is a conceptual diagram illustrating a first exemplary embodiment of a slot configured by SL resource information in a communication system. As shown in <FIG>, the symbols included in one slot may be configured as DL symbols, UL symbols, or FL symbols by at least one of the UL-DL-configuration common information, the UL-DL-configuration dedicated information, and the DCI. Some UL symbols among the UL symbols included in one slot may be reconfigured to SL symbols by the SL resource information. Here, 'D' may indicate a DL symbol, 'U' may indicate a UL symbol, 'F' may indicate an FL symbol, and 'S' may indicate an SL symbol.

Referring again to <FIG>, the UE #<NUM> may transmit an SCI including the SL resource information to the UE #<NUM> (S1220). The UE #<NUM> may be configured to receive the SCI from the UE #<NUM> and may be configured to identify the SL resource information included in the SCI (S1230). The UE #<NUM> and the UE #<NUM> may be configured to perform the SL communication using the SL resources indicated by the SL resource information included in the SCI (S1240).

The exemplary embodiments of the present disclosure may be implemented as program instructions executable by a variety of computers and recorded on non-transitory a computer readable medium. The non-transitory computer readable medium may include a program instruction, a data file, a data structure, or a combination thereof. The program instructions recorded on the non-transitory computer readable medium may be designed and configured specifically for the present disclosure or can be publicly known and available to those who are skilled in the field of computer software.

Claim 1:
An operation method of a base station (<NUM>) in a communication system (<NUM>), comprising:
configuring, by a processor (<NUM>), downlink, DL, resources, uplink, UL resources, and sidelink, SL resources;
generating, by the processor (<NUM>), time division duplex, TDD,-UL-DL configuration common information, the TDD-UL-DL-configuration common information including information regarding a DL-UL transmission period, a DL pattern indicating the DL resources, a UL pattern indicating the UL resources, and a SL pattern indicating the SL resources, wherein the DL resources, the UL resources, and the SL resources are included in the DL-UL transmission period, and resources other than the DL resources, the UL resources, and the SL resources among all resources included in the DL-UL transmission period are flexible resources;
transmitting, by the processor (<NUM>), to a user equipment, UE, system information including the TDD-UL-DL-configuration common information,
generating, by the processor (<NUM>), TDD-UL-DL-configuration dedicated information including a slot pattern that indicates resources used for the SL communication among the flexible resources configured by the TDD-UL-DL-configuration common information; and
transmitting, by the processor (<NUM>), to the UE a radio resource control, RRC, message including the TDD-UL-DL-configuration dedicated information;
wherein one or more flexible resources among the flexible resources configured by the TDD-UL-DL-configuration common information are overwritten by the TDD-UL-DL-configuration dedicated information to be the resources used for the SL communication, and the TDD-UL-DL-configuration common information is used for configuring the DL-UL transmission period.