User apparatus, and base station

Abstract

To provide a method and an apparatus capable of selectively canceling specific uplink transmissions in a case of a collision with another uplink transmission.SOLUTION: A base station is configured to transmit an instruction representing the priority level via group common downlink control information, transmit a first radio resource control signaling constituting a priority first setting, or transmit a second radio resource control signaling constituting priority second setting, compare the priority level of the UE's first uplink transmission with the instructed priority level, and prior to transmission of the group common downlink control information indicating allocation of resources for scheduling of a second uplink transmission that overlaps with resources allocated to the first uplink transmission, allow the UE to make the first uplink transmission, and based on the results of the comparison, execute or cancel the reception of the first uplink transmission.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] FIELD OF THE DISCLOSURE The present disclosure relates to transmitting and receiving signals in a communication system. In particular, the present disclosure relates to methods and apparatus for such transmission and reception. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) is working on technical specifications for next-generation cellular technology, also known as fifth generation (5G), including "New Radio" (NR) radio access technology (RAT) operating in the frequency range up to 100 GHz. NR is the successor to technologies represented by Long Term Evolution (LTE) and LTE Advanced (LTE-A).

[0003] For systems such as LTE, LTE-A, and NR, further modifications and options may facilitate efficient operation of the communication system and certain devices associated with the system. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] TR 38.913 [Non-patent document 2] 3GPP TS 38.331 V15.6.0 (2019-06), Radio Resource Control (RRC) protocol specification, section 6.3.2 [Non-patent document 3] 3GPP TS 38.331 V15.6.0 Summary of the Invention

[0005] One non-limiting exemplary embodiment facilitates enabling selective cancellation of a particular uplink transmission in the event of a collision with another uplink transmission.

[0006] A main aspect of the present invention is a base station comprising: a transceiver that transmits an instruction indirectly indicating a priority level to be applied to a plurality of user equipments (UEs) by using group common downlink control information common to the plurality of UEs, the transceiver transmitting first radio resource control signaling constituting a first setting related to priority or second radio resource control signaling constituting a second setting related to priority; and a circuit that compares a priority level of a first uplink transmission in the UE with the indicated priority level to be applied, the comparison differing depending on the first or second setting related to priority, and allows the UE to perform the first uplink transmission before transmitting the group common downlink control information indicating allocation of resources for scheduling a second uplink transmission that overlaps with resources allocated to the first uplink transmission; and the transceiver that performs or cancels reception of the first uplink transmission based on a result of the comparison.

[0007] In one embodiment, the technology disclosed herein features a user equipment (UE) including: a transceiver that, during operation, receives an indication indicating a priority level to apply; and circuitry that, during operation, compares a priority level of a first uplink transmission with the indicated priority level to apply, the first uplink transmission being granted to the UE prior to scheduling of a second uplink transmission assigned to resources that overlap with resources assigned to the first uplink transmission; and wherein the transceiver, during operation, performs the first uplink transmission based on a result of the comparison.

[0008] It should be noted that the general or specific embodiments may be realized as a system, a method, an integrated circuit, a computer program, a storage medium, or any selective combination thereof.

[0009] Further benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings. These benefits and / or advantages may be obtained individually through various embodiments and features of the specification and drawings, which need not all be provided to obtain one or more of such benefits and / or advantages. [Brief explanation of the drawings]

[0010] Exemplary embodiments will now be described in more detail with reference to the accompanying drawings.

[0011] [Figure 1] Schematic diagram illustrating an example architecture of a 3GPP NR system [Figure 2] Block diagram illustrating an exemplary user and control plane architecture for LTE eNB, gNB, and UE [Figure 3] Schematic diagram showing the division of functions between NG-RAN and 5GC [Figure 4] Sequence diagram of RRC connection setup / reconfiguration procedure [Figure 5] Schematic showing the usage scenarios for enhanced mobile broadband, massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC) [Figure 6] Block diagram illustrating an exemplary 5G system architecture [Figure 7] Schematic diagram showing the cancellation mechanism for uplink transmissions on overlapping resources [Figure 8] Block diagram showing user equipment and base station [Figure 9] Block diagram of an uplink priority determination circuit of a user equipment [Figure 10] Block diagram showing an uplink priority determination circuit of a base station [Figure 11] Flowchart showing uplink transmission and reception method [Figure 12] Schematic diagram showing the execution and cancellation of uplink transmissions on overlapping resources [Figure 13] Flowchart showing an uplink transmission method [Figure 14] Flowchart showing an uplink transmission method [Figure 15] Flowchart showing an uplink transmission method DETAILED DESCRIPTION OF THE INVENTION

[0012] 5G NR System Architecture and Protocol Stack

[0013] 3GPP is working on the next release of fifth-generation cellular technology, simply known as 5G, which involves the development of new radio access technologies (NR) that will operate in frequencies up to 100 GHz. The first version of the 5G standard was finalized at the end of 2017, allowing for the trial and commercial deployment of smartphones compliant with the 5G NR standard.

[0014] In particular, the overall system architecture assumes a Next Generation-Radio Access Network (NG-RAN) with gNBs providing NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol termination towards UEs. The gNBs are interconnected with each other via an Xn interface. The gNBs are also connected to the Next Generation Core (NGC) via a Next Generation (NG) interface, and more specifically to the Access and Mobility Management Function (AMF) (e.g., a specific core entity running AMF) via an NG-C interface, and to the User Plane Function (UPF) (e.g., a specific core entity running UPF) via an NG-U interface. The NG-RAN architecture is shown in Figure 1.

[0015] Various deployment scenarios can be supported. For example, a decentralized deployment scenario is presented herein, in which base stations supporting 5G NR can be deployed. Figure 2 illustrates an exemplary decentralized deployment scenario, but further illustrates an LTE eNB and user equipment (UE) connected to both the gNB and the LTE eNB. The new eNB for NR 5G may illustratively be referred to as a gNB. The eLTE eNB is an evolution of the eNB that supports connectivity to the Evolved Packet Core (EPC) and Next Generation Core (NGC).

[0016] The NR user plane protocol stack has the Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Medium Access Control (MAC) sublayers, which terminate at the gNB on the network side. Furthermore, a new access stratum (AS) sublayer (Service Data Adaptation Protocol (SDAP)) is introduced above PDCP. A control plane protocol stack is also defined for NR.

[0017] 5G NR function split between NG-RAN and 5GC

[0018] Figure 3 shows the functional division between NG-RAN and 5GC. The NG-RAN logical node is the gNB or ng-eNB. The 5GC has the above logical nodes AMF, UPF, and SMF.

[0019] In particular, the gNB and ng-eNB host the following main functions: - Functions for Radio Resource Management, such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, dynamic allocation (scheduling) of resources to UEs in both uplink and downlink; - IP header compression, encryption, and integrity protection of data, - AMF selection at UE attachment when routing to the AMF cannot be determined from information provided by the UE; - Routing of user plane data to the UPF, - Routing of control plane information to the AMF, - connection setup and release, - scheduling and sending paging messages; - Scheduling and transmission of system broadcast information (derived from AMF or OAM); - Measurement and measurement reporting configuration for mobility and scheduling, Transport-level packet marking in the uplink - Session Management, - Network Slicing support, - QoS flow management and mapping to data radio bearers; - support for UEs in RRC_INACTIVE state; - NAS message distribution function, - Wireless access network sharing, - Dual Connectivity, - Tight interworking between NR and E-UTRA.

[0020] The Access and Mobility Management Function (AMF) hosts the following main functions: - Non-Access Stratum (NAS) signalling termination, - NAS signaling security, - Access Stratum (AS) security control, - Inter-Core Network (CN) node signaling for mobility between 3GPP access networks; - Idle mode UE Reachability (including control and execution of paging retransmissions); - Registration Area Management, - Support for intra-system and inter-system mobility, - Access Authentication, - Access Authorization, including checking roaming rights; - Mobility management controls (subscriptions and policies), - Network Slicing support, - Selection of Session Management Function (SMF).

[0021] Furthermore, the User Plane Function (UPF) hosts the following main functions: - Anchor points for intra-RAT / inter-RAT mobility (if applicable), - External PDU Session Points for interconnection to Data Networks, - Packet routing and forwarding, - The user plane part of packet inspection and policy rule enforcement, - Traffic usage reports, - an uplink classifier that supports routing of traffic flows to the data network; - a branch point that supports multi-homed PDU sessions, - QoS processing for the user plane, e.g., packet filtering, gating, UL / DL rate enforcement, - Uplink traffic validation (SDF to QoS flow mapping), - Downlink packet buffering and downlink data notification triggers.

[0022] Finally, the Session Management Function (SMF) hosts the following main functions: - Session management, - UE IP address allocation and management; - UP function selection and control, - Configuring traffic steering in the User Plane Function (UPF) to route traffic to the appropriate destination; - Policy enforcement and QoS control parts, - Downlink Data Notification.

[0023] RRC connection setup and reconfiguration procedures

[0024] Figure 4 shows some of the interactions between the UE, gNB, and AMF (5GC entity) regarding RRC, which is the higher layer signaling (protocol) used for UE and gNB configuration. Specifically, the AMF prepares UE context data (e.g., including PDU session context, security key, UE radio capability, and UE security capabilities) and sends it to the gNB in ​​an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security with the UE. This is performed by the gNB sending a SecurityModeCommand message to the UE, and the UE responding with a SecurityModeComplete message to the gNB. The gNB then performs reconfiguration to set up Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB) using RRCReconfiguration and RRCReconfigurationComplete. If only a connection is signaled, SRB2 and DRB are not set up, so step 8 is skipped. Finally, the gNB notifies the AMF with an INITIAL CONTEXT SETUP RESPONSE that the setup procedure is complete.

[0025] Thus, the present disclosure provides a fifth generation core (5GC) entity (e.g., AMF, SMF, etc.) having a control circuit that, during operation, establishes a Next Generation (NG) connection with a gNodeB, and a transmitter that, during operation, sends an initial context setup message to the gNodeB over the NG connection to trigger a signaling radio bearer setup between the gNodeB and a user equipment (UE). In particular, the gNodeB sends Radio Resource Control (RRC) signaling including a resource allocation configuration information element to the UE over the signaling radio bearer. The UE then performs uplink transmission or downlink reception based on the resource allocation configuration.

[0026] IMT usage scenarios from 2020 onwards

[0027] Figure 5 shows some of the 5G NR use cases. The 3GPP NR (3rd Generation Partnership Project New Radio) envisions three use cases that are expected to support a wide variety of services and applications with IMT-2020. The enhanced mobile broadband (eMBB) phase 1 specification has been completed. In addition to further extending eMBB support, current and future work will involve standardizing ultra-reliable and low-latency communications (URLLC) and massive machine-type communications. Figure 5 shows some examples of anticipated usage scenarios for IMT beyond 2020.

[0028] The URLLC use case has stringent requirements for capabilities such as throughput, latency, and availability, and is envisioned as one of the enablers for future vertical applications such as wireless control of industrial manufacturing or production processes, remote medical surgery, logistics automation in smart grids, and transportation safety. The ultra-reliability of URLLC is supported by identifying technologies that meet the requirements set by [Non-Patent Document 1]. For NR URLCC in Release 15, key requirements include a target user plane delay of 0.5 ms for the uplink (UL) and 0.5 ms for the downlink (DL). A typical URLLC requirement for a single transmission of a packet is a BLER (block error rate) of 1E-5 for a 32-byte packet size with a 1 ms user plane delay.

[0029] From the RAN1 perspective, reliability can be improved in many possible ways. The current scope of reliability improvements is to define a separate CQI table for URLLC, a more compact Downlink Control Information (DCI) format, PDCCH repetition, etc. However, such scope can be broadened to achieve ultra-reliability as NR becomes more stable and developed for the critical requirements of NR URLCC. Thus, NR URLLC in Release 15 should be able to transmit 32-byte data packets within 1 ms user-plane delay with a success probability corresponding to a BLER of 1E-5. Specific use cases for NR URLCC in Release 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0030] Furthermore, targeted technology enhancements for NR URLCC aim to improve latency and reliability. Technology enhancements for latency improvement include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition of data channels, and downlink preemption. Preemption means interrupting a transmission for which resources have already been allocated and using the already allocated resources for another transmission that is requested later but requires lower latency / higher priority. Thus, an already granted transmission is preempted by a later transmission. Preemption is applicable regardless of the specific service type. For example, a transmission of service type A (URLCC) can be preempted by a transmission of service type B (e.g., eMBB). Technology enhancements for reliability improvement include dedicated CQI / MCS tables for a target BLER of 1E-5.

[0031] mMTC use cases are typically characterized by a large number of connected devices transmitting relatively small amounts of latency-insensitive data. The devices are required to be low cost and have very long battery life. From an NR perspective, utilizing very narrow bandwidth portions is one possible solution that has power savings from the UE perspective and allows for long battery life.

[0032] As mentioned above, it is expected that the reliability range in NR will expand. One key requirement for all cases, especially for URLLC and mMTC, is high or ultra-high reliability. Several mechanisms can be considered to improve reliability from a radio perspective and a network perspective. In general, there are a few key potential areas that can help improve reliability. Among these areas are compact control channel information, repetition of data / control channels, and diversity in frequency, time, and / or spatial domains. These areas are applicable to reliability in general, regardless of the specific communication scenario.

[0033] For NR URLLC, further use cases with more stringent requirements have been identified, e.g., factory automation, transportation, power supply, etc. The more stringent requirements are higher reliability (up to the 10-6 level), higher availability, packet sizes up to 256 bytes, time synchronization down to the order of a few μs (where the value can be 1 μs or a few μs depending on the frequency range), and low latency on the order of 0.5-1 ms depending on the use case (in particular, a target user plane latency of 0.5 ms).

[0034] Additionally, for NR URLCC, several technology enhancements from a RAN1 perspective have been identified. Among these are PDCCH (Physical Downlink Control Channel) enhancements related to compact DCI, PDCCH repetition, and increased PDCCH monitoring. Furthermore, UCI (Uplink Control Information) enhancements are related to enhanced Hybrid Automatic Repeat Request (HARQ) and CSI feedback enhancements. Also identified are PUSCH enhancements related to mini-slot level hopping and retransmission / repetition enhancements. The term "mini-slot" refers to a transmission time interval (TTI) containing fewer symbols than a slot (a slot with 14 symbols).

[0035] QoS Control

[0036] The 5G QoS model is based on QoS flows and supports both QoS flows that require a guaranteed flow bit rate (GBR QoS flows) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows). Therefore, at the NAS level, QoS flows are the finest granularity of QoS differentiation in a PDU session. QoS flows are identified within a PDU session by a QoS Flow ID (QFI) carried in the encapsulation header over the NG-U interface.

[0037] For each UE, the 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) with the PDU session and may then configure additional DRB(s) for the QoS flow(s) of that PDU session (when to do so is up to the NG-RAN), e.g., as described above with reference to FIG. 4. The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0038] Figure 6 shows the 5G NR non-roaming reference architecture. Application Functions (AFs) interact with the 3GP Core Network to provide services, such as traffic routing, access to the Network Exposure Function (NEF), or application influence on policy framework interaction for policy control (see Policy Control Function (PCF)). Based on operator deployment, application functions deemed trusted by the operator may be allowed to interact directly with the associated Network Functions. Application Functions not authorized by the operator to directly access the Network Functions interact with the associated Network Functions using the external exposure framework via the NEF.

[0039] Figure 6 shows further functional units of the 5G architecture, namely the Network Slice Selection Function (NSSF), the Network Repository Function (NRF), the Unified Data Management (UDM), the Authentication Server Function (AUSF), the Access and Mobility Management Function (AMF), the Session Management Function (SMF), and the Data Network (DN), e.g. operator services, internet access or third party services.

[0040] In LTE and NR, a terminal is called user equipment (UE). This may be a mobile device or communication device, such as a mobile phone, smartphone, tablet computer, or universal serial bus (USB) stick with user equipment functionality. However, the term mobile device is not limited thereto, and in general, a relay may have the functionality of such a mobile device, and a mobile device may also function as a relay.

[0041] A base station is a network node that forms part of a network for providing services to, for example, terminals. A base station is a network node or scheduling node that provides radio access to terminals. Generally, communication between terminals and base stations is standardized. In LTE and NR, the radio interface protocol stack includes a physical layer, a medium access layer (MAC), and higher layers. The control plane is provided with a Radio Resource Control protocol, which is an upper layer protocol. RRC enables base stations to control the configuration of terminals, and terminals to communicate with base stations to perform control tasks (e.g., establishing and modifying connections and bearers), measurements, and other functions.

[0042] The services provided by one layer to transfer data to a higher layer are usually called channels. For example, LTE and NR distinguish between logical channels, which are provided by the MAC layer to higher layers, transport channels, which are provided by the physical layer to the MAC layer, and physical channels, which define the mapping to physical resources.

[0043] Logical channels are the different types of data transfer services provided by the MAC. Each logical channel type is defined by the type of information it transfers. Logical channels are divided into two groups: Control Channels and Traffic Channels. Control Channels are used only for the transfer of control plane information. Traffic Channels are used only for the transfer of user plane information.

[0044] Logical channels are then mapped to transport channels by the MAC layer, for example, logical traffic channels and some logical control channels may be mapped to a transport channel called Downlink Shared Channel (DL-SCH) in the downlink and to a transport channel called Uplink Shared Channel (UL-SCH) in the uplink.

[0045] Inter-UE prioritization

[0046] Usage scenarios such as NR URLLC motivate consideration of UE-to-UE uplink (UL) prioritization and multiplexing. In particular, the need for prioritization may arise when a UL transmission is already scheduled for user equipment UE1 or there is an ongoing UL transmission performed by UE1, and a higher priority UL transmission is subsequently scheduled for another user equipment UE2, transmitting on resources that overlap at least some of the resources used by the UL transmission for UE1.

[0047] For this purpose, the following cancellation mechanism can be applied:

[0048] Step 1: A group of UEs is configured to monitor a PDCCH carrying a group-common (GC) DCI containing information related to the cancellation of an ongoing transmission.

[0049] Step 2: High priority UEs (possibly with URLLC traffic) are scheduled, which may partially or completely overlap with already scheduled or ongoing UL transmissions from other UEs.

[0050] Step 3: The gNB transmits a PDCCH with GC DCI to cancel ongoing UL transmissions. Only UEs configured to monitor GC DCI respond and cancel all ongoing transmissions if they partially or completely overlap the time-frequency region indicated by the GC DCI. The transmissions are then canceled and will not be resumed.

[0051] In the above cancellation mechanism, steps 2 and 3 can be swapped.

[0052] Additionally, as noted above, a group of UEs is configured to monitor a PDCCH carrying a group-common DCI. This group may include UEs performing uplink traffic that is generally given lower priority than other UL traffic. For example, eMBB traffic may be given lower priority than URLLC traffic or traffic performed by public safety UEs, such as police UEs.

[0053] An example of the above-mentioned cancellation mechanism is shown in Figure 7. In this example, transmissions for UE1, UE2, and UE3 are already scheduled when a new UE, whose resources partially overlap with UE2 and UE3, is scheduled, possibly with high priority. The overlap area is signaled to UE1, UE2, and UE3 by a group-common DCI. As can be seen, only UE2 and UE3's transmissions overlap with the newly scheduled transmissions, not with UE1's transmission. When the above-mentioned cancellation mechanism is applied, the entire transmissions of UE2 and UE3 are canceled starting from the time when the new transmissions are scheduled to start. Before this time, the canceled transmissions may still be performed before the overlapping part.

[0054] According to the above cancellation mechanism, a group of UEs configured to monitor the group-common DCI for cancellation will always cancel their scheduled or ongoing UL transmissions on resources that overlap with a newly scheduled high priority transmission upon detecting the group-common DCI, regardless of whether their current transmissions are low priority (perhaps eMBB) or high priority (perhaps URLCC).

[0055] However, there may be cases where UEs supporting both URLLC and eMBB traffic, or more generally, different types of traffic associated with different priorities, are configured to monitor the group-common DCI for cancellation. For example, in Figure 7, the transmission scheduled for UE2 may be an eMBB UL transmission, and the transmission scheduled for UE3 may be a URLLC transmission. In this case, UE2's transmission is allowed to be canceled because it has a lower priority (eMBB). However, if the above mechanism is applied, UE3 will also cancel its transmission, even though its transmission is URLLC (higher priority).

[0056] The present disclosure proposes techniques that enable selective cancellation of certain uplink transmissions (e.g., low priority transmissions) of a UE upon detection of a signal, such as a group-wide DCI for cancellation, where aspects and embodiments of the disclosed embodiments include both the inter-UE case, where a newly scheduled UL transmission has overlapping resources with another UE's transmission, and the intra-UE case, where a newly scheduled transmission and a previously scheduled overlapping transmission are scheduled to the same UE.

[0057] As shown in FIG. 8, a UE 860 having a transceiver 870 and circuitry 880 is provided.

[0058] In this disclosure, a "transceiver" (transmitter-receiver) refers to hardware and software capable of performing transmission and reception, for example, in a wireless communication network. The transceiver hardware components may include one or more antennas and / or oscillators, as well as control circuitry adapted to control the transceiver hardware based on corresponding software.

[0059] Furthermore, the term "circuitry" refers to processing circuitry, such as, for example, one or more processors or central processing units (CPUs), and includes hardware components, such as, for example, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), software implementations running on any hardware, or any combination of hardware and software.

[0060] During operation, the transceiver 870 of the UE 860, or "UE transceiver" for short, receives an indication indicating the priority level to apply.

[0061] The priority level indication may be a numeric or logical value that is mapped to or associated with the priority of the uplink transmission. According to various described embodiments, there may be an explicit or direct mapping between the indication and the priority level among a scale, ranking, or hierarchy of priority levels. The indication may also indicate a range of priority levels from a given or defined hierarchy of priority levels. Alternatively, there may be an implicit or indirect mapping where the indication is mapped to a transmission type, which in turn is associated with a transmission priority or priority level.

[0062] Furthermore, the "priority level to be applied" or "prevailing priority level" is the priority level at which transmission should be performed even if resources overlap.

[0063] It should be noted that the indication of the priority level to apply does not necessarily have to be associated with a specific transmission, but may refer generally to the priority level of any transmission that should be performed in the case of resources that overlap with resources of other transmissions.

[0064] In operation, the UE circuitry 880 ("UE circuitry") compares the priority level of a first uplink transmission with the indicated priority level to be applied. The first uplink transmission is an uplink transmission granted to the UE by a scheduling node, such as a base station, before the scheduling node schedules the second uplink transmission. The second uplink transmission is an uplink transmission assigned to resources that at least partially overlap with the resources assigned to the first uplink transmission.

[0065] In general, the second uplink transmission may be a transmission granted to the UE 860 that was also granted the first transmission (this corresponds to the intra-UE case), or a transmission granted to another UE (this corresponds to the inter-UE case).

[0066] The resources to which the first and second uplink transmissions are allocated may include grid time and frequency resources, such as the resource grid of an LTE, LTE-A, 3GPP NR system, or a similar communication system where time and / or frequency multiplexing is applied. Other possible resources include spatial resources, such as when multiple input multiple output (MIMO) is applied, or orthogonal codes.

[0067] The overlapping resources allocated to the first and second transmissions include fully overlapping resources (all such resource elements allocated to different transmissions are identical, and the resources of one transmission are entirely composed of the resources allocated to the other transmission) or partially overlapping resources. In general, the overlapping resources allocated to the first and second transmissions overlap if they share at least one common resource element.

[0068] For example, information regarding associated priority may be provided at the physical layer for each uplink transmission of a UE, including the first uplink transmission of the UE 860, according to the present disclosure. The information regarding priority may be utilized for selective cancellation of only low priority UL transmissions of either the same UE (intra-UE) or different UEs (inter-UE, already scheduled or in progress), and may be received via control information common to a group of UEs when overlapping with a high priority channel / signal UE (later scheduled).

[0069] For example, comparing the priority level of the first transmission with the to-be-applied priority level includes determining whether the priority level of the first uplink transmission is the same as the indicated to-be-applied priority level, or determining whether the priority level of the first uplink transmission is equal to or greater than the to-be-applied priority level. How the comparison is performed may depend on how the to-be-applied priority is indicated and, accordingly, what type of information regarding the priority of the first uplink transmission is provided.

[0070] During operation, the UE transceiver 870 performs a first uplink transmission based on the result of the comparison.

[0071] For example, if the comparison determines that the priority level of the first uplink transmission is equal to or greater than the designated priority level, the first uplink transmission is executed. Furthermore, if the first transmission begins in an OFDM symbol before the start of the overlap (e.g., before the first OFDM symbol when the overlap occurs), it continues even after the start of the overlap. For example, common resources allocated to both the first and second uplink transmissions may be shared by or divided between the first and second uplink transmissions. Furthermore, the first transmission may use resources that are not common to the first and second transmissions but are located on an OFDM symbol affected by the overlap or on an OFDM symbol after the overlap, which would not be used if the above-described cancellation mechanism (steps 1-3) is used.

[0072] On the other hand, if the comparison determines that the priority level of the first uplink transmission is lower than the indicated priority level to be applied, the first uplink transmission is not performed on resources common to at least the first and second uplink transmissions. Thus, for example, the first uplink transmission may be completely canceled or may be performed only up to the point or OFDM symbol where the overlap begins. However, even if the priority level of the first uplink transmission is lower than the priority level to be applied, the UE transceiver 870 may still perform part of the transmission on resources not common to the second uplink transmission from the start of the overlap onward.

[0073] An example of a UE circuit 880 that may include uplink priority determination circuitry is shown in Figure 9. For example, the UE circuit 880 includes a UE priority comparison circuit 981 and a UL transmission execute / cancel determination circuit 982.

[0074] Also provided is a base station 810. As shown in Figure 8, the base station 810 includes a transceiver 820 ("base station transceiver") and circuitry 830 ("base station circuitry").

[0075] In operation, the base station circuitry 830 allows the first uplink transmission before scheduling a second uplink transmission assigned to resources that overlap with resources assigned to the first uplink transmission, generates an indication indicating a priority level to apply, and compares the priority level of the first uplink transmission with the indicated priority level to apply. In operation, the base station transceiver 820 transmits the indication and performs reception of the first uplink transmission based on a result of the comparison.

[0076] The base station may be, for example, a scheduling node such as a gNodeB, an eNodeB, or a relay node that can perform scheduling and UL grants.

[0077] The base station 810 grants a first uplink transmission to the UE 860. In accordance with the above mention of the intra-UE and inter-UE cases, the base station may grant a second uplink transmission to the same UE 860 or a different UE than the first UE.

[0078] By performing a comparison according to the comparison performed by the UE 860, the base station determines whether the first UL transmission is performed or not, or whether the first UL transmission is partially performed, and receives the first UL transmission, possibly partially or on the shared resource, or not.

[0079] An example of a base station circuit 830 that may include a UL priority determination circuit is shown in Figure 10. It can be seen that the base station circuit 830 may include a UL grant circuit 1031, a priority indication generation circuit 1032, and a UL priority comparison circuit 1033.

[0080] As can be seen from FIG. 8, in operation the base station and the UE communicate over radio channels of a mobile communication system such as LTE, LTE-A, or 3GPP NR.

[0081] Corresponding to the above UE 860 and base station 810, an uplink transmission method performed by the UE and an uplink reception method performed by the base station are provided, and the steps thereof are shown in FIG.

[0082] The uplink reception method includes allowing a first uplink transmission before scheduling a second uplink transmission assigned to resources that overlap with resources assigned to the first uplink transmission (step 1110).

[0083] Thus, the base station 810 may first schedule and grant a first uplink transmission, and then, at a later point in time, schedule and grant a second uplink transmission. Allocation of overlapping resources to multiple transmissions may occur in scenarios where multiple priority levels may be defined and associated with different transmissions. For example, the transmission level of the second transmission is equal to or greater than the priority level to be applied. For example, only UL transmissions of at least the priority level to be applied are allocated resources that overlap with resources allocated to previously granted transmissions.

[0084] The UL reception method further includes generating an indication of the priority level to be applied (step S1120) and comparing the priority level of the first uplink transmission with the indicated priority level to be applied (S1130). The UL transmission method further includes transmitting an indication of the priority level to be applied (S1140). The indication is received by the UE (step S1150 of the UL transmission method).

[0085] It should be noted that the order of the steps of the UL reception method according to the present disclosure is not limited to that shown in Fig. 11. In particular, step S1130 of comparing priority levels may be performed before step S1110 or before step S1120.

[0086] Furthermore, an indication of the resources allocated to the second transmission, along with an indication of the priority level to apply, may be transmitted from the base station 810 and received by the UE 860. Based on such resource indication, the UE may determine whether the resources allocated to the first and second transmissions overlap, or may determine that the second transmission is allocated to resources that overlap with the resources allocated to the first transmission prior to scheduling the second UL transmission.

[0087] Upon receiving the UL priority indication, the UE performs a comparison of the priority level of the first uplink transmission with the indicated priority level to be applied (step S1160 of the UL transmission method) according to or in a similar manner to step S1130 performed by the base station.

[0088] In step S1170 of the UL transmission method, a first uplink transmission is performed based on the result of step S1160, and if transmitted, the first UL transmission is received by the base station in addition to the second uplink transmission (S1180).

[0089] If the priority comparison determines that both the first and second UL transmissions should be performed, the first uplink transmission may have fewer resources available than previously allocated due to the overlap. In this case, the base station may automatically reschedule the first uplink transmission. For example, the UE may interpret the indication of the priority level to be applied, relative to the indication that resources may be assigned to the second uplink transmission, as implying that the overlapping resources are reassigned or reallocated in some manner previously agreed upon by the UE 860 and the base station 810. For example, resource elements common to both transmissions may be shared equally by the first and second UL transmissions, or may be weighted depending, for example, on whether the priority level of the first UL transmission is equal to or greater than the priority level to be applied.

[0090] Alternatively, overlapping of resources of one type may be resolved by using resources of other types, e.g., spatial division multiplexing, such as multi-user multiple-input multiple-output (MU-MIMO), may be utilized in overlapping regions where the time and frequency resources of different transmissions are the same.

[0091] As noted above, the present disclosure is applicable to cases of inter-UE and intra-UE resource overlap. As an example of the inter-UE case, Figure 12 shows a scheduled resource arrangement similar to that already shown in Figure 7. As noted above, assume again that the transmission scheduled for UE3 is a URLLC uplink transmission and the transmission scheduled for UE2 is an eMBB uplink transmission. According to the present disclosure, UE3 does not need a URLLC uplink transmission because it has a sufficiently high priority with respect to the indicated priority level received in the instruction to decide whether to proceed or cancel.

[0092] As another example of an inter-UE case, assume that priority is indicated by a defined priority element (described below). For example, a first user equipment (UE) UE1 has all UL transmissions scheduled with priority level 1, a second user equipment (UE2) has UL transmissions scheduled with priority level 4, and a third user equipment (UE3) has UL transmissions scheduled with priority level 2. Subsequently, a fourth user equipment (UE4) is scheduled with UL transmissions with priority level 1 on resources that overlap with some of the resources of UE1, UE2, and UE3. Then, based on a comparison of priority levels, only the transmissions of UE2 and UE3 are canceled because they have a lower priority level than the later-scheduled priority level of UE4. At this time, UE1 and UE4 may be multiplexed on the overlapping resources.

[0093] The techniques provided by this disclosure facilitate providing that only low priority UL traffic is canceled, while high priority (possibly URLLC) UL traffic is still viable and able to meet its high delay constraints.

[0094] Furthermore, according to the above cancellation mechanism (steps 1-3), transmissions are canceled not only on overlapping resources but also on subsequent symbols after the overlap or on non-overlapping frequency resources where the overlap occurs in other frequency resources of the same symbol, which may result in resource inefficiencies, if any. Such inefficiencies may be mitigated by the techniques of this disclosure, at least for UEs capable of or designed for high-priority uplink transmissions.

[0095] The instruction indicating the priority to be applied is control information regarding a traffic type (e.g., transmission types with different priorities) or a priority level. Thus, according to the present disclosure, the UE receives control information regarding a priority level to be applied in the overlapped resources (e.g., an explicit instruction of a traffic type, transmission type, or priority level), and performs or cancels an uplink transmission (i.e., the first uplink transmission described above) based on the control information.

[0096] In some embodiments, the indication of the priority level to be applied is included in group common (GC) Downlink Control Information (DCI) that is common to or commonly monitored by a group of UEs configured to monitor the GC DCI.

[0097] The base station 810 transmits a group-common DCI to broadcast control information including an indicator of the priority to be applied.

[0098] In addition to the GC DCI used in steps 1 and 3 of the cancellation mechanism above, the GC DCI according to the present disclosure includes an indication of the priority level to be applied, for example as two or three additional bits, or four or more additional bits. Furthermore, the GC DCI may include an indication of the resources allocated to the second uplink transmission, similar to the GC DCI of the cancellation mechanism above.

[0099] Therefore, the UE 860 needs to be configured to monitor the group-common DCI to determine possible overlap of already granted resources. UEs according to this disclosure may include, for example, NR Release 16 UEs and later release UEs configured to monitor the above group-common DCI.

[0100] For example, during operation, the UE circuit 880 compares an index of the priority level of the first uplink transmission or an index of the transmission type representing the priority level of the first uplink transmission with the indicated priority level to be applied.

[0101] Examples of how or where the index is signaled from the base station 810 to the UE 860 are provided in some embodiments below. Furthermore, with regard to the indication of the priority level to apply, the priority level index corresponds to the above-described direct or explicit mapping between numerical values ​​and priority levels, while the transmission type index representing the priority level corresponds to the indirect or implicit mapping, also as described below.

[0102] In some embodiments, the mapping of the indices to the transmission types, including the transmission type of the first uplink transmission, is specific to the UE or a subset of the UEs that receive the indication.

[0103] A plurality of UEs refers to a group of UEs configured to receive an indication of the priority level to apply, for example, by monitoring the GC DCI. Thus, when each UE or each subset of UEs is specifically configured (e.g., by RRC), if the transmission type (or traffic type or channel type) to apply or cancel varies among the UEs, the value of the broadcasted indication corresponds to the traffic type, channel type, or transmission type to apply.

[0104] Thus, depending on how the UEs among a group of UEs are configured to receive an indication of the priority level to apply (e.g., via broadcast or GC DCI), the indication may indicate different types of transmissions or channels for different UEs among a group of UEs. Here, different UEs may be divided according to the class of UE, the type of traffic / transmission to transmit or perform. For example, the mapping of indexes to transmission types may be configured differently for public safety UEs than for other UEs. Other distinctions may include distinguishing between UEs capable of URLLC traffic and UEs not capable of URLLC traffic.

[0105] For example, using Radio Resource Control (RRC) signaling, the base station 810 semi-statically configures a UE-specific or subset-specific table, where each row has an index, and each index indicates a particular transmission type. For example, a transmission type may include a combination of a usage scenario associated with a channel, a signal type, and a latency.

[0106] Examples of configuration tables for different UEs are shown in Tables 1 and 2.

[0107] [Table 1]

[0108] [Table 2]

[0109] When the UE is configured with one of the above mappings shown in Table 1 and Table 2, the UE MAC layer can inform the UE PHY (Physical layer) about its own scheduled transmission type of the first UL transmission, which is derived based on or associated with the priority of the logical channel ID associated with the transport block (TB) that the MAC passes to the PHY to perform the first UL transmission.

[0110] For example, according to Non-Patent Document 2, radio resource control information elements of up to 16 priority levels can be assigned to logical channels in a logical channel configuration logicalChannelConfig. If a mapping of indexes to transmission types is provided as in Tables 1 and 2, the transmission or traffic types specified in the right-hand columns of these tables can be associated with a subset of the defined priority levels.

[0111] Therefore, based on the above configuration and information from the MAC, the UE PHY can associate the TB for UL PUSCH transmission in the PHY with the traffic priority, so that every UE (including the UE that performs the first UL transmission) will know its own traffic priority.

[0112] For example, the indication of the priority level to apply, signaled as a common bit field in the group common DCI, points to one of the indices in the RRC configuration table to tell each UE (e.g., each UE configured to monitor the GC-DCI for application / cancellation) which traffic types or UL transmission types should be applied or allowed for transmission and which ones should be canceled in case of resource overlap.

[0113] Since the RRC configuration tables may differ for different UEs, the actual cancellation / execution decision for UL transmissions may vary between UEs. In the examples of Tables 1 and 2, if the priority indication to apply in the GC DCI indicates "0", then for public safety UEs configured in Table 1, only RRC messages and HARQ-ACKs should be applied, while for other users configured in Table 2 with a GC DCI indication value of 0, all types of UL transmissions will be canceled if assigned to overlapping resources. Furthermore, the same transmission type, e.g., HARQ-NACK in the URLLC, may be applied to different UEs with different numeric indications, e.g., "0" for public safety UEs and "1" for other UEs, and therefore have different priority levels for different UEs.

[0114] It should be noted that Tables 1 and 2 are exemplary and there are many other possibilities for the type of UE, e.g., URLLC, eMBB, police UE, V2X UE, IoT UE, etc., and many other possibilities for the size of the tables, such as as few as two rows or more than five rows. For example, the type of UE that receives a particular table may be based on the capabilities of the UE and / or the intended type of usage or traffic.

[0115] A flowchart of an exemplary method in which the mapping of index to transmission type is used is shown in FIG.

[0116] In step S1310, the UE configures an RRC-specific table (either specific to the UE or to a subgroup of the group monitoring the GC DCI) with two columns: an index number for application or cancellation and a traffic or transmission type. Next, in step S1320, the UE MAC sends a TB for UL transmission (the "first" UL transmission described above) and associates a traffic or transmission type with the TB based on the logical channel priority. In step S1330, the UE receives a group-wide DCI for cancellation or application. If there is an overlap, the UE checks (S1340) the bit field related to the priority indication for cancellation or application and checks whether the traffic level (transmission type) of the current TB is the same (equal priority) or lower (corresponding to a higher priority) than the priority indication (corresponding to the transmission type) from the GC DCI indicating one of the RRC configuration table indices. If yes, the UE continues or performs the scheduled transmission (first uplink transmission) (S1350). If No, the UE executes the cancellation of the transmission (S1360).

[0117] As mentioned above, the configuration may include a mapping that varies depending on the UE, and the index is mapped to the transmission type.

[0118] However, in some embodiments, the mapping of the multiple indices to multiple priority levels, including the priority level of the first uplink transmission and the priority level of the second uplink transmission, is common to multiple UEs that receive the indication.

[0119] Thus, the transmission type (eg, traffic type or channel type) to be canceled on the overlapping resources may be the same among the UEs indicated by such control information.

[0120] If the mapping of indexes to priority levels is common to UEs, the RRC configuration of such mapping does not need to be specific to a UE (or specific to a type or class of UE), and thus RRC overhead may be reduced.

[0121] In embodiments using Tables 1 and 2, the priority level to apply is indicated indirectly by pointing to the transmission type associated with the priority level. Some embodiments described below use a direct mapping between an indication or index and a priority level.

[0122] For example, in a common mapping for UEs (eg, UEs that monitor a group common DCI), each index may be mapped to a priority level in a one-to-one correspondence.

[0123] Thus, if all UEs are commonly configured (e.g., by RRC) with information such as an indication of the priority level to apply, and the traffic / channel types to be canceled on overlapping resources are the same between UEs, each broadcasted value may correspond to a particular priority level at which transmission is permitted.

[0124] An exemplary mapping table common to all UEs monitoring GC DCI, which may again be semi-statically configured by RRC, with each row consisting of an index, each index pointing to a priority level (corresponding to an absolute priority level in MAC) is shown in Table 3.

[0125] [Table 3]

[0126] With a mapping such as that in Table 3, the UE MAC can inform the UE PHY of an absolute priority level applicable to all channels and transmission types for all UEs. Therefore, a common absolute priority level is assumed for all UL transmissions. Based on this, all UL transmissions can be associated with an absolute priority in the PHY.

[0127] For example, the number of priority levels that can be associated with a logical channel of the MAC may be 16, as described above, but may also be a number greater or less than 16. For example, as shown in Table 3, the number of priority levels of a logical channel may be increased to a greater number based on absolute priorities defined at a higher layer (e.g., a layer higher than the MAC).

[0128] Thus, an indication of the priority level to apply, e.g., a common bit field in the GC DCI, could possibly point to an index in an RRC configured table to convey to all UEs receiving the indication the lowest priority level to apply: all lower priority levels (corresponding to higher indices) should be canceled.

[0129] In the example of Table 3, if the GC DCI indicates 2, all UEs with scheduled or ongoing UL transmissions with priority levels lower than 3 (i.e., 4, 5, 6, etc.) are canceled, and only UEs with priority levels 1, 2, and 3 are allowed to continue their scheduled transmissions.

[0130] In some embodiments, in the mapping of indexes to multiple priority levels, each index is mapped to a range of priority levels.

[0131] For example, if the priority level or transmission type (or traffic type or channel) to be canceled or applied is the same (common or commonly configured, e.g., by RRC) for the UEs addressed by the priority level signaled indication, each value of the broadcasted indication may correspond to a particular priority group to which transmission is allowed or applied.

[0132] For example, a table is configured (e.g., semi-statically by RRC) where each index points to a group (e.g., range, etc.) of priority levels that are common to all UEs. An exemplary mapping of indexes to groups or ranges is shown in Table 4.

[0133] [Table 4]

[0134] Similar to the embodiment where one-to-one correspondence is used as shown in Table 3, the UE MAC may signal to the UE PHY the priority level associated with the transport block for the scheduled transmission. In the group-common DCI for apply or cancel, the common bit field may point to one of the configuration table indices to convey to each UE the range of allowed priority levels to apply on the overlapping resources. Thus, all lower priority level transmissions to which an index higher than the indicated one is mapped should be canceled.

[0135] Coarse priority indication may allow for reduced DCI overhead if a mapping to priority level ranges is used rather than a one-to-one correspondence of index to priority level.

[0136] As an example using Table 4, if the GC DCI indicates "2", all UEs with scheduled or ongoing UL transmissions with priority levels lower than 15 (e.g., levels 16 to 21 if the absolute number of defined priority levels is 21) will be canceled, and only high priority UL transmissions with priority levels 1 to 15 will be allowed to continue their scheduled transmissions.

[0137] It should be noted that the number of rows corresponding to priority levels in the configuration table may be fewer than the examples shown in Tables 1 to 5. For example, in some scenarios, two priority levels may be sufficient, such as a first priority level for URLC traffic and a second priority level for eMBB traffic.

[0138] A flowchart of an exemplary method in which a mapping of indexes to priority levels or priority level ranges is used is shown in FIG.

[0139] In step S1410, the UE configures an RRC-specific table (either specific to the UE or to a subgroup of the group monitoring the GC DCI) with two columns: an index number for application or cancellation, and a priority level or group / range. Next, in step S1420, the UE MAC sends a TB for an UL transmission (the "first" UL transmission described above) and associates a priority level or range with the TB based on the logical channel priority. In step S1430, the UE receives a group-wide DCI for cancellation or application. If there is an overlap, the UE checks (S1440) the bit field related to the priority indication for cancellation or application to see if the priority level or range of the current TB is the same (equal priority) or lower (corresponding to a higher priority) than the priority indication from the GC DCI indicating one of the RRC configuration table indices. If yes, the UE continues or performs the scheduled transmission (first uplink transmission) (S1450). If no, the UE performs the transmission cancellation (S1460).

[0140] In some embodiments, as noted in some of the examples above, the (direct) mapping of multiple indices to priority levels, priority level ranges, or transmission types associated with priority levels is configured by RRC signaling, but the present disclosure also provides techniques for priority indication without RRC influence.

[0141] In some embodiments, the mapping of multiple indices to multiple priority levels, priority level ranges, or transmission types is based on the total number of priority levels defined by the standard. For example, rather than referencing an RRC configuration, the indication of the priority level to apply may point to a mapping agreed upon by the UE 860 and the base station 810 according to the standard. For example, the total number of priority levels may be one of 16 levels in the above example (as in 3GPP TS 23.11.0), 21 levels, 2 levels (URLLC, eMBB), or some other value.

[0142] For example, if the priority level or transmission type (or traffic type or channel) to be canceled or applied is the same for the UEs addressed by the signaled indication of the priority level, each value of the broadcasted indication may correspond to a particular priority level at which transmission is allowed or applied.

[0143] For example, the UE MAC may inform the UE PHY of its currently scheduled traffic type, which is derived based on the priority of the logical channel ID. Based on the mapping from the standard, the TB for UL PUSCH transmission in the PHY can be associated with the traffic priority (a level from a total number of defined levels, e.g., 2, 16, 21), so that every UE knows its traffic priority. Priority can be associated with both the traffic type and a channel or signal, e.g., SRS / PRACH / CSI / HARQ-ACK (Sounding Reference Signal / Physical Random Access Channel / Channel State Information / Hybrid-Automatic Repeat Request Acknowledgement).

[0144] The priority indication to be applied, e.g., a bit field in the GC-DCI, indicates an absolute priority level to inform the UE that if the UE's ongoing or scheduled UL transmission has a lower priority compared to the indicated value, the UL transmission should be canceled; otherwise, the UE should continue with its UL transmission. For example, if the GC-DCI indicates 5, all UEs with ongoing or scheduled UL transmissions should cancel if their corresponding priority is lower than 5 (i.e., 6, 7, etc.).

[0145] If standard-defined settings of priority levels are used directly rather than RRC configuration settings, RRC effects can be avoided. On the other hand, if absolute numbers of priorities are indicated, which may be large, embodiments using semi-static configuration may allow for a reduction in DCI overhead.

[0146] A flowchart of an exemplary method in which a mapping of indexes to transmission types is used is shown in Figure 15. Steps S1520 to S1560 are similar to steps S1420 to S1460 of Figure 14. However, the indication of the priority to apply points to the standard-configured absolute priority level rather than a semi-static RRC-configured mapping of index and priority level or range / group.

[0147] The priority level may be defined by the transmission type. Thus, as described above, different priority levels may be assigned to different transmission types. For example, the indication of the priority level to apply may point to a mapping of an index to a transmission type or a mapping of an index to a priority level. However, in either case, the priority level may be assigned to the transmission type. Thus, the priority level may be defined by the transmission type.

[0148] Examples of transmission types include channel type (e.g., Physical Uplink Shared Channel (PUSCH), PRACH), type of information to be transmitted (SRS, HARQ-ACK), or service requirements. Service requirements may be based on the usage scenario, including, for example, URLLC, eMBB, mMTC, or public safety, in which scheduled uplink transmissions are made.

[0149] As noted above, the embodiments shown in this disclosure are applicable to inter-UE priority-based UL cancellation / UL priority adaptation based on priority indication and MAC-to-PHY information, but once a priority is associated with each UL channel / signal for a particular UE, information regarding such association can also be utilized for intra-UE prioritization / multiplexing or deferral.

[0150] Below are some possible use cases for inter-UE prioritization / multiplexing: High priority grant based PUSCHs are scheduled and low priority grant based PUSCHs are cancelled. • High priority grant based PUSCHs are scheduled and low priority configured grant PUSCHs are cancelled. • High priority grant based PUSCH is scheduled and lower priority PRACH is cancelled. • High priority grant based PUSCH is scheduled and lower SRS is cancelled. High priority grant based PUSCH is scheduled and low priority PUCCH is cancelled.

[0151] In case of intra-UE prioritization, different UL channels / UCIs of the same UE with different / same priorities may have overlapping resources and priority indication from MAC to PHY can be utilized to cancel or multiplex them.

[0152] Additionally, in some embodiments, the UE circuitry 880 includes physical layer circuitry that, during operation, receives information from a Medium Access Control layer indicating a priority level of the first uplink transmission. For example, as discussed in the context of Figures 13-15, the UE MAC may inform the UE physical layer circuitry (UE PHY) of the priority level associated with the transport block for the scheduled transmission, in relation to the TB, so that the UE PHY knows which priority is associated with the transmission to be performed.

[0153] The present disclosure can be realized by software, hardware, or software in conjunction with hardware. Each functional block described in the above embodiments can be realized, in whole or in part, by an LSI such as an integrated circuit. Furthermore, each process described in each embodiment can be controlled, in whole or in part, by the same LSI or a combination of LSIs. The LSI may be formed as an individual chip, or a single chip may be formed to include some or all of the functional blocks. The LSI may include a data input and a data output connected thereto. Here, LSIs are sometimes referred to as ICs, system LSIs, super LSIs, or ultra LSIs depending on their level of integration. However, technologies for realizing integrated circuits are not limited to LSIs and may be realized using dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, FPGAs (Field Programmable Gate Arrays), which can be programmed after LSI fabrication, or reconfigurable processors, which allow the connections and settings of circuit cells arranged within LSIs to be reconfigured, may also be used. The present disclosure can be realized as digital or analog processing. If future integrated circuit technology replaces LSI as a result of advances in semiconductor technology or other derivative technologies, the functional blocks can be integrated using that future integrated circuit technology. Biotechnology is also applicable.

[0154] The present disclosure may be implemented by any type of apparatus, device, or system having communication capabilities, referred to as a communications apparatus.

[0155] Some non-limiting examples of such communication devices include telephones (e.g., mobile phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, vehicles (e.g., automobiles, airplanes, ships) that provide communication capabilities, and various combinations thereof.

[0156] Communications devices are not limited to portable or mobile devices, but may include any type of non-portable or fixed equipment, device, or system, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, or any other "things" in an "Internet of Things" network.

[0157] Communications may include, for example, the exchange of data via cellular systems, wireless LAN systems, satellite systems, and the like, as well as various combinations thereof.

[0158] A communications device may include devices such as controllers and sensors connected to the communications device to perform the communications functions described in this disclosure. For example, a communications device may include a controller or sensor that generates control or data signals used by the communications device to perform the communications functions of the communications device.

[0159] Communications equipment may also include infrastructure facilities, such as base stations, access points, or any other equipment, device, or system that communicates with or controls the equipment in the above non-limiting examples.

[0160] There is provided a user equipment (UE) comprising: a transceiver that, during operation, receives an indication indicating a priority level to apply; and circuitry that, during operation, compares a priority level of a first uplink transmission with the indicated priority level to apply, the first uplink transmission being granted to the UE before scheduling of a second uplink transmission assigned to resources that overlap with resources assigned to the first uplink transmission, wherein the transceiver, during operation, performs the first uplink transmission based on a result of the comparison.

[0161] In some embodiments, the transceiver, during operation, receives group common downlink control information common to a plurality of UEs, the group common downlink control information including the indication of the priority level to apply.

[0162] For example, during operation, the circuit compares an index of the priority level of the first uplink transmission or an index of a transmission type representing the priority level of the first uplink transmission with the indicated priority level to be applied.

[0163] In some embodiments, the mapping of multiple indices to multiple transmission types is specific to the UE or a subset of UEs receiving the indication, the subset including the UE.

[0164] In some embodiments, the mapping of multiple indices to multiple priority levels, including the priority level of the first uplink transmission and the priority level of the second uplink transmission, is common to UEs receiving the indication.

[0165] For example, in the mapping of the plurality of indexes to the plurality of priority levels, each index is mapped to a priority level in a one-to-one correspondence.

[0166] In some embodiments, in the mapping of multiple indices to multiple priority levels, each index is mapped to a range of priority levels.

[0167] For example, the mapping of the plurality of indices is configured by radio resource control signaling.

[0168] For example, the mapping of the indexes to the priority levels is based on the total number of priority levels defined by a standard.

[0169] For example, the priority level is defined by the transmission type.

[0170] For example, the transmission type includes at least one of a channel type, a type of information to be transmitted, or a service requirement.

[0171] In some embodiments, the circuitry comprises physical layer circuitry that, in operation, receives information from a medium access control layer indicating the priority level of the first uplink transmission.

[0172] There is further provided a base station having a circuit that, during operation, allows a first uplink transmission before scheduling a second uplink transmission assigned to resources that overlap with resources assigned to the first uplink transmission, generates an indication indicating a priority level to apply, and compares the priority level of the first uplink transmission with the indicated priority level to apply; and a transceiver that, during operation, transmits the indication and performs reception of the first uplink transmission based on a result of the comparison.

[0173] In some embodiments, the transceiver, in operation, transmits group common downlink control information common to a plurality of UEs, the group common downlink control information including the indication of the priority level to be applied.

[0174] For example, during operation, the circuit compares an index of the priority level of the first uplink transmission or an index of a transmission type representing the priority level of the first uplink transmission with the indicated priority level to be applied.

[0175] In some embodiments, the mapping of multiple indices to multiple transmission types, including the transmission type of the first uplink transmission, is specific to the UE or a subset of UEs receiving the indication, the subset including the UE.

[0176] In some embodiments, the mapping of multiple indices to multiple priority levels, including the priority level of the first uplink transmission and the priority level of the second uplink transmission, is common to UEs receiving the indication.

[0177] For example, in the mapping of the plurality of indexes to the plurality of priority levels, each index is mapped to a priority level in a one-to-one correspondence.

[0178] In some embodiments, in the mapping of multiple indices to multiple priority levels, each index is mapped to a range of priority levels.

[0179] For example, the mapping of the plurality of indices is configured by radio resource control signaling.

[0180] For example, the mapping of the indexes to the priority levels is based on the total number of priority levels defined by a standard.

[0181] For example, the priority level is defined by the transmission type.

[0182] For example, the transmission type includes at least one of a channel type, a type of information to be transmitted, or a service requirement.

[0183] Also provided is an uplink (UL) transmission method comprising the steps of: receiving an indication indicating a priority level to apply; comparing a priority level of a first uplink transmission with the indicated priority level to apply, wherein the first uplink transmission is allowed before scheduling of a second uplink transmission assigned to resources that overlap with resources assigned to the first uplink transmission; and performing the first uplink transmission based on a result of the comparison.

[0184] In some embodiments, the UL transmission method includes receiving group common downlink control information common to a plurality of UEs, the group common downlink control information including the indication of the priority level to be applied.

[0185] For example, the UL transmission method includes a step of comparing an index of a priority level of the first uplink transmission or an index of a transmission type representing the priority level of the first uplink transmission with the indicated priority level to be applied.

[0186] In some embodiments, the mapping of multiple indices to multiple transmission types, including the transmission type of the first uplink transmission, is specific to the UE or a subset of UEs receiving the indication, the subset including the UE.

[0187] In some embodiments, the mapping of multiple indices to multiple priority levels, including the priority level of the first uplink transmission and the priority level of the second uplink transmission, is common to UEs receiving the indication.

[0188] For example, in the mapping of the plurality of indexes to the plurality of priority levels, each index is mapped to a priority level in a one-to-one correspondence.

[0189] In some embodiments, in the mapping of multiple indices to multiple priority levels, each index is mapped to a range of priority levels.

[0190] For example, the mapping of the plurality of indices is configured by radio resource control signaling.

[0191] For example, the mapping of the indexes to the priority levels is based on the total number of priority levels defined by a standard.

[0192] For example, the priority level is defined by the transmission type.

[0193] For example, the transmission type includes at least one of a channel type, a type of information to be transmitted, or a service requirement.

[0194] In some embodiments, the method includes receiving, on a physical layer, information from a medium access control layer indicating the priority level of the first uplink transmission.

[0195] There is further provided an uplink reception method comprising the steps of: allowing a first uplink transmission before scheduling a second uplink transmission assigned to resources that overlap with resources assigned to the first uplink transmission; generating an indication indicating a priority level to apply; comparing the priority level of the first uplink transmission with the indicated priority level to apply; transmitting the indication; and performing reception of the first uplink transmission based on a result of the comparison.

[0196] In some embodiments, the UL reception method includes transmitting group common downlink control information common to a plurality of UEs, the group common downlink control information including the indication indicating the priority level to be applied.

[0197] For example, the UL reception method includes a step of comparing an index of a priority level of the first uplink transmission or an index of a transmission type representing the priority level of the first uplink transmission with the indicated priority level to be applied.

[0198] In some embodiments, the mapping of multiple indices to multiple transmission types, including the transmission type of the first uplink transmission, is specific to the UE or a subset of UEs receiving the indication, the subset including the UE.

[0199] In some embodiments, the mapping of multiple indices to multiple priority levels, including the priority level of the first uplink transmission and the priority level of the second uplink transmission, is common to UEs receiving the indication.

[0200] For example, in the mapping of the plurality of indexes to the plurality of priority levels, each index is mapped to a priority level in a one-to-one correspondence.

[0201] In some embodiments, in the mapping of multiple indices to multiple priority levels, each index is mapped to a range of priority levels.

[0202] For example, the mapping of the plurality of indices is configured by radio resource control signaling.

[0203] For example, the mapping of the indexes to the priority levels is based on the total number of priority levels defined by a standard.

[0204] For example, the priority level is defined by the transmission type.

[0205] For example, the transmission type includes at least one of a channel type, a type of information to be transmitted, or a service requirement.

[0206] Also provided is a 5th Generation Core (5GC) entity (e.g., AMF / SMF, etc.) having: control circuitry that, in operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmitter that, in operation, sends an initial context setup message over the NG connection to the gNodeB to trigger a signaling radio bearer setup between the gNodeB and a user equipment (UE), wherein the gNodeB sends Radio Resource Control (RRC) signaling over the signaling radio bearer to the UE, the RRC signaling including a resource allocation configuration information element; and wherein the UE, in operation, receives an indication indicating a priority level to apply, compares a priority level of a first uplink transmission with the indicated priority level to apply (the first uplink transmission being allowed to the UE before scheduling a second uplink transmission assigned to resources that overlap with resources assigned to the first uplink transmission), and performs the first uplink transmission based on a result of the comparison and the resource allocation configuration.

[0207] In some embodiments, group common downlink control information common to a plurality of UEs is transmitted from the gNodeB to the UEs, the group common downlink control information including the indication indicating the priority level to be applied.

[0208] For example, an index of the priority level of the first uplink transmission or an index of a transmission type representing the priority level of the first uplink transmission is compared with the indicated priority level to be applied by at least one of the UE and the gNodeB.

[0209] In some embodiments, the mapping of multiple indices to multiple transmission types, including the transmission type of the first uplink transmission, is specific to the UE or a subset of UEs receiving the indication, the subset including the UE.

[0210] In some embodiments, the mapping of multiple indices to multiple priority levels, including the priority level of the first uplink transmission and the priority level of the second uplink transmission, is common to UEs receiving the indication.

[0211] For example, in the mapping of the plurality of indexes to the plurality of priority levels, each index is mapped to a priority level in a one-to-one correspondence.

[0212] In some embodiments, in the mapping of multiple indices to multiple priority levels, each index is mapped to a range of priority levels.

[0213] For example, the mapping of the plurality of indices is configured by radio resource control signaling.

[0214] For example, the mapping of the indexes to the priority levels is based on the total number of priority levels defined by a standard.

[0215] For example, the priority level is defined by the transmission type.

[0216] For example, the transmission type includes at least one of a channel type, a type of information to be transmitted, or a service requirement.

[0217] In some embodiments, the UE comprises physical layer circuitry that, during operation, receives information from a medium access control layer indicating the priority level of the first uplink transmission.

[0218] In summary, the present disclosure relates to a user equipment, a base station, an uplink transmission method, and an uplink reception method, the user equipment including: a transceiver that, during operation, receives an indication indicating a priority level to apply; and circuitry that, during operation, compares a priority level of a first uplink transmission with the indicated priority level to apply, the first uplink transmission being granted to the UE before scheduling of a second uplink transmission assigned to resources that overlap with resources assigned to the first uplink transmission; and the transceiver, during operation, performs the first uplink transmission based on a result of the comparison.

Claims

1. A base station, a transceiver configured to transmit an indication of an indirect priority level to be applied to a plurality of user equipments (UEs) by means of group common downlink control information, the transceiver transmitting a first radio resource control signaling constituting a first setting of priority or a second radio resource control signaling constituting a second setting of priority; a circuit for comparing a priority level of a first uplink transmission in the UE with the indicated priority level to be applied, the comparison being dependent on a first or second priority setting, and allowing the UE to perform the first uplink transmission before transmitting the group-common downlink control information indicating allocation of resources for scheduling a second uplink transmission that overlaps with resources allocated to the first uplink transmission; the transceiver performs or cancels reception of the first uplink transmission based on a result of the comparison; Base station.

2. comparing an index of a priority level of the first uplink transmission or an index of a transmission type representing the priority level of the first uplink transmission with the indicated priority level to be applied; The base station of claim 1 .

3. a mapping of a plurality of indexes to a plurality of transmission types, including the transmission type of the first uplink transmission, is specific to the UE or a subset of UEs receiving the indication, the subset including the UE; The base station of claim 2.

4. a mapping of a plurality of indexes to a plurality of priority levels, including the priority level of the first uplink transmission and the priority level of the second uplink transmission, being common to UEs receiving the indication; The base station of claim 1 .

5. wherein the mapping of the plurality of indexes to the plurality of priority levels is such that each index is mapped to a priority level in a one-to-one correspondence. The base station of claim 4.

6. wherein the mapping of the plurality of indices to the plurality of priority levels, each index is mapped to a range of priority levels. The base station of claim 4.

7. the mapping of the plurality of indices is configured by the first or second radio resource control signaling. The base station according to claim 3 .

8. the mapping of the indexes to the priority levels is based on a total number of priority levels defined by a standard. The base station of claim 4.

9. The priority level is defined by a transmission type. The base station according to claim 3 .

10. the transmission type includes at least one of a channel type, a type of information to be transmitted, or a service requirement; The base station of claim 2.

11. the circuitry includes physical layer circuitry that transmits information from a medium access control layer that indicates the priority level of the first uplink transmission. The base station of claim 1 .

12. transmitting an indication of an applicable priority level to a plurality of user equipments (UEs) via group common downlink control information common to the plurality of UEs; transmitting a first radio resource control signaling constituting a first setting of priorities or a second radio resource control signaling constituting a second setting of priorities; comparing a priority level of a first uplink transmission in the UE with the indicated priority level to be applied, the comparison being dependent on a first or second priority setting, and allowing the UE to perform the first uplink transmission before transmitting the group-common downlink control information indicating allocation of resources for scheduling a second uplink transmission that overlaps with resources allocated to the first uplink transmission; performing or not performing reception of the first uplink transmission based on a result of the comparison; and An uplink receiving method comprising:

13. An integrated circuit for controlling processing of a base station, the processing comprising: transmitting an indication of an applicable priority level to a plurality of user equipments (UEs) via group common downlink control information common to the plurality of UEs; transmitting a first radio resource control signaling constituting a first setting of priorities or a second radio resource control signaling constituting a second setting of priorities; comparing a priority level of a first uplink transmission in the UE with the indicated priority level to be applied, the comparison being dependent on a first or second priority setting, and allowing the UE to perform the first uplink transmission before transmitting the group-common downlink control information indicating allocation of resources for scheduling a second uplink transmission that overlaps with resources allocated to the first uplink transmission; performing or not performing reception of the first uplink transmission based on a result of the comparison; and 1. An integrated circuit comprising:

Images