Resource Allocation Based on Short Transmission Time Intervals

Abstract

One or more apparatuses, systems, and / or methods for receiving a short transmission time interval direct link configuration and performing direct link transmission / reception with the short transmission time interval direct 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

Background Art

[0001] With the development of communication technologies, reducing communication latency has always been a concern. However, reducing communication latency generally requires configuring a historical system replacement within different shorter communication frame / subframe configurations. Logically, this will result in existing devices no longer being compatible / feasible. Associated with such a topic, if existing devices are still in use, there are obstacles to achieving communication latency reduction. Summary of the Invention

[0002] According to one aspect of the present disclosure, there is provided a method that includes: receiving a short transmission time interval direct link configuration and performing direct link transmission / reception with the short transmission time interval direct link configuration.

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

[0004] According to one aspect of the present disclosure, there is provided a communication device that includes a processor and a memory, the memory including processor-executable instructions that, when executed by the processor, perform the methods presented within the disclosed subject matter.

[0005] According to one aspect of the present disclosure, there is provided a non-transitory computer-readable medium having processor-executable instructions stored thereon that, when executed, perform a method. Brief Description of the Drawings

[0006] Although the techniques presented herein may be embodied in alternative forms, the specific embodiments shown in the drawings are merely examples that supplement the description provided herein. These embodiments should not be construed in a limiting manner, such as limiting the claims appended hereto.

[0007] Figure 1A is a schematic diagram illustrating direct link (SL) vehicle-to-everything (V2X) communication in which a user equipment (UE) sends V2X messages to multiple UEs.

[0008] Figure 1B is a schematic diagram illustrating V2X communication in which a first UE forwards V2X messages to an evolved universal terrestrial radio access network (E-UTRAN) and the E-UTRAN broadcasts the V2X messages to multiple UEs.

[0009] Figure 1C is a schematic diagram of V2X communication in which a first UE forwards V2X messages to a roadside unit (RSU), the RSU then transmits to the E-UTRAN, and the E-UTRAN broadcasts the V2X messages to multiple UEs.

[0010] Figure 1D It is a schematic diagram of V2X communication in which the first UE forwards V2X messages to E-UTRAN, E-UTRAN then transmits them to a roadside unit (RSU), and the RSU broadcasts the V2X messages to multiple UEs.

[0011] Figure 2 It is a schematic diagram of an example broadcast-based short transmission time interval (sTTI) SL resource pool configuration.

[0012] Figure 3 It is a schematic diagram of an example sTTI SL resource pool configuration based on broadcast and dedicated signaling.

[0013] Figure 4A It is a schematic diagram of a SCI transmission mode in which the UE only sends direct link control information (SCI) based on the legacy TTI.

[0014] Figure 4B It is a schematic diagram of a SCI transmission mode in which the UE simultaneously sends legacy TTI SCI and sTTI SCI.

[0015] Figure 4C It is a schematic diagram of a SCI transmission mode in which the UE only sends SCI based on sTTI.

[0016] Figure 5A It is a schematic diagram of the first mode of data transmission based on sTTI.

[0017] Figure 5B It is a schematic diagram of the second mode of data transmission based on sTTI.

[0018] Figure 5C It is a schematic diagram of the third mode of data transmission based on sTTI.

[0019] Figure 6 It is a schematic diagram of an example UE autonomous PC5 bearer / logical channel establishment and transmission time interval (TTI) type configuration.

[0020] Figure 7 It is a schematic diagram of an example base station controlled PC5 bearer / logical channel establishment and TTI type configuration process.

[0021] Figure 8 It is a schematic diagram of an example UE sTTI capability report.

[0022] Figure 9 It is a schematic diagram of an example sTTI resource configuration signaling process.

[0023] Figure 10 It is a schematic diagram of an example of the assignment of base station scheduling of sTTI resources.

[0024] Figure 11 Schematic diagram of an example SLTS based on sTTI transmission.

[0025] Figure 12 Schematic diagram of an example Channel Busy Ratio (CBR) report based on sTTI.

[0026] Figure 13 Illustrative illustration of a scenario of an example configuration of a Base Station (BS) that can utilize and / or implement at least a portion of the techniques presented herein.

[0027] Figure 14 Illustrative illustration of a scenario of an example configuration of a UE that can utilize and / or implement at least a portion of the techniques presented herein.

[0028] Figure 15 Illustrative illustration of a scenario characterized by an example non - transitory computer - readable medium that provides one or more of those set forth herein. Detailed implementation

[0029] The subject matter will now be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof and illustrate specific example embodiments in an illustrative manner. This description is not intended as an extensive or detailed discussion of known concepts. Details generally known to those of ordinary skill in the relevant art may have been omitted or may be treated in a general manner.

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

[0031] In this document, it will be appreciated that some examples are presented with a description of one or more User Equipment (UE) and / or Base Station (eNB) / Core Network. It will be appreciated that the details regarding the UE and the base station are not limitations on the disclosed subject matter. As an example, successive generations of systems, methods, and / or devices (e.g., 5th Generation Mobile Networks, 5G) may be used with the disclosed subject matter. It is to be understood that these are examples of nodes, and the term node is to be construed to include such structures / devices, and the term node is to be construed to include any other structure / device for implementing the disclosed functions / steps. Nodes (e.g., UE) may be vehicle - based. Specifically, at least some of the nodes (e.g., UE) may be vehicle - based. However, it will be appreciated that nodes (e.g., UE) may not be vehicle - based. Specifically, at least some of the nodes (e.g., UE) may not be vehicle - based.

[0032] With the development of fifth-generation communication technology, the latency of vehicle-to-vehicle, vehicle-to-infrastructure, and vehicle-to-pedestrian (V2V / V2I / V2P) has increased, and the higher demand for transmission latency has risen from the previous value of 100 milliseconds to the requirement for 10 milliseconds or 3 milliseconds. In the existing resource allocation in cellular and PC5, the user equipment (UE) direct link control and data information transmission use 1ms long-term evolution (LTE) subframes as the basic unit, that is, the subframes within the transmission time interval (TTI). Due to the high latency requirements of vehicle-to-everything (V2X), the 1ms subframe TTI is difficult to meet the latency requirements of V2X communication.

[0033] Short TTI (sTTI) data transmission is introduced in the direct link, which is expected to achieve the goal of reducing latency. For the UE, there are more choices for resource types. However, there is no effective solution to the topic of how to allocate resources to the UE to achieve better latency performance and provide higher resource efficiency.

[0034] The disclosed subject matter solves these problems and provides a direct link (SL) resource allocation method based on short TTI. On the one hand, the disclosed subject matter provides a method that includes: 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 that includes a processor and a memory, and the memory includes processor-executable instructions that, when executed by the processor, cause such method(s) to be executed. According to another aspect, the present disclosure provides a non-transitory computer-readable medium having processor-executable instructions stored thereon that, when executed, cause such method(s) to be executed.

[0035] As the number of vehicles increases, people are increasingly concerned about how to reduce traffic accidents, how to rescue in a timely manner, 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 devices, various information exchanges may exist, such as accident warning information, traffic condition reminder information, etc. Based on the precash sensing warning system and by using advanced wireless communication technology, it is expected to achieve real-time information exchange between vehicles and between vehicles and roadside units. In addition, such information exchange may notify the current status of each other (such as vehicle geographical location, speed, acceleration, and direction) and road environment information. This is a new way to solve road traffic safety problems and provide various collision warning information to prevent road traffic safety accidents from occurring.

[0036] Vehicle-to-Everything (V2X) refers to the use of various communication technologies that enable Vehicle-to-Vehicle (V2V) communication, Vehicle-to-Pedestrian (V2P) communication, Vehicle-to-Infrastructure (V2I) communication, and Vehicle-to-Network (V2N) communication.

[0037] Generally speaking, V2X communication includes, for example, Figures 1A - 1D the three scenarios shown below.

[0038] By examining Figure 1A the scenario understood in Figure 1 supports PC5-based SL (Sidelink) V2X communication. The UE sends V2X messages to multiple UEs via the PC5 interface.

[0039] By examining Figure 1B the scenario understood in Figure 2 supports V2X communication via Uu. The UE forwards the V2X message to the E-UTRAN, and the E-UTRAN broadcasts the V2X message to multiple UEs in the local area.

[0040] Scenario 3 is understood by examining Figure 1C and Figure 1D Figure 3. Specifically, Scenario 3 can be divided into Scenario 3a ( Figure 1C ) and Scenario 3b ( Figure 1D ) that support V2V communication using both the E-UTRAN interface and the PC5 interface. In Figure 1C Scenario 3a, the UE sends V2X messages to a 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 message received from the UE-type RSU to multiple UEs in the local area. Alternatively, as Figure 1D shown in Figure 4, the UE forwards the V2X message to the radio access network, and the radio access network transmits the V2X message to one or more UE-type RSUs. The UE-type RSU then sends the V2X message to multiple UEs in the local area via the PC5 interface.

[0041] With the development of the fifth-generation communication technology, V2V / V2I / V2P services have a higher demand for latency, from the previous 100 milliseconds to 10 milliseconds or even 3 milliseconds. In the existing cellular and PC5 interface resource allocation, the sidelink control and data information transmission of the UE use 1ms LTE subframes as the basic unit, that is, one subframe serves as the TTI. Due to the high Vehicle-to-Everything (V2X) latency requirements, the 1ms subframe TTI is difficult to meet the strict latency requirements of V2X communication.

[0042] Data transmission based on short TTI is introduced in the direct link, which is expected to achieve the purpose of reducing latency. Regarding the UE, it has more resource type options. However, there is no effective solution to the topic of how to allocate resources to the UE to achieve better latency performance and provide higher resource efficiency. As mentioned, on the one hand, the disclosed subject matter provides a method that includes: 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 a method are provided herein. It is to be understood that the disclosed subject matter is not limited to the examples provided, and the disclosed subject matter is broader than the examples just provided.

[0043] One example embodiment is a short transmission time interval (sTTI)-based direct link (SL) resource pool. The traditional TTI (legacy TTI) is usually in units of 1 ms subframes. The short TTI introduced in the SL can be divided into various types. Each subframe is divided into 6 sTTIs, and each sTTI contains 2 or 3 orthogonal frequency division multiplexing / single carrier-frequency division multiple access (OFDM / SC-FDMA) symbols. Alternatively, each subframe is divided into two sTTIs, and each sTTI contains seven OFDM / SC-FDMA symbols. That is, the sTTI-based time slot. All of the above sTTI types may exist. However, considering practicality and overhead, each subframe is divided into two sTTIs, that is, the sTTI-based time slot is the most feasible. Therefore, the following description mainly uses the TTI-based time slot as an example.

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

[0045] The sTTI-based SL resources may be multiplexed with the legacy TTI resource pool, and an sTTI SL resource pool independent of the legacy TTI SL resource pool can also be designed. The sTTI SL resource pool information further includes: support for the sTTI SCI resource pool information and / or support for the sTTI data resource pool information, which can consider the following three scenarios.

[0046] As such a scenario, sTTI SL resources and legacy TTI resources share the same SCI and data resource pools. For example, a sTTI-enabled UE needs to share the resource pool with legacy TTI-based UEs. In this case, one or more sTTI types can be added to support sTTI indication in the SL transmission resource pool configuration. Additionally, the SL transmission resource pool configuration can also carry a subframe bitmap (time domain) corresponding to the sTTI resources and a physical resource block range or subband (frequency domain) range corresponding to the sTTI resources. Additionally, in the time domain, the SL resource pool configuration can also include sTTI bitmap information within the subframe. Taking slot-based sTTI as an example, the sTTI bitmap can be 01. This means that slot 1 is used as the 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 that subframe. If the sTTI offset is set to 0, this means that there is an sTTI resource in slot 0 of the subframe.

[0047] As another such scenario, sTTI SL resources and legacy TTI resources share the same data resource pool, but there is a separate allocation of the sTTI SL SCI resource pool. In this case, in addition to the initial 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 the number of SCI resources of the sTTI data subbands on the corresponding legacy TTI resource pool. In a specific resource pool configuration, the sTTI-based SCI resource pool configuration information can include support for sTTI indication. In this case, one or more sTTI types can be added to support sTTI indication in the SL transmission resource pool configuration. Additionally, the SL transmission resource pool configuration can also carry a subframe bitmap (time domain) corresponding to the sTTI resources and a physical resource block range or subband (frequency domain) range corresponding to the sTTI resources. Additionally, in the time domain, the SL resource pool configuration can also include sTTI bitmap information within the subframe. Taking slot-based sTTI as an example, the sTTI bitmap can be 01. This means that slot 1 is used as the 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 that subframe. If the sTTI offset is set to 0, this means that there is an sTTI resource in slot 0 of the subframe.

[0048] As another scenario, there can be a separate sTTI SL resource pool configuration. For example, the sTTI-based SL resource pool configuration information can include an sTTI indication, one or more sTTI types, and the time-domain - frequency-domain resource location that supports the sTTI indication. The bitmap used to indicate the time-domain resource location can be in units of sTTI duration. Optionally, the time-domain resource location is still indicated by a subframe-based bitmap, but the resource pool configuration needs to include the sTTI bitmap information within the subframe. Taking slot-based sTTI as an example, the sTTI bitmap can be 01. This means that slot 1 is used as the 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 that subframe. If the sTTI offset is set to 0, this means that there is an sTTI resource in slot 0 of the subframe.

[0049] The sTTI SL resource pool configuration information can be delivered via an SIB message (as shown in Figure 2 ), or dedicated signaling (as shown in Figure 3 ). Figure 2 An example of a broadcast-based sTTI SL resource pool configuration is shown. Figure 3 An example sTTI SL resource pool configuration based on broadcast and dedicated signaling is shown. The sTTI SL resource pool information can also be pre-configured in a UE that supports sTTI. The UE can receive the above sTTL SL resource pool configuration information from a proximity-based service (ProSe) function / V2X control function or a connected relay UE. The sTTI SL resource pool configuration information includes one or more SL transmission / reception resource pools that support sTTI configured based on the above information.

[0050] In an actual network deployment, it is possible that some base stations support sTTI while some do not. Nevertheless, mobile vehicle UEs will experience service interruptions when passing through these areas.

[0051] For V2X services such as basic safety, it is recommended that vehicle UEs use legacy TTI transmission and that vehicle UEs receive V2X SL message transmissions on legacy TTIs regardless of whether sTTI is supported. For vehicle UEs that support sTTI SL, the vehicle UE may initiate SL transmission based on sTTI in the area where the base station supports sTTI SL resource configuration. If a vehicle UE that supports sTTI enters a base station area that does not support sTTI SL transmission, the UE that supports sTTI shall notify the upper layer that sTTI SL transmission and reception are not supported in this area. Correspondingly, the vehicle UE that supports sTTI may consider using pre-configured resources. It should be noted that pre-configured sTTI SL resources can only be used by the UE when the band of the pre-configured sTTI SL resources is different from the current base station operating band and the current base station does not support the inter-carrier SL resource configuration of the pre-configured band (that is, it does not interfere with the current base station). Alternatively, or in addition, the upper layer directly stops the service message transmission that requires sTTI.

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

[0053] Summarizing this exemplary embodiment, in addition to the SL resource pool configuration that supports sTTI in this cell, the base station or cell may also transmit inter-cell / inter-frequency / PLMN (Public Land Mobile Network) -inter sTTI SL for the transmission / reception of resource configuration pool information.

[0054] For SL communication, it is intended to introduce sTTI. Accordingly, different SA / SCI and data transmission types need to be considered. For SCI, the transmission can be classified into the following types:

[0055] The first type is when the UE only sends SCI based on legacy TTI. This mode can be backward compatible with UEs using legacy TTI. As Figure 4A shown, legacy TTI UEs can correctly analyze the SCI information sent by UEs based on sTTI.

[0056] The second type is when the UE simultaneously sends legacy TTI SCI and sTTI SCI. This mode can be backward compatible with UEs that use legacy TTIs for transmission. At the same time, as Figure 4B shown, the receiving UE enabled for sTTI can receive sTTI-based SCI and the corresponding data in order to achieve the purpose of reducing latency.

[0057] The third type is when the UE only sends sTTI-based SCI. This mode / method cannot be backward compatible with legacy TTI-based UEs. Only the receiving UE enabled for sTTI can receive sTTI SCI and the corresponding data in order to reduce latency. See Figure 4C .

[0058] Therefore, the legacy TTI can be considered as the first interval, and the sTTI can be considered as a divided part of the first interval.

[0059] Accordingly, according to the disclosed method, transmission time interval resources for communication are selected. The legacy TTI can be selected and can be considered as the first interval, or the sTTI can be selected and can be considered as a divided part of the first interval.

[0060] The selection can include selecting a divided part of the first interval for communication when there is the ability to perform communication at a transmission time interval at a divided part of the first interval. The method can include multiplexing communication, which includes communication using the first transmission interval resources and communication using a divided part of the first transmission interval.

[0061] Note that the method thus includes communication for providing direct link control information. The first transmission time interval (e.g., legacy TTI) can be used to provide direct link control information. The first transmission time interval and a divided part of the first transmission interval (sTTI) can be used to provide direct link control information. A divided part of the first transmission interval can be used to provide direct link control information.

[0062] For data transmission in SL communication, only the sTTI-based transmission mode is generally 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:

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

[0064] In the second mode, the UE uses the resources of multiple sTTIs within the same frequency domain of a given subframe to transmit SL data, where the transmissions by the UE over multiple sTTIs can be multiple retransmissions of the same Media Access Control Protocol Data Unit (MAC PDU), and as Figure 5B shown, it can also transmit multiple different MAC PDUs.

[0065] In the third mode, as Figure 5C shown, within the same frequency domain of a given subframe, different UEs respectively use sTTI resources to transmit different MAC PDUs.

[0066] The method includes providing communication that provides sidelink data transmission. A divided part of the first transmission interval can be one of the multiple divided parts of the first transmission interval. Thus, several utilisations for data transmission are possible. As an example, the sidelink data transmission occurs using one of the multiple divided parts of the first transmission interval. As another example, the sidelink data transmission occurs using multiple of the multiple divided parts of the first transmission interval. As yet another example, the communication provides sidelink data transmission to a first UE (e.g., a first node) and provides sidelink data transmission to a second UE (e.g., a second node). For this, the sidelink data transmission for the first UE (node) can occur using the first of the multiple divided parts of the first transmission interval, and the sidelink data transmission for the second UE (node) can occur using the second of the multiple divided parts of the first transmission interval.

[0067] The SL SCI and data transmission methods can be flexible and freely combined together to form varying combinations. The various combinations can be used for different application scenarios. The following are several example combinations. Of course, the total number of possible combinations is not limited by these examples.

[0068] In the first example scenario, the UE only transmits legacy TTI-based SCI, and the UE will use the resources of multiple sTTIs in the same subframe to repeat the transmission of data based on sTTIs. Such an example is a combination of the content shown in Figure 4A and the content shown in Figure 5B . The UE corresponds to the data resources indicated by the legacy SCI data subbands, and can continuously retransmit over multiple sTTI resources to improve the sTTI SL transmission reliability.

[0069] In the second example scenario, the UE only transmits sTTI SCI, and different UEs transmit different data over multiple sTTIs in the same frequency domain of the same subframe. Such an example is a combination of the content shown in Figure 4C and the content shown in Figure 5CA combination of the content shown therein. This combination can make full use of resources, reduce latency, increase transmission opportunities, and alleviate the half-duplex problem. However, a UE that supports sTTI in this mode is not backward compatible with a UE that only supports legacy TTI.

[0070] In a third example scenario, the UE sends both legacy TTI SCI and sTTI SCI. Different UEs transmit different data on multiple sTTIs in the same frequency domain within the same subframe. Different UEs transmit legacy TTI SCI on the same legacy TTI resource. Meanwhile, different UEs transmit sTTI SCI on different sTTI resources respectively. Such an example is Figure 4B the content shown in Figure 5C and the combination of the content shown therein.

[0071] Accordingly, it will be appreciated that within the said method, communication provides sidelink control information and provides sidelink data transmission. Several possibilities can be exploited. For example, a first transmission time interval can be used to provide sidelink control information, and a divided portion of the first transmission interval can be used to provide sidelink data transmission. As another example, a divided portion of the first transmission interval can be used to provide sidelink control information, and a divided portion of the first transmission interval can be used to provide sidelink data transmission. As yet another example, a first transmission time interval and a divided portion of the first transmission interval can be used to provide sidelink control information, and a divided portion of the first transmission interval can be used to provide sidelink data transmission.

[0072] For different application scenarios, the above sTTI-based SLT and data transmission types may coexist. The system should have the ability to configure the SL SCI delivery type, the SL data transfer type, and / or the combination of the SL SCL and data transfer types. The configuration can be a base station configuration, which can be per-cell configuration, or per-resource pool configuration, either per-UE configuration, or per-packet configuration.

[0073] UE TTI type configuration is envisioned and discussed as follows. For scenarios where sTTI resource and legacy TTI SL resource configurations coexist, the UE can decide to select sTTI resources or legacy TTI resources based on various factors and / or multiple factors. Some example factors that can be considered are presented below.

[0074] For example, one factor for selection / determination is the latency requirement. For services with higher latency requirements, using sTTI for transmission can be considered, otherwise using legacy TTI SL resources for transmission. So, within the said method, the selection of the transmission time interval resources for communication can include the determination of using latency.

[0075] Another example factor that can be used is based on the reliability requirements of the decision. Specifically, some service data transmissions require high reliability and may need to use both sTTI and legacy TTI SL resources for transmission. Therefore, within the method, the selection of the transmission time interval resources for communication can include the determination of the reliability requirements.

[0076] Another example factor that can be used is based on the packet size determination or decision (e.g., the size of the packet). Specifically, small packets are more suitable for transmission using sTTI resources, while large packets may be more suitable for transmission via legacy TTI resources. Therefore, within the method, the selection of the transmission time interval resources for communication can include the determination based on the packet size.

[0077] Another example factor that can be used is based on the UE capability. Only UEs enabled with sTTI SL can use sTTI SL resources for transmission, otherwise legacy TTI SL resources are used. Therefore, within the method, the selection of the transmission time interval resources for communication can include the determination of using the node capacity.

[0078] Another example factor that can be used is based on the resource status. For some packets, if the time when the packet arrives at L2 and the UE schedules the transmission of the packet is close to the PDB (packet delay budget), the UE will look for the earliest available resource to select. Such as the earliest available resource based on sTTI SL resources. For such a situation, the UE uses sTTI resources to transmit the packet. Otherwise, consider using legacy TTI delivery. Therefore, within the method, the selection of the transmission time interval resources for communication can include the determination of using the resource status.

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

[0080] Another example factor that can be used is based on the base station configuration. According to the resources assigned by the base station, if the base station assigns sTTI resources, the UE uses sTTI resources for direct link transmission, otherwise legacy TTI resources are used for direct link transmission. Therefore, within the method, the selection of the transmission time interval resources for communication can include the determination based on the configuration of the base station.

[0081] The base station can be configured in several aspects. The following are several examples of the configuration. The base station can configure the mapping between ProSe per-packet priority / packet delay budget / QoS class identifier and the transmission time interval (PPPP / PDB / QCI and TTI) types. See, for example Figure 6 .. The base station can configure the mapping between the TTI type and the logical channel identifier / logical channel group identifier. The base station can configure the mapping between the logical channel identifier / logical channel group identifier and the TTI type. The base station can configure the mapping between the PPPP and the logical channel identifier / logical channel group identifier. Additionally, the base station can also configure the mapping between the packet size and the TTI type for the UE. The base station can also configure whether the packets corresponding to a specific PPPP / logical channel / logical channel group are allowed to select the nearest TTI type source. Note that the TTI types include the legacy TTI and the sTTI. Additionally, the sTTI can be further subdivided into TTI types including different numbers of symbols. For example, 2, 3, 4, or 7 symbols can be used. The above mappings can be one-to-many mappings, such as the PPPP / PDB / QCI can be mapped to multiple TTI types. For different TTI types, the base station can further configure the priority of different TTI types for the UE resource selection. For the mapping between the packet size and the TTI type, the packet size range can correspond to one or more TTI types, and different packet size ranges correspond to different TTI types. In addition to the base station configuration, the above information can also be obtained from the ProSe function / V2X control function or the UE pre-configuration information.

[0082] In addition, the UE can consider the following options to select the sTTI SL resource or the legacy TTI SL resource.

[0083] If the non-access stratum (NAS) layer / upper layer configures the AS layer to transmit the 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 according to the PPPP / PDB information carried in the packet and the mapping between the PPPP and the logical channel identifier / logical channel group identifier received by the UE from the base station. The UE then determines whether the corresponding logical channel / logical channel group has been established. If the corresponding logical channel has not been established, the UE can further establish the corresponding logical channel / logical channel group according to the logical channel identifier / logical channel group identifier. If the corresponding logical channel has been established, the UE can determine the TTI types that can be supported corresponding to the SL packet or the mapped logical channel / logical channel group according to the mapping between the logical channel identifier / logical channel group identifier and the TTI type.

[0084] If the NAS layer / upper layer configures the AS layer to transmit SL communication data, the packet from the NAS layer / upper layer carries the following information: PPPPP / PDB information. After receiving the packet, the UE AS layer determines which logical channel / logical channel group the packet should be mapped to based on the PPPPP / PDB information carried in the packet and the mapping between PPPPP and the logical channel identifier / logical channel group identifier received by the UE. The UE then determines whether the corresponding logical channel / logical channel group has been established. If the corresponding logical channel / logical channel group information has not been established, the UE can further establish the corresponding logical channel. If the corresponding logical channel has been established, as Figure 6 shown, the UE can determine the TTI type that can be supported corresponding to the logical channel / logical channel group for SL packet transmission or mapping based on the PPPPP / PDB and TTI type mapping.

[0085] If the NAS layer / upper layer configures the AS layer to transmit SL communication data, the packet from the NAS layer / upper layer carries the following information: PPPPP / PDB information. After the UE AS layer receives the packet, the UE AS layer determines through which TTI type the packet should be transmitted based on the PPPPP / PDB information carried in the packet, the mapping between the packet size, the PPPPP / PDB QCI and TTI type obtained by the UE, and the mapping between the packet size and TTI type. The UE then determines which logical channel / logical channel group the packet should be mapped to based on the mapping between the TTI type and the logical channel identifier / logical channel group. The UE then determines whether the 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 scheduling for the allocation of appropriate SL resources for data transmission.

[0086] In the UE-to-network relay scenario, the remote UE can establish the corresponding PC5 logical channel / carrier based on the Uu carrier of the remote UE and configure the same QoS parameters. The UE AS layer receives the packet that needs to be relayed through SL and maps the packet to the PC5 logical channel / carrier corresponding to the Uu carrier of the packet. The UE can then determine the TTI type that the PC5 logical channel / carrier can be used for the packet based on the pre-obtained mapping between the QCI and TTI type.

[0087] If the base station configures a PC5 logical channel / carrier, the base station may transmit the PC5 carrier / logical channel configuration information to the UE via radio resource control (RRC) dedicated signaling. In addition to the QoS configuration, the PC5 carrier / logical channel configuration information received by the UE further includes packet data convergence protocol / radio link control / media access control (PDCP / RLC / MAC) configuration, and one or more TTI type information corresponding to the PC5 carrier / logical channel. The data packets mapped to the PC5 carrier / logical channel may be transmitted through the corresponding one or more TTI type SL resources. Optionally, before the UE receives the PC5 carrier / logical channel configuration information sent by the base station, the UE may transmit an sTTI transmission interest indication, a TTI type (e.g., TTI duration), and QoS parameters corresponding to the PC5 carrier / logical channel (such as QCI / PPPP / PDB, etc.) expected to be established. See Figure 7 , and think that Figure 7 illustrates the base station-controlled PC5 carrier / logical channel and TTI type configuration establishment process.

[0088] After receiving the TTI type and priority configuration information that can be used by the PPP / logical channel / logical channel group, the UE determines the available TTI types for transmitting the packets according to the PPP / logical channel / logical channel group to which the packets are mapped. If the UE also receives the priority configuration corresponding to the TTI type, when selecting resources or requesting resources, the UE preferentially selects the TTI type with a higher priority. If the available TTI type resources are unavailable, the priority is selected again, the low TTI type, and so on.

[0089] If the UE receives the configuration that a specific PPP / logical channel / logical channel group is allowed to select the nearest TTI type source, this means that if the time between the arrival of the packets corresponding to the PPP / logical channel / logical channel group at layer 2 and the UE scheduling transmission has approached the PDB, the nearest available TTI type resources may be used by the UE and are not restricted by the TTI type corresponding to the PPP / logical channel / logical channel group.

[0090] There may be a UE sTTI capability report. For a UE in the RRC connected state, the capability may be reported to the eNB. The capability report includes an SL sTTI indication and one or more SL TTI types supported by the UE. It may also contain information such as: the sTTI SCI transmission type supported by the UE, the sTTI SL data transmission type, etc. Assuming that the UE supports multiple TTI types, the base station may then configure the SL transmission / reception resources with the TTI types supported by the UE according to the UE's capability report. This configuration may be implemented using dedicated signaling. SeeFigure 8 , Figure 8 shows an example UE sTTI capability report.

[0091] sTTI-based resource allocation signaling can be provided. For an RRC-connected UE supporting sTTI, the direct link resource configuration request information can be sent to the base station. The direct link resource configuration request information can include an SL sTTI transmission resource request and the TTI type of the requested resource. After receiving the resource configuration request sent by the enabled sTTI UE, the base station sends an SL resource configuration to the UE, which includes one or more enabled sTTI SL resource pool information supporting sTTI. For the resource allocation scheduled by the base station, the base station sends the mapping between PPP / PDB / QCI and the TTI type mapping. In addition, the base station can transmit the sTTI SCI transmission type and the sTTI data transmission type. After the UE receives the configuration sent by the base station, based on the PPP / PDB information carried by the packet and the packet size, the mapping obtained from the base station between PPP / PDB / QCI and the TTI type, and the mapping between the packet size and the TTI type, it can be determined through which TTI type the data packet can be transmitted. The UE then determines to which logical channel / logical channel group the packet should be mapped according to the mapping between the TTI type and the logical channel identifier / 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 uses the appropriate TTI type SL resource based on UE selection / base station scheduled allocation to transmit the data. See, for example Figure 9 , Figure 9 shows an example of the sTTI resource configuration signaling procedure.

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

[0093] There can be a TTI type selection. In the scenario where the UE autonomously selects resources, before the UE schedules the SL packet transmission, the UE determines the TTI type for resource selection according to the configured TTI type corresponding to the PC5 logical channel / carrier / logical channel priority and the priority of the PC5 logical channel / carrier with packet buffering. For example, the TTI type supported by the PC5 logical channel / carrier with a higher priority can be selected.

[0094] Before the UE initiates SL transmission, the UE first determines the PC5 logical channel / logical channel group to be packet buffered scheduled, and then determines which TTI type of resources will be selected according to the corresponding TTI type of the PC5 logical channel / carrier to be scheduled. If the PC5 logical channel / logical channel group to be scheduled supports various TTI types, assuming the UE receives a priority configuration corresponding to the TTI type, the UE selects the TTI type with a higher priority. If the SL resources for the selected TTI type are not available, the TTI type with a lower priority is selected.

[0095] If the UE receives a configuration that a specific PPP / logical channel / logical channel group is allowed to select the nearest TTI type resource, and if the time between the packet arriving at layer 2 and the UE scheduling transmission corresponding to the PPP / logical channel / logical channel group is close to the PDB, the TTI type with the nearest available SL resource can be selected by the UE, regardless of the TTI type corresponding to the PPP / logical channel / logical channel group.

[0096] 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 the TTI type, the UE selects an 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 pools (CBR < the 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 resources multiplexed with the legacy TTI resource pool exist, the sTTI SL resource pool independent of the legacy TTI SL resource pool is preferred.

[0097] There may be resource selection. Specifically, the SL resources corresponding to the TTI type are randomly selected or selected based on the sensing result. In the scenario where the legacy TTI and sTTI share a resource pool, if the UE transmits the sTTI SCI, different UEs can transmit different data on multiple sTTIs in the same frequency domain in the same subframe (for example, see Figure 4C and Figure 5C ) to avoid accurate sensing of UEs that only enable the legacy TTI. The resources on multiple sTTIs in the same frequency domain should be occupied as fully as possible. For UEs that enable sTTI, after sensing the sTTI SL transmission resource pool, the resources of the sTTIs in the same frequency domain of the same subframe that are not fully filled by the sTTI UEs should be given priority.

[0098] In the scenario where the legacy TTI and sTTI share a resource pool, assume that the UE simultaneously sends a legacy TTI SCI and an sTTI SCI, and different UEs transmit different data on multiple sTTIs in the same frequency domain within the same subframe (e.g., see Figure 4C and Figure 5C ). Different UEs simultaneously send legacy TTI SASCI on the same legacy TTI SCI resource, and send sTTI-based SCI and data on independent sTTI resources. In this scenario, if a UE enabled with sTTI monitors the legacy SCI and the corresponding data resource only has a part of the sTT data transmission in the time domain, this means that the sTTI is not fully occupied. Therefore, the UE selects other unoccupied sTTI resources in the same frequency domain within the same subframe for data transmission.

[0099] Packet assembly may exist. The MAC layer is responsible for scheduling data packets from the PC5 logical channel / carrier and assembling the MAC PDU. Specifically, the MAC layer schedules data packets from one or more PC5 logical channels / carriers supporting the TTI type according to the priority order of the logical channels, and assembles them into the 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 the sTTI-based BSR information.

[0100] When it comes to data transmission, the following should be noted. To support sTTI-based transmission, the UE can 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.

[0101] Assume that the UE is configured to use the resources in the same frequency domain within the same subframe to transmit the legacy TTI SCI and multiple replicated data transmissions for sTTI. Then, the reserved bits of the legacy SCI can be used to indicate the data transmission type / retransmission / retransmission times. In this way, the receiving UE enabled with sTTI can identify the retransmission of the sTTI data within the subframe according to the legacy SCI and perform the corresponding decoding.

[0102] In addition to the UE's autonomous resource allocation, the base station can control the sTTI SL resource allocation. The sTTI SL resource allocation scheduled by the base station and the sTTI SL transmission of the UE can be divided into the following processes.

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

[0104] In some scenarios, the base station cannot identify the sTTI type based on the logical channel group identifier. For example, the base station is only configured with a mapping between the packet size and the sTTI type. In this case, the BSR transmitted by the UE may include not only the logical channel identifier / logical channel group identifier, 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 a TTI type resource and may also indicate resources of multiple TTI types at the same time.

[0105] Regarding the resource allocation scheduled by the base station, if the base station is configured with a mapping between a logical channel identifier / logical channel group identifier and a TTI type, the base station may determine one or more corresponding TTI types according to the logical channel group identifier to allocate corresponding resources.

[0106] If the UE needs to transmit legacy TTI SCI, sTTI SCI, and sTTI data, the base station will transmit an SL grant to the UE, where the SL grant includes any combination of the following information: legacy TTI SCI resource index / location, sTTI SCI resource index / location, sTTI data resource index / location, 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.

[0107] Considering that the base station can support multiple TTI types, different types of packets of the UE also need to be sent through different TTI type resources. The base station may be configured with multiple SL transmission resource pools for base station scheduling. These SL transmission resource pools may correspond to different TTI types. In this scenario, when allocating SL resources to the UE, the base station needs to indicate the corresponding TTI type and / or the SL transmission resource pool index in the SL grant.

[0108] For the scenario where sTTI and legacy TTI share the same resource pool, the UE performs autonomous resource allocation, and the base station schedules the resource allocation of the same resource pool, the base station can allocate sTTI SL resources to the UEs enabled with sTTI. The eNB can allocate 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 UEs enabled with sTTI for the data to be transmitted via 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 can indicate the number of retransmissions on multiple sTTIs within the subframe in the SL grant.

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

[0110] When it comes to data transmission, the following discussion is provided. To support sTTI-based transmission, the UE can be configured with different SL SCI / SL data transmission types. As Figure 10 shown, the base station can configure the UE with the SCI transmission type and the data transmission type. Accordingly, the UE needs to perform transmission according to the transmission type configured by the base station. When a UE enabled with sTTI receives an SL grant, it can determine the corresponding SL transmission resource pool according to the TTI type / resource pool index and use the resources corresponding to the SL transmission resource pool to transmit sTTI SL SCI and data. Assume that the UE is configured to use the resources within the same frequency domain of the same subframe sTTI to transmit the legacy TTI-based SCI and the data transmissions for multiple replicas of sTTI (see Figure 4A and Figure 5B ), then the reserved bits in the legacy SCI transmitted by the UE can be used to indicate the data transmission type / retransmission / retransmission times. Accordingly, the receiving UE enabled with sTTI can identify the retransmission of sTTI data within the subframe according to the legacy SCI and perform the corresponding decoding. Again, Figure 10 such an example is shown in Figure 10 and an example of the sTTI resource allocation scheduled by the base station is shown.

[0111] The following discussion is provided regarding sTTI-based SPS. As an example, some services require low latency and periodic transmission. For UEs enabled with sTTI, data for these services can be transmitted via sTTI SL SPS. Specifically, a UE can request an SPS configuration from the eNB via UE assistance information. As Figure 11 shown, the UE can include the sTTI indication and / or TTI type information in the UE assistance information. Specifically, the TTI type information can indicate sTTI, legacy TTI, or both. Additionally, the UE can report the SPS offset and period in units of sTTI. Optionally, if the offset and period are calculated in units of legacy TTI, the sTTI index in the legacy TTI subframe should be included in the UE assistance information.

[0112] After the base station receives the UE assistance information containing the SL SPS configuration information, the base station can configure the UE with sTTI-based SPS. Specifically, the sTTI-based SPS configuration can include at least one of the following information: sTTI indication, TTI type, sTTI periodicity, etc.

[0113] The base station can 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 via the legacy TTI subframe, the SPS activation DCI can include the sTTI offset information and / or the sTTI indication. Upon receiving the SPS activation DCI, the sTTI transmission based on SPS can be performed based on the activated resource location and the SPS configuration sent by the base station.

[0114] In the legacy TTI-based SL design, the UE can measure the SL resource pool resource busy rate and report the resource pool congestion status according to the eNB configuration. For the sTTI and legacy TTI sharing the 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, in addition to the legacy TTI-based measurement, the sTTI-enabled UE should maintain multiple sets of CBR measurements, and the sTTI-based resource busy rate should be measured.

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

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

[0117] Figure 12 An example of CBR reporting processing based on sTTI is shown. First, the base station sends an sTTI-based measurement configuration. The sTTI-enabled UE receives the configuration, measures the sTTI resources, and transmits the sTTI-based SCI (cbr-PSCCH) and data measurement report (cbr-PSSCH) to the base station.

[0118] Figure 13 Schematic architecture diagram 1200 of base station 1250 is presented that can be used with a UE that uses at least a portion of the techniques provided herein. Such a base station 1250 can vary widely in configuration and / or capabilities, either alone or in combination with other base stations, nodes, terminal units, and / or servers, etc., to provide services 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.

[0119] For example, base station 1250 can connect one or more user equipment (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, etc. The network can implement radio technologies 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. Base station 1250 and / or the network can communicate using standards such as long term evolution (LTE).

[0120] 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: multiple cores; one or more coprocessors, such as a math coprocessor or an integrated graphics processing unit (GPU); and / or one or more levels of local cache memory. Base station 1250 may include a memory 1202 that stores 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. Base station 1250 may include various peripheral components, such as wired and / or wireless network adapters 1214 that can be connected 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.

[0121] Base station 1250 may include a motherboard characterized by one or more communication buses 1212 that interconnect the processor 1210, the memory 1202, and / or various peripherals using various bus technologies, such as variants of the serial or parallel AT attachment (ATA) bus protocol; the Universal Serial Bus (USB) protocol; and / or the Small Computer System Interface (SCI) bus protocol. In a multi-bus scenario, the communication buses 1212 may interconnect base station 1250 with at least one other server. Other components that may optionally be included with base station 1250 (but not shown in Figure 13 schematic 1200) include: a display; a display adapter, such as a graphics processing unit (GPU); input peripherals, such as a keyboard and / or a mouse; and / or a flash memory device that may store basic input / output system (BIOS) routines that facilitate booting base station 1250 to a ready state, etc.

[0122] Base station 1250 may operate in various physical enclosures (such as a desktop or a tower), and / or may be integrated with a display as an "all-in-one" device. Base station 1250 may be mounted horizontally and / or mounted in a cabinet or a rack, and / or may include only a set of interconnected components. 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 may supply power to another base station and / or server and / or other device and / or receive power from another base station and / or server and / or other device. Base station 1250 may include a shared and / or dedicated climate control unit 1220 that regulates climate properties (such as temperature, humidity, and / or air flow). Many such base stations 1250 may be configured to and / or adapted to utilize at least a portion of the techniques presented herein.

[0123] Figure 14 FIG. 1300 presents a schematic architecture of a user equipment (UE) 1350 (e.g., a node) on which 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 will be appreciated that a UE may be a node.

[0124] The UE 1350 may be provided in a variety of form factors, such as a mobile phone (e.g., a smart phone); a desktop or tower workstation; an “all-in-one” device integrated with a display 1308; a laptop computer, a tablet, a convertible tablet, or a handheld device; a wearable device, such as one that may be mounted in headphones, glasses, headsets, and / or a wristwatch, and / or integrated with a component of a piece of clothing and / or a piece of furniture (such as a tabletop), and / or another device (such as a vehicle or a residence). The UE 1350 may serve a user in a variety of roles, such as a phone, a workstation, a kiosk, a media player, a gaming device, and / or an appliance.

[0125] The UE 1350 may include one or more (e.g., hardware) processors 1310 that process instructions. The one or more processors 1310 may optionally include: multiple cores; one or more coprocessors, such as a math coprocessor or an integrated graphics processing unit (GPU); and / or one or more levels of local cache memory. The UE 1350 may include a memory 1301 that stores various forms of applications, such as an operating system 1303; one or more user applications 1302, such as a document application, a media application, a file and / or data access application, a communication application (such as a web browser and / or an email client), a utility, and / or a game; and / or drivers for various peripherals. The UE 1350 may include various peripheral components, such as a wired and / or wireless network adapter 1306 connectable to a local area network and / or a wide area network; one or more output components, such as a display 1308 coupled to a display adapter (optionally including a graphics processing unit (GPU)), a sound adapter coupled to a speaker, and / or a printer; input devices 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, a compass, an accelerometer, and / or a gyroscope that detect the location, rate, and / or acceleration of the UE 1350 and / or the physical orientation of the UE 1350. Other components that may optionally be included with the UE 1350 (but Figure 14(not shown in the schematic architecture diagram 1300) includes one or more storage components, such as hard disk drives, solid state storage devices (SSDs), flash memory devices, and / or magnetic and / or optical disk readers, flash memory devices that can store basic input / output system (BIOS) routines that facilitate booting the UE 1350 into a ready state, and / or climate control units that regulate climate properties such as temperature, humidity, and air flow, etc.

[0126] The UE 1350 may include a main board characterized by one or more communication buses 1312 that interconnect the processor 1310, the memory 1301, and / or various peripherals using various bus technologies, such as variants of the serial or parallel AT attachment (ATA) bus protocol; the universal serial bus (USB) protocol; and / or the 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 for other components, and / or a battery 1304 that stores power for use when the UE 1350 is not connected to a power source via the power supply 1318. The UE 1350 may supply power to other client devices and / or receive power from other client devices.

[0127] Figure 15 is an illustrative description of a scenario 1400 that involves an example of a non - transitory computer - readable medium 1402. The non - transitory computer - readable medium 1402 may include processor - executable instructions 1412 that, when executed by a processor 1416 as an embodiment 1414, cause at least some of the provisions herein to be performed (e.g., executed by the processor 1416). The non - transitory computer - readable medium 1402 may include memory semiconductors (e.g., semiconductors utilizing static random access memory (SRAM), dynamic random access memory (DRAM), and / or synchronous dynamic random access memory (SDRAM) technologies), platters of hard disk drives, flash memory devices, or magnetic or optical disks (such as compact discs (CDs), digital versatile discs (DVDs), and / or floppy disks). The example non - transitory computer - readable medium 1402 stores computer - readable data 1404 that, when read 1406 by a reader 1410 of a device 1408 (e.g., the read head of a hard disk drive, or a read operation invoked on a solid - state storage device), represents the processor - executable instructions 1412. 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 and described herein and other methods.

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

[0129] V2V: Vehicle-to-Vehicle

[0130] V2I: Vehicle-to-Infrastructure

[0131] V2P: Vehicle-to-Pedestrian

[0132] V2X: Vehicle-to-Everything

[0133] RSU: Road Side Unit

[0134] TTI: Transmission Time Interval

[0135] SCI: Sidelink Control Information

[0136] SA: Scheduling Assignment

[0137] PDB: Packet Delay Budget

[0138] PPPP: PeoSe Per-Packet Priority

[0139] 3GPP: 3rd Generation Partnership Project

[0140] eNB: E-UTRAN Node B, Base Station

[0141] E-UTRAN: Evolved Universal Terrestrial Radio Access Network

[0142] RSU: Road Side Unit

[0143] OFDM: Orthogonal Frequency Division Multiplexing

[0144] SC-FDMA: Single Carrier - Frequency Division Multiple Access

[0145] SIB: System Information Block

[0146] MAC PDU: Media Access Control Protocol Data Unit

[0147] PLMN: Public Land Mobile Network

[0148] QCI: QoS Class Identifier

[0149] QoS: Quality of Service

[0150] NAS: Non-Access Stratum

[0151] RRC: Radio Resource Control

[0152] PC5: The reference point between the ProSe-enabled UE for control and the user plane for ProSe direct discovery, ProSe direct communication, and ProSe UE-to-network latency. The lower protocol layer of the PC5 reference point can be based on E-UTRAN sidelink capabilities or WLAN technology.

[0153] R15: Release 15

[0154] PPPP: ProSe Per-Packet Priority

[0155] ProSe: Proximity-based Service

[0156] PDB: Packet Delay Budget

[0157] PRB: Physical Resource Block

[0158] QCI: QoS Class Identifier

[0159] AS: Access Stratum

[0160] PDCP: Packet Data Convergence Protocol

[0161] RLC: Radio Link Control

[0162] MAC: Media Access Control

[0163] CBR: Channel Busy Ratio

[0164] BSR: Buffer Status Report

[0165] As used in this application, "component", "module", "system", "interface", etc. generally intend to refer to computer-related entities, either hardware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, executable instructions, execution threads, a program, and / or a computer. For instance, both an application running on a controller and the controller can be components. One or more components can reside within a process and / or execution thread, and a component can be localized on one computer and / or distributed between two or more computers (e.g., nodes (one or more)).

[0166] Unless otherwise specified, "first", "second", etc. are not intended to imply aspects such as time, space, etc. Instead, such terms are only 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.

[0167] Moreover, "example" is used herein to mean serving as an instance, illustration, etc., and does not necessarily mean being advantageous. As used herein, "or" is intended to mean an inclusive "or" rather than an exclusive "or". Additionally, as used in this specification, "a" and "an" are generally interpreted to mean "one or more", unless otherwise specified or clearly intended to be in the singular form from the context. Further, at least one of A and B and / or the like generally means A, or B, or both A and B. Moreover, insofar as "comprising", "having", "including" and / or their variants are used in the detailed description or claims, such terms are intended to be inclusive in a manner similar to the term "including".

[0168] 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 above specific features and acts are disclosed as example forms for implementing at least some of the claims.

[0169] Furthermore, the claimed subject matter can be implemented as a method, apparatus, or article of manufacture by standard programming techniques and / or engineering techniques that use a control computer (e.g., a node) to implement software, firmware, hardware, or any combination thereof for the disclosed subject matter. As used herein, the term "article of manufacture" is intended to encompass a computer program accessible from any computer-readable device, carrier, or medium. Of course, many modifications can be made to the configuration without departing from the scope or spirit of the claimed subject matter.

[0170] Various operations of embodiments and / or examples are provided herein. The order of description of some or all of these operations herein should be interpreted as implying that these operations are necessarily order-independent. Alternative orderings will be appreciated by those skilled in the art to which this description pertains. Additionally, it will be understood that not all operations necessarily exist in every embodiment and / or example provided herein. Moreover, it will be understood that not all operations necessarily occur in some embodiments and / or examples.

[0171] In addition, although the present disclosure has been shown and described with respect to one or more implementations, equivalent changes and modifications will occur to other technicians in the art upon reading and understanding this specification and the drawings. The present disclosure includes all such modifications and changes and is limited only by the scope of the claims. Specifically with respect 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 to any component that performs the specified function of the described component (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structure. Additionally, although a particular feature of the present disclosure may have been disclosed with respect to only one of several implementations, such a feature may be combined with one or more other features of other implementations as may be desired or advantageous for any given or particular application.

Claims

1. A wireless communication method, applied to a first node, includes: Receiving a short transmission time interval direct link configuration, wherein the short transmission time interval direct link configuration includes: A mapping between a logical channel identifier / logical channel group identifier and a transmission time interval type, and At least one of a direct link transmission resource pool and a receiving resource pool having a short transmission time interval configuration; wherein the at least one of the direct link transmission resource pool and the receiving resource pool having a short transmission time interval direct link configuration includes at least one of the following: A short transmission time interval direct link indication or one or more direct link transmission time interval types, A short transmission time interval direct link resource bitmap / offset within a subframe, A time domain and frequency domain direct link resource indication for the short transmission time interval; and Performing direct link transmission / reception using the short transmission time interval direct link configuration, wherein the performing includes the non-access stratum / upper layer of the first node sending a data packet together with at least one of a direct link transmission indication, a transmission time interval type, a per-packet priority / packet delay budget of prose to the access stratum layer.

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

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

4. The method according to claim 1, wherein the short transmission time interval direct link configuration further includes at least one of the following: At least one of an inter-cell / inter-carrier / inter-public land mobile network direct link transmission resource pool or a receiving resource pool having a short transmission time interval configuration; At least one of an indication that a cell / neighbor cell / frequency supports a short transmission time interval or a supported transmission time interval duration type.

5. The method according to claim 1, wherein the direct link transmission time interval type includes at least one of the following: A subframe transmission time interval; A slot transmission time interval; A number of symbols of the transmission time interval; A subframe transmission time interval considered as an old-fashioned transmission time interval and other transmission time interval types considered as short transmission time intervals.

6. The method according to claim 5, wherein the short transmission time interval coexists with the old-fashioned transmission time interval in the same direct link resource pool, and the short transmission time interval direct link configuration includes at least one of the following: A subframe bitmap corresponding to the short transmission time interval resource; A physical resource block range or subband range corresponding to the short transmission time interval resource.

7. The method according to claim 1, wherein the short transmission time interval direct link configuration further includes at least one of the following: A mapping between a per-packet priority / packet delay budget / quality of service class identifier of prose and a transmission time interval type; A mapping between a data packet size and a transmission time interval type; An indication of whether the data packet transmission of each packet priority / logical channel / logical channel group of ProSe can select the resource of the nearest available transmission time interval type.

8. The method according to claim 1, wherein the receiving comprises at least one of the following: The first node receives a short transmission time interval direct link configuration from the second node; The first node receives a short transmission time interval direct link configuration from a proximity-based service function or a vehicle-to-everything control function; The first node receives a pre-configured short transmission time interval direct link configuration.

9. The method according to claim 1, wherein the performing comprises at least one of the following: The first node determines the transmission time interval type for data packet transmission according to the mapping between the logical channel / logical channel group to which the data packet belongs and the logical channel identifier / logical channel group identifier and the transmission time interval type; The first node determines the transmission time interval type for data packet transmission according to the per-packet priority of ProSe of the data packet and the mapping between the ProSe per-packet priority / packet delay budget and the transmission time interval type; The first node determines the transmission time interval type for data packet transmission according to the packet size and the mapping between the packet size and the transmission time interval type.

10. The method according to claim 1, wherein the performing comprises: The first node selects a direct link resource or receives a direct link grant for the transmission time interval type from the second node; And The first node aggregates the media access control protocol data unit and the data packets from the logical channel corresponding to the transmission time interval type, and delivers the media access control protocol data unit to the lower layer for direct link transmission.

11. The method according to claim 10, comprising the first node receiving a direct link grant for the transmission time interval type from the second node, wherein the direct link grant comprises at least one of the following: short transmission time interval indication; direct link control information resource indication; direct link data resource indication; direct link control information / data short transmission time interval offset; transmission time interval type; direct link transmission resource pool index; short transmission time interval data retransmission indication; or short transmission time interval data retransmission count.

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

13. A wireless communication method, applied to a second node, comprising: Providing a short transmission time interval direct link configuration to the first node to perform direct link transmission / reception, Wherein the short transmission time interval direct link configuration comprises: The mapping between the logical channel identifier / logical channel group identifier and the transmission time interval type, and At least one of a direct link transmission resource pool and a reception resource pool having a short transmission time interval configuration; At least one of the direct link transmission resource pool and the reception resource pool having a short transmission time interval direct link configuration includes at least one of the following: A short transmission time interval direct link indication or one or more direct link transmission time interval types; A short transmission time interval direct link resource bitmap / offset within a subframe; A time domain and frequency domain direct link resource indication for a short transmission time interval; and wherein the performing includes the non-access stratum / upper layer of the first node sending a data packet together with at least one of a direct link transmission indication, a transmission time interval type, and a per-packet priority / packet delay budget for prose to the access stratum layer.

14. The method according to claim 13, wherein the short transmission time interval direct link configuration includes at least one of the following: a subframe transmission time interval, a slot transmission time interval, and a number of symbols of the transmission time interval.

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

16. The method according to claim 13, wherein the short transmission time interval direct link configuration further includes: At least one of an inter-cell / inter-carrier / inter-public land mobile network direct link transmission resource pool or reception resource pool having a short transmission time interval configuration; At least one of an indication that a cell / neighbor cell / frequency supports a short transmission time interval or a supported transmission time interval duration type.

17. The method according to claim 13, wherein the direct link transmission time interval type includes at least one of the following: A subframe transmission time interval; A slot transmission time interval; A number of symbols of the transmission time interval; A subframe transmission time interval considered to be an old-fashioned transmission time interval and other transmission time interval types considered to be short transmission time intervals.

18. The method according to claim 17, wherein a short transmission time interval coexists with an old-fashioned transmission time interval in the same direct link resource pool, and the short transmission time interval direct link configuration includes at least one of the following: A subframe bitmap corresponding to the short transmission time interval resource; A physical resource block range or subband range corresponding to the short transmission time interval resource.

19. The method according to claim 13, wherein the short transmission time interval direct link configuration further includes at least one of the following: A mapping between a per-packet priority / packet delay budget / quality of service class identifier for prose and a transmission time interval type; A mapping between a data packet size and a transmission time interval type; An indication of whether a data packet transmission of a per-packet priority / logical channel / logical channel group for prose can select a resource of the nearest available transmission time interval type.

20. The method according to claim 13, wherein the providing includes at least one of the following: Transmit the short transmission time interval direct link configuration from the second node to the first node such that the first node is provided with a short transmission time interval direct link configuration from a proximity-based service function or vehicle-to-everything control function, and the first node is provided with a pre-configured short transmission time interval direct link configuration.

21. The method according to claim 13, wherein the short transmission time interval direct link configuration is selected based on at least one of the following: latency, reliability requirements, packet size, node capacity, available resource status, determination of resource pool congestion, or configuration of the node.

22. A communication device, comprising: a processor; and a memory including processor-executable instructions that, when executed by the processor, cause the method recited in any one of claims 1 to 21 to be performed.

23. A non-transitory computer-readable medium storing processor-executable instructions that, when executed, cause the method recited in any one of claims 1 to 21 to be performed.

Images