Resource configuration and selection for device-to-device links

Abstract

Methods, systems, and devices for resource configuration and selection for device-to-device links in mobile communication technologies are described. An exemplary method for wireless communication includes: receiving, by a wireless device, a configuration of multiple resource pools associated with a carrier set from a network node, selecting resources from the multiple resource pools based on the configuration, and performing device-to-device link communication using the resources. Another exemplary method for wireless communication includes: receiving, by a wireless device, a configuration of multiple resource pools associated with a carrier set from a network node, receiving dedicated resources from the network node, and performing device-to-device link communication using the dedicated resources.

Description

Technical Field

[0001] The present application relates generally to wireless communications. Background Art

[0002] Wireless communication technologies are driving the world towards an increasingly connected and networked society. The rapid growth of wireless communications and technological advances have led to greater demands for capacity and connectivity. Other aspects such as energy consumption, equipment cost, spectrum efficiency, and latency are also important to meet the needs of various communication scenarios. Compared with existing wireless networks, next-generation systems and wireless communication technologies need to provide support for more users and devices, as well as support for higher data rates, requiring user equipment to implement resource configuration and selection for device-to-device links. Summary of the invention

[0003] The present application relates to methods, systems and devices for generating sequences for reference signals in mobile communication technologies, including fifth generation (5G) and new radio (NR) communication systems.

[0004] In one exemplary aspect, a wireless communication method is disclosed. The method includes receiving, by a wireless device from a network node, a configuration of a plurality of resource pools associated with a set of carriers, selecting resources from the plurality of resource pools based on the configuration, and performing device-to-device link communication using the resources.

[0005] In another exemplary aspect, a wireless communication method is disclosed. The method includes receiving, by a wireless device from a network node, a configuration of a plurality of resource pools associated with a set of carriers, receiving dedicated resources from the network node, and performing device-to-device link communication using the dedicated resources.

[0006] In yet another exemplary aspect, the above method is embodied in the form of processor executable code and stored in a computer readable program medium.

[0007] In yet another exemplary embodiment, a device configured or operable to perform the above method is disclosed.

[0008] The above-mentioned aspects and other aspects and their implementations are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 An example of V2X device-to-device communication and discovery is shown.

[0010] Figure 2 Examples of a base station (BS) and a user equipment (UE) in wireless communications according to some embodiments of the disclosed technology are shown.

[0011] Figure 3An example of a dedicated resource pool configuration is shown.

[0012] Figure 4 An example of a UE being controlled simultaneously by a group head UE and a gNB is shown.

[0013] Figure 5 An example of UEs being simultaneously controlled by multiple group head UEs is shown.

[0014] Fig. 6A and Figure 6B An example of a wireless communication method according to some embodiments of the disclosed technology is shown.

[0015] Figure 7 is a block diagram representation of a portion of an apparatus according to some embodiments of the disclosed technology. DETAILED DESCRIPTION

[0016] The demand for the fourth generation of mobile communication technology (4G), long term evolution (LTE), advanced long term evolution (LTE-Advanced / LTE-A) and fifth generation of mobile communication technology (5G) is increasing. From the current development trend, 4G and 5G systems are studying the features that support enhanced mobile broadband, ultra-high reliability, ultra-low latency transmission and massive connections.

[0017] V2X is a predefined communication protocol and data exchange standard. It can be implemented in multiple scenarios, including vehicle-to-vehicle (V2V), vehicle-to-pedestrian (V2P), and vehicle-to-infrastructure (V2I), and is capable of performing wireless communications and information exchange. Based on V2X technology, vehicles can operate in safer driving conditions, are able to better navigate through traffic, and provide better convenience and entertainment to their passengers.

[0018] Currently, there are various V2X technologies, including C-V2X based on LTE technology and DSRC-V2X based on Wi-Fi technology. For C-V2X, current implementations deploy user equipment (UE) communications on a device-to-device link (also known as a side link), where data traffic is not routed from the eNB and core network, but is transmitted directly from the source UE to the target UE. This V2X communication method is called PC5-based V2X or V2X sidelink communication, such as Figure 1 shown.

[0019] As technology and the automation industry advance, the use cases for V2X communications are expanding, and performance requirements are becoming more stringent. Advanced V2X services can be categorized into the following types: vehicle platooning, extended sensors, semi-autonomous or fully autonomous driving, and remote driving. To achieve better performance, the supported packet size ranges from 50 bytes to 12,000 bytes, the supported transmission rate ranges from 2 messages per second to 50 messages per second, the supported end-to-end latency ranges from 3ms to 500ms, the supported transmission reliability ranges from 90% to 99.999%, the supported data rate ranges from 0.5Mbps to 1000Mbps, and the supported transmission range is between 50 meters and 1000 meters.

[0020] Embodiments of the disclosed technology provide methods and systems for carrier selection and reselection, resource pool selection and reselection, and resource selection and reselection. Figure 2 An example of a wireless communication system (e.g., an LTE, 5G, or New Radio (NR) cellular network) is shown that includes a BS 220 and one or more user equipment (UE) 211, 212, and 213. In some embodiments, an uplink transmission (231, 232, 233) includes an identification of the UE, which is received by the BS 220, which transmits (241, 242, 243) a configuration of multiple resource pools that may be used by the UE for subsequent communications. The UE can be, for example, a smartphone, a tablet, a mobile computer, a machine-to-machine (M2M) device, a terminal, a mobile device, an Internet of Things (IoT) device, etc.

[0021] This application uses section headings and subheadings to facilitate understanding, rather than limiting the scope of the disclosed techniques and embodiments to certain sections. Therefore, embodiments disclosed in different sections can be used together. In addition, this application uses examples from 3GPP new radio (NR) network architecture and 5G protocols only to facilitate understanding, and the disclosed techniques and embodiments can be implemented in other wireless systems using communication protocols different from 3GPP protocols.

[0022] Overview of Sidelink Resource Configuration and Selection

[0023] In some existing implementations (e.g., TS 36.321), the UE performs carrier selection (reselection) before normal V2X sidelink communication. In other existing implementations (e.g., Rel-15 V2X), PC5 carrier aggregation is supported and the UE is able to select multiple carriers.

[0024] For carrier selection (reselection), the MAC entity should first determine whether there is cached data in each logical channel. For a carrier associated with each logical channel, if its channel occupancy rate (CBR) is lower than threshCBR-FreqReselection corresponding to the priority level associated with each logical channel, the carrier can be regarded as a candidate carrier for the corresponding logical channel. If carrier reselection is triggered by the MAC entity, for each logical channel for transmitting cached data, if the CBR is lower than threshCBR-FreqKeeping associated with the priority corresponding to the logical channel, it will select the carrier and its associated resource pool. Otherwise, for each carrier configured by the higher layer, if the CBR is lower than threshCBR-FreqReselection corresponding to the priority level associated with the logical channel, the carrier can be regarded as a candidate carrier. If there are multiple carriers in the candidate carrier set, for each logical channel for transmitting cached data, it will select one or more carriers in the order of CBR from low to high. The number of selected carriers is based on the UE implementation.

[0025] In some embodiments, the carrier selection mechanism in LTE V2X depends on two factors: (1) the set of available carriers bound to the service type for the transmitted data, and (2) a comparison between the CBR measurement and the configured CBR thresholds associated with different priority levels.

[0026] In some embodiments, there may be multiple configured mode 2 resource pools for each selected carrier. The UE may also select a resource pool for subsequent resource selection. For example, if zoneConfig is present in the configuration, the UE should use its geographic location to select an appropriate resource pool. Otherwise, the UE may select a resource pool with reference only to the synchronization resource type.

[0027] After the carrier selection and resource pool selection are completed, the UE shall perform resource selection based on its own transmission period, number of retransmissions, number of subchannels and other parameters. Next, the UE can select an appropriate MCS. The UE can then forward the configured sidelink grant, HARQ information, and priority of the logical channels involved to the HARQ entity. The sidelink HARQ entity shall retrieve the MAC PDU from the MAC entity after each subframe and each sidelink process. The HARQ entity shall then forward the MAC PDU, sidelink grant, and HARQ information to each sidelink process and instruct the sidelink process to initiate sidelink transmission. In addition, during sidelink transmission, the sidelink process should also consider the impact of UL / SL priority. If there is a conflict between UL transmission and SL transmission, the sidelink process shall determine whether the sidelink priority is high enough to allow transmission.

[0028] In some embodiments, the allocated UL / SL grants cannot usually support all data transmissions for each logical channel. Therefore, the UE should respect the priority levels between each logical channel to perform multiplexing and assemble the MAC PDU. For each logical channel, a guaranteed data rate can be defined. Only when each logical channel can meet the guaranteed data rate can additional resources be allocated through different priorities. In NR, and based on various transmission durations and service types, after the UE receives the UL grant, LCP can be divided into the following two steps:

[0029] 1) The UE shall determine which logical channel shall use the grant, where each logical channel shall be linked to one or more of a set of allowed subcarrier spacing, a maximum PUSCH duration, an indication of which configured grant type can be used for which transmission, or a set of serving cells.

[0030] 2) The UE should be concerned with how to allocate resources among those eligible logical channels.

[0031] Exemplary Embodiments for Sidelink Resource Configuration and Selection

[0032] According to the techniques of this disclosure, an exemplary embodiment for sidelink resource configuration and selection includes the following steps:

[0033] 1) The UE may report its identity indication to the gNB via sidelinkUEInformation.

[0034] a) In some embodiments, the identity indication may be a one-bit field that informs the gNB that it is a special UE. If the UE is a special UE, this bit will be set to 1; otherwise, if it is a normal UE, it will be set to 0.

[0035] b) In other embodiments, the identity indication may be an optional field. For example, if the UE is a special UE, this field will appear in the sidelinkUEInformation; otherwise, if it is a normal UE, this field will not appear in the sidelinkUEInformation.

[0036] In some embodiments, the UE may report at least one of the following via sidelinkUEInformation:

[0037] a) Request for dedicated multicast resources,

[0038] b) the size of the resource pool requested, and

[0039] c) Multiple scheduled UEs.

[0040] 2) After reporting the identity indication, the special UE will receive a dedicated resource pool configuration from the gNB, which will not overlap with the normal Mode 2 resource pool. An example of a resource pool configuration is Figure 3 shown.

[0041] In some embodiments, the dedicated resource pool configuration may include at least one of the following:

[0042] οgNB id, to indicate which gNB provides this resource pool configuration

[0043] o Time domain indication of resource location

[0044] o Frequency domain indication of resource location

[0045] o Number of sub-channels

[0046] οResource reservation period

[0047] οTransmission parameters

[0048] οReceiving parameters

[0049] ο CBR configuration with different packet priorities

[0050] oSR and / or BSR resource sets

[0051] In some embodiments, for e.), f.) may also be configured by a special UE. In an example, the gNB may indicate whether the UE has the right to configure e.) and f.). In some embodiments, the indication may be:

[0052] a) Implicit; if the gNB does not configure the transmission parameters and / or reception parameters, the particular UE knows that it needs to configure them itself.

[0053] b) Explicit; the gNB can set switches to control whether a specific UE has the right to configure these parameters.

[0054] In some embodiments, parameters e.) and f.) may be configured by both the gNB and the specific UE. In an example, the gNB may provide a suggested range of values, and the specific UE may then further configure the exact value within the range.

[0055] In some embodiments, the special UE may be a group head UE or a relay UE. In an example, the special UE indication should include a destination ID and a propagation type indication.

[0056] 3) In some embodiments, and in this step, the UE may provide Mode 2 resource pool information to other UEs for their autonomous resource selection and / or scheduled resource selection in the following two scenarios:

[0057] a) In the sidelink relay scenario, the UE should be in coverage and can forward the Mode 2 resource configuration broadcast by the SIB (received from the gNB) to other UEs that are out of coverage or in poor coverage. These UEs can use the resource pool for transmission and reception.

[0058] b) In a multicast scenario, the UE is the group head UE, and the gNB allocates a specific resource pool only for the group. The group head UE forwards the resource pool configuration to other member UEs. Then, the member UEs and the group head UE share the same resource pool.

[0059] In some embodiments, the group head UE may indicate a set of dedicated resources for member UEs, which are allocated for SR and / or BSR transmissions from the member UEs toward the group head UE. The member UEs will sense the available SR and / or BSR resources in the resource pool and send SR and / or BSR to the group head UE.

[0060] In some embodiments, if a member UE is controlled by a gNB that is different from the gNB of the group head UE, the member UE shall report the resource pool configuration provided by the group head UE to its gNB.

[0061] In some embodiments, if a member UE is controlled by multiple group head UEs, the member UE should report the resource pool configuration provided by one of its group head UEs to other group head UEs. Figure 5 As shown, the gNB of each group head UE may be different.

[0062] In some embodiments, when a member UE receives multiple sidelink grants from multiple group head UEs or gNBs, and these sidelink grants are on the same frequency and overlap in the time domain, the UE should retain only one sidelink grant based on the packet priority levels of different data services.

[0063] In some embodiments, Figure 4 As shown, the group head UE may indicate a group of dedicated resources to the member UEs for use in a unicast connection between the group head UE and each member UE.

[0064] In some embodiments, the UE may provide such mode 2 resource pool information via multicast communication, and / or establish PC5 RRC connections with other UEs respectively, and then send the mode 2 resource pool information via PC5 RRC dedicated signaling.

[0065] Example of NR V2X carrier selection

[0066] Unicast scenario: 1) The NAS layer may configure a mapping relationship between each destination ID and a carrier set (which is referred to as a potential carrier set).

[0067] 2) After a unicast connection is established between two UEs, the two UEs may negotiate (transmit from UE2 to UE1, or from UE1 to UE2) a carrier set to use from a potential carrier set based on at least one of the following information:

[0068] o Frequency band combining capability between two UEs.

[0069] οSynchronization carrier and synchronization resource type.

[0070] ο Packet priority or service type priority.

[0071] o CBR of each carrier.

[0072] oQoS requirements, such as data rate or data reliability.

[0073] The above parameters are used for transmission and reception of other services simultaneously with the carrier.

[0074] Multicast scenario: 1) The NAS layer may configure a mapping relationship between each destination ID and a carrier set (which is referred to as a potential carrier set).

[0075] 2-1) In some embodiments, the group head may be responsible for carrier selection.

[0076] 2-2) In other embodiments, the gNB may be responsible for carrier selection based on the information reported by the group header, and then configure the selected carrier set for the group head UE. The information reported by the group header should include at least one of the following:

[0077] o Based on its sensed CBR measurement or CBR measurement results reported by other member UEs.

[0078] ο Packet priority for multicast services.

[0079] oQoS requirements, such as data rate and data reliability.

[0080] o The frequency band combination capability reported by each of its member UEs.

[0081] 3) When packet replication is activated by the group head, the group head shall forward the mapping relationship between each LCID and its associated carrier set to its member UEs via multicast communication or PC5-RRC dedicated signaling. In some embodiments, the group member that activates packet replication shall forward the mapping relationship between each LCID and its associated carrier set to its group head UE and other member UEs via multicast communication.

[0082] Example of NR V2X resource pool selection

[0083] 1) In Mode 2, the UE may select resources from one or more resource pools based on the amount of data it has buffered and at least one of the following parameters configured or preconfigured by the gNB:

[0084] οRegional location information

[0085] οComparison between CBR and CBR threshold with different packet priorities

[0086] οSynchronize resource types

[0087] οPropagation Type

[0088] οQoS requirements such as data rate and data reliability

[0089] 2) In a multicast scenario, the group head can select at least one resource pool and, after establishing a PC5 connection with each of its member UEs, forward the resource pool information to its member UEs through multicast communication or PC5-RRC dedicated signaling.

[0090] 3) In some embodiments, the V2X UE may be configured with multiple types of resources, which may include at least one of the following:

[0091] οNR configured authorization type 1,

[0092] οNR configured authorization type 2,

[0093] o Mode 1 resource pool, from which the gNB will allocate resources to the UE,

[0094] o Mode 2 resource pool, where the UE will autonomously select resources from the resource pool,

[0095] o a mode 2 resource pool, wherein the UE can use resources from the resource pool to schedule the mode 2 UE,

[0096] o a dynamic resource pool from which the UE can perform a one-time transmission using resources,

[0097] οSPS resource pool, where the UE can use resources from the resource pool to perform SPS scheduling.

[0098] In some embodiments, the resource pool configuration may include at least one of the following parameters:

[0099] οResource cycle

[0100] ο Resource Timing Offset

[0101] οLocation of resources in the time domain

[0102] οLocation of resources in the frequency domain

[0103] ο Antenna port configuration of resources

[0104] οThe MCS range allowed when using resources

[0105] οIndication of whether the current resource pool is allowed to sense

[0106] ο CBR thresholds with different packet priorities / packet delay budgets

[0107] In some embodiments, for each type of resource, the gNB may determine whether to allow the use of the content specified in its configuration. In an example, the configuration may be defined as follows.

[0108] οThe gNB can configure a resource type list, which will include all available resource types that the gNB can configure for the UE.

[0109] o The gNB can configure a list of resource types and use a bitmap to indicate these available resource types that the gNB can configure for the UE.

[0110] o For each type of resource, the gNB may use a Boolean parameter to indicate whether the use of each type of resource is allowed, even if it has already been configured.

[0111] o Implicitly, the gNB has no configuration for a specific type of resources.

[0112] 4) In some embodiments, the NR V2X UE may use the abnormal resource pool according to the configuration of the gNB in ​​at least one of the following scenarios:

[0113] o When the SPS service of the UE and the service data of the one-time transmission are in different resource pools and the one-time transmission has completed short sensing, if the SPS sensing result is unavailable, the UE may be allowed to use the one-time transmission resource pool for SPS service transmission.

[0114] o When the UE is configured with a configured grant type 1 and a configured grant type 2, and RLF is detected, the UE may be allowed to transmit aperiodic data traffic with the configured grant type 1 or the configured grant type 2.

[0115] o In some embodiments, both configured grant types may be configured to the UE at the same time, and in those scenarios:

[0116] The gNB transmits DCI to the UE and there is a unified index to indicate which configured grant is activated

[0117] The gNB shall configure the UE with different SL-CS-RNTIs, e.g. SL-CS-RNTI1 for configured grant type 1 and SL-CS-RNTI2 for configured grant type 2

[0118] o When the sensing result of the UE is not available in the mode 2 resource pool, in this case, the UE is allowed to use the configured grant type 1 or the configured grant type 2. In addition, when the mode 1 resource of the UE is temporarily unavailable, the UE is allowed to use the mode 2 dynamic resource pool.

[0119] For these scenarios, the UE may also be configured with an abnormal resource pool of Mode 1 or Mode 2. In addition, the UE may be configured with an abnormally configured grant.

[0120] Example of NR V2X resource selection

[0121] Broadcast scenario: When the UE's MAC entity is performing resource selection or reselection, it shall consider the following factors and report to lower layers:

[0122] 1) The MAC entity of the UE shall select a set of sidelink resources based on the sensing results, which sidelink resources correspond to different beam directions of beam scanning for one MAC PDU transmission. When ARQ is supported, the retransmission resources should be a set of sidelink resources corresponding to different beam directions, which can be used for beam scanning.

[0123] 2) To support beam scanning, the UE should be configured with a data burst period for sidelink communication through the gNB, which indicates the time length of one round of beam scanning.

[0124] 3) In order to configure the number of beams used for transmission, the UE should be configured with the data block number.

[0125] 4) Alternatively, the data block number and data burst period may be configured with multiple combinations corresponding to the same data burst but for different subcarrier spacings and different data SPS period configurations.

[0126] 5) Alternatively, the UE may request resources corresponding to:

[0127] οSpecific TX profiles

[0128] οScheduling mode

[0129] Whether the resource is configured with authorization type 1 or authorization type 2

[0130] 6) Alternatively, when the UE receives a gNB activation or deactivation of a certain configured grant type 2 resource, it may send a Grant Confirm MAC CE configured by the SL. An example MAC CE may include:

[0131] οCorresponding LCID

[0132] o One or more configured Grant Type 2 indexes

[0133] Multicast scenario: When the UE's MAC entity is performing resource reselection, it shall consider the following factors and report to lower layers:

[0134] 1) If the UE is a group head UE, it should first sense the positions of all its member UEs and select a set of beam directions based on the position information, and then use the resources corresponding to the selected beams for data packet transmission.

[0135] 2) To support beam scanning, the UE should be configured with a data burst period from the gNB for sidelink communication, which indicates the length of time for one round of beam scanning.

[0136] 3) In order to configure the number of beams used for transmission, the UE should be configured with the data block number.

[0137] 4) Alternatively, the data block number and data burst period may be configured with multiple combinations corresponding to the same data burst but for different subcarrier spacings and different data SPS period configurations.

[0138] Unicast scenario: During sidelink discovery, since the transmitter and receiver can negotiate the transmission beam, there is no need to introduce beam scanning in unicast. When the UE's MAC entity performs resource reselection, it should consider the following factors and report to the lower layer:

[0139] 1) The UE shall select a sidelink grant based on the sensing result for one MAC PDU transmission. If the service is SPS, the UE shall select an SPS resource grant.

[0140] Example of NR V2X Logical Channel Priority (LCP)

[0141] 1) The MAC entity shall perform the following logical channel priority procedure for each SCI corresponding to a new transmission in the V2X sidelink communication:

[0142] The MAC entity shall select a logical channel that satisfies the following requirements for each SL grant:

[0143] o If the allowed carrier set is configured, the allowed carrier set associated with the selected logical channel shall include the carrier associated with the SL grant.

[0144] o If allowed RAT types are configured, the allowed RATs associated with the selected logical channel shall include the RAT associated with the SL grant.

[0145] o If allowed spreading types are configured, the spreading type associated with the selected logical channel shall be the same as, or shall include, the spreading type associated with the SL grant.

[0146] o If allowed resource types are configured, the allowed resource types associated with the logical channel shall include the resource types associated with the SL grant.

[0147] οIf the allowed SCS or SCS list is configured, the SCS or SCS list associated with the selected logical channel should be the same as, or should include, the SCS or SCS list associated with the SL authorization.

[0148] 2) For connected UEs, the following methods can be used to handle the mapping between QoS and logical channels:

[0149] a) In some embodiments, the UE may report QoS flow information and characteristics to the gNB. The UE may then be configured with various SL logical channels and SDAP mapping rules.

[0150] In the example, the UE can report the service mode and related QoS parameters to the gNB, as well as the SidelinkUEInformation used. Then, the UE can be configured with different logical channels through the gNB.

[0151] In another example, the configuration may include a mapping between QoS indexes to specific logical channels and a mapping between logical channels and logical channel groups.

[0152] In yet another example, for each logical channel, the gNB may further configure the available SCS, the maximum PSSCH duration, whether the configured grant type 1 is allowed on the logical channel, whether the configured grant type 2 is allowed on the logical channel, and whether mode 1 and / or mode 2 are allowed on the logical channel. In addition, an indication of whether duplication can be activated when using the logical channel may be configured. If this indication is configured, the gNB shall configure two carrier sets.

[0153] In yet another example, for each sidelink logical channel, it may be bound to at least one of the following parameters:

[0154] οPriority level

[0155] ο Allowed SCS or list of SCS

[0156] o Allowed carrier set

[0157] ο Types of dissemination permitted

[0158] ο Allowed RAT (Radio Access Technology) types

[0159] οThe types of resources allowed

[0160] o Scheduling modes, which can be mapped to different logical channel groups

[0161] o Indication of whether dynamic scheduling is allowed on this logical channel

[0162] b) In some embodiments, the UE may utilize the auxiliary information configured by the gNB to map the QoS flow to different parameters to create corresponding logical channels and perform SDAP mapping. In an example, the auxiliary information may include at least one of the following:

[0163] οMapping relationship between PDB and maximum PSSCH duration and SCS;

[0164] o Thresholds for priority levels or PDBs, which are used to determine the mapping between priority levels and different resource types

[0165] o Thresholds for packet error rate (PER) or reliability level, which are used to determine the triggering of RLC AM and / or PDCP duplication

[0166] οMapping between LCGID and priority level

[0167] οMapping between LCGID and scheduling mode

[0168] In an example, the gNB may configure only the mapping between LCGID and QoS for Mode 1 services, or it may configure only the mapping between LCGID and QoS for Mode 2 services.

[0169] Based on the auxiliary information, the UE can map different QoS flows to the corresponding maximum PSSCH duration, SCS and resource type, and determine whether to trigger RLC AM, packet duplication, mode 1 or mode 2. The UE can then create the associated logical channel and perform SDAP mapping. In addition, when the UE reports the BSR, it should report additional information such as SCS and maximum PSSCH duration. In some embodiments, the following alternatives may be followed:

[0170] o The UE may include the SCS and maximum PSSCH duration indication in the BSR by adding additional fields.

[0171] οUE can configure the mapping relationship between LCGID and SCS, and / or the mapping relationship between LCGID and maximum PSSCH duration, and report it to gNB in ​​advance.

[0172] o For each connected UE, the gNB may configure the mapping between LCGID and QoS index with a granularity of each destination ID.

[0173] c) In some embodiments, the gNB may configure a mapping relationship between VQI (PDB or priority level) and corresponding PDCP / RLC / MAC parameters. Based on the QoS characteristics reflected in the higher layers from the data packet, the UE may use the corresponding PDCP / RLC / MAC parameters. In an example, the parameter may be at least one of the following:

[0174] οPDCP: Discard Timer / statusReportRequired / PDCP-SN-Size / DataSplitThreshold / statusPDB-Periodicity / t-Reordering / rn-IntegrityProtection / DataSplitDRB / DataSplitThreshold / outofOrderDelivery / pdcp-DuplicationSRB

[0175] οRLC:t-PollRetransmit / pollPDU / pollByte / maxRetxThreshold / t-Reordering / t-StatusProhibit / am-WithShortSN / um-WithShortSN / um-WithLongSN

[0176] οMAC:LCP-Restriction / recommendedBitRate / logicalChannelSR-DelayTimer / multipleSR-Configurations / multipleConfiguredGrants

[0177] Example of uplink / sidelink priority

[0178] When the UE has concurrent one or more SL grants and one or more UL grants for transmission, and if using all grants exceeds the UE's capability, the UE shall follow the SL / UL priority to use some grants.

[0179] 0) Priority rules between NR UL and NR SL. If the sidelink logical channels are configured with different priorities, such as NR Uu logical channel priorities, then:

[0180] a) Directly compare the priority between SL MAC PDU and UL MAC PDU (the priority will be that of the highest priority logical channel)

[0181] b) If the priority of SL MAC PDU or SL LCH is greater than or equal to the threshold, the gNB will configure the threshold of SL logical channel and then SL MAC PDU transmission will be prioritized; otherwise, UL MAC PDU transmission will be prioritized.

[0182] c) The gNB shall configure a PC5 QFI list; if the list includes the QFI of the SL MAC PDU, the SL MAC PDU transmission will be prioritized; otherwise, the UL MAC PDU transmission will be prioritized. In some embodiments, based on the mapping between SLRB / SL LCH and QFI, the UE will know how to use a specific SL LCH to transmit data with the corresponding QFI. In addition, based on whether the SL MAC PDU includes data for a specific SL LCH, the UE will know whether the SL MAC PDU includes data for a QFI in the configured QFI list.

[0183] d) If the SL LCH is associated with a 5QI / VQI / QoS index, the gNB shall configure a 5QI list. In this case, if the SL MAC PDU includes data corresponding to a 5QI in the configured list, the SL MAC PDU transmission will be prioritized.

[0184] 1) Priority rules in cross-RAT use cases.

[0185] a) Considering the priority between NR UL and LTE SL, the gNB will configure the PPPP threshold of LTE SL. In this case, if the PPPP of the current SL MAC PDU is higher than the threshold, the SL MAC PDU transmission will be prioritized; otherwise, the UL MAC PDU transmission will be prioritized.

[0186] b) When priority issue occurs between NR UL, LTE SL and NR SL transmissions (considering that LTE SL and NR SL will be non-co-channel, if NR UL will be co-channel with NR / LTE SL, then this issue will only occur in case of priority between NR UL and LTE / NR SL), then the gNB shall configure thresholds for NR SL and LTE SL. If both NR SL and LTE SL transmissions can be prioritized, then IDC issue will be encountered.

[0187] c) When a priority issue arises between NR UL, LTE SL and NR SL transmissions (considering that LTE SL and NR SL will be non-co-channel, if NR UL will be co-channel with NR / LTE SL, then this issue only occurs in the case of priority between NR UL and LTE / NR SL), and if the UE is able to complete the transmission, then, based on condition b), the UE will also transmit the SLMAC PDU.

[0188] d) Considering the priority between LTE UL and NR SL, the eNB can configure the transmission criteria of NR SL, which is similar to condition a), or the eNB can configure the mapping between Uu logical channel priority and NR sidelink logical channel priority / PC5 5QI / QoS index.

[0189] 2) Priority rules in dual connectivity scenarios. In some cases, the UE can be connected to both the MeNB and the SgNB and can also perform SL transmission. Here, if there is a transmission conflict between UL (LTE UL or NR UL) and SL (LTE SL or NR SL), as described above, the gNB can configure the transmission criteria for LTE SL or NR SL, or the MN can configure a different SL transmission criteria compared to the SL transmission criteria configured by the SN.

[0190] 3) Priority rules in dual-mode transmission (e.g., Mode 1 and Mode 2). Since both Mode 1 SL V2X transmission and UL transmission are scheduled by gNB, only Mode 1 SL transmission and Mode 2 SL transmission will conflict with each other. In this case:

[0191] a) The gNB can explicitly indicate which mode has a higher priority.

[0192] b) The gNB shall configure a list of 5QI / VQI / QoS indexes for Mode 2; if a Mode 2 SL MAC PDU contains data for 5QI in the configured list, Mode 2 SL transmission shall be prioritized; otherwise, Mode 1 SL transmission shall be prioritized.

[0193] c) The UE can directly compare the 5QI / VQI / QoS / default packet priority between Mode 1 transmission and Mode 2 transmission.

[0194] 4) If the priority rule for frequency switching gap is not configured.

[0195] Here, the gNB may configure thresholds for SL QoS and / or packet priority level and / or packet delay budget. The QoS of SL traffic above the threshold indicates that SL priority is higher than UL priority.

[0196] In another example, considering that SL traffic can be further divided into LTE V2X and NR V2X, if LTE V2X traffic and NR V2X traffic overlap, and when SL has a higher transmission priority level, the UE should compare the QoS of LTE V2X and NR V2X.

[0197] In yet another example, the gNB may configure an inter-RAT QoS priority list to indicate the overall QoS priority level for both NR V2X and LTE V2X.

[0198] 5) Priority rules when gaps are configured to span RAT frequencies. Here, the UE can decide its transmission and reception based on one of the following priority lists:

[0199] a) Uu transmission / reception for RACH

[0200] b) Inter-RAT V2X for transmission

[0201] c) Non-RACH Uu transmission / intra-RAT V2X transmission

[0202] d) Inter-RAT V2X for reception

[0203] e) Non-RACH Uu reception / intra-RAT V2X reception

[0204] In some embodiments, inter-RAT and intra-RAT are compared with the RAT used for random access.

[0205] In other embodiments, non-RACH Uu transmission and intra-RAT V2X transmission, as well as non-RACH Uu reception and intra-RAT V2X reception, should follow SL and UL priorities.

[0206] In some other embodiments, the gNB may configure a threshold for the SL QoS and / or the packet priority level and / or the packet delay budget. Here, when the QoS of the SL service is higher than the threshold, the SL priority is higher than the UL priority.

[0207] In some embodiments, for NR V2X, the gNB may configure multiple resource types (including LTE SL resource configuration) for the UE. For the configured grant type 1, the configuration may include periodicity, timing offset, time domain resource location, frequency domain resource location, antenna port, MCS, TB size, Tx resource pool, V-CS-RNTI, is_sensing_enabled, and allowed QoS index / VQI / PDB list. For the configured grant type 2, the configuration may include periodicity, Tx resource pool, V-CS-RNTI, allowed QoS index / priority / VQI / PDB list. For the scheduled resources, the configuration may include V-RNTI, MCS, Tx resource pool (e.g., sync, SCS), mapping between LCG and allowed QoS index / priority / VQI / PDB / SCS, allowed QoS index / VQI / PDB list. For mode 2a resources, the configuration may include Tx resource pool, sensing configuration, priority of CBR-Tx parameter configuration, allowed QoS index / VQI / PDB list. For mode 2d resources, the configuration may include IsMode2d allowed.

[0208] In some embodiments, the following additional configurations may be supported:

[0209] o Inter-carrier resource allocation

[0210] οPC5 carrier selection related configuration

[0211] οPDCP replication related configuration

[0212] οLTE SL resource configuration

[0213] οV2X related system information update

[0214] Another embodiment of the disclosed technology can be described as:

[0215]

[0216]

[0217]

[0218] Exemplary Methods of the Disclosed Technology

[0219] Fig. 6A An example of a wireless communication method 600 for resource configuration and selection of a device-to-device link in a mobile communication technology is shown. The method 600 includes, at step 602, receiving, by a wireless device, a configuration of a plurality of resource pools associated with a set of carriers from a network node.

[0220] The method 600 includes, at step 604, selecting a resource from a plurality of resource pools based on the configuration. The method 600 includes, at step 606, performing a device-to-device link communication using the resource.

[0221] Figure 6B Another example of a wireless communication method 610 for resource configuration and selection of a device-to-device link in a mobile communication technology is shown. The method 610 includes, at step 612, receiving, by a wireless device, a configuration of a plurality of resource pools associated with a set of carriers from a network node.

[0222] The method 610 includes, at step 614, receiving dedicated resources from a network node. The method 610 includes, at step 616, performing device-to-device link communication using the dedicated resources.

[0223] Some embodiments and techniques related to methods 600 and 610 may be described using the following clause-based description.

[0224] 1. A method for wireless communication, comprising: receiving, by a wireless device, a configuration of a plurality of resource pools associated with a carrier set from a network node; selecting resources from the plurality of resource pools based on the configuration; and performing device-to-device link communication using the resources.

[0225] 2. A method for wireless communication, comprising: receiving, by a wireless device, a configuration of a plurality of resource pools associated with a carrier set from a network node; receiving dedicated resources from the network node; and performing device-to-device link communication using the dedicated resources.

[0226] 3. A method according to clause 1 or 2, comprising: transmitting, by the wireless device to the network node, a resource configuration request associated with the wireless device itself.

[0227] 4. A method as described in clause 3, wherein the configuration includes at least one of a UE ID, a list of quality of service (QoS) of ongoing services, a list of frequencies of interest for reception, a list of frequencies of interest for transmission, a UE type, a type of radio access technology (RAT) that the wireless device can use for transmission, a resource type, an indication of whether the service is periodic, the service periodicity, a logical channel identification of the UL transmission, or a service mode.

[0228] 5. A method as described in clause 3, wherein the configuration includes a UE ID.

[0229] 6. The method of clause 3, wherein the configuration includes a quality of service (QoS) list of ongoing services.

[0230] 7. A method according to clause 3, wherein the configuration comprises a list of frequencies of interest for reception.

[0231] 8. A method according to clause 3, wherein the configuration comprises a list of frequencies of interest for transmission.

[0232] 9. A method as described in clause 3, wherein the configuration includes a UE type.

[0233] 10. A method as described in clause 3, wherein the configuration includes a type of radio access technology (RAT) that the wireless device can use for transmission.

[0234] 11. The method of clause 3, wherein the configuration includes a resource type.

[0235] 12. A method as described in clause 3, wherein the configuration includes an indication of whether the service is periodic.

[0236] 13. The method of clause 3, wherein the configuration comprises a service cycle.

[0237] 14. A method as described in clause 3, wherein the configuration comprises a logical channel identification or a traffic pattern for UL transmissions.

[0238] 15. The method of clause 3, wherein the configuration comprises a business mode.

[0239] 16. A method according to clause 1 or 2, wherein the configuration includes at least one of: a set of allowed carriers for device-to-device link communication for NRRAT, a set of allowed carriers for device-to-device link communication for LTE RAT, transmission parameters associated with different packet priorities, synchronization resource types for each carrier, resource pool configuration, mapping between logical channel groups and QoS indices, mapping between data rates and different numbers of subchannels, packet duplication thresholds associated with packet error rates, mapping between scheduling modes and QoS indices, SL-CS-RNTI associated with configured grant type 1, SL-CS-RNTI associated with configured grant type 2, or mapping between VQI and corresponding PDCP, RLC or MAC parameters.

[0240] 17. A method as described in clause 1 or 2, wherein the configuration includes a set of allowed carriers for device-to-device link communication of the NR RAT.

[0241] 18. A method as described in clause 1 or 2, wherein the configuration comprises a set of allowed carriers for device-to-device link communications of an LTE RAT.

[0242] 19. A method according to clause 1 or 2, wherein the configuration comprises transmission parameters associated with different packet priorities.

[0243] 20. A method as described in clause 1 or 2, wherein the configuration comprises a synchronization resource type for each carrier.

[0244] 21. A method according to clause 1 or 2, wherein the configuration includes a resource pool configuration.

[0245] 22. A method according to clause 1 or 2, wherein the configuration comprises a mapping between logical channel groups and QoS indices.

[0246] 23. A method according to clause 1 or 2, wherein the configuration comprises a mapping between data rates and different numbers of sub-channels.

[0247] 24. A method according to clause 1 or 2, wherein the configuration includes a packet duplication threshold associated with a packet error rate.

[0248] 25. A method according to clause 1 or 2, wherein the configuration comprises a mapping between scheduling modes and QoS indices.

[0249] 26. A method as described in clause 1 or 2, wherein the configuration includes a SL-CS-RNTI associated with the configured Grant Type 1.

[0250] 27. A method as described in clause 1 or 2, wherein the configuration includes a SL-CS-RNTI associated with the configured grant type 2.

[0251] 28. A method as described in clause 1 or 2, wherein the configuration includes a mapping between VQI and corresponding PDCP, RLC or MAC parameters.

[0252] 29. A method as described in clause 16 or 28, wherein the corresponding PDCP parameters include at least one of the following: discard timer, statusReportRequired, PDCP-SN-Size, DataSplitThreshold, statusPDB-Periodicity, t-Reordering, rn-IntegrityProtection, DataSplitDRB, DataSplitThreshold, outofOrderDelivery or pdcp-DuplicationSRB.

[0253] 30. A method as described in clause 16 or 28, wherein the corresponding RLC parameter comprises at least one of: t-PollRetransmit, pollPDU, pollByte, MaxRetxtThreshold, t-Reordering, t-StatusProhibit, am-WithShortSN, um-WithShortSN or um-WithLongSN.

[0254] 31. A method according to clause 16 or 28, wherein the corresponding MAC parameters include at least one of: LCP-Restriction, recommendedBitRate, logicalChannelSR-DelayTimer, multipleSR-Configurations or multipleConfiguredGrants.

[0255] 32. A method according to clause 16, wherein the transmission parameters associated with different packet priorities include at least one of: a range of applicable modulation and coding schemes (MCS), a range of applicable numbers of subchannels, a number of retransmissions, or a maximum allowed transmission power.

[0256] 33. A method as claimed in any of clauses 16 to 28, wherein the transmission parameters associated with different packet priorities comprise a range of applicable modulation and coding schemes (MCS).

[0257] 34. A method as claimed in any one of clauses 16 to 28, wherein the transmission parameters associated with different packet priorities comprise a range of applicable numbers of sub-channels.

[0258] 35. A method according to any of clauses 16 to 28, wherein the transmission parameters associated with different data packet priorities include a number of retransmissions.

[0259] 36. A method according to any of clauses 16 to 28, wherein the transmission parameters associated with the different data packet priorities include a maximum allowed transmission power.

[0260] 37. A method according to clause 16, wherein the resource pool configuration includes at least one of the following: resource type, resource periodicity, resource timing offset, time domain resource location, frequency domain resource location, antenna port configuration of resources, or an indication of whether the current resource pool is allowed to perform sensing.

[0261] 38. A method according to any one of clauses 16 to 28, wherein the resource pool configuration includes resource types.

[0262] 39. A method according to any one of clauses 16 to 28, wherein the resource pool configuration includes resource periodicity.

[0263] 40. A method as claimed in any one of clauses 16 to 28, wherein the resource pool configuration comprises a resource timing offset.

[0264] 41. A method as described in any one of clauses 16 to 28, wherein the resource pool configuration comprises time domain resource locations.

[0265] 42. A method as described in any one of clauses 16 to 28, wherein the resource pool configuration comprises frequency domain resource locations.

[0266] 43. A method as described in any of clauses 16 to 28, wherein the resource pool configuration comprises an antenna port configuration of resources.

[0267] 44. A method as described in any one of clauses 16 to 28, wherein the resource pool configuration includes an indication of whether the current resource pool is allowed to perform sensing.

[0268] 45. A method according to clause 4 or 37, wherein the resource type includes at least one of the following: NR configured authorization type 1, NR configured authorization type 2, mode 1 resources, mode 2 resources, dynamic resources or SPS resources.

[0269] 46. ​​A method as described in clause 1 or 2, wherein selecting resources from the plurality of resource pools is further based on an amount of buffered data of at least one carrier in the set of carriers.

[0270] 47. A method as described in clause 16, wherein selecting a resource having a certain number of sub-channels is based on a mapping between a configured data rate and a number of sub-channels.

[0271] 48. The method of clause 1, wherein the communication is capable of supporting a specific propagation type.

[0272] 49. The method of clause 48, wherein the particular broadcast type is groupcast, and wherein the wireless device is a group head user equipment (UE) for a plurality of UEs.

[0273] 50. A method as described in clause 49, further comprising receiving a configuration of resource configurations from a plurality of resource pools from a network node; and transmitting the resource configurations to a plurality of UEs.

[0274] 51. A method as described in clause 49, further comprising reporting to a network node assistance information for a resource request used for device-to-device communication between the wireless device and a plurality of UEs.

[0275] 52. The method of clause 50, the assistance information comprising at least one of: a CBR measurement for each selected carrier, a QoS requirement for the multicast service, a band combining capability of the wireless device and the plurality of UEs, or a number of UEs in the group.

[0276] 53. A method as described in clause 50, wherein the auxiliary information comprises a CBR measurement for each selected carrier.

[0277] 54. The method of clause 50, wherein the auxiliary information comprises QoS requirements for the multicast service.

[0278] 55. The method of clause 50, the assistance information comprising frequency band combination capabilities of the wireless device and the plurality of UEs.

[0279] 56. A method as described in clause 50, wherein the assistance information comprises a number of UEs in the group.

[0280] 57. The method of clause 48, further comprising determining a plurality of locations for each of a plurality of UEs; and selecting a set of beam directions for transmitting configuration and data services based on the plurality of locations and a plurality of signal strengths, wherein each of the plurality of signal strengths is associated with a particular beam direction.

[0281] 58. A method according to clause 49 or 50, wherein the configuration includes being able to provide at least one of: an identification of a group head user equipment of multiple resource pools, a time domain indication of a resource location, a frequency domain indication of a resource location, and a transmission parameter.

[0282] 59. A method according to clause 49 or 50, wherein the configuration comprises an identification of a group head user equipment capable of providing a plurality of resource pools.

[0283] 60. A method as described in clause 49 or 50, wherein the configuration comprises a time domain indication of a resource location.

[0284] 61. A method as described in clause 49 or 50, wherein the configuration comprises a frequency domain indication of resource locations.

[0285] 62. A method according to clause 49 or 50, wherein the configuration comprises transmission parameters.

[0286] 63. A method as described in clause 58, wherein the transmission parameters include at least one of: a range of applicable MCSs, a range of applicable numbers of subchannels, a number of retransmissions, or a maximum allowed transmission power.

[0287] 64. A method as described in clause 3 or 49, wherein the reported information comprises resource configuration, and wherein the group head UE is capable of transmitting the reported information to a plurality of UEs.

[0288] 65. A method as described in clause 48, further comprising selecting Mode 2 resources from a plurality of resource pools; and transmitting a configuration of the Mode 2 resources to a plurality of UEs.

[0289] 66. A method as described in clause 50 or 65, wherein the configuration is transmitted over a PC5 Radio Resource Control (RRC) connection.

[0290] 67. A method as described in clause 2, wherein the resource pool is a Mode 1 resource pool, and wherein selecting a resource is further based on an indication from a network node.

[0291] 68. The method of clause 1, wherein the resource pool is a Mode 2 resource pool, and wherein selecting a resource is performed autonomously by the wireless device.

[0292] 69. A method according to clause 1 or 2, wherein the configuration of multiple resource pools includes at least one of the following: resource periodicity, resource timing offset, resource location in the time domain, resource location in the frequency domain, antenna port configuration of resources, or a modulation and coding scheme (MCS) range allowed when using resources.

[0293] 70. A method as described in clause 1 or 2, wherein the configuration of the plurality of resource pools includes resource periodicity.

[0294] 71. A method according to clause 1 or 2, wherein the configuration of the multiple resource pools includes resource timing offsets.

[0295] 72. A method according to clause 1 or 2, wherein the configuration of the plurality of resource pools comprises resource locations in the time domain.

[0296] 73. A method as described in clause 1 or 2, wherein the configuration of the plurality of resource pools includes resource locations in the frequency domain.

[0297] 74. A method as described in clause 1 or 2, wherein the configuration of the plurality of resource pools includes an antenna port configuration of the resources.

[0298] 75. A method as described in clause 1 or 2, wherein the configuration of the plurality of resource pools includes a range of modulation and coding schemes (MCS) allowed when using the resources.

[0299] 76. The method of clause 1, further comprising associating at least one carrier of the set of carriers to a logical channel.

[0300] 77. A method according to clause 7 or 69, wherein a propagation type can be associated to each logical channel, and wherein the propagation type is unicast, multicast or broadcast.

[0301] 78. A method as described in clause 69, wherein the configuration includes a mapping between logical channels and at least one quality of service (QoS) index.

[0302] 79. The method of clause 1, wherein the resources comprise device-to-device resources or uplink (UL) resources.

[0303] 80. A method as described in clause 79, wherein the device-to-device resource is a New Radio (NR) Sidelink (SL) grant, and wherein the uplink resource is a NR UL grant.

[0304] 81. A method as described in clause 80, wherein the wireless device is capable of selecting between the NR SL grant and the NR UL grant based on comparing the priority of the SL media access control (MAC) protocol data unit (PDU) with the priority of the UL MAC PDU.

[0305] 82. A method as described in clause 80, wherein the wireless device is capable of selecting between the NR SL grant and the NR UL grant based on a SL logical channel (LCH) priority threshold configured by the network node.

[0306] 83. A method as described in clause 82, wherein the wireless device is capable of selecting between the NR SL grant and the NR UL grant based on a PC5QFI (Quality of Service Flow ID) list configured by the network node.

[0307] 84. A method as set out in clause 80, wherein the device-to-device resources are Long Term Evolution (LTE) Sidelink (SL) grants, and wherein the uplink resources are New Radio (NR) UL grants.

[0308] 85. A method as described in clause 84, wherein the wireless device is capable of selecting between the LTE SL grant and the NR UL grant by comparing a priority threshold.

[0309] 86. A method as described in clauses 1 or 2, wherein selecting a resource is also based on at least one of: a specific transmission profile, a scheduling mode, or a determination of whether the resource is configured as a grant type 1 or a configured grant type 2.

[0310] 87. A method according to clause 2, wherein the resource is a configured grant type 2, and wherein the method further comprises receiving activation or deactivation of the resource from a network node; and transmitting a device-to-device configured grant confirmation media access control (MAC) control element (CE), which includes a corresponding logical channel ID (LCID) or one or more configured grant type 2 indexes.

[0311] 88. A method as described in clause 1, wherein the configuration includes a mapping between VQI and corresponding PDCP / RLC / MAC parameters.

[0312] 89. The method of clause 1, wherein the device-to-device link is a sidelink (SL), wherein selecting a resource comprises selecting between a mode 1 SL transmission and a mode 2 SL transmission.

[0313] 90. A method as described in clause 89, wherein selecting between Mode 1 SL transmission and Mode 2 SL transmission is based on an explicit indication from the network node.

[0314] 91. A method according to clause 89, wherein the network node configures a 5QI / VQI / QoS index list for Mode 2, and wherein the selection between Mode 1 SL transmission and Mode 2 SL transmission is based on a Mode 2 SL MAC PDU, wherein the Mode 2 SL MAC PDU includes 5QI data for the 5QI / VQI / QoS index list for Mode 2.

[0315] 92. A method as described in clause 1, wherein the device-to-device link is a side link (SL), wherein there are no gaps for frequency switching configured, wherein the network node configures thresholds for SL quality of service (QoS), packet priority levels, or packet delay budgets, and wherein selecting resources includes selecting between SL LTE V2X services and SL NR V2X services.

[0316] 93. A method according to clause 92, wherein the selection is also based on comparing the QoS of the SL LTE V2X service and the QoS of the SL NR V2X service.

[0317] 94. A method as described in clause 1, wherein the device-to-device link is a side link (SL), wherein a gap is configured for spanning radio access technology (RAT) frequencies, and wherein the selecting of resources is further based on a priority list comprising (i) Uu transmission or reception for RACH, (ii) inter-RAT V2X for transmission, (iii) non-RACH Uu transmission or intra-RAT V2X transmission, (iv) inter-RAT V2X for reception, and (v) non-RACH Uu reception or intra-RAT V2X reception.

[0318] Embodiments of the disclosed technology

[0319] Figure 7 705 is a block diagram representation of a portion of an apparatus according to some embodiments of the disclosed technology. An apparatus 705, such as a base station or a wireless device (or UE), may include a processor electronic device 710, such as a microprocessor that implements one or more techniques presented in this application. The apparatus 705 may include a transceiver electronic device 715 to send and / or receive wireless signals through one or more communication interfaces (such as one or more antennas 720). The apparatus 705 may include other communication interfaces for transmitting and receiving data. The apparatus 705 may include one or more memories (not explicitly shown) that are configured to store information such as data and / or instructions. In some embodiments, the processor electronic device 710 may include at least a portion of the transceiver electronic device 715. In some embodiments, at least some of the disclosed techniques, modules, or functions are implemented using the apparatus 705.

[0320] The specification and drawings are to be regarded as examples only, wherein exemplary means examples and does not imply ideal or preferred embodiments unless otherwise specified. As used herein, the use of "or" is intended to include "and / or" unless the context clearly dictates otherwise.

[0321] Some embodiments described herein are described in the context of the entire method or process, which may be implemented in one embodiment by a computer program product, which is contained in a computer-readable medium, including computer executable instructions such as program code executed by a computer in a network environment. Computer-readable media may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), compact disk (CD), digital versatile disk (DVD), etc. Therefore, the computer-readable medium may include non-temporary storage media. Generally, program modules may include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. Computer or processor executable instructions, related data structures, and program modules represent examples of program codes for executing the method steps disclosed herein. A specific sequence of such executable instructions or related data structures represents an example of corresponding actions for implementing the functions described in such steps or processes.

[0322] Some disclosed embodiments may be implemented as devices or modules using hardware circuits, software or a combination thereof. For example, a hardware circuit implementation may include discrete analog and / or digital components that are, for example, integrated as a part of a printed circuit board. Alternatively, or additionally, the disclosed components or modules may be implemented as application specific integrated circuits (ASICs) and / or field programmable gate arrays (FPGAs) devices. Some embodiments may additionally or alternatively include a digital signal processor (DSP), which is a dedicated microprocessor with an architecture optimized for the operation needs of digital signal processing associated with the disclosed functions of the present application. Similarly, various components or subcomponents within each module may be implemented with software, hardware or firmware. The connection between the modules and / or the components within the modules may be provided using any connection method and medium known in the art, including but not limited to communication over the Internet, wired or wireless networks using appropriate protocols.

[0323] Although the present application contains many details, these should not be interpreted as limitations on the scope of the claimed invention or the content that may be claimed, but as descriptions of features for specific embodiments. Certain features described in the present application in the context of separate embodiments may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. In addition, although the above-mentioned features may be described as working in certain combinations, and even initially claimed as such, in some cases, one or more features from the combination may be deleted from the combination, and the combination may involve a sub-combination or a variant of a sub-combination. Similarly, although the operations are described in a particular order in the accompanying drawings, this should not be understood as requiring the operations to be performed in the particular order or sequence shown, or requiring the execution of all the operations shown to obtain the desired results.

[0324] Only a few implementations and examples are described, and other implementations, enhancements, and variations can be made based on what is described and illustrated in this disclosure.

Claims

1. A wireless communication method, the method comprising: receiving, by a wireless device from a network node, a configuration of a plurality of resource pools associated with a set of carriers; receiving a dedicated resource from the network node, wherein the dedicated resource is a configured grant type 2; receiving activation or deactivation of the dedicated resource from the network node; and transmitting a device-to-device configured authorization confirmation media access control MAC control element CE, the media access control MAC control element CE including a corresponding logical channel ID (LCID) or one or more configured grant type 2 indexes; and Device-to-device link communications are performed using the dedicated resources.

2. The method according to claim 1, comprising: A resource configuration request associated with the wireless device itself is transmitted by the wireless device to the network node.

3. The method according to claim 2, wherein: The configuration includes at least one of UE ID, a quality of service QoS list of ongoing services, a list of frequencies of interest for reception, a list of frequencies of interest for transmission, UE type, a radio access technology RAT type that the wireless device can use for transmission, a resource type, an indication of whether the service is periodic, service periodicity, a logical channel identifier for UL transmission, and a service mode.

4. The method according to claim 1, wherein: The configuration includes at least one of: a set of allowed carriers for device-to-device link communication of NR RAT, a set of allowed carriers for device-to-device link communication of LTE RAT, transmission parameters associated with different packet priorities, synchronization resource types for each carrier, resource pool configuration, mapping between logical channel groups and QoS indexes, mapping between data rates and different numbers of subchannels, packet duplication thresholds associated with packet error rates, mapping between scheduling modes and QoS indexes, and mapping between VQI and corresponding PDCP, RLC or MAC parameters.

5. The method according to claim 4, wherein: The corresponding PDCP parameters include at least one of the following: discard timer, statusReportRequired, PDCP-SN-Size, DataSplitThreshold, statusPDB-Periodicity, t-Reordering, rn-IntegrityProtection, DataSplitDRB, DataSplitThreshold, Outoforderedelivery, and pdcp-DuplicationSRB.

6. The method according to claim 4, wherein: The corresponding RLC parameters include at least one of the following: t-PollRetransmit, pollPDU, pollByte, MaxRetxtThreshold, t-Reordering, t-StatusProhibit, am-WithShortSN, um-WithShortSN, um-WithLongSN.

7. The method according to claim 4, wherein: The corresponding MAC parameters include at least one of the following: LCP-Restriction, recommendedBitRate, logicalChannelSR-DelayTimer, multipleSR-Configurations, multipleConfiguredGrants.

8. The method according to claim 4, wherein: The transmission parameters associated with the different data packet priorities include at least one of the following: a range of applicable modulation and coding schemes (MCS), a range of applicable numbers of subchannels, a number of retransmissions, and a maximum allowed transmission power.

9. The method according to claim 4, wherein: The configuration of the multiple resource pools includes at least one of the following: resource type, resource periodicity, resource timing offset, time domain resource location, frequency domain resource location, antenna port configuration of the resources, and an indication of whether the current resource pool is allowed to perform sensing.

10. The method according to claim 3 or 9, wherein: The resource type includes at least one of the following: mode 1 resources, mode 2 resources, dynamic resources, and SPS resources.

11. The method according to claim 1, wherein: Selecting the resource from the plurality of resource pools is also based on an amount of buffered data of at least one carrier in the set of carriers.

12. The method according to claim 4, wherein: Selecting the resource having a number of subchannels is based on a mapping between the configured data rates and the number of subchannels.

13. The method according to claim 1, wherein: The resource pool is a Mode 1 resource pool, and wherein selecting the resource is further based on an indication from the network node.

14. The method according to claim 1, wherein: The resource pool is a Mode 2 resource pool, and wherein selecting the resources is performed autonomously by the wireless device.

15. The method according to claim 1, wherein: The configuration of the multiple resource pools includes at least one of the following: resource periodicity, resource timing offset, resource location in the time domain, resource location in the frequency domain, antenna port configuration of the resources, and modulation and coding scheme MCS range allowed when using the resources.

16. The method according to claim 1, wherein: A propagation type can be associated to each logical channel, and wherein the propagation type is unicast, multicast or broadcast.

17. The method according to claim 16, wherein: The configuration comprises a mapping between the logical channels and at least one Quality of Service (QoS) index.

18. The method according to claim 1, wherein: Selecting the resource is also based on at least one of: a particular transmission profile, a scheduling mode, a determination of whether the resource is a configured grant type 1 or a configured grant type 2.

19. A wireless communication device, comprising a processor and a memory, wherein: The processor is configured to read code from the memory and implement the method according to any one of claims 1 to 18.

20. A computer program product comprising computer readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the method according to any one of claims 1 to 18.

Images