METHOD PERFORMED BY USER EQUIPMENT, AND USER EQUIPMENT

Information

  • Patent Application
  • 20250159698
  • Publication Number
    20250159698
  • Date Filed
    January 05, 2023
    2 years ago
  • Date Published
    May 15, 2025
    6 months ago
  • CPC
    • H04W72/25
    • H04W72/40
  • International Classifications
    • H04W72/25
    • H04W72/40
Abstract
Provided in the present invention are a method performed by user equipment, and user equipment. The method performed by user equipment includes: determining, according to sidelink control information (SCI) format 2-C, the content of SCI; and transmitting the SCI, wherein a field in the SCI indicates that the SCI is used to carry inter-UE coordination information, or indicates that the SCI is used to carry a coordination request, wherein the inter-UE coordination information is triggered by the UE according to a certain condition, or is a response to a coordination request transmitted by second user equipment (UE), and the coordination request is used to request inter-UE coordination information from third user equipment (UE).
Description
TECHNICAL FIELD

The present invention relates to a method performed by user equipment, and user equipment.


BACKGROUND

Sidelink (SL) communication (e.g., when SL resource allocation mode 2 is configured) can support inter-user equipment (UE) coordination functions, e.g., coordination of resource allocation between two or more UEs. The inter-UE coordination functions need to solve a series of problems, for example, how to determine two or more UEs related to inter-UE coordination, and, for example, how to determine one or more messages related to inter-UE coordination and definitions, configurations, mapping, transmission, reception, etc., of resources respectively used thereby.


PRIOR ART DOCUMENTS
Non-Patent Documents



  • Non-Patent Document 1: RP-152293, New WI proposal: Support for V2V services based on LTE sidelink

  • Non-Patent Document 2: RP-170798, New WID on 3GPP V2X Phase 2

  • Non-Patent Document 3: RP-170855, New WID on New Radio Access Technology

  • Non-Patent Document 4: RP-190766, New WID on 5G V2X with NR sidelink

  • Non-Patent Document 5: RP-201385, WID revision: NR sidelink enhancement



SUMMARY

In order to address at least part of the aforementioned issues, the present invention provides a method performed by user equipment, and user equipment. The value of a “first resource location” is flexibly indicated, so that a resource indication combination can efficiently indicate a resource in any slot in a corresponding coordination resource window.


According to the present invention, a method performed by user equipment is provided. The method is characterized by comprising: receiving first coordination information at a resource pool u; and determining a coordination resource set R on the resource pool u according to the first coordination information. The first coordination information comprises a starting slot t0,0RIV of a coordination resource window, M resource indication combinations RIC1, . . . , and RICM, and reference slots t1RIV,ref, . . . , tMRIV,ref respectively corresponding to the M resource indication combinations. For m∈{1, . . . , M}, in the first coordination information, a slot in which each resource in the resource indication combination RICm is located is indicated as an offset thereof relative to a slot tmRIV,ref, and the slot tmRIV,ref f is indicated as an offset thereof relative to a slot t0,0RIV−1+(m−1)·G, where G is a predefined constant.


Furthermore, according to the present invention, provided is user equipment, comprising: a processor; and a memory, having instructions stored therein, wherein the instructions, when run by the processor, perform the above method.


Therefore, the present invention provides a method, in which the value of a “first resource location” is flexibly indicated, so that a resource indication combination can efficiently indicate a resource in any slot in a corresponding coordination resource window.





BRIEF DESCRIPTION OF THE DRAWINGS

The above and other features of the present invention will be more apparent from the following detailed description in combination with the accompanying drawings, in which:



FIG. 1 shows a method for determining, according to a time resource indicator value (TRIV or Time RIV), the number (N) of indicated resources, an offset (t1) of a slot in which a second resource is located relative to a slot in which a first resource is located, and an offset (t2) of a slot in which a third resource is located relative to the slot in which the first resource is located.



FIG. 2 shows a method for determining, according to a frequency resource indicator value (FRIV or Frequency RIV), a starting sub-channel (nsubCH,1start) of a second resource, a starting sub-channel (nsubCH,2start) of a third resource, and the number (LsubCH) of consecutive sub-channels corresponding to each resource.



FIG. 3 shows a flowchart corresponding to a method performed by user equipment according to Embodiment 1 of the present invention.



FIG. 4 shows an example of a first resource indication combination (RIC, or referred to as resource combination) control element type.



FIG. 5 shows an example of a second RIC control element type.



FIG. 6 shows an example of a third RIC control element type.



FIG. 7 shows an example of a fourth RIC control element type.



FIG. 8 shows an example of a fifth RIC control element type.



FIG. 9 shows a block diagram of user equipment (UE) to which the present invention relates.





DETAILED DESCRIPTION

The following describes the present invention in detail with reference to the accompanying drawings and specific embodiments. It should be noted that the present invention should not be limited to the specific embodiments described below. In addition, detailed descriptions of well-known technologies not directly related to the present invention are omitted for the sake of brevity, in order to avoid obscuring the understanding of the present invention.


In the following description, a 5G (or referred to as “New Radio” (NR) or 5G NR) mobile communication system and later evolved versions thereof (e.g., 5G Advanced) are used as exemplary application environments to specifically describe a plurality of embodiments according to the present invention. However, it is to be noted that the present invention is not limited to the following embodiments, but is applicable to many other wireless communication systems, such as a communication system after 5G and a 4G mobile communication system before 5G.


The terms given in the present invention may vary in Long Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, NR, and subsequent communication systems, but unified terms are used in the present invention. When applied to a specific system, the terms can be replaced with terms used in the corresponding system.


Unless otherwise specified, in all embodiments and implementations of the present invention where applicable:

    • Optionally, an eNB may refer to a 4G base station. For example, the eNB may provide termination of Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocols to the UE. As another example, the eNB may be connected to an Evolved Packet Core (EPC) by means of an Si interface.
    • Optionally, an ng-eNB may refer to an enhanced 4G base station. For example, the ng-eNB may provide termination of E-UTRA user plane and control plane protocols to the UE. As another example, the ng-eNB may be connected to a 5G core network (5GC) by means of an NG interface.
    • Optionally, a gNB may refer to a 5G base station. For example, the gNB may provide termination of NR user plane and control plane protocols to the UE. As another example, the gNB may be connected to a 5GC by means of an NG interface.
    • Optionally, μ represents a subcarrier spacing configuration (or an SCS configuration), e.g., a subcarrier spacing configuration configured in a resource grid, or a subcarrier spacing configuration configured in a carrier, or a subcarrier spacing configuration configured in a bandwidth part (BWP) (e.g., an uplink (UL) BWP, or a downlink (DL) BWP, or an SL BWP), or a subcarrier spacing configuration corresponding to a link (e.g., a UL, a DL, or an SL). A subcarrier spacing (SCS) corresponding to μ may be denoted as Δf, e.g., Δf=2μ·15 kHz.
    • Optionally, “{a1, . . . , aN}” may represent an ordered set arranged in ascending order of values of elements in the set or indexes of elements in the set, where if aN<a1, then “{a1, . . . , aN}” may represent an empty set Ø. For example, {1, . . . , 3} may represent {1, 2, 3}. As another example, {1, . . . , 1} may represent {1}. As another example, {1, . . . , 0} may represent Ø.
    • Optionally, “symbol” may refer to an orthogonal frequency division multiplexing (OFDM) symbol.
    • Optionally, “length” and “size” are interchangeable. For example, the “size” of a field in a downlink control information (DCI) format may be referred to as the “length” of the field.
    • Optionally, “starting” and “lowest” are interchangeable. For example, the “lowest subcarrier” of a carrier may be referred to as the “starting subcarrier” of the carrier.
    • Optionally, “starting” and “first” are interchangeable. For example, the “first symbol” of a slot may be referred to as the “starting symbol” of the slot.
    • Optionally, “ending” and “highest” are interchangeable. For example, the “highest subcarrier” of a carrier may be referred to as the “ending subcarrier” of the carrier.
    • Optionally, “ending” and “last” are interchangeable. For example, the “last symbol” of a slot may be referred to as the “ending symbol” of the slot.
    • Optionally, “number” and “index” are interchangeable. For example, twelve subcarriers in one resource block may be respectively numbered (or indexed) as subcarrier 0, subcarrier 1, . . . , and subcarrier 11 in ascending order of frequencies. Accordingly, the numbers (or indexes) of these subcarriers are respectively 0, 1, . . . and 11.
    • Optionally, one “resource” may correspond to one or more of the following:
      • One or more parameters in the time domain. For example, a starting symbol of the resource. As another example, a starting slot of the resource. As another example, the number of symbols occupied by the resource. As another example, the number of slots occupied by the resource.
      • One or more parameters in the frequency domain. For example, a starting sub-channel of the resource. As another example, a starting resource block of the resource. As another example, a starting subcarrier of the resource. As another example, the number of sub-channels occupied by the resource. As another example, the number of resource blocks occupied by the resource. As another example, the number of subcarriers occupied by the resource.
      • One or more parameters in the code domain. For example, a cyclic shift corresponding to the resource or a corresponding cyclic shift index. As another example, a cyclic shift pair corresponding to the resource or a corresponding cyclic shift pair index.
      • One or more parameters in the spatial domain. For example, a multiple input multiple output (MIMO) layer corresponding to the resource.
    • Optionally, the notation of a time-domain (or frequency-domain, or code-domain, or spatial-domain) resource may be used to represent an index of the resource in the time domain (or the frequency domain, or the code domain, or the spatial domain). For example, if a slot is denoted as t1, then t1=0 may indicate that an index of the slot (e.g., an index of the slot in a corresponding subframe) is 0. As another example, if a sub-channel is denoted as f1, then f1=0 may indicate that an index of the sub-channel (e.g., an index of the sub-channel in a corresponding resource pool) is 0.
    • Optionally, any two among “within X”, “in X”, and “on X” are interchangeable. X may be one or more carriers, or one or more BWPs, or one or more resource pools, or one or more links (e.g., a UL, a DL, or an SL), or one or more channels, or one or more sub-channels, or one or more resource block groups (RBGs), or one or more resource blocks (RBs), or one or more “occasions” (e.g., a physical downlink control channel (PDCCH) monitoring occasion, a physical sidelink shared channel (PSSCH) transmission occasion, a PSSCH reception occasion, a physical sidelink feedback channel (PSFCH) monitoring occasion, a PSFCH transmission occasion, a PSFCH reception occasion, a physical sidelink control channel (PSCCH) monitoring occasion, a PSCCH transmission occasion, a PSCCH reception occasion, or the like), or one or more symbols, or one or more slots, or one or more subframes, or one or more half-frames, or one or more frames, or one or more other time-domain and/or frequency-domain and/or code-domain and/or spatial-domain resources, etc.
    • Optionally, “higher layer(s)” or “upper layer(s)” may refer to one or more protocol layers or protocol sub-layers above a reference protocol layer (or a reference protocol sub-layer) in a protocol stack. For example, if the reference protocol layer is a physical layer, then the “higher layer” may refer to a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, a PC5-S layer, a PC5 RRC layer, a vehicle-to-everything (V2X) layer, an application layer, a V2X application layer, or the like. Optionally, unless otherwise specified, the reference protocol layer (or the reference protocol sub-layer) may refer to the physical layer.
    • Optionally, “lower layer(s)” may refer to one or more protocol layers or protocol sub-layers below a reference protocol layer (or a reference protocol sub-layer) in a protocol stack. For example, if the reference protocol layer is the MAC layer, then the “lower layer” may refer to the physical layer. Optionally, unless otherwise specified, the reference protocol layer (or the reference protocol sub-layer) may refer to the RRC layer, the PC5 RRC layer, or the MAC layer.
    • Optionally, a “predefined” value may be a value related to a subcarrier spacing. For example, different subcarrier spacings each correspond to a predefined constant. Specifically, for example, for μ=0, 1, 2, and 3, the predefined values are respectively 3, 5, 9, and 17.
    • Optionally, “pre-configure” may represent pre-configuration performed in a higher layer (e.g., an RRC layer) protocol, such as pre-configured (for example, pre-configured according to the specification of the higher layer protocol) in a specific storage location in the UE, or pre-configured (for example, pre-configured according to the specification of the higher layer protocol) in a specific storage location that can be accessed by the UE.
    • Optionally, “configure” may represent configuration performed in a higher-layer protocol by means of signaling. For example, configuration is performed for the UE by means of RRC signaling transmitted from the base station to the UE. As another example, configuration is performed for UE-2 by means of PC5 RRC signaling transmitted from UE-1 to UE-2.
    • Optionally, any two among “configure”, “indicate”, and “provide” are interchangeable, and any two among “configured by . . . ”, “indicated by . . . ”, and “provided by . . . ” are interchangeable.
    • Optionally, “configure” and “signal” are interchangeable.
    • Optionally, Δ(x1, x2) represents an offset between x1 and x2, or may be referred to as an offset of x2 with respect to x1, or an offset of x2 relative to x1, or an offset from x1 to x2, where x1 and x2 may be two parameters that can be compared, or two values of one parameter (e.g., two slots, two subframes, two half-frames, two frames, two subcarriers, two resource blocks, two resource block groups, two sub-channel, or the like). For example, in a set Asetref={a1ref, . . . , aNsetrefref}, if x1=airef (1≤i≤Nsetref) and x2=ajref (1≤j≤Nsetref), then Δ(x1, x2) may be defined as j−i, or defined as ajref−airef. Optionally, if Δ(x1, x2)>0, then x1 is less (or lower, or earlier) than x2. Optionally, if Δ(x1, x2)<0, then x1 is greater (or higher, or later) than x2. Optionally, if Δ(x1, x2)=0, then x1 is equal to x2.
    • Optionally, a time-domain resource may be referred to as a time resource, and vice versa.
    • Optionally, time-domain resource numbers (e.g., in chronological order) may start from 0 or 1. For example, for 30 kHz SCS, a set of slots in a subframe may be represented by a set of corresponding slot numbers as {0, 1} or {1, 2}.
    • Optionally, a frame may be a system frame, and a corresponding frame number may be referred to as a system frame number (SFN). System frames corresponding to the same SFN may occur periodically, for example, in a period of 1024 frames, and correspondingly, SFNs in one system frame period may respectively be 0, 1, . . . , 1023. The duration of one system frame may be 10 milliseconds, and correspondingly the duration of one system frame period may be 10240 milliseconds.
    • Optionally, a frame may be a direct frame, and a corresponding frame number may be referred to as a direct frame number (DFN). Direct frames corresponding to the same DFN may occur periodically, for example, in a period of 1024 frames, and correspondingly, DFNs in a direct frame period may respectively be 0, 1, . . . , 1023. The duration of one direct frame may be 10 milliseconds, and correspondingly the duration of one direct frame period may be 10240 milliseconds.
    • Optionally, the number of a slot may be the number of the slot in a corresponding subframe. For example, a set of corresponding slot numbers is {0, 1, . . . , Nslotsubframe,μ−1}, where Nslotsubframe,μ is the number of slots in one subframe. Nslotsubframe,μ may be related to μ, for example Nslotsubframe,μ=2μ.
    • Optionally, the number of a slot may be the number of the slot in a corresponding half-frame. For example, a set of corresponding slot numbers is {0, 1, . . . , Nslothalfframe,μ−1} where Nslothalfframe,μ is the number of slots in one half-frame. Nslothalfframe,μ may be related to ρ, for example Nslothalfframe,μ=5·2μ.
    • Optionally, the number of a slot may be the number of the slot in a corresponding frame (e.g., a system frame or a direct frame). For example, a set of corresponding slot numbers is {0, 1, . . . , Nslotframe,μ−1}, where Nslotframe,μ is the number of slots in one frame. Nslotframe,μ may be related to μ, for example Nslotframe,μ=10·2μ.
    • Optionally, the number of a slot may be the number of the slot in a corresponding frame period (e.g., a system frame period or a direct frame period). For example, a set of corresponding slot numbers is {0, 1, . . . , Nslotframeperiod,μ−1}, where Nslotframeperiod,μ is the number of slots in one frame period. Nslotframeperiod,μ may be related to μ, for example Nslotframeperiod,μ=10240×2μ.
    • Optionally, a set of all slots in a predefined or configured or pre-configured time (e.g., one subframe, or one half-frame, or one frame, or one frame period) may be referred to as a “physical slot set”, wherein each slot may be referred to as a “physical slot”, and a corresponding slot number may be referred to as a “physical slot number”. For example, in one frame period, the physical slot set may be denoted as Tallphy={t0phy, t1phy, . . . , t10240×2μ-1phy}, for example, t0phy=0, t1phy=1, . . . , t10240×2μ-1phy=10240×2μ−1.
    • Optionally, a frequency-domain resource may also be referred to as a frequency resource.
    • Optionally, a resource block may refer to a Virtual Resource Block (VRB), or a Physical Resource Block (PRB), or a Common Resource Block (CRB), or a resource block defined in another manner.
    • Optionally, frequency-domain resource numbers (e.g., in ascending order of the frequency) may start from 0 or 1. For example, if the number of sub-channels (or subchannels) configured in a resource pool ρ is NsubChannelSL,u, then a set of sub-channels in the resource pool may be represented by a set of corresponding sub-channel numbers as {0, 1, . . . , NsubChannelSL,u−1} or as {1, 2, . . . , NsubChannelSL,u}. As another example, a set of subcarriers in one resource block may be represented by a set of corresponding subcarrier numbers as {0, 1, . . . , 11} or {1, 2, . . . , 12}.
    • Optionally, an offset between two subcarriers may refer to an offset between center frequencies of the two subcarriers, and is represented by, for example, the number of subcarriers or the number of resource blocks.
    • Optionally, an offset between two resource blocks may refer to an offset between center frequencies of the lowest numbered subcarriers of the two resource blocks, and is represented by, for example, the number of resource blocks or the number of subcarriers.
    • Optionally, “SCI” (sidelink control information) may refer to an SCI transmission (or an SCI reception). The SCI transmission (or the SCI reception) corresponds to an SCI format (e.g., a 1st-stage SCI format or a 2nd-stage SCI format), or an SCI format combination (e.g., a 1st-stage SCI format and a corresponding 2nd-stage SCI format).
    • Optionally, an “SL transmission” may include one or more of the following:
      • A PSSCH transmission.
      • A PSCCH transmission and a corresponding (or associated) PSSCH transmission thereof.
      • A PSCCH transmission or a corresponding (or associated) PSSCH transmission thereof.
      • A PSFCH transmission.
      • A sidelink-synchronization signal/physical sidelink broadcast channel (S-SS/PSBCH, or referred to as S-SSB) transmission.
    • Optionally, an “SL resource” is a resource that can be used for SL transmission and/or SL reception.
    • Optionally, “resource pool” may be replaced with “SL resource pool”.
    • Optionally, in a predefined or configured or pre-configured time (e.g., one subframe, or one half-frame, or one frame, or one frame period), a set formed by all slots that may belong to the same resource pool is referred to as an “SL slot set”, wherein each element thereamong may correspond to one “SL slot”, and a corresponding index may be referred to as an “SL slot index”. For example, in a frame period (e.g., a system frame period or a direct frame period), the SL slot set may be denoted as TallSL={t0SL, t1SL, . . . , tTmax-1SL}, where Tmax is the number of elements in the SL slot set TallSL. Optionally, physical slots respectively corresponding to two adjacent SL slots (e.g., the slot t0SL and the slot t1SL) in the SL slot set TallSL may be adjacent to each other, or may not be adjacent to each other. Optionally, the set TallSL may be a set of slots that remain after slots in the following sets are excluded from the physical slot set Tallphy.
      • A set formed by S-SSB slots (e.g., the number of slots in the set is denoted as NS_SSB). An S-SSB slot may be a slot in which an S-SSB is configured.
    • A set formed by non-SL slots (e.g., the number of slots in the set is denoted as NnonSL). A non-SL slot may be a slot in which at least one among consecutive NlengthSL symbols starting from a symbol lstartSL is not configured to be a UL symbol, where lstartSL represents a starting symbol (e.g., configured by a parameter sl-StartSymbol) for SL in a slot (e.g., a non-S-SSB slot), and NlengthSL represents the number (e.g., configured by a parameter sl-LengthSymbols) of symbols for SL in a slot (e.g., a non-S-SSB slot). Optionally, a non-SL slot is always a slot in which no S-SSB is configured.
      • A set formed by reserved slots (e.g., the number of slots in the set is denoted as Nreserved, where Nreserved=(10240×2μ−NS_SSB−NnonSL) mod Lbitmap, where Lbitmap may be the length of a bitmap configured by a higher layer). If slots that remain after the slots in the S-SSB slot set and the slots in the non-SL slot set are excluded from the physical slot set Tallphy are respectively denoted as l0, l1, . . . , l(10240×2μNS,SSB-NnonSL-1) in ascending order of slot indexes, and if, for 0≤r<10240×2μ−NS_SSB−NnonSL, r satisfies r=└m·(10240×2μ−NS_SSB−NnonSL)/Nreserved┘, m=0, 1, . . . , Nreserved−1, then the slot lr belongs to the reserved slot set.
    • Optionally, in a predefined or configured or pre-configured time (e.g., one subframe, or one half-frame, or one frame, or one frame period), a set of all slots in the resource pool u may be referred to as a “logical slot set”, wherein each slot may be referred to as a “logical slot”, and a corresponding slot number may be referred to as a “logical slot number”. For example, in one frame period (e.g., a system frame period or a direct frame period), the logical slot set may be denoted as TuSL={t′0SL,u, t′1SL,u, . . . , t′T′maxu-1SL,u} where T′maxu is the number of elements in the logical slot set TuSL. Optionally, SL slots (or physical slots) respectively corresponding to two adjacent logical slots (e.g., the slot t′0SL,u and the slot t′1SL,u) in the logical slot set TuSL may be adjacent to each other, or may not be adjacent to each other.
    • Optionally, for a slot t1 and a slot t2, Δ(t1, t2) may refer to an offset between physical slots respectively corresponding to the slot t1 and the slot t2 (e.g., representing the number of milliseconds or the number of physical slots in a corresponding time interval), or an offset between SL slots respectively corresponding to the slot t1 and the slot t2, or an offset between logical slots respectively corresponding to the slot t1 and the slot t2.
    • Optionally, for a slot t1 and a slot t2, if Δ(t1, t2)=D, then the slot t2 may be denoted as t2=NEXT (t1, D).
    • Optionally, for a slot t1 and a slot t2, if Δ(t1, t2)=D, then the slot t1 may be denoted as t1=PREV (t2, D).
    • Optionally, a time window (or referred to as a “time interval”, and, for example, denoted as W) corresponds to a starting slot (e.g., denoted as tstartW), an ending slot (e.g., denoted as tendW), and a size (or referred to as length, and, for example, denoted as LEN(W)). LEN(W) may be equal to Δ(tstartW, tendW), or equal to Δ(NEXT(tstartW,1),tendW), or equal to Δ(PREV(tstartW,1),tendW), or equal to Δ(tstartW,NEXT(tendW,1)), or equal to Δ(NEXT(tstartW,1),NEXT(tendW,1)), or equal to Δ(PREV(tstartW,1),NEXT(tendW,1)), or equal to Δ(tstartW,PREV(tendW,1)), or equal to Δ(NEXT(tstartW,1),PREV(tendW,1)), or equal to Δ(PREV(tstartW,1),PREV(tendW,1)).


Resource allocation modes related to SL operations may include:

    • Mode 1 (or Resource Allocation Mode 1, or Sidelink Resource Allocation Mode 1): a base station schedules a resource for SL transmission.
    • Mode 2 (or Resource Allocation Mode 2, or Sidelink Resource Allocation Mode 2): a UE determines a resource for SL transmission (i.e., the base station does not participate in scheduling of resources for SL transmission). For example, a UE performing an SL transmission operation autonomously determines a resource for SL transmission.


A PSCCH transmission and a “time resource assignment” field and a “frequency resource assignment” field in SCI (e.g., SCI format 1-A) included therein may be used to determine N resources that are associated with the SCI and may be used for SL transmission (e.g., PSCCH and/or PSSCH transmission), wherein the value range of N may be determined by one or more predefined or configured or pre-configured parameters (e.g., N≥1, and e.g., N≤NMAX, where Nu may be configured or pre-configured by a higher layer parameter (e.g., sl-MaxNumPerReserve), and specifically, e.g., if NMAX=2, then N∈{1, 2}, and e.g., if NMAX=3, then N∈{1, 2, 3}). The N resources may be respectively referred to as a “first resource”, . . . , and an “N-th resource” in chronological order. A slot (e.g., denoted as t0SL,RES) in which the first resource is located may be a slot in which the PSCCH transmission is located (or referred to as a “slot in which the SCI is located” or a “slot in which the SCI is received”), and a slot in which each of other resources is located may be expressed as a slot offset thereof relative to the slot t0SL,RES For example, the slot (e.g., denoted as t1SL,RES) in which the second resource is located may be expressed as t1=Δ(t0SL,RES,t1SL,RES), and the slot (e.g., denoted as t2SL,RES) in which the third resource is located may be expressed as t2=Δ(t0SL,RESt2SL,RES). N, t1 (e.g., when N=2 or N=3), and t2 (e.g., when N=3) may be determined according to a TRIV indicated in the “time resource assignment” field in the SCI, such as in the manner shown in FIG. 1.


In the frequency domain, the N resources correspond to the same number of sub-channels (e.g., denoted as LsubCH, e.g., representing LsubCH consecutively allocated sub-channels). In the N resources, a starting sub-channel (i.e., a starting sub-channel of a corresponding SL transmission, and, for example, denoted as nsubCH,0start) of the first resource is a sub-channel in which a starting resource block of the PSCCH transmission is located, and starting sub-channels of the other resources (e.g., starting sub-channels of the second resource and the third resource are respectively denoted as nsubCH,1start and nsubCH,2start) and LsubCH may be determined according to a FRIV indicated by the “frequency resource assignment” field in the SCI, such as in the manner shown in FIG. 2. If N<NMAX, then sub-channels corresponding to the last NMAX−N resources indicated by the FRIV are not used.


The above-described procedure of determining the time- and frequency-domain parameters of the N resources may be referred to as an “SL resource reservation procedure”.


SL communication (e.g., in SL resource allocation mode 2) can support inter-UE coordination (or simply referred to as “coordination”) functions, e.g., coordination of resource allocation and/or reservation and/or indication and/or use between two or more UEs, so as to improve the efficiency of resource allocation and/or reservation and/or indication and/or use, and/or reduce conflicts in resource allocation and/or reservation and/or indication and/or use, and/or alleviate and/or eliminate interference, etc. Specifically, for example, a UE (e.g., referred to as UE-A) may respectively transmit “inter-UE coordination information” (or referred to as “coordination information”) to one or more other UEs (e.g., referred to as UE-B if only one other UE is present, or respectively referred to as UE-B1, UE-B2, . . . if more than one other UE is present). The coordination information may explicitly or implicitly indicate (or correspond to, or be associated with) one or more resource sets (e.g., each such resource set is referred to as a “coordination resource set”, and correspondingly, each resource in a coordination resource set is referred to as a “coordination resource”).


Optionally, one UE may support one or more coordination schemes. Different coordination schemes may correspond to different coordination information determination methods, and/or coordination information contents (e.g., the content of a corresponding coordination resource set), and/or coordination information transmission triggering conditions and/or methods, and/or coordination information transmission methods, etc.


Optionally, in a first coordination scheme, resources in a coordination resource set may be “preferred resources”. Correspondingly, the coordination resource set may be referred to as “a set of preferred resources”, and coordination information including a “set of preferred resources” may be referred to as “preferred co-ordination information” (or referred to as “preferred inter-UE co-ordination information”). A preferred resource indicated by UE-A to UE-B may be a resource that UE-A wants UE-B to use (or to use preferentially), for example, when performing SL transmission the destination of which is UE-A. Upon receiving the set of preferred resources, UE-B may perform resource selection or resource reselection on the basis of one or more resource sets. The one or more resource sets may include the coordination resource set (e.g., referred to as a set SRESCO) and/or a resource set (e.g., referred to as a set SSNS) identified by UE-B on the basis of a sensing result thereof. Specifically, for example, if the number of resources in an intersection between the set SRESCO and the set SSNS is greater than (or, greater than or equal to) a certain threshold, then UE-B performs resource selection or resource reselection on the basis of the intersection between the set SRESCO and the set SSNS.


Optionally, in the first coordination scheme, resources in a coordination resource set may be “non-preferred resources”. Correspondingly, the coordination resource set may be referred to as “a set of non-preferred resources”, and coordination information including a “set of non-preferred resources” may be referred to as “non-preferred co-ordination information” (or referred to as “non-preferred inter-UE co-ordination information”). A non-preferred resource indicated by UE-A to UE-B may be a resource that UE-A wants UE-B to avoid using (or preferentially not to use, or to exclude preferentially), for example, when performing SL transmission the destination UE of which is UE-A. Upon receiving the coordination resource set, UE-B may perform resource selection or resource reselection on the basis of one or more resource sets. The one or more resource sets may include the set of non-preferred resources (e.g., referred to as a set SRESCO) and/or a resource set SSNS identified by UE-B on the basis of a sensing result thereof. Specifically, for example, UE-B may, when performing resource selection or resource reselection (e.g., when performing resource selection or resource reselection on the basis of the set SSNS), exclude resources overlapping with resources in the set SRESCO.


Optionally, transmission of coordination information may be triggered according to one or more predefined or configured or pre-configured conditions by a UE transmitting the coordination information. For example, the condition that UE-A transmits the coordination information to UE-B may include UE-A performing resource selection (or reselection) for a transport block the destination UE of which is UE-B.


Optionally, the coordination information may be a response to or triggered by a “coordination request” (or referred to as an “explicit coordination request” or an “explicit request”). For example, UE-B transmits a coordination request to UE-A to request a coordination resource set (for example, requesting a set of preferred resources or a set of non-preferred resources). In response to the coordination request, UE-A may determine a corresponding coordination resource set, and indicate the coordination resource set in coordination information transmitted to UE-B.


Optionally, part or all of the coordination information may be included in SL control information. The SL control information may be physical layer control information, or higher layer control information. For example, part or all of the coordination information may be included in 1st-stage SCI. As another example, part or all of the coordination information may be included in 2nd-stage SCI. As another example, part or all of the coordination information may be included in sidelink feedback control information (SFCI). As another example, part or all of the coordination information may be included in other SL control information (e.g., referred to as sidelink coordination control information (SCCI)).


Optionally, part or all of the coordination information may be included in higher layer (e.g., the MAC layer, or the RRC layer) signaling. For example, part or all of the coordination information may be included in a MAC Control Element (MAC CE). As another example, part or all of the coordination information may be included in an RRC message.


Optionally, part or all of the information in the coordination request may be included in SL control information. The SL control information may be physical layer control information, or higher layer control information. For example, part or all of the information in the coordination request may be included in 1st-stage SCI. As another example, part or all of the information in the coordination request may be included in 2nd-stage SCI. As another example, part or all of the information in the coordination request may be included in SFCI. As another example, part or all of the information in the coordination request may be included in other SL control information (e.g., in SCCI).


Optionally, part or all of the information in the coordination request may be included in one higher layer (e.g., the MAC layer, or the RRC layer) signaling. For example, part or all of the information in the coordination request may be included in a MAC CE. As another example, part or all of the information in the coordination request may be included in an RRC message.


Optionally, the first coordination scheme may be configured or pre-configured or indicated as enabled or disabled. Optionally, whether the first coordination scheme is enabled (or disabled) may be configured or pre-configured or indicated separately for each resource pool. Optionally, methods for enabling (or disabling) the first coordination scheme may include a semi-persistent method (e.g., configured or pre-configured by means of a higher-layer protocol) and/or a dynamic method (e.g., indicated in SCI). Optionally, enabling the first coordination scheme means enabling transmission and/or reception of a coordination request, and/or transmission and/or reception of coordination information.


Embodiment 1

A method performed by user equipment according to Embodiment 1 of the present invention will be described below with reference to FIG. 1.



FIG. 1 shows a flowchart corresponding to the method performed by user equipment according to Embodiment 1 of the present invention.


As shown in FIG. 1, in Embodiment 1 of the present invention, steps performed by user equipment (UE, for example, referred to as UE-B) include: step S101 and step S103.


Specifically, optionally, in step S101, a first coordination request is transmitted. For example, the first coordination request is transmitted on a resource pool uCR.


Optionally, the first coordination request is used to request coordination information (e.g., a coordination resource set, and/or other coordination information) from another UE (e.g., denoted as UE-A).


Optionally, part of the information included in the first coordination request is referred to as a first part of the first coordination request, and the remaining information is referred to as a second part of the first coordination request.


Optionally, the first coordination request corresponds to a source layer-2 identifier (e.g., referred to as a “first source layer-2 identifier”) and a destination layer-2 identifier (e.g., referred to as a “first destination layer-2 identifier”). The first source layer-2 identifier may be used to identify UE-B, and the first destination layer-2 identifier may be used to identify UE-A.


Optionally, the first coordination request is carried in an SL transmission (e.g., for i∈{1, . . . , NCR}, the SL transmission is denoted as TriCR) in one or more slots (e.g., respectively denoted as t1CR, . . . , tNCRCR in chronological order). The SL transmission Tr1CR may be referred to as an “initial transmission” of the first coordination request, and an SL transmission TriCR (1<i≤<NCR, if applicable) may be referred to as a “re-transmission” of the first coordination request. NCR may be a predefined or configured or pre-configured value (e.g., NCR=1), or may be determined by one or more predefined or configured or pre-configured parameters, or may be autonomously determined by UE-B, or may be determined in another manner.


Optionally, for i∈{1, . . . , NCR}, j∈{1, . . . , NCR}, and i≠j, information in the first coordination request carried in the SL transmission TriCR and information in the first coordination request carried in the SL transmission TrjCR may be completely the same or partially the same. For example, if a future slot tXCR,I is indicated in the first coordination request as an offset relative to a slot in which the SL transmission carrying the SL request is located, then the first coordination request carried in the SL transmission TriCR and the first coordination request carried in the SL transmission TrjCR respectively indicate Δ(tiCR,tXCR,IJ) and Δ(tjCR,tXCR,I)) and Δ(tiCR,tXCR,I)≠Δ(tjCR,tXCR,I).


Optionally, the SL transmissions Tr1CR, . . . TrNCRCR R are associated with the same cast type, e.g., unicast.


Optionally, the SL transmissions Tr1CR, . . . , TrNCRCR are associated with the same 1st-stage SCI format (e.g., referred to as a first SCI format).


Optionally, for i∈{1, . . . , NCR}, j∈{1, . . . , NCR}, and i≠j, the SL transmission TriCR and the SL transmission TrjCR may be associated with the same 1st-stage SCI format, or may be associated with different 1st-stage SCI formats.


Optionally, the SL transmissions TriCR, . . . , TrNCRCR are associated with the same 2nd-stage SCI format (e.g., referred to as a second SCI format).


Optionally, for i∈{1, . . . , NCR}, j∈{1, . . . , NCR}, and i≠j, the SL transmission TriCR and the SL transmission TrjCR may be associated with the same 2nd-stage SCI format, or may be associated with different 2nd-stage SCI formats.


Optionally, for i∈{1, . . . , NCR}, the 1st-stage SCI format associated with the SL transmission TriCR does not include any information in the first coordination request.


Optionally, for i∈{1, . . . , NCR}, the 1st-stage SCI format associated with the SL transmission TriCR includes part or all of the information in the first coordination request (e.g., the first part of the first coordination request, or the second part of the first coordination request, or the first part of the first coordination request and the second part of the first coordination request).


Optionally, for i∈{1, . . . , NCR}, the 2nd-stage SCI format associated with the SL transmission TriCR does not include any information in the first coordination request.


Optionally, for i∈{1, . . . , NCR}, the 2nd-stage SCI format associated with the SL transmission TriCR includes part or all of the information in the first coordination request (e.g., the first part of the first coordination request, or the second part of the first coordination request, or the first part of the first coordination request and the second part of the first coordination request).


Optionally, for i∈{1, . . . , NCR}, a source identifier indicated in the 2nd-stage SCI format associated with the SL transmission TriCR is a source layer-1 identifier (e.g., eight least significant bits of the first source layer-2 identifier) corresponding to the first source layer-2 identifier.


Optionally, for i∈{1, . . . , NCR}, a destination identifier indicated in the 2nd-stage SCI format associated with the SL transmission TriCR is a destination layer-1 identifier (e.g., sixteen least significant bits of the first destination layer-2 identifier) corresponding to the first destination layer-2 identifier.


Optionally, the 2nd-stage SCI formats associated with the SL transmissions T1CR, . . . , TrNCRCR indicate the same “HARQ feedback enabled/disabled indicator” value, e.g., “enabled” or “disabled”.


Optionally, for i∈{1, . . . , NCR}, j∈{1, . . . , NCR}, and i≠j, the “HARQ feedback enabled/disabled indicator” values indicated in the 2nd-stage SCI formats associated with the SL transmission TriCR and the SL transmission TrjCR may be the same or different.


Optionally, for i∈{1, . . . , NCR}, a transport block carried in the SL transmission TriCR may include a “coordination request MAC CE”. The coordination request MAC CE includes part or all of the information in the first coordination request (e.g., the first part of the first coordination request, or the second part of the first coordination request, or the first part of the first coordination request and the second part of the first coordination request).


Optionally, a coordination request identifier (e.g., referred to as a “first coordination request identifier”) is indicated in the first coordination request. The first coordination request identifier may be an integer randomly generated by UE-B.


Optionally, for i∈{1, . . . , NCR}, t1CR is indicated in the first coordination request transmitted in the slot tiCR. For example, tCR is indicated as Δ(tCR,tiCR).


Optionally, the first coordination request corresponds to a “coordination response window” (e.g., denoted as WRESPONSECO, a corresponding starting slot being tstartWRESPONSECO, an ending slot being tendWRESPONSECO, and the size being LEN(WRESPONSECO)). The coordination response window may be used to indicate a time range in which a reception operation is performed with respect to a response to the first coordination request. For example, if the response is not received after the end of the slot tendWRESPONSECO (or NEXT(tendWRESPONSECO,1), or PREV(tendWRESPONSECO,1)), then the response is no longer received.


Optionally, the slot tstartWRESPONSECO is related to one or more of t1CR, . . . , tNCRCR and NCR. For example, Δ(t1CR, tstartWRESPONSECO)=T′proc,1CO. As another example, Δ(t1CR,tstartWRESPONSECO)≥T′proc,1CO. As another example, Δ(tCR,tstartWRESPONSECO)>T′proc,1CO. As another example, Δ(t1CR,tstartWRESPONSECO)≤T′proc,1CO. As another example, Δ(t1CR,tstartWRESPONSECO)<T′proc,1CO. As another example, Δ(tNCRCR,tstartWRESPONSECO)=T′proc,1CO. As another example, Δ(tNCRCR,tstartWRESPONSECO)≥T′proc,1CO. As another example, Δ(tnCRCR,tstartWRESPONSECO)>T′proc,1CO. As another example, Δ(tNCRCR,tstartWRESPONSECO)≤T′proc,1CO. As another example, (tNCRCR,tstartWRESPONSECO)<T′proc,1CO may be equal to Tproc,1CO or Tproc,1CO+1 or Tproc,1CO−1.


Optionally, the slot tendWRESPONSECO is related to the slot tNCRCR. For example, Δ(tNCRCR,tendWRESPONSECO)=T′proc,2CO. As another example, Δ(tNCRCR,tendWRESPONSECO)≥T′proc,2CO. As another example, Δ(tNCRCR,tendWRESPONSECO)>T′proc,2CO. As another example, Δ(tNCRCR,tendWRESPONSECO)≤T′proc,2CO. As another example, Δ(tNCRCR,tendWRESPONSECO)<T′proc,2CO. T′proc,2CO may be equal to Tproc,2CO or Tproc,2CO+1 or Tproc,2CO−1.


Optionally, LEN(WRESPONSECO) is related to LENRESPONSECO. For example, LEN(WRESPONSECO)=LRESPONSECO. As another example, LEN((WRESPONSECO)≥LRESPONSECO. As another example, LEN(WRESPONSECO)>LRESPONSECO. As another example, LEN(WRESPONSECO)≤LRESPONSECO another example, LEN(WRESPONSECO)<LRESPONSECO. LRESPONSECO may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters.


Optionally, a coordination response timer is started in the slot tstartWRESPONSECO. The coordination response timer may be maintained by a MAC layer entity of UE-B. The value (or referred to as “initial value”) of the coordination response timer may be equal to LEN(WRESPONSECO).


Optionally, the first coordination request corresponds to a “coordination resource window” (or referred to as a “coordination resource selection window”, e.g., denoted as WRESOURCECO, a corresponding starting slot being tstartWRESOURCECO, an ending slot being tendWRESOURCECO, and the size being LEN(WRESOURCECO)). The coordination resource window may be used to indicate the range of slots in which coordination resources in a requested coordination resource set are located. For example, a slot in which any one of the coordination resources is located is not earlier than tstartWRESOURCECO (or NEXT(tstartWRESOURCECO,1), or PREV(tstartWRESOURCECO,1)). As another example, a slot in which any one of the coordination resources is located is not later than tendWRESOURCECO (or NEXT(tendWRESOURCECO,1), or PREV(tendWRESOURCECO,1)).


Optionally, one or more parameters (e.g., t tstartWRESOURCECO, or tendWRESOURCECO, or LEN(WRESOURCECO)) of the coordination resource window are indicated by the first coordination request. For example, for one or more of i∈{1, . . . , NCR}, one or more of the following are indicated in the first coordination request transmitted in the slot tiCR:

    • Δ(t1CR,tstartWRESOURCECO).
    • Δ(t1CR,tendWRESOURCECO).
    • Δ(tiCR,tstartWRESOURCECO).
    • Δ(tiCR,tendWRESOURCECO).
    • Δ(tstartWRESOURCECO,tstartWRESOURCECO).
    • Δ(tendWRESOURCECO,tstartWRESOURCECO).
    • Δ(tstartWRESOURCECO,tendWRESOURCECO).
    • Δ(tendWRESOURCECO,tendWRESOURCECO).


Optionally, the slot tendWRESOURCECO is related to the slot tendWRESOURCECO. For example, Δ(tendWRESOURCECO,tstartWRESOURCECO)=T′proc,3CO. As another example, Δ(tendWRESOURCECO,tstartWRESOURCECO)≥T′proc,3CO. As another example, Δ(tendWRESOURCECO,tstartWRESOURCECO)>T′proc,3CO. As another example, Δ(tendWRESOURCECO,tstartWRESOURCECO)≤T′proc,3CO. As another example, Δ(tendWRESOURCECO,tstartWRESOURCECO)<T′proc,3CO. T′proc,3CO may be equal to Tproc,3CO or Tproc,3CO+1 or Tproc,3CO−1.


Optionally, the slot t1CR is related to the slot tstartWRESOURCECO. For example, Δ(t1CR,tstartWRESOURCECO)=LGAP0CO. As another example, Δ(t1CR,tstartWRESOURCECO)≥LGAP0CO. As another example Δ(t1CR,tstartWRESOURCECO)>LGAP0CO. As another example, Δ(t1CR,tstartWRESOURCECO)≤LGAP0CO. As another example Δ(t1CR,tstartWRESOURCECO)<LGAP0CO. LGAP0CO may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters, or may be indicated by the first coordination request.


Optionally, LEN(WRESOURCECO) is related to LRESOURCECO. For example, LEN(WRESOURCECO)=LRESOURCECO. As another example, LEN(WRESOURCECO)≥LRESOURCECO. As another example, LEN(WRESOURCECO)>LRESOURCECO. As another example, LEN(WRESOURCECO)≤LRESOURCECO. As another example, LEN(WRESOURCECO)<LRESOURCECO. LRESOURCECO may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters, or may be indicated by the first coordination request.


Optionally, a coordination resource set type (e.g., referred to as a “first coordination resource set type”) is indicated in the first coordination request. For example, the first coordination resource set type may indicate the type of a requested coordination resource set, e.g., a “set of preferred resources” or a “set of non-preferred resources”.


Optionally, the first coordination request indicates information related to data to be transmitted by UE-B (e.g., transmitted to UE-A), e.g., a transmission priority, or the number of sub-channels corresponding to each resource, or a resource reservation period.


Optionally, the first part of the first coordination request includes part or all of time-related information in the first coordination request, e.g., one or more of tstartWRESPONSECO, tendWRESPONSECO, LEN(WRESPONSECO), tstartWRESOURCECO, tendWRESOURCECO, LEN(WRESOURCECO), Δ(t1CR,tiCR), Δ(t1CR,tendWRESPONSECO), Δ(t1CR,tstartWRESOURCECO), Δ(tiCR,tendWRESPONSECO), Δ(tiCR,tstartWRESOURCECO), and Δ(tendWRESPONSECO,tstartWRESOURCECO).


Further, in step S103, first coordination information is acquired. The first coordination information may be a response of UE-A to the first coordination request. For example, one or more SL transmissions are received (e.g., received in a resource pool uCI), and an SL transmission used to carry the first coordination information is determined therefrom (e.g., slots in which the determined SL transmissions used to carry the first coordination information are located are respectively denoted as t1CI, . . . , tNCICI, in chronological order, and the corresponding SL transmissions are respectively denoted as Tr1CI, . . . , TrNCICI, where NCI>1, and in addition, NCI=0 may correspond to a situation in which no SL transmission carrying the first coordination information is received). The SL transmissions Tr1CI, . . . . TrNCICI may be part or all of all SL transmissions that are actually transmitted by UE-A to carry the first coordination information.


Optionally, if an SL transmission satisfies a first coordination condition, the SL transmission is determined as one among Tr1CI, . . . , TrNCICI. The first coordination condition may include one or more of the following (in any combination of “and” or “or”):

    • The source identifier indicated in the 2nd-stage SCI format associated with the SL transmission is equal to eight least significant bits of the first destination layer-2 identifier.
    • The destination identifier indicated in the 2nd-stage SCI format associated with the SL transmission is equal to sixteen least significant bits of the first source layer-2 identifier.
    • Data of a transport block corresponding to an SL process associated with the SL transmission has been successfully decoded (e.g., successfully decoded for the first time).
    • The transport block corresponding to the SL process associated with the SL transmission includes a coordination information MAC CE.
    • A value indicated by a DST field in a MAC PDU subheader in the transport block corresponding to the SL process associated with the SL transmission is equal to eight most significant bits of the first source layer-2 identifier.
    • A value indicated by an SRC field in the MAC PDU subheader in the transport block corresponding to the SL process associated with the SL transmission is equal to sixteen most significant bits of the first destination layer-2 identifier.
    • The 1st-stage SCI format associated with the SL transmission includes part or all of the first coordination information.
    • The 2nd-stage SCI format associated with the SL transmission includes part or all of the first coordination information.
    • A coordination request identifier is indicated in coordination information included in the SL transmission, and the coordination request identifier is equal to the first coordination request identifier.
    • A coordination resource set type is indicated in coordination information included in the SL transmission, and the coordination resource set type is equal to the first coordination resource set type.


Optionally, the first coordination information is associated with the first source layer-2 identifier (or the first source layer-1 identifier) and/or the first destination layer-2 identifier (or the first destination layer-1 identifier). For example, coordination information received from a UE other than UE-A (e.g., UE-C) is not the first coordination information.


Optionally, after the first coordination information is received, the coordination response timer is stopped.


Optionally, if the coordination response timer expires, reception of the first coordination information is canceled.


Optionally, part of the first coordination information is referred to a first part of the first coordination information, and the remaining information is referred to as a second part of the first coordination information.


Optionally, the SL transmissions Tr1CI, . . . , TrNCICI are associated with the same 1st-stage SCI format (e.g., referred to as a third SCI format).


Optionally, for i∈{1, . . . , NCI}, j∈{1, . . . , NCI}, and i≠j, the SL transmission TriCI and the SL transmission TrjCI may be associated with the same 1st-stage SCI format, or may be associated with different 1st-stage SCI formats.


Optionally, the SL transmissions Tr1CI, . . . , TrNCICI are associated with the same 2nd-stage SCI format (e.g., referred to as a fourth SCI format).


Optionally, for i∈{1, . . . , NCI}, j∈{1, . . . , NCI}, and i≠j, the SL transmission TriCI and the SL transmission TrjCI may be associated with the same 2nd-stage SCI format, or may be associated with different 2nd-stage SCI formats.


Optionally, for i∈{1, . . . , NCI}, the 1st-stage SCI format associated with the SL transmission TriCI does not include any information in the first coordination information.


Optionally, for i∈{1, . . . , NCI}, the 1st-stage SCI format associated with the SL transmission TriCI may include part or all of the first coordination information (e.g., the first part of the first coordination information, or the second part of the first coordination information, or the first part of the first coordination information and the second part of the first coordination information).


Optionally, for i∈{1, . . . , NCI}, the 2nd-stage SCI format associated with the SL transmission TriCI does not include any information in the first coordination information.


Optionally, for i∈{1, . . . , NCI}, the 2nd-stage SCI format associated with the SL transmission TriCI may include part or all of the first coordination information (e.g., the first part of the first coordination information, or the second part of the first coordination information, or the first part of the first coordination information and the second part of the first coordination information).


Optionally, the 2nd-stage SCI formats associated with the SL transmissions Tr1CI, . . . , TrNCICI indicate the same “HARQ feedback enabled/disabled indicator” value, e.g., “enabled” or “disabled”.


For i∈{1, . . . , NCI}, j∈{1, . . . , NCI}, and i≠j, the “HARQ feedback enabled/disabled indicator” values indicated in the 1st-stage SCI formats or the 2nd-stage SCI formats associated with the SL transmission TriCI and the SL transmission TrjCI may be the same or different.


Optionally, for i∈{1, . . . , NCI}, a transport block carried in the SL transmission TriCI may include a “coordination information MAC CE”. The coordination information MAC CE includes part or all of the first coordination information (e.g., the first part of the first coordination information, or the second part of the first coordination information, or the first part of the first coordination information and the second part of the first coordination information).


Optionally, the first coordination information includes information of M resource indication combinations (RICs, or referred to as resource combinations), wherein the value range of M may be determined by one or more predefined or configured or pre-configured parameters, for example, M≥Mmin, and as another example, M≤Mmax. Optionally, Mmin (or Mmin+1, or Mmin−1) may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters, or may be autonomously determined by UE-B, or may be determined in another manner. For example, Mmin=1. As another example, Mmin=0. Optionally, Mmax (or Mmax+1, or Mmax−1) may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters, or may be autonomously determined by UE-B, or may be determined in another manner. Optionally, when M≥1, the M RICs may be respectively denoted as RIC1, . . . , RICM.


Optionally, the M RICs are used to indicate a coordination resource set (e.g., denoted as SRESCO, wherein a resource pool in which a resource in the coordination resource set SRESCO is located is denoted as uRESCO).


Optionally, for m∈{1, . . . , M}, RICm may include one or more of TRIVm, FRIVm, or Prsvp,m, wherein TRIVm is a time resource indicator value (TRIV), FRIVm is a frequency resource indicator value (FRIV), and Prsvp,m is a resource reservation period (RRP), wherein Prsvp,m may represent the number of milliseconds, or the number of physical slots, or the number of SL slots, or the number of logical slots in the resource reservation period. For example, RICm may be defined as one of the following:

    • (TRIVm, FRIVm).
    • (TRIVm, FRIVm, Prsvp,m).


Optionally, the definition and/or determination method of RICm may be related to the type of the coordination resource set SRESCO. For example, if the coordination resource set sRESCO is a set of preferred resources, then RIC=(TRIVm, FRIVm). As another example, if the coordination resource set SRESCO is a set of preferred resources, then Prsvp,m is skipped (for example, when RICm is transmitted, Prsvp,m is skipped, i.e., RIC=(TRIVm, FRIVm), and as another example, when RICm=(TRIVm, FRIVm, Prsvp,m) is received, Prsvp,m in received RICm is skipped). As another example, if the coordination resource set sRESCO is a set of non-preferred resources, then RICm=(TRIVm, FRIVm, Prsvp,m).


Optionally, for m∈{1, . . . , M}, TRIVm and FRIVm indicate NRESRIV,m resources in the coordination resource set SRESCO. The value range of NRESRIV,m may be determined by one or more predefined or configured or pre-configured parameters. For example, NRESRIV,m≥NRES,minRIV. As another example, NRESRIV,m≤NRES,maxRIV. Optionally, NRES,minRIV (or NRES,minRIV+1, or NRES,minRIV−1) may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters, or may be autonomously determined by UE-B, or may be determined in another manner. For example, NRES,minRIV=1. As another example, NRES,minRIV=0. Optionally, NRES,maxRIV (or NRES,maxRIV+1, or NRES,maxRIV−1) may be a predefined or configured or pre-configured value (e.g., the value of a higher-layer parameter sl-MaxNumPerReserve), or may be determined by one or more predefined or configured or pre-configured parameters (e.g., determined by the higher-layer parameter sl-MaxNumPerReserve), or may be autonomously determined by UE-B, or may be determined in another manner. For example, NRES,maxRIV=1. As another example, NRES,maxRIV=2. As another example, NRES,maxRIV=3. As another example, NRES,maxRIV=4.


Optionally, when NRESRIV,m≥1, slots in which the NRESRIV,m resources are located may be respectively denoted as t1RIV,m, . . . , tNRESRIV,mRIV,m in chronological order, and the corresponding NRESRIV,m resources may be respectively denoted as t1RIV,m, . . . , tNRESRIV,mRIV,m. Optionally, slots t1RIV,m, . . . , tNRESRIV,mRIV,m are different from each other. Optionally, resources t1RIV,m, . . . , tNRESRIV,mRIV,m correspond to the same number of sub-channels, e.g., denoted as LsubCHRIV,m (e.g., representing LsubCHRIV,m consecutive sub-channels). Optionally, resources r1RIV,m, . . . , rNRESRIV,mRIV,m may be respectively referred to as a “second RIC resource”, . . . , a “(NRESRIV,m+1)-th RIC resource” corresponding to RICm. For example, if NRESRIV,m=2, then resources r1RIV,m and r2RIV,m may be respectively referred to as a second RIC resource and a third RIC resource corresponding to RICm (or TRIVm).


Optionally, NRESRIV,1= . . . =NRESRIV,M=NRESRIV. Optionally, NRESRIV is a predefined or configured or pre-configured value, or is determined by one or more predefined or configured or pre-configured parameters, or is indicated by the first coordination request, or is indicated by the first coordination information, or is determined in another manner. For example, NRESRIV=1. As another example, NRESRIV=2. As another example, NRESRIV=3. As another example, NRESRIV=4. As another example, NRESRIV=0.


Optionally, for m1∈{1, . . . , M}, m2∈{1, . . . , M}, and m1≠m2, NRESRIV,m1 and NRESRIV,m2 may be equal or unequal.


Optionally, the first coordination information indicates M “first RIC resource locations”, and each “first RIC resource location” may correspond to one “first RIC resource” (e.g., the M “first RIC resources” are sequentially denoted as r0RIV,m, . . . , rNRESRIV,mRIV,m, and slots in which the resources r0RIV,1, . . . , r0RIV,M are located are respectively denoted as t1RIV,ref, . . . , tMRIV,ref, and starting sub-channels being respectively denoted as nsubCH,0RIV,1,start, . . . , nsubCH,0RIV,M,start). For m∈{1, . . . , M}, the number of sub-channels corresponding to the resource r0RIV,m may be equal to LsubCHRIV,m.


Optionally, for m∈{1, . . . , M}, the resource r0RIV,m may be associated with RICm. For example, for RICm, the resource r0RIV,m may correspond to the “first resource” in the SL resource reservation procedure, and the resources r1RIV,m, . . . , rNRESRIV,mRIV,m may respectively correspond to the “second resource”, . . . , the “(NRESRIV,m+1)-th resource” in the SL resource reservation procedure.


Optionally, the “first RIC resource location” may refer to a time domain location, a frequency domain location, or both time domain and frequency domain locations of the corresponding “first RIC resource”.


Optionally, the resources r0RIV,1, . . . , r0RIV,M belong to the coordination resource set Optionally, the resources r0RIV,1, . . . , r0RIV,M do not belong to the coordination resource set SRESCO (e.g., the resources r0RIV,1, . . . , r0RIV,M may be considered as “virtual resources” used to provide reference locations for other resources).


Optionally, the slots t1RIV,ref, . . . tMRIV,ref may be indicated in one or more of the following manners:

    • For m∈{1, . . . , M}, the slot tmRIV,ref is indicated as Δ(t0,0RIV,ref,tmRIV,ref) Δ(tmRIV,ref,t0,0RIV,ref).
    • For m∈{1, . . . , M}, the slot tmRIV,ref is indicated as Δ(t0,mRIV,ref,tmRIV,ref) or Δ(t0,0RIV,ref,t0,mRIV,ref)
    • The slot t1RIV,ref is indicated as Δ(t0RIV,ref,t1RIV,ref) or Δ(t1RIV,ref,t0RIV,ref).
    • For m∈{2, . . . , M}, the slot tmRIV,ref is indicated as Δ(tm-1RIV,ref,tmRIV,ref) or Δ(tmRIV,ref,tm-1RIV,ref).


Wherein,





    • Optionally, t0,0RIV,ref=t0,0RIV, or t0,0RIV,ref=NEXT(t0,0RIV,D0,0RIV), or t0,0RIV,ref=PREV(t0,0RIV,D0,0RIV), where D0,0RIV may be a predefined or configured or pre-configured value (e.g., D0,0RIV=−1, or D0,0RIV=0, or D0,0RIV=1), or may be determined by one or more predefined or configured or pre-configured parameters, or may be indicated by the first coordination request, or may be indicated by the first coordination information, or may be related to LEN(WRESOURCECO).

    • Optionally, for m∈{1, . . . , M}, t0,mRIV,ref=t0,0RIV, or t0,mRIV,ref=NEXT(t0,0RIV,D0,mRIV), or t0,mRIF,ref=PREV(t0,0RIVD0,mRIV), where D0,mRIV may be equal to (m+F0,0RIV)·G0,0RIV+E0,0RIV, and any one among F0,0RIV, G0,0RIV and E0,0RIV may be a predefined or configured or pre-configured value (e.g., F0,0RIV=−1 or F0,0RIV=0 or F0,0RIV=1, and G0,0RIV=−1 or G0,0RIV=0 or G0,0RIV=1 or G0,0RIV=29 or G0,0RIV=30 or G0,0RIV=31 or G0,0RIV=32 or G0,0RIV=33, and E0,0RIV=−1 or E0,0RIV=0 or E0,0RIV=1), or may be determined by one or more predefined or configured or pre-configured parameters, or may be indicated by the first coordination request, or may be indicated by the first coordination information, or may be related to LEN(WRESOURCECO).





Optionally, for m∈{1, . . . , M}, tmRIV,ref and/or nsubCH,0RIV,m,start may be considered as part of RICm, and correspondingly, indications for tmRIV,ref and/or nsubCH,0RIV,m,start may be included in an indication for RICm (i.e., the M “first RIC resource locations” are not separately indicated). For example, RICm may be defined as one of the following:

    • (TRIVm,FRIVm,tmRIV,ref).
    • (TRIVm,FRIVm,Prsvp,m,tmRIV,ref).
    • (TRIVm,FRIVm,nsubCH,0RIV,m,start).
    • (TRIVm,FRIVm,Prsvp,m,nsubCH,0RIV,m,start).
    • (TRIVm,FRIVm,tmRIV,ref,nsubCH,0RIV,m,start).
    • (TRIVm,FRIVm,Prsvp,m,tmRIV,ref,nsubCH,0RIV,m,start).


Optionally, for m∈{1, . . . , M}, TRIVm may indicate NRESRIV,m and slot offsets Δ(tmRIV,ref,t1RIV,m), . . . , Δ(tmRIV,ref,tNRESRIV,mRIV,m) and FRIVm, may indicate starting sub-channels (e.g., respectively denoted as nsubCH,1RIV,m,start, . . . , nsubCH,NRESRIV,mRIV,m,start) respectively corresponding to resources r1RIV,m, . . . , tNRESRIV,mRIV,m and the number LsubCHRIV,m of sub-channels corresponding to each resource among resources r1RIV,m, . . . , tNRESRIV,mRIV,m. Specifically, for example, the definitions of the TRIV and the FRIV in the SL resource reservation procedure may be appropriately modified to be used to respectively explain TRIVm and FRIVm, wherein the modification may include one or more of the following:

    • Replacing the TRIV with TRIVm.
    • Replacing the FRIV with FRIVm.
    • Replacing the first resource with the first RIC resource.
    • Replacing the second resource with the second RIC resource.
    • Replacing the third resource with the third RIC resource.
    • Not using (or skipping, or discarding) the “first resource”.
    • Not using (or skipping, or discarding) the “first RIC resource”.
    • Replacing the slot t0SL,RES (or “the slot in which the SCI is received”) with the slot tmRIV,ref (i.e., “the first RIC resource location” corresponding to TRIVm).
    • A slot offset of the second resource is t1−T1SL,RES. T1SL,RES may be a predefined or configured or pre-configured value (e.g., T1SL,RES=−1 or T1SL,RES=0 or T1SL,RES=1), or may be determined by one or more predefined or configured or pre-configured parameters, or may be indicated by the first coordination request, or may be indicated by the first coordination information, or may be related to LEN(WRESOURCECO).
    • A slot offset of the third resource is t2−T2SL,RES. T2SL,RES may be a predefined or configured or pre-configured value (e.g., T2SL,RES=1, or T2SL,RES=0, or T2SL,RES=1), or may be determined by one or more predefined or configured or pre-configured parameters, or may be indicated by the first coordination request, or may be indicated by the first coordination information, or may be related to LEN(WRESOURCECO).
    • Replacing the slot offset t1 with the slot offset Δ(tmRIV,ref,t1RIV,m).
    • Replacing the slot offset t2 with the slot offset Δ(tmRIV,ref,t2RIV,m).
    • Replacing the starting sub-channel nsubCH,1start with the starting sub-channel nsubCH,1RIV,m,start.
    • Replacing the starting sub-channel nsubCH,2start with the starting sub-channel nsubCH,2RIV,m,start.
    • Replacing the SCI (or “the received SC”) with (TRIVm, FRIVm).
    • Replacing N with NRESRIV,m+1 (e.g., N may represent the resource r0RIV,m and the total number of resources corresponding to r1RIV,m, . . . ,rNRESRIV,mRIV,m).
    • Replacing NsubchannelSL with the number NsubchannelSL,uRESCO se of sub-channels of the resource pool uRESCO.
    • Configuring the value of sl-MaxNumPerReserve as a fixed value (e.g., 2 or 3).
    • Replacing sl-MaxNumPerReserve with another parameter (e.g., denoted as sl-MaxNumPerReserveRlC), wherein the value of sl-MaxNumPerReserveRIC may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters, or may be indicated by the first coordination request, or may be indicated by the first coordination information.


Optionally, for m∈{1, . . . , M} and i∈{1, . . . , NRESIRV,m}, Prsvp,m (or RICm) may indicate CRESEL,0RRI,m,i resources in the coordination resource set SRESCO, where CRESEL,0RRI,m,i may be an integer greater than or equal to 0, or an integer greater than or equal to 1. When CRESEL,0RRI,m,i≥1, the slots in which the CRESEL,0RRI,m,i resources are located may be respectively denoted as ti,1RRI,m, . . . , ti,CRESEL,0RRI,m,iRRI,m in chronological order, and the corresponding resources may be respectively denoted as ri,1RRI,m, . . . , ri,CRESEL,0RRI,m,iRRI,m. Optionally, in the frequency domain, each of the resources ri,1RRI,m, . . . , ri,CRESEL,0RRI,m,iRRI,m corresponds to the same sub-channel set (i.e., LsubCHRIV,m consecutive sub-channels with nsubCH,iRIV,m,start being the starting sub-channel) as the resource riRIV,m. Optionally, in the time domain, for j∈{1, . . . , CRESEL,0RRI,m,i}, ti,jRRI,m=NEXT(tiRIV,m,j×PRSVPRRI,m), where PRSVPRRI,m may be the number of logical slots corresponding to Prsvp,m (e.g., Prsvp,m represents the number of milliseconds in a corresponding resource reservation period, and








P
RSVP

RRI
,
m


=





T
max




u
RES
CO




1

0240


ms


×

P

rsvp
,
m






;




or Prsvp,m represents the number of logical slots in a corresponding resource reservation period, and P′rsvp,m=Prsvp,m), or may be equal to Prsvp,m. The CRESEL,0RRI,m,i resources may be referred to as periodically reserved resources corresponding to the resource riRIV,m.


Optionally, if RICm does not include Prsvp,m (or Prsvp,m is skipped, or Prsvp,m=Prsvp,0, wherein Prsvp,0 is a predefined or configured or pre-configured value, or is determined by one or more predefined or configured or pre-configured parameters, or is indicated by the first coordination request, or is indicated by the first coordination information, e.g., Prsvp,0=0), then CRESEL,0RRI,m,i=0.


Optionally, for m∈{1, . . . , M} and i∈{1, . . . , NRESRIV,m}, CRESEL,0RRI,m,i is equal to one among CRESELRRI,m,i, CRESELRRI,m,i+1, and CRESELRRI,m,i−1. Optionally CRESELRRI,m,i is a predefined or configured or pre-configured value, or is determined by one or more predefined or configured or pre-configured parameters, or is indicated by the first coordination request, or is indicated by the first coordination information.


Optionally, for m∈{1, . . . , M}, CRESELRRI,m,1= . . . =CRESEL,0RRI,m,NRESRIV,m=CRESELRRI,m, where CRESELRRI,m is a predefined or configured or pre-configured value, or is determined by one or more predefined or configured or pre-configured parameters, or is indicated by the first coordination request, or is indicated by the first coordination information.


Optionally, CRESELRRI,1= . . . =CRESELRRI,NRESRIV,m=CRESELRRI, where CRESELRRI is a predefined or configured or pre-configured value, or is determined by one or more predefined or configured or pre-configured parameters, or is indicated by the first coordination request, or is indicated by the first coordination information.


Optionally, for m∈{1, . . . , M} and i∈{1, . . . , NRESRIV,m}, CRESELRRI,m,i is related to one or more parameters (e.g., LWNDCO,RESOURCE, tWND,startCO,RESOURCE, or tWND,endCO,RESOURCE) of the coordination resource window and/or Prsvp,m and/or PRSVPRRI,m. For example, CRESELRRI,m,i is the maximum value of j that causes the slot ti,jRRI,m=NEXT(tiRIV,m,j×PRSVPRRI,m) to fall within the coordination resource window. As another example, if a first resource reservation period condition is satisfied, then







C
RESEL

RRI
,
m
,
i


=





T
SCAL
RRI


P
RSVP

RRI
,
m





.





As another example, if the first resource reservation period condition is not satisfied, then CRESELRRI,m,i=1 (or CRESELRRI,m,i=0, or CRESELRRI,m,i=2). As another example, if a second resource reservation period condition is satisfied, then CRESELRRI,m,i=1 (or CRESELRRI,m,i=0, or CRESELRRI,m,i=2). As another example, if the second resource reservation period condition is not satisfied, then







C
RESEL

RRI
,
m
,
i


=





T
SCAL
RRI


P
RSVP

RRI
,
m





.





Optionally, TSCALRRI may be related to one or more among LEN(WRESOURCECO), tiRIV,m, tstartWRESOURCECO or tendWRESOURCECO. For example, TSCALRRI=LEN(WRESOURCECO). As another example, TSCALRRI=LEN(WRESOURCECO)+1. As another example, TSCALRRI=LEN(WRESOURCECO)−1. As another example, TSCALRRI=Δ(tiRIV,m,tendWRESOURCECO). As another example, TSCALRRI=Δ(tiRIV,m,tendWRESOURCECO)+1. As another example, TSCALRRI=Δ(tiRIV,m,tendWRESOURCECO)−1. As another example, TSCALRRI=LEN(WRESOURCECO)−Δ(tstartWRESOURCECO,tiRIV,m) As another example, TSCALRRI=LEN(WRESOURCECO)−Δ(tstartWRESOURCECO,tiRIV,m)+1. As another example, TSCALRRI=LEN(WRESOURCECO)−Δ(tstartWRESOURCECO,tiRIV,m)−1.


Optionally, the first resource reservation period condition may include one or more of the following (in any combination of “and” or “or”):

    • PRSVPRRI,m<TSCALRRI.
    • PRSVPRRI,m≤TSCALRRI.


Optionally, the second resource reservation period condition may include one or more of the following (in any combination of “and” or “or”):

    • PRSVPRRI,m>TSCALRRI.
    • PRSVPRRI,m≥TSCALRRI.


Optionally, the first part of the first coordination information includes one or more of the following:

    • M.
    • The M RICs (e.g., RIC1, . . . , RICM in order).
    • The M “first RIC resources locations” (e.g., t1RIV,ref, . . . , tMRIV,ref in order).
    • The second coordination resource set type.
    • The second coordination request identifier.


Optionally, the second part of the first coordination information includes one or more of the following:

    • M.
    • The M RICs (e.g., RIC1, . . . , RICM in order).
    • The M “first RIC resources locations” (e.g., t1RIV,ref, . . . , tMRIV,ref in order).
    • The second coordination resource set type.
    • The second coordination request identifier.


Optionally, the coordination information MAC CE includes a “coordination information control element” field. Optionally, the content of the coordination information control element field includes one or more of the following parameters (e.g., arranged in the following order, or arranged in any other order, such as starting from the most significant bit, or starting from the least significant bit):

    • M.
    • The M RICs (e.g., RIC1, . . . , RICM in order).
    • The M first RIC resources locations (e.g., t1RIV,ref, . . . , tMRIV,ref in order).
    • The second coordination resource set type.
    • The second coordination request identifier.


Optionally, the length and/or type of the coordination information control element field may be related to one or more of the following:

    • The number NsubchannelSL,uRESCO of sub-channels of the resource pool uRESCO.
    • The number Nrsv_periodSL,uRESCO of resource reservation periods of the resource pool uRESCO.


Optionally, if the sum (e.g., denoted as LRAWCO,CI, and e.g., representing LRAWCO,CI bits) of the lengths of all parameters corresponding to the coordination information control element field is not a multiple (e.g., an integer multiple) of 8, then a bit ‘0’ is added at the end of the content of the coordination information control element field, so that the length (e.g., denoted as LMACCECO,RESSET, and e.g., representing LMACCECO,RESSET, bits) of the coordination information control element field is a multiple (e.g., an integer multiple) of 8. Specifically, for example, if the parameters corresponding to the coordination information control element field are sequentially {RIC1, . . . , RICM, r1RIV,ref, . . . , rMRIV,ref}, and for m∈{1, . . . , M}, the lengths of RICm and tmRIV,ref are respectively LONECO,RIC and LONECO,RIV,REF, then LRAWCO,RESET=M·(LONECO,RIC+LONECO,RIV,REF), and correspondingly, (8−(LRAWCO,RESSET mod 8)) bits ‘0’ are added at the end of the content of the coordination information control element field.


Optionally, for m∈{1, . . . , M}, RICm corresponds to a “RICm control element” field in the coordination information MAC CE. The type of the “RICm control element” field may be one among a plurality of predefined types.


Optionally, the type of the “RICm control element” field may be related to one or more of the following:

    • The number NsubchannelSL,uRESCO of sub-channels of the resource pool uRESCO.
    • The number Nrsv_periodSL,uRESCO of resource reservation periods of the resource pool uRESCO.


For example, for RIC=(TRIVm, FRIVm), the type of the “RICm control element” field is determined in one or more of the following manners:

    • If N1SC,RIC1≤NsubchannelSL,uRESCO≤N2SC,RIC1 then the type of the “RICm control element” field is a “first RIC control element type”. Specifically, for example, N1SC,RIC1=1, and N2SC,RIC1=6. FIG. 4 shows an example of the first RIC control element type.
    • If N3SC,RIC1≤NsubchannelSL,uRESCO≤N4SC,RIC1, then the type of the “RICm control element” field is a “second RIC control element type”. Specifically, for example, N3SC,RIC1=7, and N4SC,RIC1=27. FIG. 5 shows an example of the second RIC control element type.


As another example, for RICm=(TRIVm, FRIVm, Prsvp,m), the type of the “RICm control element” field is determined in one or more of the following manners:

    • If N1SC,RIC2≤NsubchannelSL,uRESCO≤N2SC,RIC2, then the type of the “RICm control element” field is a “third RIC control element type”. Specifically, for example, N1SC,RIC2=1, and N2SC,RIC2=2. FIG. 6 shows an example of the third RIC control element type.
    • If N3SC,RIC2≤NsubchannelSL,uRESCO≤N4SC,RIC2, then the type of the “RICm control element” field is a “fourth RIC control element type”. Specifically, for example, N3SC,RIC2=3, and N4SC,RIC2=17. FIG. 7 shows an example of the fourth RIC control element type.
    • If N5SC,RIC2≤NsubchannelSL,uRESCO≤N6SC,RIC2, then the type of the “RICm control element” field is a “fifth RIC control element type”. Specifically, for example, N5SC,RIC2=18, N6SC,RIC2=27. FIG. 8 shows an example of the fifth RIC control element type.


Optionally, if an SL transmission satisfies a second coordination condition, a second coordination operation is performed on the SL transmission.


Optionally, the second coordination condition may include one or more of the following (in any combination of “and” or “or”):

    • The inter-UE coordination function is not enabled.
    • The first coordination scheme is not enabled.
    • The inter-UE coordination function is enabled.
    • The first coordination scheme is enabled.
    • The 1st-stage SCI format associated with the SL transmission includes part or all of the coordination information.
    • The 2nd-stage SCI format associated with the SL transmission includes part or all of the coordination information (e.g., the 2nd-stage SCI format is SCI format 2-C, or the 2nd-stage SCI format is SCI format 2-D).
    • UE-B is incapable of receiving and/or processing the 1st-stage SCI format including the coordination information.
    • UE-B is incapable of receiving and/or processing the 2nd-stage SCI format (e.g., SCI format 2-C, or SCI format 2-D) including the coordination information.
    • UE-B is incapable of receiving and/or processing the coordination information included in the 1st-stage SCI format associated with the SL transmission.
    • UE-B is incapable of receiving and/or processing the coordination information included in the 2nd-stage SCI format associated with the SL transmission.
    • The source identifier indicated in the 2nd-stage SCI format associated with the SL transmission is not equal to the first destination layer-1 identifier.
    • The destination identifier indicated in the 2nd-stage SCI format associated with the SL transmission is not equal to the first source layer-1 identifier.
    • The coordination request identifier indicated in the 1st-stage SCI format associated with the SL transmission is not equal to the first coordination request identifier.
    • The coordination request identifier indicated in the 2nd-stage SCI format associated with the SL transmission is not equal to the first coordination request identifier.
    • The coordination resource set type indicated in the 1st-stage SCI format associated with the SL transmission is not equal to the first coordination resource set type.
    • The coordination resource set type indicated in the 2nd-stage SCI format associated with the SL transmission is not equal to the first coordination resource set type.
    • The “HARQ feedback enabled/disabled indicator” value indicated in the 2nd-stage SCI format associated with the SL transmission is “enabled”.
    • The “HARQ feedback enabled/disabled indicator” value indicated in the 2nd-stage SCI format associated with the SL transmission is “disabled”.


Optionally, the second coordination operation may include one or more of the following:

    • Discarding (or skipping) the 1st-stage SCI format associated with the SL transmission.
    • Discarding (or skipping) the 2nd-stage SCI format associated with the SL transmission.
    • Discarding (or skipping) the coordination information indicated in the 1st-stage SCI format associated with the SL transmission.
    • Discarding (or skipping) the coordination information indicated in the 2nd-stage SCI format associated with the SL transmission.
    • Discarding (or skipping) the coordination resource set indicated in the 1st-stage SCI format associated with the SL transmission.
    • Discarding (or skipping) the coordination resource set indicated in the 2nd-stage SCI format associated with the SL transmission.
    • Discarding (or skipping) the transport block carried in the SL transmission.
    • Generating a negative acknowledgment for the transport block (or data in the transport block) carried in the SL transmission. For example, a MAC layer entity of UE-B instructs a physical layer entity of UE-B to generate the negative acknowledgment.


Optionally, if a transport block satisfies a third coordination condition, a third coordination operation is performed on the transport block.


Optionally, the third coordination information processing condition may include one or more of the following (in any combination of “and” or “or”):

    • The inter-UE coordination function is not enabled.
    • The first coordination scheme is not enabled.
    • The inter-UE coordination function is enabled.
    • The first coordination scheme is enabled.
    • Data of the transport block has been successfully decoded (e.g., successfully decoded for the first time).
    • The transport block includes a coordination information MAC CE.
    • The 1st-stage SCI format associated with one or more SL transmissions carrying the transport block includes part or all of the coordination information.
    • The 2nd-stage SCI format associated with one or more SL transmissions carrying the transport block includes part or all of the coordination information (e.g., the 2nd-stage SCI format is SCI format 2-C, or the 2nd-stage SCI format is SCI format 2-D).
    • UE-B is capable of receiving and/or processing the 1st-stage SCI format including the coordination information.
    • UE-B is capable of receiving and/or processing the 2nd-stage SCI format (e.g., SCI format 2-C, or SCI format 2-D) including the coordination information.
    • UE-B has processed the coordination information included in the 1st-stage SCI format associated with one or more SL transmissions carrying the transport block.
    • UE-B has processed the coordination information included in the 2nd-stage SCI format associated with one or more SL transmissions carrying the transport block.


Optionally, the third coordination operation may include: discarding (or skipping) the coordination information MAC CE in the transport block.


Optionally, if a transport block satisfies a fourth coordination condition, then a fourth coordination operation is performed on the transport block.


Optionally, the fourth coordination condition may include one or more of the following (in any combination of “and” or “or”):

    • The inter-UE coordination function is not enabled.
    • The first coordination scheme is not enabled.
    • The inter-UE coordination function is enabled.
    • The first coordination scheme is enabled.
    • Data of the transport block has been successfully decoded (e.g., successfully decoded for the first time).
    • The transport block includes a coordination information MAC CE.
    • UE-B has not processed the 1st-stage SCI format that corresponds to any SL transmission carrying the transport block and that includes the coordination information.
    • UE-B has not processed the 2nd-stage SCI format (e.g., SCI format 2-C, or SCI format 2-D) that corresponds to any SL transmission carrying the transport block and that includes the coordination information.
    • UE-B has not processed the coordination information in the 1st-stage SCI format corresponding to any SL transmission carrying the transport block.
    • UE-B has not processed the coordination information in the 2nd-stage SCI format corresponding to any SL transmission carrying the transport block.


Optionally, the fourth coordination operation may include: processing the coordination information MAC CE (e.g., determining time domain and frequency domain locations of each resource in a corresponding coordination resource set sRESCO, performing resource selection/reselection, and so on).


Optionally, in Embodiment 1 of the present invention, t0,0RIV may be the slot t1CR, or the slot tstartWRESPONSECO or the slot tendWRESPONSECO, or the slot tstartWRESOURCECO, or the slot tstartWRESOURCECO.


Optionally, in Embodiment 1 of the present invention, “included in a MAC CE” may be replaced with “transmitted by using a MAC CE”.


Optionally, in Embodiment 1 of the present invention, “included in SCI” may be replaced with “transmitted by using SCI”.


Optionally, in Embodiment 1 of the present invention, “resource reservation period” may be replaced with “resource reservation interval”.


Optionally, in Embodiment 1 of the present invention, for m∈{1, . . . , M}, items in RICm may be arranged in any manner. For example, (TRIVm, FRIVm) may be replaced with (FRIVm, TRIVm). As another example, (TRIVm,FRIVm,tmRIV,ref) may be replaced with (tmref,TRIVm,FRIVm).


Optionally, in Embodiment 1 of the present invention, the resource pools uCR, uCI, and uRESCO are the same resource pool.


Optionally, in Embodiment 1 of the present invention, the number NsubchannelSL,u of sub-channels of a resource pool u may be configured or pre-configured by a higher-layer parameter sl-NumSubchannel of the resource pool u.


Optionally, in Embodiment 1 of the present invention, the number Nrsv_periodSL,u of resource reservation periods of a resource pool u may be equal to the number of resource reservation periods configured or pre-configured by a higher-layer parameter sl-ResourceReservePeriodList of the resource pool u.


Optionally, in Embodiment 1 of the present invention, “coordination information” may be replaced with “coordination resource set” where applicable.


Optionally, in Embodiment 1 of the present invention, the first SCI format and the third SCI format may be the same SCI format (e.g., referred to as a “first coordination SCI format”).


Optionally, the first coordination SCI format includes an “SCI format identifier” field (e.g., the SCI format identifier field may be the first field in the first coordination SCI format). If the SCI format identifier field indicates that the first coordination SCI format is used for a coordination request, then the remaining fields of the first coordination SCI format are used to indicate the first coordination request. If the SCI format identifier field indicates that the first coordination SCI format is used for coordination information, then the remaining fields of the first coordination SCI format are used to indicate the first coordination information.


Optionally, in Embodiment 1 of the present invention, to determine the size of the first coordination SCI format, one or more padding operations in the following are performed:

    • If NSCI,1CO,REQUEST<NSCI,1CO,INFO, then the first coordination SCI format used for a coordination request is padded with bits ‘0’ until the size of a payload of the first coordination SCI format used for the coordination request is equal to NSCI,1CO,INFO.
    • If NSCI,1CO,INFO<NSCI,1CO,REQUEST, then the first coordination SCI format used for coordination information is padded with bits ‘0’ until the size of a payload of the first coordination SCI format used for the coordination information is equal to NSCI,1CO,REQUEST.
    • If NSCI,1CO,REQUEST<NSCI,1CO, then the first coordination SCI format used for a coordination request is padded with bits ‘0’ until the size of a payload of the first coordination SCI format used for the coordination request is equal to NSCI,1CO.
    • If NSCI,1CO,INFO<NSCI,1CO, then the first coordination SCI format used for coordination information is padded with bits ‘0’ until the size of a payload of the first coordination SCI format used for the coordination information is equal to NSCI,1CO.


NSCI,1CO,REQUEST and NSCI,1CO,INFO are respectively the sizes of information bits (or, payloads) of the first coordination SCI format used for a coordination request and the first coordination SCI format used for coordination information, and NSCI,1CO may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters.


Optionally, in Embodiment 1 of the present invention, the second SCI format and the fourth SCI format may be the same SCI format (e.g., referred to as a “second coordination SCI format”, and specifically, e.g., SCI format 2-C). Optionally, the second coordination SCI format includes an “SCI format identifier” field (e.g., the SCI format identifier field may be the first field in the second coordination SCI format). If the SCI format identifier field indicates that the second coordination SCI format is used for a coordination request, then the remaining fields of the second coordination SCI format are used to indicate the first coordination request. If the SCI format identifier field indicates that the second coordination SCI format is used for coordination information, then the remaining fields of the second coordination SCI format are used to indicate the first coordination information.


Optionally, in Embodiment 1 of the present invention, to determine the size of the second coordination SCI format, one or more padding operations in the following are performed:

    • If NSCI,2CO,REQUEST<NSCI,2CO,INFO, then the second coordination SCI format used for a coordination request is padded with bits ‘0’ until the size of a payload of the second coordination SCI format used for the coordination request is equal to NSCI,2CO,INFO.
    • If NSCI,2CO,INFO<NSCI,2CO,REQUEST, then the second coordination SCI format used for coordination information is padded with bits ‘0’ until the size of a payload of the second coordination SCI format used for the coordination information is equal to NSCI,2CO,REQUEST.
    • If NSCI,2CO,REQUEST<NSCI,2CO, then the second coordination SCI format used for a coordination request is padded with bits ‘0’ until the size of a payload of the second coordination SCI format used for the coordination request is equal to NSCI,2CO.
    • If NSCI,2CO,INFO<NSCI,2CO, then the second coordination SCI format used for coordination information is padded with bits ‘0’ until the size of a payload of the second coordination SCI format used for the coordination information is equal to NSCI,2CO.


NSCI,1CO,REQUEST and NSCI,1CO,INFO are respectively the sizes of information bits (or, payloads) of the second coordination SCI format used for a coordination request and the second coordination SCI format used for coordination information, and NSCI,1CO may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters.


Optionally, in Embodiment 1 of the present invention, Tproc,1CO may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters.


Optionally, in Embodiment 1 of the present invention, Tproc,2CO may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters.


Optionally, in Embodiment 1 of the present invention, Tproc,3CO may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters.


Optionally, in Embodiment 1 of the present invention, any one among Tproc,1CO, Tproc,2CO and Tproc,3CO may be equal to any one of the following:

    • 0.
    • Tproc,0SL.
    • Tproc,0SL+1.
    • Tproc,0SL−1.
    • Tproc,1SL.
    • Tproc,1SL+1.
    • Tproc,1SL−1.
    • max(Tproc,0SL,Tproc,1SL).
    • min(Tproc,0SL,Tproc,1SL).
    • Tproc,0SL+Tproc,1SL.
    • Tproc,0SL+Tproc,1SL+1.
    • Tproc,0SL+Tproc,1SL−1.
    • Tproc,0SL−Tproc,1SL.
    • |Tproc,0SL−Tproc,1SL|.
    • Tproc,1SL−Tproc,0SL.
    • |Tproc,1SL−Tproc,0SL|.


      wherein
    • Tproc,0 may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters. Tproc,0 may be related to μ. For example, if μ=0, then Tproc,0=1. As another example, if μ=1, then Tproc,0=1. As another example, if μ=2, then Tproc,0=2. As another example, if μ=3, then Tproc,0=4.
    • Tproc,1 may be a predefined or configured or pre-configured value, or may be determined by one or more predefined or configured or pre-configured parameters.


Tproc,1 may be related to μ. For example, if μ=0, then Tproc,1=3. As another example, if μ=1, then Tproc,1=5. As another example, if μ=2, then Tproc,1=9. As another example, if μ=3, then Tproc,1=17.


In this way, according to the description of Embodiment 1, provided in the present invention is a method, in which MAC CE field types corresponding to resource indication combinations of different lengths are determined for different resource pool size ranges, thereby effectively reducing overhead of indicating a coordination resource set indication in a MAC CE, and enabling transmission of inter-UE coordination information to be efficiently completed. In addition, the value of the “first resource location” is flexibly indicated, so that a resource in any slot in a corresponding coordination resource window can be efficiently indicated in a resource indication combination.


In the present invention, “inter-UE coordination” and other related terms (e.g., “coordination information”, “coordination request”, “preferred resource”, “non-preferred resource”, “sidelink coordination control information”, “physical sidelink coordination information channel/signal”, “physical sidelink coordination request channel/signal”, and “coordination resource set” field, etc.) may be defined by functions thereof in a system and/or a corresponding procedure and/or corresponding signaling. When applied to a specific system, the terms may be replaced with other names.


Variant Embodiment

Hereinafter, FIG. 9 is used to illustrate user equipment that can perform the method performed by user equipment described in detail above in the present invention as a variant embodiment.



FIG. 9 shows a block diagram of user equipment (UE) according to the present invention.


As shown in FIG. 9, the user equipment (UE) 90 includes a processor 901 and a memory 902. The processor 901 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like. The memory 902 may include, for example, a volatile memory (such as a random access memory (RAM)), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories. etc. The memory 902 has program instructions stored thereon. The instructions, when run by the processor 901, may perform the method performed by user equipment as described above in detail in the present invention.


The method and related equipment according to the present invention have been described above in combination with preferred embodiments. It should be understood by those skilled in the art that the method shown above is only exemplary, and the above embodiments can be combined with one another as long as no contradiction arises. The method of the present invention is not limited to the steps or sequences illustrated above. The network node and user equipment shown above may include more modules, for example, modules that may be developed or developed in the future and that may be used for a base station, an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Mobility Management Entity (MME), a Serving Gateway (S-GW), or UE. Various identifiers shown above are only exemplary, and are not meant for limiting the present invention. The present invention is not limited to specific information elements serving as examples of these identifiers. A person skilled in the art could make various alterations and modifications according to the teachings of the illustrated embodiments. Those skilled in the art should understand that part or all of the mathematical expressions, mathematical equations, or mathematical inequations may be simplified or transformed or rewritten to some extent, for example, incorporating constant terms, or interchanging two addition terms, or interchanging two multiplication terms, or moving a term from the left side of an equation or inequation to the right side after changing the plus or minus sign thereof, or moving a term from the right side of an equation or inequation to the left side after changing the plus or minus sign thereof or the like. Mathematical expressions, mathematical equations, or mathematical inequations before and after the simplification or transformation or rewriting may be considered to be equivalent to each other.


It should be understood that the above-described embodiments of the present invention may be implemented by software, hardware, or a combination of software and hardware. For example, various components in the base station and user equipment in the above embodiments can be implemented by multiple devices, and these devices include, but are not limited to: an analog circuit device, a digital circuit device, a digital signal processing (DSP) circuit, a programmable processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), and the like.


In the present invention, the term “base station” may refer to a mobile communication data and/or control switching center having specific transmission power and a specific coverage area, and, for example, has functions such as resource allocation and scheduling, and data reception and transmission. “User equipment” may refer to a user mobile terminal, for example, including terminal devices that can communicate with a base station or a micro base station wirelessly, such as a mobile phone, a laptop computer, and the like.


In addition, the embodiments of the present invention disclosed herein may be implemented on a computer program product. More specifically, the computer program product is a product provided with a computer-readable medium having computer program logic encoded thereon. When executed on a computing device, the computer program logic provides related operations to implement the above technical solutions of the present invention. When executed on at least one processor of a computing system, the computer program logic causes the processor to perform the operations (the method) described in the embodiments of the present invention. Such setting of the present invention is typically provided as software, codes and/or other data structures provided or encoded on the computer-readable medium, e.g., an optical medium (e.g., compact disc read-only memory (CD-ROM)), a flexible disk or a hard disk and the like, or other media such as firmware or micro codes on one or more read-only memory (ROM) or random access memory (RAM) or programmable read-only memory (PROM) chips, or a downloadable software image, a shared database and the like in one or more modules. Software or firmware or such configuration may be installed on a computing device such that one or more processors in the computing device perform the technical solutions described in the embodiments of the present invention.


In addition, each functional module or each feature of the base station device and the terminal device used in each of the above embodiments may be implemented or executed by a circuit, which is usually one or more integrated circuits. Circuits designed to execute various functions described in the present description may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs) or general-purpose integrated circuits, field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic, or discrete hardware components, or any combination of the above devices. The general-purpose processor may be a microprocessor, or the processor may be an existing processor, a controller, a microcontroller, or a state machine. The aforementioned general-purpose processor or each circuit may be configured by a digital circuit or may be configured by a logic circuit. Furthermore, when advanced technology capable of replacing current integrated circuits emerges due to advances in semiconductor technology, the present invention can also use integrated circuits obtained using this advanced technology.


While the present invention has been illustrated in combination with the preferred embodiments of the present invention, it will be understood by those skilled in the art that various modifications, substitutions, and alterations may be made to the present invention without departing from the spirit and scope of the present invention. Therefore, the present invention should not be limited by the above-described embodiments, but should be defined by the appended claims and their equivalents.

Claims
  • 1-2. (canceled)
  • 3. A user equipment (UE), comprising: a processor; anda memory, having instructions stored therein,wherein the instructions, when run by the processor, perform:determining contents of sidelink control information (SCI) format 2-C, wherein: candidate values of a field in the SCI format 2-C include a first value and a second value;the first value indicates that the SCI format 2-C is used for conveying inter-UE coordination information; andthe second value indicates that the SCI format 2-C is used for conveying a request for inter-UE coordination information, andtransmitting the SCI format 2-C.
  • 4. A user equipment (UE), comprising: a processor; anda memory, having instructions stored therein,wherein the instructions, when run by the processor, perform:receiving sidelink control information (SCI) format 2-C, wherein: candidate values of a field in the SCI format 2-C include a first value and a second value;the first value indicates that the SCI format 2-C is used for conveying inter-UE coordination information; andthe second value indicates that the SCI format 2-C is used for conveying a request for inter-UE coordination information.
  • 5. A method performed by user equipment (UE), the method comprising: determining contents of sidelink control information (SCI) format 2-C, wherein: candidate values of a field in the SCI format 2-C include a first value and a second value;the first value indicates that the SCI format 2-C is used for conveying inter-UE coordination information; andthe second value indicates that the SCI format 2-C is used for conveying a request for inter-UE coordination information, andtransmitting the SCI format 2-C.
Priority Claims (1)
Number Date Country Kind
202210019400.1 Jan 2022 CN national
PCT Information
Filing Document Filing Date Country Kind
PCT/CN2023/070676 1/5/2023 WO