WO2024093825A1 - 一种通信方法和相关设备 - Google Patents
一种通信方法和相关设备 Download PDFInfo
- Publication number
- WO2024093825A1 WO2024093825A1 PCT/CN2023/127148 CN2023127148W WO2024093825A1 WO 2024093825 A1 WO2024093825 A1 WO 2024093825A1 CN 2023127148 W CN2023127148 W CN 2023127148W WO 2024093825 A1 WO2024093825 A1 WO 2024093825A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- drb
- capc
- configuration
- quality
- service
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 147
- 238000004891 communication Methods 0.000 title claims abstract description 142
- 101100399876 Homo sapiens LRRC26 gene Proteins 0.000 claims abstract description 90
- 102100022842 Structural maintenance of chromosomes protein 4 Human genes 0.000 claims abstract description 90
- 101150106760 smc-4 gene Proteins 0.000 claims abstract description 90
- 238000013507 mapping Methods 0.000 claims description 33
- 238000004590 computer program Methods 0.000 claims description 11
- 230000005540 biological transmission Effects 0.000 abstract description 42
- 230000000875 corresponding effect Effects 0.000 description 120
- 238000001228 spectrum Methods 0.000 description 31
- 230000006870 function Effects 0.000 description 29
- 230000008569 process Effects 0.000 description 29
- 238000012545 processing Methods 0.000 description 17
- 238000010586 diagram Methods 0.000 description 12
- 238000005516 engineering process Methods 0.000 description 7
- 230000011664 signaling Effects 0.000 description 6
- 238000013461 design Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 4
- 238000012935 Averaging Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- XHSQDZXAVJRBMX-UHFFFAOYSA-N 2-(5,6-dichlorobenzimidazol-1-yl)-5-(hydroxymethyl)oxolane-3,4-diol Chemical compound OC1C(O)C(CO)OC1N1C2=CC(Cl)=C(Cl)C=C2N=C1 XHSQDZXAVJRBMX-UHFFFAOYSA-N 0.000 description 2
- 101001121408 Homo sapiens L-amino-acid oxidase Proteins 0.000 description 2
- 102100026388 L-amino-acid oxidase Human genes 0.000 description 2
- 101100012902 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) FIG2 gene Proteins 0.000 description 2
- 101000827703 Homo sapiens Polyphosphoinositide phosphatase Proteins 0.000 description 1
- 102100023591 Polyphosphoinositide phosphatase Human genes 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/25—Control channels or signalling for resource management between terminals via a wireless link, e.g. sidelink
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
- H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
- H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
Definitions
- the present application relates to the field of communication technology, and in particular to a communication method and related equipment.
- data communication can be performed between terminal devices through network devices (such as access network devices), or data communication can be performed directly between terminal devices without the help of network devices.
- network devices such as access network devices
- data communication can be performed directly between terminal devices without the help of network devices.
- the interface for direct data communication between terminal devices is called the PC5 interface
- the link for direct data communication between terminal devices is called the sidelink (SL).
- Typical application scenarios of sidelink communication include vehicle to everything (V2X) and proximity-based services (ProSe). Taking the vehicle to everything (V2X) as an example, each vehicle in the vehicle to everything (V2X) is a terminal device, and vehicles can directly transmit data through the sidelink without the help of network equipment, which can effectively reduce communication delays.
- the spectrum resources that can be used for sidelink communication are generally divided into two categories, one is licensed spectrum and the other is unlicensed spectrum.
- the licensed spectrum can only be used by certain organizations or operators, while the unlicensed spectrum is a shared spectrum that can be used by different operators or organizations.
- the devices working in the unlicensed spectrum need to use the listen-before-talk (LBT) channel competition access mechanism to listen to whether the channel is idle before sending data. Only when the channel is idle can it occupy the channel and transmit data.
- LBT listen-before-talk
- the embodiments of the present application provide a communication method and related equipment, which can ensure the communication quality of SL-U and the fairness of transmission of different business requirements.
- an embodiment of the present application provides a communication method, which is applied to a terminal device and may include: obtaining a first sidelink data radio link bearer SL DRB configuration; determining the CAPC of the SL DRB based on one or more service quality flows associated with the first SL DRB configuration, the SL DRB being a SL DRB established based on the first SL DRB configuration.
- the CAPC configuration corresponding to the SL DRB used by the UE is sent down by the base station or obtained through a pre-configuration message.
- the QoS characteristics of these QoS flows may be very different, that is, the CAPC required by the QoS flows may be different, so that the CAPC configuration of the SL DRB may not be suitable for the CAPC of these QoS flows, or the SL DRB may not have a CAPC configuration, affecting the performance and fairness of the entire SL-U communication.
- the UE can determine the CAPC of the SL DRB established according to the SL DRB configuration according to one or more QoS flows associated with the SL DRB configuration, wherein the number of established SL DRBs can be 1 or more. Based on this, the UE can reasonably configure or reasonably determine the CAPC corresponding to the SL DRB according to one or more QoS flows, thereby reducing the problems that affect the communication quality and fairness of the SL-U when, for example, the network does not configure the CAPC of the SL DRB or the configured CAPC is inappropriate, thereby achieving the purpose of ensuring the communication quality of the SL-U and the fairness of transmission of different business needs.
- the number of SL DRBs is 1.
- the UE can determine the CAPC corresponding to a SL DRB based on multiple QoS flows, which can reduce the problems affecting the communication quality and fairness of the SL-U when, for example, the network is not configured with the CAPC of the SL DRB or the configured CAPC is inappropriate, thereby achieving the purpose of ensuring the communication quality of the SL-U and the fairness of transmission of different business needs.
- the number of the SL DRBs is at least 2, and the CAPC of each of the at least 2 SL DRBs is different.
- the UE establishes multiple SL DRBs according to the SL DRB configuration, so that what is actually transmitted in each SL DRB is the QoS flow corresponding to the CAPC, thereby ensuring the communication quality of SL-U and the fairness of transmission for different business needs.
- the method further includes: determining a target CAPC among one or more CAPCs corresponding to one or more service quality flows associated with the first SL DRB configuration as the CAPC of the SL DRB.
- the UE can determine the target CAPC that meets the actual business needs from the multiple CAPCs corresponding to the multiple QoS flows according to the actual business needs, and determine the target CAPC as the CAPC of the SL DRB, so as to ensure that the SL DRB can meet the actual business transmission. need.
- the method further includes: determining the CAPC corresponding to the service quality flow whose characteristic parameters in one or more service quality flows associated with the SL DRB configuration meet the second preset condition as the CAPC of the SL DRB; the characteristic parameters are used to represent the service quality characteristics of the service quality flow; or determining the maximum CAPC value, the minimum CAPC value or the CAPC average value among the one or more CAPCs corresponding to the one or more service quality flows associated with the SL DRB configuration as the CAPC of the SL DRB; or determining the CAPC with the most corresponding service quality flows among the one or more CAPCs corresponding to the one or more service quality flows associated with the SL DRB configuration as the CAPC of the SL DRB.
- the UE can determine a target CAPC that meets the requirements of the rules from multiple CAPCs corresponding to multiple QoS flows according to certain rules, and determine the target CAPC as the CAPC of the SL DRB to ensure the accuracy of the CAPC corresponding to the SL DRB.
- the target CAPC includes any one or more of the following CAPCs: the CAPC of the quality of service flow with the smallest or largest packet delay budget among the one or more quality of service flows associated with the first SL DRB configuration; the CAPC of the quality of service flow with the smallest or largest default priority among the one or more quality of service flows associated with the first SL DRB configuration; the CAPC of the quality of service flow with the smallest or largest priority among the one or more quality of service flows associated with the first SL DRB configuration; the CAPC of the quality of service flow with the smallest or largest packet error rate among the one or more quality of service flows associated with the first SL DRB configuration; the maximum CAPC value, the minimum CAPC value or the average CAPC value among the one or more CAPCs corresponding to the one or more quality of service flows associated with the first SL DRB configuration; or the CAPC corresponding to the largest number of quality of service flows among the one or more CAPCs corresponding to the one or more quality of service flows associated with the first SL DRB configuration
- the UE can determine a target CAPC that meets the requirements of the rules from multiple CAPCs corresponding to multiple QoS flows according to certain rules, and determine the target CAPC as the CAPC of the SL DRB to ensure the accuracy of the CAPC corresponding to the SL DRB.
- the characteristic parameters include one or more of a packet delay budget, a default priority, a priority, and a packet error rate;
- the second preset condition includes any one of the following conditions: the packet delay budget is the minimum or maximum value of one or more packet delay budgets corresponding to one or more quality of service flows associated with the SL DRB configuration; the default priority is the minimum or maximum value of one or more default priorities corresponding to one or more quality of service flows associated with the SL DRB configuration; the priority is the minimum or maximum value of one or more priorities corresponding to one or more quality of service flows associated with the SL DRB configuration; or the packet error rate is the minimum or maximum value of one or more packet error rates corresponding to one or more quality of service flows associated with the SL DRB configuration.
- the UE can determine a target CAPC that meets the requirements of the rules from multiple CAPCs corresponding to multiple QoS flows according to certain rules, and determine the target CAPC as the CAPC of the SL DRB to ensure the accuracy of the CAPC corresponding to the SL DRB.
- the method further includes: determining the number of the at least two SL DRBs according to the different CAPC numbers corresponding to one or more service quality flows associated with the first SL DRB configuration, and establishing the at least two SL DRBs; the CAPCs of the at least two SL DRBs respectively correspond to the CAPCs of the one or more service quality flows.
- the UE can determine the number of SL DRBs based on the different CAPC numbers corresponding to the QoS flows, and establish SL DRBs according to the number.
- the CAPC of each SL DRB corresponds to the CAPC of the QoS flow, ensuring that each QoS flow can be transmitted fairly while saving link carrying resources.
- the method further includes: determining that the first SL DRB configuration satisfies a first preset condition; the first preset condition includes one or more of the following conditions: the first SL DRB configuration is a default SL DRB configuration; the first SL DRB configuration is obtained through a system information block SIB or a pre-configuration message; the first SL DRB configuration does not provide a corresponding CAPC configuration; or the CAPC configuration provided by the first SL DRB configuration is inappropriate.
- the UE may first determine whether the SL DRB configuration satisfies certain conditions (i.e., the first preset condition), and then determine the CAPC of the SL DRB after determining that the SL DRB configuration satisfies the conditions. This avoids the UE unconditionally executing the determination of the CAPC of the SL DRB, resulting in a waste of resources.
- certain conditions i.e., the first preset condition
- the inappropriate CAPC configuration provided by the first SL DRB configuration includes one or more of the following: the CAPCs corresponding to the multiple service quality flows associated with the first SL DRB configuration are different; the maximum difference between the CAPCs corresponding to the multiple service quality flows associated with the first SL DRB configuration is greater than or equal to a first threshold; the number of the multiple service quality flows associated with the first SL DRB configuration is greater than or equal to a second threshold; or the minimum value of the CAPCs corresponding to the multiple service quality flows associated with the first SL DRB configuration is greater than the CAPC value provided by the first SL DRB configuration.
- the UE can determine whether the CAPC configuration provided by the SL DRB configuration is appropriate based on certain conditions. For example, when the number of QoS flows associated with the SL DRB configuration exceeds a certain number (i.e., the second threshold), it can be directly considered that the CAPC configuration provided by the SL DRB configuration is inappropriate. Then, the UE can determine the CAPC of the SL DRB based on the QoS flow to ensure the communication quality of the SL-U and the fairness of transmission of different business needs.
- a certain number i.e., the second threshold
- the method further includes: when the first SL DRB configuration does not provide a corresponding CAPC configuration or the CAPC configuration provided by the first SL DRB configuration is inappropriate, sending an indication message to the access network device, the indication message being used to indicate that the first SL DRB configuration does not provide a corresponding CAPC configuration or the CAPC configuration provided by the first SL DRB configuration is inappropriate; receiving a second SL DRB configuration sent by the access network device, the second SL DRB configuration being different from the first SL DRB configuration; or when the first SL DRB configuration does not provide a corresponding CAPC configuration or the CAPC configuration provided by the first SL DRB configuration is inappropriate, if the terminal device is in a radio resource control RRC idle state or an RRC inactive state, entering an RRC connected state; receiving a second SL DRB configuration sent by the access network device, the second SL DRB configuration being different from the first SL DRB configuration.
- the UE when the UE determines that the SL DRB configuration does not provide the corresponding CAPC configuration or the CAPC configuration provided by the SL DRB configuration is inappropriate, the UE can send an indication message to the access network device or trigger the process of accessing the RRC connection state, and then receive a new SL DRB configuration (i.e., the second SL DRB configuration) sent by the access network device, so that the UE can use the CAPC-appropriate SL DRB to transmit the QoS flow, thereby ensuring the communication quality of SL-U and the fairness of transmission of different business requirements.
- a new SL DRB configuration i.e., the second SL DRB configuration
- the one or more quality of service flows associated with the first SL DRB configuration include a quality of service flow corresponding to a non-standard PC5 quality of service identifier
- the method further includes: determining the CAPC of the quality of service flow corresponding to the non-standard PC5 quality of service identifier based on characteristic parameters of the quality of service flow corresponding to the non-standard PC5 quality of service identifier; the characteristic parameters are used to represent the quality of service characteristics of the quality of service flow corresponding to the non-standard PC5 quality of service identifier, and the characteristic parameters include one or more of packet delay budget, default priority, priority and packet error rate.
- the UE can determine the CAPC of the non-standard service quality flow based on the characteristic parameters of the non-standard QoS flow, and then determine whether to determine the CAPC of the non-standard service quality flow as the CAPC of the SL DRB based on certain rules, thereby ensuring the fairness of the transmission of non-standard QoS flows.
- the method further includes: obtaining multiple default SL DRB configurations; each default SL DRB configuration in the multiple default SL DRB configurations is associated with a different CAPC configuration; and establishing multiple default SL DRBs based on the multiple default SL DRB configurations.
- the UE can determine the CAPC of the SL DRB by itself to ensure the communication quality of the SL-U and the transmission fairness of different business requirements, it can also obtain multiple default SL DRB configurations with different CAPC configurations, and establish default SL DRBs according to these default SL DRB configurations, that is, the CAPCs of the default SL DRBs are different, which provides a guarantee for the QoS flow subsequently mapped to the default SL DRB to have a default SL DRB with appropriate CAPC for transmission, which can further ensure the communication quality of the SL-U and the transmission fairness of different business requirements.
- the method further includes: when the mapping rule of the corresponding SL DRB is not configured or stored for the service quality flow to be transmitted, mapping the service quality flow to be transmitted to a target default SL DRB among the multiple default SL DRBs, and the CAPC of the target default SL DRB is the same as the CAPC of the service quality flow to be transmitted.
- the UE when a QoS flow needs to be mapped to a default SL DRB, that is, when the QoS flow is not configured or the mapping rule of the corresponding SL DRB is not stored, the UE can map the QoS flow to the default SL DRB (that is, the target default SL DRB) with the same CAPC according to the CAPC of the QoS flow for transmission, thereby ensuring the communication quality of the SL-U and the fairness of transmission of different business needs.
- the method further includes: when a mapping rule of a corresponding SL DRB is not configured or stored for the quality of service flow to be transmitted, mapping the quality of service flow to be transmitted to a default SL DRB among the multiple default SL DRBs whose CAPC is the same as the CAPC of the quality of service flow to be transmitted.
- the UE when a QoS flow needs to be mapped to a default SL DRB, that is, when the QoS flow is not configured or the mapping rule of the corresponding SL DRB is not stored, the UE can map the QoS flow to the default SL DRB with the same CAPC according to the CAPC of the QoS flow for transmission, thereby ensuring the communication quality of the SL-U and the fairness of transmission of different business requirements.
- an embodiment of the present application provides a communication method, which is applied to an access network device and may include: receiving an indication message sent by a terminal device, and/or sending a second SL DRB configuration to the terminal device.
- the method further includes: sending multiple default SL DRB configurations; and each of the multiple default SL DRB configurations is associated with a different CAPC configuration.
- an embodiment of the present application provides a communication method, which is applied to a terminal device and may include: obtaining multiple default SL DRB configurations; each default SL DRB configuration in the multiple default SL DRB configurations is associated with a different CAPC configuration; and establishing multiple default SL DRBs based on the multiple default SL DRB configurations.
- the UE can obtain multiple default SL DRB configurations with different CAPC configurations, and configure the default SL DRBs according to these default SL DRBs.
- the configuration establishes the default SL DRBs separately, that is, the CAPCs of the default SL DRBs are different, so as to ensure that the QoS flows subsequently mapped to the default SL DRBs can be transmitted by the default SL DRBs with appropriate CAPCs.
- the method further includes: when the mapping rule of the corresponding SL DRB is not configured or stored for the service quality flow to be transmitted, mapping the service quality flow to be transmitted to a target default SL DRB among the multiple default SL DRBs, and the CAPC of the target default SL DRB is the same as the CAPC of the service quality flow to be transmitted.
- the method further includes: when a mapping rule of a corresponding SL DRB is not configured or stored for the quality of service flow to be transmitted, mapping the quality of service flow to be transmitted to a default SL DRB among the multiple default SL DRBs whose CAPC is the same as the CAPC of the quality of service flow to be transmitted.
- an embodiment of the present application provides a communication method, which is applied to an access network device and may include: sending multiple default SL DRB configurations; each default SL DRB configuration in the multiple default SL DRB configurations is associated with a different CAPC configuration.
- an embodiment of the present application provides a communication device, which includes a processor, and the processor is configured to support the communication device to implement the corresponding functions of the communication method provided in any one of the first aspect, the second aspect, the third aspect, or the fourth aspect.
- the communication device may also include a memory, which is coupled to the processor and stores the necessary program instructions and data for the communication device.
- the communication device may also include an interface circuit for the communication device to communicate with other devices or a communication network.
- an embodiment of the present application provides a computer-readable storage medium for storing computer software instructions used by a communication device for implementing a communication method provided by one or more of the fifth aspects above, which includes a program designed for executing the above aspects.
- an embodiment of the present application provides a computer program, which includes instructions.
- the computer program When the computer program is executed by a computer, it enables the computer to execute a process performed by a communication device for implementing a communication method provided by one or more of the above-mentioned fifth aspects.
- an embodiment of the present application provides a chip system, which includes a processor for supporting a device to implement the functions involved in any of the first, second, third or fourth aspects, for example, generating or processing the information involved in the above communication method.
- the chip system also includes a memory, which is used to store program instructions and data necessary for the device.
- the chip system can be composed of chips, or it can include chips and other discrete devices.
- FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application.
- Figure 2 is a schematic diagram of the Sidelink UE-to-Network Relay scenario provided in an embodiment of the present application.
- Figure 3 is a schematic diagram of the Sidelink UE-to-UE Relay scenario provided in an embodiment of the present application.
- FIG4 is a schematic diagram of a process of performing uplink transmission based on unlicensed spectrum provided in an embodiment of the present application.
- FIG5 is a flow chart of a communication method provided in an embodiment of the present application.
- FIG6 is a flow chart of another communication method provided in an embodiment of the present application.
- FIG. 7 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
- FIG8 is another schematic diagram of the structure of a communication device provided in an embodiment of the present application.
- the following one or more items or similar expressions refer to any combination of these items, including any combination of single or plural items.
- the following one or more items: a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a, b and c.
- a, b, c can be single or multiple.
- At least one means one or more
- “multiple” means two or more.
- “And/or” describes the association relationship of associated objects, indicating that three relationships can exist.
- a and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone, among which A and B can be singular or plural.
- the character “/” generally indicates that the objects before and after are in an “or” relationship.
- the words “exemplary” or “for example” are used to indicate examples, illustrations or descriptions. Any embodiment or design described in this application as “exemplary”, “for example” or “for example” should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of the words “exemplary”, “for example” or “for example” is intended to present the related concepts in a concrete way.
- system and “network” are used interchangeably herein.
- B corresponding to A means that B is associated with A, and B can be determined according to A.
- determining B according to A does not mean determining B only according to A, and B can also be determined according to A and/or other information.
- a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program and/or a computer.
- applications and computing devices running on a computing device can be components.
- One or more components may reside in a process and/or an execution thread, and a component may be located on a computer and/or distributed between two or more computers.
- these components may be executed from various computer-readable media having various data structures stored thereon.
- Components may, for example, communicate through local and/or remote processes according to signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system and/or a network, such as the Internet interacting with other systems through signals).
- signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system and/or a network, such as the Internet interacting with other systems through signals).
- the technical solution of the embodiment of the present application can be applied to the sidelink communication system, and can also be applied to other communication systems operating in unlicensed spectrum (unlicensed band), such as long term evolution (LTE) system, new radio access technology (NR) communication system, next generation wireless local area network (WLAN) system, etc., and of course it can also be a communication system operating in unlicensed spectrum in the future, such as the sixth generation (6G) or even the seventh generation (7G) system, etc.
- LTE long term evolution
- NR new radio access technology
- WLAN next generation wireless local area network
- 6G sixth generation
- 7G seventh generation
- FIG. 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application.
- the communication system includes a wireless access network 100.
- the wireless access network 100 may include at least one wireless access network device (such as 110a and 110b in FIG. 1 ), and may also include at least one terminal device (such as 120a-120j in FIG. 1 ).
- the terminal device may be connected to the wireless access network device in a wireless manner, and the terminal devices and the wireless access network devices may be connected to each other in a wired or wireless manner.
- FIG. 1 is only a schematic diagram, and the communication system may also include other network devices, such as core network devices, wireless relay devices, and wireless backhaul devices, which are not shown in FIG. 1 .
- Radio access network equipment can be referred to as network equipment for short. It is the access equipment that the terminal uses to access the communication system wirelessly.
- Radio access network equipment can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in the fifth generation (5G) mobile communication system, The next generation base station in the sixth generation (6th generation, 6G) mobile communication system, the base station in the future mobile communication system or the access node in the WiFi system, etc.; it can also be a module or unit that completes part of the functions of the base station, for example, it can be a centralized unit (CU) or a distributed unit (DU).
- CU centralized unit
- DU distributed unit
- the CU here completes the functions of the radio resource control protocol and the packet data convergence layer protocol (PDCP) of the base station, and can also complete the function of the service data adaptation protocol (SDAP); the DU completes the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and can also complete the functions of part of the physical layer or all of the physical layer.
- PDCP packet data convergence layer protocol
- SDAP service data adaptation protocol
- the DU completes the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and can also complete the functions of part of the physical layer or all of the physical layer.
- 3GPP third generation partnership project
- the wireless access network device can be a macro base station (such as 110a in Figure 1), a micro base station or an indoor station (such as 110b in Figure 1), or a relay node or a donor node, etc.
- the embodiments of the present application do not limit the specific technology and specific device form adopted by the wireless access network device.
- the terminal device is a device with wireless transceiver function, which can send signals to the base station or receive signals from the base station.
- the terminal device can also be called a terminal, user equipment (UE), mobile station, mobile terminal, etc.
- the terminal device can be widely used in various scenarios, for example, device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc.
- D2D device-to-device
- V2X vehicle to everything
- MTC machine-type communication
- IOT Internet of Things
- virtual reality augmented reality
- industrial control automatic driving
- telemedicine smart grid
- smart furniture smart office
- smart wear smart transportation
- smart city etc.
- the terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, an airplane, a ship, a robot, a mechanical arm, a smart home device, etc.
- the embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal.
- Base stations and terminals can be fixed or movable. Base stations and terminals can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on airplanes, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of base stations and terminals.
- the helicopter or drone 120i in FIG. 1 can be configured as a mobile base station.
- the terminal 120j that accesses the wireless access network 100 through 120i
- the terminal 120i is a base station; but for the base station 110a, 120i is a terminal, that is, 110a and 120i communicate through the wireless air interface protocol.
- 110a and 120i can also communicate through the interface protocol between base stations.
- relative to 110a, 120i is also a base station. Therefore, base stations and terminals can be collectively referred to as communication devices.
- 110a and 110b in FIG. 1 can be referred to as communication devices with base station functions
- 120a-120j in FIG. 1 can be referred to as communication devices with terminal functions.
- Base stations and terminals, base stations and base stations, and terminals and terminals can communicate through authorized spectrum, through unlicensed spectrum, or through both authorized spectrum and unlicensed spectrum. They can communicate through spectrum below 6 gigahertz (GHz), through spectrum above 6 GHz, or through both spectrum below 6 GHz and spectrum above 6 GHz at the same time.
- GHz gigahertz
- This application mainly focuses on the situation where terminals communicate with each other through unlicensed spectrum.
- the interface between terminals is the PC5 interface
- the interface between the terminal and the base station is the Uu interface.
- the terminal can use the unlicensed spectrum to communicate with another terminal for sidelink, and the communication between the terminal and the terminal can be unicast communication, multicast communication, or broadcast communication.
- the terminal can be configured with one or more antennas for sending and receiving messages/information/data, etc.
- the terminal may also include multiple components related to the sending and receiving of messages/information/data (for example, a processor, a modulator, a multiplexer, a demodulator or a demultiplexer, etc.).
- the device for realizing the function of the terminal may be a terminal; or it may be a device capable of supporting the terminal to realize the function, such as a chip system, or a communication module, or a modem, etc., which may be installed in the terminal.
- the chip system may be composed of chips, or may include chips and other discrete devices.
- the device for realizing the function of the terminal is a terminal, and the terminal is a UE as an example to describe the technical solution provided in the embodiment of the present application.
- the embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.
- a UE can also be used to act as a base station.
- a UE can act as a scheduling entity that provides sidelink signals between UEs in vehicle-to-everything (V2X), device-to-device (D2D), or peer-to-peer (P2P) networks.
- V2X vehicle-to-everything
- D2D device-to-device
- P2P peer-to-peer
- UE can also be used as a relay node.
- UE can act as a relay device or an integrated access and backhaul (IAB) node to provide wireless backhaul services for terminal devices.
- IAB integrated access and backhaul
- V2X vehicle-to-everything
- the method provided in the present application can be applied not only to V2X scenarios (such as the scenario of communication between 120a and 120b in FIG1 ), but also to sidelink UE-to-network relay scenarios and sidelink UE-to-UE relay scenarios. See FIG2 , which is a schematic diagram of a Sidelink UE-to-Network Relay scenario provided in an embodiment of the present application.
- the Sidelink UE-to-Network Relay scenario includes Remote UE (remote UE) and Relay UE (relay UE), and also includes a base station; the method provided in the present application can be applied to the communication between the Remote UE and the Relay UE.
- Figure 3 is a schematic diagram of the Sidelink UE-to-UE Relay scenario provided by an embodiment of the present application.
- the Sidelink UE-to-UE Relay scenario includes a Source UE (source UE), a Relay UE (relay UE) and a target UE (target UE); the method provided in the present application can be applied to the communication between the Source UE and the Relay UE and/or the communication between the Relay UE and the target UE.
- wireless communication may also be referred to as “communication”
- communication may also be described as “data transmission”, “information transmission” or “transmission”.
- UE there are two ways for UE to obtain sidelink resources, one is base station scheduling mode (also called mode1), and the other is autonomous competition mode (also called mode2).
- base station scheduling mode also called mode1
- autonomous competition mode also called mode2
- UE obtains SL resources from the base station.
- the base station can schedule SL resources for UE through downlink control information (DCI), or configure SL configuration authorization (configured grant) for UE through radio resource control (RRC) message.
- DCI downlink control information
- RRC radio resource control
- UE can receive SL resource pool configuration from the base station, or obtain SL resource pool configuration from pre-configuration, and then select SL resources in the SL resource pool for transmission.
- the selection of SL resources can be random selection, or it can be based on the results of sensing or partial sensing.
- LBT channel access process
- a device Before a device sends a signal (for example, a data signal) on a channel, it can first detect whether the channel is idle, for example, whether it detects that a nearby device is occupying the channel to send a signal. This detection process can be called a clear channel assessment (CCA) or a channel access process.
- CCA clear channel assessment
- the first type (type1) channel access process (also referred to as a channel access process based on a fixed duration) may be: based on energy detection of a fixed duration, for a certain bandwidth, such as 20MHz, if the signal energy received by a device (the device may be a terminal device or a network device) within a fixed duration is less than or equal to a first preset threshold, the channel is considered to be idle (idle); thus, the device may use the idle channel to transmit data; if the signal energy received within a fixed duration is greater than the first preset threshold, the channel is considered to be busy (busy), so that the device does not use the busy channel to transmit data.
- the second type (type2) of channel access process can be: based on the energy detection of the backoff mechanism, a window is defined for a certain bandwidth, and the window defines the range of the number of time slots to be detected.
- the device randomly selects a value A from the window (or value range). After the device detects at least A idle time slots, it considers that the channel is idle, so that the device can use the idle channel to transmit data; if there are no empty time slots or the number of empty time slots is less than A, the channel is considered busy, so that the device does not use the busy channel to transmit data.
- an idle time slot refers to a signal energy received in a time slot that is less than or equal to a second preset threshold.
- the first preset threshold and the second preset threshold can be predefined, such as predefined by a protocol.
- the values of the first preset threshold and the second preset threshold can be the same or different.
- type 1 when the device performs type 1 (fixed-duration energy detection) LBT (that is, the first type of channel access process), it needs to determine the contention window size (CW size) and channel occupancy time (COT) according to the channel access priority class (CAPC).
- the relationship between CAPC and COT is shown in Table 1 below.
- the first column in Table 1 represents the CAPC value.
- the fifth column in Table 1 represents the COT size corresponding to different CAPC values (in milliseconds). It can be understood that the meaning of other columns in Table 1 can refer to existing standards, such as the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 37.213V17.2.0, or refer to other versions of technical specifications, which are not described in detail here.
- 3GPP 3rd Generation Partnership Project
- TS Technical Specification
- the channel access process is completed (also called LBT success) and the channel access process is not completed (also called LBT failure). If the channel is determined to be idle before the start position of a particular time domain, the channel access process can be considered completed; if the channel is determined to be busy before the start positions of all time domains, the channel access process can be considered incomplete.
- the Uu communication here refers to the communication between the UE and the base station through the air interface.
- the UE can directly use the uplink resources for uplink transmission.
- Figure 4 is a flow chart of uplink transmission based on unlicensed spectrum provided in an embodiment of the present application. After the base station schedules the uplink resources for the UE, the UE may still need to perform LBT on the uplink resources. Only after the LBT is successful can the uplink resources be used for uplink transmission. In other words, if LBT is performed on the scheduled uplink resources and LBT fails, the scheduled uplink resources cannot be used.
- the base station can configure the corresponding CAPC for each data radio bearer (DRB).
- the CAPC configuration can be included in the logical channel (LCH) configuration associated with the DRB.
- LCH logical channel
- the base station needs to consider the 5G QoS Identifier (5QI) corresponding to all Quality of Service (QoS) flows mapped to this DRB.
- the base station also needs to consider the fairness between different service types and transmissions.
- the standard defines a mapping table between standard 5QI and CAPC (that is, it defines the CAPC used by the QoS flow corresponding to the standard 5QI), as shown in Table 2.
- a lower CAPC value means a higher priority.
- the value in the second column represents the index value corresponding to the standard 5QI.
- the 5QI corresponding to a CAPC of 4 has not yet been clearly defined.
- the CAPC corresponding to the standard 5QI with the most matching QoS characteristics (QoS characteristics) must be used as its own CAPC.
- QoS characteristics may include one or more of resource type, default priority level, priority level, packet delay budget (PDB), packet error rate (PER), default maximum data burst volume (DMDV), and default averaging window (Default Averaging Window).
- PDB packet delay budget
- PER packet error rate
- DMDV default maximum data burst volume
- Default Averaging Window default averaging window
- QoS flow can also support two modes: standard PC5 QoS Identifier (standardized PQI) and non-standardized PQI.
- standard PC5 QoS Identifier standardized PQI
- non-standardized PQI There is also a mapping table between standard PQI and CAPC. Please refer to the mapping relationship between 5QI and CAPC in Table 2 above, which will not be expanded here.
- each PQI corresponds to a set of QoS characteristics, including resource type, default priority level, packet delay budget (PDB), packet error rate (PER), default maximum data burst volume (DMDV), and default averaging window.
- PDB packet delay budget
- PER packet error rate
- DMDV default maximum data burst volume
- the standard PQI may be used together with the priority indicated by the upper layer, which can be used to override the default priority corresponding to the standard PQI.
- the V2X layer can provide the access layer (Access Stratum, AS) with a complete set of specific non-standard QoS characteristics.
- Tables 3 and 4 are the mapping relationship tables of standard PQI and QoS characteristics defined for V2X and ProSe respectively.
- the technical problems to be solved by this application are analyzed and proposed.
- the UE can obtain it through RRC dedicated signaling, System Information Block (SIB) message or pre-configuration message. Specifically, it can be divided into the following different situations:
- the UE is in the RRC connected state.
- the UE reports QoS parameters through the SUI message (Sidelink UE information).
- the base station configures the mapping relationship between the QoS flow and the SL DRB and the SL DRB configuration through RRC dedicated signaling.
- the base station configures the mapping relationship between the QoS flow and the SL DRB and the SL DRB configuration through the SIB message.
- the SL DRB configuration can also support the default SL DRB configuration.
- the mapping relationship between the displayed QoS flow and the SL DRB can be represented by indicating the mapping relationship between the QoS flow identifier and the SL DRB, or by indicating the mapping relationship between the QoS parameters corresponding to the QoS flow (such as QoS file, QoS configuration file (profile)) and the SL DRB.
- the mapping relationship between QoS flow and SL DRB can be that multiple QoS flows are mapped to one SL DRB, that is, One SL DRB can carry data transmission of multiple QoS flows.
- the QoS characteristics of these QoS flows may be very different (for example, the PDB (packet delay budget) between different QoS flows is very different), especially for the case where the UE is in RRC idle state/RRC inactive state/OOC state, considering that the QoS flow may also correspond to the situation of non-standardized PQI and signaling overhead, the network cannot explicitly map all QoS flows with non-standardized PQI to non-default SL DRB for transmission, that is, many non-standardized PQI QoS flows will eventually be mapped to the default SL DRB for transmission, and the QoS characteristics between these non-standardized PQI QoS flows may be very different, which means that the CAPC corresponding to these QoS flows themselves may also be very different.
- the PDB packet delay budget
- the SL DRB that transmits these QoS flows its CAPC may not be configured or may be configured but inappropriate, which will affect the performance and fairness of the entire SL-U communication.
- the CAPC of the SL DRB is not configured, these QoS flows may not be transmitted, or the transmission may be based on an inappropriate CAPC.
- the terminal device can determine the CAPC of the SL DRB established according to the SL DRB configuration based on one or more QoS flows associated with the SL DRB configuration, wherein the number of established SL DRBs can be 1 or more.
- the terminal device can establish multiple default SL DRBs after obtaining multiple different default SL DRB configurations, wherein the CAPC configuration associated with each default SL DRB configuration in the multiple different default SL DRB configurations is different.
- the CAPC of each default SL DRB in the multiple default SL DRBs established by the terminal device according to the configuration is different, thereby ensuring that the CAPC corresponding to the QoS flow transmitted on the same default SL DRB is the same, thereby ensuring the communication quality of SL-U and the fairness of transmission of different business needs.
- Figure 5 is a flow chart of a communication method provided in an embodiment of the present application.
- the method can be applied to a terminal device, and the terminal device can be any terminal in Figure 1 or a module applied to the terminal; or, the terminal device can be any UE in Figure 2, such as Relay UE or Remote UE; or, the terminal device can be any UE in Figure 3, such as Source UE, Relay UE or Target UE. That is to say, the terminal devices in Figures 1, 2 and 3 can be used to support and execute the method flow steps S500-S501 shown in Figure 5, wherein steps S500-S501 include the following:
- Step S500 UE obtains the first sidelink data radio link bearer SL DRB configuration.
- the UE may obtain the first SL DRB configuration through a SIB message, or obtain the first SL DRB configuration based on a pre-configuration message, or obtain the first SL DRB configuration through RRC dedicated signaling, wherein the first SL DRB configuration may include a CAPC configuration or may not include a CAPC configuration, which is not specifically limited here.
- Step S501 The UE determines the CAPC of the SL DRB based on one or more service quality flows associated with the first SL DRB configuration.
- the UE can determine the CAPC of the SL DRB based on one or more QoS flows associated with the first SL DRB, that is, the UE can determine the CAPC of the SL DRB based on the QoS flows mapped to the SL DRB, where the SL DRB is established based on the configuration of the first SL DRB.
- the number of SL DRBs is 1, that is, the UE can determine the CAPC of the SL DRB according to the one or more QoS flows associated with it. Specifically, the UE can first determine that the one or more QoS flows associated with the first SL DRB configuration correspond to One or more CAPCs, and determine the target CAPC among the one or more CAPCs as the CAPC of the SL DRB. It should be noted that after the CAPC of the SL DRB is determined, the one or more QoS flows can also use the SL DRB for transmission.
- the UE determines the CAPC corresponding to the SL DRB according to multiple QoS flows, thereby reducing the problems that affect the communication quality and fairness of the SL-U, for example, when the network does not configure the CAPC of the SL DRB or the configured CAPC is inappropriate, thereby achieving the purpose of ensuring the communication quality of the SL-U and the fairness of transmission of different business needs.
- the target CAPC may include one or more of the following CAPCs:
- the CAPC of the QoS flow with the smallest or largest packet delay budget among one or more QoS flows associated with the first SL DRB configuration For example, if the number of associated QoS flows is 3 (including f1, f2, and f3), f1 has the smallest packet delay budget, and f3 has the largest packet delay budget, then the CAPC corresponding to f1 or f3 can be determined as the CAPC of the SL DRB.
- the CAPC with the largest number of service quality flows among the one or more CAPCs corresponding to the one or more service quality flows associated with the first SL DRB configuration. For example, if the CAPC of f1 is 1, the CAPC of f2 is 1, and the CAPC of f3 is 3, then the CAPC (1) corresponding to f1 and f2 can be determined as the CAPC of the SL DRB.
- the CAPC corresponding to each QoS flow can be determined according to the following methods, including:
- the CAPC corresponding to the QoS flow is the CAPC corresponding to the standardized PQI (that is, it can be determined based on the mapping table between standardized PQI and CAPC).
- the CAPC corresponding to the QoS flow can be determined by the following methods, including:
- the CAPC of the QoS flow can be determined to be 1 or 2. For example, if the priority level of the non-standardized PQI is 1 or 2 (that is, the preset range is 1 or 2), the CAPC of the QoS flow can be determined to be 1 or 2. Or
- the standardized PQI with the closest PDB means that the difference between the PDB of the standardized PQI and the PDB of the QoS flow is the smallest. Understandably, the CAPC of the standardized PQI that is closest to the default priority, priority, or packet error rate of the QoS flow can also be used as the CAPC of the QoS flow.
- the UE may first try to determine the CAPC of the QoS flow through method 1).
- the UE may determine the CAPC of the QoS flow through method 2).
- the target CAPC can be determined by the UE according to a combination of the above-mentioned methods.
- the target CAPC can also be determined by the UE according to other service characteristics of one or more service quality flows associated with the first SL DRB configuration (such as resource type, default maximum data burst size and default average window, etc.) or according to other rules (such as self-configuration and determination based on network conditions). It is understandable that the number of QoS flows in the above example can also be other values besides 3, which is not specifically limited here.
- the number of SL DRBs is multiple (i.e., at least 2), wherein the CAPC corresponding to each of the at least 2 SL DRBs is different.
- the UE may determine the number of the at least 2 SL DRBs according to the number of CAPCs corresponding to one or more QoS flows associated with the first SL DRB configuration, and establish the at least 2 SL DRBs.
- the number of the at least 2 SL DRBs may be greater than or equal to the number of CAPCs corresponding to one or more QoS flows associated with the first SL DRB configuration, and the CAPCs of some or all of the at least 2 SL DRBs correspond to the CAPCs of one or more quality of service flows, respectively.
- the number of CAPCs corresponding to one or more QoS flows is 2 (the number of QoS flows is not necessarily 2), one of the CAPC values is 1, and the other CAPC value is 2, then the number of the at least 2 SL DRBs may be 2, one of the SL DRBs has a CAPC value of 1, and the other has a CAPC value of 2; understandably, the at least 2 SL DRBs The number may also be 3 or 4 (or even more), as long as these SL DRBs include 1 SL DRB with a CAPC value of 1 and 1 SL DRB with a CAPC value of 2.
- the CAPC values of other SL DRBs may be 1 or 2, or other values, which are not specifically limited here.
- the CAPCs corresponding to the at least two SL DRBs are different, and the remaining parameters except CAPC may be the same (wherein the logical channel identifier LCID may also be different).
- the above-mentioned multiple QoS flows may be QoS flows under the same destination.
- the UE establishes multiple SL DRBs with the same CAPC value based on the same SL DRB configuration, it can also distinguish multiple SL DRBs with the same CAPC value by different logical channel identifiers (LCIDs), which will not be further explained here.
- the UE establishes multiple SL DRBs according to the SL DRB configuration, so that the QoS flow actually transmitted in each SL DRB is the QoS flow corresponding to the CAPC, thereby ensuring the communication quality of SL-U and the fairness of transmission of different business needs.
- the process of the communication method provided in the embodiment of the present application may further include step S502 in addition to the above-mentioned steps S500-S501.
- Step S502 Determine whether the first SL DRB configuration satisfies the first preset condition. Specifically, before determining the CAPC of the SL DRB, the UE may first determine whether the first SL DRB configuration satisfies the first preset condition. After determining that the first SL DRB configuration satisfies the first preset condition, the UE may determine the CAPC of the SL DRB based on one or more QoS flows associated with the first SL DRB.
- the first preset condition may include one or more of the following conditions:
- the first SL DRB configuration is the default SL DRB configuration
- the first SL DRB configuration is obtained through a system information block SIB or a pre-configuration message;
- the CAPC configuration provided by the first SL DRB configuration is not appropriate. (Understandably, (3) and (4) will not occur at the same time, and the first SL DRB configuration will not satisfy the conditions of (3) and (4) at the same time.)
- the CAPC configuration provided by the first SL DRB configuration is inappropriate when: 1) the CAPCs corresponding to the multiple service quality flows associated with the first SL DRB configuration are different; 2) the maximum difference between the CAPCs corresponding to the multiple service quality flows associated with the first SL DRB configuration is greater than or equal to the first threshold; for example, if the first threshold is 2, and the CAPCs corresponding to the multiple QoS flows associated with the first SL DRB configuration include a CAPC value of 1 and a CAPC value of 3, then it can be considered that this condition is met, that is, the CAPC configuration provided by the first SL DRB configuration is inappropriate, and then the UE can determine that the first SL DRB configuration meets the first preset condition.
- the number of multiple service quality flows associated with the first SL DRB configuration is greater than or equal to the second threshold. That is, when the number of multiple service quality flows associated with the first SL DRB configuration exceeds a certain number (for example, 5, that is, the second threshold is 5), the UE can also directly determine that the first SL DRB configuration meets the first preset condition.
- the minimum value of the CAPCs corresponding to the multiple service quality flows associated with the first SL DRB configuration is greater than the CAPC value provided by the first SL DRB configuration (or, the highest priority of the CAPCs corresponding to the multiple service quality flows associated with the first SL DRB configuration is lower than or equal to the priority of the CAPC provided by the first SL DRB configuration).
- first threshold and second threshold may also take other values, wherein the first threshold or the second threshold may be predefined by the protocol, configured by the network (for example, the base station is configured through RRC dedicated signaling or SIB message configuration), preconfigured, or configured by other UEs, and is not specifically limited here.
- the UE when the first SL DRB configuration does not provide a corresponding CAPC configuration or the CAPC configuration provided by the first SL DRB configuration is inappropriate, the UE sends an indication message to the access network device (base station), the indication message being used to indicate that the first SL DRB configuration does not provide a corresponding CAPC configuration or the CAPC configuration provided by the first SL DRB configuration is inappropriate; and receives a second SL DRB configuration sent by the access network device, the second SL DRB configuration being different from the first SL DRB configuration.
- the access network device base station
- the terminal device when the first SL DRB configuration does not provide a corresponding CAPC configuration or the CAPC configuration provided by the first SL DRB configuration is inappropriate, if the terminal device is in a radio resource control RRC idle state or an RRC inactive state, it enters an RRC connected state (for example, triggering the execution of an RRC establishment (RRC step) process or an RRC resumption (RRC resume) process); and receives a second SL DRB configuration sent by the access network device, the second SL DRB configuration being different from the first SL DRB configuration.
- the indication message sent by the UE may be sent through a SUI message when the UE enters the RRC connected state or is in mode 1.
- the indication message may also include the CAPC determined by the UE for the SL DRB.
- the second SL DRB configuration is different from the first SL DRB configuration, and may include a case where only the CAPC configuration is different but other configurations are the same, and a case where the CAPC configuration is different and other configurations are also different, which is not specifically limited here.
- the multiple QoS flows associated with the first SL DRB configuration can be understood as all QoS flows mapped to the SL DRB, or can be understood as multiple QoS flows that actually need to be transmitted among all QoS flows mapped to the SL DRB, where the SL DRB is the SL DRB established according to the first SL DRB configuration; or, it can be understood as a QoS flow with data (i.e., transmission requirements) among the multiple QoS flows currently associated with the first SL DRB configuration.
- the multiple QoS flows can be multiple QoS flows under the same destination.
- the number of multiple QoS flows associated with the first SL DRB configuration may be greater than the number of QoS flows actually transmitted on the SL DRB.
- the first SL DRB configuration is associated with QoS flow1, QoS flow2, and QoS flow3, but only QoS flow1 and QoS flow2 need to be transmitted on the SL DRB.
- the multiple QoS flows may refer to QoS flow1 and QoS flow2, but not including QoS flow3, which is not specifically limited here.
- the process of the communication method provided in the embodiment of the present application may further include step S503 and step S504 in addition to the above-mentioned steps S500-S501.
- Step S503 Obtain multiple default SL DRB configurations.
- Step S504 Establish multiple default SL DRBs according to the multiple default SL DRB configurations. Among them, the CAPC configuration associated with each default SL DRB configuration in the multiple default SL DRB configurations is different. That is, the above-mentioned steps S500-S501 can be combined with another communication method provided in the embodiment of the present application.
- the other communication method please refer to the relevant description of Figure 6 below, which will not be expanded here.
- Figure 6 is a flow chart of another communication method provided in an embodiment of the present application.
- the method can be applied to a terminal device, which has the same meaning as the terminal device applied in Figure 5.
- the method flow shown in Figure 6 includes steps S600 to S601, wherein steps S600 to S601 include the following:
- Step S600 UE obtains multiple default SL DRB configurations.
- the CAPC configuration associated with each default SL DRB configuration in the multiple default SL DRB configurations is different.
- the multiple default SL DRB configurations include a first default SL DRB configuration, a second default SL DRB configuration, and a third default SL DRB configuration, wherein the CAPC associated with the first default SL DRB configuration is 1, the CAPC associated with the second default SL DRB configuration is 2, and the CAPC associated with the third default SL DRB configuration is 3.
- the multiple default SL DRB configurations include a first default SL DRB configuration, a second default SL DRB configuration, a third default SL DRB configuration, and a fourth default SL DRB configuration, wherein the CAPC associated with the first default SL DRB configuration is 1, the CAPC associated with the second default SL DRB configuration is 2, the CAPC associated with the third default SL DRB configuration is 3, and the CAPC associated with the fourth default SL DRB configuration is 4.
- the multiple default SL DRB configurations can be obtained by the UE through SIB messages, pre-configuration messages or RRC dedicated signaling, and are not specifically limited here.
- the multiple default SL DRB configurations may also include more or fewer default SL DRB configurations of different CAPC configurations, which is not specifically limited here.
- the multiple default SL DRB configurations may be for the same communication type, wherein the communication type may include one or more of unicast, multicast, and broadcast.
- Step S601 UE establishes multiple default SL DRBs according to the multiple default SL DRB configurations.
- the UE may establish one or more default SL DRBs according to each default SL DRB configuration in the multiple default SL DRB configurations.
- the UE may establish three corresponding default SL DRBs, and the CAPC values of the three default SL DRBs are 1, 2, and 3, respectively, corresponding to the CAPC configurations of the multiple default SL DRB configurations.
- this communication method may further include step S602.
- Step S602 when the quality of service flow to be transmitted is not configured or does not store the mapping rule of the corresponding SL DRB, the quality of service flow to be transmitted is mapped to the target default SL DRB among the multiple default SL DRBs.
- the CAPC of the target default SL DRB is the same as the CAPC of the quality of service flow to be transmitted.
- the CAPC corresponding to the default SL DRB is 1, if the QoS flow is not configured (or stored) with the mapping rule of the corresponding SL DRB and the CAPC corresponding to the QoS flow is 1, the QoS flow can be mapped to the default SL DRB. It is understandable that for default SL DRBs of other CAPCs, the way in which the QoS flow is mapped to the default SL DRB is similar. Based on this, this method can ensure that the CAPCs corresponding to multiple QoS flows transmitted on the same default SL DRB are the same, thereby ensuring the communication quality of SL-U and the fairness of transmission of different business requirements.
- mapping rule of SL DRB can refer to the mapping rule of the explicitly configured QoS flow to SL DRB. It should also be noted that the UE can also establish multiple default SL DRBs with the same CAPC value based on the same default SL DRB configuration. Multiple default SL DRBs with the same CAPC value can be distinguished by different logical channel identifiers (LCIDs).
- LCIDs logical channel identifiers
- the UE can determine the CAPC of the SL DRB established according to the SL DRB configuration after obtaining the SL DRB configuration, based on one or more QoS flows associated with the SL DRB configuration, wherein the number of established SL DRBs may be one or more, and the UE reasonably configures or reasonably determines the CAPC corresponding to the SL DRB based on one or more QoS flows, which can reduce the problems affecting the communication quality and fairness of the SL-U, for example, when the network does not configure the CAPC of the SL DRB or the configured CAPC is inappropriate, thereby achieving the purpose of ensuring the communication quality of the SL-U and the fairness of transmission of different business needs.
- the terminal device can establish multiple default SL DRBs accordingly after obtaining multiple different default SL DRB configurations, wherein the CAPC configuration associated with each default SL DRB configuration in the multiple different default SL DRB configurations is different, that is, the CAPC of each default SL DRB in the multiple default SL DRBs established by the terminal device according to the configuration is different, thereby ensuring that the CAPC corresponding to the QoS flow transmitted on the same default SL DRB is the same, thereby ensuring the communication quality of SL-U and the fairness of transmission of different business requirements. Therefore, the embodiment of the present application can guarantee the performance and fairness of SL-U. Therefore, the embodiment of the present application can guarantee the performance and fairness of SL-U.
- CAPC configuration described in the above embodiment may also be equivalent to the logical channel priority, that is, the solution in which the UE can determine the priority of the logical channel information according to the associated service data should also be covered within the protection scope of this application.
- the communication device includes hardware structures and/or software modules corresponding to the execution of each function.
- the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.
- Figure 7 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
- the communication device can be used to implement the functions of the UE or access network device in the above method embodiment, and thus can also achieve the beneficial effects of the above method embodiment.
- the communication device can be one of the terminals 120a-120j shown in Figure 1, or a module (such as a chip) applied to the terminal, or a wireless access network device 110a or 110b as shown in Figure 1.
- the communication device may include a transceiver unit 10 and a processing unit 20.
- the communication device may be used to implement the functions of the UE or access network device (base station) in the method embodiments shown in Fig. 5 and Fig. 6 above.
- the transceiver unit 10 can be used to obtain the first sidelink data radio link bearer SL DRB configuration; the processing unit 20 can be used to determine the CAPC of the SL DRB according to one or more service quality flows associated with the first SL DRB configuration, and the SL DRB is a SL DRB established according to the first SL DRB configuration.
- the number of SL DRBs is 1.
- the number of the SL DRBs is at least 2, and the CAPC of each of the at least 2 SL DRBs is different.
- the processing unit 20 is specifically used to determine the target CAPC among the one or more CAPCs corresponding to one or more service quality flows associated with the first SL DRB configuration as the CAPC of the SL DRB.
- the target CAPC includes any one or more of the following CAPCs:
- the CAPC with the largest number of service quality flows among the one or more CAPCs corresponding to the one or more service quality flows associated with the first SL DRB configuration.
- the processing unit 20 is specifically used to: determine the number of the at least two SL DRBs according to the different CAPC numbers corresponding to one or more service quality flows associated with the first SL DRB configuration, and establish the at least two SL DRBs; the CAPCs of the at least two SL DRBs respectively correspond to the CAPCs of the one or more service quality flows.
- the processing unit 20 is further configured to: determine that the first SL DRB configuration satisfies a first preset condition; the first preset condition includes one or more of the following conditions:
- the first SL DRB configuration is the default SL DRB configuration
- the first SL DRB configuration is obtained by means of a system information block SIB or a pre-configuration message;
- the first SL DRB configuration does not provide a corresponding CAPC configuration
- the CAPC configuration provided by the first SL DRB configuration is not suitable.
- the CAPC configuration provided by the first SL DRB configuration is not suitable and includes one or more of the following:
- the CAPCs corresponding to the multiple quality of service flows associated with the first SL DRB configuration are different;
- the maximum difference between the CAPCs corresponding to the multiple service quality flows associated with the first SL DRB configuration is greater than or equal to the first threshold
- the number of multiple service quality flows associated with the first SL DRB configuration is greater than or equal to a second threshold
- the minimum value of the CAPCs corresponding to multiple service quality flows associated with the first SL DRB configuration is greater than the CAPC value provided by the first SL DRB configuration.
- the transceiver unit 10 is further configured to: when the first SL DRB configuration does not provide a corresponding CAPC configuration or the When the CAPC configuration provided by the first SL DRB configuration is inappropriate, an indication message is sent to the access network device, where the indication message is used to indicate that the first SL DRB configuration does not provide a corresponding CAPC configuration or the CAPC configuration provided by the first SL DRB configuration is inappropriate; receiving a second SL DRB configuration sent by the access network device, where the second SL DRB configuration is different from the first SL DRB configuration;
- the terminal device when the first SL DRB configuration does not provide the corresponding CAPC configuration or the CAPC configuration provided by the first SL DRB configuration is inappropriate, if the terminal device is in the radio resource control RRC idle state or the RRC inactive state, it enters the RRC connected state; receives the second SL DRB configuration sent by the access network device, and the second SL DRB configuration is different from the first SL DRB configuration.
- the one or more quality of service flows associated with the first SL DRB configuration include a quality of service flow corresponding to a non-standard PC5 quality of service identifier
- the processing unit 20 is further used to: determine the CAPC of the quality of service flow corresponding to the non-standard PC5 quality of service identifier based on characteristic parameters of the quality of service flow corresponding to the non-standard PC5 quality of service identifier; the characteristic parameters are used to represent the quality of service characteristics of the quality of service flow corresponding to the non-standard PC5 quality of service identifier, and the characteristic parameters include one or more of packet delay budget, default priority, priority and packet error rate.
- the transceiver unit 10 is further used to: obtain a plurality of default SL DRB configurations; each of the plurality of default SL DRB configurations is associated with a different CAPC configuration;
- the processing unit 20 is also used to establish multiple default SL DRBs according to the multiple default SL DRB configurations.
- the processing unit 20 is further specifically used for: when the mapping rule of the corresponding SL DRB is not configured or stored for the quality of service flow to be transmitted, mapping the quality of service flow to be transmitted to a target default SL DRB among the multiple default SL DRBs, and the CAPC of the target default SL DRB is the same as the CAPC of the quality of service flow to be transmitted.
- the transceiver unit 10 is used to: receive an indication message sent by a terminal device, and/or send a second SL DRB configuration to the terminal device.
- the processing unit 20 can be used to determine and generate the second SL DRB configuration.
- the transceiver unit 10 is further used to: send multiple default SL DRB configurations; each of the multiple default SL DRB configurations is associated with a different CAPC configuration.
- the transceiver unit 10 is used to: obtain multiple default SL DRB configurations; the CAPC configuration associated with each default SL DRB configuration in the multiple default SL DRB configurations is different; the processing unit 20 is used to: establish multiple default SL DRBs according to the multiple default SL DRB configurations.
- the processing unit 20 is further used to: when the mapping rule of the corresponding SL DRB is not configured or stored for the service quality flow to be transmitted, map the service quality flow to be transmitted to a target default SL DRB among the multiple default SL DRBs, and the CAPC of the target default SL DRB is the same as the CAPC of the service quality flow to be transmitted.
- the transceiver unit 10 is used to: send multiple default SL DRB configurations; the CAPC configuration associated with each default SL DRB configuration in the multiple default SL DRB configurations is different; the processing unit 20 can be used to determine and generate the multiple default SL DRB configurations.
- the communication device includes a processor 810 and an interface circuit 820.
- the processor 810 and the interface circuit 820 are coupled to each other.
- the interface circuit 820 can be a transceiver or an input-output interface.
- the communication device may also include a memory 830 for storing instructions executed by the processor 810 or storing input data required for the processor 810 to run the instructions or storing data generated after the processor 810 runs the instructions.
- the processor 810 is used to implement the function of the processing unit 20
- the interface circuit 820 is used to implement the function of the transceiver unit 10 .
- the terminal chip When the above communication device is a chip applied to a terminal, the terminal chip implements the functions of the UE or access network device (base station) in the above method embodiment.
- the terminal chip receives information from other modules in the terminal (such as a radio frequency module or an antenna), and the information is sent to the terminal by other devices; or the terminal chip sends information to other modules in the terminal (such as a radio frequency module or an antenna), and the information is sent to other devices by the terminal.
- the processor 810 in the embodiment of the present application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
- the general-purpose processor can be a microprocessor or any conventional processor.
- An embodiment of the present application further provides a computer-readable storage medium, in which a computer program code is stored.
- a computer program code is stored.
- the embodiment of the present application also provides a terminal device, which can exist in the form of a chip product, and the terminal device includes a processor, which is configured to support the terminal device to implement the corresponding functions of the method in any of the above embodiments.
- the terminal device may also include a memory, which is coupled to the processor and stores the necessary program instructions and data of the terminal device.
- the terminal device may also include a communication interface for the terminal device to communicate with other devices or communication networks.
- the embodiment of the present application also provides a computer program product.
- the computer program product When the computer program product is run on a computer, the computer executes the method in any of the aforementioned embodiments.
- the embodiment of the present application provides a chip system, which includes a processor for supporting a device to implement the functions involved in the first aspect, for example, generating or processing information involved in the register parameter transfer method of the block instruction.
- the chip system also includes a memory, which is used to store program instructions and data necessary for the device.
- the chip system can be composed of a chip, or it can include a chip and other discrete devices.
- the disclosed devices can be implemented in other ways.
- the device embodiments described above are only schematic, such as the division of the above-mentioned units, which is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
- Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, and the indirect coupling or communication connection of devices or units can be electrical or other forms.
- the units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present application.
- each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
- the above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
- the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
- the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc., specifically a processor in a computer device) to perform all or part of the steps of the above-mentioned methods of each embodiment of the present application.
- a computer device which can be a personal computer, a server or a network device, etc., specifically a processor in a computer device
- the aforementioned storage medium may include: U disk, mobile hard disk, magnetic disk, optical disk, read-only memory (Read-Only Memory, abbreviated: ROM) or random access memory (Random Access Memory, abbreviated: RAM) and other media that can store program codes.
- ROM Read-Only Memory
- RAM Random Access Memory
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请公开了一种通信方法和相关设备,该方法可包括:获取第一侧行链路数据无线链路承载SL DRB配置;根据所述第一SL DRB配置所关联的一个或多个服务质量流,确定SL DRB的CAPC,所述SL DRB为根据所述第一SL DRB配置建立的SL DRB。本申请能够保证SL-U的通信质量,以及不同业务需求传输的公平性。
Description
本申请要求于2022年11月03日提交中国专利局、申请号为202211372337.6、申请名称为“一种通信方法和相关设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及通信技术领域,尤其涉及一种通信方法和相关设备。
在无线通信系统中,终端设备和终端设备之间可以通过网络设备(如接入网设备)进行数据通信,也可以不借助网络设备,直接进行终端设备与终端设备之间的数据通信。其中,终端设备与终端设备之间直接进行数据通信的接口称为PC5接口,终端设备与终端设备之间直接进行数据通信的链路称为侧行链路(sidelink,SL)。sidelink通信的典型应用场景有车联网(vehicle to everything,V2X)和邻近业务(proximity-based services,ProSe)。以车联网为例,车联网中的每个车辆即为一个终端设备,车辆与车辆之间可以通过sidelink直接进行数据传输,而不需要借助网络设备,这样可以有效地减少通信时延。
可用于sidelink通信的频谱资源一般分为两类,一类是授权频谱,另一类是非授权频谱。其中,授权频谱只能让某一些机构或运营商使用,而非授权频谱为共享频谱,不同的运营商或机构都可以使用。为公平的使用非授权频谱,工作在非授权频谱下的设备在发送数据之前,需要采用先听后说(listen-before-talk,LBT)的信道竞争接入机制侦听信道是否空闲,当信道空闲时,才能占用信道并传输数据。
对于非授权频谱的sidelink(SL-U)通信,如何保证整个SL-U通信的性能以及公平性的方案尚待探索。
发明内容
本申请实施例提供一种通信方法和相关设备,能够保证SL-U的通信质量,以及不同业务需求传输的公平性。
第一方面,本申请实施例提供了一种通信方法,应用于终端设备,可包括:获取第一侧行链路数据无线链路承载SL DRB配置;根据所述第一SL DRB配置所关联的一个或多个服务质量流,确定SL DRB的CAPC,所述SL DRB为根据所述第一SL DRB配置建立的SL DRB。
针对UE使用的SL DRB对应的CAPC配置由基站下发或者通过预配置消息得到,当多个QoS流映射到一个SL DRB上传输时,这些QoS流的QoS特征可能差别很大,即QoS流需要的CAPC可能不同,从而可能出现SL DRB的CAPC配置与这些QoS流的CAPC不合适,或者出现SL DRB无CAPC配置的情况,影响整个SL-U通信的性能以及公平性的问题。本申请实施例中,UE可以在获取到SL DRB配置后,根据SL DRB配置关联的一个或多个QoS流,确定根据该SL DRB配置建立的SL DRB的CAPC,其中,建立的SL DRB的数量可以是1个,也可以是多个。基于此,UE可以根据一个或多个QoS流,合理的配置或者合理的确定SL DRB对应的CAPC,从而可以减少例如当网络没有配置SL DRB的CAPC或者配置的CAPC不合适时,影响SL-U的通信质量和公平性的问题,达到保证SL-U的通信质量,以及不同业务需求传输的公平性的目的。
在一种可能的实现方式中,所述SL DRB的数量为1个。
本申请实施例中,UE可以根据多个QoS flow确定一个SL DRB对应的CAPC,可以减少例如当网络没有配置SL DRB的CAPC或者配置的CAPC不合适时,影响SL-U的通信质量和公平性的问题,达到保证SL-U的通信质量,以及不同业务需求传输的公平性的目的。
在一种可能的实现方式中,所述SL DRB的数量为至少2个,所述至少2个SL DRB中每个SL DRB的CAPC不同。
本申请实施例中,UE根据SL DRB配置建立多个SL DRB,使得每个SL DRB中实际传输的都是CAPC相对应的QoS flow,保证SL-U的通信质量,以及不同业务需求传输的公平性。
在一种可能的实现方式中,所述方法,还包括:将所述第一SL DRB配置所关联的一个或多个服务质量流对应的一个或多个CAPC中的目标CAPC,确定为所述SL DRB的CAPC。
本申请实施例中,UE可以根据实际业务需求从多个QoS流对应的多个CAPC中确定出满足实际业务需求的目标CAPC,并将该目标CAPC确定为SL DRB的CAPC,保证SL DRB可以满足实际业务传输的
需求。
在一种可能的实现方式中,所述方法,还包括:将所述SL DRB配置所关联的一个或多个服务质量流中特征参数满足第二预设条件的服务质量流对应的CAPC,确定为所述一个SL DRB的CAPC;所述特征参数用于表示服务质量流的服务质量特性;或者将所述SL DRB配置所关联的一个或多个服务质量流对应的一个或多个CAPC中的最大CAPC值、最小CAPC值或CAPC平均值,确定为所述一个SL DRB的CAPC;或者将所述SL DRB配置所关联的一个或多个服务质量流对应的一个或多个CAPC中对应的服务质量流最多的CAPC,确定为所述一个SL DRB的CAPC。
本申请实施例中,UE可以根据一定的规则,从多个QoS流对应的多个CAPC中确定出满足规则要求的目标CAPC,并将该目标CAPC确定为SL DRB的CAPC,保证SL DRB对应的CAPC的准确性。
在一种可能的实现方式中,所述目标CAPC包括以下CAPC中的任意一种或多种:所述第一SL DRB配置所关联的一个或多个服务质量流中包延时预算最小或最大的服务质量流的CAPC;所述第一SL DRB配置所关联的一个或多个服务质量流中默认优先级最小或最大的服务质量流的CAPC;所述第一SL DRB配置所关联的一个或多个服务质量流中优先级最小或最大的服务质量流的CAPC;所述第一SL DRB配置所关联的一个或多个服务质量流中包错误率最小或最大的服务质量流的CAPC;所述第一SL DRB配置所关联的一个或多个服务质量流对应的一个或多个CAPC中的最大CAPC值、最小CAPC值或CAPC平均值;或所述第一SL DRB配置所关联的一个或多个服务质量流对应的一个或多个CAPC中对应服务质量流数量最多的CAPC。
本申请实施例中,UE可以根据一定的规则,从多个QoS流对应的多个CAPC中确定出满足规则要求的目标CAPC,并将该目标CAPC确定为SL DRB的CAPC,保证SL DRB对应的CAPC的准确性。
在一种可能的实现方式中,所述特征参数包括包延时预算、默认优先级、优先级和包错误率中的一种或多种;所述第二预设条件包括以下条件中的任意一种:包延时预算为所述SL DRB配置所关联的一个或多个服务质量流对应的一个或多个包延时预算中的最小值或最大值;默认优先级为所述SL DRB配置所关联的一个或多个服务质量流对应的一个或多个默认优先级中的最小值或最大值;优先级为所述SL DRB配置所关联的一个或多个服务质量流对应的一个或多个优先级中的最小值或最大值;或包错误率为所述SL DRB配置所关联的一个或多个服务质量流对应的一个或多个包错误率中的最小值或最大值。
本申请实施例中,UE可以根据一定的规则,从多个QoS流对应的多个CAPC中确定出满足规则要求的目标CAPC,并将该目标CAPC确定为SL DRB的CAPC,保证SL DRB对应的CAPC的准确性。
在一种可能的实现方式中,所述方法,还包括:根据所述第一SL DRB配置所关联的一个或多个服务质量流对应的不同的CAPC数量确定所述至少2个SL DRB的数量,并建立所述至少2个SL DRB;所述至少2个SL DRB的CAPC分别与所述一个或多个服务质量流的CAPC对应。
本申请实施例中,UE可以根据QoS流对应的不同的CAPC数量确定出SL DRB的数量,并按照该数量建立SL DRB,每个SL DRB的CAPC分别与QoS流的CAPC对应,保证各个QoS流可以公平传输的同时,节省链路承载的资源。
在一种可能的实现方式中,所述方法,还包括:确定所述第一SL DRB配置满足第一预设条件;所述第一预设条件包括以下条件中的一种或多种:所述第一SL DRB配置为缺省default SL DRB配置;所述第一SL DRB配置通过系统信息块SIB或预配置消息的方式获取;所述第一SL DRB配置未提供对应的CAPC配置;或所述第一SL DRB配置提供的CAPC配置不合适。
本申请实施例中,UE在确定SL DRB的CAPC之前,可以先确定SL DRB配置是否满足一定条件(即第一预设条件),当确定SL DRB配置满足条件后,再确定SL DRB的CAPC。避免UE无条件执行确定SL DRB的CAPC,导致资源浪费。
在一种可能的实现方式中,所述第一SL DRB配置提供的CAPC配置不合适包括以下的一种或多种:所述第一SL DRB配置所关联的多个服务质量流对应的CAPC不同;所述第一SL DRB配置所关联的多个服务质量流对应的CAPC之间的最大差值大于或等于第一阈值;所述第一SL DRB配置所关联的多个服务质量流的数量大于或等于第二阈值;或所述第一SL DRB配置所关联的多个服务质量流对应的CAPC中的最小值大于所述第一SL DRB配置提供的CAPC值。
本申请实施例中,UE可以根据一定条件判断出SL DRB配置提供的CAPC配置是否合适,例如,当SL DRB配置关联的QoS流的数量超过一定数量(即第二阈值)时,可以直接认为SL DRB配置提供的CAPC配置不合适,进而UE可以根据QoS流再确定SL DRB的CAPC,保证SL-U的通信质量,以及不同业务需求传输的公平性。
在一种可能的实现方式中,所述方法,还包括:当所述第一SL DRB配置未提供对应的CAPC配置或所述第一SL DRB配置提供的CAPC配置不合适时,向接入网设备发送指示消息,所述指示消息用于指示所述第一SL DRB配置未提供对应的CAPC配置或所述第一SL DRB配置提供的CAPC配置不合适;接收所述接入网设备发送的第二SL DRB配置,所述第二SL DRB配置与所述第一SL DRB配置不同;或者当所述第一SL DRB配置未提供对应的CAPC配置或所述第一SL DRB配置提供的CAPC配置不合适时,若所述终端设备处于无线资源控制RRC空闲态或RRC非激活态,进入RRC连接态;接收所述接入网设备发送的第二SL DRB配置,所述第二SL DRB配置与所述第一SL DRB配置不同。
本申请实施例中,UE在确定SL DRB配置未提供对应的CAPC配置或SL DRB配置提供的CAPC配置不合适时,可以向接入网设备发送指示消息或者触发接入RRC连接态的流程,然后接收接入网设备发送的新的SL DRB配置(即第二SL DRB配置),使得UE可以利用CAPC合适的SL DRB对QoS流进行传输,保证SL-U的通信质量,以及不同业务需求传输的公平性。
在一种可能的实现方式中,所述第一SL DRB配置所关联的一个或多个服务质量流包括非标准的PC5服务质量标识对应的服务质量流,所述方法,还包括:根据所述非标准的PC5服务质量标识对应的服务质量流的特征参数,确定所述非标准的PC5服务质量标识对应的服务质量流的CAPC;所述特征参数用于表示非标准的PC5服务质量标识对应的服务质量流的服务质量特性,所述特征参数包括包延时预算、默认优先级、优先级和包错误率中的一种或多种。
本申请实施例中,如果SL DRB配置关联的QoS流中有非标准的QoS流,UE可以根据非标准的QoS流的特征参数,确定该非标准的服务质量流的CAPC,进而可以根据一定规则,确定是否将该非标准的服务质量流的CAPC确定为SL DRB的CAPC,保证了非标准的QoS流传输的公平性。
在一种可能的实现方式中,所述方法,还包括:获取多个default SL DRB配置;所述多个default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同;根据所述多个default SL DRB配置建立多个default SL DRB。
本申请实施例中,UE在可以自行确定SL DRB的CAPC,保证SL-U的通信质量,以及不同业务需求传输公平性的同时,还可以获取多个CAPC配置不同的default SL DRB配置,并根据这些default SL DRB配置分别建立default SL DRB,即default SL DRB的CAPC不同,为后续映射到default SL DRB的QoS流可以有CAPC合适的default SL DRB进行传输提供保障,能够进一步保证SL-U的通信质量,以及不同业务需求传输公平性。
在一种可能的实现方式中,所述方法,还包括:当待传输的服务质量流未配置或未存储对应的SL DRB的映射规则时,将所述待传输的服务质量流映射到所述多个default SL DRB中的目标default SL DRB,所述目标default SL DRB的CAPC与所述待传输的服务质量流的CAPC相同。
本申请实施例中,当QoS流需要被映射到default SL DRB时,即当QoS流未配置或未存储对应的SL DRB的映射规则,UE可以根据QoS流的CAPC将QoS流映射到CAPC与之相同的default SL DRB(即目标default SL DRB)上进行传输,保证SL-U的通信质量,以及不同业务需求传输的公平性。
在一种可能的实现方式中,所述方法,还包括:当待传输的服务质量流未配置或未存储对应的SL DRB的映射规则时,将所述待传输的服务质量流映射到所述多个default SL DRB中CAPC与所述待传输的服务质量流的CAPC相同的default SL DRB。
本申请实施例中,当QoS流需要被映射到default SL DRB时,即当QoS流未配置或未存储对应的SL DRB的映射规则,UE可以根据QoS流的CAPC将QoS流映射到CAPC与之相同的default SL DRB上进行传输,保证SL-U的通信质量,以及不同业务需求传输的公平性。
第二方面,本申请实施例提供了一种通信方法,应用于接入网设备,可包括:接收终端设备发送的指示消息,和/或向所述终端设备发送第二SL DRB配置。
在一种可能的实现方式中,所述方法还包括:发送多个default SL DRB配置;所述多个default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同。
第三方面,本申请实施例提供了一种通信方法,应用于终端设备,可包括:获取多个default SL DRB配置;所述多个default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同;根据所述多个default SL DRB配置建立多个default SL DRB。
本申请实施例中,UE可以获取多个CAPC配置不同的default SL DRB配置,并根据这些default SL DRB
配置分别建立default SL DRB,即default SL DRB的CAPC不同,为后续映射到default SL DRB的QoS流可以有CAPC合适的default SL DRB进行传输提供保障。
在一种可能的实现方式中,所述方法,还包括:当待传输的服务质量流未配置或未存储对应的SL DRB的映射规则时,将所述待传输的服务质量流映射到所述多个default SL DRB中的目标default SL DRB,所述目标default SL DRB的CAPC与所述待传输的服务质量流的CAPC相同。
在一种可能的实现方式中,所述方法,还包括:当待传输的服务质量流未配置或未存储对应的SL DRB的映射规则时,将所述待传输的服务质量流映射到所述多个default SL DRB中CAPC与所述待传输的服务质量流的CAPC相同的default SL DRB。
第四方面,本申请实施例提供了一种通信方法,应用于接入网设备,可包括:发送多个default SL DRB配置;所述多个default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同。
第五方面,本申请实施例提供了一种通信装置,该通信装置中包括处理器,处理器被配置为支持该通信装置实现第一方面、第二方面、第三方面或第四方面中任一方面所提供的通信方法中相应的功能。该通信装置还可以包括存储器,存储器用于与处理器耦合,其保存该通信装置必要的程序指令和数据。该通信装置还可以包括接口电路,用于该通信装置与其他设备或通信网络通信。
第六方面,本申请实施例提供了一种计算机可读存储介质,用于存储上述第五方面中的一种或多种所提供的一种用于实现通信方法的通信装置所用的计算机软件指令,其包含用于执行上述方面所设计的程序。
第七方面,本申请实施例提供了一种计算机程序,该计算机程序包括指令,当该计算机程序被计算机执行时,使得计算机可以执行上述第五方面中的一种或多种所提供的一种用于实现通信方法的通信装置所执行的流程。
第八方面,本申请实施例提供了一种芯片系统,该芯片系统包括处理器,用于支持设备实现上述第一方面、第二方面、第三方面或第四方面中任一方面所涉及的功能,例如,生成或处理上述通信方法中所涉及的信息。在一种可能的设计中,所述芯片系统还包括存储器,所述存储器,用于保存设备必要的程序指令和数据。该芯片系统,可以由芯片构成,也可以包含芯片和其他分立器件。
为了更清楚地说明本申请实施例或背景技术中的技术方案,下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1是本申请实施例提供的通信系统的架构示意图。
图2是本申请实施例提供的Sidelink UE-to-Network Relay场景示意图。
图3是本申请实施例提供的Sidelink UE-to-UE Relay场景示意图。
图4是本申请实施例提供的一种基于非授权频谱进行上行传输的流程示意图。
图5是本申请实施例提供的一种通信方法的流程示意图。
图6是本申请实施例提供的另一种通信方法的流程示意图。
图7是本申请实施例提供的通信装置的一种结构示意图。
图8是本申请实施例提供的通信装置的另一种结构示意图。
下面将结合本申请实施例中的附图,对本申请实施例进行描述。
本申请中,“以下一项(个)或多项(个)”或其类似表达,是指的这些项中的任意组合,包括单项(个)或复数项(个)的任意组合。例如,以下一项(个)或多项(个):a,b,或c,可以表示:a,b,c;a和b;a和c;b和c;或a和b和c。其中a,b,c可以是单个,也可以是多个。“至少一个”是指一个或者多个,“多个”是指两个或两个以上。“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B的情况,其中A,B可以是单数或者复
数。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请的说明书和权利要求书及所述附图中的术语“第一”、“第二”、“第三”和“第四”等是用于区别不同对象,而不是用于描述特定顺序。此外,术语“包括”和“具有”以及它们任何变形,意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元,而是可选地还包括没有列出的步骤或单元,或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
在本文中提及“实施例”意味着,结合实施例描述的特定特征、结构或特性可以包含在本申请的一个或多个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例,也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员显式地和隐式地理解的是,本文所描述的实施例可以与其它实施例相结合。
本申请中,“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”、“举例来说”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言,使用“示例性的”、“举例来说”或者“例如”等词旨在以具体方式呈现相关概念。
应理解,在本申请中,“当…时”、“若”以及“如果”均指在某种客观情况下装置会做出相应的处理,并非是限定时间,且也不要求装置实现时一定要有判断的动作,也不意味着存在其它限定。
本申请中的“同时”可以理解为在相同的时间点,也可以理解为在一段时间段内,还可以理解为在同一个周期内,具体可以结合上下文进行理解。
本申请中对于使用单数表示的元素旨在用于表示“一个或多个”,而并非表示“一个且仅一个”,除非有特别说明。
另外,本文中术语“系统”和“网络”可互换替换使用。
应理解,在本申请各实施例中,“与A对应的B”表示B与A相关联,根据A可以确定B。但还应理解,根据A确定B并不意味着仅仅根据A确定B,还可以根据A和/或其它信息确定B。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如,部件可以是但不限于,在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示,在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中,部件可位于一个计算机上和/或分布在2个或更多个计算机之间。此外,这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据,例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本申请实施例的技术方案可以应用于sidelink通信系统中,也可以应用于其它工作在非授权频谱(unlicensed band)的通信系统中,例如;长期演进(long term evolution,LTE)系统、新一代无线接入技术(new radio access technology,NR)通信系统、下一代无线局域网(wireless local area network,WLAN)系统等,当然也可以是未来工作在非授权频谱的通信系统,如第六代(6th generation,6G)甚至第七代(7th generation,7G)系统等。可理解,本申请提及的“工作在非授权频谱的通信系统”是指该通信系统在一些情况下工作在非授权频谱,当然在其它的一些情况下该通信系统也可以工作在授权频谱。
应理解,本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案,并不构成对于本申请实施例提供的技术方案的限定,本领域普通技术人员可知,随着通信网络架构的演变和新业务场景的出现,本申请实施例提供的技术方案对于类似的技术问题,同样适用。
参见图1,图1是本申请实施例提供的通信系统的架构示意图。如图1所示,该通信系统包括无线接入网100。其中,无线接入网100可以包括至少一个无线接入网设备(如图1中的110a和110b),还可以包括至少一个终端设备(如图1中的120a-120j)。终端设备可以通过无线的方式与无线接入网设备相连,终端设备和终端设备之间以及无线接入网设备和无线接入网设备之间可以通过有线或无线的方式相互连接。可理解,图1只是示意图,该通信系统中还可以包括其它网络设备,如还可以包括核心网设备、无线中继设备以及无线回传设备等,在图1中未画出。
无线接入网设备可以简称为网络设备,是终端通过无线方式接入到通信系统中的接入设备。无线接入网设备可以是基站(base station)、演进型基站(evolved NodeB,eNodeB)、发送接收点(transmission reception point,TRP)、第五代(5th generation,5G)移动通信系统中的下一代基站(next generation NodeB,gNB)、
第六代(6th generation,6G)移动通信系统中的下一代基站、未来移动通信系统中的基站或WiFi系统中的接入节点等;也可以是完成基站部分功能的模块或单元,例如,可以是集中式单元(central unit,CU),也可以是分布式单元(distributed unit,DU)。这里的CU完成基站的无线资源控制协议和分组数据汇聚层协议(packet data convergence protocol,PDCP)的功能,还可以完成业务数据适配协议(service data adaptation protocol,SDAP)的功能;DU完成基站的无线链路控制层和介质访问控制(medium access control,MAC)层的功能,还可以完成部分物理层或全部物理层的功能,有关上述各个协议层的具体描述,可以参考第三代合作伙伴计划(3rd generation partnership project,3GPP)的相关技术规范。无线接入网设备可以是宏基站(如图1中的110a),也可以是微基站或室内站(如图1中的110b),还可以是中继节点或施主节点等。本申请的实施例对无线接入网设备所采用的具体技术和具体设备形态不做限定。为了便于描述,下文以基站作为无线接入网设备的例子进行描述。
终端设备是具有无线收发功能的设备,可以向基站发送信号,或接收来自基站的信号。终端设备也可以称为终端、用户设备(user equipment,UE)、移动台、移动终端等。终端设备可以广泛应用于各种场景,例如,设备到设备(device-to-device,D2D)、车物(vehicle to everything,V2X)通信、机器类通信(machine-type communication,MTC)、物联网(internet of things,IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、飞机、轮船、机器人、机械臂、智能家居设备等。本申请的实施例对终端所采用的具体技术和具体设备形态不做限定。
基站和终端可以是固定位置的,也可以是可移动的。基站和终端可以部署在陆地上,包括室内或室外、手持或车载;也可以部署在水面上;还可以部署在飞机、气球和人造卫星上。本申请的实施例对基站和终端的应用场景不做限定。
基站和终端的角色可以是相对的,例如,图1中的直升机或无人机120i可以被配置成移动基站,对于那些通过120i接入到无线接入网100的终端120j来说,终端120i是基站;但对于基站110a来说,120i是终端,即110a与120i之间是通过无线空口协议进行通信的。当然,110a与120i之间也可以是通过基站与基站之间的接口协议进行通信的,此时,相对于110a来说,120i也是基站。因此,基站和终端都可以统一称为通信装置,图1中的110a和110b可以称为具有基站功能的通信装置,图1中的120a-120j可以称为具有终端功能的通信装置。
基站和终端之间、基站和基站之间、终端和终端之间可以通过授权频谱进行通信,也可以通过非授权频谱进行通信,也可以同时通过授权频谱和非授权频谱进行通信;可以通过6千兆赫(gigahertz,GHz)以下的频谱进行通信,也可以通过6GHz以上的频谱进行通信,还可以同时使用6GHz以下的频谱和6GHz以上的频谱进行通信。
本申请主要关注终端和终端之间通过非授权频谱进行通信的情况。可理解,终端和终端之间的接口为PC5接口,终端与基站之间的接口为Uu接口。终端可以使用非授权频谱与另一终端进行sidelink通信,终端与终端备之间的通信可以是单播通信、组播通信、或广播通信。在sidelink通信中,终端可配置一个或多个天线,用于收发消息/信息/数据等。可理解,终端还可包括与消息/信息/数据发送和接收相关的多个部件(例如,处理器、调制器、复用器、解调器或解复用器等)。
本申请实施例中,用于实现终端的功能的装置可以是终端;也可以是能够支持终端实现该功能的装置,例如芯片系统、或通信模块、或调制解调器等,该装置可以被安装在终端中。本申请实施例中,芯片系统可以由芯片构成,也可以包括芯片和其他分立器件。本申请实施例提供的技术方案中,以用于实现终端的功能的装置是终端,以终端是UE为例,描述本申请实施例提供的技术方案。本申请的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
一些场景中,UE也可以用于充当基站。例如,UE可以充当调度实体,其在车联网(vehicle-to-everything,V2X)、设备到设备(device-to-device,D2D)或点对点(peer to peer,P2P)等中的UE之间提供侧行链路信号。
一些场景中,UE也可以用于充当中继节点。例如:UE可以充当中继设备(relay),或者接入回传一体化(integrated access and backhaul,IAB)节点,用于为终端设备提供无线回传服务。
可选的,sidelink通信的一个典型应用场景即车联网(V2X)。本申请提供的方法不仅可以应用于V2X场景(如前述图1中120a与120b通信的场景),还可以应用于侧行链路UE到网络中继(Sidelink UE-to-Network Relay)场景,和侧行链路UE到UE中继(Sidelink UE-to-UE Relay)场景。参见图2,图2是本申请实施例提供的Sidelink UE-to-Network Relay场景示意图。如图2所示,Sidelink UE-to-Network Relay场景中包括Remote
UE(远程UE)和Relay UE(中继UE),还包括基站;本申请提供的方法可以应用于Remote UE和Relay UE之间的通信。参见图3,图3是本申请实施例提供的Sidelink UE-to-UE Relay场景示意图。如图3所示,Sidelink UE-to-UE Relay场景中包括Source UE(源UE)、Relay UE(中继UE)以及target UE(目标UE);本申请提供的方法可以应用于Source UE和Relay UE之间的通信和/或Relay UE和target UE之间的通信。
在本申请实施例中,术语“无线通信”还可以简称为“通信”,术语“通信”还可以描述为“数据传输”、“信息传输”或“传输”。
下面,对本申请相关的部分用语进行解释说明,以便于本领域技术人员理解。
(1)UE获取sidelink资源的方式
UE获取sidelink资源的方式有两种,一种是基站调度模式(也称为mode1),另一种是自主竞争模式(也称为mode2)。当UE工作在mode1时,UE从基站获取SL资源,具体的,基站可以通过下行链路控制信息(downlink control information,DCI)给UE调度SL资源,或者通过无线资源控制(radio resource control,RRC)消息给UE配置SL配置授权(configured grant)。当UE工作在mode2时,UE可以从基站接收SL资源池配置,或者从预配置中获取SL资源池配置,然后在SL资源池中选择SL资源进行发送。具体的,SL资源的选择可以是随机选择,也可以是基于监听(sensing)或者部分监听(partial sensing)的结果进行选择。
(2)先听后说(listen-before-talk,LBT)的信道竞争接入机制
为了公平的使用非授权频谱,终端和网络设备在发送数据之前,需要进行LBT过程(信道接入过程)。通常,LBT是以信道(例如20MHz的信道)为粒度进行的。设备在某个信道上发送信号(例如,数据信号)之前,可以先检测该信道是否空闲,例如,是否检测到附近的设备正在占用该信道发送信号,这一检测过程可以称为空闲信道评估(clear channel assessment,CCA)或者称为信道接入过程。信道接入过程有两种,分别是第一类型的信道接入过程和第二类型的信道接入过程。
第一类型(type1)的信道接入过程(也可以称为基于固定时长的信道接入过程)可以是:基于固定时长的能量检测,针对一定带宽,例如20MHz,设备(该设备可以是终端设备,也可以是网络设备)在固定时长内接收到的信号能量小于或等于第一预设门限,则认为信道空闲(idle);从而该设备可以使用该空闲的信道传输数据;在固定时长内接收到的信号能量大于第一预设门限,认为信道忙碌(busy),从而该设备不使用该忙碌的信道传输数据。
第二类型(type2)的信道接入过程(也可以称为基于回退的信道接入过程)可以是:基于回退机制的能量检测,针对一定带宽,定义一个窗口,该窗口定义了检测的时隙数量的范围,设备从该窗口(或取值范围)内,随机选择一个数值A,设备检测到至少A个空闲的时隙之后,则认为信道空闲,从而该设备可以使用该空闲的信道传输数据;如果没有空隙的时隙或空隙的时隙少于A个,则认为信道忙碌,从而该设备不使用该忙碌的信道传输数据。其中,空闲的时隙是指在一个时隙内接收到的信号能量小于或等于第二预设门限。其中,第一预设门限和第二预设门限可以是预定义的,例如协议预定义的。此外第一预设门限和第二预设门限的取值可以相同,也可以不相同。
以type1为例,设备在进行type1(固定时长的能量检测)的LBT时(也就是第一类型的信道接入过程),需要根据信道接入优先级类别(channel access priority class,CAPC)来确定竞争窗口大小(Contention Window size,CW size)以及信道占用时间(channel occupancy time,COT)。CAPC与COT的关系如下述表1所示,表1中第一列表示CAPC值,该CAPC值越小,该CAPC对应的优先级越高;表1中第五列表示不同CAPC值对应的COT大小(单位为毫秒ms)。可理解,表1中其它列的含义可以参考现有标准,比如,第三代合作伙伴计划(3rd generation partnership project,3GPP)技术规范(technical specification,TS)37.213V17.2.0,或者参考其它版本的技术规范,这里不一一详述。
表1
执行信道接入过程可以得到两种结果:信道接入过程完成(也称为LBT成功)和信道接入过程未完成(也称为LBT失败)。其中,示例性地,在可用于数据传输的时频资源中可以有多个时域起始位置,在任
意时域起始位置之前确定信道空闲,则可以认为信道接入过程完成;在所有时域起始位置之前都确定信道忙碌,则可以认为信道接入过程未完成。
(3)基于非授权频谱的Uu通信
这里的Uu通信是指UE和基站之间通过空口进行通信。对于基站和UE都在授权频谱工作的情况,基站为UE调度上行资源后,UE可以直接使用该上行资源进行上行传输。而对于基站和UE都在非授权频谱工作的情况,可参见图4,图4是本申请实施例提供的一种基于非授权频谱进行上行传输的流程示意图,基站为UE调度上行资源之后,UE可能仍然需要对该上行资源进行LBT,只有在LBT成功之后,才可以使用该上行资源进行上行传输。换句话说,如果对调度的上行资源进行LBT,LBT失败,则无法使用该调度的上行资源。
针对Uu口的非授权频谱通信(NR-U),基站可以为每个数据无线链路承载(Data Radio Bearer,DRB)配置对应的CAPC。具体地,DRB所关联的逻辑信道(Logical Channel,LCH)配置中可以包括CAPC配置。当基站配置DRB的CAPC时,基站需要考虑映射到这个DRB的所有服务质量(Quality of Service,QoS)流(flows)对应的5G服务质量标识(5G QoS Identifier,5QI),同时基站也需要考虑不同业务类型和传输之间的公平性。标准上定义了标准5QI和CAPC的映射表(也就是定义了标准5QI所对应的QoS flow所使用的CAPC),如表2所示,较低的CAPC值意味着较高的优先级,第二列中的数值表示对应标准5QI的索引值,CAPC为4对应的5QI目前尚未明确定义;同时规定了对于非标5QI(non-standardized 5QI)的QoS flow,需要使用QoS特性(QoS characteristics)最匹配的标准5QI所对应的CAPC作为自身的CAPC。
表2
5QI用来表示一组QoS characteristics,其中,QoS characteristics可以包括资源类型(resource type)、默认优先级(default priority level)、优先级(priority level)、包延时预算(packet delay budget,PDB)、包错误率(packet error rate,PER)、默认最大数据突发量(Default Maximum Data Burst Volume,DMDV)、默认平均窗口(Default Averaging Window)中的一种或多种。
(4)关于SL通信的QoS flow
针对SL通信,QoS flow也可以支持标准PC5服务质量标识(standardized PC5QoS Identifier,standardized PQI)和非标PQI(non-standardized PQI)两种方式。其中,标准PQI与CAPC之间也有一个映射表,可参考上述表2中5QI与CAPC的映射关系,在此不另外展开。
对于标准PQI,每个PQI对应一组QoS characteristics,包括资源类型(resource type)、默认优先级(default priority level)、包延时预算(packet delay budget,PDB)、包错误率(packet error rate,PER)、默认最大数据突发量(Default Maximum Data Burst Volume,DMDV)、默认平均窗口(Default Averaging Window)中的一种或多种。同时,标准PQI可能和上层指示的优先级一起使用,该优先级可以用来覆盖(override)标准PQI对应的默认优先级。
对于非标PQI,V2X层可以给接入层(Access Stratum,AS)提供整套具体的非标QoS characteristics。
其中,标准PQI与QoS characteristics的映射关系可以参考以下表3和表4,表3和表4分别为针对V2X和ProSe所定义的标准PQI和QoS characteristics映射关系表。
表3
表4
首先,分析并提出本申请所具体要解决的技术问题。对于SL DRB配置,UE可以通过RRC专用信令、系统信息块(System Information Block,SIB)消息或者预配置消息等方式获取。具体地,可以分为以下几种不同的情况:
(1)UE处于RRC连接态,UE通过SUI消息(Sidelink UE information)上报QoS参数,基站通过RRC专用信令配置QoS流到SL DRB的映射关系以及SL DRB配置。
(2)UE处于RRC空闲态/RRC非激活态,基站通过SIB消息配置QoS流到SL DRB的映射关系以及SL DRB配置。
(3)UE处于覆盖范围外(Out of coverage,OOC)态,使用预配置消息的QoS流到SL DRB的映射关系以及SL DRB配置。
同时,SL DRB配置也可以支持缺省(default)SL DRB配置。具体地,当UE在存储的显示的QoS流到SL DRB的映射关系中找不到对应的QoS流,那么该QoS flow会被映射到default SL DRB上进行传输。其中,显示的QoS流到SL DRB的映射关系,可以通过指示QoS流标识到SL DRB的映射关系进行表示,也可以是通过指示QoS流对应的QoS参数(例如QoS文件、QoS配置文件(profile))到SL DRB的映射关系进行表示。QoS flow到SL DRB的映射关系可以是多个QoS flow映射到一个SL DRB上,也即是说,
一个SL DRB上可以承载多个QoS flow的数据传输。
该方案存在以下缺点:
影响整个SL-U通信的性能以及公平性。具体地,多个QoS flow映射到一个SL DRB上进行传输时,这些QoS flow的QoS characteristics可能差别很大(例如不同QoS流之间的PDB(包延迟预算)差异很大),特别是针对UE处于RRC空闲态/RRC非激活态/OOC态的情况,考虑到QoS flow也可能对应non-standardized PQI的情况以及信令开销,网络不可能将所有与non-standardized PQI的QoS flow显示的映射到非default SL DRB上进行传输,也即是说,很多non-standardized PQI的QoS flow最终会被映射到default SL DRB上进行传输,而这些non-standardized PQI的QoS flow之间的QoS characteristics可能差别很大,这也就意味着,这些QoS flow本身所对应的CAPC的差别可能也是很大。那么,对于传输这些QoS flow的SL DRB而言,它的CAPC可能是没有配置的或者配置了但是其实是不合适的,这会影响整个SL-U通信的性能以及公平性,例如,SL DRB的CAPC没有配置,可能无法传输这些QoS flow,或者基于不合适的CAPC进行传输。
为了解决整个SL-U通信的性能以及公平性的问题,综合考虑上述存在的缺点,本申请实际要解决的技术问题包括如下:
合理的配置或者合理的确定SL DRB对应的CAPC,保证整个SL-U通信的性能和公平性。本申请实施例中,终端设备可以在获取到SL DRB配置后,根据SL DRB配置关联的一个或多个QoS流,确定根据该SL DRB配置建立的SL DRB的CAPC,其中,建立的SL DRB的数量可以是1个,也可以是多个,当SL DRB的数量为多个时,每个SL DRB对应的CAPC不同,减少例如当网络没有配置SL DRB的CAPC或者配置的CAPC不合适时,影响SL-U的通信质量和公平性的问题,达到保证SL-U的通信质量,以及不同业务需求传输的公平性的目的。另外,针对使用default SL DRB的场景,终端设备可以在获取到多个不同的default SL DRB配置后,对应建立多个default SL DRB,其中,多个不同的default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同,也即是说,终端设备根据配置对应建立的多个default SL DRB中每个default SL DRB的CAPC不同,从而可以保证同一个default SL DRB上传输的QoS flow对应的CAPC都是相同的,以此保证SL-U的通信质量,以及不同业务需求传输的公平性。
为更好地理解本申请实施例提供的通信方法,下面将结合更多附图对本申请实施例提供的通信方法的技术方案进行说明。
为便于清楚描述本申请的技术方案,本申请将通过多个实施例对本申请的技术方案进行阐述,具体参见下文。本申请中,除特殊说明外,各个实施例或实现方式之间相同或相似的部分可以互相参考。在本申请中各个实施例、以及各实施例中的各个实施方式/实施方法/实现方法中,如果没有特殊说明以及逻辑冲突,不同的实施例之间、以及各实施例中的各个实施方式/实施方法/实现方法之间的术语和/或描述具有一致性、且可以相互引用,不同的实施例、以及各实施例中的各个实施方式/实施方法/实现方法中的技术特征根据其内在的逻辑关系可以组合形成新的实施例、实施方式、实施方法、或实现方法。以下所述的本申请实施方式并不构成对本申请保护范围的限定。
请参见图5,图5是本申请实施例提供的一种通信方法的流程示意图,该方法可应用于终端设备,该终端设备可以为前述图1中的任一终端或应用于该终端的模块;或者,该终端设备可以为前述图2中的任一UE,如Relay UE或Remote UE;或者,该终端设备可以为前述图3中的任一UE,如Source UE、Relay UE或Target UE。也即是说,上述图1、图2以及图3中终端设备可以用于支持并执行图5中所示的方法流程步骤S500-步骤S501,其中,步骤S500-步骤S501包括以下:
步骤S500:UE获取第一侧行链路数据无线链路承载SL DRB配置。
具体地,UE可以通过SIB消息获取到第一SL DRB配置,或者基于预配置消息获取到第一SL DRB配置,或者RRC专用信令获取到第一SL DRB配置,其中,第一SL DRB配置可以包括CAPC配置,也可以没有CAPC配置,在此不作具体限定。
步骤S501:UE根据所述第一SL DRB配置所关联的一个或多个服务质量流,确定SL DRB的CAPC。
具体地,UE可以根据第一SL DRB所关联的一个或多个QoS流,确定SL DRB的CAPC,也即是说,UE可以根据被映射到SL DRB上的QoS流,确定SL DRB的CAPC,其中,SL DRB是根据第一SL DRB配置建立的。
在一种可能的实现方式中,SL DRB的数量为1,也即是说,UE可以根据所关联的一个或多个QoS流,确定该1个SL DRB的CAPC。具体地,UE可以先确定出第一SL DRB配置关联的一个或多个QoS流分别对应
的一个或多个CAPC,并将这一个或多个CAPC中的目标CAPC确定为SL DRB的CAPC。需要说明的是,在确定出该1个SL DRB的CAPC后,这一个或多个QoS流也都可以利用该SL DRB进行传输。因此,UE通过根据多个QoS flow确定SL DRB对应的CAPC,减少例如当网络没有配置SL DRB的CAPC或者配置的CAPC不合适时,影响SL-U的通信质量和公平性的问题,达到保证SL-U的通信质量,以及不同业务需求传输的公平性的目的。
可选地,目标CAPC可以包括以下CAPC中的一种或多种:
(1)所述第一SL DRB配置所关联的一个或多个服务质量流中包延时预算最小或最大的服务质量流的CAPC。例如,关联的QoS流的数量为3(包括f1、f2和f3),f1的包延时预算最小,f3的包延时预算最大,则可以将f1或者f3对应的CAPC确定为SL DRB的CAPC。
(2)所述第一SL DRB配置所关联的一个或多个服务质量流中默认优先级最小或最大的服务质量流的CAPC;如上述例子,若f1的默认优先级最小,f3的默认优先级最大,则可以将f1或者f3对应的CAPC确定为SL DRB的CAPC。
(3)所述第一SL DRB配置所关联的一个或多个服务质量流中优先级最小或最大的服务质量流的CAPC;如上述例子,若f1的优先级最小,f3的优先级最大,则可以将f1或者f3对应的CAPC确定为SL DRB的CAPC。
(4)所述第一SL DRB配置所关联的一个或多个服务质量流中包错误率最小或最大的服务质量流的CAPC;如上述例子,若f1的包错误率最小,f3的包错误率最大,则可以将f1或者f3对应的CAPC确定为SL DRB的CAPC。
(5)所述第一SL DRB配置所关联的一个或多个服务质量流对应的一个或多个CAPC中的最大CAPC值、最小CAPC值或CAPC平均值;如上述例子,若f1的CAPC为1,f2的CAPC为2,f3的CAPC为3,则可以将f1或者f3对应的CAPC(1或3)或者CAPC平均值(2)确定为SL DRB的CAPC。
(6)所述第一SL DRB配置所关联的一个或多个服务质量流对应的一个或多个CAPC中对应服务质量流数量最多的CAPC。如上述例子,若f1的CAPC为1,f2的CAPC为1,f3的CAPC为3,则可以将f1和f2对应的CAPC(1)确定为SL DRB的CAPC。
可选地,各个QoS flow对应的CAPC可以根据以下方式进行确定,包括:
(1)如果QoS flow是standardized PQI对应的QoS flow,则QoS flow对应的CAPC为该standardized PQI对应的CAPC(即可以根据standardized PQI和CAPC的映射表进行确定)。
(2)如果QoS flow是non-standardized PQI对应的QoS flow,可以通过以下方式确定QoS flow对应的CAPC,包括:
1)如果non-standardized PQI的priority level(优先级)属于预设范围(或者该QoS flow是关键任务Mission Critical的QoS flow),则可以将该QoS flow的CAPC确定为1或2。示例性的,如果non-standardized PQI的priority level属于1或2(也就是预设范围是1或2),则可以将该QoS flow的CAPC确定为1或2。或
2)确定和该QoS flow的PDB最接近的standardized PQI的CAPC为该QoS flow的CAPC。其中,PDB最接近的standardized PQI指的是该standardized PQI的PDB和该QoS flow的PDB差值最小。可理解地,也可以将与该QoS flow的默认优先级、优先级或者包错误率等特征最接近的standardized PQI的CAPC为该QoS flow的CAPC。
可选地,UE可以先尝试通过1)的方式确定QoS flow的CAPC,当UE确定通过1)的方式无法确定出该QoS flow的CAPC时,可以再通过2)的方式确定该QoS flow的CAPC。
需要说明的是,目标CAPC可以由UE根据上述各种方式的组合确定,目标CAPC也可以由UE根据第一SL DRB配置所关联的一个或多个服务质量流的其它服务特征(如资源类型、默认最大数据突发量和默认平均窗口等)或者根据其它规则(如根据网络情况自行配置决定)进行确定。可理解地,上述例子中QoS流的数量也可以为3以外的其它取值,在此不作具体限定。
在一种可能的实现方式中,SL DRB的数量为多个(即至少2个),其中,该至少2个SL DRB中每个SL DRB对应的CAPC不同。具体地,UE可以根据第一SL DRB配置所关联的一个或多个QoS流对应的CAPC数量确定该至少2个SL DRB的数量,并建立所述至少2个SL DRB。其中,该至少2个SL DRB的数量可以大于或等于第一SL DRB配置所关联的一个或多个QoS流对应的CAPC数量,且该至少2个SL DRB中的部分或全部SL DRB的CAPC分别与一个或多个服务质量流的CAPC对应。例如,一个或多个QoS流对应的CAPC数量为2(QoS流的数量不一定也为2),其中一个CAPC值为1,另一个CAPC值为2,则该至少2个SL DRB的数量可以为2,其中一个SL DRB的CAPC值为1,另一个SL DRB的CAPC值为2;可理解地,该至少2个SL DRB
的数量也可以为3或者4(甚至更多),只要这些SL DRB中包括1个CAPC值为1的SL DRB和1个CAPC值为2的SL DRB即可,其它的SL DRB的CAPC值可以为1或者2,或者其它值,在此不作具体限定。可选地,该至少2个SL DRB对应的CAPC不同,除了CAPC外的其余参数可以都相同(其中,逻辑信道标识LCID也可以不同)。需要说明的是,上述多个QoS流可以是同一个目标(destination)下的QoS流。还需要说明的是,如果UE基于同一个SL DRB配置建立的多个CAPC值相同的SL DRB,也可以通过不同的逻辑信道标识(LCID)对多个CAPC值相同的SL DRB进行区分,在此不另外展开说明。因此,UE根据SL DRB配置建立多个SL DRB,使得每个SL DRB中实际传输的都是CAPC相对应的QoS flow,保证SL-U的通信质量,以及不同业务需求传输的公平性。
在一种可能的实现方式中,本申请实施例提供的通信方法的流程,除了上述步骤S500-步骤S501之外,还可以包括步骤S502。步骤S502:确定所述第一SL DRB配置满足第一预设条件。具体地,UE可以在确定SL DRB的CAPC之前,先确定所述第一SL DRB配置是否满足第一预设条件,在确定所述第一SL DRB配置满足第一预设条件后,UE可以根据第一SL DRB所关联的一个或多个QoS流,确定SL DRB的CAPC。其中,第一预设条件可以包括以下条件中的一种或多种:
(1)所述第一SL DRB配置为缺省default SL DRB配置;
(2)所述第一SL DRB配置通过系统信息块SIB或预配置消息的方式获取;
(3)所述第一SL DRB配置未提供对应的CAPC配置;或
(4)所述第一SL DRB配置提供的CAPC配置不合适。(可理解地,(3)和(4)不会同时出现,所述第一SL DRB配置不会同时满足(3)和(4)的情况。)
进一步地,所述第一SL DRB配置提供的CAPC配置不合适是指:1)所述第一SL DRB配置所关联的多个服务质量流对应的CAPC不同;2)所述第一SL DRB配置所关联的多个服务质量流对应的CAPC之间的最大差值大于或等于第一阈值;例如,例如第一阈值为2,第一SL DRB配置关联的多个QoS flow对应的CAPC包括CAPC值为1和CAPC值为3,则可以认为满足本条件,即第一SL DRB配置提供的CAPC配置不合适,进而UE可以确定所述第一SL DRB配置满足第一预设条件。3)所述第一SL DRB配置所关联的多个服务质量流的数量大于或等于第二阈值。即当所述第一SL DRB配置所关联的多个服务质量流超过一定数量(例如5,即第二阈值为5)时,UE也可以直接确定所述第一SL DRB配置满足第一预设条件。或者4)所述第一SL DRB配置所关联的多个服务质量流对应的CAPC中的最小值大于所述第一SL DRB配置提供的CAPC值(或者说,所述第一SL DRB配置所关联的多个服务质量流对应的CAPC中的最高优先级低于或等于所述第一SL DRB配置提供的CAPC的优先级)。需要说明的是,上述第一阈值和第二阈值也可以取其它值,其中,第一阈值或第二阈值可以是协议预定义的、网络配置的(例如基站通过RRC专用信令配置或SIB消息配置)、预配置的、或者其它UE配置的,在此不作具体限定。
可选地,当所述第一SL DRB配置未提供对应的CAPC配置或所述第一SL DRB配置提供的CAPC配置不合适时,UE向接入网设备(基站)发送指示消息,所述指示消息用于指示所述第一SL DRB配置未提供对应的CAPC配置或所述第一SL DRB配置提供的CAPC配置不合适;接收所述接入网设备发送的第二SL DRB配置,所述第二SL DRB配置与所述第一SL DRB配置不同。或者,当所述第一SL DRB配置未提供对应的CAPC配置或所述第一SL DRB配置提供的CAPC配置不合适时,若所述终端设备处于无线资源控制RRC空闲态或RRC非激活态,进入RRC连接态(例如,触发执行RRC建立(RRC step)过程或RRC恢复(RRC resume)过程);接收所述接入网设备发送的第二SL DRB配置,所述第二SL DRB配置与所述第一SL DRB配置不同。其中,UE发送的指示消息可以是UE进入RRC连接态或者处于mode1模式下通过SUI消息发送的,进一步地,该指示消息也可以包括UE针对SL DRB确定出的CAPC。需要说明的是,所述第二SL DRB配置与所述第一SL DRB配置不同,可以包括仅CAPC配置不同但其它配置都相同的情况,以及CAPC配置不同且其它配置也不相同的情况,在此不作具体限定。
需要说明的是,第一SL DRB配置关联的多个QoS flow可以理解为映射到SL DRB上的所有QoS flow,也可以理解为映射到SL DRB上的所有QoS flow中实际需要传输的多个QoS flow,其中SL DRB是根据所述第一SL DRB配置建立的SL DRB;或者,可以理解为当前第一SL DRB配置关联的多个QoS flow中有数据(即有传输需求)的QoS flow。可选的,多个QoS flow可以是同一个destination下的多个QoS flow。换句话说,所述第一SL DRB配置关联的多个QoS flow的数量可能大于在SL DRB上实际传输的QoS flow的数量,例如,所述第一SL DRB配置关联了QoS flow1、QoS flow2和QoS flow3,但是在SL DRB上只有QoS flow1和QoS flow2需要传输,此时,该多个QoS flow可以指的是QoS flow1和QoS flow2,而不包括QoS flow3,在此不作具体限定。
在一种可能实现方式中,本申请实施例提供的通信方法的流程,除了上述步骤S500-步骤S501之外,还可以包括步骤S503和步骤S504。步骤S503:获取多个default SL DRB配置。步骤S504:根据所述多个default SL DRB配置建立多个default SL DRB。其中,所述多个default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同。即上述步骤S500-步骤S501可以与本申请实施例提供的另一种通信方法进行组合,关于另一种通信方法的描述可以参见以下图6的相关描述,在此不另外展开。
请参见图6,图6是本申请实施例提供的另一种通信方法的流程示意图,该方法可应用于终端设备,该终端设备与图5所应用的终端设备含义相同。图6中所示的方法流程步骤S600-步骤S601,其中,步骤S600-步骤S601包括以下:
步骤S600:UE获取多个default SL DRB配置。
具体地,多个default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同,例如,该多个default SL DRB配置包括第一default SL DRB配置、第二default SL DRB配置和第三default SL DRB配置,其中,第一default SL DRB配置关联的CAPC为1,第二default SL DRB配置关联的CAPC为2,第三default SL DRB配置关联的CAPC为3。又例如,该多个default SL DRB配置包括第一default SL DRB配置、第二default SL DRB配置、第三default SL DRB配置和第四default SL DRB配置,其中,第一default SL DRB配置关联的CAPC为1,第二default SL DRB配置关联的CAPC为2,第三default SL DRB配置关联的CAPC为3,第四default SL DRB配置关联的CAPC为4。需要说明的是,该多个default SL DRB配置可以是UE通过SIB消息、预配置消息或者RRC专用信令获取到的,在此不作具体限定。
可理解地,该多个default SL DRB配置也可以包括更多或者更少的不同CAPC配置的default SL DRB配置,在此不作具体限定。
可选地,该多个default SL DRB配置针对的可以是同一个通信类型。其中,通信类型可以包括单播、组播、广播中的一种或多种。
步骤S601:UE根据所述多个default SL DRB配置建立多个default SL DRB。
具体地,UE可以根据该多个default SL DRB配置中的每个default SL DRB配置分别建立一个或多个default SL DRB。为方便理解,以UE根据每个default SL DRB配置分别建立一个default SL DRB为例,当该多个default SL DRB配置关联的多个不同的CAPC分别为1、2和3时,UE可以建立3个对应的default SL DRB,这3个default SL DRB的CAPC值分别为1、2和3,即与该多个default SL DRB配置的CAPC配置对应。
在一种可能的实现方式中,除图6中所示的步骤S600-步骤S601之外,此通信方法还可以包括步骤S602,步骤S602:当待传输的服务质量流未配置或未存储对应的SL DRB的映射规则时,将所述待传输的服务质量流映射到所述多个default SL DRB中的目标default SL DRB。其中,所述目标default SL DRB的CAPC与所述待传输的服务质量流的CAPC相同。示例性的,当default SL DRB对应的CAPC为1,如果QoS flow没有配置(或存储)对应的SL DRB的映射规则且该QoS flow对应的CAPC为1,则QoS flow可以被映射到该default SL DRB。可理解地,针对其它CAPC的default SL DRB,QoS flow映射到default SL DRB的方式也是类似的。基于此,此方法可以保证在同一个default SL DRB上传输的多个QoS flow对应的CAPC都是相同的,从而保证SL-U的通信质量,以及不同业务需求传输的公平性。需要说明的是,SL DRB的映射规则指的可以是显示配置的QoS flow到SL DRB的映射规则。还需要说明的是,UE也可以基于同一个default SL DRB配置建立的多个CAPC值相同的default SL DRB,多个CAPC值相同的default SL DRB之间可以通过不同的逻辑信道标识(LCID)进行区分。
综上,对比于UE使用基站下发或者预配置的SL DRB配置对多个QoS流进行传输的方案,即使用基站下发或预配置SL DRB的CAPC配置,本申请实施例中,UE可以在获取到SL DRB配置后,根据SL DRB配置关联的一个或多个QoS流,确定根据该SL DRB配置建立的SL DRB的CAPC,其中,建立的SL DRB的数量可以是1个,也可以是多个,UE根据一个或多个QoS流,合理的配置或者合理的确定SL DRB对应的CAPC,可以减少例如当网络没有配置SL DRB的CAPC或者配置的CAPC不合适时,影响SL-U的通信质量和公平性的问题,达到保证SL-U的通信质量,以及不同业务需求传输的公平性的目的。另外,针对使用default SL DRB的场景,终端设备可以在获取到多个不同的default SL DRB配置后,对应建立多个default SL DRB,其中,多个不同的default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同,也即是说,终端设备根据配置对应建立的多个default SL DRB中每个default SL DRB的CAPC不同,从而可以保证同一个default SL DRB上传输的QoS flow对应的CAPC都是相同的,以此保证SL-U的通信质量,以及不同业务需求传输的公平性。因此,本申请实施例可以保证SL-U的性能和公平性。因此,本申请实施例可以保证SL-U的性能和公平性。
需要说明的是,上述实施例中所述的CAPC配置也可以等价于逻辑信道优先级,即UE可以根据关联的业务数据确定逻辑信道信息优先级的方案,也应涵盖在本申请的保护范围之内。
上述详细阐述了本申请实施例的方法,下面提供本申请实施例的几种相关装置。
可以理解的是,为了实现上述实施例中功能,通信装置包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本申请中所公开的实施例描述的各示例的单元及方法步骤,本申请能够以硬件或硬件和计算机软件相结合的形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用场景和设计约束条件。
请参见图7,图7是本申请实施例提供的通信装置的一种结构示意图,该通信装置可以用于实现上述方法实施例中UE或接入网设备的功能,因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中,该通信装置可以是如图1所示的终端120a-120j中的一个,还可以是应用于终端的模块(如芯片),也可以是如图1所示的无线接入网设备110a或110b。
如图7所示,该通信装置可以包括收发单元10和处理单元20。该通信装置可用于实现上述图5、图6中所示的方法实施例中UE或接入网设备(基站)的功能。
当该通信装置用于实现图5所示的方法实施例中UE的功能时:收发单元10可用于获取第一侧行链路数据无线链路承载SL DRB配置;处理单元20可用于根据该第一SL DRB配置所关联的一个或多个服务质量流,确定SL DRB的CAPC,该SL DRB为根据该第一SL DRB配置建立的SL DRB。
在一种可能的实现方式中,所述SL DRB的数量为1个。
在一种可能的实现方式中,所述SL DRB的数量为至少2个,所述至少2个SL DRB中每个SL DRB的CAPC不同。
在一种可能的实现方式中,处理单元20具体用于:将所述第一SL DRB配置所关联的一个或多个服务质量流对应的一个或多个CAPC中的目标CAPC,确定为所述SL DRB的CAPC。
在一种可能的实现方式中,所述目标CAPC包括以下CAPC中的任意一种或多种:
所述第一SL DRB配置所关联的一个或多个服务质量流中包延时预算最小或最大的服务质量流的CAPC;
所述第一SL DRB配置所关联的一个或多个服务质量流中默认优先级最小或最大的服务质量流的CAPC;
所述第一SL DRB配置所关联的一个或多个服务质量流中优先级最小或最大的服务质量流的CAPC;
所述第一SL DRB配置所关联的一个或多个服务质量流中包错误率最小或最大的服务质量流的CAPC;
所述第一SL DRB配置所关联的一个或多个服务质量流对应的一个或多个CAPC中的最大CAPC值、最小CAPC值或CAPC平均值;或
所述第一SL DRB配置所关联的一个或多个服务质量流对应的一个或多个CAPC中对应服务质量流数量最多的CAPC。
在一种可能的实现方式中,处理单元20具体用于:根据所述第一SL DRB配置所关联的一个或多个服务质量流对应的不同的CAPC数量确定所述至少2个SL DRB的数量,并建立所述至少2个SL DRB;所述至少2个SL DRB的CAPC分别与所述一个或多个服务质量流的CAPC对应。
在一种可能的实现方式中,处理单元20还用于:确定所述第一SL DRB配置满足第一预设条件;所述第一预设条件包括以下条件中的一种或多种:
所述第一SL DRB配置为缺省default SL DRB配置;
所述第一SL DRB配置通过系统信息块SIB或预配置消息的方式获取;
所述第一SL DRB配置未提供对应的CAPC配置;或
所述第一SL DRB配置提供的CAPC配置不合适。
在一种可能的实现方式中,所述第一SL DRB配置提供的CAPC配置不合适包括以下的一种或多种:
所述第一SL DRB配置所关联的多个服务质量流对应的CAPC不同;
所述第一SL DRB配置所关联的多个服务质量流对应的CAPC之间的最大差值大于或等于第一阈值;
所述第一SL DRB配置所关联的多个服务质量流的数量大于或等于第二阈值;或
所述第一SL DRB配置所关联的多个服务质量流对应的CAPC中的最小值大于所述第一SL DRB配置提供的CAPC值。
在一种可能的实现方式中,收发单元10还用于:当所述第一SL DRB配置未提供对应的CAPC配置或所
述第一SL DRB配置提供的CAPC配置不合适时,向接入网设备发送指示消息,所述指示消息用于指示所述第一SL DRB配置未提供对应的CAPC配置或所述第一SL DRB配置提供的CAPC配置不合适;接收所述接入网设备发送的第二SL DRB配置,所述第二SL DRB配置与所述第一SL DRB配置不同;
或者当所述第一SL DRB配置未提供对应的CAPC配置或所述第一SL DRB配置提供的CAPC配置不合适时,若所述终端设备处于无线资源控制RRC空闲态或RRC非激活态,进入RRC连接态;接收所述接入网设备发送的第二SL DRB配置,所述第二SL DRB配置与所述第一SL DRB配置不同。
在一种可能的实现方式中,所述第一SL DRB配置所关联的一个或多个服务质量流包括非标准的PC5服务质量标识对应的服务质量流,处理单元20还用于:根据所述非标准的PC5服务质量标识对应的服务质量流的特征参数,确定所述非标准的PC5服务质量标识对应的服务质量流的CAPC;所述特征参数用于表示非标准的PC5服务质量标识对应的服务质量流的服务质量特性,所述特征参数包括包延时预算、默认优先级、优先级和包错误率中的一种或多种。
在一种可能的实现方式中,收发单元10还用于:获取多个default SL DRB配置;所述多个default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同;
处理单元20还用于:根据所述多个default SL DRB配置建立多个default SL DRB。
在一种可能的实现方式中,处理单元20具体还用于:当待传输的服务质量流未配置或未存储对应的SL DRB的映射规则时,将所述待传输的服务质量流映射到所述多个default SL DRB中的目标default SL DRB,所述目标default SL DRB的CAPC与所述待传输的服务质量流的CAPC相同。
当该通信装置用于实现图5所示的方法实施例中接入网设备(基站)的功能时:收发单元10用于:接收终端设备发送的指示消息,和/或向所述终端设备发送第二SL DRB配置。处理单元20可用于确定和生成该第二SL DRB配置。
在一种可能的实现方式中,收发单元10还用于:发送多个default SL DRB配置;所述多个default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同。
当该通信装置用于实现图6所示的方法实施例中UE的功能时:收发单元10用于:获取多个default SL DRB配置;所述多个default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同;处理单元20用于:根据所述多个default SL DRB配置建立多个default SL DRB。
在一种可能的实现方式中,处理单元20还用于:当待传输的服务质量流未配置或未存储对应的SL DRB的映射规则时,将所述待传输的服务质量流映射到所述多个default SL DRB中的目标default SL DRB,所述目标default SL DRB的CAPC与所述待传输的服务质量流的CAPC相同。
当该通信装置用于实现图6所示的方法实施例中接入网设备(基站)的功能时:收发单元10用于:发送多个default SL DRB配置;所述多个default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同;处理单元20可用于确定和生成该多个default SL DRB配置。
请参见图8,图8是本申请实施例提供的通信装置的另一种结构示意图。如图8所示,该通信装置包括处理器810和接口电路820。处理器810和接口电路820之间相互耦合。可以理解的是,接口电路820可以为收发器或输入输出接口。可选的,该通信装置还可以包括存储器830,用于存储处理器810执行的指令或存储处理器810运行指令所需要的输入数据或存储处理器810运行指令后产生的数据。
当通信装置用于实现图5或图6所示的方法时,处理器810用于实现上述处理单元20的功能,接口电路820用于实现上述收发单元10的功能。
当上述通信装置为应用于终端的芯片时,该终端芯片实现上述方法实施例中UE或接入网设备(基站)的功能。该终端芯片从终端中的其它模块(如射频模块或天线)接收信息,该信息是其他设备发送给这个终端的;或者,该终端芯片向终端中的其它模块(如射频模块或天线)发送信息,该信息是这个终端发送给其他设备的。
可以理解的是,本申请的实施例中的处理器810可以是中央处理单元(Central Processing Unit,CPU),还可以是其它通用处理器、数字信号处理器(Digital Signal Processor,DSP)、专用集成电路(Application Specific Integrated Circuit,ASIC)、现场可编程门阵列(Field Programmable Gate Array,FPGA)或者其它可编程逻辑器件、晶体管逻辑器件,硬件部件或者其任意组合。通用处理器可以是微处理器,也可以是任何常规的处理器。
本申请实施例还提供一种计算机可读存储介质,该计算机可读存储介质中存储有计算机程序代码,当上述处理器执行该计算机程序代码时,使得计算机执行前述任一实施例中的方法。
本申请实施例还提供一种终端设备,该终端设备可以以芯片的产品形态存在,该终端设备中包括处理器,处理器被配置为支持该终端设备实现前述任一实施例中的方法中相应的功能。该终端设备还可以包括存储器,存储器用于与处理器耦合,其保存该终端设备必要的程序指令和数据。该终端设备还可以包括通信接口,用于该终端设备与其他设备或通信网络通信。
本申请实施例还提供一种计算机程序产品,当该计算机程序产品在计算机上运行时,使得计算机执行前述任一实施例中的方法。
本申请实施例提供了一种芯片系统,该芯片系统包括处理器,用于支持设备实现上述第一方面所涉及的功能,例如,生成或处理上述块指令的寄存器参数传递方法中所涉及的信息。在一种可能的设计中,所述芯片系统还包括存储器,所述存储器,用于保存设备必要的程序指令和数据。该芯片系统,可以由芯片构成,也可以包含芯片和其他分立器件。
在上述实施例中,对各个实施例的描述都各有侧重,某个实施例中没有详述的部分,可以参见其他实施例的相关描述。
需要说明的是,对于前述的各方法实施例,为了简单描述,故将其都表述为一系列的动作组合,但是本领域技术人员应该知悉,本申请并不受所描述的动作顺序的限制,因为依据本申请,某些步骤可能可以采用其他顺序或者同时进行。其次,本领域技术人员也应该知悉,说明书中所描述的实施例均属于优选实施例,所涉及的动作和模块并不一定是本申请所必须的。
在本申请所提供的几个实施例中,应该理解到,所揭露的装置,可通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如上述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性或其它的形式。
上述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外,在本申请各实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
上述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以为个人计算机、服务端或者网络设备等,具体可以是计算机设备中的处理器)执行本申请各个实施例上述方法的全部或部分步骤。其中,而前述的存储介质可包括:U盘、移动硬盘、磁碟、光盘、只读存储器(Read-OnlyMemory,缩写:ROM)或者随机存取存储器(RandomAccessMemory,缩写:RAM)等各种可以存储程序代码的介质。
以上所述,以上实施例仅用以说明本申请的技术方案,而非对其限制;尽管参照前述实施例对本申请进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。
Claims (20)
- 一种通信方法,其特征在于,应用于终端设备,所述方法包括:获取第一侧行链路数据无线链路承载SL DRB配置;根据所述第一SL DRB配置所关联的一个或多个服务质量流,确定SL DRB的CAPC,所述SL DRB为根据所述第一SL DRB配置建立的SL DRB。
- 如权利要求1所述的方法,其特征在于,所述SL DRB的数量为1个。
- 如权利要求1所述的方法,其特征在于,所述SL DRB的数量为至少2个,所述至少2个SL DRB中每个SL DRB的CAPC不同。
- 如权利要求2所述的方法,其特征在于,所述方法,还包括:将所述第一SL DRB配置所关联的一个或多个服务质量流对应的一个或多个CAPC中的目标CAPC,确定为所述SL DRB的CAPC。
- 如权利要求4所述的方法,其特征在于,所述目标CAPC包括以下CAPC中的任意一种或多种:所述第一SL DRB配置所关联的一个或多个服务质量流中包延时预算最小或最大的服务质量流的CAPC;所述第一SL DRB配置所关联的一个或多个服务质量流中默认优先级最小或最大的服务质量流的CAPC;所述第一SL DRB配置所关联的一个或多个服务质量流中优先级最小或最大的服务质量流的CAPC;所述第一SL DRB配置所关联的一个或多个服务质量流中包错误率最小或最大的服务质量流的CAPC;所述第一SL DRB配置所关联的一个或多个服务质量流对应的一个或多个CAPC中的最大CAPC值、最小CAPC值或CAPC平均值;或所述第一SL DRB配置所关联的一个或多个服务质量流对应的一个或多个CAPC中对应服务质量流数量最多的CAPC。
- 如权利要求3所述的方法,其特征在于,所述方法,还包括:根据所述第一SL DRB配置所关联的一个或多个服务质量流对应的不同的CAPC数量确定所述至少2个SL DRB的数量,并建立所述至少2个SL DRB;所述至少2个SL DRB的CAPC分别与所述一个或多个服务质量流的CAPC对应。
- 如权利要求1-6中任一项所述的方法,其特征在于,所述方法,还包括:确定所述第一SL DRB配置满足第一预设条件;所述第一预设条件包括以下条件中的一种或多种:所述第一SL DRB配置为缺省default SL DRB配置;所述第一SL DRB配置通过系统信息块SIB或预配置消息的方式获取;所述第一SL DRB配置未提供对应的CAPC配置;或所述第一SL DRB配置提供的CAPC配置不合适。
- 如权利要求7所述的方法,其特征在于,所述第一SL DRB配置提供的CAPC配置不合适包括以下的一种或多种:所述第一SL DRB配置所关联的多个服务质量流对应的CAPC不同;所述第一SL DRB配置所关联的多个服务质量流对应的CAPC之间的最大差值大于或等于第一阈值;所述第一SL DRB配置所关联的多个服务质量流的数量大于或等于第二阈值;或所述第一SL DRB配置所关联的多个服务质量流对应的CAPC中的最小值大于所述第一SL DRB配置提供的CAPC值。
- 如权利要求7-8中任一项所述的方法,其特征在于,所述方法,还包括:当所述第一SL DRB配置未提供对应的CAPC配置或所述第一SL DRB配置提供的CAPC配置不合适时,向接入网设备发送指示消息,所述指示消息用于指示所述第一SL DRB配置未提供对应的CAPC配置或所述第一SL DRB配置提供的CAPC配置不合适;接收所述接入网设备发送的第二SL DRB配置,所述第二SL DRB配置与所述第一SL DRB配置不同;或者当所述第一SL DRB配置未提供对应的CAPC配置或所述第一SL DRB配置提供的CAPC配置不合适时,若所述终端设备处于无线资源控制RRC空闲态或RRC非激活态,进入RRC连接态;接收所述接入网设备发送的第二SL DRB配置,所述第二SL DRB配置与所述第一SL DRB配置不同。
- 如权利要求1-9中任一项所述的方法,其特征在于,所述第一SL DRB配置所关联的一个或多个服务质量流包括非标准的PC5服务质量标识对应的服务质量流,所述方法,还包括:根据所述非标准的PC5服务质量标识对应的服务质量流的特征参数,确定所述非标准的PC5服务质量标识对应的服务质量流的CAPC;所述特征参数用于表示非标准的PC5服务质量标识对应的服务质量流的服务质量特性,所述特征参数包括包延时预算、默认优先级、优先级和包错误率中的一种或多种。
- 如权利要求1-10中任一项所述的方法,其特征在于,所述第一SL DRB配置所关联的一个或多个服务质量流包括非标准的PC5服务质量标识对应的服务质量流,所述方法,还包括:将与所述非标准的PC5服务质量标识对应的服务质量流的包延迟预算最接近的标准的PC5服务质量标识对应的CAPC,确定为所述非标准的PC5服务质量标识对应的服务质量流的CAPC。
- 如权利要求1-11中任一项所述的方法,其特征在于,所述方法,还包括:获取多个default SL DRB配置;所述多个default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同;根据所述多个default SL DRB配置建立多个default SL DRB。
- 如权利要求12所述的方法,其特征在于,所述方法,还包括:当待传输的服务质量流未配置或未存储对应的SL DRB的映射规则时,将所述待传输的服务质量流映射到所述多个default SL DRB中的目标default SL DRB,所述目标default SL DRB的CAPC与所述待传输的服务质量流的CAPC相同。
- 一种通信方法,其特征在于,应用于接入网设备,所述方法包括:接收终端设备发送的指示消息,和/或向所述终端设备发送第二SL DRB配置。
- 一种通信方法,其特征在于,应用于终端设备,所述方法包括:获取多个default SL DRB配置;所述多个default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同;根据所述多个default SL DRB配置建立多个default SL DRB。
- 如权利要求15所述的方法,其特征在于,所述方法,还包括:当待传输的服务质量流未配置或未存储对应的SL DRB的映射规则时,将所述待传输的服务质量流映射到所述多个default SL DRB中的目标default SL DRB,所述目标default SL DRB的CAPC与所述待传输的服务质量流的CAPC相同。
- 一种通信方法,其特征在于,应用于接入网设备,所述方法包括:发送多个default SL DRB配置;所述多个default SL DRB配置中每个default SL DRB配置关联的CAPC配置不同。
- 一种通信装置,其特征在于,包括处理器和接口电路,所述接口电路用于接收来自其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给其它通信装置,所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1-17任一项所述的方法。
- 一种计算机可读存储介质,其特征在于,所述存储介质中存储有计算机程序或指令,当所述计算机程序或指令被通信装置执行时,实现如权利要求1-17中任一项所述的方法。
- 一种计算机程序,其特征在于,所述计算机程序包括指令,当所述计算机程序被通信装置执行时,实现如权利要求1-17中任一项所述的方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202211372337.6A CN117998652A (zh) | 2022-11-03 | 2022-11-03 | 一种通信方法和相关设备 |
CN202211372337.6 | 2022-11-03 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2024093825A1 true WO2024093825A1 (zh) | 2024-05-10 |
Family
ID=90901654
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2023/127148 WO2024093825A1 (zh) | 2022-11-03 | 2023-10-27 | 一种通信方法和相关设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN117998652A (zh) |
WO (1) | WO2024093825A1 (zh) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110831075A (zh) * | 2018-08-10 | 2020-02-21 | 中兴通讯股份有限公司 | 数据传输方法及装置,业务切换方法及装置 |
CN114303412A (zh) * | 2019-08-23 | 2022-04-08 | 高通股份有限公司 | 用于nr-u数据承载的信道接入优先级 |
US11490448B1 (en) * | 2021-07-09 | 2022-11-01 | Asustek Computer Inc. | Method and apparatus for radio bearer configuration to support UE-to-network relaying in a wireless communication system |
-
2022
- 2022-11-03 CN CN202211372337.6A patent/CN117998652A/zh active Pending
-
2023
- 2023-10-27 WO PCT/CN2023/127148 patent/WO2024093825A1/zh unknown
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110831075A (zh) * | 2018-08-10 | 2020-02-21 | 中兴通讯股份有限公司 | 数据传输方法及装置,业务切换方法及装置 |
CN114303412A (zh) * | 2019-08-23 | 2022-04-08 | 高通股份有限公司 | 用于nr-u数据承载的信道接入优先级 |
US11490448B1 (en) * | 2021-07-09 | 2022-11-01 | Asustek Computer Inc. | Method and apparatus for radio bearer configuration to support UE-to-network relaying in a wireless communication system |
Non-Patent Citations (1)
Title |
---|
OPPO: "Summary of [AT119bis-e][503][V2X/SL] CAPC (OPPO)", 3GPP DRAFT; R2-2210934, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. E-meeting; 20221001, 21 October 2022 (2022-10-21), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052264212 * |
Also Published As
Publication number | Publication date |
---|---|
CN117998652A (zh) | 2024-05-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210410129A1 (en) | L2 procedures for unicast and/or multicast link establishment and maintenance | |
TWI710276B (zh) | 用於d2d通信的方法、d2d設備、和基站 | |
CN115297555A (zh) | 无线通信系统的中继 | |
JP7277002B2 (ja) | 通信方法及び装置 | |
CN113940130B (zh) | 边链路调度请求的触发方法、装置和系统 | |
KR20130113485A (ko) | 무선 다이렉트 링크 동작을 위한 방법 및 장치 | |
CN113079712B (zh) | 双向侧链路无线电链路控制承载 | |
JP7342936B2 (ja) | 通信方法、装置及び通信システム | |
US20170118770A1 (en) | Methods and apparatus for selecting enhanced distributed channel access parameters for multi-user transmissions | |
US20230422085A1 (en) | Managing a wireless local area network (wlan) to support a mobile communication network service | |
US20230284206A1 (en) | Sidelink discovery associated with nr relays | |
WO2021036910A1 (zh) | 数据传输方法及装置 | |
WO2016083659A1 (en) | Managing operation during absence in wireless network | |
WO2024093825A1 (zh) | 一种通信方法和相关设备 | |
CN116349259A (zh) | 通信方法及装置 | |
CN116830697A (zh) | 一种cg资源处理方法、终端设备及网络设备 | |
WO2024032456A1 (zh) | 侧行链路的信息交互方法、装置及可读存储介质 | |
WO2024032285A1 (zh) | 一种通信方法及装置 | |
US10575316B2 (en) | Prioritizing radio resources between overlapping wireless access point nodes | |
US20240224332A1 (en) | Communication method and terminal device | |
WO2024065667A1 (zh) | 用于侧行通信的方法以及通信设备 | |
US20240023179A1 (en) | Radios with simultaneous transmit and receive | |
WO2021235410A1 (ja) | 基地局及びその制御方法 | |
WO2024060187A1 (zh) | 用于侧行通信方法以及终端设备 | |
WO2024094811A1 (en) | Technique for handling a sidelink between radio devices |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 23884757 Country of ref document: EP Kind code of ref document: A1 |