CN116724657A

CN116724657A - Method and device for configuring side uplink Data Radio Bearer (DRB)

Info

Publication number: CN116724657A
Application number: CN202380008865.XA
Authority: CN
Inventors: 江小威
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2023-03-31
Filing date: 2023-03-31
Publication date: 2023-09-08

Abstract

The embodiment of the application discloses a configuration method and a device for a side-link Data Radio Bearer (DRB). By determining the Channel Access Priority (CAPC) of the side-link SL Data Radio Bearer (DRB), terminal equipment can determine the CAPC of the SL DRB no matter whether the network side is configured with the Channel Access Priority (CAPC) of the side-link data radio bearer (SL DRB) or not under the scene of a sidelink-U, and can Listen Before Talk (LBT) based on the CAPC in the subsequent communication process, thereby further realizing the transmission of the sidelink.

Description

Method and device for configuring side uplink Data Radio Bearer (DRB)

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for configuring a DRB of a side uplink data radio bearer.

Background

In order to support direct communication between the terminal equipment and the terminal equipment, a Side Link (SL) communication mode is introduced, and an interface between the terminal equipment and the terminal equipment is PC-5. The sidelink enhancement in R18 supports sidelink transmission over unlicensed spectrum, which requires listen before talk (Listen Before Talk, LBT), while channel access priority (Channel Access Priority Class, cap) is a parameter associated with LBT, different caps affect priority when competing for channels.

In the related art, the CAPC of the data signaling bearer (Data Radio Bearer, DRB) is configurable in a new air interface (New Radioin Unlicensed Spectrum, NR-U) scenario operating in an unlicensed band.

Disclosure of Invention

An embodiment of a first aspect of the present application proposes a method for configuring a side uplink data radio bearer DRB, the method being performed by a network device, the method comprising:

channel access priority CAPC of the side-link SL data radio bearer DRB is determined.

Optionally, the method further comprises:

and receiving first information sent by network equipment, wherein the first information is used for configuring the SL DRB, and the first information comprises CAPC of the SL DRB.

Optionally, the CAPC is an optional parameter in the first information.

Optionally, the first information is included in radio resource control RRC signaling or a system information block SIB.

Optionally, in a case where the network device is not configured with a CAPC of the SL DRB, the method further comprises:

determining CAPC corresponding to each QoS flow in at least one QoS flow mapped to the SL DRB;

and determining the CAPC of the SL DRB according to the CAPC corresponding to each QoS flow.

Optionally, the determining the CAPC of the SL DRB according to the CAPC corresponding to each QoS flow includes:

And determining the CAPC with the minimum value in the CAPCs corresponding to the at least one QoS flow as the CAPC of the SL DRB.

determining an average value of the caps corresponding to the at least one QoS flow as the caps of the SL DRBs; or alternatively, the process may be performed,

and determining the intermediate value of the CAPC corresponding to the at least one QoS flow as the CAPC of the SL DRB.

Optionally, the determining the CAPC corresponding to each QoS flow in the at least one QoS flow mapped to the SL DRB includes:

determining a PC5 interface quality of service identifier PQI of each QoS flow;

if the PQI of the QoS flow is a standard PQI, determining the CAPC corresponding to the standard PQI as the CAPC corresponding to the QoS flow;

in the case that the PQI of the QoS flow is a nonstandard PQI, determining a CAPC corresponding to one standard PQI matched with the nonstandard PQI as the CAPC corresponding to the QoS flow.

Optionally, one standard PQI that matches the non-standard PQI is a standard PQI that differs minimally from the packet delay budget PDB of the non-standard PQI; and/or the number of the groups of groups,

one standard PQI that matches the non-standard PQI is the standard PQI that differs minimally from the default priority of the non-standard PQI.

Optionally, in a case where the network device is not configured with a CAPC of the SL DRB, the determining the channel access priority CAPC of the side uplink SL data radio bearer DRB includes:

and determining the CAPC of the SL DRB according to the implementation of the terminal equipment.

An embodiment of a second aspect of the present application proposes a side uplink data radio bearer DRB configuration apparatus, the apparatus comprising:

a processing unit for determining a channel access priority CAPC of the side-link SL data radio bearer DRB.

Optionally, the apparatus further comprises:

and the receiving and transmitting unit is used for receiving first information sent by the network equipment, wherein the first information is used for configuring the SL DRB, and the first information comprises CAPC of the SL DRB.

Optionally, the CAPC is an optional parameter in the first information.

Optionally, the processing unit is further configured to:

Optionally, the processing unit is specifically configured to:

determining a PC5 interface quality of service identifier PQI of each QoS flow;

Optionally, the processing unit is specifically configured to:

and determining the CAPC of the SL DRB according to the implementation of the device.

An embodiment of a third aspect of the present application proposes a communication device, the device comprising a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory, to cause the device to execute the side uplink data radio bearer DRB configuration method according to the embodiment of the first aspect.

An embodiment of a fourth aspect of the present application proposes a communication device, the device comprising a processor and an interface circuit for receiving code instructions and transmitting to the processor, the processor being configured to execute the code instructions to cause the device to perform the method for configuring a sidelink data radio bearer DRB as described in the embodiment of the first aspect.

An embodiment of a fifth aspect of the present application proposes a computer readable storage medium storing instructions that, when executed, cause the side uplink data radio bearer DRB configuration method described in the above embodiment of the first aspect to be implemented.

An embodiment of a sixth aspect of the present application proposes a computer program which, when run on a computer, causes the computer to perform the side uplink data radio bearer DRB configuration method of the embodiment of the first aspect.

According to the configuration method and device for the side-link data radio bearer DRB, the channel access priority CAPC of the side-link SL data radio bearer DRB is determined, so that terminal equipment can determine the CAPC of the SL DRB no matter whether the network side is configured with the channel access priority CAPC of the side-link data radio bearer SL DRB or not under the scene of a sidelink-U, and can listen before talk LBT based on the CAPC in the subsequent communication process, so that the transmission of the sidelink is further realized.

Additional aspects and advantages of the application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the application.

Drawings

In order to more clearly describe the embodiments of the present application or the technical solutions in the background art, the following description will describe the drawings that are required to be used in the embodiments of the present application or the background art.

Fig. 1a is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 1b is a schematic diagram of PDCCH resource mapping according to an embodiment of the present application;

fig. 2 is a flow chart of a SL DRB configuration method according to an embodiment of the present application;

Fig. 3 is a flow chart of a SL DRB configuration method according to an embodiment of the present application;

fig. 4 is a flow chart of a SL DRB configuration method according to an embodiment of the present application;

fig. 5 is a flow chart of a SL DRB configuration method according to an embodiment of the present application;

fig. 6 is a flow chart of a SL DRB configuration method according to an embodiment of the present application;

fig. 7 is a flow chart of a SL DRB configuration method according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of an SL DRB configuration apparatus according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of another SL DRB configuration apparatus according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a chip according to an embodiment of the disclosure.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with embodiments of the application. Rather, they are merely examples of apparatus and methods consistent with aspects of embodiments of the application as detailed in the accompanying claims.

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

It should be understood that although the terms first, second, third, etc. may be used in embodiments of the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of embodiments of the present application. The words "if" and "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination", depending on the context.

Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the like or similar elements throughout. The embodiments described below by referring to the drawings are illustrative and intended to explain the present application and should not be construed as limiting the application.

In order to better understand a configuration method of a side uplink data radio bearer DRB disclosed in the embodiments of the present application, a description is first given below of a communication system to which the embodiments of the present application are applicable.

Referring to fig. 1a, fig. 1a is a schematic diagram of a communication system according to an embodiment of the application. The communication system may include, but is not limited to, a network device and a first terminal device and a second terminal device, and the number and form of devices shown in fig. 1a are only used as examples and not to limit the embodiments of the present application, and may include two or more network devices and two or more terminal devices in practical applications. The communication system shown in fig. 1a is exemplified as comprising a first terminal device 101, a second terminal device 102 and a network device 103.

It should be noted that the technical solution of the embodiment of the present application may be applied to various communication systems. For example: long term evolution (Long Term Evolution, LTE) system, railway global system for mobile communications (Global System for Mobile Communications-Railway, GSM-R), fifth generation mobile communications system, 5G new air interface system, or other future new mobile communications systems, etc.

The network device 103 in the embodiment of the present application is an entity for transmitting or receiving signals on the network side. For example, the network device 103 and an access node which may be an Evolved NodeB (eNB), a transmission point (Transmission Reception Point, TRP), a Next Generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems or a wireless fidelity (Wireless Fidelity, wiFi) system, etc. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the network equipment. The network device provided by the embodiment of the application can be composed of a Centralized Unit (CU) and a Distributed Unit (DU), wherein the CU can also be called a Control Unit (Control Unit), the protocol layers of the network device such as a base station can be separated by adopting the structure of the CU-DU, the functions of part of the protocol layers are placed in the CU for centralized Control, the functions of the rest part or all of the protocol layers are Distributed in the DU, and the DU is centralized controlled by the CU.

The first terminal device 101 and the second terminal device 102 in the embodiment of the present application are both an entity on the user side for receiving or transmitting signals, such as a mobile phone. The Terminal device may also be referred to as a Terminal device (Terminal), a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal device (MT), etc. The terminal device may be an automobile with communication function, a Smart car, a Mobile Phone (Mobile Phone), an internet of things (Internet of Things, ioT) terminal, a wearable device, a tablet (Pad), a computer with wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (Industrial Control), a wireless terminal device in Self-Driving, a wireless terminal device in teleoperation (Remote Medical Surgery), a wireless terminal device in Smart Grid (Smart Grid), a wireless terminal device in transportation security (Transportation Safety), a wireless terminal device in Smart City (Smart City), a wireless terminal device in Smart Home (Smart Home), and the like. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the terminal equipment.

In order to support direct communication between the terminal equipment and the terminal equipment, a Side Link (SL) communication mode is introduced, and an interface between the terminal equipment and the terminal equipment is PC-5 (bottom layer direct connection cellular communication protocol interface). The sidelink communication supports two terminal device states, as shown in fig. 1b, and the terminal device under the network coverage (in coverage) and the terminal device not under the network coverage (out of coverage, OOC) can perform the sidelink communication. The terminal device in coverage may be in a radio resource control (Radio Resources Control, RRC) connected state (connected), or an RRC IDLE state (IDLE), or an RRC INACTIVE state (INACTIVE).

The sidelink enhancement in R18 supports sidelink transmission on unlicensed spectrum, which requires listen before talk (Listen Before Talk, LBT), and the channel access priority (Channel Access Priority Class, cap) is a parameter related to LBT, and a smaller cap value indicates a higher priority when different caps affect the priority when competing for channels.

In the related art, in a new air interface (New Radioin Unlicensed Spectrum, NR-U) scenario operating in an unlicensed band, channel access for both downlink and uplink depends on LBT characteristics. The wireless device or base station must first "perceive" the communication channel and discover that there is no communication prior to any transmission. When a communication channel is an unlicensed wideband carrier, the LBT procedure relies on detecting energy levels over multiple subbands of the communication channel. LBT parameters (e.g., type/duration, clear channel assessment parameters, etc.) are configured by the base station on the wireless device. In the NR-U, the CAPC of the data signaling bearers (Data Radio Bearer, DRB) is configurable.

In the side-link (sidelinkin Unlicensed Spectrum, sidelink-U) scenario operating in unlicensed band, there may be a case where the network does not configure the CAPC of a SL DRB, and how the terminal device determines the CAPC of the SL DRB is a currently unsolved problem.

It may be understood that, the communication system described in the embodiment of the present application is for more clearly describing the technical solution of the embodiment of the present application, and is not limited to the technical solution provided in the embodiment of the present application, and those skilled in the art can know that, with the evolution of the system architecture and the appearance of the new service scenario, the technical solution provided in the embodiment of the present application is equally applicable to similar technical problems.

The method and apparatus for configuring a side uplink data radio bearer DRB according to the present application are described in detail below with reference to the accompanying drawings.

Referring to fig. 2, fig. 2 is a flowchart of a configuration method of a side uplink data radio bearer DRB according to an embodiment of the present application. It should be noted that, the configuration method of the side uplink data radio bearer DRB in the embodiment of the present application is executed by the terminal device. The method may be performed independently or in combination with any of the other embodiments of the application. As shown in fig. 2, the method may include the steps of:

Step 201, determining a channel access priority CAPC of a side uplink SL data radio bearer DRB.

In the embodiment of the application, the terminal equipment can determine the channel access priority CAPC of the SL DRB of the terminal equipment and carry out subsequent sidelink transmission based on the CAPC.

In an embodiment of the present application, the sidelink transmission may be in an unlicensed band.

In some embodiments, the terminal device is capable of receiving first information sent by the network device, where the first information is used to configure the SL DRB, and the first information includes the CAPC.

It should be noted that the CAPC is an optional (mandatory present) parameter in the first information, that is, the network device has to carry the CAPC configuration of the SL DRB in the configuration of the SL DRB.

Alternatively, the first information may be included in RRC signaling, or the first information may be included in a system information block (System Information Block, SIB). Alternatively, the first information may be preconfigured to the terminal device by the network side.

It can be appreciated that the terminal device in RRC connected state can acquire the configuration of the SL DRB of the network device (i.e., the first information) through dedicated RRC signaling; terminal equipment in an RRC idle state or an RRC inactive state can acquire the configuration of SL DRB through SIB; the OOC-capable terminal device may obtain the configuration of the SL DRB through the pre-configuration of the network device.

In some embodiments, the network device is not configured with a CAPC of the SL DRB, in which case the terminal device may determine a CAPC corresponding to each QoS flow in at least one quality of service (Quality of Service, qoS) flow (flow) mapped to the SL DRB, and may be able to determine the CAPC of the SL DRB based on the CAPC corresponding to each QoS flow.

Alternatively, the lowest value of the caps corresponding to the at least one QoS flow may be determined as the cap of the SL DRB.

Alternatively, an average value of the CAPCs corresponding to the at least one QoS flow may also be determined as the CAPCs of the SL DRBs; or alternatively, the process may be performed,

The terminal device can determine the CAPCs corresponding to each QoS flow, specifically:

the terminal equipment can determine a PC5 interface service quality identifier (PC-5QoS Indicator,PQI) of each QoS flow, and when the PQI of the QoS flow is a standard PQI, the CAPC corresponding to the standard PQI is determined as the CAPC corresponding to the QoS flow; if the PQI of the QoS flow is a nonstandard PQI, a cap corresponding to one standard PQI that matches the nonstandard PQI is determined as the cap corresponding to the QoS flow.

Alternatively, a standard PQI that matches the non-standard PQI is one that best matches the QoS attribute of the non-standard PQI.

As one possible implementation, a standard PQI that matches the non-standard PQI is a standard PQI that differs minimally from the packet delay budget (Packet Delay Budget, PDB) of the non-standard PQI.

As another possible implementation, a standard PQI that matches the non-standard PQI is a standard PQI that differs minimally from the default priority (default priority) of the non-standard PQI.

As yet another possible implementation, one standard PQI that matches the non-standard PQI is a standard PQI that has the smallest packet delay budget PDB for the non-standard PQI and the smallest default priority for the non-standard PQI.

As an example, the terminal device may consider the standard PQI with the smallest packet delay budget PDB gap as the standard PQI that best matches this non-standard PQI. When the PDB differences of the plurality of standard PQI are the same as the non-standard PQI, the terminal device may further select a standard PQI having a smallest default priority difference from the non-standard PQI among the standard PQI as a standard PQI that best matches the non-standard PQI.

It should be noted that, the PQI parameter is carried in the QoS information, and the value of the PQI may reflect the QoS attribute to a certain extent, and the influence on the value of the PQI includes, but is not limited to, priority, delay tolerance, bit error rate, and the like. Standard PQI is a value for some PQI specified in the prior art.

And the CAPC corresponding to the standard PQI can be determined by a mapping relation table between the CAPC and the PQI.

As an example, the mapping relationship of standard PQI and CAPC is as follows:

the standard PQI value is 90/91/92/93/21/22/23/55/56/57/58, which corresponds to CAPC priority level 1;

the standard PQI value is 59/61 corresponding to CAPC priority level 3;

the standard PQI value is 25 and corresponds to CAPC priority level 2;

the standard PQI value is 24/26/60 corresponding to CAPC priority level 1.

In some embodiments, the network device is not configured with a CAPC of the SL DRB, in which case the terminal device can also determine the CAPC of the SL DRB based on its implementation.

That is, the terminal device may flexibly determine the CAPC of the SL DRB according to the actual communication implementation situation by itself. As a possible implementation, the maximum value of the CAPCs corresponding to the at least one QoS flow mapped to the SL DRB may be determined as the CAPC of the SL DRB, or the CAPC of the SL DRB may be determined as priority level 2 by default, or the like, which is not limited herein.

In summary, by determining the channel access priority CAPC of the side link SL data radio bearer DRB, the terminal device can determine the CAPC of the side link SL data radio bearer regardless of whether the network side configures the channel access priority CAPC of the side link SL data radio bearer DRB in the scenario of the sidelink-U, and can perform listen-before-talk LBT based on the CAPC in the subsequent communication process, so as to further realize the transmission of the sidelink.

Referring to fig. 3, fig. 3 is a flowchart of a configuration method of a side uplink data radio bearer DRB according to an embodiment of the present application. It should be noted that, the configuration method of the side uplink data radio bearer DRB in the embodiment of the present application is executed by the terminal device. The method may be performed independently or in combination with any of the other embodiments of the application. As shown in fig. 3, the method may include the steps of:

step 301, receiving first information sent by a network device, where the first information is used to configure a SL DRB, and the first information includes a CAPC of the SL DRB.

In the embodiment of the application, the terminal equipment can receive the first information for configuring the SL DRB sent by the network equipment and determine the CAPC of the SL DRB according to the first information.

Alternatively, the first information may be included in RRC signaling, or the first information may be included in SIB. Alternatively, the first information may be preconfigured to the terminal device by the network side.

In the embodiment of the present application, when the network device configures the cap for the SL DRB, the PQI of all QoS flows multiplexed to the SLDRB may be considered, and fairness among different service types is comprehensively considered to configure the cap for the SL DRB.

Step 302, determining a CAPC of the SL DRB based on the first information.

In the embodiment of the application, the terminal equipment can determine the CAPC of the SL DRB based on the configuration of the network equipment.

In summary, by receiving first information sent by a network device, where the first information is used to configure a SL DRB, where the first information includes a CAPC of the SL DRB, determining, based on the first information, a CAPC of the SL DRB, where it is specified that in a scenario of a sidelink-U, the network side must configure the CAPC of the SL DRB, so that in the scenario of the sidelink-U, a terminal device may determine the CAPC of the SL DRB, and in a subsequent communication process, may perform listen before talk LBT based on the CAPC, thereby further implementing the transmission of the sidelink.

Referring to fig. 4, fig. 4 is a flowchart of a configuration method of a side uplink data radio bearer DRB according to an embodiment of the present application. It should be noted that, the configuration method of the side uplink data radio bearer DRB in the embodiment of the present application is executed by the terminal device. The method may be performed independently or in combination with any of the other embodiments of the application. As shown in fig. 4, the method may include the steps of:

in step 401, in the case that the network device is not configured with a CAPC of the SL DRB, a corresponding CAPC of each QoS flow in at least one QoS flow mapped to the SL DRB is determined.

In the embodiment of the present application, in the case that the network device is not configured with the CAPCs of the SL DRB, the terminal device can determine the CAPCs corresponding to at least one QoS flow mapped to the SL DRB, and can further determine the CAPCs of the SL DRB according to the CAPCs corresponding to the QoS flows.

In the embodiment of the present application, the terminal device can determine the CAPCs corresponding to each QoS flow, specifically:

the terminal device can determine the PQI of each QoS flow. If the PQI of the QoS flow is a standard PQI, determining a cap corresponding to the standard PQI as a cap corresponding to the QoS flow; if the PQI of the QoS flow is a nonstandard PQI, a cap corresponding to one standard PQI that matches the nonstandard PQI is determined as the cap corresponding to the QoS flow.

As one possible implementation, one standard PQI that best matches the non-standard PQI is the standard PQI that differs minimally from the packet delay budget PDB of the non-standard PQI.

As another possible implementation, one standard PQI that best matches the non-standard PQI is the standard PQI that differs least from the default priority (default priority) of the non-standard PQI.

As yet another possible implementation, one standard PQI that best matches the non-standard PQI is a standard PQI that has the smallest packet delay budget PDB for the non-standard PQI and the smallest default priority for the non-standard PQI.

As an example, the mapping relationship of standard PQI and CAPC is as follows:

the standard PQI value is 59/61 corresponding to CAPC priority level 3;

the standard PQI value is 25 and corresponds to CAPC priority level 2;

the standard PQI value is 24/26/60 corresponding to CAPC priority level 1.

Step 402, determining the CAPC with the smallest value in the CAPCs corresponding to the at least one QoS flow as the CAPC of the SL DRB.

In the embodiment of the present application, after determining the CAPC corresponding to at least one QoS flow mapped to the SL DRB, the terminal device can determine the CAPC with the smallest value in the CAPCs corresponding to the at least one QoS flow as the CAPC of the SL DRB.

As an example, if there is a priority level of 1, a priority level of 2, and a priority level of 3 in the caps corresponding to at least one QoS flow mapped to the SL DRB, the terminal device determines that the cap of the SL DRB is 1.

In summary, by determining, when the network device does not configure the CAPCs of the SL DRBs, the CAPCs corresponding to each QoS flow in at least one QoS flow mapped to the SL DRBs, and determining the CAPC with the smallest value in the CAPCs corresponding to the at least one QoS flow as the CAPCs of the SL DRBs, the terminal device can still determine the CAPCs of the SL DRBs when the network side does not configure the channel access priority CAPCs of the side uplink data radio bearers SL DRBs in the scenario of the sidelink-U, and can listen before talk LBT based on the CAPCs in the process of subsequent communication, so as to further realize the transmission of the sidelink.

Referring to fig. 5, fig. 5 is a flowchart of a configuration method of a side uplink data radio bearer DRB according to an embodiment of the present application. It should be noted that, the configuration method of the side uplink data radio bearer DRB in the embodiment of the present application is executed by the terminal device. The method may be performed independently or in combination with any of the other embodiments of the application. As shown in fig. 5, the method may include the steps of:

in step 501, in the case that the network device does not configure the CAPCs of the SL DRB, a corresponding CAPC of each QoS flow in at least one QoS flow mapped to the SL DRB is determined.

As an example, the mapping relationship of standard PQI and CAPC is as follows:

the standard PQI value is 59/61 corresponding to CAPC priority level 3;

the standard PQI value is 25 and corresponds to CAPC priority level 2;

the standard PQI value is 24/26/60 corresponding to CAPC priority level 1.

Step 502, determining an average value of the CAPCs corresponding to the at least one QoS flow as the CAPCs of the SL DRB.

In the embodiment of the present application, after determining the CAPCs corresponding to the at least one QoS flow mapped to the SL DRB, the terminal device can determine an average value of the CAPCs corresponding to the at least one QoS flow as the CAPCs of the SL DRB.

As an example, the terminal device may determine that the cap of the SL DRB is 2, with a priority level of 1 and a priority level of 3 in the caps corresponding to the at least one QoS flow mapped to the SL DRB.

It is understood that if it is determined that the average value of the CAPCs corresponding to the QoS flows is not an integer, a rounding operation may be performed.

In summary, by determining, when the network device does not configure the CAPCs of the SL DRBs, the CAPCs corresponding to each QoS flow in at least one QoS flow mapped to the SL DRBs, and determining an average value of the CAPCs corresponding to the at least one QoS flow as the CAPCs of the SL DRBs, the terminal device can still determine the CAPCs of the SL DRBs when the network side does not configure the channel access priority CAPCs of the SL DRBs in the scenario of the sidelink-U, and can perform listen before talk LBT based on the CAPCs in the subsequent communication process, so as to further implement the transmission of the sidelink.

Referring to fig. 6, fig. 6 is a flowchart of a configuration method of a side uplink data radio bearer DRB according to an embodiment of the present application. It should be noted that, the configuration method of the side uplink data radio bearer DRB in the embodiment of the present application is executed by the terminal device. The method may be performed independently or in combination with any of the other embodiments of the application. As shown in fig. 6, the method may include the steps of:

in step 601, in the case that the network device is not configured with a CAPC of the SL DRB, a corresponding CAPC of each QoS flow in at least one QoS flow mapped to the SL DRB is determined.

As an example, the mapping relationship of standard PQI and CAPC is as follows:

the standard PQI value is 59/61 corresponding to CAPC priority level 3;

the standard PQI value is 25 and corresponds to CAPC priority level 2;

the standard PQI value is 24/26/60 corresponding to CAPC priority level 1.

Step 602, determining an intermediate value of the CAPCs corresponding to the at least one QoS flow as the CAPCs of the SL DRB.

In the embodiment of the present application, after determining the CAPCs corresponding to the at least one QoS flow mapped to the SL DRB, the terminal device can determine the intermediate value of the CAPCs corresponding to the at least one QoS flow as the CAPCs of the SL DRB.

As an example, the terminal device may perform an operation of obtaining an intermediate value, for example, determining that the intermediate value is 2 finally, and the CAPC of the SL DRB is 2, where the CAPC corresponding to the at least one QoS flow mapped to the SL DRB has a priority level of 1, a priority level of 2, and a priority level of 3.

In summary, by determining, when the network device does not configure the CAPCs of the SL DRBs, the CAPCs corresponding to each QoS flow in at least one QoS flow mapped to the SL DRBs, and determining the intermediate value of the CAPCs corresponding to the at least one QoS flow as the CAPCs of the SL DRBs, the terminal device can still determine the CAPCs of the SL DRBs when the network side does not configure the channel access priority CAPCs of the SL DRBs in the scenario of the sidelink-U, and can perform listen before talk LBT based on the CAPCs in the subsequent communication process, so as to further implement the transmission of the sidelink.

Referring to fig. 7, fig. 7 is a flowchart of a configuration method of a side uplink data radio bearer DRB according to an embodiment of the present application. It should be noted that, the configuration method of the side uplink data radio bearer DRB in the embodiment of the present application is executed by the terminal device. The method may be performed independently or in combination with any of the other embodiments of the application. As shown in fig. 7, the method may include the steps of:

in step 701, in the case that the network device is not configured with the CAPCs of the SL DRBs, the CAPCs of the SL DRBs are determined according to the implementation of the terminal device.

In the embodiment of the present application, the network device does not configure the CAPCs of the SL DRBs, in which case the terminal device can determine the CAPCs of the SL DRBs according to its implementation.

That is, the terminal device may flexibly determine the CAPC of the SL DRB according to the actual communication implementation situation by itself.

As a possible implementation, the terminal device may determine the maximum value of the CAPCs corresponding to the at least one QoS flow mapped to the SL DRB as the CAPCs of the SL DRB, may determine the minimum value of the CAPCs corresponding to the at least one QoS flow as the CAPCs of the SL DRB, may determine the CAPCs of the SL DRB as priority level 2 by default, and so on, which embodiments of the present application are not limited herein.

In summary, by determining the CAPC of the SL DRB according to the implementation of the terminal device in the case that the network device is not configured with the CAPC of the SL DRB, the terminal device can still determine the CAPC of the SL DRB in the case that the network side is not configured with the channel access priority CAPC of the SL DRB in the scenario of the sidelink-U, and can listen before talk LBT based on the CAPC in the subsequent communication process, so as to further implement the transmission of the sidelink.

The present application also provides a configuration device for a side uplink data radio bearer corresponding to the configuration method for a side uplink data radio bearer provided in the above-mentioned embodiments, and since the configuration device for a side uplink data radio bearer provided in the embodiment of the present application corresponds to the configuration method provided in the above-mentioned embodiments, implementation of the configuration method for a side uplink data radio bearer is also applicable to the configuration device for a side uplink data radio bearer provided in the below-mentioned embodiments, which will not be described in detail in the below-mentioned embodiments.

Referring to fig. 8, fig. 8 is a schematic structural diagram of a configuration apparatus for a side uplink data radio bearer DRB according to an embodiment of the present application.

As shown in fig. 8, the side uplink data radio bearer DRB configuration apparatus 800 includes: a processing unit 810, wherein:

a processing unit 810 is configured to determine a channel access priority CAPC of the side-link SL data radio bearer DRB.

Optionally, the apparatus further comprises:

a transceiver unit (not shown in the figure) for receiving first information sent by the network device, where the first information is used to configure the SL DRB, and the first information includes a CAPC of the SL DRB.

Optionally, the CAPC is an optional parameter in the first information.

Optionally, the first information is included in a radio resource control RRC signaling or system information block SIB.

Optionally, the processing unit 810 is further configured to:

Optionally, the processing unit 810 is specifically configured to:

determining a PC5 interface quality of service identifier PQI for each QoS flow;

if the PQI of the QoS flow is a standard PQI, determining a cap corresponding to the standard PQI as a cap corresponding to the QoS flow;

if the PQI of the QoS flow is a nonstandard PQI, a cap corresponding to one standard PQI that matches the nonstandard PQI is determined as the cap corresponding to the QoS flow.

Alternatively, one standard PQI that matches the non-standard PQI is a standard PQI that differs minimally from the packet delay budget PDB of the non-standard PQI; and/or the number of the groups of groups,

Optionally, the processing unit 810 is specifically configured to:

according to the implementation of the apparatus, a CAPC of the SL DRB is determined.

The configuration device of the side-link data radio bearer DRB in this embodiment can determine the channel access priority CAPC of the side-link SL data radio bearer DRB, so that the terminal device can determine the CAPC of the SL DRB regardless of whether the network side configures the channel access priority CAPC of the side-link data radio bearer SL DRB in the scene of the sidelink-U, and can perform listen-before-talk LBT based on the CAPC in the subsequent communication process, thereby further realizing the transmission of the sidelink.

In order to achieve the above embodiments, an embodiment of the present application further provides a communication device, including: a processor and a memory in which a computer program is stored, the processor executing the computer program stored in the memory to cause the apparatus to perform the method shown in the embodiments of fig. 2 to 7.

In order to achieve the above embodiments, an embodiment of the present application further provides a communication device, including: a processor and interface circuitry for receiving code instructions and transmitting to the processor, the processor for executing the code instructions to perform the methods shown in the embodiments of fig. 2-7.

Referring to fig. 9, fig. 9 is a schematic structural diagram of another configuration apparatus for a side uplink data radio bearer DRB according to an embodiment of the present disclosure. The side uplink data radio bearer DRB configuration apparatus 900 may be a network device, a terminal device, a chip system, a processor or the like that supports the network device to implement the above method, or a chip, a chip system, a processor or the like that supports the terminal device to implement the above method. The device can be used for realizing the method described in the method embodiment, and can be particularly referred to the description in the method embodiment.

The side-uplink data radio bearer DRB configuration apparatus 900 may include one or more processors 901. The processor 901 may be a general purpose processor or a special purpose processor, etc. For example, a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processor may be used to control the side-link data radio bearer DRB configuration means (e.g., base station, baseband chip, terminal device chip, DU or CU, etc.), execute the computer program, and process the data of the computer program.

Optionally, the side uplink data radio bearer DRB configuration apparatus 900 may further include one or more memories 902, on which a computer program 903 may be stored, and the processor 901 executes the computer program 903, so that the side uplink data radio bearer DRB configuration apparatus 900 performs the method described in the above method embodiments. The computer program 903 may be solidified in the processor 901, in which case the processor 901 may be implemented in hardware.

Optionally, the memory 902 may also have data stored therein. The side-uplink data radio bearer DRB configuration means 900 and the memory 902 may be provided separately or may be integrated.

Optionally, the side uplink data radio bearer DRB configuration apparatus 900 may further comprise a transceiver 905, an antenna 906. The transceiver 905 may be referred to as a transceiver unit, transceiver circuitry, or the like, for implementing a transceiver function. The transceiver 905 may include a receiver, which may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function, and a transmitter; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.

Optionally, one or more interface circuits 907 may also be included in the side-uplink data radio bearer DRB configuration device 900. The interface circuit 907 is used to receive code instructions and transmit them to the processor 901. The processor 901 executes code instructions to cause the side-uplink data radio bearer DRB configuration apparatus 900 to perform the methods described in the method embodiments described above.

In one implementation, a transceiver for implementing the receive and transmit functions may be included in processor 901. For example, the transceiver may be a transceiver circuit, or an interface circuit. The transceiver circuitry, interface or interface circuitry for implementing the receive and transmit functions may be separate or may be integrated. The transceiver circuit, interface or interface circuit may be used for reading and writing codes/data, or the transceiver circuit, interface or interface circuit may be used for transmitting or transferring signals.

In one implementation, the side-uplink data radio bearer DRB configuration apparatus 900 may include circuitry that may implement the functions of transmitting or receiving or communicating in the foregoing method embodiments. The processors and transceivers described in this disclosure may be implemented on integrated circuits (integrated circuit, ICs), analog ICs, radio frequency integrated circuits RFICs, mixed signal ICs, application specific integrated circuits (application specific integrated circuit, ASIC), printed circuit boards (printed circuit board, PCB), electronic devices, and the like. The processor and transceiver may also be fabricated using a variety of IC process technologies such as complementary metal oxide semiconductor (complementary metal oxide semiconductor, CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

The side-uplink data radio bearer DRB configuration means in the above embodiment description may be a network device or a terminal device, but the scope of the side-uplink data radio bearer DRB configuration means described in the present disclosure is not limited thereto, and the structure of the side-uplink data radio bearer DRB configuration means may not be limited by fig. 8. The side-uplink data radio bearer DRB configuration means may be a stand alone device or may be part of a larger device. For example, the side-uplink data radio bearer DRB configuration means may be:

(1) A stand-alone integrated circuit IC, or chip, or a system-on-a-chip or subsystem;

(2) A set of one or more ICs, optionally including storage means for storing data, a computer program;

(3) An ASIC, such as a Modem (Modem);

(4) Modules that may be embedded within other devices;

(5) A receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handset, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligent device, and the like;

(6) Others, and so on.

For the case where the side-uplink data radio bearer DRB configuration means may be a chip or a system of chips, reference may be made to the schematic diagram of the chip shown in fig. 10. The chip shown in fig. 10 includes a processor 1001 and an interface 1002. Wherein the number of processors 1001 may be one or more, and the number of interfaces 1002 may be a plurality.

For the case where the chip is used to implement the functions of the terminal device in the embodiments of the present disclosure:

an interface 1002 for code instructions and transmitting to the processor;

a processor 1001 for executing code instructions to perform the methods of fig. 2-7.

Optionally, the chip further comprises a memory 1003, the memory 1003 being used for storing the necessary computer programs and data.

Those of skill in the art will further appreciate that the various illustrative logical blocks (illustrative logical block) and steps (step) described in connection with the embodiments of the disclosure may be implemented by electronic hardware, computer software, or combinations of both. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Those skilled in the art may implement the functionality in a variety of ways for each particular application, but such implementation should not be construed as beyond the scope of the embodiments of the present disclosure.

The disclosed embodiments also provide a communication system comprising the aforementioned side-uplink data radio bearer DRB configuration apparatus as a terminal device in the embodiment of fig. 8, or the system comprises the aforementioned side-uplink data radio bearer DRB configuration apparatus as a terminal device in the embodiment of fig. 9.

The present disclosure also provides a readable storage medium having instructions stored thereon which, when executed by a computer, perform the functions of any of the method embodiments described above.

The present disclosure also provides a computer program product which, when executed by a computer, performs the functions of any of the method embodiments described above.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer programs. When the computer program is loaded and executed on a computer, the flow or functions in accordance with embodiments of the present disclosure are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer program may be stored in or transmitted from one computer readable storage medium to another, for example, a website, computer, server, or data center via a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) connection. Computer readable storage media can be any available media that can be accessed by a computer or data storage devices, such as servers, data centers, etc., that contain an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Those of ordinary skill in the art will appreciate that: the various numbers of first, second, etc. referred to in this disclosure are merely for ease of description and are not intended to limit the scope of embodiments of this disclosure, nor to indicate sequencing.

At least one of the present disclosure may also be described as one or more, a plurality may be two, three, four or more, and the present disclosure is not limited. In the embodiment of the disclosure, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "a", "B", "C", and "D", and the technical features described by "first", "second", "third", "a", "B", "C", and "D" are not in sequence or in order of magnitude.

The correspondence relationships shown in the tables in the present disclosure may be configured or predefined. The values of the information in each table are merely examples, and may be configured as other values, and the present disclosure is not limited thereto. In the case of the correspondence between the configuration information and each parameter, it is not necessarily required to configure all the correspondence shown in each table. For example, in the table in the present disclosure, the correspondence shown by some rows may not be configured. For another example, appropriate morphing adjustments, e.g., splitting, merging, etc., may be made based on the tables described above. The names of the parameters indicated in the tables may be other names which are understood by the communication device, and the values or expressions of the parameters may be other values or expressions which are understood by the communication device. When the tables are implemented, other data structures may be used, for example, an array, a queue, a container, a stack, a linear table, a pointer, a linked list, a tree, a graph, a structure, a class, a heap, a hash table, or a hash table.

Predefined in this disclosure may be understood as defining, predefining, storing, pre-negotiating, pre-configuring, curing, or pre-sintering.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the embodiments of the present disclosure may be performed in parallel, sequentially, or in a different order, so long as the desired result of the technical solution of the present disclosure is achieved, and the present disclosure is not limited herein.

The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims

1. A method of configuring a side-uplink SL data radio bearer, DRB, said method being performed by a terminal device, said method comprising:

and determining the channel access priority CAPC of the SL data radio bearer DRB.

2. The method according to claim 1, wherein the method further comprises:

3. The method of claim 2, wherein the first information is included in radio resource control, RRC, signaling or a system information block, SIB.

4. The method of claim 1, wherein in the case where a network device is not configured with a CAPC of the SL DRB, the method further comprises:

5. The method of claim 4, wherein the determining the CAPC of the SL DRB based on the CAPC corresponding to each QoS flow comprises:

6. The method of claim 4, wherein the determining the CAPC of the SL DRB based on the CAPC corresponding to each QoS flow comprises:

7. The method according to any of claims 4-6, wherein said determining a respective CAPC for each QoS flow of at least one QoS flow mapped to the SL DRB comprises:

determining a PC5 interface quality of service identifier PQI of each QoS flow;

8. The method of claim 7, wherein the step of determining the position of the probe is performed,

one standard PQI that matches the non-standard PQI is a standard PQI that differs minimally from the packet delay budget PDB of the non-standard PQI; and/or the number of the groups of groups,

9. A side-uplink SL data radio bearer DRB configuration apparatus, said apparatus comprising:

and the processing unit is used for determining the channel access priority CAPC of the SL data radio bearer DRB.

10. The apparatus of claim 9, wherein the apparatus further comprises:

11. The apparatus of claim 10, wherein the first information is included in radio resource control, RRC, signaling or a system information block, SIB.

12. The apparatus of claim 9, wherein the processing unit is further configured to:

13. The apparatus according to claim 12, wherein the processing unit is specifically configured to:

14. The apparatus according to claim 12, wherein the processing unit is specifically configured to:

15. The apparatus according to any one of claims 12-14, wherein the processing unit is specifically configured to:

determining a PC5 interface quality of service identifier PQI of each QoS flow;

16. The apparatus of claim 15, wherein the device comprises a plurality of sensors,

17. A communication device, characterized in that the device comprises a processor and a memory, the memory having stored therein a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method according to any of claims 1 to 8.

18. A communication device, comprising: a processor and interface circuit;

the interface circuit is used for receiving code instructions and transmitting the code instructions to the processor;

the processor for executing the code instructions to perform the method of any one of claims 1 to 8.

19. A computer readable storage medium storing instructions which, when executed, cause the method of any one of claims 1 to 8 to be implemented.