Multiplexing of configured licensed transmissions in new air interface systems operating in unlicensed spectrum

Multiplexing and discarding rules for CG PUSCH in NR-U systems address overlapping issues with PUCCH, enhancing flexibility and performance by optimizing UCI handling and resource utilization in unlicensed spectrum.

CN114026813BActive Publication Date: 2024-12-03APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080046302.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-07-01
Filing Date
2020-07-01
Publication Date
2024-12-03
Estimated Expiration
2040-07-01

AI Technical Summary

Technical Problem

The challenge of operating wireless devices in unlicensed spectrum is ensuring fair coexistence with other technologies and addressing performance degradation due to contention-based channel access, particularly in configured grant (CG) PUSCH transmissions that may overlap with uplink control information (UCI) in NR-U systems.

Method used

Implement multiplexing and discarding rules for CG PUSCH when it overlaps with PUCCH, including 'always reuse', 'only discard', and 'discard or reuse based on available resources' strategies, with specific priority rules and encoding methods for UCI transmission.

Benefits of technology

Enhances flexibility and performance of CG PUSCH transmissions by optimizing UCI handling, ensuring efficient resource utilization and reducing transmission delays in unlicensed spectrum environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114026813B_ABST
    Figure CN114026813B_ABST
Patent Text Reader

Abstract

The present application relates to wireless devices, and more particularly to apparatus, systems and methods for multiplexing configured grant (CG) transmissions in a new air interface (NR) system operating on an unlicensed spectrum. In some embodiments, uplink control information may be transmitted in one or more configured grant physical uplink shared channels mapped to corresponding one or more mini-slots.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Related Applications

[0002] This application claims priority to U.S. Provisional Application No. 62 / 869,258, entitled “DESIGN OF MULTIPLEXING RULES FOR CONFIGURED GRANT TRANSMISSIONS IN NR SYSTEMS OPERATING ON UNLICENSEDSPECTRUM,” filed on July 1, 2019. The disclosure of said application is hereby incorporated by reference in its entirety. Technical Field

[0003] The present application relates to wireless communication systems, and more particularly to apparatus, systems and methods for multiplexing configuration grant transmissions in a new air interface system operating on an unlicensed spectrum. Background Art

[0004] Every year, the number of mobile devices connected to wireless networks increases significantly. In order to meet the demand for mobile data traffic, system requirements must change to be able to meet these demands. Three areas that can be enhanced to achieve this traffic increase are greater bandwidth, lower latency, and higher data rates.

[0005] One of the limiting factors in wireless innovation is the availability of spectrum. To alleviate this, unlicensed spectrum has been an area of ​​interest to extend the availability of Long Term Evolution (LTE). In this context, one of the major enhancements to LTE in the 3rd Generation Partnership Project (3GPP) Release 13 has been to enable it to operate in unlicensed spectrum via Licensed Assisted Access (LAA), which extends the system bandwidth by leveraging the flexible carrier aggregation (CA) framework introduced by the Advanced LTE system. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] A better understanding of the present subject matter may be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings.

[0007] Figure 1 A time slot structure according to some embodiments is shown.

[0008] Figure 2 shows a multi-slot structure according to some embodiments;

[0009] Figure 3 An operational flow / algorithm structure according to some embodiments is shown.

[0010] Figure 4 An operational flow / algorithm structure according to some embodiments is shown.

[0011] Figure 5 An operational flow / algorithm structure according to some embodiments is shown.

[0012] Figure 6 An exemplary architecture of a system according to some embodiments is shown.

[0013] Figure 7 An example of a platform (or "device") according to some embodiments is shown.

[0014] Figure 8 Exemplary components of a baseband circuit and a radio front end module are shown according to some embodiments.

[0015] Fig. 9 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium and capable of performing any one or more of the methodologies discussed herein, according to some embodiments.

[0016] Although the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and described in detail herein. However, it should be understood that the drawings and detailed description thereof are not intended to limit this document to the specific forms disclosed, but on the contrary, the purpose is to cover all modifications, equivalents and alternatives that fall within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0017] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of illustration and not limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments may be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so that the description of various embodiments will not be obscured by unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0018] The following is a glossary of terms that may be used in this disclosure:

[0019] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or a memory (shared, dedicated, or group) configured to provide the described functions, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), a digital signal processor (DSP), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0020] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, and / or transmitting digital data. The term "processor circuit" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes). The terms "application circuit" and / or "baseband circuit" may be considered synonymous with "processor circuit" and may be referred to as "processor circuit".

[0021] As used herein, the term "interface circuit" refers to a circuit that enables, is a part of, or includes information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0022] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0023] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN equipment, RAN node, gateway, server, virtualized VNF, NFVI, etc.

[0024] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to one another and configured to share computing and / or networking resources.

[0025] As used herein, the terms "appliance", "computer appliance", etc. refer to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image to be implemented by a device equipped with a hypervisor that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.

[0026] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time and / or a processor / CPU usage rate, a processor and accelerator load, a hardware time or usage rate, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage rate, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computing, storage and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage and / or network resources provided by a virtualized infrastructure to an application, a device, a system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources and / or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0027] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous and / or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" and / or any other similar terms representing a path or medium through which data is transmitted. In addition, the term "link" as used herein refers to a connection between two devices for transmitting and receiving information over a RAT.

[0028] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0029] The terms "coupled," "communicatively coupled," and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements said to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other by means of communication, including through a wire or other interconnect connection, through a wireless communication channel or link, etc.

[0030] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents.

[0031] 3GPP fifth generation (5G) new radio (NR) systems may improve LTE and LTE-A operations on unlicensed spectrum. Purpose for utilizing shared / unlicensed spectrum in 5G NR may include physical layer aspects handled by Radio Access Network (RAN) Working Group 1 (WG1), and physical layer procedures handled by RAN WG1 and RAN Working Group 2 (WG2).

[0032] Physical layer aspects may include a frame structure including single and multiple downlink (DL) to uplink (UL) and UL to DL switching points within a shared channel occupation time (COT) with associated identified listen-before-talk (LBT) requirements. See, e.g., Technical Report (TR) 38.889, v16.0.0 (2018-12-19), Section 7.2.1.3.1. Physical layer aspects may also include: a UL data channel including an extension of a physical uplink shared channel (PUSCH) to support frequency block interleaved transmission based on physical resource blocks (PRBs); it should be understood that the end position is indicated by a UL grant, supporting multiple PUSCH start positions in one or more time slots based on the LBT results; a design that does not require the user equipment (UE) to change the granted transport block size (TBS) for PUSCH transmission based on the LBT results. Various PUSCH enhancements based on cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) may also be considered. The applicability of sub-PRB frequency block interleaved transmission to 60 kHz may be determined by RAN WG1.

[0033] The physical layer procedures may include: a channel access mechanism for load-based equipment (LBE) in accordance with the protocol from the NR unlicensed spectrum (NR-U) study project (see, e.g., TR 38.889, Section 7.2.1.3.1). The physical layer procedures may also include a hybrid automatic repeat request (HARQ) operation concept. For example, the NR HARQ feedback mechanism may be a baseline for NR-U operation with extensions in accordance with the protocol during the study phase (see, e.g., TR 38.889, Section 7.2.1.3.3), including the immediate transmission of HARQ acknowledgment / negative acknowledgment (A / N) for corresponding data in the same shared COT and the transmission of HARQ A / N in a subsequent COT. Support mechanisms for providing multiple supplementary time domain and / or frequency domain transmission opportunities may be possible. The physical layer procedures may also include aspects related to scheduling multiple transmission time intervals (TTIs) of PUSCH in accordance with the protocol during the study phase (see, e.g., TR 38.889, Section 7.2.1.3.3). The physical layer procedures may also include aspects related to configured grant operation. For example, the NR Type 1 and Type 2 configured grant mechanisms may be a baseline for NR-U operation with modifications consistent with the protocol during the study phase (see, e.g., TR 38.889, Section 7.2.1.3.4). Further, the physical layer procedures may include data multiplexing aspects (for both UL and DL) that take into account LBT and channel access priority.

[0034] One of the challenges of operating devices in unlicensed spectrum is to ensure fair coexistence with other existing technologies. To do so, some restrictions may be considered when designing the NR-U system, depending on the specific frequency band in which the device operates. For example, if operating in the 5 gigahertz (GHz) band, the device may perform an LBT process to acquire the medium before transmission can occur.

[0035] The NR-U system can be designed to allow configured authorized (CG) operation on unlicensed spectrum. In CG operation, the UE can be allowed to transmit uplink communications, such as PUSCH, without having to receive individual resource allocations on the PDCCH. However, in some cases, the CG PUSCH may overlap with other UL transmissions. Some embodiments of the present disclosure address the situation where the CG PUSCH overlaps with the PUCCH. For example, various embodiments describe the multiplexing or discarding rules applied when the CG PUSCH overlaps with the authorized uplink control information (UCI) based on the authorization. Authorization-based UL control information (also referred to as "scheduled UCI") may include, but is not limited to, HARQ-ACK, scheduling requests (SRs), and channel state information (CSI).

[0036] Configured authorized transmissions operating on unlicensed spectrum

[0037] When operating on unlicensed spectrum that requires a contention-based protocol (e.g., LBT) to access the channel, the performance of scheduled UL transmissions may be degraded compared to operating on licensed spectrum due to "four-way" contention for UEs to access the UL. As an example, before a UE can perform an UL transmission, the system may be subject to the following operations: 1) the UE sends a scheduling request (SR); 2) LBT is performed at the gNB before sending an UL grant (particularly in the case of self-carrier scheduling); 3) UE scheduling (internal contention between UEs associated with the same gNB); and 4) LBT is performed only by scheduled UEs. In addition, the four time slots that may be required to handle the delay between the UL grant and the PUSCH transmission represent an additional performance constraint.

[0038] To help overcome these issues, devices in the NR-U system can use CG operation to perform unlicensed transmissions. To help provide UEs with greater flexibility and freedom, CG UEs in NR-U can independently attempt to transmit over predefined resources and independently select the HARQ ID process to use from a given pool. Since this information along with the UE-ID and other information may not be known at the gNB, the CG UE can transmit this information within a specific UCI (referred to herein as CG-UCI) within each CG-PUSCH.

[0039] The embodiments disclosed herein teach multiplexing and discarding rules for situations where CG PUSCH overlaps with uplink control channel transmissions, such as in PUCCH. Some of the disclosed embodiments include an "always reuse" embodiment, an "only discard" embodiment, and a "discard or reuse based on available resources" embodiment. It should be understood that these embodiments are not mutually exclusive. That is, aspects of each of these embodiments can be combined with aspects of other embodiments.

[0040] "Always reuse" implementation

[0041] In one embodiment, when PUCCH overlaps with CG PUSCH within a PUCCH group, and if the timeline requirements defined in Section 9.2.5 of 3GPP Technical Specification (TS) 38.213v15.6.0 (2019-06-24) are met, the existing UCI may be multiplexed with the CG-UCI on the CG PUSCH. The existing UCI in the PUCCH may be the UCI of the resources granted by the gNB for uplink transmission. This UCI may also be referred to as "grant-based UCI".

[0042] Figure 1 A timeslot 100 for NR transmission according to some embodiments is shown. The timeslot 100 may include fourteen orthogonal frequency division multiplexing (OFDM) symbols, labeled OS#0–OS#13. In various embodiments, the CG-PUSCH may be mapped to one or more of the OFDM symbols of the timeslot. The CG-PUSCH may be mapped based on a type A mapping type or a type B mapping type. The mapping type may indicate the valid starting symbol and length of a normal cyclic prefix (with 14 symbols per timeslot) or an extended cyclic prefix (with 12 symbols per timeslot). The length may be defined as the duration of a symbol. The mapping type may also be used to determine the location of a demodulation reference signal (DMRS). For example, for a type A mapping, the DMRS may be located within symbol 2 or symbol 3, and for a type B mapping, the DMRS is located in the first symbol of the PUSCH. Type B mapping may correspond to a frontloading configuration that allows a gNB receiver to estimate the uplink channel response before receiving uplink data.

[0043] As shown, slot 100 shows a type A mapping, where DMRS 104A is in OS#2. CG-UCI 102 may be scheduled to follow DMRS 104A. In some cases, if the CG-UCI otherwise scheduled after DMRS 104B would be the last symbol of the radio frame, the CG-UCI may be truncated (e.g., discarded). Note that existing UCI (e.g., grant-based UCI) may include HARQ-ACK in response to a PDSCH transmission or CSI report.

[0044] In one embodiment, the mapping order of all other existing UCIs may be defined as follows: CG-UCI is followed by HARQ-ACK, CSI part 1, and CSI part 2 (if any), followed by data. In another embodiment, the mapping order may be defined as follows: HARQ-ACK, followed by CG-UCI, CSI part 1, and CSI part 2 (if any), followed by data. In one embodiment, to help avoid blind detection or additional calculations at the gNB, the CG-UCI may include one or two bits indicating whether HARQ-ACK and / or CSI are multiplexed. In some cases, if one bit is used, the bit may indicate whether multiplexing is performed. If two bits are provided, the bits may indicate whether multiplexing is not performed (e.g., "00"), and whether HARQ-ACK feedback (e.g., "01") or CSI (e.g., "10") or both (e.g., "11") are multiplexed with the CG-UCI.

[0045] In another embodiment, the CG-UCI and HARQ-ACK feedback are encoded together, regardless of the HARQ-ACK feedback payload. The actual number of HARQ-ACK bits can be jointly encoded with the CG-UCI. Alternatively, if the number of HARQ-ACK bits is less than or equal to K bits, for example K=2, K bits are added to the CG-UCI and joint encoding is performed. If the number of HARQ-ACK bits is higher than K, the actual number of HARQ-ACK bits can be jointly encoded with the CG-UCI. For decoding of the CG-UCI, the gNB can assume different numbers of bits for the GC-UCI based on the knowledge of whether HARQ-ACK is transmitted and how many HARQ-ACK bits are transmitted.

[0046] In one embodiment, the CG-UCI and HARQ-ACK feedback may be encoded together or separately based on the HARQ-ACK feedback. For example, if HARQ-ACK <= 2 bits, the CG-UCI and HARQ-ACK are encoded separately; and if HARQ-ACK> 2 bits, the CG-UCI and HARQ-ACK are jointly encoded.

[0047] Although time slot 100 is shown as an example of CG-PUSCH transmission using type A mapping, other embodiments apply to CG-PUSCH transmission using type B mapping or CG-PUSCH transmitted via mini-slots. As used herein, a mini-slot may refer to an uplink resource that does not contain all symbols of a time slot for a relatively short PUSCH transmission. In various embodiments, a mini-slot may include 2, 4, or 7 symbols. However, a mini-slot in other embodiments may include other numbers of symbols. In various embodiments, a mini-slot transmission may be designed to transmit a relatively small amount of data that can be used for machine type communication or ultra-reliable low latency communication (URLLC).

[0048] In one embodiment, the CG-UCI is transmitted in each PUSCH transmission within a period (or CG burst) and can be mapped starting from a DMRS symbol within each time slot or mini-slot. In some embodiments, the CG-PUSCH can be transmitted in mini-slots that include time allocations across time slot boundaries. These mini-slots may be referred to as "border mini-slots" herein. In contrast, a "non-border mini-slot" may refer to a mini-slot that includes a time allocation that is only located in one time slot. In some embodiments, the CG-UCI may be transmitted only in a CG-PUSCH conveyed through a non-border mini-slot. For example, consider a CG burst that includes multiple CG-PUSCH transmissions. The CG-PUSCH transmission of the CG burst corresponding to the non-border mini-slot may include the CG-UCI, while the CG-PUSCH transmission of the CG burst corresponding to the boundary micro-slot may not include it.

[0049] In some embodiments, the CG-UCI may include a field for indicating the start and length value (SLIV) of each individual mini-slot in which the CG-UCI is transmitted, and / or an indication of the number of repetitions of the corresponding transmission. SLIV may be used to provide an indication of the starting symbol (S) of the mini-slot carrying the CG-PUSCH and a number of consecutive symbols (L) of the mini-slot. In some embodiments, SLIV may be encoded according to the following method: if (L–1)<=7, then SLIV=14×(L–1)+S; otherwise SLIV=14×(14–L+1)+(14–1–S), where 0 <L<=14–S。

[0050] For the case where the LBT gap is located at the starting symbol S of the first CG-PUSCH and the LBT gap has a length of Y OFDM symbols, the actual starting symbol of the PUSCH indicated in the CG-UCI can be OS#S+Y. Therefore, OS#S+Y can contain DMRS, which is transmitted in the first OFDM symbol after the LBT gap, and the length of the actual PUSCH transmission is L–Y. For example, consider S=3, Y=2 and L=4. In this embodiment, the LBT gap can start at OS#3 and end at OS#4. DMRS can occur at OS#5, and the actual length of the CG-PUSCH transmission will be 2 symbols, OS#5 and OS#6.

[0051] In one embodiment, the CG-UCI may indicate that the starting symbol S is the same as the starting symbol of the SLIV configured for PUSCH via, for example, CG configuration information provided to the UE from the gNB. This may be the case even if the actual PUSCH starts at symbol S+Y.

[0052] In another embodiment, the CG-UCI may indicate the starting symbol as S + Y. This may provide the gNB with knowledge of the LBT gap of length Y at the start of the CG-PUSCH.

[0053] In another embodiment, the UE may be configured with a SLIV indicating a start symbol S, so that the LBT gap is configured to occur in Y symbols before S. For example, if S=0 and Y=1, the LBT gap is in OS#13 of the previous slot. In another example, if S=7 and Y=2, the LBT gap is in OS#5 and OS#6. In this case, the start symbol indicated by the CG-UCI may always be the same as the start symbol configured in the SLIV, and the length of the PUSCH may always be L.

[0054] Figure 2A transmission sequence 200 according to some embodiments is shown. The transmission sequence 200 may include multiple PUSCHs transmitted on the first time slot 204 and the last time slot 208. Specifically, the transmission sequence 200 may include PUSCH 212, PUSCH 216, and PUSCH 220. The LBT gap 202 may occur before PUSCH 212. Each of the PUSCHs may include a length of seven. PUSCH 212 and 220 may include a starting symbol of 4; while PUSCH 216 may include a starting symbol of 11. Taking into account the corresponding lengths and starting symbols, both PUSCH 212 and 220 can be mapped to uplink resources that are completely covered by the corresponding time slots. Therefore, PUSCH 212 and 220 can be mapped to corresponding non-border micro-time slots. However, on the other hand, the starting symbol and length of PUSCH 216 may cause PUSCH 216 to be mapped to uplink resources that cross the time slot boundary. This may occur when, for example, S+L>14. Therefore, the PUSCH 216 may be mapped to a boundary mini-slot. The mapping of the PUSCH 216 to the boundary mini-slot may have a direct impact on the CG-UCI mapping (as described above).

[0055] In some embodiments, the UE may transmit only a portion of the PUSCH mapped to the boundary mini-slot on the symbols of the boundary mini-slot within the first slot. The UE may truncate (e.g., discard) a portion of the PUSCH mapped to the symbols of the boundary mini-slot within the last slot. With respect to PUSCH 216, this may mean that the UE may transmit a portion of the PUSCH 216 on the symbols OS#11–OS#13 of the first slot 204 and may discard a portion of the PUSCH 216 on the symbols OS#0–OS#3 of the last slot 208.

[0056] As described above, if the UE uses mapping type B to map PUSCH, the DMRS can be mapped to the first symbol in the slot / mini-slot, and the CG-UCI can be mapped starting in the next symbol. In some embodiments, if the starting symbol is too late in the first slot so that the DMRS and CG-UCI cannot be mapped to the symbols allocated at the end of the first slot, the entire PUSCH can be discarded.

[0057] In some embodiments, the CG-PUSCH mapped to the boundary micro-slot may be divided into two repetitions. The first repetition may be mapped to the end of the first slot, and the second repetition may be mapped to the beginning of the second slot. The combined length of the two repetitions may be equal to L. Each repetition may include a front-loaded DMRS, and the CG-UCI may be mapped to each repetition after the DMRS. The CG-UCI of each repetition may indicate the starting symbol and length of the corresponding repetition. For example, considering PUSCH 216, let (S1, L1) and (S2, L2) be the starting symbol and length of two corresponding repetitions. In this case, (S1=11, L1=3) and (S2=0, L2=4). UCI (including CG-UCI or other UCI) may be multiplexed starting from symbols 12 and 1, respectively. In some cases, this may result in the first part of the UCI being mapped to one or more symbols starting at OS#12 of the first slot 204, and the second part of the UCI being mapped to one or more symbols starting at OS#1 of the last slot 208. In another embodiment, the UCI may be mapped to two repetitions, and the two UCIs may indicate S as the starting symbol of the first repetition and length L as the length of the combined repetition. Figure 2 , S=11, L=7.

[0058] In another embodiment, the CG-UCI may be mapped only to the first repetition of PUSCH 216, and S1=11, L1=7. In still another embodiment, the CG-UCI may be mapped only to repetitions with a larger length. By indicating S1=11, L1=7 by the CG-UCI, it can be understood that the second repetition in the last time slot 208 may have a larger length and can therefore be mapped with the CG-UCI. In yet another embodiment, the CG-UCI may be mapped only to the first repetition in the first time slot 204, and any scheduled UCI to be multiplexed on the PUSCH in the last time slot 208 is mapped to the second repetition, or vice versa. In another embodiment, when the PUSCH is mapped to a boundary microslot, only the CG-UCI is allowed. For example, the CG-UCI may not be multiplexed with other UCIs (such as HARQ or other authorization-based UCIs).

[0059] Various embodiments may perform various LBT operations for PUSCH mapped to a boundary microslot. For example, in a first embodiment, if PUSCH is mapped to a boundary microslot, LBT operations may only be performed for the first repetition, for example, for a portion of the PUSCH in the first slot. If the LBT operation fails, the UE may not transmit any repetition. In another embodiment, LBT operations may also be allowed for the second repetition. For example, if the LBT operation fails for the first repetition, the UE may attempt additional LBT for the second repetition.

[0060] "Discard Only" Implementation

[0061] In one embodiment, if the CG PUSCH overlaps with a PUCCH within a PUCCH group, and if the timeline requirements defined in Section 9.2.5 of 3GPP TS 38.213 are met, the CG-UCI or legacy UCI (e.g., grant-based UCI) carried within the PUCCH may be discarded according to a predefined order or priority rule. The predefined order or priority rule may indicate a specific priority of the CG-UCI compared to other UCI.

[0062] In one embodiment, the priority may be defined as follows, where the UCIs are listed in descending priority order, i.e., where the UCIs listed earlier have relatively higher priority:

[0063] HARQ-ACK→SR→CG-UCI→CSI part 1 (eg, a part of the CSI with a fixed payload size)→CSI part 2 (eg, a part of the CSI with a variable payload size).

[0064] If HARQ-ACK and / or SR are carried in PUCCH, CG PUSCH can be dropped. Otherwise, PUCCH can be dropped instead:

[0065] CG-UCI→HARQ-ACK→SR→CSI part 1→CSI part 2.

[0066] In some embodiments, CG PUSCH may be given high priority and when PUCCH overlaps with CG PUSCH, PUCCH may be dropped:

[0067] HARQ-ACK→SR→CSI part 1→CSI part 2→CG-UCI.

[0068] In some embodiments, PUCCH may be given high priority and when CG-PUSCH overlaps with PUCCH, CG-PUSCH may be dropped.

[0069] In another embodiment, if the CG PUSCH overlaps with the PUCCH within the PUCCH group, and if the timeline requirements defined in Section 9.2.5 of TS 38.213 are met, the UE may transmit only one of the CG PUSCH and PUCCH, and the other channel may be discarded. Specifically, the UE may first perform UCI multiplexing on the PUCCH according to the process defined in Section 9.2.5 of TS 38.213. When the resulting PUCCH resource overlaps with the CG PUSCH, if the timeline requirements defined in Section 9.2.5 of TS 38.213 are met, and if one of the UCI types in the PUCCH has a higher priority than the CG-UCI, the CG PUSCH may be discarded and the PUCCH may be transmitted. If any UCI type in the PUCCH has a lower priority than the CG-UCI, the CG PUSCH is transmitted and the PUCCH is discarded. The priority rules may be defined as described above.

[0070] In another embodiment, the UE may transmit the CG PUSCH or PUCCH with the earliest starting symbol and drop the other channel. If both channels have the same starting symbol, the UE may drop the channel with the shorter or longer duration.

[0071] In some embodiments, the type or duration of a PUSCH transmission may be used as a basis for determining the UCI carried by the PUSCH transmission. For example, in some embodiments, if a mini-slot PUSCH transmission has a length (which may be milliseconds or symbols) less than or equal to a predetermined threshold X, then the CG-UCI or grant-based UCI may be discarded. UCI discard may be based on the priorities discussed herein.

[0072] "Discard or reuse based on available resources" implementation plan

[0073] In one embodiment, if resources are sufficient, the existing UCI (eg, grant-based UCI) may be multiplexed with the CG-UCI within the CGPUSCH, otherwise the CG PUSCH or PUCCH may be dropped.

[0074] In one embodiment, if the CG PUSCH has sufficient resources to accommodate multiplexing, the mapping order of UCI may be as follows: CG-UCI first, then HARQ-ACK, CSI part 1 and CSI part 2, and finally data. In one embodiment, to help avoid blind detection or additional calculations at the gNB, the CG-UCI may include one or two bits indicating whether HARQ-ACK and / or CSI are multiplexed. If one bit is used, the bit may indicate whether multiplexing is performed. If two bits are provided, the bits may indicate that multiplexing is not performed (e.g., "00"), and whether HARQ-ACK feedback (e.g., "01") or CSI (e.g., "10") or both (e.g., "11") are multiplexed with the CG-UCI.

[0075] In another embodiment, CG-UCI and HARQ-ACK feedback may always be encoded together.

[0076] In one embodiment, if the PUCCH and CG PUSCH overlap and the available resources within the CG PUSCH are insufficient to carry the CG-UCI with UCI carried on the PUCCH, the CG-UCI or legacy UCI carried within the PUCCH may be discarded according to a predefined list indicating a specific priority compared to other UCIs.

[0077] In one embodiment, the priorities may be defined as follows, where the UCIs listed have relatively higher priorities:

[0078] HARQ-ACK→CG-UCI→CSI part 1→CSI part 2.

[0079] In some embodiments, if HARQ-ACK is carried in PUCCH, CG PUSCH may be dropped. Otherwise, PUCCH may be dropped instead:

[0080] CG-UCI→HARQ-ACK→CSI part 1→CSI part 2.

[0081] In some embodiments, CG PUSCH may be given high priority and this may always be dropped when PUCCH overlaps with CG PUSCH:

[0082] HARQ-ACK→CSI part 1→CSI part 2→CG-UCI.

[0083] In some embodiments, PUCCH may be given higher priority and CG-PUSCH may be dropped when CG PUSCH overlaps with PUCCH.

[0084] In another embodiment, if the CG PUSCH overlaps with the PUCCH within the PUCCH group and if the timeline requirements defined in Section 9.2.5 of TS 38.213 are met, then based on the available resources, the UE may multiplex some uplink information on the CG PUSCH based on one of the following priority lists:

[0085] HARQ-ACK→CG-UCI→CSI part 1→CSI part 2→data;

[0086] CG-UCI → HARQ-ACK → CSI part 1 → CSI part 2 → data; or

[0087] HARQ-ACK→CSI part 1→CSI part 2→CG-UCI→data.

[0088] In this case, the UE may perform encoding to allow use of all resource elements (REs).

[0089] In one embodiment, if the data is discarded, the CG-UCI may also be discarded.

[0090] For the case when the PUSCH is mapped to a boundary mini-slot, making R symbols available from the start symbol of the PUSCH to the slot boundary, the following multiplexing or dropping rules may be applied.

[0091] In one embodiment, if R is such that there are not enough resources to transmit the CG-UCI, then only the DMRS is mapped to the starting symbol, and the HARQ-ACK and other grant-based UCI are rate matched to the remaining R-1 symbols. In one embodiment, if the R symbol does not contain enough resources for the CG-UCI, and the CG-UCI is discarded, the CGPUSCH can be moved to the beginning of the next time slot, and other (e.g., grant-based) UCI ​​scheduled for this time slot can be discarded for the first mini-time slot transmission.

[0092] In another embodiment, if the R symbol at the end of the timeslot contains sufficient resources for DMRS and CG-UCI, then HARQ-ACK and other legacy UCI are only multiplexed into the first repetition if sufficient resources are available, otherwise they are discarded.

[0093] In some embodiments, if the PUSCH is divided into two mini-slot PUSCH repetitions and the CG-UCI is mapped to the first repetition, the CG-UCI can be discarded from the second repetition and only other UCI (e.g., HARQ or other grant-based UCI) is mapped to the second repetition. In embodiments where the CG-UCI is mapped to both the first and second repetitions, the grant-based UCI can be multiplexed in the repetition with more resources (e.g., a portion with more symbols). In some embodiments, if there are sufficient resources in each repetition, the CG-UCI and grant-based UCI can be multiplexed on both repetitions.

[0094] "Configurable discard or reuse" implementation

[0095] In one embodiment, the gNB may configure whether and which type of discarding or multiplexing to use, such as through higher layer signaling or as indicated in the DCI. For example, in some embodiments, the gNB may configure the UE to perform the always multiplexing implementation or the discard-only implementation discussed herein.

[0096] Example encoding rules

[0097] In one embodiment, the CG-UCI may be encoded as follows:

[0098] If GC-UCI is encoded first, then:

[0099]

[0100] If CG-UCI is encoded after HARQ-ACK feedback, then:

[0101]

[0102] Among them, CG-UCI represents the number of bits constituting CG-UCI, and L CG-UCI is the number of CRC bits. This is equivalent to or Or equivalently the new beta offset of CG-UCI.

[0103] In one embodiment, if the CG-UCI is encoded together with the HARQ-ACK, the CG-UCI and the HARQ-ACK may be encoded as follows:

[0104]

[0105] Among them, CG-UCI Indicates the number of bits constituting CG-UCI, O ACK Indicates the number of bits that make up HARQ-ACK, and LCG-UCI+ACK is the number of CRC bits. Therefore, this is equivalent to a new set of β offsets that are redefined to maintain the same reliability. Alternatively, if the HARQ-ACK is less than or equal to 2 bits, the HARQ-ACK and CG-UCI may be encoded separately, and if the HARQ-ACK is greater than 2 bits, the HARQ-ACK and CG-UCI may be encoded together using the above formula.

[0106] In one embodiment, if HARQ-ACK is multiplexed with CG-UCI and encoded separately, the encoding of HARQ-ACK may be performed as follows:

[0107] If GC-UCI is encoded before HARQ-ACK:

[0108]

[0109] If GC-UCI is encoded after HARQ-ACK, the conventional process may be reused as is.

[0110] In one embodiment, if CSI part 1 is multiplexed with CG-UCI, the encoding of CSI part 1 may be performed as follows:

[0111] If ACK-ACK and CG-UCI are encoded separately, then:

[0112]

[0113] If ACK-ACK and CG-UCI are jointly coded, then:

[0114]

[0115] In one embodiment, if CSI part 2 is also multiplexed with CG-UCI, the encoding of CSI part 2 may be performed as follows:

[0116] If ACK-ACK and CG-UCI are encoded separately, then:

[0117]

[0118] If ACK-ACK and CG-UCI are jointly coded, then:

[0119]

[0120] In one embodiment, if the data is discarded, but the CG-UCI is still transmitted and encoded with the HARQ-ACK, the CG-UCI and HARQ-ACK may be encoded as follows:

[0121]

[0122] In one embodiment, if the data is discarded, but the CG-UCI is still transmitted and encoded separately from the HARQ-ACK, the CG-UCI may be encoded as follows:

[0123] If CG-UCI is mapped first, then:

[0124]

[0125] If CG-UCI is mapped after HARQ-ACK, then

[0126]

[0127] In one embodiment, if the data is discarded, but the CG-UCI is still transmitted and encoded separately from the HARQ-ACK, the HARQ-ACK may be encoded as follows:

[0128] If HARQ-ACK is mapped first, the conventional formula can be used.

[0129] If HARQ-ACK is mapped after CG-UCI, then:

[0130]

[0131] In one embodiment, if data is dropped but CG-UCI is still transmitted, the encoding of CSI part 1 may be performed as follows:

[0132] If HARQ-ACK and CG-UCI are encoded together, then:

[0133] If there is CSI Part 2 to be transmitted on PUSCH:

[0134]

[0135] Otherwise, if there is no CSI part 2 to transmit:

[0136]

[0137] If HARQ-ACK and CG-UCI are encoded separately, then:

[0138] If there is CSI Part 2 to be transmitted on PUSCH:

[0139]

[0140] Otherwise, if there is no CSI part 2 to transmit:

[0141]

[0142] In one embodiment, if the data is dropped but the CG-UCI is still transmitted, the encoding of CSI Part 2 may be performed as follows:

[0143] If HARQ-ACK and CG-UCI are encoded together, then:

[0144]

[0145] If HARQ-ACK and CG-UCI are encoded separately, then:

[0146]

[0147] In one embodiment, if CG-UCI and other UCI types including CSI part 2 are multiplexed in the CG PUSCH, some parts of CSI part 2 may be dropped depending on the amount of resources allocated to CSI part 2.

[0148] Specifically, the calculation of the resource amount of CSI part 2 can be performed as follows:

[0149] When a UE is scheduled to transmit a transport block on the PUSCH multiplexed with a CSI report, it shall Greater than (if HARQ-ACK and CG-UCI are jointly encoded); or greater (if HARQ-ACK and CG-UCI are encoded separately) only omits part 2CSI, where parameter O CSI-2 , L CSI-2 , C UL-SCH , K r , Q' CSI-1 , Q' ACK and α are defined in section 6.3.2.4 of [5, TS 38.212], or as provided above.

[0150] In one embodiment, the Part 2 CSI is omitted level by level starting from the lowest priority until the lowest priority is reached, which makes Less than or equal to:

[0151] (if HARQ-ACK and CG-UCI are jointly coded); or (If HARQ-ACK and CG-UCI are encoded separately).

[0152] Operational process and algorithm structure

[0153] Aspects of the embodiments described herein may be implemented by devices or components that execute operational flow / algorithm structures. Figure 3-Figure 5 Some operational flows / algorithm structures according to some embodiments are shown. Figure 3-Figure 5 Some or all of the details of may be performed by: UE, e.g. Figure 6 UE601a or 601b; components, such as Figure 7 Baseband circuit 710 or radio front end module 715; or Fig. 9 A processor 910 and a memory / storage device 920 are provided.

[0154] Figure 3 An operational flow / algorithm structure 300 is illustrated according to some embodiments.

[0155] The operational flow / algorithm structure 300 may include, at 304, determining that the CG-PUSCH is to be transmitted in a mini-slot. In some embodiments, the determination at 304 may include an initial determination of available CG resources. This initial determination may include processing configuration information received from the gNB using, for example, radio resource control (RRC) signaling.

[0156] In some embodiments, the gNB may configure the UE with either a Type 1CG allocation or a Type 2CG allocation. Type 1CG allocations may be fully configured and released using RRC signaling. Once configured, the UE may have a set of periodic opportunities for PUSCH transmissions. When retransmissions are requested, only the PDCCH may be required. With a Type 2CG allocation, the resource allocation may be partially configured using RRC signaling, but may be subsequently activated or deactivated using PDCCH transmissions.

[0157] In some embodiments, the gNB may also configure the UE to transmit CG-PUSCH with repetitions. In some embodiments, the gNB may indicate the number of repetitions that the UE will use via an RRC information element (e.g., PUSCH aggregation factor). This may be part of the CG information or separate from it.

[0158] After the UE determines the resources allocated for CG transmission, the UE may identify information to be transmitted in the uplink transmission. The information may include data or control signals to be transmitted to the gNB in ​​one or more physical channels (such as, but not limited to, PUSCH, PUCCH, etc.). In some embodiments, the information may include grant-based information (e.g., grant-based UCI) and CG information (e.g., CG-UCI).

[0159] In some embodiments described herein, the UE may determine that the CG-PUSCH is to be transmitted in a boundary mini-slot, e.g., a mini-slot that includes uplink resources (e.g., OFDM symbols) in multiple slots. This determination may be based on the SLIV that may be configured by the CG configuration information received from the gNB.

[0160] The operational flow / algorithm structure 300 may also include, at 308, selecting a UCI based on the determination of 304. The UCI selected at 308 may include a grant-based UCI or a CG-UCI. For example, in some embodiments, the selected UCI may include a grant-based UCI without a CG-UCI; a CG-UCI without a grant-based UCI; or both a grant-based UCI and a CG-UCI.

[0161] The selection of the UCI may be based on any of a number of factors, including, but not limited to, the mapping type (e.g., type A or type B mapping type) used to map the PUSCH to the OFDM symbol; or whether the mini-slot is a boundary or non-border mini-slot. If the mini-slot is a boundary mini-slot, the selection of the UCI may also be based on the amount of uplink resources in the first slot as opposed to the second slot, and the selection may also include selecting the UCI to be transmitted in the first slot (if any) and selecting the UCI to be transmitted in the second slot (if any). In some embodiments, the selection of the UCI may be additionally / alternatively based on the relative priorities of different UCIs as discussed herein.

[0162] The operational flow / algorithm structure 300 may also include encoding the CG-PUSCH with the selected UCI for transmission in the mini-slot at 312. In an embodiment where the CG-UCI is selected, the CG-UCI may be encoded with an indication of a SLIV or repetition corresponding to a particular CG-PUSCH.

[0163] In some embodiments, the CG-PUSCH may be one of multiple PUSCHs of a CG burst to be transmitted in corresponding multiple mini-slots. The CG-PUSCH may transmit the same information or different information. Some of the CG-PUSCHs may be transmitted in boundary mini-slots, and others may be transmitted in non-boundary mini-slots. Based on whether the mini-slot is boundary or non-boundary, the selection of UCI for the CG-PUSCH may be different. For example, as discussed elsewhere herein, in some embodiments, a CG-PUSCH transmitted in a boundary mini-slot may not include a CG-UCI.

[0164] Figure 4 An operational flow / algorithm structure 400 is shown according to some embodiments.

[0165] The operational flow / algorithm structure 400 may include, at 404, identifying information to be transmitted in the CG-PUSCH. In some embodiments, the upper layers of the UE may provide the lower layers of the UE, such as the media access control (MAC) / physical (PHY) layer of the UE with information to be transmitted (e.g., data or control information). The lower layers of the UE may identify the information as information to be transmitted in the CG-PUSCH. The information to be transmitted may include, among other information, a UCI or a CG-UCI based on a grant.

[0166] The operational flow / algorithm structure 400 may also include determining uplink resources to be used for the CG-PUSCH at 408. The determination at 408 may be based on the SLIV configured via the CG configuration information provided from the gNB to the UE. Thus, the uplink resources may correspond to the configured granted resources and, in some embodiments, may include multiple CGs of a CG burst.

[0167] The operational flow / algorithm structure 400 may also include, at 412, determining that the uplink resources are in the first time slot and the second time slot. For example, the uplink resources may correspond to a mini-time slot having a time allocation that crosses a time slot boundary. For example, in the case of a normal cyclic prefix, the determination at 412 may be based on the configured S and L values ​​of the SLIV being greater than 14.

[0168] The operational flow / algorithm structure 400 may also include determining whether to encode zero, one, or two portions at 416. In various embodiments, the determination at 416 may be based at least in part on the size of the resource allocation in the first time slot, for example, the number of OFDM symbols available in the first time slot.

[0169] In some embodiments, the determination at 416 may include determining to encode a zero portion. In some embodiments, the UE may determine to encode a zero portion if, for example, the uplink resources included in the first time slot are insufficient to transmit both the DMRS and the CG-UCI. For example, if the DMRS and the CG-UCI require more symbols than are available in the first time slot, the UE may determine that no portion of the CG-PUSCH is to be encoded.

[0170] If it is determined at 416 that the zero portion is to be encoded, the operational flow / algorithm structure 400 may include, at 420, dropping the CG-PUSCH.

[0171] In some embodiments, the determination at 416 may include determining to encode a portion of the CG-PUSCH in the uplink resources in the first time slot (and truncating the second portion). In some embodiments, the UE may determine to truncate the second portion based at least in part on the size of the resource allocation in the second time slot. For example, if the number of symbols included in the second time slot is insufficient to carry the DMRS and the CG-UCI, the second portion may be truncated.

[0172] If it is determined at 416 to encode the first portion, then the operational flow / algorithm structure 400 may include, at 424, encoding the first portion for transmission in the first time slot.

[0173] In some embodiments, the determination at 416 may include determining to encode two portions of the CG-PUSCH in the uplink resources in the first time slot and the second time slot. The UE may decide to encode the two portions based at least in part on the size of the resources in the first time slot and the second time slot. For example, if the mini-slot includes enough symbols in the first time slot and the second time slot to transmit, for example, a DMRS and a CG-UCI in two time slots, the UE may determine to encode the two portions.

[0174] If it is determined at 416 that both portions are to be encoded, then the operational flow / algorithm structure 400 may include, at 428, encoding the first portion and the second portion for transmission in the first time slot and the second time slot, respectively.

[0175] In various embodiments, the determination at 416 may also include determining what to encode in the first part or the second part. For example, in an embodiment in which two parts are to be encoded, the UE may determine which parts of the CG-PUSCH are to be encoded in the first part and which parts are to be encoded in the second part. This may include dividing the CG-PUSCH into two parts (or "repeating" in some embodiments), wherein the first part is mapped to the symbol at the end of the first time slot, and the second part is mapped to the symbol at the beginning of the second time slot. In some embodiments, each part may include a front-loaded DMRS, wherein the CG-UCI is mapped to each part after the DMRS. The CG-UCI of each part may include a SLIV providing S and L values ​​corresponding to the corresponding CG-UCI. For example, the S value of the CG-UCI transmitted in the first time slot may indicate the starting symbol of the first time slot, which may include a DMRS and toward the end of the time slot. The S value of the CG-UCI transmitted in the second time slot may indicate the starting symbol of the second time slot, which may also include a DMRS and may be the first time slot, such as OS#0. The sum of the two L values ​​for the two parts may be equal to the L value configured for the UE for the total size of the uplink resource allocation, e.g., mini-slots.

[0176] Figure 5 An operational flow / algorithm structure 500 is shown according to some embodiments.

[0177] The operational flow / algorithm structure 500 may include, at 504, determining that the mini-slot PUSCH is to cross a boundary between a first slot and a second slot. In some embodiments, determining that the mini-slot PUSCH crosses a boundary may be based on the UE selecting a CG uplink resource for transmitting the PUSCH. The selected resource may correspond to a configured mini-slot having a starting symbol later in the first symbol and a length such that at least some of the symbols of the mini-slot occur in a second slot after the first slot.

[0178] The operation flow / algorithm structure 500 may also include encoding the first part and the second part of the mini-time slot PUSCH at 508. In some embodiments, the UE may determine which parts and information of the UCI are to be encoded in each part. For example, the UE may determine whether the CG-UCI, the grant-based UCI, the DMRS, or the data is to be included in the first part, the second part, or both the first part and the second part.

[0179] The operational flow / algorithm structure 500 may include, at 512, performing one or more LBT processes. In order to perform the LBT process, the UE may first perform a clear channel assessment (CCA) by listening to the operating channel for a time period corresponding to the CCA observation time. If the UE detects energy on the channel that exceeds a predetermined threshold, the UE may determine a backoff period based on a random value multiplied by the CCA observation time. After the backoff period, the UE may attempt the CCA again. If the channel is occupied for more than a predetermined number of CCAs, the LBT process may be considered unsuccessful. If the UE determines that the energy detected by the CCA observation time does not exceed a predetermined threshold, the LBT process may be considered successful.

[0180] In some embodiments, the LBT process may be performed only for the first part. For example, if the LBT process is successfully performed on the first part, the UE may be able to transmit both the first part and the second part. Alternatively, if the LBT process is unsuccessful, the UE may discard both the first part and the second part.

[0181] In other embodiments, the LBT process may also be performed for the second part. For example, if the LBT process is unsuccessful for the first part, the first part may be discarded, but another LBT process may be performed for the second part. If the second LBT process is successful, the UE may send the second part.

[0182] The operational flow / algorithm structure 500 may include, at 516 , transmitting the first portion or the second portion based on the LBT process performed at 512 .

[0183] System and implementation

[0184] Now go to Figure 6 , an exemplary architecture of a system 600 of a network according to various embodiments is shown. For example, the following description is provided for an exemplary system 600 operating in conjunction with a 5G or NR system standard provided by a 3GPP technical specification. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems or other wireless networks.

[0185] like Figure 6 As shown, system 600 includes UE 601a and UE 601b (collectively referred to as "UE 601"). In this example, UE 601 is shown as a smart phone (e.g., a handheld touch screen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument panels (ICs), head-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine electronic control units (ECUs), electronic / engine electronic control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0186] In some embodiments, any of the UEs 601 may be an Internet of Things (IoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe or D2D communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0187] UE 601 may be configured to connect, e.g., be communicatively coupled, to a radio access network (RAN) 610. In an embodiment, RAN 610 may be an NG RAN or a 5G RAN. As used herein, the term "NG RAN" or the like may refer to RAN 610 operating in an NR or 5G system 600. UE 601 utilizes connections (or channels) 603 and 604, respectively, each of which includes a physical communication interface or layer (discussed in further detail below).

[0188] In this example, connections 603 and 604 are shown as air interfaces to achieve communication coupling, and may be consistent with a cellular communication protocol, such as the 3GPP 5G / NR protocol or any other communication protocol discussed herein. In an embodiment, the UE 601 may directly exchange communication data via the ProSe interface 605. The ProSe interface 605 may alternatively be referred to as a sidelink (SL) interface 605.

[0189] UE 601b is shown as being configured to access AP 606 (also referred to as "WLAN node 606," "WLAN 606," "WLAN terminal 606," "WT 606," etc.) via connection 607. Connection 607 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 606 will include Wireless Fidelity. Router. In this example, AP 606 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 601b, RAN 610, and AP 606 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 601b in RRC_CONNECTED state being configured by RAN nodes 611a-611b to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 601b using WLAN radio resources (e.g., connection 607) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through connection 607. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0190] The RAN 610 includes one or more access nodes (ANs) or RAN nodes 611a and 611b (collectively referred to as "RAN nodes 611") that enable connections 603 and 604. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, or TRPs, 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 nodes," and the like may refer to RAN nodes 611 (e.g., gNBs) operating in NR or 5G systems 600, while the terms "E-UTRAN nodes," and the like may refer to RAN nodes 611 (e.g., eNBs) operating in LTE or 4G systems. According to various embodiments, the RAN node 611 may be implemented as one or more of a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0191] In a vehicle-to-everything (V2X) scenario, one or more of the RAN nodes 611 may be a roadside unit (RSU) or act as an RSU. An RSU may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein 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", and so on. In one example, an RSU is a computing device coupled to a radio frequency circuit located on the road side that provides connectivity support to a passing vehicle UE 601 (vUE). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, etc. In addition or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications as well as other cellular communication services. In addition 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 and the RSU's RF circuitry may be packaged in a weather-resistant 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 backhaul network.

[0192] Any of the RAN nodes 611 may terminate the air interface protocol and may be the first point of contact for the UE 601. In some embodiments, any of the RAN nodes 611 may fulfill various logical functions of the RAN 610, including but not limited to the functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0193] In an embodiment, UE 601 may be configured to communicate with each other or with any of RAN nodes 611 over a multi-carrier communication channel using OFDM communication signals according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0194] In some embodiments, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 611 to the UE 601, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is a common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0195] According to various embodiments, UE 601 and RAN node 611 communicate data (e.g., transmit data and receive data) through licensed media (also known as "licensed spectrum" and / or "licensed band") and unlicensed shared media (also known as "unlicensed spectrum" and / or "unlicensed band").

[0196] To operate in the unlicensed spectrum, the UE 601 and the RAN node 611 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UE 601 and the RAN node 611 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether 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.

[0197] As described above, LBT is a mechanism whereby equipment (e.g., UE 601 RAN node 611, etc.) utilizes the mechanism to sense the medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least energy detection (ED) to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy on an expected transmission band over a period of time, and comparing the sensed RF energy to a predefined or configured threshold.

[0198] The RAN nodes 611 may be configured to communicate with each other via an interface 612. The interface 612 may be an Xn interface 612. The Xn interface is defined between two or more RAN nodes 611 (e.g., two or more gNBs, etc.) connected to the 5GC 620, between a RAN node 611 (e.g., a gNB) and an eNB connected to the 5GC 620, and / or between two eNBs connected to the 5GC 620. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for the UE 601 in a connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 611. The mobility support may include context transfer from the old (source) serving RAN node 611 to the new (target) serving RAN node 611; and control of the user plane tunnel between the old (source) serving RAN node 611 and the new (target) serving RAN node 611. 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 for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the 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. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0199] RAN 610 is shown as being communicatively coupled to a core network—in this embodiment, communicatively coupled to a core network (CN) 620. CN 620 may include a plurality of network elements 622 configured to provide various data and telecommunication services to customers / users (e.g., users of UE 601) connected to CN 620 via RAN 610. The components of CN 620 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 used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 620 may be referred to as a network slice, and a logical instance of a portion of CN 620 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0200] Generally speaking, the application server 630 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 630 may also be configured to support one or more communication services for the UE 601 via the CN 620 (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.).

[0201] In an embodiment, CN 620 may be a 5GC (referred to as "5GC 620" or the like), and RAN 610 may be connected to CN 620 via an NG interface 613. In an embodiment, NG interface 613 may be divided into two parts: an NG user plane (NG-U) interface 614, which carries traffic data between RAN node 611 and UPF; and an S1 control plane (NG-C) interface 615, which is a signaling interface between RAN node 611 and AMF.

[0202] Figure 7An example of a platform 700 (or "device 700") according to various embodiments is shown. In an embodiment, the computer platform 700 may be suitable for use as a UE 601, an application server, and / or any other element / device discussed herein. The platform 700 may include any combination of components shown in the example. The components of the platform 700 may be implemented as an integrated circuit (IC), a portion thereof, a discrete electronic device, or other modules, logic, hardware, software, firmware, or a combination thereof suitable for use in the computer platform 700, or implemented as components otherwise incorporated within the chassis of a larger system. Figure 7 The block diagram is intended to show a high-level view of the components of computer platform 700. 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.

[0203] The application circuit 705 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: a low dropout regulator (LDO), an interrupt controller, a serial interface, a general purpose programmable serial interface module, a real-time clock (RTC), a timer-counter (including an interval timer and a watchdog timer), a general purpose I / O, a memory card controller such as a secure digital multimedia card (SD MMC) or similar product, a universal serial bus (USB) interface, a mobile industry processor interface interface and a Joint Test Access Group (JTAG) test access port. The processor (or core) of the application circuit 605 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the system 600. In some specific implementations, the memory / storage element may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as a dynamic random access memory (DRAM), a static random access memory (SRAM), an erasable programmable read-only memory (EPROM), an electrically EPROM (EEPROM), flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0204] The processor of the application circuit 705 may include, for example, one or more processor cores, one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computer (RISC) processors, one or more Arm processors, one or more complex instruction set computer (CISC) processors, one or more digital signal processors (DSPs), one or more field programmable gate arrays (FPGAs), one or more programmable logic devices (PLDs), one or more application specific integrated circuits (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, the application circuit 705 may include or may be a dedicated processor / controller for operating according to various embodiments herein.

[0205] As an example, the processor of the application circuit 705 may include a processor based on Architecture Core TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU class processors, or available from Santa Clara, CA The processor of application circuit 705 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s A5-A9 processors, Snapdragon by Technologies, Inc. TM Processor, Texas Instruments, Open Multimedia Applications Platform(OMAP) TM processors; 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 series processors; etc. In some implementations, the application circuit 705 can be part of a system on a chip (SoC), in which the application circuit 705 and other components are formed as a single integrated circuit or a single package, such as company( Edison Corporation TM or Galileo TM SoC board.

[0206] Additionally or alternatively, the application circuit 705 may include circuits such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, PLDs such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), ASICs such as structured ASICs, programmable SoCs (PSoCs), and the like. In such embodiments, the circuits of the application circuit 705 may include logic blocks or logic structures, and other interconnected resources that may be programmed to perform various functions such as the processes, methods, functions, and the like of the various embodiments discussed herein. In such embodiments, the circuits of the application circuit 705 may include memory cells (e.g., EPROM, EEPROM, flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, and the like)) for storing logic blocks, logic structures, data, and the like in look-up tables (LUTs), and the like.

[0207] Baseband circuit 710 may be implemented, for example, as a solder-in substrate including 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. Figure 8 The various hardware electronic components of baseband circuit 710 are discussed.

[0208] The radio front end module (RFEM) 715 may also be referred to as a "radio front end circuit" and may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Figure 8 Antenna array 811), and the RFEM can be connected to multiple antennas. In an alternative implementation, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM 715 that combines both millimeter wave antennas and sub-millimeter waves.

[0209] The memory circuit 720 may include any number and type of memory devices for providing a quantitative system memory. For example, the memory circuit 620 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (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), etc. The memory circuit 720 may be developed according to the Joint Electron Device Engineering Council (JEDEC) based low power double data rate (LPDDR) design such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 720 may be implemented as one or more of a solder-in 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 to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 720 may be an on-chip memory or register associated with the application circuit 705. In order to provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 720 may include one or more mass storage devices, which may include, among others, a solid state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory. For example, the computer platform 700 may be combined with and Three-dimensional (3D) cross-point (XPOINT) memory.

[0210] Removable memory circuitry 723 may include devices, circuitry, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 700. These portable data storage devices may be used for mass storage, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, micro SD cards, xD picture cards, etc.), as well as USB flash drives, optical disks, external HDDs, etc.

[0211] The platform 700 may further include an interface circuit (not shown) for connecting external devices to the platform 700. External devices connected to the platform 600 via the interface circuit include a sensor circuit 721 and an electromechanical component (EMC) 722, and a removable memory device coupled to a removable memory circuit 723.

[0212] Sensor circuitry 721 comprises a device, module, or subsystem that is intended to detect events or changes in its environment, and to send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit (IMU) including an accelerometer, a gyroscope, and / or a magnetometer; a microelectromechanical system (MEMS) or a nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other similar audio capture device; etc.

[0213] The EMC 722 includes devices, modules or subsystems that are intended to enable the platform 700 to change its state, position and / or orientation or to move or control a mechanism or (sub) system. In addition, the EMC 722 may be configured to generate messages / signaling and send messages / signaling to other components of the platform 700 to indicate the current state of the EMC 722. Examples of the EMC 722 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 700 is configured to operate one or more EMCs 722 based on one or more capture events and / or instructions or control signals received from a service provider and / or various clients.

[0214] In some specific implementations, the interface circuit may connect the platform 700 to the positioning circuit 745. The positioning circuit 745 includes a circuit for receiving and decoding signals transmitted / broadcasted by the positioning network of the GNSS. Examples of navigation satellite constellations (or GNSS) may include the GPS of the United States, the GLONASS of Russia, the Galileo system of the European Union, the Beidou navigation satellite system of China, regional navigation systems or GNSS augmentation systems (e.g., NAVIC, QZSS of Japan, DORIS of France, etc.), etc. The positioning circuit 745 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communication) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 745 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 745 may also be part of the baseband circuit 710 and / or the RFEM 715 or interact with it to communicate with nodes and components of the positioning network. Positioning circuitry 745 may also provide position data and / or time data to application circuitry 705, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations) for use in turn-by-turn navigation applications, etc.

[0215] In some implementations, the interface circuit may connect the platform 700 with a near field communication (NFC) circuit 740. The NFC circuit 740 is configured to provide contactless short-range communication based on the radio frequency identification (RFID) standard, where a magnetic field is sensed to enable communication between the NFC circuit 740 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 700. The NFC circuit 740 includes 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 NFC functionality to the NFC circuit 740 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 transmit a short-range RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuit 640, or initiate data transfer between the NFC circuit 640 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) proximate to the platform 700.

[0216] The driver circuit 746 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 700. The driver circuit 746 may include various drivers to allow other components of the platform 700 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 700. For example, the driver circuit 746 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface of the platform 700, a sensor driver for obtaining sensor readings of the sensor circuit 721 and controlling and allowing access to the sensor circuit 721, an EMC driver for obtaining an actuator position of the EMC 722 and / or controlling and allowing access to the EMC 722, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0217] A power management integrated circuit (PMIC) 725 (also referred to as “power management circuit 725”) may manage power provided to various components of the platform 700. Specifically, the PMIC 725 may control power selection, voltage scaling, battery charging, or DC-DC conversion relative to the baseband circuit 710. When the platform 700 is capable of being powered by a battery 730, for example, when the device is included in the UE 601, the PMIC 725 may generally be included.

[0218] In some embodiments, the PMIC 725 may control or otherwise be part of various power saving mechanisms of the platform 700. For example, if the platform 700 is in the RRC_Connected state, where the device is still connected to the RAN node because it expects to receive traffic immediately, then after a period of inactivity, the device may enter a state known as discontinuous reception mode (DRX). During this state, the platform 700 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 700 may transition to the RRC_Idle state, where the device is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The platform 700 enters a very low power state and performs paging, where the device wakes up periodically again to listen to the network and then powers off again. The platform 700 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to a few hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0219] The battery 730 can power the platform 700, but in some examples, the platform 700 can be mounted in a fixed location and can have a power source coupled to a power grid. The battery 730 can 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 in V2X applications, the battery 730 can be a typical lead-acid car battery.

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

[0221] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 730. In some examples, the power block can be replaced with a wireless power receiver to obtain power wirelessly, for example, through a loop antenna in the computer platform 700. In these examples, a wireless battery charging circuit can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 730 and therefore the required current. Charging can be performed using the aviation fuel standard published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Wireless Power Alliance, or the Rezence charging standard published by the Wireless Power Alliance.

[0222] The user interface circuit 750 includes various input / output (I / O) devices present in or connected to the platform 700, and includes one or more user interfaces designed to enable user interaction with the platform 700 and / or a peripheral component interface designed to enable peripheral components to interact with the platform 700. The user interface circuit 750 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including, in particular, 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. The output device circuit includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, including, in particular, one or more simple visual outputs / indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where outputs of characters, graphics, multimedia objects, etc. are generated or produced by the operation of the platform 700. The output device circuitry may also include speakers or other audio emitting devices, printers, etc. In some embodiments, the sensor circuitry 721 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 circuit may be included to read an electronic tag and / or connect to another NFC-enabled device, the NFC circuitry including an NFC controller and a processing device coupled to an antenna element. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a USB port, an audio jack, a power interface, etc.

[0223] Although not shown, the components of platform 700 can communicate with each other using a suitable bus or interconnect (IX) technology, which can 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 can be a proprietary bus / IX, for example, used in a SoC-based system. Other bus / IX systems can be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, etc.

[0224] Figure 8 8 shows exemplary components of a baseband circuit 810 and a radio front end module (RFEM) 815 according to various embodiments. The baseband circuit 810 corresponds to Figure 7 7 , wherein like-named components correspond to each other.

[0225] The baseband circuit 810 includes circuits and / or control logic components that are configured to execute various radio / network protocols and radio control functions that enable communication with one or more radio networks via the RF circuit 806. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 810 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 810 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples and may include other suitable functions in other embodiments. The baseband circuit 810 is configured to process baseband signals received from the receive signal path of the RF circuit 806 and generate baseband signals for the transmit signal path of the RF circuit 806. The baseband circuit 810 is configured to communicate with the application circuit 705 (see Figure 7 ) to generate and process baseband signals and control the operation of RF circuit 806. Baseband circuit 810 may handle various radio control functions.

[0226] The aforementioned circuits and / or control logic components of the baseband circuit 810 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 804A, a 4G / LTE baseband processor 804B, a 5G / NR baseband processor 804C, or some other baseband processors 804D for other existing generations, generations under development or generations to be developed in the future (e.g., the sixth generation (6G), etc.). In other embodiments, some or all of the functions of the baseband processors 804A to 804D may be included in a module stored in the memory 804G and executed via a central processing unit (CPU) 804E. In other embodiments, some or all of the functions of the baseband processors 804A to 804D may be provided as a hardware accelerator (e.g., FPGA, ASIC, etc.) loaded with an appropriate bitstream or logic block stored in a corresponding memory unit. In various embodiments, the memory 804G may store program code of a real-time operating system (RTOS), which, when executed by the CPU 804E (or other baseband processor), will enable the CPU 804E (or other baseband processor) to manage resources of the baseband circuit 810, schedule tasks, etc. Examples of RTOS may include: Operating System Embedded (OSE) provided TM , by Mentor Nucleus RTOS provided TM , by Mentor Versatile Real-TimeExecutive (VRTX) provided by Express Provided by ThreadX TM ,Depend on FreeRTOS and REX OS provided by Open Kernel (OK) OKL4 is provided, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuit 810 includes one or more audio DSPs 804F. The audio DSP 804F includes elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

[0227] In some embodiments, each of processors 804A to 704E includes a corresponding memory interface to send data to / receive data from memory 804G. Baseband circuit 810 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as an interface for sending data to / receiving data from a memory external to baseband circuit 810; an interface for sending data to / receiving data from a memory external to the baseband circuit; Figure 7 Application circuit interface for sending data to / receiving data from the application circuit 705; Figure 8 RF circuit 806 to send data / receive data from the RF circuit RF circuit interface; for receiving data from one or more wireless hardware elements (e.g., near field communication (NFC) components, Low power consumption components, components, etc.) to send data / receive data from these wireless hardware elements; and a power management interface for sending power or control signals to / receiving power or control signals from the PMIC 725.

[0228] In an alternative embodiment (which can be combined with the above embodiment), the baseband circuit 810 includes one or more digital baseband systems, which are coupled to each other and to the CPU subsystem, the audio subsystem and the interface subsystem via an interconnection subsystem. The digital baseband subsystem can also be coupled to the digital baseband interface and the mixed signal baseband subsystem via another interconnection subsystem. Each of the interconnection subsystems may include a bus system, a point-to-point connector, a network on chip (NOC) structure and / or some other suitable bus or interconnection technology, such as those discussed herein. The audio subsystem may include a DSP circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and / or other similar components. In one aspect of the present disclosure, the baseband circuit 810 may include a protocol processing circuit with one or more control circuit instances (not shown) to provide control functions for the digital baseband circuit and / or the radio frequency circuit (e.g., the radio front end module 815).

[0229] although Figure 8 Not shown, but in some embodiments, the baseband circuit 810 includes various processing devices (e.g., "multi-protocol baseband processor" or "protocol processing circuit") for operating one or more wireless communication protocols and various processing devices for implementing PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuit operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when the baseband circuit 810 and / or the RF circuit 806 are part of a millimeter wave communication circuit or some other suitable cellular communication circuit, the protocol processing circuit can operate LTE protocol entities and / or 5G / NR protocol entities. In a first example, the protocol processing circuit will operate MAC, radio link control (RLC), packet data convergence protocol (PDCP), service data adaptation (SDAP), RRC, and non-access stratum (NAS) functions. The protocol processing circuit may include one or more memory structures (e.g., 804G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using data. The baseband circuit 810 may also support radio communications of more than one wireless protocol.

[0230] The various hardware elements of the baseband circuit 810 discussed herein may be implemented as, for example, a solder-in substrate including one or more integrated circuits (ICs), a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more ICs. In one example, the components of the baseband circuit 810 may be appropriately combined in a single chip or a single chipset, or disposed on the same circuit board. In another example, some or all of the components of the baseband circuit 810 and the RF circuit 806 may be implemented together, such as, for example, a system on a chip (SoC) or a system-in-package (SiP). In another example, some or all of the components of the baseband circuit 810 may be implemented as a separate SoC communicatively coupled to the RF circuit 806 (or multiple instances of the RF circuit 806). In yet another example, some or all of the components of the baseband circuit 810 and the application circuit 705 may be implemented together as a separate SoC mounted to the same circuit board (e.g., a "multi-chip package").

[0231] In some embodiments, the baseband circuit 810 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 810 may support communications with NG-RAN, E-UTRAN or other WMAN, WLAN, WPAN. Embodiments in which the baseband circuit 810 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0232] The RF circuit 806 can communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, the RF circuit 806 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 806 may include a receive signal path, which may include circuits for down-converting RF signals received from the FEM circuit 808 and providing baseband signals to the baseband circuit 810. The RF circuit 806 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by the baseband circuit 810 and providing an RF output signal for transmission to the FEM circuit 808.

[0233] In some embodiments, the receive signal path of the RF circuit 806 may include a mixer circuit 806a, an amplifier circuit 806b, and a filter circuit 806c. In some embodiments, the transmit signal path of the RF circuit 806 may include a filter circuit 806c and a mixer circuit 806a. The RF circuit 806 may also include a synthesizer circuit 806d for synthesizing the frequencies used by the mixer circuit 806a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 806a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 808 based on the synthesized frequency provided by the synthesizer circuit 806d. The amplifier circuit 806b may be configured to amplify the down-converted signal, and the filter circuit 806c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 810 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required.In some embodiments, the mixer circuit 806a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0234] In some embodiments, mixer circuit 806a of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 806d to generate an RF output signal for FEM circuit 808. The baseband signal may be provided by baseband circuit 810 and may be filtered by filter circuit 806c.

[0235] In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and quadrature up-conversion, respectively. In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may be configured for superheterodyne operation.

[0236] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 806 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 810 may include a digital baseband interface to communicate with the RF circuit 806.

[0237] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0238] In some embodiments, synthesizer circuit 806d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 806d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0239] Synthesizer circuit 806d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 806a of RF circuit 806. In some embodiments, synthesizer circuit 806d may be a fractional-N / N+1 synthesizer.

[0240] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by the baseband circuit 810 or the application circuit 505 / 605 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 505 / 605.

[0241] The synthesizer circuit 806d of the RF circuit 806 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0242] In some embodiments, the synthesizer circuit 806d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 806 can include an IQ / polarity converter.

[0243] The FEM circuitry 808 may include a receive signal path that may include circuitry configured to operate on RF signals received from the antenna array 811, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 806 for further processing. The FEM circuitry 808 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 806 for transmission by one or more antenna elements in the antenna array 811. In various embodiments, amplification by the transmit or receive signal path may be accomplished only in the RF circuitry 806, only in the FEM circuitry 808, or in both the RF circuitry 806 and the FEM circuitry 808.

[0244] In some embodiments, the FEM circuit 808 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 808 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 808 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 806). The transmit signal path of the FEM circuit 808 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 806), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 811.

[0245] The antenna array 811 includes one or more antenna elements, each of which is configured to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. For example, a digital baseband signal provided by the baseband circuit 810 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of the antenna array 811 including one or more antenna elements (not shown). The antenna elements may be omnidirectional, directional, or a combination thereof. The antenna elements may be formed into a variety of arrangements as known and / or discussed herein. The antenna array 811 may include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. The antenna array 811 may be formed as a patch of metal foil of various shapes (e.g., a patch antenna) and may be coupled to the RF circuit 806 and / or the FEM circuit 808 using a metal transmission line or the like.

[0246] Fig. 9 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Fig. 9 A schematic diagram of hardware resources 900 is shown, including one or more processors (or processor cores) 910, one or more memory / storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled via a bus 940. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 902 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 900.

[0247] Processor 910 may include, for example, processor 912 and processor 914. Processor 910 may be, for example, a CPU, a RISC processor, a CISC processor, a GPU, a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

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

[0249] The communication resources 930 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 904 or one or more databases 906 via the network 908. For example, the communication resources 930 may include a wired communication component (e.g., for coupling via USB), a cellular communication component, an NFC component, (or Low power consumption) components, components and other communication components.

[0250] The instructions 950 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 910 to perform any one or more of the methods discussed herein. The instructions 950 may reside completely or partially in at least one of the processors 910 (e.g., within a cache memory of the processor), the memory / storage device 920, or any suitable combination thereof. In addition, any portion of the instructions 950 may be transmitted to the hardware resources 900 from any combination of the peripheral device 904 or the database 906. Therefore, the memory of the processor 910, the memory / storage device 920, the peripheral device 904, and the database 906 are examples of computer-readable media and machine-readable media.

[0251] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

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

[0253] Example

[0254] In the following sections, additional exemplary embodiments are provided.

[0255] Embodiment 1 may include a method of operating a UE, the method comprising: determining that a CG-PUSCH is to be transmitted in a micro-slot including a time allocation that crosses a time slot boundary; selecting UCI to include a grant-based UCI or a CG-UCI based on the micro-slot including a time allocation that crosses a time slot boundary; and encoding the CG-PUSCH with the UCI for transmission in the micro-slot.

[0256] Embodiment 2 may include the method according to embodiment 1 or some other embodiments herein, wherein selecting the UCI further comprises: selecting the UCI based on mini-slots including time allocations across slot boundaries to include grant-based UCI without CG-UCI.

[0257] Embodiment 3 may include the method according to embodiment 1 or some other embodiments herein, further comprising: encoding multiple CG-PUSCHs of a configured grant (CG) burst for transmission in corresponding multiple micro-slots, wherein the CG-PUSCH to be transmitted in a micro-slot that does not include a time allocation across a time slot boundary will include a corresponding CG-UCI, and the CG-PUSCH to be transmitted in a micro-slot that includes a time allocation across a time slot boundary will not include a corresponding CG-UCI.

[0258] Embodiment 4 may include a method according to embodiment 1 or some other embodiments herein, wherein the CG-PUSCH is a first CG-PUSCH, the CG-UCI is a first CG-UCI, the microslot is a first microslot, and the method further includes: encoding a second CG-PUSCH to be transmitted in a second microslot, the second CG-PUSCH including a second CG-UCI, the second CG-UCI including an indication of a SLIV for the second microslot.

[0259] Embodiment 5 may include a method according to embodiment 4 or some other embodiments herein, wherein SLIV indicates that the second CG-PUSCH starts at a first OFDM symbol, wherein the second CG-PUSCH starts at a second OFDM symbol, and the second OFDM symbol is the number of OFDM symbols after the first OFDM symbol, wherein the number of OFDM symbols corresponds to the length of the LBT gap starting at the first OFDM symbol.

[0260] Embodiment 6 may include the method according to embodiment 5 or some other embodiments herein, further comprising: identifying a configured SLIV for a second CG-PUSCH, wherein both the SLIV and the configured SLIV indicate that the second CG-PUSCH starts at a first OFDM symbol.

[0261] Embodiment 7 may include a method according to embodiment 4 or some other embodiments herein, wherein the SLIV indicates that the second CG-PUSCH starts at the first OFDM symbol, wherein the second CG-PUSCH starts at the first OFDM symbol, and the LBT gap ends at the second OFDM symbol immediately before the first OFDM symbol.

[0262] Embodiment 8 may include a method according to embodiment 1 or some other embodiments herein, wherein the CG-PUSCH is a first CG-PUSCH, the CG-UCI is a first CG-UCI, the microslot is a first microslot, and the method further includes: encoding a second CG-PUSCH to be transmitted in a second microslot, the second CG-PUSCH including a second CG-UCI, the second CG-UCI including an indication of the number of repetitions corresponding to the second CG-PUSCH.

[0263] Embodiment 9 may include the method according to embodiment 1 or some other embodiments of the present invention, further including: determining the type or duration of CG-PUSCH; and selecting UCI based on the type or duration of CG-PUSCH to include authorization-based UCI or CG-UCI.

[0264] Embodiment 10 may include a method of operating a UE, the method comprising: identifying information to be transmitted in a configured grant-physical uplink shared channel (CG-PUSCH), the information comprising grant-based UCI or CG-UCI; determining uplink resources for the CG-PUSCH based on a start symbol and a length value; determining that the uplink resources are in a first time slot and a second time slot; encoding at least a portion of the information in a first part of the CG-PUSCH; and transmitting the first part of the CG-PUSCH in the first time slot.

[0265] Embodiment 11 may include the method according to embodiment 10 or some other embodiments herein, further comprising: truncating a second portion of the CG-PUSCH corresponding to uplink resources in a second time slot.

[0266] Embodiment 12 may include the method described in accordance with embodiment 10 or some other embodiments herein, further comprising: mapping the DMRS to a first symbol corresponding to a start symbol, and mapping the CG-UCI to a second symbol immediately following the first symbol, wherein the first symbol and the second symbol are in a first time slot.

[0267] Embodiment 13 may include a method according to embodiment 10 or some other embodiments herein, wherein the CG-PUSCH is a first CG-PUSCH, the CG-UCI is a first CG-UCI, and the boundary is a first boundary, and the method further includes: determining that the second CG-PUSCH spans a second time slot boundary between a third time slot and a fourth time slot; and based on determining that the number of symbols of a demodulation reference signal (DMRS) and a second CG-UCI to be transmitted is greater than the number of available symbols in the third time slot for transmitting the first part of the second CG-PUSCH, discarding the second CG-PUSCH.

[0268] Embodiment 14 may include the method according to embodiment 10 or some other embodiments herein, further comprising: encoding at least another portion of the information in the second part of the CG-PUSCH; and transmitting the second part of the CG-PUSCH in the second time slot.

[0269] Embodiment 15 may include a method according to embodiment 10 or some other embodiments herein, wherein the first part of the CG-PUSCH includes a first CG-UCI, which includes an indication of a first SLIV corresponding to a first length of the first part of the CG-PUSCH; the second part of the CG-PUSCH includes a second CG-UCI, which includes an indication of a second SLIV corresponding to a second length of the second part of the CG-PUSCH, and the length corresponding to the CG-PUSCH is equal to the sum of the first length and the second length.

[0270] Embodiment 16 may include a method according to embodiment 14 or some other embodiments herein, further comprising: based on determining that the available uplink resources in the first time slot are insufficient for the CG-UCI, encoding at least that portion of the information in the first part of the CG-PUSCH to include an authorization-based UCI that matches the available uplink resource rate.

[0271] Embodiment 17 includes a method for configured authorized transmission, the method comprising: determining that a micro-slot PUSCH is to cross a boundary between a first time slot and a second time slot; encoding a first part and a second part of the micro-slot PUSCH, wherein a CG-UCI corresponding to the micro-slot PUSCH is included in the first part or the second part; performing one or more listen-before-talk (LBT) operations; and transmitting the first part in the first time slot or transmitting the second part in the second time slot based on the performance of one or more LBT operations.

[0272] Embodiment 18 may include the method according to Embodiment 17 or some other embodiments herein, further comprising: mapping the CG-UCI to one of the first part or the second part having a relatively larger length.

[0273] Embodiment 19 may include the method described in accordance with Embodiment 17 or some other embodiments herein, further comprising: determining that a first LBT operation among one or more LBT operations is successful; and transmitting a first part in a first time slot and a second part in a second time slot based on the first LBT operation.

[0274] Embodiment 20 may include the method described in accordance with Embodiment 17 or some other embodiments herein, further comprising: based on determining that a first LBT operation among one or more LBT operations is unsuccessful, discarding the first part; and based on determining that a second LBT operation among the one or more LBT operations is successful, transmitting the second part.

[0275] Example 21 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Examples 1-20, or any other method or process described herein.

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

[0277] Embodiment 23 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1 to 20, or any other method or process described herein.

[0278] Embodiment 24 may include methods, techniques or processes described or related to any one of Embodiments 1 to 20, or parts or components thereof.

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

[0280] Embodiment 26 may include a signal as described or related to any one of Embodiments 1 to 20, or a portion or component thereof.

[0281] Embodiment 27 may include a datagram, information, element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or related to any one of Embodiments 1 to 20, or otherwise described in the present disclosure.

[0282] Embodiment 28 may include a signal encoded with data as described or associated with any one of Embodiments 1 to 20, or a portion or component thereof, or as otherwise described in this disclosure.

[0283] Embodiment 29 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU or message as described or associated with any of the above embodiments 1 to 64, or a portion or component thereof, or otherwise described in the present disclosure.

[0284] Embodiment 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, described in or related to any one of Embodiments 1 to 20.

[0285] Embodiment 31 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any one of Embodiments 1 to 20, or a portion thereof.

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

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

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

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

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

[0291] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. One or more storage media having instructions that, when executed by one or more processors, cause a user equipment UE to perform the following operations: determining that a configured grant-physical uplink shared channel CG-PUSCH is to be transmitted in a mini-slot including a time allocation spanning a slot boundary between a first slot and a second slot; selecting uplink control information UCI to include grant-based UCI or configured grant-uplink control information CG-UCI based on the mini-slot including the time allocation across the slot boundary; encoding at least a portion of the UCI in a first part of the CG-PUSCH to transmit the first part of the CG-PUSCH in the first time slot; as well as Encode at least another portion of the UCI in a second portion of the CG-PUSCH to transmit the second portion of the CG-PUSCH in the second time slot.

2. One or more storage media according to claim 1, wherein to select the UCI, the UE is configured to: select the UCI based on the mini-slot including the time allocation across the time slot boundary to include the grant-based UCI without the CG-UCI.

3. One or more storage media according to claim 1, wherein the instructions, when executed, further cause the UE to: encode multiple CG-PUSCHs of configured authorized CG bursts to be transmitted in corresponding multiple micro-time slots, wherein the CG-PUSCH to be transmitted in a micro-time slot that does not include a time allocation across a time slot boundary includes a corresponding CG-UCI, and the CG-PUSCH to be transmitted in a micro-time slot that does include a time allocation across a time slot boundary does not include a corresponding CG-UCI.

4. The one or more storage media of claim 1, wherein the CG-PUSCH is a first CG-PUSCH, the CG-UCI is a first CG-UCI, the mini-slot is a first mini-slot, and the instructions when executed further cause the UE to: A second CG-PUSCH to be transmitted in a second mini-slot is encoded, wherein the second CG-PUSCH includes a second CG-UCI including an indication of a start symbol and a length value SLIV for the second mini-slot.

5. One or more storage media according to claim 4, wherein the SLIV indicates that the second CG-PUSCH starts at a first orthogonal frequency division multiplexing (OFDM) symbol, wherein the second CG-PUSCH starts at a second OFDM symbol, and the second OFDM symbol is the number of OFDM symbols after the first OFDM symbol, wherein the number of OFDM symbols corresponds to the length of a listen-before-talk (LBT) gap starting at the first OFDM symbol.

6. One or more storage media according to claim 5, wherein the instructions, when executed, further cause the UE to: identify a configured SLIV for the second CG-PUSCH, wherein both the SLIV and the configured SLIV are used to indicate that the second CG-PUSCH is to start at the first OFDM symbol.

7. One or more storage media according to claim 4, wherein the SLIV indicates that the second CG-PUSCH starts at a first orthogonal frequency division multiplexing (OFDM) symbol, wherein the second CG-PUSCH starts at the first OFDM symbol, and a listen-before-talk (LBT) gap ends at a second OFDM symbol immediately before the first OFDM symbol.

8. The one or more storage media of claim 1, wherein the CG-PUSCH is a first CG-PUSCH, the CG-UCI is a first CG-UCI, the mini-slot is a first mini-slot, and the instructions when executed further cause the UE to: A second CG-PUSCH to be transmitted in a second mini-time slot is encoded, wherein the second CG-PUSCH includes a second CG-UCI, and the second CG-UCI includes an indication of the number of repetitions corresponding to the second CG-PUSCH.

9. One or more storage media according to any one of claims 1 to 8, wherein the instructions, when executed, further cause the UE to: determine the type or duration of the CG-PUSCH; and select the UCI to include the authorization-based UCI or the CG-UCI based on the type or duration of the CG-PUSCH.

10. A user equipment UE, comprising: A protocol processing circuit, wherein the protocol processing circuit is used for: identifying information to be transmitted in a configured grant-physical uplink shared channel CG-PUSCH, the information comprising grant-based uplink control information UCI or configured grant-uplink control information CG-UCI; Determine uplink resources for CG-PUSCH based on the start symbol and length value; Determining that the uplink resource is in a first time slot and a second time slot; as well as encoding at least a portion of the information in a first part of the CG-PUSCH; encoding at least another portion of the information in a second part of the CG-PUSCH; and a radio front end circuit coupled to the protocol processing circuit to: transmitting the first part of the CG-PUSCH in the first time slot; as well as The second part of the CG-PUSCH is transmitted in the second time slot.

11. The UE according to claim 10, wherein the protocol processing circuit is further configured to: truncate a second portion of the CG-PUSCH corresponding to uplink resources in the second time slot.

12. The UE according to claim 10, wherein the protocol processing circuit is further used to: map a demodulation reference signal DMRS to a first symbol corresponding to the start symbol, and map the CG-UCI to a second symbol immediately following the first symbol, wherein the first symbol and the second symbol are in the first time slot.

13. The UE according to claim 10, wherein the CG-PUSCH is a first CG-PUSCH, the CG-UCI is a first CG-UCI, and there is a first time slot boundary between the first time slot and the second time slot, and the protocol processing circuit is further configured to: Determining that the second CG-PUSCH spans a second time slot boundary between the third time slot and the fourth time slot; and Based on determining that the number of symbols of the second CG-UCI to be transmitted with the demodulation reference signal DMRS and the second CG-PUSCH is greater than the number of available symbols in the third time slot for transmitting the first part of the second CG-PUSCH, the second CG-PUSCH is discarded.

14. The UE according to claim 10, wherein the first part of the CG-PUSCH includes a first CG-UCI, the first CG-UCI includes a first start symbol corresponding to a first length of the first part of the CG-PUSCH and an indication of a length value SLIV; the second part of the CG-PUSCH includes a second CG-UCI, the second CG- The UCI includes an indication of a second SLIV corresponding to a second length of the second part of the CG-PUSCH, and the length corresponding to the CG-PUSCH is equal to the sum of the first length and the second length.

15. A UE according to claim 10, wherein the protocol processing circuit is further used to: based on determining that the available uplink resources in the first time slot are insufficient for CG-UCI, encode at least the portion of the information in the first part of the CG-PUSCH to include the authorization-based UCI that matches the available uplink resource rate.

16. A method of performing a configured authorization transmission, the method comprising: Determining that a mini-slot physical uplink shared channel PUSCH is to cross a boundary between a first time slot and a second time slot; encoding at least a portion of information in a first portion of the mini-slot PUSCH, wherein the information includes configured grant-uplink control information CG-UCI corresponding to the mini-slot PUSCH; encoding at least another portion of the information in a second portion of the mini-slot PUSCH; Perform one or more listen-before-speak (LBT) operations; as well as Based on the execution of the one or more LBT operations, it is determined whether to transmit the first part in the first time slot and whether to transmit the second part in the second time slot.

17. The method according to claim 16, further comprising: The CG-UCI is mapped to one of the first part or the second part having a relatively larger length.

18. The method according to claim 16, further comprising: Determining that a first LBT operation of the one or more LBT operations is successful; as well as The first portion is transmitted in the first time slot and the second portion is transmitted in the second time slot based on the first LBT operation.

19. The method according to claim 16, further comprising: discarding the first portion based on determining that a first LBT operation of the one or more LBT operations was unsuccessful; as well as Based on determining that a second LBT operation among the one or more LBT operations is successful, transmitting the second portion.