RU2809557C2 - User equipment and base station - Google Patents

Abstract

FIELD: communication system.

SUBSTANCE: invention relates to the transmission and reception of signals in a communication system. To provide the ability to selectively cancel specific uplink transmissions in the event of a conflict with another uplink transmission, the user equipment containing the transceiver receives a priority level indicator to be enforced. The circuit compares the priority level of the first uplink transmission with the specified priority level to be enforced. Moreover, the first uplink transmission is allowed by the UE before scheduling the second uplink transmission, which is assigned resources that overlap with the resources assigned to the first uplink transmission. The transceiver, in operation, makes the first uplink transmission based on the comparison result.

EFFECT: provision of ability to selectively cancel specific uplink transmissions in the event of a conflict with another uplink transmission.

17 cl, 15 dwg

Description

TECHNICAL FIELD

The present invention relates to the transmission and reception of signals in a communication system. In particular, the present invention relates to methods and apparatus for such transmission and reception.

BACKGROUND OF THE ART

The Third Generation Partnership Project (3GPP consortium) is working on the technical specifications for the next generation of cellular technology, called fifth generation (5G), including radio access technology (RAT) “New Radio” (NR), which operates in frequency bands up to 100 GHz . The NR system is a successor of the technology represented by Long-Term Evolution (LTE) technology and Long-Term Evolution-Advanced Technology (LTE-A).

For systems such as LTE, LTE-A and NR, additional modifications and options can assist in the efficient operation of the communications system as well as the specific devices associated with the system.

DISCLOSURE OF THE INVENTION

One non-limiting and exemplary embodiment facilitates the ability to selectively cancel specific uplink transmissions in the event of a conflict with another uplink transmission.

In one embodiment, the technologies disclosed herein include a user equipment (UE) comprising a transceiver that operatively receives an indicator indicating a priority level to be enforced, and circuitry that operatively compares the priority level of a first uplink transmission with a specified priority level to be enforced, wherein the first uplink transmission is granted to the user equipment (UE) before scheduling a second uplink transmission assigned to resources overlapping with the resources assigned to the first uplink transmission, wherein the transceiver in operation performs the first uplink transmission based on the comparison result.

It should be noted that general or specific embodiments may be implemented as a system, method, integrated circuit, computer program, storage medium, or any selected combination thereof.

Additional advantages and disadvantages of the disclosed embodiments will become apparent from the description and accompanying drawings. Benefits and/or advantages may be selectively obtained by implementing various embodiments and features described herein and shown in the accompanying drawings, which need not all be provided in order to obtain one or more of such benefits and/or advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

The following example implementations are described in more detail with reference to the accompanying diagrams and accompanying drawings.

In FIG. 1 is a schematic drawing illustrating an exemplary architecture for a 3GPP NR system;

In FIG. 2 is a block diagram illustrating an exemplary user and control plane architecture for an LTE eNB, a gNB, and a user equipment (UE);

In FIG. 3 is a schematic drawing illustrating the functional separation between NG-RAN and 5GC;

In FIG. 4 shows a sequence diagram for radio resource control (RRC) connection setup/reconfiguration procedures;

In FIG. 5 is a schematic drawing showing use cases for enhanced mobile broadband, mass machine type communications (mMTC), and ultra-reliable low latency communications (URLLC);

In FIG. 6 is a block diagram illustrating an exemplary 5G system architecture;

In FIG. 7 is a schematic diagram illustrating a mechanism for canceling uplink transmissions when resources overlap;

In FIG. 8 is a block diagram illustrating a user equipment and a base station;

In FIG. 9 is a block diagram showing a user equipment uplink priority determination scheme;

In FIG. 10 is a block diagram showing an uplink priority determination scheme of a base station;

In FIG. 11 is a block diagram illustrating uplink transmission and reception methods;

In FIG. 12 is a schematic diagram illustrating the execution and cancellation of uplink transmissions under overlapping resources;

In FIG. 13-15 are block diagrams showing uplink transmission methods.

IMPLEMENTATION OF THE INVENTION

NR 5G system architecture and protocol stacks

The 3GPP consortium is working on the next release of ^5th generation cellular technology, simply called 5G, including the development of New Radio (NR) access technology operating at frequencies up to 100 GHz. The first version of the 5G standard was completed in late 2017, allowing 5G NR standard testing and commercial smartphone deployments to begin.

Among other things, the overall system architecture assumes a Next Generation - Radio Access Network (NG-RAN), which includes gNBs providing the user plane (access layer / packet data convergence protocol / radio link control protocol access control protocol to the medium/physical layer (SDAP/PDCP/RLC/MAC/PHY) with next generation radio access (NG-radio access) and control plane protocol pins (RRC) towards the UE. The gNB stations are interconnected via the Xn interface. The gNBs are also connected via a Next Generation (NG) interface to the Next Generation Core (NGC), more specifically to the Access and Mobility Management Function (AMF) (e.g., to a specific entity kernel performing the AMF function) via the NG-C interface, and to a User Plane Function (UPF) (e.g., a specific kernel object performing the UPF function) via the NG-U interface. The NG-RAN architecture is shown in FIG. 1.

Various deployment scenarios can be supported. For example, the document presents a non-centralized deployment scenario in which base stations supporting NR 5G can be deployed. In FIG. 2 shows an exemplary non-centralized deployment scenario while further illustrating an LTE eNB as well as a user equipment (UE) that is connected to both the gNB and the LTE eNB. The new eNB for NR 5G can be called gNB as an example. The eLTE eNB is an evolution of the eNB that supports connectivity to the Evolved Packet Core (EPC) and Next Generation Core (NGC).

The user plane protocol stack for NR contains PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control) and MAC (Medium Access Control) sublayers, which terminate at the gNB on the network side. In addition, a new sublayer of the access layer (Access Stratum, AS) (SDAP, Service Data Adaptation Protocol) is introduced above PDCP. The control plane protocol stack is also defined for NR.

5G NR functional separation between NG-RAN and 5GC

In FIG. Figure 3 shows the functional separation between NG-RAN and 5GC. A logical node of an NG-RAN is a gNB or ng-eNB. The 5GC core has the AMF, UPF and SMF logical nodes mentioned above.

Specifically, gNB and ng-eNB perform the following main functions:

- Functions for radio resource management such as radio bearer control, radio receiver control, connection mobility management, dynamic resource assignment to UEs in both uplink and downlink (scheduling);

- Compression, encryption and data integrity protection of IP headers;

- AMF selection upon UE attach when routing to the AMF cannot be determined from information provided by the user equipment (UE);

- Routing user plane data towards the UPF function(UPF functions);

- Routing control plane information towards AMF;

- Setting up and releasing the connection;

- Dispatching and transmission of paging messages;

- Dispatching and transmission of system broadcast information (emanating from AMF or OAM);

- Configuration of measurements and measurement reports for mobility and dispatching;

- Marking of transport layer packets in the uplink;

- Session management;

- Support for network segmentation;

- QoS flow control and mapping of QoS flow to radio data media;

- Support for user equipment (UE) devices in the RRC_INAKTIVE state;

- NAS message distribution function;

- Sharing of a radio access network;

- Possibility of double connection;

- Tight interaction between NR and E-UTRA.

The Access and Mobility Management Function (AMF) performs the following main functions:

- Stopping the transmission of signals from an inaccessible layer (Non-Access Stratum, NAS);

- Security of NAS signaling;

- Security management of the access layer (AC, Access Stratum);

- Inter Core Network (CN) node signaling for mobility between 3GPP access networks;

- Reachability of user equipment (UE) in idle mode (including control and execution of paging relay);

- Management of the registration area;

- Support for intra-system and inter-system mobility;

- Access authentication;

- Access authorization, including checking roaming rights;

- Control of mobility management (subscription and policies);

- Support for network segmentation;

- Selecting the Session Management Function (SMF).

In addition, the User Plane Function (UPF) contains the following core functions:

- Anchor point for intra-/inter-technological mobility (if applicable);

- Connection point for an external PDU session to the data network;

- Routing and redirection of packets;

- Compliance with packet inspection rules and parts of the user policy plane;

- Reporting on traffic usage;

- Uplink classifier to support routing of traffic flows into the data network;

- Branch point to support PDU session with multiple connections;

- QoS processing for the user plane, such as packet filtering, gating, UL/DL rate assurance;

- Checking uplink traffic (mapping SDF to QoS stream);

- Buffering downlink packets and triggering downlink data notification.

Finally, the Session Management function (SMF) contains the following main functions:

- Session management;

- Assignment and management of the UE IP address;

- Selection and control of the UP function;

- Configure traffic control in the User Plane Function (UPF) to direct traffic to the appropriate destination;

- Control part of policy implementation and QoS;

- Downlink data notification.

Procedures for setting up and reconfiguring an RRC connection

In FIG. 4 illustrates some interactions between the UE, gNB and AMF (5GC entity) in that RRC is a higher layer signaling information (protocol) used to configure the UE and gNB. Specifically, the AMF prepares UE context data (including, for example, PDU session context, security key, UE radio capability, and UE security capability, etc.) and sends it to the gNB with an INITIAL CONTEXT SETUP REQUEST. . The gNB then activates AS security with the specified UE, which is accomplished by the gNB sending a SecurityModeCommand message to the UE and the UE responding to the gNB with a SecurityModeComplete message. The gNB then performs reconfiguration to set up Radio Signaling Bearer 2 (SRB2) and Radio Data Bearer (DRB) via RRCReconfiguration and RRCReconfigurationComplete messages. For a signaling-only connection, step 8 is skipped because SRB2 and DRB are not installed. Finally, the gNB informs the AMF that the setup procedure is complete with an INITIAL CONTEXT SETUP RESPONSE response.

Thus, in the present invention, there is provided an object (eg, AMF, SMF, etc.) of a 5th generation core (5GC) comprising a control circuit that, when operative, establishes a Next Generation (NG) connection with a gNodeB, and a transmitter that operatively transmits a context initialization setup message via an NG connection to a gNodeB to cause radio signaling information bearer setup between the gNodeB and a user equipment (UE). Specifically, the gNodeB transmits radio resource control (RRC) signaling information containing a resource assignment configuration information element to the UE via a radio signaling information bearer. The UE then performs uplink transmission or downlink reception based on the resource assignment configuration.

IMT use cases for 2020 and beyond

In FIG. Figure 5 shows some of the use cases for 5G NR. The 3rd Generation Partnership New Radio (3GPP NR) project explores three use cases designed to support a wide range of services and applications using the IMT-2020 specification. The specification for phase 1 of enhanced mobile broadband (eMBB) has been completed. In addition to further expanding support for advanced mobile broadband eMBB, current and future work may include standardization of ultra-reliable low-latency communications (URLLC) and machine-type mass communications. In FIG. Figure 5 shows some examples of envisioned IMT use cases up to 2020 and beyond.

The Ultra Reliable Low Latency Communications (URLLC) use case places stringent demands on throughput, latency and availability and has been envisioned as one of the enablers to enable future vertical applications such as wireless industrial or process control. remote medical surgery, automation of distribution in a smart network, transport safety, etc. The ultra-reliability of the URLLC system is maintained by defining methods that meet the requirements established by technical report TR 38.913. For the NR URLCC v15 network, key requirements include a user plane delay target of 0.5 ms for UL (uplink) and 0.5 ms for DL (downlink). A common URLLC requirement for a single packet transmission is a block error rate (BLER) of 1E-5 for a packet size of 32 bytes with a user plane of 1 ms.

From the perspective of the RAN1 standard, reliability can be improved in various ways. Current areas of improvement in reliability are the definition of separate CQI tables for URLLC communications, more compact downlink control information (DCI) formats, PDCCH repetition, and the like. However, this area can be expanded to achieve ultra-reliability as the NR network becomes more stable and mature to meet the key requirements of the URLCC NR communication network. Accordingly, an NR URLLC network under Release 15 must be capable of transmitting 32 bytes of data packet with a user plane delay of 1 ms with a success rate that corresponds to the error rate of BLER 1E-5 blocks. Special cases of using NR URLCC Vol. 15 include Augmented Reality/Virtual Reality (AR/VR), e-health, e-security and mission-critical applications.

Moreover, technological improvements targeted at the NR URLCC network aim to improve latency and improve reliability. display display display Technology enhancements to improve latency include configurable numerology, slot-free scheduling with flexible mapping, resolution-free uplink (with configurable resolution), slot-level retry for data channels, and downlink priority interruption. Preemption means that a transfer for which resources have already been assigned is stopped and the already allocated resources are used for another transfer that was requested later but has lower latency requirements/higher priority. Accordingly, an already authorized transmission is interrupted by a later transmission. Priority interruption is applied regardless of the specific type of service. For example, a transmission for service type A (URLCC) may be interrupted by a transmission for service type B (eg eMBB). Reliability enhancements to the technology include dedicated CQI/MCS tables for target error rates across BLER 1E-5 blocks.

The massive machine-type communication (mMTC) use case is characterized by a very large number of connected devices, typically transferring a relatively small amount of latency-insensitive data. The devices must be inexpensive and must have a very long battery life. From the NR network point of view, using parts with very narrow bandwidth is one of the possible solutions to save energy from the UE point of view and ensure long battery life.

As mentioned above, the scope of reliability in the NR network is expected to become broader. One of the key requirements for all cases, especially necessary for URLLC and mMTC communication, is high reliability or ultra-reliability. Several mechanisms for improving reliability can be considered from a radio and network perspective. Overall, there are several key potential areas that can help improve reliability. These areas include compact control channel information, data/control channel repetition, and frequency, time and/or spatial domain diversity. These areas apply to reliability in general, regardless of specific communication scenarios.

Additional use cases with more stringent requirements have been identified for the URLLC NR communications network, including manufacturing automation, transportation, and power distribution. More stringent requirements are higher reliability (up to level 10-6), higher availability, packet sizes up to 256 bytes, time synchronization up to several µs, where the value can be one or more µs depending on the frequency range, and short latency of the order of 0 ,5-1ms, specifically the user target plane latency of 0.5ms, depending on the use cases.

Moreover, for the NR communication network URLCC, several technology improvements have been identified in terms of the RAN1 standard. These include improvements to the Physical Downlink Control Channel (PDCCH) related to compact DCI information, PDCCH repetition, and enhanced PDCCH monitoring. Additionally, Uplink Control Information (UCI) enhancements are coupled with enhanced Hybrid Automatic Repeat Request (HARQ) and CSI feedback enhancements. PUSCH enhancements related to mini-slot level hopping and relay/repeat enhancements were also identified. The term "mini-slot" refers to a Transmission Time Interval (TTI) containing fewer symbols than a slot (a slot contains fourteen symbols).

QoS management

The 5G QoS model is based on QoS flows and supports both QoS flows that require a guaranteed bit rate (QoS flows with GBR guarantee) and QoS flows that do not require a guaranteed bit rate (QoS flows without GBR guarantee). Thus, at the NAS layer level, the QoS flow is the finest granularity of QoS differentiation in a PDU session. A QoS flow is identified in a PDU session by a QoS flow identifier (QFI) carried in the encapsulation header over the NG-U interface.

For each UE, the 5GC core establishes one or more PDU sessions. For each UE, the NG-RAN node installs at least one radio data bearer (DRB) along with the PDU session, and additional radio data bearers DRB for the QoS flow(s) of that PDU session can be subsequently configured (this is NG-RAN dependent, when to do this), for example, as shown above with reference to FIG. 4. The NG-RAN node maps packets belonging to different PDU sessions to different DRB bearers. NAS layer packet filters in the UE and 5GC core associate UL and DL packets with QoS flows, while AS layer mapping rules in the UE and NG-RAN node associate UL and DL QoS flows with DRB bearers.

In FIG. Figure 6 shows a 5G NR reference architecture without roaming. The Application Function (AF) interacts with the 3GPP core network to provide services, such as supporting application influence on traffic routing, accessing the Network Exposure Function (NEF), or interacting with the Policy framework for policy management (see .Policy Control Function (PCF). Based on the operator's deployment, Application Functions that the operator considers trusted may be allowed to communicate directly with the corresponding Network Functions. Application functions that the operator does not allow direct access to network functions use the external exposure infrastructure through the NEF function to interact with the corresponding network functions.

In FIG. Figure 6 shows additional functional blocks of the 5G architecture, namely: Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function ( Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF) and Data Network (DN), e.g. operator services, access to Internet or third party services.

The terminal device in LTE and NR systems is called user equipment (UE). It may be a mobile or communications device such as a cordless phone, smartphone, tablet or USB flash drive with user equipment functionality. However, the term "mobile device" is not limited to this, and, in general, a repeater may also have the functionality of such a mobile device, and the mobile device may also operate as a repeater.

The base station is a network node, for example, it forms part of the network to provide services to end devices. The base station is the network node or dispatch node that provides wireless access to end devices. Communication between the terminal and the base station is usually standardized. In LTE and NR systems, the wireless interface protocol stack includes the physical layer, the media access layer (MAC), and higher layers. In the control plane, a radio resource control protocol upper layer protocol is provided. Through RRC, the base station can manage the configuration of the end devices, and the end devices can communicate with the base station to perform management tasks such as connection and media establishment, modification thereof, or the like, as well as measurements and other functions.

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

Logical channels are various types of data services, such as those offered by the MAC layer. Each type of logical channel is determined by the type of information transmitted. Logical channels are divided into two groups: Control channels and traffic channels. Control channels are used only to transmit information to the control plane. Traffic channels are used only to transmit information to the user plane.

Logical channels are then mapped by the MAC layer to transport channels. For example, logical traffic channels and some logical control channels can be mapped to a transport channel called a downlink shared channel (DL-SCH) and a transport channel called an uplink shared channel (UL-SCH). SCH).

Prioritization between UEs

Use cases such as NR URLLC motivate consideration regarding the prioritization and multiplexing of uplink (UL) transmissions between user equipment (UE) devices. In particular, the need for prioritization may arise when a UL transmission is already scheduled for UE1, or there is a current UL transmission being performed by UE1 and a high priority UL transmission is later scheduled for another UE2 to transmit on resources that overlap at least at least with some of the resources used by UL transmission for UE1.

The following cancellation mechanism may be used for this purpose:

Step 1: A specific group of user equipment (UE) is configured to monitor a PDCCH carrying group-wide (GC) downlink control information (DCI) that contains information related to termination of an ongoing transmission.

Step 2: Dispatch the UL transmission of the high priority UE (possibly with URLLC traffic), which may partially or completely overlap with already scheduled or ongoing UL transmission from other UEs.

Step 3: The gNB sends a PDCCH with DCI GC information to cancel ongoing UL transmissions. Only those UEs that are configured to monitor the DCI GC will respond to and cancel any ongoing transmissions if they partially or completely overlap with the time-frequency domain specified in the DCI GC in which the transmission is canceled and not resumed.

In the cancellation mechanism described above, stage 2 and stage 3 are interchangeable in order of execution.

In addition, it should be noted that a certain group of UEs is configured to monitor a PDCCH carrying group-wide DCI information. This group may include UEs carrying uplink traffic, which is typically given a lower priority than other UL traffic. For example, eMBB traffic may be given a lower priority than URLLC traffic or traffic carried by public safety UEs, such as police UEs.

An example of the cancellation mechanism described above is shown in FIG. 7. In this example, transmissions of UE1, UE2 and UE3 are already scheduled when a new transmission is scheduled for a possibly high priority UE that uses resources that overlap with those of UE2 and UE3. The overlap area is communicated to UE1, UE2 and UE3 via group-wide DCI information. As can be seen in the figure, only the transmissions of UE2 and UE3 overlap with the new scheduled transmission, but not the transmission of UE1. When the cancellation mechanism described above is applied, all transmissions of UE2 and UE3 are canceled starting from the time at which the new transmission is scheduled to start. Until this point in time, i.e. before the overlap, some of the canceled transfers can still be carried out.

According to the cancellation mechanism described above, a group of UEs that are configured to monitor a group-wide DCI for cancellation always cancel their scheduled or ongoing UL transmissions using resources overlapping with a new scheduled high-priority transmission upon detection of a group-wide DCI, regardless of whether whether their current transmission is low priority (perhaps eMBB) or high priority (perhaps URLCC).

However, it may be that UEs that support both URLLC traffic and eMBB traffic, or more generally different types of traffic associated with different priorities, are configured to monitor the group-wide DCI for cancellation. For example, in FIG. 7 shows that 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, it is acceptable to cancel the transmission of UE2 because it is a low priority equipment (eMBB). However, when the mechanism described above is applied, UE3 also cancels the transmission, although the transmission is a URLLC (high priority) transmission.

The present invention provides methods for allowing selective cancellation of specific UE uplink transmissions, eg, low priority transmissions, upon detection of a signal such as group-wide DCI downlink control information for cancellation. Disclosed aspects of the embodiments and embodiments include both the case of inter-User Equipment (UE) transmissions where a newly scheduled UL transmission has resource overlap with another UE's transmission resources, and the case of intra-UE transmissions where there is resource overlap newly scheduled transmission and previously scheduled transmission for the same UE.

A user equipment (UE) 860 is provided, including a transceiver 870 and circuitry 880, as shown in FIG. 8.

As used herein, the term “transceiver” (transmitter-receiver) refers to hardware and software configured to transmit and receive, such as in a wireless communication network. The transceiver hardware components may include one or more antennas and/or oscillators, as well as control circuitry configured to control the transceiver hardware based on associated software.

Additionally, the term "circuitry" refers to a processing circuit such as one or more processors or CPUs (central processing unit(s)), and includes hardware components such as an ASIC (application specific integrated circuit), FPGA (field programmable gate array), software implementations running on any hardware, or any combination of hardware and software.

The transceiver 870 of the UE 860, or “UE transceiver” for short, operationally receives an indicator indicating the priority level to be enforced.

The priority level indicator may be a numeric or logical value that is mapped to or associated with priority for uplink transmissions. According to various embodiments to be described, there may be an explicit or direct mapping between an indicator and a priority level from a scale, ranking, or hierarchy of priority levels. The pointer may also point to a range of priority levels from a given or defined hierarchy of priority levels. Alternatively, an implicit or indirect mapping may be performed where the pointer is mapped to a transmission type and the transmission type is associated with a transmission priority or transmission priority level.

In addition, the “enforceable priority level” or “overriding priority level” is the priority level that must be assigned to transmissions that must be carried out even in the event of resource overlap.

In addition, it should be noted that the indication of the priority level to be enforced is not necessarily associated with a specific transfer, but may generally refer to the priority level of any transfers that must be made in the event of resource overlap with those of another transfer.

UE circuitry 880 (“UE circuitry”) operates by comparing the priority level of the first uplink transmission with a specified priority level to be enforced. The first uplink transmission is an uplink transmission that was provided to the UE by a dispatch node, such as a base station, before scheduling the second uplink transmission by the dispatch node. The second uplink transmission is an uplink transmission that is assigned resources that at least partially overlap with the resources assigned to the first uplink transmission.

In general, the second uplink transmission may be a transmission provided to a UE 860 that was also provided the first transmission, corresponding to the case of prioritizing transmissions within the same UE, or to a different UE, corresponding to the case of prioritizing transmissions between different UEs.

The resources that are allocated for the first and second uplink transmissions may include time and frequency grid resources, for example, the resource grid of an LTE, LTE-A, 3GPP NR or similar communication system that employs time and/or frequency multiplexing . Other possible resources include spatial resources, for example when MIMO (multiple input, multiple output) or orthogonal codes are used.

The overlapping resources assigned to the first transmission and the second transmission include completely overlapping resources, all resource elements assigned to different transmissions are identical, and the resources of one transmission consist entirely of resources assigned to another transmission or partially overlapping resources. In general, overlapping resources assigned to a first transmission and a second transmission are overlapping if they have at least one resource element in common.

For example, corresponding priority information may be provided at the physical layer for each UE uplink transmission, including the first uplink transmission of user equipment (UE) 860 in accordance with the present invention. The priority information can be used to selectively cancel only low priority UL transmissions of either the same UE (to prioritize transmissions within the same UE) or different UEs (to prioritize transmissions between UEs that are already scheduled or in progress) and obtained by control information that is common to a group of UEs in case of overlap with high priority UE channels/signals (which are scheduled later).

For example, comparing the first transmission priority level with the priority level to be enforced includes determining whether the first transmission priority level on the uplink is the same as the specified priority level to be enforced, or determining whether the first transmission priority level is uplink equal to or higher than the priority level to be enforced. The manner in which the comparison is performed may depend on the manner in which the priority indicator to be enforced is specified and, accordingly, on what type of priority information about the first uplink transmission is provided.

The UE transceiver 870, in operation, performs a first uplink transmission based on the comparison result.

For example, if the comparison determines that the priority level of the first uplink transmission is the same as the priority level to be enforced, or equal to or greater than the specified priority level to be enforced, then the first uplink transmission is performed. In addition, if the first transmission begins with an OFDM symbol before the start of the overlap (eg, before the first OFDM symbol in the time when the overlap occurs), it continues even from the start of the overlap onwards. For example, common resources assigned to both the first transmission and the second transmission may be shared or shared between the first and second transmissions on the uplink. In addition, the first transmission may use resources that are not common to the first and second transmissions, but which are on the OFDM symbols affected by the overlap, or OFDM symbols after the overlap, that would not have been used if the cancellation mechanism described above had been applied ( stages 1-3).

On the other hand, if the comparison determines that the priority level of the first uplink transmission is lower than the specified priority level to be enforced, then the first uplink transmission is not performed on at least the resources common to the first uplink transmission and the second transmission via the ascending channel. For example, in this case, the first uplink transmission is completely canceled or performed only up to the point in time or OFDM symbol when overlap begins. However, even in the case where the priority level of the first uplink transmission is lower than the priority level to be enforced, the UE transceiver 870 may still perform portions of the transmission on resources not shared with the resources of the second uplink transmission from the start of the overlap and further.

An example of a UE circuit 880 that may include an uplink priority determination circuit is shown in FIG. 9. For example, UE circuitry 880 includes a UE priority comparison circuitry 981 and a UL decision making/aborting circuitry 982.

A base station 810 is also provided. As shown in FIG. 8, base station 810 includes a transceiver 820 (“base station transceiver”) and circuitry 830 (“base station circuit”).

Base station circuitry 830, in operation, allows a first uplink transmission before scheduling a second uplink transmission that is assigned resources that overlap with the resources assigned to the first uplink transmission, generates an indicator indicating the priority level to be enforced, and compares the level priority of the first uplink transmission with a specified priority level to be enforced. The base station transceiver 820 operatively transmits the indicated indicator and receives the first uplink transmission based on the comparison result.

The base station may be, for example, a scheduling node such as a gNodeB, eNodeB, or a relay node configured to perform scheduling and UL provisioning.

The base station 810 allows the UE 860 to transmit the first uplink transmission. In accordance with the above cases of prioritizing transmissions of the same UE and prioritizing transmissions between different UEs, the base station may allow a second uplink transmission to the same UE 860 or a UE different from the first UE.

By performing a comparison in accordance with the comparison performed by the UE 860, the base station determines whether the first UL transmission is in progress or the first UL transmission is partially in progress, and receives either partially, using shared resources, or does not receive the first UL transmission at all.

An example of a base station circuit 830 that may include a UL priority determination circuit is shown in FIG. 10. As shown in the drawing, the base station circuit 830 may include a UL grant circuit 1031, a priority indicator generation circuit 1032, and a UL priority comparison circuit 1033.

As seen in FIG. 8, the base station and the UE operate to communicate over a wireless channel of a mobile communication system such as LTE, LTE-A or 3GPP NR.

In accordance with the above-disclosed UE 860 and the base station 810, an uplink transmission method to be performed by the UE and an uplink reception method to be performed by the base station are proposed, steps of which are shown in FIG. eleven.

A method for receiving an uplink includes the step 1110 of allowing a first uplink transmission before scheduling a second uplink transmission that is assigned resources that overlap with the resources assigned to the first uplink transmission.

Accordingly, base station 810 first schedules and allows the first uplink transmission, and then schedules and allows the second uplink transmission at a subsequent time. The assignment of overlapping resources to multiple transmissions may occur in scenarios in which multiple priority levels are defined and may be associated with different transmissions. For example, the priority level of the second transmission is the same as the priority level to be enforced, or a higher priority level. For example, only UL transmissions of at least the priority level to be enforced are assigned resources that overlap with resources assigned to previously allowed transmissions.

The UL receiving method also includes a step S1120 of generating an indicator indicating a priority level to be enforced, and a step S1130 of comparing the priority level of the first uplink transmission with the indicated priority level to be enforced. The UL transmission method also includes a step S1140 of transmitting a priority level indicator to be enforced, which is received by the UE in a step S1150 of the UL transmission method.

It should be noted that the order of steps of the UL receiving method according to the present invention is not limited to the order shown in FIG. 11. In particular, priority level comparison step S1130 may also be performed before step S1110 or before step 1120.

Moreover, in addition to an indication of the priority level to be enforced, an indicator of resources assigned to the second transmission may be transmitted by base station 810 and received by UE 860. Based on such resource indicator, the UE may determine whether resources assigned to the first transmission and for the second transmission, or determine that the second transmission is assigned resources that overlap with the resources that were assigned to the first transmission, before scheduling the second UL transmission.

When receiving the UL priority indicator, the UE, in step S1160 of the UL transmission method, compares the priority level of the first uplink transmission with the indicated priority level to be enforced in accordance with step S1130 performed by the base station or the like.

In step S1170 of the UL transmission method, the first uplink transmission is performed based on the result of step S1160, and if the first UL transmission occurs, the base station receives it in step S1180 in addition to the second uplink transmission.

If the priority comparison determines that both the first UL transmission and the second UL transmission should be performed, a situation may arise where, due to overlap, the first uplink transmission receives few or very few resources than previously allocated. In this case, the base station may automatically reschedule the first uplink transmission. For example, a priority level indicator to be enforced in connection with a possible indicator assigned to a second uplink transmission may be interpreted by the UE to imply that overlapping resources have been reassigned or reallocated in some previously agreed upon manner by the UE 860 and the base station 810. For example, resource elements common to both transmissions may be divided equally between the first UL transmission and the second UL transmission, or weighted, for example, depending on whether the priority level of the first UL transmission is equal to or higher than the priority level subject to forced application.

Alternatively, resource overlap of a certain type can be resolved by using resources of a different type. For example, in an overlapping area where the time and frequency resources of different transmissions are the same, space division multiplexing such as MU-MIMO (multi-user multiple-input multiple-output) technology can be used.

As already mentioned, the present invention is applicable to cases of resource overlap with prioritization of transmissions between different UEs and the same UE. As an example of the case of prioritizing transmissions between different UEs in FIG. 12 shows an assignment of scheduled resources similar to that shown in FIG. 7. As mentioned above, it is again assumed that the transmission scheduled for UE3 is a URLLC uplink transmission and the transmission scheduled for UE2 is an eMBB uplink transmission. In accordance with the present invention, the UE3 does not need to transmit URLLC on the uplink since it has a sufficiently high priority relative to the specified priority level received in the pointers to determine execution or cancellation.

As another example of the case of prioritizing transmissions between different UEs, it is assumed that the priority is indicated by certain priority elements, which are described below. For example, the first user equipment UE1 is already scheduled for priority level 1 UL transmission, the second user equipment UE2 is already scheduled for priority level 4 UL transmission, and the third user equipment UE3 is already scheduled for priority level 2 UL transmission. Later, for the fourth user equipment, UE4 is scheduled to transmit UL with priority level 1 using resources that overlap with some resources of each of UE1, UE2 and UE3. Then, based on the priority level comparison, only UE2 and UE3's transmissions are canceled because they have a priority level that is lower than the priority level of UE4's later scheduled transmissions, i.e., UE1 and UE4 may be multiplexed using overlapping resources.

The methods proposed in the present invention facilitate cancellation of only lower priority UL traffic, while high priority UL traffic (eg, URLLC) can still be implemented and satisfy its high latency constraints.

In addition, according to the previously discussed cancellation mechanism (steps 1-3), transmission is canceled not only on overlapping resources, but also on subsequent symbols after the overlap, or on non-overlapping frequency resources where overlap occurs on other frequency resources in the same symbol, if any. , which may be resource inefficient, and such inefficiency can be mitigated by the methods of the present invention for at least UEs capable of or designed to perform high priority uplink transmissions.

An indicator indicating the priority level to be enforced is control information related to traffic types (eg, transmission types differing in priority) or priority levels. That is, according to the present invention, the UE receives control information related to priority levels (eg, traffic types, transmission types, or an explicitly specified priority level indicator) to be enforced on overlapping resources, and performs or cancels uplink transmission, namely the above-mentioned first uplink transmission based on the control information.

In some implementations, an indicator indicating the priority level to be enforced is included in group-wide (GC) downlink control information (DCI) common to multiple groups of UEs configured to monitor the DCI GC, or typically monitored by multiple groups of UEs configured to monitor the DCI GC. GC DCI monitoring capability.

The base station 810 transmitting group-wide DCI transmits control information including an indicator of the priority level to be enforced.

Except for the GC DCI used in steps 1 and 3 of the cancellation mechanism described above, the GC DCI in accordance with the present invention includes, for example, as two or three or more additional bits, an indicator of the priority level to be enforced. In addition, the DCI GC may include an indicator of resources allocated for the second uplink transmission, similar to the DCI GC of the cancellation mechanism described above.

Accordingly, the UE 860 must be configured to monitor the group-wide DCI to determine possible overlap of already granted resources. UEs in accordance with the present invention, for example, may include NR network release 16 and later release UEs configured to monitor the above-mentioned group-wide DCI.

For example, UE circuitry 880 operates by comparing the index of the priority level of the first uplink transmission or transmission type representing the priority level of the first uplink transmission with the specified priority level to be enforced.

Examples of how or where said index is transmitted from base station 810 to UE 860 will be presented in several embodiments described below. Moreover, with respect to the priority level indicator to be enforced, as also described below and given as an example, the priority level index corresponds to the above-mentioned direct or explicit mapping between the numeric value and the priority level, while the transmission type index representing the priority level , corresponds to an indirect or implicit mapping.

In some implementations, the mapping of a plurality of indexes for a plurality of transmission types, including a first uplink transmission type, is specific to a UE or to a subset of a plurality of UEs receiving the indicated index.

A set of UEs refers to a group of UEs configured to receive a priority level indicator to be enforced, for example, by monitoring a DCI GC. Accordingly, when transmission types (or traffic types or channel types) to be enforced or canceled differ between UEs, when each UE or each subset of UEs is specifically configured (for example, by RRC), the value broadcast from the indicator corresponds to the traffic type. channel or transmission subject to enforcement.

Accordingly, depending on how a UE is configured among the UEs receiving (eg, via broadcast or GC DCI) the priority level indicator to be enforced, the indicator may indicate different types of transmission or channel for different UEs in the specified group of UEs. Here, different UEs can be classified according to the UE class, the type of traffic/transmissions to be transmitted or performed. For example, the mapping of indices to transmission types may be configured differently for a public safety UE than for other UEs. Other differences may include distinguishing UEs capable of carrying URLLC traffic from UEs not capable of carrying URLLC traffic.

For example, using Radio Resource Control (RRC) signaling information, base station 810 semi-statically configures a UE-specific or UE-specific table in which each row contains an index and each index indicates a particular transmission type. For example, the transmission type may include a combination of channel, signal type, and latency-related use case.

Examples of configuration tables for various UEs are shown in Table 1 and Table 2.

Table 1 Configuration table for public safety UE Index Traffic type/channels/UCI for public safety UE 0 RRC, HARQ-ACK (URLLC) 1 URLLC and higher (PUSCH/HARQ-ACK/SR) 2 eMBB (PUSCH/HARQ-ACK/SR) 3 None

Table 2 Configuration table for non-public safety UEs Index Traffic type/channels/UCI for regular UE 0 None 1 RRC, HARQ-ACK (URLLC) 2 URLLC and higher (PUSCH/HARQ-ACK/SR) 3 eMBB and higher (PUSCH/HARQ-ACK/SR)

When the UE is configured with one of the above mappings shown in Table 1 and Table 2, the UE's MAC layer may inform the UE's Physical layer (PHY) of its own UL dispatched first transmission type, which is inferred based on identifier priority. logical channel or associated with the priority of the logical channel identifier to which the transport block (TB) transmitted by the MAC layer to the physical layer (PHY) to perform the first UL transmission is associated.

For example, according to 3GPP TS 38.331 V15.6.0 (2019-06), Radio Resource Control (RRC) Protocol Specification, section 6.3.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 specified transmission types or traffic types specified in the right columns of the tables may be associated with a subset of the given priority levels.

Accordingly, based on the configuration and information from the MAC layer, the physical layer (PHY) of the specified UE can associate a TB for UL PUSCH transmission in the physical layer (PHY) with traffic priority, and therefore each UE (including the UE performing the first UL transmission ) learns about its own traffic priority.

The priority level indicator to be enforced, carried, for example, as a common bit field in the group-wide DCI, points to one of the indexes of the table configured by radio resource control (RRC) to report to each user equipment (for example, each user equipment (UE) that configured to monitor the GC-DCI for enforcement/cancellation) which type of traffic or UL transmission type should be enforced or allowed to be transmitted, and which should be canceled in case of resource overlap.

Since the tables configured by Radio Resource Control (RRC) may differ for different UEs, the actual decisions to cancel/do UL transmissions may differ for different UEs. In the example Tables 1 and 2, if the priority indicator to be enforced in the DCI GC indicates "0", for a public safety UE configured according to Table 1, only RRC and HARQ-ACK messages shall be enforced, but for other user equipment configured according to Table 2 with a GC DCI indicating a value of 0, all types of UL transmissions will be canceled if they are assigned using overlapping resources. In addition, the same transmission type, such as HARQ-NACK in URLLC, can be enforced for different UEs using different numeric designators, for example, "0" for public safety UEs and "1" for other UEs, and, thus, can provide different priority levels for different UEs.

It should be noted that Tables 1 and 2 are for exemplary purposes and there may be many other implementations in terms of UE types such as URLLC, eMBB, Police UE, V2X UE, IoT UE, etc., as well as table size , which may contain as few as two lines or many more than 4 lines. For example, the types of UEs to receive specific tables may be based on the capabilities of the UE and/or the intended type of use or traffic.

A flow diagram of an exemplary method that uses index to transmission type mapping is shown in FIG. 13.

In step S1310, the UE is configured in accordance with a specific table (UE-specific or subgroup-specific from the DCI GC snooping group) in the RRC with two columns for index number and traffic type or transmission type for enforcement or cancellation. Then, 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 this TB based on the priority of the logical channel. In step S1330, the UE receives a group-wide DCI for cancellation or enforcement. If there is overlap, the UE, in step S1340, checks the bit field related to the priority indicator to cancel or enforce, and checks whether the traffic level (transmission type) of the current TB is the same (equal to the priority) or a lower level (corresponding to a higher priority ) than the level indicated in the priority indicators from the GC DCI information indicating one of the indexes of the table configured by radio resource management (corresponding to the transmission type). If yes, the UE continues to perform or performs a scheduled transmission (first uplink transmission) in step S1350. If not, the UE performs transmission cancellation in step S1360.

As stated above, the configuration may include a different mapping for different UEs, and the indices are mapped to transmission types.

However, in some embodiments, the mapping of a plurality of indices to a plurality of priority levels, including a first uplink transmission priority level and a second uplink transmission priority level, is common to a plurality of UEs receiving the indicated indicator.

Accordingly, the types of transmissions (eg, traffic types or channel types) that need to be canceled in overlapping resources may be the same among UEs that have received such control information.

When the mapping of indexes to priority levels is common to UEs, the RRC configuration of such mapping does not need to be UE specific (or specific to UE types or classes), and hence the resource overhead associated with RRC can be reduced.

In embodiments using Tables 1 and 2, the priority level to be enforced is indicated indirectly by indicating the transmission types associated with the priority levels. Some implementations described below use a direct mapping between pointers or indices and priority levels.

For example, in a common mapping for multiple UEs, eg, UEs monitoring a group-wide DCI, each index may be mapped to a priority level in a one-to-one correspondence.

Accordingly, when the traffic/channel types to be canceled in overlapping resources are the same among UEs, when all UEs are configured to be in common use (eg, via RRC) using information such as a priority level indicator to be enforced, each value broadcast may correspond to a certain priority level that is allowed for transmission.

An example of a mapping table common to all UEs monitoring DCI GC information, which again can be semi-statically configured by RRC, where each row consists of an index and each index indicates a priority level (corresponding to absolute priority levels in the MAC), is presented as Tables 3.

Table 3 Correspondence between indexes and priority levels Index Priority level 0 1 1 2 2 3 ….. ….. 20 21

If a mapping such as Table 3 is provided, the UE's MAC layer is able to inform the UE's physical layer (PHY) of an absolute priority level that applies to all channels and transmission types of all UEs. Accordingly, absolute priority levels common to all UL transmissions are assumed. Based on this, each UL transmission can be associated with an absolute priority at the physical layer (PHY).

For example, the number of priority levels that may be associated with logical channels in the MAC layer may be 16, as mentioned above, but may also be more or less. For example, as shown in FIG. 3, the number of priority levels of logical channels can be increased to a larger number based on absolute priorities defined at a higher layer (eg, higher than the MAC layer).

Accordingly, the priority level indicator to be enforced, such as a common bit field in the DCI GC, may point to index 1 of the specified table, which may be configured by RRC, to be reported to all UEs receiving the lowest priority level indicator to be enforced. All lower priority levels (corresponding to higher indexes) must be overridden.

In the example of Table 3, if the DCI GC indicates 2, transmissions of all UEs that have a scheduled or ongoing UL transmission with a priority level below 3 (i.e. 4, 5, 6, and so on) are canceled, and only priority levels 1. 2 and 3 will be allowed to continue scheduled transmission.

In some implementations, when mapping indexes to a plurality of priority levels, each index is mapped to a range of priority levels.

For example, when the priority levels or transmission types (or traffic types or channels) to be canceled or enforced are the same (common or configured to be in common use, e.g., via RRC) for UEs receiving the transmitted priority level indicator, each value The circularly transmitted pointer may correspond to a particular group of priorities that are allowed or enforced for transmission.

For example, a table is configured (eg, semi-statically via RRC) in which each index indicates a group, such as a range, of priority levels common to all UEs. An example mapping of indexes to groups or ranges is given in Table 4.

Table 4 Correspondence between indices and priority level ranges Index Priority level 0 1-5 1 1-10 2 1-15 3 1-21

Similar to embodiments that use the above-described one-to-one mapping shown in Table 3, the MAC layer of the UE may inform the physical layer (PHY) of the UE about the priority level associated with the transport block for the scheduled transmission. In a group-wide DCI for enforcement or override, the common bit field may point to one of the indexes of the configured table to inform each UE of the range of allowed priority levels to be enforced on overlapping resources. Transmissions of all lower priority levels that are mapped to an index higher than that specified must be cancelled.

When a mapping to ranges of priority levels is used, rather than a one-to-one mapping of indexes to priority levels, a coarse priority indicator can help reduce the resource overhead associated with DCI.

As an example using Table 4, if the group-wide GC DCI information indicates "2", then all UEs that have a scheduled or ongoing UL transmission with a priority level below 15 (for example, with levels ranging from 16 to 21 inclusive, if the absolute number certain priority levels is 21) are overridden and only scheduled UL transmission with the higher priority from priority levels 1-15 will be allowed to continue.

Additionally, it should be noted that the number of rows corresponding to priority levels in the configured table may be less than the examples shown in Tables 1-5. For example, in some scenarios, two priority levels may be sufficient, such as the first priority level for URLLC traffic and the second priority level for eMBB traffic.

A flow diagram of an exemplary method that uses mapping of indices to priority levels or ranges of priority levels is shown in FIG. 14.

In step S1410, the UE is configured using a specific table (UE specific or subgroup specific of a group tracking GC DCI information) in the RRC with two columns for index number and priority level or group/range for enforcement or cancellation. Then, in step S1420, the MAC layer of the UE sends the TB for UL transmission (the above-mentioned “first” UL transmission) and associates a priority level or range of priority levels with the TB based on the priority of the logical channel. In step S1430, the UE receives a group-wide DCI for cancellation or enforcement. If there is overlap, the UE in step S1440 checks the bit field related to the priority indicator to cancel or enforce, and checks whether the priority level or range of priority levels of the current TB is the same (equal to the priority) or a lower level (corresponding to a higher priority) than the priority indicator from the GC DCI information indicating one of the indexes of the table configured by radio resource control (RRC). If yes, the UE continues or performs a scheduled transmission (first uplink transmission) in step S1450. If not, the UE performs transmission cancellation in step S1460.

In some implementations, as also mentioned in some of the examples described above, the mapping of multiple indices (directly) to priority levels, ranges of priority levels, or transmission types associated with priority levels is configured via RRC signaling information. However, the present invention also provides methods for indicating priority without using RRC.

In some implementations, 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, instead of referring to the RRC configuration, the priority level indicator to be enforced may indicate a mapping negotiated between the UE 860 and the base station 810 in accordance with the standard. For example, the total number of priority levels could be one of the examples mentioned above: 16 levels (as in 3GPP TS 38.331 V15.6.0), 21 levels, 2 levels (URLLC, eMBB) or some other value.

For example, when the priority levels or transmission types (or traffic types or channels) to be canceled or enforced are the same for all UEs to which the specified priority level indicator is broadcast, each value of the circularly transmitted indicator may correspond to a specific priority level that is allowed or forced to transfer.

For example, the UE's MAC layer may inform the UE's physical layer (PHY) of its own current scheduled traffic type, which is obtained based on the priority of the logical channel identifier. Based on the mapping according to the standard, the TB for uplink transmission of the UL PUSCH on the physical layer (PHY) can be associated with a traffic priority (layer out of a total number of defined layers, e.g. 2, 16, 21), and therefore each UE is notified about your own traffic priority. The priority may be related to traffic types as well as channels or signals such as SRS/PRACH/CSI/HARQ-ACK (Sounding Reference Signal/Physical Random Access Channel/Channel State Information/Hybrid Automatic Repeat Request Acknowledgment).

An enforceable priority indicator, such as a bit field in the GC-DCI, indicates an absolute priority level for communicating to all UEs that if their current or scheduled UL transmissions have a lower priority than a specified value, those UL transmissions shall be canceled, otherwise the UE shall continue to transmit UL. For example, if the DCI GC indicates 5, all UEs that have an ongoing or scheduled UL transmission will have to cancel if their corresponding priority is below 5 (ie, 6, 7, and so on).

By directly using the standard priority level configuration instead of the RRC configuration, the use of RRC can be avoided. On the other hand, if the absolute number of priorities is specified, which may be large, an implementation option using a semi-static configuration may be able to reduce the resource overhead associated with DCI.

A flow diagram of an exemplary method that uses index to transmission type mapping is shown in FIG. 14. Steps S1520 to S1560 are the same as steps S1420 to S1460 shown in FIG. 14. However, the enforceable priority indicator points to the standard configured absolute priority level and not to the semi-statically configured RRC mapping of indexes and priority levels or ranges/groups.

The priority level can be determined by the type of transmission. Accordingly, as already mentioned, different priority levels may be assigned to different types of transmission. For example, the priority level indicator to be enforced may indicate a mapping of indices to transmission types or a mapping of indices to priority levels. However, in both cases priority levels can be assigned to transmission types. Accordingly, the priority level can be determined by the type of transmission.

Examples of transmission types include channel type (eg, PUSCH (Physical Uplink Shared Channel), PRACH), transmission type (SRS, HARQ-ACK), or service request. The service request may be based, for example, on a use case including URLLC, eMBB, mMTC, or public safety in which a scheduled uplink transmission occurs.

As already mentioned, the implementations disclosed herein are applicable to priority-based UL transmission cancellation enforcement/UL transmission priority enforcement based on the priority indicator and information passed from the MAC layer to the physical layer (PHY) in the case of prioritization of transmissions between different UEs. However, if a priority is associated with each UL channel/UL signal for a given UE, information about such association can also be used to prioritize/multiplex or defer transmissions in case of prioritizing transmissions of the same UE.

Some use cases for prioritization/multiplexing in case of prioritizing transmissions between different UEs are discussed below:

- The high-priority grant-based PUSCH is scheduled and the low-priority grant-based PUSCH is cancelled;

- The high-priority grant-based PUSCH is dispatched and the low-priority grant-configured PUSCH is cancelled;

- The high-priority grant-based PUSCH is dispatched and the low-priority PRACH is cancelled;

- The high priority grant-based PUSCH is dispatched and the low priority SRS is cancelled;

- The high-priority grant-based PUSCH is dispatched and the low-priority PUCCH is cancelled.

In case of prioritization of transmissions of the same UE, different UL/UCI channels of the same UE with different/same priorities may have overlapping resources, and the priority indicator passed from the MAC layer to the physical layer (PHY) may be used for their cancellation or multiplexing.

Additionally, in some embodiments, UE circuitry 880 includes physical layer circuitry that, in operation, receives information indicating the priority level of the first uplink transmission from the Medium Access Control layer. As mentioned, for example, in the context of FIG. 13-15 The TV MAC layer of the UE may inform the UE Physical Layer (UE PHY) circuitry of the priority level associated with the transport block for a scheduled transmission so that the UE Physical Layer (PHY) is aware that , what priority is associated with the transfer to be performed.

The present invention may be implemented by software, hardware, or software in conjunction with hardware. Each of the functional blocks used in the description of each of the above-described embodiments may be partially or completely implemented by a large integrated circuit (LSI), such as an integrated circuit, and each of the processes described in each of the embodiments may be partially or completely controlled one LSI or a combination of LSIs. LSIs may be individually implemented as chips, or a single chip may be configured to contain some or all of the functional blocks. The LSI may include input and output of data related to it. The LSI in this case may be called an integrated circuit (IC), system LSI, very large-scale IC (VLSI), or ultra-large-scale IC (ULSI), depending on the difference in the degree of integration. However, the implementation method of an integrated circuit is not limited to an LSI circuit and may be implemented using a dedicated circuit, a general purpose processor or a special purpose processor. Additionally, a field programmable gate array (FPGA) can be used, which can be programmed after the LSI is manufactured, or a reconfigurable processor, in which the connections and settings of the circuit elements located in the LSI can be reconfigured. The present invention may be implemented as digital processing or analog processing. If the latest integrated circuit technology replaces modern LSIs as a result of the development of semiconductor technology or other technology derived from it, the functional blocks can be embedded using the specified latest integrated circuit technology. Biotechnology can also be used.

The present disclosure may be implemented by any type of equipment, device, or system having a communication function implemented by a communication device.

Some non-limiting examples of such a communication device include a telephone (e.g., cell phone, smartphone), tablet, personal computer (PC) (e.g., laptop, desktop, netbook), camera (e.g., digital photo/video camera). camera), digital player (digital audio/video player), wearable device (e.g. wearable camera, smart watch, tracking device), game console, digital book reader, telemedicine device/telemedicine device ( remote health and medicine) and a vehicle with communication functions (for example, a car, an airplane, a ship), as well as their various combinations.

Said communication device is not limited to a portable or movable communication device and may also include any type of equipment, device or system that is non-portable or stationary, such as a smart home device (e.g., appliance, lighting, smart meter, control panel), a vending machine and any other “things” in the Internet of Things (IoT) network.

Communication may include data exchange, for example, through a cellular communication system, a wireless network (LAN) system, a satellite communication system, etc., as well as various combinations thereof.

The communication device may include a device, such as a controller or sensor, that is coupled to the communication device that performs the communication function described in the present disclosure. For example, a communication device may include a controller or sensor that generates control signals or data signals that are used by a communication device performing a communication function of the communication device.

A communications device may also include an infrastructure entity such as a base station, an access point, and any other equipment, device, or system that communicates with or controls the devices, such as in the above non-limiting examples.

A user equipment (UE) is provided comprising a transceiver that operatively receives an indicator indicating a priority level to be enforced, and circuitry that operatively compares the priority level of a first uplink transmission with an indicated priority level to be enforced, wherein the first transmission uplink is enabled by the UE prior to scheduling a second uplink transmission that is assigned resources overlapping with resources assigned to the first uplink transmission, wherein the transceiver operatively performs the first uplink transmission based on the result of the comparison.

In some embodiments, the transceiver operatively receives group-wide downlink control information common to multiple UEs, including an indicator indicating the priority level to be enforced.

For example, the circuit in operation compares the index of the priority level of the first uplink transmission or transmission type representing the priority level of the first uplink transmission with the specified priority level to be enforced.

In some embodiments, the mapping of a plurality of indices to a plurality of transmission types, including a first uplink transmission type, is specific to a UE or to a subset of UEs receiving the indicated index, wherein said subset includes the specified UE.

In some implementations, the mapping of a plurality of indices to a plurality of priority levels, including a first uplink transmission priority level and a second uplink transmission priority level, is common to all UEs receiving the indicated indicator.

For example, when mapping multiple indexes to multiple priority levels, each index is mapped to a priority level in a one-to-one correspondence.

In some implementations, when mapping indexes to a plurality of priority levels, each index is mapped to a range of priority levels.

For example, the mapping of a plurality of indexes is configured by radio resource management signaling information.

For example, the mapping of multiple indexes to multiple priority levels is based on the total number of priority levels defined by the standard.

For example, the priority level is determined by the type of transmission.

For example, the transmission type includes at least one of the following: channel type; the type of information to be transmitted; or service request.

In some embodiments, the circuit includes physical layer circuitry that, in operation, receives information from the Medium Access Control layer indicating the priority level of the first uplink transmission.

In addition, a base station is provided comprising circuitry that, when operative, permits a first uplink transmission prior to scheduling a second uplink transmission that is assigned resources overlapping with resources assigned to the first uplink transmission, generating an indicator indicating the priority level to be to be enforced, and compares the priority level of the first uplink transmission with the specified priority level to be enforced, and the transceiver, which, in operation, transmits an indicator and receives the first uplink transmission based on the result of the comparison.

In some embodiments, the transceiver, in operation, transmits group-wide downlink control information common to multiple UEs, including an indicator indicating the priority level to be enforced.

For example, the circuit in operation compares the index of the priority level of the first uplink transmission or transmission type representing the priority level of the first uplink transmission with the specified priority level to be enforced.

In some embodiments, the mapping of a plurality of indices to a plurality of transmission types, including a first uplink transmission type, is specific to a UE or to a subset of UEs receiving the indicated index, wherein said subset includes the specified UE.

In some implementations, the mapping of a plurality of indices to a plurality of priority levels, including a first uplink transmission priority level and a second uplink transmission priority level, is common to all UEs receiving the indicated indicator.

For example, when mapping multiple indexes to multiple priority levels, each index is mapped to a priority level in a one-to-one correspondence.

In some implementations, when mapping indexes to a plurality of priority levels, each index is mapped to a range of priority levels.

For example, the mapping of a plurality of indexes is configured by radio resource management signaling information.

For example, the mapping of multiple indexes to multiple priority levels is based on the total number of priority levels defined by the standard.

For example, the priority level is determined by the type of transmission.

For example, the transmission type includes at least one of the following: channel type; the type of information to be transmitted; or service request.

Also provided is an uplink (UL) transmission method comprising receiving an indicator indicating a priority level to be enforced, comparing the priority level of a first uplink transmission with the indicated priority level to be enforced, wherein the first uplink transmission is allowed before the second is dispatched. an uplink transmission to which resources are assigned overlapping with those assigned to the first uplink transmission, and performing the first uplink transmission based on the comparison result.

In some embodiments, a UL transmission method includes receiving group-wide downlink control information common to multiple UEs including an indicator indicating a priority level to be enforced.

For example, the UL transmission method includes comparing a priority level index of the first uplink transmission or a transmission type representing the priority level of the first uplink transmission with a specified priority level to be enforced.

In some embodiments, the mapping of a plurality of indices to a plurality of transmission types, including a first uplink transmission type, is specific to a UE or to a subset of a plurality of UEs receiving the specified index, wherein the subset includes the specified UE.

In some implementations, the mapping of a plurality of indices to a plurality of priority levels, including a first uplink transmission priority level and a second uplink transmission priority level, is common to all UEs receiving the indicated indicator.

For example, when mapping multiple indexes to multiple priority levels, each index is mapped to a priority level in a one-to-one correspondence.

In some implementations, when mapping indexes to a plurality of priority levels, each index is mapped to a range of priority levels.

For example, the mapping of a plurality of indexes is configured by radio resource management signaling information.

For example, the mapping of multiple indexes to multiple priority levels is based on the total number of priority levels defined by the standard.

For example, the priority level is determined by the type of transmission.

For example, the transmission type includes at least one of the following: channel type; the type of information to be transmitted; or service request.

In some embodiments, the method includes obtaining, at the physical layer, from the medium access control layer, information indicating the priority level of the first uplink transmission.

Also provided is a method for receiving an uplink, including allowing a first uplink transmission before scheduling a second uplink transmission that is assigned resources overlapping with resources assigned to the first uplink transmission, generating an indicator indicating a priority level to be enforced, comparing the level priority of the first uplink transmission with the specified priority level to be enforced, transmitting the specified indicator, and performing reception of the first uplink transmission based on the comparison result.

In some embodiments, a method of receiving UL includes transmitting group-wide downlink control information common to multiple UEs including an indicator indicating a priority level to be enforced.

For example, a UL receiving method includes comparing a priority level index of a first uplink transmission or a transmission type representing a priority level of a first uplink transmission with a specified priority level to be enforced.

In some embodiments, the mapping of a plurality of indices to a plurality of transmission types, including a first uplink transmission type, is specific to a UE or to a subset of a plurality of UEs receiving the specified index, wherein the subset includes the specified UE.

In some implementations, the mapping of a plurality of indices to a plurality of priority levels, including a first uplink transmission priority level and a second uplink transmission priority level, is common to all UEs receiving the indicated indicator.

For example, when mapping multiple indexes to multiple priority levels, each index is mapped to a priority level in a one-to-one correspondence.

In some implementations, when mapping indexes to a plurality of priority levels, each index is mapped to a range of priority levels.

For example, the mapping of a plurality of indexes is configured by radio resource management signaling information.

For example, the mapping of multiple indexes to multiple priority levels is based on the total number of priority levels defined by the standard.

For example, the priority level is determined by the type of transmission.

For example, the transmission type includes at least one of the following: channel type; the type of information to be transmitted; or service request.

Also provided is an object (eg, AMF/SMF, etc.) of a 5th Generation Core (5GC) comprising: a control circuit that, when operative, establishes a Next Generation (NG) connection with the gNodeB; and a transmitter that, in operation, transmits a context initialization setup message via an NG connection to the gNodeB to cause radio signaling information bearer setup between the gNodeB and the user equipment (UE); wherein the gNodeB transmits radio resource control (RRC) signaling information containing a resource assignment configuration information element to the UE via a radio signaling information bearer, and the UE operatively receives an indicator indicating the priority level to be enforced, compares the priority level of the first uplink transmission with a specified priority level to be enforced, wherein the first uplink transmission is allowed by the UE before scheduling a second uplink transmission that is assigned resources overlapping with the resources assigned to the first uplink transmission, and performs the first uplink transmission based on the result of the comparison and based on resource assignment configuration.

In some embodiments, the gNodeB to the UE transmits group-wide downlink control information common to multiple UEs, including an indicator indicating the priority level to be enforced.

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

In some embodiments, the mapping of a plurality of indices to a plurality of transmission types, including a first uplink transmission type, is specific to a UE or to a subset of UEs receiving the indicated index, wherein the subset includes the specified UE.

In some implementations, the mapping of a plurality of indices to a plurality of priority levels, including a first uplink transmission priority level and a second uplink transmission priority level, is common to all UEs receiving the indicated indicator.

For example, when mapping multiple indexes to multiple priority levels, each index is mapped to a priority level in a one-to-one correspondence.

In some implementations, when mapping indexes to a plurality of priority levels, each index is mapped to a range of priority levels.

For example, the mapping of a plurality of indexes is configured by radio resource management signaling information.

For example, the mapping of multiple indexes to multiple priority levels is based on the total number of priority levels defined by the standard.

For example, the priority level is determined by the type of transmission.

For example, the transmission type includes at least one of the following: channel type; the type of information to be transmitted; or service request.

In some implementations, the UE includes physical layer circuitry that, in operation, receives from the medium access control layer information indicating the priority level of the first uplink transmission.

In summary, the present invention relates to user equipment, a base station, and methods for uplink transmission and reception. The user equipment includes a transceiver that operatively receives an indicator indicating a priority level to be enforced, and circuitry that operatively compares the priority level of the first uplink transmission with the indicated priority level to be enforced, wherein the first uplink transmission is enabled by the UE before scheduling a second uplink transmission that is assigned resources overlapping with resources assigned to the first uplink transmission, wherein the transceiver operatively performs the first uplink transmission based on the result of the comparison.

Claims (38)

1 User equipment (UE) containing: a transceiver that, in operation, receives an indicator indicating a priority level to be enforced; And a circuit that, in operation, compares the priority level of a first uplink transmission with a specified priority level to be enforced, wherein the first uplink transmission is allowed by the UE prior to scheduling a second uplink transmission assigned to resources overlapping with resources assigned to the first uplink transmission channel, wherein in operation, the transceiver performs a first uplink transmission based on the comparison result. 2. The user equipment (UE) of claim 1, wherein the transceiver operatively receives group-wide downlink control information common to a plurality of UEs, including an indicator indicating a priority level to be enforced. 3. User equipment (UE) according to claim 1 or 2, in which the specified circuit, when operating, compares the priority level index of the first uplink transmission or transmission type representing the priority level of the first uplink transmission, with the specified priority level to be enforced. 4. User equipment (UE) according to any one of paragraphs. 1-3, wherein the mapping of a plurality of indices to a plurality of transmission types, including a first uplink transmission type, is specific to a UE or to a subset of UEs receiving said index, wherein said subset includes said UE. 5. The user equipment (UE) of claim 1 or 3, wherein the mapping of the plurality of indices to the plurality of priority levels including a first uplink transmission priority level and a second uplink transmission priority level is common to UEs receiving said indicator. 6. The user equipment (UE) of claim 5, wherein when mapping a plurality of indices to a plurality of priority levels, each index is mapped to a priority level in a one-to-one correspondence. 7. The user equipment (UE) of claim 5, wherein, by mapping a plurality of indexes to a plurality of priority levels, each index is mapped to a range of priority levels. 8. User equipment (UE) according to any one of paragraphs. 4-7, in which a plurality of index mappings are configured by radio resource control signaling information. 9. User equipment (UE) according to any one of paragraphs. 5-7, wherein the mapping of a plurality of indexes to a plurality of priority levels is based on the total number of priority levels defined by the standard. 10. User equipment (UE) according to any one of paragraphs. 4-9, in which the priority level is determined by the transmission type. 11. The user equipment (UE) of claim 3 or 9, wherein the transmission type includes at least one of the following: a channel type; the type of information to be transmitted or service request. 12. The user equipment (UE) of claim 1 or 2, wherein the circuit comprises physical layer circuitry that operatively receives from the media access control layer information indicating a priority level of the first uplink transmission. 13. Base station containing: a circuit that, in operation, permits a first uplink transmission before dispatching a second uplink transmission assigned to resources overlapping with resources assigned to the first uplink transmission, generates an indicator indicating the priority level to be enforced, and compares the priority level of the first transmission on an uplink with a specified priority level to be enforced; And a transceiver that operatively transmits a specified indicator and performs reception of a first uplink transmission based on the result of the comparison. 14. An uplink transmission method comprising: receiving an indicator indicating a priority level to be enforced; comparing a priority level of the first uplink transmission with a specified priority level to be enforced, wherein the first uplink transmission is allowed before scheduling a second uplink transmission assigned to resources overlapping with resources assigned to the first uplink transmission; And performing the first uplink transmission based on the comparison result. 15. A method for receiving an uplink channel, including: allowing the first uplink transmission before scheduling a second uplink transmission assigned to resources overlapping with the resources assigned to the first uplink transmission; generating an indicator indicating the priority level to be enforced; comparing the priority level of the first uplink transmission with the specified priority level to be enforced; passing a pointer and performing reception of the first uplink transmission based on the comparison result. 16. An integrated circuit that, in operation, controls the uplink transmission process of a user equipment, the process including: receiving an indicator indicating a priority level to be enforced; comparing a priority level of the first uplink transmission with a specified priority level to be enforced, wherein the first uplink transmission is allowed before scheduling a second uplink transmission assigned to resources overlapping with resources assigned to the first uplink transmission; And performing the first uplink transmission based on the comparison result. 17. An integrated circuit that, in operation, controls the process of receiving a base station uplink, the process including: allowing the first uplink transmission before scheduling a second uplink transmission assigned to resources overlapping with the resources assigned to the first uplink transmission; generating an indicator indicating the priority level to be enforced; comparing the priority level of the first uplink transmission with the specified priority level to be enforced; passing a pointer and performing reception of the first uplink transmission based on the comparison result.