User Equipment and Base Stations

Abstract

To provide an integrated circuit that performs or cancels an uplink transmission based on a result of the comparison between a priority level of the uplink transmission and an indicated priority level to be enforced.SOLUTION: An integrated circuit that controls processing of user equipment (UE) is provided, the integrated circuit performs transmission / reception processing for receiving the priority level to be enforced through group-common Downlink Control Information common to a plurality of UEs. The transmission / reception processing receives a first setting on the priority level or a second setting on the priority level. Then, the integrated circuit compares the priority level of a first uplink transmission with an indicated priority level to be enforced and performs control processing of either executing or cancelling the first uplink transmission based on a result of the comparison.SELECTED DRAWING: Figure 11

Description

Technical Field

[0001] The present disclosure relates to the transmission and reception of signals in a communication system. In particular, the present disclosure relates to methods and apparatuses for such transmission and reception.

Background Art

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

[0003] In the case of systems such as LTE, LTE-A, and NR, further changes and options can facilitate the efficient operation of the communication system and specific devices related to the system.

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

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 an integrated circuit that controls processing of a user equipment (UE), the processing including: a transmission / reception process that receives an instruction indirectly indicating a priority level to be applied by group-common downlink control information common to a plurality of UEs, the transmission / reception process receiving 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 control process that compares a priority level of a first uplink transmission with the indicated priority level to be applied, the comparison differing depending on the first or second setting related to priority, the first uplink transmission being permitted to the UE before reception of 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 control process performing or canceling 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] Note that general or specific embodiments can be realized as a system, method, integrated circuit, computer program, storage medium, or any optional combination thereof.

[0009] Further benefits and advantages of the disclosed embodiments will become apparent from the present specification and drawings. These benefits and / or advantages can be obtained individually by various embodiments and features of the specification and drawings, but not all of them are provided to obtain one or more of such benefits and / or advantages.

Brief Description of the Drawings

[0010] Hereinafter, exemplary embodiments will be described in more detail with reference to the accompanying drawings.

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

[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 in late 2017, allowing for the trial and commercial deployment of smartphones compliant with the 5G NR standard.

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

[0015] Various deployment scenarios can be supported. For example, a non-centralized deployment scenario is presented herein, where a base station supporting 5G NR can be deployed. FIG. 2 shows an exemplary non-centralized deployment scenario, further showing an LTE eNB, and a user equipment (UE) connected to both the gNB and the LTE eNB. The new eNB for NR 5G may be exemplarily called a gNB. The eLTE eNB is an evolved version of the eNB that supports connectivity to the EPC (Evolved Packet Core) and the NGC (Next Generation Core).

[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 Functional 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 roaming right check, - Mobility management control (subscription and policy), - Support for Network Slicing, - Selection of Session Management Function (SMF).

[0021] Furthermore, the User Plane Function (UPF) hosts the following main functions. - Anchor point for RAT-in / RAT-out mobility (if applicable), - External PDU session point for interconnection to the Data Network, - Packet routing and forwarding, - User plane part of packet inspection and policy rule enforcement, - Traffic usage reporting, - Uplink classifier to support routing of traffic flows to the Data Network, - Branch point to support multi-homed PDU sessions, - QoS processing for the user plane, e.g., packet filtering, gating, UL / DL rate enforcement, - Uplink traffic verification (flow mapping from SDF to QoS), - Downlink packet buffering and downlink data notification trigger.

[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] Procedures for RRC Connection Setup and Reconfiguration

[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 keys, UE radio capabilities, 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] Therefore, in the present disclosure, during operation, an entity (such as AMF, SMF, etc.) of the 5th Generation Core (5GC) is provided, which has a control circuit for establishing a Next Generation (NG) connection with a gNodeB, and a transmitter for transmitting an initial context setup message to the gNodeB via the NG connection during operation to trigger the setup of a signaling radio bearer between the gNodeB and a User Equipment (UE). In particular, the gNodeB transmits Radio Resource Control (RRC) signaling including resource allocation configuration information elements to the UE via the signaling radio bearer. Thereafter, the UE performs uplink transmission or downlink reception based on the resource allocation setting.

[0026] IMT Usage Scenarios after 2020

[0027] Figure 5 shows a part of the 5G NR use cases. In the new radio of the 3rd generation partnership project (3GPP NR), three use cases are considered that are expected to support a variety of services and applications by IMT-2020. The Phase 1 specifications for enhanced mobile-broadband (eMBB) are completed. In addition to further expanding eMBB support, current and future work will involve the standardization of ultra-reliable and low-latency communications (URLLC) and massive machine-type communications. Figure 5 shows some examples of the expected usage scenarios of IMT after 2020.

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

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

[0030] Furthermore, the targeted technical enhancements for NR URLCC aim to improve latency and reliability. Technical enhancements for latency improvement include configurable numerology, non-slot-based scheduling by flexible mapping, grant-free (configured grant) uplink, slot-level repetition of data channels, and downlink pre-emption. Pre-emption means interrupting a transmission for which resources have already been allocated and using the already allocated resources for other transmissions that are requested later but require lower latency / higher priority. Thus, an already permitted transmission is pre-empted by a later transmission. Pre-emption is applicable regardless of the specific service type. For example, a transmission of service type A (URLCC) can be pre-empted by a transmission of service type B (such as eMBB). Technical enhancements for reliability improvement include a dedicated CQI / MCS table for a target BLER of 1E-5.

[0031] The use cases of mMTC are generally characterized by a very large number of connected devices that transmit relatively small amounts of data that are not sensitive to latency. The devices are required to be low-cost and have a very long battery life. From the perspective of NR, utilizing a very narrow bandwidth portion is one possible solution that is power-saving from the UE perspective and enables a long battery life.

[0032] As described above, it is expected that the range of reliability in NR will expand. An important requirement for all cases, especially for URLLC and mMTC, is high reliability or ultra-high reliability. To improve reliability from the wireless and network perspectives, several mechanisms can be considered. Generally, there are few important potential areas that can help improve reliability. Among these areas are compact control channel information, repetition of data / control channels, and diversity regarding frequency, time, and / or spatial domains. These areas are generally applicable to reliability regardless of the specific communication scenario.

[0033] In the case of NR URLLC, for example, additional use cases with more stringent requirements have been identified, such as factory automation, transportation, and power supply. The more stringent requirements are higher reliability (up to the 10^-6 level), higher availability, packet sizes up to 256 bytes, time synchronization reduced to the order of several μs (where the value can be 1 μs or several μs depending on the frequency range), and low latency on the order of 0.5 - 1 ms depending on the use case (especially, the target user plane latency is 0.5 ms).

[0034] Furthermore, in the case of NR URLCC, several technical enhancements from the perspective of RAN1 have been identified. Among these are enhancements related to compact DCI, PDCCH repetition, PDCCH (Physical Downlink Control Channel) enhancements related to increased PDCCH monitoring. Additionally, UCI (Uplink Control Information) enhancements are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback. Also, PUSCH enhancements related to mini-slot level hopping and retransmission / repetition enhancements have been identified. The term "mini-slot" refers to a transmission time interval (TTI: Transmission Time Interval) that contains a smaller number of 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, the QoS flow is the finest granularity for QoS differentiation in a PDU session. A QoS flow is identified within a PDU session by a QoS flow ID (QFI) that is carried in a capsule header through 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) together with the PDU session and can then configure additional DRBs (if any) for the QoS flows (if any) of that PDU session, as described above with reference to Figure 4 (when doing so, it is up to the NG-RAN). The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and the 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and the NG-RAN associate UL and DL QoS flows with DRBs.

[0038] Figure 6 shows the 5G NR non-roaming reference architecture. The Application Function (AF) interacts with the 3GPP Core Network to provide services that support, for example, traffic routing, access to the Network Exposure Function (NEF), or the application's influence on the policy framework for policy control (see Policy Control Function (PCF)). Based on operator deployment, application functions considered trusted by the operator may be permitted to interact directly with the relevant Network Function. Application functions not permitted by the operator to directly access network functions interact with the relevant network functions using the external exposure framework provided by the NEF.

[0039] Figure 6 shows further functional units of the 5G architecture, namely, the Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and Data Network (DN), for example, 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 various types of data transfer services provided by the MAC. Each logical channel type is defined by the type of information being transferred. Logical channels are classified into two groups: the control channel and the traffic channel. The control channel is used only for the transfer of control plane information. The traffic channel is used only for the transfer of user plane information.

[0044] And logical channels are mapped to transport channels by the MAC layer. For example, logical traffic channels and some logical control channels can be mapped to a transport channel called the downlink shared channel (DL-SCH) in the downlink, and also to a transport channel called the uplink shared channel (UL-SCH) in the uplink.

[0045] Inter-UE prioritization

[0046] Usage scenarios such as NR URLLC motivate the study of uplink (UL) prioritization and multiplexing among UEs. In particular, the need for prioritization arises when UL transmission has already been scheduled for user equipment UE1, or when there is an ongoing UL transmission being executed by UE1, and then a high-priority UL transmission is scheduled for another user equipment UE2 to be transmitted on resources that at least partially overlap with the resources used for the UL transmission of UE1.

[0047] For this reason, the following cancellation mechanism can be applied.

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

[0049] Step 2: A high-priority UE (possibly URLLC traffic) that may partially or fully overlap with already scheduled or ongoing UL transmissions from other UEs is scheduled.

[0050] Step 3: The gNB transmits a PDCCH with GC DCI to cancel the ongoing UL transmission. Only the UEs configured to monitor the GC DCI respond and, if the ongoing transmissions partially or fully overlap with the time-frequency region indicated by the GC DCI, cancel all those ongoing transmissions. Here, the transmission is cancelled and not resumed.

[0051] In the above cancellation mechanism, Steps 2 and 3 can be interchanged.

[0052] Furthermore, as described above, a group of UEs is configured to monitor a PDCCH carrying group-common DCI. This group may include UEs that carry out uplink traffic that is generally given a lower priority than other UL traffic. For example, eMBB traffic may be given a lower priority than traffic carried out by URLLC traffic or 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 a technique that enables selective cancellation of specific uplink transmissions (e.g., low-priority transmissions) of a UE when detecting signals such as group-common DCI for cancellation. Among them, aspects and embodiments of the disclosed embodiments include an inter-UE case where a newly scheduled UL transmission has resources overlapping with transmissions of other UEs, and an intra-UE case where a newly scheduled transmission and a previously scheduled overlapping transmission are scheduled for the same UE.

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

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

[0059] Furthermore, the term "circuit" refers to a processing circuit such as, for example, one or more processors or a CPU (central processing unit), and includes hardware components such as an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a software implementation executed on any hardware, or any combination of hardware and software.

[0060] The transceiver 870 of the UE 860, or simply the "UE transceiver", receives an indication indicating the priority level to be applied during operation.

[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 be applied 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 assigned 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 to which time and / or frequency multiplexing is applied. Other possible resources include spatial resources, such as when MIMO (multiple input multiple output) is applied, or orthogonal codes are included.

[0067] The overlapping resources assigned to the first transmission and the second transmission include completely overlapping resources (all such resource elements assigned to different transmissions are identical, and the resources of one transmission are completely constituted by the resources assigned to the other transmission), or partially overlapping resources. Generally, the overlapping resources assigned to the first transmission and the second transmission are overlapping if they share at least one common resource element.

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

[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, in the comparison, if it is determined that the priority level of the first uplink transmission is lower than the priority level to be applied as instructed, the first uplink transmission is not executed on at least the resources common to the first uplink transmission and the second uplink transmission. Thus, for example, the first uplink transmission is either completely canceled or executed only up to the point where the overlap starts or up to the OFDM symbol. 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 execute a part of the transmission on resources that are not common with the second uplink transmission from the start of the overlap onwards.

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

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

[0075] During operation, the base station circuit 830 permits the first uplink transmission before scheduling a second uplink transmission assigned to resources overlapping with the resources assigned to the first uplink transmission, generates an instruction indicating the priority level to be applied, and compares the priority level of the first uplink transmission with the priority level to be applied as instructed. During operation, the base station transceiver 820 transmits the instruction and executes the reception of the first uplink transmission based on the 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 capable of performing scheduling and UL grants.

[0077] The base station 810 permits a first uplink transmission to the UE 860. In accordance with the above references for the in-UE case and the inter-UE case, the base station may permit a second uplink transmission to the same UE 860 or a UE different from 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 whether the first UL transmission is partially performed, and receives the first UL transmission, optionally partially or on shared resources, or does not receive it.

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

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

[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 their steps are shown in FIG. 11.

[0082] The uplink reception method includes permitting a first uplink transmission (step 1110) before scheduling a second uplink transmission assigned to a resource overlapping with the resource assigned to the first uplink transmission.

[0083] Therefore, the base station 810 first schedules and permits the first uplink transmission, and then, at a later time, schedules and permits the second uplink transmission. The allocation of multiple transmissions to overlapping resources can occur in a scenario where multiple priority levels are defined and can be associated with different transmissions. For example, the transmission level of the second transmission is equal to or higher than the priority level to be applied. For example, only UL transmissions with at least the priority level to be applied are allocated to resources that overlap with the resources allocated to the previously permitted transmission.

[0084] Furthermore, the UL reception method includes generating an indication indicating 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). This indication is received by the UE (step S1150 of the UL transmission method).

[0085] Note that the order of each step of the UL reception method according to the present disclosure is not limited to that shown in FIG. 11. In particular, the step S1130 of comparing the priority levels may be executed before step S1110 or before step 1120.

[0086] Furthermore, in addition to the indication of the priority level to be applied, an indication of the resources allocated to the second transmission can be transmitted from the base station 810 and received by the UE 860. Based on such a resource indication, the UE can determine whether the resources allocated to the first transmission and the second transmission overlap, or can determine that the second transmission is allocated to resources that overlap with the resources allocated to the first transmission before scheduling this 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 to 3), transmission is cancelled not only on overlapping resources, but also on subsequent symbols after the overlap, or on non-overlapping frequency resources where the overlap occurs on other frequency resources of the same symbol, which may be inefficient resources if any. Such inefficiency can be reduced by the technology of the present disclosure, at least for high-priority uplink transmissions or for UEs designed for high-priority uplink transmissions.

[0095] An indication indicating the priority to be applied is control information regarding a traffic type (for example, transmission types with different priorities) or a priority level. Therefore, according to the present disclosure, a UE receives control information regarding the priority level to be applied (for example, an explicit indication of a traffic type, a transmission type, or a priority level) in overlapping resources, and based on this control information, executes or cancels an uplink transmission (that is, the first uplink transmission described above).

[0096] In some embodiments, an indication indicating the priority level to be applied is included in group common (GC) downlink control information (DCI) that is common to a plurality of UE groups configured to monitor GC DCI or is generally monitored by the plurality of UE groups.

[0097] By transmitting group common DCI by the base station 810, control information including an indicator of the priority to be applied is broadcast.

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

[0099] Therefore, the UE 860 needs to be configured to monitor the group common DCI in order to determine the possibility of duplication of already permitted resources. The UE according to the present disclosure may include, for example, a UE of NR Release 16 and a UE of subsequent releases configured to monitor the above group common DCI.

[0100] For example, during operation, the UE circuit 880 compares the index of the priority level of the first uplink transmission or the 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 described below. Further, regarding the indication of the priority level to be applied, as will also be described below, the index of the priority level corresponds to the above-described direct or explicit mapping between the numerical value and the priority level, and the index of the transmission type representing the priority level corresponds to an indirect or implicit mapping.

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

[0103] The plurality of UEs refers to a group of UEs configured to receive an indication of the priority level to be applied, for example, by monitoring the GC DCI. Therefore, when each UE or each subset of UEs is specifically configured (e.g., by RRC), if the transmission types (or traffic types or channel types) to be applied or canceled are different among the UEs, the value of the broadcast indication corresponds to the traffic type, channel type, or transmission type to be applied.

[0104] Thus, depending on how the UE that receives an indication of the priority level to be applied (e.g., by broadcast or GC DCI) is configured among the UEs, the indication may indicate different types of transmissions or channels for different UEs from among the group of UEs. Here, the different UEs may be split according to the class of the UE, the type of traffic / transmission to be sent or executed. For example, the mapping of the index to the transmission type may be configured differently for public safety UEs than for other UEs. Other distinctions may include the distinction between UEs capable of URLLC traffic and UEs not capable of URLLC traffic.

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

[0106] Examples of configuration tables for different UEs are shown in Table 1 and Table 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 is configured with a specific table of RRC (unique to the UE or unique to a subgroup of the group monitoring GC DCI) having two columns of an index number for application or cancellation and a traffic type or transmission type. Next, in step S1320, the UE MAC sends a TB for UL transmission (the above-mentioned "first" UL transmission) and associates a traffic type or transmission type with that TB based on the logical channel priority. In step S1330, the UE receives group-common DCI for cancellation or application. If there is an overlap, the UE checks a bit field regarding the priority indication for cancellation or application (S1340) and checks whether the traffic level (transmission type) of the current TB is the same (equal priority) as or lower than the priority indication (corresponding to the transmission type) from the GC DCI indicating one of the indexes in the RRC configuration table. If Yes, the UE continues or performs the scheduled transmission (the first uplink transmission) (S1350). If No, the UE performs cancellation of the transmission (S1360).

[0117] As described above, the configuration can include different mappings by the UE, and the index is mapped to the transmission type.

[0118] However, in some embodiments, the 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 is common to a plurality of UEs receiving the indication.

[0119] Therefore, the transmission types (e.g., traffic type or channel type) canceled in overlapping resources can be the same among the UEs indicated by such control information.

[0120] When the mapping of the index to the priority level is common to the UEs, the RRC configuration of such mapping does not need to be UE-specific (or specific to the type or class of the UE), and thus, the RRC overhead can be reduced.

[0121] In embodiments using Tables 1 and 2, the priority levels to be applied are indirectly indicated by indicating the transmission type associated with the priority level. Some embodiments described below use a direct mapping between the indication or index and the priority level.

[0122] For example, in a common mapping for a UE (e.g., a UE monitoring group-common DCI), each index can be mapped to a priority level in a one-to-one correspondence.

[0123] Thus, when all UEs are generally configured (e.g., by RRC) with information such as an indication of the priority level to be applied, and when the traffic / channel types to be cancelled in overlapping resources are the same among the UEs, each broadcast value can correspond to a specific priority level for which transmission is permitted.

[0124] Table 3 shows an exemplary mapping table common to all UEs monitoring GC DCI, which can be statically configured again by RRC, where each row consists of an index and each index indicates a priority level (corresponding to the absolute priority level in the MAC).

[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 of using Table 4, when the GC DCI indicates "2", all UEs for which UL transmissions with a priority level lower than 15 (for example, when the absolute number of defined priority levels is 21, levels 16 to 21) are scheduled or in progress are cancelled, and only high-priority UL transmissions with priority levels 1 to 15 are permitted to continue the scheduled transmissions.

[0137] Note that it should be noted that the number of rows corresponding to the priority levels in the configuration table may be less than those shown in the examples of 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 to an index priority level or priority level range is used is shown in FIG. 14.

[0139] In step S1410, the UE is configured with a specific table of RRC that has two columns of an index number for application or cancellation and a priority level or group / range, which is specific to the UE or specific to a subgroup of the group monitoring the GC DCI. Next, in step S1420, the UE MAC sends a TB for UL transmission (the above-mentioned "first" UL transmission) and associates a priority level or range with that TB based on the logical channel priority. In step S1430, the UE receives a group-common DCI for cancellation or application. If there is an overlap, the UE checks a bit field regarding the priority indication for cancellation or application (S1440) and checks whether the priority level or range of the current TB is the same (equal priority) as or lower than the priority indication from the GC DCI indicating one of the indexes in the RRC configuration table (corresponding to higher priority). If Yes, the UE continues or executes the scheduled transmission (the first uplink transmission) (S1450). If No, the UE executes a cancellation of the transmission (S1460).

[0140] In some embodiments, as also described in some of the above examples, the (direct) mapping of a plurality of indexes to priority levels, priority level ranges, or transmission types associated with priority levels is configured by RRC signaling. However, the present disclosure also provides a technique for priority indication without the influence of RRC.

[0141] In some embodiments, the mapping of a plurality of indexes to a plurality of priority levels, priority level ranges, or transmission types is based on the total number of priority levels defined by the standard. For example, instead of referring to the RRC configuration, the indication of the priority level to be applied may indicate the mapping agreed upon by the UE860 and the base station 810 according to the standard. For example, the total number of priority levels may be one of 16 levels (as in Non-Patent Document 3), 21 levels, 2 levels (URLLC, eMBB), or some other value in the above example.

[0142] For example, if the priority level or transmission type (or traffic type or channel) to be cancelled or applied is the same for the UE to which the priority level is signaled by the indication, each value of the broadcast indication may correspond to a specific priority level for which transmission is permitted or applied.

[0143] For example, the UE MAC may notify 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 transport block (TB) for UL PUSCH transmission in the PHY can be associated with the traffic priority (the total number of defined levels, e.g., levels from 2, 16, 21), and thus all UEs will know their traffic priorities. The priority can also be associated with the traffic type and with channels or signals such as, for example, SRS / PRACH / CSI / HARQ-ACK (Sounding Reference Signal / Physical Random Access Channel / Channel State Information / Hybrid-Automatic Repeat Request Acknowledgement).

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

[0145] When directly using the setting of the priority level standard definition instead of the RRC configuration setting, the influence of RRC can be avoided. On the other hand, when the absolute number of priorities is indicated, although it may be large, embodiments using a quasi-static configuration can enable reduction of DCI overhead.

[0146] A flowchart of an exemplary method in which mapping to the transmission type of an index is used is shown in FIG. 15. Steps S1520 to S1560 are the same as steps S1420 to S1460 in FIG. 14. However, the priority indication to be applied indicates the absolute priority level of the standard configuration, rather than the quasi-static RRC configuration mapping of the index and the priority level or range / group.

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

[0148] Examples of the transmission type include the channel type (e.g., PUSCH (Physical Uplink Shared Channel), PRACH), the type of information to be transmitted (SRS, HARQ-ACK), or the service requirement. The service requirement can be based on, for example, a usage scenario including URLLC, eMBB, mMTC, or public safety in which scheduled uplink transmission is performed.

[0149] As described above, the embodiments shown in the present disclosure are applicable to UE - based UL cancellation / UL priority application based on priority indication and information from MAC to PHY. However, once the priority is associated with each UL channel / signal for a particular UE, the information regarding such an association can also be used for in - UE prioritization / multiplexing or deferral.

[0150] Some use cases for inter - UE prioritization / multiplexing are considered below. ● The PUSCH based on a high - priority grant is scheduled, and the PUSCH based on a low - priority grant is cancelled. ● The PUSCH based on a high - priority grant is scheduled, and the PUSCH based on a low - priority configured grant is cancelled. ● The PUSCH based on a high - priority grant is scheduled, and the lower - level PRACH is cancelled. ● The PUSCH based on a high - priority grant is scheduled, and the lower - level SRS is cancelled. ● The PUSCH based on a high - priority grant is scheduled, and the low - priority PUCCH is cancelled.

[0151] In the case of in - UE prioritization, different / same UL channels / UCI of the same UE having different priorities can have overlapping resources, and the priority indication from MAC to PHY can be used to cancel or multiplex them.

[0152] Furthermore, in some embodiments, the UE circuitry 880 has a physical - layer circuitry that receives, during operation, information indicating a priority level of a first uplink transmission from a Medium Access Control layer. For example, as described in the context of FIGS. 13 - 15, the UE MAC can notify the UE physical - layer circuitry (UE PHY) of the priority level associated with the transport block for a scheduled transmission, so that the UE PHY knows which priority is associated with the transmission to be executed for the TB.

[0153] The present disclosure can be implemented by software, hardware, or software in cooperation with hardware. Each functional block used in the description of each of the above embodiments can be realized, partially or entirely, by an LSI such as an integrated circuit, and each process described in each embodiment may be controlled, partially or entirely, by the same LSI or a combination of LSIs. The LSI may be formed individually as a chip, or one chip may be formed to include part or all of the functional blocks. The LSI may include a data input and a data output connected thereto. Here, depending on the degree of integration, the LSI may be referred to as an IC, a system LSI, a super LSI, or an ultra LSI. However, the technology for realizing the integrated circuit is not limited to the LSI, and it may be realized using an application-specific circuit, a general-purpose processor, or a dedicated processor. Further, an FPGA (Field Programmable Gate Array) that can be programmed after manufacturing the LSI, or a reconfigurable processor that can reconfigure the connection and setting of circuit cells arranged inside the LSI may be used. The present disclosure can be realized as digital processing or analog processing. When future integrated circuit technology replaces the LSI as a result of the progress of semiconductor technology or other derivative technologies, the functional blocks can be integrated using the future integrated circuit technology. Biotechnology is also applicable.

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

[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, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine (remote health and medicine) devices, vehicles that provide communication capabilities (e.g., automobiles, airplanes, ships), and various combinations thereof.

[0156] The communication device is not limited to being portable or mobile, and may include, for example, smart home devices (e.g., home appliances, lighting, smart meters, control panels), vending machines, and any type of device, apparatus, or system that is non-portable or fixed, such as any "things" in the network of the "Internet of Things (IoT)".

[0157] Communication may include, for example, the exchange of data by a cellular system, a wireless LAN system, a communication satellite system, etc., and the exchange of data by various combinations thereof.

[0158] The communication device may have devices such as a controller or a sensor connected to a communication device that executes the communication function described in the present disclosure. For example, the communication device may have a controller or a sensor that generates a control signal or a data signal used by a communication device that executes the communication function of the communication device.

[0159] In addition, the communication device may include infrastructure facilities, such as base stations, access points, and any other device, apparatus, or system that communicates with or controls the devices in the above non-limiting examples.

[0160] A user equipment (UE) includes a transceiver that receives, during operation, an indication indicating a priority level to be applied, and a circuit that compares, during operation, a priority level of a first uplink transmission with the indicated priority level to be applied, where the first uplink transmission is permitted in the UE before scheduling of a second uplink transmission assigned to a resource overlapping with a resource assigned to the first uplink transmission, and the transceiver executes the first uplink transmission based on a result of the comparison during operation.

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

[0162] For example, the circuit compares, during operation, 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, a mapping of a plurality of indices to a plurality of transmission types is specific to the UE or a subset of UEs that receive the indication, and the subset includes the UE.

[0164] In some embodiments, a mapping of a plurality of indices to a plurality of priority levels including the priority level of the first uplink transmission and the priority level of the second uplink transmission is common to the UE that receives the indication.

[0165] For example, in the mapping of the plurality of indices 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 the plurality of indexes to the plurality of priority levels, each index is mapped to a range of priority levels.

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

[0168] For example, the mapping of the plurality of indexes to the plurality of priority levels is based on the total number of priority levels defined by the 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 circuit has a physical layer circuit that, during operation, receives information indicating the priority level of the first uplink transmission from a media access control layer.

[0172] During operation, before scheduling a second uplink transmission assigned to a resource overlapping with the resource assigned to the first uplink transmission, the first uplink transmission is permitted, an instruction indicating the priority level to be applied is generated, and the priority level of the first uplink transmission is compared with the indicated priority level to be applied; and during operation, the instruction is transmitted, and a transceiver that executes reception of the first uplink transmission based on the result of the comparison is further provided in a base station.

[0173] In some embodiments, the transceiver transmits, during operation, group common downlink control information common to a plurality of UEs, including the instruction indicating 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 a plurality of indices 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 that receive the indication, and the subset includes the UE.

[0176] In some embodiments, the mapping of a plurality of indices to a plurality of priority levels including the priority level of the first uplink transmission and the priority level of the second uplink transmission is common to the UE that receives the indication.

[0177] For example, in the mapping of the plurality of indices 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 a plurality of indices to a plurality of 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 plurality of indices to the plurality of priority levels is based on the total number of priority levels defined by the 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 service requirements.

[0183] Also provided is an uplink (UL) transmission method, which includes: receiving an instruction indicating a priority level to be applied; comparing a priority level of a first uplink transmission with the priority level to be applied indicated by the instruction, where the first uplink transmission is permitted before scheduling of a second uplink transmission allocated to a resource overlapping with the resource allocated to the first uplink transmission; and executing the first uplink transmission based on a result of the comparison.

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

[0185] For example, the UL transmission method includes comparing 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 priority level to be applied indicated by the instruction.

[0186] In some embodiments, a mapping of a plurality of indices 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 instruction, and the subset includes the UE.

[0187] In some embodiments, a mapping of a plurality of indices to a plurality of priority levels including the priority level of the first uplink transmission and the priority level of the second uplink transmission is common to the UE receiving the instruction.

[0188] For example, in the mapping of the plurality of indices 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 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 priority level to be applied as indicated.

[0198] In some embodiments, the 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 that receive the indication, and the subset includes the UE.

[0199] In some embodiments, the 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 is common to the UEs that receive 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 a plurality of indexes to a plurality of priority levels, each index is mapped to a range of priority levels.

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

[0203] For example, the mapping of the plurality of indexes to the plurality of priority levels is based on the total number of priority levels defined by the 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 an entity of a 5th Generation Core (5GC) (e.g., AMF / SMF, etc.), which includes a control circuit that establishes a Next Generation (NG) connection with a gNodeB during operation, and a transmitter that transmits an initial context setup message to the gNodeB via the NG connection during operation to trigger signaling radio bearer setup between the gNodeB and a User Equipment (UE). The gNodeB transmits Radio Resource Control (RRC) signaling including a resource allocation configuration information element to the UE via the signaling radio bearer. The UE receives an instruction indicating a priority level to be applied during operation, compares the priority level of a first uplink transmission (the first uplink transmission is permitted to the UE prior to scheduling of a second uplink transmission allocated to a resource overlapping with the resource allocated to the first uplink transmission) with the indicated priority level to be applied, and executes the first uplink transmission based on the result of the comparison and the resource allocation configuration.

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

[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 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 that receive the indication, and the subset includes the UE.

[0210] In some embodiments, the 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 is common to the UEs that receive 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 a plurality of indexes to a plurality of priority levels, each index is mapped to a range of priority levels.

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

[0214] For example, the mapping of the plurality of indexes to the plurality of priority levels is based on the total number of priority levels defined by the 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 has a physical layer circuit that receives, during operation, from the media access control layer, information indicating the priority level of the first uplink transmission.

[0218] Briefly, the present disclosure relates to a user equipment, a base station, an uplink transmission method, and an uplink reception method. The user equipment includes a transceiver that receives an instruction indicating a priority level to be applied during operation, and a circuit that compares, during operation, a priority level of a first uplink transmission with the indicated priority level to be applied, wherein the first uplink transmission is permitted by the UE prior to scheduling of a second uplink transmission assigned to a resource overlapping with a resource assigned to the first uplink transmission, and the transceiver executes the first uplink transmission based on a result of the comparison during operation.

Claims

1. An integrated circuit for controlling the processing of a user equipment (UE), wherein the processing is a transmission / reception process of receiving, by group common downlink control information common to a plurality of UEs, an instruction indirectly indicating a priority level to be applied, and receiving first radio resource control signaling configuring a first setting regarding priority or second radio resource control signaling configuring a second setting regarding priority, and the transmission / reception process, a control process of comparing a priority level of a first uplink transmission with the indicated priority level to be applied, the comparison being different according to the first or second setting regarding priority, and the first uplink transmission being permitted by the UE before receiving the group common downlink control information indicating an allocation of resources for scheduling a second uplink transmission overlapping with the resources allocated to the first uplink transmission, and the control process, wherein the transmission / reception process executes or cancels the first uplink transmission based on the result of the comparison, the integrated circuit.

2. The control process 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. The integrated circuit according to claim 1.

3. The mapping of a plurality of indices 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 instruction, and the subset includes the UE. The integrated circuit according to claim 2.

4. The mapping of a plurality of indices to a plurality of priority levels including the priority level of the first uplink transmission and the priority level of the second uplink transmission is common to the UEs receiving the instruction. The integrated circuit according to claim 1.

5. In the mapping of the plurality of indices to the plurality of priority levels, each index is mapped to a priority level in a one-to-one correspondence. The integrated circuit according to claim 4.

6. In the mapping of the plurality of indices to the plurality of priority levels, each index is mapped to a range of priority levels. The integrated circuit according to claim 4.

7. The mapping of the plurality of indexes is configured by the first or second radio resource control signaling. The integrated circuit according to claim 3.

8. The mapping of the plurality of indexes to the plurality of priority levels is based on the total number of priority levels defined by a standard. The integrated circuit according to claim 4.

9. The priority level is defined by a transmission type. The integrated circuit 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 integrated circuit according to claim 2.

11. The control process has a physical layer circuit that receives information indicating the priority level of the first uplink transmission from a media access control layer. The integrated circuit according to claim 1.

Images