Techniques for PUCCH operation with multiple TRPs

Dynamic PUCCH repetition and beam management techniques address the reliability challenges in multi-TRP operations, enhancing PUCCH performance in 5G NR systems through flexible and efficient transmission configurations.

JP7590546B2Active Publication Date: 2024-11-26APPLE INC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2023507639
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-08-06
Filing Date
2021-06-11
Publication Date
2024-11-26
Estimated Expiration
2041-06-11

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in enhancing the reliability of Physical Uplink Control Channels (PUCCH) in multi-TRP operations, particularly in 5G NR systems, due to limitations in configuring dynamic PUCCH repetitions and beam configurations, which affect the robustness of data transmission.

Method used

The implementation of dynamic PUCCH repetition configurations using DCI fields, such as PDSCH-to-HARQ_Feedback Timing Indicator, new DCI fields, PUCCH resource indicators, and MAC-CE enhancements, along with beam expansion techniques like multiple beam configurations and default beam settings, to improve PUCCH reliability and coverage.

Benefits of technology

Enhances PUCCH reliability and coverage by allowing for flexible and efficient repetition and beam management, thereby improving the overall performance of wireless communication systems in multi-TRP scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007590546000001
    Figure 0007590546000001
  • Figure 0007590546000002
    Figure 0007590546000002
  • Figure 0007590546000003
    Figure 0007590546000003
Patent Text Reader

Abstract

Techniques are disclosed for physical uplink control channel (PUCCH) operation with multiple transmission and reception points (multi-TRPs). In some embodiments, determining a PUCCH transmission repetition may include determining that the original PUCCH transmission overlaps a slot boundary between a first slot for the PUCCH transmission and a second slot for the PUCCH transmission, and configuring a PUCCH repetition of the original PUCCH transmission. The PUCCH repetition may include one or more symbols of the original PUCCH transmission and may be located in one or more slots other than the first slot and the second slot. The PUCCH repetition may be configured by a downlink control information (DCI) configuration including a physical downlink shared channel-hybrid automatic repeat request-acknowledgement feedback (PDSCH-to-HARQ_feedback) timing indicator, a PUCCH repetition number field configuring the number of transmissions of the PUCCH repetition, or a PUCCH resource indicator field configuring the number of transmissions of the PUCCH repetition.
Need to check novelty before this filing date? Find Prior Art

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 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, the RAN node may include a 5G node, an NR node (also referred to as next-generation Node B, or gNode B (gNB)).

[0003] The RAN communicates between the RAN nodes and the UEs using radio access technologies (RATs). The RANs may include 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 RATs, the UTRAN implements the universal mobile telecommunication system (UMTS) RAT or other 3GPP RATs, the E-UTRAN implements the LTE RAT, and the NG-RAN implements the 5G RAT. In certain deployments, the E-UTRAN may also implement the 5G RAT.

[0004] The 5G NR frequency band can be divided into two different frequency ranges. Frequency Range 1 (FR1) includes sub-6 GHz frequency bands, some of which may be used by previous standards, but which may be extended to cover potential new frequency bands offering 410 MHz to 7125 MHz. Frequency Range 2 (FR2) includes the 24.25 GHz to 52.6 GHz frequency bands. The FR2 mmWave range bands have a shorter range than the FR1 bands, but the available bandwidth is higher. It will be understood by those skilled in the art that these frequency ranges, provided as examples, may vary from time to time or from region to region.

[0005] 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]

[0006] [Figure 1] 1 illustrates a process for configuring physical uplink control channel (PUCCH) repetition in accordance with some embodiments. [Diagram 2] 1 illustrates a process for configuring PUCCH recurrence scheduling according to some embodiments. [Figure 3A] 1 shows a diagram illustrating an example minimum timing offset reflecting a minimum Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) processing time for a Physical Downlink Shared Channel (PDSCH) in accordance with some embodiments. [Figure 3B] FIG. 2 shows a diagram illustrating a first iterative mode and a second iterative mode according to some embodiments. [Figure 4] 1 illustrates a process for PUCCH repetition according to some embodiments. [Diagram 5] 1 shows a diagram illustrating a PUCCH repetition solution according to some embodiments. [Figure 6] 1 illustrates another process for PUCCH repetition according to some embodiments. [Figure 7] 1 shows another diagram illustrating a PUCCH repetition solution according to some embodiments. [Figure 8] 1 illustrates an example architecture of a system of a network, according to some embodiments. [Figure 9] 1 illustrates infrastructure equipment according to some embodiments. [Figure 10] 1 illustrates a platform according to some embodiments. [Figure 11] 1 illustrates system components according to some embodiments. [Figure 12] 1 illustrates a table for Medium Access Control - Control Element (MAC-CE) in accordance with some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] In a New Radio (NR) Physical Uplink Control Channel (PUCCH) design, the PUCCH may have one of the following formats: PUCCH Format 0: 1-2 symbols, 1-2 bit payload; PUCCH Format 1: 4 symbols or more, 1-2 bit payload; PUCCH Format 2: 1-2 symbols, greater than 2 bit payload; PUCCH Format 3: 4 symbols or more, greater than 2 bit payload; PUCCH Format 4: 4 symbols or more, greater than 2 bit payload. PUCCH slot aggregation may be allowed. For example, a radio resource control (RRC) may configure a parameter nrofSlots in a PUCCH-FormatConfig parameter of a PUCCH-Config Parameter. Furthermore, the PUCCH beam may be changed via a Medium Access Control (MAC) Control Element (CE), MAC-CE. For example, the RRC may configure a list of PUCCH-SpatialRelationInfo parameters in the PUCCH-Config parameter, and the MAC-CE may be used to activate a particular beam for a particular PUCCH resource. Only one beam can be configured for one PUCCH resource.

[0008] In 3GPP Release 16, for multiple transmit / receive point (multi-TRP) operation, physical downlink shared channel (PDSCH) reliability can be increased by enabling more dynamic PDSCH aggregation using downlink control information (DCI) control, and multiple beams can be configured for the same PDSCH with multiple transmission occasions. Embodiments of the present disclosure can increase PUCCH reliability, including, for example, multi-TRP operation. In some embodiments, DCI is used to configure dynamic PUCCH repetition. In some embodiments, PUCCH repetition extensions are provided. In some embodiments, PUCCH beam configuration extensions are provided. In some embodiments, if PUCCH-SpatialRelationInfo is not provided, a default beam is provided.

[0009] As mentioned above, in some embodiments, DCI may be used to configure dynamic PUCCH repetition according to one or more of the following solutions. Solution 1.1

[0010] In some embodiments, the DCI may be used to configure dynamic PUCCH repetitions by extending the DCI field "PDSCH-to-HARQ_Feedback Timing Indicator". For example, a codepoint may be configured for the DCI field "PDSCH-to-HARQ_Feedback Timing Indicator". The codepoint may be configured in the dl-DataToUL-ACK, dl-DataToUL-ACK-r16 or dl-DataToUL-ACKForDCIFormat1_2 parameters of the PUCCH-Config parameters. For each codepoint, the RRC may simultaneously configure the following information: a timing offset, which may be a value ranging for example from 0 to 15, and a number of PUCCH repetitions, which may be a value ranging for example from 1 to N, where N is at least greater than 8. Alternatively, the number of repetitions may not be configured and in such a case the number of repetitions may be assumed to be 1. Solution 1.2

[0011] In some embodiments, the DCI may be used to configure dynamic PUCCH repetitions by introducing a new DCI field. For example, the new DCI field may be the number of PUCCH repetitions. The value of the new DCI field may be from 1 to N, where N is at least greater than 8. If the new DCI field is not configured, the number of repetitions may be assumed to be 1. Solution 1.3

[0012] In some embodiments, the DCI may be used to configure dynamic PUCCH repetitions by configuring the DCI field "PUCCH resource indicator". The PUCCH resource configuration may be extended by adding a configuration information element (IE) for the number of repetitions. The value of the number of repetitions and / or the PUCCH resource indicator may be from 1 to N, where N is at least greater than 8. If the value of the number of repetitions and / or the PUCCH resource indicator is not configured, the value is assumed to be 1. Solution 1.4

[0013] In some embodiments, the PUCCH aggregation (or repetition) extension may be limited to some of the PUCCH formats described above, for example, only for long PUCCH formats, e.g., one, a subset, or all of the following formats: PUCCH format 1, PUCCH format 3, PUCCH format 4, may have the extension.

[0014] In some embodiments, the PUCCH repetition extension may be provided using one or more of the following solutions: Solution 2.1

[0015] In some embodiments, when PUCCH repetitions are scheduled, the user equipment (UE) is allowed to operate in two possible repetition modes: mode 1, where the PUCCH is repeated consecutively and a constant may also be configured between the PUCCH repetitions, or mode 2, where the PUCCH is repeated in consecutive slots and the same time domain allocation may be used within each slot. Solution 2.2

[0016] In some embodiments, the UE may report a maximum number of PUCCH repetitions that the UE may transmit in a slot. For example, candidate values ​​for the maximum number of PUCCH repetitions that the UE may transmit in a slot may be 2, 4, or 7. For example, if the number of repetitions in a slot exceeds the UE capability, the additional repetitions may be transmitted in the next available slot using the same time domain resource allocation as the repetitions that do not exceed the capability. Solution 2.3

[0017] In some embodiments, a minimum timing offset is determined between the PDSCH and the PUCCH for Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) and / or between the Channel State Information Reference Signal (CSI-RS) / Synchronization Signal Block (SSB) measurement and the corresponding CSI report on the PUCCH. For example, the minimum timing offset may be based on the first PUCCH transmission occasion. In another example, the minimum timing offset may be based on any PUCCH transmission occasion. In some embodiments, the minimum timing offset must meet a PUCCH minimum timing offset requirement, where the UE transmits only PUCCH repetition occasions that meet this PUCCH minimum timing offset requirement. Solution 2.4

[0018] In some embodiments, when there is a single PUCCH transmission occasion across a slot boundary, there are the following alternative solutions for repeated PUCCH transmission: Alternative 1: PUCCH repetitions are allowed and transmitted by the UE as normal. Alternative 2: Repeated PUCCH is truncated (e.g. symbols of the original PUCCH that cross the slot boundary are not transmitted in the repetition). Alternative 3: The repeated PUCCH is segmented (e.g., the original PUCCH is split into two repeated PUCCHs, with the first repeated PUCCH containing all symbols of the first slot and the second repeated PUCCH containing all symbols of the second slot). Alternative 4: The entire PUCCH repetition is skipped. Solution 2.5

[0019] In some embodiments, if a single PUCCH transmission occasion becomes invalid (e.g., it has at least one symbol configured as a downlink (DL) symbol, its uplink transmission is preempted, and / or it collides with other higher priority channels and is dropped), PUCCH repetitions may be provided according to one or more of the following alternatives: Alternative 1: The repeated PUCCH is truncated, for example if no symbols of the original PUCCH beyond the DL symbols of the original PUCCH are transmitted. Alternative 2: The repeated PUCCH is segmented based on the DL symbols of the original PUCCH, eg a first segment includes symbols up to the DL symbol and a second segment includes symbols after the DL symbol. Alternative 3: The entire PUCCH repetition is skipped.

[0020] In some embodiments, the PUCCH beam configuration is extended according to one or more of the following solutions: Solution 3.1

[0021] In some embodiments, if PUCCH repetition is configured, multiple beams (e.g., two beams) may be configured for the PUCCH. For example, the configuration may specify the following beam patterns: {beam 1, beam 2, beam 1, beam 2, ...} sequential pattern, or {beam 1, beam 1, beam 2, beam 2, ...} cyclic pattern. Solution 3.2

[0022] In some embodiments, the DCI may explicitly indicate the PUCCH beam. For example, a new field in the DCI may be introduced to configure the PUCCH beam. For example, the new field may include one or two quasi-collocation (QCL) configurations. For example, if the new field includes two QCL configurations, two reference signals (RS) may be configured for QCL-TypeA or QCL-Typed or both, and each RS may be a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), or a sounding reference signal (SRS). Solution 3.3

[0023] In some embodiments, the PUCCH-SpatialRelationInfo parameter can be extended to allow for the configuration of two PUCCH beams. For example, a PUCCH-SpatialRelationInfo codepoint can be configured to include two PUCCH-SpatialRelationInfo parameters. For example, a single PUCCH-SpatialRelationInfo parameter can be configured to include two beams (e.g., referenceSignal parameters). Solution 3.4

[0024] In some embodiments, the MAC-CE is permitted to activate two PUCCH spatial relationships of PUCCH resources. For example, this solution may modify the existing MAC-CE (shown as table 1200 in FIG. 12, which reflects FIG. 6.1.3.18-1 in 3GPP Release 16) as follows:

[0025] For example, an additional octet row (e.g., another S0-S7) may be added under Oct 3 and used to configure a second PUCCH beam. Furthermore, for each octet row (e.g., Oct 3 and the additional octet row), for example, the last two rows, only a single PUCCH spatial relationship (e.g., PUCCH-SpatialRelationInfo parameter) may be activated. In another example, both rows may activate the same PUCCH spatial relationship. In another example, both rows may activate different PUCCH spatial relationships.

[0026] In some embodiments, a default beam may be used if the PUCCH-SpatialRelationInfo parameter is not provided according to the following solution. Solution 4.1

[0027] In some embodiments, if the PUCCH-SpatialRelationInfo parameter is not provided and the UE is configured with PUCCH repetition, a default beam may be provided according to the following alternatives: Alternative 1: Default for the PDSCH activation transmission configuration indicator (TCI) codepoint with the lowest index with two TCI states. Alternative 2: Default for each CORESETPoolIndex parameter CORESET with the lowest ID for each beam. Alternative 3: Default for the PDSCH activation TCI codepoint with the lowest ID only. Alternative 4: Default for the CORESET with the lowest ID in the latest PDCCH monitoring slot.

[0028] Various solutions will now be described in more detail with reference to the accompanying drawings. It should be noted that each of the solutions may be implemented by a UE (e.g., the UE executes one or more blocks of the disclosed processes), by a combination of a UE and other system components, or by a system component other than a UE, the order of the blocks described in the disclosed processes may differ from the order shown in the figures, one or more blocks of the disclosed processes may be combined with each other (including from different processes) and / or removed, and processes may be combined with each other such that blocks from one or more processes are used with blocks of one or more other processes to form a combined process.

[0029] 1 shows a process 100 for configuring a PUCCH repetition according to some embodiments. In some embodiments, a DCI may be used to configure a dynamic PUCCH repetition. For example, configuring a DCI may configure a dynamic PUCCH repetition.

[0030] In block 102, multiple transmission / reception point (multi-TRP) operation is determined. In some embodiments, the UE may determine that it is configured for multi-TRP operation and PUCCH. In some embodiments, the network may determine that the UE is configured for multi-TRP operation and PUCCH.

[0031] In block 104, the PUCCH repetitions are configured. In some embodiments, the DCI is configured to configure the PUCCH repetitions. In some embodiments, the DCI is configured by using a DCI field "PDSCH-to-HARQ_Feedback Timing Indicator". For example, a code point (e.g., one or more values, such as numeric values, reflecting a desired setting or parameter) may be configured for the DCI field "PDSCH-to-HARQ_Feedback Timing Indicator". The code point may be configured, for example, in a dl-DataToUL-ACK parameter, a dl-DataToUL-ACK-r16 parameter, or a dl-DataToUL-ACKForDCIFormat1_2 parameter of the PUCCH-Config parameters. In some embodiments, the DCI field PDSCH-to-HARQ_Feedback Timing Indicator is configured by radio resource control (RRC) to configure the number of transmissions of the PUCCH repetitions (e.g., the number of PUCCH repetitions). In some embodiments, for one or more of the code points, the RRC configures the timing offset and / or the number of PUCCH repetitions. For example, the configuration of the timing offset and the number of PUCCH repetitions may be simultaneous. For example, the timing offset may be a value ranging from 0 to 15. For example, the number of PUCCH repetitions may be a value ranging from 1 to N, where N is at least greater than 8. In some embodiments, if the number of PUCCH repetitions is not configured, the number of repetitions is assumed to be 1. For example, the number of PUCCH repetitions may be the number of times the PUCCH repetitions are transmitted.

[0032] In some embodiments, the DCI is configured to configure the PUCCH repetitions by introducing or including a new DCI field. For example, the new DCI field can be the number of PUCCH repetitions. In some embodiments, the value of the new DCI field can be from 1 to N, where N is at least greater than 8. In some embodiments, if the new DCI field is not configured, the number of repetitions is assumed to be 1. For example, the number of PUCCH repetitions can be the number of times the PUCCH repetitions are transmitted.

[0033] In some embodiments, the DCI is configured to configure the PUCCH repetitions by configuring the DCI field "PUCCH resource indicator". For example, a configuration information element (IE) of number of repetitions is used to configure the PUCCH resource indicator field. In some embodiments, the value of the number of repetitions and / or the PUCCH resource indicator may be from 1 to N, where N is at least greater than 8. In some embodiments, if the value of the number of repetitions and / or the PUCCH resource indicator is not configured, the value is assumed to be 1. For example, the number of PUCCH repetitions may be the number of times the PUCCH repetitions are transmitted.

[0034] In some embodiments, PUCCH repetitions using DCI (e.g., PUCCH repetition extension) are restricted to certain PUCCH formats. For example, the PUCCH may have one of the following formats: PUCCH format 0: 1-2 symbols, 1-2 bit payload, PUCCH format 1: 4 symbols or more, 1-2 bit payload, PUCCH format 2: 1-2 symbols, more than 2 bit payload, PUCCH format 3: 4 symbols or more, more than 2 bit payload, PUCCH format 4: 4 symbols or more, more than 2 bit payload. In some embodiments, PUCCH repetitions are configured only for one, a subset, or all of the above PUCCH formats. In some embodiments, PUCCH repetitions are configured only for one, a subset, or all of PUCCH format 1, PUCCH format 3, and / or PUCCH format 4.

[0035] In some embodiments, multiple beams are configured in a PUCCH repetitive configuration. For example, multiple beams (e.g., two beams) may be configured for the PUCCH. In some embodiments, the multiple beams are configured in a pattern. For example, the pattern may be a sequential pattern, and the first beam and the second beam are configured to be transmitted according to the following pattern: {number of cycles, first beam, second beam, first beam, second beam, ... etc.}. In another example, the pattern may be a periodic pattern, and the first beam and the second beam are configured to be transmitted according to the following pattern: {number of cycles, first beam, first beam, second beam, second beam, ... etc.}.

[0036] In some embodiments, the DCI may explicitly indicate a PUCCH beam for a PUCCH repetition configuration. For example, a new field in the DCI may be introduced to configure a PUCCH beam. For example, the new field may include one or two quasi-collocation (QCL) configurations. For example, if the new field includes two QCL configurations, two reference signals (RS) may be configured for QCL-TypeA or QCL-Typed or both, and each RS may be a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), or a sounding reference signal (SRS).

[0037] In some embodiments, the PUCCH-SpatialRelationInfo parameter can be extended to allow configuration of two PUCCH beams for a PUCCH repetition configuration. For example, a PUCCH-SpatialRelationInfo codepoint can be configured to include two PUCCH-SpatialRelationInfo parameters. For example, a single PUCCH-SpatialRelationInfo parameter can be configured to include two beams (e.g., referenceSignal parameters).

[0038] In some embodiments, the MAC-CE is permitted to activate two PUCCH spatial relationships of PUCCH resources (e.g., for a PUCCH repetition configuration). For example, this solution may modify the existing MAC-CE (shown as table 1200 in FIG. 12, which reflects FIG. 6.1.3.18-1 in 3GPP Release 16) as follows:

[0039] In some embodiments, additional octet rows S0-S7 are added below Oct 3 and are used to configure a second PUCCH beam. In some embodiments, for each octet row of the last two rows (e.g., Oct 3 and the additional octet row), only a single PUCCH spatial relationship (e.g., PUCCH-SpatialRelationInfo parameter) may be activated. In another example, both rows may activate the same PUCCH spatial relationship. In another example, both rows may activate different PUCCH spatial relationships.

[0040] In some embodiments, if the PUCCH-SpatialRelationInfo parameter is not provided, a default beam is used. In some embodiments, if the PUCCH-SpatialRelationInfo parameter is not provided and the UE is configured with PUCCH repetition, a default beam may be provided according to the following alternatives: In some embodiments, in alternative 1, each beam defaults to the PDSCH activation transmission configuration indicator (TCI) codepoint with the lowest index having two TCI states. In some embodiments, in alternative 2, each beam defaults to the respective CORESETPoolIndex parameter CORESET with the lowest ID. In some embodiments, in alternative 3, each beam defaults to the PDSCH activation TCI codepoint with only the lowest ID. In some embodiments, in alternative 4, each beam defaults to the CORESET with the lowest ID in the latest PDCCH monitoring slot.

[0041] In block 106, one or more PUCCH repetitions are transmitted according to the PUCCH repetition configuration / configuration.

[0042] FIG. 2 illustrates a process 200 for configuring PUCCH recurrence scheduling according to some embodiments.

[0043] In block 202, a PUCCH repetition configuration is determined. In some embodiments, the UE determines that it is configured for PUCCH repetition. In some embodiments, the network determines that the UE is configured for PUCCH repetition. In some embodiments, the PUCCH repetition is configured as described in block 104.

[0044] In block 204, the PUCCH repetition parameter is reported. In some embodiments, a UE configured for PUCCH repetition reports or transmits the PUCCH repetition parameter to the network. For example, the UE may report the maximum number of PUCCH repetitions that the UE can or is configured to transmit in a slot. In some embodiments, the candidate values ​​for the number of repetitions are 2, 4, or 7. In some embodiments, if the number of repetitions in a slot exceeds the UE's capabilities, the additional repetitions are transmitted in the next available slot. In some embodiments, these additional repetitions are transmitted in the next available slot using the same time domain resource allocation as the repetitions that do not exceed the capabilities. In some embodiments, the next available slot is a slot adjacent to the current slot. In some embodiments, the next available slot is not adjacent to the current slot and is located one or more slots away from the current slot.

[0045] In block 206, a minimum timing offset of the PUCCH repetition is determined. In some embodiments, the minimum timing offset determines when the first PUCCH can be scheduled. In some embodiments, the minimum timing offset is between the PDSCU for HARQ-ACK and its respective PUCCH, reflecting the minimum HARQ-ACK processing time. In some embodiments, the minimum timing offset is between the CSI-RS / SSB measurement and the corresponding CSI report on the PUCCH.

[0046] In some embodiments, the minimum timing offset is based on the first PUCCH transmission occasion. In some embodiments, the minimum timing offset is based on any PUCCH transmission occasion. In some embodiments, the minimum timing offset must meet a PUCCH minimum timing offset requirement. For example, the UE transmits only PUCCH recurring occasions that meet this PUCCH minimum timing offset requirement.

[0047] As discussed above, in some embodiments, the minimum timing offset reflects a minimum HARQ-ACK processing time. In some embodiments, the first PUCCH repetition occasion meets a minimum HARQ-ACK processing time associated with a PDSCH. In some embodiments, the first or any other PUCCH repetition occasion meets a minimum HARQ-ACK processing time associated with a PDSCH. In some embodiments, the UE need not transmit a PUCCH repetition occasion that does not meet a minimum HARQ-ACK processing time associated with a PDSCH. In some embodiments, the UE transmits a PUCCH repetition occasion that meets a minimum HARQ-ACK processing time associated with a PDSCH.

[0048] 3A illustrates a diagram 300 illustrating an example minimum timing offset reflecting a minimum HARQ-ACK processing time 302 for a PDSCH 304, according to some embodiments. In diagram 300, PUCCHs 306, 308, 310, and 312 are possible PUCCH transmissions for the PDSCH 304. As illustrated by diagram 300, the minimum HARQ-ACK processing time 302 extends from the PDSCH 304 (e.g., from after the last symbol of the PDSCH 304) to a portion of slot 4. Thus, in the illustrated example, PUCCHs 306 and 308 do not meet the minimum timing offset because they are located within the minimum HARQ-ACK processing time 302. Thus, PUCCHs 306 and 308 may not be the first PUCCH transmissions after the PDSCH 304. In the illustrated example, PUCCHs 310 and 312 comply with the minimum timing offset because they are located in slots 5 and 6 after slots 1, 2, 3, and 4, which are covered by the minimum HARQ-ACK processing time 302. Thus, the first PUCCH transmission after PDSCH 304 may be PUCCH 310 and the repeated PUCCH may be PUCCH 312, since it complies with the minimum timing offset.

[0049] Returning to FIG. 2, in block 208, PUCCH repetitions are scheduled. In some embodiments, the scheduled PUCCH repetitions comply with a minimum timing offset of the PUCCH repetitions. In some embodiments, PUCCH repetition scheduling provides that the UE is allowed to operate in a first repetition mode and / or a second repetition mode. FIG. 3B shows a diagram 314 illustrating a first repetition mode and a second repetition mode, according to some embodiments. In the first repetition mode, the PUCCH repetitions are repeated consecutively. In some embodiments, a constant number can also be configured between the PUCCH repetitions. In some embodiments, the consecutive repetitions overlap one or more slot boundaries. As shown in FIG. 314, in the first repetition mode 316, the PUCCH repetitions 318, 320, 322, and 324 are repeated consecutively and overlap the boundaries between slots 1, 2, and 3. In the second repetition mode, the PUCCH repetitions are repeated in consecutive slots, and one or more slot boundaries do not overlap the PUCCH. In some embodiments, the repetitions can use the same time domain allocation within each slot. As shown in diagram 314, in a second repetition mode 326, PUCCH repetitions 328, 330, 332, and 334 are repeated in consecutive slots, which do not overlap with the PUCCH.

[0050] In block 210, one or more PUCCH repetitions are transmitted according to the schedule / scheduled PUCCH repetitions.

[0051] 4 shows a process 400 for PUCCH repetition according to some embodiments. In block 402, a PUCCH repetition configuration is determined. In some embodiments, the UE determines that it is configured for PUCCH repetition. In some embodiments, the network determines that the UE is configured for PUCCH repetition. In some embodiments, this block may be the same as or similar to block 202. In some embodiments, the PUCCH repetition is configured as described in block 104.

[0052] At block 404, an original PUCCH transmission that overlaps a slot boundary is determined. For example, the slot boundary may be a boundary between a first slot for PUCCH transmission and a second slot for PUCCH transmission. In some embodiments, the original PUCCH transmission overlaps a single slot boundary. In some embodiments, the original PUCCH transmission overlaps one or more slot boundaries. In some embodiments, the original PUCCH transmission overlaps two or more slot boundaries.

[0053] In block 406, a PUCCH repetition technique for an original PUCCH transmission that overlaps one or more slot boundaries is determined. Various PUCCH repetition techniques / solutions according to some embodiments are illustrated in diagram 500 of Figure 5. For example, diagram 502 of Figure 5 illustrates an original PUCCH 504 that overlaps with a slot boundary 506 between slot 1 and slot 2.

[0054] In some embodiments, the PUCCH repetition is a repetition of the original PUCCH transmission. In solution 508, a PUCCH repetition 510 is permitted and transmitted by the UE in slots 3 and 4 across the boundary 512 between slots 3 and 4 (e.g., the repetition 510 overlaps the boundary 512). The PUCCH repetition 510 is a repetition of the original PUCCH 504 and includes all symbols of the PUCCH 504.

[0055] In some embodiments, the PUCCH repetition is a shortened version of the original PUCCH transmission. For example, in solution 514, one or more or all of the symbols of the original PUCCH 504 that cross or overlap the slot boundary 506 are not transmitted in the repetition. Thus, one or more symbols transmitted in the repetition are within the repetition PUCCH 516, and the remaining truncated symbols 518 of the original PUCCH 504 that are located after the slot boundary 520 are not transmitted in the repetition.

[0056] In some embodiments, the PUCCH repetitions are segmented versions of the original PUCCH transmission. For example, in solution 522, the original PUCCH 504 is segmented for repetition into a repeated PUCCH 524 and a repeated PUCCH' 526, where the segmentation occurs at the slot boundary 528. Here, the repeated PUCCH 524 includes one or more or all symbols of the original PUCCH 504 from slot 1, and the repeated PUCCH' 526 includes one or more or all symbols of the original PUCCH 504 from slot 2.

[0057] In some embodiments, the PUCCH repetition is skipped, as shown in solution 530 of Figure 5. For example, the PUCCH repetition may be generated but not transmitted. In another example, the PUCCH repetition is not generated at all.

[0058] 4, one or more PUCCH repetitions are transmitted according to the determined repetition in block 408. If the PUCCH repetition is skipped, the PUCCH repetition is not transmitted.

[0059] 6 illustrates a process 600 for PUCCH repetition according to some embodiments. In block 602, an invalid original PUCCH transmission is determined. For example, the determination may include one or more of determining that the original PUCCH transmission has at least one symbol configured as a downlink (DL) symbol, determining that the original PUCCH transmission has a preempted uplink transmission, and / or determining that the original PUCCH transmission collides with one or more other higher priority channels and is to be dropped.

[0060] At block 604, a PUCCH repetition for the determined invalid original PUCCH transmission is determined. A PUCCH repetition solution according to some embodiments is shown in diagram 700 of Figure 7. In some embodiments, the original PUCCH includes one or more downlink (DL) symbols. For example, diagram 702 shows an original PUCCH 704 including a DL symbol 706. The original PUCCH 704 straddles the slot boundary between slot 1 and slot 2, but need not cross a slot boundary and may be contained in a single slot.

[0061] In some embodiments, the PUCCH repetition is a shortened version of the original PUCCH based on the location of the DL symbol in the original PUCCH. For example, in solution 708, the repeated PUCCH 710 includes symbols of the original PUCCH 704 through the DL symbol 706, where the DL symbol 706 is represented by DL 712 in the repeated PUCCH 710. Symbols of the original PUCCH 704 located before or after the DL symbol 706 are not transmitted in the repeated PUCCH 710. In some embodiments, the DL 712 is not included in the repeated PUCCH 710.

[0062] In some embodiments, the PUCCH repetition is a segmented version of the original PUCCH based on the location of the DL symbol in the original PUCCH. For example, in solution 714, the first segment repetition PUCCH 716 includes symbols located up to (e.g., before) but not including the DL symbol 706 in the original PUCCH 704, and the second segment repetition PUCCH 720 includes symbols located after but not including the DL symbol 706 in the original PUCCH 704. If included, region 718 reflects where the DL symbol 706 of the original PUCCH 704 would have been located in the repetition. In some embodiments, the DL symbol is included in one or both of the first segment repetition PUCCH 716 and / or the second segment repetition PUCCH 720.

[0063] In some embodiments, the PUCCH repetition is skipped, as shown in solution 722 of Figure 7. For example, the PUCCH repetition may be generated but not transmitted. In another example, the PUCCH repetition is not generated at all.

[0064] Returning to Figure 6, one or more PUCCH repetitions are transmitted according to the determined repetition in block 606. If the PUCCH repetition is skipped, the PUCCH repetition is not transmitted.

[0065] 8 illustrates an example architecture of a system 800 of networks according to various embodiments. The following description is provided for the example system 800 operating in conjunction with LTE and 5G or NR system standards as provided by 3GPP technical specifications. However, the example embodiments are not limited in this respect, and the described embodiments may be applied to other networks that would benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.).

[0066] 8, system 800 includes UE 822 and UE 820. In this example, UE 822 and UE 820 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may include any mobile or non-mobile computing device, such as a consumer electronics device, a cellular phone, a smartphone, a feature phone, a tablet computer, a wearable computing device, a personal digital assistant (PDA), a pager, a wireless handset, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-vehicle entertainment (ICE) device, an instrument cluster (IC), a head-up display (HUD) device, an on-board diagnostics (OBD) device, a dash-top mobile equipment (DME), a mobile data terminal (MDT), an electronic engine management system (EEMS), an electronic / engine control unit (ECU), an electronic engine / engine control module (ECM), an embedded system, a microcontroller, a control module, an engine management system (EMS), a networked or "smart" appliance, an MTC device, an M2M, an IoT device, or the like.

[0067] In some embodiments, the UE 822 and / or UE 820 may be IoT UEs, which may have a network access layer designed for low-power IoT applications utilizing short-lived UE connections. The IoT UEs may utilize technologies such as M2M or MTC to exchange data with MTC servers or devices over PLMN, ProSe or D2D communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated exchanges of data. An IoT network refers to IoT UEs connecting with each other, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) over short-lived connections. The IoT UEs may run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity of the IoT network.

[0068] The UE 822 and the UE 820 may be configured to connect, e.g., be communicatively coupled, to an access node or radio access node (depicted as (R)AN 808). In an embodiment, the (R)AN 808 may be an NG RAN or SG RAN, an E-UTRAN, or a legacy RAN such as a UTRAN or GERAN. As used herein, the terms "NG RAN" and the like may refer to an (R)AN 808 operating in an NR or SG system, and the terms "E-UTRAN" and the like may refer to an (R)AN 808 operating in an LTE or 4G system. The UE 822 and the UE 820 each utilize a connection (or channel) (depicted as connection 804 and connection 802), each of which comprises a physical communication interface or layer (described in more detail below).

[0069] In this example, the connection 804 and the connection 802 are shown as air interfaces to enable a communicative coupling and may correspond to a cellular communication protocol such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a SG protocol, a NR protocol, and / or any of the other communication protocols discussed herein. In an embodiment, the UE 822 and the UE 820 may directly exchange communication data via a ProSe interface 810. The ProSe interface 810 may alternatively be referred to as a sidelink (SL) interface 110 and may include one or more logical channels including, but not limited to, a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

[0070] The UE 820 is shown configured to access the AP 812 (also referred to as a "WLAN node", "WLAN", "WLAN terminal", "WT", etc.) via a connection 824. The connection 824 may comprise a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, where the AP 812 would comprise a Wi-Fi (Wireless Fidelity) router. In this example, the AP 812 may be connected to the Internet without connecting to a core network of a wireless system (described in more detail below). In various embodiments, the UE 820, (R)AN 808, and AP 812 may be configured to utilize LWA and / or LWIP operations. LWA operations may require the UE 820 of an RRC connection configured with the RAN node 814 or RAN node 816 to utilize LTE and WLAN radio resources. LWIP operations may involve the UE 820 using WLAN radio resources (e.g., connection 824) through an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent over the connection 824. IPsec tunneling may involve encapsulating the entire original IP packet and adding a new packet header, thereby protecting the IP packet's original header.

[0071] The (R)AN 808 may include one or more AN nodes, such as RAN node 814 and RAN node 816, that enable connection 804 and connection 802. As used herein, the terms “access node”, “access point”, etc. may refer to equipment that provides wireless baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeBs, RSUs, TRxP, TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms “NG RAN node” etc. may refer to a RAN node operating in a NR or SG system (e.g., gNB), and the terms “E-UTRAN node” etc. may refer to a RAN node operating in a LTE or 4G system 800 (e.g., eNB). According to various implementations, the RAN node 814 or the RAN node 816 may be implemented as one or more of a macrocell base station and / or a dedicated physical device, such as a low power (LP) base station to provide a femtocell, picocell, or other similar cell having a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0072] In some implementations, all or a portion of the RAN node 814 or RAN node 816 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement a RAN functionality split, such as a PDCP split, where the RRC and PDCP layers are operated by the CRAN / vBBUP and other L2 protocol entities are operated by an individual RAN node (e.g., the RAN node 814 or the RAN node 816), a MAC / PHY split, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP and the PHY layer is operated by an individual RAN node (e.g., the RAN node 814 or the RAN node 816), or a "lower PHY" split, where the RRC, PDCP, RLC, MAC layers, and the upper part of the PHY layer are operated by the CRAN / vBBUP and the lower part of the PHY layer is operated by an individual RAN node. This virtualized framework allows freed processor cores of the RAN node 814 or RAN node 816 to run other virtualized applications. In some aspects, each RAN node may represent an individual gNB-DU connected to a gNB-CU via an individual F1 interface (not shown in FIG. 8). In these implementations, the gNB-DUs may include one or more remote radio heads or RFEMs, and the gNB-CU may be operated by a server located in the (R)AN 808 (not shown) or by a server pool in a manner similar to CRAN / vBBUP. Additionally or alternatively, one or more of the RAN node 814 or RAN node 816 may be a next-generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminals toward the UE 822 and UE 820 and is connected to the SGC via an NG interface (described below). In a V2X scenario, one or more of the RAN node 814 or RAN node 816 may be or serve as an RSU.

[0073] The term "Road Side Unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, and an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", etc. In one example, the RSU is a computing device coupled to radio frequency circuitry located at the roadside that provides connectivity support to passing vehicular UEs (vUEs). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for detecting and controlling ongoing vehicular and pedestrian traffic. The RSU may operate in the 5.9 GHz Direct Short Range Communication (DSRC) band to provide very low latency communications necessary for high speed events such as collision avoidance, traffic warnings, etc. Additionally or alternatively, the RSU may operate in a cellular V2X band to provide the aforementioned low latency communications, as well as other cellular communication services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device(s) and the radio frequency circuitry of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or a backhaul network.

[0074] Either the RAN node 814 and / or the RAN node 816 may terminate the air interface protocols and be the first point of contact for the UE 822 and the UE 820. In some embodiments, the RAN node 814 and / or the RAN node 816 may perform various logical functions for the (R)AN 808, including, but not limited to, a Radio Network Controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0075] In an embodiment, the UE 822 and the UE 820 may be configured to communicate with each other or with the RAN node 814 and / or the RAN node 816 using OFDM communication signals over multi-carrier communication channels according to various communication technologies, such as, but not limited to, OFDMA communication technologies (e.g., for downlink communications) or SC-FDMA communication technologies (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. An OFDM signal may include multiple orthogonal subcarriers.

[0076] In some embodiments, a downlink resource grid can be used for downlink transmissions from the RAN node 814 and / or the RAN node 816 to the UE 822 and UE 820, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or a time-frequency resource grid, which is the physical resources of the downlink in each slot. Such a time-frequency plane representation is common in OFDM systems, making the allocation of radio resources intuitive. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit of the resource grid is denoted as a resource element. Each resource grid contains a number of resource blocks, which represent the mapping of a particular physical channel to the resource elements. Each resource block contains a set of resource elements, which in the frequency domain can represent the smallest amount of resources that can currently be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

[0077] According to various embodiments, UE 822 and UE 820 and RAN node 814 and / or RAN node 816 communicate data (e.g., transmit and receive) over licensed media (also referred to as "licensed spectrum" and / or "licensed band") and unlicensed shared media (also referred to as "unlicensed spectrum" and / or "unlicensed band"). The licensed spectrum may include channels operating in a frequency range from about 400 MHz to about 3.8 GHz, and the unlicensed spectrum may include the 5 GHz band.

[0078] To operate in the unlicensed spectrum, the UE 822 and UE 820 and the RAN node 814 or RAN node 816 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UE 822 and UE 820 and the RAN node 814 or RAN node 816 may perform one or more known medium sensing and / or carrier sensing operations to determine if one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a Listen Before Talk (LBT) protocol.

[0079] LBT is a mechanism by which devices (e.g., UE 822 and UE 820, RAN node 814 or RAN node 816, etc.) sense the medium (e.g., channel or carrier frequency) and transmit when the medium is sensed to be idle (or a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA utilizing at least ED to determine the presence or absence of other signals on the channel to determine whether the channel is occupied or free. This LBT mechanism allows cellular / LAA networks to coexist with current occupied systems and with other LAA networks in unlicensed spectrum. The ED may include sensing RF energy over the intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.

[0080] Typically, the current occupying system in the 5 GHz band is WLAN based on IEEE 802.11 technology. WLAN adopts a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS), such as UE 822, AP 812, etc.) intends to transmit, the WLAN node may first perform CCA before transmitting. Furthermore, a back-off mechanism is used to avoid collisions in a situation where two or more WLAN nodes simultaneously sense the channel as idle and transmit. The back-off mechanism may be a randomly drawn counter in the CWS, which is exponentially increased upon occurrence of a collision and reset to a minimum value upon successful transmission. The LBT mechanism designed for LAA is somewhat similar to CSMA / CA in WLAN. In some implementations, the LBT procedure for DL ​​or UL transmission bursts including PDSCH or PUSCH transmissions, respectively, may have an LAA contention window with a variable length between X ECCA slots and Y ECCA slots, where X and Y are the minimum and maximum values ​​of the CWS for LAA. In one example, the minimum CWS for an LAA transmission may be 9 microseconds (μs), although the size of the CWS and MCOT (e.g., transmission burst) may be based on government regulatory requirements.

[0081] The LAA mechanism is built on the CA technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and can aggregate up to 5 CCs, so the maximum aggregated bandwidth is 100 MHz. In an FDD system, the number of aggregated carriers can be different for DL ​​and UL, and the number of UL CCs is equal to or less than the number of DL component carriers. In some cases, individual CCs can have different bandwidths from other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are usually the same for DL ​​and UL.

[0082] CA also includes individual serving cells providing individual CCs. For example, CCs in different frequency bands experience different path losses, so the coverage of serving cells may differ. A primary serving cell or PCell may provide a PCC for both UL and DL and may handle RRC and NAS related activities. Other serving cells are called SCells, and each SCell may provide a separate SCC for both UL and DL. While SCCs may be added and removed as needed, changing a PCC requires the UE 822 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in an unlicensed spectrum (called "LAA SCell"), and the LAA SCell is backed by a PCell operating in a licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within the same subframe.

[0083] The PDSCH carries user data and higher layer signaling to the UE 822 and the UE 820. The PDCCH carries, among other things, information regarding transport formats and resource allocations related to the PDSCH channel. It may also inform the UE 822 and the UE 820 about transmission formats, resource allocations, and HARQ information for the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to the UE 820 in the cell) may be performed in either the RAN node 814 or the RAN node 816 based on channel quality information fed back from either the UE 822 and the UE 820. The downlink resource allocation information may be transmitted in the PDCCH used (e.g., assigned) for the UE 822 and the UE 820, respectively.

[0084] The PDCCH conveys control information using CCEs. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets and then permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, and each CCE may correspond to nine sets of four physical resource elements known as REGs. Four quadrature phase shift keying (QPSK) symbols may be mapped to each REG. The PDCCH may be transmitted using one or more CCEs depending on the size of the DCI and the channel conditions. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0085] Some embodiments may use a concept for resource allocation for control channel information that is an extension of the concept above. For example, some embodiments may utilize an EPDCCH that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more ECCEs. As above, each ECCE may correspond to nine sets of four physical resource elements known as EREGs. An ECCE may have other numbers of EREGs in some situations.

[0086] The RAN node 814 or the RAN node 816 may be configured to communicate with each other via an interface 830. In an embodiment where the system 800 is an LTE system (e.g., where the CN 806 is the EPC), the interface 830 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes (e.g., two or more eNBs) that connect to the EPC and / or between two eNBs that connect to the EPC. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user data packets forwarded over the X2 interface and may be used to communicate information regarding delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information for user data forwarded from the MeNB to the SeNB, information regarding successful sequence delivery of PDCP PDUs from the SeNB to the UE 822 for user data, information regarding PDCP PDUs that were not delivered to the UE 822, information regarding the current minimum desired buffer size at the SeNB for transmitting UE user data, etc. X2-C may provide intra-LTE access mobility functions, load management functions, and inter-cell interference coordination functions, including context transfer from source eNB to target eNB, user plane transport control, etc.

[0087] In embodiments where the system 800 is an SG or NR system (e.g., where the CN 806 is an SGC), the interface 830 may be an Xn interface. An Xn interface is defined between two or more RAN nodes (e.g., two or more gNBs, etc.) that connect to an SGC, between a RAN node 814 (e.g., a gNB) and an eNB that connect to an SGC, and / or between two eNBs that connect to a 5GC (e.g., the CN 806). 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 transfer and flow control functions. The Xn-C may provide mobility support for the UE 822 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 RAN nodes 814 or RAN nodes 816. Mobility support may include context transfer from the old (source) serving RAN node 814 to the new (target) serving RAN node 816 and control of user plane tunnels between the old (source) serving RAN node 814 and the new (target) serving RAN node 816. To carry user plane PDUs, the protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer and a GTP-U layer on top of a UDP and / or IP layer(s). The Xn-C protocol stack may include an application layer signaling protocol (called Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP may be on top of the IP layer and may provide guaranteed delivery of application layer messages. At the transport IP layer, point-to-point transmission is used to deliver signaling PDUs.In other implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stack(s) shown and described herein.

[0088] The (R)AN 808 is shown communicatively coupled to a core network, in this embodiment the CN 806. The CN 806 may comprise one or more network elements 832 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 822 and UE 820) connected to the CN 806 via the (R)AN 808. The components of the CN 806 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be utilized to virtualize any or all of the network node functions described above via executable instructions stored in one or more computer-readable storage media (described in more detail below). A logical instantiation of the CN 806 may be referred to as a network slice, and a logical instantiation of a portion of the CN 806 may be referred to as a network sub-slice. The NFV architecture and infrastructure may be used to virtualize one or more network functions on physical resources including a combination of industry-standard server hardware, storage hardware, or switches, or may be performed by dedicated hardware. In other words, an NFV system may be used to execute a virtual or reconfigurable implementation of one or more EPC components / functions.

[0089] In general, the application server 818 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 818 may also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 822 and the UE 820 via the EPC. The application server 818 may communicate with the CN 806 via an IP communication interface 836.

[0090] In an embodiment, the CN 806 may be an SGC, and the (R)AN 116 may be connected to the CN 806 via an NG interface 834. In an embodiment, the NG interface 834 may be divided into two parts: an NG User Plane (NG-U) interface 826, which carries traffic data to and from the RAN node 814 or the RAN node 816, and an S1 Control Plane (NG-C) interface 828, which is a signaling interface between the RAN node 814 or the RAN node 816 and the AMF.

[0091] In an embodiment, the CN 806 may be an SG CN, and in other embodiments, the CN 806 may be an EPC. When the CN 806 is an EPC, the (R)AN 116 may be connected to the CN 806 via an S1 interface 834. In an embodiment, the S1 interface 834 may be divided into two parts: an S1 user plane (S1-U) interface 826 that carries traffic data between the RAN node 814 or RAN node 816 and the S-GW, and an S1-MME interface 828 that is a signaling interface between the RAN node 814 or RAN node 816 and the MME.

[0092] 9 illustrates an example of infrastructure equipment 900 in accordance with various embodiments. The infrastructure equipment 900 may be implemented as a base station, a radio head, a RAN node, an AN, an application server, and / or any other element / device described herein. In other examples, the infrastructure equipment 900 may be implemented in or by a UE.

[0093] The infrastructure equipment 900 includes application circuitry 902, baseband circuitry 904, one or more radio front-end modules 906 (RFEM), memory circuitry 908, power management integrated circuit (shown as PMIC 910), power T circuitry 912, network controller circuitry 914, network interface connector 920, satellite positioning circuitry 916, and user interface circuitry 918. In some embodiments, the device infrastructure equipment 900 may include additional elements, such as, for example, memory / storage, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, the components described below may be included in two or more devices. For example, the circuits may be included separately in two or more devices for CRAN, vBBU, or other similar implementations. The application circuitry 902 may include, but is not limited to, one or more processors (or processor cores), cache memory, as well as low dropout regulators (LDOs), interrupt controllers, SPI, I / O, and other similar implementations. 2The application circuitry 902 may include one or more of the following circuits: a serial interface, such as a universal programmable serial interface module (PLC), a real-time clock (RTC), timer counters including interval and watchdog timers, a general purpose input / output (I / O or IO), a memory card controller, such as a Secure Digital (SD) Multimedia Card (MMC), a universal serial bus (USB) interface, a mobile industry processor interface (MIPI) interface, and a Joint Test Access Group (JTAG) test access port. The processor (or core) of the application circuitry 902 may be coupled to or may include memory / storage elements and may be configured to execute instructions stored in the memory / storage elements to enable various applications or operating systems to run on the infrastructure equipment 900. In some implementations, the memory / storage elements may be on-chip memory circuits, which may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology as described herein.

[0094] The processor(s) of application circuitry 902 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, application circuitry 902 may include or be a special purpose processor / controller that operates in accordance with various embodiments herein. By way of example, the processor(s) of application circuitry 902 may include one or more Intel Pentium®, Core®, or Xeon® processor(s), Advanced Micro Devices (AMD) Ryzen® processor(s), Accelerated Processing Unit (APU), or Epyc® processor, ARM-based processor(s) licensed from ARM Holdings Ltd., such as the ARM Cortex-A family processors, and processors of MIPS-based designs offered by MIPS Technologies, Inc., such as ThunderX2® offered by Cavium™, Inc., MIPS Warrior P-class processors, etc. In some embodiments, infrastructure equipment 900 may not utilize application circuitry 902, and instead may include a dedicated processor / controller for processing IP data received, for example, from an EPC or 5GC.

[0095] In some implementations, the application circuitry 902 may include one or more hardware accelerators, which may be a microprocessor, a programmable processing device, or the like. The one or more hardware accelerators may include, for example, a computer vision (CV) and / or a deep learning (DL) accelerator. By way of example, the programmable processing device may be one or more of a field programmable device (FPD) such as a field programmable gate array (FPGA), a programmable logic device (PLD) such as a complex PLD (CPLD), a high capacity PLD (HCPLD), an ASIC such as a structured ASIC, a programmable SoC (PSoC), or the like. In such implementations, the circuitry of the application circuitry 902 may include logic blocks or logic fabrics and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions of various implementations described herein. In such an embodiment, the circuitry of the application circuitry 902 may include memory cells (e.g., erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc., in look-up tables (LUTs), etc. The baseband circuitry 904 may be implemented, for example, as a soldered board containing one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0096] User interface circuitry 918 may include one or more user interfaces designed to enable user interaction with infrastructure equipment 900 or peripheral component interfaces designed to enable peripheral component interaction with infrastructure equipment 900. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touch screen, a speaker or other audio emitting device, a microphone, a printer, a scanner, a headset, a display screen or device, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0097] The wireless front-end module 906 may include a millimeter-wave (mm-wave) radio front-end module (RFEM) and one or more sub-mm-wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mm-wave RFICs may be physically separate from the mm-wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both mm-wave and sub-mm-wave wireless functions may be implemented within the same physical wireless front-end module 906 that incorporates both mm-wave and sub-mm-wave antennas.

[0098] The memory circuitry 908 may include one or more of volatile memory including dynamic random access memory (DRAM) and / or synchronous dynamic random access memory (SDRAM), and non-volatile memory (NVM) including high speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), and the like, and may incorporate Intel® and Micron® three-dimensional (3D) cross point (XPOINT) memory. The memory circuitry 908 may be implemented as one or more of a solder packaged integrated circuit, a socketed memory module, and a plug-in memory card.

[0099] The PMIC 910 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or a capacitor. The power alarm detection circuit may detect one or more of brownout (under-voltage) and surge (over-voltage) conditions. The power T-circuit 912 may supply power drawn from a network cable that provides both power and data connectivity to the infrastructure equipment 900 using a single cable.

[0100] The network controller circuitry 914 may provide connectivity to a network using a standard network interface protocol, such as Ethernet, Ethernet over a GRE tunnel, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol. Network connectivity may be provided to / from the infrastructure equipment 900 via the network interface connectors 920 using a physical connection that may be electrical (commonly referred to as "copper wiring"), optical, or wireless. The network controller circuitry 914 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the network controller circuitry 914 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0101] The positioning circuitry 916 includes circuitry for receiving and decoding signals transmitted / broadcast by a positioning network of a Global Navigation Satellite System (GNSS). Examples of navigation satellite constellations (or GNSS) include the United States' Global Positioning System (GPS), the Russian Global Navigation System (GLONASS), the European Union's Galileo system, the Chinese BeiDou navigation satellite system, regional navigation systems or GNSS augmentation systems (e.g., Navigation by Indian Constellation (NAVIC), the Japanese Quasi-Zenith Satellite System (QZSS), the French Doppler Orbitography and Radio positioning Integrated by Satellite (DORIS), etc.). The positioning circuitry 916 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. to facilitate OTA communication) for communicating with components of the positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry 916 may include a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC for performing position tracking / estimation without GNSS assistance using a master timing clock. The positioning circuitry 916 may also be part of or interact with the baseband circuitry 904 and / or the radio front-end module 906 to communicate with nodes and components of a positioning network. The positioning circuitry 916 may also provide position and / or time data to the application circuitry 902, which may use the data to synchronize operations with various infrastructures, etc. The components shown in FIG. 9 may communicate with each other using interface circuitry, which may include any number of buses and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Enhanced ISA (EISA), Peripheral Component Interconnect (PCI), Enhanced Peripheral Component Interconnect (PCix), PCI Express (PCie), or any number of other technologies.The bus / IX may be, for example, a proprietary bus used in an SoC-based system. Other bus / IX systems, among others, include I. 2 C interface, SPI interface, point-to-point interface, power bus, etc. may be included.

[0102] FIG. 10 illustrates an exemplary platform 1000 according to various embodiments. In an embodiment, the computer platform 1000 may be suitable for use as a UE, an application server, and / or any other element / device described herein. The platform 1000 may include any combination of components shown in the examples. The components of the platform 1000 may be implemented as an integrated circuit (IC), a part thereof, a separate electronic device, or other module, logic, hardware, software, firmware, or a combination thereof adapted to the computer platform 1000, or as components integrated within the chassis of a larger system. The block diagram of FIG. 10 is intended to illustrate a high-level view of the components of the computer platform 1000. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0103] The application circuit 1002 may include, but is not limited to, one or more processors (or processor cores), cache memory, and one or more LDOs, interrupt controllers, SPIs, I 2The application circuitry 1002 may include circuits such as a serial interface such as a SPI, SPI-C, or universal programmable serial interface module, timer counters including RTC, interval and watchdog timers, general purpose IO, memory card controllers such as SD MMC, USB interface, MIPI interface, and JTAG test access port. The processor (or core) of the application circuitry 1002 may be coupled to or may include memory / storage elements and may be configured to execute instructions stored in the memory / storage elements to enable various applications or operating systems to run on the platform 1000. In some implementations, the memory / storage elements may be on-chip memory circuits, which may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid state memory, and / or any other type of memory device technology as described herein.

[0104] The processor(s) of application circuit 1002 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, application circuit 1002 may include or be a special purpose processor / controller that operates in accordance with various embodiments herein.

[0105] By way of example, the processor of the application circuit 1002 may include an Intel® Architecture Core™ based processor, such as a Quark™, ​​Atom™, i3, i5, i7, or MCU class processor, or another such processor available from Intel® Corporation. The processor of the application circuit 1002 may also be one or more of an Advanced Micro Devices (AMD) Ryzen® processor or an accelerated processing unit (APU). These may include one or more of the AS-A9 processor(s) from Apple® Inc., Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia Applications Platform (OMAP)™ processor(s), MIPS-based designs from MIPS Technologies, Inc. such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors, ARM-based designs licensed from ARM Holdings, Ltd, such as the ARM Cortex-A, Cortex-R, and Cortex-M families of processors, etc. In some implementations, the application circuit 1002 may be part of a system-on-chip (SoC) in which the application circuit 1002 and other components are formed on a single integrated circuit or package, such as the Edison™ or Galileo™ SoC boards from Intel® Corporation.

[0106] Additionally or alternatively, the application circuit 1002 may include circuitry such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, programmable logic devices (PLDs) such as composite PLDs (CPLDs) and high capacity PLDs (HCPLDs), ASICs such as structured ASICs, programmable SoCs (PSoCs), etc. In such embodiments, the circuitry of the application circuit 1002 may include logic blocks or logic fabrics and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, and functions of various embodiments described herein. In such embodiments, the circuitry of the application circuit 1002 may include memory cells (e.g., erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.) used to store logic blocks, logic fabric, data, etc., in look-up tables (LUTs), etc.

[0107] The baseband circuitry 1004 may be implemented, for example, as a soldered board containing one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0108] The wireless front-end module 1006 may include a millimeter-wave (mm-wave) radio front-end module (RFEM) and one or more sub-mm-wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mm-wave RFICs may be physically separate from the mm-wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both mm-wave and sub-mm-wave wireless functions may be implemented within the same physical wireless front-end module 1006 that incorporates both mm-wave and sub-mm-wave antennas.

[0109] The memory circuit 1008 may include any number and type of memory devices used to provide a given amount of system memory. By way of example, the memory circuit 1008 may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (SD RAM), and non-volatile memory (NVM) including high speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 1008 may be developed according to the Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR) based designs, such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 1008 may be implemented as one or more of a solder package integrated circuit, a single die package (SDP), a dual die package (DDP) or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or a mini DIMM, and / or soldered onto a motherboard via a ball grid array (BGA). In a low power implementation, the memory circuit 1008 may be an on-die memory or register associated with the application circuit 1002. To provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 1008 may include one or more mass storage devices, which may include a solid state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive memory, a phase change memory, a holographic memory, or a chemical memory, among others. For example, the computer platform 1000 may incorporate a three-dimensional (3D) cross point (XPOINT) memory from Intel® and Micron®.

[0110] Removable memory 1026 may include devices, circuits, enclosures, ports or receptacles, etc. used to couple portable data storage devices with platform 1000. These portable data storage devices may be used for mass storage purposes and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD image cards, etc.), USB flash drives, optical disks, external HDDs, etc.

[0111] The platform 1000 may also include interface circuitry (not shown) used to connect external devices with the platform 1000. External devices connected to the platform 1000 via the interface circuitry include sensors 1022 and electromechanical components (shown as EMC 1024), as well as a removable memory device coupled to a removable memory 1026.

[0112] The sensors 1022 may include devices, modules, or subsystems intended to detect events or changes in the environment and transmit information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others, inertial measurement units (IMUs) including accelerometers, gyroscopes, and / or magnetometers, Microelectromechanical Systems (MEMS) or Nanoelectromechanical Systems (NEMS) including 3-axis accelerometers, 3-axis gyroscopes, and / or magnetometers, level sensors, flow sensors, temperature sensors (e.g., thermistors), pressure sensors, barometric pressure sensors, gravimeters, altimeters, image capture devices (e.g., cameras or lensless apertures), Light Detection and Ranging (LiDAR) sensors, proximity sensors (e.g., infrared detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers, microphones or other similar audio capture devices, etc.

[0113] The EMC 1024 includes devices, modules, or subsystems whose purpose is to enable the platform 1000 to change its state, position, and / or orientation, or to move or control a mechanism or (sub)system. Additionally, the EMC 1024 may be configured to generate and send messages / signaling to other components of the platform 1000 to indicate the current state of the EMC 1024. Examples of the EMC 1024 include one or more power switches, relays including electromechanical relays (EMRs) and / or solid-state relays (SSRs), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and / or other similar electromechanical components. In an embodiment, the platform 1000 is configured to operate one or more EMCs 1024 based on one or more captured events and / or commands or control signals received from a service provider and / or various clients. In some implementations, the interface circuit may connect the platform 1000 with the positioning circuit 1016. The positioning circuit 1016 includes circuitry for receiving and decoding signals transmitted / broadcast by a GNSS positioning network. Examples of navigation satellite constellations (or GNSS) include the United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's Beidou navigation satellite system, regional navigation systems or GNSS augmentation systems (e.g., NAVIC, Japan's QZSS, France's DORIS, etc.), etc. The positioning circuit 1016 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. to facilitate OTA communications) for communicating with components of the positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 1016 may include a Micro-PNT IC for performing position tracking / estimation without GNSS assistance using a master timing clock.The positioning circuitry 1016 may also be part of or interact with the baseband circuitry 1004 and / or the wireless front-end module 1006 to communicate with nodes and components of a positioning network. The positioning circuitry 1016 may also provide position and / or time data to the application circuitry 1002, which may use the data to synchronize operation with various infrastructures (e.g., wireless base stations), such as for turn-by-turn navigation applications.

[0114] In some implementations, the interface circuit may connect the platform 1000 with a near-field communication circuit (shown as NFC circuit 1012). The NFC circuit 1012 is configured to provide contactless short-range communication based on the Radio Frequency Identification (RFID) standard, where magnetic field induction is used to enable communication between the NFC circuit 1012 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 1000. The NFC circuit 1012 comprises an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides the NFC circuit 1012 with NFC functionality by executing an NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit a short-range RF signal. The RF signal can power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry 1012, or initiate data transmission between the NFC circuitry 1012 in proximity to the platform 1000 and another active NFC device (e.g., a smartphone or NFC-enabled POS terminal).

[0115] The driver circuitry 1018 may include software and hardware elements that operate to control specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 1000. The driver circuitry 1018 may include individual drivers that enable other components of the platform 1000 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 1000. For example, the driver circuitry 1018 may include a display driver for controlling and allowing access to a display device, a touchscreen driver for controlling and allowing access to a touchscreen interface of the platform 1000, a sensor driver for obtaining sensor readings of the sensor 1022 and controlling and allowing access to the sensor 1022, an EMC driver for obtaining actuator positions of the EMC 1024 and / or controlling and allowing access to the EMC 1024, a camera driver for controlling and allowing access to an embedded capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0116] A power management integrated circuit (shown as PMIC 1010) (also referred to as a "power management circuit") may manage the power supplied to various components of platform 1000. In particular, with respect to baseband circuitry 1004, PMIC 1010 may control power source selection, voltage scaling, battery charging, or DC-DC conversion. PMIC 1010 may often be included when platform 1000 can be powered by a battery 1014, for example, when this device is included in a UE.

[0117] In some embodiments, the PMIC 1010 may control or otherwise be part of various power saving mechanisms of the platform 1000. For example, if the platform 1000 is in an RRC connected state and is still connected to a RAN node because it expects to receive traffic shortly, after some period of inactivity the platform may enter a state known as discontinuous reception mode (DRX). During this state, the platform 1000 may power down for a short period of time, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 1000 may transition to an RRC idle state, disconnecting from the network and not performing operations such as channel quality feedback, handovers, etc. The platform 1000 may enter a very low power state, perform paging, where it will again periodically wake up to listen to the network, and then power down again. The platform 1000 cannot receive data in this state, and must transition to the RRC connected state to receive data. In further power saving modes, the device may be allowed to be unavailable from the network for longer than the paging interval (which may range from a few seconds to a few hours). During this time the device may not be able to reach the network at all and may be powered down completely. Any data sent during this time will be significantly delayed, but the delay is deemed acceptable.

[0118] The battery 1014 may power the platform 1000, although in some examples the platform 1000 may be deployed and mounted at a fixed location and may have a power source coupled to a power grid. The battery 1014 may be a lithium ion battery, a metal air battery such as a zinc air battery, an aluminum air battery, a lithium air battery, etc. In some implementations, such as for V2X applications, the battery 1014 may be a typical lead acid automobile battery.

[0119] In some implementations, the battery 1014 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or battery monitoring integrated circuit. The BMS may be included in the platform 1000 to track the state of charge (SoCh) of the battery 1014. The BMS may be used to monitor other parameters of the battery 1014 to provide fault predictions, such as the state of health (SoH) and state of function (SoF) of the battery 1014. The BMS may communicate information about the battery 1014 to the application circuit 1002 or other components of the platform 1000. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 1002 to directly monitor the voltage of the battery 1014 or the current from the battery 1014. The battery parameters may be used to determine operations that the platform 1000 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0120] A power block, or other power source coupled to an electrical grid, may be coupled to the BMS to charge the battery 1014. In some embodiments, the power block may be replaced with a wireless power receiver to obtain power wirelessly, for example, via a loop antenna in the computer platform 1000. In these examples, wireless battery charging circuitry may be included in the BMS. The particular charging circuitry selected may depend on the size of the battery 1014 and thus the current required. Charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power Consortium, or the Rezence charging standard promulgated by the Alliance for Wireless Power, among others.

[0121] User interface circuitry 1020 includes various input / output (I / O) devices present in or connected to platform 1000 and may include one or more user interfaces designed to enable user interaction with platform 1000 and / or peripheral component interfaces designed to enable peripheral component interaction with platform 1000. User interface circuitry 1020 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input including, among others, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying or otherwise communicating information, such as a sensor reading, an actuator position(s), or other similar information. The output device circuitry may include any number and / or combination of audio or visual displays, among others, one or more simple visual outputs / indicators, such as binary status indicators (e.g., light emitting diodes (LEDs)), and multi-character visual outputs or more complex outputs, such as a display device or touch screen (e.g., liquid crystal display (LCD), LED display, quantum dot display, projector, etc.), which may output characters, graphics, multimedia objects, etc., generated or created from operation of the platform 1000. The output device circuitry may also include a speaker or other audio emitting device, printer(s), and / or the like. In some embodiments, the sensor 1022 may be used as an input device circuitry (e.g., an image capture device, a motion capture device, etc.), and one or more EMCs may be used as output device circuitry (e.g., an actuator for providing tactile feedback, etc.). In another example, an NFC circuitry comprising an NFC controller coupled to an antenna element and a processing device may be included for reading an electronic tag and / or connecting with another NFC-enabled device.Peripheral component interfaces include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power interface, and the like.

[0122] Although not shown, the components of platform 1000 may communicate with each other using any suitable bus or interconnect (IX) technology, which may include any number of technologies including ISA, EISA, PCI, PCIx, PCIe, Time Triggered Protocol (TTP) systems, FlexRay systems, or any number of other technologies. The bus / IX may be, for example, a proprietary bus / IX used in SoC-based systems. Other bus / IX systems, including, among others, the I 2 C interface, SPI interface, point-to-point interface, and power bus, etc. may be included.

[0123] 11 is a block diagram illustrating a component 1100 that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methods discussed herein, according to some embodiments. Specifically, FIG. 11 illustrates a diagrammatic representation of hardware resources 1102, including one or more processors 1106 (or processor cores), one or more memory / storage devices 1114, and one or more communication resources 1124, each of which may be communicatively coupled via a bus 1116. In embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1122 may execute to provide an execution environment for one or more network slices / sub-slices that utilize the hardware resources 1102.

[0124] Processor 1106 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1108 and processor 1110.

[0125] The memory / storage 1114 may include main memory, disk storage, or any suitable combination thereof. The memory / storage 1114 may include any type of volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0126] Communications resources 1124 may include interconnect or network interface components or other suitable devices for communicating with one or more peripherals 1104 or one or more databases 1120 over network 1118. For example, communications resources 1124 may include a wired communications component (e.g., for coupling via a Universal Serial Bus (USB)), a cellular communications component, an NFC component, a Bluetooth® component (e.g., Bluetooth® Low Energy), a Wi-Fi® component, and other communications components.

[0127] The instructions 1112 may include software, programs, applications, applets, apps, or other executable code to cause at least one of the processors 1106 to perform any one or more of the methodologies discussed herein. The instructions 1112 may reside, completely or partially, in at least one of the processors 1106 (e.g., in a cache memory of the processor), the memory / storage 1114, or any suitable combination thereof. Additionally, any portion of the instructions 1112 may be transferred to the hardware resources 1102 from any combination of the peripherals 1104 or the database 1120. Thus, the memory of the processor 1106, the memory / storage 1114, the peripherals 1104, and the database 1120 are examples of computer-readable and machine-readable media.

[0128] 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.

[0129] Example Section

[0130] The following examples relate to further embodiments.

[0131] Example 1 may include a method for determining a physical uplink control channel (PUCCH) transmission repetition. The method may include the steps of determining that an original PUCCH transmission overlaps a slot boundary, the slot boundary being a boundary between a first slot for the PUCCH transmission and a second slot for the PUCCH transmission, and configuring a PUCCH repetition of the original PUCCH transmission, the PUCCH repetition including one or more symbols of the original PUCCH transmission and located in one or more slots other than the first slot and the second slot, the PUCCH repetition being configured by a downlink control information (DCI) configuration including a physical downlink shared channel-hybrid automatic repeat request acknowledgement feedback (PDSCH-to-HARQ_feedback) timing indicator, a PUCCH repetition number field configuring the number of transmissions of the PUCCH repetition, or a PUCCH resource indicator field configuring the number of transmissions of the PUCCH repetition. The method may further include transmitting the PUCCH repetition.

[0132] Example 2 may include the method of example 1, wherein the DCI configuration includes a PDSCH-to-HARQ_feedback timing indicator, and the PDSCH-to-HARQ_feedback timing indicator is configured by a radio resource control (RRC) to configure a number of PUCCH repetition transmissions, the number of PUCCH repetition transmissions being a value in the range of 1 to N, and N being greater than 8.

[0133] Example 3 may include the method of example 1, in which the DCI configuration includes a PUCCH repetition number field, where the value of the PUCCH repetition number field is a number of transmissions of the PUCCH repetition, ranging from 1 to N, where N is greater than 8.

[0134] Example 4 may include the method of example 1, in which the DCI configuration includes a PUCCH resource indicator field, and a value of the PUCCH resource indicator field is a number of transmissions of the PUCCH repetitions, ranging from 1 to N, where N is greater than 8.

[0135] Example 5 may include the method of example 1, in which the PUCCH repetition is limited to PUCCH format 1, PUCCH format 3, or PUCCH format 4.

[0136] Example 6 may include the method of example 1, in which the PUCCH repetition includes all symbols of the original PUCCH transmission.

[0137] Example 7 may include the method of example 1, in which the PUCCH repetition is a shortened version of the original PUCCH transmission that does not include any symbols of the original PUCCH transmission that overlap with a slot boundary.

[0138] Example 8 may include the method of Example 1, in which the PUCCH repetition is a segmented version of the original PUCCH transmission formed by a first repeat PUCCH segment including all symbols of the original PUCCH transmission located in a first slot and a second repeat PUCCH segment including all symbols of the original PUCCH transmission located in a second slot.

[0139] Example 9 may include the method of Example 1, in which the PUCCH repetition is a first PUCCH repetition that satisfies a minimum HARQ-ACK processing time associated with the PDSCH.

[0140] Example 10 may include the method of Example 1, wherein the PUCCH repetition satisfies a minimum HARQ-ACK processing time associated with the PDSCH, and the user equipment (UE) is configured to transmit the PUCCH repetition and not transmit one or more other PUCCH repetitions that do not satisfy the minimum HARQ-ACK processing time associated with the PDSCH.

[0141] Example 11 may include the method of example 1, in which the PUCCH repetition is one of a plurality of PUCCH repetitions that are consecutively scheduled and overlap one or more slot boundaries.

[0142] Example 12 may include the method of example 1, in which the PUCCH repetition is one of a plurality of PUCCH repetitions scheduled in consecutive slots and not overlapping any slot boundary.

[0143] Example 13 may include the method of example 12, wherein the multiple PUCCH repetitions use the same time domain allocation in each of the consecutive slots.

[0144] Example 14 may include the method of example 1, in which the original PUCCH transmission includes a downlink (DL) symbol.

[0145] Example 15 may include the method of Example 14, in which the PUCCH repetition is a shortened version of the original PUCCH transmission that does not include any symbols of the original PUCCH transmission that are located after the DL symbol.

[0146] Example 16 may include the method of Example 14, wherein the PUCCH repetition is a segmented version of the original PUCCH formed by a first repeated PUCCH segment including all symbols of the original PUCCH transmission located before the DL symbol and a second repeated PUCCH segment including all symbols of the original PUCCH transmission located after the DL symbol.

[0147] Example 17 may include the method of example 1, further including reporting a maximum number of PUCCH repetitions that the user equipment is configured to transmit in the slot.

[0148] Example 18 may include a non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that, when executed by a processor, cause the processor to determine that an original physical uplink control channel (PUCCH) transmission overlaps with a slot boundary, the slot boundary being a boundary between a first slot for the PUCCH transmission and a second slot for the PUCCH transmission, and configure a PUCCH repetition of the original PUCCH transmission, the PUCCH repetition including one or more symbols of the original PUCCH transmission and located in one or more slots other than the first slot and the second slot, the PUCCH repetition being configured by a downlink control information (DCI) configuration including a physical downlink shared channel-hybrid automatic repeat request acknowledgement feedback (PDSCH-to-HARQ_feedback) timing indicator, a PUCCH repetition number field configuring the number of transmissions of the PUCCH repetition, or a PUCCH resource indicator field configuring the number of transmissions of the PUCCH repetition. The instructions, when executed by the processor, may cause the processor to transmit the PUCCH repetition.

[0149] Example 19 may include the non-transitory computer-readable storage medium of Example 18, in which the PUCCH repetition is a shortened version of the original PUCCH transmission that does not include any symbols of the original PUCCH transmission that overlap a slot boundary.

[0150] Example 20 may include a computing device for determining a physical uplink control channel (PUCCH) transmission repetition. The computing device may include a processor and a memory storing instructions, which when executed by the processor, cause the device to determine that an original PUCCH transmission overlaps with a slot boundary, the slot boundary being a boundary between a first slot for the PUCCH transmission and a second slot for the PUCCH transmission, and configure a PUCCH repetition of the original PUCCH transmission, the PUCCH repetition including one or more symbols of the original PUCCH transmission, located in one or more slots other than the first slot and the second slot, the PUCCH repetition being configured by a downlink control information (DCI) configuration including a physical downlink shared channel-hybrid automatic repeat request acknowledgement feedback (PDSCH-to-HARQ_feedback) timing indicator, a PUCCH repetition number field configuring the number of transmissions of the PUCCH repetition, or a PUCCH resource indicator field configuring the number of transmissions of the PUCCH repetition. The instructions, when executed by the processor, may further configure the device to transmit the PUCCH repetition.

[0151] Example 21 may include the computing device of Example 20, wherein the PUCCH repetition is a shortened version of the original PUCCH transmission that does not include any symbols of the original PUCCH transmission that overlap a slot boundary.

[0152] Example 22 may include an apparatus including means for performing one or more elements of a method described or related to any of the above examples, or any other method or process described herein.

[0153] Example 23 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.

[0154] Example 24 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.

[0155] Example 25 may include any method, technique, or process described or related to any of the above examples or any portion or part thereof.

[0156] Example 26 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 preceding examples or portions thereof.

[0157] Example 27 may include a signal as described or related to any of the above examples or any portion or part thereof.

[0158] Example 28 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.

[0159] Example 29 can 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.

[0160] Example 30 may include a signal encoded using a datagram, packet, frame, segment, PDU, or message described or associated with any of the above examples or any portion or part thereof, or described in the present disclosure.

[0161] Example 31 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.

[0162] Example 32 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.

[0163] Example 33 may include signals in a wireless network as shown and described herein.

[0164] Example 34 may include a method of communicating in a wireless network as shown and described herein.

[0165] Example 35 may include a system for providing wireless communication as shown and described herein.

[0166] Example 36 may include a device for providing wireless communication as shown and described herein.

[0167] 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.

[0168] 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.

[0169] 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.

[0170] It is well understood that use of personal information should comply with privacy policies and practices generally recognized as meeting or exceeding industry or governmental requirements for maintaining user privacy. In particular, personal information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of permitted uses should be clearly indicated to users.

[0171] 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 determining a physical uplink control channel (PUCCH) transmission repetition, comprising: determining that an original PUCCH transmission overlaps a slot boundary, the slot boundary being a boundary between a first slot for PUCCH transmission and a second slot for PUCCH transmission; configuring a PUCCH repetition of the original PUCCH transmission, the PUCCH repetition comprising one or more symbols of the original PUCCH transmission and located in one or more slots other than the first slot and the second slot, the PUCCH repetition being configured by a Downlink Control Information (DCI) configuration including a Physical Downlink Shared Channel - Hybrid Automatic Repeat Request Acknowledgement Feedback (PDSCH-to-HARQ_Feedback) timing indicator and a Number of PUCCH Repetitions field configuring the number of transmissions of the PUCCH repetition or a PUCCH resource indicator field configuring the number of transmissions of the PUCCH repetition; and transmitting the PUCCH signal.

2. 2. The method of claim 1, wherein the DCI configuration includes the PDSCH-to-HARQ feedback timing indicator, the PDSCH-to-HARQ feedback timing indicator being configured by a radio resource control (RRC) to configure a number of transmissions of the PUCCH repetitions, the number of transmissions being a value in the range of 1 to N, where N is greater than 8.

3. The method of claim 1 , wherein the DCI configuration includes a Number of PUCCH Repetitions field, the value of the Number of PUCCH Repetitions field being a number of transmissions of the PUCCH repetitions and ranging from 1 to N, where N is greater than 8.

4. The method of claim 1 , wherein the DCI configuration includes the PUCCH resource indicator field, the value of the PUCCH resource indicator field being a number of transmissions of the PUCCH repetitions and ranging from 1 to N, where N is greater than 8.

5. The method of claim 1 , wherein the PUCCH repetition is restricted to PUCCH format 1, PUCCH format 3, or PUCCH format 4.

6. The method of claim 1 , wherein the PUCCH repetition includes all symbols of the original PUCCH transmission.

7. 2. The method of claim 1, wherein the PUCCH repetition is a shortened version of the original PUCCH transmission that does not include any symbols of the original PUCCH transmission that overlap with the slot boundary.

8. 2. The method of claim 1, wherein the PUCCH repetition is a segmented version of the original PUCCH transmission formed by a first repeat PUCCH segment including all symbols of the original PUCCH transmission located in the first slot and a second repeat PUCCH segment including all symbols of the original PUCCH transmission located in the second slot.

9. The method of claim 1 , wherein the PUCCH repetition is a first PUCCH repetition that satisfies a minimum HARQ-ACK processing time associated with a PDSCH.

10. 2. The method of claim 1, wherein the PUCCH repetition satisfies a minimum HARQ-ACK processing time associated with a PDSCH, and a user equipment (UE) is configured to transmit the PUCCH repetition and not transmit one or more other PUCCH repetitions that do not satisfy the minimum HARQ-ACK processing time associated with the PDSCH.

11. 2. The method of claim 1, wherein the PUCCH repetition is one of a plurality of PUCCH repetitions that are scheduled contiguously and overlap one or more slot boundaries.

12. 2. The method of claim 1, wherein the PUCCH repetition is one of a number of PUCCH repetitions scheduled in consecutive slots and not overlapping any slot boundary.

13. The method of claim 12 , wherein the multiple PUCCH repetitions use the same time domain allocation in each of the consecutive slots.

14. The method of claim 1 , wherein the original PUCCH transmission comprises a downlink (DL) symbol.

15. 15. The method of claim 14, wherein the PUCCH repetition is a shortened version of the original PUCCH transmission that does not include any symbols of the original PUCCH transmission that are located after the DL symbol.

16. 15. The method of claim 14, wherein the PUCCH repetition is a segmented version of the original PUCCH formed by a first repeated PUCCH segment including all symbols of the original PUCCH transmission located before the DL symbol and a second repeated PUCCH segment including all symbols of the original PUCCH transmission located after the DL symbol.

17. reporting a maximum number of PUCCH repetitions that the user equipment is configured to transmit in a slot; The method of claim 1 further comprising:

18. A non-transitory computer-readable storage medium that, when executed by a processor, causes the processor to: determining that an original physical uplink control channel (PUCCH) transmission overlaps with a slot boundary, the slot boundary being a boundary between a first slot for the PUCCH transmission and a second slot for the PUCCH transmission; configuring a PUCCH repetition of the original PUCCH transmission, the PUCCH repetition including one or more symbols of the original PUCCH transmission and located in one or more slots other than the first slot and the second slot, the PUCCH repetition being configured by a Downlink Control Information (DCI) configuration including a Physical Downlink Shared Channel - Hybrid Automatic Repeat Request Acknowledgement Feedback (PDSCH-to-HARQ_Feedback) timing indicator and a PUCCH repetition number field configuring a number of transmissions of the PUCCH repetition or a PUCCH resource indicator field configuring the number of transmissions of the PUCCH repetition; A non-transitory computer-readable storage medium comprising instructions for causing the PUCCH repetitions to be transmitted.

19. 20. The non-transitory computer-readable storage medium of claim 18, wherein the PUCCH repetition is a shortened version of the original PUCCH transmission that does not include any symbols of the original PUCCH transmission that overlap the slot boundary.

20. 1. A computing device for determining a physical uplink control channel (PUCCH) transmission repetition, comprising: A processor; A memory storing instructions that, when executed by the processor, cause the device to: determining that the original PUCCH transmission overlaps with a slot boundary, the slot boundary being a boundary between a first slot for the PUCCH transmission and a second slot for the PUCCH transmission; configuring a PUCCH repetition of the original PUCCH transmission, the PUCCH repetition including one or more symbols of the original PUCCH transmission and located in one or more slots other than the first slot and the second slot, the PUCCH repetition being configured by a Downlink Control Information (DCI) configuration including a Physical Downlink Shared Channel - Hybrid Automatic Repeat Request Acknowledgement Feedback (PDSCH-to-HARQ_Feedback) timing indicator and a PUCCH repetition number field configuring a number of transmissions of the PUCCH repetition or a PUCCH resource indicator field configuring the number of transmissions of the PUCCH repetition; and a memory for causing the PUCCH repetitions to be transmitted.

21. 21. The computing device of claim 20, wherein the PUCCH repetition is a shortened version of the original PUCCH transmission that does not include any symbols of the original PUCCH transmission that overlap the slot boundary.

22. 1. An apparatus for determining a physical uplink control channel (PUCCH) transmission repetition, comprising: Apparatus comprising means for carrying out the method according to any one of claims 1 to 17.

Citation Information

Patent Citations

  • Transmission channel configuration method and apparatus, transmission channel sending method and apparatus, device and storage medium

    US20220408420A1

  • Physical uplink control channel repetition

    WO2020010006A1

  • User terminal

    WO2020017059A1