Cancellation and replacement of PUSCH

Abstract

The present disclosure provides apparatuses, systems, and methods for canceling and / or replacing a PUSCH. A user equipment device (UE) can configure a first PUSCH and a second PUSCH, where the first PUSCH can correspond to a configured grant, and where the second PUSCH can correspond to a configured grant or be scheduled by a PDCCH on a serving cell. The UE can determine that at least one transmission occasion associated with the first PUSCH and at least one transmission occasion associated with the second PUSCH overlap in time. The UE can drop a transmission scheduled for the second PUSCH, e.g., starting from a first symbol of a repetition of the second PUSCH that overlaps in time with one or more repetitions of the first PUSCH, e.g., based on determining that a priority of the first PUSCH is higher than a priority of the second PUSCH.

Description

Technical Field

[0001] The present invention relates to wireless communication, and more particularly to apparatus, systems, and methods for eliminating and / or replacing physical uplink shared channels (PUSCH) with different priorities, such as those for ultra-reliable low-latency communication (URLLC) and / or enhanced URLLC (eURLLC).

[0002] Related technical descriptions

[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and can operate complex applications that utilize these functions.

[0004] Long Term Evolution (LTE) has become the technology of choice for most wireless network operators worldwide, providing their user base with mobile broadband data and high-speed internet access. LTE defines multiple downlink (DL) physical channels, classified as transport or control channels, to carry blocks of information received from Medium Access Control (MAC) and higher layers. LTE also defines the number of physical layer channels for the uplink (UL).

[0005] For example, LTE defines the Physical Downlink Shared Channel (PDSCH) as the DL transport channel. The PDSCH is the primary data bearer channel allocated to users on a dynamic and opportunistic basis. The PDSCH carries data in transport blocks (TBs) corresponding to MAC Protocol Data Units (PDUs), which are passed from the MAC layer to the physical (PHY) layer once every transmission time interval (TTI). The PDSCH is also used to transmit broadcast information such as System Information Blocks (SIBs) and paging messages.

[0006] For example, LTE defines the Physical Downlink Control Channel (PDCCH) as the DL Control Channel, which carries the UE's resource allocation contained in the Downlink Control Information (DCI) message. Multiple PDCCHs can be transmitted in the same subframe using Control Channel Elements (CCEs), each consisting of nine groups of four resource elements called Resource Element Groups (REGs). The PDCCH uses Quadrature Phase Shift Keying (QPSK) modulation, where four QPSK symbols are mapped to each REG. Furthermore, depending on channel conditions, 1, 2, 4, or 8 CCEs can be used for the UE to ensure sufficient robustness.

[0007] Additionally, LTE defines the Physical Uplink Shared Channel (PUSCH) as a UL channel shared by all devices (User Equipment, UE) in a radio cell to transmit user data to the network. Scheduling of all UEs is under the control of the LTE base station (Enhanced Node B or eNB). The eNB uses uplink scheduling clearance (DCI format 0) to inform the UE of resource block (RB) allocations and the modulation and coding schemes to be used. The PUSCH typically supports QPSK and Quadrature Amplitude Modulation (QAM). In addition to user data, the PUSCH carries any control information required for decoding, such as transport format indicators and multiple-input multiple-output (MIMO) parameters. Control data is multiplexed with information data before the Digital Fourier Transform (DFT) expansion.

[0008] The next telecommunications standard proposed to surpass the current International Mobile Telecommunications Advanced (IMT-Advanced) standard is called 5G mobile network or 5G radio system, or simply 5G (also known as 5G-NR for 5G New Radio, or simply NR). 5G-NR offers higher capacity for higher density mobile broadband users, while supporting ultra-reliable and massive machine-type communication between devices, as well as lower latency and / or lower battery consumption. Furthermore, compared to current LTE, 5G-NR allows for more flexible UE scheduling. Therefore, efforts are underway to leverage the potentially higher throughput at higher frequencies in the ongoing development of 5G-NR. Summary of the Invention

[0009] The implementations relate to wireless communication, and more specifically to apparatus, systems, and methods for eliminating and / or replacing physical uplink shared channels (PUSCH) with different priorities, such as those for ultra-reliable low-latency communication (URLLC) and / or enhanced URLLC (eURLLC).

[0010] For example, a User Equipment (UE) may be configured to configure a first PUSCH and a second PUSCH. For instance, the UE may determine resources for transmission on the first PUSCH and the second PUSCH. The first PUSCH may correspond to a configuration grant. The second PUSCH may correspond to a configuration grant or may be scheduled by the Physical Downlink Control Channel (PDCCH) on the serving cell. Therefore, the UE may configure the first PUSCH based on the configuration grant (e.g., determining resources for transmission on the first PUSCH). Similarly, the UE may configure the second PUSCH based on scheduling provided by the PDCCH (e.g., dynamic grant) on the serving cell and / or another configuration grant (e.g., determining resources for transmission on the second PUSCH). In other words, the UE may prepare for the transmission of first data on the first PUSCH resources based on the configuration grant. Similarly, the UE may prepare for the transmission of second data on the second PUSCH resources based on scheduling provided by the PDCCH on the serving cell and / or another configuration grant. Additionally, the UE may be configured to determine that at least one transmission opportunity associated with the first PUSCH and at least one transmission opportunity associated with the second PUSCH overlap in time. Furthermore, the UE can be configured to discard transmissions (e.g., one or more transmissions) scheduled for the second PUSCH, for example, at least in part based on the priority of the first PUSCH. For instance, the UE can discard transmissions scheduled for the second PUSCH at least in part based on determining that the priority of the first PUSCH is higher than the priority of the second PUSCH. Transmissions T scheduled for the second PUSCH can be discarded starting from the first symbol of a repetition of the second PUSCH, the repetition of which overlaps in time with one or more repetitions of the first PUSCH.

[0011] The techniques described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to any one of the following computing devices: unmanned aerial vehicles (UAVs), unmanned controllers (UACs), UTM servers, base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, and various other computing devices.

[0012] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0013] A better understanding of the subject matter can be obtained by considering the following detailed description of the various embodiments in conjunction with the accompanying drawings, in which:

[0014] Figure 1A An exemplary wireless communication system according to some implementation schemes is shown.

[0015] Figure 1B Examples of base stations (BS) and access points communicating with user equipment (UE) devices according to some implementation schemes are shown.

[0016] Figure 2 An exemplary simplified block diagram of a WLAN access point (AP) according to some implementation schemes is shown.

[0017] Figure 3 An exemplary block diagram of a BS according to some implementation schemes is shown.

[0018] Figure 4 An exemplary block diagram of a server according to some implementation schemes is shown.

[0019] Figure 5A An exemplary block diagram of a UE according to some implementation schemes is shown.

[0020] Figure 5B An exemplary block diagram of a cellular communication circuit according to some implementation schemes is shown.

[0021] Figure 6A An example of the connection between the EPC network, LTE base station (eNB), and 5G NR base station (gNB) is shown.

[0022] Figure 6B An example of the protocol stack used for eNB and gNB is shown.

[0023] Figure 7A Examples of 5G network architectures according to some implementation schemes are shown, which combine 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to 5G CN.

[0024] Figure 7B Examples of 5G network architectures according to some implementation schemes are shown, which combine dual 3GPP (e.g., LTE and 5G NR) access to 5G CN as well as non-3GPP access.

[0025] Figure 8 An example of a baseband processor architecture for a UE according to some implementation schemes is shown.

[0026] Figure 9 An example of dynamic authorization conflicting with configuration authorization is shown.

[0027] Figure 10 Another example of dynamic licensing that conflicts with configuration licensing is shown.

[0028] Figure 11 An example of nested configuration and dynamic authorization is shown.

[0029] Figures 12A to 12C An example of a specific implementation of configuration authorization / dynamic authorization conflict handling is shown.

[0030] Figure 13 Possible examples of handling conflict transmissions according to some implementation schemes are shown.

[0031] Figures 14 to 16 An example of the interweaving of dynamic authorization and configuration authorization according to some implementation schemes is shown.

[0032] Figures 17 to 19 A block diagram illustrating an example of a method for selecting Physical Uplink Shared Channels (PUSCHs) with different priorities, according to some implementation schemes, is shown.

[0033] While the features described herein may be subject to various modifications and alternatives, specific embodiments thereof are shown by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0034] acronym

[0035] Various acronyms are used throughout this disclosure. The definitions of the most prominent acronyms that may appear throughout this disclosure are as follows:

[0036] • 3GPP: Third Generation Partnership Project

[0037] • UE: User Equipment

[0038] • RF: Radio Frequency

[0039] • BS: Base Station

[0040] • DL: Downlink

[0041] • UL: Uplink

[0042] • LTE: Long Term Evolution

[0043] • NR: New Radio

[0044] • 5GS: 5G system

[0045] • 5GMM: 5GS Mobility Management

[0046] • 5GC / 5GCN: 5G Core Network

[0047] • IE: Information Elements

[0048] • CE: Control Element

[0049] • MAC: Media Access Control

[0050] • SSB: Synchronization Signal Block

[0051] • CSI-RS: Channel State Information Reference Signal

[0052] • PDCCH: Physical Downlink Control Channel

[0053] • PDSCH: Physical Downlink Shared Channel

[0054] • RRC: Radio Resource Control

[0055] • RRM: Radio Resource Management

[0056] • CORESET: Control Resource Set

[0057] • TCI: Transport Configuration Indicator

[0058] • DCI: Downlink Control Indicator

[0059] the term

[0060] The following is a glossary of terms used in this disclosure:

[0061] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory media" may include two or more memory media that may reside in different locations on different computer systems, for example, connected via a network. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0062] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks, and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals, or digital signals).

[0063] Programmable hardware elements encompass a variety of hardware devices that include multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can vary from fine-grained (combinatorial logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."

[0064] Computer system (or computer) — any of the various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0065] User equipment (UE) (or “UE device”) — any of a variety of computer system devices that are mobile or portable and perform wireless communications. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). ™ Based on Android™ Telephones), portable gaming devices (e.g., Nintendo DS) ™ PlayStation Portable ™ Gameboy Advance ™ iPhone ™ This includes laptops, wearable devices (e.g., smartwatches, smart glasses), PDAs, portable internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined as encompassing any electronic, computing, and / or telecommunications equipment (or combination of equipment) that is easily transportable by the user and capable of wireless communication.

[0066] Base station—The term “base station” has the full range of its common meaning and includes at least a wireless communication station that is installed in a fixed location and is used for communication as part of a wireless telephone system or radio system.

[0067] A processing element (or processor) is a component or combination of components capable of performing the functions of a device such as user equipment or cellular network equipment. A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0068] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on different wireless protocols, the term "channel" as used herein can be considered to be used in a standard manner consistent with the type of device to which the term is referenced. In some standards, the channel width can be variable (e.g., depending on device capabilities, frequency band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0069] Frequency band—The term “frequency band” has the full range of its general meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which a channel is used or reserved for the same purpose.

[0070] Wi-Fi—The term “Wi-Fi” (or WiFi) has the full range of its usual meaning and includes at least wireless communication networks or RATs that are served by and provide connectivity to the Internet through wireless LAN (WLAN) access points. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name “Wi-Fi.” Wi-Fi (WLAN) networks are different from cellular networks.

[0071] 3GPP access refers to access technologies (e.g., radio access technologies) specified by 3GPP standards. These access technologies include, but are not limited to, GSM / GPRS, LTE, LTE-A, and / or 5G NR. Generally speaking, 3GPP access refers to various types of cellular access technologies.

[0072] Non-3GPP access refers to any access technology (e.g., radio access technologies) not specified by 3GPP standards. These accesses include, but are not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and / or fixed networks. Non-3GPP access can be categorized into two types: "trusted" and "untrusted." Trusted non-3GPP access can interact directly with the Evolved Packet Core (EPC) and / or 5G Core (5GC), while untrusted non-3GPP access interoperates with the EPC / 5GC via network entities such as Evolved Packet Data Gateways and / or 5G NR Gateways. Generally speaking, non-3GPP access refers to various types of non-cellular access technologies.

[0073] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatically" is the opposite of an operation performed or specified manually by a user, where the user provides input to directly perform the operation. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0074] Approximately—means a value close to the correct or precise value. For example, approximately can refer to a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can vary depending on the application. For example, in some implementations, “approximately” may mean within 0.1% of some specified or expected value, while in various other implementations, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of the specific application.

[0075] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that at least partially overlaps. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0076] Various components can be described as being "configured" to perform one or more tasks. In such contexts, "configured" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently switched on. Typically, the circuit forming the structure corresponding to "configured" can include hardware circuitry.

[0077] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase “configured to”. Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 USC § 112(f) for that component.

[0078] Figure 1A and 1B Communication system

[0079] Figure 1A A simplified exemplary wireless communication system according to some implementation schemes is shown. It should be noted that... Figure 1A The system described herein is merely one example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.

[0080] As shown in the figure, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipments 106A, 106B to 106N via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE). Therefore, user equipment 106 is referred to as a UE or UE device.

[0081] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (“cellular base station”), and may include hardware that enables wireless communication with UE 106A to UE 106N.

[0082] The communication area (or coverage area) of a base station can be referred to as a "cell". Base station 102A and UE 106 can be configured to communicate via a transmission medium using any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-A Advanced, 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if base station 102A is implemented in an LTE environment, its alternative location can be referred to as an "eNodeB" or "eNB". Note that if base station 102A is implemented in a 5G NR environment, its alternative location can be referred to as a "gNodeB" or "gNB".

[0083] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A can facilitate communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various communication capabilities such as voice, SMS, and / or data services.

[0084] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping services to UE 106A-N and similar devices over a geographical area via one or more cellular communication standards.

[0085] Therefore, although base station 102A can act as such Figure 1A The diagram shows the "serving cell" of UEs 106A-N, but each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B-N and / or any other base stations), which may be referred to as "neighboring cells". Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. These cells may include "macro" cells, "micro" cells, "pecimen" cells, and / or any other cells of various other granularities providing service area size. For example, in Figure 1A Base stations 102A to 102B shown can be macro cells, while base station 102N can be a micro cell. Other configurations are also possible.

[0086] In some implementations, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a "gNB". In some implementations, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, the gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0087] It should be noted that UE 106 can communicate using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD, etc.), UE 106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, UE 106 can also or alternatively be configured to communicate using one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0088] Figure 1B User equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 and access point 112 according to some embodiments is shown. UE 106 can be a device with cellular and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet computer, or virtually any type of wireless device.

[0089] UE 106 may include a processor configured to execute program instructions stored in memory. UE 106 may execute any of the method embodiments of the present invention by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as a field-programmable gate array (FPGA) configured to execute any of the method embodiments of the present invention or any portion thereof.

[0090] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / Advanced LTE, or 5G NR and / or GSM, LTE, Advanced LTE, or 5G NR using a single shared radio component. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Typically, the radio component may include any combination of baseband processor, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of the receive chain and / or transmit chain among various wireless communication technologies such as those discussed above.

[0091] In some implementations, UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 may include shared radio components for communication using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and separate radio components for communication using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0092] Figure 2 Access point diagram

[0093] Figure 2 An exemplary block diagram of access point (AP) 112 is shown. Note that... Figure 2 The block diagram of the AP is only one example of a possible system. As shown, AP 112 may include a processor 204 capable of executing program instructions for AP 112. Processor 204 may also be (directly or indirectly) coupled to a memory management unit (MMU) 240 or other circuitry or device, which may be configured to receive addresses from processor 204 and translate those addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0094] AP 112 may include at least one network port 270. Network port 270 may be configured to couple to a wired network and provide access to the Internet to multiple devices such as UE 106. For example, network port 270 (or additional network ports) may be configured to couple to a local network, such as a home network or a corporate network. For example, port 270 may be an Ethernet port. The local network may provide connectivity to additional networks such as the Internet.

[0095] AP 112 may include at least one antenna 234, which may be configured to function as a wireless transceiver and may be further configured to communicate with UE 106 via wireless communication circuitry 230. Antenna 234 communicates with wireless communication circuitry 230 via communication link 232. Communication link 232 may include one or more receive links, one or more transmit links, or both. Wireless communication circuitry 230 may be configured to communicate via Wi-Fi or WLAN (e.g., 802.11). For example, in the case of a small cell where the AP coexists with a base station, or in other situations where it may be desirable for AP 112 to communicate via various different wireless communication technologies, wireless communication circuitry 230 may also or alternatively be configured to communicate via various other wireless communication technologies, including, but not limited to, 5G NR, LTE, LTE-A Advanced, GSM, WCDMA, CDMA2000, etc.

[0096] In some implementations, as further described below, AP 112 may be configured to perform methods for eliminating and / or replacing physical uplink shared channels (PUSCH) with different priorities, such as those for ultra-reliable low-latency communication (URLLC) and / or enhanced URLLC (eURLLC) as further described herein.

[0097] Figure 3 Block diagram of a base station

[0098] Figure 3 An exemplary block diagram of a base station 102 according to some embodiments is shown. It should be noted that... Figure 3 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 404 capable of executing program instructions for base station 102. Processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuitry or device, which may be configured to receive addresses from processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0099] Base station 102 may include at least one network port 470. Network port 470 may be configured to be coupled to a telephone network and provide access rights as described above in Figure 1 and... Figure 2 The telephone network described herein includes multiple devices such as UE device 106.

[0100] Network port 470 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as UE device 106. In some cases, network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0101] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or "gNB". In such implementations, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0102] Base station 102 may include at least one antenna 434 and possibly multiple antennas. The at least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with UE device 106 via radio component 430. Antenna 434 communicates with radio component 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio component 430 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0103] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, base station 102 may include multiple radios that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communication according to LTE and a 5G NR radio component for performing communication according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0104] As further described herein, BS 102 may include hardware and software components for implementing or supporting specific implementations of the features described herein. The processor 404 of base station 102 may be configured to implement or support some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 404 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 430, 432, 434, 440, 450, 460, and 470, the processor 404 of base station 102 may be configured to implement or support some or all of the features described herein.

[0105] Furthermore, as described herein, processor 404 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 404. Therefore, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.

[0106] Additionally, as described herein, the radio component 430 may comprise one or more processing elements. In other words, one or more processing elements may be included in the radio component 430. Therefore, the radio component 430 may include one or more integrated circuits (ICs) configured to perform the functions of the radio component 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the radio component 430.

[0107] Figure 4 Server block diagram

[0108] Figure 4 An exemplary block diagram of server 104 according to some implementation schemes is shown. It should be noted that... Figure 4 The base station is merely one example of a possible server. As shown, server 104 may include processor 444 capable of executing program instructions for server 104. Processor 444 may also be coupled to memory management unit (MMU) 474, which may be configured to receive addresses from processor 444 and translate those addresses into locations in memory (e.g., memory 464 and read-only memory (ROM) 454) or to other circuitry or devices.

[0109] Server 104 can be configured to provide access to network functions to multiple devices, such as base station 102, UE device 106 and / or UTM 108, for example, as further described herein.

[0110] In some implementations, server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) access network. In some implementations, server 104 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network.

[0111] As further described herein, server 104 may include hardware and software components for implementing or supporting the implementation of the features described herein. Processor 444 of server 104 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 444 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or configured as an ASIC (Application-Specific Integrated Circuit) or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 454, 464, and / or 474, processor 444 of server 104 may be configured to implement or support some or all of the features described herein.

[0112] Furthermore, as described herein, processor 444 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 444. Therefore, processor 444 may include one or more integrated circuits (ICs) configured to perform the functions of processor 444. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 444.

[0113] Figure 5A : UE block diagram

[0114] Figure 5AAn exemplary simplified block diagram of a communication device 106 according to some embodiments is shown. It should be noted that... Figure 5A The block diagram of the communication device is merely one example of possible communication devices. According to embodiments, communication device 106 may be a user equipment (UE) device, mobile device or mobile station, wireless device or wireless station, desktop computer or computing device, mobile computing device (e.g., laptop computer, notebook computer, or portable computing device), tablet computer, unmanned aerial vehicle (UAV), UAV controller (UAC) and / or combination of devices, and other devices. As shown, communication device 106 may include a set of components 300 configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, this set of components 300 may be implemented as individual components or groups of components for various purposes. This set of components 300 may be (e.g., communicatively; directly or indirectly) coupled to various other circuits of communication device 106.

[0115] For example, communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as connector I / F 320 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 360 that may be integrated with or external to communication device 106, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., and short- to medium-range wireless communication circuitry 329 (e.g., Bluetooth). ™ (and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0116] Cellular communication circuitry 330 may be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 335 and 336 shown. Short-to-medium-range wireless communication circuitry 329 may also be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 337 and 338 shown. Alternatively, short-to-medium-range wireless communication circuitry 329 may be coupled (e.g., communicatively grounded; directly or indirectly) to antennas 337 and 338, or as an alternative, to antennas 335 and 336. Short-to-medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple-output (MIMO) configuration.

[0117] In some embodiments, as further described below, the cellular communication circuit 330 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). Furthermore, in some embodiments, the cellular communication circuit 330 may include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component may be dedicated to a first RAT, such as LTE, and may communicate with a dedicated receive chain and a transmit chain shared with additional radio components, such as a second radio component that may be dedicated to a second RAT (e.g., 5G NR) and may communicate with a dedicated receive chain and a shared transmit chain.

[0118] The communication device 106 may also include one or more user interface elements and / or be configured to be used with one or more user interface elements. User interface elements may include any of a variety of components such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of the touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other components capable of providing information to the user and / or receiving or interpreting user input.

[0119] The communication device 106 may also include one or more smart cards 345 with SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more general-purpose integrated circuit cards) 345. It should be noted that the term "SIM" or "SIM entity" is intended to include any of various types of SIM implementations or SIM functions, such as one or more UICC cards 345, one or more eUICCs, one or more eSIMs, removable or embedded, etc. In some embodiments, the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that can be embedded, for example, soldered to a circuit board in the UE 106, or each SIM 310 may be implemented as a removable smart card. Therefore, a SIM may be one or more removable smart cards (such as UICC cards, sometimes referred to as "SIM cards"), and / or SIM 310 may be one or more embedded cards (such as embedded UICCs (eUICCs), sometimes referred to as "eSIMs" or "eSIM cards"). In some implementations (such as when the SIM includes an eUICC), one or more SIMs within the SIM can implement embedded SIM (eSIM) functionality; in such implementations, a single SIM within the SIM can execute multiple SIM applications. Each SIM may include components such as a processor and / or memory; instructions for performing SIM / eSIM functionality may be stored in memory and executed by the processor. In some implementations, UE 106 may include, as needed, a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUICC cards implementing eSIM functionality). For example, UE 106 may include two embedded SIMs, two removable SIMs, or a combination of one embedded SIM and one removable SIM. Various other SIM configurations are also envisioned.

[0120] As described above, in some implementations, UE 106 may include two or more SIMs. Including two or more SIMs in UE 106 allows UE 106 to support two different phone numbers and allows UE 106 to communicate on two or more corresponding networks. For example, the first SIM may support a first RAT such as LTE, and the second SIM 106 may support a second RAT such as 5G NR. Other implementations and RATs are also possible. In some implementations, when UE 106 includes two SIMs, UE 106 may support Dual SIM Dual Standby (DSDA) functionality. DSDA functionality allows UE 106 to connect to two networks simultaneously (and use two different RATs), or allows two connections supported by two different SIMs using the same or different RATs to be maintained simultaneously on the same or different networks. DSDA functionality also allows UE 106 to receive voice calls or data traffic simultaneously on either phone number. In some implementations, voice calls may be packet-switched communications. In other words, voice calls can be received using LTE-based Voice (VoLTE) technology and / or NR-based Voice (VoNR) technology. In some implementations, UE 106 may support Dual SIM Dual Standby (DSDS) functionality. DSDS functionality allows either of the two SIMs in UE 106 to remain in standby while awaiting a voice call and / or data connection. In DSDS, when a call / data connection is established on one SIM, the other SIM is no longer active. In some implementations, DSDx functionality (DSDA or DSDS functionality) can be implemented using a single SIM (e.g., eUICC) that performs multiple SIM applications for different carriers and / or RATs.

[0121] As shown in the figure, the SOC 300 may include a processor 302 and a display circuit 304. The processor executes program instructions for the communication device 106, and the display circuit performs graphics processing and provides display signals to the display 360. One or more processors 302 may also be coupled to a memory management unit (MMU) 340 (which may be configured to receive addresses from one or more processors 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or coupled to other circuitry or devices (such as the display circuit 304, short-to-medium range wireless communication circuitry 329, cellular communication circuitry 330, connector I / F 320, and / or display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0122] As described above, communication device 106 can be configured to communicate using wireless and / or wired communication circuits. Communication device 106 can be configured to perform methods for eliminating and / or replacing Physical Uplink Shared Channel (PUSCH) with different priorities, such as those used for Ultra Reliable Low Latency Communication (URLLC) and / or Enhanced URLLC (eURLLC) as further described herein.

[0123] As described herein, communication device 106 may include hardware and software components for implementing the features described above to transmit a scheduling profile for power saving to a network. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium), processor 302 of communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or in addition), processor 302 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit). Alternatively (or in addition), in conjunction with one or more of other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, processor 302 of communication device 106 may be configured to implement some or all of the features described herein.

[0124] Furthermore, as described in this invention, processor 302 may include one or more processing elements. Therefore, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 302.

[0125] Further, as described herein, the cellular communication circuit 330 and the short-to-medium-range wireless communication circuit 329 may each include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 330, and similarly, one or more processing elements may be included in the short-to-medium-range wireless communication circuit 329. Therefore, the cellular communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 330. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 330. Similarly, the short-to-medium-range wireless communication circuit 329 may include one or more ICs configured to perform the functions of the short-to-medium-range wireless communication circuit 329. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-to-medium-range wireless communication circuit 329.

[0126] Figure 5B Block diagram of cellular communication circuit

[0127] Figure 5B An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is shown. It should be noted that... Figure 5B The block diagram of the cellular communication circuit is merely one example of a possible cellular communication circuit. According to the implementation, the cellular communication circuit 330 may be included in a communication device such as the communication device 106 described above. As mentioned above, among other devices, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop computer, notebook computer, or portable computing device), a tablet computer, and / or a combination of these devices.

[0128] Cellular communication circuit 330 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as ( Figure 3 Antennas 335a-335b and 336 are shown in the diagram. In some embodiments, the cellular communication circuit 330 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, as shown... Figure 5B As shown, the cellular communication circuit 330 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT (such as LTE or LTE-A), and the modem 520 may be configured for communication according to a second RAT (such as 5G NR).

[0129] As shown, modem 510 may include one or more processors 512 and memory 516 communicating with processors 512. Modem 510 may communicate with radio frequency (RF) front end 530. RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, RF front end 530 may include receiver circuitry (RX) 532 and transmitter circuitry (TX) 534. In some embodiments, receiver circuitry 532 may communicate with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0130] Similarly, modem 520 may include one or more processors 522 and memory 526 communicating with processor 522. Modem 520 may communicate with RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some embodiments, receiving circuitry 542 may communicate with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0131] In some implementations, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 330 receives an instruction to transmit according to a first RAT (e.g., supported by modem 510), switch 570 may be switched to a first state allowing modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 330 receives an instruction to transmit according to a second RAT (e.g., supported by modem 520), switch 570 may be switched to a second state allowing modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).

[0132] In some implementations, the cellular communication circuit 330 may be configured to perform methods for eliminating and / or replacing physical uplink shared channels (PUSCH) with different priorities, such as those used for ultra-reliable low-latency communication (URLLC) and / or enhanced URLLC (eURLLC) as further described herein.

[0133] As described herein, modem 510 may include hardware and software components for implementing the features described above or for UL data used in time-division multiplexing NSA NR operation, as well as various other technologies described herein. For example, processor 512 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 512 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or otherwise), processor 512 may be configured to implement some or all of the features described herein by combining with one or more of other components 530, 532, 534, 550, 570, 572, 335, and 336.

[0134] Furthermore, as described herein, processor 512 may include one or more processing elements. Therefore, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0135] As described herein, modem 520 may include hardware and software components designed to implement the aforementioned features for transmitting power-saving scheduling profiles to the network, as well as various other technologies described herein. For example, processor 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 522 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or additionally), processor 522 may be configured to implement some or all of the features described herein by combining one or more of other components 540, 542, 544, 550, 570, 572, 335, and 336.

[0136] Furthermore, as described herein, processor 522 may include one or more processing elements. Therefore, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0137] Figure 6A and Figure 6B 5G NR architecture with LTE

[0138] In some specific implementations, fifth-generation (5G) wireless communication will initially be deployed concurrently with current wireless communication standards, such as LTE. For example, dual connectivity between LTE and 5G New Radio (5G NR or NR) has been designated as part of the initial NR deployment. Therefore, as... Figures 6A to 6B As shown, the Evolved Packet Core (EPC) network 600 can continue to communicate with the current LTE base station (e.g., eNB 602). Furthermore, eNB 602 can communicate with the 5G NR base station (e.g., gNB 604) and can transfer data between the core network 600 and gNB 604. Therefore, the EPC network 600 can be used (or reused), and gNB 604 can serve as additional capacity for user equipment, for example, to provide increased downlink throughput for the UE. In other words, LTE can be used for control plane signaling, and NR can be used for user plane signaling. Therefore, LTE can be used to establish connections to the network, and NR can be used for data services.

[0139] Figure 6B The proposed protocol stack for eNB 602 and gNB 604 is illustrated. As shown, eNB 602 may include a Media Access Control (MAC) layer 632 that interfacing with Radio Link Control (RLC) layers 622a-622b. RLC layer 622a may also interfacing with Packet Data Convergence Protocol (PDCP) layer 612a, and RLC layer 622b may interfacing with PDCP layer 612b. Similar to the dual connectivity specified in Advanced LTE Release 12, PDCP layer 612a may interfacing with EPC network 600 via Primary Cell Group (MCG) bearer, while PDCP layer 612b may interfacing with EPC network 600 via decoupling bearer.

[0140] Additionally, as shown in the figure, gNB 604 may include a MAC layer 634 that interfacing with RLC layers 624a-624b. RLC layer 624a may interfacing with the PDCP layer 612b of eNB 602 via the X2 interface for information exchange and / or coordination (e.g., UE scheduling) between eNB 602 and gNB 604. Furthermore, RLC layer 624b may interfacing with PDCP layer 614. Similar to the dual connectivity specified in Advanced LTE Release 12, PDCP layer 614 may interfacing with EPC network 600 via a secondary cell group (SCG) bearer. Therefore, eNB 602 can be considered as the primary node (MeNB), and gNB 604 can be considered as the secondary node (SgNB). In some cases, it may be required that the UE maintain connectivity with both the MeNB and the SgNB. In such cases, the MeNB can be used to maintain the Radio Resource Control (RRC) connection with the EPC, while the SgNB can be used for capacity (e.g., additional downlink and / or uplink throughput).

[0141] Figure 7A , Figure 7B and Figure 8 5G Core Network Architecture—Interoperability with Wi-Fi

[0142] In some implementations, access to the 5G core network (CN) can be made via (or through) cellular connections / interfaces (e.g., via 3GPP communication architecture / protocols) and non-cellular connections / interfaces (e.g., non-3GPP access architecture / protocols such as Wi-Fi connections). Figure 7AAn example of a 5G network architecture according to some implementation schemes is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN. As shown, a user equipment device (e.g., UE 106) can access the 5G CN via both a radio access network (RAN, e.g., gNB or base station 604) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to a non-3GPP Interoperability Function (N3IWF) 702 network entity. N3IWF may include a connection to the core access and mobility management function (AMF) 704 of the 5G CN. AMF 704 may include an instance of 5G mobility management (5G MM) functions associated with UE 106. Additionally, the RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register access simultaneously via gNB 604 and AP 112. As shown, AMF 704 may include one or more functional entities associated with the 5G CN (e.g., Network Slice Selection Function (NSSF) 720, Short Message Service Function (SMSF) 722, Application Function (AF) 724, Unified Data Management (UDM) 726, Policy Control Function (PCF) 728, and / or Authentication Server Function (AUSF) 730). It should be noted that these functional entities can also be supported by the 5G CN's Session Management Functions (SMF) 706a and SMF 706b. AMF 706 can connect to (or communicate with) SMF 706a. Furthermore, gNB 604 can communicate with (or connect to) User Plane Function (UPF) 708a, which can also communicate with SMF 706a. Similarly, N3IWF 702 can communicate with UPF 708b, which can also communicate with SMF 706b. Both UPFs can communicate with data networks (e.g., DN 710a and 710b) and / or the Internet 700 and the Internet Protocol (IP) Multimedia Subsystem / IP Multimedia Core Network Subsystem (IMS) Core Network 710.

[0143] Figure 7BAn example of a 5G network architecture according to some implementation schemes is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access to the 5G CN as well as non-3GPP access. As shown, a user equipment device (e.g., UE 106) can access the 5G CN via both a radio access network (RAN, such as gNB or base station 604 or eNB or base station 602) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to the N3IWF 702 network entity. The N3IWF may include a connection to the AMF 704 of the 5G CN. AMF 704 may include an instance of 5G MM functionality associated with UE 106. Additionally, the RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register access simultaneously via gNB 604 and AP 112. Additionally, the 5G CN can support dual registration of the UE on both a legacy network (e.g., LTE via base station 602) and a 5G network (e.g., via base station 604). As shown, base station 602 can have connections to both the Mobility Management Entity (MME) 742 and the Service Gateway (SGW) 744. MME 742 can have connections to both SGW 744 and AMF 704. Furthermore, SGW 744 can have connections to both SMF 706a and UPF 708a. As shown, AMF 704 can include one or more functional entities associated with the 5G CN (e.g., NSSF 720, SMSF 722, AF 724, UDM 726, PCF 728, and / or AUSF 730). Note that UDM 726 can also include Home Subscriber Server (HSS) functionality, and PCF can also include Policy and Charging Rules (PCRF) functionality. It should also be noted that these functional entities can also be supported by the 5G CN's SMF 706a and SMF 706b. The AMF 706 can connect to (or communicate with) the SMF 706a. Furthermore, the gNB 604 can communicate with (or connect to) the UPF 708a, which in turn can communicate with the SMF 706a. Similarly, the N3IWF 702 can communicate with the UPF 708b, which in turn can communicate with the SMF 706b. Both UPFs can communicate with data networks (e.g., DN 710a and 710b) and / or the Internet 700 and the IMS core network 710.

[0144] It should be noted that, in various implementations, one or more of the network entities described above may be configured to perform methods for improving security checks in 5G NR networks, including mechanisms for eliminating and / or replacing Physical Uplink Shared Channels (PUSCH) with different priorities, such as those used for Ultra Reliable Low Latency Communication (URLLC) and / or Enhanced URLLC (eURLLC) as further described herein.

[0145] Figure 8 An example of a baseband processor architecture for a UE (e.g., UE 106) according to some implementation schemes is shown. As described above, Figure 8 The baseband processor architecture 800 described herein can be implemented on one or more radio components (e.g., radio components 329 and / or 330) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access stratum 810 may include a 5G NAS 820 and a traditional NAS 850. The traditional NAS 850 may include a communication connection with a traditional access stratum (AS) 870. The 5G NAS 820 may include communication connections with a 5G AS 840 and a non-3GPP AS 830, as well as a Wi-Fi AS 832. The 5G NAS 820 may include functional entities associated with both access strata. Therefore, the 5G NAS 820 may include multiple 5G MM entities 826 and 828 and 5G session management (SM) entities 822 and 824. The traditional NAS 850 may include functional entities such as Short Message Service (SMS) entity 852, Evolved Packet System (EPS) Session Management (ESM) entity 854, Session Management (SM) entity 856, EPS Mobility Management (EMM) entity 858, and Mobility Management (MM) / GPRS Mobility Management (GMM) entity 860. Furthermore, the traditional AS 870 may include functional entities such as LTE AS 872, UMTS AS 874, and / or GSM / GPRS 876.

[0146] Therefore, the baseband processor architecture 800 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access) networks. It's important to note that, as shown in the figure, the 5G MM can maintain separate connection management and registration management state machines for each connection. Furthermore, a device (e.g., UE 106) can register to a single PLMN (e.g., a 5G CN) using both 5G cellular and non-cellular access. Additionally, a device can be connected in one access and idle in another, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0147] It should be noted that, in various implementations, one or more of the aforementioned functional entities of the 5G NAS and / or 5G AS may be configured to perform methods for eliminating and / or replacing Physical Uplink Shared Channels (PUSCH) with different priorities, such as those used for Ultra Reliable Low Latency Communication (URLLC) and / or Enhanced URLLC (eURLLC) as further described herein.

[0148] PUSCH elimination and / or replacement

[0149] In current implementations, such as those in 3GPP Release 15 standardization, downlink control information (DCI) on the Physical Downlink Control Channel (PDCCH) and / or scheduling of the Physical Uplink Shared Channel (PUSCH) via Configuration Grant (CG) can be utilized. It should be noted that in various implementations, the PUSCH can be used to carry (e.g., from the UE to network entities such as base stations) Radio Resource Control (RRC) signaling messages, uplink control information, and / or application (or user) data. Furthermore, there are two types of configured (uplink) grants: Type 1 and Type 2. For Type 1 CG, RRC signaling provides the configured uplink grant (including periodicity), while for Type 2, RRC signaling defines the periodicity of the configured uplink grant, and the PDCCH addressed to the configured Scheduled Radio Network Temporary Identifier (CS-RNTI) can signal and activate or deactivate the configured uplink grant. In other words, the PDCCH addressed to CS-RNTI can indicate that the configured uplink grant can be implicitly reused according to the periodicity defined by the RRC, for example, until deactivation.

[0150] Furthermore, in current implementations, such as those in 3GPP Release 15 standardization, single-slot transmissions with PUSCH mapping type A or PUSCH mapping type B can be used for dynamic uplink granting or configured uplink granting. Additionally, PUSCHs with slot aggregation can be used for dynamic uplink granting (DG) and / or configured uplink granting (CG). Therefore, for PUSCHs with slot aggregation, transport blocks can be used for transmissions in different slots following a Hybrid Automatic Repeat Request (HARQ) redundancy version sequence. The number of slots involved in slot aggregation (e.g., aggregation factor) can be configured individually via RRC signaling. Furthermore, for DG PUSCHs, the aggregation factor can be configured for DG PUSCHs via the pusch-AggregationFactor {n2, n4, n8} (e.g., 2 slots, 4 slots, and / or 8 slots). Additionally, for CGPUSCH, the aggregation coefficient can be configured via the parameter repK {n1, n2, n4, n8} (e.g., 1 slot, 2 slots, 4 slots, or 8 slots). For the HARQ redundancy version sequence used for slot aggregation, for CG PUSCH, the HARQ redundancy version sequence can be configured with RRC, for example, repK-RV{s1-0231, s2-0303, s3-0000}. Furthermore, the HARQ redundancy version sequence for DG PUSCH can be derived by repeating from s1-0231, and the first redundancy version used can be dynamically signaled by the base station in the uplink DCI; for example, the base station can signal the start of PUSCH slot aggregation with a "3". Therefore, if the pusch-AggregationFactor is n8, the HARQ redundancy version sequence [3102 3102] can be used for transmission over 8 slots. It should be noted that in 3GPP Release 15, the pusch-AggregationFactor and repK can be configured with RRC for both DG and CG respectively. Additionally, in the case of PUSCH slot aggregation, although the HARQ redundancy version can differ for transmissions in different slots, the time-frequency resources occupied by the PUSCH can be the same across slots.

[0151] Furthermore, in current implementations, such as those standardized by 3GPP Release 15, the higher-level configuration parameters repK and repK-RV define the K repetitions to be applied to the transmitted transport block and the redundancy version pattern to be applied to these repetitions. Additionally, if the repK-RV parameter is not provided in the CG configuration (e.g., via the configuredGrantConfig parameter), the redundancy version authorized by the configuration for uplink transmission can be set to 0. Otherwise, for the nth transmission timing in the K repetitions, n=1, 2, ..., K, the redundancy version can be associated with the (mod(n-1,4)+1)th value in the configured RV sequence. Therefore, the initial transmission of the transport block can begin at...

[0152] (i) If the configured RV sequence is {0,2,3,1}, then it is the first transmission opportunity of K repetitions;

[0153] (ii) If the configured RV sequence is {0,3,0,3}, then any transmission timing of K repetitions associated with RV=0; and / or

[0154] (iii) If the configured RV sequence is {0,0,0,0}, then it is any transmission timing that is repeated K times, except for the last transmission timing when K=8.

[0155] It should be noted that for any RV sequence, a repetition may terminate after K repetitions and / or at the last transmission opportunity among the K repetitions within period P and / or from the start symbol of a repetition overlapping with a PUSCH having the same HARQ process scheduled by DCI format 0_0 or DCI format 0_1, whichever arrives first. It should also be noted that it may not be desirable for the UE to be configured with a duration for transmitting K repetitions greater than the duration derived from periodicity P. Additionally, if the UE determines that, for a transmission opportunity, the number of symbols available for PUSCH transmission in the time slot is less than the transmission duration L, the UE will not transmit PUSCH in the transmission opportunity. It should be noted that for both Type 1 PUSCH transmissions and Type 2 PUSCH transmissions utilizing configuration grants, when the UE is configured with repK>1, the UE may repeat the transmission block on repK consecutive time slots with the same symbol allocation in each time slot. Furthermore, according to the conditions specified in 3GPP TS 38.213, Type 1 PUSCH transmissions or Type 2 PUSCH transmissions utilizing configuration grants in a time slot may be omitted.

[0156] Furthermore, in current implementations (such as those standardized by 3GPP Release 15), uplink resources are available for data transmission from the UE using configuration granting. However, if there is no data in the buffer for configuration granting transmissions, the UE does not need to transmit on the configured resources. Therefore, it is useful to distinguish between actual CG PUSCH transmissions and CGPUSCH transmissions. Since CG transmissions are initiated by the UE and the base station may not be aware of potential CG transmissions initiated by the UE, two conditions are defined regarding DG scheduling timing: for example, if DG transmissions overlap with CG transmissions, the UE may have sufficient time to prepare for the DG transmission.

[0157] The first condition / restriction regarding the scheduling of DG on a (e.g., time-overlapping a) CG transmission timing is that it may not be desirable for the UE to be scheduled by the Physical Downlink Control Channel (PDCCH) ending with symbol i to transmit the Physical Uplink Shared Channel (PUSCH) on the serving cell that time overlaps with the transmission timing, in which the symbol i is not expected to be scheduled. I The end is not at the symbol j At least before the start N 2 If a symbol is specified, the UE is allowed to utilize configuration authorization (e.g., as defined in 3GPP TS38.321 Release 15) from the serving cell to obtain symbols. j PUSCH transmission begins. Note that in such instances, the number of symbols is determined based on the UE's processing capabilities, as defined in 3GPP Release 15. N 2 The value of . Additionally, in such instances, N 2 The symbol duration can be based on the minimum of the subcarrier interval corresponding to the PUSCH authorized by the configuration and the subcarrier interval of the PDCCH that schedules the PUSCH.

[0158] Additionally, the second condition regarding CG is that there exists a transmission opportunity that allows the UE to utilize configuration authorization (e.g., as defined in 3GPP TS38.321 Release 15) to transmit PUSCH, where the Hybrid Automatic Repeat Request (HARQ) process on the serving cell begins at symbol [symbol missing]. i The symbols that appeared later j And if the end of PDCCH and the symbol j The gap between the beginnings is less than N 2 If there is a symbol, then it may not be expected that the UE will be represented by the symbol. iThe terminating PDCCH scheduling is used to transmit PUSCH on the serving cell for the HARQ process. Note that in such instances, the symbol is determined based on the UE's processing capabilities as defined in 3GPP Release 15. N 2 The value of . Additionally, in such instances, N 2 The symbol duration can be based on the minimum of the subcarrier interval corresponding to the PUSCH authorized by the configuration and the subcarrier interval of the PDCCH that schedules the PUSCH.

[0159] In the first condition described above, the PDCCH scheduling DG PUSCH that overlaps with the CG PUSCH transmission timing must have N² symbols present before the start of the CGPUSCH transmission timing. Therefore, using this first condition, the UE does not need to handle cases where the PDCCH scheduling DGPUSCH has fewer than N² symbols present before the start of the CG PUSCH transmission timing. In the second condition described above, if the DG PUSCH has the same HARQ process ID as the HARQ process ID associated with the CG PUSCH transmission timing, then regardless of whether the DG PUSCH overlaps with the CG PUSCH transmission timing, the PDCCH scheduling DG PUSCH must have at least N² symbols present before the start of the CG transmission timing.

[0160] For example, under the first condition mentioned above, it can be defined as follows: Figure 9 The three scenarios are illustrated below. In the first scenario, where dynamic granting (e.g., PDCCH 920 of DG PUSCH) schedules the transmission to occur before the configuration granting opportunity, the transmission will succeed as long as PUSCH-1 922 (e.g., configured by PDCCH 920 of DG PUSCH) occurs for at least N² symbols after the dynamic granting, as shown in the figure. In the second scenario, where dynamic granting (e.g., PDCCH 930 of DG PUSCH) schedules the transmission to occur after the configuration granting opportunity, the transmission will be dropped to support configuration-granted transmissions, such as CG transmission 932, even if PUSCH-2 934 occurs for at least N² symbols after the dynamic granting, as shown in the figure. In the third scenario, where dynamic granting (e.g., PDCCH 940 of DG PUSCH) occurs for less than N² symbols before the configuration granting opportunity, the scheduled transmission PUSCH-2 942 will be dropped because the dynamic granting occurs within N² symbols of the configuration granting opportunity and is therefore not permitted.

[0161] For example, under the second condition mentioned above, it can be defined as follows: Figure 10The diagram illustrates two scenarios. As shown, a first CG configuration can be associated with a first HARQ process, and a second CG configuration can be associated with a second HARQ process; therefore, CG transmission 1022 can be associated with both the first and second HARQ processes. In the first scenario, dynamic licensing (e.g., PDCCH 1030 of DG PUSCH) schedules the transmission associated with the first HARQ process (e.g., PUSCH-5 1032) to occur at the earliest start time of dynamic licensing. However, in the second scenario, the transmission will be dropped because it is not permitted. In the second scenario, dynamic licensing (e.g., PDCCH 1040 of DG PUSCH) schedules the transmission associated with the third HARQ process (e.g., PUSCH-6 1042) to occur at the earliest start time of dynamic licensing, and in the second scenario, the transmission will occur because it is not associated with either the first or second HARQ process.

[0162] Therefore, in the current implementation, any DG transmission is allowed if the DG grant for PUSCH is sent with at least N² symbols before the start of the CG transmission timing (e.g., there are no restrictions on the HARQ process ID or the overlap with the CG transmission timing, but there must be at least N² symbols between the scheduling DCI and the DG transmission). Additionally, in the current implementation, if the DG grant for PUSCH is sent with fewer than N² symbols before the start of the CG transmission timing, DG PUSCH is allowed as long as it starts after the CG transmission timing (note that the first condition excludes the case where DG PUSCH overlaps with the CG transmission timing and does not allow DG PUSCH to start before the CG transmission timing, because the gap between it and the scheduling DCI will be less than N²), and the DG PUSCH HARQ process identifier (ID) does not overlap with any of the HARQ process IDs of the CG transmission timing.

[0163] In addition to these conditions, in current specific implementations, such as those standardized by 3GPP Release 15, for DG PUSCH overwrite configurations with a repetition factor K>1:

[0164] (i) If the HARQ process is the same between DG and CG, then DG overwrites all remaining repetition timings after PDCCH reception ends, for example, at the time line specified in Section 6.1 of 3GPP TS 38.214.

[0165] (ii) Otherwise, the DG only overwrites the CG repeats that overlap with the DG at timelines specified, for example, in Section 6.1 of 3GPP TS 38.214.

[0166] In addition, DG supports overwriting CG when timeline conditions are met under various circumstances.

[0167] For example, if the HARQ process ID of the DG is different from the HARQ process ID of the CG, then overwriting the DG of the CG is supported when the timeline conditions are met. Note that in the first scenario, both the DG and CG can be single-transmissions. In this case, if the CG conflicts with the DG, the CG is discarded or overwritten, and the UE can use the DG for transmission. Note that in the second scenario, the DG can be a single-transmission, and the CG can have time-slot aggregation. In this case, if the CG transmission at a transmission time conflicts with the DG, the CG transmission at that transmission time is discarded or overwritten, and the UE can use the DG for transmission. Additionally, for transmission times that do not conflict with the DG, the CG transmission can be performed by the UE. Further note that in the third scenario, both the DG and CG can have time-slot aggregation. In this case, if the CG transmission at a transmission time conflicts with the DG transmission, the CG transmission at that transmission time is discarded or overwritten, and the UE can use the DG transmission for transmission. Additionally, for CG transmission timings that do not conflict with any DG transmissions, CG transmission can be performed by the UE. Furthermore, in the fourth scenario, DG can have time slot aggregation, and CG can be transmitted in a single time slot.

[0168] Furthermore, if the HARQ process ID of the DG is the same as the HARQ process ID of the CG, then overwriting the DG of the CG is supported when the timeline conditions are met. It should be noted that in the first scenario, both the DG and CG can be single-transmissions. In this scenario, if the CG conflicts with the DG, the CG is discarded or overwritten, and the UE can use the DG for transmission. In the second scenario, the DG can be a single-transmission, and the CG can have time-slot aggregation. In this scenario, if the CG transmission at a given time slot conflicts with the DG, the CG transmission at that time slot and subsequent transmission times are discarded (or overwritten), and the UE can use the DG for transmission. In the third scenario, both the DG and CG can have time-slot aggregation.

[0169] As another example, if a CG transmission conflicts with a DG transmission at a certain time, then the DG that supports overwriting the CG is supported when the timeline conditions are met. Then, the CG transmissions at that time and subsequent times are discarded (or overwritten), and the UE uses the DG transmission for transmission.

[0170] Additionally, if a CG transmission conflicts with a DG transmission at a certain time, the DG that supports overwriting the CG will be supported when the timeline conditions are met. Then, the CG transmission at that time will be discarded or overwritten, and the UE will use the DG transmission for transmission.

[0171] Figures 12A to 12CAn example of a specific implementation of configuration-based authorization / dynamic authorization conflict handling based on the above conditions is shown. For example, Figure 12A It shows spanning multiple time slots (e.g., time slots) n to n+ 3) An example of a conflict between a scheduled configuration grant (e.g., CG 1210a-CG1210d) and a dynamic grant (e.g., DG1212 with a different HARQ-ID) that has a different HARQ process ID compared to the configuration grant. As shown in the figure, based on the above conditions / rules, the UE will discard and / or overwrite the transmission opportunity corresponding to the dynamic grant (e.g., therefore the UE can transmit the dynamic grant), and transmit during the remaining configuration grant transmission opportunity. For example, Figure 12B It shows spanning multiple time slots (e.g., time slots) n to n+3 An example of a conflict between a scheduled configuration grant (e.g., CG 1210a-CG 1210d) and a dynamic grant (e.g., DG 1222 with the same HARQ-ID) having the same HARQ process ID as the configuration grant. As shown in the figure, based on the above conditions / rules, the UE will discard and / or overwrite the transmission timing corresponding to the dynamic grant (e.g., so the UE can transmit the dynamic grant) and any configuration grants occurring after the dynamic grant, and transmit during the remaining configuration grant transmission timing. As another example, Figure 12C It shows spanning multiple time slots (e.g., time slots) n to n+ 3 An example of a conflict between a scheduled configuration grant (e.g., CG 1210a-CG 1210d) and a dynamic grant (e.g., DG 1212 with a different HARQ-ID) that has a different HARQ process ID compared to the configuration grant and is also scheduled across multiple time slots. As shown in the figure, based on the above conditions / rules, the UE will discard and / or overwrite the transmission opportunity corresponding to the dynamic grant (e.g., so the UE can transmit the dynamic grant), and transmit during the remaining configuration grant transmission opportunities.

[0172] Given the above, 3GPP Release 16 standardization enhancements include the introduction of PUSCH repetition type A and PUSCH repetition type B. Under PUSCH repetition type A, for dynamically licensed PUSCHs, the repetition factor (which can be dynamically indicated by the base station) indicates the number of time slots for transmitting the PUSCH. It should be noted that the main difference between PUSCH repetition type A and PUSCHs with time slot aggregation lies in how the aggregation factor or repetition factor is signaled; for PUSCH repetition type A, it is via dynamic signaling (e.g., UL DCI), while for PUSCHs with time slot aggregation, it is via RRC signaling. Under PUSCH repetition type B, PUSCH transmission includes one or more nominal repetitions, and if a nominal repetition will cross a time slot boundary, each nominal repetition can be segmented into 0, 1, or 1 actual repetitions, thus conflicting with OFDM symbols not used for uplink transmission (e.g., from SFI or invalid symbol mode). It should be noted that due to conflicts with symbols not used for uplink transmission and / or crossing time slot boundaries, nominal repetitions may not result in any actual repetitions; for example, the entire nominal repetition may be discarded. It should be further noted that if a nominal repeat has more than one OFDM symbol, but an actual repeat derived from the nominal repeat has a single OFDM symbol, then one symbol of the actual repeat can be discarded. Additionally, a PUSCH transmission with repeat type B can be characterized by three parameters: the starting symbol (S), the number of symbols in the nominal repeat (L), and the number of nominal repeats in the PUSCH (K).

[0173] In addition to introducing PUSCH repetition type A and PUSCH repetition type B, 3GPP Release 16 also introduces enhancements to configuration authorization. Specifically, for the uplink bandwidth portion at the uplink serving cell, the network can be configured with up to 12 configuration authorization configurations, including type 1 and type 2 configuration authorizations. Therefore, three types of transmission schemes can be considered, such as single-slot transmission, multi-slot transmission, and PUSCH slot aggregation or PUSCH repetition type A and / or PUSCH repetition type B.

[0174] Furthermore, 3GPP Release 16 introduced physical layer priority indicators, for example, to support the multiplexing of UCI and PUSCH for different services such as enhanced mobile broadband (eMBB), URLLC, and / or eURLLC. Specifically, for PUSCH, configuration granting configuration can be an RRC configured using physical layer priorities (low priority, high priority), thus configuration granting PUSCH transmissions can be associated with physical layer priorities. Similarly, for dynamically granting PUSCH, priority indicator fields are introduced in DCI format 0_1 ​​and UL DCI format (0_2), thus dynamically granting PUSCH can also be associated with physical layer priorities.

[0175] Furthermore, since multiple configuration grant configurations are supported on the Bandwidth Part (BWP) in 3GPP Release 16, it is unclear whether a later configuration grant with the same physical layer priority is allowed to override an earlier configuration grant. Additionally, assuming such UE behavior is supported, blind detection by the base station could become extremely difficult, essentially requiring the base station receiver to attempt to decode every possible configuration grant. This scenario would also negatively impact system performance and potentially hinder network utilization of configuration grants, ultimately harming the UE experience.

[0176] Furthermore, due to the support for multiple configuration licenses on the bandwidth portion, nested transmissions may occur, for example, such as... Figure 11 As shown in the figure, the UE can be configured with multiple configuration-granted PUSCHs as well as dynamically-granted PUSCHs. In such instances, the UE may need to hold multiple transport blocks in its Layer 1 buffer, and blind detection at the base station can be very difficult.

[0177] The enhancements introduced in 3GPP Release 16 may result in different UE behaviors than those discussed above with respect to 3GPP Release 15, such as those based on PUSCH repetition type A and PUSCH repetition type B, multiple configuration authorization configurations on the bandwidth portion, and / or due to the physical layer priority of PUSCH. Furthermore, with the introduction of physical layer priority for PUSCH, elimination and replacement behaviors have been pursued as a solution for handling URLLC services in the face of ongoing eMBB services, in order to reduce scheduling / transmission latency. Additionally, given the introduction of PUSCH repetition type A and PUSCH repetition type B, the conditions / rules mentioned above associated with 3GPP Release 15 behavior do not cover all aspects of the enhancements introduced in 3GPP Release 16.

[0178] The embodiments described herein provide systems, methods, and mechanisms for eliminating and / or replacing transmissions on a Physical Uplink Shared Channel (PUSCH) with different priorities, such as those for Ultra-Reliable Low-Latency Communication (URLLC) and / or Enhanced URLLC (eURLLC). In some embodiments, any duplicates of the first PUSCH transmission that overlap with any portion of the second PUSCH transmission can be overwritten if the second PUSCH transmission does not share a HARQ process ID with the first PUSCH transmission (e.g., an existing PUSCH transmission). In some embodiments, any duplicates of the first PUSCH transmission that overlap with any portion of the second PUSCH transmission (e.g., time-overlapping and / or temporally overlapping) between the earliest duplicate of the first PUSCH transmission that overlaps with any portion of the second PUSCH transmission (e.g., time-overlapping and / or temporally overlapping) and the last duplicate of the first PUSCH transmission that overlaps with any portion of the second PUSCH transmission can be overwritten. In other words, in some implementations, all repetitions (including the earliest and latest repetitions) between the earliest and latest repetitions of the first PUSCH transmission that overlap with any part of the second PUSCH transmission may be discarded and / or omitted. In some implementations, if the second PUSCH transmission shares a HARQ process ID with the first PUSCH transmission (e.g., an existing PUSCH transmission) (and / or when that is), any repetitions of the first PUSCH transmission between the earliest repetition of the first PUSCH transmission that overlaps with any part of the second PUSCH transmission and the last repetition of the first PUSCH transmission may be overwritten.

[0179] For example, Figure 13Examples of possible handling of conflicting transmissions according to some implementation schemes are illustrated. As shown, in cases where a transmission associated with a configuration-granted PUSCH configured as a single-slot PUSCH conflicts with a transmission associated with a dynamically-granted PUSCH configured as a single-slot PUSCH, having aggregated PUSCHs, and / or having PUSCHs with repetition type A, for example, as described above, the UE (such as UE 106) may comply with 3GPP Release 15 timing requirements, and PUSCH repetition type A may comply with PUSCHs with aggregated handling. Additionally, in cases where a transmission associated with a configuration-granted PUSCH configured as having repetitions and / or having PUSCHs with repetition type A conflicts with a transmission associated with a dynamically-granted PUSCH configured as a single-slot PUSCH, having aggregated PUSCHs, and / or having PUSCHs with repetition type A, for example, as described above, the UE (such as UE 106) may comply with 3GPP Release 15 timing requirements, and PUSCH repetition type A may comply with PUSCHs with aggregated handling. Furthermore, in cases where a transmission associated with a configuration-granted PUSCH configured to have repetition type B conflicts with a transmission associated with a dynamically-granted PUSCH configured as a single-slot PUSCH, an aggregated PUSCH, and / or a PUSCH with repetition type A, the UE (such as UE 106) may comply with the 3GPP Release 15 timing requirements, and the transmission associated with the dynamically-granted PUSCH may overwrite the transmission associated with the configuration-granted PUSCH, provided that any part of the transmission associated with the dynamically-granted PUSCH conflicts with any part of the transmission associated with the configuration-granted PUSCH, for example, as referenced herein. Figure 14 , Figure 15 and Figure 16 Further described. Furthermore, in cases where a transport associated with a configuration-granted PUSCH conflicts with a transport associated with a dynamically-granted PUSCH configured with PUSCH repetition type B, any transport of the dynamically-granted PUSCH that partially overlaps with the transport associated with the configuration-granted PUSCH may overwrite the transport associated with the configuration-granted PUSCH, for example, as referenced herein. Figure 14 , Figure 15 and Figure 16 Further description.

[0180] In some implementations, if all OFDM symbols in a nominal repetition of a dynamically licensed PUSCH with repetition type B are used in a transmission (and / or when), the 3GPP Release 15 overwrite rules as discussed above can be used. In some implementations, if a transmission associated with a single-slot PUSCH overlaps (and / or when) any nominal repetition of another PUSCH transmission configured with PUSCH repetition type B, the two PUSCHs are considered to overlap (e.g., time-overlapping and / or temporally overlapping). In some implementations, if a transmission associated with a single-slot PUSCH overlaps (and / or when) at least one actual repetition of another PUSCH transmission configured with PUSCH repetition type B, the two PUSCHs are considered to overlap. For example, as... Figure 14 As shown, if a single-slot configuration grant PUSCH overlaps at least a portion of the nominal repetition of a dynamic grant PUSCH with repetition type B, but does not overlap with any actual repetition of a dynamic grant PUSCH with repetition type B (and / or when), then a UE (such as UE 106) may transmit on the configuration grant within a single slot that does not overlap with the actual transmission of a dynamic grant PUSCH with repetition type B.

[0181] In some implementations, if a transmission associated with a configuration-granted PUSCH having slot aggregation and / or PUSCH repetition type A overlaps at least a portion of the nominal repetition of a dynamic-granted PUSCH having repetition type B, but does not overlap with any actual repetition of the dynamic-granted PUSCH having repetition type B (and / or when), then the UE (such as UE 106) may transmit on the configuration-granted PUSCH within a slot that does not overlap with the actual transmission of the dynamic-granted PUSCH having repetition type B. Note that the symbol... j (For example, as discussed above) could be about a first time slot in which configuration-granted PUSCH transmissions overlap with dynamic-granted PUSCH transmissions.

[0182] In some implementations, if a transmission associated with a single-slot dynamic grant PUSCH overlaps at least a portion of a nominal repetition of a configuration grant PUSCH with repetition type B, but does not overlap with any actual repetition of a configuration grant PUSCH with repetition type B (and / or when), then the UE (such as UE 106) may transmit on the dynamic grant PUSCH within a slot that does not overlap with the actual transmission of the configuration grant PUSCH with repetition type B. Note that the symbol... j (For example, as discussed above) could be the first actual repetition of all actual repetitions of configuration-authorized PUSCH transports that overlap with the dynamic-authorized PUSCH.

[0183] In some implementations, if a transmission associated with a configuration-granted PUSCH having repetition type B overlaps (and / or when) at least a portion of a repetition of a dynamic-granted PUSCH having slot aggregation and / or PUSCH repetition type A, then a UE (such as UE 106) may transmit on the configuration-granted PUSCH within slots that do not overlap with transmissions of the dynamic-granted PUSCH having repetition type A, for example, as Figure 15 As shown. Figure 15 As shown, configuring the authorization PUSCH can configure the UE in the first time slot (e.g., time slot). n CG-1 and CG-2 are transmitted in the second time slot (e.g., time slot 1). n +1) transmits CG-3 and CG-4. Additionally, the Dynamic Grant PUSCH can configure the UE to transmit DG-1 in the first time slot and DG-2 in the second time slot. As shown in the figure, a UE supporting inter-column transmission (such as UE 106) can transmit CG-1 and DG-1 in the first time slot and CG-3 and DG-2 in the second time slot. Therefore, when the configured grant and dynamic grant overlap, the UE can transmit the dynamic grant. Furthermore, when the configured grant and dynamic grant do not overlap, the UE can transmit the configured grant. In other words, on a repetitive basis, each actual repetition in the configured grant PUSCH is checked against each actual repetition in the dynamic grant PUSCH.

[0184] In some implementations, if a transmission associated with a configuration grant PUSCH having repetition type B overlaps (and / or when) at least a portion of a repetition of a dynamic grant PUSCH having slot aggregation and / or PUSCH repetition type A, then the UE (such as UE 106) may transmit on any configuration grant PUSCH that occurs prior to the transmission of the dynamic grant PUSCH having repetition type A, for example, as Figure 16 As shown. Figure 16 As shown, configuring the authorization PUSCH can configure the UE in the first time slot (e.g., time slot). n CG-1 and CG-2 are transmitted in the second time slot (e.g., time slot 1). n +1) transmits CG-3 and CG-4. Additionally, Dynamic Grant PUCSH can configure the UE to transmit DG-1 in the first time slot and DG-2 in the second time slot. As shown in the figure, UEs that do not support inter-column transmission (such as UE 106) can transmit CG-1 and DG-1 in the first time slot and DG-2 in the second time slot. Therefore, in cases where configuration grant and dynamic grant overlap, the UE can transmit dynamic grant. Furthermore, in cases where configuration grant performs the first dynamic grant transmission, the UE can transmit configuration grant.

[0185] In some implementations, if a transmission associated with a configuration grant PUSCH having repetition type B overlaps (and / or when) with at least a portion of a repetition of a dynamic grant PUSCH having repetition type B, the UE (such as UE 106) may transmit on the configuration grant PUSCH in a time slot that does not overlap with a transmission of the dynamic grant PUSCH having repetition type B. Therefore, in the case of overlapping configuration grant PUSCHs and dynamic grant PUSCHs, the UE may transmit on the dynamic grant PUSCH. Furthermore, in the case of non-overlapping configuration grant PUSCHs and dynamic grant PUSCHs, the UE may transmit on the configuration grant PUSCH. In other words, each actual repetition in the configuration grant PUSCH is checked against each actual repetition in the dynamic grant PUSCH on a repetition-by-repetition basis.

[0186] In some implementations, if a transmission associated with a configuration grant PUSCH of repetition type B overlaps (and / or when) with at least a portion of a repetition of a dynamic grant PUSCH of repetition type B, the UE (such as UE 106) may transmit on any configuration grant PUSCH that occurs prior to the transmission of the dynamic grant PUSCH of repetition type B. Therefore, in the case of overlapping configuration grant PUSCHs and dynamic grant PUSCHs, the UE may transmit on the dynamic grant PUSCH. Furthermore, in the case of a first dynamic grant PUSCH transmission occurring on a configuration grant PUSCH, the UE may transmit on the configuration grant PUSCH.

[0187] In some implementations, a PUSCH can be specified using one of two priority levels. The first priority level can be associated with low priority and / or no priority (e.g., a PUSCH scheduled without a priority level, such as a PUSCH scheduled by DCI format 0_0, a configuration-granted PUSCH with a configuration grant configuration that is not configured with physical layer priority, etc.). The second priority level can be associated with high priority. Similarly, in some implementations, when dynamic grant has a first priority level, the aforementioned 3GPP version 15 timeline for dynamic grant can be maintained using repetition by overwriting, for example, to cover PUSCH repetition type A and PUSCH repetition type B. Similarly, in some implementations, when dynamic grant has a second priority level, the aforementioned 3GPP version 15 timeline for dynamic grant can be maintained using repetition by overwriting, for example, to cover PUSCH repetition type A and PUSCH repetition type B. In some implementations, a configuration grant with a second priority level can overwrite a priority dynamic grant with a first priority level. In some implementations, such rules (and / or conditions) may be applied on a per-repetition basis, for example to cover PUSCH repetition type A and PUSCH repetition type B.

[0188] In some implementations, Section 6.1 of 3GPP TS 38.214 version 16.2 can be modified to declare:

[0189] If the UE reports the ability to prioritize within the UE, and if the PUSCH corresponding to the configuration authorization and the PUSCH scheduled by the PDCCH on the serving cell partially or completely overlap in time,

[0190] If the PUSCH corresponding to the configuration authorization has in configuredGrantConfig If a PUSCH scheduled by the PDCCH is set to a priority of 1 (i.e., high priority) and is indicated as low priority by setting the priority indicator field in the scheduling DCI to 0 or by having no priority indicator field in the scheduling DCI, then the UE is expected to transmit the PUSCH corresponding to the configuration grant, and the PUSCH transmission scheduled by the PDCCH is discarded starting from the first symbol of the PUSCH transmission scheduled by the PDCCH that overlaps with the PUSCH corresponding to the configuration grant.

[0191] In the case of repeated PUSCH, overlap processing is performed separately for each repeated PUSCH.

[0192] It is not expected that the UE will be scheduled by PDCCH for another PUSCH, wherein the PUSCH is not earlier than the end of the priority PUSCH and begins before the end of the time domain allocation of the eliminated PUSCH.

[0193] Furthermore, in some implementations, Section 6.1 of 3GPP TS 38.214 version 16.2 can be modified to declare:

[0194] If the UE reports the ability to prioritize within the UE, and if the PUSCH corresponding to the configuration authorization and the PUSCH scheduled by the PDCCH on the serving cell partially or completely overlap in time,

[0195] If the PUSCH corresponding to the configuration authorization has in configuredGrantConfig If a PUSCH scheduled by the PDCCH is set to a priority of 1 (i.e., high priority) and is indicated as low priority by setting the priority indicator field in the scheduling DCI to 0 or by having no priority indicator field in the scheduling DCI, then the UE is expected to transmit the PUSCH corresponding to the configuration grant, and the PUSCH transmission scheduled by the PDCCH is discarded starting from the first symbol of the PUSCH transmission scheduled by the PDCCH that overlaps with the PUSCH corresponding to the configuration grant.

[0196] In the case of PUSCH repetition, if the HPI of the PUSCH corresponding to the configuration grant is different from the HPI of the PUSCH transmission scheduled by the PDCCH, then overlap processing is performed separately for each PUSCH repetition. If the HPI of the PUSCH corresponding to the configuration grant is the same as the HPI of the PUSCH transmission scheduled by the PDCCH, then the PUSCH transmission scheduled by the PDCCH is discarded from the first symbol of the repetition of the PUSCH transmission scheduled by the PDCCH that overlaps with the repetition of the PUSCH corresponding to the configuration grant to the last symbol of the last repetition of the PUSCH transmission scheduled by the PDCCH.

[0197] It is not expected that the UE will be scheduled by PDCCH for another PUSCH, wherein the PUSCH is not earlier than the end of the priority PUSCH and begins before the end of the time domain allocation of the eliminated PUSCH.

[0198] In some implementations, assuming the first configuration grant PUSCH and the second configuration grant PUSCH have the same physical layer priority, the second configuration grant PUSCH may not be allowed to overwrite the first configuration grant PUSCH, where the transmission timing of the first configuration grant PUSCH occurs before the transmission timing of the second configuration grant PUSCH. Alternatively, in some implementations, under certain circumstances, the second configuration grant PUSCH may be allowed to overwrite the first configuration grant PUSCH, where the transmission timing of the first configuration grant PUSCH occurs before the transmission timing of the second configuration grant PUSCH. For example, if the downlink HARQ process ID (HPID) will conflict with the HPI of the first configuration grant PUSCH (and / or at that time), the UE (such as UE 106) may be prohibited from using the second configuration grant PUSCH. As another example, if the HPI of the first configuration grant PUSCH is the same as the HPI of the second configuration grant PUSCH (and / or at that time), the UE (such as UE 106) may use the second configuration grant PUSCH. In such implementations, starting from the first repetition of the first configuration-granted PUSCH that overlaps with the second configuration-granted PUSCH, the remaining repetitions of the first configuration-granted PUSCH can be discarded. As another example, a UE (such as UE106) can perform repetition through repetition overlap processing.

[0199] In some implementations, assuming the first configuration grant PUSCH and the second configuration grant PUSCH have different physical layer priorities, the first configuration grant PUSCH may override the second configuration grant PUSCH in certain circumstances. For example, if the HPI of the second configuration grant PUSCH conflicts with (and / or when) the HPI of the first configuration grant PUSCH with a first priority level, the UE (such as UE 106) may be prohibited from using the second configuration grant PUSCH with a second priority level. As another example, if the HPI of the second configuration grant PUSCH is the same as (and / or when) the HPI of the first configuration grant PUSCH with a first priority level, the UE (such as UE 106) may use the second configuration grant PUSCH with a second priority level. In such implementations, starting from the first repetition of the first configuration grant PUSCH that overlaps with the second configuration grant PUSCH, the remaining repetitions of the first configuration grant PUSCH may be discarded. As another example, the UE (such as UE 106) may perform repetition through repetition overlap processing.

[0200] Furthermore, in some implementations, Section 6.1 of 3GPP TS 38.214 version 16.2 can be modified to declare:

[0201] If the UE reports the ability to prioritize within the UE, and if the second PUSCH corresponding to the configuration authorization and the first PUSCH corresponding to the configuration authorization on the serving cell partially or completely overlap in time,

[0202] If the second PUSCH corresponding to the configuration grant has a priority set to 1 in configuredGrantConfig (i.e., high priority), and the first PUSCH corresponding to the configuration grant has a priority set to 0 in configuredGrantConfig (i.e., low priority) or no priority configuration, then the UE is expected to transmit the second PUSCH and discard the first PUSCH transmission starting from the first symbol of the first PUSCH transmission that overlaps with the second PUSCH.

[0203] In the case of PUSCH repetition, if the HPI of the second PUSCH is different from that of the second PUSCH, then overlap processing is performed separately for each PUSCH repetition. If the HPI of the second PUSCH is the same as that of the second PUSCH transmission, then the first PUSCH transmission is discarded from the first symbol of the first PUSCH repetition that overlaps with the second PUSCH transmission to the last symbol of the last repetition of the first PUSCH transmission.

[0204] It is not expected that the UE will be scheduled by PDCCH for another PUSCH, wherein the PUSCH is not earlier than the end of the priority PUSCH and begins before the end of the time domain allocation of the eliminated PUSCH.

[0205] As discussed above, nested transmissions can be problematic for both the UE and the base station. Therefore, in some implementations, the number of nested levels may be limited to X, where X can be configured by the UE (e.g., UE 106) for example based on UE capabilities and / or via higher-layer signaling (e.g., the UE may provide UE capabilities to the base station, and the base station may determine the value of X, for example, based on UE capabilities and / or network service conditions). In some implementations, up to X-1 levels of nested transmissions may be allowed for a configuration-granted PUSCH, for example, reserving one level for potential transmissions of a dynamic-granted PUSCH. In some implementations, if a radio system in which a high-priority dynamic-granted PUSCH can override a low-priority dynamic-granted PUSCH is permitted (such as a radio system compliant with 3GPP Release 17 and / or when that is), then X-2 levels may be allowed for a configuration-granted PUSCH, for example, reserving two levels for potential transmissions of both the high-priority and / or low-priority dynamic-granted PUSCHs.

[0206] Figure 17A block diagram illustrating an example of a method for selecting Physical Uplink Shared Channels (PUSCHs) with different priorities, according to some implementation schemes, is shown. Among other things, Figure 17 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0207] At 1702, the first PUSCH and the second PUSCH can be configured, for example, by a UE (such as UE 106), which may determine the resources used for transmission on the first PUSCH and the second PUSCH. In some embodiments, the first PUSCH may correspond to a configuration grant. In some embodiments, the second PUSCH may also correspond to a configuration grant. In some embodiments, the second PUSCH may be scheduled by the physical downlink control channel (PDCCH) on the serving cell. Therefore, the UE can configure the first PUSCH based on the configuration grant (e.g., determine the resources used for transmission on the first PUSCH). Similarly, the UE can configure the second PUSCH based on the scheduling provided by the PDCCH on the serving cell and / or another configuration grant (e.g., determine the resources used for transmission on the second PUSCH). In other words, the UE can prepare for the transmission of first data on the first PUSCH resources based on the configuration grant. Similarly, the UE can prepare for the transmission of second data on the second PUSCH resources based on the scheduling provided by the PDCCH on the serving cell and / or another configuration grant.

[0208] In some implementations, a first PUSCH may be associated with a first priority level. Additionally, a second PUSCH may be associated with a second priority level. In such implementations, the first priority level may be associated with a high priority, and the second priority level may be associated with either a low priority or no priority. In some implementations, the first PUSCH may be one of a PUSCH with slot aggregation, a PUSCH with repetition type A, and / or a PUSCH with repetition type B. In some implementations, the second PUSCH may be one of a PUSCH with slot aggregation, a PUSCH with repetition type A, and / or a PUSCH with repetition type B.

[0209] At 1704, the UE can determine the time overlap between at least one transmission timing of the first PUSCH and the second PUSCH. In other words, the UE can determine that at least one transmission timing associated with the first PUSCH and at least one transmission timing associated with the second PUSCH overlap in time (e.g., time overlap).

[0210] At 1706, the UE may discard transmissions (e.g., one or more transmissions) scheduled for the second PUSCH based at least in part on the priority of the first PUSCH. In some embodiments, the UE may determine that the priority of the first PUSCH is higher than the priority of the second PUSCH. In some embodiments, transmissions scheduled for the second PUSCH may be discarded starting from the first symbol of a repetition of the second PUSCH that overlaps temporally with one or more repetitions of the first PUSCH. In some embodiments, for each corresponding repetition of the second PUSCH, transmissions scheduled for the second PUSCH may be discarded starting from the first symbol of the corresponding repetition of the second PUSCH that overlaps temporally with one or more repetitions of the first PUSCH.

[0211] In some implementations, discarding transmissions scheduled for the second PUSCH may include: the UE determining whether the downlink Hybrid Automatic Repeat Request (HARQ) process identifier (HPID) of the first PUSCH is different from the HPDI of the second PUSCH. In such implementations, in response to determining that the HPDI of the first PUSCH is different from the HPDI of the second PUSCH, for each corresponding repetition of the second PUSCH, the UE may discard transmissions scheduled for the second PUSCH starting from the first symbol of the corresponding repetition of the second PUSCH, which overlaps in time with one or more repetitions of the first PUSCH. Alternatively, in such implementations, in response to determining that the HPDI of the first PUSCH is not different from the HPDI of the second PUSCH, the UE may discard transmissions scheduled for the second PUSCH from the first symbol of a repetition of the second PUSCH to the last symbol of the last repetition of the second PUSCH, which overlaps in time with one or more repetitions of the first PUSCH.

[0212] In some implementations, the UE may transmit at least a portion of a transmission scheduled for a second PUSCH, the transmission scheduled for the second PUSCH not overlapping in time with a transmission scheduled for the first PUSCH. In some implementations, the UE may skip at least a portion of a transmission scheduled for the second PUSCH, the transmission scheduled for the second PUSCH not overlapping in time with a transmission scheduled for the first PUSCH.

[0213] Figure 18 Another block diagram illustrates an example of a method for selecting Physical Uplink Shared Channels (PUSCHs) with different priorities, according to some implementation schemes. Among other things, Figure 18The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0214] At 1802, the first PUSCH and the second PUSCH can be configured, for example, by a UE (such as UE 106), which may determine the resources to be used for transmission on the first PUSCH and the second PUSCH. In some embodiments, the first PUSCH may correspond to a configuration grant, and the second PUSCH may be scheduled by the physical downlink control channel (PDCCH) on the serving cell. Therefore, the UE can configure the first PUSCH based on the configuration grant (e.g., determine the resources to be used for transmission on the first PUSCH). Similarly, the UE can configure the second PUSCH based on the scheduling provided by the PDCCH on the serving cell (e.g., determine the resources to be used for transmission on the second PUSCH). In other words, the UE can prepare for the transmission of first data on the first PUSCH resources based on the configuration grant. Similarly, the UE can prepare for the transmission of second data on the second PUSCH resources based on the scheduling provided by the PDCCH on the serving cell.

[0215] In some implementations, a first PUSCH may be associated with a first priority level. Additionally, a second PUSCH may be associated with a second priority level. In such implementations, a first priority level may be associated with a high priority, and a second priority level may be associated with either a low priority or no priority. In some implementations, the first PUSCH may be one of a PUSCH with slot aggregation, a PUSCH with repetition type A, and / or a PUSCH with repetition type B. In some implementations, the second PUSCH may be one of a PUSCH with slot aggregation, a PUSCH with repetition type A, and / or a PUSCH with repetition type B.

[0216] At 1804, the UE can determine the time overlap between at least one transmission timing of the first PUSCH and the second PUSCH. In other words, the UE can determine that at least one transmission timing associated with the first PUSCH and at least one transmission timing associated with the second PUSCH overlap in time (e.g., time overlap).

[0217] At 1806, the UE may discard transmissions (e.g., one or more transmissions) scheduled for the second PUSCH based at least in part on the priority of the first PUSCH. In some embodiments, the UE may determine that the priority of the first PUSCH is higher than the priority of the second PUSCH. In some embodiments, transmissions scheduled for the second PUSCH may be discarded starting from the first symbol of a repetition of the second PUSCH that overlaps temporally with one or more repetitions of the first PUSCH. In some embodiments, for each corresponding repetition of the second PUSCH, transmissions scheduled for the second PUSCH may be discarded starting from the first symbol of the corresponding repetition of the second PUSCH that overlaps temporally with one or more repetitions of the first PUSCH.

[0218] In some implementations, discarding transmissions scheduled for the second PUSCH may include: the UE determining whether the downlink Hybrid Automatic Repeat Request (HARQ) process identifier (HPID) of the first PUSCH is different from the HPDI of the second PUSCH. In such implementations, in response to determining that the HPDI of the first PUSCH is different from the HPDI of the second PUSCH, for each corresponding repetition of the second PUSCH, the UE may discard transmissions scheduled for the second PUSCH starting from the first symbol of the corresponding repetition of the second PUSCH, which overlaps in time with one or more repetitions of the first PUSCH. Alternatively, in such implementations, in response to determining that the HPDI of the first PUSCH is not different from the HPDI of the second PUSCH, the UE may discard transmissions scheduled for the second PUSCH from the first symbol of a repetition of the second PUSCH to the last symbol of the last repetition of the second PUSCH, which overlaps in time with one or more repetitions of the first PUSCH.

[0219] In some implementations, the UE may transmit at least a portion of a transmission scheduled for a second PUSCH, the transmission scheduled for the second PUSCH not overlapping in time with a transmission scheduled for the first PUSCH. In some implementations, the UE may skip at least a portion of a transmission scheduled for the second PUSCH, the transmission scheduled for the second PUSCH not overlapping in time with a transmission scheduled for the first PUSCH.

[0220] Figure 19 Another block diagram illustrating an example of a method for selecting Physical Uplink Shared Channels (PUSCHs) with different priorities, according to some implementation schemes, is shown. Among other things, Figure 19The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0221] At 1902, the first PUSCH and the second PUSCH can be configured, for example, by a UE (such as UE 106). In some embodiments, the first PUSCH may correspond to a first configuration grant and the second PUSCH may correspond to a second configuration grant. Therefore, the UE can configure the first PUSCH based on the first configuration grant (e.g., determine the resources for transmission on the first PUSCH). Similarly, the UE can configure the second PUSCH based on the second configuration grant (e.g., determine the resources for transmission on the second PUSCH). In other words, the UE can prepare for the transmission of first data on the first PUSCH resources based on the first configuration grant. Similarly, the UE can prepare for the transmission of second data on the second PUSCH resources based on the second configuration grant.

[0222] In some implementations, a first PUSCH may be associated with a first priority level. Additionally, a second PUSCH may be associated with a second priority level. In such implementations, the first priority level may be associated with a high priority, and the second priority level may be associated with either a low priority or no priority. In some implementations, the first PUSCH may be one of a PUSCH with slot aggregation, a PUSCH with repetition type A, and / or a PUSCH with repetition type B. In some implementations, the second PUSCH may be one of a PUSCH with slot aggregation, a PUSCH with repetition type A, and / or a PUSCH with repetition type B.

[0223] At 1904, the UE can determine the time overlap between at least one transmission timing of the first PUSCH and the second PUSCH. In other words, the UE can determine that at least one transmission timing associated with the first PUSCH and at least one transmission timing associated with the second PUSCH overlap in time (e.g., time overlap).

[0224] At 1906, the UE may discard transmissions (e.g., one or more transmissions) scheduled for the second PUSCH based at least in part on the priority of the first PUSCH. In some embodiments, the UE may determine that the priority of the first PUSCH is higher than the priority of the second PUSCH. In some embodiments, transmissions scheduled for the second PUSCH may be discarded starting from the first symbol of a repetition of the second PUSCH that overlaps in time with one or more repetitions of the first PUSCH. In some embodiments, for each corresponding repetition of the second PUSCH, transmissions scheduled for the second PUSCH may be discarded starting from the first symbol of the corresponding repetition of the second PUSCH that overlaps in time with one or more repetitions of the first PUSCH.

[0225] In some implementations, discarding transmissions scheduled for the second PUSCH may include: the UE determining whether the downlink Hybrid Automatic Repeat Request (HARQ) process identifier (HPID) of the first PUSCH is different from the HPDI of the second PUSCH. In such implementations, in response to determining that the HPDI of the first PUSCH is different from the HPDI of the second PUSCH, for each corresponding repetition of the second PUSCH, the UE may discard transmissions scheduled for the second PUSCH starting from the first symbol of the corresponding repetition of the second PUSCH, which overlaps in time with one or more repetitions of the first PUSCH. Alternatively, in such implementations, in response to determining that the HPDI of the first PUSCH is not different from the HPDI of the second PUSCH, the UE may discard transmissions scheduled for the second PUSCH from the first symbol of a repetition of the second PUSCH to the last symbol of the last repetition of the second PUSCH, which overlaps in time with one or more repetitions of the first PUSCH.

[0226] In some implementations, the UE may transmit at least a portion of a transmission scheduled for a second PUSCH, the transmission scheduled for the second PUSCH not overlapping in time with a transmission scheduled for the first PUSCH. In some implementations, the UE may skip at least a portion of a transmission scheduled for the second PUSCH, the transmission scheduled for the second PUSCH not overlapping in time with a transmission scheduled for the first PUSCH.

[0227] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0228] Embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0229] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein, if executed by a computer system, the program instructions cause the computer system to perform a method, such as any method embodiment of the method embodiments described herein, or any combination of method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

[0230] In some implementations, the device (e.g., UE 106) may be configured to include a processor (or a set of processors) and a memory medium, wherein the memory medium stores program instructions, and the processor is configured to read from and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method implementations described herein (or any combination of method implementations described herein, or any subset of any method implementations described herein, or any combination of such subsets). The device may be implemented in any of a variety of forms.

[0231] By interpreting each message / signal X received by the user equipment (UE) in the downlink as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station, any method described herein for operating the UE can serve as the basis for a corresponding method for operating the base station.

[0232] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A method for selecting a Physical Uplink Shared Channel (PUSCH), comprising: Configure a first PUSCH and a second PUSCH, wherein the first PUSCH corresponds to a first configuration authorization, and wherein the second PUSCH is scheduled by the physical downlink control channel (PDCCH) on the serving cell; Determine that at least one transmission repeat associated with the first PUSCH and at least one transmission repeat associated with the second PUSCH overlap in time; as well as Discard one or more duplicate transmissions, wherein the discarding includes: Determine whether the downlink Hybrid Automatic Repeat Request (HARQ) process identifier HPI of the first PUSCH is different from that of the second PUSCH; In response to determining that the HPI of the first PUSCH is different from the HPI of the second PUSCH, when the priority of the first PUSCH is higher than the priority of the second PUSCH, for each corresponding repetition of the second PUSCH, the transmission repetition scheduled for the second PUSCH is discarded starting from the first symbol of the corresponding repetition of the second PUSCH, the corresponding repetition of the second PUSCH overlapping with one or more repetitions of the first PUSCH in time. as well as In response to determining that the HPI of the first PUSCH is no different from the HPI of the second PUSCH, transmission duplicates scheduled for the first PUSCH are discarded starting from the first symbol of the duplicate of the first PUSCH that overlaps with one or more duplicates of the second PUSCH in time.

2. The method according to claim 1, The first PUSCH is associated with a first priority level, the second PUSCH is associated with a second priority level, the first priority level is associated with a high priority, and the second priority level is associated with either a low priority or no priority.

3. The method according to claim 1, The first PUSCH is one of a PUSCH with time slot aggregation, a PUSCH with repetition type A, or a PUSCH with repetition type B.

4. The method according to claim 1, The second PUSCH is one of a PUSCH with time slot aggregation, a PUSCH with repetition type A, or a PUSCH with repetition type B.

5. The method according to claim 1, further comprising: The transmission is at least a portion of the transmission scheduled by the second PUSCH, and the transmission scheduled by the second PUSCH does not overlap in time with the transmission scheduled by the first PUSCH.

6. The method according to claim 1, further comprising: Skip at least a portion of the transmissions scheduled for the second PUSCH, where the transmissions scheduled for the second PUSCH do not overlap in time with the transmissions scheduled for the first PUSCH.

7. An apparatus comprising: Memory; and A processing element that communicates with the memory, wherein the processing element is configured to: Configure a first physical uplink shared channel (PUSCH) and a second PUSCH, wherein the first PUSCH corresponds to a first configuration grant, and wherein the second PUSCH is scheduled by the physical downlink control channel (PDCCH) on the serving cell. Determine that at least one transmission repeat associated with the first PUSCH and at least one transmission repeat associated with the second PUSCH overlap in time; and Discard one or more transmission duplicates, wherein, in order to discard the one or more transmission duplicates, the processing element is further configured to: Determine whether the downlink Hybrid Automatic Repeat Request (HARQ) process identifier HPI of the first PUSCH is different from that of the second PUSCH; In response to determining that the HPI of the first PUSCH is different from the HPI of the second PUSCH, when the priority of the first PUSCH is higher than the priority of the second PUSCH, for each corresponding repetition of the second PUSCH, the transmission repetition scheduled for the second PUSCH is discarded starting from the first symbol of the corresponding repetition of the second PUSCH, the corresponding repetition of the second PUSCH overlapping with one or more repetitions of the first PUSCH in time. as well as In response to determining that the HPI of the first PUSCH is no different from the HPI of the second PUSCH, transmission duplicates scheduled for the first PUSCH are discarded starting from the first symbol of the duplicate of the first PUSCH that overlaps with one or more duplicates of the second PUSCH in time.

8. The apparatus according to claim 7, The first PUSCH is associated with a first priority level, the second PUSCH is associated with a second priority level, the first priority level is associated with a high priority, and the second priority level is associated with either a low priority or no priority.

9. The apparatus according to claim 7, The first PUSCH is one of a PUSCH with time slot aggregation, a PUSCH with repetition type A, or a PUSCH with repetition type B.

10. The apparatus according to claim 7, The second PUSCH is one of a PUSCH with time slot aggregation, a PUSCH with repetition type A, or a PUSCH with repetition type B.

11. A user equipment (UE) comprising: At least one antenna; At least one radio component, wherein the at least one radio component is configured to perform cellular communication using at least one radio access technology (RAT); and One or more processors, said one or more processors being coupled to said at least one radio component, wherein said one or more processors and said at least one radio component are configured to perform voice and / or data communication; The one or more processors wherein the UE is configured to: It is determined that at least one transmission duplicate associated with the first configuration-granted physical uplink shared channel (PUSCH) and at least one transmission duplicate associated with the second PUSCH overlap in time, the second PUSCH being scheduled by the physical downlink control channel (PDCCH) on the serving cell. as well as Discard one or more transmission duplicates, wherein, in order to discard the one or more transmission duplicates, the one or more processors are further configured to cause the UE to: Determine whether the downlink Hybrid Automatic Repeat Request (HARQ) process identifier HPI of the first configuration authorized PUSCH is different from the HPI of the second PUSCH; In response to determining that the HPI of the first configuration-granted PUSCH is different from the HPI of the second PUSCH, when the priority of the first configuration-granted PUSCH is higher than the priority of the second PUSCH, for each corresponding repetition of the second PUSCH, the transmission repetition scheduled for the second PUSCH is discarded starting from the first symbol of the corresponding repetition of the second PUSCH, the corresponding repetition of the second PUSCH overlapping with one or more repetitions of the first configuration-granted PUSCH in time. as well as In response to determining that the HPI of the first configuration-granted PUSCH is no different from the HPI of the second PUSCH, transmission duplicates scheduled for the first configuration-granted PUSCH are discarded starting from the first symbol of a duplicate of the first configuration-granted PUSCH that overlaps with one or more duplicates of the second PUSCH in time.

12. The UE according to claim 11, The first configuration authorization PUSCH is associated with a first priority level, the second PUSCH is associated with a second priority level, the first priority level is associated with high priority, and the second priority level is associated with either low priority or no priority.

13. The UE according to claim 11, The first configuration authorization PUSCH uses repeating type B.

14. The UE according to claim 11, The second PUSCH uses slot aggregation or repetition type A.

15. The UE according to claim 11, The UE mentioned above supports inter-column transmission.

16. The UE according to claim 11, The one or more processors thereon are further configured to cause the UE to: On a per-repeat basis, each actual repetition in the first configuration authorization PUSCH is examined with each actual repetition in the second PUSCH to determine whether the repetitions overlap in time.

17. The UE according to claim 11, The first configuration-authorized PUSCH is one of a PUSCH with slot aggregation, a PUSCH with repetition type A, or a PUSCH with repetition type B.

18. The UE according to claim 11, The second PUSCH is one of a PUSCH with time slot aggregation, a PUSCH with repetition type A, or a PUSCH with repetition type B.

19. The UE according to claim 11, The one or more processors thereon are further configured to cause the UE to: The transmission is at least a first portion of the transmission scheduled for the second PUSCH, and the transmission scheduled for the second PUSCH does not overlap in time with the transmission scheduled for the first configuration-authorized PUSCH; and Skip at least a second portion of the transmission scheduled for the second PUSCH, the transmission scheduled for the second PUSCH does not overlap in time with the transmission scheduled for the first configuration-authorized PUSCH.

20. The UE according to claim 11, The one or more processors thereon are further configured to cause the UE to: The transmission is at least a portion of the transmission scheduled by the second PUSCH, and the transmission scheduled by the second PUSCH does not overlap in time with the transmission scheduled by the first configuration-authorized PUSCH.

Images