WO2020032203A1

WO2020032203A1 - Configurable beam management of sidelink resources

Info

Publication number: WO2020032203A1
Application number: PCT/JP2019/031470
Authority: WO
Inventors: Kazunari Yokomakura; Tatsushi Aiba; Kenneth James Park
Original assignee: Sharp Kabushiki Kaisha
Priority date: 2018-08-09
Filing date: 2019-08-08
Publication date: 2020-02-13

Abstract

A user equipment (UE) is described. The UE includes receiving circuitry configured to receive first information. The UE also includes transmitting circuitry configured to transmit a sidelink channel, wherein the first information includes one or more resource pools for V2X communication, a subcarrier spacing for each of the resource pools, and a number of reference signal resources.

Description

CONFIGURABLE BEAM MANAGEMENT OF SIDELINK RESOURCES

The present disclosure relates generally to communication systems. More specifically, the present disclosure relates to configurable beam management of sidelink resources.

Wireless communication devices have become smaller and more powerful in order to meet consumer needs and to improve portability and convenience. Consumers have become dependent upon wireless communication devices and have come to expect reliable service, expanded areas of coverage and increased functionality. A wireless communication system may provide communication for a number of wireless communication devices, each of which may be serviced by a base station. A base station may be a device that communicates with wireless communication devices.

As wireless communication devices have advanced, improvements in communication capacity, speed, flexibility and/or efficiency have been sought. However, improving communication capacity, speed, flexibility, and/or efficiency may present certain problems.

For example, wireless communication devices may communicate with one or more devices using a communication structure. However, the communication structure used may only offer limited flexibility and/or efficiency. As illustrated by this discussion, systems and methods that improve communication flexibility and/or efficiency may be beneficial.

In one example, a user equipment (UE), comprising: receiving circuitry configured to receive first information; and transmitting circuitry configured to transmit a sidelink channel, wherein the first information includes one or more resource pools for V2X communication, a subcarrier spacing for each of the resource pools, and a number of reference signal resources.

In one example, a base station (gNB), comprising: transmitting circuitry configured to transmit first information; and receiving circuitry configured to receive a sidelink channel, wherein the first information includes one or more resource pools for V2X communication, a subcarrier spacing for each of the resource pools, and a number of reference signal resources.

In one example, a communication method by a user equipment (UE), comprising: receiving first information; and transmitting a sidelink channel, wherein the first information includes one or more resource pools for V2X communication, a subcarrier spacing for each of the resource pools, and a number of reference signal resources.

In one example, a communication method by a base station (gNB), comprising: transmitting first information; and receiving a sidelink channel, wherein the first information includes one or more resource pools for V2X communication, a subcarrier spacing for each of the resource pools, and a number of reference signal resources.

Figure 1 is a block diagram illustrating one implementation of one or more base stations (gNBs) and one or more user equipments (UEs) in which configurable beam management of sidelink resources may be implemented. Figure 2 is an example illustrating architecture enhancements for V2X services. Figure 3 is a flow diagram illustrating a method for enhanced V2X resource selection. Figure 4 illustrates an example of configured beam management for a NR V2X transmission using frequency range 2 (FR2). Figure 5 illustrates an example of configured beam management for a NR V2X transmission using frequency range 1 (FR1). Figure 6 is a diagram illustrating an example of a resource grid for the downlink. Figure 7 is a diagram illustrating one example of a resource grid for the uplink. Figure 8 shows examples of several numerologies. Figure 9 shows examples of subframe structures for the numerologies that are shown in Figure 8. Figure 10 shows examples of slots and sub-slots. Figure 11 shows examples of scheduling timelines. Figure 12 shows examples of DL control channel monitoring regions. Figure 13 shows examples of DL control channel which includes more than one control channel elements. Figure 14 shows examples of UL control channel structures. Figure 15 is a block diagram illustrating one implementation of a gNB. Figure 16 is a block diagram illustrating one implementation of a UE. Figure 17 illustrates various components that may be utilized in a UE. Figure 18 illustrates various components that may be utilized in a gNB. Figure 19 is a block diagram illustrating one implementation of a UE in which configurable beam management of sidelink resources may be implemented. Figure 20 is a block diagram illustrating one implementation of a gNB in which configurable beam management of sidelink resources may be implemented.

A base station (gNB) is also described. The gNB includes transmitting circuitry configured to transmit first information. The gNB also includes receiving circuitry configured to receive a sidelink channel. The first information includes one or more resource pools for V2X communication, a subcarrier spacing for each of the resource pools, and a number of reference signal resources.

A communication method by a UE is also described. The method includes receiving first information. The method also includes transmitting a sidelink channel. The first information includes one or more resource pools for V2X communication, a subcarrier spacing for each of the resource pools, and a number of reference signal resources.

A communication method by a gNB is also described. The method includes transmitting first information. The method also includes receiving a sidelink channel. The first information includes one or more resource pools for V2X communication, a subcarrier spacing for each of the resource pools, and a number of reference signal resources.

The 3rd Generation Partnership Project, also referred to as “3GPP,” is a collaboration agreement that aims to define globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. The 3GPP may define specifications for next generation mobile networks, systems and devices.

3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future requirements. In one aspect, UMTS has been modified to provide support and specification for the Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

At least some aspects of the systems and methods disclosed herein may be described in relation to the 3GPP LTE, LTE-Advanced (LTE-A) and other standards (e.g., 3GPP Releases 8, 9, 10, 11 and/or 12). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be utilized in other types of wireless communication systems.

A wireless communication device may be an electronic device used to communicate voice and/or data to a base station, which in turn may communicate with a network of devices (e.g., public switched telephone network (PSTN), the Internet, etc.). In describing systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, a UE, an access terminal, a subscriber station, a mobile terminal, a remote station, a user terminal, a terminal, a subscriber unit, a mobile device, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, a wireless communication device is typically referred to as a UE. However, as the scope of the present disclosure should not be limited to the 3GPP standards, the terms “UE” and “wireless communication device” may be used interchangeably herein to mean the more general term “wireless communication device.” A UE may also be more generally referred to as a terminal device.

In 3GPP specifications, a base station is typically referred to as a Node B, an evolved Node B (eNB), a home enhanced or evolved Node B (HeNB) or some other similar terminology. As the scope of the disclosure should not be limited to 3GPP standards, the terms “base station,” “Node B,” “eNB,” “gNB” and/or “HeNB” may be used interchangeably herein to mean the more general term “base station.” Furthermore, the term “base station” may be used to denote an access point. An access point may be an electronic device that provides access to a network (e.g., Local Area Network (LAN), the Internet, etc.) for wireless communication devices. The term “communication device” may be used to denote both a wireless communication device and/or a base station. An eNB may also be more generally referred to as a base station device.

It should be noted that as used herein, a “cell” may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP as licensed bands (e.g., frequency bands) to be used for communication between an eNB and a UE. It should also be noted that in E-UTRA and E-UTRAN overall description, as used herein, a “cell” may be defined as “combination of downlink and optionally uplink resources.” The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information transmitted on the downlink resources.

“Configured cells” are those cells of which the UE is aware and is allowed by an eNB to transmit or receive information. “Configured cell(s)” may be serving cell(s). The UE may receive system information and perform the required measurements on all configured cells. “Configured cell(s)” for a radio connection may include a primary cell and/or no, one, or more secondary cell(s). “Activated cells” are those configured cells on which the UE is transmitting and receiving. That is, activated cells are those cells for which the UE monitors the physical downlink control channel (PDCCH) and in the case of a downlink transmission, those cells for which the UE decodes a physical downlink shared channel (PDSCH). “Deactivated cells” are those configured cells that the UE is not monitoring the transmission PDCCH. It should be noted that a “cell” may be described in terms of differing dimensions. For example, a “cell” may have temporal, spatial (e.g., geographical) and frequency characteristics.

Fifth generation (5G) cellular communications (also referred to as “New Radio,” “New Radio Access Technology” or “NR” by 3GPP) envisions the use of time/frequency/space resources to allow for enhanced mobile broadband (eMBB) communication and ultra-reliable low-latency communication (URLLC) services, as well as massive machine type communication (MMTC) like services. A new radio (NR) base station may be referred to as a gNB. A gNB may also be more generally referred to as a base station device.

Various examples of the systems and methods disclosed herein are now described with reference to the Figures, where like reference numbers may indicate functionally similar elements. The systems and methods as generally described and illustrated in the Figures herein could be arranged and designed in a wide variety of different implementations. Thus, the following more detailed description of several implementations, as represented in the Figures, is not intended to limit scope, as claimed, but is merely representative of the systems and methods.

Figure 1 is a block diagram illustrating one implementation of one or more base stations (gNBs) 160 and one or more user equipments (UEs) 102 in which configurable beam management of sidelink resources may be implemented. The one or more UEs 102 communicate with one or more gNBs 160 using one or more antennas 122a-n. For example, a UE 102 transmits electromagnetic signals to the gNB 160 and receives electromagnetic signals from the gNB 160 using the one or more antennas 122a-n. The gNB 160 communicates with the UE 102 using one or more antennas 180a-n.

The UE 102 and the gNB 160 may use one or more channels 119, 121 to communicate with each other. For example, a UE 102 may transmit information or data to the gNB 160 using one or more uplink channels 121. Examples of uplink channels 121 include a PUCCH (Physical Uplink Control Channel) and a PUSCH (Physical Uplink Shared Channel), PRACH (Physical Random Access Channel), etc. For example, uplink channels 121 (e.g., PUSCH) may be used for transmitting UL data (i.e., Transport Block(s), MAC PDU, and/or UL-SCH (Uplink-Shared Channel)).

Here, UL data may include URLLC data. The URLLC data may be UL-SCH data. Here, URLLC-PUSCH (i.e., a different Physical Uplink Shared Channel from PUSCH) may be defined for transmitting the URLLC data. For the sake of simple description, the term “PUSCH” may mean any of (1) only PUSCH (e.g., regular PUSCH, non-URLLC-PUSCH, etc.), (2) PUSCH or URLLC-PUSCH, (3) PUSCH and URLLC-PUSCH, or (4) only URLLC-PUSCH (e.g., not regular PUSCH).

Also, for example, uplink channels 121 may be used for transmitting Hybrid Automatic Repeat Request-ACK (HARQ-ACK), Channel State Information (CSI), and/or Scheduling Request (SR). The HARQ-ACK may include information indicating a positive acknowledgment (ACK) or a negative acknowledgment (NACK) for DL data (i.e., Transport Block(s), Medium Access Control Protocol Data Unit (MAC PDU), and/or DL-SCH (Downlink-Shared Channel)).

The CSI may include information indicating a channel quality of downlink. The SR may be used for requesting UL-SCH (Uplink-Shared Channel) resources for new transmission and/or retransmission. Namely, the SR may be used for requesting UL resources for transmitting UL data.

The one or more gNBs 160 may also transmit information or data to the one or more UEs 102 using one or more downlink channels 119, for instance. Examples of downlink channels 119 include a PDCCH, a PDSCH, etc. Other kinds of channels may be used. The PDCCH may be used for transmitting Downlink Control Information (DCI).

Each of the one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104 and a UE operations module 124. For example, one or more reception and/or transmission paths may be implemented in the UE 102. For convenience, only a single transceiver 118, decoder 108, demodulator 114, encoder 150 and modulator 154 are illustrated in the UE 102, though multiple parallel elements (e.g., transceivers 118, decoders 108, demodulators 114, encoders 150 and modulators 154) may be implemented.

The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. The one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert signals to produce one or more received signals 116. The one or more received signals 116 may be provided to a demodulator 114. The one or more transmitters 158 may transmit signals to the gNB 160 using one or more antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit one or more modulated signals 156.

The demodulator 114 may demodulate the one or more received signals 116 to produce one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode signals. The decoder 108 may produce decoded signals 110, which may include a UE-decoded signal 106 (also referred to as a first UE-decoded signal 106). For example, the first UE-decoded signal 106 may comprise received payload data, which may be stored in a data buffer 104. Another signal included in the decoded signals 110 (also referred to as a second UE-decoded signal 110) may comprise overhead data and/or control data. For example, the second UE-decoded signal 110 may provide data that may be used by the UE operations module 124 to perform one or more operations.

In general, the UE operations module 124 may enable the UE 102 to communicate with the one or more gNBs 160. The UE operations module 124 may include a UE scheduling module 126.

The UE scheduling module 126 may perform configurable beam management of sidelink resources. 3GPP V2X services will be used to transport SAE J2735 Basic Safety Message(s) (BSM). The BSM has two parts: part 1 contains the core data elements (e.g., vehicle size, position, speed, heading acceleration, brake system status), and is transmitted approximately 10 times per second. Part 2 contains a variable set of data elements drawn from many optional data elements, and is transmitted less frequently than part 1. The BSM is expected to have a transmission range of ~1,000 meters, and is tailored for localized broadcast required by V2V safety applications.

In Rel-14 LTE V2X (also known as LTE V2X), a basic set of requirements for V2X service in TR 22.885 is supported, which are considered sufficient for basic road safety service. An LTE V2X enabled vehicle (e.g., a vehicle configured with a UE 102 that supports V2X applications) can directly exchange status information via the PC5 interface. It should be noted that sidelink defines the procedures for realizing a single-hop UE-UE communication, similar to Uplink and Downlink, which define the procedures for UE-base station (BS) and BS-UE access, respectively. Along the same lines, PC5 was introduced as the new direct UE interface, similar to the Uu (UE-BS/BS-UE) interface. Thus, the PC5 interface is also known as sidelink at the physical layer such as position, speed and heading, with other nearby vehicles, infrastructure nodes and/or pedestrians that are also enabled with LTE V2X.

Rel-16 NR provides higher throughput, lower latency and higher reliability as compared to LTE, via a combination of enchantments to protocol numerology, usage of higher frequency bands (e.g., mm Wave Frequencies) and a selection of wider sub carrier spacings (SCS) (e.g., 30kHz, 60kHz, 120kHz, and/or 240kHz, in addition to the 15kHz used by LTE) to match the higher frequency bands, and process for beam management (BM). Rel-16 NR is expected to provide an enhanced V2X service (also referred to as NR V2X) that leverages the higher throughput, lower latency and higher reliability provided by Rel-16 NR data transport services.

Therefore, it is desirable to enable a process in the NR V2X UE 102 that configures the physical layer to transmit different transmission beams, with different SCS, according to the available V2X frequency bands.

In NR, there are roughly two large frequency range specified in 3GPP. One is below 6 GHz (also referred to as sub 6 GHz or FR1). The other is above 6GHz (also referred to as millimeter wave or FR2. Depending on the frequency ranges, the maximum bandwidth and subcarrier spacing varies. In FR1, the maximum bandwidth is 100 MHz and in the FR2 range the maximum bandwidth is 400 MHz. Some subcarrier spacing (e.g., 15kHz and 30kHz) can be used only in FR1 and some subcarrier spacing (e.g., 120kHz and 240kHz) can be used in FR2 only, and some subcarrier spacing (e.g., 60kHz) can be used both in the FR1 and FR2 range.

As mentioned above, two types of frequency ranges are defined in 3GPP. Sub 6 GHz range is called FR1, and millimeter wave range is called FR2. The exact frequency range for FR1 (sub 6 GHz) and FR2 (millimeter wave) may be defined as in Table 1. Table 2 provides examples of NR operating bands in FR1. Table 3 provides examples of NR operating bands in FR2. Table 4 provides applicable synchronization signal (SS) raster entries per operating band (FR1). Table 5 provides applicable SS raster entries per operating band (FR2).

The mmWave frequencies (FR2) offer the availability of very wide bandwidths, which support the high data rates required by NR. However, mmWave links are highly susceptible to rapid channel variations and suffer from severe free-space pathloss and atmospheric absorption. To address these challenges, the NR base stations (gNB) 160 and the NR UE 102 may use highly directional Tx antennas to achieve sufficient link budget in wide area networks. The consequence of the directional Tx antennas is the need to transmit multiple narrow/directional beams. In NR, the concept of beam management is used in high frequency band (e.g., FR2) to configure and coordinate the multiple narrow/directional transmission beams used by the multi-beam based system (e.g., the configuration and coordination of beams used by a directional multi-beam based communication system).

In the LTE specification TS23.285 it is specified that the V2X Control Function is the logical function that is used for network related actions required for V2X, and that the V2X Control Function is used to provision the UE 102 with necessary parameters that enable the UE 102 to use V2X communication. Thus for NR V2X, it is expected that the same type of V2X Control Function will be specified in TS 38.xxx, and that the NR V2X Control Function will determine if the V2X message is to be transported using NR or LTE type transmission resources (i.e., LTE or NR V2X Resource Pools) and if FR1 or FR2 is used, and if FR2 is used if BM and SCS will be assigned to specific beams.

The NR V2X Control Function may enable the NR V2X UE 102 with parameters for using NR or LTE V2X transmission resources (i.e., LTE or NR V2X Resource Pools), and that the NR V2X Control Function may provide an additional set of parameters related to SCS and BM that then enable the NR V2X UE 102 to configure the physical layer to generate a specific set of directional Tx beams, and each directional Tx beam will be assigned an unique index, and each directional Tx beam will be assigned to a specific band in FR2, and each band in FR2 will have a specific SCS.

This disclosure covers aspects of how the UE 102 may be configured which resource to use (NR or LTE) to transport the V2X message over the PC5 communication channel, per the parameters provided by the NR V2X Control Function. This disclosure also covers a process in the NR V2X UE 102 that configures the physical layer with a specific set of directional Tx beam, a unique index for each directional Tx beam and specific band in FR2 for each Tx beam, and specific SCS for each band in FR2. Figure 2 illustrates architecture enhancements for V2X services.

This disclosure look to enhance the NR V2X resource selection capabilities of a Rel-16 NR UE to include a process that configures the physical layer of the UE 102 to use a specific set of directional Tx beams, a unique index for each directional Tx beam, and specific band in FR2 for each directional Tx beam, and specific SCS for each band in FR2, if the UE 102 receives System Information message (SI) that contains FR2 type information, and if that FR2 type information also contains BM and SCS configuration information. If the UE 102 receives an SI message that contains FR1 type information, then the physical layer is configured to use FR1 type V2X resources and does not configure the physical layer for BM and SCS.

This disclosure defines the BM and SCS configuration data that is used by the NR V2X resource selection process (e.g. a table of data). Additionally, this disclosure provides a method of transport of the BM and SCS configuration data via a reuse of, and enhancement to, the content of IE SL-CommTxPoolSensingConfig-14, and transport of the enhanced SL-CommTxPoolSensingConfig-14 in a new NR SIB. Alternately the enhanced SL-CommTxPoolSensingConfig-14 may be transported in a RRC Reconfiguration message.

This disclosure discusses a NR V2X UE that is transmitting a V2X message to a NR V2X UE 102. However, it is understood that the systems and methods of this disclosure can also be applied to the receiving NR V2X UE 102 for the purpose of selecting resources to reply to the received V2X message.

Since Rel-14, LTE has been capable of LTE V2X sidelink communications, whereby the EPC configures, and the E-UTRAN broadcasts, LTE V2X sidelink communications configuration information in SIB21 for use by LTE UEs 102 that provide LTE V2X services. SIB21 uses many of the same Information Elements as SIB18 and SIB19. SIB 18 and SIB19 were first implemented in Rel-12 in support of Device to Device (D2D) Communications and Discovery parameters respectively. SIB21 contains an Information Element (IE) know as SL-CommTxPoolSensingConfig-14. This IE may be used to specify UE autonomous resource selection for LTE V2X sidelink communication when the UE is in IDLE mode or CONNECTED mode.

Starting with Rel-16, NR is expected to be capable of supporting enhanced V2X sidelink communications for use by 5G UEs 102 that provide 5G V2X services using 5G resources.

This disclosure provides enhancements to the V2X resource selection capabilities of a Rel-16 NR UE 102 to include a new process that takes as input from the network BM and SCS configuration data related to: parameters for configuring a set of directional Tx beams; a unique index for addressing each directional Tx beam in the set; assignment of a specific band in FR2 for each directional Tx beam in the set; and/or assignment of a specific SCS for each band in FR2.

This disclosure also provides enhancements to the V2X resource selection capabilities of a Rel-16 NR UE 102 to include a new process that is capable of configuring the physical layer of the UE 102 to use a specific set of directional Tx beams, a unique index for each directional Tx beam, and specific band in FR2 for each directional Tx beam, and specific SCS for each band in FR2.

This disclosure also defines a procedure in the new process that, if the UE 102 receives a System Information message (SI) that contains FR2 type information, and if that FR2 type information also contains BM and SCS configuration information, then the process will configure the physical layer per the BM and SCS information. For example, it may be that Beam1 will use a SCS of 120 KHz, Beam2 will use a SCS of 15 KHz, Beam3 will use a SCS of 60 KHz, etc.

Furthermore, this disclosure also defines a procedure in the new process that, if the UE 102 receives System Information message (SI) that contains FR1 type information, then the physical layer is configured to use FR1 type V2X resources and does not configure the physical layer for BM and SCS.

To provide the enhancement for the V2X resource selection capabilities, a process (also referred to as NR_V2X_Beam) is defined that determines, based on the FR1 or FR2 configured by the network, if the physical layer will be further configured to use directional Tx beams and associated SCS, or not. Figure 3 illustrates an example of this process. Figure 4 illustrates an example of configured beam management for a NR V2X transmission using FR2. Figure 5 illustrates an example of configured beam management for a NR V2X transmission using FR1.

An example in Listing 1 describes what the NR V2X UE may do upon reception of a SIBx-NR-V2X.

Configuration data may be provided into the NR_V2X_Beam process via a reuse and enhancement to the autonomous resource selection content of IE SL-CommTxPoolSensingConfig-14. In addition, the Rel-14 SIB21 may be reused to transport SL-CommTxPoolSensingConfig-14.

The IE in that carries information regarding UE autonomous resource selection may be carried in some as yet to be defined IE. This IE may be referred to as CommTxPoolSensingConfig-16.

The SIB in that carries IE CommTxPoolSensingConfig-16 is also yet to be defined. This SIB may be referred to as “SIBx-NR-V2X”.

One enhancement to CommTxPoolSensingConfig-16 is the inclusion of new configuration elements for defining a beam management and SCS assignments for FR2.

The beam management elements may be captured in the sl-BeamManagement information element, which contains: the assignment of SCS to each beam to be generated; the assignment of FR2 frequencies to each beam to be generated; and/or some additional info.

It should be noted that the sl-BeamManagement may be sent to the UE 102 as part of an RRC_Reconfiguration message, and the UE 102 will use that data instead of the data sent in the SIBx-NR-V2X message until the UE 102 receives a new SIBx-NR-V2X from a different gNB 160. Sl-BeamInfoTBD may include the maximum number of reference signals for sidelink communication and/or synchronization signals for slidelink communication.

An example of what the SL-CommTxPoolSensingConfig-r16 with the addition of sl-BeamManagement is provided in Listing 2.

As another example, SL-CommTxPoolSensingConfig-r16 may include subcarrier spacing (sl-SCS) for each sidelink transmission pool. SL-CommTxPoolSensingConfig-r16 may be defined as illustrated in Listing 3.

As described above, the UE 102 may perform the sidelink communication by using LTE type resources (LTE resources), NR type resources (NR resources), or LTE and NR type resources (LTE and NR resources). For example, the UE 102 may switch the resources used for the sidelink communication, based on the conditions (e.g., the conditions configured by the gNB 160).

Here, in a case that LTE resources (e.g., LTE resource pools) are used, the UE 102 may receive, based on a parameter (e.g., v2x-RxPool-LTE), the sidelink communication (e.g., the sidelink communication monitoring). Also, in a case that LTE resources (e.g., LTE resource pools) are used, the UE 102 may transmit, based on a parameter (e.g., v2x-TxPool-LTE), the sidelink communications. For example, if the UE 102 is configured to receive the sidelink communication, the UE 102 may use the LTE resources based on the parameter (e.g., v2x-RxPool-LTE). Also, if the UE 102 is configured to transmit the sidelink communication, the UE 102 may use the LTE resources based on the parameter (e.g., v2x-TxPool-LTE).

Also, in a case that NR resources (e.g., NR resource pools) are used, the UE 102 may receive, based on a parameter (e.g., v2x-RxPool-NR), the sidelink communication (e.g., the sidelink communication monitoring). Also, in a case that NR resources (e.g., NR resource pools) are used, the UE 102 may transmit, based on a parameter (e.g., v2x-TxPool-NR), the sidelink communications. For example, if the UE 102 is configured to receive the sidelink communication, the UE 102 may use the NR resources based on the parameter (e.g., v2x-RxPool-NR). Also, if the UE 102 is configured to transmit the sidelink communication, the UE 102 may use the NR resources based on the parameter (e.g., v2x-TxPool-NR).

Also, in a case that LTE and/or NR resources (e.g., LTE resource pools and/or NR resource pools) are used, the UE 102 may receive, based on a parameter (e.g., v2x-RxPool-LTE and/or v2x-RxPool-NR), the sidelink communication (e.g., the sidelink communication monitoring), as described above. Also, in a case that LTE and/or NR resources (e.g., LTE resource pools and/or NR resource pools) are used, the UE 102 may transmit, based on a parameter (e.g., v2x-TxPool-LTE, and/or v2x-TxPool-NR), the sidelink communications, as described above. For example, if the UE 102 is configured to receive the sidelink communication, the UE 102 may use LTE and/or NR resources based on the parameter (e.g., v2x-RxPool-LTE, and/or v2x-RxPool-NR). Also, if the UE 102 is configured to transmit the sidelink communication, the UE 102 may use LTE and/or NR resources based on the parameter (e.g., v2x-TxPool-LTE, and/or v2x-TxPool-NR).

Namely, the parameters “v2x-TxPool-LTE”, and/or “v2x-TxPool-NR” may be used for indicating the resources by which the UE 102 is allowed to transmit the sidelink communication. Also, the parameters “v2x-RxPool-LTE”, and/or “v2x-RxPool-NR” may be used for indicating the resources by which the UE 102 is allowed to receive the sidelink communication. Here, the maximum number of resource pools for “v2x-TxPool-LTE”, “v2x-TxPool-NR”, “v2x-RxPool-LTE”, and/or “v2x-RxPool-NR” may be independently defined (e.g., configured). Namely, the different maximum number of pools for LTE resources (e.g., transmission pools and/or reception pools) and/or NR resources (e.g., transmission pools and/or reception pools) may be defined. Also, LTE resources (e.g., transmission pools and/or reception pools) indicated by the parameters and NR resources (e.g., transmission pools and/or reception pools) indicated by the parameters may be overlapped.

Namely, for example, SIB “SIBx-NR-V2X” may include the parameters for resources (e.g., LTE resources (e.g., v2x-RxPool-LTE, v2x-TxPool-LTE)) used for the sidelink communication. Also, SIB “SIBx-NR-V2X” may include the parameters for resources (e.g., NR resources (e.g., v2x-RxPool-NR, v2x-TxPool-NR)) used for the sidelink communication.

Here, in a case that the parameter(s) for NR resources (e.g., v2x-RxPool-NR, v2x-TxPool-NR) is configured, the gNB 160 may further configure a parameter(s) used for the sidelink communication.

For example, the parameter(s) further configured by the gNB 160 may include: configuration for a block comprising, at least, a primary sidelink synchronization signal (PSSS), a secondary sidelink synchronization signal (SSSS), a physical broadcast channel (PBCH), and/or a demodulation reference signal (DM-RS) associated with the PBCH. The PBCH for sidelink may be called a physical broadcast sidelink channel (PSBCH).

An example of the SIB “SIBx-NR-V2X” is provided in Listing 4. The IE SystemInformationBlockTypeX-NR-V2X may include V2X sidelink communication configuration.

In Listing “SL-CommRxPoolListV2X-LTE”, “SL-CommTxPoolListV2X-LTE”, “SL-CommRxPoolListV2X-NR”, and “SL-CommTxPoolListV2X-NR”, may respectively include, for example, one or more of the following: a parameter(s) used for identifying an identification for the resources (e.g., the resource pool(s)) for the sidelink transmission; a parameter(s) used for indicating a periodicity for the side link transmission; a parameter(s) used for indicating an offset value for the sidelink transmission; a parameter(s) used for indicating a position of the resources (e.g., the resource pool(s)) for the sidelink transmission; a parameter(s) used for indicating TDD configuration associated with the sidelink transmission.

An example of the “SL-CommConfig” is provided in Listing 5.

In Listing 5, a parameter(s) “ssb-PositionsInBurst” may be used for indicating the time domain position(s) of the SSSB. For example, a parameter “shortBitmap” may be used for the sidelink transmission on sub 3 GHz (i.e., a frequency band(s) of sub 3 GHz). Also, a parameter “mediumBitmap” may be used for the sidelink transmission on 3-6 GHz (i.e., a frequency band(s) of 3-6 GHz). Also, a parameter “longBitmap” may be used for the sidelink transmission on above 6 GHz (i.e., a frequency band(s) of above 6 GHz). Also, a parameter(s) “ssb-periodicityServingCell” may be used for indicating periodicity of the SSSB. Also, a parameter(s) “subcarrierSpacing” may be used for indicating the SCS(s) (subcarrier spacing(s)) (e.g., the numerology) of the SSSB. Also, a parameter(s) “ss-PBCH-BlockPower” may be used for determining Tx power used for the SSSB transmission.

In the above examples, the number of Tx beams may be defined by the number of reference signal resources, e.g. CSI-RS (channel state information reference signal), physical sidelink synchronization signal, SSSB, etc. In the above examples, the subcarrier spacing and/or the number of reference signal resources may be indicated/defined per V2X resource pool. The number of reference signal resources may be different dependent on the frequency band. The number of reference signal resources may be defined as the maximum number of reference signals.

In the above examples, subcarrier spacing may be indicated separately for each channel or signal (e.g., SSSB, control channel (physical sidelink control channel (PSCCH), or shared channel (physical sidelink shared channel (PSSCH)). For example, SCS#1, SCS#2, and SCS#3 may be indicated for SSSB, PSCCH, and PSSCH, respectively. As another example, the indicated SCS is used for PSCCH and/or PSSCH.

The UE operations module 124 may provide information 148 to the one or more receivers 120. For example, the UE operations module 124 may inform the receiver(s) 120 when to receive retransmissions.

The UE operations module 124 may provide information 138 to the demodulator 114. For example, the UE operations module 124 may inform the demodulator 114 of a modulation pattern anticipated for transmissions from the gNB 160.

The UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of an anticipated encoding for transmissions from the gNB 160.

The UE operations module 124 may provide information 142 to the encoder 150. The information 142 may include data to be encoded and/or instructions for encoding. For example, the UE operations module 124 may instruct the encoder 150 to encode transmission data 146 and/or other information 142. The other information 142 may include PDSCH HARQ-ACK information.

The encoder 150 may encode transmission data 146 and/or other information 142 provided by the UE operations module 124. For example, encoding the data 146 and/or other information 142 may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide encoded data 152 to the modulator 154.

The UE operations module 124 may provide information 144 to the modulator 154. For example, the UE operations module 124 may inform the modulator 154 of a modulation type (e.g., constellation mapping) to be used for transmissions to the gNB 160. The modulator 154 may modulate the encoded data 152 to provide one or more modulated signals 156 to the one or more transmitters 158.

The UE operations module 124 may provide information 140 to the one or more transmitters 158. This information 140 may include instructions for the one or more transmitters 158. For example, the UE operations module 124 may instruct the one or more transmitters 158 when to transmit a signal to the gNB 160. For instance, the one or more transmitters 158 may transmit during a UL subframe. The one or more transmitters 158 may upconvert and transmit the modulated signal(s) 156 to one or more gNBs 160.

Each of the one or more gNBs 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162 and a gNB operations module 182. For example, one or more reception and/or transmission paths may be implemented in a gNB 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109 and modulator 113 are illustrated in the gNB 160, though multiple parallel elements (e.g., transceivers 176, decoders 166, demodulators 172, encoders 109 and modulators 113) may be implemented.

The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. The one or more receivers 178 may receive signals from the UE 102 using one or more antennas 180a-n. For example, the receiver 178 may receive and downconvert signals to produce one or more received signals 174. The one or more received signals 174 may be provided to a demodulator 172. The one or more transmitters 117 may transmit signals to the UE 102 using one or more antennas 180a-n. For example, the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.

The demodulator 172 may demodulate the one or more received signals 174 to produce one or more demodulated signals 170. The one or more demodulated signals 170 may be provided to the decoder 166. The gNB 160 may use the decoder 166 to decode signals. The decoder 166 may produce one or more decoded signals 164, 168. For example, a first eNB-decoded signal 164 may comprise received payload data, which may be stored in a data buffer 162. A second eNB-decoded signal 168 may comprise overhead data and/or control data. For example, the second eNB-decoded signal 168 may provide data (e.g., PDSCH HARQ-ACK information) that may be used by the gNB operations module 182 to perform one or more operations.

In general, the gNB operations module 182 may enable the gNB 160 to communicate with the one or more UEs 102. The gNB operations module 182 may include a gNB scheduling module 194. The gNB scheduling module 194 may perform operations for configurable beam management of sidelink resources as described herein.

The gNB operations module 182 may provide information 188 to the demodulator 172. For example, the gNB operations module 182 may inform the demodulator 172 of a modulation pattern anticipated for transmissions from the UE(s) 102.

The gNB operations module 182 may provide information 186 to the decoder 166. For example, the gNB operations module 182 may inform the decoder 166 of an anticipated encoding for transmissions from the UE(s) 102.

The gNB operations module 182 may provide information 101 to the encoder 109. The information 101 may include data to be encoded and/or instructions for encoding. For example, the gNB operations module 182 may instruct the encoder 109 to encode information 101, including transmission data 105.

The encoder 109 may encode transmission data 105 and/or other information included in the information 101 provided by the gNB operations module 182. For example, encoding the data 105 and/or other information included in the information 101 may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder 109 may provide encoded data 111 to the modulator 113. The transmission data 105 may include network data to be relayed to the UE 102.

The gNB operations module 182 may provide information 103 to the modulator 113. This information 103 may include instructions for the modulator 113. For example, the gNB operations module 182 may inform the modulator 113 of a modulation type (e.g., constellation mapping) to be used for transmissions to the UE(s) 102. The modulator 113 may modulate the encoded data 111 to provide one or more modulated signals 115 to the one or more transmitters 117.

The gNB operations module 182 may provide information 192 to the one or more transmitters 117. This information 192 may include instructions for the one or more transmitters 117. For example, the gNB operations module 182 may instruct the one or more transmitters 117 when to (or when not to) transmit a signal to the UE(s) 102. The one or more transmitters 117 may upconvert and transmit the modulated signal(s) 115 to one or more UEs 102.

It should be noted that a DL subframe may be transmitted from the gNB 160 to one or more UEs 102 and that a UL subframe may be transmitted from one or more UEs 102 to the gNB 160. Furthermore, both the gNB 160 and the one or more UEs 102 may transmit data in a standard special subframe.

It should also be noted that one or more of the elements or parts thereof included in the eNB(s) 160 and UE(s) 102 may be implemented in hardware. For example, one or more of these elements or parts thereof may be implemented as a chip, circuitry or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc.

URLLC may coexist with other services (e.g., eMBB). Due to the latency requirement, URLLC may have a highest priority in some approaches. Some examples of URLLC coexistence with other services are given herein (e.g., in one or more of the following Figure descriptions).

Figure 2 is an example illustrating architecture enhancements for V2X services. In Figure 2, V2 is the reference point between the V2X application server and the V2X control function in the operator's network. The V2X application server may connect to V2X control functions belonging to multiple PLMNs.

V3 is the reference point between the UE and the V2X control function in UE's home PLMN. V3 is based on the service authorization and provisioning part of the PC3 reference point defined in clause 5.2 of TS 23.303 [5]. It is applicable to both PC5 and LTE-Uu based V2X communication and optionally MBMS and LTE-Uu based V2X communication.

V4 is the reference point between the HSS and the V2X control function in the operator's network.

V6 is the reference point between the V2X control function in the HPLMN and the V2X control function in the VPLMN.

PC5 is the reference point between the UEs used for user plane for ProSe direct communication for V2X service.

In addition to the relevant functions defined in TS 23.401 [6] for S6a, in case of V2X Service, S6a is used to download V2X service related subscription information to MME during E-UTRAN attach procedure or to inform MME subscription information in the HSS has changed.

In addition to the relevant functions defined in TS 23.401 [6] for S1-MME, in case of V2X service, S1-MME is also used to convey the V2X service authorization from MME to eNodeB or gNB.

xMB is the reference point between the V2X application server (e.g. content provider) and the BM-SC, and may be defined as in TS 26.346 [11].

MB2 is the reference point between the V2X application server and the BM-SC, and may be defined as in TS 23.468 [7].

The SGmb/SGi-mb/M1/M3 reference points are internal to the MBMS system and are defined in TS 23.246 [8].

LTE-Uu is the reference point between the UE and the E-UTRAN.

Figure 3 is a flow diagram illustrating a method 300 for enhanced V2X resource selection. A UE 102 may determine 302 if it receives SI with FR1 type information. If the UE 102 receives SI with FR1 type information, then the UE 102 may perform 312 SL using FR1 type SL resources.

If the UE 102 does not receive SI with FR1 type information, then the UE 102 may determine 304 whether it receives SI with FR2 type information. If the UE 102 does not receive SI with FR2 type information, then the method 300 ends. If the UE 102 receives SI with FR2 type information, then the UE 102 may determine 306 whether the FR2 type information includes BM and SCS configurations.

If the FR2 type information does not include BM and SCS configurations, then the UE 102 may perform 310 SL using FR2 type SL resources. If the FR2 type information does include BM and SCS configurations, then the UE 102 may perform 308 SL using FR2 type SL resources that include beam and FR2 and SCS specific assignments.

Figure 4 illustrates an example of configured beam management for a NR V2X transmission using FR2. A transmitting terminal #1 may have a multi-type antenna. The transmitting terminal #1 may use FR1 or FR2. The transmitting terminal #1 may be configured according to Rel-16.

The transmitting terminal #1 may transmit a number of beams. For example, a first beam (Beam₁) may be transmitted at 120kHz SCS. A second beam (Beam₂) may be transmitted at 240kHz SCS. A third beam (Beam₃) may be transmitted at 60kHz SCS, and so forth.

A receiving terminal #2 may be configured according to Rel-16. In this example, the receiving terminal #2 may receive the third beam (Beam₃).

Figure 5 illustrates an example of configured beam management for a NR V2X transmission using FR1. A transmitting terminal #3 may have a single-type antenna. The transmitting terminal #3 may use FR1 The transmitting terminal #3 may be configured according to Rel-16. The transmitting terminal #3 may transmit a single beam at 15kHz SCS.

A receiving terminal #4 may be configured according to Rel-16, Rel-5 or Rel-14. In this example, the receiving terminal #2 may receive the beam transmitted from transmitting terminal #3.

Figure 6 is a diagram illustrating one example of a resource grid for the downlink. The resource grid illustrated in Figure 6 may be utilized in some implementations of the systems and methods disclosed herein. More detail regarding the resource grid is given in connection with Figure 1.

In Figure 6, one downlink subframe 769 may include two downlink slots 783. N^DL _RB is downlink bandwidth configuration of the serving cell, expressed in multiples of N^RB _sc, where N^RB _sc is a resource block 789 size in the frequency domain expressed as a number of subcarriers, and N^DL _symb is the number of OFDM symbols 787 in a downlink slot 783. A resource block 789 may include a number of resource elements (RE) 791.

In the downlink, the OFDM access scheme with cyclic prefix (CP) may be employed, which may be also referred to as CP-OFDM. In the downlink, PDCCH, enhanced PDCCH (EPDCCH), PDSCH and the like may be transmitted. A downlink radio frame may include multiple pairs of downlink resource blocks (RBs) which is also referred to as physical resource blocks (PRBs). The downlink RB pair is a unit for assigning downlink radio resources, defined by a predetermined bandwidth (RB bandwidth) and a time slot. The downlink RB pair includes two downlink RBs that are continuous in the time domain.

The downlink RB includes twelve sub-carriers in frequency domain. The downlink slot includes fourteen (for normal CP) or twelve (for extended CP) OFDM symbols in time domain. A region defined by one sub-carrier in frequency domain and one OFDM symbol in time domain is referred to as a resource element (RE) and is uniquely identified by the index pair (k,l) in a slot, where k and l are indices in the frequency and time domains, respectively. While downlink subframes in one component carrier (CC) are discussed herein, downlink subframes are defined for each CC and downlink subframes are substantially in synchronization with each other among CCs.

Figure 7 is a diagram illustrating one example of a resource grid for the uplink. The resource grid illustrated in Figure 7 may be utilized in some implementations of the systems and methods disclosed herein. More detail regarding the resource grid is given in connection with Figure 1.

In Figure 7, one uplink subframe 869 may include two uplink slots 883. N^UL _RB is uplink bandwidth configuration of the serving cell, expressed in multiples of N^RB _sc, where N^RB _sc is a resource block 889 size in the frequency domain expressed as a number of subcarriers, and N^UL _symb is the number of SC-FDMA symbols 893 in an uplink slot 883. A resource block 889 may include a number of resource elements (RE) 891.

For a PCell, N^UL _RB is broadcast as a part of system information. For an SCell (including an LAA SCell), N^UL _RB is configured by a RRC message dedicated to a UE 102.

In the uplink, in addition to CP-OFDM, a Single-Carrier Frequency Division Multiple Access (SC-FDMA) access scheme may be employed, which is also referred to as Discrete Fourier Transform-Spreading OFDM (DFT-S-OFDM). In the uplink, PUCCH, PUSCH, PRACH and the like may be transmitted. An uplink radio frame may include multiple pairs of uplink resource blocks. The uplink RB pair is a unit for assigning uplink radio resources, defined by a predetermined bandwidth (RB bandwidth) and a time slot. The uplink RB pair includes two uplink RBs that are continuous in the time domain.

The uplink RB may include twelve sub-carriers in frequency domain. The uplink slot includes fourteen (for normal CP) or twelve (for extended CP) OFDM/DFT-S-OFDM symbols in time domain. A region defined by one sub-carrier in the frequency domain and one OFDM/DFT-S-OFDM symbol in the time domain is referred to as a RE and is uniquely identified by the index pair (k,l) in a slot, where k and l are indices in the frequency and time domains respectively. While uplink subframes in one component carrier (CC) are discussed herein, uplink subframes are defined for each CC.

Figure 8 shows examples of several numerologies 901. The numerology #1 901a may be a basic numerology (e.g., a reference numerology). For example, a RE 995a of the basic numerology 901a may be defined with subcarrier spacing 905a of 15 kHz in frequency domain and 2048Ts + CP length (e.g., 160Ts or 144Ts) in time domain (i.e., symbol length #1 903a), where Ts denotes a baseband sampling time unit defined as 1/(15000*2048) seconds. For the i-th numerology, the subcarrier spacing 905 may be equal to 15*2ⁱ and the effective OFDM symbol length 2048*2^-i*Ts. It may cause the symbol length is 2048*2^-i *Ts + CP length (e.g., 160*2^-i *Ts or 144*2^-i *Ts). In other words, the subcarrier spacing of the i+1-th numerology is a double of the one for the i-th numerology, and the symbol length of the i+1-th numerology is a half of the one for the i-th numerology. Figure 8 shows four numerologies, but the system may support another number of numerologies. Furthermore, the system does not have to support all of the 0-th to the I-th numerologies, i=0, 1, …, I.

For example, the first UL transmission on the first SPS resource as above mentioned may be performed only on the numerology #1 (e.g., a subcarrier spacing of 15 kHz). Here, the UE 102 may acquire (detect) the numerology #1 based on a synchronization signal. Also, the UE 102 may receive a dedicated RRC signal including information (e.g., a handover command) configuring the numerology #1. The dedicated RRC signal may be a UE-specific signal. Here, the first UL transmission on the first SPS resource may be performed on the numerology #1, the numerology #2 (a subcarrier spacing of 30 kHz), and/or the numerology #3 (a subcarrier spacing of 60 kHz).

Also, the second UL transmission on the second SPS resource as above mentioned may be performed only on the numerology #3. Here, for example, the UE 102 may receive System Information (e.g., Master Information Block (MIB) and/or System Information Block (SIB)) including information configuring the numerology #2 and/or the numerology #3.

Also, the UE 102 may receive the dedicated RRC signal including information (e.g., the handover command) configuring the numerology #2 and/or the numerology #3. The System Information (e.g., MIB) may be transmitted on BCH (Broadcast Channel) and/or the dedicated RRC signal. The System Information (e.g., SIB) may contain information relevant when evaluating if a UE 102 is allowed to access a cell and/or defines the scheduling of other system information. The System Information (SIB) may contain radio resource configuration information that is common for multiple UEs 102. Namely, the dedicated RRC signal may include each of multiple numerology configurations (the first numerology, the second numerology, and/or the third numerology) for each of UL transmissions (e.g., each of UL-SCH transmissions, each of PUSCH transmissions). Also, the dedicated RRC signal may include each of multiple numerology configurations (the first numerology, the second numerology, and/or the third numerology) for each of DL transmissions (each of PDCCH transmissions).

Figure 9 shows examples of subframe structures for the numerologies 1001 that are shown in Figure 8. Given that a slot 1083 includes N^DL _symb (or N^UL _symb) = 7 symbols, the slot length of the i+1-th numerology 1001 is a half of the one for the i-th numerology 1001, and eventually the number of slots 1083 in a subframe (i.e., 1 ms) becomes double. It may be noted that a radio frame may include 10 subframes, and the radio frame length may be equal to 10 ms.

Figure 10 shows examples of slots 1183 and sub-slots 1107. If a sub-slot 1107 is not configured by higher layer, the UE 102 and the eNB/gNB 160 may only use a slot 1183 as a scheduling unit. More specifically, a given transport block may be allocated to a slot 1183. If the sub-slot 1107 is configured by higher layer, the UE 102 and the eNB/gNB 160 may use the sub-slot 1107 as well as the slot 1183. The sub-slot 1107 may include one or more OFDM symbols. The maximum number of OFDM symbols that constitute the sub-slot 1107 may be N^DL _symb-1 (or N^UL _symb-1).

The sub-slot length may be configured by higher layer signaling. Alternatively, the sub-slot length may be indicated by a physical layer control channel (e.g., by DCI format).

The sub-slot 1107 may start at any symbol within a slot 1183 unless it collides with a control channel. There could be restrictions of mini-slot length based on restrictions on starting position. For example, the sub-slot 1107 with the length of N^DL _symb-1 (or N^UL _symb-1) may start at the second symbol in a slot 1183. The starting position of a sub-slot 1107 may be indicated by a physical layer control channel (e.g., by DCI format). Alternatively, the starting position of a sub-slot 1107 may be derived from information (e.g., search space index, blind decoding candidate index, frequency and/or time resource indices, PRB index, a control channel element index, control channel element aggregation level, an antenna port index, etc.) of the physical layer control channel which schedules the data in the concerned sub-slot 1107.

In cases when the sub-slot 1107 is configured, a given transport block may be allocated to either a slot 1183, a sub-slot 1107, aggregated sub-slots 1107 or aggregated sub-slot(s) 1107 and slot 1183. This unit may also be a unit for HARQ-ACK bit generation.

Figure 11 shows examples of scheduling timelines 1209. For a normal DL scheduling timeline 1209a, DL control channels are mapped the initial part of a slot 1283a. The DL control channels 1211 schedule DL shared channels 1213a in the same slot 1283a. HARQ-ACKs for the DL shared channels 1213a (i.e., HARQ-ACKs each of which indicates whether or not transport block in each DL shared channel 1213a is detected successfully) are reported via UL control channels 1215a in a later slot 1283b. In this instance, a given slot 1283 may contain either one of DL transmission and UL transmission.

For a normal UL scheduling timeline 1209b, DL control channels 1211b are mapped the initial part of a slot 1283c. The DL control channels 1211b schedule UL shared channels 1217a in a later slot 1283d. For these cases, the association timing (time shift) between the DL slot 1283c and the UL slot 1283d may be fixed or configured by higher layer signaling. Alternatively, it may be indicated by a physical layer control channel (e.g., the DL assignment DCI format, the UL grant DCI format, or another DCI format such as UE-common signaling DCI format which may be monitored in common search space).

For a self-contained base DL scheduling timeline 1209c, DL control channels 1211c are mapped to the initial part of a slot 1283e. The DL control channels 1211c schedule DL shared channels 1213b in the same slot 1283e. HARQ-ACKs for the DL shared channels 1213b are reported in UL control channels 1215b, which are mapped at the ending part of the slot 1283e.

For a self-contained base UL scheduling timeline 1209d, DL control channels 1211d are mapped to the initial part of a slot 1283f. The DL control channels 1211d schedule UL shared channels 1217b in the same slot 1283f. For these cases, the slot 1283f may contain DL and UL portions, and there may be a guard period between the DL and UL transmissions.

The use of a self-contained slot may be upon a configuration of self-contained slot. Alternatively, the use of a self-contained slot may be upon a configuration of the sub-slot. Yet alternatively, the use of a self-contained slot may be upon a configuration of shortened physical channel (e.g., PDSCH, PUSCH, PUCCH, etc.).

Figure 12 shows examples of DL control channel monitoring regions. One or more sets of PRB(s) may be configured for DL control channel monitoring. In other words, a control resource set is, in the frequency domain, a set of PRBs within which the UE 102 attempts to blindly decode downlink control information, where the PRBs may or may not be frequency contiguous, a UE 102 may have one or more control resource sets, and one DCI message may be located within one control resource set. In the frequency-domain, a PRB is the resource unit size (which may or may not include Demodulation reference signals (DM-RS)) for a control channel. A DL shared channel may start at a later OFDM symbol than the one(s) which carries the detected DL control channel. Alternatively, the DL shared channel may start at (or earlier than) an OFDM symbol than the last OFDM symbol which carries the detected DL control channel. In other words, dynamic reuse of at least part of resources in the control resource sets for data for the same or a different UE 102, at least in the frequency domain may be supported.

Figure 13 shows examples of DL control channel which includes more than one control channel elements. When the control resource set spans multiple OFDM symbols, a control channel candidate may be mapped to multiple OFDM symbols or may be mapped to a single OFDM symbol. One DL control channel element may be mapped on REs defined by a single PRB and a single OFDM symbol. If more than one DL control channel elements are used for a single DL control channel transmission, DL control channel element aggregation may be performed.

The number of aggregated DL control channel elements is referred to as DL control channel element aggregation level. The DL control channel element aggregation level may be 1 or 2 to the power of an integer. The gNB 160 may inform a UE 102 of which control channel candidates are mapped to each subset of OFDM symbols in the control resource set. If one DL control channel is mapped to a single OFDM symbol and does not span multiple OFDM symbols, the DL control channel element aggregation is performed within an OFDM symbol, namely multiple DL control channel elements within an OFDM symbol are aggregated. Otherwise, DL control channel elements in different OFDM symbols can be aggregated.

Figure 14 shows examples of UL control channel structures. UL control channel may be mapped on REs which are defined a PRB and a slot in frequency and time domains, respectively. This UL control channel may be referred to as a long format (or just the 1st format). UL control channels may be mapped on REs on a limited OFDM symbols in time domain. This may be referred to as a short format (or just the 2nd format). The UL control channels with a short format may be mapped on REs within a single PRB. Alternatively, the UL control channels with a short format may be mapped on REs within multiple PRBs. For example, interlaced mapping may be applied, namely the UL control channel may be mapped to every N PRBs (e.g. 5 or 10) within a system bandwidth.

Figure 15 is a block diagram illustrating one implementation of a gNB 1660. The gNB 1660 may include a higher layer processor 1623, a DL transmitter 1625, a UL receiver 1633, and one or more antenna 1631. The DL transmitter 1625 may include a PDCCH transmitter 1627 and a PDSCH transmitter 1629. The UL receiver 1633 may include a PUCCH receiver 1635 and a PUSCH receiver 1637.

The higher layer processor 1623 may manage physical layer’s behaviors (the DL transmitter’s and the UL receiver’s behaviors) and provide higher layer parameters to the physical layer. The higher layer processor 1623 may obtain transport blocks from the physical layer. The higher layer processor 1623 may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE’s higher layer. The higher layer processor 1623 may provide the PDSCH transmitter transport blocks and provide the PDCCH transmitter transmission parameters related to the transport blocks.

The DL transmitter 1625 may multiplex downlink physical channels and downlink physical signals (including reservation signal) and transmit them via transmission antennas 1631. The UL receiver 1633 may receive multiplexed uplink physical channels and uplink physical signals via receiving antennas 1631 and de-multiplex them. The PUCCH receiver 1635 may provide the higher layer processor 1623 UCI. The PUSCH receiver 1637 may provide the higher layer processor 1623 received transport blocks.

Figure 16 is a block diagram illustrating one implementation of a UE 1702. The UE 1702 may include a higher layer processor 1723, a UL transmitter 1751, a DL receiver 1743, and one or more antenna 1731. The UL transmitter 1751 may include a PUCCH transmitter 1753 and a PUSCH transmitter 1755. The DL receiver 1743 may include a PDCCH receiver 1745 and a PDSCH receiver 1747.

The higher layer processor 1723 may manage physical layer’s behaviors (the UL transmitter’s and the DL receiver’s behaviors) and provide higher layer parameters to the physical layer. The higher layer processor 1723 may obtain transport blocks from the physical layer. The higher layer processor 1723 may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE’s higher layer. The higher layer processor 1723 may provide the PUSCH transmitter transport blocks and provide the PUCCH transmitter 1753 UCI.

The DL receiver 1743 may receive multiplexed downlink physical channels and downlink physical signals via receiving antennas 1731 and de-multiplex them. The PDCCH receiver 1745 may provide the higher layer processor 1723 DCI. The PDSCH receiver 1747 may provide the higher layer processor 1723 received transport blocks.

It should be noted that names of physical channels described herein are examples. The other names such as “NRPDCCH, NRPDSCH, NRPUCCH and NRPUSCH”, “new Generation-(G)PDCCH, GPDSCH, GPUCCH and GPUSCH” or the like can be used.

Figure 17 illustrates various components that may be utilized in a UE 1802. The UE 1802 described in connection with Figure 17 may be implemented in accordance with the UE 102 described in connection with Figure 1. The UE 1802 includes a processor 1803 that controls operation of the UE 1802. The processor 1803 may also be referred to as a central processing unit (CPU). Memory 1805, which may include read-only memory (ROM), random access memory (RAM), a combination of the two or any type of device that may store information, provides instructions 1807a and data 1809a to the processor 1803. A portion of the memory 1805 may also include non-volatile random-access memory (NVRAM). Instructions 1807b and data 1809b may also reside in the processor 1803. Instructions 1807b and/or data 1809b loaded into the processor 1803 may also include instructions 1807a and/or data 1809a from memory 1805 that were loaded for execution or processing by the processor 1803. The instructions 1807b may be executed by the processor 1803 to implement the methods described above.

The UE 1802 may also include a housing that contains one or more transmitters 1858 and one or more receivers 1820 to allow transmission and reception of data. The transmitter(s) 1858 and receiver(s) 1820 may be combined into one or more transceivers 1818. One or more antennas 1822a-n are attached to the housing and electrically coupled to the transceiver 1818.

The various components of the UE 1802 are coupled together by a bus system 1811, which may include a power bus, a control signal bus and a status signal bus, in addition to a data bus. However, for the sake of clarity, the various buses are illustrated in Figure 17 as the bus system 1811. The UE 1802 may also include a digital signal processor (DSP) 1813 for use in processing signals. The UE 1802 may also include a communications interface 1815 that provides user access to the functions of the UE 1802. The UE 1802 illustrated in Figure 17 is a functional block diagram rather than a listing of specific components.

Figure 18 illustrates various components that may be utilized in a gNB 1960. The gNB 1960 described in connection with Figure 18 may be implemented in accordance with the gNB 160 described in connection with Figure 1. The gNB 1960 includes a processor 1903 that controls operation of the gNB 1960. The processor 1903 may also be referred to as a central processing unit (CPU). Memory 1905, which may include read-only memory (ROM), random access memory (RAM), a combination of the two or any type of device that may store information, provides instructions 1907a and data 1909a to the processor 1903. A portion of the memory 1905 may also include non-volatile random-access memory (NVRAM). Instructions 1907b and data 1909b may also reside in the processor 1903. Instructions 1907b and/or data 1909b loaded into the processor 1903 may also include instructions 1907a and/or data 1909a from memory 1905 that were loaded for execution or processing by the processor 1903. The instructions 1907b may be executed by the processor 1903 to implement the methods described above.

The gNB 1960 may also include a housing that contains one or more transmitters 1917 and one or more receivers 1978 to allow transmission and reception of data. The transmitter(s) 1917 and receiver(s) 1978 may be combined into one or more transceivers 1976. One or more antennas 1980a-n are attached to the housing and electrically coupled to the transceiver 1976.

The various components of the gNB 1960 are coupled together by a bus system 1911, which may include a power bus, a control signal bus and a status signal bus, in addition to a data bus. However, for the sake of clarity, the various buses are illustrated in Figure 18 as the bus system 1911. The gNB 1960 may also include a digital signal processor (DSP) 1913 for use in processing signals. The gNB 1960 may also include a communications interface 1915 that provides user access to the functions of the gNB 1960. The gNB 1960 illustrated in Figure 18 is a functional block diagram rather than a listing of specific components.

Figure 19 is a block diagram illustrating one implementation of a UE 2002 in which configurable beam management of sidelink resources may be implemented. The UE 2002 includes transmit means 2058, receive means 2020 and control means 2024. The transmit means 2058, receive means 2020 and control means 2024 may be configured to perform one or more of the functions described in connection with Figure 1 above. Figure 17 above illustrates one example of a concrete apparatus structure of Figure 19. Other various structures may be implemented to realize one or more of the functions of Figure 1. For example, a DSP may be realized by software.

Figure 20 is a block diagram illustrating one implementation of a gNB 2160 in which configurable beam management of sidelink resources may be implemented. The gNB 2160 includes transmit means 2123, receive means 2178 and control means 2182. The transmit means 2123, receive means 2178 and control means 2182 may be configured to perform one or more of the functions described in connection with Figure 1 above. Figure 18 above illustrates one example of a concrete apparatus structure of Figure 20. Other various structures may be implemented to realize one or more of the functions of Figure 1. For example, a DSP may be realized by software.

It should be noted that one or more of the methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc.

Each of the methods disclosed herein comprises one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another and/or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for proper operation of the method that is being described, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.

It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the systems, methods, and apparatus described herein without departing from the scope of the claims.

A program running on the gNB 160 or the UE 102 according to the described systems and methods is a program (a program for causing a computer to operate) that controls a CPU and the like in such a manner as to realize the function according to the described systems and methods. Then, the information that is handled in these apparatuses is temporarily stored in a RAM while being processed. Thereafter, the information is stored in various ROMs or HDDs, and whenever necessary, is read by the CPU to be modified or written. As a recording medium on which the program is stored, among a semiconductor (for example, a ROM, a nonvolatile memory card, and the like), an optical storage medium (for example, a DVD, a MO, a MD, a CD, a BD, and the like), a magnetic storage medium (for example, a magnetic tape, a flexible disk, and the like), and the like, any one may be possible. Furthermore, in some cases, the function according to the described systems and methods described above is realized by running the loaded program, and in addition, the function according to the described systems and methods is realized in conjunction with an operating system or other application programs, based on an instruction from the program.

Furthermore, in a case where the programs are available on the market, the program stored on a portable recording medium can be distributed or the program can be transmitted to a server computer that connects through a network such as the Internet. In this case, a storage device in the server computer also is included. Furthermore, some or all of the gNB 160 and the UE 102 according to the systems and methods described above may be realized as an LSI that is a typical integrated circuit. Each functional block of the gNB 160 and the UE 102 may be individually built into a chip, and some or all functional blocks may be integrated into a chip. Furthermore, a technique of the integrated circuit is not limited to the LSI, and an integrated circuit for the functional block may be realized with a dedicated circuit or a general-purpose processor. Furthermore, if with advances in a semiconductor technology, a technology of an integrated circuit that substitutes for the LSI appears, it is also possible to use an integrated circuit to which the technology applies.

Moreover, each functional block or various features of the base station device and the terminal device used in each of the aforementioned implementations may be implemented or executed by a circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each circuit described above may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used.

As used herein, the term “and/or” should be interpreted to mean one or more items. For example, the phrase “A, B and/or C” should be interpreted to mean any of: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase “at least one of” should be interpreted to mean one or more items. For example, the phrase “at least one of A, B and C” or the phrase “at least one of A, B or C” should be interpreted to mean any of: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase “one or more of” should be interpreted to mean one or more items. For example, the phrase “one or more of A, B and C” or the phrase “one or more of A, B or C” should be interpreted to mean any of: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C.

<Summery>
In one example, a user equipment (UE), comprising: receiving circuitry configured to receive first information; and transmitting circuitry configured to transmit a sidelink channel, wherein the first information includes one or more resource pools for V2X communication, a subcarrier spacing for each of the resource pools, and a number of reference signal resources.

In one example, the user equipment (UE), wherein Each of the reference signal resources is a sidelink synchronization signal block (SSSB) or a sidelink channel state information - reference signal (CSI-RS).

In one example, the base station (gNB), wherein Each of the reference signal resources is a sidelink synchronization signal block (SSSB) or a sidelink channel state information - reference signal (CSI-RS).

<Cross Reference>
This Nonprovisional application claims priority under 35 U.S.C. § 119 on provisional Application No. 62/716,828 on August 9, 2018, the entire contents of which are hereby incorporated by reference.

What is claimed is:

Claims

A user equipment (UE), comprising:
receiving circuitry configured to receive first information; and
transmitting circuitry configured to transmit a sidelink channel, wherein the first information includes one or more resource pools for V2X communication, a subcarrier spacing for each of the resource pools, and a number of reference signal resources.
The user equipment (UE) of claim 1, wherein
Each of the reference signal resources is a sidelink synchronization signal block (SSSB) or a sidelink channel state information - reference signal (CSI-RS).
A base station (gNB), comprising:
transmitting circuitry configured to transmit first information; and
receiving circuitry configured to receive a sidelink channel, wherein the first information includes one or more resource pools for V2X communication, a subcarrier spacing for each of the resource pools, and a number of reference signal resources.
The base station (gNB) of claim 3, wherein
Each of the reference signal resources is a sidelink synchronization signal block (SSSB) or a sidelink channel state information - reference signal (CSI-RS).
A communication method by a user equipment (UE), comprising:
receiving first information; and
transmitting a sidelink channel, wherein the first information includes one or more resource pools for V2X communication, a subcarrier spacing for each of the resource pools, and a number of reference signal resources.
A communication method by a base station (gNB), comprising:
transmitting first information; and
receiving a sidelink channel, wherein the first information includes one or more resource pools for V2X communication, a subcarrier spacing for each of the resource pools, and a number of reference signal resources.