Method and device for determining channel access priority level, equipment and medium

Abstract

The invention discloses a channel access priority level determination method and device, equipment, a medium and a program product, and belongs to the field of communication. The method is executed by a terminal, and the method comprises the following steps: determining a CAPC of a first non-standard QoS flow; based on the CAPC of the first non-standard QoS flow, determining the CAPC of an associated radio bearer of the first non-standard QoS flow; and based on the CAPC of the first non-standard QoS flow, determining the CAPC of the associated RLC SDU / PDU of the first non-standard QoS flow. According to the method, under the condition that the network does not provide the CAPC of the first non-standard QoS flow, the terminal can determine the CAPC, and the associated radio bearer of the first non-standard QoS flow and the CAPC of the associated RLC SDU / PDU, thereby executing tasks such as LBT monitoring and data packet assembly.

Description

Method, device, equipment and medium for determining channel access priority level Technical Field

[0001] Embodiments of the present application relate to the field of communications, and in particular to a method, apparatus, device, medium, and program product for determining a channel access priority level. Background Art

[0002] During sidelink communication between user equipment (UE) and other terminals, the UE needs to perform tasks such as listen before talk (LBT) monitoring and data packet assembly according to the channel access priority classes (CAPC) of the radio bearer (RB).

[0003] For a UE with a standard Quality of Service flow (QoS flow), the network may provide relevant CAPCs, and the UE performs tasks according to the relevant CAPCs.

[0004] However, for UEs with non-standard QoS flows, the network is unaware of the non-standard QoS flows and cannot provide relevant CAPCs, so the UE cannot perform tasks.

[0005] Summary of the Invention

[0006] This application provides a method, apparatus, device, medium, and program product for determining a channel access priority level. The technical solution at least includes:

[0007] According to one aspect of an embodiment of the present application, a method for determining a channel access priority level is provided, the method being performed by a terminal, the method including:

[0008] A CAPC for the first non-standard QoS flow is determined.

[0009] According to another aspect of an embodiment of the present application, a method for determining a channel access priority level is provided, the method being performed by a terminal, the method comprising:

[0010] Based on the CAPC of the first non-standard QoS flow, a CAPC of an associated radio bearer of the first non-standard QoS flow is determined.

[0011] According to another aspect of an embodiment of the present application, a method for determining a channel access priority level is provided, the method being performed by a terminal, the method comprising:

[0012] Based on the CAPC of the first non-standard QoS flow, a CAPC of an associated Radio Link Control Service Data Unit / Protocol Data Unit (RLC SDU / PDU) of the first non-standard QoS flow is determined.

[0013] According to another aspect of an embodiment of the present application, a device for determining a channel access priority level is provided, the device including:

[0014] A determination module is configured to determine a CAPC for a first non-standard QoS flow.

[0015] According to another aspect of an embodiment of the present application, a device for determining a channel access priority level is provided, the device including:

[0016] The determining module is configured to determine the CAPC of the radio bearer associated with the first non-standard QoS flow based on the CAPC of the first non-standard QoS flow.

[0017] According to another aspect of an embodiment of the present application, a device for determining a channel access priority level is provided, the device including:

[0018] A determination module is configured to determine a CAPC of an associated RLC SDU / PDU of the first non-standard QoS flow based on the CAPC of the first non-standard QoS flow.

[0019] According to another aspect of an embodiment of the present application, a communication device is provided, the communication device including:

[0020] processor;

[0021] a transceiver connected to the processor;

[0022] a memory for storing executable instructions for the processor;

[0023] The processor is configured to load and execute executable instructions to implement the method for determining the channel access priority level in the above aspects.

[0024] According to another aspect of an embodiment of the present application, a computer-readable storage medium is provided, which stores at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by a processor to implement a method for determining a channel access priority level as described in the above aspects.

[0025] According to another aspect of an embodiment of the present application, a computer program product (or computer program) is provided, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method for determining the channel access priority level as described in the above aspects.

[0026] The technical solutions provided by the embodiments of the present application may have the following beneficial effects:

[0027] The present application determines the CAPC of the non-standard QoS flow, and determines the CAPC of the associated radio bearer and the associated RLC SDU / PDU of the non-standard QoS flow based on the CAPC of the non-standard QoS flow. When the network does not provide the CAPC of the non-standard QoS flow, the terminal can determine the CAPC of the non-standard QoS flow, as well as the CAPC of the associated radio bearer and the associated RLC SDU / PDU of the non-standard QoS flow, thereby performing tasks such as LBT monitoring and data packet assembly. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0029] FIG1 shows a schematic diagram of a data transmission system provided by an exemplary embodiment of the present application;

[0030] FIG2 shows a flow chart of a method for determining a channel access priority level provided by an exemplary embodiment of the present application;

[0031] FIG3 shows a flow chart of a method for determining a channel access priority level provided by an exemplary embodiment of the present application;

[0032] FIG4 shows a flow chart of a method for determining a channel access priority level provided by an exemplary embodiment of the present application;

[0033] FIG5 shows a flow chart of a method for determining a channel access priority level provided by an exemplary embodiment of the present application;

[0034] FIG6 shows a flow chart of a method for determining a channel access priority level provided by an exemplary embodiment of the present application;

[0035] FIG7 shows a flow chart of a method for determining a channel access priority level provided by an exemplary embodiment of the present application;

[0036] FIG8 is a schematic diagram showing a method for determining a channel access priority level provided by an exemplary embodiment of the present application;

[0037] FIG9 shows a block diagram of a device for determining a channel access priority level provided by an exemplary embodiment of the present application;

[0038] FIG10 shows a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0040] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0041] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. As used in this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0042] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions.

[0043] It should be understood that although the terms first, second, etc. may be used in this application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this application, a first parameter may also be referred to as a second parameter, and similarly, a second parameter may also be referred to as a first parameter. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0044] Some key terms in this application are briefly introduced as follows:

[0045] Standard QoS flow: QoS flow defined in the communication protocol.

[0046] Non-standard QoS flow: In contrast to standard QoS flow, it is a QoS flow not defined by the communication protocol.

[0047] 1 shows a schematic diagram of a data transmission system 100 provided in an exemplary embodiment of the present application. The data transmission system 100 includes: a network device 110 , a first terminal 120 , and a second terminal 130 .

[0048] The network device 110 may be a base station, which is a device that provides wireless communication functions for the first terminal 120 and the second terminal 130. The base station may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems using different wireless access technologies, the names of devices with base station functions may be different. For example, in the Long Term Evolution (LTE) system, it is called an evolved base station (eNodeB, eNB); in the 5th Generation New Radio (5G NR) system, it is called a next generation base station (gNB). As communication technology evolves, the description of "base station" may change. For the convenience of description in this application, the above-mentioned devices that provide wireless communication functions for the first terminal 120 and the second terminal 130 are collectively referred to as network devices 110.

[0049] The first terminal 120 and the second terminal 130 include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems with wireless communication functions, as well as various forms of user equipment, mobile stations (MS), terminal devices, etc.

[0050] Device-to-device communication is a sidelink transmission technology based on device-to-device (D2D). Unlike traditional cellular systems where communication data is received or sent through base stations, the Internet of Vehicles system uses terminal-to-terminal direct communication, resulting in higher spectrum efficiency and lower transmission latency. The 3rd Generation Partnership Project (3GPP) defines two transmission modes: Mode A and Mode B.

[0051] Mode A: The terminal's transmission resources are allocated by the base station, and the terminal sends data on the sidelink based on the resources allocated by the base station. The base station can allocate resources for a single transmission or for semi-static transmission.

[0052] Mode B: The terminal listens to a resource pool to obtain a set of available transmission resources. It then randomly selects a resource from this set to transmit sidelink data. Because services in connected vehicle systems are cyclical, terminals typically employ a semi-static transmission approach. This means that once a terminal selects a transmission resource, it uses it continuously for multiple transmission cycles, minimizing the probability of resource reselection and resource conflicts.

[0053] In this application, the sidelink transmission of the first terminal 120 and the second terminal 130 through mode B is used as an example for description. The "5G NR system" in this application may also be referred to as a 5G system or an NR system, but those skilled in the art will understand their meanings. The technical solutions described in the embodiments of this application can be applied to the 5G NR system and can also be applied to subsequent evolution systems of the 5G NR system.

[0054] FIG2 shows a flow chart of a method for determining a channel access priority level provided by an exemplary embodiment of the present application. The method is executed by a terminal and includes:

[0055] Step 200: Determine the CAPC of a first non-standard QoS flow.

[0056] When conducting sidelink communications on unlicensed spectrum, the UE must perform LBT monitoring, packet assembly, and other operations according to the CAPC. For non-connected UEs, non-standard QoS flows may exist. A non-connected state includes at least one of the following: idle state, inactive state, and out-of-coverage state. This embodiment uses the first non-standard QoS flow as an example for illustration.

[0057] Since the network is unaware of the first non-standard QoS flow, the UE cannot obtain the CAPC of the first non-standard QoS flow. Therefore, the UE needs to determine the CAPC of the first non-standard QoS flow.

[0058] The manner of determining the CAPC of the first non-standard QoS flow includes at least one of the following:

[0059] 1. Determine a CAPC for the first non-standard QoS flow based on one or more QoS parameters of the first non-standard QoS flow;

[0060] 2. Determine a CAPC for the first non-standard QoS flow based on information configured by the network for the first non-standard QoS flow;

[0061] 3. Based on the terminal implementation, determine the CAPC of the first non-standard QoS flow.

[0062] In some embodiments, a CAPC for the first non-standard QoS flow is determined based on one or more QoS parameters of the first non-standard QoS flow.

[0063] The QoS parameters include at least one of the following: packet delay budget (PDB), default priority (DP), packet error rate (PER), service type, and resource type.

[0064] Optionally, the CAPC of the first non-standard QoS flow is determined based on all QoS parameters of the first non-standard QoS flow.

[0065] Optionally, the CAPC of the first non-standard QoS flow is determined based on some QoS parameters of the first non-standard QoS flow.

[0066] Among them, the above-mentioned part of QoS parameters is determined by at least one of the following methods: network device configuration; terminal autonomous selection; communication protocol definition.

[0067] Exemplarily, based on the fact that the CAPC corresponding to all QoS parameters of the first non-standard QoS flow is 1, it is determined that the CAPC of the first non-standard QoS flow is 1.

[0068] In some embodiments, the CAPC for the first non-standard QoS flow is determined based on information configured by the network for the first non-standard QoS flow.

[0069] The information configured by the network for the first non-standard QoS flow includes at least one of the following:

[0070] 1. QoS parameters used when determining the CAPC for the first non-standard QoS flow;

[0071] 2. The matching conditions between the QoS parameters and the first CAPC.

[0072] The matching condition includes a parameter matching condition corresponding to each QoS parameter in the plurality of QoS parameters, wherein the parameter matching condition includes at least one of the following:

[0073] 1. The QoS parameter values ​​meet the target values;

[0074] 2. QoS parameter values ​​fall within the target range;

[0075] 3. The QoS parameter value type belongs to the target type;

[0076] 4. The QoS parameter value is the closest gear threshold among different gear thresholds, where different gear thresholds correspond to different CAPCs, and the closest gear threshold is the CAPC value defined for the standard QoS flow.

[0077] Exemplarily, the CAPC corresponding to the gear threshold closest to the QoS parameter values ​​among different gear thresholds is 2, and the CAPC of the first non-standard QoS flow is determined to be 2.

[0078] In some embodiments, a CAPC for the first non-standard QoS flow is determined based on terminal implementation.

[0079] The terminal determines the CAPC of the first non-standard QoS flow based on a matching condition between the QoS parameter set by the terminal and the first CAPC, where the matching condition includes a parameter matching condition corresponding to each of the multiple QoS parameters.

[0080] Exemplarily, when the terminal sets the QoS parameter value type to be a target type, the corresponding CAPC is 3, and the CAPC of the first non-standard QoS flow is determined to be 3.

[0081] In some embodiments, the network provides CAPC and allows the terminal to ignore the CAPC and determine the CAPC according to the above method, and the allowing situation includes at least one of the following: standard default permission; network indication permission.

[0082] In summary, the method provided in this embodiment determines the CAPC of the first non-standard QoS flow based on the QoS parameters of the first non-standard QoS flow when the network does not provide CAPC, thereby performing tasks such as LBT monitoring and data packet assembly.

[0083] The method provided in this embodiment also determines the CAPC of the first non-standard QoS flow based on the information configured by the network for the first non-standard QoS flow, when the network does not provide CAPC, thereby performing tasks such as LBT monitoring and data packet assembly.

[0084] The method provided in this embodiment is also implemented based on the terminal. When the network does not provide CAPC, the terminal determines the CAPC of the first non-standard QoS flow, thereby performing tasks such as LBT monitoring and data packet assembly.

[0085] FIG3 shows a flow chart of a method for determining a channel access priority level provided by an exemplary embodiment of the present application. The method is executed by a terminal and includes:

[0086] Step 210: Determine a CAPC for the first non-standard QoS flow based on one or more QoS parameters of the first non-standard QoS flow.

[0087] The one or more QoS parameters of the first non-standard QoS flow include at least one of the following:

[0088] PDB;

[0089] DP;

[0090] PER;

[0091] Business type;

[0092] Resource type.

[0093] Among them, PDB defines the upper limit of the possible delay time after the data packet is sent; DP is the priority parameter preset by the system; PER is the value obtained by dividing the number of erroneously received data packets by the total number of received data packets.

[0094] The one or more QoS parameters used in determining the CAPC of the first non-standard QoS Flow are determined or selected in at least one of the following ways:

[0095] Network device configuration;

[0096] Communication protocol provisions;

[0097] ·Select based on business type;

[0098] ·Select based on resource type.

[0099] In some embodiments, determining a CAPC for the first non-standard QoS flow based on a parameter matching condition met by a QoS parameter of the first non-standard QoS flow;

[0100] In some embodiments, determining the CAPC for the first nonstandard QoS flow based on a number of parameters of the plurality of QoS parameters of the first nonstandard QoS flow that meet a matching condition corresponding to the first CAPC;

[0101] The matching condition includes a parameter matching condition corresponding to each QoS parameter in the plurality of QoS parameters.

[0102] The parameter matching conditions include at least one of the following:

[0103] (1) The value is consistent with the target value;

[0104] (2) The value falls within the target value range;

[0105] (3) The value type belongs to the target type;

[0106] (4) The gear threshold value closest to the gear threshold value among different gear threshold values, wherein different gear threshold values ​​correspond to different CAPCs.

[0107] Among them, at least one of the target value, target value range, target type, and gear threshold is determined by at least one of the following methods: network device configuration; communication protocol regulations.

[0108] The network device configuration method includes at least one of the following:

[0109] (1) Network device configuration via dedicated Radio Resource Control (RRC);

[0110] (2) Network device configuration through the System Information Block (SIB);

[0111] (3) Configure network devices through pre-configuration.

[0112] The value is consistent with the target value

[0113] When one or more QoS parameter values ​​meet the target values, at least one of the following conditions may apply:

[0114] When one or more QoS parameters include PDB, the value of PDB meets the target value;

[0115] When one or more QoS parameters include DP, the value of DP complies with the target value;

[0116] When one or more QoS parameters include PER, the value of PER complies with the target value.

[0117] For example, as shown in Table 1, when one or more QoS parameters include a DP, and the DP value meets the target value, the CAPC of the first non-standard QoS flow is determined. If the DP is 1, the CAPC is 1; if the DP is 2, the CAPC is 2; and if the DP is 3, the CAPC is 3.

[0118] Table 1

[0119] Default priority DP channel access priority level CAPC112233

[0120] The value falls within the target range

[0121] When one or more QoS parameter values ​​fall within the target value range, at least one of the following is included:

[0122] When one or more QoS parameters include PDB, the value of PDB falls within the target value range;

[0123] When one or more QoS parameters include PER, the value of PER falls within the target value range.

[0124] Different target value ranges correspond to different CAPCs, and the target value range corresponding to the CAPC is specified by network device configuration or communication protocol.

[0125] Exemplarily, as shown in Table 2, when one or more QoS parameters include PDB, the value of PDB belongs to the target value range, and the CAPC of the first non-standard QoS flow is determined.

[0126] When the PDB value range is 0-100ms, the corresponding CAPC is 1; when the PDB value range is 100-200ms, the corresponding CAPC is 2; when the PDB value range is 200-300ms, the corresponding CAPC is 3. Specifically, when the PDB value is 100ms, the corresponding CAPC is 1; when the PDB value is 200ms, the corresponding CAPC is 2. When the PDB value is 50ms, within the value range corresponding to CAPC 1, the CAPC for the first non-standard QoS flow is determined to be 1.

[0127] Table 2

[0128] Packet delay budget PDBCAPC 0-100ms 1100-200ms 2200-300ms 3

[0129] The value type belongs to the target type

[0130] When one or more QoS parameter value types are of a specific value type or a specified value type, that is, a target type, at least one of the following is included:

[0131] In the case where one or more QoS parameters include a service type, the value type of the service type belongs to the target type;

[0132] In the case where one or more QoS parameters include a resource type, the value type of the resource type belongs to the target type.

[0133] For example, as shown in Table 3, the value type of the service type is Mission Critical Service (MCS), and the corresponding CAPC is 1; the value type of the resource type is Delay Critical Guaranteed Bit Rate (DCGBR), and the corresponding CAPC is 1.

[0134] Table 3

[0135] Business type resource type CAPCMCSDCGBR1

[0136] The gear threshold value closest to the gear threshold value among different gear threshold values

[0137] In the case where one or more QoS parameter values ​​are closest to the gear threshold among different gear thresholds, the value includes at least one of the following:

[0138] If one or more QoS parameters include PDB, the value of PDB is the closest gear threshold among the different gear thresholds;

[0139] In the case where one or more QoS parameters include PER, the PER value is the closest gear threshold among the different gear thresholds.

[0140] For example, as shown in Table 4, when the PDB is at the first gear threshold of 100ms, the corresponding CAPC is 1; when the PDB is at the second gear threshold of 200ms, the corresponding CAPC is 2; and when the PDB is at the third gear threshold of 300ms, the corresponding CAPC is 3. When the PDB is 120ms, the difference from the first gear threshold of 100ms is 20ms, and the difference from the second gear threshold of 200ms is 80ms, which is greater than 20ms. Therefore, the CAPC for the first non-standard QoS flow is determined to be the CAPC corresponding to the closest first gear threshold of 100ms.

[0141] Table 4

[0142] PDBCAPC100ms1200ms2300ms3

[0143] In some embodiments, determining the CAPC for the first non-standard QoS flow based on the number of parameters among the plurality of QoS parameters of the first non-standard QoS flow that meet a matching condition corresponding to the first CAPC includes at least one of the following:

[0144] (1) When multiple QoS parameters all meet the matching conditions corresponding to the first CAPC, determine the CAPC of the first non-standard QoS flow as the first CAPC;

[0145] (2) When the number of parameters that meet the matching condition corresponding to the first CAPC among the multiple QoS parameters reaches a first number, determine the CAPC of the first non-standard QoS flow as the first CAPC.

[0146] Multiple QoS parameters meet the matching conditions corresponding to the first CAPC

[0147] For example, as shown in Table 5, the multiple QoS parameters include: DP, PDB. When DP is 1, the corresponding CAPC is 1;

[0148] When DP is 2, the corresponding CAPC is 1;

[0149] When DP is 3, the corresponding CAPC is 1;

[0150] When the PDB value range is 0-100ms, the corresponding CAPC is 1;

[0151] When the PDB value range is 100-200ms, the corresponding CAPC is 2;

[0152] When the PDB value range is 200-300ms, the corresponding CAPC is 3.

[0153] When the DP is 1 and the PDB is 50 ms, both meet the matching conditions corresponding to the first CAPC, and the CAPC of the first non-standard QoS flow is determined to be 1.

[0154] Table 5

[0155] DPPDBCAPC10-100ms12100-200ms23200-300ms3

[0156] The number of QoS parameters that meet the matching conditions corresponding to the first CAPC reaches a first number.

[0157] In some embodiments, when the number of parameters in the plurality of QoS parameters that meet the matching condition corresponding to the first CAPC reaches a first number, the CAPC of the first non-standard QoS flow is determined to be the first CAPC.

[0158] Exemplarily, the first number is 2, the first CAPC is 2, and the multiple QoS parameters include: DP and PDB. As shown in Table 5, when the DP is 2 and the PDB is 150ms, the number of parameters that meet the matching conditions corresponding to the first CAPC reaches the first number, and the CAPC of the first non-standard QoS flow is determined to be 2.

[0159] In some embodiments, when it is determined that the number of parameters that meet the matching condition corresponding to the first CAPC among the plurality of QoS parameters according to the priority reaches a first number, the CAPC of the first non-standard QoS flow is determined to be the first CAPC;

[0160] Among them, the priority is used to indicate the judgment order of multiple QoS parameters. According to the network device configuration or communication protocol regulations, the smaller the priority value, the earlier the QoS parameter is judged.

[0161] Exemplarily, the first number is 2, the first CAPC is 3, and the multiple QoS parameters include: DP, PDB, and PER, the priority of DP is 1, the priority of PDB is 2, and the priority of PER is 3. As shown in Table 5, when the DP of the first non-standard QoS flow is 3 and the PDB is 250ms, that is, when the number of parameters that meet the matching conditions corresponding to the first CAPC in the multiple QoS parameters determined according to the priorities reaches the first number, the CAPC of the first non-standard QoS flow is determined to be 3.

[0162] The state of the terminal when executing the above method includes at least one of the following:

[0163] RRC connected state;

[0164] RRC idle state;

[0165] RRC inactive state;

[0166] Out-of-coverage status.

[0167] In summary, the method provided in this embodiment determines the CAPC of the non-standard QoS flow based on one or more QoS parameters of the first non-standard QoS flow when the network does not provide CAPC, thereby performing tasks such as LBT monitoring and data packet assembly.

[0168] FIG4 shows a flow chart of a method for determining a channel access priority level provided by an exemplary embodiment of the present application. The method is executed by a terminal and includes:

[0169] Step 400: Based on the CAPC of the first non-standard QoS flow, determine the CAPC of the radio bearer associated with the first non-standard QoS flow.

[0170] By determining the CAPC of the first non-standard QoS flow, the mapped CAPC configuration of the associated radio bearer is further obtained. The CAPC is determined by the CAPC determination method in the above embodiment. The associated radio bearer is a specific radio bearer, including a default radio bearer.

[0171] In the case that there is only the CAPC of the first non-standard QoS flow, the CAPC of the radio bearer associated with the first non-standard QoS flow is determined to be the CAPC of the first non-standard QoS flow.

[0172] In some embodiments, if the network device configures CAPC for the associated radio bearer, the network device may instruct the UE to use the CAPC configured by the network device; or instruct the UE to autonomously determine the CAPC of the radio bearer based on the CAPC of the non-standard QoS flow; or the UE may ignore the CAPC configured by the network device by default and autonomously determine the CAPC of the radio bearer.

[0173] To summarize, the method provided in this embodiment determines the CAPC of the associated radio bearer of the first non-standard QoS flow based on the CAPC of the first non-standard QoS flow. When the network does not provide CAPC, the terminal determines the CAPC of the associated radio bearer of the first non-standard QoS flow, thereby performing tasks such as LBT monitoring and data packet assembly.

[0174] FIG5 shows a flowchart of a method for determining a channel access priority level provided by an exemplary embodiment of the present application. The method is executed by a terminal and includes:

[0175] Step 410: Determine the CAPC of the associated radio bearer based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow.

[0176] In the case of a CAPC for a first non-standard QoS flow and a CAPC for a second non-standard QoS flow, the CAPC for an associated radio bearer is determined to be one of the two CAPCs based on a certain rule, wherein the associated radio bearer is a radio bearer associated with the first non-standard QoS flow and the second non-standard QoS flow.

[0177] The method of determining the CAPC of the associated radio bearer based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow includes at least one of the following:

[0178] Determine the maximum of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer;

[0179] Determine the minimum of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer;

[0180] Determine any value between the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer;

[0181] Determine the average of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer.

[0182] (1) The maximum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated radio bearer.

[0183] In the case of a CAPC for a first non-standard QoS flow and a CAPC for a second non-standard QoS flow, a maximum value of the two CAPCs is determined as the CAPC for the associated radio bearer, the maximum value corresponding to the minimum priority.

[0184] Exemplarily, two CAPCs are CAPC1 and CAPC2, where the value of CAPC1 is 1 and the value of CAPC2 is 2. CAPC2 has the largest value, so the CAPC value of the associated radio bearer is determined to be 2.

[0185] (2) The minimum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated radio bearer.

[0186] In the case of a CAPC for a first non-standard QoS flow and a CAPC for a second non-standard QoS flow, the minimum value of the two CAPCs is determined as the CAPC for the associated radio bearer, the minimum value corresponding to the maximum priority.

[0187] Exemplarily, two CAPCs are CAPC1 and CAPC2, where the value of CAPC1 is 1 and the value of CAPC2 is 2. CAPC1 has the smallest value, so the CAPC value of the associated radio bearer is determined to be 1.

[0188] (3) Determine any value between the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer.

[0189] In case there is a CAPC for a first non-standard QoS flow and a CAPC for a second non-standard QoS flow, any value of the two CAPCs is determined as the CAPC for the associated radio bearer.

[0190] Exemplarily, taking two CAPCs, CAPC1 and CAPC2, where the value of CAPC1 is 1 and the value of CAPC2 is 2, as an example, it is described to determine whether the CAPC value of the associated radio bearer is 1 or 2.

[0191] (4) Determine the average of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer.

[0192] In the case of a CAPC for a first non-standard QoS flow and a CAPC for a second non-standard QoS flow, an average of the two CAPCs is determined as the CAPC for the associated radio bearer. The average may be rounded up or down.

[0193] For example, take two CAPCs, CAPC1 and CAPC2, where the value of CAPC1 is 1 and the value of CAPC2 is 2, as an example. The rounded-up average of the CAPC1 and CAPC2 values ​​is 2, and the rounded-down average of the CAPC1 and CAPC2 values ​​is 1. When the CAPC value of the associated radio bearer is determined to be the rounded-up average, the CAPC value of the associated radio bearer is 2; when the CAPC value of the associated radio bearer is determined to be the rounded-down average, the CAPC value of the associated radio bearer is 1.

[0194] (5) In some embodiments, the QoS parameters of the first non-standard QoS flow include the first parameter, and the QoS parameters of the second non-standard QoS flow include the first parameter.

[0195] When the first parameter corresponding to the first non-standard QoS flow is the smallest, determining the CAPC of the first non-standard QoS flow as the CAPC of the associated radio bearer;

[0196] When the first parameter corresponding to the second non-standard QoS flow is the smallest, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated radio bearer.

[0197] The first parameter includes at least one of the following: PDB; DP; PER.

[0198] Exemplarily, the DP value in the QoS parameters of the first non-standard QoS flow is 1, the DP value in the QoS parameters of the second non-standard QoS flow is 2, and 1 is less than 2, then the CAPC of the associated radio bearer is the CAPC of the first non-standard QoS flow.

[0199] (6) In some embodiments, the QoS parameters of the first non-standard QoS flow include the second parameter, and the QoS parameters of the second non-standard QoS flow include the second parameter.

[0200] In a case where the second parameter corresponding to the first non-standard QoS flow is of the first type, determining the CAPC of the first non-standard QoS flow as the CAPC of the associated radio bearer;

[0201] In a case where the second parameter corresponding to the second non-standard QoS flow is of the first type, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated radio bearer.

[0202] The second parameter includes at least one of the following: business type; resource type.

[0203] The first type corresponding to the service type is MCS, and the first type corresponding to the resource type is DCGBR.

[0204] Exemplarily, when the service type corresponding to the first non-standard QoS flow is MCS, the CAPC of the associated radio bearer is the CAPC of the first non-standard QoS flow.

[0205] In summary, the method provided in this embodiment determines the CAPC of the associated radio bearer based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow. If the network does not provide a CAPC, the terminal determines the CAPC of the associated radio bearer to perform tasks such as LBT monitoring and packet assembly.

[0206] FIG6 shows a flowchart of a method for determining a channel access priority level provided by an exemplary embodiment of the present application. The method is executed by a terminal and includes:

[0207] Step 500: Based on the CAPC of the first non-standard QoS flow, determine the CAPC of the associated RLC PDU / SDU of the first non-standard QoS flow.

[0208] The unprocessed data entering each sublayer is called an SDU. The data in a specific format after being processed by the sublayer is called a PDU. The SDU of layer N and the PDU of layer N-1 are one-to-one corresponding.

[0209] The CAPC of the first non-standard QoS flow is determined by the method for determining the CAPC of the first non-standard QoS flow in the above embodiment. The RLC PDU / SDU associated with the non-standard QoS flow is related to a specific radio bearer, such as a default radio bearer.

[0210] In a case where there is only the CAPC of the first non-standard QoS flow, determining the CAPC of the RLC PDU / SDU associated with the first non-standard QoS flow as the CAPC of the first non-standard QoS flow;

[0211] In summary, the method provided in this embodiment determines the CAPC of the RLC PDU / SDU associated with the first non-standard QoS flow based on the CAPC of the first non-standard QoS flow. If the network does not provide a CAPC, the terminal determines the CAPC of the RLC PDU / SDU associated with the first non-standard QoS flow, thereby performing tasks such as LBT monitoring and data packet assembly.

[0212] FIG7 shows a flowchart of a method for determining a channel access priority level provided by an exemplary embodiment of the present application. The method is executed by a terminal and includes:

[0213] Step 510: Determine the CAPC of the associated RLC PDU / SDU based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow.

[0214] In the case of a CAPC for a first non-standard QoS flow and a CAPC for a second non-standard QoS flow, when the two CAPCs are of the same priority, the CAPC for an associated RLC PDU / SDU is determined to be of the same priority, wherein the associated RLC PDU / SDU is an RLC PDU / SDU associated with the first non-standard QoS flow and the second non-standard QoS flow.

[0215] Exemplarily, CAPC1 of the first non-standard QoS flow and CAPC2 of the second non-standard QoS flow have the same priority, and the CAPC of the associated RLC PDU / SDU is determined to have the same priority.

[0216] In the case of a CAPC for a first non-standard QoS flow and a CAPC for a second non-standard QoS flow, when the two CAPCs are of different priorities, the CAPC of the associated RLC PDU / SDU is determined to be one of the different priorities based on a certain rule.

[0217] The method of determining the CAPC of the associated RLC PDU / SDU based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow includes at least one of the following:

[0218] Determine the maximum of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU;

[0219] Determine the minimum of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU;

[0220] Determine any value between the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU;

[0221] Determine the average of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU;

[0222] (1) The maximum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated RLC PDU / SDU.

[0223] In case of a CAPC for a first non-standard QoS flow and a CAPC for a second non-standard QoS flow, the maximum value of the two CAPCs is determined as the CAPC for the associated RLC PDU / SDU, the maximum value corresponding to the minimum priority.

[0224] For example, take two CAPCs, CAPC1 and CAPC2, with a CAPC1 value of 1 and a CAPC2 value of 2 as an example for description. CAPC2 has the largest value, so the CAPC value of the associated RLC PDU / SDU is determined to be 2.

[0225] (2) The minimum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated RLC PDU / SDU.

[0226] In case of a CAPC for a first non-standard QoS flow and a CAPC for a second non-standard QoS flow, the minimum value of the two CAPCs is determined as the CAPC for the associated RLC PDU / SDU, the minimum value corresponding to the maximum priority.

[0227] Exemplarily, take two CAPCs, CAPC1 and CAPC2, with a CAPC1 value of 1 and a CAPC2 value of 2 as an example for explanation. CAPC1 has the smallest value, so the CAPC value of the associated RLC PDU / SDU is determined to be 1.

[0228] (3) Any value among the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated RLC PDU / SDU.

[0229] In case there is a CAPC for a first non-standard QoS flow and a CAPC for a second non-standard QoS flow, any value of the two CAPCs is determined as the CAPC for the associated RLC PDU / SDU.

[0230] Exemplarily, taking two CAPCs, CAPC1 and CAPC2, with a CAPC1 value of 1 and a CAPC2 value of 2, as an example, it is determined that the CAPC value of the associated RLC PDU / SDU is 1 or 2.

[0231] (4) The average of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow is determined as the CAPCC of the associated RLC PDU / SDU.

[0232] In the case of a CAPC for a first non-standard QoS flow and a CAPC for a second non-standard QoS flow, an average of the two CAPCs is determined as the CAPC for the associated RLC PDU / SDU, and the average may be rounded up or down.

[0233] For example, take two CAPCs, CAPC1 and CAPC2, with a CAPC1 value of 1 and a CAPC2 value of 2, as an example for explanation. The rounded-up average of the CAPC1 and CAPC2 values ​​is 2, and the rounded-down average of the CAPC1 and CAPC2 values ​​is 1. When the CAPC of the associated RLC PDU / SDU is determined to be the rounded-up average, the CAPC value of the associated RLC PDU / SDU is 2; when the CAPC of the associated RLC PDU / SDU is determined to be the rounded-down average, the CAPC value of the associated RLC PDU / SDU is 1.

[0234] (5) In some embodiments, the QoS parameters of the first non-standard QoS flow include a third parameter, and the QoS parameters of the second non-standard QoS flow include a third parameter.

[0235] When the third parameter corresponding to the first non-standard QoS flow is the smallest, determining the CAPC of the first non-standard QoS flow as the CAPC of the associated RLC PDU / SDU;

[0236] When the third parameter corresponding to the second non-standard QoS flow is the smallest, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated RLC PDU / SDU.

[0237] The third parameter includes at least one of the following: PDB; DP; PER.

[0238] Exemplarily, the DP value in the QoS parameters of the first non-standard QoS flow is 1, and the DP value in the QoS parameters of the second non-standard QoS flow is 2, and 1 is less than 2, then the CAPC of the associated RLC PDU / SDU is the CAPC of the first non-standard QoS flow.

[0239] (6) In some embodiments, the QoS parameters of the first non-standard QoS flow include a fourth parameter, and the QoS parameters of the second non-standard QoS flow include a fourth parameter.

[0240] When the fourth parameter corresponding to the first non-standard QoS flow is of the second type, determining the CAPC of the first non-standard QoS flow as the CAPC of the associated RLC PDU / SDU;

[0241] In a case where the fourth parameter corresponding to the second non-standard QoS flow is of the second type, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated RLC PDU / SDU.

[0242] The fourth parameter includes at least one of the following: business type; resource type.

[0243] The second type corresponding to the service type is MCS, and the second type corresponding to the resource type is DCGBR.

[0244] Exemplarily, when the service type corresponding to the first non-standard QoS flow is MCS, the CAPC of the associated RLC PDU / SDU is the CAPC of the first non-standard QoS flow.

[0245] In some embodiments, the first non-standard QoS flow and the second non-standard QoS flow having the same CAPC are mapped to the same RLC PDU / SDU, and the CAPC of the same RLC PDU / SDU is determined.

[0246] In the case that non-standard QoS flows having the same CAPC value are mapped to the same RLC SDU / PDU, the UE determines the CAPC value of the RLC SDU / PDU to be the same CAPC value.

[0247] Exemplarily, the first non-standard QoS flow and the second non-standard QoS flow have the same CAPC value of 1. When the first non-standard QoS flow and the second non-standard QoS flow are mapped to the same RLC SDU / PDU, the UE determines that the CAPC value of the same RLC SDU / PDU is 1.

[0248] In some embodiments, a first non-standard QoS flow and a second non-standard QoS flow having similar CAPCs are mapped to the same RLC PDU / SDU, and the CAPCs of the same RLC PDU / SDU are determined.

[0249] The CAPC being close means that the difference between the CAPC values ​​is less than a first threshold, where the first threshold is specified by the network device configuration or the communication protocol.

[0250] In case non-standard QoS flows with similar CAPC values ​​are mapped to the same RLC SDU / PDU, the UE determines the CAPC of the RLC SDU / PDU.

[0251] Exemplarily, the first threshold is 2, the CAPC1 value of the first non-standard QoS flow is 1, and the CAPC2 value of the second non-standard QoS flow is 2. When the first non-standard QoS flow and the second non-standard QoS flow are mapped to the same RLC SDU / PDU, the UE determines the CAPC of the same RLC SDU / PDU based on the above-mentioned method for determining the CAPC of the associated RLC SDU / PDU.

[0252] In summary, the method provided in this embodiment determines the CAPC for the associated RLC SDU / PDU based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow. If the network does not provide a CAPC, the terminal determines the CAPC for the associated RLC SDU / PDU to perform tasks such as LBT monitoring and packet assembly.

[0253] The above embodiments of determining the CAPC of the first non-standard QoS flow, determining the CAPC of the associated radio bearer, and determining the CAPC of the associated RLC SDU / PDU can be implemented in pairs or in combination, and this application does not limit them.

[0254] When conducting sidelink communication, the UE needs to perform tasks such as LBT monitoring and data packet assembly according to the CAPC of the RB. For UEs with standard QoS flows, the network can provide relevant CAPCs, and the UE performs tasks according to the relevant CAPCs. However, for UEs with non-standard QoS flows, since the network is unaware of the non-standard QoS flow, it is unable to provide relevant CAPCs, and the UE cannot perform tasks. To this end, the present application provides a method for determining a channel access priority level, which is used for the UE to determine the CAPC of the QoS flow. Figure 8 shows a schematic diagram of a method for determining a channel access priority level provided by an exemplary embodiment of the present application. The method is executed by a terminal, and the state of the terminal when executing the method includes at least one of the following: RRC connected state, RRC idle state, RRC inactive state, and out-of-coverage state.

[0255] For a UE with one or more non-standard QoS flows, taking non-standard QoS flow1 and non-standard QoS flow2 as an example, non-standard QoS flow1 is described below.

[0256] The UE determines CAPC1 according to one or more QoS parameters in the non-standard QoS flow1, where the QoS parameters include at least one of the following: PDB, DP, PER, service type, and resource type.

[0257] The one or more QoS parameters are specified by network device configuration or a communication protocol, and are configured by the network device through a dedicated RRC or SIB or pre-configuration. The dedicated RRC refers to an RRC dedicated to the UE.

[0258] The one or more QoS parameters have priorities. The priorities of different QoS parameters are specified by the network device configuration or communication protocol. The network device configuration is performed through a dedicated RRC or SIB or pre-configuration. The smaller the priority value, the earlier the QoS parameter is judged.

[0259] The parameter matching conditions include at least one of the following:

[0260] The value is consistent with the target value;

[0261] The value falls within the target value range;

[0262] The value type belongs to the target type;

[0263] The gear threshold value that is closest to the gear threshold value among different gear threshold values, where different gear threshold values ​​correspond to different CAPCs.

[0264] (1) The value is consistent with the target value

[0265] When one or more QoS parameter values ​​meet the target values, at least one of the following conditions may apply:

[0266] When one or more QoS parameters include PDB, the value of PDB meets the target value;

[0267] When one or more QoS parameters include DP, the value of DP complies with the target value;

[0268] When one or more QoS parameters include PER, the value of PER complies with the target value.

[0269] For example, as shown in Table 1, when one or more QoS parameters include DP, the DP value meets the target value, and CAPC1 is determined for non-standard QoS flow 1. When DP is 1, CAPC1 is 1; when DP is 2, CAPC1 is 2; and when DP is 3, CAPC1 is 3.

[0270] (2) The value falls within the target value range

[0271] When one or more QoS parameter values ​​fall within the target value range, at least one of the following is included:

[0272] When one or more QoS parameters include PDB, the value of PDB falls within the target value range;

[0273] When one or more QoS parameters include PER, the value of PER falls within the target value range.

[0274] Different target value ranges correspond to different CAPCs, and the target value range corresponding to the CAPC is specified by network device configuration or communication protocol.

[0275] Exemplarily, as shown in Table 2, when one or more QoS parameters include PDB, the value of PDB falls within the target value range, and CAPC1 of non-standard QoS flow1 is determined.

[0276] When the PDB value range is 0-100ms, the corresponding CAPC is 1; when the PDB value range is 100-200ms, the corresponding CAPC is 2; and when the PDB value range is 200-300ms, the corresponding CAPC is 3. Specifically, when the PDB value is 100ms, the corresponding CAPC is 1; and when the PDB value is 200ms, the corresponding CAPC is 2. When the PDB value is 50ms, within the value range corresponding to CAPC 1, CAPC 1 for non-standard QoS flow 1 is determined to be 1.

[0277] (3) The value type belongs to the target type

[0278] When one or more QoS parameter value types are of a specific value type or a specified value type, that is, a target type, at least one of the following is included:

[0279] In the case where one or more QoS parameters include a service type, the value type of the service type belongs to the target type;

[0280] In the case where one or more QoS parameters include a resource type, the value type of the resource type belongs to the target type.

[0281] For example, as shown in Table 3, the value type of the service type is MCS, and the corresponding CAPC is 1; the value type of the resource type is DCGBR, and the corresponding CAPC is 1. When the QoS parameter of non-standard QoS flow1 includes the service type, the value type of the service type is MCS, and the CAPC1 of non-standard QoS flow1 is determined to be 1.

[0282] (4) The gear threshold value closest to the gear threshold value among different gear threshold values

[0283] In the case where one or more QoS parameter values ​​are closest to the gear threshold among different gear thresholds, the value includes at least one of the following:

[0284] If one or more QoS parameters include PDB, the value of PDB is the closest gear threshold among the different gear thresholds;

[0285] In the case where one or more QoS parameters include PER, the PER value is the closest gear threshold among the different gear thresholds.

[0286] For example, as shown in Table 4, when the PDB is at the first-gear threshold of 100ms, the corresponding CAPC is 1; when the PDB is at the second-gear threshold of 200ms, the corresponding CAPC is 2; and when the PDB is at the third-gear threshold of 300ms, the corresponding CAPC is 3. When the PDB is 120ms, the difference from the first-gear threshold of 100ms is 20ms, and the difference from the second-gear threshold of 200ms is 80ms, which is greater than 20ms. Therefore, CAPC1 for non-standard QoS flow1 is determined to be the CAPC corresponding to the closest first-gear threshold of 100ms.

[0287] In some embodiments, determining CAPC1 for non-standard QoS flow1 based on the number of parameters in the plurality of QoS parameters of the first non-standard QoS flow that meet the matching condition corresponding to the first CAPC includes at least one of the following:

[0288] (1) When multiple QoS parameters all meet the matching conditions corresponding to the first CAPC, CAPC1 of non-standard QoS flow1 is determined to be the first CAPC;

[0289] (2) When the number of parameters that meet the matching condition corresponding to the first CAPC among the multiple QoS parameters reaches a first number, CAPC1 of the non-standard QoS flow1 is determined to be the first CAPC.

[0290] (1) Multiple QoS parameters meet the matching conditions corresponding to the first CAPC

[0291] For example, as shown in Table 5, the multiple QoS parameters include: DP, PDB. When DP is 1, the corresponding CAPC is 1;

[0292] When DP is 2, the corresponding CAPC is 1;

[0293] When DP is 3, the corresponding CAPC is 1;

[0294] When the PDB value range is 0-100ms, the corresponding CAPC is 1;

[0295] When the PDB value range is 100-200ms, the corresponding CAPC is 2;

[0296] When the PDB value range is 200-300ms, the corresponding CAPC is 3.

[0297] When the DP is 1 and the PDB is 50 ms, both meet the matching conditions corresponding to the first CAPC, and it is determined that the CAPC1 of the non-standard QoS flow1 is 1.

[0298] (2) The number of parameters in the plurality of QoS parameters that meet the matching conditions corresponding to the first CAPC reaches a first number

[0299] In some embodiments, when the number of parameters in the plurality of QoS parameters that meet the matching condition corresponding to the first CAPC reaches a first number, CAPC1 of the non-standard QoS flow1 is determined to be the first CAPC.

[0300] For example, the first number is 2, the first CAPC is 2, and the multiple QoS parameters include: DP and PDB. As shown in Table 5, when the DP is 2 and the PDB is 150ms, the number of parameters that meet the matching conditions corresponding to the first CAPC reaches the first number, and it is determined that the CAPC1 of the non-standard QoS flow1 is 2.

[0301] In some embodiments, when the number of parameters that meet the matching condition corresponding to the first CAPC among the plurality of QoS parameters determined according to the priority reaches a first number, CAPC1 of the non-standard QoS flow1 is determined as the first CAPC;

[0302] Among them, the priority is used to indicate the judgment order of multiple QoS parameters. According to the network device configuration or communication protocol regulations, the smaller the priority value, the earlier the QoS parameter is judged.

[0303] For example, the first number is 2, the first CAPC is 3, and the multiple QoS parameters include: DP, PDB, and PER. The priority of DP is 1, the priority of PDB is 2, and the priority of PER is 3. As shown in Table 5, the DP in the QoS parameters of non-standard QoS flow1 is 3 and the PDB is 250ms. That is, when the number of parameters that meet the matching condition corresponding to the first CAPC in the multiple QoS parameters determined according to the priority reaches the first number, the CAPC1 of the non-standard QoS flow1 is determined to be 3.

[0304] The method for determining CAPC2 of non-standard QoS flow2 is the same as the above method and will not be repeated here.

[0305] After determining CAPC1 of non-standard QoS flow1 and CAPC2 of non-standard QoS flow2, the UE determines CAPC3 associated with the default bearer. This is described using an example where the CAPC1 value is 1 and the CAPC2 value is 2. The method for determining CAPC3 associated with the default bearer includes at least one of the following:

[0306] (1) The CAPC3 value of the associated default bearer is determined to be the maximum of the CAPC1 value and the CAPC2 value.

[0307] For example, if the maximum value of the CAPC1 value and the CAPC2 value is 2, then the CAPC3 value is 2.

[0308] (2) The CAPC3 value of the associated default bearer is determined to be the minimum value of the CAPC1 value and the CAPC2 value.

[0309] For example, if the minimum value of the CAPC1 value and the CAPC2 value is 1, then the CAPC3 value is 1.

[0310] (3) The CAPC3 value of the associated default bearer is determined to be any value between the CAPC1 value and the CAPC2 value.

[0311] Exemplarily, the CAPC3 value is either 1 or 2.

[0312] (4) The CAPC3 value of the associated default bearer is determined to be the average of the CAPC1 value and the CAPC2 value.

[0313] The average value can be rounded up or down. For example, the average value of the CAPC1 value and the CAPC2 value rounded up is 2. When the CAPC3 value is determined to be the average value rounded up, the CAPC3 value is 2; the average value of the CAPC1 value and the CAPC2 value rounded down is 1. When the CAPC3 value is determined to be the average value rounded down, the CAPC3 value is 1.

[0314] (5) Determine the CAPC3 value associated with the default bearer, which is the CAPC value of the non-standard QoS flow corresponding to the minimum first parameter.

[0315] In some embodiments, the QoS parameters of the non-standard QoS flow1 include the first parameter, and the QoS parameters of the non-standard QoS flow2 include the first parameter.

[0316] When the first parameter corresponding to the non-standard QoS flow1 is the smallest, the CAPC1 of the non-standard QoS flow1 is determined to be the CAPC3 associated with the default bearer;

[0317] When the first parameter corresponding to the non-standard QoS flow2 is the smallest, the CAPC2 of the non-standard QoS flow2 is determined to be the CAPC3 associated with the default bearer.

[0318] The first parameter includes at least one of the following: PDB; DP; PER.

[0319] For example, when the DP value in the QoS parameters of non-standard QoS flow1 is 1 and the DP value in the QoS parameters of non-standard QoS flow2 is 2, and 1 is less than 2, the CAPC3 value is the CAPC1 value of non-standard QoS flow1, that is, 1.

[0320] (6) Determine the CAPC3 value associated with the default bearer, which is the CAPC value of the corresponding non-standard QoS flow whose second parameter is the first type.

[0321] In some embodiments, the QoS parameters of the non-standard QoS flow1 include the second parameter, and the QoS parameters of the non-standard QoS flow2 include the second parameter.

[0322] In a case where the second parameter corresponding to the non-standard QoS flow1 is of the first type, the CAPC1 of the non-standard QoS flow1 is determined to be the CAPC3 associated with the default bearer;

[0323] In a case where the second parameter corresponding to the non-standard QoS flow2 is of the first type, the CAPC2 of the non-standard QoS flow is determined to be the CAPC3 associated with the default bearer.

[0324] The second parameter includes at least one of the following: business type; resource type.

[0325] The first type corresponding to the service type is MCS, and the first type corresponding to the resource type is DCGBR.

[0326] Exemplarily, when the service type corresponding to the non-standard QoS flow1 is MCS, the CAPC3 value associated with the default bearer is the CAPC1 value of the non-standard QoS flow1, that is, 1.

[0327] The above method may be configured by a network device or specified by a communication protocol or implemented based on the UE itself. The UE dynamically determines the CAPC3 associated with the default bearer as the non-standard QoS flow1 and the non-standard QoS flow2 change through the above method.

[0328] In some embodiments, when the network device is configured with CAPC3 associated with the default bearer, the network device may instruct the UE to use the CAPC3 configured by the network device, or instruct the UE to make an autonomous decision according to the method in the above embodiment, or the UE may ignore the CAPC3 configured by the network device and make an autonomous decision by default.

[0329] In some embodiments, the UE maps similar non-standard QoS flows to the same RLC SDU / PDU. Similar non-standard QoS flows are non-standard QoS flows with the same or similar CAPCs as determined by the method for determining the CAPC of a non-standard QoS flow described above. Similar CAPCs refer to CAPC values ​​that differ by less than a first threshold, which is specified by the network device configuration or communication protocol. Unprocessed data entering each sublayer is called an SDU. Data processed by the sublayer and formatted in a specific format is called a PDU. There is a one-to-one correspondence between the SDU at layer N and the PDU at layer N-1.

[0330] In the case that non-standard QoS flows having the same CAPC value are mapped to the same RLC SDU / PDU, the UE determines the CAPC value of the RLC SDU / PDU to be the same CAPC value.

[0331] In the case where non-standard QoS flows with different CAPC values ​​are mapped to the same RLC SDU / PDU, the UE determines the CAPC value of the RLC SDU / PDU according to the above method principle for determining the CAPC3 value associated with the default bearer.

[0332] In summary, the method provided in this embodiment determines the CAPC of a non-standard QoS flow based on its QoS parameters. When the network does not provide a CAPC, the terminal determines the CAPC of the non-standard QoS flow and performs tasks such as LBT monitoring and packet assembly.

[0333] The method provided in this embodiment also determines the CAPC of the default bearer associated with the non-standard QoS flow based on the CAPC of the non-standard QoS flow. If the network does not provide a CAPC, the terminal determines the CAPC of the default bearer associated with the non-standard QoS flow to perform tasks such as LBT monitoring and packet assembly.

[0334] The method provided in this embodiment also determines the CAPC of the RLC SDU / PDU associated with the non-standard QoS flow based on the CAPC of the non-standard QoS flow. If the network does not provide CAPC, the terminal determines the CAPC of the RLC SDU / PDU associated with the non-standard QoS flow to perform tasks such as LBT monitoring and data packet assembly.

[0335] FIG9 shows a block diagram of a device for determining a channel access priority level provided by an exemplary embodiment of the present application, the device comprising:

[0336] The determination module 910 is configured to determine a CAPC of a first non-standard QoS flow.

[0337] In a possible design of this embodiment, the determination module 910 is configured to determine the CAPC of the first non-standard QoS flow based on one or more QoS parameters of the first non-standard QoS flow.

[0338] In a possible design of this embodiment, the determination module 910 is configured to determine the CAPC of the first non-standard QoS flow based on information configured by the network for the first non-standard QoS flow.

[0339] In a possible design of this embodiment, the determination module 910 is configured to determine the CAPC of the first non-standard QoS flow based on terminal implementation.

[0340] In a possible design of this embodiment, the determination module 910 is configured to determine the CAPC of the first non-standard QoS flow based on a parameter matching condition met by a QoS parameter of the first non-standard QoS flow.

[0341] In one possible design of this embodiment, the determining module 910 is configured to determine the CAPC for the first non-standard QoS flow based on the number of parameters in the plurality of QoS parameters of the first non-standard QoS flow that meet a matching condition corresponding to the first CAPC;

[0342] The matching condition includes a parameter matching condition corresponding to each QoS parameter in the plurality of QoS parameters.

[0343] In a possible design of this embodiment, the determination module 910 is configured to determine that the CAPC of the first non-standard QoS flow is the first CAPC when the multiple QoS parameters all meet the matching conditions corresponding to the first CAPC; or,

[0344] When the number of parameters that meet the matching condition corresponding to the first CAPC among the multiple QoS parameters reaches a first number, the CAPC of the first non-standard QoS flow is determined to be the first CAPC.

[0345] In one possible design of this embodiment, the determining module 910 is configured to determine the CAPC of the first non-standard QoS flow as the first CAPC if the number of parameters that meet the matching condition corresponding to the first CAPC among the multiple QoS parameters determined according to the priority reaches a first number;

[0346] The priority is used to indicate the order of determining multiple QoS parameters.

[0347] In one possible design of this embodiment, the parameter matching condition includes at least one of the following:

[0348] The value is consistent with the target value;

[0349] The value falls within the target value range;

[0350] The value type belongs to the target type;

[0351] The value is the closest gear threshold among different gear thresholds, where different gear thresholds correspond to different CAPCs.

[0352] In one possible design of this embodiment, the values ​​that meet the target values ​​include:

[0353] In the case where one or more QoS parameters include PDB, the value of PDB complies with the target value;

[0354] In the case where one or more QoS parameters include DP, the value of DP complies with the target value;

[0355] In the case where one or more QoS parameters include PER, the value of PER complies with the target value.

[0356] In one possible design of this embodiment, the values ​​that meet the target values ​​include:

[0357] In the case where one or more QoS parameters include PDB, the value of PDB complies with the target value;

[0358] In the case where one or more QoS parameters include DP, the value of DP complies with the target value;

[0359] In the case where one or more QoS parameters include PER, the value of PER complies with the target value.

[0360] In a possible design of this embodiment, the value type belongs to the target type, including:

[0361] In the case where one or more QoS parameters include a service type, the value type of the service type belongs to the target type;

[0362] In the case where one or more QoS parameters include a resource type, the value type of the resource type belongs to the target type.

[0363] In a possible design of this embodiment, the gear threshold value closest to the gear threshold value among different gear threshold values ​​includes:

[0364] In the case where one or more QoS parameters include PDB, the value of PDB is the gear threshold closest to the gear thresholds among the different gear thresholds;

[0365] In the case where the one or more QoS parameters include PER, the value of PER is the closest gear threshold among the different gear thresholds.

[0366] In a possible design of this embodiment, at least one of the target value, the target value range, the target type, and the gear threshold is determined by at least one of the following methods:

[0367] Network device configuration;

[0368] Communication protocol provisions.

[0369] In one possible design of this embodiment, the one or more QoS parameters include at least one of the following:

[0370] PDB;

[0371] DP;

[0372] PER;

[0373] Business type;

[0374] Resource type.

[0375] In one possible design of this embodiment, one or more QoS parameters are determined or selected by at least one of the following methods:

[0376] Network device configuration;

[0377] Communication protocol provisions;

[0378] Select based on business type;

[0379] Select based on resource type.

[0380] In a possible design of this embodiment, the state of the terminal when executing the method includes at least one of the following:

[0381] Radio Resource Control RRC connected state;

[0382] RRC idle state;

[0383] RRC inactive state;

[0384] Override outer state.

[0385] In some embodiments, the determining module 910 is further configured to determine the CAPC of the radio bearer associated with the first non-standard QoS flow based on the CAPC of the first non-standard QoS flow.

[0386] In a possible design of this embodiment, the determination module 910 is used to determine the CAPC of the associated radio bearer based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow, wherein the associated radio bearer is a radio bearer associated with the first non-standard QoS flow and the second non-standard QoS flow.

[0387] In one possible design of this embodiment, the determining module 910 is configured to determine the maximum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer; or

[0388] used to determine the minimum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer; or

[0389] used to determine any value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer; or

[0390] Used to determine an average of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer.

[0391] In one possible design of this embodiment, the determining module 910 is configured to determine the CAPC of the first non-standard QoS flow as the CAPC of the associated radio bearer when the first parameter corresponding to the first non-standard QoS flow is minimum;

[0392] When the first parameter corresponding to the second non-standard QoS flow is the smallest, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated radio bearer.

[0393] The QoS parameters of the first non-standard QoS flow include the first parameter, and the QoS parameters of the second non-standard QoS flow include the first parameter.

[0394] In one possible design of this embodiment, the determining module 910 is configured to determine the CAPC of the first non-standard QoS flow as the CAPC of the associated radio bearer when the second parameter corresponding to the first non-standard QoS flow is of the first type;

[0395] In a case where the second parameter corresponding to the second non-standard QoS flow is of the first type, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated radio bearer.

[0396] The QoS parameters of the first non-standard QoS flow include the second parameter, and the QoS parameters of the second non-standard QoS flow include the second parameter;

[0397] In a possible design of this embodiment, the associated radio bearer includes a default radio bearer.

[0398] In some embodiments, the determining module 910 is further configured to determine the CAPC of the RLC PDU / SDU associated with the first non-standard QoS flow based on the CAPC of the first non-standard QoS flow.

[0399] In a possible design of this embodiment, the determination module 910 is used to determine the CAPC of the associated RLC PDU / SDU based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow, wherein the associated RLC PDU / SDU is the RLC PDU / SDU associated with the first non-standard QoS flow and the second non-standard QoS flow.

[0400] In one possible design of this embodiment, the determining module 910 is configured to determine the maximum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU; or

[0401] used to determine the minimum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU; or

[0402] used to determine any value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU; or

[0403] Used to determine the average of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU.

[0404] In one possible design of this embodiment, the determining module 910 is configured to determine the CAPC of the first non-standard QoS flow as the CAPC of the associated RLC PDU / SDU when the third parameter corresponding to the first non-standard QoS flow is the smallest;

[0405] When the third parameter corresponding to the second non-standard QoS flow is the smallest, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated RLC PDU / SDU.

[0406] The QoS parameters of the first non-standard QoS flow include the third parameter, and the QoS parameters of the second non-standard QoS flow include the third parameter.

[0407] In one possible design of this embodiment, the determining module 910 is configured to determine the CAPC of the first non-standard QoS flow as the CAPC of the associated RLC PDU / SDU when the fourth parameter corresponding to the first non-standard QoS flow is of the second type;

[0408] In a case where the fourth parameter corresponding to the second non-standard QoS flow is of the second type, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated RLC PDU / SDU.

[0409] The QoS parameters of the first non-standard QoS flow include the fourth parameter, and the QoS parameters of the second non-standard QoS flow include the fourth parameter.

[0410] In a possible design of this embodiment, the determination module 910 is configured to map the first non-standard QoS flow and the second non-standard QoS flow having the same CAPC to the same RLC PDU / SDU, and determine the CAPC of the same RLC PDU / SDU.

[0411] In a possible design of this embodiment, the determination module 910 is used to map the first non-standard QoS flow and the second non-standard QoS flow with similar CAPCs to the same RLC PDU / SDU, and determine the CAPCs of the same RLC PDU / SDU, where similar CAPCs are CAPCs whose CAPC value difference is less than a first threshold.

[0412] FIG10 shows a schematic structural diagram of a communication device 1000 provided by an exemplary embodiment of the present application. The communication device 1000 includes a processor 1001 , a receiver 1002 , a transmitter 1003 , a memory 1004 , and a bus 1005 .

[0413] The processor 1001 includes one or more processing cores. The processor 1001 executes various functional applications and information processing by running software programs and modules.

[0414] The receiver 1002 and the transmitter 1003 may be implemented as a communication component, which may be a communication chip, and may be referred to as a transceiver.

[0415] The memory 1004 is connected to the processor 1001 via a bus 1005 .

[0416] The memory 1004 may be used to store at least one instruction, and the processor 1001 may be used to execute the at least one instruction to implement each step in the above method embodiment.

[0417] In addition, the memory 1004 can be implemented by any type of volatile or non-volatile storage device or a combination thereof. Volatile or non-volatile storage devices include but are not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), read-only memory (ROM), magnetic memory, flash memory, and programmable read-only memory (PROM).

[0418] In one possible implementation, a processor in a communication device is configured to determine a CAPC of a first non-standard QoS flow.

[0419] In a possible implementation, a transceiver in the communication device is configured to transmit and receive a CAPC of a first non-standard QoS flow.

[0420] In one possible implementation, a processor in a communication device is configured to determine a CAPC of a radio bearer associated with the first non-standard QoS flow based on a CAPC of the first non-standard QoS flow.

[0421] In one possible implementation, a processor in a communication device is configured to determine a CAPC of an associated RLC PDU / SDU of the first non-standard QoS flow based on the CAPC of the first non-standard QoS flow.

[0422] In an exemplary embodiment, a computer-readable storage medium is also provided, in which at least one instruction, at least one program, code set or instruction set is stored, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by a processor to implement the method for determining the channel access priority level provided in the above-mentioned method embodiments.

[0423] In an exemplary embodiment, a computer program product is further provided. When the computer program product is executed on a processor of a computer device, the computer device implements the method for determining the channel access priority level provided in the above-mentioned various method embodiments.

[0424] Those skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware, or may be accomplished by a program instructing the relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk, or an optical disk, etc.

[0425] The above are only optional embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application.

Claims

1. A method for determining a channel access priority level, characterized in that: The method is executed by a terminal, and includes: A channel access priority level CAPC of a first non-standard quality of service flow QoS flow is determined.

2. The method according to claim 1, characterized in that Determining the CAPC of the first non-standard QoS flow includes at least one of the following: determining a CAPC for the first non-standard QoS flow based on one or more QoS parameters of the first non-standard QoS flow; Determining a CAPC for the first non-standard QoS flow based on information configured by the network for the first non-standard QoS flow; Based on the terminal implementation, determine the CAPC of the first non-standard QoS flow.

3. The method according to claim 2, characterized in that The determining, based on a quality of service (QoS) parameter of the first non-standard QoS flow, a CAPC of the first non-standard QoS flow includes: Determine a CAPC for the first non-standard QoS flow based on a parameter matching condition met by a QoS parameter of the first non-standard QoS flow.

4. The method according to claim 2, characterized in that The determining, based on the plurality of QoS parameters of the first non-standard QoS flow, the CAPC of the first non-standard QoS flow comprises: determining a CAPC for the first non-standard QoS flow based on a number of parameters of the plurality of QoS parameters of the first non-standard QoS flow that meet a matching condition corresponding to the first CAPC; The matching condition includes a parameter matching condition corresponding to each QoS parameter in the multiple QoS parameters.

5. The method according to claim 4, characterized in that The determining the CAPC of the first non-standard QoS flow based on the number of QoS parameters that meet the matching condition corresponding to the first CAPC among the multiple QoS parameters of the first non-standard QoS flow includes: If the multiple QoS parameters all meet the matching conditions corresponding to the first CAPC, determine the CAPC of the first non-standard QoS flow as the first CAPC; or When the number of parameters in the plurality of QoS parameters that meet the matching condition corresponding to the first CAPC reaches a first number, the CAPC of the first non-standard QoS flow is determined to be the first CAPC.

6. The method according to claim 5, characterized in that The determining, when the number of parameters that meet the matching condition corresponding to the first CAPC among the multiple QoS parameters reaches a first number, of the CAPC of the first non-standard QoS flow as the first CAPC includes: When it is determined according to the priorities that the number of parameters that meet the matching condition corresponding to the first CAPC among the multiple QoS parameters reaches the first number, determining the CAPC of the first non-standard QoS flow as the first CAPC; The priority is used to indicate the judgment order of the multiple QoS parameters.

7. The method according to any one of claims 3 to 6, characterized in that: The parameter matching condition includes at least one of the following: The value is consistent with the target value; The value falls within the target value range; The value type belongs to the target type; The value is the closest gear threshold among different gear thresholds, wherein the different gear thresholds correspond to different CAPCs.

8. The method according to claim 7, characterized in that The values ​​are consistent with the target values, including: In the case where the one or more QoS parameters include a packet delay budget (PDB), the value of the PDB complies with the target value; In the case where the one or more QoS parameters include a default priority DP, the value of the DP complies with the target value; In a case where the one or more QoS parameters include a packet error rate (PER), a value of the PER complies with the target value.

9. The method according to claim 7, characterized in that The values ​​fall within the target value range, including: In the case where the one or more QoS parameters include a PDB, a value of the PDB falls within the target value range; In a case where the one or more QoS parameters include PER, the value of the PER falls within the target value range.

10. The method according to claim 7, characterized in that The value type belongs to the target type, including: In the case where the one or more QoS parameters include a service type, a value type of the service type belongs to the target type; In the case that the one or more QoS parameters include a resource type, the value type of the resource type belongs to the target type.

11. The method according to claim 7, characterized in that The gear threshold value that is closest to the gear threshold value among different gear threshold values ​​includes: In the case where the one or more QoS parameters include a PDB, the value of the PDB is the gear threshold closest to the different gear thresholds; In a case where the one or more QoS parameters include PER, the value of the PER is the closest gear threshold among the different gear thresholds.

12. The method according to claim 7, characterized in that At least one of the target value, the target value range, the target type, and the gear threshold is determined by at least one of the following methods: Network device configuration; Communication protocol provisions.

13. The method according to claim 2, characterized in that The one or more QoS parameters include at least one of the following: PDB; DP; PER; Business type; Resource type.

14. The method according to claim 2, characterized in that The one or more QoS parameters are determined or selected by at least one of the following methods: Network device configuration; Communication protocol provisions; Select based on business type; Select based on resource type.

15. The method according to any one of claims 1 to 14, characterized in that: The state of the terminal when executing the method includes at least one of the following: Radio Resource Control RRC connected state; RRC idle state; RRC inactive state; Override outer state.

16. The method according to any one of claims 1 to 15, characterized in that The method further comprises: Based on the CAPC of the first non-standard QoS flow, determine the CAPC of the associated radio bearer of the first non-standard QoS flow.

17. The method according to claim 16, characterized in that The determining, based on the CAPC of the first non-standard QoS flow, a CAPC of a radio bearer associated with the first non-standard QoS flow includes: Based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow, a CAPC of an associated radio bearer is determined, wherein the associated radio bearer is the radio bearer associated with the first non-standard QoS flow and the second non-standard QoS flow.

18. The method according to claim 17, characterized in that The determining of the CAPC of the associated radio bearer based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow includes: Determine the maximum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer; or Determine the minimum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer; or Determine any value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer; or An average of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated radio bearer.

19. The method according to claim 17, wherein The QoS parameters of the first non-standard QoS flow include the first parameter, and the QoS parameters of the second non-standard QoS flow include the first parameter; The determining of the CAPC of the associated radio bearer based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow includes: When the first parameter corresponding to the first non-standard QoS flow is the smallest, determining the CAPC of the first non-standard QoS flow as the CAPC of the associated radio bearer; When the first parameter corresponding to the second non-standard QoS flow is the smallest, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated radio bearer.

20. The method according to claim 17, wherein The QoS parameters of the first non-standard QoS flow include the second parameter, and the QoS parameters of the second non-standard QoS flow include the second parameter; The determining of the CAPC of the associated radio bearer based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow includes: When the second parameter corresponding to the first non-standard QoS flow is of the first type, determining the CAPC of the first non-standard QoS flow as the CAPC of the associated radio bearer; In a case where the second parameter corresponding to the second non-standard QoS flow is of the first type, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated radio bearer.

21. The method according to any one of claims 16 to 20, characterized in that The associated radio bearer includes a default radio bearer.

22. The method according to any one of claims 1 to 21, characterized in that The method further comprises: Based on the CAPC of the first non-standard QoS flow, a CAPC of an associated radio link control service data unit / protocol data unit RLC PDU / SDU of the first non-standard QoS flow is determined.

23. The method according to claim 22, characterized in that The determining, based on the CAPC of the first non-standard QoS flow, a CAPC of a radio link control service data unit / protocol data unit RLC PDU / SDU associated with the first non-standard QoS flow includes: Based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow, determine the CAPC of the associated RLC PDU / SDU, wherein the associated RLC PDU / SDU is the RLC PDU / SDU associated with the first non-standard QoS flow and the second non-standard QoS flow.

24. The method according to claim 23, wherein The determining, based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow, the CAPC of the associated RLC PDU / SDU includes: Based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow being of the same priority, determining that the CAPC of the associated RLC PDU / SDU is of the same priority.

25. The method according to claim 23, characterized in that The determining, based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow, the CAPC of the associated RLC PDU / SDU includes: Based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow being of different priorities, the CAPC of the associated RLC PDU / SDU is determined to be one of the different priorities.

26. The method according to claim 25, characterized in that The determining, based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow having different priorities, that the CAPC of the associated RLC PDU / SDU is one of the different priorities, includes: Determine the maximum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU; or Determine the minimum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU; or Determine any value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU; or An average of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated RLC PDU / SDU.

27. The method according to claim 25, characterized in that The QoS parameters of the first non-standard QoS flow include a third parameter, and the QoS parameters of the second non-standard QoS flow include the third parameter; The determining, based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow having different priorities, that the CAPC of the associated RLC PDU / SDU is one of the different priorities, includes: When the third parameter corresponding to the first non-standard QoS flow is the smallest, determining the CAPC of the first non-standard QoS flow as the CAPC of the associated RLC PDU / SDU; When the third parameter corresponding to the second non-standard QoS flow is the smallest, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated RLC PDU / SDU.

28. The method according to claim 25, characterized in that The QoS parameters of the first non-standard QoS flow include a fourth parameter, and the QoS parameters of the second non-standard QoS flow include the fourth parameter; The determining, based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow having different priorities, that the CAPC of the associated RLC PDU / SDU is one of the different priorities, includes: When the fourth parameter corresponding to the first non-standard QoS flow is of the second type, determining the CAPC of the first non-standard QoS flow as the CAPC of the associated RLC PDU / SDU; In a case where the fourth parameter corresponding to the second non-standard QoS flow is the second type, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated RLC PDU / SDU.

29. The method according to claim 23, wherein The method further comprises at least one of the following: Mapping the first non-standard QoS flow and the second non-standard QoS flow having the same CAPC to the same RLC PDU / SDU, and determining the CAPC of the same RLC PDU / SDU; The first non-standard QoS flow and the second non-standard QoS flow with similar CAPC are mapped to the same RLC PDU / SDU, and the CAPC of the same RLC PDU / SDU is determined, wherein the similar CAPC is a CAPC whose CAPC value difference is less than a first threshold.

30. A method for determining a channel access priority level, characterized in that: The method is executed by a terminal, and includes: Based on the CAPC of the first non-standard QoS flow, determine the CAPC of the radio bearer associated with the first non-standard QoS flow.

31. The method according to claim 30, wherein The determining, based on the CAPC of the first non-standard QoS flow, a CAPC of a radio bearer associated with the first non-standard QoS flow includes: Based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow, a CAPC of an associated radio bearer is determined, wherein the associated radio bearer is the radio bearer associated with the first non-standard QoS flow and the second non-standard QoS flow.

32. The method according to claim 31, characterized in that The determining of the CAPC of the associated radio bearer based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow includes: Determine the maximum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer; or Determine the minimum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer; or Determine any value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated radio bearer; or An average of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated radio bearer.

33. The method according to claim 31, characterized in that The QoS parameters of the first non-standard QoS flow include the first parameter, and the QoS parameters of the second non-standard QoS flow include the first parameter; The determining of the CAPC of the associated radio bearer based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow includes: When the first parameter corresponding to the first non-standard QoS flow is the smallest, determining the CAPC of the first non-standard QoS flow as the CAPC of the associated radio bearer; When the first parameter corresponding to the second non-standard QoS flow is the smallest, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated radio bearer.

34. The method according to claim 31, wherein The QoS parameters of the first non-standard QoS flow include the second parameter, and the QoS parameters of the second non-standard QoS flow include the second parameter; The determining of the CAPC of the associated radio bearer based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow includes: When the second parameter corresponding to the first non-standard QoS flow is of the first type, determining the CAPC of the first non-standard QoS flow as the CAPC of the associated radio bearer; In a case where the second parameter corresponding to the second non-standard QoS flow is of the first type, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated radio bearer.

35. The method according to any one of claims 30 to 34, characterized in that The associated radio bearer includes a default radio bearer.

36. A method for determining a channel access priority level, characterized in that: The method is executed by a terminal, and includes: Based on the CAPC of the first non-standard QoS flow, a CAPC of an associated RLC PDU / SDU of the first non-standard QoS flow is determined.

37. The method according to claim 36, wherein The determining, based on the CAPC of the first non-standard QoS flow, a CAPC of a radio link control service data unit / protocol data unit RLC PDU / SDU associated with the first non-standard QoS flow includes: Based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow, determine the CAPC of the associated RLC PDU / SDU, wherein the associated RLC PDU / SDU is the RLC PDU / SDU associated with the first non-standard QoS flow and the second non-standard QoS flow.

38. The method according to claim 37, wherein The determining, based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow, the CAPC of the associated RLC PDU / SDU includes: Based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow being of the same priority, determining that the CAPC of the associated RLC PDU / SDU is of the same priority.

39. The method according to claim 37, wherein The determining, based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow, the CAPC of the associated RLC PDU / SDU includes: Based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow being of different priorities, the CAPC of the associated RLC PDU / SDU is determined to be one of the different priorities.

40. The method according to claim 39, wherein The determining, based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow having different priorities, that the CAPC of the associated RLC PDU / SDU is one of the different priorities, includes: Determine the maximum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU; or Determine the minimum value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU; or Determine any value of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow as the CAPC of the associated RLC PDU / SDU; or An average of the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated RLC PDU / SDU.

41. The method according to claim 39, wherein The QoS parameters of the first non-standard QoS flow include a third parameter, and the QoS parameters of the second non-standard QoS flow include the third parameter; The determining, based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow having different priorities, that the CAPC of the associated RLC PDU / SDU is one of the different priorities, includes: When the third parameter corresponding to the first non-standard QoS flow is the smallest, determining the CAPC of the first non-standard QoS flow as the CAPC of the associated RLC PDU / SDU; When the third parameter corresponding to the second non-standard QoS flow is the smallest, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated RLC PDU / SDU.

42. The method according to claim 39, wherein The QoS parameters of the first non-standard QoS flow include a fourth parameter, and the QoS parameters of the second non-standard QoS flow include the fourth parameter; The determining, based on the CAPC of the first non-standard QoS flow and the CAPC of the second non-standard QoS flow having different priorities, that the CAPC of the associated RLC PDU / SDU is one of the different priorities, includes: When the fourth parameter corresponding to the first non-standard QoS flow is of the second type, determining the CAPC of the first non-standard QoS flow as the CAPC of the associated RLC PDU / SDU; In a case where the fourth parameter corresponding to the second non-standard QoS flow is the second type, the CAPC of the second non-standard QoS flow is determined as the CAPC of the associated RLC PDU / SDU.

43. The method according to claim 37, wherein The method further comprises at least one of the following: Mapping the first non-standard QoS flow and the second non-standard QoS flow having the same CAPC to the same RLC PDU / SDU, and determining the CAPC of the same RLC PDU / SDU; The first non-standard QoS flow and the second non-standard QoS flow with similar CAPC are mapped to the same RLC PDU / SDU, and the CAPC of the same RLC PDU / SDU is determined, wherein the similar CAPC is a CAPC whose CAPC value difference is less than a first threshold.

44. A device for determining a channel access priority level, characterized in that: The device comprises: A determination module is configured to determine a CAPC for a first non-standard QoS flow.

45. A device for determining a channel access priority level, characterized in that: The device comprises: The determining module is configured to determine the CAPC of the radio bearer associated with the first non-standard QoS flow based on the CAPC of the first non-standard QoS flow.

46. ​​A device for determining a channel access priority level, characterized in that: The device comprises: A determination module is configured to determine a CAPC of an RLC PDU / SDU of the first non-standard QoS flow based on the CAPC of the first non-standard QoS flow.

47. A communication device, characterized in that The communication device comprises: processor; a transceiver connected to the processor; a memory for storing executable instructions for the processor; The processor is configured to load and execute the executable instructions to implement the method for determining the channel access priority level as described in any one of claims 1 to 43.

48. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which is loaded and executed by a processor to implement the method for determining the channel access priority level according to any one of claims 1 to 43.

49. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium. The processor obtains the computer instructions from the computer-readable storage medium, so that the processor loads and executes them to implement the method for determining the channel access priority level as described in any one of claims 1 to 43.

Images