System and method for signaling scheme for propagation type indication and resource indication

Abstract

The present disclosure generally relates to systems and methods for signaling schemes for propagation type indications and resource indications. Methods, systems, and devices for signaling in propagation type indication of a wireless communication system may include receiving, at a first user equipment (UE), a first level sidelink control information (SCI) format from a second UE; decoding the first level SCI format; determining a second level SCI format using the decoded first level SCI format; decoding the second level SCI format; and determining a sidelink feedback state using the second level SCI format. The sidelink feedback state may indicate whether sidelink feedback is enabled. The second level SCI content may include a distance setting associated with a communication range between the first UE and the second UE.

Description

[0001] This application is a divisional application of the application with international application number PCT / CN2021 / 085720, international application date April 6, 2021, date of entry into the Chinese national phase September 30, 2022, national application number 202180026785.8, and invention name “System and method for signaling scheme for propagation type indication and resource indication”. Technical Field

[0002] The present application relates generally to wireless communication systems. Background Art

[0003] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is generally referred to as Worldwide Interoperability for Microwave Access (WiMAX) by industry organizations; and the IEEE 802.11 standard for wireless local area networks (WLANs), which is generally referred to as Wi-Fi by industry organizations. In the 3GPP radio access network (RAN) in the LTE system, the base station may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as an evolved Node B, enhanced Node B, eNodeB, or eNB) and / or a radio network controller (RNC) in the E-UTRAN, which communicates with a wireless communication device referred to as a user equipment (UE). In the fifth generation (5G) wireless RAN, the RAN node may include a 5G node, an NR node, or a gNodeB (gNB).

[0004] The RAN uses radio access technologies (RATs) to communicate between RAN nodes and UEs. The RAN may include a Global System for Mobile Communications (GSM), an Enhanced Data Rate for GSM Evolution (EDGE) RAN (GERAN), a Universal Terrestrial Radio Access Network (UTRAN), and / or an E-UTRAN, which provides access to communication services through a core network. Each of the RANs operates according to a specific 3GPP RAT. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements the Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, and the E-UTRAN implements the LTE RAT. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0006] Figure 1 A diagram is shown illustrating resource reservation and indication in LTE V2X according to certain embodiments.

[0007] Figure 2 A diagram is shown showing resource reservation and indication in NR V2X according to certain embodiments.

[0008] Figure 3 A process is shown for a signaling scheme for propagation type indication according to certain embodiments.

[0009] Figure 4 A process is shown for a signaling scheme for propagation type indication according to certain embodiments.

[0010] Figure 5 A process is shown for a signaling scheme for propagation type indication according to certain embodiments.

[0011] Figure 6 A process for a signaling scheme for resource indication according to certain embodiments is shown.

[0012] Figure 7 A diagram is shown illustrating side link channel occupancy over-the-air (SL CR) assessment according to certain embodiments.

[0013] Figure 8 An exemplary service-based architecture is shown in accordance with certain embodiments.

[0014] Fig. 9 A UE according to one embodiment is shown.

[0015] Fig.10 A network node according to one embodiment is shown. DETAILED DESCRIPTION

[0016] Second level SCI

[0017] In the new radio (NR) vehicle-to-everything (V2X) communication, two levels of sidelink control information (SCI) are supported. Level 1 SCI is carried on the physical sidelink control channel (PSCCH) and may include polarity coding adopted by NR downlink control information and applied to PSCCH. Level 2 SCI is carried on the physical sidelink shared channel (PSSCH) and may include polarity coding applied to level 2 SCI and used for the physical downlink control channel (PDCCH).

[0018] The level 1 SCI content may include one or more of the following: priority bit (e.g., 3 bits), PSSCH frequency and time resource allocation, resource reservation period, demodulation reference signal (DMRS) mode (e.g., if more than 1 mode is configured per resource pool), level 2 SCI format, beta_offset indicator, DMRS port number (e.g., 1 bit), modulation and coding scheme (MCS) (e.g., 5 bits), and reserved bits (e.g., all zeros) (e.g., 2-4 bits). Each resource pool may provide a single level 1 SCI format, and the resource size may be fixed.

[0019] The level 2 SCI content may include a cyclic redundancy check (CRC) (e.g., 24 bits) and additional fields as needed. Table 1 below shows exemplary level 2 SCI content fields for various level 2 SCI formats, including, for example, broadcast, unicast without feedback, multicast without feedback, unicast with feedback, multicast option 1 with feedback, and multicast option 2 with feedback. The level 2 SCI content fields include, for example, source ID; destination ID; hybrid automatic repeat request (HARQ) ID, new data indicator (NDI), redundancy version (RV); channel state information (CSI) request; and communication range and area ID. Table 1 shows each field that exists for a specific format, and exemplary bits for each content field. The total number of bits without (w / o) CRC and the reserved bits for each format are also shown in Table 1. As shown in Table 1, only CSI requests may be provided for unicast formats, and only communication range and area IDs may be provided for multicast option 1 with feedback. For example, the communication range and area ID are related to the following items: the communication range between the transmitting user equipment (UE) and the receiving UE. For example, the communication range is a distance setting associated with the communication range between a receiving UE and a transmitting UE.

[0020]

[0021] Table 1

[0022] Feedback associated with the Level 2 SCI format included in Table 1 may include an acknowledgement (ACK) and / or a negative acknowledgement (NACK) indicating to the transmitting UE whether the receiving UE successfully received the transmission from the transmitting UE. If the receiving UE successfully received the transmission, an ACK may be transmitted. If the receiving UE did not successfully receive the transmission, a NACK may be transmitted. For example, in a Level 2 SCI, a unicast with feedback may include both an ACK and a NACK, a multicast with feedback option 1 may include only a NACK, and a multicast with feedback option 2 may include both an ACK and a NACK.

[0023] Multicast HARQ Feedback Option 1

[0024] For example, option 1 with feedback multicast may include only HARQ NACK. Here, in the transmission from the transmitter UE to the receiver UE, if the receiver UE decodes the PSSCH, it may not provide feedback, and if the receiver UE does not decode the PSSCH, it may only provide feedback NACK. A single physical sidelink feedback channel (PSFCH) resource may be shared by all receiver UEs that sent NACK feedback.

[0025] For example, feedback-based multicast option 1 may include distance-based feedback. If the transmitter UE (Tx UE) position is not available, distance-based feedback is not used. If the receiver UE (Rx UE) position is not available, the radio access network 2 (RAN2) may process the feedback. For example, the transmitter-receiver (Tx-Rx) distance may be between the center position of the indicated area of ​​the Tx UE closest to the Rx UE and the precise position of the Rx UE itself. For example, the Tx UE may send the area ID to the Rx UE to which the Tx UE belongs. If its distance to the Tx UE is greater than the defined communication range requirement (e.g., the distance is out of range), the Rx UE may not provide feedback. In addition, the Tx UE position may be carried in a level 2 SCI for distance calculation of the Rx UE, wherein the area may be preconfigured relative to a geographic area, the area ID may be associated with the location of the Tx UE, and the area length and area width may always be the same and may be configured to be, for example, one of 5 meters, 10 meters, 20 meters, 30 meters, 40 meters, and 50 meters. For example, the communication range requirement may be explicitly indicated in the Level 2 SCI using, for example, 4 bits, where the distances may include, for example, 20, 50, 80, 100, 120, 150, 180, 200, 220, 250, 270, 300, 320, 350, 370, 400, 420, 450, 480, 500, 550, 600, 700, 1000 reserve meters. Reserve implies for future use.

[0026] Resource Indication in LTE V2X

[0027] Figure 1A diagram 100 is shown, which shows resource reservation and indication for the current transport block (TB) in LTE V2X according to certain embodiments. For the current TB, there may be two transmissions, for example: an initial transmission TB 102 and a retransmission TB 104. Since in the example shown in diagram 100, the resource reservation window has 16 time slots, there may be up to 16 transmissions for the current TB. Each transmission may have an associated SCI. For example, in the resource reservation for the current TB, a maximum of Nmax=2 side link resources may be reserved in the SCI for blind retransmission, and SCI signaling may be allowed to indicate one or two resources. For each resource, the same number of subchannels may be included. Resource reservation may include full flexibility in the time and frequency position of resources in the resource reservation window. In the example of diagram 100, the time gap between all reserved resources indicated in the SCI may be less than 16 time slots.

[0028] The SCI may include a "resource index" field that indicates to the receiving UE whether the current resource is a first resource (e.g., with a forward indication) or a second resource (e.g., with a backward indication). Figure 1 In the example, the resource index for the initial transmission TB 102 in the SCI may indicate that the current resource is the first resource because it includes the forward indication 106. The initial transmission TB 102 may retain the retransmission in the SCI. For example, the resource index for the retransmission TB 104 in the SCI may indicate that the current resource is the second resource because it indicates the backward indication 108. The retransmission TB 104 may indicate its own resources and past resources via the backward indication 108.

[0029] Resource indication in NR V2X

[0030] Figure 2A diagram 200 is shown illustrating resource reservation and indication in NR V2X for a current TB according to certain embodiments. For a current TB, there may be three transmissions, for example: an initial transmission TB 202, a retransmission TB 204, and a retransmission TB 206. Since in the example shown in diagram 200, the resource reservation window has 32 time slots, there may be up to 32 transmissions for the current TB. Each transmission may have an associated SCI. For example, in resource reservation for a current TB, up to Nmax sidelink resources are reserved in the SCI, and each resource pool may be preconfigured as two sidelink resources or three sidelink resources. For example, SCI signaling may be allowed to indicate one, two, or three resources. The time resource may indicate and reflect: (1) a time gap between a first resource and a second resource; and (2) a time gap between a first resource and a third resource. The frequency resource may indicate and may reflect: (1) a starting subchannel index of a second resource; (2) a starting subchannel index of a third resource; and (3) the number of subchannels for each resource. In the example shown in diagram 200 , initial transmission TB 202 points to retransmission TB 204 via forward indication 208 , and points to retransmission TB 206 via forward indication 210 .

[0031] The RAN1#100e protocol indicates the selection the next time one of the following options 1, 2 or 3 regarding the backward and forward indications is satisfied.

[0032] Option 1: There is no separate field in the first-level SCI to indicate the resource index for the purpose of backward indication, that is, backward indication is not supported. In option 1, the initial transmission TB 202 points to the retransmission TB 204 via the forward indication 208 and points to the retransmission TB 206 via the forward indication 210, the retransmission TB 204 points to the retransmission TB 206 via the forward indication, and the retransmission TB 206 does not have a forward or backward indication.

[0033] Option 2: When the resource pool has periodic reservation enabled, a 1-bit separate field in the first-level SCI indicates a resource index for the purpose of backward indication. In option 2, the initial transmission TB 202 points to the retransmission TB 204 via the forward indication 208 and to the retransmission TB 206 via the forward indication 210, the retransmission TB 204 points to the retransmission TB 206 via the forward indication and to the initial transmission TB 202 via the backward indication, and the retransmission TB 206 points to the initial transmission TB 202 via the backward indication and has no forward indication.

[0034] Option 3: When the resource pool has periodic reservation enabled, a separate field of ceil(log2(Nmax)) bits in the first-level SCI indicates a resource index for the purpose of backward indication. In option 3, the initial transmission TB 202 points to the retransmission TB 204 via the forward indication 208 and to the retransmission TB 206 via the forward indication 210, the retransmission TB 204 points to the retransmission TB 206 via the forward indication, and the retransmission TB 206 points to the initial transmission TB 202 via the backward indication and to the retransmission TB 204 via the backward indication and has no forward indication.

[0035] In some embodiments, the second level SCI format of the present disclosure is designed to provide certain indications. For example, a signaling scheme for propagation type indication is provided.

[0036] For example, in one embodiment, two second-level SCI formats may be defined. The first format is used for broadcast, unicast, and multicast without feedback; multicast option 2 and unicast with feedback. The second format may be used for multicast option 1. Here, the field of the second-level SCI format in the first-level SCI may be 2 bits to indicate one of the two second-level SCI formats. The last two code points of this field may be reserved for future use.

[0037] For example, in one embodiment, for the first format of the second level SCI, an additional bit is included in the second level SCI to indicate whether HARQ feedback is disabled. The first format of the second level SCI is used for multicast option 2 and unicast with feedback. The PSFCH resource determination scheme is different for these two types of broadcasts. For example, the PSFCH resources for unicast are determined only by the layer 1 source ID, while the PSFCH resources for multicast option 2 are determined by both the layer 1 source ID and the group member ID. Therefore, if HARQ feedback is enabled, the PSFCH resource determination scheme can be indicated.

[0038] For example, in one embodiment, for the first format of the second-level SCI, an additional bit is included in the second-level SCI to indicate the PSFCH resource determination scheme. Polar coding for PDCCH is applied to the second-level SCI. The CRC length of the second-level SCI is 24 bits, which is the same as the CRC length of PDCCH. The 24-bit CRC polynomial is designed to support the early termination function of polar decoding, which is valuable for UEs with limited processing power and energy consumption. In the side link, the same polar decoding is applied early termination at the Rx UE to save processing time and energy consumption.

[0039] In some examples, a shorter CRC length for the second-level SCI may be used to reduce overhead. However, the payload size of the second-level SCI may be greater than 30 bits, which may be similar to the fallback DCI payload size. Since the fallback DCI uses a 24-bit CRC, the same CRC length may apply to the second-level SCI.

[0040] Signaling scheme for propagation type indication (1-1)

[0041] Figure 3 A process 300 of a signaling scheme for propagation type indication according to certain embodiments is shown. It should be noted that, as used herein, a level 1 SCI format may also be referred to as a first level SCI format (and vice versa), and a level 2 SCI format may also be referred to as a second level SCI format (and vice versa). In block 302, at a UE, a level 1 SCI format is received and decoded. For example, at a first UE, a level 1 SCI format is received from a second UE. For example, a level 1 SCI format may include a single format. In block 304, a level 2 SCI format is determined by the level 1 SCI format decoded in block 302. For example, a level 2 SCI format may be format 1, which includes broadcast, unicast without feedback, multicast without feedback, multicast HARQ feedback option 2, and unicast with feedback format. Otherwise, a level 2 SCI format may be format 2, which is multicast HARQ feedback option 1. If the level 2 SCI format is determined to be format 2, the process 300 continues to block 306, which will be explained below. If the Level 2 SCI format is determined to be one of the formats in Format 1, process 300 continues to block 308 .

[0042] In block 308, at the UE, the 2-level SCI format is decoded. In some embodiments, the decoding allows determination of whether feedback is enabled. For example, in some embodiments, in the 2-level SCI format field, 1 bit is used to indicate whether side link feedback is enabled. For example, for broadcast format, unicast without feedback format, and multicast without feedback format, the bit is zero. For example, for multicast HARQ feedback option 2 and unicast with feedback format, the bit is one. In block 310, the 2-level SCI format decoded in block 308 is used to determine the side link feedback state (e.g., whether side link feedback is enabled or disabled). If feedback is not enabled (e.g., the bit in the 2-level SCI format field for indicating whether side link feedback is enabled is zero), HARQ feedback is not enabled, as shown in block 312. Here, for example, the 2-level SCI format is broadcast, unicast without feedback, or multicast without feedback.

[0043] For example, if feedback is enabled (e.g., the bit in the Level 2 SCI format field that indicates whether sidelink feedback is enabled is one), the Level 2 SCI format is multicast HARQ feedback option 2 or unicast with feedback. Process 300 therefore continues to box 314, in which the PSFCH resource determination scheme is determined. In certain embodiments, if feedback is enabled, 1 bit is used to indicate the PSFCH resource determination scheme. For example, if the PSFCH resource determination scheme is determined by the source ID, the bit is zero. If the PSFCH resources are determined by the source ID and the group member ID, the bit is one. In unicast, the PSFCH resources are determined by the source ID, so the bit is zero. For multicast HARQ option 2, the PSFCH resources are determined by the source ID and the group member ID, so the bit is one.

[0044] As described above, if at box 304, the 2-level SCI format is determined to be format 2, i.e., multicast HARQ feedback option 1, the process 300 continues to box 306. At box 306, it is determined that since the format is multicast HARQ feedback option 1, only NACK feedback is available. In some embodiments, only distance-based multicast option 1 NACK feedback is supported. In some other embodiments, both distance-based multicast option 1 NACK feedback and non-distance-based multicast option 1 NACK feedback are supported. For example, in order to support non-distance-based multicast option 1 NACK feedback, in the 2-level SCI content, the communication range requirement field is set to infinity. Therefore, no matter what the distance between the Tx UE and the Rx UE is, the HARQ feedback is always triggered and NACK feedback will be sent for PSSCH decoding errors. Therefore, this makes the actual distance between the Tx UE and the Rx UE irrelevant in the non-distance-based multicast option 1 NACK feedback. For example, the communication range requirement may be (pre)configured to an infinite value and the level 2 SCI content may have a code point indicating the infinite communication range requirement. For example, non-distance based multicast option 1 NACK feedback may be enabled or disabled by resource pool (pre)configuration, thereby configuring the 4 bits of the range requirement to infinity.

[0045] For example, in some embodiments, support for non-distance-based multicast HARQ feedback option 1 is based on resource pool (pre) configuration. If the (pre) configured communication range requirement includes an infinity value, then when the configured communication range requirement includes an infinity value and the value is indicated in the SCI, non-distance-based multicast HARQ feedback option 1 is applied. Here, the sidelink multicast HARQ feedback options can be distinguished by different second-level SCI formats. In other words, for example, one second-level SCI format can be used for multicast HARQ feedback option 1, and another second-level SCI format can be used for multicast HARQ feedback option 2 and broadcast and unicast.

[0046] For example, in some embodiments, different second-level SCI formats may be used for multicast HARQ feedback option 1 and option 2. Since one second-level SCI format is used for multicast HARQ feedback option 1, it may not include another flag indicating whether HARQ feedback is enabled or disabled. However, for another second-level SCI format used for broadcast, unicast, and multicast HARQ feedback option 2, a flag may be used to indicate whether HARQ feedback is enabled. This scheme indicates to the receiver UE whether HARQ feedback is enabled or disabled.

[0047] For example, in some embodiments, in the second level SCI format for broadcast, unicast, and multicast option 2, a flag may be used to indicate whether HARQ feedback is enabled.

[0048] Signaling scheme for propagation type indication (1-2)

[0049] Figure 4 A process 400 for a signaling scheme for propagation type indication according to certain embodiments is shown. At box 402, at a first UE, a first level SCI format is received and decoded. For example, at the first UE, a first level SCI format is received from a second UE. A second level SCI format is determined by the decoded first level SCI format. For example, the level 2 SCI format can be format 1, which includes: broadcast, unicast, and multicast without feedback; multicast HARQ feedback option 2; unicast with feedback; and non-distance-based multicast HARQ option 1 format. Otherwise, the level 2 SCI format can be format 2, which is distance-based multicast HARQ feedback option 1.

[0050] In box 404, determine the feedback option field of the second-level SCI determination format. In some embodiments, there is a joint indication of HARQ enable / disable and feedback options using two bits. For example, when there is HARQ feedback, these two bits are "00", and these two bits appear when the 2-level SCI format is broadcast, unicast without feedback, or multicast without feedback. For example, when there is HARQ feedback for multicast option 2, these two bits are "01". Here, depending on the source ID and group member ID, ACK / NACK feedback appears with PSFCH resources. For example, when there is HARQ feedback for multicast option 1, these two bits are "10". Here, depending on the source ID, non-distance-based NACK exists with PSFCH resources. For example, when there is HARQ feedback for unicast, these two bits are "11". Here, depending on the source ID, AC / NACK feedback appears with PSFCH resources.

[0051] At block 406, a CSI request field of the second level SCI format is determined. The CSI request field may be enabled (i.e., set to one) or disabled (i.e., set to zero). At block 408, an error condition is determined. For example, an error condition is determined when the CSI request is one (enabled) and the joint indication of HARQ enable / disable and feedback option is "01" (i.e., HARQ feedback for multicast option 2) or "10" (i.e., HARQ feedback for multicast option 1).

[0052] Signaling scheme for propagation type indication (1-3)

[0053] Figure 5 A process 500 for a signaling scheme for propagation type indication according to certain embodiments is shown. At box 502, at a first UE, a first level SCI format is received and decoded. For example, at the first UE, a first level SCI format is received from a second UE. A second level SCI format is determined by the decoded first level SCI format. For example, the 2-level SCI format can be format 1, which includes: broadcast, unicast, and multicast without feedback; multicast HARQ feedback option 2; unicast with feedback; and non-distance-based multicast HARQ option 1 format. Otherwise, the 2-level SCI format can be format 2, which is distance-based multicast HARQ feedback option 1.

[0054] In box 504, the feedback option field and CSI request field of the second-level SCI determination format are determined. In box 506, the determination result of box 504 is used to determine the HARQ feedback scheme and CSI request indication. In some embodiments, there is a joint indication of HARQ enable / disable, feedback option and CSI request using three bits. For example, when the format is broadcast or multicast without feedback, the three bits are "000". For example, when the format is unicast with CSI request without feedback, the three bits are "001". For example, when the format is unicast with no feedback and no CSI request, the three bits are "010". For example, when the format is unicast with CSI request with feedback, the three bits are "011". For example, when the format is unicast with feedback and no CSI request, the three bits are "100". For example, when the format is non-distance-based multicast HARQ feedback option 1, the three bits are "101". For example, when the format is multicast HARQ feedback option 2, the three bits are "110". For example, three bits "111" are reserved but can be used for CSI request details, such as CSI reporting delay limit indication or CSI reference resource indication.

[0055] Signaling scheme for resource indication

[0056] Figure 6A process 600 is shown for a signaling scheme for resource indication according to certain embodiments. In certain embodiments, a resource pool (pre) configuration may be performed for the SCI resource index field length. For example, in block 602, the (pre) configuration for a level 2 SCI may be determined. In block 604, the (pre) configuration for the level 2 SCI may be adjusted by (pre) configuring the SCI resource index field length. For example, the resource index field length is part of the resource pool (pre) configuration for a PSCCH or PSSCH. In certain embodiments, the resource index field length range may be an enumeration of 0, 1, or 2. For example, a resource index field length of "0" means that there is no backward resource indication and the SCI has no resource index field.

[0057] For example, a resource index field length of "1" means that the SCI supports backward resource indication and the SCI resource index field has 1 bit. max = 2, resource index equal to 0 implies forward resource indication, while resource index equal to 1 implies backward resource indication. In addition, for example, for N max =3, a resource index equal to 0 implies a forward resource indication, and a resource index equal to 1 implies a backward resource indication for the second resource and a forward resource indication for the third resource.

[0058] In another example, the resource index field length "2" means that the SCI supports backward resource indication and the SCI resource index field has 2 bits. Here, for example, for N max = 2, resource index equal to 0 implies forward resource indication, and resource index equal to 1 implies backward resource indication. max =3, resource index equal to 0 implies forward resource indication, resource index equal to 1 implies backward resource indication for the second resource and forward resource indication for the third resource, and resource index equal to 2 implies backward resource indication.

[0059] Resource reselection trigger conditions

[0060] In certain embodiments, for example, a Mode 2 UE resource reselection trigger condition may occur when the UE selects resources for retransmission when it receives an initial transmission. In certain embodiments, for retransmission, the UE may reselect resources based on a transmission priority ranking. For example, the UE may reselect resources based on a NR uplink (UL) and NR sidelink (SL) transmission priority ranking, where NR UL transmissions may have a higher priority than NR SL transmissions. In another example, the UE may reselect resources based on a LTE SL and NE SL transmission priority ranking, where LTE SL may have a higher priority than NR SL transmissions. In another example, the UE may reselect resources based on a congestion control indicating channel availability for transmission.

[0061] Sidelink CR evaluation without resource preemption

[0062] Figure 7 A diagram 700 is shown illustrating a side link channel occupancy wireless (SLCR) evaluation according to certain embodiments. In certain embodiments, resources are released by a UE and are not counted in the SL CR evaluation. In certain embodiments, reserved resources seized by another UE are also not counted in the SL CR evaluation.

[0063] For example, in Figure 7 In FIG. 700 , diagram 700 includes a transmission pool 702 including resource 704 and resource 706. At time slot n of diagram 700 , SL CR is evaluated as the total number of subchannels used for its transmission in time slot [na, n-1] and permitted in time slot [n, n+b] divided by the total number of subchannels configured by [na, n+b] in transmission pool 702. In some embodiments, one or more resources (e.g., resource 704, resource 706) are released by the UE and are not counted in the SL CR evaluation. In some embodiments, one or more resources (e.g., resource 704, resource 706) are reserved by the UE and then preempted by another UE with higher priority data. In this case, these resources are not counted as used for SL CR evaluation. Conversely, resources that are not counted as used can be counted as not used for SL CR evaluation.

[0064] In some embodiments, if a transmission on a resource is dropped due to UL-SL priority or high channel busy rate (CBR), the resource is not counted as used for SL CR evaluation. In some embodiments, the reserved resources may be released due to HARQ ACK feedback or preemption and are not counted as used for SL CR evaluation. In one example, resource 704 is a resource released due to HARQ ACK feedback, and resource 706 is a resource released due to preemption. Here, resource 704 and resource 706 are not counted as resources used for SL CR evaluation, and instead, are counted as resources not used for SL CR evaluation.

[0065] Exemplary System Architecture

[0066] In certain embodiments, the 5G system architecture supports data connectivity and services, enabling deployment to use technologies such as network function virtualization and software defined networks. The 5G system architecture can utilize service-based interactions between control plane network functions. Separating user plane functions from control plane functions allows independent scalability, evolution, and flexible deployment (e.g., centralized locations or distributed (remote) locations). Modular function design allows functional reuse, and flexible and effective network slicing can be achieved. Network functions and their network function services can interact with another NF and its network function services directly or indirectly via a service communication agent. Another intermediate function can help route control plane messages. The architecture minimizes the dependency between AN and CN. The architecture may include an aggregated core network with a public AN-CN interface that integrates different access types (e.g., 3GPP access and non-3GPP access). The architecture may also support a unified authentication framework, stateless NFs with decoupling of computing resources from storage resources, capability exposure, concurrent access to local and centralized services (to support low-latency services and access to local data networks, user plane functions may be deployed near the AN), and / or roaming in the visited PLMN with both home-routed traffic as well as local breakout traffic.

[0067] The 5G architecture may be defined as service-based, and the interactions between network functions may include a service-based representation, where a network function (e.g., AMF) within the control plane enables other authorized network functions to access its services. The service-based representation may also include a point-to-point reference point. The reference point representation may also be used to show the interactions between NF services in a network function described by a point-to-point reference point (e.g., N11) between any two network functions (e.g., AMF and SMF).

[0068] Figure 8 A service-based architecture 800 in 5GS according to one embodiment is shown. As described in 3GPP TS23.501, the service-based architecture 800 includes NFs such as NSSF 802, NEF 804, NRF 806, PCF 808, UDM 810, AUSF 812, AMF 814, and SMF 816 for communicating with UE 820, (R) AN 822, UPF 824, and DN 826. NFs and NF services can communicate directly (referred to as direct communication) or indirectly via SCP 818 (referred to as indirect communication). Figure 8 Also shown are corresponding service-based interfaces including Nutm, Naf, Nudm, Npcf, Nsmf, Nnrf, Namf, Nnef, Nnssf and Nausf and reference points N1, N2, N3, N4 and N6. Figure 8 Some exemplary functions provided by the NF shown.

[0069] The NSSF 802 supports functions such as: selecting a set of network slice instances to serve the UE; determining the allowed NSSAIs and, if necessary, determining the mapping to the subscribed S-NSSAI; determining the configured NSSAI and, if necessary, determining the mapping to the subscribed S-NSSAI; and / or determining the set of AMFs to be used to serve the UE, or based on the configuration, possibly determining a list of candidate AMFs by querying the NRF.

[0070] NEF 804 supports the exposure of capabilities and events. NF capabilities and events can be securely exposed by NEF 804 (e.g., for 3rd parties, application functions and / or edge computing). NEF 804 can store / retrieve information as structured data using a standardized interface (Nudr) to UDR. NEF 804 can also securely provide information to the 3GPP network from external applications, and can provide application functions to securely provide information to the 3GPP network (e.g., expected UE behavior, 5GLAN group information, and service-specific information), where NEF 804 can authenticate and authorize and help limit application functions. NEF 804 can provide internal-external information conversion by converting between information exchanged with AF and information exchanged with internal network functions. For example, NEF 804 converts between AF service identifiers and internal 5G core information (such as DNN and S-NSSAI). NEF 804 can handle the masking of network and user sensitive information of external AF according to network policy. NEF 804 may receive information from other network functions (based on the exposed capabilities of other network functions) and store the received information as structured data using a standardized interface to UDR. The stored information may be accessed by NEF 804 and re-exposed to other network functions and application functions, and used for other purposes such as analysis. For external exposure of services related to a specific UE, NEF 804 may reside in the HPLMN. Depending on the operator agreement, the NEF 804 in the HPLMN may have an interface with the NF in the VPLMN. SCEF+NEF may be used for service exposure when the UE is able to switch between EPC and 5GC.

[0071] The NRF 806 supports the service discovery function by receiving NF discovery requests from NF instances or SCPs and providing information of the discovered NF instances to the NF instances or SCPs. The NRF 806 may also support P-CSCF discovery (a special case of SMF discovery of AFs), maintain NF profiles of available NF instances and their supported services, and / or notify subscribed NF service consumers or SCPs of newly registered / updated / deregistered NF instances together with their NF services. In the context of network slicing, multiple NRFs may be deployed at different levels, such as PLMN level (NRF configured with information of the entire PLMN), shared slice level (NRF configured with information belonging to a network slice set), and / or slice-specific level (NRF configured with information belonging to S-NSSAI), based on network specific implementation. In the context of roaming, multiple NRFs may be deployed in different networks, wherein the NRF in the visited PLMN (referred to as vNRF) is configured with information of the visited PLMN, and wherein the NRF in the home PLMN (referred to as hNRF) is configured with information of the home PLMN, referenced by the vNRF via the N27 interface.

[0072] The PCF 808 supports a unified policy framework to govern network behavior. The PCF 808 provides policy rules for control plane functions to implement them. The PCF 808 accesses subscription information related to policy decisions in a unified data repository (UDR). The PCF 808 can access a UDR located in the same PLMN as the PCF.

[0073] The UDM 810 supports the generation of 3GPP AKA authentication credentials, user identification processing (e.g., storage and management of SUPI for each subscriber in the 5G system), unhiding of the privacy-preserving subscription identifier (SUCI), access authorization based on subscription data (e.g., roaming restrictions), UE's serving NF registration management (e.g., storing the service AMF for the UE, storing the PDU session storage service SMF for the UE), service / session continuity (e.g., by maintaining the SMF / DNN allocation for ongoing sessions), MT-SMS delivery, lawful interception functions (especially in outbound roaming situations where the UDM is the only contact point for the LI), subscription management, SMS management, 5GLAN group management processing, and / or external parameter configuration (expected UE behavior parameters or network configuration parameters). To provide such functions, the UDM 810 uses subscription data (including authentication data) that can be stored in the UDR, in which case the UDM implements the application logic and may not require internal user data storage, and several different UDMs can serve the same user in different transactions. The UDM 810 can be located in the HPLMN of the subscriber it serves and can access the information of the UDR located in the same PLMN.

[0074] AF 828 interacts with the core network to provide services such as supporting: application impact on traffic routing; access to NEF 804; interaction with the policy framework for policy control; and / or IMS interaction with 5GC. Based on operator deployment, application functions that are considered to be trusted by the operator may be allowed to interact directly with related network functions. Application functions that the operator does not allow direct access to network functions may interact with related network functions using an external exposure framework via NEF 804.

[0075] AUSF 812 supports authentication for 3GPP access and untrusted non-3GPP access. AUSF 812 may also provide support for network slice-specific authentication and authorization.

[0076] AMF 814 supports termination of RAN CP interface (N2), termination of NAS (N1) for NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (for AMF events and interfaces to LI systems), transmission of SM messages between UE and SMF, transparent proxy for routing SM messages, access authentication, access authorization, transmission of SMS messages between UE and SMSF, SEAF, location service management for regulatory services, transmission of location service messages between UE and LMF and between RAN and LMF, EPS bearer ID allocation for interworking with EPS, UE mobility event notification, control plane CIoT 5GS optimization, user plane CIoT 5GS optimization, configuration of external parameters (expected UE behavior parameters or network configuration parameters) and / or network slice-specific authentication and authorization. Some or all of the AMF functions may be supported in a single instance of AMF 814. Regardless of the number of network functions, in some embodiments, only one NAS interface instance per access network between UE and CN terminates at one of the network functions that implements at least NAS security and mobility management. AMF 814 may also include policy-related functions.

[0077] In addition to the above functions, AMF 814 may also include the following functions to support non-3GPP access networks: support N2 interface with N3IWF / TNGF, on which some information (e.g., 3GPP cell identity) and procedures (e.g., handover related) defined on 3GPP access may not be applicable, and non-3GPP access specific information not applicable to 3GPP access may be applied; support NAS signaling with UE through N3IWF / TNGF, where some procedures supported by NAS signaling through 3GPP access may not be applicable to untrusted non-3GPP (e.g., paging) access; support authentication of UE connected through N3IWF / TNGF; management of mobility, authentication and separate security context states of UE connected via non-3GPP access or via 3GPP access or non-3GPP access at the same time; support coordinated RM management context valid on 3GPP access and non-3GPP access; and / or support dedicated CM management context for UE connected via non-3GPP access. It may not be necessary to support all of the above functions in the instance of network slicing.

[0078] SMF 816 supports session management (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes), UE IP address allocation and management (including optional authorization) (where the UE IP address can be received from the UPF or from an external data network), DHCPv4 (server and client) and DHCPv6 (server and client) functions, functions for responding to address resolution protocol requests and / or IPv6 neighbor solicitation requests based on local cache information of Ethernet PDUs (e.g., SMF responds to ARP and / or IPv6 neighbor solicitation requests by providing a MAC address corresponding to the IP address sent in the request), selection and control of user plane functions (including controlling the UPF to proxy ARP or IPv6 neighbor discovery or forwarding all ARP / IPv6 neighbor solicitation traffic to the SMF for Ethernet PDU sessions), traffic steering configuration at the UPF to route traffic to the appropriate destination, 5G VN group management (e.g., maintaining the topology of the PSA UPFs involved, in the PSA Establish and publish N19 tunnels between UPFs, configure traffic forwarding at UPF to apply local switching and / or N6-based forwarding or N19-based forwarding), terminate interfaces towards policy control functions, lawful interception (for SM events and interfaces to LI systems), charge for data collection and support charging interfaces, control and coordinate charging data collection at UPF, terminate the SM part of NAS messages, downlink data notification, initiator of AN-specific SM information sent to AN via AMF over N2, determination of SSC mode for session, control plane CIoT 5GS optimization, header compression, act as I-SMF in deployments where I-SMF can be inserted / removed / relocated, configure external parameters (expected UE behavior parameters or network configuration parameters), P-CSCF discovery for IMS services, roaming functions (e.g., handling local implementation to apply QoS SLA (VPLMN), charging data collection and charging interface (VPLMN) and / or lawful interception (in VPLMN for SM events and interface to LI system), interaction with external DN to transmit signaling for PDU session authentication / authorization for external DN and / or instructing UPF and NG-RAN to perform redundant transmission on N3 / N9 interface. Some or all of the SMF functions may be supported in a single instance of SMF. However, in some embodiments, not all functions need to be supported in an instance of a network slice. In addition to the functions, SMF 816 may include policy-related functions.

[0079] SCP 818 includes one or more of the following functions: indirect communication; delegated discovery; message forwarding and routing to destination NF / NF service; communication security (e.g., authorization of NF service consumer to access NF service manufacturer API), load balancing, monitoring, overload control, etc.; and / or optionally interacting with UDR to resolve UDM group ID / UDR group ID / AUSF group ID / PCF group ID / CHF group ID / HSS group ID based on UE identity (e.g., SUPI or IMPI / IMPU). Some or all of the SCP functions may be supported in a single instance of SCP. In some embodiments, SCP 818 may be deployed in a distributed manner and / or more than one SCP may be present in the communication path between NF services. SCP may be deployed at PLMN level, shared slice level, and slice-specific level. Operator deployment may be left to ensure that SCP can communicate with relevant NRFs.

[0080] UE 820 may include a device with radio communication capabilities. For example, UE 820 may include a smart phone (e.g., a handheld touch screen mobile computing device that can be connected to one or more cellular networks). UE 820 may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handheld device, or any computing device including a wireless communication interface. UE is also referred to as a client, a mobile phone, a mobile device, a mobile terminal, a user terminal, a mobile unit, a mobile station, a mobile user, a subscriber, a user, a remote station, an access agent, a user agent, a receiver, a radio equipment, a reconfigurable radio equipment, or a reconfigurable mobile device. UE 820 may include an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. IoT UE may utilize technology (e.g., M2M, MTC, or mMTC technology) to exchange data with an MTC server or device via a PLMN, other UEs using ProSe or D2D communication, a sensor network, or an IoT network. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0081] The UE 820 may be configured to be connected or communicatively coupled to the (R)AN 822 via a radio interface 830, which may be a physical communication interface or layer configured to operate with a cellular communication protocol such as a GSM protocol, a CDMA network protocol, a push-to-talk (PTT) protocol, a cellular PTT (POC) protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, etc. For example, the UE 820 and the (R)AN 822 may use a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack including a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and an RRC layer. DL transmissions may be from the (R)AN 822 to the UE 820, and UL transmissions may be from the UE 820 to the (R)AN 822. The UE 820 may also communicate directly with another UE (not shown) using a side link for D2D, P2P, and / or ProSe communication. For example, the ProSe interface may include one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0082] (R)AN 822 may include one or more access nodes, which may be referred to as base stations (BS), node Bs, evolved node Bs (eNBs), next generation node Bs (gNBs), RAN nodes, controllers, transmission reception points (TRPs), etc., and may include ground stations (e.g., terrestrial access points) or satellite stations, which provide coverage within a geographic area (e.g., a cell). (R)AN 822 may include one or more RAN nodes for providing macro cells, pico cells, femto cells, or other types of cells. A macro cell may cover a relatively large geographic area (e.g., several thousand meters in radius) and may allow unrestricted access to a UE with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access to a UE with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to a UE associated with the femto cell (e.g., a UE in a closed subscriber group (CSG) , a UE of a user in a home, etc.).

[0083] Although not shown, multiple RAN nodes (such as (R)AN 822) may be used, with an Xn interface defined between two or more nodes. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE 820 in connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected mode between one or more (R)AN nodes. The mobility support may include context transfer from an old (source) serving (R)AN node to a new (target) serving (R)AN node; and control of a user plane tunnel between an old (source) serving (R)AN node and a new (target) serving (R)AN node.

[0084] The UPF 824 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with the DN 826, and a branch point to support multi-homed PDU sessions. The UPF 824 may also perform packet routing and forwarding, packet inspection, user plane portion of policy rule enforcement, lawful interception of packets (UP collection); traffic usage reporting, QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic validation (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. The UPF 824 may include an uplink classifier for supporting routing of traffic flows to a data network. The DN 826 may represent various network operator services, Internet access, or third-party services. The DN 826 may include, for example, an application server.

[0085] Fig. 9 900 is a block diagram of an example UE 900 that can be configured according to various embodiments of the present disclosure, including by executing instructions corresponding to any exemplary method and / or process described herein on a computer-readable medium. The UE 900 includes one or more processors 902, a transceiver 904, a memory 906, a user interface 908, and a control interface 910.

[0086] The one or more processors 902 may include, for example, an application processor, an audio digital signal processor, a central processing unit, and / or one or more baseband processors. Each of the one or more processors 902 may include an internal memory and / or may include an interface for communicating with an external memory (including memory 906). The internal or external memory may store software code, programs, and / or instructions for execution by the one or more processors 902 to configure and / or facilitate the UE 900 to perform various operations, including the operations described herein. For example, the execution of the instructions may configure the UE 900 to communicate using one or more wired or wireless communication protocols (including one or more wireless communication protocols standardized by 3GPP, such as those commonly referred to as 5G / NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, etc.) or any other current or future protocol that may be used in conjunction with the one or more transceivers 904, the user interface 908, and / or the control interface 910. For another example, the one or more processors 902 may execute program codes stored in the memory 906 or other memory corresponding to the MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP (e.g., for NR and / or LTE). For another example, the processor 902 may execute program codes stored in the memory 906 or other memory, which together with the one or more transceivers 904 implement corresponding PHY layer protocols, such as orthogonal frequency division multiplexing (OFDM), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA).

[0087] The memory 906 may include a memory area for the one or more processors 902 to store variables used in protocols, configurations, controls, and other functions of the UE 900 (including operations corresponding to or including any of the example methods and / or processes described herein). In addition, the memory 906 may include non-volatile memory (e.g., flash memory), volatile memory (e.g., static or dynamic RAM), or a combination thereof. In addition, the memory 906 may interact with a memory slot through which removable memory cards of one or more formats (e.g., SD card, memory stick, compact flash, etc.) may be inserted and removed.

[0088] The one or more transceivers 904 may include radio frequency transmitters and / or receiver circuits that facilitate the UE 900 to communicate with other equipment supporting similar wireless communication standards and / or protocols. For example, the one or more transceivers 904 may include switches, mixer circuits, amplifier circuits, filter circuits, and synthesizer circuits. Such RF circuits may include a receive signal path having a circuit for down-converting an RF signal received from a front-end module (FEM) and providing a baseband signal to a baseband processor of the one or more processors 902. The RF circuit may also include a transmit signal path, which may include a circuit for up-converting a baseband signal provided by a baseband processor and providing an RF output signal for transmission to the FEM. The FEM may include a receive signal path, which may include a circuit configured to operate on an RF signal received from one or more antennas, amplify the receive signal, and provide an amplified version of the receive signal to the RF circuit for further processing. The FEM may also include a transmit signal path, which may include a circuit configured to amplify a transmit signal provided by the RF circuit for transmission by one or more antennas. In various embodiments, amplification through the transmit or receive signal path may be accomplished in the RF circuitry only, in the FEM only, or in both the RF circuitry and the FEM circuitry. In some embodiments, the FEM circuitry may include a TX / RX switch to switch between transmit mode and receive mode operation.

[0089] In some exemplary embodiments, the one or more transceivers 904 include transmitters and receivers that enable the device 1200 to communicate with various 5G / NR networks according to various protocols and / or methods proposed for standardization by 3GPP and / or other standards bodies. For example, such functionality may operate in cooperation with the one or more processors 902 to implement a PHY layer based on OFDM, OFDMA, and / or SC-FDMA techniques, such as described herein with reference to other figures.

[0090] The user interface 908 may take various forms according to a particular embodiment, or may not be present in the UE 900. In some embodiments, the user interface 908 includes a microphone, a speaker, a slidable button, a depressible button, a display, a touch screen display, a mechanical or virtual keypad, a mechanical or virtual keyboard, and / or any other user interface feature that is typically present on a mobile phone. In other embodiments, the UE 900 may include a tablet computing device with a larger touch screen display. In such embodiments, one or more of the mechanical features of the user interface 908 may be replaced by a virtual user interface feature (e.g., a virtual keypad, a virtual button, etc.) that is equivalent or functionally equivalent to that implemented using a touch screen display, as is familiar to those of ordinary skill in the art. In other embodiments, the UE 900 may be a digital computing device, such as a laptop computer, a desktop computer, a workstation, etc., which includes a mechanical keyboard that may be integrated, detachable, or detachable according to a particular exemplary embodiment. Such a digital computing device may also include a touch screen display. Many example embodiments of the UE 900 with a touch screen display are capable of receiving user input, such as input related to the exemplary methods and / or processes described herein or known to those of ordinary skill in the art.

[0091] In some exemplary embodiments of the present disclosure, UE 900 may include an orientation sensor that may be used in various ways by the features and functions of UE 900. For example, UE 900 may use the output of the orientation sensor to determine when a user has changed the physical orientation of the touch screen display of UE 900. The indication signal from the orientation sensor may be used for any application executed on UE 900, so that the application may automatically change the orientation of the screen display (e.g., from portrait to landscape) when the indication signal indicates an approximately 90-degree change in the physical orientation of the device. In this way, the application is able to maintain the screen display in a user-readable manner regardless of the physical orientation of the device. In addition, the output of the orientation sensor may be used in conjunction with various exemplary embodiments of the present disclosure.

[0092] The control interface 910 can take various forms depending on the particular implementation. For example, the control interface 910 can include an RS-232 interface, an RS-485 interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE ("FireWire") interface, an I 2 C interface, PCMCIA interface, etc. In some exemplary embodiments of the present disclosure, the control interface 1260 may include an IEEE 802.3 Ethernet interface, such as described above. In some exemplary embodiments of the present disclosure, the control interface 910 may include an analog interface circuit, which includes, for example, one or more digital-to-analog (D / A) converters and / or analog-to-digital (A / D) converters.

[0093] Those skilled in the art will recognize that the above list of features, interfaces, and radio frequency communication standards is merely exemplary and does not limit the scope of the present disclosure. Fig. 9 The UE 900 may include more functions as shown, including, for example, video and / or still image cameras, microphones, media players and / or recorders, etc. In addition, the one or more transceivers 904 may include circuits for communicating using additional radio frequency communication standards including Bluetooth, GPS and / or others. In addition, the one or more processors 902 may execute software code stored in the memory 906 to control such additional functions. For example, the directional speed and / or position estimate output from the GPS receiver may be used for any application executed on the UE 900, including various exemplary methods and / or computer-readable media according to various exemplary embodiments of the present disclosure.

[0094] Fig.10 is a block diagram of an exemplary network node 1000 that may be configured according to various embodiments of the present disclosure, including by executing instructions on a computer-readable medium corresponding to any of the exemplary methods and / or processes described herein.

[0095] The network node 1000 includes one or more processors 1002, a radio network interface 1004, a memory 1006, a core network interface 1008 and other interfaces 1010. The network node 1000 may include, for example, a base station, an eNB, a gNB, an access node or a component thereof.

[0096] The one or more processors 1002 may include any type of processor or processing circuit, and may be configured to perform one of the methods or processes disclosed herein. The memory 1006 may store software codes, programs and / or instructions executed by the one or more processors 1002 to configure the network node 1000 to perform various operations, including the operations described herein. For example, the execution of such stored instructions may configure the network node 1000 to communicate with one or more other devices using protocols according to various embodiments of the present disclosure (including one or more methods and / or processes described above). In addition, the execution of such stored instructions may also configure and / or facilitate the network node 1000 to communicate with one or more other devices using other protocols or protocol layers (such as one or more of the PHY, MAC, RLC, PDCP and RRC layer protocols standardized by 3GPP for LTE, LTE-A and / or NR or any other higher layer protocol used in combination with the radio network interface 1004 and the core network interface 1008). By way of example and not limitation, the core network interface 1008 includes an S1 interface, and the radio network interface 1004 may include a Uu interface, such as standardized by 3GPP. The memory 1006 may also store variables used in protocols, configuration, control, and other functions of the network node 1000. Thus, the memory 1006 may include non-volatile memory (e.g., flash memory, hard disk, etc.), volatile memory (e.g., static or dynamic RAM), network-based (e.g., "cloud") storage, or a combination thereof.

[0097] The radio network interface 1004 may include a transmitter, a receiver, a signal processor, an ASIC, an antenna, a beamforming unit, and other circuits that enable the network node 1000 to communicate with other equipment (in some embodiments, such as multiple compatible user equipment (UE)). In some embodiments, the network node 1000 may include various protocols or protocol layers, such as PHY, MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and / or 5G / NR. According to other embodiments of the present disclosure, the radio network interface 1004 may include a PHY layer based on OFDM, OFDMA, and / or SC-FDMA technology. In some embodiments, the functions of such a PHY layer may be provided collaboratively by the radio network interface 1004 and the one or more processors 1002.

[0098] The core network interface 1008 may include a transmitter, a receiver, and other circuits that enable the network node 1000 to communicate with other equipment in the core network (in some embodiments, such as circuit switching (CS) and / or packet switching core (PS) network). In some embodiments, the core network interface 1008 may include an S1 interface standardized by 3GPP. In some embodiments, the core network interface 1008 may include one or more interfaces to one or more SGWs, MMEs, SGSNs, GGSNs, and other physical devices, including functions known to those of ordinary skill in the art that exist in GERAN, UTRAN, E-UTRAN, and CDMA2000 core networks. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface. In some embodiments, the lower layer of the core network interface 1008 may include one or more of asynchronous transfer mode (ATM), Internet Protocol (IP) on Ethernet, SDH on optical fiber, T1 / E1 / PDH on copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.

[0099] Other interfaces 1010 may include transmitters, receivers, and other circuits that enable network node 1000 to communicate with external networks, computers, databases, etc., for operation, management, and maintenance of network node 1000 or other network equipment operably connected thereto.

[0100] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following examples section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the examples section below.

[0101] Examples

[0102] The following examples relate to additional embodiments.

[0103] Embodiment 1A may include a method for signaling in a propagation type indication in a wireless communication system, the method comprising: at a first user equipment (UE), receiving a first-level sidelink control information (SCI) format from a second UE; decoding the first-level SCI format; using the decoded first-level SCI format to determine a second-level SCI format; decoding the second-level SCI format; and using the second-level SCI format to determine a sidelink feedback status, wherein the sidelink feedback status indicates whether sidelink feedback is enabled, and wherein the second-level SCI content includes a distance setting associated with a communication range between the first UE and the second UE.

[0104] Embodiment 2A may include the method of embodiment 1A, further comprising: determining that sidelink feedback is enabled, wherein the type of sidelink feedback depends on a distance setting of the second level SCI content.

[0105] Embodiment 3A may include the method of embodiment 2A, wherein the types of sidelink feedback are distance-based NACK feedback and non-distance-based NACK feedback.

[0106] Embodiment 4A may include the method of embodiment 3A, wherein the distance setting is a communication range requirement field, and wherein for non-distance based NACK feedback, the communication range requirement field is set to infinity.

[0107] Embodiment 5A may include the method of embodiment 3A, wherein the distance setting is a communication range requirement field, and wherein for distance-based NACK feedback, the communication range requirement field is set to a non-infinite value.

[0108] Embodiment 6A may include the method of embodiment 1, wherein the second level SCI format is multicast hybrid automatic repeat request (HARQ) feedback option 1, and wherein the method further comprises: determining that only negative acknowledgement (NACK) feedback is available.

[0109] Embodiment 7A may include the method of embodiment 6A, wherein the only NACK feedback is distance-based NACK feedback.

[0110] Embodiment 8A may include the method of embodiment 3A, wherein the only NACK feedback is distance-based NACK feedback and non-distance-based NACK feedback.

[0111] Embodiment 9A may include the method of embodiment 1A, further comprising: determining that sidelink feedback is enabled; and determining a physical sidelink feedback channel (PSFCH) resource determination scheme.

[0112] Embodiment 10A may include the method of embodiment 9A, wherein the PSFCH resource determination scheme is indicated by one bit, and wherein when the PSFCH resource determination scheme is determined by a source identifier (ID), the bit is 0, and when the PSFCH resource determination scheme is determined by a source ID and a group member ID, the bit is 1.

[0113] Embodiment 11A may include the method of embodiment 1A, wherein the feedback status is represented by a bit in a second level SCI format field of the decoded second level SCI format.

[0114] Embodiment 12A may include the method of embodiment 11A, wherein the bit is 0 when feedback is disabled.

[0115] Embodiment 13A may include the method of embodiment 12A, wherein the second level SCI format is broadcast, unicast without feedback, or multicast without feedback.

[0116] Embodiment 14A may include the method of embodiment 11A, wherein the bit is 1 when feedback is enabled.

[0117] Embodiment 15A may include the method of embodiment 14A, wherein the second level SCI format is multicast hybrid automatic repeat request (HARQ) feedback option 2 or unicast with feedback.

[0118] Embodiment 16A may include a non-transitory computer-readable storage medium comprising instructions that, when executed by a processor, cause the processor to: at a first user equipment (UE), receive a first-level sidelink control information (SCI) format from a second UE; decode the first-level SCI format; use the decoded first-level SCI format to determine a second-level SCI format; decode the second-level SCI format; and use the second-level SCI format to determine a sidelink feedback status, wherein the sidelink feedback status indicates whether sidelink feedback is enabled, and wherein the second-level SCI content includes a distance setting associated with a communication range between the first UE and the second UE.

[0119] Embodiment 17A may include the non-transitory computer readable storage medium of embodiment 16A, wherein the instructions further cause the processor to: determine that sidelink feedback is enabled, wherein the type of sidelink feedback depends on a distance setting of the second level SCI content.

[0120] Embodiment 18A may include the non-transitory computer-readable storage medium of embodiment 17A, wherein the types of sidelink feedback are distance-based NACK feedback and non-distance-based NACK feedback.

[0121] Embodiment 19A may include the non-transitory computer-readable storage medium of embodiment 18A, wherein the distance setting is a communication range requirement field, and wherein for non-distance based NACK feedback, the communication range requirement field is set to infinity.

[0122] Embodiment 20A may include the non-transitory computer readable storage medium of embodiment 18A, wherein the distance setting is a communication range requirement field, and wherein for distance-based NACK feedback, the communication range requirement field is set to a non-infinity value.

[0123] Embodiment 21A may include a computing device comprising: a processor; and a memory storing instructions that, when executed by the processor, configure the device to: at a first user equipment (UE), receive a first-level sidelink control information (SCI) format from a second UE; decode the first-level SCI format; use the decoded first-level SCI format to determine a second-level SCI format; decode the second-level SCI format; and use the second-level SCI format to determine a sidelink feedback status, wherein the sidelink feedback status indicates whether sidelink feedback is enabled, and wherein the second-level SCI content includes a distance setting associated with a communication range between the first UE and the second UE.

[0124] Embodiment 22A may include the computing device of embodiment 21A, wherein the instructions further configure the device to: determine that sidelink feedback is enabled, wherein the type of sidelink feedback depends on a distance setting of the second level SCI content.

[0125] Embodiment 23A may include the computing device of embodiment 22A, wherein the types of sidelink feedback are distance-based NACK feedback and non-distance-based NACK feedback.

[0126] Embodiment 24A may include the computing device of embodiment 23A, wherein the distance setting is a communication range requirement field, and wherein for non-distance based NACK feedback, the communication range requirement field is set to infinity.

[0127] Embodiment 25A may include the computing device of embodiment 23A, wherein the distance setting is a communication range requirement field, and wherein for distance-based NACK feedback, the communication range requirement field is set to a non-infinity value.

[0128] Embodiment 1 may include an apparatus comprising means for performing one or more elements of a method described in or related to any other method or process described herein.

[0129] Embodiment 2 may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0130] Embodiment 3 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of the above embodiments or any other method or process described herein.

[0131] Embodiment 4 may include any of the methods, techniques or processes described in or related to the above embodiments, or parts or components thereof.

[0132] Embodiment 5 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or a portion thereof, described in any one of the above embodiments or related thereto.

[0133] Embodiment 6 may include a signal or a portion or component thereof as described in or related to any one of the above embodiments.

[0134] Embodiment 7 may include a datagram, packet, frame, segment, protocol data unit (PDU) or message or a portion or component thereof as described in any of the above embodiments or related thereto, or as otherwise described in the present disclosure.

[0135] Embodiment 8 may include a signal encoded with data or a portion or component thereof as described in any of the above embodiments or related thereto, or described in other ways in this disclosure.

[0136] Embodiment 9 may include a signal or a portion or component thereof encoded with a datagram, packet, frame, segment, PDU or message as described in any of the above embodiments or related thereto, or as otherwise described in the present disclosure.

[0137] Embodiment 10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, of any of or related to the above embodiments.

[0138] Embodiment 11 may include a computer program including instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process or a portion thereof as described in or related to any one of the above embodiments.

[0139] Embodiment 12 may include signals in a wireless network as shown and described herein.

[0140] Embodiment 13 may include a method of communicating in a wireless network as shown and described herein.

[0141] Embodiment 14 may include a system for providing wireless communications as shown and described herein.

[0142] Embodiment 15 may include an apparatus for providing wireless communications as shown and described herein.

[0143] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of the various embodiments.

[0144] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations, or may include a combination of hardware, software, and / or firmware.

[0145] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that unless otherwise stated herein, these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment.

[0146] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention are to be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method performed by a UE, the method comprising: reserving one or more resources for a sidelink channel; identifying one or more preempted resources from the one or more resources for the sidelink; as well as A sidelink channel occupancy over-the-air (SL CR) evaluation is performed, wherein the preempted resources are counted as unused for the SL CR evaluation. 2 . The method of claim 1 , wherein the one or more preempted resources comprise reserved resources preempted by the second UE.

3. The method of claim 1, wherein the one or more resources reserved by the UE are preempted by another UE having higher priority data. The method of claim 1 , wherein the one or more preempted resources are not counted towards the SLCR evaluation.

5. The method of claim 1, wherein the one or more preempted resources comprise a sub-portion of the one or more resources reserved by the UE. The method of claim 1 , further comprising releasing the one or more preempted resources as a result of the preemption.

7. The method of claim 1, wherein the SL CR is evaluated as the total number of subchannels permitted for transmission in time slot [na, n-1] and in time slot [n, n+b] divided by the total number of subchannels configured by [na, n+b] in the transmission pool.

8. A computing device, comprising: processor; and a memory storing instructions that, when executed by the processor, configure the apparatus to: reserving one or more resources for a sidelink channel; identifying one or more preempted resources from the one or more resources for the sidelink; as well as A sidelink channel occupancy over-the-air (SL CR) evaluation is performed, wherein the preempted resources are counted as unused for the SL CR evaluation.

9. The computing device of claim 8, wherein the one or more preempted resources include reserved resources preempted by the second UE.

10. The computing device of claim 8, wherein the one or more resources reserved by the UE are preempted by another UE having higher priority data.

11. The computing device of claim 8, wherein the one or more preempted resources are not counted towards the SL CR evaluation.

12. The computing device of claim 8, wherein the one or more preempted resources comprise a sub-portion of the one or more resources reserved by the UE.

13. The computing device of claim 8, wherein the instructions further configure the device to release the one or more preempted resources as a result of preemption.

14. The computing device of claim 8, wherein the SL CR is evaluated as the total number of subchannels permitted for transmission in time slot [na, n-1] and in time slot [n, n+b] divided by the total number of subchannels configured by [na, n+b] in the transmission pool.

15. A non-transitory computer-readable storage medium comprising instructions which, when executed by a computer, cause the computer to: reserving one or more resources for a sidelink channel; identifying one or more preempted resources from the one or more resources for the sidelink; and A sidelink channel occupancy over-the-air (SL CR) evaluation is performed, wherein the preempted resources are counted as unused for the SL CR evaluation.

16. The computer-readable storage medium of claim 15, wherein the one or more preempted resources comprise reserved resources preempted by a second UE.

17. The computer-readable storage medium of claim 15, wherein the one or more resources reserved by the UE are preempted by another UE having higher priority data.

18. The computer-readable storage medium of claim 15, wherein the one or more preempted resources comprise a sub-portion of the one or more resources reserved by the UE.

19. The computer-readable storage medium of claim 15, wherein the instructions further configure the computer to release the one or more preempted resources as a result of preemption.

20. The computer-readable storage medium of claim 15, wherein the SL CR is evaluated as the total number of subchannels permitted for transmission in time slot [na, n-1] and in time slot [n, n+b] divided by the total number of subchannels configured by [na, n+b] in the transmission pool.

Images