Logical channel prioritization mechanism

Abstract

The application relates to devices and components, including apparatuses, systems, and methods for performing a logical channel prioritization (LCP) process based on dynamic information of a logical channel (LCH).

Description

Technical Field

[0001] This application relates generally to cellular communication networks, and more specifically to techniques for logical channel priority ordering. Background Technology

[0002] Extended Reality (XR) is a workload that can be supported by cellular wireless networks. The goal is to improve the capacity of XR-specific traffic through more efficient resource allocation and to improve quality of service by applying more granular quality of service controls. Attached Figure Description

[0003] Figure 1 Examples of network environments based on some implementation schemes are provided.

[0004] Figure 2 The operational flow / algorithm structure according to some implementation schemes is illustrated.

[0005] Figure 3 The operational flow / algorithm structure according to some implementation schemes is illustrated.

[0006] Figure 4 The operational flow / algorithm structure according to some implementation schemes is illustrated.

[0007] Figure 5 The operational flow / algorithm structure according to some implementation schemes is illustrated.

[0008] Figure 6 The operational flow / algorithm structure according to some implementation schemes is illustrated.

[0009] Figure 7 The operational flow / algorithm structure according to some implementation schemes is illustrated.

[0010] Figure 8 The operational flow / algorithm structure according to some implementation schemes is illustrated.

[0011] Figure 9 Examples of user equipment according to some implementation schemes are shown.

[0012] Figure 10 Examples of network nodes according to some implementation schemes are shown. Detailed Implementation

[0013] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as particular structures, architectures, interfaces, and / or technologies, are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of some embodiments. However, it will be apparent to those skilled in the art that various aspects may be practiced in other examples departing from these specific details. In some instances, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of various aspects with unnecessary detail. For the purposes of this document, the phrase “A or B” means (A), (B), or (A and B), and the phrase “based on A” means “at least partially based on A,” for example, it can be “based solely on A” or it can be “partially based on A.”

[0014] The following is a glossary of terms that may be used in this disclosure.

[0015] As used herein, the term "circuit" means, is part of, or includes hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-chips (SoCs)), and / or digital signal processors (DSPs) configured to provide the described functionality. In some aspects, a circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and program code for executing the functionality of that program code. In these aspects, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0016] As used herein, the term "processor circuit" means, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations; or recording, storing, or transmitting digital data. The term "processor circuit" can also refer to an application processor; a baseband processor; a central processing unit (CPU); a graphics processing unit; a single-core processor; a dual-core processor; a triple-core processor; a quad-core processor; or any other device capable of executing or otherwise operating computer-executable instructions (such as program code); a software module; or a functional process.

[0017] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces; for example, a bus, I / O interface, peripheral component interface, or network interface card.

[0018] As used herein, the term "User Equipment" or "UE" refers to a device with radio communication capabilities and can describe a remote user of network resources in a communication network. The terms "User Equipment" or "UE" can be considered synonymous and can refer to a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "User Equipment" or "UE" can include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0019] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" can refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" can refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0020] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computer, storage, or network resources provided by physical hardware components. "Virtualized resource" can refer to computer, storage, or network resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that computer devices / systems can access via a communication network. The term "system resource" can refer to any kind of shared entity providing services and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0021] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to transmit data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a means or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices for the purpose of transmitting and receiving information.

[0022] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which can occur, for example, during the execution of program code.

[0023] The term "connection" can refer to an established signaling relationship between two or more elements at a common communication protocol layer through a communication channel, link, interface, or reference point.

[0024] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

[0025] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to a single piece of content within an information element or a data element that contains content. An information element may include one or more additional information elements.

[0026] Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include a UE 104 coupled to a base station (BS) 108 of a radio access network (RAN). In some implementations, the BS 108 is a next-generation node B (gNB) providing one or more 3GPP New Radio (NR) cells. In other implementations, the BS 108 is an evolved Node B (eNB) providing one or more Long Term Evolution (LTE) cells. The air interfaces through which the UE 104 and BS 108 communicate may be compatible with 3GPP Technical Specifications (TS), such as those defining fifth-generation (5G) NR or later system standards (e.g., sixth-generation (6G) standards).

[0027] The network can provide XR or Multimedia (XRM) services to the UE. In XRM services, information generated by the application can be represented by a set of PDUs in a Packet Data Unit (PDU) session. A PDU set consists of one or more PDUs carrying the payload of an information unit generated at the application layer. For example, frames (e.g., I-frames, B-frames, or P-frames) or video slices used for XRM services can form a PDU set. In some instances, the application layer requires all PDUs in the PDU set to retrieve the corresponding information unit. In some cases, the application layer can recover portions of the information unit even if some PDUs are lost. The PDUs in the PDU set for XRM services may contain packets with different latency requirements, importance levels, or typically different Quality of Service (QoS) requirements. In some instances, QoS is applied as a whole to the PDU set; for example, QoS parameter maintenance, retransmission, and QoS scheduling in the MAC are uniformly applied to all packets in the PDU and all PDUs in the PDU set.

[0028] In Layer 2 (L2), application data is assigned to one or more logical channels (LCHs). L2 may include a Media Access (MAC) layer, which is a sublayer of L2 in the 3GPP cellular architecture. Packets with different QoS requirements may be transmitted via the same LCH. For example, XRM traffic may include packets with different QoS requirements served by the same LCH.

[0029] In one example, legacy LTE networks assign priorities to each LCH via dedicated radio resource control (RRC) signaling. During uplink (UL) transmission, the UE scheduler selects an LCH group based on the LCH configuration and priorities set by the RRC signaling and executes a bucket token algorithm. In the bucket token algorithm, each LCH has its own priority bit rate (PBR) B. For example, the PBR of LCH_1 could be B_1, the PBR of LCH_2 could be B_2, and so on. The UE scheduler starts with the LCH with the highest priority and moves down the list of selected LCHs in descending priority order, allocating B_i bits to LCH_i.

[0030] Traffic characteristics of 5G and higher technologies may be more dynamic and include packets with different QoS requirements. For example, XRM packet QoS requirements (e.g., latency requirements or urgency levels for each packet) can change rapidly and dynamically. Changing LCH priority via legacy RRC signaling may not be sufficient to meet the dynamic demands of 5G traffic. It is expected that LCH selection will be performed, and resources will be dynamically allocated to each selected LCH based on its current LCH state (e.g., LCH data buffer state).

[0031] The network scheduler at BS 108 can schedule uplink transmissions at UE 104. UE 104 can report latency and buffer status reports (BSRs) to BS 108 to facilitate UL scheduling. For example, UE 104 can use a buffer status report (BSR) to convey information to BS 108 about data ready to be transmitted at the UE. The network scheduler at BS 108 can use the latency information reported by the UE and BSIs for UL scheduling (e.g., information conveyed by the BSR). For example, BS 108 can schedule urgent packets or data faster than packets with more flexible latency requirements. BS 108 can transmit priority ordering configurations via L1 or L2 signaling (L1 / L2 signaling) to dynamically adjust LCH priorities and LCP (logical channel prioritization) procedures to meet the QoS requirements of UL traffic. The UE performs the LCP procedure and selects LCHs and packets to assemble MAC PDUs based on dynamic L1 / L2 signaling.

[0032] In one implementation, BS 108 can activate dynamic LCP configurations at UE 104. BS 108 configures UE 104 to have a set that includes multiple LCP configurations for a given LCH. An index can identify each LCP configuration in the set. BS 108 can transmit L1 / L2 commands, activating one LCP configuration per LCH. For example, an L1 / L2 command may include an index for identifying the LCH and another index for indicating the active LCP configuration associated with that LCH.

[0033] BS 108 can use UL permission to transmit L1 commands. In one instance, several LCHs (e.g., only one or two LCHs) can be activated via UL permission. BS 108 can use MAC CE to transmit L2 commands. In one instance, MAC CE can activate an LCP configuration from a set of LCPs configured by RRC. In another instance, MAC CE can explicitly provide the LCP configuration of an LCH, for example, setting the priority of the LCH.

[0034] When performing the LCP procedure, UE 104 can apply the LCP configuration for each LCH. If the L1 / L2 command explicitly activates the LCP configuration for the LCH, UE 104 can apply the activated configuration. In one example, UE 104 can ignore any previous LCP configuration (e.g., RRC configuration) and apply and use the explicit configuration based on the L1 / L2 command. However, if the LCH is not explicitly configured with LCP in the L1 / L2 command, UE 104 can select a default LCP configuration, such as the LCP configuration with the highest or lowest index.

[0035] In one example implementation, BS 108 uses RRC signaling to configure UE 104's LCH_1 to have two priorities ( X and Y LCH_1 priority X It has an index with a value of 1 and LCH_1 priority. Y It has an index with a value of 2. BS108 transmits an L2 command to UE104 via MAC CE to activate LCH_1 with a priority index of 2. BS108 can then transmit a UL clearance to UE104 for scheduling uplink transmission. UE104 is based on the priority index. Y The LCP process is executed using LCH_1.

[0036] In one example implementation, BS 108 uses RRC signaling to configure UE 104's LCH_1 to have priority. X BS 108 transmits an L2 command to UE 104 via MAC CE to activate a priority-based system. Y LCH_1. BS 108 can send UL clearance to UE104 for scheduling uplink transmission. UE 104 is based on priority. Y The LCP process is executed using LCH_1.

[0037] In one example implementation, BS 108 uses RRC signaling to configure UE 104's LCH_1 to have two priorities ( X and Y LCH_1 priority X It has an index with a value of 1 and LCH_1 priority. Y It has an index with a value of 2. BS108 can transmit UL permission to UE 104 for scheduling uplink transmission. UL permission can activate LCH_1 with a priority index equal to 2. UE 104 is based on having a priority index. Y The LCP process is executed using LCH_1.

[0038] In one example implementation, BS 108 uses RRC signaling to configure UE 104's LCH_1 to have two priorities ( X and Y LCH_1 priority X It has an index with a value of 1 and LCH_1 priority. Y It has an index with a value of 2. Furthermore, BS 108 can configure UE 104's LCH_1 to have a default priority index of 1. BS 108 can send UL clearances to UE 104 for scheduling uplink transmission. UL clearances do not contain any activation commands for LCH_1. UE 104 is based on a priority index.X The LCP process is executed using LCH_1 (default priority).

[0039] The LCH LCP configuration can include various parameters. For example, the LCP configuration can include the LCH, PBR, or bucket size (referred to as LCH in the 3GPP specification) in relation to the bucket token algorithm. Bj The associated priority. In one instance, RRC configures the LCH with a set of LCP configurations. Each LCP configuration in this set can be a complete configuration that includes all parameters (e.g., priority, PBR, or bucket size). In another instance, RRC configures the LCH with a set of LCP configurations where each LCP configuration includes a subset of parameters (e.g., priority only).

[0040] In one implementation, the network (e.g., BS 108) may provide LCP configuration for the LCH, where the LCP includes an emergency flag. For example, BS 108 may configure UE 104 via RRC signaling, including an LCP configuration for the LCH with an emergency flag. The emergency flag can function similarly to the priority level of the LCH. In one instance, the emergency flag may indicate whether the LCH has data that needs to be sent immediately. In another example, the emergency flag may take several values ​​or levels, each indicating the urgency of the LCH to be scheduled. For example, emergency level 0 may indicate no urgency (non-urgent LCH), and emergency level 2 may indicate a higher urgency than emergency level 1. An LCH with an active emergency flag or an emergency level different from the value associated with no urgency may be referred to as an emergency LCH.

[0041] BS 108 can also configure UE 104 with an emergency LCP configuration via RRC signaling. The emergency LCP configuration can configure all LCP parameters (e.g., LCH priority, PBR, or Bj) or a subset of LCP parameters (e.g., priority).

[0042] In one example, BS 108 can activate the Emergency LCP procedure via L1 / L2 signaling. The Emergency LCP procedure can select only LCHs with the configured emergency flag. The Emergency LCP procedure can also select LCHs with or without the configured emergency flag. However, the LCP procedure can prioritize LCHs with the emergency flag to assemble the MAC PDU.

[0043] In one instance, BS 108 can indicate the emergency level in L1 / L2 signaling. An LCH with an active emergency flag can activate or enable the emergency LCP procedure. For example, BS 108 can indicate the emergency level in the scheduled UL grant. In another instance, the UE can decide to enable the emergency LCP procedure based on its local information or conditions. UE 104 can enable the emergency LCP procedure based on the buffer state parameters of the LCH. For example, UE 104 can compare the delay of packets in the LCH (e.g., average delay) and compare the packet delay to a threshold, and when the packet delay is greater than the threshold, activate the emergency LCP procedure, set the emergency level of the LCH, or activate the emergency flag of the LCH.

[0044] During an emergency LCP procedure, UE 104 may apply an emergency LCP configuration or prioritize emergency LCHs. In one implementation, UE 104 may include only emergency LCHs during the LCP procedure and use emergency LCH data to assemble a MACPDU. In another implementation, UE 104 may determine the allowed set of LCHs based on LCH mapping restrictions and prioritize these LCHs during the LCP procedure based on the emergency flag of the selected LCHs. In yet another implementation, the UE may determine the allowed set of LCHs (the set of LCHs considered by the LCP procedure) based on LCH mapping restrictions and apply the emergency LCP configuration to the LCHs if one is provided. LCH mapping restrictions may be based on legacy implementations, such as those defined in the 3GPP specifications for LTE. While legacy LCH mapping restrictions provide the set of LCHs, updated LCH prioritization provided by emergency flags and dynamic L1 / L2 signaling enables dynamic adjustment of legacy LCP procedures.

[0045] For example, consider UE 104 with three LCHs (LCH_1, LCH_2, and LCH_3). BS 108 can configure CH_1 and LCH_2 to have emergency indications or emergency flags, and LCH_3 to have no emergency indications or flags. BS 108 enables the emergency LCP procedure, or UE 104 enables the emergency LCP procedure based on local conditions. In one example, UE 104 considers only LCH_1 and LCH_2 in the emergency LCP based on the emergency flags configured for LCH_1 and LCH_2. In another example, UE 104 can consider LCH_1, LCH_2, and LCH_3 during the LCP procedure, but prioritize LCH_1 and LCH_2 over LCH_3 based on their configured emergency flags.

[0046] In another example, consider UE 104 with three LCHs (LCH_1, LCH_2, and LCH_3). LCH_1 and LCH_2 are configured with an emergency LCP configuration, while LCH_3 is not. For example, BS 108 can configure LCH_1 and LCH_2 with an emergency LCP configuration via RRC signaling. BS 108 or UE 104 (e.g., based on a condition detected at UE 104) can enable the emergency LCP procedure. In one instance, the LCP procedure can select only LCH_1 and LCH_2 to assemble the MAC PDU based on the emergency LCP configuration of LCH_1 and LCH_2. In another instance, the LCP procedure can select LCH_1, LCH_2, and LCH_3 based on legacy LCH mapping constraints and apply the emergency LCP configuration to LCH_1 and LCH_2. As mentioned above, the LCP configuration can configure the priority of the LCH and other parameters associated with the LCH (such as PBR or bucket token parameter Bj).

[0047] In one implementation, BS 108 may explicitly indicate the permitted set of LCHs. The permitted set of LCHs is the set of LCHs included during the LCP process for assembling the MAC PDU. In one instance, BS 108 may indicate the permitted set of LCHs in an L1 / L2 command. For example, BS 108 may indicate the permitted set of LCHs in a UL grant (e.g., a dynamic grant (DG)).

[0048] In one instance, BS 108 may indicate the allowed set of LCHs in L3 signaling. For example, BS 108 may indicate the allowed set of LCHs in RRC configuration (e.g., permission (CG) for configuration used for UL transmission). BS 108 may transmit L1 commands (e.g., downlink control information (DCI)) to activate or deactivate the CG. UE 104 may apply the indicated set of LCHs to all active CG times. Alternatively, UE 104 may apply the indicated set of LCHs to a subset of CG times during the LCP procedure. The subset of CG times may be configured by BS 108 or based on predefined rules, for example, during the first CG time or before. K At each CG timing point, the indicated LCH set is applied to the LCP process.

[0049] In another implementation, BS 108 may explicitly indicate a prohibited (e.g., disallowed or restricted) set of LCHs. The prohibited set of LCHs is the set of LCHs excluded from the assembled MAC PDU during the LCP procedure. In one instance, BS 108 may indicate a permitted set of LCHs in an L1 / L2 command. For example, BS 108 may indicate a prohibited set of LCHs in a UL grant (e.g., dynamic grant (DG)). UE 104 may exclude LCHs from the prohibited set during the LCP procedure.

[0050] In one instance, BS 108 may indicate the prohibited set of LCHs in L3 signaling. For example, BS 108 may indicate the prohibited set of LCHs in RRC configuration (e.g., permission (CG) for configuration used for UL transmission). BS 108 may transmit L1 commands (e.g., downlink control information (DCI)) to activate or deactivate the CG. UE 104 may apply the indicated set of LCHs to all active CG times. Alternatively, UE 104 may apply the indicated set of LCHs to a subset of CG times during the LCP procedure. The subset of CG times may be configured by BS 108 or based on predefined rules, for example, during the first CG time or before. K At each CG timing point, the indicated LCH set is applied to the LCP process.

[0051] In one implementation, UE 104 may select the LCHs to be considered and involved in during the LCP procedure based on the latency characteristics of packets buffered in the LCH. BS 108 may provide latency thresholds via L1 / L2 / L3 signaling. The same latency threshold may be applied to all LCHs, or the LCHs may be divided into subsets, and each subset may be assigned a threshold. For example, an LCH may be associated with a threshold that may differ from the thresholds associated with different LCHs.

[0052] UE 104 can calculate the delay associated with each LCH. The delay can be based on the waiting time of data in the buffer associated with the LCH. In one instance, UE 104 can select an LCH only if the calculated delay for the LCH is greater than or equal to a threshold. The selected LCH is included in the LCP procedure. If no LCH meets the delay condition, UE 104 can follow the legacy or default LCP procedure. In some instances, UE 104 can prioritize LCHs with calculated delays greater than or equal to the threshold and apply the priorities to the legacy or default LCP procedure. LCH priorities can be based on the value of the calculated delay or the difference between the calculated delay and the threshold. Alternatively, LCH priorities can follow priorities configured for the LCH.

[0053] The latency threshold can be an absolute value. The latency threshold can also be a relative value. A relative value can be a small fraction of the packet delay budget (PDB) associated with the QoS flow mapped to the LCH.

[0054] During the LCP process, data from participating LCHs is selected and included in the MAC PDU. UE 104 may include data from the LCHs that meet delay conditions in the MAC PDU. For example, UE 104 may include data when the delay associated with data from the LCH is greater than or equal to a threshold. For each selected LCH, UE 104 may select packets that meet the delay conditions, regardless of the bucket token algorithm. After selecting packets that meet the delay conditions, the remaining capacity of the MAC PDU (if any) may be filled according to a legacy mechanism. UE 104 may limit the number of bits or bytes of data selected from each LCH, for example, based on a legacy mechanism associated with the LCH (e.g., PBR or token bucket parameter Bj).

[0055] In legacy implementations, MAC CEs can have a higher priority than data. In one implementation, BS108 can explicitly instruct deprioritization of MAC CE transmissions in dynamic or configured grants via L1 / L2 / L3 messages. UE 104 prioritizes data transmissions compared to MAC CEs during the LCP procedure for the indicated UL grant. Here, L1 messages can be DCI signaling, L2 messages can be MAC CEs, and L3 messages can be RRC signaling. Deprioritization is applied only if there is data to be transmitted. If additional capacity in the MAC PDU is available after assembling the MAC PDU with data, UE 104 can consider MAC CEs to fill all or part of the remaining capacity.

[0056] In one implementation, the LCH can be in one of at least two states based on network configuration. UE104 can determine the state of the LCH based on the state of the buffered data associated with the LCH. For example, if the latency of the buffered data is below a threshold, the LCH is in a first state, and if the latency of the buffered data is above a threshold, the LCH is in a second state. In another example, if the amount of buffered data is below a threshold, the LCH is in a first state, and if the amount of buffered data is above a threshold, the LCH is in a second state.

[0057] BS 108 can configure each LCH individually with conditions. UE 104 uses these conditions to determine or switch LCH states. For example, a condition could be a latency or data volume threshold. BS 108 can allocate uplink resources only to LCHs in a specific state.

[0058] BS 108 can determine the LCH state and configure UE 104 to have that LCH state. For example, BS 108 can transmit a 1-bit flag in the dynamic grant DCI to determine the LCH state. BS 108 can use parameters in the configuration grant information element of the corresponding RRC signaling to set the LCH state.

[0059] BS 108 can allocate uplink resources and prioritize LCHs in a specific state for use. BS 108 can use a 1-bit flag in L1 / L2 / L3 commands to restrict resources to LCHs in a specific state or prioritize LCHs in a specific state. When BS 108 allocates uplink resources and restricts them to use by LCHs in a specific state, UE 104 can select LCHs in the state associated with the resource and use the selected LCHs to generate MAC PDUs. When BS 108 allocates uplink resources and prioritizes LCHs in a specific state for use, UE 104 can prioritize LCHs in the state associated with the resource. If spare resources exist within the permitted range after allocating resources to prioritized LCHs, UE 104 can reuse data from LCHs not in the state associated with the resource.

[0060] Figure 2 An operational flow / algorithm structure 200 according to some implementation schemes is illustrated. Operational flow / algorithm structure 200 is an example of operating a UE to provide dynamic LCH priority ordering for the LCP procedure. Operational flow / algorithm structure 200 may be implemented by a UE (e.g., UE 104, UE 900) or a component therein (e.g., processor 904).

[0061] The operation flow / algorithm structure 200 may include receiving LCP configuration from the BS at point 204. The LCP configuration may be included in L1 / L2 / L3 messages. The LCP configuration may be a priority set associated with the LCH or a set of LCP configurations. The LCP configuration may include an emergency flag associated with the LCH.

[0062] The operation flow / algorithm structure 200 may include receiving an L1 / L2 message from the BS at 206, wherein the message includes an indication for activating the LCP configuration. The L1 message may be a DCI carrying dynamic UL authorization. The L2 message may be a MAC CE.

[0063] The operation flow / algorithm structure 200 may include executing an LCP procedure based on the LCP configuration at point 208. The LCP procedure may be a configuration emergency LCP procedure.

[0064] Figure 3An operational flow / algorithm structure 300 according to some implementation schemes is illustrated. The operational flow / algorithm structure 300 is an example of an operation BS to provide dynamic LCH priority ordering for the LCP process. The operational flow / algorithm structure 300 may be implemented by a BS (e.g., BS 108, BS 1000) or a component therein (e.g., processor 1004).

[0065] The operation flow / algorithm structure 300 may include transmitting LCP configuration to the UE at 304. The LCP configuration may be included in L1 / L2 / L3 messages. The LCP configuration may be a priority set associated with the LCH or a set of LCP configurations. The LCP configuration may include an emergency flag associated with the LCH.

[0066] The operation flow / algorithm structure 300 may include transmitting an L1 / L2 message to the UE at 306, wherein the message includes an indication for activating the LCP configuration. The L1 message may be a DCI carrying dynamic UL authorization. The L2 message may be a MAC CE.

[0067] The operation procedure / algorithm structure 300 may include receiving uplink transmissions from the UE based on the LCP configuration at 308. The UE can use the LCP configuration to assemble the MAC PDU.

[0068] Figure 4 An operational flow / algorithm structure 400 according to some implementation schemes is illustrated. Operational flow / algorithm structure 400 is an example of operating a UE to provide dynamic LCH priority ordering for the LCP procedure. Operational flow / algorithm structure 400 may be implemented by a UE (e.g., UE 104, UE 900) or a component therein (e.g., processor 904).

[0069] The operation flow / algorithm structure 400 may include receiving L1 / L2 messages from the BS at 404, where the messages include indications for the LCH. The L1 message may be a UL grant included in the DCI. The L2 message may be a configuration grant (CG), including the timing of the active CG.

[0070] The operation flow / algorithm structure 400 may include, at 406, including or excluding the indicated LCH in the LCP process based on the indication of LCH in the L1 / L2 message.

[0071] The operation flow / algorithm structure 400 may include at 408 performing the LCP process based on the included or excluded LCH.

[0072] Figure 5An operational flow / algorithm structure 500 according to some implementation schemes is illustrated. Operational flow / algorithm structure 500 is an example of an operation BS to provide dynamic LCH priority ordering for the LCP process. Operational flow / algorithm structure 500 may be implemented by a BS (e.g., BS 108, BS 1000) or a component therein (e.g., processor 1004).

[0073] Operational flow / algorithm structure 500 may include transmitting an L1 / L2 message to the UE at 504, wherein the message includes an indication of an LCH. The L1 / L2 message indicates to the UE to include or exclude the indicated LCH during the LCP process. The L1 message may be a UL grant included in the DCI. The L2 message may be a configuration grant (CG), including the timing of the active CG.

[0074] The operation procedure / algorithm structure 500 may include receiving uplink transmissions from the UE at 506 based on the inclusion or exclusion of the LCH. The UE may apply the inclusion or exclusion of the LCH during the LCP process to assemble the MAC PDU and transmit the MAC PDU to the BS.

[0075] Figure 6 An operational flow / algorithm structure 600 according to some implementation schemes is illustrated. Operational flow / algorithm structure 600 is an example of operating a UE to provide dynamic LCH priority ordering for the LCP procedure. Operational flow / algorithm structure 600 may be implemented by a UE (e.g., UE 104, UE 900) or a component therein (e.g., processor 904).

[0076] The operation flow / algorithm structure 600 may include receiving an indication of a delay threshold from the BS at 604.

[0077] The operation flow / algorithm structure 600 may include performing an LCP procedure based on a delay threshold at 606. The UE may calculate the delay associated with the LCH and compare the calculated LCH delay with the delay threshold. The UE may set the priority of the LCH based on this comparison. Increasing the priority of an LCH may be referred to as prioritizing the LCH. When prioritizing an LCH, the UE may increase the priority of the LCH, set the priority of the LCH to be higher than the priority of some LCHs, or set the priority of the LCH to the highest priority. For example, if the delay of an LCH is greater than or equal to the threshold, the UE may increase the priority of the LCH. In one example, the UE may set the priority or LCH to the highest priority. The UE may select logical channels with delays greater than or equal to the delay threshold and prioritize the LCHs based on the configured LCH priorities. For example, if multiple LCHs meet the delay condition (e.g., have a delay greater than or equal to the threshold), the order of LCH selection among these LCHs follows the configured LCH priorities. The configured LCH priority can be assigned to the LCH based on the latency associated with the LCH, or the LCH priority can be set to a pre-configured level.

[0078] Figure 7 An operational flow / algorithm structure 700 according to some implementation schemes is illustrated. Operational flow / algorithm structure 700 is an example of operating a UE to provide dynamic LCH priority ordering for the LCP procedure. Operational flow / algorithm structure 700 may be implemented by a UE (e.g., UE 104, UE 900) or a component therein (e.g., processor 904).

[0079] The operation flow / algorithm structure 700 may include receiving at 704 an instruction from the BS to deprioritize the transmission of the MAC CE.

[0080] The operation flow / algorithm structure 700 may include performing the LCP procedure at 706 based on an instruction to deprioritize the transmission of the MAC CE.

[0081] Figure 8 An operational flow / algorithm structure 800 according to some implementation schemes is illustrated. Operational flow / algorithm structure 800 is an example of operating a UE to provide dynamic LCH priority ordering for the LCP procedure. Operational flow / algorithm structure 800 may be implemented by a UE (e.g., UE 104, UE 900) or a component therein (e.g., processor 904).

[0082] The operation flow / algorithm structure 800 may include receiving configuration from the BS at 804. This configuration may be included in an RRC message, a MAC message, or a DCI.

[0083] The operation flow / algorithm structure 800 may include assigning a state to the LCH at 804 based on the configuration and the state of the buffered data at the LCH.

[0084] The operation flow / algorithm structure 800 may include performing an LCP process for the LCH at 808 based on the state. The LCP process may include: selecting the LCH based on the state associated with the LCH; and prioritizing the LCHs based on the configured LCH priority or the state associated with the LCH.

[0085] Figure 9 An example of a UE 900 according to some implementation schemes is shown. UE 900 may be similar to... Figure 1 The UE 104 is essentially interchangeable with it.

[0086] UE 900 can be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, XR devices, glasses, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, voltmeters / ammeters, or actuators), video surveillance / monitoring devices (e.g., cameras or camcorders), wearable devices (e.g., smartwatches), or Internet of Things (IoT) devices.

[0087] UE 900 may include a processor 904, RF interface circuitry 908, memory / storage device 912, user interface 916, sensor 920, drive circuitry 922, power management integrated circuit (PMIC) 924, antenna structure 926, and battery 928. The components of UE 900 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 9 The block diagram is intended to show a high-level view of some of the components in the UE 900. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0088] The components of UE 900 can be coupled to various other components via one or more interconnects 932, which can represent any type of interface, input / output, bus (local, system, or extension), transmit line, trace, or optical connector, allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0089] Processor 904 may include processor circuitry, such as, for example, baseband processor circuitry (BB) 904A, central processing unit circuitry (CPU) 904B, and graphics processing unit circuitry (GPU) 904C. Processor 904 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 912) to cause UE 900 to perform the operations described herein.

[0090] Processor 904 may perform operations associated with executing the LCP procedure based on the dynamic conditions of the LCH. For example, processor 904 may: receive configuration, indication, or command; identify the LCH based on the configuration, indication, or command; assign LCP configuration or priority; or execute the LPC procedure based on the LCH-associated LCP configuration or priority consistent with the implementation described herein.

[0091] In some implementations, the baseband processor circuitry 904A can access the communication protocol stack 936 in the memory / storage device 912 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuitry 904A can access the communication protocol stack 936 to: perform user plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, SDAP sublayer, and upper layers; and perform control plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, RRC layer, and NAS layer. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuitry 908.

[0092] The baseband processor circuit 904A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0093] Memory / storage device 912 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 936) that can be executed by one or more processors in processor 904 to cause UE 900 to perform the various operations described herein. Memory / storage device 912 includes any type of volatile or non-volatile memory that can be distributed throughout UE 900. In some embodiments, some memory / storage devices 912 may be located on processor 904 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 912 may be located external to processor 904 but accessible via a memory interface. Memory / storage device 912 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0094] RF interface circuitry 908 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows UE 900 to communicate with other devices via a radio access network. RF interface circuitry 908 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.

[0095] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 926, and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which down-converts the RF signal into a baseband signal, which is then provided to the baseband processor of processor 904.

[0096] In the transmission path, the transceiver's transmitter up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can then amplify the RF signal using a power amplifier before it is radiated across the air interface via antenna 926.

[0097] In various implementations, the RF interface circuit 908 can be configured to transmit / receive signals in a manner compatible with NR access technology.

[0098] Antenna 926 may include antenna elements to convert electrical signals into radio waves for propagation through the air, and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 926 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input multiple-output communication. Antenna 926 may include a microstrip antenna, patch antenna, phased array antenna, or a printed antenna fabricated on the surface of one or more printed circuit boards. Antenna 926 may have one or more panels designed for a specific frequency band (including bands in FR1 or FR2).

[0099] User interface circuitry 916 includes various input / output (I / O) devices designed to enable users to interact with UE 900. User interface 916 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, particularly one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual components for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly one or more simple visual outputs / indicators (e.g., binary status indicators, such as light-emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced through the operation of UE 900.

[0100] Sensor 920 may include devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, or subsystems. Examples of such sensors include: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors); depth sensors; ambient light sensors; ultrasonic transceivers; and microphones or other similar audio capture devices.

[0101] The driving circuitry 922 may include software and hardware elements that operate to control specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 900. The driving circuitry 922 may include individual drivers that allow other components to interact with or control various I / O devices that may be present within or connected to the UE 900. For example, the driving circuitry 922 may include circuitry for facilitating the coupling of a Universal Integrated Circuit Card (UICC) or a Universal Subscriber Identity Module (USIM) to the UE 900. Furthermore, the driving circuitry 922 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for obtaining sensor readings from sensor circuitry 920 and controlling and allowing access to sensor circuitry 920; a driver for obtaining actuator positioning of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0102] The PMIC 924 can manage the power supplied to various components of the UE 900. Specifically, relative to the processor 904, the PMIC 924 can control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0103] In some implementations, the PMIC 924 may control or otherwise become part of various power-saving mechanisms of the UE 900, including DRX, as discussed herein.

[0104] Battery 928 can power UE 900, but in some examples, UE 900 may be installed and deployed in a fixed location and may have a power source coupled to the grid. Battery 928 may be a lithium-ion battery, a metal-air battery (such as zinc-air batteries, aluminum-air batteries, lithium-air batteries, etc.). In some specific implementations, such as in vehicle-based applications, battery 928 may be a typical lead-acid automotive battery.

[0105] Figure 10 A network node 1000 is illustrated according to some implementation schemes. The network node 1000 may resemble a base station 108, a device that implements a network hop, an integrated access and backhaul (IAB) node, a network control repeater, or a server in the core network or external data network, and is substantially interchangeable with them.

[0106] Network node 1000 may include processor 1004, RF interface circuitry 1008 (if implemented as an access node), core node (CN) interface circuitry 1012, memory / storage device circuitry 1016, and antenna structure 1026.

[0107] The components of network node 1000 can be coupled to various other components through one or more interconnectors 1028.

[0108] The processor 1004, RF interface circuit 1008, memory / storage device circuit 1016 (including communication protocol stack 1010), antenna structure 1026, and interconnect 1028 can be similar to those relative to... Figure 9 Similar named elements are shown and described.

[0109] Processor 1004 can perform operations associated with enabling the UE to dynamically modify the LCP procedure. For example, processor 1004 can configure the UE to dynamically modify the LCP procedure and receive UL transmissions from the UE based on a UE configuration consistent with the implementation described herein.

[0110] The CN interface circuit 1012 can provide connectivity to a core network (e.g., a 5GC using a fifth-generation core network (5GC) compatible network interface protocol, such as Carrier Ethernet or some other suitable protocol). Network connectivity can be provided to / from network node 1000 via fiber optic or wireless backhaul. The CN interface circuit 1012 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1012 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0111] In some implementations, network node 1000 may be coupled to transmit-receive point (TRP) using antenna structure 1026, CN interface circuitry or other interface circuitry.

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

[0113] For one or more aspects, at least one of the components depicted in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below. Similarly, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below in the Embodiments section.

[0114] Example Further exemplary aspects are provided in the following sections.

[0115] Example 1 includes a method for operating a user equipment (UE), the method comprising: receiving a Logical Channel Priority Ordering (LCP) configuration from a base station (BS); receiving from the BS a Layer 1 (L1) or Layer 2 (L2) message including an indication for activating the LCP configuration; and performing an LCP procedure based on the LCP configuration.

[0116] Example 2 includes the method described according to Example 1 or some other embodiments herein, wherein the LCP configuration is included in a Radio Resource Control (RRC) message.

[0117] Example 3 includes the method according to Example 1 or 2 or some other embodiments herein, wherein the LCP configuration is included in the L1 or L2 message.

[0118] Example 4 includes the method according to any one of Examples 1 to 3 or some other embodiments herein, wherein receiving an L1 message or an L2 message includes receiving an L1 message with uplink permission or an L2 message with a Media Access Control (MAC) Control Element (CE).

[0119] Example 5 includes the method according to any one of Examples 1 to 4 or some other embodiments herein, wherein the LCP configuration is associated with a logical channel (LCH) including an emergency flag.

[0120] Example 6 includes the method according to any one of Examples 1 to 5 or some other embodiments herein, wherein the L1 or L2 message includes an emergency level associated with the emergency flag of the LCH.

[0121] Example 7 includes the method according to any one of Examples 1 to 6 or some other embodiments herein, wherein the LCP procedure is an emergency LCP procedure based on the L1 or L2 message or based on conditions detected by the UE, the emergency LCP procedure including: determining a set of LCHs based on the emergency flag or the LCP configuration; and prioritizing the LCHs based on the emergency flag or the LCP configuration.

[0122] Example 8 includes a method of operating a base station (BS), the method comprising: transmitting a Logical Channel Priority (LCP) configuration to a user equipment (UE); transmitting a Layer 1 (L1) or Layer 2 (L2) message to the UE including an indication for activating the LCP configuration; and receiving uplink transmissions from the UE based on the LCP configuration.

[0123] Example 9 includes the method described according to Example 8 or some other embodiments herein, wherein the LCP configuration is included in a Radio Resource Control (RRC) message.

[0124] Example 10 includes the method according to Example 8 or 9 or some other embodiments herein, wherein the indication for activating the LCP configuration is the LCP configuration.

[0125] Example 11 includes the method according to any one of Examples 8 to 10 or some other embodiments herein, wherein transmitting the L1 or L2 message includes transmitting an L1 message with uplink permission or an L2 message with a Media Access Control (MAC) Control Element (CE).

[0126] Example 12 includes a method of operating a user equipment (UE), the method comprising: receiving from a base station a Layer 1 or Layer 2 (L1 / L2) message including an indication of a logical channel (LCH); including or excluding the LCH in a logical channel priority ordering (LCP) process based on the indication of the L1 / L2 message; and performing the LCP process based on the inclusion or exclusion of the LCH.

[0127] Example 13 includes the method according to Example 12 or some other embodiments herein, wherein receiving L1 / l2 messages includes receiving L1 messages with uplink permission.

[0128] Example 14 includes the method according to Example 12 or 13 or some other embodiments herein, wherein receiving the L1 / L2 message includes receiving an L2 message with a configuration grant (CG), the configuration grant including an active CG timing, and the execution of the LCP procedure is applied during the active CG timing.

[0129] Example 15 includes a method of operating a base station (BS), the method comprising: transmitting a Layer 1 or Layer 2 (L1 / L2) message to a user equipment (UE), the L1 / L2 message including an indication of a logical channel (LCH) for including or excluding the LCH during a logical channel priority ordering (LCP) process; and receiving uplink transmissions from the UE based on including or excluding the LCH.

[0130] Example 16 includes the method according to Example 15 or some other embodiments herein, wherein transmitting the L1 / L2 message includes transmitting an L1 message with uplink permission, or the L2 message is a configuration permission.

[0131] Example 17 includes a method of operating a user equipment (UE), the method comprising: receiving an indication of a delay threshold from a base station; and performing a logical channel priority (LCP) process based on the delay threshold.

[0132] Example 18 includes the method according to Example 17 or some other embodiments herein, wherein the delay threshold is associated with a logical channel (LCH).

[0133] Example 19 includes the method according to Example 17 or 18 or some other embodiments herein, wherein the LCP process includes: calculating a delay associated with a logical channel (LCH); selecting the LCH based on the delay being greater than or equal to the delay threshold; and prioritizing the LCH.

[0134] Example 20 includes a method of operating a user equipment (UE), the method comprising: receiving from a base station an indication to de-prioritize the transmission of a medium access control (MAC) control element (CE); and performing a logical channel priority ordering (LCP) procedure based on the indication.

[0135] Example 21 includes the method according to Example 20 or some other embodiments herein, wherein the transmission of the MACCE is associated with dynamic grant or configuration grant.

[0136] Example 22 includes the method according to Example 20 or 21 or some other embodiments herein, wherein the indication is included in a Radio Resource Control (RRC) message, a MAC message or a Downlink Control Information message.

[0137] Example 23 includes a method of operating a user equipment (UE), the method comprising: receiving configuration from a base station; assigning state to a logical channel (LCH) based on the configuration and the state of buffered data; and performing a logical channel priority ordering (LCP) procedure for the LCH based on the state.

[0138] Example 24 includes the method according to Example 23 or some other embodiments herein, wherein the LCP process includes: selecting a logical channel (LCH) based on the state; and prioritizing the LCH based on a configured LCH priority or the state.

[0139] Another embodiment may include an apparatus comprising one or more elements for performing the methods described or associated with any of Embodiments 1 to 24 or any other methods or processes described herein.

[0140] Another embodiment may include the methods, techniques or processes described or associated with any one of embodiments 1 to 24 or any part or component thereof.

[0141] Another embodiment may include an apparatus comprising: one or more processors; and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform the methods, techniques, or processes described or associated with any one or more of embodiments 1 to 24.

[0142] Another embodiment includes the signal described or associated with any one of embodiments 1 to 24 or a part or component thereof.

[0143] Another embodiment may include datagrams, information elements, packets, frames, segments, PDUs, or messages described or associated with any one of embodiments 1 to 24 or any part or component thereof, or otherwise described in this disclosure.

[0144] Another embodiment may include a data-encoded signal described or associated with any one of embodiments 1 to 24 or a portion or component thereof, or otherwise described in this disclosure.

[0145] Another embodiment may include signals encoded as datagrams, IEs, packets, frames, segments, PDUs, or messages as described or associated with any one of embodiments 1 to 24 or any part or component thereof, or otherwise described in this disclosure.

[0146] Another embodiment may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform the methods, techniques or processes described or associated with any one or more of embodiments 1 to 24.

[0147] Another embodiment may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process described or associated with any one or a portion thereof according to Embodiments 1 to 24.

[0148] Another embodiment may include signals in a wireless network as shown and described herein.

[0149] Another embodiment may include a method for communicating in a wireless network as shown and described herein.

[0150] Another embodiment may include a system for providing wireless communication as shown and described herein.

[0151] Another embodiment may include a device for providing wireless communication as shown and described herein.

[0152] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the aspects to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from practice in various aspects.

[0153] Although the foregoing aspects have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the foregoing disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. A method for operating a user equipment (UE), the method comprising: Receive Logical Channel Priority Ordering (LCP) configuration from the base station (BS); Receive from the BS a Layer 1 (L1) message or a Layer 2 (L2) message including an indication for activating the LCP configuration; as well as The LCP process is executed based on the LCP configuration.

2. The method of claim 1, wherein the LCP configuration is included in a Radio Resource Control (RRC) message.

3. The method of claim 1, wherein the LCP configuration is included in the L1 message or the L2 message.

4. The method of claim 1, wherein receiving an L1 message or an L2 message includes receiving an L1 message with uplink permission or an L2 message with a Media Access Control (MAC) control element (CE).

5. The method of claim 1, wherein the LCP configuration is associated with a logical channel (LCH) including an emergency flag.

6. The method of claim 5, wherein the L1 message or the L2 message includes an emergency level associated with the emergency flag of the LCH.

7. The method of claim 5, wherein the LCP procedure is an emergency LCP procedure based on the L1 message or the L2 message or based on a condition detected by the UE, the emergency LCP procedure comprising: The LCH set is determined based on the emergency flag or the LCP configuration; as well as Prioritize LCHs based on the emergency flag or the LCP configuration.

8. A method for operating a base station (BS), the method comprising: Transmit Logical Channel Priority (LCP) configuration to User Equipment (UE); Transmit a Layer 1 (L1) message or a Layer 2 (L2) message to the UE, including an indication for activating the LCP configuration; as well as The uplink transmission is received from the UE based on the LCP configuration.

9. The method of claim 8, wherein the LCP configuration is included in a Radio Resource Control (RRC) message.

10. The method of claim 8, wherein the indication for activating the LCP configuration is the LCP configuration.

11. The method of claim 8, wherein transmitting the L1 message or L2 message includes transmitting an L1 message with uplink permission or an L2 message with a Media Access Control (MAC) control element (CE).

12. A method of operating a user equipment (UE), the method comprising: Receive from the base station a Layer 1 or Layer 2 (L1 / L2) message that includes an indication of the logical channel (LCH); Based on the indication of the L1 / L2 messages, include or exclude the LCH during the Logical Channel Prioritization (LCP) process; and The LCP process is performed based on the inclusion or exclusion of the LCH.

13. The method of claim 12, wherein receiving the L1 / l2 message comprises: Receive an L1 message with uplink permission.

14. The method of claim 12, wherein receiving the L1 / L2 message comprises receiving an L2 message having a configuration grant (CG), the configuration grant including an active CG timing, and the execution of the LCP procedure being applied during the active CG timing.

15. A method of operating a base station (BS), the method comprising: Transmitting Layer 1 or Layer 2 (L1 / L2) messages to User Equipment (UE), the L1 / L2 messages including indications of Logical Channels (LCHs) for inclusion or exclusion during Logical Channel Prioritization (LCP) processes; and The uplink transmission is received from the UE based on whether or not the LCH is included.

16. The method of claim 15, wherein transmitting the L1 / L2 message comprises transmitting an L1 message with uplink permission, or the L2 message is a configuration permission.

17. A method of operating a user equipment (UE), the method comprising: Receive an indication of the delay threshold from the base station; as well as The Logical Channel Priority (LCP) process is performed based on the aforementioned delay threshold.

18. The method of claim 17, wherein the delay threshold is associated with a logical channel (LCH).

19. The method of claim 17, wherein the LCP process comprises: Calculate the delay associated with the logical channel (LCH); The LCH is selected based on the delay being greater than or equal to the delay threshold. as well as The LCH is prioritized.

20. A method of operating a user equipment (UE), the method comprising: Receive instructions from the base station to deprioritize the transmission of Media Access Control (MAC) Control Elements (CEs); as well as The Logical Channel Priority (LCP) process is performed based on the instructions.

21. The method of claim 20, wherein the transmission of the MAC CE is associated with dynamic grant or configuration grant.

22. The method of claim 20, wherein the indication is included in a Radio Resource Control (RRC) message, a MAC message, or a Downlink Control Information message.

23. A method of operating a user equipment (UE), the method comprising: Receive configuration from the base station; State is assigned to the Logical Channel (LCH) based on the state of the configuration and buffer data; as well as Based on the state, perform the Logical Channel Priority Ordering (LCP) process for the LCH.

24. The method of claim 23, wherein the LCP process comprises: Select the logical channel (LCH) based on the state. as well as The LCH is prioritized based on the configured LCH priority or the state.

Images