Systems and methods for multiplexing or cancelling overlapping ul transmissions

Abstract

The present disclosure provides systems and methods for multiplexing or cancelling overlapping UL transmissions. The present disclosure provides an apparatus comprising a processor circuit. The processor circuit is configured to determine that two or more UL transmissions overlap, determine whether at least one of the two or more UL transmissions is indicated to be cancelled, multiplex the at least one UL transmission with remaining UL transmissions of the two or more UL transmissions for transmission to an AN if the at least one UL transmission is not indicated to be cancelled, and cancel the at least one UL transmission if the at least one UL transmission is indicated to be cancelled. Other embodiments are also disclosed and claimed.

Description

[0001] Priority Statement

[0002] This application is based on and claims priority to U.S. Provisional Application No. 63 / 013,962, filed April 22, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Embodiments of this disclosure generally relate to the field of wireless communication, and more specifically, to systems and methods for multiplexing or canceling overlapping uplink (UL) transmissions. Background Technology

[0004] Mobile communications have evolved dramatically from early voice systems to today's highly complex integrated communication platforms. Next-generation wireless communication systems, fifth-generation (5G) or New Radio (NR), will provide information access and data sharing anytime, anywhere through various terminals and applications. NR promises to be a unified network / system designed to meet distinct and sometimes conflicting performance dimensions and services. These diverse, multi-dimensional needs are driven by different services and applications. Typically, NR can evolve based on the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE-Advanced) and other potential New Radio Access Technologies (RATs), enriching people's lives with better, simpler, and seamless wireless connectivity solutions. NR can enable everything wirelessly connected and deliver fast, rich content and services. Summary of the Invention

[0005] One aspect of this disclosure provides an apparatus comprising: a radio frequency (RF) interface; and processor circuitry coupled to the RF interface, wherein the processor circuitry is configured to: determine that two or more uplink (UL) transmissions overlap; determine whether at least one of the two or more UL transmissions is indicated to be cancelled; if the at least one UL transmission is not indicated to be cancelled, multiplex the at least one UL transmission with the remaining UL transmissions of the two or more UL transmissions for transmission to an access node (AN) via the RF interface; and if the at least one UL transmission is indicated to be cancelled, cancel the at least one UL transmission.

[0006] One aspect of this disclosure provides a method comprising: determining two or more uplink (UL) transmission overlaps; determining whether at least one of the two or more UL transmissions is indicated to be cancelled; if the at least one UL transmission is not indicated to be cancelled, multiplexing the at least one UL transmission with the remaining UL transmissions of the two or more UL transmissions for transmission to an access node (AN); and if the at least one UL transmission is indicated to be cancelled, cancelling the at least one UL transmission.

[0007] One aspect of this disclosure provides a computer-readable medium including instructions that, when executed, cause the above-described methods to be performed. Attached Figure Description

[0008] In the accompanying drawings, embodiments of the present disclosure will be illustrated by way of example rather than limitation, wherein like reference numerals refer to similar elements.

[0009] Figure 1 A communication system according to some embodiments of the present disclosure is shown.

[0010] Figure 2 A flowchart is shown illustrating a method for multiplexing or canceling overlapping UL transmissions according to some embodiments of this disclosure.

[0011] Figure 3 An example of overlap between one PUCCH transmission and more than one PUSCH transmission is shown according to some embodiments of the present disclosure.

[0012] Figure 4 Examples of using multiplexing / cancellation to handle overlapping PUCCH and PUSCH transmissions according to some embodiments of this disclosure are shown.

[0013] Figure 5 An example of overlap between more than one PUCCH transmission is shown according to some embodiments of this disclosure.

[0014] Figure 6 Examples of using multiplexing / cancellation to handle overlapping PUCCH transmissions according to some embodiments of this disclosure are shown.

[0015] Figure 7 Examples of overlap between SPS HARQ-ACK / SR PUCCH transmissions and two non-overlapping CSI PUCCH transmissions according to some embodiments of this disclosure are shown.

[0016] Figure 8Examples of using multiplexing / cancellation to handle overlapping SPS HARQ-ACK / SR PUCCH and CSI PUCCH transmissions according to some embodiments of this disclosure are shown.

[0017] Figure 9 This is a block diagram illustrating a component capable of reading instructions from a machine-readable or computer-readable medium and performing any one or more methods discussed herein, according to some example embodiments.

[0018] Figure 10 Networks according to various embodiments of this disclosure are shown.

[0019] Figure 11 Wireless networks according to various embodiments of this disclosure are illustrated schematically.

[0020] Figure 12 Example components of a device according to some embodiments of this disclosure are shown.

[0021] Figure 13 Examples of infrastructure devices according to various embodiments are shown. Detailed Implementation

[0022] Various aspects of the illustrative embodiments will be described using terminology commonly employed by those skilled in the art to convey the essence of this disclosure to others skilled in the art. However, it will be readily understood by those skilled in the art that many alternative embodiments can be practiced using portions of the described aspects. Specific figures, materials, and configurations are set forth for illustrative purposes to provide a thorough understanding of the illustrative embodiments. However, it will be readily understood by those skilled in the art that alternative embodiments can be practiced without these specific details. In other instances, well-known features may be omitted or simplified to avoid obscuring the illustrative embodiments.

[0023] Furthermore, the various operations will be described as multiple discrete operations in a manner most conducive to understanding the illustrative embodiments; however, the order of description should not be construed as implying that these operations must depend on the order. In particular, these operations do not need to be performed in the order presented.

[0024] The phrases “in an embodiment,” “in one embodiment,” and “in some embodiments” are used repeatedly throughout this document. These phrases do not typically refer to the same embodiment; however, they may refer to the same embodiment. Unless the context otherwise specifies, the terms “comprising,” “having,” and “including” are synonyms. The phrases “A or B” and “A / B” mean “(A), (B), or (A and B).”

[0025] Figure 1A communication system 100 according to some embodiments of the present disclosure is illustrated. The communication system 100 is shown as including a user equipment (UE) 101. The UE 101 may be a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks). However, it may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), tablet computer, pager, laptop computer, desktop computer, wireless handheld device, or any computing device including a wireless communication interface.

[0026] In some embodiments, UE 101 may include an Internet of Things (IoT) UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connectivity. The IoT UE may utilize technologies such as machine-to-machine (M2M), machine-type communication (MTC), enhanced MTC (eMTC), and narrowband IoT (NB-IoT) to exchange data with IoT servers or devices via public terrestrial mobile networks (PLMNs), proximity-based services (ProSe), device-to-device (D2D) communication, sensor networks, or IoT networks. M2M or MTC data exchange may be machine-initiated. The IoT network describes the interconnection of IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connectivity. The IoT UE may execute background applications (e.g., maintaining active messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0027] UE 101 can be configured to connect (e.g., communicatively coupled) to a radio access network (RAN) 110, which may be, for example, an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), a next-generation RAN (NG RAN), or some other type of RAN. UE 101 can operate in accordance with cellular communication protocols, such as Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, Cellular PTT (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP Long Term Evolution (LTE) protocol, 5G protocol, New Radio (NR) protocol, etc.

[0028] RAN 110 may include one or more access nodes (ANs). These ANs may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), etc., and may include ground stations (e.g., ground access points) or satellite stations providing coverage within a geographic area (e.g., a cell). Figure 1 As shown, for example, RAN 110 includes AN 111 and AN 112.

[0029] UE 101 can achieve communication coupling with RAN 110 by utilizing connection 103 with AN 111, such as Figure 1 As shown. Connection 103 can be implemented using one or more beams (not shown). A beam can indicate a spatial domain transmit and / or receive filter or a spatial relation; therefore, the terms “beam,” “spatial domain transmit and / or receive filter,” and “spatial relation” are interchangeable herein.

[0030] AN 111 and AN 112 can communicate with each other via X2 interface 113. AN 111 and AN 112 can be macro ANs, which can provide a larger coverage area. Alternatively, they can be femtocell ANs or picocell ANs, which can provide a smaller coverage area, smaller user capacity, or higher bandwidth compared to macro ANs. For example, one or both of AN 111 and AN 112 can be low-power (LP) ANs. In one embodiment, AN 111 and AN 112 can be ANs of the same type. In another embodiment, they are ANs of different types.

[0031] AN 111 can terminate the air interface protocol and can be the first point of contact for UE 101. In some embodiments, AN 111 and 112 can implement various logical functions of RAN 110, including but not limited to radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0032] According to some embodiments, UE 101 can be configured to communicate with AN 111 or other UEs via a multi-carrier communication channel using Orthogonal Frequency Division Multiplexing (OFDM) communication signals, based on various communication technologies such as, but not limited to, Orthogonal Frequency Division Multiple Access (OFDMA) communication technology (e.g., for downlink communication) or Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technology (e.g., for uplink and proximity-based service (ProSe) or sidelink communication), but the scope of the embodiments is not limited thereto. OFDM signals may include multiple orthogonal subcarriers.

[0033] In some embodiments, a downlink resource grid can be used for downlink transmission from AN 111 to UE 101, while uplink transmission can use a similar technique. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink for each time slot. This time-frequency plane representation is common practice in OFDM systems, making radio resource allocation intuitive. Each column and 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 comprises multiple resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements. In the frequency domain, this can represent the minimum amount of resources that can currently be allocated. Several different physical downlink channels exist that are transmitted using such resource blocks.

[0034] Downlink channels can include the Physical Downlink Shared Channel (PDSCH) and the Physical Downlink Control Channel (PDCCH).

[0035] The PDSCH can carry user data and higher-layer signaling to UE 101. The PDCCH can carry information about the transmission format and resource allocation related to the PDSCH channel. It can also inform UE 101 about the transmission format, resource allocation, and Hybrid Automatic Repeat Request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UE 101 within the cell) can be performed at AN 111 based on channel quality information fed back from UE 101. Downlink resource allocation information for (e.g., allocated to) UE 101 can be transmitted on the PDCCH.

[0036] PDCCH can use Control Channel Elements (CCEs) to transmit control information. Before mapping to resource elements, PDCCH complex-valued symbols are first organized into quadruplets, which are then permuted using a sub-block interleaver for rate matching. Each PDCCH can be transmitted using one or more of these CCEs, where each CCE can correspond to nine groups of physical resource elements (called a resource element group (REG)), each group consisting of four physical resource elements. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. The number of CCEs used to transmit PDCCH depends on the size of the downlink control information (DCI) and channel conditions. In LTE, there may be four or more different PDCCH formats with different numbers of CCEs (e.g., aggregation levels, L = 1, 2, 4, or 8).

[0037] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the concepts described above. For example, some embodiments may use an Enhanced Physical Downlink Control Channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more Enhanced Control Channel Elements (ECCEs). Similar to the above, each ECCE may correspond to nine sets of physical resource elements (referred to as an Enhanced Resource Element Group (EREG)), with each group comprising four physical resource elements. In some cases, an ECCE may have a different number of EREGs.

[0038] The uplink channel may include the Physical Uplink Shared Channel (PUSCH) and the Physical Uplink Control Channel (PUCCH). The PUSCH can carry user data and control information to one or more ANs, and the PUCCH can carry control information to one or more ANs.

[0039] RAN 110 is shown communicatively coupled to core network (CN) 120 via S1 interface 114. In some embodiments, CN 120 may be an evolved packet core (EPC) network, a NextGen packet core (NPC) network, or other types of CN. In one embodiment, S1 interface 114 is divided into two parts: S1-Mobility Management Entity (MME) interface 115, which is the signaling interface between AN 111 and 112 and MME 121; and S1-U interface 116, which carries service data between AN 111 and 112 and Serving Gateway (S-GW) 122.

[0040] In one embodiment, CN 120 may include MME 121, S-GW 122, Packet Data Network (PDN) Gateway (P-GW) 123, and Home Subscriber Server (HSS) 124. MME 121 may functionally resemble the control plane of a legacy General Packet Radio Service (GPRS) Support Node (SGSN). MME 121 may manage mobility aspects of access, such as gateway selection and tracking area list management. HSS 124 may include a database for network users, including subscription-related information to support network entities in handling communication sessions. CN 120 may include one or more HSS 124s, depending on the number of mobile subscribers, device capacity, network organization, etc. For example, HSS 124 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc.

[0041] S-GW 122 can terminate S1 interface 114 toward RAN 110 and route data packets between RAN 110 and CN 120. Furthermore, S-GW 122 can serve as a local mobility anchor point for inter-AN handovers and can also provide anchoring for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0042] P-GW 123 can terminate the SGi interface toward the PDN. P-GW 123 can route data packets between CN 120 and external networks, such as a network including an application server (AS) 130 (or application function (AF)). Typically, application server 130 can be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). In one embodiment, P-GW 123 is communicatively coupled to application server 130 via an IP communication interface. Application server 130 can also be configured to support one or more communication services of UE 101 (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) via CN 120.

[0043] P-GW 123 can also be responsible for policy enforcement and charging data collection. The Policy and Charging Rule Function (PCRF) 126 is the policy and charging control element of CN 120. In non-roaming scenarios, a single PCRF may exist in the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In roaming scenarios with local traffic bursts, two PCRFs may exist associated with the UE's IP-CAN session: the Home PCRF (H-PCRF) within the HPLMMN and the Access PCRF (V-PCRF) in the Access Public Land Mobile Network (VPLMN). PCRF 126 can be communicatively coupled to application server 130 via P-GW 123. Application server 130 can signal PCRF 126 to indicate new service flows and select appropriate Quality of Service (QoS) and charging parameters. PCRF 126 can provide the rule to the Policy and Charging Enforcement Function (PCEF) (not shown) using an appropriate Service Flow Template (TFT) and QoS Class Identifier (QCI), which begins with the QoS and charging specified by the application server 130.

[0044] Figure 1 The number of devices and / or networks shown is for illustrative purposes only. In reality, there may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or [other types of networks]. Figure 1The devices and / or networks shown are compared to devices and / or networks with different configurations. Optionally or additionally, one or more devices of system 100 may perform one or more functions described as being performed by other devices of system 100. Furthermore, although Figure 1 The diagram shows "direct" connections, but these connections should be interpreted as logical communication paths. Furthermore, in practice, one or more intermediate devices (e.g., routers, gateways, modems, switches, hubs, etc.) may be present.

[0045] Enhanced mobile broadband (eMBB) and ultra-reliable low-latency communications (URLCC) are two important service types in NR systems. They have very different requirements regarding user plane latency and required coverage. For example, for the critical requirements of URLCC related to user plane latency and reliability, the target user plane latency for both UL and downlink (DL) is 0.5 ms, and the reliability target is 1x10 within 1 ms. -5 .

[0046] In NR, uplink control information (UCI) can be carried by either PUCCH or PUSCH. Specifically, UCI can include scheduling requests (SR), hybrid automatic repeat request acknowledgment (HARQ-ACK) feedback, channel state information (CSI) reports (e.g., channel quality indicator (CQI), precoding matrix indicator (PMI), CSI resource indicator (CRI), and rank indicator (RI), and / or beam-related information (e.g., Layer 1-reference signal received power (L1-RSRP)). CSI reports can be periodic, semi-permanent, or aperiodic. Aperiodic CSI reports can be triggered by UL scheduling DCI and can be carried in the PUSCH. Alternatively, non-periodic CSI reports can be triggered by the DL-scheduled DCI and can be carried in the PUCCH. The PUSCH carries UL data transmissions, which can be scheduled by the DCI or not (e.g., with configuration permission). Other UL transmissions include probe reference signal (SRS) transmissions for UL channel sensing, which can be periodic, semi-permanent, or non-periodic. Non-periodic SRS can be triggered by the UL-scheduled DCI, the DL-scheduled DCI, or a group common DCI. Data communication within the UL can take place in a PUSCH with dynamic permission or configuration permission.

[0047] This disclosure provides a mechanism for handling conflicts in overlapping UL transmissions.

[0048] At a given time, an NR UE may have multiple overlapping UL transmissions. One or more overlapping UL transmissions may be semi-statically configured, such as a configuration-granted PUSCH transmission, a PUCCH transmission carrying a periodic or semi-permanent CSI, or a PUCCH transmission carrying a semi-permanent scheduling (SPS) HARQ-ACK. One or more overlapping UL transmissions may be dynamically scheduled, such as a PUSCH based on dynamic UL grants, or a PUCCH carrying a HARQ-ACK corresponding to a PDSCH scheduled by dynamic DL grants. The UE may multiplex one or more overlapping UL transmissions. For example, a HARQ-ACK may be multiplexed with a PUSCH or with another HARQ-ACK in a PUCCH. For example, SR and / or CSI may be multiplexed with a HARQ-ACK in a PUCCH. This disclosure is not limited in this respect.

[0049] When control information is multiplexed onto a PUCCH, the PUCCH carrying the multiplexed information can be the same as or different from one of the original PUCCHs (which can carry HARQ-ACK, CSI, or SR). Between overlapping UL transmissions, one or more UL transmissions may need to be cancelled, so the UE may need to determine the order of operations involving overlapping UL channels, for example, whether to multiplex first and then cancel, or vice versa.

[0050] In some embodiments, the UE may receive a cancellation indication (e.g., a separate indication) via DCI or higher-level signaling to cancel one or more overlapping UL transmissions, such as semi-statically configured transmissions(one or more). In one example, the DCI carrying the cancellation indication may be DCI format 2_0 indicating a slot format indication (SFI). In one example, DCI format 2_0 is received after a DCI that triggers a PUCCH transmission in two or more UL transmissions.

[0051] In some embodiments, the UE may identify overlapping UL transmissions (e.g., semi-static UL channels) to be cancelled based on predefined rules, which will be described in detail below.

[0052] In one embodiment, the cancellation of a UL transmission can be indicated when at least one symbol in a set of symbols for a UL transmission is indicated as a DL symbol or a flexible symbol. This can be indicated by a semi-static time-division duplex (TDD) DL / UL configuration. In one example, at least one symbol in the set is scheduled for a DL transmission via a DCI that schedules DL transmissions. In another example, at least one symbol in the set is indicated as a DL symbol via an RRC for slot format configuration. In yet another example, at least one symbol in the set is indicated as a DL symbol or a flexible symbol via an SFI (e.g., via DCI format 2_0).

[0053] In one embodiment, when at least one of the symbols in a set of symbols used for UL transmission is configured for Synchronization Signal Block (SSB) transmission, for example via RRC signaling, this may indicate that the UL transmission is to be cancelled.

[0054] In one embodiment, the UL transmission can be cancelled if the UE does not receive an SFI after a first time period starting from the last symbol of the control resource set (CORESET) for the SFI, and at least one symbol in the set of symbols used for UL transmission is indicated as a flexible symbol. The first time period can be T2, which is predefined or configured by DCI or higher-level signaling. For example, T2 can be the minimum PUSCH preparation time, as marked as T in Section 6 of 3GPP TS 38.214V16.1.0 (2020-03) (3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 16)). proc,2 That way.

[0055] In one embodiment, when a UL transmission includes a Configured-Grant (CG) PUSCH transmission that overlaps with a Downlink-Grant (DG) PUSCH transmission, and the scheduling DCI for the CG PUSCH transmission and the scheduling DCI for the DG PUSCH transmission are at least separated by a second time period, this can indicate that the UL transmission is to be cancelled. The second time period can be N2, which is predefined or configured by the DCI or higher-level signaling. For example, N2 can be the PUSCH timing capability reported by the UE (see Section 6 of TS 38.214) and depends at least on the SCS of the PUSCH.

[0056] In one embodiment, when a UL transmission includes a CG PUSCH transmission having the same HARQ process number as a DG PUSCH transmission, and the scheduling DCI for the CG PUSCH transmission and the scheduling DCI for the DG PUSCH transmission are at least three time intervals apart, it can be indicated that the UL transmission is to be cancelled. The third time interval can be N2, which is predefined or configured by the DCI or higher-level signaling. For example, N2 can be the PUSCH timing capability reported by the UE (see Section 6 of TS38.214) and depends at least on the SCS of the PUSCH.

[0057] Figure 2 A flowchart of a method 200 for multiplexing or canceling overlapping UL transmissions according to some embodiments of the present disclosure is shown. Method 200 can be performed by a UE and includes steps 210, 220, 230, and 240.

[0058] At 210, two or more UL transmissions are identified as overlapping.

[0059] At 220, determine whether at least one of two or more UL transmissions is indicated as to be cancelled.

[0060] At 230, if the at least one UL transmission is not indicated as to be cancelled, it is multiplexed with the remaining UL transmissions from two or more UL transmissions to be transmitted to the AN, for example, gNB.

[0061] At 240, if at least one UL transmission is indicated to be cancelled, it is cancelled.

[0062] As described above, two or more UL transmissions may include one or more PUCCH transmissions and / or one or more PUSCH transmissions. In some embodiments, when the UE determines that PUCCH and / or PUSCH transmissions (where at least one transmission is a semi-statically configured PUCCH and / or PUSCH transmission) overlap, the UE determines to transmit a PUCCH after multiplexing the overlapping PUCCH, or to transmit a PUSCH after multiplexing the overlapping PUCCH and PUSCH, if the PUCCH or PUSCH to be transmitted will not be canceled. Otherwise, the UE does not multiplex one or more UL transmissions in the PUCCH or PUSCH, cancels the PUCCH or PUSCH, and transmits the remaining one or more UL transmissions that have not been indicated to be canceled.

[0063] In some embodiments, the above mechanism is applied only when the overlapping UL transmission includes more than one PUSCH transmission such that the UCI from the overlapping PUCCH is multiplexed in the PUSCH transmission.

[0064] In some embodiments, the above mechanism is applied only when the overlapping UL transmission includes a single PUSCH transmission such that the UCI is multiplexed in the PUSCH.

[0065] In some embodiments, overlapping PUSCH or PUCCH transmissions further include PUSCH or PUCCH transmissions with repetition, respectively.

[0066] In some embodiments, overlapping UL transmissions may overlap in one or more symbols. In some embodiments, subsets of overlapping UL transmissions may overlap in pairs. In some embodiments, subsets of overlapping UL transmissions may overlap with each other (e.g., they may have mutual temporal overlap).

[0067] In some embodiments, two or more overlapping UL transmissions may include at least one PUCCH transmission and at least two PUSCH transmissions. If the first PUSCH transmission among the at least two PUSCH transmissions is not indicated as to be cancelled, the UE may multiplex the PUCCH transmission from at least one PUCCH transmission in the first PUSCH transmission. Otherwise, if the first PUSCH transmission is indicated as to be cancelled, the UE may multiplex the PUCCH transmission from at least one PUCCH transmission in the second PUSCH transmission if the second PUSCH transmission among the at least two PUSCH transmissions is not indicated as to be cancelled. Otherwise, if all PUSCH transmissions among the at least two PUSCH transmissions are indicated as to be cancelled, the UE may encode the PUCCH transmissions from at least one PUCCH transmission for transmission to the AN.

[0068] In these embodiments, the first PUSCH transmission precedes the second PUSCH transmission in the time domain; the first PUSCH transmission has a lower component carrier (CC) index than the second PUSCH transmission; and / or the first PUSCH transmission is dynamically scheduled, and the second PUSCH transmission is configured to be permitted.

[0069] In one example, a PUCCH transmission overlaps with more than one PUSCH transmission in a time slot, and the first PUSCH transmission is indicated to be canceled. In this example, UCI can be multiplexed on the second PUSCH transmission if the first PUSCH transmission precedes the second PUSCH transmission, or if the first PUSCH transmission has a lower CC index than the second PUSCH transmission, or if the first PUSCH transmission is based on dynamic scheduling and the second PUSCH transmission is configured to be permitted. Alternatively, both the PUCCH transmission and the first PUSCH transmission can be discarded, and the UE can transmit only the second PUSCH transmission.

[0070] Figure 3An example of overlap between one PUCCH transmission and more than one PUSCH transmission is shown according to some embodiments of the present disclosure. Figure 4 Examples of using multiplexing / cancellation to handle overlapping PUCCH and PUSCH transmissions according to some embodiments of this disclosure are shown. In other words, Figure 3 and Figure 4 The overlap between processing a PUCCH and more than one PUSCH before and after the multiplexing / cancellation operation is shown respectively.

[0071] In the attached diagram, D represents the downlink symbol, F represents the flexible symbol, and U represents the uplink symbol.

[0072] like Figure 3 and Figure 4 As shown, based on the above mechanism, as indicated in the semi-static TDD DL / UL configuration, since the first CG PUSCH is indicated to be canceled due to a conflict with the DL direction, the UE can multiplex the UCI of the overlapping PUCCH transmission on the second CG PUSCH and discard the first CG PUSCH and PUCCH transmissions.

[0073] In some embodiments, overlapping UL transmissions may include at least two PUCCH transmissions. If the first PUCCH transmission of the at least two PUCCH transmissions is indicated to be cancelled, the UE may cancel the first PUCCH transmission and the remaining PUCCH transmissions of the at least two PUCCH transmissions that are in the same resource set as the first PUCCH transmission. This resource set is used for non-repeating PUCCH transmissions in a single time slot. For example, this resource set may be the resource set Q defined in Section 9.2.5 of 3GPP TS 38.213V16.1.0 (2020-03) (3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 16)).

[0074] In one example, the UE determines that multiple PUCCH resources used for UCI multiplexing overlap, satisfying the timeline requirements defined in Section 9.2.5 of TS38.213. When the UE determines a new PUCCH resource after executing pseudo-code as defined in Section 9.2.5 of TS38.213, if the determined new PUCCH resource is indicated to be cancelled, the UE can cancel the transmission of the determined new PUCCH and one or more overlapping PUCCH transmissions in resource set Q as defined in Section 9.2.5. In some cases, this mechanism applies to each resource set Q when pseudo-code is executed.

[0075] Figure 5 An example of overlap between more than one PUCCH transmission is shown according to some embodiments of this disclosure. Figure 6 Examples of using multiplexing / cancellation to handle overlapping PUCCH transmissions according to some embodiments of this disclosure are shown. In other words, Figure 5 and Figure 6 The overlapping of processing more than one PUCCH transmission before and after multiplexing / cancellation is shown respectively.

[0076] exist Figure 5 and Figure 6 In the example, the timeline requirements defined in Section 9.2.5 of TS38.213 are met, and a new PUCCH resource is determined after the pseudocode defined in Section 9.2.5 of TS38.213 is executed. As indicated in the semi-static TDDDL / UL configuration, if due to a new PUCCH resource (e.g., as...) Figure 6 If the dynamic HARQ-ACK+CSI shown conflicts with the DL direction and is indicated to be cancelled, the UE can cancel the new PUCCH resource and one or more overlapping PUCCH resources in resource set Q (e.g., such as...). Figure 5 and Figure 6 The dynamic HARQ-ACK and CSI shown are illustrated.

[0077] In some embodiments, overlapping UL transmissions include a first PUCCH transmission, a second PUCCH transmission, and a third PUCCH transmission, which reside in the same resource set for non-repeating PUCCH transmissions within a single time slot. The first PUCCH transmission overlaps with both the second and third PUCCH transmissions, but the second and third PUCCH transmissions do not overlap. If the second PUCCH transmission is indicated to be cancelled and the third PUCCH transmission is not indicated to be cancelled, the first PUCCH transmission may be multiplexed within the third PUCCH transmission.

[0078] Figure 7Examples of overlap between SPS HARQ-ACK / SR PUCCH transmissions and two non-overlapping CSI PUCCH transmissions according to some embodiments of this disclosure are shown. Figure 8 Examples of using multiplexing / cancellation to handle overlapping SPS HARQ-ACK / SR PUCCH and CSI PUCCH transmissions according to some embodiments of this disclosure are shown. Figure 7 and Figure 8 The diagram illustrates the processing of overlap between SPS HARQ-ACK / SR and two non-overlapping CSI PUCCHs before and after multiplexing / cancellation. Based on the above mechanism, as indicated in the semi-static TDD DL / UL configuration, a higher-priority CSI PUCCH resource is indicated as to be cancelled due to a conflict with the DL direction. Therefore, the UE can multiplex SPS HARQ-ACK / SR on a lower-priority CSI PUCCH resource, discarding both the PUCCH carrying the higher-priority CSI and the PUCCH carrying SPS HARQ-ACK / SR.

[0079] In some embodiments, overlapping UL transmissions include a first PUCCH transmission and a second PUCCH transmission. If the first PUCCH transmission is not indicated as to be cancelled, the second PUCCH transmission may be multiplexed within the first PUCCH transmission to obtain a fourth PUCCH transmission. If the resulting fourth PUCCH transmission is not indicated as to be cancelled, the fourth PUCCH transmission may be sent to the AN. If the fourth PUCCH transmission is indicated as to be cancelled, the fourth PUCCH transmission may be cancelled.

[0080] For example, when the UE determines that PUCCH transmissions overlap, where at least one PUCCH transmission is semi-statically configured, and the overlapping PUCCH transmissions include a first group of PUCCHs and a second group of PUCCHs, the UE receives the following indication: UL transmissions in one or more symbols will be canceled or not allowed.

[0081] In this scenario, in one option, the UE may transmit a PUCCH after multiplexing the first set of overlapping PUCCH transmissions, wherein the PUCCH does not overlap with one or more symbols indicated to be cancelled. The UE does not include a second set of PUCCH in the multiplexing because a PUCCH multiplexed from both the first and second sets would overlap with one or more UL symbols indicated to be cancelled. The UE may then transmit the remaining one or more PUCCH transmissions that were not indicated to be cancelled and were not multiplexed.

[0082] In another option, if the resulting PUCCH resources inevitably overlap with one or more symbols that may require cancellation of UL transmissions, the UE does not multiplex the first or second set of PUCCHs in the PUCCH. The UE may then transmit the remaining one or more PUCCH transmissions that are not indicated as to be cancelled.

[0083] In another option, if the resulting PUCCH resources inevitably overlap with one or more symbols that may require cancellation of UL transmissions, the UE does not multiplex the first or second set of PUCCHs in the PUCCH. In this case, the UE can cancel all overlapping PUCCHs and their corresponding UCIs.

[0084] In other words, even if the original PUCCH before multiplexing does not overlap with one or more symbols that may require the cancellation of UL transmission, the UE can determine whether the PUCCH generated due to multiplexing overlaps with one or more such symbols.

[0085] In some embodiments, the overlapping UL transmissions in this disclosure may include at least one semi-statically configured UL transmission. All of the above multiplexing / cancellation mechanisms may be applied to these embodiments. This disclosure is not limited in this respect.

[0086] In some embodiments, all of the above multiplexing / cancellation mechanisms may be applied to situations where at least one semi-statically configured PUCCH and / or PUSCH transmission is indicated to be cancelled. This disclosure is not limited in this respect.

[0087] By utilizing the mechanisms for multiplexing or canceling overlapping UL transmissions described in this disclosure, multiplexing and / or cancellation can be determined based on whether one or more symbols used for the UL transmission are indicated as canceled. This improves spectral efficiency and enhances resource management flexibility.

[0088] Figure 9 This is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more methods discussed herein, according to some example embodiments. Specifically, Figure 9 A schematic representation of hardware resource 900 is shown, which includes 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 can be communicatively coupled via bus 940. Hardware resource 900 may be part of a UE, AN, or LMF. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 902 may be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resource 900.

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

[0090] The memory / storage device 920 may include main memory, disk storage, 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 dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage devices, etc.

[0091] Communication resource 930 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 904 or one or more databases 906 via network 908. For example, communication resource 930 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth components (e.g., Bluetooth Low Energy), Wi-Fi components, and other communication components.

[0092] Instructions 950 may include software, programs, applications, applets, or other executable code for causing at least any processor 910 to perform any one or more of the methods discussed herein. Instructions 950 may reside wholly or partially within processor 910 (e.g., within the processor's buffer memory), memory / storage device 920, or any suitable combination thereof. Furthermore, any portion of instructions 950 may be transferred from any combination of peripheral device 904 or database 906 to hardware resource 900. Therefore, the memories of processor 910, memory / storage device 920, peripheral device 904, and database 906 are examples of computer-readable and machine-readable media.

[0093] Figure 10 Illustrations of a network 1000 according to various embodiments of the present disclosure are shown. The network 1000 can operate in a manner consistent with the 3GPP technical specifications of LTE or 5G / NR systems. However, the exemplary embodiments are not limited in this respect, and the described embodiments can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, etc.

[0094] Network 1000 may include UE 1002, which may include any mobile or non-mobile computing device designed to communicate with RAN 1004 via an over-the-air connection. UE 1002 may be, but is not limited to, smartphones, tablets, wearable computing devices, desktop computers, laptops, in-vehicle infotainment devices, in-vehicle entertainment devices, instrument clusters, head-up displays, in-vehicle diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M or D2D devices, Internet of Things devices, etc.

[0095] In some embodiments, network 1000 may include multiple UEs that are directly coupled to each other via sidelink interfaces. The UEs may be M2M / D2D devices that communicate using physical sidelink channels (e.g., but not limited to, physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), physical sidelink basic channel (PSFCH), etc.).

[0096] In some embodiments, UE 1002 can also communicate with AP 1006 via an over-the-air connection. AP 1006 manages WLAN connections and can be used to offload some / all network traffic from RAN 1004. The connection between UE 1002 and AP 1006 can be consistent with any IEEE 802.13 protocol, wherein AP 1006 can be Wireless Fibre. Router. In some embodiments, UE 1002, RAN 1004, and AP 1006 may utilize cellular WLAN aggregation (e.g., LTE-WLAN aggregation (LWA) / Lightweight IP (LWIP)). Cellular WLAN aggregation may involve UE 1002, configured by RAN 1004, utilizing both cellular radio resources and WLAN resources.

[0097] RAN 1004 may include one or more access nodes, such as AN 1008. AN 1008 can terminate the air interface protocol of UE 1002 by providing access layer protocols including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Media Access Control (MAC), and L1 protocol. In this way, AN 1008 enables data / voice connectivity between CN 1020 and UE 1002. In some embodiments, AN 1008 may be implemented in a discrete device or as one or more software entities running on a server computer as part of, for example, a virtual network, which may be referred to as CRAN or a virtual baseband unit pool. AN 1008 may be referred to as a base station (BS), gNB, RAN node, evolved Node B (eNB), next-generation eNB (ng-eNB), Node B (NodeB), roadside unit (RSU), TRxP, TRP, etc. AN 1008 can be a macro cell base station or a low-power base station, used to provide micro cells, pico cells, or other similar cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macro cells.

[0098] In embodiments where RAN 1004 includes multiple ANs, they can be coupled to each other via an X2 interface (in the case of RAN 1004 being an LTE RAN) or an Xn interface (in the case of RAN 1004 being a 5G RAN). In some embodiments, the X2 / Xn interfaces, which can be separated into a control plane interface and a user plane interface, can allow ANs to transmit and handover, data / context transfer, mobility, payload management, interference coordination, and other related information.

[0099] The AN of RAN 1004 can manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE 1002. UE 1002 can simultaneously connect to multiple cells provided by the same or different ANs of RAN 1004. For example, UE 1002 and RAN 1004 can use carrier aggregation to allow UE 1002 to connect to multiple component carriers, each component carrier corresponding to a primary cell (Pcell) or a secondary cell (Scell). In a dual connectivity scenario, the first AN can be the primary node providing the primary cell group (MCG), and the second AN can be the secondary node providing the secondary cell group (SCG). The first / second AN can be any combination of eNB, gNB, ng-eNB, etc.

[0100] RAN 1004 can provide an air interface on either licensed or unlicensed spectrum. For operation in unlicensed spectrum, nodes can use Licensed Assisted Access (LAA), Enhanced LAA (eLAA), and / or further enhanced LAA (feLAA) mechanisms based on carrier aggregation (CA) technology with PCell / Scell. Before accessing unlicensed spectrum, nodes can perform medium / carrier sensing operations based on, for example, a Listen-Before-Speak (LBT) protocol.

[0101] In a vehicle-to-everything (V2X) scenario, UE 1002 or AN 1008 can be or act as a roadside unit (RSU), which can refer to any transportation infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE can be referred to as a "UE-type RSU"; an RSU implemented in or by an eNB can be referred to as an "eNB-type RSU"; an RSU implemented in or by a next-generation NodeB (gNB) can be referred to as a "gNB-type RSU"; and so on. In one example, the RSU is a computing device coupled to radio frequency circuitry located on the roadside, providing connectivity support to passing vehicle UEs. 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 can provide very low-latency communication required for high-speed events, such as collision avoidance, traffic warnings, etc. Alternatively or additionally, the RSU can provide other cellular / WLAN communication services. RSU components can be enclosed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide wired connectivity (e.g., Ethernet) to traffic signal controllers or backhaul networks.

[0102] In some embodiments, RAN 1004 may be LTE RAN 1010, which includes an evolved Node B (eNB), such as eNB 1012. LTE RAN 1010 can provide an LTE air interface with the following characteristics: 15kHz SCS; CP-OFDM waveforms for DL ​​and SC-FDMA waveforms for UL; turbo codes for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; rely on PDSCH / PDCCH demodulation reference signals (DMRS) for PDSCH / PDCCH demodulation; and rely on CRS for cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface can operate in the sub-6GHz band.

[0103] In some embodiments, RAN 1004 may be a next-generation (NG)-RAN 1014 with a gNB (e.g., gNB 1016) or a gn-eNB (e.g., ng-eNB 1018). gNB 1016 can connect to a 5G-enabled UE using a 5G NR interface. gNB 1016 can connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. Ng-eNB 1018 can also connect to the 5G core via an NG interface, but can connect to the UE via an LTE air interface. gNB 1016 and ng-eNB 1018 can connect to each other via an Xn interface.

[0104] In some embodiments, the NG interface can be divided into two parts: the NG user plane (NG-U) interface and the NG control plane (NG-C) interface. The former carries traffic data between the nodes of NG-RAN 1014 and UPF 1048, while the latter is the signaling interface (e.g., N2 interface) between NG-RAN 1014 and the nodes of Access and Mobility Management Function (AMF) 1044.

[0105] NG-RAN 1014 can provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polarity, repetition, simplex, and Reed-Muller codes for control, and LDPC for data. The 5G-NR air interface can rely on CSI-RS, PDSCH / PDCCH DMRS similar to those of the LTE air interface. The 5G-NR air interface may not use CRS, but can use PBCH DMRS for PBCH demodulation; PTRS for PDSCH phase tracking; and a tracking reference signal for time tracking. The 5G-NR air interface can operate on the FR1 band, including the sub-6GHz band, or the FR2 band, including the 24.25GHz to 52.6GHz band. The 5G-NR air interface may include an SSB, which is an area of ​​the downlink resource grid including PSS / SSS / PBCH.

[0106] In some embodiments, the 5G-NR air interface can use BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For instance, UE 1002 can be configured with multiple BWPs, each configured with a different SCS. When a BWP is indicated to UE 1002 for a change, the transmitted SCS also changes. Another use case for BWPs relates to power saving. Specifically, multiple BWPs with different numbers of frequency resources (e.g., PRBs) can be configured for UE 1002 to support data transmission under different traffic load scenarios. A BWP containing fewer PRBs can be used for data transmission with lower traffic loads, while allowing power saving at UE 1002 and, in some cases, at gNB 1016. A BWP containing more PRBs can be used for scenarios with higher traffic loads.

[0107] RAN 1004 is communicatively coupled to CN 1020, which includes network elements, to provide various functions supporting data and telecommunications services to customers / subscribers (e.g., users of UE 1002). Components of CN 1020 may be implemented in a single physical node or in different physical nodes. In some embodiments, NFV may be used to virtualize any or all of the functionality provided by the network elements of CN 1020 onto physical computing / storage resources such as servers, switches, etc. A logical instance of CN 1020 may be referred to as a network slice, and a logical instantiation of a portion of CN 1020 may be referred to as a network subslice.

[0108] In some embodiments, CN 1020 may be LTE CN 1022, which may also be referred to as the Evolved Packet Core (EPC). LTE CN 1022 may include a Mobility Management Entity (MME) 1024, a Serving Gateway (SGW) 1026, a Serving GPRS Support Node (SGSN) 1028, a Home Subscriber Server (HSS) 1030, a Proxy Gateway (PGW) 1032, and a Policy Control and Charging Rules Function (PCRF) 1034, as shown in the figure. These components are coupled to each other through interfaces (or "reference points"). The functions of the elements of LTE CN 1022 can be briefly described below.

[0109] MME 1024 can implement mobility management functions to track the current location of UE 1002, thereby facilitating patrol, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0110] The SGW 1026 can terminate the S1 interface toward the RAN and route data packets between the RAN and the LTE CN 1022. The SGW 1026 can serve as a local mobility anchor for handover between RAN nodes and can also provide anchoring for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0111] SGSN 1028 can track the location of UE 1002 and perform security functions and access control. Additionally, SGSN 1028 can perform EPC inter-node signaling for mobility between different RAT networks; PDN and S-GW selection specified by MME 1024; MME selection for handover, etc. The S3 reference point between MME 1024 and SGSN 1028 enables the exchange of user and bearer information for 3GPP indirect network access mobility in idle / active states.

[0112] The HSS 1030 may include a database for network users, containing subscription-related information that supports network entities in handling communication sessions. The HSS 1030 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 1030 and the MME 1024 enables the transmission of subscription and authentication data to authenticate / authorize user access to the LTE CN 1020.

[0113] PGW 1032 can terminate the SGi interface toward a data network (DN) 1036, which may include an application / content server 1038. PGW 1032 can route data packets between the LTE CN 1022 and the data network 1036. PGW 1032 can be coupled to SGW 1026 via an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 1032 may also include nodes for policy enforcement and charging data collection (e.g., PCEF). Additionally, the SGi reference point between PGW 1032 and the data network 1036 can be, for example, an external public or private PDN or an internal packet data network for providing IMS services. PGW 1032 can be coupled to PCRF 1034 via a Gx reference point.

[0114] PCRF 1034 is the policy and charging control element of LTE CN 1022. PCRF 1034 can be communicatively coupled to application / content server 1038 to determine appropriate QoS and charging parameters for service flows. PCRF 1032 can provide the associated rules to PCEF (via Gx reference point) with appropriate TFT and QCI.

[0115] In some embodiments, CN 1020 may be a 5G core network (5GC) 1040. 5GC 1040 may include an Authentication Server Function (AUSF) 1042, Access and Mobility Management Function (AMF) 1044, Session Management Function (SMF) 1046, User Plane Function (UPF) 1048, Network Slice Selection Function (NSSF) 1050, Network Open Function (NEF) 1052, Network NF Storage Function (NRF) 1054, Policy Control Function (PCF) 1056, Unified Data Management (UDM) 1058, and Application Function (AF) 1060, as shown in the figure. These functions are coupled to each other through interfaces (or "reference points"). The functions of the components of 5GC 1040 can be briefly described below.

[0116] The AUSF 1042 can store data for UE 1002 authentication and handle authentication-related functions. The AUSF 1042 facilitates a common authentication framework for various access types. In addition to communicating with other components of the 5GC 1040 via a reference point, as shown in the figure, the AUSF 1042 can also demonstrate an interface based on Nausf services.

[0117] AMF 1044 allows other functions of 5GC 1040 to communicate with UE 1002 and RAN 1004 and subscribe to notifications regarding mobility events for UE 1002. AMF 1044 can handle registration management (e.g., registering UE 1002), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. AMF 1044 can provide the transmission of Session Management (SM) messages between UE 1002 and SMF 1046 and acts as a transparent broker for routing SM messages. AMF 1044 can also provide the transmission of SMS messages between UE 1002 and the SMSF. AMF 1044 can interact with AUSF 1042 and UE 1002 to perform various security anchoring and context management functions. Furthermore, AMF 1044 can be the termination point of the RANCP interface, which may include or be the N2 reference point between RAN 1004 and AMF 1044; AMF 1044 can serve as the termination point for NAS (N1) signaling and perform NAS encryption and integrity protection. AMF 1044 can also support NAS signaling with UE 1002 via the N3 IWF interface.

[0118] SMF 1046 can be responsible for SM (e.g., session establishment, tunnel management between UPF 1048 and AN 1008); UE IP address allocation and management (including optional licensing); selection and control of UP functions; configuring flow control at UPF 1048 to route traffic to appropriate destinations; termination of interfaces to policy control functions; control of policy enforcement, charging, and QoS as a part; lawful interception (for SM events and interfaces to the LI system); termination of the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information (sent to AN 1008 on N2 via AMF 1044); and determining the SSC mode of the session. SM can refer to the management of PDU sessions, and a PDU session or "session" can refer to the PDU connectivity service that provides or enables PDU exchange between UE 1002 and data network 1036.

[0119] The UPF 1048 can be used as an anchor point for mobility within and between RATs, an external PDU session point interconnecting with the data network 1036, and a branch point supporting multi-homed PDU sessions. The UPF 1048 can also perform packet routing and forwarding, packet inspection, user plane portion of policy rules, lawful packet interception (UP collection), traffic usage reporting, QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic authentication (e.g., SDF-to-QoS flow mapping), transport-level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. The UPF 1048 may include an uplink classifier to support traffic flow routing to the data network.

[0120] The NSSF 1050 can select a set of network slice instances to serve UE 1002. If needed, the NSSF 1050 can also determine the allowed network slice selection assistance information (NSSAI) and the mapping to the subscribed individual NSSAI (S-NSSAI). The NSSF 1050 can also determine the set of AMFs to be used to serve UE 1002 based on appropriate configuration and possibly by querying the NRF 1054, or determine a list of candidate AMFs. The selection of a set of network slice instances for UE 1002 can be triggered by the AMF 1044 (which UE 1002 registers with by interacting with the NSSF 1050), resulting in a change of AMF. The NSSF 1050 can interact with the AMF 1044 via the N22 reference point; and can communicate with another NSSF in the visited network via the N31 reference point (not shown). Furthermore, the NSSF 1050 can expose an interface based on NNSSF services.

[0121] The NEF 1052 can securely disclose services and capabilities provided by 3GPP network functions for third parties, internal disclosure / redisclosure, AFs (e.g., AF 1060), edge computing, or fog computing systems. In these embodiments, the NEF 1052 can authenticate, license, or suppress AFs. The NEF 1052 can also translate information exchanged with the AF 1060 and information exchanged with internal network functions. For example, the NEF 1052 can translate between AF service identifiers and internal 5GC information. The NEF 1052 can also receive information from other NFs based on their public capabilities. This information can be stored as structured data at the NEF 1052 or stored at a data storage NF using a standardized interface. The NEF 1052 can then redistribute the stored information to other NFs and AFs, or use it for other purposes such as analytics. Additionally, the NEF 1052 can expose interfaces based on Nnef services.

[0122] NRF 1054 supports service discovery, receiving NF discovery requests from NF instances and providing information about discovered NF instances to them. NRF 1054 also maintains information about available NF instances and the services they support. As used herein, the terms "instantiation," "instance," etc., can refer to the creation of an instance, and an "instance" can refer to the concrete occurrence of an object, such as during program code execution. Furthermore, NRF 1054 can demonstrate interfaces based on NRF services.

[0123] The PCF 1056 can provide policy rules to control plane functions to enforce them, and can also support a unified policy framework to manage network behavior. The PCF 1056 can also implement a frontend to access subscription information related to policy decisions in the UDR of the UDM 1058. In addition to communicating with functions via reference points as shown in the figure, the PCF 1056 also demonstrates an interface based on Npcf services.

[0124] UDM 1058 can process subscription-related information to support network entities in handling communication sessions and can store subscription data for UE 1002. For example, subscription data can be transmitted via the N8 reference point between UDM 1058 and AMF 1044. UDM 1058 may include two parts: an application front-end and a UDR. The UDR may store policy data and subscription data for UDM 1058 and PCF 1056, and / or structured data and application data for disclosure (including PFD for application detection and application request information for multiple UEs 1002) for NEF 1052. UDR 221 may expose a Nudr service-based interface to allow UDM 1058, PCF 1056, and NEF 1052 to access specific sets of stored data, as well as to read, update (e.g., add, modify), delete, and notify of relevant data changes in the subscription UDR. UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front-ends can provide services to the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown in the figure, the UDM 1058 can also demonstrate interfaces based on Nudm services.

[0125] The AF 1060 can provide application impact on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

[0126] In some embodiments, 5GC 1040 can enable edge computing by selecting an operator / third-party service that is geographically close to the point to which UE 1002 attaches to the network. This can reduce latency and load on the network. To provide edge computing implementation, 5GC 1040 can select a UPF 1048 close to UE 1002 and perform traffic routing from UPF 1048 to data network 1036 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 1060. In this way, AF 1060 can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1060 is considered a trusted entity, the network operator can allow AF 1060 to interact directly with the relevant NF. Additionally, AF 1060 can expose interfaces based on Naf services.

[0127] Data network 1036 can represent various network operator services, Internet access, or third-party services that can be provided by one or more servers (including, for example, application / content server 1038).

[0128] Figure 11 A wireless network 1100 according to various embodiments is schematically illustrated. The wireless network 1100 may include a UE 1102 that communicates wirelessly with an AN 1104. The UE 1102 and the AN 1104 may be similar to and substantially interchangeable with equivalent components described elsewhere herein.

[0129] UE 1102 can be communicatively coupled to AN 1104 via connection 1106. Connection 1106 is shown as an air interface to enable communication coupling and can be consistent with cellular communication protocols operating at millimeter wave (mmWave) or sub-6 GHz frequencies, such as LTE or 5G NR protocols.

[0130] UE 1102 may include a host platform 1108 coupled to a modem platform 1110. Host platform 1108 may include application processing circuitry 1112, which may be coupled to protocol processing circuitry 1114 of modem platform 1110. Application processing circuitry 1112 may run various applications for UE 1102 to process source / receive application data. Application processing circuitry 1112 may also implement one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0131] Protocol processing circuitry 1114 can implement one or more layer operations to facilitate the transmission or reception of data via connection 1106. Layer operations implemented by protocol processing circuitry 1114 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0132] The modem platform 1110 may further include a digital baseband circuit 1116 that can implement one or more layer operations of "below" layer operations performed by the protocol processing circuit 1114 in the network protocol stack. These operations may include, for example, one or more of the following PHY operations: HARQ-ACK function, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, and multi-antenna port precoding / decoding. These functions may include one or more of the following: space-time, space-frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals, and other related functions.

[0133] The modem platform 1110 may further include transmitting circuitry 1118, receiving circuitry 1120, RF circuitry 1122, and RF front-end (RFFE) circuitry 1124, which may include or be connected to one or more antenna panels 1126. In short, transmitting circuitry 1118 may include a digital-to-analog converter, mixer, intermediate frequency (IF) component, etc.; receiving circuitry 1120 may include an analog-to-digital converter, mixer, IF component, etc.; RF circuitry 1122 may include a low-noise amplifier, power amplifier, power point tracking component, etc.; RFFE circuitry 1124 may include filters (e.g., surface acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of components of transmitting circuitry 1118, receiving circuitry 1120, RF circuitry 1122, RFFE circuitry 1124, and antenna panels 1126 (collectively, the "transmit / receive components") may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, at mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmitting / receiving components may be arranged in multiple parallel transmitting / receiving chains, and may be arranged in the same or different chips / modules, etc.

[0134] In some embodiments, the protocol processing circuit 1114 may include one or more instances of control circuitry (not shown) to provide control functions for the transmitting / receiving components.

[0135] UE reception can be established via and through antenna panel 1126, RFFE circuit 1124, RF circuit 1122, receiving circuit 1120, digital baseband circuit 1116, and protocol processing circuit 1114. In some embodiments, antenna panel 1126 can receive transmissions from AN 1104 by receiving beamforming signals received by a plurality of antennas / antenna elements of one or more antenna panels 1126.

[0136] UE transmission can be established via and through protocol processing circuitry 1114, digital baseband circuitry 1116, transmission circuitry 1118, RF circuitry 1122, RFFE circuitry 1124, and antenna panel 1126. In some embodiments, the transmission components of UE 1104 can apply a spatial filter to the data to be transmitted to form a transmission beam emitted by the antenna elements of antenna panel 1126.

[0137] Similar to UE 1102, AN 1104 may include a host platform 1128 coupled to modem platform 1130. Host platform 1128 may include application processing circuitry 1132 coupled to protocol processing circuitry 1134 of modem platform 1130. Modem platform may also include digital baseband circuitry 1136, transmitting circuitry 1138, receiving circuitry 1140, RF circuitry 1142, RFFE circuitry 1144, and antenna panel 1146. Components of AN 1104 may be similar to their namesake components in UE 1102 and are substantially interchangeable with those in UE 1102. In addition to performing data transmission / reception as described above, components of AN 1108 may also perform various logical functions, including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0138] Figure 12 Example components of a device 1200 according to some embodiments are shown. In some embodiments, device 1200 may include at least application circuitry 1202, baseband circuitry 1204, radio frequency (RF) circuitry 1206, front-end module (FEM) circuitry 1208, one or more antennas 1210, and power management circuitry (PMC) 1212 coupled together as shown. Components of the illustrated device 1200 may be included in a UE or AN. In some embodiments, device 1200 may include fewer components (e.g., the AN may not use application circuitry 1202, but instead include a processor / controller to process IP data received from the EPC). In some embodiments, device 1200 may include additional components such as memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, the components described below may be included in more than one device (e.g., for a Cloud-RAN (C-RAN) implementation, the circuitry may be separately included in more than one device).

[0139] Application circuitry 1202 may include one or more application processors. For example, application circuitry 1202 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications and / or operating systems to run on device 1200. In some embodiments, the processor of application circuitry 1202 may process IP packets received from the EPC.

[0140] Baseband circuit 1204 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. Baseband circuit 1204 may include one or more baseband processors or control logic to process baseband signals received from the receive signal path of RF circuit 1206 and generate baseband signals for the transmit signal path of RF circuit 1206. Baseband processing circuitry 1204 may interface with application circuitry 1202 to generate and process baseband signals and control the operation of RF circuit 1206. For example, in some embodiments, baseband circuitry 1204 may include a third-generation (3G) baseband processor 1204A, a fourth-generation (4G) baseband processor 1204B, a fifth-generation (5G) baseband processor 1204C, or one or more other baseband processors 1204D for other existing generations, generations under development, or future generations (e.g., sixth generation (6G), etc.). The baseband circuitry 1204 (e.g., one or more of baseband processors 1204A-D) can handle various radio control functions that support communication with one or more radio networks via RF circuitry 1206. In other embodiments, some or all of the functions of the baseband processors 1204A-D may be included in modules stored in memory 1204G and these functions may be executed via a central processing unit (CPU) 1204E. 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 circuitry of the baseband circuitry 1204 may include Fast Fourier Transform (FFT), precoding, and / or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 1204 may include convolution, tail-biting convolution, turbo, Viterbi, and / or low-density parity-check (LDPC) encoder / decoder functions. Embodiments of modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

[0141] In some embodiments, the baseband circuitry 1204 may include one or more audio digital signal processors (DSPs) 1204F. The audio DSP(s) 1204F may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or arranged on the same circuit board. In some embodiments, some or all of the components of the baseband circuitry 1204 and the application circuitry 1202 may be implemented together, for example, on a system-on-a-chip (SoC).

[0142] In some embodiments, baseband circuitry 1204 can provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 1204 can support communications with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), or Wireless Personal Area Networks (WPAN). Embodiments of baseband circuitry 1204 configured to support radio communications with more than one radio protocol may be referred to as multimode baseband circuitry.

[0143] RF circuit 1206 can support communication with wireless networks using modulated electromagnetic radiation via non-solid-state media. In various embodiments, RF circuit 1206 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 1206 may include a receive signal path, which may include circuitry for down-converting the RF signal received from FEM circuit 1208 and providing a baseband signal to baseband circuit 1204. RF circuit 1206 may also include a transmit signal path, which may include circuitry for up-converting the baseband signal provided by baseband circuit 1204 and providing an RF output signal to FEM circuit 1208 for transmission.

[0144] In some embodiments, the receive signal path of the RF circuit 1206 may include a mixer circuit 1206a, an amplifier circuit 1206b, and a filter circuit 1206c. In some embodiments, the transmit signal path of the RF circuit 1206 may include a filter circuit 1206c and a mixer circuit 1206a. The RF circuit 1206 may also include a synthesizer circuit 1206d for synthesizing frequencies for use by the mixer circuit 1206a in both the receive and transmit signal paths. In some embodiments, the mixer circuit 1206a in the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1208 based on the synthesized frequency provided by the synthesizer circuit 1206d. The amplifier circuit 1206b may be configured to amplify the down-converted signal, and the filter circuit 1206c 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 can be provided to the baseband circuit 1204 for further processing. In some embodiments, the output baseband signal may be a zero-frequency baseband signal, but this is not required. In some embodiments, the mixer circuit 1206a receiving the signal path may include a passive mixer, but the scope of the embodiments is not limited in this respect.

[0145] In some embodiments, the mixer circuit 1206a of the transmit signal path can be configured to up-convert the input baseband signal based on the synthesis frequency provided by the synthesizer circuit 1206d to generate an RF output signal for the FEM circuit 1208. The baseband signal can be provided by the baseband circuit 1204 and can be filtered by the filter circuit 1206c.

[0146] In some embodiments, the mixer circuit 1206a for the receive signal path and the mixer circuit 1206a for the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and / or upconversion, respectively. In some embodiments, the mixer circuit 1206a for the receive signal path and the mixer circuit 1206a for 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 1206a for the receive signal path and the mixer circuit 1206a for the transmit signal path may be arranged for direct downconversion and / or direct upconversion, respectively. In some embodiments, the mixer circuit 1206a for the receive signal path and the mixer circuit 1206a for the transmit signal path may be configured for superheterodyne operation.

[0147] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, but 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 1206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuit 1204 may include a digital baseband interface for communicating with the RF circuit 1206.

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

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

[0150] The synthesizer circuit 1206d can be configured to synthesize an output frequency for use by the mixer circuit 1206a of the RF circuit 1206 based on the frequency input and the divider control input. In some embodiments, the synthesizer circuit 1206d can be a fractional N / N+1 type synthesizer.

[0151] In some embodiments, the frequency input may be provided by a voltage-controlled oscillator (VCO), but this is not required. The divider control input may be provided by the baseband circuit 1204 or the application processor 1202 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 processor 1202.

[0152] The synthesizer circuit 1206d of the RF circuit 1206 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 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 carry output) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to decompose the VCO cycle into at most 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.

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

[0154] FEM circuit 1208 may include a receive signal path, which may include circuitry configured to operate RF signals received from one or more antennas 1210, amplify the received signals, and provide an amplified version of the received signals to RF circuit 1206 for further processing. FEM circuit 1208 may also include a transmit signal path, which may include circuitry configured to amplify signals provided by RF circuit 1206 for transmission by one or more antennas of the one or more antennas 1210. In various embodiments, amplification via the transmit or receive signal path may be performed only in RF circuit 1206, only in FEM 1208, or in both RF circuit 1206 and FEM 1208.

[0155] In some embodiments, FEM circuit 1208 may include a TX / RX switch to switch between transmit and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include a low-noise amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to RF circuit 1206). The transmit signal path of FEM circuit 1208 may include a power amplifier (PA) for amplifying (e.g., provided by RF circuit 1206) the input RF signal and one or more filters for generating RF signals for subsequent transmission (e.g., via one or more antennas in one or more antennas 1210).

[0156] In some embodiments, the PMC 1212 can manage the power supplied to the baseband circuitry 1204. Specifically, the PMC 1212 can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 1212 is typically included when the device 1200 can be powered by a battery, for example, when the device is included in a UE. The PMC 1212 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0157] Although Figure 12 The diagram shows that PMC 1212 is coupled only to baseband circuitry 1204. However, in other embodiments, PMC 1212 may additionally or alternatively be coupled to other components and perform similar power management operations on those other components, such as, but not limited to, application circuitry 1202, RF circuitry 1206, or FEM 1208.

[0158] In some embodiments, PMC 1212 may control various power-saving mechanisms of device 1200, or otherwise become part of various power-saving mechanisms of device 1200. For example, if device 1200 is in the RRC_Connected state, in which device 1200 remains connected to the RAN node when it anticipates receiving traffic soon, it may then enter a state known as Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, device 1200 may power down for short intervals to save power.

[0159] If there is no data service activity during the extended period, device 1200 can transition to the RRC_Idle state. In this state, device 1200 disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 1200 enters a very low-power state and performs paging, during which it periodically wakes up again to listen to the network and then powers off again. Device 1200 can not receive data in this state; to receive data, it can transition back to the RRC_Connected state.

[0160] An additional power-saving mode allows the device to be unavailable to the network for periods longer than the paging interval (ranging from seconds to hours). During this time, the device has no network access whatsoever and may lose power completely. Any data sent during this period will incur significant latency, assuming the latency is acceptable.

[0161] The processors of application circuit 1202 and baseband circuit 1204 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of baseband circuit 1204 (alone or in combination) can be used to execute layer 3, layer 2, or layer 1 functions, while the processor of application circuit 1204 can utilize data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, layer 3 may include the RRC layer. As mentioned herein, layer 2 may include the Media Access Control (MAC) layer, Radio Link Control (RLC) layer, and Packet Data Convergence Protocol (PDCP) layer. As mentioned herein, layer 1 may include the physical (PHY) layer of the UE / RAN node.

[0162] Figure 13Examples of infrastructure device 1300 according to various embodiments are shown. Infrastructure device 1300 (or “system 1300”) may be implemented as a base station, radio headend, RAN node, etc., such as RAN nodes 111 and 112 previously shown and described. In other examples, system 1300 may be implemented in or by a UE, one or more application servers 130 and / or any other element / device discussed herein. System 1300 may include one or more of the following: application circuitry 1305, baseband circuitry 1310, one or more radio headend modules 1315, memory 1320, power management integrated circuitry (PMIC) 1325, power tee circuitry 1330, network controller 1335, network interface connector 1340, satellite positioning circuitry 1345, and user interface 1350. In some embodiments, device 1300 may include additional elements such as memory / storage devices, displays, cameras, sensors, or input / output (I / O) interface elements. In other embodiments, the components described below may be included in more than one device (e.g., for a cloud RAN (C-RAN) implementation, the circuitry may be separately included in more than one device).

[0163] For the purposes of this document, the term "circuit" can refer to, be part of, or include hardware components configured to provide the described functions, such as: electronic circuitry, logic circuitry, processors (shared, dedicated, or grouped) and / or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or system-on-chips (SoCs)), digital signal processors (DSPs), and the like. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. Furthermore, the term "circuit" can also refer to a combination of one or more hardware elements (or circuitry used in an electrical or electronic system) and program code for performing the functions of that program code. In these embodiments, the combination of hardware components and program code can be referred to as a specific type of circuit.

[0164] The terms “application circuit” and / or “baseband circuit” may be considered synonymous with “processor circuit” and may be referred to as “processor circuit”. For the purposes of this document, the term “processor circuit” may refer to, be part of, or include circuits capable of sequentially and automatically performing a sequence of arithmetic or logical operations; and 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.

[0165] Application circuitry 1305 may include one or more central processing unit (CPU) cores and one or more of the following: cache memory, low drop-out (LDO) regulator, interrupt controller, serial interface such as SPI, I2C, or a universal programmable serial interface module, real time clock (RTC), timer-counter including interval and watchdog timers, general purpose input / output (I / O), memory card controller such as Secure Digital (SD) / MultiMediaCard (MMC), Universal Serial Bus (USB) interface, Mobile Industry Processor Interface (MIPI) interface, and Joint Test Access Group (JTAG) test access port. As an example, application circuitry 1305 may include one or more Intel... or Processor; Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or Processor; etc. In some embodiments, system 1300 may not utilize application circuitry 1305, but may instead include, for example, a dedicated processor / controller to process IP data received from EPC or 5GC.

[0166] Additionally or alternatively, application circuitry 1305 may include, but is not limited to, circuitry such as, but not limited to, one or more field-programmable devices (FPDs), such as field-programmable gate arrays (FPGAs); programmable logic devices (PLDs), such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs); and so on. In this embodiment, the circuitry of application circuitry 1305 may include logic blocks or logic architectures, including other interconnected resources, which may be programmed to perform various functions, such as the processes, methods, functions, etc., of the various embodiments discussed herein. In this embodiment, the circuitry of application circuitry 1305 may include storage cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), antifuse, etc.) for storing logic blocks, logic architectures, data, etc. in a lookup table (LUT), etc.), etc.

[0167] The baseband circuit 1310 may be implemented, for example, as a soldered substrate including one or more integrated circuits, a single-package integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Although not shown, the baseband circuit 1310 may include one or more digital baseband systems that may be coupled to a CPU subsystem, an audio subsystem, and an interface subsystem via interconnect subsystems. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via additional interconnect subsystems. Each interconnect subsystem may include a bus system, a point-to-point connection, a network-on-chip (NOC) architecture, and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include digital signal processing circuitry, buffer memory, program memory, voice processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more amplifiers and filters, and / or other similar components. In one aspect of this disclosure, the baseband circuit 1310 may include protocol processing circuitry having one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and / or radio frequency circuitry (e.g., radio front-end module 1315).

[0168] User interface circuitry 1350 may include one or more user interfaces designed to enable interaction with a user of system 1300 or peripheral component interfaces designed to enable interaction with peripheral components of system 1300. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light-emitting diodes, LEDs), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, a speaker or other audio emitting device, a microphone, a printer, a scanner, headphones, a display screen or display device, etc. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, universal serial bus (USB) ports, audio jacks, power supply interfaces, etc.

[0169] The radio front-end module (RFEM) 1315 may include a millimeter-wave RFEM and one or more submillimeter-wave radio frequency integrated circuits (RFICs). In some implementations, the one or more submillimeter-wave RFICs may be physically separated from the millimeter-wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter-wave and submillimeter-wave radio functions may be implemented in the same physical radio front-end module 1315. The RFEM 1315 may contain both millimeter-wave and submillimeter-wave antennas.

[0170] The memory circuitry 1320 may include one or more of the following: volatile memory, including dynamic random access memory (DRAM) and / or synchronous dynamic random access memory (SDRAM); and nonvolatile 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., and may contain information from… and A three-dimensional (3D) XPOINT memory. The memory circuit 1320 can be implemented as one or more of a solder-in packaged integrated circuit, a socket-type memory module, and an insertable memory card.

[0171] The PMIC 1325 may include a voltage regulator, surge protector, power alarm detection circuitry, and one or more backup power sources such as batteries or capacitors. The power alarm detection circuitry can detect one or more of a power outage (undervoltage) and a power surge (overvoltage) condition. The power tee circuit 1330 can provide power drawn from the network cable to supply both power and data connectivity to infrastructure equipment 1300 via a single cable.

[0172] Network controller circuitry 1335 may provide connectivity to the network using standard network interface protocols such as Ethernet, GRE-tunneled Ethernet, Multiprotocol Label Switching (MPLS) based Ethernet, or some other suitable protocol. Network connectivity to / from infrastructure device 1300 may be provided via a physical connection through network interface connector 1340, which may be electrical (typically referred to as a "copper interconnect"), optical, or wireless. Network controller circuitry 1335 may include one or more dedicated processors and / or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, network controller circuitry 1335 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

[0173] Positioning circuit 1345 may include circuitry for receiving and decoding signals transmitted by one or more navigation satellite constellations of a global navigation satellite system (GNSS). Examples of navigation satellite constellations (or GNSS) may include the U.S. Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., Navigation with Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbitography and Radio-positioning Integrated by Satellite (DORIS), etc.). Positioning circuit 1345 may include various hardware components (e.g., hardware devices such as switches, filters, amplifiers, antenna elements, etc., to facilitate communication over-the-air (OTA) communication) to communicate with components of the positioning network (e.g., navigation satellite constellation nodes).

[0174] Nodes or satellites of one or more navigation satellite constellations (“GNSS nodes”) can provide positioning services by continuously transmitting or broadcasting GNSS signals along the line of sight. These GNSS signals can be used by GNSS receivers (e.g., positioning circuitry 1345 and / or positioning circuitry implemented by UEs 101, 102, etc.) to determine their GNSS positions. GNSS signals may include pseudo-random codes (e.g., sequences of ones and zeros) known to the GNSS receiver and a message including the time of transmission (ToT) of the code epoch (e.g., a defined point in the pseudo-random code sequence) and the GNSS node position at the ToT. The GNSS receiver can monitor / measure GNSS signals transmitted / broadcast by multiple GNSS nodes (e.g., four or more satellites) and solve various equations to determine the corresponding GNSS positions (e.g., spatial coordinates). The GNSS receiver also implements a clock that is typically not as stable and accurate as the atomic clocks of the GNSS nodes, and can use the measured GNSS signals to determine the GNSS receiver's deviation from real time (e.g., the deviation of the GNSS receiver clock from the GNSS node time). In some embodiments, the positioning circuit 1345 may include a micro-technology for positioning, navigation, and timing (Micro-PNT) IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance.

[0175] A GNSS receiver can measure the time of arrival (ToA) of GNSS signals from multiple GNSS nodes according to its own clock. The GNSS receiver can determine the time of flight (ToF) value for each received GNSS signal based on the ToA and ToT, and then determine the three-dimensional (3D) position and clock offset based on the ToF. The 3D position can then be converted into latitude, longitude, and altitude. Positioning circuitry 1345 can provide data to application circuitry 1305, which may include one or more of position data or time data. Application circuitry 1305 can use the time data to synchronize its operation with other radio base stations (e.g., RAN nodes 111, 112, etc.).

[0176] Figure 13The components shown can communicate with each other using interface circuitry. For the purposes of this document, the term "interface circuitry" can refer to, be part of, or include circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" can refer to one or more hardware interfaces, such as a bus, input / output (I / O) interface, peripheral component interface, network interface card, etc. Any suitable bus technology can be used in various implementations, including any number of technologies such as industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus can be, for example, a proprietary bus used in a SoC-based system. Other bus systems can be included, such as I2C interfaces, SPI interfaces, point-to-point interfaces, and power buses, etc.

[0177] The following paragraphs describe examples of various embodiments.

[0178] Example 1 includes an apparatus comprising: a radio frequency (RF) interface; and processor circuitry coupled to the RF interface, wherein the processor circuitry is configured to: determine that two or more uplink (UL) transmissions overlap; determine whether at least one of the two or more UL transmissions is indicated to be cancelled; if the at least one UL transmission is not indicated to be cancelled, multiplex the at least one UL transmission with the remaining UL transmissions of the two or more UL transmissions for transmission to an access node (AN) via the RF interface; and if the at least one UL transmission is indicated to be cancelled, cancel the at least one UL transmission.

[0179] Example 2 includes the apparatus described in Example 1, wherein the two or more UL transmissions include one or more Physical Uplink Control Channel (PUCCH) transmissions and / or one or more Physical Uplink Shared Channel (PUSCH) transmissions.

[0180] Example 3 includes the apparatus described in Example 1, wherein the UL transmissions of the two or more UL transmissions carry uplink control information (UCI), and wherein the UCI includes at least one of the following: Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK), Channel State Information (CSI), Scheduling Request (SR), and Sound Reference Signal (SRS).

[0181] Example 4 includes the apparatus described in Example 3, wherein the HARQ-ACK corresponds to a Physical Downlink Shared Channel (PDSCH) scheduled by Dynamic Downlink Grant Downlink Control Information (DCI).

[0182] Example 5 includes the apparatus described in Example 1, wherein the two or more UL transmissions overlap in one or more symbols.

[0183] Example 6 includes the apparatus described in Example 1, wherein the sub-integration pairs of the two or more UL transmissions overlap.

[0184] Example 7 includes the apparatus described in Example 1, wherein subsets of the two or more UL transmissions overlap each other.

[0185] Example 8 includes the apparatus described in Example 1, wherein the processor circuitry is further configured to: if the at least one UL transmission is indicated to be cancelled, determine whether the remaining UL transmission among the two or more UL transmissions is indicated to be cancelled; and if the remaining UL transmission is not indicated to be cancelled, encode the remaining UL transmission for transmission to the AN via the RF interface.

[0186] Example 9 includes the apparatus described in Example 1, wherein the processor circuitry is further configured to: determine whether the at least one UL transmission is indicated to be cancelled based on a cancellation instruction or predetermined rule from the AN.

[0187] Example 10 includes the apparatus described in Example 9, wherein the cancellation instruction is carried via DCI or higher-level signaling.

[0188] Example 11 includes the apparatus described in Example 10, wherein the DCI includes DCI format 2_0 indicating a slot format indication (SFI).

[0189] Example 12 includes the apparatus described in Example 11, wherein the DCI format 2_0 is received after a DCI that triggers a PUCCH transmission in one or more UL transmissions.

[0190] Example 13 includes the apparatus of Example 9, wherein the processor circuitry is further configured to determine that the at least one UL transmission is indicated to be cancelled if: at least one symbol in a set of symbols for the at least one UL transmission is indicated as a downlink (DL) symbol or a flexible symbol; at least one symbol in a set of symbols for the at least one UL transmission is configured for a Synchronization Signal Block (SSB) transmission; the User Equipment (UE) has not received the SFI after a first time period starting from the last symbol of the Control Resource Set (CORESET) for the SFI, and at least one symbol in a set of symbols for the at least one UL transmission is indicated as a flexible symbol; the at least one UL transmission includes a Configuration Grant (CG) PUSCH transmission that overlaps with a Downlink Grant (DG) PUSCH transmission, and the scheduling DCI for the CG PUSCH transmission and the scheduling DCI for the DG PUSCH transmission are separated by at least a second time period; and / or the at least one UL transmission includes a CG PUSCH transmission that has the same Hybrid Automatic Repeat Request (HARQ) process number as the DG PUSCH transmission, and the CG PUSCH transmission is cancelled. The scheduling DCI for PUSCH transmissions and the scheduling DCI for the DG PUSCH transmissions are separated by at least a third time interval.

[0191] Example 14 includes the apparatus of any one of Examples 1 to 13, wherein the at least one UL transmission is semi-statically configured.

[0192] Example 15 includes the apparatus of any one of Examples 1 to 13, wherein the at least one UL transmission is dynamically scheduled.

[0193] Example 16 includes the apparatus of Example 1, wherein the two or more UL transmissions include at least one PUCCH transmission and at least two PUSCH transmissions, and wherein the processor circuitry is further configured to: if a first PUSCH transmission among the at least two PUSCH transmissions is not indicated as to be cancelled, then multiplex the PUCCH transmission in the at least one PUCCH transmission in the first PUSCH transmission; if the first PUSCH transmission is indicated as to be cancelled, then if a second PUSCH transmission among the at least two PUSCH transmissions is not indicated as to be cancelled, then multiplex the PUCCH transmission in the at least one PUCCH transmission in the second PUSCH transmission; and if all PUSCH transmissions among the at least two PUSCH transmissions are indicated as to be cancelled, then encode the PUCCH transmission in the at least one PUCCH transmission for transmission to the AN via the RF interface.

[0194] Example 17 includes the apparatus of Example 16, wherein: in the time domain, the first PUSCH transmission precedes the second PUSCH transmission; the first PUSCH transmission has a lower component carrier (CC) index than the second PUSCH transmission; and / or the first PUSCH transmission is dynamically scheduled, and the second PUSCH transmission is configured to be permitted.

[0195] Example 18 includes the apparatus of Example 1, wherein the two or more UL transmissions include at least two PUCCH transmissions, and wherein the processor circuitry is further configured to: if a first PUCCH transmission of the at least two PUCCH transmissions is indicated to be cancelled, cancel the first PUCCH transmission and any remaining PUCCH transmissions of the at least two PUCCH transmissions that are in the same resource set as the first PUCCH transmission, wherein the resource set is used for non-repeating PUCCH transmissions in a single time slot.

[0196] Example 19 includes the apparatus of Example 1, wherein the two or more UL transmissions include a first PUCCH transmission, a second PUCCH transmission, and a third PUCCH transmission, the first PUCCH transmission, the second PUCCH transmission, and the third PUCCH transmission being located in the same resource set for non-repeating PUCCH transmissions in a single time slot, wherein the first PUCCH transmission overlaps with both the second PUCCH transmission and the third PUCCH transmission, and the second PUCCH transmission does not overlap with the third PUCCH transmission, and wherein the processor circuitry is further configured to: if the second PUCCH transmission is indicated to be cancelled and the third PUCCH transmission is not indicated to be cancelled, then multiplex the first PUCCH transmission in the third PUCCH transmission.

[0197] Example 20 includes the apparatus of Example 1, wherein the two or more UL transmissions include a first PUCCH transmission and a second PUCCH transmission, and wherein the processor circuitry is further configured to: if the first PUCCH transmission is not indicated as to be cancelled, multiplex the second PUCCH transmission in the first PUCCH transmission to obtain a fourth PUCCH transmission; if the fourth PUCCH transmission is not indicated as to be cancelled, cause the fourth PUCCH transmission to be transmitted to the AN via the RF interface; and if the fourth PUCCH transmission is indicated as to be cancelled, cancel the fourth PUCCH transmission.

[0198] Example 21 includes a method comprising: determining that two or more uplink (UL) transmissions overlap; determining whether at least one of the two or more UL transmissions is indicated to be cancelled; if the at least one UL transmission is not indicated to be cancelled, multiplexing the at least one UL transmission with the remaining UL transmissions of the two or more UL transmissions for transmission to an access node (AN); and if the at least one UL transmission is indicated to be cancelled, cancelling the at least one UL transmission.

[0199] Example 22 includes the method described in Example 21, wherein the two or more UL transmissions include one or more Physical Uplink Control Channel (PUCCH) transmissions and / or one or more Physical Uplink Shared Channel (PUSCH) transmissions.

[0200] Example 23 includes the method of Example 21, wherein the UL transmissions in the two or more UL transmissions carry uplink control information (UCI), and wherein the UCI includes at least one of the following: Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK), Channel State Information (CSI), Scheduling Request (SR), and Sound Reference Signal (SRS).

[0201] Example 24 includes the method described in Example 23, wherein the HARQ-ACK corresponds to a Physical Downlink Shared Channel (PDSCH) scheduled by Dynamic Downlink Grant Downlink Control Information (DCI).

[0202] Example 25 includes the method of Example 21, wherein the two or more UL transmissions overlap in one or more symbols.

[0203] Example 26 includes the method of Example 21, wherein the sub-integration pairs of the two or more UL transmissions overlap.

[0204] Example 27 includes the method described in Example 21, wherein subsets of the two or more UL transmissions overlap each other.

[0205] Example 28 includes the method of Example 21, further comprising: if the at least one UL transmission is indicated to be cancelled, determining whether the remaining UL transmission among the two or more UL transmissions is indicated to be cancelled; and if the remaining UL transmission is not indicated to be cancelled, encoding the remaining UL transmission for transmission to the AN.

[0206] Example 29 includes the method of Example 21, further comprising: determining whether the at least one UL transmission is indicated to be cancelled based on a cancellation instruction or predetermined rule from the AN.

[0207] Example 30 includes the method of Example 29, wherein the cancellation instruction is carried via DCI or higher-level signaling.

[0208] Example 31 includes the method of Example 30, wherein the DCI includes DCI format 2_0 indicating a slot format indication (SFI).

[0209] Example 32 includes the method described in Example 31, wherein the DCI format 2_0 is received after a DCI that triggers a PUCCH transmission in one or more UL transmissions.

[0210] Example 33 includes the method of Example 29, further comprising determining that the at least one UL transmission is indicated to be cancelled if: at least one symbol in a set of symbols for the at least one UL transmission is indicated as a downlink (DL) symbol or a flexible symbol; at least one symbol in a set of symbols for the at least one UL transmission is configured for a Synchronization Signal Block (SSB) transmission; the User Equipment (UE) has not received the SFI after a first time period starting from the last symbol of the Control Resource Set (CORESET) for the SFI, and at least one symbol in a set of symbols for the at least one UL transmission is indicated as a flexible symbol; the at least one UL transmission includes a Configuration Granted (CG) PUSCH transmission that overlaps with a Downlink Granted (DG) PUSCH transmission, and the scheduling DCI for the CG PUSCH transmission and the scheduling DCI for the DG PUSCH transmission are at least separated by a second time period; and / or the at least one UL transmission includes a CG PUSCH transmission that has the same Hybrid Automatic Repeat Request (HARQ) process number as the DG PUSCH transmission, and the CG PUSCH transmission is cancelled. The scheduling DCI for PUSCH transmissions and the scheduling DCI for the DG PUSCH transmissions are separated by at least a third time interval.

[0211] Example 34 includes the method of any one of Examples 21 to 33, wherein the at least one UL transmission is semi-statically configured.

[0212] Example 35 includes the method of any one of Examples 21 to 33, wherein the at least one UL transmission is dynamically scheduled.

[0213] Example 36 includes the method of Example 21, wherein the two or more UL transmissions include at least one PUCCH transmission and at least two PUSCH transmissions, and the method further includes: if a first PUSCH transmission among the at least two PUSCH transmissions is not indicated as to be cancelled, then multiplexing the PUCCH transmission in the at least one PUCCH transmission in the first PUSCH transmission; if the first PUSCH transmission is indicated as to be cancelled, then multiplexing the PUCCH transmission in the at least one PUCCH transmission in the second PUSCH transmission if a second PUSCH transmission among the at least two PUSCH transmissions is not indicated as to be cancelled; and if all PUSCH transmissions among the at least two PUSCH transmissions are indicated as to be cancelled, then encoding the PUCCH transmission in the at least one PUCCH transmission for transmission to the AN.

[0214] Example 37 includes the method described in Example 36, wherein: in the time domain, the first PUSCH transmission precedes the second PUSCH transmission; the first PUSCH transmission has a lower component carrier (CC) index than the second PUSCH transmission; and / or the first PUSCH transmission is dynamically scheduled, and the second PUSCH transmission is configured to be permitted.

[0215] Example 38 includes the method of Example 21, wherein the two or more UL transmissions include at least two PUCCH transmissions, and the method further includes: if a first PUCCH transmission of the at least two PUCCH transmissions is indicated to be cancelled, then cancel the first PUCCH transmission and the remaining PUCCH transmissions of the at least two PUCCH transmissions that are in the same resource set as the first PUCCH transmission, wherein the resource set is used for non-repeating PUCCH transmissions in a single time slot.

[0216] Example 39 includes the method of Example 21, wherein the two or more UL transmissions include a first PUCCH transmission, a second PUCCH transmission, and a third PUCCH transmission, the first PUCCH transmission, the second PUCCH transmission, and the third PUCCH transmission being located in the same resource set for non-repeating PUCCH transmissions in a single time slot, wherein the first PUCCH transmission overlaps with both the second PUCCH transmission and the third PUCCH transmission, and the second PUCCH transmission does not overlap with the third PUCCH transmission, and the method further includes: if the second PUCCH transmission is indicated to be cancelled and the third PUCCH transmission is not indicated to be cancelled, then multiplexing the first PUCCH transmission in the third PUCCH transmission.

[0217] Example 40 includes the method of Example 21, wherein the two or more UL transmissions include a first PUCCH transmission and a second PUCCH transmission, and the method further includes: if the first PUCCH transmission is not indicated to be cancelled, then multiplexing the second PUCCH transmission in the first PUCCH transmission to obtain a fourth PUCCH transmission; if the fourth PUCCH transmission is not indicated to be cancelled, then causing the fourth PUCCH transmission to be sent to the AN; and if the fourth PUCCH transmission is indicated to be cancelled, then cancelling the fourth PUCCH transmission.

[0218] Example 41 includes an apparatus comprising: components for determining that two or more uplink (UL) transmissions overlap; components for determining whether at least one of the two or more UL transmissions is indicated to be cancelled; components for multiplexing the at least one UL transmission with the remaining UL transmissions of the two or more UL transmissions for transmission to an access node (AN) if the at least one UL transmission is not indicated to be cancelled; and components for cancelling the at least one UL transmission if the at least one UL transmission is indicated to be cancelled.

[0219] Example 42 includes the apparatus described in Example 41, wherein the two or more UL transmissions include one or more Physical Uplink Control Channel (PUCCH) transmissions and / or one or more Physical Uplink Shared Channel (PUSCH) transmissions.

[0220] Example 43 includes the apparatus of Example 41, wherein the UL transmissions of the two or more UL transmissions carry uplink control information (UCI), and wherein the UCI includes at least one of the following: Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK), Channel State Information (CSI), Scheduling Request (SR), and Sound Reference Signal (SRS).

[0221] Example 44 includes the apparatus described in Example 43, wherein the HARQ-ACK corresponds to a Physical Downlink Shared Channel (PDSCH) scheduled by Dynamic Downlink Grant Downlink Control Information (DCI).

[0222] Example 45 includes the apparatus described in Example 41, wherein the two or more UL transmissions overlap in one or more symbols.

[0223] Example 46 includes the apparatus described in Example 41, wherein the sub-integration pairs of the two or more UL transmissions overlap.

[0224] Example 47 includes the apparatus described in Example 41, wherein subsets of the two or more UL transmissions overlap each other.

[0225] Example 48 includes the apparatus of Example 41, further comprising: a component for determining whether a remaining UL transmission among the two or more UL transmissions is indicated to be cancelled if the at least one UL transmission is indicated to be cancelled; and a component for encoding the remaining UL transmission to transmit to the AN if the remaining UL transmission is not indicated to be cancelled.

[0226] Example 49 includes the apparatus of Example 41, and further includes a component for determining whether the at least one UL transmission is indicated to be cancelled based on a cancellation instruction or predetermined rule from the AN.

[0227] Example 50 includes the apparatus described in Example 49, wherein the cancellation instruction is carried via DCI or higher-level signaling.

[0228] Example 51 includes the apparatus described in Example 50, wherein the DCI includes DCI format 2_0 indicating a slot format indication (SFI).

[0229] Example 52 includes the apparatus described in Example 51, wherein the DCI format 2_0 is received after a DCI that triggers a PUCCH transmission in one or more UL transmissions.

[0230] Example 53 includes the apparatus of Example 49, further comprising components for determining that the at least one UL transmission is indicated to be cancelled if: at least one symbol in a set of symbols for the at least one UL transmission is indicated as a downlink (DL) symbol or a flexible symbol; at least one symbol in a set of symbols for the at least one UL transmission is configured for a Synchronization Signal Block (SSB) transmission; the User Equipment (UE) has not received the SFI after a first time period starting from the last symbol of the Control Resource Set (CORESET) for the SFI, and at least one symbol in a set of symbols for the at least one UL transmission is indicated as a flexible symbol; the at least one UL transmission includes a Configuration Grant (CG) PUSCH transmission that overlaps with a Downlink Grant (DG) PUSCH transmission, and the scheduling DCI for the CG PUSCH transmission and the scheduling DCI for the DG PUSCH transmission are at least separated by a second time period; and / or the at least one UL transmission includes a CG PUSCH transmission that has the same Hybrid Automatic Repeat Request (HARQ) process number as the DG PUSCH transmission, and the CG PUSCH transmission is cancelled. The scheduling DCI for PUSCH transmissions and the scheduling DCI for the DG PUSCH transmissions are separated by at least a third time interval.

[0231] Example 54 includes the apparatus of any one of Examples 41 to 53, wherein the at least one UL transmission is semi-statically configured.

[0232] Example 55 includes the apparatus of any one of Examples 41 to 53, wherein the at least one UL transmission is dynamically scheduled.

[0233] Example 56 includes the apparatus of Example 41, wherein the two or more UL transmissions include at least one PUCCH transmission and at least two PUSCH transmissions, and the apparatus further includes: a component for multiplexing a PUCCH transmission in the at least one PUCCH transmission in the first PUSCH transmission if the first PUSCH transmission in the at least two PUSCH transmissions is not indicated as to be cancelled; a component for multiplexing a PUCCH transmission in the at least one PUCCH transmission in the second PUSCH transmission if the first PUSCH transmission is indicated as to be cancelled and the second PUSCH transmission in the at least two PUSCH transmissions is not indicated as to be cancelled; and a component for encoding a PUCCH transmission in the at least one PUCCH transmission for transmission to the AN if all PUSCH transmissions in the at least two PUSCH transmissions are indicated as to be cancelled.

[0234] Example 57 includes the apparatus of Example 56, wherein: in the time domain, the first PUSCH transmission precedes the second PUSCH transmission; the first PUSCH transmission has a lower component carrier (CC) index than the second PUSCH transmission; and / or the first PUSCH transmission is dynamically scheduled, and the second PUSCH transmission is configured to be permitted.

[0235] Example 58 includes the apparatus of Example 41, wherein the two or more UL transmissions include at least two PUCCH transmissions, and the apparatus further includes: a component for canceling the first PUCCH transmission and any remaining PUCCH transmissions in the at least two PUCCH transmissions that are in the same resource set as the first PUCCH transmission if the first PUCCH transmission in the at least two PUCCH transmissions is indicated to be canceled, wherein the resource set is used for non-repeating PUCCH transmissions in a single time slot.

[0236] Example 59 includes the apparatus of Example 41, wherein the two or more UL transmissions include a first PUCCH transmission, a second PUCCH transmission, and a third PUCCH transmission, the first PUCCH transmission, the second PUCCH transmission, and the third PUCCH transmission being located in the same resource set for non-repeating PUCCH transmissions in a single time slot, wherein the first PUCCH transmission overlaps with both the second PUCCH transmission and the third PUCCH transmission, and the second PUCCH transmission does not overlap with the third PUCCH transmission, and the apparatus further includes a component for multiplexing the first PUCCH transmission in the third PUCCH transmission if the second PUCCH transmission is indicated to be canceled and the third PUCCH transmission is not indicated to be canceled.

[0237] Example 60 includes the apparatus of Example 41, wherein the two or more UL transmissions include a first PUCCH transmission and a second PUCCH transmission, and the apparatus further includes: a component for multiplexing the second PUCCH transmission in the first PUCCH transmission to obtain a fourth PUCCH transmission if the first PUCCH transmission is not indicated to be cancelled; a component for causing the fourth PUCCH transmission to be sent to the AN if the fourth PUCCH transmission is not indicated to be cancelled; and a component for cancelling the fourth PUCCH transmission if the fourth PUCCH transmission is indicated to be cancelled.

[0238] Example 61 includes a computer-readable medium having instructions stored thereon that, when executed by processor circuitry, cause processor circuitry to perform the method described in any one of Examples 21 to 40.

[0239] Example 62 includes a user equipment (UE) as shown and described in the specification.

[0240] Example 63 includes a method performed at the user equipment (UE) as shown and described in the specification.

[0241] Example 64 includes an access node (AN) as shown and described in the specification.

[0242] Example 65 includes methods performed at the access node (AN) as shown and described in the specification.

[0243] While certain embodiments have been illustrated and described herein for purposes of description, various alternative and / or equivalent embodiments or implementations devised to achieve the same purpose may replace the illustrated and described embodiments without departing from the scope of this disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is readily understood that the embodiments described herein are limited only by the appended claims and their equivalents.

Claims

1. A device for communication, comprising: Radio frequency (RF) interface; as well as The processor circuit is coupled to the RF interface. The processor circuit is used for: Identify two or more uplink (UL) transmission overlaps; Determine whether at least one of the two or more UL transmissions is indicated as to be cancelled; If the at least one UL transmission is not indicated as to be cancelled, the at least one UL transmission is multiplexed with the remaining UL transmissions from the two or more UL transmissions for transmission to the access node (AN) via the RF interface; and If at least one UL transmission is indicated to be cancelled, then the at least one UL transmission is cancelled. The processor circuitry is further configured to determine if the at least one UL transmission is indicated to be cancelled in the following circumstances: At least one of the symbols in a set used for the at least one UL transmission is designated as a downlink (DL) symbol or a flexible symbol; At least one of the symbols in a set used for the at least one UL transmission is configured for the transmission of a synchronization signal block (SSB); The user equipment (UE) has not received the SFI since the last symbol of the control resource set (CORESET) used for the SFI, after a first time period, and at least one symbol in the set of symbols used for the at least one UL transmission is indicated as a flexible symbol; The at least one UL transmission includes a Configuration Grant (CG) PUSCH transmission that overlaps with a Downlink Grant (DG) PUSCH transmission, and the scheduling DCI for the CG PUSCH transmission and the scheduling DCI for the DG PUSCH transmission are separated by at least a second time interval; and / or The at least one UL transmission includes a CG PUSCH transmission, which has the same Hybrid Automatic Repeat Request (HARQ) process number as the DG PUSCH transmission, and the scheduling DCI for the CG PUSCH transmission and the scheduling DCI for the DGPUSCH transmission are at least three time intervals apart.

2. The apparatus according to claim 1, wherein, The two or more UL transmissions include one or more Physical Uplink Control Channel (PUCCH) transmissions and / or one or more Physical Uplink Shared Channel (PUSCH) transmissions.

3. The apparatus according to claim 1, wherein, The UL transmissions in the two or more UL transmissions carry uplink control information (UCI), wherein the UCI includes at least one of the following: Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK), Channel State Information (CSI), Scheduling Request (SR), and Sound Reference Signal (SRS).

4. The apparatus according to claim 3, wherein, The HARQ-ACK corresponds to the Physical Downlink Shared Channel (PDSCH) scheduled by Dynamic Downlink Grant Downlink Control Information (DCI).

5. The apparatus according to claim 1, wherein, The two or more UL transmissions overlap in one or more symbols.

6. The apparatus according to claim 1, wherein, The sub-integration pairs of the two or more UL transmissions overlap.

7. The apparatus according to claim 1, wherein, The subsets of the two or more UL transmissions overlap with each other.

8. The apparatus according to claim 1, wherein, The processor circuit is also used for: If at least one UL transmission is indicated to be cancelled, then determine whether the remaining UL transmissions among the two or more UL transmissions are indicated to be cancelled; as well as If the remaining UL transmission is not indicated as to be cancelled, the remaining UL transmission is encoded to be transmitted to the AN via the RF interface.

9. The apparatus according to claim 1, wherein, The processor circuit is also used for: Based on the cancellation instruction or predetermined rule from the AN, it is determined whether the at least one UL transmission is indicated to be cancelled.

10. The apparatus according to claim 9, wherein, The cancellation instruction is carried via DCI or higher-level signaling.

11. The apparatus according to claim 10, wherein, The DCI includes DCI format 2_0, which indicates the slot format indication (SFI).

12. The apparatus according to claim 11, wherein, The DCI format 2_0 is received after the DCI that triggers the PUCCH transmission in the two or more UL transmissions.

13. The apparatus according to any one of claims 1 to 12, wherein, The at least one UL transmission is semi-statically configured.

14. The apparatus according to any one of claims 1 to 12, wherein, The at least one UL transmission is dynamically scheduled.

15. The apparatus according to claim 1, wherein, The two or more UL transmissions include at least one PUCCH transmission and at least two PUSCH transmissions, and wherein the processor circuitry is further configured to: If the first PUSCH transmission of the at least two PUSCH transmissions is not indicated as to be canceled, then the PUCCH transmission of the at least one PUCCH transmission is multiplexed in the first PUSCH transmission. If the first PUSCH transmission is indicated to be cancelled, then if the second PUSCH transmission out of the at least two PUSCH transmissions is not indicated to be cancelled, the PUCCH transmission in the at least one PUCCH transmission is multiplexed in the second PUSCH transmission; and If all PUSCH transmissions in the at least two PUSCH transmissions are indicated to be cancelled, then the PUCCH transmissions in the at least one PUCCH transmission are encoded for transmission to the AN via the RF interface.

16. The apparatus according to claim 15, wherein: In the time domain, the first PUSCH transmission precedes the second PUSCH transmission; The first PUSCH transmission has a lower component carrier (CC) index than the second PUSCH transmission; and / or The first PUSCH transmission is dynamically scheduled, and the second PUSCH transmission is configured to be permitted.

17. The apparatus according to claim 1, wherein, The two or more UL transmissions include at least two PUCCH transmissions, and wherein the processor circuitry is further configured to: If the first PUCCH transmission of the at least two PUCCH transmissions is indicated to be cancelled, then the first PUCCH transmission and the remaining PUCCH transmissions of the at least two PUCCH transmissions that are in the same resource set as the first PUCCH transmission are cancelled. The resource set is used for non-repeating PUCCH transmissions in a single time slot.

18. The apparatus according to claim 1, wherein, The two or more UL transmissions include a first PUCCH transmission, a second PUCCH transmission, and a third PUCCH transmission, wherein the first PUCCH transmission, the second PUCCH transmission, and the third PUCCH transmission are located in the same resource set for non-repeating PUCCH transmissions in a single time slot, wherein the first PUCCH transmission overlaps with both the second and third PUCCH transmissions, and the second PUCCH transmission does not overlap with the third PUCCH transmission, and wherein the processor circuitry is further configured to: If the second PUCCH transmission is indicated to be cancelled and the third PUCCH transmission is not indicated to be cancelled, then the first PUCCH transmission is multiplexed in the third PUCCH transmission.

19. The apparatus according to claim 1, wherein, The two or more UL transmissions include a first PUCCH transmission and a second PUCCH transmission, and wherein the processor circuitry is further configured to: If the first PUCCH transmission is not indicated as to be cancelled, the second PUCCH transmission is multiplexed in the first PUCCH transmission to obtain the fourth PUCCH transmission; If the fourth PUCCH transmission is not indicated as to be cancelled, then the fourth PUCCH transmission is sent to the AN via the RF interface; and If the fourth PUCCH transmission is indicated to be cancelled, then the fourth PUCCH transmission is cancelled.

Images