System and method for signaling scheme of cast type indication and resource indication
The two-stage SCI framework in NR V2X optimizes resource allocation and feedback for vehicle-to-everything communications, addressing inefficiencies in existing systems and enhancing data transmission reliability and efficiency.
Patent Information
- Application Number
- JP2024111158
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2020-04-07
- Filing Date
- 2024-07-10
- Publication Date
- 2024-11-06
- Estimated Expiration
- 2041-04-06
AI Technical Summary
Existing wireless communication systems face challenges in efficiently managing resource allocation and feedback mechanisms for vehicle-to-everything (V2X) communications, particularly in New Radio (NR) V2X, which affect the reliability and efficiency of data transmission between user equipment (UE) and base stations.
Implementing a two-stage sidelink control information (SCI) framework in NR V2X, where Stage 1 includes priority bits, resource allocation, and DMRS patterns, and Stage 2 includes detailed content like source ID, destination ID, and HARQ feedback, with specific formats for different cast types to optimize resource reservation and feedback schemes.
Enhances the reliability and efficiency of NR V2X communications by optimizing resource allocation and feedback mechanisms, ensuring effective data transmission and reducing processing overhead for UEs with limited power, thereby improving overall system performance.
Smart Images

Figure 2024156689000001_ABST
Abstract
Description
[Technical field]
[0001] The present application relates generally to wireless communication systems. [Background technology]
[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless mobile devices. Standards and protocols for wireless communication systems can 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, commonly known to industry groups as worldwide interoperability for microwave access (WiMAX), and the IEEE 802.11 standard for wireless local area networks (WLANs), commonly known to industry groups as Wi-Fi. In a 3GPP radio access network (RAN) of an LTE system, a 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 an E-UTRAN Radio Network Controller (RNC), which communicates with wireless communication devices known as user equipment (UE). In a fifth generation (5G) wireless RAN, a RAN node may include a 5G node, an NR node, or a gNode B (gNB).
[0003] The RAN communicates between the RAN nodes and the UEs using a radio access technology (RAT). The RAN may include the global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and / or E-UTRAN, which provide access to communication services via a core network. Each of the RANs operates according to a particular 3GPP RAT. For example, the GERAN implements the GSM and / or EDGE RAT, the UTRAN implements the universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT, and the E-UTRAN implements the LTE RAT.
[0004] To easily identify the discussion of any particular element or act, the most significant digit(s) of a reference number refers to the figure number in which that element is first introduced. [Brief description of the drawings]
[0005] [Figure 1] 1 illustrates a diagram illustrating resource reservation and resource indication in LTE V2X according to certain embodiments. [Diagram 2] 1 illustrates a diagram showing resource reservation and resource indication in NR V2X in accordance with certain embodiments. [Diagram 3] 1 illustrates a procedure for a signaling scheme for cast type indication according to certain embodiments. [Figure 4] 1 illustrates a procedure for a signaling scheme for cast type indication according to certain embodiments. [Diagram 5]1 illustrates a procedure for a signaling scheme for cast type indication according to certain embodiments. [Figure 6] 1 illustrates a procedure for a signaling scheme for resource indication according to a particular embodiment; [Figure 7] 1 illustrates a diagram illustrating Sidelink Channel Occupied Radio (SL CR) assessment in accordance with certain embodiments. [Figure 8] 1 illustrates an exemplary service-based architecture in accordance with certain embodiments. [Figure 9] 1 illustrates a UE according to an embodiment. [Figure 10] 1 illustrates a network node according to one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0006] 2nd stage SCI
[0007] In New Radio (NR) vehicle to everything (V2X), two stage sidelink control information (SCI) is supported. SCI stage 1 is carried on the physical sidelink control channel (PSCCH) and may include the polarity coding employed for the NR downlink control information and applied to the PSCCH. SCI stage 2 is carried on the physical sidelink shared channel (PSCCH) and may include the polarity coding used for the physical downlink control channel (PSCCH) that applies to SCI stage 2.
[0008] The SCI stage 1 content may include one or more of the following: priority bits (e.g., 3 bits), PSSCH frequency and time resource allocation, resource reservation period, demodulation reference signal (DMRS) pattern (e.g., if more than one pattern is configured per resource pool), SCI stage 2 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). One SCI stage 1 format may be provided per resource pool, and the resource size may be fixed.
[0009] The SCI stage 2 content may include a cyclic redundancy check (CRC) (e.g., 24 bits) and additional fields as needed. Table 1 below shows exemplary SCI stage 2 content fields for various SCI stage 2 formats, including, for example, broadcast, unicast without feedback, groupcast without feedback, unicast with feedback, groupcast option 1 with feedback, and groupcast option 2 with feedback. The SCI stage 2 content fields include, for example, a source ID, a destination ID, a hybrid automatic repeat request (HARQ) ID, a new data indicator (NDI), a redundancy version (RV), a channel status information (CSI) request, and a communication range and zone ID. The presence of each field for a particular format, as well as exemplary bits for each content field, are shown in Table 1. For each format, the total bits without CRC and reserved bits are also shown in Table 1. As shown by Table 1, the CSI request may only be provided for the unicast format, and the communication range and zone ID may only be provided for the groupcast option 1 with feedback. For example, the communication range and zone ID relate to the communication range between a transmitting user equipment (UE) and a receiving UE. For example, the communication range is a distance setting associated with the communication range between a receiving UE and a transmitting UE. [Table 1]
[0010] The feedback associated with the SCI stage 2 formats included in Table 1 may include an acknowledgement (ACK) and / or a negative acknowledgement (NACK) to indicate to the transmitting UE whether the receiving UE successfully received the transmission from the transmitting UE. An ACK may be sent if the transmission was successfully received by the receiving UE. A NACK may be sent if the transmission was not successfully received by the receiving UE. For example, in SCI stage 2, unicast with feedback may include both ACK and NACK feedback, groupcast option 1 with feedback may include only NACK, and groupcast option 2 with feedback may include both ACK and NACK.
[0011] Groupcast HARQ Feedback Option 1
[0012] For example, groupcast option 1 with feedback may include only HARQ NACK, where in the transmission from the transmitter UE to the receiver UE, the receiver UE may not feedback if it decodes the PSSCH, and may only feedback NACK if it does not decode the PSSCH. A single physical sidelink feedback channel (PSFCH) resource may be shared by all receiver UEs sending NACK feedback.
[0013] For example, groupcast option 1 with feedback may include distance-based feedback. If the transmitter UE (Tx UE) location is not available, distance-based feedback is not used. If the receiver UE (Rx UE) location 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 location of the indicated zone of the Rx UE and the closest Tx UE to the exact location of the Rx UE itself. For example, the Tx UE may send the zone ID to which the Tx UE belongs to the Rx UE. The Rx UE may not feedback if the distance to the Tx UE is greater than the defined communication range requirement (e.g., the distance is out of range). Additionally, the location of the Tx UE can be conveyed in the SCI Stage 2 for the distance calculation of the Rx UE, the zones can be pre-configured with respect to geographical areas, the zone ID can be associated with the location of the Tx UE, the zone length and zone width can always be the same and can be configurable among, for example, 5, 10, 20, 30, 40, 50 meters. For example, using, for example, 4 bits can explicitly indicate the communication range requirement to the SCI Stage 2, and the distances can 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, spare meters, where the spare indicates future use.
[0014] Resource Indication in LTE V2X
[0015] FIG. 1 shows a diagram 100 illustrating resource reservation and resource indication in LTE V2X for a current transport block (TB) according to a particular embodiment. There may be two transmissions for the current TB, e.g., initial transmission TB 102 and retransmission TB 104. Since the example resource reservation window shown by diagram 100 has 16 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, at most Nmax=2 sidelink resources may be reserved in the SCI for blind retransmissions, and SCI signaling may be enabled to indicate one or two resources. For each resource, the same number of subchannels may be included. Resource reservation may include full flexibility in time and frequency location of resources in the resource reservation window. The time gap between all reserved resources indicated in the SCI may be less than 16 slots in the example of diagram 100.
[0016] The SCI may include a "resource index" field that indicates to the receiving UE whether the current resource is the first resource (e.g., has a forward indication) or the second resource (e.g., has a backward indication). In FIG. 1, for example, since the first resource includes a forward indication 106, the resource index in the SCI of the initial transmission TB 102 may indicate that the current resource is the first resource. The initial transmission TB 102 may reserve a retransmission in the SCI. For example, since the second resource indicates a backward indication 108, the resource index in the SCI of the retransmission TB 104 may indicate that the current resource is the second resource. The retransmission TB 104 may indicate its own resource and also the past resource by the backward indication 108.
[0017] NR V2X Resource Indication
[0018] FIG. 2 illustrates a diagram 200 illustrating resource reservation and resource indication in NR V2X for a current TB according to certain embodiments. There may be three transmissions for the current TB, e.g., initial transmission TB 202, retransmission TB 204, and retransmission TB 206. Since the example resource reservation window illustrated by diagram 200 has 32 slots, there may be up to 32 transmissions for the current TB. Each transmission may have an associated SCI. For example, resource reservation for the current TB may be preconfigured as two sidelink resources or three sidelink resources per resource pool, reserving at most Nmax sidelink resources in the SCI. For example, the SCI signaling may be able to indicate one, two, or three resources. Time resources are indicated, which may reflect (1) a time gap between the first resource and the second resource and (2) a time gap between the first resource and the third resource. A frequency resource is shown, which may reflect (1) a starting subchannel index for the second resource, (2) a starting subchannel index for the third resource, and (3) a number of subchannels per resource. In the example shown by diagram 200, initial transmission TB 202 points to retransmission TB 204 by forward indication 208 and points to retransmission TB 206 by forward indication 210.
[0019] The RAN1 #100e agreement indicated a choice of one of the following options for rearward and forward direction upon next agreement: Option 1, Option 2, or Option 3.
[0020] Option 1: There is no separate field in the first stage SCI indicating the resource index for backward pointing purposes, i.e., backward pointing is not supported. In option 1, the initial transmission TB 202 points to the retransmission TB 204 by a forward indication 208 and points to the retransmission TB 206 by a forward indication 210, the retransmission TB 204 points to the retransmission TB 206 by a forward indication, and the retransmission TB 206 has no forward or backward indication.
[0021] Option 2: If periodic reservation is enabled in the resource pool, a separate field of 1 bit in the first stage SCI indicates the resource index for backward pointing purposes. In option 2, the initial transmission TB 202 points to the retransmission TB 204 by a forward indication 208 and points to the retransmission TB 206 by a forward indication 210, the retransmission TB 204 points to the retransmission TB 206 by a forward indication and points to the initial transmission TB 202 by a backward indication, and the retransmission TB 206 points to the initial transmission TB 202 by a backward indication and has no forward indication.
[0022] Option 3: If periodic reservation is enabled in the resource pool, a separate field of ceil(log2(Nmax)) bits in the first stage SCI indicates the resource index for backward pointing purposes. In option 3, the initial transmission TB 202 points to the retransmission TB 204 by a forward pointing 208 and points to the retransmission TB 206 by a forward pointing 210, the retransmission TB 204 points to the retransmission TB 206 by a forward pointing, and the retransmission TB 206 points to the initial transmission TB 202 by a backward pointing, points to the retransmission TB 204 by a backward pointing, and has no forward pointing.
[0023] In a particular embodiment, the second stage SCI format of the present disclosure is designed to provide a particular indication, for example, a signaling scheme for cast type indication is provided.
[0024] For example, in one embodiment, two second stage SCI formats may be defined. The first format may be used for broadcast, unicast and groupcast without feedback, groupcast option 2, and unicast with feedback. The second format may be used for groupcast option 1. Here, the second stage SCI format field in the first stage SCI may be 2 bits to indicate one of the two second stage SCI formats. The last two code points of this field may be reserved for future use.
[0025] For example, in one embodiment, an additional bit is included in the second stage SCI to indicate whether HARQ feedback is disabled for the first format of the second stage SCI. The first format of the second stage SCI is used for groupcast option 2 and unicast with feedback. The PSFCH resource determination schemes for these two cast types are different. For example, the PSFCH resource for unicast is determined only by the Layer 1 source ID, and the PSFCH resource for groupcast option 2 is determined by both the Layer 1 source ID and the group member ID. Thus, the PSFCH resource determination scheme can be indicated if HARQ feedback is enabled.
[0026] For example, in one embodiment, for the first format of the second stage SCI, an additional bit is included in the second stage SCI to indicate the PSFCH resource determination scheme. The polarity coding used for the PDCCH is applied to the second stage SCI. The CRC length of the second stage SCI is 24 bits, which is the same as the CRC length of the PDCCH. The 24-bit CRC polynomial is designed to support an early termination of polarity decoding function, which may be useful for UEs with limited processing power and power. In the sidelink, the same early termination of polarity decoding is applied in the Rx UE to save processing time and power.
[0027] In some examples, a shorter CRC length of the second stage SCI may be used to reduce overhead. However, the payload size of the second stage SCI may be more 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 be applicable to the second stage SCI.
[0028] Signaling scheme for cast type indication (1-1)
[0029] FIG. 3 illustrates a procedure 300 of a signaling scheme of a cast type indication according to a particular embodiment. It should be noted that as used herein, a stage 1 SCI format may also be referred to as a first stage SCI format (and vice versa), and a stage 2 SCI format may also be referred to as a second stage SCI format (and vice versa). In block 302, at a UE, an SCI stage 1 format is received and decoded. For example, the SCI stage 1 format is received at a first UE from a second UE. For example, the SCI stage 1 format may include a single format. In block 304, from the decoded SCI stage 1 format of block 302, an SCI stage 2 format is determined. For example, the SCI stage 2 format may be format 1, which includes a broadcast format, a unicast format without feedback, a groupcast format without feedback, a groupcast HARQ feedback option 2 format, and a unicast format with feedback. Otherwise, the SCI stage 2 format may be format 2, which is groupcast HARQ feedback option 1. If the SCI Stage 2 format is determined as Format 2, the procedure 300 continues to block 306, described below. If the SCI Stage 2 format is determined as one of the Format 1 formats, the procedure 300 continues to block 308.
[0030] At block 308, the UE decodes the SCI stage 2 format. In certain embodiments, the decoding allows a determination of whether feedback is enabled. For example, in certain embodiments, one bit is used in the SCI stage 2 format field to indicate whether sidelink feedback is enabled or not. For example, for broadcast format, unicast format without feedback, and groupcast format without feedback, this bit is zero. For example, for groupcast HARQ feedback option 2 and unicast format with feedback, this bit is one. At block 310, the decoded SCI stage 2 format of block 308 is used to determine the sidelink feedback status (e.g., whether sidelink feedback is enabled or disabled). If no feedback is enabled (e.g., using a bit in the SCI stage 2 format field to indicate whether sidelink feedback is enabled or not or non-zero), HARQ feedback is not enabled, as shown in block 312. Here, for example, the SCI stage 2 format is broadcast, unicast without feedback, or groupcast without feedback.
[0031] For example, the SCI stage 2 format is groupcast HARQ feedback option 2 or unicast with feedback if feedback is enabled (e.g., using a bit in the SCI stage 2 format field to indicate whether sidelink feedback is enabled or not 1). Thus, the procedure 300 continues to block 314 to determine the PSFCH resource determination scheme. In a particular embodiment, if feedback is enabled, one bit is used to indicate the PSFCH resource determination scheme. For example, if the PSFCH resource determination scheme is determined by a source identifier, this bit is zero. If the PSFCH resource is determined by a source ID and a group member ID, this bit is one. In unicast, the PSFCH resource is determined by a source ID, and therefore the bit is zero. In groupcast HARQ option 2, the PSFCH resource is determined by a source ID and a group member ID, and therefore this bit is one.
[0032] As described above, if the SCI stage 2 format is determined in block 304 as format 2, which is groupcast HARQ feedback option 1, the procedure 300 continues to block 306. In block 306, it is determined that since the format is groupcast HARQ feedback option 1, NACK-only feedback is available. In certain embodiments, only distance-based groupcast option 1 NACK feedback is supported. In certain other embodiments, both distance-based groupcast option 1 NACK feedback and non-distance-based groupcast option 1 NACK feedback are supported. For example, to support non-distance-based groupcast option 1 NACK feedback, the communication range requirement field is set as infinite in the SCI stage 2 content. Thus, regardless of the distance between the Tx UE and the Rx UE, HARQ feedback is always triggered and NACK feedback is sent for PSSCH decoding error. Thus, the actual distance between the Tx UE and the Rx UE becomes irrelevant in non-distance-based groupcast option 1 NACK feedback. For example, the communication range requirement may be (pre)configured to an infinite value and the SCI Stage 2 content may have a code point indicating an infinite communication range requirement. For example, non-distance based Groupcast Option 1 NACK feedback may be enabled or disabled by resource pool (pre)configuration and 4 bits of the range requirement may be configured as infinity.
[0033] For example, in a particular embodiment, support for non-distance-based groupcast HARQ feedback option 1 is based on resource pool (pre-)configuration. If the (pre-)configured communication range requirement includes an infinity value, non-distance-based groupcast HARQ feedback option 1 is applied when the configured communication range requirement includes an infinity value and this value is indicated in the SCI. Here, the sidelink groupcast HARQ feedback options can be differentiated by different second stage SCI formats. In other words, for example, one second stage SCI format can be used for groupcast HARQ feedback option 1 and another second stage SCI format can be used for groupcast HARQ feedback option 2 as well as broadcast and unicast.
[0034] For example, in certain embodiments, different second stage SCI formats may be used for groupcast HARQ feedback option 1 and option 2. Since one second stage SCI format is used for groupcast HARQ feedback option 1, it may not include a separate flag indicating whether HARQ feedback is enabled or disabled. However, for separate second stage SCI formats for broadcast, unicast and groupcast HARQ feedback option 2, a flag may be used to indicate whether HARQ feedback is enabled or disabled. This scheme indicates whether HARQ feedback is enabled or disabled to the receiver UE.
[0035] For example, in certain embodiments, a flag may be used in the second stage SCI formats for broadcast, unicast and groupcast option 2 to indicate whether HARQ feedback is enabled or not.
[0036] Signaling scheme for cast type indication (1-2)
[0037] 4 illustrates a procedure 400 for a signaling scheme of a broadcast type indication according to a particular embodiment. In block 402, a first stage SCI format is received and decoded at a first UE. For example, the first stage SCI format is received at the first UE from a second UE. From the decoded first stage SCI format, a second stage SCI format is determined. For example, the SCI stage 2 format may be format 1, which includes broadcast format, unicast and groupcast formats without feedback, groupcast HARQ feedback option 2 format, unicast format with feedback, and non-distance-based groupcast HARQ option 1 format. Otherwise, the SCI stage 2 format may be format 2, which is distance-based groupcast HARQ feedback option 1.
[0038] In block 404, a feedback option field is determined for the determined second stage SCI format. In a particular embodiment, there is a joint indication of HARQ enable / disable and feedback option using two bits. For example, when there is no HARQ feedback present when the SCI stage 2 format is broadcast, unicast without feedback, or groupcast without feedback, the two bits are "00". For example, when there is HARQ feedback for groupcast option 2, the two bits are "01". Here, there is ACK / NACK feedback with PSFCH resources depending on source ID and group member ID. For example, when there is HARQ feedback for groupcast option 1, the two bits are "10". Here, there is non-distance based NACK with PSFCH resources depending on source ID. For example, when there is unicast HARQ feedback, the two bits are "11". Here, there is AC / NACK feedback with PSFCH resources depending on source ID.
[0039] In block 406, the CSI request field of the second stage SCI format is determined. The CSI request field may be enabled (i.e., set to 1) or disabled (i.e., set to zero). In block 408, an error case is determined. For example, an error case is determined when the CSI request is 1 (enabled) and the joint indication of HARQ enable / disable and feedback option is '01' (i.e., HARQ feedback for groupcast option 2) or '10' (i.e., HARQ feedback for groupcast option 1).
[0040] Signaling scheme for cast type indication (1-3)
[0041] 5 illustrates a procedure 500 for a signaling scheme of a broadcast type indication according to a particular embodiment. In block 502, a first stage SCI format is received and decoded at a first UE. For example, the first stage SCI format is received at the first UE from a second UE. From the decoded first stage SCI format, a second stage SCI format is determined. For example, the SCI stage 2 format may be format 1, which includes broadcast format, unicast and groupcast formats without feedback, groupcast HARQ feedback option 2 format, unicast format with feedback, and non-distance-based groupcast HARQ option 1 format. Otherwise, the SCI stage 2 format may be format 2, which is distance-based groupcast HARQ feedback option 1.
[0042] At block 504, a feedback option field and a CSI request field are determined for the determined second stage SCI format. At block 506, a HARQ feedback scheme and a CSI request indication are determined using the determination of block 504. In a particular embodiment, 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 groupcast without feedback, the three bits are "000". For example, when the format is unicast without feedback with CSI request, the three bits are "001". For example, when the format is unicast without feedback with CSI request, the three bits are "010". For example, when the format is unicast with feedback with CSI request, the three bits are "011". For example, when the format is unicast with feedback without CSI request, the three bits are "100". For example, when the format is non-distance-based groupcast HARQ feedback option 1, the three bits are '101'. For example, when the format is groupcast HARQ feedback option 2, the three bits are '110'. For example, the three bits '111' are reserved but can be used for CSI request details such as CSI report latency combining indication or CSI reference resource indication.
[0043] Signaling scheme for resource indication - Patents.com
[0044] FIG. 6 illustrates a procedure 600 of a signaling scheme for resource indication according to certain embodiments. In certain embodiments, a resource pool (pre)configuration can be performed for the SCI resource index field length. For example, in block 602, a SCI stage 2 (pre)configuration can be determined. In block 604, the SCI stage 2 (pre)configuration can 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 on the PSCCH or PSSCH. In certain embodiments, the resource index field length range can be an enumerate of 0, 1, or 2. For example, a resource index field length of "0" means there is no backward resource indication, and the SCI does not include a resource index field.
[0045] 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 For example, if N = 2, then resource index = 0 indicates a forward resource indication, whereas resource index = 1 indicates a backward resource indication. max For =3, resource index=0 implies forward resource pointing, while resource index=1 implies backward resource pointing on the second resource and forward resource pointing on the third resource.
[0046] In another example, a resource index field length of "2" means that the SCI supports backward resource indication, and the SCI resource index field has 2 bits. max For example, if N = 2, then resource index = 0 indicates forward resource indication and resource index = 1 indicates backward resource indication. maxFor =3, resource index=0 suggests forward resource indication, while resource index=1 suggests backward resource indication on the second resource and forward resource indication on the third resource, and resource index=2 suggests backward resource indication.
[0047] Resource reselection trigger conditions
[0048] In a particular embodiment, there may be a Mode 2 UE resource reselection trigger condition, for example, where the UE selects the resource for retransmission itself upon receiving an initial transmission. In a particular embodiment, for retransmission, the UE may reselect the resource according to a transmission priority. For example, the UE may reselect the resource according to a transmission priority of NR uplink (UL) and NR sidelink (SL), where NR UL transmissions may have a higher priority than NR SL transmissions. In another example, the UE may reselect the resource according to a transmission priority of LTE SL and NE SL, where LTE SL may have a higher priority than NR SL transmissions. In another example, the UE may reselect the resource according to a congestion control, which indicates channel availability for transmission.
[0049] Sidelink CR Evaluation without Preempted Resources
[0050] 7 illustrates a diagram 700 illustrating Sidelink Channel Occupied Radio (SL CR) evaluation according to a particular embodiment. In a particular embodiment, resources released by a UE are not counted in the SL CR evaluation. In a particular embodiment, reserved resources preempted by another UE are also not counted in the SL CR evaluation.
[0051] For example, in FIG. 7, diagram 700 includes a transmission pool 702 that includes resource 704 and resource 706. For slot n of diagram 700, the SL CR is evaluated as the total number of subchannels used for that transmission in slot [na,n-1] and granted in slot [n,n+b] divided by the total number of configured subchannels in transmission pool 702 across [na,n+b]. In certain 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 certain 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 in the SL CR evaluation. Resources that are not counted as used may instead be counted as unused in the SL CR evaluation.
[0052] In a particular embodiment, if a transmission on a resource is dropped due to UL-SL priority or a high channel busy ratio (CBR), the resource is not counted as used in the SL CR evaluation. In a particular embodiment, a reserved resource may be released due to HARQ ACK feedback or preemption and is not counted as used in the SL CR evaluation. In one example, resource 704 is a released resource due to HARQ ACK feedback and resource 706 is a released resource due to preemption. Here, resource 704 and resource 706 are not counted as used resources in the SL CR evaluation, but instead are counted as unused resources in the SL CR evaluation.
[0053] Exemplary System Architecture
[0054] In certain embodiments, the 5G system architecture supports data connectivity and services that are deployable using technologies such as network function virtualization and software defined networks. The 5G system architecture can leverage service-based interactions between control plane network functions. Separating user plane functions from control plane functions allows for independent scalability, evolution, and flexible deployment (e.g., centralized or distributed (remote) deployment). Modularized function design allows for reuse of functions, enabling flexible and efficient network slicing. A network function and its network function services can interact directly or indirectly with another NF and its network function services via a service communication proxy. Another intermediate function can assist in routing of control plane messages. The architecture minimizes dependencies between the AN and the CN. The architecture can include a converged core network with a common AN-CN interface that integrates different access types (e.g., 3GPP access and non-3GPP access). The architecture also supports a unified authentication framework, stateless NFs where computational resources are separated from storage resources, functionality exposure, simultaneous access to local and centralized services (to support low latency services and access to local data networks, user plane functions may be deployed in close proximity to the AN), and / or roaming for both home routed traffic and local breakout traffic within visited PLMNs.
[0055] The 5G architecture may be defined as service-based, and interactions between network functions may include service-based representations, where network functions in the control plane (e.g., AMF) allow other authorized network functions to access their services. The service-based representations may also include point-to-point reference points. The reference point representations may also be used to indicate interactions between NF services in network functions described by a point-to-point reference point (e.g., N11) between any two network functions (e.g., AMF and SMF).
[0056] FIG. 8 illustrates a service-based architecture 800 in 5GS according to one embodiment. As described in 3GPP TS 23.501, the service-based architecture 800 includes NFs such as NSSF 802, NEF 804, NRF 806, PCF 808, UDM 810, AUSF 812, AMF 814, 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. FIG. 8 also illustrates 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. Some exemplary functions provided by the NFs illustrated in FIG. 8 are described below.
[0057] The NSSF802 supports functions such as selecting a set of network slice instances to serve the UE, determining an allowed NSSAI and mapping it to a subscribed S-NSSAI, if necessary, determining a configured NSSAI and mapping it to a subscribed S-NSSAI, if necessary, and / or determining an AMF set to be used to serve the UE or determining a list of candidate AMF(s) based on the configuration, possibly by querying the NRF.
[0058] The NEF 804 supports publishing of functions and events. NF functions and events can be securely published by the NEF 804 (e.g., for third parties, application functions, and / or edge computing). The NEF 804 can store / retrieve information as structured data using a standardized interface (Nudr) to the UDR. The NEF 804 can also protect the provision of information from external applications to the 3GPP network and provide application functions to securely provide information (e.g., expected UE behavior, 5G LAN group information, and service specific information) to the 3GPP network, where the NEF 804 can authenticate, authorize, and assist in the coordination of application functions. The NEF 804 can provide internal-external information translation by translating between information exchanged with the AF and information exchanged with internal network functions. For example, the NEF 804 translates between AF service identifiers and internal 5G core information such as DNN and S-NSSAI. The NEF 804 can handle masking of network and user sensitive information to the external AF according to network policies. The NEF 804 can receive information from other network functions (based on their exposed capabilities) and store the received information in the UDR as structured data using standardized interfaces. The stored information can then be accessed by the NEF 804 and re-exposed to other network and application functions and used for other purposes such as analytics. For external exposure of services related to a particular UE(s), the NEF 804 can be in the HPLMN. Depending on the operator's agreement, the NEF 804 in the HPLMN can have interface(s) with NF(s) in the VPLMN. If the UE is capable of switching between EPC and 5GC, the SCEF+NEF can be used for service exposure.
[0059] The NRF 806 supports service discovery functionality by receiving NF discovery requests from NF instances or SCPs and providing information of discovered NF instances to the NF instances or SCPs. The NRF 806 also supports P-CSCF discovery (a special case of AF discovery by the SMF), maintains NF profiles of available NF instances and their supported services, and / or can notify subscribed NF service consumers or SCPs about newly registered / updated / deregistered NF instances along with their NF services. In the context of network slicing, based on the network implementation, multiple NRFs may be deployed at various levels, such as at the PLMN level (the NRF is configured with information about the entire PLMN), at the shared slice level (the NRF is configured with information belonging to a set of network slices), and / or at a slice-specific level (the NRF is configured with information belonging to an S-NSSAI). In the context of roaming, multiple NRFs may be deployed in different networks, where the NRF(s) in a visited PLMN (known as a vNRF) are configured with information about the visited PLMNs, and the NRF(s) in a home PLMN (known as a hNRF) are configured with information about the home PLMN referenced by the vNRF via the N27 interface.
[0060] The PCF 808 supports a unified policy framework to manage network behavior. The PCF 808 provides policy rules to the control plane function(s) and enforces them. The PCF 808 accesses subscription information relevant to policy decisions in a unified data repository (UDR). The PCF 808 can access a UDR located in the same PLMN as the PCF.
[0061] The UDM 810 supports generation of 3GPP AKA authentication credentials, user identification handling (e.g., storage and management of SUPI per subscriber in 5G systems), deciphering of Privacy Preserving Subscription Identifiers (SUCI), access authorization based on subscription data (e.g., roaming restrictions), serving NF registration management of the UE (e.g., storing the serving AMF of the UE, storing the serving SMF of the UE's PDU sessions), service / session continuity (e.g., by maintaining SMF / DNN assignments for ongoing sessions), MT-SMS delivery, lawful interception functionality (especially in the case of outbound roaming where the UDM is the only point of contact for the LI), subscription management, SMS management, 5G LAN group management handling, and / or external parameter provisioning (expected UE behavior parameters or network configuration parameters). To provide such functionality, the UDM 810 uses subscription data (including authentication data) that may 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 may serve the same user in different transactions. The UDM 810 may be located in the HPLMN of the subscribers it serves and may have access to information of UDRs located in the same PLMN.
[0062] The AF 828 interacts with the core network to provide services supporting, for example, application influence on traffic routing, access to the NEF 804, interaction with a policy framework for policy control, and / or IMS interaction with the 5GC. Based on the operator's deployment, application functions that the operator deems trustworthy may interact directly with the associated network functions. Application functions for which the operator does not have direct access to network functions may interact with the associated network functions using an external exposure framework via the NEF 804.
[0063] The AUSF 812 supports authentication for 3GPP access and untrusted non-3GPP access. The AUSF 812 can also provide network slice-specific authentication and authorization support.
[0064] The AMF 814 supports termination of the RAN CP interface (N2), termination of the NAS (N1) for NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (for AMF events and interface to the LI system), transport of SM messages between the UE and the SMF, transparent proxy for routing SM messages, access authentication, access authorization, transport of SMS messages between the UE and the SMSF, the SEAF, location service management for barring services, transport of location service messages between the UE and the LMF and between the RAN and the LMF, EPS bearer ID allocation for interworking with the EPS, UE mobility event notification, control plane CIoT 5GS optimization, user plane CIoT 5GS optimization, provisioning 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 within a single instance of the AMF 814. Regardless of the number of network functions, in certain embodiments, there is only one NAS interface instance per access network between the UE and the CN, terminating in one of the network functions that implements at least NAS security and mobility management. The AMF 814 may also include policy-related functions.
[0065] In addition to the above-mentioned functions, the AMF 814 may include the following functions to support non-3GPP access networks: support of an N2 interface with the N3IWF / TNGF, where some information (e.g., 3GPP cell identification) and procedures (e.g., handover related) defined on 3GPP access may not apply and non-3GPP access specific information that does not apply to 3GPP access may apply; support of NAS signaling with the UE on the N3IWF / TNGF, where some procedures supported by NAS signaling on 3GPP access may not be applicable to untrusted non-3GPP (e.g., paging) access; support of authentication of UEs connected via the N3IWF / TNGF; management of mobility, authentication, and separate security context state(s) of UEs connected via non-3GPP access or connected simultaneously via 3GPP access and non-3GPP access; support of coordinated RM management context valid on 3GPP access and non-3GPP access; and / or support of a CM management context dedicated to the UE for connection via non-3GPP access. It may not be necessary for all of the above functions to be supported within an instance of a network slice.
[0066] The SMF 816 supports session management (e.g., session establishment, modification, release, including tunnel maintenance between the UPF and AN nodes), UE IP address allocation and management (including optional authorization), where the UE IP address may be received from the UPF or from an external data network, DHCPv4 (server and client) and DHCPv6 (server and client) functions, functions that respond to Address Resolution Protocol requests and / or IPv6 Neighbor Solicitation requests based on local cache information in Ethernet PDUs (e.g., the SMF responds to ARP and / or IPv6 Neighbor Solicitation requests by providing the 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 in the UPF to route traffic to the appropriate destination, 5G VN group management (e.g., maintaining the topology of the associated PSA UPFs, PSA Establishment and release of N19 tunnels between UPFs, configuration of traffic forwarding in the UPF to apply local switching and / or N6 based forwarding or N19 based forwarding), termination of interface to policy control function, Lawful Interception (for SM events and interface to LI system), collection of charging data and support of charging interface, control and coordination of charging data collection in the UPF, termination of SM part of NAS message, downlink data notification, initiation of AN specific SM information sent from N2 to AN via AMF, determination of SSC mode of session, control plane CIoT 5GS optimization, header compression, functioning as I-SMF in deployments where I-SMF can be inserted / removed / relocated, provisioning of external parameters (expected UE behavior parameters or network configuration parameters), P-CSCF discovery of IMS services, roaming functionality (e.g. handling local enforcement and QoSThis includes instructing the UPF and NG-RAN to apply SLAs (VPLMN), charging data collection and charging interface (VPLMN), and / or lawful intercept (at the VPLMN for SM events and interface to the LI system), interacting with external DNs for forwarding signaling for PDU session authentication / authorization by the external DN, and / or performing redundant transmissions on the N3 / N9 interface. Some or all of the SMF functions may be supported within a single instance of the SMF. However, in certain embodiments, it is not necessary that all of the functions be supported within an instance of a network slice. In addition to this function, the SMF 816 may include policy-related functions.
[0067] The SCP 818 includes any one or more of the following functions: indirect communication; delegation discovery; message forwarding and routing to destination NF / NF service; communication security (e.g., authorization for NF service consumers to access NF service producers' APIs), load balancing, monitoring, overload control, etc.; and / or optionally interacting with UDRs to resolve UDM Group ID / UDR Group ID / AUSF Group ID / PCF Group ID / CHF Group ID / HSS Group ID based on UE ID (SUPI or IMPI / IMPU, etc.). Some or all of the SCP functions may be supported within a single instance of an SCP. In certain embodiments, the SCP 818 may be deployed in a distributed manner and / or more than one SCP may be in the communication path between NF services. SCPs may be deployed at the PLMN level, the shared slice level, and the slice-specific level. It may be up to the operator to ensure that the SCP communicates with the associated NRF.
[0068] The UE 820 may include devices having wireless communication capabilities. For example, the UE 820 may include a smartphone (e.g., a handheld touchscreen mobile computing device capable of connecting to one or more cellular networks). The 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 handset, or any computing device that includes a wireless communication interface. A UE may also be referred to as a client, a mobile, 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 equipment. The UE 820 may comprise an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize a technology (e.g., M2M technology, MTC technology, or mMTC technology) for exchanging data with other UEs over the PLMN, an MTC server or device, ProSe or D2D communication, a sensor network, or an IoT network. M2M data exchange or MTC data exchange may be an exchange of machine initiated data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). IoT UEs may run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.
[0069] The UE 820 may be configured to connect or communicatively couple with 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 CDMAP network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, or the like. For example, the UE 820 and the (R)AN 822 may exchange control plane data via a protocol stack including a PHY layer, a MAC layer, a RLC layer, a PDCP layer, and an RRC layer using a Uu interface (e.g., an LTE-Uu interface). 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 further use a sidelink to directly communicate with another UE (not shown) for D2D, P2P, and / or ProSe communications. For example, the ProSe interface comprises 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).
[0070] The (R)AN 822 includes one or more access nodes, which may be referred to as a base station (BS), Node B, evolved Node B (eNB), next generation Node B (gNB), RAN node, controller, transmit / receive point (TRP), etc., and may comprise a ground station (e.g., terrestrial access point) or satellite station that provides coverage within a geographic area (e.g., a cell). The (R)AN 822 may include one or more RAN nodes for providing a macrocell, a picocell, a femtocell, or other type of cell. A macrocell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs with an association with the femtocell (e.g., UEs in a closed subscriber group (CSG), UEs for users in the home, etc.).
[0071] Although not shown, multiple RAN nodes (such as (R)AN 822) may be used, where an Xn interface is defined between two or more nodes. In some 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 mobility support for the UE 820 in connected mode (e.g., CM connected) including management and error handling functions, functions to manage the Xn-C interface, and functions to manage UE mobility in connected mode between one or more (R)AN nodes. 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 user plane tunnels between the old (source) serving (R)AN node and the new (target) serving (R)AN node.
[0072] The UPF 824 can function as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnecting to the DN 826, and a branching point to support multi-homed PDU sessions. The UPF 824 can also perform packet routing and packet forwarding, packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection); traffic usage reporting, perform QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement) for the user plane, perform uplink traffic validation (e.g., SDF to QoS flow mapping), transport level packet marking in the uplink and downlink, and downlink packet buffer and downlink data notification triggers. The UPF 824 can include an uplink classifier to support routing traffic flows to the data network. The DN 826 can represent various network operator services, Internet access, or third party services. The DN 826 may include, for example, an application server.
[0073] 9 is a block diagram of an example UE 900 configurable in accordance with various embodiments of the present disclosure, including instructions executing on a computer-readable medium corresponding to any of the example methods and / or procedures described herein. The UE 900 includes one or more processors 902, a transceiver 904, a memory 906, a user interface 908, and a control interface 910.
[0074] The one or more processors 902 may include, for example, an application processor, a voice 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 an interface(s) for communicating with an external memory (including memory 906). The internal or external memory may store software codes, programs, and / or instructions executed by the one or more processors 902 to configure and / or facilitate the UE 900 to perform various operations, including those described herein. For example, 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 known as 5G / NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, etc., or any other current or future protocols that may be utilized in conjunction with the one or more transceivers 904, user interface 908, and / or control interface 910. As another example, the one or more processors 902 may execute program code stored in other memory 906 corresponding to MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP (e.g., for NR and / or LTE). As a further example, the processor 902, in conjunction with one or more transceivers 904, may execute program code stored in memory 906 or other memory that implements 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).
[0075] The memory 906 may include memory areas for one or more processors 902 to store variables used for protocols, configurations, control, and other functions of the UE 900, including operations corresponding to or having any of the example methods and / or procedures described herein. Additionally, the memory 906 may include non-volatile memory (e.g., flash memory), volatile memory (e.g., static RAM or dynamic RAM), or a combination thereof. Additionally, the memory 906 may interface with a memory slot into which removable memory cards (e.g., SD cards, memory sticks, compact flash, etc.) in one or more formats can be inserted and removed.
[0076] The one or more transceivers 904 may include radio frequency transmitter and / or receiver circuitry that facilitates the UE 900 to communicate with other devices supporting wireless communication standards and / or protocols, etc. For example, the one or more transceivers 904 may include switches, mixer circuits, amplifier circuits, filter circuits, and combiner circuits. Such RF circuitry may include a receive signal path having circuitry for downconverting RF signals received from a front-end module (FEM) and providing baseband signals to a baseband processor of the one or more processors 902. The RF circuitry may also include a transmit signal path, which may include circuitry for upconverting baseband signals provided by the baseband processor and providing an RF output signal to the FEM for transmission. The FEM may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry for further processing. The FEM may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry for transmission by one or more antennas. In various embodiments, amplification through the transmit or receive signal paths may occur in the RF circuitry only, in the FEM circuitry only, or in both the RF and FEM circuits. In some embodiments, the FEM circuitry may include a TX / RX switch to switch between transmit and receive modes of operation.
[0077] 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 in accordance with various protocols and / or methods proposed for standardization by 3GPP and / or other standards bodies. For example, such functionality may operate cooperatively with the one or more processors 902 to implement a PHY layer based on OFDM, OFDMA, and / or SC-FDMA techniques as described herein with respect to other figures.
[0078] The user interface 908 may take various forms or may not be present in the UE 900 depending on the particular embodiment. In some embodiments, the user interface 908 has a microphone, a loudspeaker, 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 features commonly found on a mobile phone. In other embodiments, the UE 900 may include a tablet computing device with a larger touch screen display. In such an embodiment, one or more of the mechanical features of the user interface 908 may be replaced by an equivalent or functionally equivalent virtual user interface feature (e.g., a virtual keypad, virtual buttons, etc.) implemented with a touch screen display, as is well known to those skilled in the art. In other embodiments, the UE 900 may be a digital computing device, such as a laptop computer, desktop computer, workstation, etc., with a mechanical keyboard that may be integrated, separate, or removable depending on the particular exemplary embodiment. Such a digital computing device may also include a touch screen display. Many exemplary embodiments of a UE 900 having a touch screen display can receive user input, such as input related to the exemplary methods and / or procedures described herein or as known to one of ordinary skill in the art.
[0079] In some exemplary embodiments of the present disclosure, the UE 900 may include an orientation sensor that may be used in a variety of ways depending on the features and capabilities of the UE 900. For example, the 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 the UE 900. An indication signal from the orientation sensor may be available to any application program executing on the UE 900 such that the application program may automatically change the orientation of the display screen (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 manner, the application program may maintain the display screen in a manner that is readable by the user regardless of the physical orientation of the device. Additionally, the output of the orientation sensor may be used with various exemplary embodiments of the present disclosure.
[0080] The control interface 910 can take a variety of forms depending on the particular embodiment. For example, the control interface 910 can be 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, a PCMCIA interface, etc. In some exemplary embodiments of the present disclosure, the control interface 1260 may include an IEEE 802.3 Ethernet interface as described above. In some embodiments of the present disclosure, the control interface 910 may include an analog interface circuit including, for example, one or more digital-to-analog (D / A) converters and / or analog-to-digital (A / D) converters.
[0081] Those skilled in the art will appreciate that the above list of features, interfaces, and radio frequency communication standards are merely exemplary and are not intended to limit the scope of the present disclosure. In other words, the UE 900 may include more functionality than that shown in FIG. 9, including, for example, a video and / or still image camera, a microphone, a media player and / or recorder, etc. Additionally, the one or more transceivers 904 may include communication circuitry using additional radio frequency communication standards, including Bluetooth, GPS, and / or others. Additionally, the one or more processors 902 may execute software code stored in the memory 906 to control such additional functionality. For example, the direction speed and / or position estimate output from the GPS receiver may be available to any application program executing on the UE 900, including various exemplary methods and / or computer readable media according to various exemplary embodiments of the present disclosure.
[0082] FIG. 10 is a block diagram of an example network node 1000 configurable in accordance with various embodiments of the disclosure, including instructions executing on a computer-readable medium corresponding to any of the example methods and / or procedures described herein.
[0083] 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 components thereof.
[0084] The one or more processors 1002 may include any type of processor or processing circuitry and may be configured to perform one of the methods or procedures 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 those described herein. For example, execution of such stored instructions may configure the network node 1000 to communicate with one or more other devices using a protocol according to various embodiments of the present disclosure, including one or more of the methods and / or procedures described above. Furthermore, 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 layer protocol, MAC layer protocol, RLC layer protocol, PDCP layer protocol, and RRC layer protocol standardized by 3GPP for LTE, LTE-A, and / or NR, or any other higher layer protocol utilized 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 may include an S1 interface and the radio network interface 1004 may include a Uu interface standardized by 3GPP. The memory 1006 may also store variables, configurations, control, and other functions used in protocols 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.
[0085] The radio network interface 1004 may include transmitters, receivers, signal processors, ASICs, antennas, beam forming units, and other circuitry that enables the network node 1000 to communicate with other devices, such as, in some embodiments, multiple compatible user equipment (UE). In some embodiments, the network node 1000 may include various protocols or protocol layers, such as PHY layer protocols, MAC layer protocols, RLC layer protocols, PDCP layer protocols, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and / or 5G / NR. According to further embodiments of the present disclosure, the radio network interface 1004 may include a PHY layer based on OFDM, OFDMA, and / or SC-FDMA technologies. In some embodiments, the functionality of such a PHY layer may be provided cooperatively by the radio network interface 1004 and one or more processors 1002.
[0086] The core network interface 1008, in some embodiments, may include transmitters, receivers, and other circuitry that enable the network node 1000 to communicate with other devices in a core network, such as a circuit-switched (CS) and / or packet-switched 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 found in GERAN, UTRAN, E-UTRAN, and CDMA2000 core networks known to those skilled in the art. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface. In some embodiments, the lower layers of the core network interface 1008 may include one or more of Asynchronous Transfer Mode (ATM), Internet Protocol (IP) over Ethernet, SDH over fiber optics, T1 / E1 / PDH over copper, microwave radio, or other wired or wireless transmission technologies known to those skilled in the art.
[0087] Other interfaces 1010 may include transmitters, receivers, and other circuitry that enable network node 1000 to communicate with external networks, computers, databases, etc., for purposes of operation, management, and maintenance of network node 1000 or other network equipment operably connected thereto.
[0088] In one or more embodiments, at least one of the components described in one or more of the preceding figures may be configured to perform one or more of the operations, techniques, processes, and / or methods as described in the Examples section below. For example, the baseband circuitry described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below. As another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below in the Examples section.
[0089] Example Section
[0090] The following examples relate to further embodiments.
[0091] Example 1A may include a method for signaling in a cast type indication in a wireless communication system, the method including: receiving, at a first user equipment (UE), a first stage sidelink control information (SCI) format from a second UE; decoding the first stage SCI format; determining a second stage SCI format using the decoded first stage SCI format; decoding the second stage SCI format; and determining a sidelink feedback status using the second stage SCI format, where the sidelink feedback status indicates whether sidelink feedback is enabled or not enabled, and the second stage SCI content includes a distance setting associated with a communication range between the first UE and the second UE.
[0092] Example 2A may include the method of example 1A, further including determining that sidelink feedback is enabled, where the type of sidelink feedback depends on a distance setting of the second stage SCI content.
[0093] Example 3A may include the method of example 2A, in which the types of sidelink feedback are distance-based NACK feedback and non-distance-based NACK feedback.
[0094] Example 4A may include the method of example 3A, in which the distance setting is a communication range requirement field, and the communication range requirement field is set to infinity for non-distance based NACK feedback.
[0095] Example 5A may include the method of example 3A, in which the distance setting is a communication range requirement field, and the communication range requirement field is set to a non-infinite value for distance-based NACK feedback.
[0096] Example 6A may include the method of Example 1, where the second stage SCI format is groupcast hybrid automatic repeat request (HARQ) feedback option 1, and the method further includes determining that negative acknowledgment (NACK)-only feedback is available.
[0097] Example 7A may include the method of example 6A, in which the NACK-only feedback is distance-based NACK feedback.
[0098] Example 8A may include the method according to Example 3A, in which the NACK-only feedback is distance-based NACK feedback and non-distance-based NACK feedback.
[0099] Example 9A may include the method of example 1A, further including determining that sidelink feedback is enabled and determining a physical sidelink feedback channel (PSFCH) resource determination scheme.
[0100] Example 10A may include the method described in Example 9A, in which the PSFCH resource determination scheme is indicated by a bit, and 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.
[0101] Example 11A may include the method of example 1A, in which the feedback status is represented by a bit of a second stage SCI format field of the decoded second stage SCI format.
[0102] Example 12A may include the method of example 11A, in which the bit is 0 when feedback is disabled.
[0103] Example 13A may include the method of example 12A, in which the second stage SCI format is broadcast, unicast without feedback, or groupcast without feedback.
[0104] Example 14A may include the method of example 11A, in which the bit is 1 when feedback is enabled.
[0105] Example 15A may include the method of example 14A, in which the second stage SCI format is groupcast hybrid automatic repeat request (HARQ) feedback option 2 or unicast with feedback.
[0106] Example 16A can include a non-transitory computer-readable storage medium including instructions that, when executed by a processor, cause the processor to receive, at a first user equipment (UE), a first stage sidelink control information (SCI) format from a second UE, decode the first stage SCI format, determine a second stage SCI format using the decoded first stage SCI format, decode the second stage SCI format, and determine a sidelink feedback status using the second stage SCI format, where the sidelink feedback status indicates whether sidelink feedback is enabled or not enabled, and the second stage SCI content includes a distance setting associated with a communication range between the first UE and the second UE.
[0107] Example 17A may include the non-transitory computer-readable storage medium of example 16A, wherein the instructions further cause the processor to determine that sidelink feedback is enabled, and wherein the type of sidelink feedback depends on a distance setting of the second stage SCI content.
[0108] Example 18A may include the non-transitory computer-readable storage medium of Example 17A, wherein the types of sidelink feedback are distance-based NACK feedback and non-distance-based NACK feedback.
[0109] Example 19A may include the non-transitory computer-readable storage medium of example 18A, wherein the distance setting is a communication range requirement field, and the communication range requirement field is set to infinity for non-distance based NACK feedback.
[0110] Example 20A may include the non-transitory computer-readable storage medium of example 18A, wherein the distance setting is a communication range requirement field, and the communication range requirement field is set to a non-infinite value for distance-based NACK feedback.
[0111] Example 21A may include a computing device comprising: a processor; and a memory storing instructions that, when executed by the processor, configure the device to: receive, at a first user equipment (UE), a first stage sidelink control information (SCI) format from a second UE; decode the first stage SCI format; determine a second stage SCI format using the decoded first stage SCI format; decode the second stage SCI format; and determine a sidelink feedback status using the second stage SCI format, wherein the sidelink feedback status indicates whether sidelink feedback is enabled or not, and the second stage SCI content includes a distance setting associated with a communication range between the first UE and the second UE.
[0112] Example 22A may include the computing device of example 21A, wherein the instructions further configure the device to determine that sidelink feedback is enabled, and wherein the type of sidelink feedback depends on a distance setting of the second stage SCI content.
[0113] Example 23A may include the computing device of example 22A, wherein the type of sidelink feedback is distance-based NACK feedback and non-distance-based NACK feedback.
[0114] Example 24A may include the computing device of example 23A, wherein the distance setting is a communication range requirement field, and the communication range requirement field is set to infinity for non-distance based NACK feedback.
[0115] Example 25A may include the computing device of example 23A, wherein the distance setting is a communication range requirement field, and the communication range requirement field is set to a non-infinite value for distance-based NACK feedback.
[0116] Example 1 may include an apparatus including means for performing one or more elements described or related to any other method or process described herein.
[0117] Example 2 may include one or more non-transitory computer-readable media containing 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 examples or any other method or process described herein.
[0118] Example 3 may include a device including logic, modules, or circuitry that performs one or more elements of a method described in or related to any of the above examples or any other method or process described herein.
[0119] Example 4 may include any method, technique, or process described or related to any of the above examples or any portion or part thereof.
[0120] Example 5 may include an apparatus including one or more processors and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any of the above examples or portions thereof.
[0121] Example 6 may include a signal as described or related to any of the above examples or portions or parts thereof.
[0122] Example 7 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described or related to any of the above examples or any portion or part thereof, or as described in the present disclosure.
[0123] Example 8 may include a signal encoded with data as described or related to any of the above examples or portions or parts thereof or as described in this disclosure.
[0124] Example 9 may include a signal encoded with a datagram, packet, frame, segment, PDU, or message as described or related to any of the above examples or any portion or part thereof, or as described in this disclosure.
[0125] Example 10 may include an electromagnetic signal carrying computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any of the above examples or portions thereof.
[0126] Example 11 may include a computer program having instructions that, when executed by a processing element, cause the processing element to perform a method, technique, or process described in or related to any of the above examples or portions thereof.
[0127] Example 12 may include signals in a wireless network as shown and described herein.
[0128] Example 13 may include a method of communicating in a wireless network as shown and described herein.
[0129] Example 14 may include a system for providing wireless communication as shown and described herein.
[0130] Example 15 may include a device for providing wireless communication, as shown and described herein.
[0131] Any of the above-described examples can be combined with any other example (or combination of examples) unless otherwise stated. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
[0132] The embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine-executable instructions executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that contain specific logic for performing the operations, or may include a combination of hardware, software, and / or firmware.
[0133] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially combined into other systems, split into multiple systems, or otherwise split or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be used in another embodiment. It is appreciated that parameters, attributes, aspects, etc. are described in one or more embodiments for clarity only, and that parameters, attributes, aspects, etc. may be combined or substituted with parameters, attributes, etc. of another embodiment, unless specifically disclaimed herein.
[0134] Although the foregoing has been described in some detail for clarity, it will be apparent that certain changes and modifications can be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and the apparatus described herein. Thus, the present embodiments should be considered as illustrative and not restrictive, and the description should not be limited to the details given herein, but may be modified within the scope of the appended claims and their equivalents.
Claims
1. 1. A method for signaling in a cast type indication in a wireless communication system, the method comprising: receiving, at a first user equipment (UE), a first stage sidelink control information (SCI) format from a second UE; decoding the first stage SCI format; determining a second stage SCI format using the decoded first stage SCI format; decoding the second stage SCI format; determining a sidelink feedback status using the second stage SCI format; and Including, the sidelink feedback status indicates whether sidelink feedback is enabled or not enabled, and the second stage SCI content includes a distance setting associated with a communication range between the first UE and the second UE. A method for signaling a cast type indication in a wireless communication system.
2. and determining that the sidelink feedback is enabled, the type of the sidelink feedback depending on the distance setting of the second stage SCI content. The method of claim 1.
3. 3. The method of claim 2, wherein the types of sidelink feedback are distance-based NACK feedback and non-distance-based NACK feedback.
4. The method of claim 3 , wherein the distance setting is a communication range requirement field, and the communication range requirement field is set to infinity for the non-distance based NACK feedback.
5. The method of claim 3 , wherein the distance setting is a communication range requirement field, and the communication range requirement field is set to a non-infinite value for the distance-based NACK feedback.
6. 2. The method of claim 1, wherein the second stage SCI format is a groupcast Hybrid Automatic Repeat Request (HARQ) feedback option 1, the method further comprising determining that negative acknowledgement (NACK)-only feedback is available.
7. The method of claim 6 , wherein the NACK-only feedback is distance-based NACK feedback.
8. The method of claim 3 , wherein the NACK-only feedback is distance-based NACK feedback and non-distance-based NACK feedback.
9. determining that sidelink feedback is enabled; and determining a physical sidelink feedback channel (PSFCH) resource determination scheme; The method of claim 1 further comprising:
10. The PSFCH resource determination scheme is indicated by a bit, When the PSFCH resource determination scheme is determined by a source identifier (ID), the bit is 0; the bit is 1 when the PSFCH resource determination scheme is determined by a source ID and a group member ID; 10. The method of claim 9.
11. 2. The method of claim 1, wherein the feedback status is represented by a bit of a second stage SCI format field of the decoded second stage SCI format.
12. The method of claim 11 , wherein the bit is 0 when feedback is disabled.
13. The method of claim 12 , wherein the second stage SCI format is broadcast, unicast without feedback, or groupcast without feedback.
14. The method of claim 11 , wherein the bit is one when feedback is enabled.
15. 15. The method of claim 14, wherein the second stage SCI format is groupcast Hybrid Automatic Repeat Request (HARQ) feedback option 2 or unicast with feedback.
16. A non-transitory computer-readable storage medium, the computer-readable storage medium, when executed by a processor, causing the processor to: receiving, at a first user equipment (UE), a first stage sidelink control information (SCI) format from a second UE; Decoding the first stage SCI format; determining a second stage SCI format using the decoded first stage SCI format; Decoding the second stage SCI format; determining a sidelink feedback status using the second stage SCI format; and wherein the sidelink feedback status indicates whether sidelink feedback is enabled or not enabled, and the second stage SCI content includes a distance setting associated with a communication range between the first UE and the second UE. A non-transitory computer-readable storage medium.
17. The instructions further cause the processor to: determining that the sidelink feedback is enabled, the type of the sidelink feedback depending on the distance setting of the second stage SCI content.
20. The non-transitory computer-readable storage medium of claim 16.
18. 20. The non-transitory computer-readable storage medium of claim 17, wherein the types of sidelink feedback are distance-based NACK feedback and non-distance-based NACK feedback.
19. 20. The non-transitory computer-readable storage medium of claim 18, wherein the distance setting is a communication range requirement field, and the communication range requirement field is set to infinity for the non-distance based NACK feedback.
20. 20. The non-transitory computer-readable storage medium of claim 18, wherein the distance setting is a communication range requirement field, and the communication range requirement field is set to a non-infinite value for the distance-based NACK feedback.
21. 1. A computing device, comprising: A processor; a memory storing instructions that, when executed by the processor, cause the apparatus to: receiving, at a first user equipment (UE), from a second UE, a first stage sidelink control information (SCI) format; Decoding the first stage SCI format; determining a second stage SCI format using the decoded first stage SCI format; Decoding the second stage SCI format; determining a sidelink feedback status using the second stage SCI format; and a memory configured to: Computing device.
22. The instructions further cause the device to: determining that the sidelink feedback is enabled, the type of the sidelink feedback depending on the distance setting of the second stage SCI content.
22. The computing device of claim 21.
23. 23. The computing device of claim 22, wherein the types of sidelink feedback are distance-based NACK feedback and non-distance-based NACK feedback.
24. 24. The computing device of claim 23, wherein the distance setting is a communication range requirement field, and the communication range requirement field is set to infinity for the non-distance based NACK feedback.
25. 24. The computing device of claim 23, wherein the distance setting is a communication range requirement field, and the communication range requirement field is set to a non-infinite value for the distance-based NACK feedback.
Citation Information
Patent Citations
Improved Radio Resource Selection and Sensing for V2X Transmissions
JP2019525602A
User device and signal transmission method
WO2017179286A1
User terminal and wireless communication method
WO2020031350A1
