Method and apparatus for supporting priority of logical channel, and communication system

Abstract

Provided in the embodiments of the present application are a method and apparatus for supporting the priority of a logical channel, and a communication system. The apparatus is applied to a terminal device, and comprises: a configuration unit, which configures a first parameter and a default priority for a logical channel of a media access control (MAC) entity of the terminal device, the first parameter being configured to set the priority of the logical channel containing first data; and a determination unit, which determines the priority of the logical channel, wherein the first parameter is configured by means of radio resource control (RRC) signaling, and the remaining time of a packet data convergence protocol layer service data unit (PDCP SDU) associated with the first data is less than a first threshold.

Description

Methods, apparatus and communication systems supporting logical channel priority Technical Field

[0001] The embodiments of this application relate to the field of communication technology. Background Technology

[0002] Extended Reality (XR) refers to all environments and human-computer interactions that combine the real and virtual worlds, created through computer technology and wearable devices. XR is a general term encompassing different types of reality. It includes representative forms such as Virtual Reality (VR), Augmented Reality (AR), and Mixed Reality (MR), as well as their interdisciplinary applications. Different application areas of XR include entertainment, healthcare, and education.

[0003] VR is a rendered version of the released visual and audio scene. As an observer or user moves within the constraints defined by the application, the rendering is designed to simulate the visual and auditory sensory stimuli of the real world as naturally as possible.

[0004] AR refers to providing users with additional information or artificially generated items or content that overlays their current environment.

[0005] MR is an advanced form of AR, in which some virtual elements are inserted into the physical scene to create the illusion that these elements are part of the real scene.

[0006] 5G technology is exploring key issues, solutions, and conclusions to support advanced media services, such as High Data Rate Low Latency (HDRLL) services, AR / VR / XR services, and haptic / multimodal communication services. Objectives include enhanced capabilities and improved scheduling methods to support multimodal services.

[0007] For enhancements to multimodal services, the study investigates whether and how to enable applications to provide users with relevant haptic and multimodal data at similar times. Multimodal data includes, for example, time-specific audio, video, and haptic data. The focus is on the need for enhanced policy control, such as Quality of Service (QoS) policy coordination.

[0008] For enhanced scheduling methods, research is conducted on using enhanced functions with latency or deadline information to support enhanced uplink scheduling for uplink services, thereby achieving higher XR capacity while meeting latency requirements or avoiding transmission delays of Media Access Control (MAC) Protocol Data Units (PDUs). Since logical channel prioritization (LCP) is implemented on the terminal side, it is necessary to minimize the complexity of the terminal equipment.

[0009] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application. Summary of the Invention

[0010] In current communication systems, the Logical Channel Prioritization (LCP) process is defined by the Media Access Control (MAC) protocol. To support various Ultra-Reliable and Low-Latency Communication (URLLCU) services and to meet the stringent latency requirements of URLLCU services, various resource conflict scenarios need to be considered. For uplink resource conflicts within the same user, the main considerations are conflicts between data and conflicts between data and scheduling requests (SRs). The method for resolving these resource conflicts is called intra-UE prioritization. When the MAC performs prioritization, it adopts a logical channel-based prioritization method, meaning the MAC layer selects resources for priority transmission based on logical channel priority.

[0011] The inventors of this application have discovered that in existing LCP processes, when allocating resources based on uplink grants, the selection order of logical channels is determined by their priority, without considering the latency requirements of the data within each logical channel. For example, if a logical channel has a low priority but the data it contains has high latency requirements and the remaining time (i.e., the remaining latency budget) is low, this data may be preempted by data from relatively high-priority logical channels, leading to transmission delays. Latency-sensitive XR services may not be able to meet latency requirements, thus affecting the performance of XR services.

[0012] Enhancing logical channel priority during LCP can affect logical channel priority selection during intra-user prioritization. The following issues need to be addressed: how to determine logical channel priority in enhanced intra-user overlapping resource prioritization; how to select the process ID for Hybrid Automatic Repeat-reQuest (HARQ) within configured grant intra-CG prioritization; and how to trigger a regular buffer status report (BSR).

[0013] To address at least one of the aforementioned problems or other similar issues, embodiments of this application provide a method, apparatus, and communication system that support logical channel priority. When a logical channel contains delayed data during resource allocation, a priority configuration is added to the logical channel corresponding to the XR service data. For example, during intra-UE prioritization and intra-CG prioritization, the priority of the logical channel is selected based on whether the logical channel contains delayed data. This solves the problem of how to prioritize the transmission of XR data with short latency requirements, thus better supporting XR services with high latency requirements and improving the user experience of XR and media services.

[0014] According to one aspect of the embodiments of this application, a method for supporting logical channel priority is provided, applied to a terminal device, the method comprising:

[0015] The logical channel of the Media Access Control (MAC) entity of the terminal device is configured with a first parameter and a default priority, wherein the first parameter is used to set the priority of the logical channel containing first data; and

[0016] Determine the priority of the logical channel.

[0017] in,

[0018] The first parameter is configured via Radio Resource Control (RRC) signaling.

[0019] The remaining time of the Service Data Unit (PDCP SDU) of the Packet Data Convergence Protocol layer associated with the first data is less than the first threshold.

[0020] According to one aspect of the embodiments of this application, an apparatus supporting logical channel priority is provided, applied to a terminal device, the apparatus comprising:

[0021] A configuration unit configures a first parameter and a default priority for a logical channel of the Media Access Control (MAC) entity of the terminal device, wherein the first parameter is used to set the priority of the logical channel containing first data; and

[0022] The determining unit determines the priority of the logical channel.

[0023] in,

[0024] The first parameter is configured via Radio Resource Control (RRC) signaling.

[0025] The remaining time of the Service Data Unit (PDCP SDU) of the Packet Data Convergence Protocol layer associated with the first data is less than the first threshold.

[0026] One of the beneficial effects of this application's embodiments is that, when the logical channel contains delayed data during resource allocation, a priority configuration is added to the logical channel corresponding to the XR service data. This solves the problem of how to prioritize the transmission of XR data with short latency requirements during intra-UE prioritization and intra-CG prioritization, thus better supporting XR with high latency requirements and improving the user experience of XR and media services.

[0027] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.

[0028] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0029] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0030] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0031] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application;

[0032] Figure 2 is a schematic diagram of a method for supporting logical channel priority according to an embodiment of this application;

[0033] Figure 3 is a schematic diagram of a method for supporting logical channel priority according to Embodiment 1 of this application;

[0034] Figure 4 is a schematic diagram of a method for a media access control entity to determine logical channel priority according to Embodiment 1 of this application;

[0035] Figure 5 is another schematic diagram of the method for determining logical channel priority by the media access control entity according to Embodiment 1 of this application;

[0036] Figure 6 is another schematic diagram of the method by which the media access control entity determines the logical channel priority in Embodiment 1 of this application;

[0037] Figure 7 is another schematic diagram of the method for supporting logical channel priority according to Embodiment 1 of this application;

[0038] Figure 8 is another schematic diagram of the method for supporting logical channel priority in Embodiment 1 of this application;

[0039] Figure 9 is another schematic diagram of the method for supporting logical channel priority in Embodiment 1 of this application;

[0040] Figure 10 is another schematic diagram of the method for supporting logical channel priority according to Embodiment 1 of this application;

[0041] Figure 11 is a schematic diagram of a method for supporting logical channel priority according to Embodiment 2 of this application;

[0042] Figure 12 is another schematic diagram of the method for supporting logical channel priority according to Embodiment 2 of this application;

[0043] Figure 13 is another schematic diagram of the method for supporting logical channel priority in Embodiment 2 of this application;

[0044] Figure 14 is a schematic diagram of a method for supporting logical channel priority according to Embodiment 3 of this application;

[0045] Figure 15 is a schematic diagram of an apparatus supporting logical channel priority according to an embodiment of this application;

[0046] Figure 16 is a schematic block diagram of the electronic device of this application. Detailed Implementation

[0047] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.

[0048] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.

[0049] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly understood as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," and the term "based on" should be understood as "at least partially based on…," unless the context explicitly indicates otherwise.

[0050] In the embodiments of this application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0051] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other currently known or future communication protocols.

[0052] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, the following devices: integrated access and backhaul node (IAB-node), base station (BS), access point (AP), transmission and reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0053] The term "base station" can include, but is not limited to, NodeBs (or NBs), evolved NodeBs (or eNodeBs or eNBs), and 5G base stations (gNBs), etc. It can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (such as femeto, pico, etc.). The term "base station" can encompass some or all of its functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0054] In the embodiments of this application, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer, for example, to a device that accesses a communication network and receives network services through a network device. A terminal device can be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc.

[0055] The terminal device may include, but is not limited to, the following devices: cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, machine-type communication device, laptop computer, cordless phone, smartphone, smartwatch, digital camera, etc.

[0056] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, such as including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and so on.

[0057] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above.

[0058] In the following description, without causing confusion, the terms “uplink control signal” and “uplink control information (UCI)” or “physical uplink control channel (PUCCH)” are used interchangeably, as are the terms “uplink data signal” and “uplink data information” or “physical uplink shared channel (PUSCH)”.

[0059] The terms “downlink control signal” and “downlink control information (DCI)” or “physical downlink control channel (PDCCH)” are interchangeable, as are the terms “downlink data signal” and “downlink data information (PDSCH)” or “physical downlink shared channel (PDSCH)”.

[0060] Furthermore, sending or receiving a PUSCH can be understood as sending or receiving uplink data carried by the PUSCH; sending or receiving a PUCCH can be understood as sending or receiving uplink information carried by the PUCCH; and sending or receiving a PRACH can be understood as sending or receiving a preamble carried by the PRACH. Uplink signals can include uplink data signals and / or uplink control signals, and can also be referred to as uplink transmission (UL transmission), uplink information, or uplink channel. Sending an uplink transmission on uplink resources can be understood as using those uplink resources to send the uplink transmission. Similarly, downlink data / signals / channels / information can be understood accordingly.

[0061] In the embodiments of this application, higher-layer signaling may be, for example, Radio Resource Control (RRC) signaling; for example, referred to as an RRC message, including MIB, system information, dedicated RRC messages; or referred to as an RRC information element. Higher-layer signaling may also be, for example, Medium Access Control (MAC) signaling; or referred to as a MAC control element. However, this application is not limited to these.

[0062] In the embodiments of this application, "at least one" and "one or more" can be used interchangeably, and "multiple" and "more than one" can be used interchangeably. "Multiple" means at least two, or two or more.

[0063] In the embodiments of this application, "predefined" refers to what is specified by the protocol or determined according to the rules specified by the protocol, and does not require additional configuration. "Configuration / instruction" refers to what the network device directly or indirectly configures / instructs through higher-layer signaling and / or physical layer signaling. Configuration / instruction can be achieved by introducing higher-layer parameters into the higher-layer signaling. Higher-layer parameters refer to information fields and / or information elements / information units / information cells / information cells (IEs) in the higher-layer signaling. Physical layer signaling refers to, for example, control information (DCI) carried by the physical downlink control channel or control information carried by the sequence, but is not limited to these.

[0064] For ease of description, the following text uses a base station as an example of an access network device.

[0065] In the following explanation, without causing confusion, “if…”, “in the case of…” and “when…” can be used interchangeably.

[0066] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0067] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application, illustrating the case of a terminal device and a network device as examples. As shown in Figure 1, the communication system 100 may include a network device 101, a terminal device 102, and a terminal device 103. For simplicity, Figure 1 only illustrates the case of two terminal devices and one network device, but the embodiments of this application are not limited to this.

[0068] In this embodiment of the application, network device 101, terminal device 102, and terminal device 103 can transmit existing services or services that can be implemented in the future. For example, these services may include, but are not limited to: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), ultra-reliable and low-latency communication (URLLC), and related communications of terminal devices with reduced capabilities, etc.

[0069] Terminal devices 102 and 103 can be in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED states. Terminal devices 102 and 103 can also communicate with network device 101. For example, taking terminal device 102 as an example, terminal device 102 can send data to network device 101 or perform data retransmission. Network device 101 can send paging messages to terminal device 102 or send data to terminal device 102, and terminal device 102 can receive data sent by network device 101. Furthermore, different terminal devices can also communicate with each other; for example, terminal device 102 and terminal device 103 can exchange data.

[0070] It is worth noting that Figure 1 shows that both terminal device 102 and terminal device 103 are within the coverage area of ​​network device 101, but this application is not limited to this. Terminal device 102 and terminal device 103 may both be outside the coverage area of ​​network device 101, or one of terminal device 102 and terminal device 103 may be within the coverage area of ​​network device 101 while the other is outside the coverage area of ​​network device 101.

[0071] First aspect of the embodiments

[0072] This application provides a method for supporting logical channel priority, applied to terminal device 102.

[0073] Figure 2 is a schematic diagram of a method for supporting logical channel priority according to an embodiment of this application. As shown in Figure 2, the method for supporting logical channel priority includes:

[0074] Operation 201: The logical channel of the Media Access Control (MAC) entity of terminal device 102 is configured with a first parameter and a default priority, the first parameter being used to set the priority of the logical channel containing the first data; and

[0075] Operation 202: Determine the priority of the logical channel. In different scenarios, determining the priority of the logical channel allows us to determine the priority of uplink grants, the priority of HARQ procedures, the priority of scheduling requests, etc.

[0076] In operation 201 of this application, the first parameter can be configured via Radio Resource Control (RRC) signaling, and the remaining time of the Packet Data Convergence Protocol Layer Service Data Unit (PDCP SDU) associated with the first data is less than a first threshold.

[0077] In operation 201 of this application, the larger the value of the first parameter, the lower the priority of the logical channel containing the first data.

[0078] In operation 201 of this application, the priority of the logical channel containing the first data is higher than the default priority of the logical channel.

[0079] In this application, when terminal device 102 performs new data transmission, the Media Access Control (MAC) entity of terminal device 102 needs to apply the LCP procedure.

[0080] In operation 201 of this application, the first parameter is a possible new priority configured for each logical channel, used to control the scheduling of uplink data, and can be called a priority adjustment parameter. If a logical channel is configured with the first parameter, the first parameter is higher than or equal to the original priority of the logical channel, and the value of the first parameter is less than or equal to the original priority of the logical channel. If a logical channel is configured with the first parameter, it indicates that the logical channel supports logical channel priority adjustment based on the first data during LCP.

[0081] In this application, the original priority of a logical channel is defined by a priority parameter, which can be referred to as the default priority or initial priority of the logical channel. The priority parameter is configured for each logical channel by RRC signaling.

[0082] In this application, the first data is data with a remaining time less than a first threshold, that is, data with a remaining time less than the first threshold indicated by the remaining value of the discard timer of the Packet Data Convergence Protocol Layer Service Data Unit (PDCP SDU) associated with the first data.

[0083] In this application, the first data can be referred to as data that has completed logical channel priority adjustment (LCH priority-adjusted) or data that can be logically priority-adjustable (LCH priority-adjustable); it can also be referred to as delay-critical data, urgent data, delay-sensitive data, short-delay data, short-remaining-time data, etc.

[0084] In this application, the first data may be a service data unit (SDU) of the media access control (MAC) that can be used for transmission. Each MAC SDU corresponds to a packet data aggregation protocol layer service data unit (PDCP SDU) including a discard timer. The running value of the discard timer can be compared with a first threshold to determine whether the MAC SDU is the first data. Alternatively, the remaining delay budget of the MAC SDU can be compared with the first threshold to determine whether the MAC SDU is the first data.

[0085] In this application, the first threshold can be configured by RRC signaling.

[0086] For example, a first threshold can be configured in the LogicalChannelConfig information element (IE) of the RRC Reconfiguration message. That is, a first threshold IE (remainingTimeThresholdLCH IE) is added to the LogicalChannelConfig IE to configure a first threshold for each logical channel. This threshold is used to set a threshold for the remaining time of data available for transmission on that logical channel, and to determine whether to use the first parameter.

[0087] For example, a first threshold can be configured in the MAC-CellGroupConfig IE of the RRCReconfiguration message. The first threshold can be configured based on each logical channel, that is, each first threshold corresponds to the identifier of a logical channel; or the first threshold can be configured based on each logical channel group (LCG), that is, each first threshold corresponds to the identifier of a logical channel group.

[0088] Operation 202 of this application is an enhancement to different processes of Media Access Control (MAC) of a terminal device (UE). The methods overlap, and these enhancements can be used independently or in combination.

[0089] The method for supporting logical channel priority in this application will be further explained below in conjunction with each process of the Media Access Control (MAC) of the terminal equipment (UE).

[0090] Example 1

[0091] Example 1 is an enhancement to the priority processing procedure for overlapping resources within a terminal device (UE).

[0092] When a logical channel-based prioritization (lch-Based Prioritization) method is configured for a Media Access Control (MAC) entity, in the event of a transmission resource conflict, the MAC prioritizes the transmission of uplink transmission resources carrying higher-priority data. The priority of an uplink transmission resource is determined by the priority of the logical channel that is multiplexed to or can be multiplexed to the highest priority logical channel within that resource. Whether a logical channel can be multiplexed into a corresponding transmission resource depends on whether the logical channel has data to be transmitted and the configured logical channel mapping restrictions.

[0093] The method for determining the priority of each logical channel that is multiplexed to or can be multiplexed to the corresponding resource includes any one of the following methods 1, 2, 3, 4 and 5.

[0094] Method 1:

[0095] Figure 3 is a schematic diagram of a method for supporting logical channel priorities according to Embodiment 1 of this application. As shown in Figure 3, when determining the logical channel priority of uplink grant and / or determining the logical channel priority that triggers the scheduling request (i.e., the priority of the scheduling request), the terminal device 102 performs the following operations:

[0096] Operation 301: When determining the logical channel priority for uplink grant and / or the logical channel priority for triggering a scheduling request, use the default priority for each logical channel configured with the first parameter.

[0097] In operation 301, the uplink authorization reception process can be enhanced, and the terminal device 102 performs the following:

[0098] Operation 301a: For a Media Access Control (MAC) entity configured with logical channel-based priority, the uplink grant priority is determined by the highest default priority among one or more logical channels that are multiplexed to the MAC layer Protocol Data Unit (MAC PDU) or have available data that can be multiplexed to the MAC layer.

[0099] In Operation 301a, one or more logical channels for which available data can be multiplexed to Media Access Control Protocol Data Units (MAC PDUs) are determined by mapping constraints during the logical channel selection process.

[0100] Among them, the priority of uplink grant for data without a logical channel being multiplexed to or being multiplexed to a MAC PDU is lower than the priority of uplink grant for data with any logical channel being multiplexed to or having available data multiplexed to a MAC PDU, and also lower than the priority of the logical channel that triggers the scheduling request.

[0101] A logical channel multiplexed to a MAC PDU refers to a logical channel whose data has already been used by the multiplexing and assembly entities to generate a MAC PDU, which is then stored in the HARQ buffer. A logical channel with available data that can be multiplexed to a MAC PDU refers to a logical channel (i.e., in the Layer 2 buffer) containing data to be transmitted, which will be used by the multiplexing and assembly entities to generate a MAC PDU.

[0102] Figure 4 is a schematic diagram of a method for a media access control entity to determine logical channel priority according to Embodiment 1 of this application. As shown in Figure 4, in operation 301a, when the media access control (MAC) entity is configured with logical channel-based priority, for each uplink grant submitted to an entity that submits a Hybrid Automatic Repeat Request (HARQ), and the physical uplink shared channel (PUSCH) associated with the uplink grant can be transmitted at the lower layer, the media access control (MAC) entity performs the following operations:

[0103] Operation 401: If the uplink grant is for a configured Scheduled Radio Network Temporary Identifier (CS-RNTI) and the new data indication is the first value (NDI=1), or for a Cell Radio Network Temporary Identifier (C-RNTI), then:

[0104] Operation 402: If, within the same bandwidth portion (BWP), the duration of an uplink grant does not overlap with that of a physical uplink shared channel (PUSCH) for a configured uplink grant that has not been de-prioritized, and its priority is higher than that of the uplink grant; and

[0105] Operation 403: If the uplink grant does not overlap with the physical uplink control channel (PUCCH) resource of a scheduling request transmission that has not been downgraded, and based on the fact that simultaneous transmission of the scheduling request and uplink grant is not allowed, and the default priority of the logical channel that triggered the scheduling request is higher than the priority of the uplink grant, then:

[0106] Operation 404: The uplink grant is designated as the prioritized uplink grant. Other overlapping uplink grants (if any) are designated as downgraded uplink grants.

[0107] Figure 5 is another schematic diagram of the method for determining logical channel priority by the media access control entity according to Embodiment 1 of this application. As shown in Figure 5, in operation 301a, when the media access control (MAC) entity is configured with logical channel-based priority, for each uplink grant submitted to an entity that submits a Hybrid Automatic Repeat Request (HARQ), and the physical uplink shared channel (PUSCH) associated with the uplink grant can be transmitted at the lower layer, the media access control entity performs the following operations:

[0108] Operation 501: If the uplink grant is a configured uplink grant, then:

[0109] Operation 502: If, within the same bandwidth portion (BWP), the uplink grant does not overlap in duration with another un-de-prioritized configured uplink grant's Physical Uplink Shared Channel (PUSCH), and its priority is higher than the uplink grant's priority; and

[0110] Operation 503: If, within the same bandwidth portion (BWP), the uplink grant does not overlap with the duration of a physical uplink shared channel for an uplink grant that has not been downgraded and is for a configured scheduled radio network temporary identifier (CS-RNTI) with new data indicated as the second value (NDI=0) or a cell radio network temporary identifier (C-RNTI), and its priority is higher than or equal to the priority of that uplink grant; and

[0111] Operation 504: If the uplink grant does not overlap with the physical uplink control channel (PUCCH) resource of a scheduling request transmission that has not been downgraded, and based on the configuration, scheduling request, and uplink grant not allowing simultaneous transmission, the default priority of the logical channel that triggered the scheduling request is higher than the priority of the uplink grant, then:

[0112] Operation 505: Determine the uplink grant as the priority uplink grant. Determine other overlapping uplink grants (if any) as downlink grants.

[0113] Figure 6 is a schematic diagram of a method for determining logical channel priority by a media access control entity according to Embodiment 1 of this application.

[0114] Operation 301b: For a Media Access Control (MAC) entity configured with logical channel-based priority, the priority of SR transmissions is determined by the priority of the logical channel that triggered the scheduling request (and other conditions).

[0115] As shown in Figure 6, in operation 301b, when the Media Access Control (MAC) entity is configured with logical channel-based prioritization, the MAC entity performs the following operations for scheduling request configurations for pending scheduling requests (SRs):

[0116] Operation 601: If the PUCCH resource used for SR transmission timing does not overlap with the PUSCH duration of an uplink grant received in a random access response message, does not overlap with the PUSCH duration of an uplink grant for a temporary C-RNTI, and does not overlap with the PUSCH duration of the payload of message A (MsgA); and

[0117] Operation 602: If the PUCCH resource used for SR transmission timing overlaps with any other Uplink Shared Channel (UL-SCH) resource, and the physical layer can transmit the SR on a valid PUCCH resource for SR, and the default priority of the logical channel triggering the SR is higher than the uplink grant priority of any UL-SCH resource that has not been downgraded, and based on configuration, scheduling requests and uplink grants are not allowed to be transmitted simultaneously, then:

[0118] Operation 603: Determine the SR transport as the priority SR transport and determine other overlapping uplink grants (if any) as down-priority uplink grants, except for uplink grants that are configured to be transported simultaneously.

[0119] Method 2:

[0120] Figure 7 is another schematic diagram of the method for supporting logical channel priority according to Embodiment 1 of this application. As shown in Figure 7, when determining the priority of the logical channel, the terminal device 102 can perform the following operations:

[0121] Operation 701: For a logical channel that includes data multiplexed to the Media Access Control layer Protocol Data Unit (MAC PDU) and is configured with the first parameter, the priority of the logical channel is the priority used when the data of the logical channel is multiplexed;

[0122] Operation 702: For logical channels that include reusable data and are configured with a first parameter, the logical channel priority uses the default priority.

[0123] In Operation 701, the priority used when logical channel data is multiplexed is the priority used by the logical channel during resource allocation in the logical channel priority processing procedure. If the logical channel uses the priority represented by the first parameter during resource allocation, then the logical channel's priority uses the priority represented by the first parameter; otherwise, the default priority is used. Logical channel data multiplexing can also be referred to as data assembly, MAC PDU generation, MAC PDU assembly, etc. The priority used when logical channel data is multiplexed can also be called the priority used by the multiplexing and assembly entities.

[0124] The priority represented by the first parameter can be used in the first round of resource allocation, in both the first and second rounds of resource allocation, or in either the first or second round of resource allocation.

[0125] The first round of resource allocation refers to the uplink grant, which allocates resources to logical channels with Bj>0 to satisfy the priority bit rate of the logical channels. Here, Bj is a logical channel variable, representing the number of tokens currently available in the token bucket. The second round of resource allocation refers to the allocation of resources to logical channels if there are still remaining resources after the first round of resource allocation.

[0126] Similar to operation 301a in Method 1, the uplink grant priority is determined for MAC entities configured with lch-BasedPrioritization. Data multiplexing from a logical channel to a MAC PDU means the MAC PDU to be transmitted already exists in the HARQ buffer; this could be new transmitted data or retransmitted data. In this case, the logical channel priority can use the logical channel priority used during packet assembly. This priority can be recorded by the terminal device (UE) during resource allocation to determine the uplink grant priority. If there is available data on the logical channel that can be multiplexed to a MAC PDU, it means the MAC PDU to be transmitted is not in the HARQ buffer, meaning the MAC PDU packet assembly is not yet complete. In this case, it is not necessary to determine whether the first parameter will be used in the future; the default priority of the logical channel can be used directly, thereby reducing the complexity of UE operations.

[0127] Method 3:

[0128] Figure 8 is another schematic diagram of the method for supporting logical channel priority according to Embodiment 1 of this application. As shown in Figure 8, when determining the priority of the logical channel, the terminal device 102 can perform the following operations:

[0129] Operation 801: For a logical channel that includes data multiplexed to the Media Access Control layer Protocol Data Unit (MAC PDU) and / or reusable data, and / or a logical channel that triggers a scheduling request, if the logical channel is configured with a first parameter and includes first data, the priority of the logical channel is the priority represented by the first parameter; otherwise, the priority of the logical channel is the default priority.

[0130] In operation 801, for a logical channel that includes data multiplexed to a MAC PDU, the data multiplexed to the MAC PDU is stored in a HARQ buffer, and the terminal device (UE) determines the priority of the logical channel by determining whether this data is the first data.

[0131] The timing for a terminal device (UE) to determine whether a logical channel contains the first data can be when determining the priority of an uplink grant or scheduling request, or it can be determined by the terminal device (UE) itself.

[0132] Similar to operation 301a in Method 1, the priority of uplink grant and / or scheduling requests is determined for MAC entities configured with lch-BasedPrioritization.

[0133] Method 4:

[0134] Figure 9 is another schematic diagram of the method for supporting logical channel priority in Embodiment 1 of this application. As shown in Figure 9, when determining the priority of the logical channel in the uplink grant, the terminal device 102 can perform operation 701 in method 2, and can also perform the following operations:

[0135] Operation 901: For a logical channel that includes multiplexable data and is configured with a first parameter, if the first data is transmitted in the first symbol time of the Physical Uplink Shared Channel (PUSCH) corresponding to the uplink grant, then the priority of the logical channel shall be the priority represented by the first parameter; otherwise, the priority of the logical channel shall be the default priority.

[0136] In Operation 901, for logical channels containing multiplexable data, where the MAC PDU has not yet been generated, the future PUSCH time can be used as a reference time to determine whether the logical channel contains the first data. This means predicting whether the data in the multiplexed logical channel will be the first data during PUSCH transmission. Specifically, at the first symbol time of the PUSCH transmission corresponding to the uplink grant, if the minimum remaining value of the discard timer running in all buffered packet data aggregation protocol layer service data units (PDCP SDUs) in the logical channel is less than a first threshold, then the logical channel priority uses the value of the first parameter; otherwise, the default priority is used.

[0137] To reduce the complexity of UE implementation, a unified method can be used to determine the priority of uplink grants. For example, for logical channels configured with a first parameter that have data multiplexed to a MAC PDU, the method of operation 901 (replacing operation 701) is also used. That is, if the first data is contained in the first symbol time of the transmission on the Physical Uplink Shared Channel (PUSCH) corresponding to the uplink grant, then the priority of the logical channel uses the priority represented by the first parameter; otherwise, the priority of the logical channel uses the default priority.

[0138] Similar to operation 301a in Method 1, the priority of uplink grant and / or scheduling requests is determined for MAC entities configured with lch-BasedPrioritization.

[0139] Method 5:

[0140] Figure 10 is another schematic diagram of the method for supporting logical channel priority according to Embodiment 1 of this application. As shown in Figure 10, when the logical channel priority that triggers the scheduling request is determined, the terminal device 102 performs the following operations:

[0141] Operation 1001: When the logical channel is configured with the first parameter and includes the first data when the logical channel triggers the scheduling request, the priority of the logical channel uses the priority set by the first parameter of the logical channel; otherwise, the priority of the logical channel uses the default priority.

[0142] In operation 1001, when determining the priority of the logical channel that triggers the scheduling request, the timing for determining whether the logical channel contains the first data is when the logical channel triggers the scheduling request.

[0143] Similar to operation 301a in method 1, the priority of scheduling requests is determined for MAC entities configured with lch-BasedPrioritization.

[0144] Example 2

[0145] Example 2 is an enhancement to the Hybrid Automatic Repeat Request (HARQ) process selection process.

[0146] In the current network configuration of communication systems (e.g., New Radio), resource configuration methods can be adopted using either configured grant (CG) for licensed spectrum or configured grant (CG) for unlicensed spectrum, for example, indicated by a configured grant retransmission timer (cgRetransmissionTimer). To better support URLLC services, the network can be configured for the terminal equipment (UE) to simultaneously use the configured grant retransmission timer (cgRetransmissionTimer) and an enhanced UE-internal conflict resource priority handling mechanism.

[0147] To select Hybrid Automatic Repeat Request (HARQ) processes within a configuration grant, the network can configure intraCG-Prioritization for Media Access Control (MAC) entities. That is, when both intraCG-Prioritization and logical channel-based prioritization are configured, the UE can select the HARQ process to transmit on that configuration grant (CG) resource based on the priority of the HARQ process.

[0148] The URLLC-related parameters and configurations mentioned above can also be configured for XR services. When selecting the Hybrid Automatic Repeat Request (HARQ) process in the Configuration Grant (CG), the priority of the logical channel corresponding to the HARQ process is required. Since the logical channel indicated by the first parameter has two priority parameters, it is necessary to specify which logical channel priority parameter to use when determining the priority of the HARQ process.

[0149] In Embodiment 2, the method for determining the priority of each logical channel includes any one of the following methods 6, 7, 8 and 9.

[0150] Method 6:

[0151] Figure 11 is a schematic diagram of a method for supporting logical channel priorities according to Embodiment 2 of this application. As shown in Figure 11, the method for determining the priority of each logical channel multiplexed to or capable of being multiplexed to the corresponding resource includes:

[0152] Operation 1101: When determining the logical channel priority of the Hybrid Automatic Repeat Request (HARQ) process, use the default priority for each logical channel configured with the first parameter.

[0153] For example, in operation 1101, the uplink authorization receiving process can be enhanced through operation 1101a.

[0154] Operation 1101a: When determining the priority of a Hybrid Automatic Repeat Request (HARQ) process, for a Media Access Control (MAC) entity configured with intraCG-Prioritization, terminal device 102 selects the identifier (ID) of the highest priority Hybrid Automatic Repeat Request (HARQ) process.

[0155] In Operation 1101a, the priority of the Hybrid Automatic Repeat Request (HARQ) process is determined by the highest default priority among one or more logical channels that have Protocol Data Units (MAC PDUs) multiplexed to the Media Access Control layer (i.e., the MAC PDU to be transmitted is already stored in the HARQ buffer) or have available data multiplexed to the Media Access Control layer (i.e., the MAC PDU to be transmitted is not stored in the HARQ buffer).

[0156] One or more logical channels with available data multiplexed to Media Access Control Protocol Data Units (MAC PDUs) are determined by mapping constraints during the logical channel selection process. Hybrid Automatic Repeat Request (HARQ) processes where data without a logical channel is multiplexed to or can be multiplexed to MAC PDUs have a lower priority than those where data with any logical channel is multiplexed to or can be multiplexed to MAC PDUs.

[0157] Method 7:

[0158] Figure 12 is another schematic diagram of the method for supporting logical channel priority according to Embodiment 2 of this application. As shown in Figure 12, when determining the priority of the HARQ process, the terminal device 102 performs the following operations:

[0159] Operation 1201: For a logical channel that includes data multiplexed to the Media Access Control layer Protocol Data Unit (MAC PDU) and is configured with the first parameter, the priority of the logical channel is the priority used when the data of the logical channel is multiplexed.

[0160] Operation 1202: For logical channels that include reusable data and are configured with the first parameter, the logical channel priority uses the default priority.

[0161] In operation 1201, the priority used when data is reused and the priority at which data can (or will be) reused are the same as in Example 1.

[0162] Similar to operation 1101a in method 6, the priority of the HARQ process is determined for MAC entities configured with intraCG-Prioritization.

[0163] Method 8:

[0164] When determining the priority of a HARQ process, for a logical channel containing multiplexed or reusable data, if the logical channel is configured with a first parameter and contains first data, then the priority of the logical channel is the priority represented by the first parameter; otherwise, the priority of the logical channel is the default priority. This operation can refer to operation 801 of method 3 above.

[0165] For logical channels containing data that has been multiplexed to MAC PDUs, these data already exist in the HARQ cache, and the above judgment can still be made by determining whether these data are the first data.

[0166] The timing for determining whether a logical channel contains the first data can be either when determining the priority of the HARQ process or when the specific timing is determined by the UE implementation.

[0167] Similar to operation 1101a in method 6, the priority of the HARQ process is determined for MAC entities configured with intraCG-Prioritization.

[0168] Method 9:

[0169] Figure 13 is another schematic diagram of the method for supporting logical channel priority in Embodiment 2 of this application. As shown in Figure 13, when determining the priority of the logical channel in the HARQ process, the terminal device 102 can perform operation 1201 in method 7, and can also perform the following operations:

[0170] Operation 1301: For a logical channel that includes reusable data and is configured with a first parameter, if the first data is transmitted in the first symbol time of the Physical Uplink Shared Channel (PUSCH) corresponding to the configuration uplink grant of the HARQ process, then the priority of the logical channel shall be the priority represented by the first parameter; otherwise, the priority of the logical channel shall be the default priority.

[0171] In operation 1301, the method for determining whether the data of the multiplexed logical channel is the first data is the same as the method for determining it in method 4 of embodiment 1.

[0172] To reduce the complexity of UE implementation, a unified method can be used to determine the priority of HARQ processes. For example, for logical channels configured with a first parameter that have data multiplexed to a MAC PDU, the method of operation 1301 (replacing operation 1201) is also used. That is, if the first data is contained in the first symbol time of the transmission on the Physical Uplink Shared Channel (PUSCH) corresponding to the uplink grant of the HARQ process, then the priority of the logical channel uses the priority represented by the first parameter; otherwise, the priority of the logical channel uses the default priority.

[0173] Similar to operation 1101a in method 6, the priority of the HARQ process is determined for MAC entities configured with intraCG-Prioritization.

[0174] Example 3

[0175] Example 3 is an enhancement to the regular cache status report (BSR) triggering process.

[0176] When triggering a regular BSR, the priority of the logical channel needs to be considered. The BSR triggering process can be enhanced by using the default logical channel priority when the first parameter is configured for the logical channel.

[0177] Method 10:

[0178] Enhancements to the Cache Status Report (BSR) triggering process include:

[0179] Operation 1401: For active cell groups, trigger a regular cache status report (BSR) in the following situations:

[0180] Uplink data in a logical channel belonging to a logical channel group becomes available to the Media Access Control (MAC) layer entity, and the uplink data belongs to a logical channel whose default priority is higher than the default priority of any logical channel belonging to any logical channel group containing available uplink data; or none of the logical channels belonging to the logical channel group have available uplink data.

[0181] Example 4

[0182] New UE radio access capabilities can be added to terminal device 102, indicating whether the priority configured by the first parameter is supported during priority processing within the UE and / or priority processing within the configuration authorization, i.e., using the methods of Embodiment 1 and Embodiment 2.

[0183] The terminal device can use a first capability parameter to indicate whether it supports applying the priority configured by the first parameter during priority processing within the UE and priority processing within the configuration authorization. The first capability parameter can also be divided into two (sub)capability parameters, indicating whether it supports applying the priority configured by the first parameter during priority processing within the UE and whether it supports applying the priority configured by the first parameter during priority processing within the configuration authorization, respectively.

[0184] The first capability parameter can be used as a UE-based (per-UE) capability parameter, meaning the granularity of the parameter applies to the entire UE. This capability parameter does not distinguish between the usage scenarios of Time Division Duplexing (TDD) and Frequency Division Duplexing (FDD), nor does it distinguish between the usage scenarios of the first frequency band (Frequency Range 1, FR1) and the second frequency band (FR2).

[0185] The aforementioned UE wireless access capability parameters can be used as MAC layer capability parameters, reported by the terminal device to the network device, so that the network device can configure and manage the terminal device.

[0186] Second aspect of the embodiments

[0187] This application provides an apparatus for supporting logical channel priority. This apparatus may be, for example, a terminal device, or one or more components or parts configured within the terminal device. It corresponds to the method applied to the terminal device side in the first aspect embodiment, and the content identical to that in the first aspect embodiment will not be repeated.

[0188] Figure 15 is a schematic diagram of an apparatus supporting logical channel priority according to an embodiment of this application. As shown in Figure 15, the apparatus 1500 supporting logical channel priority includes a configuration unit 1501 and a determination unit 1502. The configuration unit 1501 configures a first parameter and a default priority for the logical channel of the Media Access Control (MAC) layer entity of the terminal device 102. The first parameter is used to set the priority of the logical channel containing first data. The determination unit 1502 is used to determine the priority of the logical channel.

[0189] Configuration unit 1501 can configure the first parameter via Radio Resource Control (RRC) signaling, wherein the remaining time of the Service Data Unit (PDCP SDU) of the Packet Data Convergence Protocol layer associated with the first data is less than a first threshold.

[0190] In some embodiments, the larger the value of the first parameter, the lower the priority of the logical channel containing the first data.

[0191] In some embodiments, the logical channel containing the first data has a higher priority than the default priority of the logical channel.

[0192] In some embodiments, when determining the logical channel priority of uplink grant and / or determining the logical channel priority of triggering scheduling request and / or determining the logical channel priority of Hybrid Automatic Repeat Request (HARQ) process, the determining unit 1502 uses a default priority for each logical channel configured with a first parameter.

[0193] In some embodiments, for a Media Access Control (MAC) layer entity configured with logical channel-based prioritization, determining unit 1502 determines the priority of uplink grant based on the highest default priority among one or more logical channels multiplexed to the MAC layer Protocol Data Unit (MAC PDU) or MAC PDUs with available data multiplexed to the MAC layer.

[0194] In some embodiments, one or more logical channels that are multiplexed to a Media Access Control Protocol Data Unit (MAC PDU) or have available data multiplexed to a MAC PDU are determined by mapping constraints during the logical channel selection process.

[0195] In some embodiments, when the Media Access Control (MAC) entity is configured with logical channel-based prioritization, for each uplink grant submitted to an entity that submits a Hybrid Automatic Repeat Request (HARQ), and the associated Physical Uplink Shared Channel (PUSCH) of the uplink grant can be transmitted at lower layers, the MAC entity performs the following operations:

[0196] If the uplink grant is for a configured Scheduled Radio Network Temporary Identifier (CS-RNTI) and the new data indication is the first value (NDI=1), or for a Cell Radio Network Temporary Identifier (C-RNTI), then:

[0197] If, within the same bandwidth portion (BWP), the uplink grant does not overlap in duration with the physical uplink shared channel (PUSCH) of a de-prioritized configured uplink grant, and its priority is higher than the uplink grant's priority; and

[0198] If the uplink grant does not overlap with the physical uplink control channel (PUCCH) resource of a scheduling request transmission that has not been downgraded, and based on the fact that simultaneous transmission of the configuration, scheduling request, and uplink grant is not allowed, and the default priority of the logical channel that triggered the scheduling request is higher than the priority of the uplink grant, then:

[0199] Unit 1502 determines the uplink grant as an uplink grant with priority.

[0200] In some embodiments, when the Media Access Control (MAC) entity is configured with logical channel-based prioritization, for each uplink grant submitted to an entity that submits a Hybrid Automatic Repeat Request (HARQ), and the associated Physical Uplink Shared Channel (PUSCH) of the uplink grant can be transmitted at lower layers, the MAC entity performs the following operations:

[0201] If the uplink grant is a configured uplink grant, then:

[0202] If, within the same bandwidth portion (BWP), the duration of the uplink grant does not overlap with that of another un-de-prioritized configured uplink grant (PUSCH), and its priority is higher than that of the uplink grant;

[0203] If, within the same bandwidth portion (BWP), the uplink grant does not overlap with the duration of a physical uplink shared channel for an uplink grant that has not been downgraded and is for a configured scheduled radio network temporary identifier (CS-RNTI) with new data indicated as the second value (NDI=0) or a cell radio network temporary identifier (C-RNTI), and its priority is higher than or equal to the priority of that uplink grant; and

[0204] If the uplink grant does not overlap with the physical uplink control channel (PUCCH) resource of a scheduling request transmission that has not been downgraded, and based on the fact that simultaneous transmission of the configuration, scheduling request, and uplink grant is not allowed, and the default priority of the logical channel that triggered the scheduling request is higher than the priority of the uplink grant, then:

[0205] Unit 1502 determines the uplink authorization as the priority uplink authorization.

[0206] In some embodiments, when determining the priority of a Hybrid Automatic Repeat Request (HARQ) process, for a Media Access Control (MAC) entity configured with intraCG-Prioritization, configuration unit 1501 selects the identifier (ID) of the highest priority HARQ process, wherein determination unit 1502 determines the priority of the HARQ process based on the highest default priority among one or more logical channels multiplexed to the Media Access Control layer Protocol Data Unit (MAC PDU) or Protocol Data Unit (MAC PDU) with available data multiplexed to the Media Access Control layer.

[0207] In some embodiments, one or more logical channels that are multiplexed to a Media Access Control Protocol Data Unit (MAC PDU) or have available data multiplexed to a MAC PDU are determined by mapping constraints during the logical channel selection process.

[0208] In some embodiments, for an active cell group, a regular buffer status report (BSR) is triggered in the following situations:

[0209] Uplink data in a logical channel belonging to a logical channel group becomes available to the Media Access Control (MAC) layer entity, and the uplink data belongs to a logical channel whose default priority is higher than the default priority of any logical channel containing available uplink data belonging to any logical channel group; or

[0210] None of the logical channels belonging to the logical channel group have available uplink data.

[0211] In some embodiments, when determining the priority of a logical channel, for a logical channel that includes data multiplexed to the Media Access Control layer Protocol Data Unit (MAC PDU) and is configured with a first parameter, the priority of the logical channel is the priority used when the data of the logical channel is multiplexed.

[0212] In some embodiments, when determining the priority of a logical channel, for a logical channel that includes multiplexable data and is configured with a first parameter, the default priority is used.

[0213] In some embodiments, when determining the priority of a logical channel in an uplink grant, for a logical channel that includes multiplexable data and is configured with a first parameter, if the first data is contained in the first symbol time of the PUSCH transmission corresponding to the uplink grant, then the priority of the logical channel uses the priority represented by the first parameter; otherwise, the priority of the logical channel uses the default priority.

[0214] In some embodiments, when determining the priority of a logical channel in a HARQ process, for a logical channel that includes reusable data and is configured with a first parameter, if the first data is contained in the first symbol time of the PUSCH transmission corresponding to the configuration uplink grant of the HARQ process, then the priority of the logical channel uses the priority represented by the first parameter; otherwise, the priority of the logical channel uses the default priority.

[0215] In some embodiments, the logical channel priority is used to determine the uplink grant priority, and the MAC entity configures logical channel-based prioritization; and / or

[0216] The priority of the logical channel is used to determine the priority of the HARQ process, and the MAC entity is configured with intraCG-Prioritization.

[0217] In some embodiments, the priority used when data in a logical channel is multiplexed is the priority used by the logical channel during the resource allocation process of the logical channel priority processing procedure.

[0218] If the logical channel uses the priority represented by the first parameter during resource allocation, then the priority of the logical channel will use the priority represented by the first parameter; otherwise, the default priority will be used.

[0219] In some embodiments, the priority represented by the first parameter is used in the first round of resource allocation, in both the first and second rounds of resource allocation, or in either the first or second round of resource allocation.

[0220] In some embodiments, when determining the priority of a logical channel, for a logical channel that includes data multiplexed to the Media Access Control layer Protocol Data Unit (MAC PDU) and / or reusable data, and / or a logical channel that triggers a scheduling request, if the logical channel is configured with a first parameter and includes first data, the priority of the logical channel is the priority represented by the first parameter; otherwise, the priority of the logical channel is the default priority.

[0221] In some embodiments, when determining the priority of the logical channel that triggers the scheduling request, if the logical channel is configured with a first parameter and includes first data when triggering the scheduling request, the priority of the logical channel uses the priority set by the first parameter of the logical channel; otherwise, the priority of the logical channel uses the default priority.

[0222] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0223] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The device 1500 may also include other components or modules; for details regarding these components or modules, please refer to related technologies.

[0224] Furthermore, for simplicity, Figure 15 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0225] Third aspect of the embodiments

[0226] This application provides a communication system, including a terminal device and a network device.

[0227] For example, the structure of the communication system can be seen with reference to FIG1. ​​As shown in FIG1, the communication system 100 includes network device 101 and terminal devices 102 and 103. At least one of terminal device 102 and terminal device 103 may have the configuration of the electronic device shown in FIG16.

[0228] Figure 16 is a schematic block diagram of the electronic device. As shown in Figure 16, the electronic device 1600 may include a processor 1610 and a memory 1620; the memory 1620 is coupled to the processor 1610. The memory 1620 can store various data; in addition, it also stores an information processing program 1630, and executes the program 1630 under the control of the processor 1610 to receive or send various information.

[0229] In one embodiment, processor 1610 may be configured to perform the method described in the first aspect embodiment.

[0230] Furthermore, as shown in Figure 16, the electronic device 1600 may also include a transceiver 1640 and an antenna 1650, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that the electronic device 1600 does not necessarily include all the components shown in Figure 16; in addition, the electronic device 1600 may also include components not shown in Figure 16, which can be referred to in the prior art.

[0231] This application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to perform the method for supporting logical channel priority as described in the first aspect embodiment.

[0232] This application also provides a storage medium storing a computer program, wherein the computer program causes a terminal device to execute the method for supporting logical channel priority as described in the first aspect embodiment.

[0233] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, etc.

[0234] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.

[0235] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.

[0236] One or more and / or one or more combinations of functional blocks described in the accompanying drawings can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more and / or one or more combinations of functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0237] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.

[0238] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:

[0239] 1. A method for supporting logical channel priority, applied to a terminal device, the method comprising:

[0240] The logical channel of the Media Access Control (MAC) entity of the terminal device is configured with a first parameter and a default priority, wherein the first parameter is used to set the priority of the logical channel containing first data; and

[0241] Determine the priority of the logical channel.

[0242] in,

[0243] The first parameter is configured via Radio Resource Control (RRC) signaling.

[0244] The remaining time of the Service Data Unit (PDCP SDU) of the Packet Data Convergence Protocol layer associated with the first data is less than the first threshold.

[0245] 2. The method as described in Appendix 1, wherein,

[0246] When the Media Access Control (MAC) entity is configured with logical channel-based prioritization, for scheduling request configurations targeting pending scheduling requests (SRs), the MAC entity performs the following operations:

[0247] If the PUCCH resource used for SR transmission timing does not overlap with the PUSCH duration of an uplink grant received in a random access response message, does not overlap with the PUSCH duration of an uplink grant for a temporary C-RNTI, and does not overlap with the PUSCH duration of the payload of message A (MsgA); and

[0248] If the PUCCH resource used for SR transmission overlaps with any other Uplink Shared Channel (UL-SCH) resource, and the physical layer can transmit the SR on a valid PUCCH resource for SR, and the default priority of the logical channel triggering the SR is higher than the uplink grant priority of any UL-SCH resource that has not been downgraded, and based on configuration, scheduling requests and uplink grants are not allowed to be transmitted simultaneously, then:

[0249] The SR transmission is determined as the preferred SR transmission.

[0250] 3. The method as described in Appendix 1, wherein,

[0251] The terminal device reports a first capability parameter to the network device, indicating whether it supports applying the priority configured by the first parameter during priority processing within the UE and / or priority processing within the configuration authorization.

[0252] The first capability parameter is the MAC layer capability parameter in the UE radio access capability parameters.

[0253] 4. A method for supporting logical channel priority, applied to a network device, the method comprising:

[0254] The network device configures a first parameter based on a logical channel for the Media Access Control (MAC) entity of the terminal device, the first parameter being used to set the priority of the logical channel containing first data; and

[0255] The network device receives the first capability parameters sent by the terminal device.

[0256] in,

[0257] The first parameter is configured via Radio Resource Control (RRC) signaling.

[0258] The remaining time of the Service Data Unit (PDCP SDU) of the Packet Data Convergence Protocol layer associated with the first data is less than the first threshold.

[0259] 5. A terminal device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the method as described in any one of Appendices 1 to 3.

[0260] 6. A network device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the method as described in Appendix 4.

[0261] 7. A computer program product comprising at least a computer program that, when executed by a processor, causes a terminal device to perform the method as described in any one of Appendix 1 to Appendix 3, or, when executed by a processor, causes a network device to perform the method as described in Appendix 4.

Claims

1. An apparatus supporting logical channel priority, applied to a terminal device, the apparatus comprising: A configuration unit configures a first parameter and a default priority for a logical channel of the Media Access Control (MAC) entity of the terminal device, wherein the first parameter is used to set the priority of the logical channel containing first data; as well as The determining unit determines the priority of the logical channel. in, The first parameter is configured via Radio Resource Control (RRC) signaling. The remaining time of the Service Data Unit (PDCP SDU) of the Packet Data Convergence Protocol layer associated with the first data is less than the first threshold.

2. The apparatus of claim 1, wherein, The larger the value of the first parameter, the lower the priority of the logical channel containing the first data.

3. The apparatus of claim 1, wherein, The logical channel containing the first data has a higher priority than the default priority of the logical channel.

4. The apparatus of claim 1, wherein, When determining the logical channel priority for uplink granting and / or the logical channel priority for triggering scheduling requests and / or the logical channel priority for Hybrid Automatic Repeat Request (HARQ) processes, the determining unit uses the default priority for each logical channel configured with the first parameter.

5. The apparatus of claim 4, wherein, For the Media Access Control (MAC) entity configured with logical channel-based prioritization, the uplink grant priority is determined by the highest default priority among one or more logical channels that are multiplexed to the MAC layer or have available data that can be multiplexed to the MAC layer.

6. The apparatus of claim 5, wherein, The availability of data that can be multiplexed to a Media Access Control Protocol Data Unit (MAC PDU) is determined by mapping constraints during the logical channel selection process.

7. The apparatus of claim 5, wherein, When the Media Access Control (MAC) entity is configured with logical channel-based prioritization, for each uplink grant submitted to an entity that submits a Hybrid Automatic Repeat Request (HARQ), and the associated Physical Uplink Shared Channel (PUSCH) of the uplink grant can be transmitted at lower layers, the MAC entity performs the following operations: If the uplink grant is for a configured Scheduled Radio Network Temporary Identifier (CS-RNTI) and the new data indication is a first value (NDI=1), or for a Cell Radio Network Temporary Identifier (C-RNTI), then: If, within the same bandwidth portion (BWP), the uplink grant does not overlap with the duration of a physical uplink shared channel (PUSCH) of a configured uplink grant that has not been de-prioritized, and its priority is higher than that of the uplink grant; as well as If the uplink grant does not overlap with the physical uplink control channel (PUCCH) resource of a scheduling request transmission that has not been downgraded, and based on the fact that simultaneous transmission of the scheduling request and uplink grant is not allowed, and the default priority of the logical channel that triggered the scheduling request is higher than the priority of the uplink grant, then: The determining unit determines the uplink grant as the priority uplink grant.

8. The apparatus of claim 5, wherein, When the Media Access Control (MAC) entity is configured with logical channel-based prioritization, for each uplink grant submitted to an entity that submits a Hybrid Automatic Repeat Request (HARQ), and the associated Physical Uplink Shared Channel (PUSCH) of the uplink grant can be transmitted at lower layers, the MAC entity performs the following operations: If the uplink grant is a configured uplink grant, then: If, within the same bandwidth portion (BWP), the uplink grant does not overlap with the duration of the physical uplink shared channel (PUSCH) of another un-de-prioritized configured uplink grant, and its priority is higher than that of the uplink grant; If, within the same bandwidth portion (BWP), the uplink grant does not overlap with the duration of a physical uplink shared channel for an uplink grant that has not been downgraded and is for a configured scheduled radio network temporary identifier (CS-RNTI) with new data indicated as a second value (NDI=0) or a cell radio network temporary identifier (C-RNTI), and its priority is higher than or equal to the priority of that uplink grant; as well as If the uplink grant does not overlap with the physical uplink control channel (PUCCH) resource of a scheduling request transmission that has not been downgraded, and based on the fact that simultaneous transmission of the scheduling request and uplink grant is not allowed, and the default priority of the logical channel that triggered the scheduling request is higher than the priority of the uplink grant, then: The determining unit determines the uplink grant as the priority uplink grant.

9. The apparatus of claim 4, wherein, When determining the priority of a Hybrid Automatic Repeat Request (HARQ) process, for the Media Access Control (MAC) entity configured with intraCG-Prioritization, the configuration unit selects the identifier (ID) of the highest-priority HARQ process, wherein the priority of the HARQ process is determined by the highest default priority among one or more logical channels that are multiplexed to the MAC layer or have available data that can be multiplexed to the MAC layer.

10. The apparatus of claim 9, wherein, The one or more logical channels with available data that can be multiplexed to Media Access Control Protocol Data Units (MAC PDUs) are determined by mapping constraints during the logical channel selection process.

11. The apparatus of claim 1, wherein, For active cell groups, a regular cache status report (BSR) is triggered in the following situations: Uplink data in a logical channel belonging to a logical channel group becomes available to the Media Access Control (MAC) entity, and the uplink data belongs to a logical channel whose default priority is higher than the default priority of any logical channel containing available uplink data belonging to any logical channel group. or There is no available uplink data on any of the logical channels belonging to the logical channel group.

12. The apparatus of claim 1, wherein, When determining the priority of the logical channel, For a logical channel that includes data multiplexed to the Media Access Control layer Protocol Data Unit (MAC PDU) and is configured with a first parameter, the priority of the logical channel is the priority used when the data of the logical channel is multiplexed.

13. The apparatus of claim 1, wherein When determining the priority of the logical channel, For logical channels that include reusable data and are configured with a first parameter, the priority of the logical channel uses the default priority.

14. The apparatus of claim 1, wherein When determining the priority of the logical channel mentioned in the uplink grant, For a logical channel that includes reusable data and is configured with a first parameter, if the first data is contained in the first symbol time of the PUSCH transmission corresponding to the uplink grant, then the priority of the logical channel uses the priority represented by the first parameter; otherwise, the priority of the logical channel uses the default priority.

15. The apparatus of claim 1, wherein When determining the priority of the logical channel in the HARQ process, For a logical channel that includes reusable data and is configured with a first parameter, if the first symbol time of the PUSCH transmission corresponding to the configuration uplink grant of the HARQ process contains the first data, then the priority of the logical channel uses the priority represented by the first parameter; otherwise, the priority of the logical channel uses the default priority.

16. The apparatus of claim 12 or 13, wherein, The priority of the logical channel is used to determine the priority of uplink grant, and the MAC entity is configured with logical channel-based priority processing; and / or The priority of the logical channel is used to determine the priority of the HARQ process, and the MAC entity is configured with intraCG-Prioritization.

17. The apparatus of claim 12, wherein, The priority used when data in the logical channel is multiplexed is the priority used by the logical channel during the resource allocation process of the logical channel priority processing. If the logical channel uses the priority represented by the first parameter during the resource allocation process, then the priority of the logical channel uses the priority represented by the first parameter; otherwise, the default priority is used.

18. The apparatus of claim 17, wherein, The priority represented by the first parameter is used in the first round of resource allocation, in both the first and second rounds of resource allocation, or in either the first or second round of resource allocation.

19. The apparatus of claim 1, wherein, When determining the priority of the logical channel, For logical channels that include data multiplexed to the Media Access Control layer Protocol Data Units (MAC PDUs) and / or reusable data, and / or logical channels that trigger scheduling requests, If the logical channel is configured with the first parameter and includes the first data, the priority of the logical channel uses the priority represented by the first parameter; otherwise, the priority of the logical channel uses the default priority.

20. The apparatus of claim 1, wherein, When the priority of the logical channel that triggers the scheduling request is determined, if the logical channel is configured with the first parameter and includes the first data when triggering the scheduling request, the priority of the logical channel uses the priority set by the first parameter of the logical channel; otherwise, the priority of the logical channel uses the default priority.

Images