System and method for signaling schemes for cast type and resource instructions

Abstract

To provide a method, a system, and a device for signaling in a cast type indication of a wireless communication system.SOLUTION: A method includes, by a first user equipment (UE), receiving a first stage sidelink control information (SCI) format from a second UE to decode 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 SC format. The sidelink feedback status indicates whether sidelink feedback is enabled or not enabled. Second stage SCI content includes a distance setting associated with a communication range between the first UE and the second UE.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] This application generally relates to wireless communication systems.

Background Art

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless mobile devices. Examples of standards and protocols for wireless communication systems 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, generally known to industry groups as Worldwide Interoperability for Microwave Access (WiMAX), and the IEEE 802.11 standard for wireless local area network (WLAN), generally known to industry groups as Wi-Fi. In the 3GPP radio access network (RAN) of an LTE system, the base station can include RAN nodes such as evolved universal terrestrial radio access network (E-UTRAN) Node B (generally also called evolved Node B, enhanced Node B, eNodeB, or eNB) and / or radio network controller (RNC) of E-UTRAN, which communicate with wireless communication devices known as user equipment (UE). In a 5th generation (5G) wireless RAN, the RAN nodes can include 5G nodes, NR nodes, or g-node B (gNB).

[0003] A RAN communicates between RAN nodes and UEs using radio access technology (RAT). Examples of RANs 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, all of which provide access to communication services via the core network. Each RAN operates according to a specific 3GPP RAT. For example, GERAN implements the GSM and / or EDGE RAT, UTRAN implements the Universal Mobile Telecommunication System (UMTS) RAT or other 3GPP RAT, and E-UTRAN implements the LTE RAT.

[0004] To facilitate the identification of any particular element or action, the most significant digit(s) of the reference number refers to the number of the figure in which that element was first introduced. [Brief explanation of the drawing]

[0005] [Figure 1] A diagram illustrating resource reservation and resource instruction in LTE V2X according to a specific embodiment is shown. [Figure 2] A diagram illustrating resource reservation and resource instruction in NR V2X according to a specific embodiment is shown. [Figure 3] The procedure for a cast type indication signaling scheme according to a specific embodiment is shown below. [Figure 4] The procedure for a cast type indication signaling scheme according to a specific embodiment is shown below. [Figure 5]The procedure for a cast type indication signaling scheme according to a specific embodiment is shown below. [Figure 6] The procedure for a resource instruction signaling scheme according to a specific embodiment is shown below. [Figure 7] A diagram illustrating the evaluation of sidelink channel occupancy radio (SLCR) according to a specific embodiment is shown. [Figure 8] This document illustrates an exemplary service-based architecture relating to a specific embodiment. [Figure 9] The UE according to one embodiment is shown. [Figure 10] A network node according to one embodiment is shown. [Modes for carrying out the invention]

[0006] Stage 2 SCI

[0007] The new NR Vehicle to Everything (V2X) supports two stage sidelink control information (SCI). SCI Stage 1 is carried over the Physical Sidelink Control Channel (PSCCH) and can be used in NR downlink control information, and may include polarity codes applied to the PSCCH. SCI Stage 2 is carried over the Physical Sidelink Shared Channel (PSCCH) and may include polarity coding used for the Physical Downlink Control Channel (PSCCH) applied 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 two or more patterns are 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] SCI Stage 2 content can 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. SCI Stage 2 content fields include, for example, source ID, destination ID, hybrid automatic retransmission request (HARQ) ID, new data indicator (NDI), redundant version (RV), channel status information (CSI) request, and communication range and zone ID. The presence of each field in a particular format, as well as exemplary bits for each content field, are shown in Table 1. For each format, the total bits and reserved bits without CRC are also shown in Table 1. As shown in 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 groupcast option 1 with feedback. For example, the communication range and zone ID relate to the communication range between the transmitting user equipment (UE) and the receiving UE. For instance, the communication range is a distance setting associated with the communication range between the receiving UE and the transmitting UE. [Table 1]

[0010] The feedback associated with the SCI Stage 2 formats included in Table 1 may include an acknowledgment (ACK) and / or a negative acknowledgment (NACK) indicating to the sending UE whether the receiving UE has successfully received the transmission from the sending UE. An ACK may be sent if the transmission has been successfully received by the receiving UE. A NACK may be sent if the transmission has not been successfully received by the receiving UE. For example, in SCI Stage 2, a unicast with feedback may include both ACK and NACK feedback, a groupcast option 1 with feedback may include only a NACK, and a 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. Here, in transmission from the transmitter UE to the receiver UE, the receiver UE may not provide feedback if it decodes the PSSCH, or it may only provide NACK feedback if it does not decode the PSSCH. All receiver UEs transmitting NACK feedback can share a single physical sidelink feedback channel (PSFCH) resource.

[0013] For example, groupcast option 1 with feedback may include distance-based feedback. Distance-based feedback is not used if the transmitter UE (Tx UE) location is unavailable. If the receiver UE (Rx UE) location is unavailable, the radio access network 2 (RAN2) may process feedback. For example, the transmitter-receiver (Tx-Rx) distance may be between the center of the indicated zone of the Tx UE closest to the exact location of the Rx UE and the Rx UE itself. For example, the Tx UE may transmit the zone ID to which the Tx UE belongs to the Rx UE. The Rx UE does not have to provide feedback if the distance to the Tx UE is greater than the defined communication range requirement (e.g., the distance is outside the range). Furthermore, the location of the Tx UE can be transmitted in SCI stage 2 for distance calculation of the Rx UE, zones can be pre-configured with respect to geographical area, zone IDs can be associated with the location of the Tx UE, zone length and zone width are always the same and can be configured from, for example, 5, 10, 20, 30, 40, 50 meters. For example, using 4 bits, the communication range requirement can be explicitly indicated in SCI stage 2, and the distance 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, and spare meters. The spare suggests future use.

[0014] Resource instruction 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). There may be two transmissions for the current TB, e.g., an initial transmission TB102 and a retransmission TB104. Since the resource reservation window shown by diagram 100 has 16 slots, at most 16 transmissions of the current TB may exist. Each transmission may have an associated SCI. For example, in the resource reservation of the current TB, for blind retransmission, at most Nmax = 2 sidelink resources can be reserved in the SCI, and SCI signaling can be enabled to indicate one or two resources. For each resource, the same number of subchannels may be included. The resource reservation can include complete flexibility in the time and frequency positions of the resources within 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 can include a "resource index" field that indicates to the receiving UE whether the current resource is the first resource (e.g., having a forward indication) or the second resource (e.g., having 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 TB102 can indicate that the current resource is the first resource. The initial transmission TB102 can 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 TB104 can indicate that the current resource is the second resource. The retransmission TB104 can indicate, by the backward indication 108, the resource of the retransmission TB104 itself and can also indicate past resources.

[0017] Resource Indication in NR V2X

[0018] FIG. 2 shows a diagram 200 showing resource reservation and resource indication in NR V2X for a current TB according to a particular embodiment. In the current TB, there may be three transmissions, for example, an initial transmission TB202, a retransmission TB204, and a retransmission TB206. Since the resource reservation window in the example shown by diagram 200 has 32 slots, at most 32 transmissions of the current TB may exist. Each transmission may have an associated SCI. For example, in the resource reservation of the current TB, at most Nmax sidelink resources are reserved in the SCI and may be preconfigured as two sidelink resources or three sidelink resources per resource pool. For example, SCI signaling may be capable of indicating one, two, or three resources. Time resources are shown, and the time resources can reflect (1) the time gap between the first resource and the second resource and (2) the time gap between the first resource and the third resource. Frequency resources are shown, and the frequency resources can reflect (1) the start subchannel index of the second resource, (2) the start subchannel index of the third resource, and (3) the number of subchannels per resource. In the example shown by diagram 200, the initial transmission TB202 indicates the retransmission TB204 by the forward indication 208 and indicates the retransmission TB206 by the forward indication 210.

[0019] The RAN1 #100e agreement indicated the selection when it next agreed to one of the following options 1, 2, or 3 for backward and forward indications.

[0020] Option 1: The first-stage SCI indicating the resource index for the backward indication has no separate field, that is, the backward indication is not supported. In Option 1, the initial transmission TB202 indicates the retransmission TB204 by the forward indication 208, indicates the retransmission TB206 by the forward indication 210, the retransmission TB204 indicates the retransmission TB206 by the forward indication, and the retransmission TB206 has no forward or backward indication.

[0021] Option 2: If periodic reservation is enabled in the resource pool, a separate 1-bit field in the first stage SCI indicates a resource index intended for backward indication. In Option 2, the initial transmit TB202 points to the retransmit TB204 by the forward indication 208 and to the retransmit TB206 by the forward indication 210, the retransmit TB204 points to the retransmit TB206 by the forward indication and to the initial transmit TB202 by the backward indication, and the retransmit TB206 points to the initial transmit TB202 by the backward indication and has no forward indication.

[0022] Option 3: If periodic reservations are enabled in the resource pool, a separate field of the ceil(log2(Nmax)) bit in the first stage SCI indicates a resource index intended for backward indication. In Option 3, the initial transmit TB202 points to the retransmit TB204 by forward indication 208 and to the retransmit TB206 by forward indication 210, the retransmit TB204 points to the retransmit TB206 by forward indication, the retransmit TB206 points to the initial transmit TB202 by backward indication and to the retransmit TB204 by backward indication, and has no forward indication.

[0023] In certain embodiments, the second-stage SCI format of this disclosure is designed to provide specific instructions. For example, a signaling scheme for cast type instructions is provided.

[0024] For example, in one embodiment, two second-stage SCI formats may be defined. The first format is 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 field of the second-stage SCI format in the first-stage SCI may be 2 bits to indicate one of the two second-stage SCI formats. The last two sign points of this field may be reserved for future use.

[0025] For example, in one embodiment, the second-stage SCI includes an additional bit 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 group cast option 2 and unicast with feedback. The PSFCH resource determination schemes for these two cast types are different. For example, a unicast PSFCH resource is determined by the layer 1 source ID only, while a group cast option 2 PSFCH resource is determined by both the layer 1 source ID and the group member ID. Thus, the PSFCH resource determination scheme may be shown when HARQ feedback is enabled.

[0026] For example, in one embodiment, the second-stage SCI includes additional bits to indicate the PSFCH resource determination scheme for the first format of the second-stage SCI. 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 polynomial of the 24-bit CRC is designed to support an early termination feature of polarity decoding, which may be useful for UEs with limited processing power and power. In sidelinks, the same early termination of polarity decoding is applied in the Rx UE to save processing time and power.

[0027] In some cases, overhead can be reduced by using a shorter CRC length for the second-stage SCI. However, the payload size of the second-stage SCI can be over 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] Cast type indication signaling scheme (1-1)

[0029] Figure 3 shows procedure 300 of a signaling scheme for cast type indication according to a particular embodiment. Note that, as used herein, the Stage 1 SCI format may also be called the First Stage SCI format (and vice versa), and the Stage 2 SCI format may also be called the Second Stage SCI format (and vice versa). In block 302, the UE receives and decodes the SCI Stage 1 format. For example, the SCI Stage 1 format is received by the First UE from the Second UE. For example, the SCI Stage 1 format may include a single format. In block 304, the SCI Stage 2 format is determined from the decoded SCI Stage 1 format of block 302. 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 to be Format 2, step 300 proceeds to block 306, which is described below. If the SCI Stage 2 format is determined to be one of the Format 1 formats, step 300 proceeds to block 308.

[0030] In block 308, the UE decodes the SCI Stage 2 format. In certain embodiments, decoding allows for the determination of whether feedback is enabled. For example, in certain embodiments, a bit is used in the SCI Stage 2 format field to indicate whether sidelink feedback is enabled. For example, in the broadcast format, the unicast format without feedback, and the groupcast format without feedback, this bit is zero. For example, in the groupcast HARQ feedback option 2 and the unicast format with feedback, this bit is 1. In block 310, the sidelink feedback status (e.g., whether sidelink feedback is enabled or disabled) is determined using the decoded SCI Stage 2 format from block 308. If there is no enabled feedback (e.g., a bit is used in the SCI Stage 2 format field to indicate whether sidelink feedback is enabled or not), then 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] If feedback is enabled (for example, using a bit in the SCI Stage 2 format field to indicate whether sidelink feedback is enabled or not), for example, the SCI Stage 2 format is a groupcast HARQ feedback option 2 or a unicast with feedback. Thus, procedure 300 proceeds to block 314 to determine the PSFCH resource determination scheme. In certain embodiments, if feedback is enabled, a bit is used to indicate the PSFCH resource determination scheme. For example, if the PSFCH resource determination scheme is determined by the source identifier, this bit is zero. If the PSFCH resource is determined by the source ID and group member ID, this bit is 1. In a unicast, the PSFCH resource is determined by the source ID, and therefore the bit is zero. In a groupcast HARQ option 2, the PSFCH resource is determined by the source ID and group member ID, and therefore this bit is 1.

[0032] As described above, if in block 304 the SCI stage 2 format is determined to be format 2, which is groupcast HARQ feedback option 1, then step 300 proceeds to block 306. In block 306, since the format is groupcast HARQ feedback option 1, it is determined that only NACK 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 to infinite in the SCI stage 2 content. Thus, regardless of the distance between the Tx UE and Rx UE, HARQ feedback is always triggered and NACK feedback is sent for PSSCH decoding errors. Thus, the actual distance between the Tx UE and Rx UE is irrelevant for non-distance-based groupcast option 1 NACK feedback. For example, the communication range requirement can be (pre)configured to an infinite value, and the SCI Stage 2 content may have a sign point indicating an infinite communication range requirement. For example, the non-distance-based group cast option 1NACK feedback may be enabled or disabled by the resource pool (pre)configuration, and the 4 bits of the range requirement may be configured as infinite.

[0033] For example, in certain embodiments, support for non-distance-based groupcast HARQ feedback option 1 is based on a resource pool (pre)configuration. If the (pre)configured communication range requirement includes an infinite value, then non-distance-based groupcast HARQ feedback option 1 is applied when the configured communication range requirement includes an infinite value and this value is indicated in the SCI. Here, sidelink groupcast HARQ feedback options can be distinguished 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 for broadcast and unicast.

[0034] For example, in certain embodiments, different second-stage SCI formats can be used for groupcast HARQ feedback options 1 and 2. Since one second-stage SCI format is used for groupcast HARQ feedback option 1, it may not be necessary to include a separate flag indicating whether HARQ feedback is enabled or disabled. However, for the other second-stage SCI formats for broadcast, unicast, and groupcast HARQ feedback option 2, a flag indicating whether HARQ feedback is enabled or disabled can be used. This scheme indicates whether HARQ feedback is enabled or disabled for the receiver UE.

[0035] For example, in certain embodiments, a flag indicating whether HARQ feedback is enabled can be used in the second-stage SCI format of broadcast, unicast, and groupcast option 2.

[0036] Cast type indication signaling scheme (1-2)

[0037] Figure 4 shows a step 400 of a signaling scheme for cast type indication according to a particular embodiment. In block 402, the first UE receives and decodes the first stage SCI format. For example, the first stage SCI format is received by the first UE from the second UE. The second stage SCI format is determined from the decoded first stage SCI format. For example, the SCI stage 2 format may be format 1, which includes broadcast formats, unicast and groupcast formats without feedback, groupcast HARQ feedback option 2 formats, unicast formats with feedback, and non-distance-based groupcast HARQ option 1 formats. Otherwise, the SCI stage 2 format may be format 2, which is distance-based groupcast HARQ feedback option 1.

[0038] In block 404, the feedback option field is determined for the determined second-stage SCI format. In certain embodiments, there is a joint indication for enabling / disabling HARQ and feedback options, 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 dependent 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 dependent on source ID. For example, when there is HARQ feedback for unicast, the two bits are "11". Here, there is AC / NACK feedback with PSFCH resources dependent 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, error cases are determined. For example, an error case is determined when the CSI request is 1 (enabled) and the HARQ enable / disable and feedback option joint instruction is "01" (i.e., HARQ feedback for group cast option 2) or "10" (i.e., HARQ feedback for group cast option 1).

[0040] Cast type indication signaling scheme (1-3)

[0041] Figure 5 shows a step 500 of a signaling scheme for cast type indication according to a particular embodiment. In block 502, the first UE receives and decodes the first stage SCI format. For example, the first stage SCI format is received by the first UE from the second UE. The second stage SCI format is determined from the decoded first stage SCI format. For example, the SCI stage 2 format may be format 1, which includes broadcast formats, unicast and groupcast formats without feedback, groupcast HARQ feedback option 2 formats, unicast formats with feedback, and non-distance-based groupcast HARQ option 1 formats. Otherwise, the SCI stage 2 format may be format 2, which is distance-based groupcast HARQ feedback option 1.

[0042] In block 504, the feedback option field and the CSI request field are determined for the determined second-stage SCI format. In block 506, the HARQ feedback scheme and CSI request instruction are determined using the determination in block 504. In certain embodiments, there are three bits used for the HARQ enable / disable, feedback option, and CSI request joint instruction. For example, when the format is a broadcast or a group cast without feedback, the three bits are "000". For example, when the format is a unicast without feedback with a CSI request, the three bits are "001". For example, when the format is a unicast without feedback with a CSI request, the three bits are "010". For example, when the format is a unicast with feedback with a CSI request, the three bits are "011". For example, when the format is a unicast with feedback but without a 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 details of a CSI request, such as a CSI report latency join instruction or a CSI reference resource instruction.

[0043] Signaling scheme for resource allocation

[0044] Figure 6 shows procedure 600 of a resource instruction signaling scheme according to a particular embodiment. In a particular embodiment, a resource pool (pre)configuration can be performed on the SCI resource index field length. For example, in block 602, the (pre)configuration of SCI stage 2 can be determined. In block 604, the (pre)configuration of SCI stage 2 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 PSCCH or PSSCH. In a particular embodiment, the resource index field length range may be an enumerate of 0, 1, or 2. For example, a resource index field length of "0" means there is no backward resource instruction, and the SCI does not contain a resource index field.

[0045] For example, a resource index field length of "1" means that the SCI supports backward resource instruction and that the SCI resource index field has 1 bit. Here, for example, N max When =2, resource index=0 suggests a forward resource instruction, while resource index=1 suggests a backward resource instruction. Furthermore, for example, N max When =3, resource index=0 suggests a forward resource instruction, while resource index=1 suggests a backward resource instruction on the second resource and a forward resource instruction on the third resource.

[0046] In another example, a resource index field length of "2" means that the SCI supports backward resource instruction, and that the SCI resource index field has 2 bits. Here, for example, N max When = 2, resource index = 0 suggests a forward resource instruction, and resource index = 1 suggests a backward resource instruction. For example, N maxWhen =3, resource index=0 suggests a forward resource instruction, resource index=1 suggests a backward resource instruction on the second resource and a forward resource instruction on the third resource, and resource index=2 suggests a backward resource instruction.

[0047] Resource re-selection trigger conditions

[0048] In certain embodiments, for example, there may be a Mode 2UE resource reselection trigger condition in which the UE selects the resource itself for retransmission when it receives an initial transmission. In certain embodiments, for retransmission, the UE may reselect a resource according to transmission priority. For example, the UE may reselect a resource according to the 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 a resource according to the transmission priority of LTE SL and NE SL, where LTE SL may have a higher priority than NR SL transmissions. In yet another example, the UE may reselect a resource according to congestion control indicating channel availability for transmission.

[0049] Preempted resource-free sidelink CR evaluation

[0050] Figure 7 shows a diagram 700 illustrating a sidelink channel occupancy radio (SL CR) evaluation according to a particular embodiment. In this particular embodiment, resources are released by the UE and are not counted in the SL CR evaluation. In this particular embodiment, reserved resources preempted by another UE are also not counted in the SL CR evaluation.

[0051] For example, in Figure 7, diagram 700 includes a transmit pool 702 containing resources 704 and 706. In slot n of diagram 700, the SL CR is evaluated as the total number of subchannels used for its transmit in slot [na, n-1] and allowed in slot [n, n+b], which is obtained by dividing this by the total number of configured subchannels in the transmit pool 702 over [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 not counted as used can instead be counted as unused in the SL CR evaluation.

[0052] In certain embodiments, 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 certain embodiments, reserved resources may be released due to HARQ ACK feedback or preemption and are not counted as used in the SL CR evaluation. For example, resource 704 is a released resource due to HARQ ACK feedback, and resource 706 is a released resource due to preemption. Here, resources 704 and 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 can be deployed using technologies such as network function virtualization and software-defined networking. The 5G system architecture can leverage service-based bidirectional interaction between control plane network functions. Separating user plane functions from control plane functions enables independent scalability, evolution, and flexible deployment (e.g., centralized or distributed (remote) deployment). Modular functional design enables function reuse and flexible and efficient network slicing. Network functions and their network function services can interact directly or indirectly bidirectionally with other NFs and their network function services via service communication proxies. Another intermediate function can assist in routing control plane messages. The architecture minimizes dependencies between ANs and CNs. 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, a stateless NF where computing resources are separated from storage resources, feature exposure, simultaneous access to local and centralized services (user plane functions may be deployed close to the AN to support low-latency services and access to the local data network), and / or roaming for both home routing traffic and local breakout traffic within visited PLMNs.

[0055] A 5G architecture can be defined as service-based, and bidirectional interaction between network functions can include a service-based representation, where a network function in the control plane (e.g., AMF) enables other authorized network functions to access those services. A service-based representation can also include a point-to-point reference point. A reference point representation can also be used to show bidirectional interaction 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).

[0056] Figure 8 shows 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 NSSF802, NEF804, NRF806, PCF808, UDM810, AUSF812, AMF814, and SMF816 for communicating with UE820, (R)AN822, UPF824, and DN826. NFs and NF services can communicate directly, which is called direct communication, or indirectly via SCP818, which is called indirect communication. Figure 8 also shows the corresponding service-based interfaces, including Nutm, Naf, Nudm, Npcf, Nsmf, Nnrf, Namf, Nnef, Nnssf, and Nausf, as well as reference points N1, N2, N3, N4, and N6. Some exemplary functions provided by the NFs shown in Figure 8 are described below.

[0057] NSSF802 supports functions such as selecting a set of network slice instances to serve the UE, determining authorized NSSAIs and mapping them to subscribed S-NSSAIs as needed, determining configured NSSAIs and mapping them to subscribed S-NSSAIs as needed, and / or determining a list of candidate AMFs (one or more) to use to serve the UE, or, based on the configuration, querying the NRF as needed.

[0058] NEF804 supports the exposure of functions and events. NF functions and events can be securely exposed by NEF804 (e.g., for third parties, application functions, and / or edge computing). NEF804 can store / retrieve information as structured data using a standardized interface to UDR (Nudr). NEF804 can also protect the provision of information from external applications to the 3GPP network and provide application functions for securely providing information to the 3GPP network (e.g., expected UE behavior, 5GLAN group information, and service-specific information), where NEF804 can authenticate, authorize, and assist in the coordination of application functions. NEF804 can provide internal-external information conversion by converting between information exchanged with AF and information exchanged with internal network functions. For example, NEF804 converts between AF service identifiers and internal 5G core information such as DNN and S-NSSAI. NEF804 can handle the masking of network and user sensitive information to external AF according to network policies. The NEF804 can receive information from other network functions (based on the exposed functions of those other network functions) and store the received information as structured data in the UDR using a standardized interface. The stored information can then be accessed by the NEF804, republished to other network and application functions, and used for other purposes such as analysis. For the external exposure of services related to a specific UE(s), the NEF804 may reside within the HPLMN. With the operator's consent, the NEF804 within the HPLMN may have interfaces with NF(s) within the VPLMN. If the UE can switch between EPC and 5GC, SCEF+NEF can be used for service exposure.

[0059] NRF806 supports service discovery by receiving NF discovery requests from NF instances or SCPs and providing information on discovered NF instances to the NF instances or SCPs. NRF806 also supports P-CSCF discovery (a special case of AF discovery by SMF), maintains NF profiles of available NF instances and their supported services, and / or can notify subscribed NF service consumers or SCPs of newly registered / updated / deregistered NF instances along with their NF services. In the context of network slicing, depending on the network implementation, multiple NRFs may be deployed at various levels, such as the PLMN level (NRFs consist of information about the entire PLMN), the shared slice level (NRFs consist of information belonging to a set of network slices), and / or the slice-specific level (NRFs consist of information belonging to S-NSSAI). In the context of roaming, multiple NRFs can be deployed in different networks, where the NRF(s) within a visited PLMN (known as vNRF) consist of information about the visited PLMN, and the NRF(s) within a home PLMN (known as hNRF) consist of information about the home PLMN referenced by the vNRF via the N27 interface.

[0060] PCF808 supports a unified policy framework to manage network behavior. PCF808 provides and enforces policy rules for control plane functions (one or more). PCF808 accesses subscription information related to policy decisions in the Unified Data Repository (UDR). PCF808 can access UDRs located within the same PLMN as PCF.

[0061] The UDM810 supports the generation of 3GPP AKA authentication credentials, user identification processing (e.g., storage and management of SUPI per subscriber in 5G systems), decryption of privacy-protected subscriber identifiers (SUCI), access authorization based on subscriber data (e.g., roaming restrictions), UE serving NF registration management (e.g., storing the UE's serving AMF, storing the UE's serving SMF for PDU sessions), service / session continuity (e.g., by maintaining SMF / DNN allocation for ongoing sessions), MT-SMS delivery, lawful interception functionality (especially in the case of outbound roaming where the UDM is the sole contact point to the LI), subscriber management, SMS management, 5GLAN group management processing, and / or external parameter provisioning (expected UE behavior parameters or network configuration parameters). To provide such functionality, the UDM810 uses subscriber data (including authentication data) that can be stored in the UDR, in which case the UDM does not need to implement application logic and internal user data storage, and several different UDMs can serve the same user in different transactions. The UDM810 may be located within the HPLMN of the subscriber it serves, and may access information from the UDR located within the same PLMN.

[0062] AF828 interacts bidirectionally with the core network to provide services such as application influence on traffic routing, access to NEF804, bidirectional interaction with the policy framework for policy control, and / or bidirectional IMS interaction with 5GC. Based on the operator's deployment, application functions that the operator considers to be trusted can interact directly bidirectionally with the relevant network functions. Application functions that the operator cannot directly access the network functions can interact bidirectionally with the relevant network functions using an externally exposed framework via NEF804.

[0063] AUSF812 supports authentication for 3GPP access and untrusted non-3GPP access. AUSF812 can also provide network slice-specific authentication and authorization support.

[0064] The AMF814 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 LI systems), transport of SM messages between the UE and SMF, transparent proxy for routing SM messages, access authentication, access authorization, transport of SMS messages between the UE and SMSF and SEAF, location service management for regulatory services, transport of location service messages between the UE and LMF and between the RAN and LMF, EPS bearer ID assignment for interworking with 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 AMF814. Regardless of the number of network functions, in certain embodiments, there is only one NAS interface instance per access network between the UE and CN, terminating at least one of the network functions that implement NAS security and mobility management. The AMF814 may also include policy-related functions.

[0065] In addition to the above-mentioned functions, the AMF814 may include the following functions to support non-3GPP access networks: support for an N2 interface with N3IWF / TNGF, where some information (e.g., 3GPP cell identification) 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 applicable; support for NAS signaling using UEs on 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 for authentication of UEs connected via N3IWF / TNGF; management of mobility, authentication, and separate security context states (one or more) of UEs connected via non-3GPP access, or simultaneously connected via 3GPP access and non-3GPP access; support for a coordinated RM management context valid on 3GPP access and non-3GPP access; and / or support for a CM management context dedicated to UEs for connections via non-3GPP access. It may not always be necessary to support all of the above features within a network slice instance.

[0066] The SMF816 supports session management (e.g., establishing, modifying, and releasing sessions, including maintaining tunnels between UPF and AN nodes), UE IP address allocation and management (including optional approval), where the UE's IP address may be received from the UPF or from external data networks, DHCPv4 (server and client) and DHCPv6 (server and client) functions, address resolution protocol requests and / or functions responding to IPv6 Neighbor Solicitation requests based on local cache information of 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 at the time of 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 for routing traffic to appropriate destinations, and 5G VN group management (e.g., maintaining the topology of the associated PSA UPF, PSA Establishing and releasing N19 tunnels between UPFs, configuring traffic forwarding in UPFs with local switching applied, and / or N6-based or N19-based forwarding), terminating interfaces to policy control functions, lawful interception (for SM events and interfaces to LI systems), collecting billing data and supporting billing interfaces, controlling and coordinating billing data collection in UPFs, terminating the SM portion of NAS messages, downlink data notification, initiating AN-specific SM information sent from N2 to AN via AMF, determining the SSC mode of a session, optimizing the control plane CIoT 5GS, header compression, deployments that can insert / delete / reposition I-SMFs, functioning as an I-SMF, provisioning external parameters (expected UE behavior parameters or network configuration parameters), P-CSCF discovery for IMS services, roaming functions (e.g., handling local enforcement and QoS)This includes applying SLAs (VPLMN), billing data collection and billing interfaces (VPLMN), and / or lawful interception (in VPLMN for SM events and interfaces to LI systems), bidirectional interaction with external DNs for forwarding signaling for PDU session authentication / authorization by external DNs, and / or instructing UPF and NG-RAN to perform redundant transmission on N3 / N9 interfaces. Some or all of the SMF functions may be supported within a single instance of SMF. However, in certain embodiments, it is not necessary for all functions to be supported within an instance of a network slice. In addition to these functions, SMF816 may include policy-related functions.

[0067] SCP818 includes any one or more of the following functions: indirect communication; delegated discovery; message forwarding and routing to destination NF / NF services; communication security (e.g., authorization for NF service consumers to access NF service producer APIs), load balancing, monitoring, overload control, etc.; and / or optionally bidirectional interaction with UDRs to resolve UDM group IDs / UDR group IDs / AUSF group IDs / PCF group IDs / CHF group IDs / HSS group IDs based on UE IDs (such as SUPI or IMPI / IMPU). Some or all of the SCP functions may be supported within a single instance of SCP. In certain embodiments, SCP818 may be deployed in a distributed manner, and / or more than one SCP may exist in the communication path between NF services. SCPs may be deployed at the PLMN level, shared slice level, and slice-specific level. It may be left to the operator's placement to ensure that SCPs can reliably communicate with the relevant NRF.

[0068] The UE820 may include devices with wireless communication capabilities. For example, the UE820 may include a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks). The UE820 may also include any mobile or non-mobile computing device, or any computing device that includes a wireless communication interface, such as a personal data assistant (PDA), pager, laptop computer, desktop computer, or wireless handset. The UE may also be referred to as a client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, wireless equipment, reconfigurable wireless equipment, or reconfigurable mobile device. The UE820 may include 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 technologies for exchanging data with other UEs via the PLMN, such as MTC servers or devices, ProSe or D2D communication, sensor networks, or IoT networks (e.g., M2M technology, MTC technology, or mMTC technology). M2M data exchange or MTC data exchange may be the exchange of machine startup data. An IoT network describes interconnected 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 within the IoT network.

[0069] UE820 may be configured to connect to or communicate with (R)AN822 via a radio interface 830, which may be a physical communication interface or layer configured to operate on cellular communication protocols such as GSM protocol, CDMAP network protocol, PTT (Push-to-Talk) protocol, POC (PTT over Cellular) protocol, UMTS protocol, 3GPP LTE protocol, 5G protocol, and NR protocol. For example, UE820 and (R)AN822 can exchange control plane data via a protocol stack including the PHY layer, MAC layer, RLC layer, PDCP layer, and RRC layer using a Uu interface (e.g., LTE-Uu interface). DL transmission may be from (R)AN822 to UE820, and UL transmission may be from UE820 to (R)AN822. UE820 may further communicate directly with another UE (not shown) for D2D, P2P, and / or ProSe communication using a sidelink. 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 sharing channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0070] (R)AN822 includes one or more access nodes, which may be referred to as base stations (BS), node B, evolved node B (eNB), next-generation node B (gNB), RAN nodes, controllers, transmit / receive points (TRP), etc., and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographical area (e.g., a cell). (R)AN822 may include one or more RAN nodes to provide macrocells, picocells, femtocells, or other types of cells. Macrocells can cover relatively large geographical areas (e.g., a radius of several kilometers) and may enable unrestricted access by UEs with service subscriptions. Picocells can cover relatively small geographical areas and may enable unrestricted access by UEs with service subscriptions. Femtocells can cover relatively small geographical areas (e.g., a home) and may enable restricted access by UEs associated with the femtocell (e.g., UEs within a closed subscriber group (CSG), UEs for users in a home, etc.).

[0071] Although not shown in the diagram, multiple RAN nodes (such as (R)AN822) may be used, where the 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 provides unguaranteed delivery of user plane PDUs and can support / provide data transmission and flow control functions. The Xn-C can provide mobility support for the UE820 in connection modes (e.g., CM connection), including management and error handling functions, functions to manage the Xn-C interface, and functions to manage UE mobility in connection modes between one or more (R)AN nodes. Mobility support may include context transfer from the old (source) serving (R)AN node to the new (target) serving (R)AN node, and control of the user plane tunnel between the old (source) serving (R)AN node and the new (target) serving (R)AN node.

[0072] The UPF824 can function as an anchor point for internal and inter-RAT mobility, an external PDU session point interconnecting to the DN826, and a branching point to support multi-homed PDU sessions. The UPF824 can also perform packet routing and outgoing, packet inspection, enforce the user plane portion of policy rules, legally intercept packets (UP collection); traffic usage reports, perform QoS processing on the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., QoS flow mapping from SDF), transport-level packet marking on uplinks and downlinks, and perform downlink packet buffering and downlink data notification triggers. The UPF824 may include uplink classifiers to support routing traffic flows to the data network. The DN826 can represent various network operator services, internet access, or third-party services. The DN826 may include, for example, an application server.

[0073] Figure 9 is a block diagram of an exemplary UE900 that can be configured according to various embodiments of this disclosure, including the execution of instructions on a computer-readable medium corresponding to any of the exemplary methods and / or procedures described herein. The UE900 includes one or more processors 902, a transceiver 904, a memory 906, a user interface 908, and a control interface 910.

[0074] 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 internal memory and / or one or more interfaces for communicating with external memory (including memory 906). The internal or external memory may store software code, programs, and / or instructions executed by one or more processors 902 to configure and / or facilitate the UE 900 to perform various operations, including those described herein. For example, instruction execution may be configured to communicate using one or more wired or wireless communication protocols, including one or more wireless communication protocols standardized by 3GPP, such as 5G / NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, etc., or any other current or future protocols that can be used in conjunction with one or more transceivers 904, user interface 908, and / or control interface 910. As another example, one or more processors 902 may execute program code stored in other memory 906 corresponding to MAC layer protocols (e.g., for NR and / or LTE) standardized by 3GPP (e.g., for NR and / or LTE). As yet another example, the processor 902, together with one or more transceivers 904, may execute program code stored in memory 906 or other memory implementing 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] Memory 906 may include memory areas for one or more processors 902 that store variables used for protocols, configuration, control, and other functions of the UE 900, including operations corresponding to or having operations corresponding to any of the exemplary methods and / or procedures described herein. Furthermore, memory 906 may include non-volatile memory (e.g., flash memory), volatile memory (e.g., static RAM or dynamic RAM), or a combination thereof. Furthermore, memory 906 may interface with a memory slot from which removable memory cards (e.g., SD card, memory stick, compact flash, etc.) in one or more formats can be inserted and removed.

[0076] One or more transceivers 904 may include radio frequency transmitters and / or receiver circuits that facilitate communication between the UE 900 and other devices supporting wireless communication standards and / or protocols. For example, one or more transceivers 904 may include switches, mixer circuits, amplifier circuits, filter circuits, and combiner circuits. Such RF circuits may include a receive signal path having a circuit that downconverts RF signals received from a front-end module (FEM) and provides the baseband signals to baseband processors of one or more processors 902. The RF circuit may also include a transmit signal path that may include a circuit that upconverts the baseband signals provided by the baseband processors and provides the FEM with RF output signals for transmission. The FEM may include a receive signal path that may include a circuit configured to operate on RF signals received from one or more antennas, amplify the received signals, and provide the amplified version of the received signals to the RF circuit for further processing. The FEM may also include a transmit signal path that may include a circuit configured to amplify signals for transmission provided by RF circuits transmitted by one or more antennas. In various embodiments, amplification through the transmit signal path or the receive signal path may be performed in the RF circuit only, in the FEM circuit only, or in both the RF circuit and the FEM circuit. In some embodiments, the FEM circuit may include a TX / RX switch to switch between transmit mode and receive mode operation.

[0077] In some exemplary embodiments, one or more transceivers 904 include transmitters and receivers that enable 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 organizations. For example, such functionality can work in cooperation with one or more processors 902 to implement a PHY layer based on OFDM, OFDMA, and / or SC-FDMA technologies as described herein with respect to other figures.

[0078] The user interface 908 can take various forms depending on the particular embodiment, or may not be present in the UE900. In some embodiments, the user interface 908 has a microphone, a loudspeaker, a sliding button, a pressable button, a display, a touchscreen display, a mechanical keypad or virtual keypad, a mechanical keyboard or virtual keyboard, and / or any other user interface functions commonly found on a mobile phone. In other embodiments, the UE900 may include a tablet computing device having a larger touchscreen display. In such embodiments, one or more of the mechanical functions of the user interface 908 may be replaced by equivalent or functionally equivalent virtual user interface functions (e.g., virtual keypad, virtual buttons, etc.) implemented using a touchscreen display, as is well known to those skilled in the art. In other embodiments, the UE900 may be a digital computing device such as a laptop computer, desktop computer, or workstation, having a mechanical keyboard that may be integrated, detachable, or removable depending on the particular exemplary embodiment. Such a digital computing device may also include a touchscreen display. Many exemplary embodiments of the UE900 having a touchscreen display can receive user inputs such as inputs related to the exemplary methods and / or procedures described herein, or inputs known to those skilled in the art.

[0079] In some exemplary embodiments of this disclosure, the UE900 may include an orientation sensor that can be used in various ways depending on the features and functions of the UE900. For example, the UE900 may use the output of the orientation sensor to determine when the user has changed the physical orientation of the UE900's touchscreen display. The instruction signal from the orientation sensor may be available to any application program running on the UE900 so that the application program can automatically change the orientation of the display screen (e.g., from portrait to landscape) when the instruction signal indicates a change of approximately 90 degrees in the device's physical orientation. In this way, the application program can maintain the display screen in a user-readable manner regardless of the device's physical orientation. In addition, the output of the orientation sensor can be used in conjunction with various exemplary embodiments of this disclosure.

[0080] The control interface 910 can take various forms depending on the specific embodiment. For example, the control interface 910 may be an RS-232 interface, an RS-485 interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE ("FireWire") interface, or an I 2 Examples include C interfaces and PCMCIA interfaces. In some exemplary embodiments of this disclosure, the control interface 1260 may include an IEEE 802.3 Ethernet interface as described above. In some embodiments of this disclosure, the control interface 910 may include, for example, an analog interface circuit including one or more digital-to-analog (D / A) converters and / or analog-to-digital (A / D) converters.

[0081] Those skilled in the art will understand that the above list of features, interfaces, and radio frequency communication standards is merely illustrative and does not limit the scope of this disclosure. In other words, the UE900 may include more functions than those shown in Figure 9, including, for example, video and / or still image cameras, microphones, media players and / or recorders. Furthermore, one or more transceivers 904 may include communication circuits using additional radio frequency communication standards, including Bluetooth, GPS, and / or others. Furthermore, one or more processors 902 can control such additional functions by executing software code stored in memory 906. For example, the output of directional velocity and / or position estimates from a GPS receiver may be available to any application program running on the UE900, including various exemplary methods and / or computer-readable media according to various exemplary embodiments of this disclosure.

[0082] Figure 10 is a block diagram of an exemplary network node 1000 that can be configured according to various embodiments of this disclosure, including the execution of instructions on a computer-readable medium corresponding to any of the exemplary methods and / or procedures described herein.

[0083] The network node 1000 includes one or more processors 1002, a wireless network interface 1004, 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] 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 procedures disclosed herein. Memory 1006 stores software code, programs, and / or instructions executed by one or more processors 1002 and can 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 this disclosure, including one or more of the methods and / or procedures described above. Furthermore, 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 layer protocols, MAC layer protocols, RLC layer protocols, PDCP layer protocols, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and / or NR, or any other higher layer protocols used in combination with the radio network interface 1004 and the core network interface 1008. For example, but not limited to, the core network interface 1008 may include an S1 interface, and the wireless network interface 1004 may include a Uu interface standardized by 3GPP. Memory 1006 can also store variables, configurations, controls, and other functions used for the network node 1000's protocols. Thus, memory 1006 may include non-volatile memory (e.g., flash memory, hard disk, etc.), volatile memory (e.g., static RAM or dynamic RAM), network-based storage (e.g., "cloud"), or a combination thereof.

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

[0086] In some embodiments, the core network interface 1008 may include transmitters, receivers, and other circuits that enable network nodes 1000 to communicate with other devices in the core network, such as circuit-switched (CS) and / or packet-switched core (PS) networks. In some embodiments, the core network interface 1008 may include the 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 features 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 the following wired or wireless transmission technologies known to those skilled in the art: Asynchronous Transfer Mode (ATM), Internet Protocol over Ethernet (IP), SDH over optical fiber, T1 / E1 / PDH over copper, microwave radio, or other wired or wireless transmission technologies.

[0087] Other interfaces 1010 may include transmitters, receivers, and other circuits that enable the network node 1000 to communicate with external networks, computers, databases, etc., for the purpose of operating, managing, and maintaining the network node 1000 or other network equipment operably connected thereto.

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

[0089] Examples section

[0090] The following examples relate to further embodiments.

[0091] Embodiment 1A is a method for signaling in cast type indication of a wireless communication system, the method comprising: receiving a first-stage sidelink control information (SCI) format from a second UE at a first user equipment (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, wherein the sidelink feedback status indicates whether sidelink feedback is enabled or disabled, and the second-stage SCI content includes a distance setting associated with the communication range between the first UE and the second UE.

[0092] Example 2A further includes determining that sidelink feedback is enabled, and may include the method of Example 1A, wherein the type of sidelink feedback depends on the distance setting of the second stage SCI content.

[0093] Example 3A may include the method of Example 2A, wherein the type of sidelink feedback is distance-based NACK feedback and non-distance-based NACK feedback.

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

[0095] Example 5A may include the method of Example 3A, 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.

[0096] Example 6A may include the method of Example 1, wherein the second-stage SCI format is Group Cast Hybrid Auto-Retransmission Request (HARQ) feedback option 1, and the method further includes determining that only negative response (NACK) feedback is available.

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

[0098] Example 8A may include the method of Example 3A, wherein 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 comprising determining that side link feedback is enabled and determining the physical side link feedback channel (PSFCH) resource determination scheme.

[0100] Example 10A may include the method of Example 9A, wherein the PSFCH resource determination scheme is represented by bits, the bits are 0 when the PSFCH resource determination scheme is determined by a source identifier (ID), and the bits are 1 when the PSFCH resource determination scheme is determined by a source ID and a group member ID.

[0101] Example 11A may include the method of Example 1A, wherein the feedback status is represented by bits in the second-stage SCI format field of the decoded second-stage SCI format.

[0102] Example 12A may include the method of Example 11A, wherein the bit is 0 when the feedback is disabled.

[0103] Example 13A may include the method described in Example 12A, wherein the second-stage SCI format is broadcast, unicast without feedback, or groupcast without feedback.

[0104] Example 14A may include the method described in Example 11A, wherein the bit is 1 when feedback is enabled.

[0105] Example 15A may include the method described in Example 14A, wherein the second-stage SCI format is a Group Cast Hybrid Auto Resend Request (HARQ) feedback option 2, or a unicast with feedback.

[0106] Embodiment 16A may include a non-temporary computer-readable storage medium that, when executed by a processor, includes instructions to cause the processor to receive a first-stage sidelink control information (SCI) format from a second UE at a first user device (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 disabled, and the second-stage SCI content includes a distance setting associated with the communication range between the first UE and the second UE.

[0107] Example 17A may include a non-temporary computer-readable storage medium of Example 16A, wherein the instruction further causes the processor to determine that sidelink feedback is enabled, and the type of sidelink feedback depends on the distance setting of the second-stage SCI content.

[0108] Example 18A may include the non-temporary computer-readable storage medium of Example 17A, wherein the side-link feedback type is distance-based NACK feedback and non-distance-based NACK feedback.

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

[0110] Example 20A may include a non-temporary 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] Embodiment 21A is a computing device comprising a processor and a memory for storing instructions, the memory configured such that when an instruction is executed by the processor, the device receives a first-stage sidelink control information (SCI) format from a second UE at a first user device (UE), decodes the first-stage SCI format, determines the second-stage SCI format using the decoded first-stage SCI format, decodes the second-stage SCI format, and determines the 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 the communication range between the first UE and the second UE.

[0112] Embodiment 22A may include the computing device of Embodiment 21A, wherein the instruction further configures the device to determine that sidelink feedback is enabled, and the type of sidelink feedback depends on the distance setting of the second stage SCI content.

[0113] Example 23A may include the computing device of Example 22A, wherein the sidelink feedback type 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 infinitely 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 that includes means for performing one or more elements described in or related to any other method or process described herein.

[0117] Embodiment 2 may include one or more non-temporary computer-readable media containing instructions, wherein when an instruction is executed by one or more processors of an electronic device, the instruction causes the electronic device to execute one or more elements of any of the above embodiments or any other method or process described herein or related thereto.

[0118] Example 3 may include a device comprising logic, modules, or circuits that perform one or more elements of any of the above examples or any other method or process described herein or related thereto.

[0119] Example 4 may include methods, techniques, or processes described in or related to any of the above Examples, or parts thereof.

[0120] Embodiment 5 may include an apparatus comprising one or more processors and one or more computer-readable media containing 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 or part of the above embodiments.

[0121] Example 6 may include signals described in or related to any of the above examples, or a part or part thereof.

[0122] Example 7 may include datagrams, packets, frames, segments, protocol data units (PDUs), or messages described in or related to any of the above examples, or in part or in part thereof, or described in this disclosure.

[0123] Example 8 may include a data-encoded signal as described in or related to any of the above examples, or as described in this disclosure.

[0124] Example 9 may include signals encoded using datagrams, packets, frames, segments, PDUs, or messages described in or related to any of the above examples, or in part or in part thereof, or as described in this disclosure.

[0125] Example 10 may include an electromagnetic signal that carries a computer-readable instruction, which, when executed by one or more processors, causes one or more processors to execute a method, technique, or process described in or related to any or part of the above examples.

[0126] Example 11 may include a computer program in which the execution of a program by a processing element includes instructions that cause the processing element to execute a method, technique, or process described in or related to any or part of the above examples.

[0127] Example 12 may include signals within a wireless network as shown and described herein.

[0128] Example 13 may include a method of communication within 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 embodiments described above can be combined with any other embodiment (or combination of embodiments) unless otherwise specified. The above descriptions of one or more implementation forms are illustrative and illustrative, but are not intended to be exhaustive or to limit the scope of embodiments to the exact forms disclosed. Modifications and variations are possible based on the above teachings or can be derived from the practice of various embodiments.

[0132] The embodiments and implementations of the systems and methods described herein may include a variety of operations that can be embodied by machine-executable instructions performed by a computer system. The computer system may include one or more general-purpose computers or dedicated computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing operations, or it may include a combination of hardware, software, and / or firmware.

[0133] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially combined into other systems, divided into multiple systems, or otherwise divided or combined. In addition, parameters, attributes, aspects, etc. of one embodiment are intended to be usable in another embodiment. Parameters, attributes, aspects, etc. are described in one or more embodiments for clarity only, and it should be recognized that parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, etc. of another embodiment unless specifically abandoned herein.

[0134] While the foregoing has been described in some detail for clarity, it will be clear that certain changes and modifications can be made without departing from the principles. It should be noted that many alternative methods exist for implementing both the processes and apparatus described herein. Therefore, these embodiments should be considered illustrative and not limiting, and the description is not limited to the details given herein and may be modified within the appended claims and equivalents.

Claims

1. A method that is performed by UE, Reserving one or more resources for a sidelink channel, Identifying one or more preempted resources from the one or more resources for the side link, wherein the one or more preempted resources include one or more resources to be assigned to the UE in a future slot, which are taken over by a second UE having higher priority data, and the preempted resources include resources to be assigned in a future slot. Performing a sidelink channel occupancy radio (SLCR) evaluation to assess the channel availability for transmission from the UE, wherein the preempted resources corresponding to future slots are counted as unused in the SLCR evaluation. Methods that include...

2. The one or more preempted resources include reserved resources preempted by the second UE. The method according to claim 1.

3. The one or more resources reserved by the aforementioned UE are preempted by another UE having higher priority data. The method according to claim 1.

4. The one or more preempted resources mentioned above will not be counted as used in the SL CR evaluation. The method according to claim 1.

5. The one or more preempted resources include sub-parts of the one or more resources reserved by the UE. The method according to claim 1.

6. Further comprising releasing one or more of the aforementioned preempted resources due to preemption, The method according to claim 1.

7. SL CR is evaluated by dividing the total number of subchannels used for transmission within the transmission pool and the subchannels assigned within the transmission pool by the total number of subchannels configured within the transmission pool. The method according to claim 1.

8. A computing device, Processor and Memory for storing instructions, The device is provided, and when the instruction is executed by the processor, the device is configured to Reserve one or more resources for the sidelink channel, Identify one or more preempted resources from the one or more resources for the side link, the one or more preempted resources include one or more resources to be assigned to the UE in a future slot, which are taken over by a second UE having higher priority data, and the preempted resources include resources to be assigned in a future slot. The system is configured to perform a sidelink channel occupancy radio (SLCR) evaluation to assess the channel availability for transmission from the UE, and the preempted resources corresponding to future slots are counted as unused in the SLCR evaluation. Computing device.

9. The one or more preempted resources include reserved resources preempted by the second UE. The computing device according to claim 8.

10. The one or more resources reserved by the aforementioned UE are preempted by another UE having higher priority data. The computing device according to claim 8.

11. The one or more preempted resources mentioned above will not be counted as used in the SL CR evaluation. The computing device according to claim 8.

12. The one or more preempted resources include sub-parts of the one or more resources reserved by the UE. The computing device according to claim 8.

13. The instruction further configures the device to release the one or more preempted resources due to preemption. The computing device according to claim 8.

14. SL CR is evaluated by dividing the total number of subchannels used for transmission within the transmission pool and the subchannels assigned within the transmission pool by the total number of subchannels configured within the transmission pool. The computing device according to claim 8.

15. A non-temporary computer-readable storage medium, wherein when the computer-readable storage medium is executed by a processor, the processor receives The purpose is to reserve one or more resources for a sidelink channel, wherein the one or more preempted resources include one or more resources to be granted to a second UE in a future slot, which are taken over by a second UE with higher priority data, and the preempted resources include resources to be granted in a future slot. Identifying one or more preempted resources from the one or more resources for the side link, Performing a sidelink channel occupancy radio (SLCR) evaluation to assess the channel availability for transmission from the UE, wherein the preempted resources corresponding to future slots are counted as unused in the SLCR evaluation. A computer-readable medium containing instructions that cause something to be executed.

16. The one or more preempted resources include reserved resources preempted by the second UE. The computer-readable medium according to claim 15.

17. The one or more resources reserved by the aforementioned UE are preempted by another UE having higher priority data. The computer-readable medium according to claim 15.

18. The one or more preempted resources include sub-parts of the one or more resources reserved by the UE. The computer-readable medium according to claim 15.

19. The instruction further configures the computer to release the one or more preempted resources due to preemption. Computer-readable medium according to claim 15

20. SL CR is evaluated by dividing the total number of subchannels used for transmission within the transmission pool and the subchannels assigned within the transmission pool by the total number of subchannels configured within the transmission pool. The computer-readable medium according to claim 15.

Images