WO2019028846A1

WO2019028846A1 - Short transmission time interval based resource assignment

Info

Publication number: WO2019028846A1
Application number: PCT/CN2017/097140
Authority: WO
Inventors: Lin Chen; Wei Luo; Ying Huang; Mengzhen WANG; Jin Yang; Youxiong Lu
Original assignee: Zte Corporation
Priority date: 2017-08-11
Filing date: 2017-08-11
Publication date: 2019-02-14
Also published as: CN110786062A

Abstract

One or more devices, systems, and/or methods for receiving a short transmission time interval sidelink configuration; and performing a sidelink transmission/reception with the short transmission time interval sidelink configuration. One or more devices, systems, and/or methods for providing a short transmission time interval sidelink configuration to perform a sidelink transmission/reception.

Description

SHORT TRANSMISSION TIME INTERVAL BASED RESOURCE ASSIGNMENT

BACKGROUND

As communication technologies evolve, there has been an interest in reduced communication delay. However, reduced communication delay would typically require holistic system replacement configured within a different, shorter communication frame/subframe configuration. Logically, such would result in prior equipment that is no longer compatible/viable. Associated with such topic, if prior equipment remains in use, there are impediments to achieving reduced communication delay.

SUMMARY

In accordance with an aspect of the present disclosure a method is provided that includes receiving a short transmission time interval sidelink configuration, and performing a sidelink transmission/reception with the short transmission time interval sidelink configuration.

In accordance with an aspect of the present disclosure a method is provided that includes providing a short transmission time interval sidelink configuration to perform a sidelink transmission/reception.

In accordance with an aspect of the present disclosure a communication device is provided that includes a processor, and memory including processor-executable instructions that when executed by the processor perform a method presented within the disclosed subject matter.

In accordance with an aspect of the present disclosure a non-transitory computer readable medium is provided having stored thereon processor-executable instructions that when executed perform a method..

DESCRIPTION OF THE DRAWINGS

While the techniques presented herein may be embodied in alternative forms, the particular embodiments illustrated in the drawings are only a few examples that are supplemental of the description provided herein. These embodiments are not to be interpreted in a limiting manner, such as limiting the claims appended hereto.

FIG. 1A is schematic diagram illustrating sidelink (SL) vehicle-to-everything (V2X) communication in which a user equipment (UE) sends a V2X message to a plurality of UEs.

FIG. 1B is schematic diagram illustrating V2X communication in which a first UE forwards the V2X message to an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) , and the E-UTRAN broadcasts the V2X message to a plurality of UEs.

FIG. 1C is schematic diagram illustrating V2X communication in which a first UE forwards the V2X message to a roadside unit (RSU) , which in turn transmits to a E-UTRAN, and the E-UTRAN broadcasts the V2X message to a plurality of UEs.

FIG. 1D is schematic diagram illustrating V2X communication in which a first UE forwards the V2X message to a E-UTRAN, which in turn transmits to a Road Side Unit (RSU) , and the RSU broadcasts the V2X message to a plurality of UEs.

FIG. 2 is a schematic diagram of an example Broadcast-based short transmission time interval (sTTI) SL resource pool configuration.

FIG. 3 is a schematic diagram of an example sTTI SL resource pool configuration based on broadcast and dedicated signaling.

FIG. 4 is a schematic diagram of a Sidelink Control Information (SCI) transmission mode.

FIG. 5 is a schematic diagram of a sTTI-based data transmission.

FIG. 6 is a schematic diagram of an example UE autonomous PC5 bearer /logical channel establishment and Transmission Time Interval (TTI) type configuration.

FIG. 7 is a schematic diagram of an example Base station control PC5 bearer /logical channel establishment and TTI type configuration process.

FIG. 8 is a schematic diagram of an example UE sTTI capability report.

FIG. 9 is a schematic diagram of an example sTTI resource configuration signaling flow.

FIG. 10 is a schematic diagram of an example of a Base station scheduled allocation of sTTI resources.

FIG. 11 is a schematic diagram of an example SLTS based on sTTI transmission.

FIG. 12 is a schematic diagram of an example Channel Busy Ratio (CBR) reporting based on sTTI.

FIG. 13 is an illustration of a scenario involving an example configuration of a base station (BS) that may utilize and/or implement at least a portion of the techniques presented herein.

FIG. 14 is an illustration of a scenario involving an example configuration of a UE that may utilize and/or implement at least a portion of the techniques presented herein.

FIG. 15 is an illustration of a scenario featuring an example non-transitory computer readable medium in accordance with one or more of the provisions set forth herein.

DETAILED DESCRIPTION

Subject matter will now be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific example embodiments. This description is not intended as an extensive or detailed discussion of known concepts. Details that are known generally to those of ordinary skill in the relevant art may have been omitted, or may be handled in summary fashion.

The following subject matter may be embodied in a variety of different forms, such as methods, devices, components, and/or systems. Accordingly, this subject matter is not intended to be construed as limited to any example embodiments set forth herein. Rather, example embodiments are provided merely to be illustrative. Such embodiments may, for example, take the form of hardware, software, firmware or any combination thereof.

Herein it is to be appreciated that some examples are presented with descriptions for one or more user equipment (UE) and/or base station (eNB) /core network. It is to be appreciated that specifics regarding the UE and base station are not limitations to the disclosed subject matter. As an example, successive generations of systems, technologies, and/or equipment (e.g., 5th generation mobile network, 5G) can be utilized with the disclosed subject matter. It is to be understood that these are examples of nodes and that the term node is to be construed to include such structures/devices, and that the term nodes is to be construed to include any other structures/devices for accomplishing the disclosed functions/steps. The nodes (e.g., UEs) may be vehicle based. In particular, at least some of the nodes (e.g., UEs) may be vehicle based. However, it is to be appreciated that the nodes (e.g., UEs) may not be vehicle based. In particular, at least some of the nodes (e.g., UEs) may not be vehicle based.

As fifth-generation communication technologies evolve, delay for Vehicle-to-Vehicle, Vehicle-to-Infrastructure and Vehicle-to-Pedestrian (V2V/V2I/V2P) there has been a higher demand upon a transmission delay from a previous value of 100 milliseconds raised to demand for 10 milliseconds or 3 milliseconds. In the existing resource allocation in cellular and PC5, user equipment (UE) sidelink control and data information transmission use 1ms Long Term Evolution (LTE) subframe as the basic unit, namely a subframe for a Transmission Time Interval (TTI) . Due to the high Vehicle-to-Everything (V2X) delay requirements, 1ms subframe TTI is hard to satisfy the delay requirements of V2X communication.

Short TTI (sTTI) data transmission is introduced in a sidelink, which is expected to achieve the objective of reducing delay. For the UE, there are more choices for the resource type. However, the topic of how to assign resources to the UE in order to achieve better latency performance and provide greater resource efficiency has yet to find effective solutions.

The disclosed subject matter solves these problems, and gives sidelink (SL) resource allocation methods based on short TTI. In one aspect, the disclosed subject matter provides a method that includes: receiving a short transmission time interval relevant sidelink configuration； and performing the sidelink transmission/reception with the short transmission time interval relevant sidelink configuration. In accordance with another aspect the present disclosure provides a communication device that includes a processor, and memory including processor-executable instructions that when executed by the processor cause performance of such method (s) . In accordance with another aspect the present disclosure provides a non-transitory computer readable medium having stored thereon processor-executable instructions that when executed cause performance of such method (s) .

With the increase in the number of vehicles, people pay more and more attention on how to reduce traffic accidents, how to rescue timely and how to coordinate on-site traffic, etc. With the development of communication technology and electronic technology, more and more vehicles are equipped with vehicle communication modules. Through such vehicle equipment there can be a variety of information exchange, such as accident pre-warning information, traffic status reminder information and so on. Based on the pre-cash sensing warning system and through the use of advanced wireless communication technology, it is expected to achieve real-time information exchange between vehicle and vehicle, and between vehicle and roadside unit. In addition, such information exchange is likely to inform each other's current state (such as vehicle geographical location, speed, acceleration and direction) and road environment information. Such is a new way to solve the problem of road traffic safety, and to provide a variety of collision warning information to prevent the occurrence of road traffic safety accidents.

Vehicle to Everything Communications (V2X) refers to the use of a variety of communication technology to achieve Vehicle-to-Vehicle Communications (V2V) , Vehicle-to-Pedestrian Communications (V2P) , Vehicle-to-Infrastructure Communications (V2I) , Vehicle-to Network Communications (V2N) .

Generally speaking, V2X communication includes three scenarios, as shown in FIGS. 1A-1D.

Scenario 1, which is appreciated via review of FIG. 1A, supports PC5-based SL (sidelink) V2X communication. The UE sends a V2X message to the plurality of UEs via the PC5 interface.

Scenario 2, which is appreciated via review of FIG. 1B, supports V2X communication via Uu. The UE forwards the V2X message to the E-UTRAN, and the E-UTRAN broadcasts the V2X message to a plurality of UEs in the local area.

Scenario 3 is appreciated via review of FIGS. 1C and 1D. Specifically, Scenario 3 can be divided into Scenario 3a (FIG. 1C) and Scenario 3b (FIG. 1D) , which supports V2V communication using the E-UTRAN and PC5 interfaces. Within FIG. 1C, the UE sends a V2X message to the UE type Road Side Unit (RSU) via the PC5 interface. The UE type RSU receives the V2X message from the PC5 interface and transmits the V2X message to the radio access network. The radio access network broadcasts the V2X messages received from the UE type RSU to multiple UEs in the local area. Alternatively, as shown within FIG. 1D, the UE forwards the V2X message to the radio access network, which transmits the V2X message to one or more UE type RSUs. The UE type RSU then sent the V2X message over the PC5 interface to multiple UEs in the local area.

With the evolution of the fifth generation of communication technology, the V2V /V2I /V2P business has a higher demand for delay, from a previously 100 milliseconds to 10 milliseconds or even 3 milliseconds. In the existing cellular and PC5 interface resource allocation, the UE's sidelink control and data information transmission uses 1ms LTE subframe as the basic unit, that is, a subframe as a TTI. Due to the high Vehicle-to-Everything (V2X) delay requirements, 1ms subframe TTI is hard to satisfy the stringent delay requirements of V2X communication.

The short TTI-based data transmission is introduced in sidelink, which is expected to achieve the purpose of reducing the delay. For the UE, it has more choices of resource type. However, the topic of how to allocate the resources to the UE to achieve better delay performance, and provide higher resource efficiency, has not yet found an effective solution. As mentioned, in one aspect, the disclosed subject matter provides a method including receiving a short transmission time interval relevant sidelink configuration, and performing the sidelink transmission/reception with the short transmission time interval relevant sidelink configuration. Provided herein are several example embodiments for such method. It is to be understood that the disclosed subject matter is not limited to the provided examples and that the disclosed subject matter is broader than just the provided examples.

One example embodiment is a sidelink (SL) resource pool based on sTTI. Traditional TTI (legacy TTI) is usually in 1ms subframe units. The short TTI introduced in SL can be divided into a variety of types. Each subframe is divided into 6 sTTIs, each containing 2 or 3 Orthogonal Frequency Division Multiplexing /Single Carrier –Frequency Division Multiple Access (OFDM /SC-FDMA) symbols. Or each subframe is divided into two sTTIs, each sTTI contains seven OFDM /SC-FDMA symbols. That is, a slot based sTTI. All the above sTTI types are likely to exist. However, taking into account the practicality and overhead, each subframe is divided into two sTTIs, that is, a slot based sTTI is the most feasible. So, the following description mainly uses slot based TTI as an example.

So, as some examples, the short transmission time interval relevant sidelink configuration can include at least one of a subframe transmission time interval, a slot transmission time interval or a number of symbols of transmission time interval. With regard to the number of symbols of transmission time interval, the number of symbols can be 2, 3, 4 or 7 as some examples.

SL resources based on sTTI are likely to be multiplexed with the legacy TTI resource pool, and it is also possible to design a sTTI SL resource pool that is independent of the legacy TTI SL resource pool. The SL resource pool information that supports sTTI further includes: support for sTTI's SCI resource pool information and/or support sTTI data resource pool information, which can take into account the following three scenarios.

As one such scenario, sTTI SL resources and legacy TTI resources share the same SCI and data resource pool. For example, sTTI-capable UEs need to share resource pools with legacy TTI-based UEs. In this case, one or more sTTI types can be added to support the sTTI indication in the SL transmission resource pool configuration. In addition, the SL transmitting resource pool configuration can also carry a subframe bitmap (time domain) corresponding to the sTTI resource and a physical resource block range or subband (frequency domain) range corresponding to the sTTI resource. In addition, in the time domain, the SL resource pool configuration can also contain sTTI bitmap information within subframes. With the slot-based sTTI as an example, sTTI bitmaps can be 01. It means that slot1 is used as sTTI resource. On the other hand, if only one sTTI is configured for SL transmission in a subframe, it can be indicated by the sTTI offset in the subframe. If the sTTI offset is set to 0, it means that there are sTTI resources in slot0 of the subframe.

As another such scenario, sTTI SL resources and legacy TTI resources share the same data resource pool, but there is an allocation of independent sTTI SL SCI resource pool. In this case, in addition to the original legacy TTI resource pool configuration, there is one more sTTI SCI resource pool configuration. The number of SCI resources corresponding to the resource pool is the same as that of the sTTI data subband on the corresponding legacy TTI resource pool. In the specific resource pool configuration, the sTTI-based SCI resource pool configuration information may include support for the sTTI indication. In this case, one or more sTTI types can be added to support the sTTI indication in the SL transmission resource pool configuration. In addition, the SL transmission resource pool configuration can also carry a subframe bitmap (time domain) corresponding to the sTTI resource and a physical resource block range or subband (frequency domain) range corresponding to the sTTI resource. In addition, in the time domain, the SL resource pool configuration can also contain sTTI bitmap information within subframes. With the slot based sTTI as an example, sTTI bitmaps can be 01. It means that slot1 is used as sTTI resource. On the other hand, if only one sTTI is configured for SL transmission in a subframe, it can be indicated by the sTTI offset in the subframe. If the sTTI offset is set to 0, it means that there are sTTI resources in slot0 of the subframe.

As another scenario, there can be an independent sTTI SL resource pool configuration. For example, the sTTI-based SL resource pool configuration information may contain sTTI indication, one or more sTTI types, time-frequency domain resource locations that support the sTTI indication. The bitmap for indicating the time domain resource location can be in the unit of sTTI duration. Optionally, the time domain resource location is still indicated by the subframe based bitmap, but the resource pool configuration needs to contain the sTTI bitmap information within the subframe. With the slot based sTTI as an example, sTTI bitmaps can be 01. This means that slot1 is used as sTTI resource. On the other hand, if only one sTTI is configured for SL transmission in a subframe, it can be indicated by the sTTI offset in the subframe. If the sTTI offset is set to 0, it means that there are sTTI resources in slot0 of the subframe.

The sTTI SL resource pool configuration information can be delivered through SIB messages (as shown in FIG. 2) or dedicated signaling (as shown in FIG. 3) . FIG. 2 shows an example broadcast-based sTTI SL resource pool configuration. FIG. 3 shows an example sTTI SL resource pool configuration based on broadcast and dedicated signaling. It is also possible to preconfigure the sTTI SL resource pool information in a UE that supports sTTI. The UE may receive the above sTTL SL resource pool configuration information from the Proximity-based Services (ProSe) Function /V2X control function or the connected Relay UE. The sTTI SL resource pool configuration information includes one or more SL transmission/reception resource pools that support sTTI based on the above information configuration.

In actual network deployments, it is possible that some base stations support sTTI, while some base stations do not support sTTI. Nonetheless, the moving vehicle UE will suffer from service dis-continuity when passing through these areas.

For the V2X service such as basic safety, it is suggested that the vehicle UE adopt legacy TTI transmission, and whether or not the sTTI is supported, the vehicle UE will receive the V2X SL message transmission on the legacy TTI. For a vehicle UE that supports sTTI SL, the vehicle UE can initiate SL transmission based on sTTI in the area where the base station supports the sTTI SL resource configuration. If the vehicle UE supporting sTTI enters a base station area that does not support sTTI SL transmission, the UE supporting sTTI shall inform the upper layer that the area does not support sTTI SL transmission and reception. Correspondingly, the vehicle UE supporting sTTI may consider the use of preconfigured resources. It should be noted that the only if the frequency band of the preconfigured sTTI SL resource is different from the current base station operating frequency band and the current base station does not support the inter-carrier SL resource configuration of pre-configured frequency band, that is, without interfering with the current base station, could the pre-configured sTTI SL resource be used by UE. Alternatively, or additionally, the upper layer directly stops the service message transmission that requires sTTI.

It can be seen that the base station can indicate whether the sTTI SL is supported in the SIB message. It can also indicate whether the sTTI SL is supported in the neighbor cells and even the sTTI SL resource pool information of neighbor cells to facilitate the inter-cell and or inter-carrier sTTI SL transmission and reception of the sTTI capable UE. In order to support service continuity, it is recommended to configure an exceptional resource pool that supports sTTI SL transmission, which could be used by sTTI capable UE when sensing result of normal sTTI SL resource pool is unavailable. In this case, UE may temporarily use exceptional resource pool for sTTI SL transmission.

In summary for this example embodiment, in addition to supporting the SL resource pool configuration of the sTTI in this cell, the base station or cell can also transmit inter-cell/inter-frequency/inter-PLMN (Public Land Mobile Network) sTTI SL for transmission/reception of resource configuration pool information.

For SL communication, it is intended to introduce the sTTI. As such, there needs to be a consideration of the different SA /SCI and data transmission type. For SCI, the transmission can be divided into the following types:

A first type is when the UE only sends the legacy TTI-based SCI. This mode can be backward compatible with the UE that uses legacy TTI. The legacy TTI UE can correctly analyze the SCI information sent by the sTTI-based UE, as shown in FIG. 4A.

A second type is when the UE simultaneously sends legacy TTI SCI and sTTI SCI. This mode can be backward compatible with the UE that uses legacy TTI for transmission. At the same time, the receiving UE capable of sTTI can receive the sTTI based SCI and the corresponding data, so as to achieve the purpose of reducing the delay, as shown in FIG. 4B.

A third type is when the UE only sends the sTTI based SCI. This mode/method cannot be backward compatible with the legacy TTI-based UE. Only the sTTI capable of receiving UE can receive the sTTI-based SCI and the corresponding data, so as to reduce the delay. See FIG. 4C.

So, the legacy TTI can be considered to be a first interval and the sTTI can be considered to be a divided portion of the first interval.

As such, according to the disclosed methodology, a transmission time interval resource for communication is selected. The legacy TTI can be selected, and can be considered to be a first interval, or the sTTI can be selected, and can be considered to be a divided portion of the first interval.

The selection can include selection of the divided portion of the first interval for communication when there is ability to perform communication at the transmission time interval that is at the divided portion of the first interval. The method can include multiplex communication that includes communication that utilizes the first transmission interval resource and communication that utilizes the divided portion of the first transmission interval.

It is to be noted that the method thus includes communication that provides sidelink Control Information. The sidelink Control Information can be provided using the first transmission time interval (e.g., legacy TTI) . The sidelink Control Information can be provided using the first transmission time interval and using the divided portion of the first transmission interval (sTTI) . The sidelink Control Information can be provided using the divided portion of the first transmission interval.

For the data transmission in SL communication, only the transmission mode based on sTTI is usually considered. However, according to the SL resource usage of each sTTI in the same frequency domain of the same subframe, it can be divided into the following transmission modes:

Within a first mode, the UE uses only one sTTI resource for SL data transmission in the same frequency domain for a given subframe, as shown in FIG. 5A.

Within a second mode, the UE transmits SL data using the resources of multiple sTTIs within the same frequency domain of a given subframe, where the transmission of the UE over multiple sTTIs may be multiple retransmissions of the same Medium Access Control Protocol Data Unit (MAC PDU) , and it is also possible for the transmission of multiple different MAC PDUs, as shown in FIG. 5B.

Within a third mode, in the same frequency domain of a given subframe, different UEs use different sTTI resources to transmit different MAC PDUs respectively, as shown in FIG. 5C.

The method includes providing communication that provides sidelink data transmission. The divided portion of the first transmission interval can be one of a plurality of divided portions of the first transmission interval. As such, several utilizations for data transmission are possible. As an example, the sidelink data transmission occurs using one of the plurality of divided portions of the first transmission interval. As another example, the sidelink data transmission occurs using multiple of the plurality of divided portions of the first transmission interval. As yet another example, communication provides sidelink data transmission for a first UE (e.g., a first node) and provides sidelink data transmission for a second UE (e.g., a second node) . For such, the sidelink data transmission for the first UE (node) can occur using a first of the plurality of divided portions of the first transmission interval and the sidelink data transmission for the second UE (node) can occur using a second of the plurality of divided portions of the first transmission interval.

The SL SCI and data transmission methods can be flexible and free to combine together to make varied combinations. The various combinations can be for different application scenarios. Following are a few example combinations. Of course, the overall number of possible combinations is not limited by these examples.

In a first example scenario, the UE only transmits the legacy TTI-based SCI, and the UE is to repeat the transmission of the data based on sTTI using the resources of multiple sTTIs in the same subframe. Such an example is a combination of the content shown within FIG. 4A and the content shown within FIG. 5B. The UE corresponds to the data resources indicated by the legacy SCI Data subband, and there can be continuous retransmission on multiple sTTI resources to improve sTTI SL transmission reliability.

In a second example scenario, UEs only transmits sTTI SCI and different UEs transmits different data on multiple sTTIs in the same frequency domain in the same subframe. Such an example is a combination of the content shown within FIG. 4C and the content shown within FIG. 5C. This combination can take full advantage of resources, reduce latency, increase transmission opportunities, and alleviate half Duplex issue. However, the UE that supports sTTI in this mode cannot be backward compatible with a UE that only supports legacy TTI.

In a third example scenario, the UE sends both the legacy TTI SCI and the sTTI SCI. The different UEs transmit different data on the multiple sTTIs in the same frequency domain in the same subframe. The different UEs transmit the legacy TTIs SCI on the same legacy TTI resource. Meanwhile, the different UEs transmit the sTTI SCIs respectively on different sTTI resource. Such an example is a combination of the content shown within FIG. 4B and the content shown within FIG. 5C.

As such, it is to be appreciated that, within the method, communication provides sidelink Control Information and provides sidelink data transmission. Several possibilities can be utilized. For example, the sidelink Control Information can be provided using the first transmission time interval and the sidelink data transmission can be provided using the divided portion of the first transmission interval. As another example, the sidelink Control Information can be provided using the divided portion of the first transmission interval and the sidelink data transmission can be provided using the divided portion of the first transmission interval. As yet another example, the sidelink Control Information can be provided using the first transmission time interval and using the divided portion of the first transmission interval, and the sidelink data transmission can be provided using the divided portion of the first transmission interval.

The above SLT and data transmission types based on sTTI are likely to coexist for different application scenarios. The system should have the ability to configure SL SCI transport type, SL data transfer type, and /or SL SCI and data transfer type combination. The configuration may be a base station configuration, which can be per cell configuration, or per resource pool configuration, either per UE configuration or per packet configuration.

UE TTI Type configuration is contemplated and discussed as follows. For scenarios where sTTI resources and legacy TTI SL resource configurations coexist, the UE may decide whether to select sTTI resources or legacy TTI resources based upon various and/or plural factors. Some example factors that can be considered are presented following.

For example, one factor used to select/determine is delay requirement. For the service with higher delay requirement, it can be considered to use sTTI to transmit, otherwise use the legacy TTI SL resource to transmit. So, within the methodology, selection of a transmission time interval resource for communication may include a determination using delay.

Another example factor that can be use is based upon a reliability requirement of the decision. Specifically, some service data transmission requires high reliability, and may need to use both sTTI and legacy TTI SL resources to transmit. So, within the methodology, selection of a transmission time interval resource for communication may include a determination using a reliability requirement.

Another example factor that can be use is based upon a packet size determination or decision (i.e., size of the packet) . Specifically, small packets are more suitable for sTTI resources to transmit, whereas large packets may be more suitable for transmission through the legacy TTI resources. So, within the methodology, selection of a transmission time interval resource for communication may include a packet size based determination

Another example factor that can be use is based on UE capability. Only a sTTI SL capable UE can sent using sTTI SL resource, otherwise legacy TTI SL resources are used. So, within the methodology, selection of a transmission time interval resource for communication may include a determination using node capacity.

Another example factor that can be use is based on the resource status. For some packets, if the time to reach L2 and UE scheduling to transmit the packet is close to the PDB (Packet Delay Budget) , the UE will look for the earliest available resources to choose. Such as the earliest available resource that is based on sTTI SL resources. For such a situation, the UE uses sTTI resources for packet transmission. Otherwise consider using legacy TTI transport. So, within the methodology, selection of a transmission time interval resource for communication may include a determination using resource status.

Another example factor that can be use is based on a decision regarding the SL resource pool congestion level. If the legacy TTI SL transmission resource pool is not congested (Channel Busy Ratio or CBR <system pre-configured threshold 1) , the UE may select the legacy TTI SL transmission resource for data transmission. If the sTTI SL transmission resource pool is not congested (CBR <system pre-configured threshold 2) , the UE may choose sTTI SL transmission resource for data transmission. So, within the methodology, selection of a transmission time interval resource for communication may include a determination about resource pool congestion level.

Another example factor that can be use is based on Base station configuration. According to the resources allocated by the base station, if the base station allocates the sTTI resource, the UE uses the sTTI resource for sidelink transmission, otherwise the legacy TTI resource is used for sidelink transmission. So, within the methodology, selection of a transmission time interval resource for communication may include a determination based upon configuration of the base station.

The base station may configure several aspects. The following are some examples of configuration. The base station may configure the mapping between the ProSe Per-Packet Priority /Packet Delay Budget /Quality of Service (QoS) Class Identifier and Transmission Time Interval (PPPP /PDB /QCI and the TTI) type. See for example FIG. 6. The base station may configure the mapping between the TTI type and the logical channel identification /logical channel group identification. The base station may configure the logical channel identification /logical channel group identification and the TTI type mapping. The base station may configure the mapping between PPPP and logical channel identification /logical channel group identification. In addition, the base station can also configure the mapping between the packet size and the TTI type for the UE. The base station may also configure whether the packet corresponding to a specific PPPP /logical channel /logical channel group is allowed to select the nearest TTI type source. Note that the TTI type includes legacy TTI and sTTI. Further, sTTI can also be subdivided into TTI types that include different number of symbols. For example, 2, 3, 4 or 7 symbols may be used. The above mapping can be a one-to-many mapping, such as a PPPP /PDB /QCI can be mapped to multiple TTI types. For different TTI types, the base station may further configure the priority of different TTI types for UE resource selection. For a mapping between packet size and TTI type, a packet size range can correspond to one or more TTI types, and different packet size ranges correspond to different TTI types. The above information, in addition to the base station configuration, can also be obtained from the ProSe Function /V2X control function or UE pre-configuration information.

Further, the following options may be considered by the UE to select the sTTI SL resource or the legacy TTI SL resource.

If the Non-Access Stratum (NAS) layer /upper layer configure AS layer to transmit SL communication data, the packets from the NAS layer /upper layer carry the following information: PPPP /PDB information. After receiving the packet, the UE AS layer determines that the UE should map the packet to which logical channel /logical channel group according to the PPPP /PDB information carried by the packet and the mapping between the PPPP and the logical channel identification /logical channel group identifier received by the UE from the base station. The UE then determines whether a corresponding logical channel /logical channel group has been established. If the corresponding logical channel has not been established, the UE may further establish the corresponding logical channel /logical channel group according to the logical channel identification /logical channel group identification. If the corresponding logical channel has been established, the UE may determine the TTI type that can be supported corresponding to the SL packet or the mapped logical channel /logical channel group according to the mapping between logical channel identification /logical channel group identification and the TTI type.

If the NAS layer /upper layer configures AS layer to transmit SL communication data, the packets from the NAS layer /upper layer carry the following information: PPPP /PDB information. After receiving the packet, the UE AS layer determines that the packet should be mapped to which logical channel /logical channel group according to the PPPP /PDB information carried by the packet and the mapping between the PPPP and the logical channel identification /logical channel group identifier received by the UE. The UE then determines whether a corresponding logical channel /logical channel group has been established. If the corresponding logical channel /logical channel group information has not been established, the UE may further establish the corresponding logical channel. If the corresponding logical channel has been established, the UE may determine the TTI type that can be supported corresponding to the SL packet transmission or the mapped logical channel /logical channel group according to the PPPP /PDB and the TTI type Mapping, as shown in FIG. 6. Recall that FIG. 6 shows a UE autonomous PC5 bearer /logical channel establishment and TTI type configuration.

If the NAS layer /upper layer configures AS layer to transmit SL communication data, the packets from the NAS layer /upper layer carry the following information: PPPP /PDB information. After the UE AS layer receives the packet, the UE AS layer determines that the packet should be transmitted through which TTI type according to the PPPP /PDB information and packet size carried by the packet, and the mapping between the PPPP /PDB /QCI and TTI types acquired by the UE and the mapping between the packet size and the TTI type. The UE then determines which logical channel /logical channel group the packet should be mapped according to the mapping between the TTI type and the logical channel identification /logical channel group. The UE then determines whether a corresponding logical channel /logical channel group has been established. If the corresponding logical channel /logical channel group information has been established, the UE delivers the packet to the corresponding logical channel and waits for the UE autonomous selection /base station to schedule the allocation of the appropriate SL resource for data transmission.

In the UE-to-network relay scenario, the remote UE may establish the corresponding PC5 logical channel /bearer according to the Uu bearer of the remote UE and configures the same QoS parameters. The UE AS layer receives the packet that needs to be transmitted through the SL relay and maps the packet to the PC5 logical channel /bearer corresponding to the Uu bearer of the packet. The UE can determine the TTI type that the PC5 logical channel /bearer can use for the packet according to the pre-acquired mapping between the QCI and TTI types.

If the base station configures the PC 5 logical channel /bearer, the base station may transmit the PC5 bearer /logical channel configuration information to the UE via Radio Resource Control (RRC) dedicated signaling. The PC5 bearer /logical channel configuration information received by the UE includes, in addition to the QoS configuration, the Packet Data Convergence Protocol /Radio Link Control /Medium Access Control (PDCP /RLC /MAC) configuration, and one or more TTI type information corresponding to the PC5 bearer /logical channel. The data packets mapped to the PC5 bearer /logical channel can be transmitted through the corresponding one or more TTI type SL resources. Optionally, the UE may transmit a sTTI transmission interest indication, TTI type (e.g., TTI duration) , and a QoS parameter corresponding to the PC5 bearer /logical channel that is desired to be established such as QCI/PPPP/PDB, etc., before the UE receives the PC5 bearer /logical channel configuration information sent by the base station. See FIG. 7 and recall that FIG. 7 shows base station controlled PC5 bearer /logical channel and TTI type configuration establishment process.

After receiving the TTI type and priority configuration information that the PPPP /logical channel /logical channel group can use, the UE determines the available TTI type for the packet to be transmitted according to the PPPP /logical channel /logical channel group to which it mapped. If the UE also receives the priority configuration corresponding to the TTI type, the UE preferentially selects the higher priority TTI type when selecting the resource or requesting the resource. If the available TTI type resource is not available, the priority is selected again Low TTI type, and so on.

If the UE receives a configuration of the specific PPPP /logical channel /logical channel group is allowed to select the nearest TTI type source, it means that if the time between the packet corresponding to the PPPP /logical channel /logical channel group arrives at layer 2 and the UE scheduling transmission is already close to the PDB, the nearest available TTI type resources could be used by the UE, and is not limited by the TTI type corresponding to the PPPP /logical channel /logical channel group.

There can be a UE sTTI capability report. For the UE in the RRC connected state, the capability can be reported to the eNB. The capability report includes SL sTTI indication and one or more SL TTI types that UE support. It can also contain information such as sTTI SCI transmission type supported by UE, sTTI SL data transmission type and so on. Assuming that the UE supports multiple TTI types, the base station may then configure the UE with the SL transmission/reception resource with TTI type supported by UE according to the UE’s capability report. This configuration can be implemented by dedicated signaling. See FIG. 8 which shows and example UE sTTI capability report.

Resource allocation signaling based on sTTI can be provided. For a RRC connected UE supporting the sTTI, the sidelink resource configuration request information may be sent to the base station. The sidelink resource configuration request information may include the SL sTTI transmission resource request and the TTI type of the requested resource. After receiving the resource configuration request sent by the UE capable of sTTI, the base station sends an SL resource configuration for the UE, which contains one or more sTTI-enabled SL resource pool information that supports sTTI. For the base station scheduled resource allocation, the base station sends the mapping between PPPP /PDB /QCI and TTI type mapping. In addition, the base station can transmit sTTI SCI transmission type, sTTI data transmission type. After the UE receives the configuration sent by the base station, according to the PPPP /PDB information and packet size carried by the packet, and the mapping between the PPPP /PDB /QCI and the TTI type obtained from the base station and the mapping between the packet size and the TTI type, it can be determined the data packets can be transmitted through which TTI type. The UE then determines which logical channel /logical channel group the packet should map to according to the mapping between the TTI type and the logical channel identification /logical channel group. If the corresponding logical channel /logical channel group information has been established, the UE delivers the packet to the corresponding logical channel and subsequently transmits the data with the appropriate TTI type SL resource based on the UE selection /base station scheduling allocation. See for example, FIG. 9, which shows an example that is based on sTTI resource configuration signaling flow.

The UE may perform autonomous sTTI SL resource selection and transmission. UE autonomous sTTI SL resource selection and transmission can be divided into several processes. Examples of such are described following.

There may be TTI type selection. In the scenario where the UE autonomous selecting resource, the UE determines the TTI type for the resource selection according to the configured TTI type corresponding to the PC5 logical channel /bearer /logical channel priority and the priority of PC5 logical channel /bearer with packet buffering before the UE schedules the SL packet transmission. For example, the TTI type which is supported by the higher priority PC5 logical channel /bearer may be selected.

Before UE initiates the SL transmission, UE first determines the PC5 logical channel /logical channel group to be scheduled with packet buffering, and then there is a determination of the TTI type of which resource to be selected according to the corresponding TTI type of PC5 logical channel /bearer to be scheduled. If the PC5 logical channel /logical channel group needs to be scheduled support a variety of TTI types, assuming that the UE receives the priority configuration corresponding to the TTI type, the UE selects the higher priority TTI type. If the SL resource for the selected TTI type is not available, then the lower priority TTI type is selected.

If the UE receives a configuration of the specific PPPP /logical channel /logical channel group is allowed to select the nearest TTI type resource, and if the time between the packet corresponding to the PPPP /logical channel /logical channel group arrives at layer 2 and the UE scheduling transmission is already close to the PDB, the TTI type with the nearest available SL resource could be selected by the UE, not limited by the TTI type corresponding to the PPPP /logical channel /logical channel group.

There may be resource pool selection. After the UE selects the TTI type, the UE selects the corresponding SL transmission resource pool according to the TTI type. If there are multiple SL transmission resource pools corresponding to a TTI type, the UE selects the appropriate SL transmission resource pool based on the detected congestion level of the SL transmission resource pool, for example, prioritize the non-congested SL transmission resource pool (CBR <system preconfigured threshold 2) . On the other hand, if both sTTI SL resource pools independent of the legacy TTI SL resource pool and the sTTI SL resource multiplexed with the legacy TTI resource pool exist, the sTTI SL resource pools independent of the legacy TTI SL resource pool are preferred.

There may be resource selection. Specifically, selecting SL resources corresponding to the TTI type from the SL transmission resource randomly or based on the sensing result. In the legacy TTI and sTTI shared resource pool scenarios, if the UE transmits sTTI SCI and different UE may transmit different data (e.g., see FIGS. 4C and 5C) on multiple sTTIs in the same frequency domain in the same subframe, in order to avoid in accurate sensing of UE only capable of legacy TTIs, the resources on multiple sTTIs in the same frequency domain should be fully occupied as much as possible. For the sTTI capable UE, after sensing the sTTI SL transmission resource pool, the resources of sTTIs on the same frequency domain of the same subframe that are not fully filled by the sTTI UE should be prioritized.

In the legacy TTI and sTTI shared resource pool scenarios, suppose the UE simultaneously sends legacy TTI SCI and sTTI SCI and different UEs transmit different data (e.g., see FIGS. 4C and 5C) on multiple sTTIs in the same frequency domain in the same subframe. Different UEs send the legacy TTI SA SCI on the same legacy TTI SCI resource at the same time, while sending the sTTI-based SCI and data on the independent sTTI sources. In this scenario, if the sTTI capable UE monitors the legacy SCI and the corresponding data resource has only part of the sTTI data transmission in the time domain, it means that sTTI is not fully occupied. So the UE selects the other unoccupied sTTI resource within the same frequency domain in the same subframe for data transmission.

There may be packet assembly. MAC layer is responsible for scheduling data packet from PC5 logical channels /bearer, assemble MAC PDU. Specifically, the MAC layer schedules the data packets from one or more PC5 logical channels /bearers supporting the TTI type according to the priority order of the logical channels and assembles them into MAC PDU. If the MAC PDU for sTTI SL transmission has more space to include the sTTI based Buffer Status Report (BSR) , the MAC PDU can carry sTTI based BSR information.

When it comes to data transmission, the following is to be noted. In order to support sTTI-based transmission, UE may be configured with different SL SCI /SL data transmission types. If the base station configures the SCI transmission type and the data transmission type for the UE, the UE needs to transmit according to the configured transmission type.

Suppose the UE is configured to transmit the legacy TTI SCI and multiple duplicate data transmissions for the sTTIs using the resources of the same frequency domain within the same subframe, the legacy SCI's reserve bits could be used to indicate the data transmission type /retransmission /retransmission times. In this way, the sTTI is capable receiving UE can recognize the retransmission of the sTTI data within the subframe according to the legacy SCI and perform the corresponding decoding.

In addition to the UE autonomous resource allocation, the base station can control the sTTI SL resource allocation. The base station scheduled sTTI SL resource allocation and UE’s sTTI SL transmission can be divided into following procedures.

For a UE sTTI resource request, if the UE is configured with the mapping between logical channel identification /logical channel group identification and TTI type, UE may transmit the BSR to eNB which includes the logical channel identification /logical channel group identification, the buffer size, and the communication destination index information.

In some scenarios, the base station cannot identify the sTTI type according to the logical channel group identification. For example, the base station only configures the mapping between packet size and sTTI type. In this case, BSR transmitted by UE may include not only the logical channel identification /logical channel group identification, the buffer size, the communication target index, but also one or more TTI type information corresponding to the packet size within the logical channel. Specifically, the TTI type information may indicate the one TTI type resource, and may also indicate multiple TTI types of resources at the same time.

With regard to base station scheduled resource allocation, if the base station is configured with a mapping between logical channel identification /logical channel group identification and TTI type, the base station may determine the corresponding one or more TTI types according to the logical channel group identification to allocate the corresponding resources.

If the UE needs to transmit legacy TTI SCI, sTTI SCI and sTTI data, the base station will transmit the SL grant to UE which include any combination of the following information: legacy TTI SCI resource index/position, sTTI SCI resource index/position, sTTI data resource index/position, TTI type indication, and sTTI data start offset. If the UE only sends legacy TTI SCI and sTTI data, the UE includes the TTI type indication and the sTTI data start offset in the legacy SCI.

Considering that the base station can support multiple TTI types, different types of packets of the UE may also need to be sent through different TTI type resources. It is possible for the base station to configure multiple base station scheduled SL transmission resources pool. These SL transmission resource pools may correspond to different TTI types. In this scenario, the base station needs to indicate the corresponding TTI type and /or the SL transmission resource pool index in the SL grant when assigning the SL resource to the UE.

For the sTTI and legacy TTI share the same resource pool, and the UE autonomous resource allocation and base station scheduled resource allocation of the same resource pool scenario, the base station can allocate sTTI SL resources to the UE capable of sTTI. The eNB may allocate sTTIs resources within the same frequency domain of the same subframe to multiple UEs that need to transmit data at the same time. If the eNB cannot find multiple such sTTI capable UEs with data to be transmitted through sTTI, the eNB can indicate in the SL grant that the UE occupies multiple sTTI resources on the same frequency domain for multiple transmissions within the same subframe. Specifically, the eNB may indicate in the SL grant the number of retransmissions on multiple sTTIs within a subframe.

For packet assembly, MAC layer is responsible for scheduling data packet from PC5 logical channel /bearer, assemble MAC PDU. Specifically, the MAC layer schedules the packets from one or more PC5 logical channels /bearers supporting the TTI type according to the priority order of the logical channels and assembles them into MAC PDU. If the MAC PDU for sTTI SL transmission has more space to include the sTTI based BSR, the MAC PDU can include sTTI based BSR.

When it comes to data transmission, the following discussion is provided. In order to support sTTI-based transmission, a UE may be configured with different SL SCI /SL data transmission types. As shown in FIG. 10, the base station can configure the SCI transmission type and data transmission type for the UE. As such, the UE needs to transmit according to the transmission type configured by the base station. When the UE capable of sTTI receives the SL grant, it can determine the corresponding SL transmission resource pool according to the TTI type /resource pool index, and use the resource corresponding to the SL transmission resource pool to transmit the sTTI SL SCI and data. Suppose the UE is configured to transmit legacy TTI-based SCI and multiple duplicate data transmissions for the sTTIs using the resources of the same frequency domain within the same subframe sTTI (See FIGS. 4A and 5B) , the reserve bit in the legacy SCI transmitted by UE could be used to indicate the data transmission type /retransmission /retransmission times. As such, the sTTI capable receiving UE can recognize the retransmission of the sTTI data within the subframe according to the legacy SCI and perform the corresponding decoding. Again, an example of such is shown within FIG. 10, which shows an example of the base station scheduled sTTI resource allocation.

With regard to SPS based on sTTI, the following discussion is provided. As one example, some services require low latency and periodical transmission. For the sTTI capable UE, the data of these services can be transmitted through sTTI SL SPS. Specifically, the UE may request SPS configuration from the eNB through UE Assistance information. As shown in FIG. 11, the UE may include the sTTI indication and/or TTI type information to the UE Assistance information. Specifically, the TTI type information may indicate sTTI, legacy TTI, or both. In addition, the UE can report the SPS offset and period in units of sTTI. Optionally, if the offset and period is calculated in units of legacy TTI, the sTTI index in the legacy TTI subframe should be included in UE Assistance information.

After the base station receives the UE Assistance information containing the SL SPS configuration info, the base station can configure the sTTI-based SPS for the UE. Specifically, sTTI based SPS configuration may include at least one of the following information: sTTI indication, TTI type, sTTI periodicity and so on.

The base station may activate the SPS by transmitting DCI at the corresponding sTTI subframe or legacy TTI subframe. If the SPS activation DCI corresponding to the sTTI resource is sent over the legacy TTI subframe, the SPS activation DCI may contain sTTI offset information and/or the sTTI indication. Upon receiving the SPS activation DCI, SPS-based sTTI transmission can be performed based on the activated resource location and the SPS configuration sent by the base station.

In the legacy TTI-based SL design, the UE can measure the SL resource pool resource busy ratio and report the resource pool congestion status according to the eNB configuration. For sTTI and legacy TTI shared SL resource pool, some SL transmissions utilize sTTI as the resource granularity, and some SL transmissions are transmitted with the legacy TTI as the resource granularity. Considering this, the UE capable of sTTI should maintain multiple sets of CBR measurements, in addition to the legacy TTI based measurements, and sTTI based resource busy ratio should be measured.

Specifically, if the legacy TTI SCI and sTTI data transmission is required, the UE may report both the legacy TTI-based SCI and the sTTI-based data resource CBR when the SCI and data resources are not adjacent, and when the SCI and data resource are adjacent, the UE still need to report the CBR based on the legacy TTI SCI and the sTTI-based data resource.

If the UE simultaneously transmits legacy TTI SCI, sTTI SCI, and data, it is possible to have an independent sTTI SCI resource pool or reuse the sTTI data resource for sTTI SCI transmission. For the former case, it needs to report the CBR of both legacy TIT SCI and sTTI SCI resources, together with the CBR of sTTI data resource； for the latter case, only the CBR of legacy TTI SCI resource and sTTI data resource need to be reported.

FIG. 12 shows an example of the CBR reporting process based on sTTI. First, the base station sends a sTTI-based measurement configuration. The sTTI capable UE receives the configuration and measures the sTTI resources and transmit the sTTI-based SCI (cbr-PSCCH) and Data measurement report (cbr-PSSCH) to base station.

FIG. 13 presents a schematic architecture diagram 1200 of a base station 1250 that may be utilized with UEs that use at least a portion of the techniques provided herein. Such a base station 1250 may vary widely in configuration and/or capabilities, alone or in conjunction with other base stations, nodes, end units and/or servers, etc. in order to provide a service, such as at least some of one or more of the other disclosed techniques, scenarios, etc. It is contemplated that the base station is a node.

For example, the base station 1250 may connect one or more user equipment (UE) to a (e.g., wireless) network (e.g., which may be connected and/or include one or more other base stations) , such as Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single-Carrier FDMA (SC-FDMA) networks, etc. The network may implement a radio technology, such as Universal Terrestrial Radio Access (UTRA) , CDMA13000, Global System for Mobile Communications (GSM) , Evolved UTRA (E-UTRA) , IEEE 802.11, IEEE 802.16, IEEE 802.20, Flash-OFDM, etc. The base station 1250 and/or the network may communicate using a standard, such as Long-Term Evolution (LTE) .

The base station 1250 may comprise one or more (e.g., hardware) processors 1210 that process instructions. The one or more processors 1210 may optionally include a plurality of cores； one or more coprocessors, such as a mathematics coprocessor or an integrated graphical processing unit (GPU) ； and/or one or more layers of local cache memory. The base station 1250 may comprise memory 1202 storing various forms of applications, such as an operating system 1204； one or more base station applications 1206； and/or various forms of data, such as a database 1208 and/or a file system, etc. The base station 1250 may comprise a variety of peripheral components, such as a wired and/or wireless network adapter 1214 connectible to a local area network and/or wide area network； one or more storage components 1216, such as a hard disk drive, a solid-state storage device (SSD) , a flash memory device, and/or a magnetic and/or optical disk reader； and/or other peripheral components.

The base station 1250 may comprise a mainboard featuring one or more communication buses 1212 that interconnect the processor 1210, the memory 1202, and/or various peripherals, using a variety of bus technologies, such as a variant of a serial or parallel AT Attachment (ATA) bus protocol； a Uniform Serial Bus (USB) protocol； and/or Small Computer System Interface (SCI) bus protocol. In a multibus scenario, a communication bus 1212 may interconnect the base station 1250 with at least one other server. Other components that may optionally be included with the base station 1250 (though not shown in the schematic diagram 1200 of FIG. 13) include a display； a display adapter, such as a graphical processing unit (GPU) ； input peripherals, such as a keyboard and/or mouse； and/or a flash memory device that may store a basic input/output system (BIOS) routine that facilitates booting the base station 1250 to a state of readiness, etc.

The base station 1250 may operate in various physical enclosures, such as a desktop or tower, and/or may be integrated with a display as an “all-in-one” device. The base station 1250 may be mounted horizontally and/or in a cabinet or rack, and/or may simply comprise an interconnected set of components. The base station 1250 may comprise a dedicated and/or shared power supply 1218 that supplies and/or regulates power for the other components. The base station 1250 may provide power to and/or receive power from another base station and/or server and/or other devices. The base station 1250 may comprise a shared and/or dedicated climate control unit 1220 that regulates climate properties, such as temperature, humidity, and/or airflow. Many such base stations 1250 may be configured and/or adapted to utilize at least a portion of the techniques presented herein.

FIG. 14 presents a schematic architecture diagram 1300 of a user equipment (UE) 1350 (e.g., a node) whereupon at least a portion of the techniques presented herein may be implemented. Such a UE 1350 may vary widely in configuration and/or capabilities, in order to provide a variety of functionality to a user. It is to be appreciated that the UE can be a node.

The UE 1350 may be provided in a variety of form factors, such as a mobile phone (e.g., a smartphone) ； a desktop or tower workstation； an “all-in-one” device integrated with a display 1308； a laptop, tablet, convertible tablet, or palmtop device； a wearable device, such as mountable in a headset, eyeglass, earpiece, and/or wristwatch, and/or integrated with an article of clothing； and/or a component of a piece of furniture, such as a tabletop, and/or of another device, such as a vehicle or residence. The UE 1350 may serve the user in a variety of roles, such as a telephone, a workstation, kiosk, media player, gaming device, and/or appliance.

The UE 1350 may comprise one or more (e.g., hardware) processors 1310 that process instructions. The one or more processors 1310 may optionally include a plurality of cores； one or more coprocessors, such as a mathematics coprocessor or an integrated graphical processing unit (GPU) ； and/or one or more layers of local cache memory. The UE 1350 may comprise memory 1301 storing various forms of applications, such as an operating system 1303； one or more user applications 1302, such as document applications, media applications, file and/or data access applications, communication applications, such as web browsers and/or email clients, utilities, and/or games； and/or drivers for various peripherals. The UE 1350 may comprise a variety of peripheral components, such as a wired and/or wireless network adapter 1306 connectible to a local area network and/or wide area network； one or more output components, such as a display 1308 coupled with a display adapter (optionally including a graphical processing unit (GPU) ) , a sound adapter coupled with a speaker, and/or a printer； input devices for receiving input from the user, such as a keyboard 1311, a mouse, a microphone, a camera, and/or a touch-sensitive component of the display 1308； and/or environmental sensors, such as a GPS receiver 1319 that detects the location, velocity, and/or acceleration of the UE 1350, a compass, accelerometer, and/or gyroscope that detects a physical orientation of the UE 1350. Other components that may optionally be included with the UE 1350 (though not shown in the schematic architecture diagram 1300 of FIG. 14) include one or more storage components, such as a hard disk drive, a solid-state storage device (SSD) , a flash memory device, and/or a magnetic and/or optical disk reader； a flash memory device that may store a basic input/output system (BIOS) routine that facilitates booting the UE 1350 to a state of readiness； and/or a climate control unit that regulates climate properties, such as temperature, humidity, and airflow, etc.

The UE 1350 may comprise a mainboard featuring one or more communication buses 1312 that interconnect the processor 1310, the memory 1301, and/or various peripherals, using a variety of bus technologies, such as a variant of a serial or parallel AT Attachment (ATA) bus protocol； the Uniform Serial Bus (USB) protocol； and/or the Small Computer System Interface (SCI) bus protocol. The UE 1350 may comprise a dedicated and/or shared power supply 1318 that supplies and/or regulates power for other components, and/or a battery 1304 that stores power for use while the UE 1350 is not connected to a power source via the power supply 1318. The UE 1350 may provide power to and/or receive power from other client devices.

FIG. 15 is an illustration of a scenario 1400 involving an example non-transitory computer readable medium 1402. The non-transitory computer readable medium 1402 may comprise processor-executable instructions 1412 that when executed, as an embodiment 1414, by a processor 1416 cause performance (e.g., by the processor 1416) of at least some of the provisions herein. The non-transitory computer readable medium 1402 may comprise a memory semiconductor (e.g., a semiconductor utilizing static random access memory (SRAM) , dynamic random access memory (DRAM) , and/or synchronous dynamic random access memory (SDRAM) technologies) , a platter of a hard disk drives, a flash memory device, or a magnetic or optical disc (such as a compact disc (CD) , digital versatile disc (DVD) , and/or floppy disk) . The example non-transitory computer readable medium 1402 stores computer-readable data 1404 that, when subjected to reading 1406 by a reader 1410 of a device 1408 (e.g., a read head of a hard disk drive, or a read operation invoked on a solid-state storage device) , express the processor-executable instructions 1412. In some embodiments, the processor-executable instructions 1412, when executed, cause performance of operations, such as at least some of the above-discussed example methods. The example methods include, but are not limited to the methods shown herein, and the other described methods.

Following is a listing of some acronyms/definitions used herein:

V2V: Vehicle-to-Vehicle

V2I: Vehicle-to-Infrastructure

V2P: Vehicle-to-Pedestrian

V2X: Vehicle-to-Everything

RSU: Road Side Unit

TTI: Transmission Time Interval

SCI: sidelink Control Information

SA: Scheduling Assignment

PDB: Packet Delay Budget

PPPP: ProSe Per-Packet Priority

3GPP: 3rd Generation Partnership Project

eNb: E-UTRAN NodeB, base station

E-UTRAN: Evolved Universal Terrestrial Radio Access Network

RSU: Road Side Unit

OFDM: Orthogonal Frequency Division Multiplexing

SC-FDMA: Single Carrier –Frequency Division Multiple Access

SIB: System Information Block

MAC PDU: Medium Access Control Protocol Data Unit

PLMN: Public Land Mobile Network

QCI: QoS Class Identifier

QoS: Quality of Service

NAS: Non Access Stratum

RRC: Radio Resource Control

PC5: The reference point between ProSe-enabled UEs used for control and user plane for ProSe Direct Discovery, ProSe Direct Communication and ProSe UE-to-Network Relay. The lower protocol layers of the PC5 reference point can be based on E-UTRA sidelink capabilities or on WLAN technology.

R15: Release 15

PPPP: ProSe Per-Packet Priority

ProSe: Proximity-based Services

PDB: Packet Delay Budget

PRB: Physical Resource Block

QCI: QoS Class Identifier

AS: Access Stratum

PDCP: Packet Data Convergence Protocol

RLC: Radio Link Control

MAC: Medium Access Control

CBR: Channel Busy Ratio

BSR: Buffer Status Report

As used in this application, "component, " "module, " "system" , "interface" , and/or the like are generally intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a controller and the controller can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers (e.g., nodes (s) ) .

Unless specified otherwise, “first, ” “second, ” and/or the like are not intended to imply a temporal aspect, a spatial aspect, an ordering, etc. Rather, such terms are merely used as identifiers, names, etc. for features, elements, items, etc. For example, a first object and a second object generally correspond to object A and object B or two different or two identical objects or the same object.

Moreover, "example" is used herein to mean serving as an instance, illustration, etc., and not necessarily as advantageous. As used herein, "or" is intended to mean an inclusive "or" rather than an exclusive "or" . In addition, "a" and "an" as used in this application are generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form. Also, at least one of A and B and/or the like generally means A or B or both A and B. Furthermore, to the extent that "includes" , "having″ , "has" , "with" , and/or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term "comprising” .

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing at least some of the claims.

Furthermore, the claimed subject matter may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer (e.g., node) to implement the disclosed subject matter. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. Of course, many modifications may be made to this configuration without departing from the scope or spirit of the claimed subject matter.

Various operations of embodiments and/or examples are provided herein. The order in which some or all of the operations are described herein should not be construed as to imply that these operations are necessarily order dependent. Alternative ordering will be appreciated by one skilled in the art having the benefit of this description. Further, it will be understood that not all operations are necessarily present in each embodiment and/or example provided herein. Also, it will be understood that not all operations are necessary in some embodiments and/or examples.

Also, although the disclosure has been shown and described with respect to one or more implementations, equivalent alterations and modifications will occur to others skilled in the art based upon a reading and understanding of this specification and the annexed drawings. The disclosure includes all such modifications and alterations and is limited only by the scope of the following claims. In particular regard to the various functions performed by the above described components (e.g., elements, resources, etc. ) , the terms used to describe such components are intended to correspond, unless otherwise indicated, to any component which performs the specified function of the described component (e.g., that is functionally equivalent) , even though not structurally equivalent to the disclosed structure. In addition, while a particular feature of the disclosure may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application.

Claims

A method comprising:

receiving a short transmission time interval sidelink configuration； and

performing a sidelink transmission/reception with the short transmission time interval sidelink configuration.
The method of claim 1, wherein the short transmission time interval sidelink configuration comprises at least one of a subframe transmission time interval, a slot transmission time interval or a number of symbols of transmission time interval.
The method of claim 2, wherein for the number of symbols of transmission time interval, the number of symbols is 2, 3, 4, or 7.
The method of claim 1, wherein the short transmission time interval sidelink configuration comprises at least one of:

at least one of a sidelink transmission or reception resource pool with short transmission time interval configuration；

at least one of an inter-cell/inter-carrier/inter-public land mobile network sidelink transmission or reception resource pools with short transmission time interval configuration； or

at least one of an indication of a cell/neighbor cell/frequency support short transmission time interval or a supported transmission time interval duration type.
The method of claim 4, wherein the at least one of the sidelink transmission or the reception resource pool with short transmission time interval sidelink configuration comprises at least one of:

short transmission time interval sidelink indication or one or more sidelink transmission time interval type；

a short transmission time interval sidelink resource bitmap/offset within a subframe； or

time and frequency domain sidelink resource indication for short transmission time interval.
The method of claim 5, wherein the sidelink transmission time interval type comprises at least one of:

a subframe transmission time interval；

a slot transmission time interval；

a number of symbols of transmission time interval； or

a subframe transmission time interval regarded as legacy transmission time interval and other transmission time interval types regarded as short transmission time interval.
The method of claim 1, wherein a short transmission time interval co-exists with a legacy transmission time interval in a same sidelink resource pool, and the short transmission time interval sidelink configuration comprises at least one of:

subframe bitmap corresponding to a short transmission time interval resource； or

physical resource block range or subband range corresponding to the short transmission time interval resource.
The method of claim 1, wherein the short transmission time interval sidelink configuration further comprises at least one of:

mapping between logical channel identification/logical channel group identification and transmission time interval type；

mapping between prose per-packet priority /packet delay budget /quality of serviced class identifier and transmission time interval type；

mapping between data packet size and transmission time interval type； or

an indication of whether a data packet transmission of prose per-packet priority/logical channel/logical channel group may select a resource of nearest available transmission time interval type.
The method of claim 1, wherein the receiving comprises at least one of:

a first node receiving the short transmission time interval sidelink configuration from a second node；

the first node receiving the short transmission time interval sidelink configuration from a proximity-based services function or a vehicle-to-everything control function； or

the first node receiving a pre-configured short transmission time interval sidelink configuration.
The method of claim 1, wherein the performing comprises a non-access stratum/upper layer of a first node sending a data packet to an access stratum layer along with at least one of a sidelink transmission indication, a transmission time interval type, or a prose per-packet priority /packet delay budget.
The method of claim 1, wherein the performing comprises at least one of:

a first node determining a transmission time interval type for data packet transmission according to a logical channel/logical channel group of data packets belonging to and a mapping between logical channel identification/logical channel group identification and transmission time interval type；

the first node determining the transmission time interval type for data packet transmission according to a prose per-packet priority of data packet and a mapping between prose per-packet priority /packet delay budget and transmission time interval type； or

the first node determining the transmission time interval type for data packet transmission according to a packet size and a mapping between packet size and transmission time interval type.
The method of claim 1, wherein the performing comprises:

a first node selecting a sidelink resource or receiving a sidelink grant from a second node for a transmission time interval type； and

the first node assembling a medium access control protocol data unit with data packets from logical channels corresponding to the transmission time interval type and delivering the medium access control protocol data unit to a lower layer for sidelink transmission.
The method of claim 12, comprising the first node receiving a sidelink grant from a second node for the transmission time interval type, wherein the sidelink grant comprises at least one of: short transmission time interval indication, sidelink control information resource indication, sidelink data resource indication, sidelink control information /data short transmission time interval offset, transmission time interval type； sidelink transmission resource pool index, short transmission time interval data retransmission indication, or short transmission time interval data retransmission number.
The method of claim 1, wherein the short transmission time interval sidelink configuration is selected based upon at least one of a delay, a reliability requirement, a packet size, a node capacity, an available resource status, a determination about resource pool congestion, or a configuration of a node.
A method comprising:

providing a short transmission time interval sidelink configuration to perform a sidelink transmission/reception.
The method of claim 15, wherein the short transmission time interval sidelink configuration comprises at least one of a subframe transmission time interval, a slot transmission time interval, or a number of symbols of transmission time interval.
The method of claim 16, wherein for the number of symbols of transmission time interval, the number of symbols is 2, 3, 4, or 7.
The method of claim 15, wherein the short transmission time interval sidelink configuration comprises at least one of:

at least one of a sidelink transmission or reception resource pool with short transmission time interval configuration；

at least one of an inter-cell/inter-carrier/inter-public land mobile network sidelink transmission or reception resource pools with short transmission time interval configuration； or

at least one of an indication of a cell/neighbor cell/frequency support short transmission time interval or a supported transmission time interval duration type.
The method of claim 18, wherein the at least one of the sidelink transmission or the reception resource pool with short transmission time interval sidelink configuration comprises at least one of:

short transmission time interval sidelink indication or one or more sidelink transmission time interval type；

a short transmission time interval sidelink resource bitmap/offset within a subframe； or

time and frequency domain sidelink resource indication for short transmission time interval.
The method of claim 19, wherein the sidelink transmission time interval type comprises at least one of:

a subframe transmission time interval；

a slot transmission time interval；

a number of symbols of transmission time interval； or

a subframe transmission time interval regarded as legacy transmission time interval and other transmission time interval types regarded as short transmission time interval.
The method of claim 15, wherein a short transmission time interval co-exists with a legacy transmission time interval in a same sidelink resource pool, and the short transmission time interval sidelink configuration comprises at least one of:

subframe bitmap corresponding to a short transmission time interval resource； or

physical resource block range or subband range corresponding to the short transmission time interval resource.
The method of claim 15, wherein the short transmission time interval sidelink configuration further comprises at least one of:

mapping between logical channel identification/logical channel group identification and transmission time interval type；

mapping between prose per-packet priority /packet delay budget /quality of serviced class identifier and transmission time interval type；

mapping between data packet size and transmission time interval type； or

an indication of whether a data packet transmission of prose per-packet priority/logical channel/logical channel group may select a resource of nearest available transmission time interval type.
The method of claim 15, wherein the providing comprises at least one of:

transmitting to a first node the short transmission time interval sidelink configuration from a second node such that the first node is provided with the short transmission time interval sidelink configuration from a proximity-based services function or a vehicle-to-everything control function or the first node is provided a pre-configured short transmission time interval sidelink configuration.
The method of claim 15, wherein the short transmission time interval sidelink configuration is selected based upon at least one of a delay, a reliability requirement, a packet size, a node capacity, an available resource status, a determination about resource pool congestion, or a configuration of a node.
A communication device comprising:

a processor； and

memory comprising processor-executable instructions that when executed by the processor cause performance of a method recited in any of claims 1 to 24.
A non-transitory computer readable medium having stored thereon processor-executable instructions that when executed cause performance of a method recited in any of claims 1 to 24.