CN110786062A

CN110786062A - Resource allocation based on short transmission time interval

Info

Publication number: CN110786062A
Application number: CN201780092470.7A
Authority: CN
Inventors: 陈琳; 罗薇; 黄莹; 汪梦珍; 杨瑾; 卢有雄
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2017-08-11
Filing date: 2017-08-11
Publication date: 2020-02-11
Also published as: WO2019028846A1

Abstract

One or more apparatuses, systems, and/or methods for receiving a short transmission time interval through link configuration and performing through link transmission/reception with the short transmission time interval through link configuration. One or more apparatuses, systems, and/or methods for providing a short transmission time interval direct link configuration to perform direct link transmission/reception.

Description

Resource allocation based on short transmission time interval

Background

As communication technologies develop, there is a constant interest in reducing communication delay. However, reducing communication delay will typically require configuring historical system changes within different shorter communication frame/subframe configurations. Logically, this would result in existing devices no longer being compatible/viable. Associated with such a theme, there is an obstacle to achieving communication delay reduction if existing devices are still in use.

Disclosure of Invention

According to an aspect of the present disclosure, there is provided a method comprising: receiving a short transmission time interval direct link configuration and performing direct link transmission/reception with the short transmission time interval direct link configuration.

According to an aspect of the present disclosure, a method is provided that includes providing a short transmission time interval direct link configuration to perform direct link transmission/reception.

According to an aspect of the present disclosure, there is provided a communication device comprising a processor and a memory, the memory comprising processor executable instructions that when executed by the processor perform the method set forth within the disclosed subject matter.

According to an aspect of the disclosure, a non-transitory computer-readable medium is provided having stored thereon processor-executable instructions that, when executed, perform a method.

Drawings

Although the techniques presented herein may be embodied in alternate forms, the specific embodiments shown in the drawings are merely a few examples that supplement the description provided herein. These examples should not be construed in a limiting sense, such as to limit the claims appended hereto.

Fig. 1A is a schematic diagram illustrating a direct link (SL) vehicle-to-all (V2X) communication in which a User Equipment (UE) sends a V2X message to a plurality of UEs.

Fig. 1B is a diagram illustrating V2X communications in which a first UE forwards a V2X message to an evolved universal terrestrial radio access network (E-UTRAN) and the E-UTRAN broadcasts a V2X message to a plurality of UEs.

Fig. 1C is a schematic diagram of V2X communication in which a first UE forwards a V2X message to a roadside unit (RSU), which in turn transmits to an E-UTRAN, which broadcasts a V2X message to multiple UEs.

FIG. 1D is a schematic illustration of V2X communication in which a first UE forwards a V2X message to an E-UTRAN, which in turn transmits to a roadside unit (RSU), which broadcasts a 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 diagram illustrating a through link control information (SCI) transmission mode.

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

Fig. 6 is a schematic diagram of an example UE autonomous PC5 bearer/logical channel setup 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 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 assignment of base station scheduling of sTTI resources.

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

Fig. 12 is a diagram of an example Channel Busy Rate (CBR) report 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 according to one or more of the provisions set forth herein.

Detailed Description

The subject matter now will 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 to be an extensive or detailed discussion of known concepts. Details that are generally known to one of ordinary skill in the relevant art may have been omitted or may be processed in an overview manner.

The following subject matter may be embodied in various forms, such as methods, apparatus, components, and/or systems. Thus, the present subject matter is not intended to be construed as limited to any of the example embodiments set forth herein. Rather, the example embodiments are provided for illustration only. Such embodiments may take the form of, for example, hardware, software, firmware, or any combination thereof.

In this context, it will be appreciated that some examples are presented with the description for one or more User Equipments (UEs) and/or base stations (enbs)/core networks. It will be appreciated that details regarding the UE and base station are not limitations on the disclosed subject matter. By way of example, successive generations of systems, methods, and/or devices (e.g., 5 th generation mobile networks, 5G) may be used with the disclosed subject matter. It is to be understood that these are examples of nodes and that the term node is to be interpreted as including such structures/means and that the term node is to be interpreted as including any other structures/means for implementing the disclosed functions/steps. The node (e.g., UE) may be vehicle-based. In particular, at least some of the nodes (e.g., UEs) may be vehicle-based. However, it will be appreciated that the node (e.g., UE) may not be vehicle-based. In particular, at least some of the nodes (e.g., UEs) may not be vehicle-based.

With the development of fifth generation communication technologies, vehicle-to-vehicle, vehicle-to-infrastructure, and vehicle-to-pedestrian (V2V/V2I/V2P) delays, the higher demand for transmission delays has risen from previous values of 100 milliseconds up to demands for 10 milliseconds or 3 milliseconds. In existing resource assignments in cellular and PC5, User Equipment (UE) direct link control and data information transmission use 1ms Long Term Evolution (LTE) subframes as the basic unit, i.e., subframes within a Transmission Time Interval (TTI). Since vehicle-to-all (V2X) latency requirements are high, the 1ms subframe TTI is difficult to meet the latency requirements of V2X communications.

Short tti (stti) data transmission is introduced in the direct link, which is expected to achieve the goal of reduced latency. For the UE, there are more choices for the resource type. However, the topic of how to allocate resources to UEs in order to achieve better latency performance and provide higher resource efficiency has not yet found an effective solution.

The disclosed subject matter addresses these issues and presents a short TTI based direct link (SL) resource assignment methodology. In one aspect, the disclosed subject matter provides a method comprising: receiving a short transmission time interval direct link configuration and performing direct link transmission/reception with the short transmission time interval direct link configuration. According to another aspect, the present disclosure provides a communication device comprising a processor and a memory, the memory comprising processor-executable instructions that when executed by the processor cause such method(s) to be performed. According to another aspect, the present disclosure provides a non-transitory computer-readable medium having stored thereon processor-executable instructions that, when executed, cause such method(s) to be performed.

As the number of vehicles increases, there is an increasing concern about how to reduce traffic accidents, how to rescue in a timely manner, how to coordinate on-site traffic, and the like. With the development of communication technology and electronic technology, more and more vehicles are equipped with vehicle communication modules. With such a vehicle device, there may be various information exchanges such as accident warning information, traffic condition warning information, and the like. Based on the precash sensing alert system, and by using advanced wireless communication technology, it is expected that real-time information exchange will be achieved between vehicles and roadside units. In addition, such information exchange may inform the other party of the current status (such as vehicle geographical position, speed, acceleration and direction) and road environment information. This is a new way to solve the road traffic safety problem and provide various collision warning information to prevent the occurrence of a road traffic safety accident.

Vehicle-to-all communication (V2X) refers to the use of various communication technologies enabling vehicle-to-vehicle communication (V2V), vehicle-to-pedestrian communication (V2P), vehicle-to-infrastructure communication (V2I), vehicle-to-network communication (V2N).

In general, V2X communication includes three scenarios as shown in FIGS. 1A-1D.

Scene 1, which is appreciated by reviewing fig. 1A, supports SL (through link) V2X communication based on PC 5. The UE transmits the V2X message to a plurality of UEs via a PC5 interface.

Scene 2, which is appreciated by reviewing view 1B, supports V2X communication via Uu. The UE forwards the V2X message to the E-UTRAN, which broadcasts the V2X message to multiple UEs in the local area.

Scene 3 is appreciated by reviewing fig. 1C and 1D. Specifically, scenario 3 may be divided into scenario 3a (FIG. 1C) and scenario 3b (FIG. 1D) that support V2V communications using an E-UTRAN interface and a PC5 interface. In fig. 1C, the UE transmits a V2X message to a UE-type roadside unit (RSU) via a 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 message received from the UE-type RSU to a plurality of UEs in the local area. Alternatively, as shown in 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 transmits the V2X message to a plurality of UEs in the local area through the PC5 interface.

With the development of fifth generation communication technologies, V2V/V2I/V2P traffic has a higher demand for delay from the previous 100 milliseconds to 10 milliseconds, or even 3 milliseconds. In existing cellular and PC5 interface resource assignments, the direct link control and data information transmission of a UE uses a 1ms LTE sub-frame as a basic unit, that is, one sub-frame as a TTI. Due to high vehicle-to-all (V2X) latency requirements, the 1ms subframe TTI is difficult to meet the stringent latency requirements of V2X communications.

Data transmission based on short TTIs is introduced in the direct link, which is expected to achieve the goal of reducing delay. With respect to the UE, it has more resource type choices. However, the topic of how to assign resources to UEs to achieve better latency 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 comprising: receiving a short transmission time interval direct link configuration and performing direct link transmission/reception with the short transmission time interval direct link configuration. Several example embodiments of such methods are provided herein. It is to be understood that the disclosed subject matter is not limited to the examples provided, and that the disclosed subject matter is broader than the examples provided immediately above.

One example embodiment is a direct link (SL) resource pool based on sTTI. Conventional TTIs (legacy TTIs) are typically in units of 1ms subframes. The short TTI introduced in SL can be divided into various types. Each subframe is divided into 6 sTTI, each sTTI containing 2 or 3 orthogonal frequency division multiplexing/single carrier-frequency division multiple access (OFDM/SC-FDMA) symbols. Alternatively, each subframe is divided into two sTTI, each sTTI containing seven OFDM/SC-FDMA symbols. That is, slots based on sTTI. All of the above sTTI types may be present. However, in consideration of practicality and overhead, it is most feasible that each subframe is divided into two sTTI, that is, slots based on sTTI. Therefore, the following description mainly uses a TTI-based slot as an example.

Therefore, as some examples, the short transmission time interval related through-link configuration may include at least one of: a subframe transmission time interval, a slot transmission time interval, or a number of symbols of a transmission time interval. Regarding the number of symbols of the transmission time interval, the number of symbols may be 2, 3, 4, or 7, as some examples.

The SL resources based on sTTI may be multiplexed with the legacy TTI resource pool, and the sTTI SL resource pool may also be designed independently of the legacy TTISL resource pool. The SL resource pool information supporting sTTI further includes: for the support of sTTI SCI resource pool information and/or the support of sTTI data resource pool information, the following three scenarios may be considered.

As one such scenario, sTTI SL resources and legacy TTI resources share the same SCI and data resource pool. For example, sTTI-enabled UEs need to share a resource pool with legacy TTI-based UEs. In this case, one or more sTTI types may be added to support sTTI indication in SL transport resource pool configuration. In addition, the SL transmission resource pool configuration may also carry a subframe bitmap (time domain) corresponding to the sTTI resources and a physical resource block range or sub-band (frequency domain) range corresponding to the sTTI resources. In addition, in the time domain, the SL resource pool configuration may further include sTTI bitmap information within a subframe. Taking the slot-based sTTI as an example, the sTTI bitmap may be 01. This means that slot 1 is used as sTTI resource. On the other hand, if only one sTTI is configured for SL transmission in a subframe, it may be indicated by an sTTI offset in the subframe. If the sTTI offset is set to 0, this means that sTTI resources are present in slot 0 of the subframe.

As another such scenario, the sTTI SL resources and legacy TTI resources share the same data resource pool, but there is an assignment of separate sTTI SL SCI resource pools. In this case, there is one more sTTI SCI resource pool configuration in addition to the original legacy TTI resource pool configuration. The number of SCI resources corresponding to a resource pool is the same as the number of SCI resources of the sTTI data sub-band on the corresponding legacy TTI resource pool. In a specific resource pool configuration, SCI resource pool configuration information based on sTTI may include support for sTTI indication. In this case, one or more sTTI types may be added to support sTTI indication in SL transport resource pool configuration. In addition, the SL transmission resource pool configuration may also carry a subframe bitmap (time domain) corresponding to the sTTI resources and a physical resource block range or sub-band (frequency domain) range corresponding to the sTTI resources. In addition, in the time domain, the SL resource pool configuration may further include sTTI bitmap information within a subframe. Taking the slot-based sTTI as an example, the sTTI bitmap may be 01. This means that slot 1 is used as sTTI resource. On the other hand, if only one sTTI is configured for SL transmission in a subframe, it may be indicated by an sTTI offset in the subframe. If the sTTI offset is set to 0, this means that sTTI resources are present in slot 0 of the subframe.

As another scenario, there may be an independent sTTI SL resource pool configuration. For example, the SL resource pool configuration information based on the sTTI may include an sTTI indication, one or more sTTI types, a time-frequency domain resource location supporting the sTTI indication. The bitmap for indicating the time domain resource location may be in units of sTTI durations. Alternatively, the time domain resource location is still indicated by the subframe based bitmap, but the resource pool configuration requires that the sTTI bitmap information be contained within the subframe. Taking the slot-based sTTI as an example, the sTTI bitmap may be 01. This means that slot 1 is used as sTTI resource. On the other hand, if only one sTTI is configured for SL transmission in a subframe, it may be indicated by an sTTI offset in the subframe. If the sTTI offset is set to 0, this means that sTTI resources are present in slot 0 of the subframe.

The sTTI SL resource pool configuration information may be delivered through SIB messages (as shown in figure 2) or dedicated signaling (as shown in figure 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. The resource pool information of the sTTI SL can also be pre-configured in the UE supporting the sTTI. The UE may receive the above ttl SL resource pool configuration information from a proximity-based service (ProSe) function/V2X control function or connected relay UE. The sTTI SL resource pool configuration information includes one or more SL transmit/receive resource pools that support sTTI configured based on the above information.

In an actual network deployment, it is possible that some base stations support sTTI, and some base stations do not support sTTI. Nevertheless, moving vehicle UEs will suffer service breaks when passing through these areas.

For services such as basic safety V2X, it is proposed that vehicular UEs employ legacy TTI transmissions and that vehicular UEs will receive V2X SL message transmissions over legacy TTIs regardless of whether sTTI is supported. For vehicular UEs that support sTTI SL, the vehicular UE may initiate SL transmissions based on the sTTI in the region where the base station supports sTTI SL resource configurations. If the vehicular UE supporting the sTTI enters the base station region not supporting the sTTI SL transmission, the UE supporting the sTTI should inform the upper layer that the region does not support the sTTI SL transmission and reception. Correspondingly, vehicular UEs supporting sTTI may consider using pre-configured resources. It should be noted that the preconfigured sttil resources may be used by the UE only if the frequency band of the preconfigured sttil resources 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 the preconfigured frequency band (that is, does not interfere with the current base station). Alternatively, or in addition, the upper layer directly stops the transmission of service messages requiring sTTI.

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

Summarizing the example embodiment, in addition to supporting SL resource pool configuration for sTTI in the cell, the base station or cell may transmit inter-cell/inter-frequency/inter-PLMN (public land mobile network) sTTI SL for transmission/reception of resource configuration pool information.

For SL communication, the introduction of sTTI is intended. As such, different SA/SCIs and data transfer types need to be considered. For SCI, the transmission can be divided into the following types:

the first type is when the UE transmits only the SCI based on the legacy TTI. This mode may be backward compatible with UEs using legacy TTIs. As shown in fig. 4A, the legacy TTI UE can correctly analyze SCI information transmitted by the sTTI-based UE.

The second type is when the UE transmits the legacy TTI SCI and the sTTI SCI simultaneously. This mode may be backward compatible with UEs transmitting using legacy TTIs. Meanwhile, as shown in fig. 4B, the sTTI-enabled receiving UE may receive the SCI and corresponding data based on the sTTI, so as to achieve the purpose of reducing the delay.

The third type is when the UE transmits only the sTTI-based SCI. This mode/method is not backward compatible with legacy TTI based UEs. Only the sTTI-enabled receiving UEs may receive sTTI-based SCIs and corresponding data in order to reduce delay. See fig. 4C.

Therefore, the legacy TTI may be considered as the first interval, and the sTTI may be considered as a divided part of the first interval.

As such, according to the disclosed method, transmission time interval resources are selected for communication. The legacy TTI may be selected and may be considered to be the first interval, or the sTTI may be selected and may be considered to be a divided portion of the first interval.

The selecting may include selecting the divided portions of the first interval for communication when there is a capability to perform communication at transmission time intervals at the divided portions of the first interval. The method can include multiplexing communications including communications utilizing a first transmission interval resource and communications utilizing a divided portion of a first transmission interval.

It is to be noted that the method thus comprises providing communication of through link control information. The first transmission time interval (e.g., the legacy TTI) may be used to provide the direct link control information. The through link control information may be provided using the first transmission time interval and using a divided part (sTTI) of the first transmission interval. The through link control information may be provided using a divided portion of the first transmission interval.

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

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

In the second mode, the UE transmits SL data using resources of multiple sttis within the same frequency domain of a given subframe, where the transmission by the UE of the multiple sttis may be multiple retransmissions of the same medium access control protocol data unit (MAC PDU), and may also transmit multiple different MAC PDUs, as shown in fig. 5B.

In the third mode, as shown in fig. 5C, different UEs transmit different MAC PDUs using the sTTI resources, respectively, in the same frequency domain of a given subframe.

The method includes providing communication that provides through link data transfer. The divided part of the first transmission interval may be one of a plurality of divided parts of the first transmission interval. As such, several utilizations for data transmission are possible. As an example, the through-link data transmission occurs using one of the plurality of divided portions of the first transmission interval. As another example, the through-link data transmission occurs using a plurality of the plurality of divided portions of the first transmission interval. As yet another example, the communication provides direct link data transmission to a first UE (e.g., a first node) and direct link data transmission to a second UE (e.g., a second node). For this, through-link data transmission for a first UE (node) may occur using a first of the plurality of divided portions of the first transmission interval, and through-link data transmission for a second UE (node) may 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 freely combined together to form varying combinations. The various combinations may be used in different application scenarios. The following are several example combinations. Of course, the total number of possible combinations is not limited by these examples.

In a first example scenario, the UE transmits only the SCI based on the legacy TTI, and the UE will repeat the transmission of data based on the sTTI using the resources of multiple sTTI in the same subframe. An example of this is a combination of the content shown in fig. 4A and the content shown in fig. 5B. The UE corresponds to data resources indicated by the legacy SCI data sub-band and may retransmit consecutively over multiple sTTI resources to improve sTTI SL transmission reliability.

In a second example scenario, a UE transmits only sTTI SCI, with different UEs transmitting different data over sTTI in the same frequency domain in the same subframe. An example of this is a combination of the content shown in fig. 4C and the content shown in fig. 5C. The combination can make full use of resources, reduce delay, increase transmission opportunities, and alleviate half-duplex problems. However, a UE supporting sTTI in this mode cannot be backward compatible with a UE supporting only legacy TTIs.

In a third exemplary scenario, the UE sends both the legacy TTI SCI and the sTTI SCI. Different UEs transmit different data over multiple sttis in the same frequency domain in the same subframe. Different UEs transmit the legacy TTI SCI on the same legacy TTI resource. Meanwhile, different UEs transmit the sTTI SCI on different sTTI resources, respectively. An example of this is a combination of the content shown in fig. 4B and the content shown in fig. 5C.

As such, it will be appreciated that within the method, communication provides through link control information and through link data transfer. Several possibilities can be utilized. For example, the first transmission time interval may be used to provide the through-link control information, and the divided portion of the first transmission interval may be used to provide the through-link data transmission. As another example, the through-link control information may be provided using a divided portion of the first transmission interval, and the through-link data transmission may be provided using a divided portion of the first transmission interval. As yet another example, the first transmission time interval may be used and the divided portion of the first transmission interval may be used to provide the through-link control information, and the divided portion of the first transmission interval may be used to provide the through-link data transmission.

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

UE TTI type configurations are contemplated and discussed below. For scenarios where sTTI resources and legacy TTI SL resource configurations coexist, the UE may decide to select sTTI resources or legacy TTI resources based on various factors and/or multiple factors. Some example factors that may be considered are presented below.

For example, one factor for selection/determination is the delay requirement. For services with higher delay requirements, it may be considered to transmit using sTTI, otherwise using legacy TTI SL resources. Therefore, within the method, the selection of transmission time interval resources for communication may include a determination of usage delay.

Another example factor that may be used is a decision-based reliability requirement. In particular, some service data transmissions require high reliability and may require transmission using both resources, sTTI and legacy TTI SL. Therefore, in the method, the selection of transmission time interval resources for communication may comprise using a determination of reliability requirements.

Another example factor that may be used is based on packet size determination or determination (e.g., size of packet). In particular, small packets may be more suitable for transmission over sTTI resources, while large packets may be more suitable for transmission over legacy TTI resources. Therefore, in the method, the selection of transmission time interval resources for communication may include a determination based on packet size.

Another example factor that may be used is based on UE capabilities. Only UEs that are enabled for sTTI SL may transmit using sTTI SL resources, otherwise legacy TTI SL resources are used. Therefore, in the method, the selection of transmission time interval resources for communication may comprise a determination of the capacity of the usage node.

Another example factor that may be used is based on resource status. For some packets, if the time of arrival at L2 and the UE scheduling transmission of the packet is close to the PDB (packet delay budget), the UE will look for the earliest available resource to choose. Such as the earliest available resource based on the sTTI SL resource. For such a case, the UE transmits the packet using the sTTI resource. Otherwise the old TTI transport is considered. Therefore, in the method, the selection of transmission time interval resources for communication may include a determination of a status of the usage resources.

Another example factor that may be used is based on a decision on how congested the SL resource pool is. If the legacy TTISL transmission resource pool is not congested (channel busy rate or CBR < system preconfigured threshold 1), the UE may select the legacy TTISL transmission resource for data transmission. If the sTTI SL transport resource pool is not congested (CBR < system preconfigured threshold 2), the UE may select the sTTI SL transport resources for data transmission. Therefore, within the method, the selection of transmission time interval resources for communication may include a determination of a degree of resource pool congestion.

Another example factor that may be used is based on base station configuration. And according to the resources allocated by the base station, if the base station allocates the sTTI resources, the UE uses the sTTI resources for the direct link transmission, otherwise, the old TTI resources are used for the direct link transmission. Therefore, within the method, the selection of transmission time interval resources for communication may comprise a determination based on the configuration of the base station.

The base station may be configured in several ways. The following are several examples of configurations. The base station may configure a mapping between ProSe per packet priority/packet delay budget/quality of service (QoS) class identifier and transmission time interval (PPPP/PDB/QCI and TTI) type. See, for example, fig. 6. The base station may configure a mapping between TTI types and logical channel identities/logical channel group identities. The base station may configure logical channel identification/logical channel group identification and TTI type mapping. The base station may configure a mapping between PPPP and logical channel identity/logical channel group identity. In addition, the base station may also configure the UE with a mapping between packet sizes and TTI types. The base station may also configure whether the packet corresponding to a particular PPPP/logical channel group is allowed to select the most recent TTI type source. Note that TTI types include legacy TTIs and sTTI. Furthermore, sTTI may also be subdivided into TTI types comprising different numbers of symbols. For example, 2, 3, 4, or 7 symbols may be used. The above mapping may be a one-to-many mapping, such as PPPP/PDB/QCI may be mapped to multiple TTI types. For different TTI types, the base station may further configure the priority of the different TTI types for UE resource selection. For mapping between packet sizes and TTI types, the packet size range may correspond to one or more TTI types, with different packet size ranges corresponding to different TTI types. The above information may be obtained from ProSe function/V2X control function or UE pre-configuration information in addition to base station configuration.

Furthermore, the UE may select the sTTI SL resource or the legacy TTI SL resource in view of the following options.

If the non-access stratum (NAS) layer/upper layer configures the AS layer to transport 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 which logical channel/logical channel group the UE should map the packet to based on the PPPP/PDB information carried by the packet and the mapping between the PPPP and the logical channel identity/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 identity/logical channel group identity. If the corresponding logical channel has been established, the UE may determine a TTI type that may be supported corresponding to the SL packet or the mapped logical channel/logical channel group according to the mapping between the logical channel identification/logical channel group identification and the TTI type.

If the NAS layer/upper layer configures the AS layer to transport SL traffic data, the packets from the NAS layer/upper layer carry the following information: PPPP/PDB information. After receiving a packet, the UE AS layer determines which logical channel/logical channel group the packet should be mapped to based on the PPPP/PDB information carried by the packet and the mapping between the PPPP and the logical channel identity/logical channel group identifier received by the UE. The UE then determines whether a corresponding logical channel/logical channel group has been established. The UE may further establish the corresponding logical channel if the corresponding logical channel/logical channel group information has not been established. If the corresponding logical channel has been established, the UE may determine the TTI type that may be supported corresponding to the SL packet transmission or mapped logical channel/logical channel group from the PPPP/PDB and TTI type mapping, as shown in FIG. 6.

If the NAS layer/upper layer configures the AS layer to transport SL traffic 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 the TTI type through which the packet should be transmitted according to the PPPP/PDB information and the packet size carried by the packet, the mapping between the PPPP/PDB QCI and the TTI type acquired by the UE, and the mapping between the packet size and the mapping between the TTI types. The UE then determines which logical channel/logical channel group the packet should be mapped to based on the mapping between TTI type and logical channel identity/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 to autonomously select/base station schedule an appropriate SL resource for data transmission.

In a UE-to-network relay scenario, the remote UE may establish a corresponding PC5 logical channel/bearer from the remote UE's Uu bearer and configure the same QoS parameters. The UE AS layer receives the packet that needs to be transmitted over the SL relay and maps the packet to the PC5 logical channel/bearer corresponding to the Uu bearer of the packet. The UE may then determine the TTI type that the PC5 logical channel/bearer may use for the packet according to the pre-obtained mapping between QCI and TTI types.

If the base station configures the PC5 logical channel/bearer, the base station may transmit PC5 bearer/logical channel configuration information to the UE via Radio Resource Control (RRC) dedicated signaling. In addition to QoS configuration, the PC5 bearer/logical channel configuration information received by the UE includes 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. Data packets mapped to PC5 bearers/logical channels may be transmitted over corresponding one or more TTI type SL resources. Optionally, the UE may transmit the sTTI transmission interest indication, TTI type (e.g., TTI duration), and QoS parameters corresponding to the PC5 bearer/logical channel 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. Referring to fig. 7, and in mind, fig. 7 shows a 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 group can use, the UE determines an available TTI type for the packet to be transmitted according to the PPPP/logical channel group to which the packet is mapped. If the UE also receives a priority configuration corresponding to the TTI type, the UE preferentially selects the TTI type with the higher priority when selecting resources or requesting resources. If available TTI type resources are not available, the priority is selected again, the low TTI type, and so on.

If the UE receives a configuration that a particular PPPP/logical channel group is allowed to select the closest TTI type source, this means that if the time between the arrival of a packet corresponding to the PPPP/logical channel group at layer 2 and the UE scheduling transmission is already close to the PDB, the latest available TTI type resources can be used by the UE and are not restricted by the TTI type corresponding to the PPPP/logical channel group.

There may be a UE sTTI capability report. For a UE in an RRC connected state, the capabilities may be reported to the eNB. The capability report includes the SL TTI indication and one or more SL TTI types supported by the UE. It may also contain information such as: the supported sTTI SCI transmission type, sTTI SL data transmission type and the like of the UE. Assuming that the UE supports multiple TTI types, the base station may then configure the UE with SL transmission/reception resources with the TTI types supported by the UE according to the capability report of the UE. The configuration may be implemented with dedicated signaling. Referring to fig. 8, fig. 8 illustrates an example UE sTTI capability report.

Resource assignment signaling based on sTTI can be provided. For RRC connected UEs supporting sTTI, the direct link resource configuration request information may be sent to the base station. The direct link resource configuration request information may include a SL TTI transmission resource request and a TTI type of the requested resource. After receiving a resource configuration request sent by the UE with the sTTI enabled, the base station sends SL resource configuration to the UE, wherein the configuration comprises SL resource pool information of one or more enabled sTTI supporting the sTTI. For resource assignment scheduled by the base station, the base station transmits a mapping between PPPP/PDB/QCI and TTI type mapping. In addition, the base station can transmit the sTTI SCI transmission type, the sTTI data transmission type. After the UE receives the configuration sent by the base station, it may determine which TTI type the data packet may be transmitted through according to the PPPP/PDB information and the packet size carried by the packet, 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. The UE then determines which logical channel/logical channel group the packet should be mapped to based on the mapping between TTI type and logical channel identity/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 then is used to transmit data based on the appropriate TTI-type SL resource that the UE selects/base station schedules to assign. Referring to, for example, fig. 9 shows an example of signaling flow configured based on sTTI resources.

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

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

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

If the UE receives a configuration where a particular PPPP/logical channel group is allowed to select the most recent TTI type resource, and if the time between the arrival of a packet corresponding to the PPPP/logical channel group at layer 2 and the UE scheduling transmission is already close to the PDB, the TTI type with the most recent SL resources available may be selected by the UE, unrestricted by the TTI type corresponding to the PPPP/logical channel group.

There may be a resource pool selection. After the UE selects the TTI type, the UE selects a corresponding SL transmission resource pool according to the TTI type. If there are multiple SL transmission resource pools corresponding to TTI types, the UE selects the appropriate SL transmission resource pool based on the detected congestion level of the SL transmission resource pools, e.g., prioritizes the SL transmission resource pools that are not congested (CBR < system preconfigured threshold 2). On the other hand, if both the sTTI SL resource pool independent of the legacy TTI SL resource pool and the sTTI SL resource multiplexed with the legacy TTI resource pool are present, then the sTTISL resource pool independent of the legacy TTI SL resource pool is preferred.

There may be a resource selection. Specifically, SL resources corresponding to the TTI type are selected from SL transmission resources randomly or based on the sensing result. In a scenario where legacy TTIs and sTTI share a resource pool, if a UE transmits the sTTI SCI, different UEs may transmit different data over multiple sttis in the same frequency domain in the same subframe (e.g., see fig. 4C and 5C) in order to avoid accurate sensing by UEs that only enable legacy TTIs, the resources over multiple sttis in the same frequency domain should be occupied as fully as possible. For sTTI enabled UEs, resources of sTTI on the same frequency domain of the same subframe that are not sufficiently filled by sTTI UEs should be given priority after sensing the sTTI SL transmission resource pool.

In a scenario where the legacy TTI and sTTI share a resource pool, it is assumed that the UE transmits the legacy TTI SCI and sttici simultaneously, and different UEs transmit different data over multiple sttis in the same frequency domain in the same subframe (e.g., see fig. 4C and 5C). Different UEs simultaneously transmit the legacy TTI SA SCI on the same legacy TTI SCI resource, and simultaneously transmit the sTTI-based SCI and data on separate sTTI resources. In this scenario, if an sTTI-enabled UE monitors the legacy SCI and the corresponding data resource has only a portion of sTT data transmissions in the time domain, this means that the sTTI is not fully occupied. Therefore, the UE selects other unoccupied sTTI resources within the same frequency domain in the same subframe for data transmission.

There may be a package assembly. The MAC layer is responsible for scheduling data packets from the PC5 logical channels/bearers, assembling MAC PDUs. Specifically, the MAC layer schedules data packets from one or more PC5 logical channels/bearers supporting TTI types according to their priority order and assembles them into MAC PDUs. A MAC PDU for sTTI SL transmission may carry sTTI-based Buffer Status Report (BSR) information if the MAC PDU has more room to include sTTI-based Buffer Status Reports (BSRs).

When it comes to data transmission, the following will be noted. To support STTI-based transmission, the 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.

Assuming that the UE is configured to transmit the legacy TTI SCI and the multiple replicated data transmissions for the sTTI using the same frequency domain resources within the same subframe, the reserved bits of the legacy SCI may be used to indicate the data transmission type/retransmission times. In this way, an sTTI-enabled receiving UE may recognize the retransmission of sTTI data within a subframe according to the legacy SCI and perform corresponding decoding.

In addition to UE autonomous resource assignment, the base station may control sTTI SL resource assignment. The base station scheduled sTTI SL resource assignment and the sTTI SL transmission of the UE may be divided into the following procedures.

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

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

With respect to resource assignment scheduled by the base station, if the base station is configured with mapping between logical channel identifications/logical channel group identifications and TTI types, the base station may determine corresponding one or more TTI types to assign corresponding resources according to the logical channel group identifications.

If the UE needs to transmit legacy TTI SCI, sTTI SCI, and sTTI data, the base station will transmit a SL grant to the UE that includes any combination of the following information: legacy TTI SCI resource index/location, sTTI data resource index/location, TTI type indication, and sTTI data start offset. If the UE transmits only legacy TTISCI and sTTI data, the UE includes a TTI type indication and an sTTI data start offset in the legacy SCI.

Considering that the base station can support multiple TTI types, different types of packets for the UE also need to be transmitted over different TTI type resources. The base station may be caused to configure a pool of SL transmission resources scheduled by multiple base stations. These SL transmission resource pools may correspond to different TTI types. In this scenario, when allocating SL resources to a UE, the base station needs to indicate the corresponding TTI type and/or SL transmission resource pool index in the SL grant.

For scenarios where sTTI and legacy TTI share the same resource pool, UEs perform autonomous resource assignment, and a base station schedules resource assignment of the same resource pool, the base station may assign sTTI SL resources to the sTTI-enabled UEs. The eNB may assign sTTI resources within the same frequency domain of the same subframe to multiple UEs that need to transmit data simultaneously. If the eNB cannot find multiple such sTTI-enabled UEs with data to be transmitted over the sTTI, the eNB may instruct the UEs to occupy multiple sTTI resources on the same frequency domain for multiple transmissions within the same subframe in the SL grant. In particular, the eNB may indicate the number of retransmissions over multiple sTTI within a subframe in the SL grant.

For packet assembly, the MAC layer is responsible for scheduling data packets from the PC5 logical channel/bearer, assembling MAC PDUs. Specifically, the MAC layer schedules packets from one or more PC5 logical channels/bearers supporting TTI types according to their priority order and assembles them into MAC PDUs. A MAC PDU for sTTI SL transmission may include an sTTI based BSR if the MAC PDU has more room to include the sTTI based BSR.

When it is time for data transfer, the following discussion is provided. To support sTTI-based transmission, the UE may be configured with different SL SCI/SL data transmission types. As shown in fig. 10, the base station may configure the SCI transmission type and the data transmission type for the UE. As such, the UE needs to transmit according to the transmission type configured by the base station. When an sTTI-enabled UE receives a SL grant, it may determine a corresponding SL transmission resource pool according to the TTI type/resource pool index, and transmit the sTTI SL SCI and data using resources corresponding to the SL transmission resource pool. Assuming that the UE is configured to transmit the legacy-TTI-based SCI and the multiple-duplicate data transmission for the sTTI using the same frequency-domain resources within the same subframe sTTI (see fig. 4A and 5B), the reserved bits in the legacy SCI of the UE transmission may be used to indicate the data transmission type/retransmission number. As such, an sTTI-enabled receiving UE may recognize the retransmission of sTTI data within a subframe according to the legacy SCI and perform corresponding decoding. Again, such an example is shown in fig. 10, and fig. 10 shows an example of sTTI resource assignment scheduled by the base station.

With respect to SPS based on sTTI, the following discussion is provided. As an example, some services require low latency and periodic transmissions. For the sTTI enabled UEs, data for these services may be transmitted over the 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 an sTTI, an old-fashioned TTI, or both. In addition, the UE may report SPS offset and periodicity in sTTI units. Alternatively, if the offset and periodicity are calculated in units of legacy TTIs, then the sTTI index in legacy TTI subframes should be included in the UE assistance information.

After the base station receives the UE assistance information including the SL SPS configuration information, the base station may configure the sTTI-based SPS for the UE. Specifically, the sTTI-based SPS configuration may include at least one of the following information: sTTI indication, TTI type, sTTI periodicity, etc.

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

In legacy TTI based SL designs, the UE may measure SL resource pool resource busy rate and report resource pool congestion status according to eNB configuration. For the shared SL resource pool for both the sTTI and the legacy TTI, some SL transmissions utilize the sTTI as the resource granularity, and some SL transmissions are transmitted with the legacy TTI as the resource granularity. In view of this, in addition to legacy TTI based measurements, sTTI enabled UEs should maintain multiple sets of CBR measurements and sTTI based resource busy rates should be measured.

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

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

Fig. 12 shows an example of the CBR reporting process based on sTTI. First, the base station transmits a measurement configuration based on sTTI. The sTTI-enabled UE receives the configuration, measures sTTI resources, and transmits an sTTI-based SCI (cbr-PSCCH) and a data measurement report (cbr-PSCCH) to the base station.

Fig. 13 presents a schematic architecture diagram 1200 of a base station 1250 that may be used with a UE that uses at least a portion of the techniques provided herein. Such base stations 1250 can vary widely in configuration and/or capability, alone or in combination with other base stations, nodes, terminal units and/or servers and/or the like, to provide services such as at least some of one or more of the other disclosed techniques, scenarios, and/or the like. It is envisaged that the base stations are nodes.

For example, base station 1250 may connect one or more User Equipments (UEs) to a (e.g., wireless) network (e.g., which may be connected and/or include one or more other base stations), such as a Code Division Multiple Access (CDMA) network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an orthogonal FDMA (ofdma) network, a single-carrier FDMA (SC-FDMA) network, and/or the like. The network may implement radio technologies such as universal independent radio access (UTRA), CDMA13000, global system for mobile communications (GSM), evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE802.20, Flash-OFDM, etc. The base station 1250 and/or the network may communicate using a standard such as Long Term Evolution (LTE).

Base station 1250 may include 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 math coprocessors or integrated Graphics Processing Units (GPUs); and/or one or more levels of local cache memory. Base station 1250 may include memory 1202, memory 1202 storing various forms of applications, such as operating system 1204; one or more base station applications 1206; and/or various forms of data, such as database 1208 and/or file systems, etc. The base station 1250 may include various peripheral components, such as a wired and/or wireless network adapter 1214 that may connect to a local area network and/or a 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.

Base station 1250 may include a motherboard that features one or more communication buses 1212, which interconnects processor 1210, memory 1202, and/or various peripherals using various bus technologies, such as variations of the serial or parallel AT attachment (ATA) bus protocol; universal Serial Bus (USB) protocol; and/or a small computer system interface (SCI) bus protocol. In a multi-bus scenario, the communication bus 1212 may interconnect the base station 1250 with at least one other server. Other components that may optionally be included with base station 1250 (but are not shown in diagram 1200 of fig. 13) include: a display; a display adapter, such as a Graphics Processing Unit (GPU); input peripherals such as a keyboard and/or mouse; and/or a flash memory device that may store basic input/output system (BIOS) routines that facilitate directing the base station 1250 to a ready state, among other things.

The base station 1250 may operate in various physical peripherals such as a desktop or tower, and/or may be integrated with a display into an "all-in-one" device. The base station 1250 may be mounted horizontally and/or in a cabinet or rack, and/or may include only one set of components interconnected. Base station 1250 may include a dedicated and/or shared power supply 1218 that supplies and/or regulates power to other components. Base station 1250 can provide power to and/or receive power from another base station and/or server and/or other device. The base station 1250 may include 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 to 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., node) on which at least a portion of the techniques presented herein can be implemented. Such UEs 1350 may vary widely in configuration and/or capabilities to provide various functionality to users. It will be appreciated that the UE may be a node.

The UE 1350 may be provided in various specifications, such as a mobile phone (e.g., a smartphone); a desk or tower workstation; an "all-in-one" device integrated with the display 1308; a laptop, tablet, convertible tablet, or palmtop device; a wearable device, such as may be mounted in a headset, glasses, earpiece, and/or wristwatch, and/or integrated with a piece of clothing and/or a component of a piece of furniture (such as a desktop), and/or another device (such as a vehicle or home). The UE 1350 can serve users in various roles, such as telephone, workstation, kiosk, media player, gaming device, and/or appliance.

UE 1350 may include 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 math coprocessors or integrated Graphics Processing Units (GPUs); and/or one or more levels of local cache memory. UE 1350 may include memory 1301, memory 1301 storing various forms of applications, such as 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 include various peripheral components, such as a wired and/or wireless network adapter 1306 that may connect to a local area network and/or a wide area network; one or more output components, such as a display 1308 (optionally including a Graphics Processing Unit (GPU)) coupled to a display adapter, a sound adapter coupled to speakers, and/or a printer; an input device for receiving input from a 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 position, velocity, and/or acceleration of the UE 1350, a compass, an accelerometer, and/or a gyroscope that detects the physical orientation of the UE 1350. Other components that may optionally be included with the UE 1350 (but are 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 directing the UE 1350 to a ready state, and/or a climate control unit that regulates climate properties, such as temperature, humidity, and airflow, etc.

The UE 1350 may include a motherboard featuring one or more communication buses 1312, the one or more communication buses 1312 interconnecting the processor 1310, the memory 1301, and/or various peripherals using various bus technologies, such as variations of the serial or parallel AT attachment (ATA) bus protocol; universal Serial Bus (USB) protocol; and/or a small computer system interface (SCI) bus protocol. The UE 1350 may include a dedicated and/or shared power supply 1318 that supplies and/or regulates power to other components, and/or a battery 1304 that stores power for use when the UE 1350 is not connected to power via the power supply 1318. 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 of a non-transitory computer-readable medium 1402. Non-transitory computer-readable medium 1402 may include processor-executable instructions 1412 that, when executed by processor 1416 as embodiment 1414, cause at least some of the provisions herein to be performed (e.g., executed by processor 1416). The non-transitory computer-readable medium 1402 may include 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) technology), a platter for a hard disk drive, a flash memory device, or a magnetic or optical disk such as a Compact Disk (CD), a Digital Versatile Disk (DVD), and/or a floppy disk. The example non-transitory computer-readable medium 1402 stores computer-readable data 1404, the computer-readable data 1404 expressing processor-executable instructions 1412 when read 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). In some instances, the processor-executable instructions 1412, when executed, cause operations (such as at least some of the example methods discussed above) to be performed. Example methods include, but are not limited to, the methods shown herein and other methods described.

The following is a list of some abbreviations/definitions used herein:

V2V: vehicle-to-vehicle

V2I: vehicle-to-infrastructure

V2P: vehicle to pedestrian

V2X: vehicle to all

RSU: roadside unit

TTI: transmission time interval

SCI: direct link control information

And SA: scheduling assignment

PDB: packet delay budget

PPPP: per packet priority of PeoSE

3 GPP: third generation partnership project

eNB: E-UTRAN node B, base station

E-UTRAN: evolved universal terrestrial radio access network

RSU: roadside unit

OFDM: orthogonal frequency division multiplexing

SC-FDMA: single carrier-frequency division multiple access

SIB: system information block

MAC PDU: media 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

PC 5: a reference point between ProSe-enabled UEs for control and user plane for ProSe direct discovery, ProSe direct communication and ProSe UE-to-network delay. The lower protocol layer of the PC5 reference point may be based on E-UTRAN direct link capability or WLAN technology.

R15: release 15

PPPP: ProSe per packet priority

And (3) ProSe: proximity-based services

PDB: packet delay budget

PRB: physical resource block

QCI: QoS class identifier

AS: access hierarchy

PDCP: packet data convergence protocol

RLC: radio link control

MAC: media access control

CBR: channel busy rate

BSR: buffer status reporting

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

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

Also, "examples" is used herein to mean serving as an example, illustration, or the like, and does not necessarily mean to be 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 specification are generally to be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form. Furthermore, 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," has, "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., a 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 be construed to imply that these operations are necessarily order independent. Alternative ordering will be appreciated by those 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. Further, it is to be understood that not all operations are necessarily in some embodiments and/or examples.

Further, 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 upon the reading and understanding of this specification and the annexed drawings. The present disclosure includes all such modifications and alterations, and is limited only by the scope of the 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

1. A method, comprising:

receiving a short transmission time interval direct link configuration; and is

Performing through-link transmission/reception with the short transmission time interval through-link configuration.

2. The method of claim 1, wherein the short transmission time interval direct link configuration comprises at least one of: a subframe transmission time interval, a slot transmission time interval, or a number of symbols of a transmission time interval.

3. The method of claim 2, wherein the number of symbols is 2, 3, 4 or 7 with respect to the number of symbols of the transmission time interval.

4. The method of claim 1, wherein the short transmission time interval direct link configuration comprises at least one of:

at least one of a pool of direct link transmission or reception resources having a short transmission time interval configuration;

at least one of an inter-cell/inter-carrier/inter-public land mobile network direct link transmission or reception resource pool with a short transmission time interval configuration; or

The cell/neighbor cell/frequency supports at least one of a short transmission time interval or an indication of supported transmission time interval duration types.

5. The method of claim 4, wherein the at least one of a pool of direct link transmission or reception resources having a short transmission time interval direct link configuration comprises at least one of:

a short transmission time interval direct link indication or one or more direct link transmission time interval types;

short transmission time interval direct link resource bitmap/offset within a subframe; or

Time and frequency domain through link resource indications for short transmission time intervals.

6. The method of claim 5, wherein the through link transmission time interval type comprises at least one of:

a subframe transmission time interval;

a time slot transmission time interval;

a number of symbols of a transmission time interval; or

Subframe transmission time intervals that are considered legacy transmission time intervals and other transmission time interval types that are considered short transmission time intervals.

7. The method of claim 1, wherein a short transmission time interval co-exists in the same pool of through-link resources as an old transmission time interval, and the short transmission time interval through-link configuration comprises at least one of:

a subframe bitmap corresponding to short transmission time interval resources; or

A physical resource block range or sub-band range corresponding to the short transmission time interval resource.

8. The method of claim 1, wherein the short transmission time interval direct link configuration further comprises at least one of:

mapping between logical channel identity/logical channel group identity and transmission time interval type;

mapping between the pro-per-packet priority/packet delay budget/quality of service class identifier and the transmission time interval type;

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

An indication of whether or not the data packet transmission for each packet priority/logical channel group can select the most recent available transmission time interval type resource.

9. The method of claim 1, wherein the receiving comprises at least one of:

a first node receiving a short transmission time interval direct link configuration from a second node;

the first node receiving a short transmission time interval direct link configuration from a proximity-based service function or a vehicle-to-all control function; or

The first node receives a pre-configured short transmission time interval direct link configuration.

10. The method of claim 1, wherein the performing comprises a non-access stratum/upper layer of the first node sending data packets to an access stratum layer with at least one of a direct link transmission indication, a transmission time interval type, or a prose per packet priority/packet delay budget.

11. The method of claim 1, wherein the performing comprises at least one of:

the first node determines the transmission time interval type for data packet transmission according to the logical channel/logical channel group to which the data packet belongs and the mapping between the logical channel identifier/logical channel group identifier and the transmission time interval type;

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

The first node determines a transmission time interval type for transmission of the data packet based on the packet size and a mapping between the packet size and the transmission time interval type.

12. The method of claim 1, wherein the performing comprises:

the first node selecting a direct link resource or receiving a direct link grant for a transmission time interval type from the second node; and is

The first node aggregates medium access control protocol data units with data packets from a logical channel corresponding to the transmission time interval type and delivers the medium access control protocol data units to a lower layer for through link transmission.

13. The method of claim 12, comprising a first node receiving a through-link grant from a second node for the transmission time interval type, wherein the through-link grant comprises at least one of: a short transmission time interval indication; direct link control information resource indication; a direct link data resource indication; straight-through link control information/data short transmission time interval offset; a transmission time interval type; direct link transmission resource pool index; a short transmission time interval data retransmission indication; or the number of short tti data retransmissions.

14. The method of claim 1, wherein the short transmission time interval direct link configuration is selected based on at least one of: delay, reliability requirements, packet size, node capacity, available resource status, determination of resource pool congestion, or configuration of a node.

15. A method, comprising:

a short transmission time interval direct link configuration is provided to perform direct link transmission/reception.

16. The method of claim 15, wherein the short transmission time interval direct link configuration comprises at least one of: a subframe transmission time interval, a slot transmission time interval, or a number of symbols of a transmission time interval.

17. The method of claim 16, wherein the number of symbols is 2, 3, 4 or 7 with respect to the number of symbols of the transmission time interval.

18. The method of claim 15, wherein the short transmission time interval direct link configuration comprises at least one of:

19. The method of claim 18, wherein the at least one of a pool of direct link transmission or reception resources having a short transmission time interval direct link configuration comprises at least one of:

20. The method of claim 19, wherein the through link transmission time interval type comprises at least one of:

a subframe transmission time interval;

a time slot transmission time interval;

a number of symbols of a transmission time interval; or

21. The method of claim 15, wherein a short transmission time interval co-exists in the same pool of through-link resources as an old transmission time interval, and the short transmission time interval through-link configuration comprises at least one of:

22. The method of claim 15, wherein the short transmission time interval direct link configuration further comprises at least one of:

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

23. The method of claim 15, wherein the providing comprises at least one of:

transmitting the short transmission time interval direct link configuration from the second node to the first node such that the first node is provided with the short transmission time interval direct link configuration from a proximity-based service function or a vehicle-to-all control function, or the first node is provided with a preconfigured short transmission time interval direct link configuration.

24. The method of claim 15, wherein the short transmission time interval direct link configuration is selected based on at least one of: delay, reliability requirements, packet size, node capacity, available resource status, determination of resource pool congestion, or configuration of a node.

25. A communication device, comprising:

a processor; and

a memory comprising processor-executable instructions that when executed by the processor cause the method recited in any one of claims 1 to 24 to be performed.

26. A non-transitory computer readable medium having stored thereon processor-executable instructions that, when executed, cause the method recited in any one of claims 1-24 to be performed.