WO2022151262A1

WO2022151262A1 - Discontinuous reception configuration method, communication device and communication system

Info

Publication number: WO2022151262A1
Application number: PCT/CN2021/071917
Authority: WO
Inventors: 李翔宇; 彭文杰
Original assignee: 华为技术有限公司
Priority date: 2021-01-14
Filing date: 2021-01-14
Publication date: 2022-07-21

Abstract

The present application provides a discontinuous reception (DRX) configuration method, a communication device and a communication system. Said method comprises: determining a target QoS parameter on the basis of a plurality of groups of QoS parameters corresponding to a plurality of QoS flows included in a first target; determining a target DRX configuration on the basis of a first mapping relationship and the target QoS parameter, wherein the first mapping relationship can be used for indicating a correlation between the QoS parameters and the DRX configuration, and the target DRX configuration can correspond to the first target; and performing sidelink communication on the basis of the target DRX configuration. The first target comprises one target address, a plurality of target addresses, or a terminal device, that is, the plurality of QoS flows can perform sidelink communication on the basis of the same target DRX configuration. The target QoS parameter used for determining the target DRX configuration is determined according to the plurality of groups of QoS parameters, and QoS requirements are considered. Thus, a balance between QoS performance and energy saving and power saving can be obtained.

Description

Discontinuous reception configuration method, communication device and communication system

technical field

The present application relates to the field of communications, and more particularly, to a discontinuous reception configuration method, a communication device, and a communication system.

Background technique

At present, in some communication systems, such as the 5th generation wireless system (5G), signaling and data transmission can be performed between terminal equipment and terminal equipment through a sidelink (SL). . This manner of transmission over the sidelink may be referred to as sidelink communication.

In order to obtain better quality of service (QoS) performance, such as higher transmission reliability, sidelink communication can be performed between terminal devices based on the same discontinuous reception (DRX) configuration. The originating terminal equipment and the receiving terminal equipment can send and receive control information, such as sidelink control information (SCI), in the same time period for normal communication; and can turn off the radio frequency ( radio frequency, RF) channel, does not send and receive control information, in order to achieve the effect of energy saving.

However, how to perform DRX configuration on terminal devices at both ends of the transceiver to achieve a balance between QoS performance and energy saving is a technical problem that needs to be solved urgently.

SUMMARY OF THE INVENTION

The present application provides a DRX configuration method, a communication device, and a communication system, so as to achieve a balance between QoS performance and energy saving.

In a first aspect, the present application provides a DRX configuration method, which can be executed by a terminal device (such as the first terminal device exemplified below), or by a component (such as the first terminal device) configured in the terminal device (such as the first terminal device). For example, a chip, a chip system, etc.) are executed, which is not limited in this embodiment of the present application.

Exemplarily, the method includes: determining target QoS parameters based on multiple groups of QoS parameters corresponding to a first target, where the first target includes multiple QoS flows; and determining a target DRX based on the first mapping relationship and the target QoS parameters configuration, the first mapping relationship is used to indicate the corresponding relationship between the QoS parameter and the DRX configuration, the target DRX configuration corresponds to the first target; and the sidelink communication is performed based on the target DRX configuration.

Based on the above technical content, the first terminal device may determine target QoS parameters according to multiple sets of QoS parameters corresponding to the first target, and then determine the target DRX configuration according to the target QoS parameters and the corresponding relationship between the QoS parameters and the DRX configuration. Thus, multiple QoS flows in the first target can all perform sidelink communication based on the DRX configuration. In this way, multiple QoS flows in the first terminal device can open and close the radio frequency channel based on the same DRX configuration, so that the switching frequency of the first terminal device between on and off of the radio frequency channel can be avoided to a certain extent, Reduce processing complexity and save energy. Moreover, since the target DRX configuration is determined based on the target QoS parameters, and the target QoS parameters are determined based on multiple sets of QoS parameters corresponding to the above-mentioned first target, the determined target DRX configuration can meet the QoS requirements to a certain extent, This enables the first terminal device to have better QoS performance, thereby achieving a balance between QoS performance and energy saving.

With reference to the first aspect, in some possible implementations, the first target includes: one target address, multiple target addresses or terminal devices.

The terminal device may specifically refer to all target addresses of a terminal device. Therefore, the first target corresponding to a terminal device may specifically refer to all target addresses of the first target corresponding to a terminal device.

The multiple destination addresses may specifically refer to multiple destination addresses of a terminal device, for example, may be part of all destination addresses of the terminal device. Therefore, the multiple target addresses corresponding to the first target may specifically refer to a partial target address of a terminal device corresponding to the first target.

Since each destination address may include one or more QoS flows, the first destination may include one or more QoS flows. That is, the first terminal device may configure DRX for one or more QoS flows. Therefore, the first terminal device can maintain a set of DRX configurations based on a larger granularity than the QoS flow, so that the implementation complexity can be reduced.

With reference to the first aspect, in some possible implementations, the method further includes: determining the target QoS parameter according to one or more of the following QoS parameters: priority level, packet error rate (packet error rate) error rate (PER), packet delay budget (PDB), maximum data burst volume (MDBV), guaranteed flow bit rate (GFBR), maximum flow bit rate ( maximum flow bit rate, MFBR), PC5 link aggregate maximum bit rate (PC5 link aggregate maximum bit rate, PC5Link-AMBR), minimum communication distance (range) and PC5 interface 5G quality of service identifier (PC55G QoS identifier, PQI), where , the PQI is used to indicate the following QoS parameters: default priority level, PDB, PER, MDBV, GFBR, MFBR, default AMBR and default averaging window.

Two possible implementations for determining target QoS parameters are provided below.

In a first possible implementation manner, the target QoS parameter is a set of QoS parameters corresponding to a target QoS flow in the first target; the target QoS flow is the multiple Among the QoS flows, the QoS flow with the smallest priority, or the QoS flow with the smallest PER, or the QoS flow with the smallest PDB, or the QoS flow with the largest MDBV.

That is, the first terminal device may determine the target DRX configuration by using, as the target QoS parameter, the QoS parameter corresponding to one QoS flow with a higher QoS requirement among the multiple QoS flows in the first target. Therefore, it is beneficial to obtain better QoS performance. And, the target DRX configuration determined based on the target QoS parameter may correspond to the first target, that is, to the QoS flow in the first target. That is, a set of DRX configurations can be maintained based on a larger granularity than QoS flows, with lower implementation complexity.

In a second possible implementation manner, each parameter in the target QoS parameters is respectively selected from multiple groups of QoS parameters corresponding to the multiple QoS flows included in the first target.

That is, the first terminal device may select a value with higher QoS requirements for each parameter as one of the target QoS parameters, and then determine the target DRX configuration. Therefore, it is beneficial to obtain better QoS performance. And, the target DRX configuration determined based on the target QoS parameter may correspond to the first target, that is, to the QoS flow in the first target. That is, a set of DRX configurations can be maintained based on a larger granularity than QoS flows, with lower implementation complexity.

With reference to the first aspect, in some possible implementation manners, the method further includes: receiving first indication information, where the first indication information is used to indicate the first mapping relationship.

A first possible situation is that the first indication information may be sent by a network device. The receiving the first indication information includes: receiving the first indication information from the network device.

The second possible situation is that the first indication information may be sent by another terminal device (eg, a second terminal device). The receiving the first indication information includes: receiving the first indication information from the second terminal device.

A third possible situation is that the receiving the first indication information includes: the access layer receives the first indication information from the upper layer.

The first terminal device may determine the first mapping relationship based on the received first indication information, and then determine the target DRX configuration corresponding to the target QoS parameter.

With reference to the first aspect, in some possible implementation manners, the method further includes: sending the target DRX configuration.

The first terminal device may send the determined target DRX configuration to the second terminal device, so as to align the DRX configuration with the second terminal device. Thus, the first terminal device and the second terminal device can perform sidelink communication based on the same DRX configuration. Since the target DRX configuration corresponds to the first target, the first target may include multiple QoS flows, so that a balance can be obtained between QoS performance and energy saving.

In a second aspect, the present application provides a DRX configuration method, which can be executed by a terminal device (such as the first terminal device in the following example), or by a component (such as the first terminal device) configured in the terminal device (such as the first terminal device). For example, a chip, a chip system, etc.) are executed, which is not limited in this embodiment of the present application.

Exemplarily, the method includes: determining a target service based on multiple sets of QoS parameters corresponding to a first target, the first target includes one or more services, and each service includes one or more QoS flows; based on the second mapping relationship and the target service, determine the target DRX configuration, the second mapping relationship is used to indicate the corresponding relationship between the service and the DRX configuration, the target DRX configuration corresponds to the first target; uplink communication.

Based on the above technical content, the first terminal device may determine the target service according to multiple sets of QoS parameters corresponding to the first target, and then determine the target DRX configuration according to the target service and the corresponding relationship between the service and the DRX configuration. Thus, multiple QoS flows in the first target can all perform sidelink communication based on the DRX configuration. In this way, multiple QoS flows in the first terminal device can open and close the radio frequency channel based on the same DRX configuration, so that the switching frequency of the first terminal device between on and off of the radio frequency channel can be avoided to a certain extent, Reduce processing complexity and save energy. Moreover, since the target DRX configuration is determined based on the target QoS parameters, and the target QoS parameters are determined based on multiple sets of QoS parameters corresponding to the above-mentioned first target, the determined target DRX configuration can meet the QoS requirements to a certain extent, This enables the first terminal device to have better QoS performance, thereby achieving a balance between QoS performance and energy saving.

With reference to the second aspect, in some possible implementations, the first target includes: one target address, multiple target addresses or terminal devices.

With reference to the second aspect, in some possible implementations, the second mapping relationship is specifically used to indicate the corresponding relationship between the service type and the DRX configuration; and the method further includes: based on the second mapping relationship and the target The service type of the service determines the target DRX configuration.

In an example, the second mapping relationship includes a corresponding relationship between a provider service identifier (provider service identifier, PSID) and a DRX configuration, where the PSID is used to indicate the service type; and the method further includes: based on the PSID The corresponding relationship with the DRX configuration and the service type of the target service determine the target DRX configuration.

In another example, the second mapping relationship includes a corresponding relationship between an intelligent traffic system application identifier (intelligent traffic system application identifier, ITS-AID) and a DRX configuration, where the ITS-AID is used to indicate the service type; and the The method further includes: determining the target DRX configuration based on the corresponding relationship between the ITS-AID and the DRX configuration and the service type of the target service.

It should be understood that one service type may correspond to one DRX configuration, and multiple service types may also correspond to one DRX configuration. This embodiment of the present application does not limit this.

It should also be understood that the correspondence between the service type and the DRX configuration is only a possible form of the correspondence between the service and the DRX configuration, and should not constitute any limitation to this application. In addition, the PSID and ITS-AID used to indicate the service type listed above are only examples, and should not constitute any limitation to the present application.

With reference to the second aspect, in some possible implementations, the method further includes: determining the target service according to one or more of the following QoS parameters: priority level, packet error rate PER, packet delay budget PDB , maximum data burst MDBV, guaranteed flow bit rate GFBR, maximum flow bit rate MFBR, PC5 link aggregation maximum bit rate AMBR, minimum communication distance and PC5 interface quality of service identification PQI, wherein, the PQI is used to indicate the following QoS Parameters: Default priority level, PDB, PER, MDBV, GFBR, MFBR, default AMBR and default sliding window.

Since the first terminal device can determine a target service based on multiple sets of QoS parameters corresponding to multiple QoS flows, for example, a target service can be determined for one target address, multiple target addresses, or multiple sets of QoS parameters corresponding to one terminal device, so that the When the target DRX configuration is subsequently determined, the DRX is configured based on a larger granularity than the QoS flow.

With reference to the second aspect, in some possible implementation manners, the method further includes: the target service is a service corresponding to the target QoS flow included in the first target; the target QoS flow is the first target including Among the multiple QoS flows, the QoS flow with the smallest priority, or the QoS flow with the smallest PER, or the QoS flow with the smallest PDB, or the QoS flow with the largest MDBV.

That is, the first terminal device may use a service corresponding to a QoS flow with a higher QoS requirement among the multiple QoS flows in the first target as the target service, and determine the target DRX configuration based on the target service. On the one hand, it is beneficial to obtain better QoS performance; on the other hand, since the target DRX configuration can correspond to the first target, that is, it corresponds to the QoS flow in the first target, that is, it can be based on a larger granularity than the QoS flow. To maintain a set of DRX configuration, the implementation complexity is low.

With reference to the second aspect, in some possible implementation manners, the method further includes: receiving second indication information, where the second indication information is used to indicate the second mapping relationship.

A first possible situation is that the second indication information may be sent by a network device. The receiving the second indication information includes: receiving the second indication information from the network device.

The second possible situation is that the second indication information may be sent by another terminal device (eg, a second terminal device). The receiving the second indication information includes: receiving the second indication information from the second terminal device.

A third possible situation is that the receiving the second indication information includes: the access layer receives the second indication information from the upper layer.

The second terminal device may determine the second mapping relationship based on the received second indication information, and then determine the target DRX configuration corresponding to the target service.

In a third aspect, the present application provides a DRX configuration method, which can be executed by a terminal device (such as the second terminal device exemplified below), or by a component (such as the second terminal device) configured in the terminal device (such as the second terminal device). For example, a chip, a chip system, etc.) are executed, which is not limited in this embodiment of the present application.

Exemplarily, the method includes: receiving a target DRX configuration, where the target DRX configuration is determined based on a first mapping relationship and a target quality of service QoS parameter; wherein the first mapping relationship is used to indicate the difference between the QoS parameter and the DRX configuration. Corresponding relationship, the target QoS parameter is determined based on multiple groups of QoS parameters corresponding to the first target; the target DRX configuration corresponds to the first target, and the first target includes multiple QoS flows of the first terminal device ; perform sidelink communication based on the target DRX configuration.

Based on the above technical content, the second terminal device may not need to determine the target DRX configuration by itself, but may directly receive the target DRX configuration from the opposite end (eg, the first terminal device), and perform sidelinking with the opposite end based on the target DRX configuration road communication.

With reference to the third aspect, in some possible implementation manners, the first target includes: one target address, multiple target addresses or terminal devices.

With reference to the third aspect, in some possible implementations, the target QoS parameter is determined according to one or more of the following parameters: priority level, packet error rate PER, packet delay budget PDB, maximum data burst size MDBV, Guaranteed Traffic Bit Rate GFBR, Maximum Traffic Bit Rate MFBR, PC5 Link Aggregation Maximum Bit Rate AMBR, Minimum Communication Distance, and PC5 Interface Quality of Service Identifier PQI, where the PQI is used to indicate the following QoS parameters: Default priority amount Level, PDB, PER, MDBV, GFBR, MFBR, Default AMBR, and Default Sliding Window.

Some possible implementation manners in the third aspect correspond to some possible implementation manners in the first aspect, and reference may be made to the relevant descriptions in the first aspect, which are not repeated here for brevity.

In a fourth aspect, the present application provides a DRX configuration method for discontinuous reception. The method can be executed by a terminal device (such as the first terminal device in the following example), or configured in the terminal device (such as the first terminal device) components (eg, chips, chip systems, etc.) are executed, which is not limited in this embodiment of the present application.

Exemplarily, the method includes: receiving a target DRX configuration, where the target DRX configuration is determined based on a second mapping relationship and a target service; wherein the second mapping relationship is used to indicate a corresponding relationship between the service and the DRX configuration, and the The target service is determined based on multiple sets of service quality QoS parameters corresponding to the first target, the target DRX configuration corresponds to the first target, and the first target includes one or more services of the first terminal device, each Each service includes one or more QoS flows; sidelink communication is performed based on the target DRX configuration.

With reference to the fourth aspect, in some possible implementation manners, the first target includes: one target address, multiple target addresses or terminal devices.

With reference to the fourth aspect, in some possible implementation manners, the second mapping relationship is specifically used to indicate the corresponding relationship between the service type and the DRX configuration.

With reference to the fourth aspect, in some possible implementations, the target service is determined according to one or more of the following QoS: priority level, packet error rate PER, packet delay budget PDB, maximum data burst volume MDBV , Guaranteed traffic bit rate GFBR, maximum traffic bit rate MFBR, PC5 link aggregation maximum bit rate AMBR, minimum communication distance and PC5 interface quality of service identification PQI, wherein, the PQI is used to indicate the following QoS parameters: default priority level , PDB, PER, MDBV, GFBR, MFBR, default AMBR and default sliding window.

Some possible implementation manners in the fourth aspect correspond to some possible implementation manners in the second aspect, and reference may be made to the relevant descriptions in the second aspect, which are not repeated here for brevity.

With reference to the first to fourth aspects, in some possible implementations, the target DRX configuration may be a default DRX configuration or a public DRX configuration.

For example, when the first terminal device does not find a corresponding relationship matching the target QoS parameter from the first mapping relationship or does not find a corresponding relationship matching the target service in the second mapping relationship, the default DRX configuration or the public DRX configuration can be configured. as the target DRX configuration.

In a fifth aspect, the present application provides a communication device, the device including each module for implementing the DRX configuration method in any of the first to fourth aspects and any possible implementation manner of the first to fourth aspects or unit. It should be understood that the respective modules or units may implement corresponding functions by executing computer programs.

In a sixth aspect, the present application provides a communication apparatus including a processor. The processor is coupled to the memory and can be used to execute a computer program in the memory to implement the DRX configuration method in the first aspect to the fourth aspect and any one of the possible implementations of the first aspect to the fourth aspect. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface. Illustratively, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

In a seventh aspect, the present application provides a communication system, which includes the first terminal device and the second terminal device in any possible implementation manners of the first to fourth aspects and the first to fourth aspects. Optionally, the communication system further includes a network device.

In an eighth aspect, the present application provides a chip, which is connected to a memory and used to read and execute a software program stored in the memory, so as to realize the above-mentioned first to fourth aspects and the first to fourth aspects method in any possible implementation of .

In a ninth aspect, the present application provides a computer-readable storage medium on which a computer program (also referred to as code, or instruction) is stored, and when the computer program is executed by a processor, causes The method in any one of the above-mentioned first to fourth aspects and possible implementations of the first to fourth aspects is performed.

In a tenth aspect, the present application provides a computer program product. The computer program product includes: a computer program (which may also be referred to as code, or instructions) that, when the computer program is executed, causes any of the above-mentioned first to fourth aspects and the first to fourth aspects Methods in possible implementations are executed.

It should be understood that the fifth to tenth aspects of the present application correspond to the technical solutions of the first to fourth aspects of the present application, and the beneficial effects obtained by each aspect and the corresponding feasible embodiments are similar, and no Repeat.

Description of drawings

1 to 3 are schematic diagrams of a communication system applicable to the DRX configuration method provided by the embodiments of the present application;

Fig. 4 is the schematic diagram of the relation of target address, business and QoS flow;

5 and 6 are schematic diagrams of DRX;

7 is a schematic flowchart of a DRX configuration method provided by an embodiment of the present application;

8 is a schematic flowchart of a DRX configuration method provided by another embodiment of the present application;

9 is a schematic diagram of a direct connection communication establishment process;

FIG. 10 is a schematic flowchart of a DRX configuration method provided by another embodiment of the present application;

FIG. 11 and FIG. 12 are schematic block diagrams of a communication apparatus provided by an embodiment of the present application;

FIG. 13 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the present application will be described below with reference to the accompanying drawings.

The technical solutions provided in this application can be applied to various communication systems, for example, a fifth generation (5th generation, 5G) mobile communication system or a new radio access technology (NR). The 5G mobile communication system may include a non-standalone (NSA, NSA) and/or an independent network (standalone, SA).

The technical solutions provided in this application can also be applied to machine type communication (MTC), Long Term Evolution-machine (LTE-M), device-to-device (D2D) Network, machine to machine (M2M) network, internet of things (IoT) network or other network. The IoT network may include, for example, the Internet of Vehicles. Among them, the communication methods in the Internet of Vehicles system are collectively referred to as vehicle to other equipment (vehicle to X, V2X, X can represent anything) system, for example, the V2X may include: vehicle to vehicle (vehicle to vehicle, V2V) communication, vehicle Communication with infrastructure (V2I), communication between vehicle and pedestrian (V2P) or communication between vehicle and network (V2N), etc.

The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system. This application does not limit this.

In this embodiment of the present application, the network device may be any device with a wireless transceiver function. Network equipment includes but is not limited to: evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller, BSC) , base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), wireless fidelity (wireless fidelity, WiFi) system Access point (AP), radio relay node (RRN), wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc. It can be a 5G, such as NR, a gNB in the system, or a transmission point (TRP or TP), one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also constitute a gNB Or a network node of a transmission point, such as a baseband unit (BBU), or a distributed unit (distributed unit, DU), etc.

In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU can be responsible for processing non-real-time protocols and services, such as the radio resource control (radio resource control, RRC) layer, service data adaptation protocol (service data) function of the adaptation protocol (SDAP) layer and/or the packet data convergence protocol (PDCP) layer. The DU can be responsible for handling physical layer protocols and real-time services. For example, functions of a radio link control (radio link control, RLC) layer, a media access control (media access control, MAC) layer, and a physical (physical, PHY) layer can be implemented. One DU can be connected to only one CU or to multiple CUs, and one CU can be connected to multiple DUs, and communication between CUs and DUs can be performed through the F1 interface. AAU can realize some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually be submitted to the PHY layer and become the information of the PHY layer, or, converted from the information of the PHY layer, therefore, in this architecture, high-level signaling, such as RRC layer signaling, also It can be considered to be sent by DU, or sent by DU+AAU.

It can be understood that the network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU can be divided into network devices in an access network (radio access network, RAN), and the CU can also be divided into network devices in a core network (core network, CN), which is not limited in this application.

The network equipment provides services for the cell, and the terminal equipment communicates with the cell through transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the network equipment, and the cell may belong to a macro base station (for example, a macro eNB or a macro gNB, etc.) , can also belong to the base station corresponding to the small cell, where the small cell can include: urban cell (metro cell), micro cell (micro cell), pico cell (pico cell), femto cell (femto cell), etc. , these small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

In this embodiment of the present application, a terminal device may also be referred to as user equipment (user equipment, UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, Terminal, wireless communication device, user agent or user equipment.

The terminal device may be a device that provides voice/data connectivity to the user, such as a handheld device with a wireless connection function, a vehicle-mounted device, and the like. At present, some examples of terminals can be: mobile phone (mobile phone), tablet computer (pad), computer with wireless transceiver function (such as notebook computer, palmtop computer, etc.), mobile internet device (mobile internet device, MID), virtual reality (virtual reality, VR) equipment, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control (industrial control), wireless terminals in unmanned driving (self driving), wireless terminals in remote medical (remote medical) Terminal, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, cellular phone, cordless Telephone, session initiation protocol (SIP) telephone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device, computing device or connection with wireless communication capabilities Other processing equipment to wireless modems, in-vehicle equipment, wearable equipment, terminal equipment in 5G networks or terminal equipment in the future evolved public land mobile network (PLMN), etc.

Among them, wearable devices can also be called wearable smart devices, which is a general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones. Use, such as all kinds of smart bracelets, smart jewelry, etc. for physical sign monitoring.

In addition, the terminal device may also be a terminal device in an Internet of things (Internet of things, IoT) system. IoT is an important part of the development of information technology in the future. Its main technical feature is to connect items to the network through communication technology, so as to realize the intelligent network of human-machine interconnection and interconnection of things. IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrow band (NB) technology.

It should be understood that the present application does not limit the specific forms of the network device and the terminal device.

In addition, in the embodiments of the present application, UE and terminal device are used interchangeably, and the meanings expressed by the two are the same.

In a wireless communication system, terminal devices can communicate through sidelinks. The interface between the terminal devices communicating through the side link may be referred to as the PC5 interface.

A typical application scenario for sidelink communication is V2X. In V2X, each vehicle can be regarded as a terminal device, and data transmission between terminal devices can be performed directly through sidelinks without going through the network, which can effectively reduce the communication delay.

FIG. 1 is a schematic diagram of a communication system applicable to the communication method of the embodiment of the present application. The communication system 100 shown in FIG. 1 may include at least one network device and a plurality of terminal devices, for example, the network device 110 and the terminal devices 121 to 123 shown in FIG. 1 . The network device 110 and each of the terminal devices 121 to 123 may communicate through a wireless air interface, respectively, and the terminal devices 121 to 123 may communicate through a vehicle wireless communication technology. For example, the terminal device 121 and the terminal device 122 can also communicate with each other, the terminal device 121 and the terminal device 123 can also communicate with each other, and the terminal device 122 and the terminal device 123 can also communicate with each other.

It should be noted that, in the communication system 100 shown in FIG. 1, one or more of the terminal devices 121 to 123 may be located within the coverage of the network device 110, and one or more of the terminal devices 121 to 123 may also be located in Out of coverage of network device 110 . For example, terminal device 121, terminal device 122, and terminal device 123 may all be located within the coverage of network device 110; or, terminal device 121 may be located within the coverage of network device 110, and terminal device 122 and terminal device 123 out of coverage; or, the terminal device 121 and the terminal device 122 are located within the coverage of the network device 110, and the terminal device 123 is located outside the coverage of the network device 110; or, the terminal device 123 is located within the coverage of the network device 110, and the terminal device 121 and the terminal device 122 are located outside the coverage of the network device 110 ; or, the terminal device 121 , the terminal device 122 and the terminal device 123 are all located outside the coverage of the network device 110 . For brevity, they are not listed here.

It should be understood that FIG. 1 is only an example, showing one network device and three terminal devices. However, this should not constitute any limitation to this application. The communication system 100 may further include more network devices, and may also include more or less terminal devices. This embodiment of the present application does not limit this.

In the communication system 100 shown in FIG. 1 , the terminal device may perform sidelink communication based on resources scheduled by the network device, or may use resources preconfigured by the network device (such as a resource pool) based on autonomous competition. ) to select unoccupied resources for sidelink communication. This embodiment of the present application does not limit this.

FIG. 2 is another schematic diagram of a communication system applicable to the communication method of the embodiment of the present application. The communication system 200 shown in FIG. 2 is a communication system in a UE-to-network relay (such as UE-to-network relay) scenario.

As shown in FIG. 2, the communication system 200 may include a network device 210, a UE (may be referred to as a relay UE (relay UE) for short) 220 that can implement a UE-to-network relay (UE-to-network relay), a remote end UE (remote UE) 230 . It should be understood that

In FIG. 2, the relay UE 220 can communicate with the network device 210 directly, and the remote UE 230 can communicate with the network device 210 based on the relay service provided by the relay UE 220. It should be understood that the communication interface between the remote UE 230 and the relay UE 220 may be a PC5 interface, and the remote UE 230 may communicate with the relay UE 220 through the PC5 interface. Therefore, the communication between the relay UE 220 and the remote UE 230 may also be referred to as sidelink communication.

It should be noted that, if a UE can successfully establish a PC5 link with the relay UE, the UE can be regarded as a remote UE. The remote UE may be within the coverage of the wireless access network, or may be outside the coverage of the wireless access network, which is not limited in this embodiment of the present application.

FIG. 3 is another schematic diagram of a communication system applicable to the communication method of the embodiment of the present application. The communication system 300 shown in FIG. 3 is a communication system in a UE-to-UE relay (eg, UE-to-UE relay) scenario.

A UE-to-UE relay scenario may include at least 3 UEs, and at least one of them can serve as a relay UE. As shown in FIG. 3 , the communication system 300 may include at least 3 UEs, such as UE 310, UE 320 and UE 330 in the figure. The UE 320 is a relay UE, the UE 310 can communicate directly with the relay UE 320, the UE 330 can also communicate directly with the relay UE 320, and the UE 310 and the UE 330 can communicate based on the relay service provided by the relay UE 320 . The UE 310 may be, for example, a source UE (source UE), and the UE 330 may be, for example, a target UE (target UE).

It should be understood that the communication interface between the UE 310 and the UE 320 may be a PC5 interface, and the UE 310 may communicate with the UE 320 through the PC5 interface. The communication interface between the UE 320 and the UE 330 can also be a PC5 interface, and the UE 320 can communicate with the UE 330 through the PC5 interface. Therefore, the communication between UE 310 and UE 320, and the communication between UE 320 and UE 330 may also be referred to as sidelink communication.

It should be understood that the communication systems described above in conjunction with FIG. 1 to FIG. 3 are only exemplary, and should not constitute any limitation to the embodiments of the present application.

It should be noted that the sidelink communication can support unicast communication, multicast communication and broadcast communication.

Wherein, unicast communication may refer to transmitting signaling and/or data to a device. In sidelink communication, communication between terminal devices can be based on a unicast connection. The unicast connection can be uniquely associated with a source layer 2 identifier (source layer 2 identifier, source L2 ID) and a destination layer 2 identifier (destination L2 ID).

Multicast communication may refer to the simultaneous transmission of signaling and/or data to a group of devices. In sidelink communication, a group can be associated with a group identifier, and the upper layer (such as the V2X layer) can submit the group identifier to the access stratum (AS), and the access layer can convert the group identifier to the corresponding The target layer 2 identifier. Alternatively, when the upper layer does not provide a group identifier, the access layer can also determine the target layer 2 identifier corresponding to the multicast based on the pre-configured mapping relationship between the V2X service type (service type) and the layer 2 identifier (L2 ID). In other words, the target layer 2 identification can be used to identify a group.

Broadcast communication may refer to a transmission device whose destination address is all devices in the communication system. It should be understood that all the devices described here are also limited within a scope; for example, all the devices described are devices that are interested in the broadcast communication service. One broadcast communication may correspond to one service. The target layer 2 identifier may be determined based on the pre-configured mapping relationship between the V2X service type and the layer 2 identifier.

In order to facilitate the understanding of the embodiments of the present application, firstly, the terms involved in the present application are briefly described.

1. Destination address: In unicast communication, the destination address can be used to identify a receiving UE; in multicast communication, the destination address can be used to identify a group; in broadcast communication, the destination address can be used to identify a service. It can be understood that the target address may be the target layer 2 identifier. In other words, the target layer 2 identifier is an example of the target address.

2. Quality of service (QoS) flow (QoS flow) and QoS parameters: QoS flow is a QoS differentiation granularity in a protocol data unit (protocol data unit, PDU) session. In the 5G system, a QoS Flow identifier (QFI) can be used to identify a QoS flow. A PDU session can include multiple QoS flows, but the QFI of each QoS flow is different.

In this embodiment of the present application, one target address may include one or more services (service), and one service may include one or more QoS flows. Figure 4 shows the relationship of destination addresses, services and QoS flows. As shown, a destination address can include one or more services. Each service may include one or more QoS flows.

For example, in FIG. 4 , target address 1 includes 3 services, namely service 1 , service 2 and service 3 . Service 1 includes 4 QoS flows, namely QoS 1, QoS 2, QoS 3, and QoS 4; Service 2 includes 2 QoS flows, namely QoS 5 and QoS 6; Service 3 includes 1 quality of service flow, that is, quality of service flow 7.

Each QoS flow may be associated with (or correspond to) a set of QoS parameters. The QoS parameters associated with each QoS flow can be determined by, for example, the upper layer of the terminal device (such as the V2X layer), or can be obtained from the terminal device at the opposite end, such as through a PC5-RRC message or a PC5-S message. Here, the terminal device at the opposite end may specifically refer to a terminal device that performs sidelink communication with the terminal device.

Each group of QoS parameters can include one or more of the following: PC5 interface QoS flow identifier (PC5 QoS flow identifier, PFI), PC5 interface 5G service quality identifier (PC5 5QI, PQI), guaranteed flow bit rate (guaranteed flow bit rate, GFBR), maximum flow bit rate (MFBR), maximum bit rate of PC5 link aggregation (PC5 link aggregate maximum bit rate, PC5Link-AMBR), minimum communication distance (range), resource type (resource type), Priority level (priority level), packet delay budget (packet delay budget, PDB), packet error rate (packet error rate, PER), sliding window (averaging window) and maximum data burst volume (maximum data burst volume, MDBV). Thus, a destination address may include one or more QoS flows, corresponding to one or more sets of QoS parameters.

It should be understood that a standard PQI may correspond to a set of QoS characteristics. Specifically, the corresponding relationship between the PQI and the QoS feature may be specifically determined by the corresponding relationship predefined in the protocol. For example, one PQI may be used to indicate one or more of default priority level, resource type, PDB, PER, default sliding window, default MDBV. The QoS parameters corresponding to each QoS flow can be obtained by standard PQI mapping, or can be directly configured. This embodiment of the present application does not limit this. It is understood that the QoS parameters include QoS characteristics. In the following, for the convenience of distinction and description, the QoS parameters corresponding to the PQI configured by the PQI are referred to as QoS features, and may also be referred to as the QoS features corresponding to the PQI, so as to facilitate the integration with other QoS parameters other than the QoS parameters configured by the PQI. parameter distinction.

It should be noted that, in a set of QoS parameters, in addition to configuring the corresponding default priority level, PDB, PER, resource type, default MDBV, default sliding window and other QoS features through PQI, you can also configure it directly in the QoS parameters. One or more of Priority Level, PDB, PER, Resource Type, MDBV, Sliding Window. The direct mentioned here is relative to the QoS feature corresponding to the PQI configured through the PQI. In other words, in addition to the QoS characteristics corresponding to the PQI, the set of QoS parameters may also include one or more parameters of priority level, PDB, PER, resource type, MDBV, and sliding window.

In other words, two values of one or more of the following parameters may be configured simultaneously in a set of QoS parameters: priority level, PDB, PER, resource type, MDBV, and sliding window. When two values are configured for the same parameter in a set of QoS parameters, the value included in the QoS parameter (that is, the value directly configured through the QoS parameter) may prevail, and the value of the same parameter corresponding to the configuration in the PQI may be used. cover.

For example, a corresponding default priority level is configured in the PQI of a QoS flow, and the QoS parameter of the QoS flow also includes the priority level. Therefore, two priority levels may be configured for the QoS flow, one is the default priority level corresponding to the PQI, and the other is the priority level directly configured in the QoS parameters. In this case, the priority level of the QoS flow is based on the value directly configured in the QoS parameter, and the priority level can override the default priority level in the PQI. Conversely, if the priority level is not directly included in the QoS parameters of the QoS flow, but the PQI is included, the default priority level in the PQI may be used.

It should be understood that "configured" here can also be replaced with "include", "indicate" and the like.

3. PC5 interface: a direct communication interface from terminal equipment to terminal equipment defined in 3GPP, which can be used to support data transmission between any two terminal equipment through a direct link within a preset range. Connections based on the PC5 interface may be referred to as PC5 connections or side row connections. Links based on the PC5 interface may be referred to as PC5 links or sidelinks.

It should be understood that the PC5 interface is a possible name of a direct communication interface from a terminal device to a terminal device, which should not constitute any limitation to this application. This application does not exclude the possibility of defining other interfaces in future protocols to achieve the same or similar functions as the PC5 interface.

The terminal equipment can monitor sidelink control information (SCI) to listen for messages sent by possible originating UEs. However, the actual situation is that most of the time, the transmitting UE may not need to send data, which greatly increases the power consumption of the receiving UE. From the perspective of energy saving, a discontinuous reception DRX mechanism is introduced, and sidelink communication can be performed between the transmitting UE and the receiving UE based on the same DRX configuration. The originating UE and the terminating UE can send and receive control information, such as SCI or physical sidelink control channel (PSSCH), in the same time period for normal communication; and can be turned off in the same time period The radio frequency (RF) channel does not send and receive control information, so as to achieve the effect of energy saving. Since it is applied to the sidelink communication between terminal devices, the DRX configuration is specifically the SL DRX configuration.

FIG. 5 shows an example of the SL DRX configuration. As shown in FIG. 5 , the originating UE may send control information at the on time, but not at the off time; the receiving UE may monitor the control information at the on time, and not monitor the control information at the off time. In one possible design, the SL DRX configuration may include one or more of the following timers: onDurationTimer, InactivityTimer, RetransmissionTimer, Hybrid Automatic Retransmission Transmission request (hybrid automatic repeat request, HARQ) - round trip time (round trip time, RTT) - timer (Timer) and short cycle timer (shortCycleTimer) and so on. Optionally, the SL DRX configuration may further include one or more of parameters such as slot offset (SlotOffset), long cycle start offset (LongCycleStartOffset), short cycle (ShortCycle), and long cycle (LongCycle).

Referring to Figure 5, the on time shown in Figure 5 can also be represented by the active time. The on time can specifically refer to the running time of any of the following timers: onDurationTimer, RetransmissionTimer and InactivityTimer, except for the on time. The outside time can be the off time. In other words, based on the running time of the above-mentioned timers of onDurationTimer, RetransmissionTimer and InactivityTimer, the on time and off time of the DRX can be determined.

Optionally, the SL DRX configuration is included in an RRC message, a SIB message or a preconfigured message.

Optionally, the SL DRX configuration is included in the resource pool configuration. Exemplarily, one resource pool configuration may include one or more SL DRX configurations, and each SL DRX configuration may include one or more of the following: onDurationTimer, InactivityTimer, SlotOffset, LongCycleStartOffset, ShortCycle, LongCycle, and the like. In this case, the on time shown in FIG. 5 may specifically refer to the time when any one of onDurationTimer and InactivityTimer runs.

Further optionally, the resource pool configuration also includes the mapping relationship between one or more groups of QoS parameters and the SDL DRX configuration (that is, the first mapping relationship described below) or the mapping relationship between the service and the SDL DRX configuration (that is, the following. the second mapping relationship).

In another possible design, the SL DRX configuration may correspond to a resource pattern. Figure 6 shows the SL DRX configuration corresponding to the resource pattern. As shown in Figure 6, the resource mode can divide the resources in the resource pool into DRX resources and non-DRX resources. The DRX resource may correspond to the on time in FIG. 5 , and the non-DRX resource may correspond to the off time in the figure. A terminal device that performs sidelink communication based on the SL DRX configuration corresponding to the resource mode can send or receive data on the DRX resources in the resource mode, and does not send or receive data on the non-DRX resources in the resource mode. take over.

Optionally, the SL DRX configuration may be included in a resource pool configuration.

Exemplarily, a resource pool configuration may include one or more resource modes. Each resource mode can correspond to one SL DRX configuration.

Further optionally, the resource pool configuration also includes the mapping relationship between one or more groups of QoS parameters and the SDL DRX configuration (that is, the first mapping relationship described below) or the mapping relationship between the service and the SDL DRX configuration (that is, the following. the second mapping relationship). It should be understood that the specific content in the SL DRX configuration and the signaling including the DRX configuration described above are only examples, and should not constitute any limitation to this application. This application does not limit the specific manner of SL DRX configuration.

Since the DRX configurations involved in the embodiments of the present application are all SL DRX configurations, for the convenience of description, the SL DRX configurations are hereinafter referred to as DRX configurations for short.

Each terminal device can communicate with one or more terminal devices, whereby each terminal device can correspond to one or more destination addresses. As previously mentioned, each destination address may include one or more QoS flows. The DRX configuration is related to QoS parameters; exemplarily, different QoS requirements expressed by different QoS parameters, such as delay, reliability, etc., and DRX configurations corresponding to different QoS requirements (the length and period of the corresponding on time, etc. ) can be different. If the terminal device performs DRX configuration for each QoS flow, if the terminal device is based on the DRX configuration corresponding to each QoS flow, it may constantly switch between the on and off of the radio frequency channel, which may not achieve the effect of energy saving and power saving. .

In view of this, the present application provides a DRX configuration method in order to achieve a balance between QoS performance and energy saving.

As mentioned above, the DRX configuration is related to the QoS parameters. Based on the correlation between the DRX configuration and the QoS parameters, the embodiments of the present application propose the following technical solutions: determine a set of target QoS parameters based on multiple QoS flows, and based on the QoS The mapping relationship between the parameter and the DRX configuration and the target QoS parameter determine the target DRX configuration. The target DRX configuration may be used for transmission of the plurality of QoS flows.

Further, as can be seen in the foregoing description in conjunction with Figure 4, services and QoS flows are related, each service may include one or more QoS flows, and each QoS flow may correspond to a set of QoS parameters, so the DRX configuration is related to the QoS flow. Business is also relevant. Based on the correlation between the DRX configuration and the service, the embodiments of the present application also propose the following technical solutions: determine a target service based on multiple QoS flows, and determine the target DRX configuration based on the mapping relationship between the service and the DRX configuration and the target service. The target DRX configuration may be used for transmission of the plurality of QoS flows.

The technical solutions provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

For ease of understanding, before introducing the embodiments of the present application, the following points are first made.

First, "based on" can also be replaced with "according to", "reference", "according to", etc.

Second, the first, the second, and various numerical numbers are only for the convenience of description, and are not used to limit the scope of the embodiments of the present application. For example, different indication information, different terminal devices, etc. are distinguished.

Third, descriptions such as "when", "in the case of", "if", and "if" all mean that the device (such as a terminal device or a network device) will respond accordingly under certain objective circumstances The processing does not limit the time, and does not require the device (eg, terminal device or network device) to have a judgment action during implementation, nor does it mean that there are other limitations.

Fourth, "default" can also be replaced with "default".

Fifth, "including" can also be replaced with "associated", "corresponding" and so on.

Sixth, "pre-configuration" can be achieved by pre-saving corresponding codes, tables or other means that can be used to indicate relevant information in the device (for example, terminal equipment, etc.) (for example, in the chip of the device), or by Signaling pre-configuration, for example, other devices (eg, network devices, etc.) are implemented by means of signaling pre-configuration, and the present application does not limit its specific implementation.

Exemplarily, when the terminal device is in the RRC connected state or, it can be pre-configured through RRC dedicated signaling; when the terminal device is in the RRC idle state or inactive state, it can be configured through a system information block (system information block, SIB) message to perform pre-configuration; when the terminal device is out of coverage (out of coverage, OOC), it can be pre-configured through a message pre-sent by the network device, such as a pre-configuration message pre-sent by the core network device.

The pre-configured content may include one or more of the following: a first mapping relationship, a second mapping relationship, a mapping relationship between V2X service types and layer 2 identifiers, default DRX configuration or public DRX configuration, and dedicated DRX configuration.

Seventh, the embodiment of the present application involves interaction between the upper layer of the terminal device and the access layer. The upper layer may specifically refer to the V2X layer or the PC5-S layer.

The DRX configuration method provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings. In the following embodiments, without loss of generality, various embodiments are described by taking the determination of the target DRX configuration by the first terminal device as an example. It can be understood that the second terminal device may also determine the target DRX configuration based on the method provided in the following embodiments, which is not limited in this embodiment of the present application.

For ease of understanding, each embodiment shows the interaction between the first terminal device and the second terminal device, but this should not constitute any limitation to the present application. The first terminal device may interact with the second terminal device after determining the target DRX configuration, or may interact with the second terminal device during the process of determining the target DRX configuration, but the determination of the target DRX configuration is still performed by the first terminal device. .

In addition, the first terminal device and the second terminal device may be, for example, terminal devices capable of sidelink communication in the communication system shown in Figs. 1 to 3 . The first terminal device may be configured to execute the following DRX configuration method, and the second terminal device is a terminal device that performs sidelink communication with the first terminal device. It should be understood that the accompanying drawings are only examples, and should not constitute any limitation on the execution subject of each step. As long as the program that records the codes of the methods provided by the embodiments of the present application can be executed according to the methods provided by the embodiments of the present application, it can be used as the execution body of the methods provided by the embodiments of the present application. For example, the first terminal device shown in the following embodiments may also be replaced by components in the first terminal device, such as a chip, a chip system, or other functional modules capable of calling and executing programs. The second terminal device can also be replaced with components in the second terminal device, such as a chip, a chip system, or other functional modules capable of calling a program and executing the program.

FIG. 7 is a schematic flowchart of a DRX configuration method 700 for discontinuous reception provided by an embodiment of the present application. The method 700 shown in FIG. 7 shows the flow of DRX configuration based on the mapping relationship between QoS parameters and DRX configuration.

As shown in FIG. 7 , the method 700 may include steps 710 to 740 . Each step in the method 700 will be described in detail below.

In step 710, the first terminal device determines target QoS parameters based on multiple sets of QoS parameters corresponding to the first target.

Here, the first target includes: a target address, a plurality of target addresses (also referred to as a group of target addresses), or a terminal device (eg, a first terminal device).

Wherein, a terminal device may specifically refer to all target addresses of a terminal device. Therefore, the first target corresponding to a terminal device may specifically refer to all target addresses of the first target corresponding to a terminal device.

As mentioned earlier, multiple target addresses can also be referred to as a group of target addresses. The set of destination addresses can be obtained, for example, by grouping the destination addresses of the first terminal devices. The specific manner of grouping is not limited in this embodiment of the present application. In an example, the set of target addresses may be determined by the upper layer of the first terminal device, and the upper layer may further notify the access layer of multiple target addresses corresponding to the set of target addresses. In another example, the set of target addresses may also be determined by the access layer of the first terminal device. The upper layer or the access layer of the first terminal device may obtain, for example, a plurality of target addresses corresponding to the group of target addresses through a device discovery (discovery) process or a direct connection communication process.

As mentioned above, in unicast communication, the target address can be used to identify a peer terminal equipment (sending or receiving terminal equipment), so the first target can correspond to a pair that performs sidelink communication with the first terminal equipment. terminal equipment or multiple peer terminal equipment; in multicast communication, the target address can be used to identify a group, so the first target can correspond to the terminal equipment of one or more groups receiving the multicast service of the first terminal equipment ; In broadcast communication, the target address can be used to identify a service, so the first target can correspond to a terminal device that receives one or more broadcast services of the first terminal device.

Based on the above description of the relationship between the target address and the QoS flow, it can be known that the first target may include one or more QoS flows. In this embodiment of the present application, the first target includes multiple QoS flows. The multiple QoS flows may be, for example, multiple QoS flows in one destination address, multiple QoS flows in multiple destination addresses, or multiple QoS flows in one terminal device.

Thus, the first target may be a collective term for multiple QoS flows. In another formulation, the first target may be replaced by a plurality of QoS flows. Step 710 can also be expressed as: the first terminal device determines target QoS parameters based on multiple sets of QoS parameters corresponding to multiple QoS flows.

Each QoS flow corresponds to a set of QoS parameters. As mentioned earlier, each set of QoS parameters can include one or more of the following: PQI, Priority Level, PER, PDB, MDBV, GFBR, MFBR, PC5 Link AMBR, range, resource type, sliding window, and PFI, etc. .

Based on the above-mentioned relationship between the first target and QoS flow and the corresponding relationship between QoS flow and QoS parameters, it can be known that the multiple groups of QoS parameters corresponding to the first target may be multiple groups corresponding to multiple QoS flows included in one target address. QoS parameters, or multiple sets of QoS parameters corresponding to multiple QoS flows included in multiple target addresses, or multiple sets of QoS parameters corresponding to multiple QoS flows in the first terminal device.

The first terminal device may first acquire information of multiple QoS flows in the first target, and then determine target QoS parameters based on multiple sets of QoS parameters corresponding to the multiple QoS flows. The information of the multiple QoS flows is used to indicate the multiple QoS flows. The target QoS parameters may include one or more of the following: PQI, priority level, PER, PDB, MDBV, GFBR, MFBR, PC5 link AMBR, range, resource type, and sliding window.

The first terminal device may determine the target QoS parameter in the following manner.

In an implementation manner, the upper layer of the first terminal device may send information of multiple QoS flows included in the first target to the AS layer, and the AS layer may determine target QoS parameters according to multiple sets of QoS parameters corresponding to the multiple QoS flows .

In another implementation manner, the first terminal device may obtain multiple groups of QoS corresponding to multiple QoS flows included in the first target through a PC5-RRC message or a PC5-S message sent by the opposite terminal (eg, the second terminal device). parameters, and then determine target QoS parameters according to the multiple groups of QoS parameters. Optionally, the first terminal device is a receiving terminal device, and the second terminal device is an originating terminal device.

In yet another implementation manner, the first terminal device may directly acquire the target QoS parameter corresponding to the first target through a PC5-RRC message or a PC5-S message sent by the opposite end (eg, the second terminal device). In other words, the target QoS parameter corresponding to the first target may be determined by the second terminal device. Optionally, the first terminal device is a receiving terminal device, and the second terminal device is an originating terminal device.

Exemplarily, the target QoS parameter can be determined through the following two possible implementation manners.

In a first possible implementation manner, the target QoS parameter may be a set of QoS parameters corresponding to the target QoS flow in the first target. Exemplarily, the first terminal device may determine the target QoS flow from the multiple QoS flows, and then use the QoS parameter corresponding to the target QoS flow as the target QoS parameter.

The target QoS flow may be determined based on a certain QoS parameter of the multiple QoS flows in the first target.

Optionally, the target QoS flow may be: the QoS flow with the smallest priority among the multiple QoS flows included in the first target, or the QoS flow with the smallest PDB among the multiple QoS flows included in the first target, or the first target Among the multiple QoS flows included, the QoS flow with the smallest PER, or the QoS flow with the largest MDBV among the multiple QoS flows included in the first target, or the QoS flow with the maximum GFBR among the multiple QoS flows included in the first target, or the first The QoS flow with the largest MFBR among the multiple QoS flows included in the target, or the QoS flow with the largest PC5 link AMBR among the multiple QoS flows included in the first target, or the QoS flow with the largest range among the multiple QoS flows included in the first target Wait.

The target QoS flow may also be determined based on a plurality of QoS parameters of the plurality of QoS flows in the first target.

Optionally, the target QoS flow may be a QoS flow that satisfies at least two of the following among the multiple QoS flows included in the first target: minimum priority level, minimum PER, minimum PDB, and maximum MDBV.

In one example, if there are multiple QoS flows in the first target with the same and minimum priorities, the QoS flow with the smallest PDB, the smallest PER, or the largest MDBV among the multiple QoS flows may be determined as the target QoS flow.

For example, if QoS flow 1 and QoS flow 2 have the same and the smallest priority, and the PDB of QoS flow 1 is smaller than the PDB of QoS flow 2, then QoS flow 1 is finally determined as the target QoS flow.

In another example, if there are multiple QoS flows in the first target, the priority levels are the same and the smallest, and the PDBs are the same and the smallest, then the QoS flow with the smallest PER or the largest MDBV among the multiple QoS flows may be further determined as the target. QoS flow.

For example, if the priorities of QoS flow 1, QoS flow 2 and QoS flow 3 are the same and the smallest, and the PDBs are the same and the smallest, then the PER or MDBR of QoS flow 1, QoS flow 2 and QoS flow 3 can be further compared. For example, the QoS flow with the smallest PER among QoS flow 1, QoS flow 2 and QoS flow 3 may be used as the target QoS flow. For another example, among QoS flow 1, QoS flow 2 and QoS flow 3, the QoS flow with the smallest PER and the largest MDBV may be used as the target QoS flow.

In another example, if there are multiple QoS flows in the first target, the priority level is the same and the smallest, and the PER is the same and the smallest, then the QoS flow with the smallest PDB or the largest MDBV among the multiple QoS flows can be further determined as: Target QoS flow.

As another example, if there are multiple QoS flows in the first target, the priority levels are the same and the smallest, and the MDBVs are the same and the largest, then the QoS flow with the smallest PDB or the smallest PER among the multiple QoS flows may be further determined as Target QoS flow.

Similar to the above example, if there are multiple QoS flows in the first target, and the PER is the same and the smallest, the QoS flow with the smallest priority level, the QoS flow with the smallest PDB, or the QoS flow with the largest MDBV among the multiple QoS flows can be used. The QoS flow is determined as the target QoS flow.

For example, if the PER of QoS flow 1 and QoS flow 2 are the same and the smallest, and the priority level of QoS flow 1 is smaller than that of QoS flow 2, then QoS flow 1 is finally determined as the target QoS flow.

If there are multiple QoS flows in the first target and the PDBs are the same and the smallest, the QoS flow with the smallest priority, the QoS flow with the smallest PER, or the QoS flow with the largest MDBV among the multiple QoS flows can be determined as the target QoS flow.

For example, if the PDBs of QoS flow 1 and QoS flow 2 are the same and the smallest, and the priority level of QoS flow 1 is smaller than that of QoS flow 2, then QoS flow 1 is finally determined as the target QoS flow.

If there are multiple QoS flows in the first target, and the MDBV is the same and the largest, the QoS flow with the smallest priority, the QoS flow with the smallest PDB, or the QoS flow with the smallest PER among the multiple QoS flows can be determined as the target QoS flow.

For example, if the MDBV of QoS flow 1 and QoS flow 2 are the same and the largest, and the priority level of QoS flow 1 is smaller than that of QoS flow 2, then QoS flow 1 is finally determined as the target QoS flow.

Further, if there are multiple QoS flows in the first target, the PER is the same and the smallest, and the priority level is the same and the smallest, then the QoS flow with the smallest PDB or the largest MDBV among the multiple QoS flows can be determined as the target QoS flow. .

If there are multiple QoS flows in the first target, the PDBs are the same and the smallest, and the priorities are the same and the smallest, the QoS flow with the smallest PER or the largest MDBV among the multiple QoS flows may be determined as the target QoS flow.

If there are multiple QoS flows in the first target, the MDBV is the same and the largest, and the priority level is the same and the smallest, the QoS flow with the smallest PER or the smallest PDB among the multiple QoS flows may be determined as the target QoS flow.

If there are multiple QoS flows in the first target, the PER is the same and the smallest, the PDB is the same and the smallest, and the MDBV is the same and the largest, then the QoS flow with the smallest priority among the multiple QoS flows can be the target QoS flow.

Based on the above examples, more possible situations can also be deduced, which are not listed here for brevity.

It should be understood that the above examples are only shown for ease of understanding, and should not constitute any limitation to the present application. When determining the target QoS flow, the first terminal device may determine the target QoS flow according to one or more predefined QoS parameters. One or more of the predefined QoS parameters described here can be notified by the network device through signaling in advance (for example, RRC dedicated signaling, SIB message, pre-configuration message, etc.), or can be communicated with the first terminal device. The terminal equipment (for example, the second terminal equipment) that performs sidelink communication is notified in advance through signaling (for example, a PC5-RRC message, a PC5-S message, etc.), or it can also be predefined by a protocol, which is implemented in this application The example does not limit this.

In a second possible implementation manner, each QoS parameter in the target QoS parameters is selected from multiple groups of QoS parameters corresponding to multiple QoS flows included in the first target. Exemplarily, the first terminal device may, based on each item of QoS parameters, select one parameter from multiple groups of QoS parameters corresponding to multiple QoS flows as one item of the target QoS parameters.

If the QoS parameter corresponding to each QoS flow includes a PQI, the PQI in the target QoS parameter may be the minimum default priority level, or the minimum PDB, or The PQI with the smallest PER is determined as the PQI in the target QoS parameter.

In addition to PQI, other QoS parameters, such as GFBR, MFBR, PC5 link AMBR, range, MDBV, etc., can be selected from the QoS parameters corresponding to the multiple QoS flows, respectively.

For example, the maximum value of GFBR, the maximum value of MFBR, the maximum value of PC5 link AMBR, the maximum value of range, and the maximum value of MDBV in the multiple sets of QoS parameters corresponding to the multiple QoS flows may be determined as the target QoS parameters. GFBR, MFBR, PC5Link-AMBR, range, MDBV.

As mentioned above, if one or more of the QoS parameters (such as priority level, PDB, PER, GFBR, MFBR, PC5 link AMBR, range, and MDBV) in the multiple sets of QoS parameters or more) are included in both the PQI and the QoS parameters directly, that is, two values are configured for some QoS parameters. In this case, the value directly configured in the QoS parameters can be used to cover the same PQI corresponding The value of the item parameter. Then, when the target QoS parameter is determined, the PQI in the target QoS parameter can be selected according to the parameter not covered in the PQI. For example, if the default priority level in the PQI is overwritten, but the PDB, PER, default MDBV, default sliding window, and resource type are not overwritten, the multiple PQIs included in the multiple sets of QoS parameters can One or more parameters of PER, Default MDBV, and Default Sliding Window to select a PQI as the PQI in the target QoS parameters. For example, select the PQI with the smallest PDB, or select the PQI with the smallest PER, or select the PQI with the smallest PDB and PER, and so on. The QoS parameters not included in the PQI and the one or more parameters covered in the PQI can be selected from multiple groups of QoS parameters corresponding to multiple QoS flows included in the first target. For example, for the priority level, the priority level with the smallest priority level may be selected from the multiple groups of QoS parameters as the priority level in the target QoS parameter.

If the QoS parameters corresponding to each QoS flow do not include PQI, each parameter in the target QoS parameters may also be selected from multiple groups of QoS parameters corresponding to multiple QoS flows included in the first target.

For example, the minimum value of priority level, the minimum value of PER, the minimum value of PDB, the maximum value of GFBR, the maximum value of MFBR, the maximum value of AMBR of PC5 link, the maximum value of range , and the maximum value of MDBR is determined as the priority level, PER, PDB, GFBR, MFBR, PC5Link-AMBR, range, and MDBV in the target QoS parameters, respectively.

For example, the first target includes three QoS flows, namely QoS flow 1, QoS flow 2, and QoS flow 3. Among them, the default priority level in the PQI of QoS flow 1 is the smallest, the GFBR of QoS flow 2 is the largest, and the QoS flow 3 MFBR is the largest, the target QoS parameters may include: PQI of QoS flow 1, GFBR of QoS flow 2, and MFBR of QoS flow 3.

For another example, the first target includes four QoS flows, namely, QoS flow 1, QoS flow 2, QoS flow 3, and QoS flow 4. Among them, QoS flow 1 has the smallest priority level, QoS flow 2 has the smallest PDB, and QoS flow 2 has the smallest PDB. Flow 3 has the largest GFBR and QoS flow 14 has the largest MFBR. The target QoS parameters may include: priority level of QoS flow 1, PDB of QoS flow 2, GFBR of QoS flow 3, and MFBR of QoS flow 4. It can be seen that, in the second implementation manner, the target QoS parameters may be determined by synthesizing multiple groups of QoS parameters corresponding to multiple QoS flows in the first target.

It should be understood that the above is only for the convenience of understanding, and various parameters included in the target QoS parameter are exemplified in combination with different implementation manners, but this should not constitute any limitation to the present application. The embodiments of the present application include but are not limited to this.

From the above determination of target QoS parameters, it can be seen that in this embodiment of the present application, a set of target QoS parameters is determined for multiple QoS flows, for example, for one target address, multiple target addresses, or multiple QoS flows corresponding to one terminal device A set of target QoS parameters is determined so that DRX can be configured based on a larger granularity than QoS flows in subsequent determination of target DRX configuration. That is, the first terminal device can maintain a set of DRX configurations based on a larger granularity than QoS flows.

The granularity of one target address is smaller than that of multiple target addresses, and the granularity of multiple target addresses is smaller than that of one terminal device. Compared with configuring DRX based on multiple target addresses, configuring DRX based on one target address has higher implementation complexity; configuring DRX based on multiple target addresses is more complex than configuring DRX based on one terminal device. The implementation complexity is higher. In other words, as the granularity gradually increases, the implementation complexity gradually decreases.

It should be noted that, for the case where the first target includes only one QoS flow, since one QoS flow may correspond to a group of QoS parameters, the group of QoS flows is the target QoS parameter of the first target. The first terminal device may also determine the target DRX configuration according to the process described in steps 720 to 740 below, and perform sidelink communication based on the target DRX configuration.

In step 720, a target DRX configuration is determined based on the first mapping relationship and the target QoS parameters.

The first mapping relationship may be used to indicate the corresponding relationship between the QoS parameter and the DRX configuration.

In this embodiment of the present application, the corresponding relationship between the QoS parameters and the DRX configuration may be, for example, the corresponding relationship between at least one group of QoS parameters and at least one DRX configuration. One DRX configuration may correspond to one set of QoS parameters, or may correspond to multiple sets of QoS parameters.

It should be noted that, in the correspondence between the QoS parameters indicated by the first mapping relationship and the DRX configuration, the QoS parameters corresponding to the target DRX configuration may be a subset of the above-mentioned target QoS parameters.

For example, the target QoS parameter may be the same as the set of QoS parameters in the first mapping relationship. For example, the target QoS parameters include PQI, priority level, PER, PDB, MDBV, and GFBR, and the set of QoS parameters indicated in the first mapping relationship includes PQI, priority level, PER, PDB, MDBV, and GFBR.

For another example, the target QoS parameters may include a group of QoS parameters in the first mapping relationship, or in other words, the group of QoS parameters in the first mapping relationship may be part of the parameters in the target QoS parameters. For example, the target QoS parameters include PQI, priority level, PER, PDB, MDBV, GFBR, MFBR, and the set of QoS parameters indicated in the first mapping relationship includes priority level, PER, PDB, MDBV, and GFBR.

It should be understood that whether the target QoS parameter may be the same as a group of QoS parameters in the first mapping relationship, or the target QoS parameter may include a group of QoS parameters in the first mapping relationship, it can be considered that the first mapping relationship can be found in the first mapping relationship. A set of QoS parameters matches the target QoS parameters, that is, the target DRX configuration corresponding to the target QoS parameters can be found.

It should also be understood that when there are multiple sets of QoS parameters in the first mapping relationship, all of which are subsets of the target QoS parameters, the same set of QoS parameters as the target QoS parameters may be preferentially selected to determine the target DRX configuration.

Hereinafter, "matching" may mean that in at least one group of QoS parameters indicated by the first mapping relationship, there is a group of QoS parameters that is a subset of the above-mentioned target QoS parameters. That is, the target QoS parameter is the same as a group of QoS parameters in the first mapping relationship, or the target QoS parameter includes a group of QoS parameters in the first mapping relationship. In contrast, "mismatch" may mean that any set of QoS parameters in the first mapping relationship is not a subset of the above-mentioned target QoS parameters.

In this embodiment of the present application, the first mapping relationship may be determined by the first terminal device itself, may also be received from other devices, or may be received from an upper layer of the first terminal device.

Optionally, before step 720, the method further includes: the first terminal device receives first indication information, where the first indication information is used to indicate the first mapping relationship.

A first possible situation is that the first indication information may be received from a network device. The foregoing first terminal device receiving the first indication information may specifically include: the first terminal device receiving the first indication information from the network device.

Exemplarily, the first indication information may be carried in, for example, a radio resource control (radio resource control, RRC) message, a system information block (system information block, SIB) message, or a preconfiguration message. When the first terminal device is in the RRC connection state, the first indication information may be carried in the RRC message received from the network device. When the first terminal device is in the RRC idle state or the inactive state, the first indication information may be carried in the SIB message received from the network device. When the first terminal device is in an out-of-coverage (OOC) state, the first at least information may be carried in a pre-configuration message received from the network device

The second possible situation is that the first indication information may be received from other terminal devices. For example, the first terminal device obtains the first indication information by receiving a PC5-RRC message or a PC5-S message sent by the opposite end (second terminal device), where the first indication information is used to indicate the first mapping relationship. Correspondingly, the second terminal device sends the first indication information.

The second terminal device may configure the first mapping relationship by itself, and send the configured first mapping relationship to the first terminal device. Optionally, the first terminal device is a receiving terminal device, and the second terminal device is an originating terminal device.

A third possible situation is that the first indication information may be received by the access layer of the first terminal device from an upper layer (eg, a V2X or PC5-S layer). The above-mentioned first terminal device receiving the first indication information may specifically include: the access layer of the first terminal device receives the first indication information from the upper layer, where the first indication information is used to indicate the first mapping relationship.

The upper layer of the first terminal device may configure the first mapping relationship by itself, and deliver the configured first mapping relationship to the AS layer.

It should be understood that the several manners in which the first terminal device obtains the first indication information listed above are only examples, and should not constitute any limitation to the present application.

In addition to the DRX configurations corresponding to different QoS parameters indicated in the first mapping relationship, the target DRX configuration may also be a default (default) DRX configuration or a common (common) DRX configuration. In the case of using the default DRX configuration or the public DRX configuration, it can be considered that the target DRX configuration is not associated with QoS parameters.

A possible situation is that the first terminal device does not find a corresponding relationship matching the target QoS parameter from the first mapping relationship. In this case, the first terminal device may use the default DRX configuration or the public DRX configuration as the target DRX configuration.

Of course, using the default DRX configuration or the public DRX configuration as the target DRX configuration is not limited to the above case. For example, the following method 1000 shows the case of using the default DRX configuration or the common DRX configuration during the establishment of the direct communication.

In this embodiment of the present application, the target DRX configuration corresponds to the first target. As mentioned above, the first target may include a target address, multiple target addresses, or a terminal device. In other words, the target DRX configuration may correspond to one target address, or multiple target addresses or one terminal device.

Specifically, when the target DRX configuration corresponds to a target address, multiple QoS flows in the target address can all perform sidelink communication based on the target DRX configuration. In other words, the DRX configurations of multiple QoS flows on the sidelink corresponding to the same target address are the same.

When the target DRX configuration corresponds to multiple target addresses, multiple QoS flows in the target addresses can all perform sidelink communication based on the target DRX configuration. In other words, the DRX configurations of multiple QoS flows corresponding to multiple destination addresses on the sidelink are the same.

When the target DRX configuration corresponds to the first terminal device, multiple QoS flows in all target addresses of the first terminal device may perform sidelink communication based on the target DRX configuration. In other words, the DRX configurations of the multiple QoS flows corresponding to the first terminal device on the sidelink are the same.

Based on the determination of the target DRX configuration above, the first terminal device can configure the same DRX for multiple QoS flows in the first target, so that multiple QoS flows in the first terminal device can be enabled based on the same DRX configuration and closing the radio frequency channel, so that the switching frequency of the first terminal device between on and off of the radio frequency channel can be avoided to a certain extent, the processing complexity is reduced, and the energy is saved. Moreover, since the target DRX configuration is determined based on the target QoS parameters, and the target QoS parameters are determined based on multiple sets of QoS parameters corresponding to the above-mentioned first target, the determined target DRX configuration can meet the QoS requirements to a certain extent, This enables the first terminal device to have better QoS performance.

In step 730, the first terminal device performs sidelink communication based on the target DRX configuration.

It should be understood that for the first terminal device, communication may include sending or receiving. In other words, the first terminal device may be an originating terminal device or a receiving terminal device. This embodiment of the present application does not limit this.

Exemplarily, the first terminal device may perform sidelink communication with the second terminal device based on the target DRX configuration.

When the first terminal device is an originating terminal device, the second terminal device may be a receiving terminal device that performs unicast communication with the first terminal device, or may be a group of receiving terminal devices that perform multicast communication with the first terminal device One of the devices may also be a receiving terminal device in the communication system that receives the broadcast service.

When the first terminal equipment is a receiving terminal equipment, the first terminal equipment may be a receiving terminal equipment that performs unicast communication with the second terminal equipment, or may be a group of receiving terminal equipment that performs multicast communication with the second terminal equipment. One of the end terminal devices may also be a receiving end terminal device in the communication system that receives the broadcast service of the second terminal device.

Optionally, before step 730, the method 700 further includes: step 740, the first terminal device sends the target DRX configuration to the second terminal device. Accordingly, the second terminal device receives the target DRX configuration.

For example, the first terminal device may send the target DRX configuration to the second terminal device through signaling such as PC5-S, PC5-RRC, SL MAC layer control element (control element, CE), and SL-SIB. The target DRX configuration may be sent, for example, in a unicast, multicast or broadcast manner. This embodiment of the present application does not limit the signaling carrying the target DRX configuration and the manner of sending the signaling.

Thus, the first terminal device and the second terminal device can perform sidelink communication based on the same DRX configuration (ie, the target DRX configuration). The two can send and receive at the same time, close the RF channel at the same time, and stop sending and receiving. Thus, the reliability of transmission can be guaranteed, thereby ensuring better QoS performance.

In this embodiment of the present application, the first terminal device may determine the target QoS parameters according to multiple sets of QoS parameters corresponding to the first target, and then determine the target DRX configuration according to the target QoS parameters and the corresponding relationship between the QoS parameters and the DRX configuration. Thus, multiple QoS flows in the first target can all perform sidelink communication based on the DRX configuration. In this way, multiple QoS flows in the first terminal device can open and close the radio frequency channel based on the same DRX configuration, so that the switching frequency of the first terminal device between on and off of the radio frequency channel can be avoided to a certain extent, Reduce processing complexity and save energy. Moreover, since the target DRX configuration is determined based on the target QoS parameters, and the target QoS parameters are determined based on multiple sets of QoS parameters corresponding to the above-mentioned first target, the determined target DRX configuration can meet the QoS requirements to a certain extent, This enables the first terminal device to have better QoS performance, thereby achieving a balance between QoS performance and energy saving.

In addition to the DRX configuration method described above in conjunction with FIG. 7 , an embodiment of the present application further provides a DRX configuration method. In this method, the first terminal device can determine the target DRX configuration based on the target service, so as to provide a more flexible configuration manner for the DRX configuration. The method will be described below in conjunction with the FIG. 8 pair.

FIG. 8 is a schematic flowchart of a DRX configuration method provided by another embodiment of the present application. The method 800 shown in FIG. 8 shows the flow of DRX configuration based on the mapping relationship between services and DRX configuration.

As shown in FIG. 8 , the method 800 is implemented based on the mapping relationship between services and DRX, and may include steps 810 to 840 . Each step in the method 800 will be described in detail below.

In step 810, a target service is determined based on multiple sets of QoS parameters corresponding to the first target.

The first target includes: one target address, multiple target addresses (also referred to as a group of target addresses), or a terminal device (eg, a first terminal device).

The multiple destination addresses may specifically refer to multiple destination addresses of a terminal device, for example, may be part of all destination addresses of the terminal device. Therefore, the multiple target addresses corresponding to the first target may specifically refer to a partial target address corresponding to a terminal device by the first target.

Based on the above description of the relationship between the target address and the QoS flow, it can be known that the first target may include one or more QoS. In this embodiment of the present application, the first target includes multiple QoS flows. The multiple QoS flows may be multiple QoS flows in one target address, multiple QoS flows in multiple destination addresses, or multiple QoS flows in one terminal device. Based on the above-mentioned relationship between the first target and QoS flow and the corresponding relationship between QoS flow and QoS parameters, it can be known that the multiple groups of QoS parameters corresponding to the first target may be multiple groups corresponding to multiple QoS flows included in one target address. QoS parameters, or multiple sets of QoS parameters corresponding to multiple QoS flows included in multiple target addresses, or multiple sets of QoS parameters corresponding to multiple QoS flows in the first terminal device.

Thus, the first target may be a collective term for multiple QoS flows. In another formulation, the first target may be replaced by a plurality of QoS flows. Step 810 can also be expressed as: the first terminal device determines the target service based on multiple sets of QoS parameters corresponding to multiple QoS flows.

The first terminal device may first acquire information of multiple QoS flows in the first target, and then determine the target service based on multiple sets of QoS parameters corresponding to the multiple QoS flows.

The first terminal device may determine the target service in the following manner.

In an implementation manner, the upper layer of the first terminal device may send information of multiple QoS flows included in the first target to the access layer, and the access layer may determine the target according to multiple sets of QoS parameters corresponding to the multiple QoS flows business. The information of the multiple QoS flows is used to indicate the multiple QoS flows.

In another implementation manner, the first terminal device may obtain multiple groups of QoS corresponding to multiple QoS flows included in the first target through a PC5-RRC message or a PC5-S message sent by the opposite terminal (eg, the second terminal device). parameters, and then determine the target service according to the multiple groups of QoS parameters. Optionally, the first terminal device is a receiving terminal device, and the second terminal device is an originating terminal device.

In yet another implementation manner, the first terminal device may obtain the target service corresponding to the first target through the PC5-RRC message or the PC5-S message sent by the opposite end (eg, the second terminal device). In other words, the target service corresponding to the first target may be determined by the second terminal device. Optionally, the first terminal device is a receiving terminal device, and the second terminal device is an originating terminal device.

Exemplarily, the first terminal device may determine the target service based on one or more of the following QoS parameters: priority level, PER, PDB, MDBV, GFBR, MFBR, PC5 link AMBR, range, and PQI.

In a possible implementation manner, the first terminal device may select the service corresponding to the target QoS flow as the target service.

For example, the first target includes business 1, business 2, and business 3. If the priority level of a certain QoS flow in service 1 is the smallest QoS flow among the multiple QoS flows included in service 1, 2, and 3, this service 1 can be determined as the target service.

For example, the first target includes business 1, business 2, and business 3. There are multiple QoS flows in service 1 and service 2, and the priority is the same and the smallest, but the PER of one QoS flow in service 1 is smaller than the PER of any QoS flow in service 2, then service 1 can be determined as The target business of the first target.

For another example, the first target includes business 1, business 2, and business 3. There are multiple QoS flows in service 2 and service 3, and the PER is the same and the smallest, but the priority level of a QoS flow in service 2 is smaller than that of any QoS flow in service 3, the service can be 2. Determine the target business as the first target.

The first terminal device may determine the target service based on the target QoS flow. The target service may be the service corresponding to the target QoS flow, or in other words, the target service may be the service to which the target QoS flow belongs. Taking the relationship between the service and QoS flow shown in Figure 4 as an example, assuming that the target QoS flow is QoS flow 1 in Figure 4, the target service is Service 1; assuming that the target QoS flow is QoS flow 7 in Figure 4, then the target Business is business 3.

From the determination of the target service above, it can be seen that in this embodiment of the present application, a target service is determined based on multiple sets of QoS parameters corresponding to multiple QoS flows, for example, based on one target address, multiple target addresses, or multiple The group QoS parameter determines a target service, so that the DRX can be configured based on a larger granularity than the QoS flow when the target DRX configuration is subsequently determined. That is, the first terminal device can maintain a set of DRX configurations based on a larger granularity than QoS flows.

It should be noted that, for the case where the first target includes only one QoS flow, since the QoS flow is included in the service, the service is the target service of the first target. The first terminal device may also determine the target DRX configuration according to the procedures described in steps 820 to 840 below, and perform sidelink communication based on the target DRX configuration.

In step 820, a target DRX configuration is determined based on the second mapping relationship and the target service.

The second mapping relationship may be used to indicate the corresponding relationship between the service and the DRX configuration.

As an example and not a limitation, the second mapping relationship may be specifically used to indicate the corresponding relationship between the service type and the DRX configuration. Correspondingly, the target DRX configuration determined based on the second mapping relationship and the target service is the DRX configuration corresponding to the service type of the target service.

The service type may be specifically identified by, for example, PSID or ITS-AID. Therefore, the second mapping relationship may specifically be the corresponding relationship between the PSID and the DRX configuration, or may also be the corresponding relationship between the ITS-AID and the DRX configuration.

In this embodiment of the present application, the second mapping relationship may be determined by the first terminal device itself, may also be received from other devices, or may be received from an upper layer of the first terminal device. This embodiment of the present application does not limit this.

Optionally, before step 820, the method further includes: the first terminal device receives second indication information, where the second indication information is used to indicate the second mapping relationship.

A first possible situation is that the second indication information may be received from a network device. The foregoing first terminal device receiving the second indication information may specifically include: the first terminal device receiving the second indication information from the network device, where the second indication information is used to indicate the second mapping relationship. Correspondingly, the second terminal device sends the second indication information.

Exemplarily, the second indication information may be carried in, for example, an RRC message, an SIB message, or a pre-configuration message. When the first terminal device is in the RRC connection state, the second indication information may be carried in the RRC message received from the network device. When the first terminal device is in the RRC idle state or the deactivated state, the second indication information may be carried in the SIB message received from the network device. When the first terminal device is in the OOC state, the second indication information may be carried in the pre-configuration message received from the network device.

The second possible situation is that the first indication information may be received from the second terminal device. The above-mentioned first terminal device receiving the second indication information may specifically include: the first terminal device receiving the second indication information from the opposite end (eg, the second terminal device), where the second indication information is used to indicate the second mapping relationship. Correspondingly, the second terminal device sends the second indication information.

The second terminal device may configure the second mapping relationship by itself, and send the configured second mapping relationship to the first terminal device. Optionally, the first terminal device is a receiving terminal device, and the second terminal device is an originating terminal device.

A third possible situation is that the second indication information may be received by the access layer of the first terminal device from the upper layer. The above-mentioned first terminal device receiving the second indication information may specifically include: the access layer of the first terminal device receives the second indication information from the upper layer, where the first indication information is used to indicate the first mapping relationship.

The V2X layer of the first terminal device can configure the second mapping relationship by itself, and deliver the configured second mapping relationship to the access layer.

In addition to the DRX configurations corresponding to different services indicated in the second mapping relationship, the target DRX configuration may also be a default DRX configuration or a common DRX configuration. In the case of using the default DRX configuration or the public DRX configuration, it can be considered that the target DRX configuration is not associated with services.

A possible situation is that the first terminal device does not find a corresponding relationship matching the target service from the second mapping relationship. In this case, the first terminal device may use the preconfigured default DRX configuration or the public DRX configuration as the target DRX configuration.

In this embodiment of the present application, the target DRX configuration corresponds to the first target. For the corresponding relationship between the target DRX configuration and the first target, reference may be made to the detailed description in the above block 700, which is not repeated here for brevity.

In step 830, the first terminal device sends the target DRX configuration to the second terminal device. Accordingly, the second terminal device receives the target DRX configuration.

In step 840, the first terminal device performs sidelink communication based on the target DRX configuration.

It should be understood that, for steps 830 and 840, reference may be made to the relevant descriptions of steps 740 and 730 in the above method 700, and for brevity, details are not repeated here.

In this embodiment of the present application, the first terminal device may determine the target service according to multiple sets of QoS parameters corresponding to the first target, and then determine the target DRX configuration according to the target service and the corresponding relationship between the service and the DRX configuration. Thus, multiple QoS flows in the first target can all perform sidelink communication based on the DRX configuration. In this way, multiple QoS flows in the first terminal device can open and close the radio frequency channel based on the same DRX configuration, so that the switching frequency of the first terminal device between on and off of the radio frequency channel can be avoided to a certain extent, Reduce processing complexity and save energy. Moreover, since the target DRX configuration is determined based on the target QoS parameters, and the target QoS parameters are determined based on multiple sets of QoS parameters corresponding to the above-mentioned first target, the determined target DRX configuration can meet the QoS requirements to a certain extent, This enables the first terminal device to have better QoS performance, thereby achieving a balance between QoS performance and energy saving.

The specific process of DRX configuration for sidelink communication is described in detail above with reference to FIG. 7 and FIG. 8 . However, in some cases, QoS parameters or service types may not be available. For example, before the direct communication is established, the terminal device may not have been configured with QoS parameters or service types.

FIG. 9 shows the direct connection communication establishment flow. FIG. 9 shows a specific flow of establishing direct communication between the first terminal device and the second terminal device. It should be understood that the direct connection communication establishment procedure is used for the establishment of unicast communication.

In step 910, the first terminal device sends a direct communication request (direct communication request, DCR) message to the second terminal device. The second terminal device receives the DCR message.

In step 920, in response to the DCR message, the second terminal device sends a direct security mode command message to the first terminal device. The first terminal device receives the security establishment command message.

In step 930, the first terminal device sends a direct security mode complete message to the second terminal device.

In step 940, the second terminal device sends a direct command accept message to the first terminal device.

Thus, a unicast connection is established between the first terminal device and the second terminal device. In the PC5-S message or PC5-RRC message listed in the above process, there is no directly corresponding QoS parameter or service type. In the case where QoS parameters or service types are not configured, the first terminal device may not be able to determine the target DRX configuration based on the first mapping relationship or the second mapping relationship described above to determine the unicast configuration for the unicast The target DRX configuration for the connection. That is to say, the DRX configuration may not be aligned between the terminal devices that establish the unicast connection before the unicast DRX negotiation is completed, which may cause the above message not to be received, which will lead to the failure of the unicast connection establishment and the unicast connection configuration. failure, which ultimately affects the communication quality of the sidelink.

In view of this, an embodiment of the present application also provides a DRX configuration method, so as to align the DRX configuration between terminal devices that need to establish direct communication without configuring QoS parameters or service types.

The DRX configuration method provided by the embodiment of the present application will be described below with reference to FIG. 10 . It should be understood that although the embodiment shown in FIG. 10 shows the process of the first terminal device executing the DRX configuration method, this should not constitute any limitation to the present application. The second terminal device may also be used to execute the following DRX configuration method, which is not limited in this embodiment of the present application.

FIG. 10 is a schematic flowchart of a DRX configuration method provided by another embodiment of the present application. As shown in FIG. 10 , the method 1000 may include steps 1010 to 1030 .

In step 1010, the first terminal device acquires one or more DRX configurations.

For example, the first terminal device may obtain one or more DRX configurations through an RRC message, or a SIB message, or a pre-configuration message, or a PC5-RRC message, or a PC5-S message, or an upper layer or protocol definition of the terminal device. The one or more DRX configurations may be understood as one or more pre-configured optional DRX configurations, and the first terminal device may determine an appropriate DRX configuration based on this for the current direct connection communication establishment procedure.

Optionally, the method 1000 specifically includes: the first terminal device acquires a first mapping relationship or a second mapping relationship, where the first mapping relationship or the second mapping relationship is used to indicate one or more DRX configurations.

As mentioned above, the first mapping relationship may be used to indicate the corresponding relationship between the QoS parameters and the DRX configuration, and the second mapping relationship may be used to indicate the corresponding relationship between the service and the DRX configuration. The first terminal device acquires the first mapping relationship, that is, the first terminal device acquires the corresponding relationship between the QoS parameter and the DRX configuration. The first terminal device acquires the second mapping relationship, that is, the second terminal device acquires the correspondence between the service and the DRX configuration. Based on the acquisition of the first mapping relationship or the second mapping relationship, the first terminal device may acquire the above-mentioned one or more DRX configurations.

In step 1020, the first terminal device determines the first DRX configuration corresponding to the first message.

The first message may be any PC5-S message or PC5-RRC message before the DRX configuration negotiation is completed. For example, the first message may include one or more of the following messages: a direct connection communication request message, a direct connection security establishment command message, a direct connection security establishment completion message, a direct connection communication acceptance message, and a device discovery (discovery) process. The announcement message, the solicitation message in the device discovery process, the response message to the inquiry message in the device discovery process, the UE Capability Enquiry Sidelink message, the UE capability notification side downlink (UECapabilityInformationSidelink) message, the first RRC Reconfiguration Sidelink (RRCReconfigurationSidelink) message after the establishment of direct communication between the first terminal device and the second terminal device, the first terminal device and the second terminal device The first RRC reconfiguration complete sidelink (RRCReconfigurationCompleteSidelink) message after the direct connection communication is established between the terminal devices.

It should be understood that the first RRCReconfigurationSidelink message or the first RRCReconfigurationCompleteSidelink message sent or received by the first terminal equipment involved in the following may specifically refer to the first RRCReconfigurationSidelink after the first terminal equipment establishes direct communication with the second terminal equipment. message or the first RRCReconfigurationCompleteSidelink message.

It can be understood that "direct connection communication" can also be replaced with "unicast connection". The first terminal device may determine the first DRX configuration corresponding to the first message through the following five possible implementation manners:

method one,

The first terminal device may first determine the QoS parameter (or service type) corresponding to the first message, and then may further determine its corresponding first SL DRX configuration according to the QoS parameter (or service type) corresponding to the first message. In other words, the first DRX configuration may correspond to the QoS parameter (or service type) corresponding to the first message.

Exemplarily, the QoS parameter (or service type) corresponding to the first message may be predefined by a protocol, or may also be received from a network device, such as an RRC message, SIB message, or pre-configuration message, etc., or may be received from the first terminal. The upper layer of the device can also receive it from the first terminal device at the opposite end, such as through a PC5RRC message or a PC5-S message. It can be understood that the QoS parameters (or service types) corresponding to different first messages may be different. For example, the QoS parameters (or service types) corresponding to the DCR message and the security setup command message are different.

For the specific process of determining the first DRX configuration based on the QoS parameter (or service type) corresponding to the first message, for example, reference may be made to the embodiments shown above in conjunction with FIG. 7 or FIG. 8 , that is, the first terminal device may correspond to the first message based on The first DRX configuration is determined based on the QoS parameters corresponding to the first message and the first mapping relationship, or the first DRX configuration may also be determined based on the service type corresponding to the first message and the second mapping relationship. For brevity, the specific process is not repeated here.

Optionally, the first DRX configuration is a DRX configuration corresponding to multicast or broadcast. That is, the first DRX configuration can also be used for multicast communication or broadcast communication.

Method two,

The first terminal device determines the default DRX configuration or the common DRX configuration as the first DRX configuration.

Exemplarily, each resource pool may include a corresponding default DRX configuration or a common DRX configuration, and the first terminal device may use the corresponding default DRX configuration or common DRX configuration in the resource pool to send or receive the first message.

It can be understood that using the default DRX configuration or the common DRX configuration to send or receive the first message may specifically refer to using the resources corresponding to the default DRX configuration or the common DRX configuration to send or receive the first message. Here, the resources corresponding to the default DRX configuration or the common DRX configuration may specifically refer to resources used for transmission or reception on the sidelink. The resources corresponding to the default DRX configuration or the public DRX configuration may be, for example, the DRX resources shown in FIG. 6 , or may also be the resources corresponding to the on time shown in FIG. 5 . It can be understood that this resource is a part of the resource in the resource pool.

Optionally, after sending or receiving the direct connection communication request message, the first terminal device may trigger to use the default DRX configuration or the public DRX configuration to send or receive the first message. Further optionally, when the first terminal device is configured by an upper layer to allow sending or receiving of the direct connection communication request message, it may trigger to use the default DRX configuration or the public DRX configuration to send or receive the first message. Further optionally, when the first terminal device is interested in the target layer 2 identifier of the first message or the service corresponding to the target layer 2 identifier, it can trigger to use the default DRX configuration or the public DRX configuration to send the first message or take over. It should be understood that the service corresponding to the target layer 2 identifier may be determined according to the previously described mapping relationship between the pre-configured V2X service type and the layer 2 identifier. Hereinafter, descriptions of the same or similar situations are omitted for brevity.

Optionally, after sending or receiving the first RRCReconfigurationSidelink message, or after the first terminal device completes the unicast SL DRX configuration negotiation, the first terminal device may trigger to stop using the default DRX configuration or the public DRX configuration to perform the first The sending or receiving of messages.

Optionally, the first terminal device starts the first timer in the case of sending or receiving the direct connection communication request message, and the first terminal device uses the default DRX configuration or the public DRX configuration when the first timer runs. For sending or receiving the first message, the first terminal device stops sending or receiving the first message using the default DRX configuration or the common DRX configuration when the first timer expires or stops running. The first timer may be predefined by a protocol, or configured by a network device, or configured by other terminal devices (such as a second terminal device).

Optionally, the first terminal device may start or restart the first timer each time a direct connection communication request message is sent or received.

Optionally, the first terminal device may stop the first timer every time the first RRCReconfigurationSidelink message is sent or received.

Method three,

The first terminal device determines the dedicated DRX configuration as the first SL DRX configuration.

Exemplarily, each resource pool may include a corresponding dedicated DRX configuration, which may be dedicated to the transmission of the first message. In other words, the first terminal device may use the corresponding dedicated DRX configuration in the resource pool to send or receive the first message.

It can be understood that using the dedicated DRX configuration to send or receive the first message may specifically refer to using the DRX resource corresponding to the dedicated DRX configuration to send or receive the first message. Here, the resources corresponding to the dedicated DRX configuration may specifically refer to resources used for transmission or reception on the sidelink. The resources corresponding to the dedicated DRX configuration may be, for example, the DRX resources shown in FIG. 6 , or may also be the resources corresponding to the on time shown in FIG. 5 . It can be understood that this resource is a part of the resource in the resource pool.

Optionally, after sending or receiving the unicast connection establishment request message, the first terminal device may trigger the use of the dedicated DRX configuration to send or receive the first message. Further optionally, in the case that the first terminal device is configured by an upper layer to allow sending or receiving of the direct connection communication request message, the first terminal device may trigger the use of a dedicated DRX configuration to send or receive the first message. Further optionally, when the first terminal device is interested in the target layer 2 identifier of the first message or the service corresponding to the target layer 2 identifier, the first terminal device may trigger the use of the dedicated DRX configuration to send or receive the first message.

Optionally, after the first terminal device sends or receives the first RRCReconfigurationSidelink message, or after the first terminal device completes the unicast SL DRX configuration negotiation, triggers to stop using the dedicated DRX configuration to send or receive the first message. .

Optionally, in the case of sending or receiving a direct connection communication request message, the first terminal device starts a first timer, and the first terminal device uses the dedicated DRX configuration to perform the first message at the moment when the first timer runs. For sending or receiving, the first terminal device stops sending or receiving the first message by using the dedicated DRX configuration when the first timer expires or stops running. The first timer may be predefined by a protocol, or configured by a network device, or configured by other terminal devices (such as a second terminal device).

Optionally, the first terminal device may start or restart the first timer every time it sends or receives a unicast connection establishment request message.

Method four,

The first terminal device may determine the DRX configuration with the highest QoS requirement among the one or more DRX configurations acquired by the first terminal device in step 1010 as the first DRX configuration. In other words, the first DRX configuration is a DRX configuration with the highest QoS requirement among one or more DRX configurations obtained in advance.

The highest QoS requirement may include, for example, one or more of the following: minimum priority level, minimum PER, minimum PDB, and maximum MDBV.

That is, the first DRX configuration may be a DRX configuration corresponding to a group of QoS parameters with the highest QoS requirement among one or more groups of QoS parameters corresponding to multiple DRX configurations. The QoS parameters corresponding to each DRX configuration may be determined according to the first mapping relationship described above.

Exemplarily, the first DRX configuration is one or more sets of QoS parameters corresponding to one or more DRX configurations included in the resource pool corresponding to the first message sending or receiving, and the set of QoS parameters with the highest QoS requirements corresponds to the one or more sets of QoS parameters. DRX configuration.

For example, the first terminal device may acquire the above-mentioned one or more DRX configurations in step 1010, for example, acquire the one or more DRX configurations by acquiring the first mapping relationship. Since the specific manner of acquiring the DRX configuration has been described in detail in step 1010, for the sake of brevity, details are not repeated here.

It should be noted that the resource pool corresponding to the sending or receiving of the first message may refer to a sending resource pool selected by the first terminal device for sending the first message or a receiving resource pool for receiving the first message. This application does not limit the specific manner in which the first terminal device selects the resource pool. Hereinafter, descriptions of the same or similar situations are omitted for brevity.

Method five,

The first terminal device determines the union of one or more DRX configurations acquired by the first terminal device in step 1010 as the first DRX configuration. In other words, the first DRX configuration may be a union of one or more DRX configurations obtained in advance.

Exemplarily, the first SL DRX configuration is a union of multiple DRX configurations included in the corresponding resource pool for sending or receiving the first message. It can be understood that the first terminal device may send or receive the first message on each resource corresponding to multiple DRX configurations included in the corresponding resource pool.

In step 1030, the first terminal device sends or receives the first message based on the first DRX configuration.

The first terminal device sends or receives the first message on the sidelink resource corresponding to the first DRX configuration.

Exemplarily, the first terminal device may send or receive the first message with the second terminal device based on the target DRX configuration.

It should be understood that after the unicast connection establishment procedure is completed, the first terminal device may determine a target DRX configuration for sidelink communication based on the DRX configuration method in method 700 or method 800 provided above.

In the embodiment of the present application, in the direct connection communication establishment stage, the first terminal device may first determine the first DRX configuration corresponding to the first message in this stage, and then send or receive the first message based on the first DRX configuration, Therefore, the terminal devices that establish the unicast connection can align the DRX configuration before completing the unicast DRX negotiation, so that the unicast connection can be successfully established and provide support for the subsequent sidelink communication, which is conducive to improving the sidelink chain. communication quality of the road.

It should be understood that, in the above-mentioned embodiments of the present application, the methods provided in the embodiments of the present application are described from the perspective of interaction between the first terminal device and the second terminal device and the perspective of the interaction between the first terminal device and the network device. introduce. In order to implement the functions in the methods provided by the above embodiments of the present application, the network device and the terminal device may include hardware structures and/or software modules, and implement the above functions in the form of hardware structures, software modules, or hardware structures plus software modules . Whether one of the above functions is performed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

Hereinafter, the communication apparatus provided by the embodiments of the present application will be described in detail with reference to FIG. 11 to FIG. 13 .

FIG. 11 is a schematic block diagram of a communication apparatus 1100 provided by an embodiment of the present application. It should be understood that the communication apparatus 1100 may correspond to the first terminal device or the second terminal device in the above method embodiments, and may be used to execute various steps performed by the first terminal device or the second terminal device in the above method embodiments.

As shown in FIG. 11 , the communication apparatus 1100 may include a transceiver module 1110 and a processing module 1120 .

Optionally, the apparatus 1100 may correspond to the first terminal device in the embodiments shown in FIG. 7 , FIG. 8 and FIG. 10 , and may include modules of the method executed by the first terminal device.

Specifically, when the apparatus 1100 is used to perform the method performed by the first terminal device in FIG. 7 , the transceiver module 1110 can be used to perform steps 730 and 740 in the above method 700 . The processing module 1120 may be used to perform steps 710 and 720 in the method 700 .

Exemplarily, the transceiver module 1110 may be configured to determine target QoS parameters based on multiple groups of QoS parameters corresponding to the first target; the first target includes multiple QoS flows; and determine the target DRX configuration based on the first mapping relationship and the target QoS parameters , the first mapping relationship is used to indicate the corresponding relationship between the QoS parameter and the DRX configuration; the transceiver module 1110 can be used to perform sidelink communication based on the target DRX configuration.

Optionally, the first target includes: one target address, multiple target addresses or terminal devices.

Optionally, the processing module 1120 may be configured to determine the target QoS parameter according to one or more of the following QoS parameters: priority level, PER, PDB, MDBV, GFBR, MFBR, PC5 link AMBR, range, and PQI , wherein the PQI is used to indicate the following QoS parameters: default priority level, PDB, PER, MDBV, GFBR, MFBR, default AMBR and default sliding window.

In a first possible implementation manner, the target QoS parameter is a set of QoS parameters corresponding to the target QoS flow in the first target; the target QoS flow is one of the multiple QoS flows included in the first target, The QoS flow with the smallest priority, or the QoS flow with the smallest PER, or the QoS flow with the smallest PDB, or the QoS flow with the largest MDBV.

Optionally, the target DRX configuration is a default DRX configuration or a public DRX configuration.

Optionally, the transceiver module 1110 is further configured to receive first indication information, where the first indication information is used to indicate the first mapping relationship.

A first possible situation is that the first indication information is sent by a network device. The transceiver module 1110 may be configured to receive the first indication information from the network device.

The second possible situation is that the first indication information is sent by the second terminal device. The transceiver module 1110 may be configured to receive the first indication information from the second terminal device.

A third possible situation is that the first indication information is sent by the upper layer of the apparatus 1100 to the access layer. The transceiver module 1110 may be configured at the access layer of the device 1100 , and may be specifically configured to receive the first indication information from the upper layer of the device 1100 .

Optionally, the transceiver module 1110 can also be used to send the target DRX configuration.

When the apparatus 1100 is used to perform the method performed by the first terminal device in FIG. 8 , the transceiver module 1110 can be used to perform steps 830 and 840 in the above method 800 . The processing module 1120 can be used to perform steps 810 and 820 in the method 800 .

Exemplarily, the processing module 1120 may be configured to determine target services based on multiple sets of QoS parameters corresponding to the first target, where the first target includes one or more services, and each service includes one or more QoS flows; the processing module 1120 is further configured to determine a target DRX configuration based on a second mapping relationship and the target service, where the second mapping relationship is used to indicate a corresponding relationship between a service and a DRX configuration, and the target DRX configuration corresponds to the first target; The transceiver module 1110 may implement sidelink communication based on the target DRX configuration.

Optionally, the second mapping relationship is specifically used to indicate the corresponding relationship between the service type and the DRX configuration; the processing module 1120 can be specifically used to realize the service type based on the second mapping relationship and the target service, determine the target service DRX configuration.

In an example, the second mapping relationship includes a corresponding relationship between PSID and DRX configuration, and the PSID is used to indicate a service type; and the processing module 1120 can be specifically configured to be based on the corresponding relationship between PSID and DRX configuration, and the service type of the target service, Determine the target DRX configuration.

In another example, the second mapping relationship includes a corresponding relationship between an ITS-AID and a DRX configuration, where the ITS-AID is used to indicate a service type; the processing module 1120 may be specifically configured to implement a corresponding relationship based on the ITS-AID and the DRX configuration, and the service type of the target service to determine the target DRX configuration.

Optionally, the processing module 1120 can be specifically configured to determine the target service according to one or more of the following QoS parameters: priority level, PER, PDB, MDBV, GFBR, MFBR, PC5 link aggregation maximum bit rate AMBR, range and PQI, where PQI is used to indicate the following QoS parameters: Default Priority Level, PDB, PER, MDBV, GFBR, MFBR, Default AMBR, and Default Sliding Window.

In a possible implementation manner, the target service is the service corresponding to the target QoS flow included in the first target; the target QoS flow is the QoS flow with the smallest priority among the multiple QoS flows included in the first target, the Or the QoS flow with the smallest PER, or the QoS flow with the smallest PDB, or the QoS flow with the largest MDBV.

Optionally, the target DRX configuration is the default DRX configuration or the public DRX configuration.

Optionally, the transceiver module 1110 is further configured to receive second indication information, where the second indication information is used to indicate the second mapping relationship.

A first possible situation is that the second indication information is sent by a network device. The transceiver module 1110 may be configured to receive the second indication information from the network device.

The second possible situation is that the second indication information is sent by the second terminal device. The transceiver module 1110 may be configured to receive the second indication information from the second terminal device.

A third possible situation is that the second indication information is sent by the upper layer of the apparatus 1100 to the access layer. The transceiver module 1110 may be configured at the access layer of the device 1100 , and may be specifically configured to receive the second indication information from the upper layer of the device 1100 .

When the apparatus 1100 is used to perform the method performed by the second terminal device in FIG. 10 , the transceiver module 1110 can be used to perform step 1030 in the above method 1000 . The processing module 1120 can be used to perform steps 1010 and 1020 in the method 1000 .

Exemplarily, the processing module 1120 can be used to obtain one or more DRX configurations; can be used to determine the first DRX configuration corresponding to the first message; the transceiver module 1110 can be used to send the first message or send the first message based on the first DRX configuration. take over.

Optionally, the first DRX configuration is a DRX configuration corresponding to a QoS parameter corresponding to the first message, and the QoS parameter of the first message is pre-configured or predefined by a protocol.

Optionally, the first DRX configuration is a DRX configuration corresponding to a service type corresponding to the first message, and the service type corresponding to the first message is pre-configured or predefined by a protocol.

Optionally, the first DRX configuration is a default DRX configuration or a public DRX configuration.

Optionally, the first DRX configuration is a dedicated DRX configuration.

Optionally, the first DRX configuration is a DRX configuration with the highest QoS requirement among one or more DRX configurations acquired by the apparatus 1100 . Among them, the highest QoS requirements include one or more of the following: minimum priority level, minimum PER, minimum PDB, and maximum MDBV.

Optionally, the first DRX configuration is a union of one or more DRX configurations acquired by the apparatus 1100 .

Optionally, the apparatus 1100 may correspond to the second terminal device in the embodiments shown in FIG. 7 , FIG. 8 and FIG. 10 , and may include modules of the method executed by the second terminal device.

Specifically, when the apparatus 1100 is used to perform the method performed by the second terminal device in FIG. 7 , the transceiver module 1110 can be used to perform steps 730 and 740 in the above method 700 .

Exemplarily, the transceiver module 1100 may be configured to receive a target DRX configuration, where the target DRX configuration is determined based on a first mapping relationship and a target QoS parameter; wherein the first mapping relationship is used to indicate a corresponding relationship between the QoS parameter and the DRX configuration, the The target QoS parameter is determined based on multiple groups of QoS parameters corresponding to the first target; the target DRX configuration corresponds to the first target, and the first target includes multiple QoS flows of the first terminal device; the transceiver module 1100 is further configured to base on the The target DRX is configured for sidelink communication.

When the apparatus 1100 is used to perform the method performed by the second terminal device in FIG. 8 , the transceiver module 1110 can be used to perform steps 830 and 840 in the above method 800 .

Exemplarily, the transceiver module 1100 may be configured to receive a target DRX configuration, where the target DRX configuration is determined based on the second mapping relationship and the target service; wherein, the second mapping relationship is used to indicate the corresponding relationship between the service and the DRX configuration, and the target DRX configuration is determined based on the second mapping relationship and the target service. The service is determined based on multiple sets of QoS parameters corresponding to the first target, the target DRX configuration corresponds to the first target, the first target includes one or more services of the first terminal device, and each service includes one or more QoS parameters flow; the transceiver module 1100 can also be used for sidelink communication based on the target DRX configuration.

When the apparatus 1100 is used to perform the method performed by the second terminal device in FIG. 10 , the transceiver module 1110 can be used to perform step 1030 in the above method 1000 .

Exemplarily, the transceiver module 1100 may be configured to send or receive the first message based on the first DRX configuration.

It should be understood that when the apparatus 1100 corresponds to the second terminal device, for the relevant description of each term, reference may be made to the above description when the apparatus 1100 corresponds to the first terminal device, which is not repeated here for brevity.

It should be understood that the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation. In addition, each functional module in each embodiment of the present application may be integrated into one processor, or may exist physically alone, or two or more modules may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules.

FIG. 12 is another schematic block diagram of a communication apparatus provided by an embodiment of the present application. As shown in FIG. 12 , as shown in FIG. 12 , the communication apparatus 1200 includes at least one processor 1210 for implementing the function of the first terminal device in the method provided by the embodiment of the present application.

Exemplarily, if the communication apparatus 1200 corresponds to the first terminal device in the foregoing method 700 embodiment, the processor 1210 may be configured to determine target QoS parameters based on multiple sets of QoS parameters corresponding to the first target, where the first target includes multiple sets of QoS parameters. and can be used to determine the target DRX configuration based on the first mapping relationship and the target QoS parameters. For details, refer to the detailed description in the method example, which is not repeated here.

Exemplarily, if the communication apparatus 1200 corresponds to the first terminal device in the foregoing method 800 embodiment, the processor 1210 may be configured to determine the target service based on multiple sets of QoS parameters corresponding to the first target, where the first target includes one or more QoS parameters. multiple services, each of which includes one or more QoS flows; and can be used to determine a target DRX configuration based on the second mapping relationship and the target service. For details, refer to the detailed description in the method example, which is not repeated here.

Exemplarily, if the communication apparatus 1200 corresponds to the first terminal device in the foregoing method 1000 embodiment, the processor 1210 may be configured to acquire one or more DRX configurations; and may be configured to determine the first DRX configuration corresponding to the first message. For details, refer to the detailed description in the method example, which is not repeated here.

Communication apparatus 1200 may also include at least one memory 1220 for storing program instructions and/or data. Memory 1220 and processor 1210 are coupled. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 1210 may cooperate with the memory 1220. The processor 1210 may execute program instructions stored in the memory 1220 . At least one of the at least one memory may be included in the processor.

The communication device 1200 may also include a communication interface 1230 . Wherein, the communication interface 1230 may be a transceiver, an interface, a bus, a circuit, or a device capable of implementing a transceiver function. The communication interface 1230 is used to communicate with other devices through a transmission medium, so that the devices in the communication device 1200 can communicate with other devices. Exemplarily, the other device may be a second terminal device or a network device. The processor 1210 uses the communication interface 1230 to send and receive data, and is configured to implement the method executed by the first terminal device in the embodiments corresponding to FIG. 7 , FIG. 8 , and FIG. 10 .

The specific connection medium between the processor 1210, the memory 1220, and the communication interface 1230 is not limited in the embodiments of the present application. In the embodiment of the present application, the memory 1220, the processor 1210, and the communication interface 1230 are connected by a bus 1240 in FIG. 12. The bus is represented by a thick line in FIG. 12, and the connection between other components is only for schematic illustration. , is not limited. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 12, but it does not mean that there is only one bus or one type of bus.

FIG. 13 is a schematic structural diagram of a terminal device provided by an embodiment of the present application. The terminal device can be applied to the systems shown in FIG. 1 , FIG. 2 , and FIG. 3 . As shown in FIG. 13 , the terminal device 1300 includes a processor 1301 and a transceiver 1302 . Optionally, the terminal device 1300 further includes a memory 1303 . Among them, the processor 1301, the transceiver 1302 and the memory 1303 can communicate with each other through an internal connection path to transmit control and/or data signals. The computer program is invoked and executed to control the transceiver 1302 to send and receive signals. Optionally, the terminal device 1300 may further include an antenna 1304 for sending the uplink data or uplink control signaling output by the transceiver 1302 through wireless signals.

The above-mentioned processor 1301 and the memory 1303 can be combined into a processing device, and the processor 1301 is configured to execute the program codes stored in the memory 1303 to realize the above-mentioned functions. During specific implementation, the memory 1303 may also be integrated in the processor 1301 or independent of the processor 1301 . The processor 1301 may correspond to the processing module 1120 in FIG. 11 or the processor 1210 in FIG. 12 .

The transceiver 1302 described above may correspond to the transceiver module 1120 in FIG. 11 or the communication interface 1230 in FIG. 12 . The transceiver 1202 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Among them, the receiver is used for receiving signals, and the transmitter is used for transmitting signals.

Optionally, the above-mentioned terminal device 1300 may further include a power supply 1305 for providing power to various devices or circuits in the terminal device 1300 .

In addition, in order to make the function of the terminal device more complete, the terminal device 1300 may also include one or more of an input unit 1306, a display unit 1307, an audio circuit 1308, a camera 1309, a sensor 1310, etc. The audio circuitry may also include speakers 1308a, microphones 1308b, and the like.

It should be understood that the terminal device 1300 shown in FIG. 13 can implement various processes involving the first terminal device in the method embodiments shown in FIG. 7 , FIG. 8 and FIG. 10 . The operations and/or functions of each module in the terminal device 1300 are respectively to implement the corresponding processes in the foregoing method embodiments. For details, reference may be made to the descriptions in the foregoing method embodiments, and to avoid repetition, the detailed descriptions are appropriately omitted here.

When the terminal device 1300 is used to execute the operation flow involving the first terminal device in the above method embodiments, the processor 1301 can be used to perform the actions implemented inside the first terminal device described in the previous method embodiments, while the transceiver 1302 may be configured to perform the action of the first terminal device performing sidelink communication based on the target DRX configuration described in the foregoing method embodiments. For details, please refer to the descriptions in the foregoing method embodiments, which will not be repeated here.

When the terminal device 1300 is used to execute the operation process involving the second terminal device in the above method embodiments, the processor 1301 can be used to perform the actions implemented by the second terminal device described in the previous method embodiments, and the transceiver 1302 may be configured to perform the action of performing sidelink communication based on the target DRX configuration by the second terminal device described in the foregoing method embodiments. For details, please refer to the descriptions in the foregoing method embodiments, which will not be repeated here.

In this embodiment of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, which can implement or The methods, steps and logic block diagrams disclosed in the embodiments of this application are executed. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

In this embodiment of the present application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or may also be a volatile memory (volatile memory), for example Random-access memory (RAM). Memory is, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory in this embodiment of the present application may also be a circuit or any other device capable of implementing a storage function, for storing program instructions and/or data.

According to the method provided by the embodiment of the present application, the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code is run on a computer, the computer is made to execute FIG. 7 , FIG. 8 and In the embodiment shown in FIG. 10 , the method performed by the first terminal device or the method performed by the second terminal device.

According to the method provided by the embodiment of the present application, the present application also provides a computer-readable storage medium, where the computer-readable storage medium stores program codes, and when the program codes are run on a computer, the computer is made to execute FIG. 7 , FIG. 8 and the embodiments shown in FIG. 10 are the method performed by the first terminal device or the method performed by the second terminal device.

According to the method provided by the embodiment of the present application, the present application further provides a communication system, where the communication system may include the aforementioned first terminal device and the second terminal device. Optionally, the communication system may further include the aforementioned network device.

The technical solutions provided in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal device, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, digital video discs (DVDs)), or semiconductor media, and the like.

In the embodiments of the present application, on the premise of no logical contradiction, the embodiments may refer to each other. For example, the methods and/or terms between the method embodiments may refer to each other, such as the functions and/or the device embodiments. Or terms may refer to each other, eg, functions and/or terms between an apparatus embodiment and a method embodiment may refer to each other.

Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

A DRX configuration method for discontinuous reception, comprising:

determining target QoS parameters based on multiple sets of service quality QoS parameters corresponding to the first target, where the first target includes multiple QoS flows;

determining a target DRX configuration based on a first mapping relationship and the target QoS parameter, where the first mapping relationship is used to indicate a corresponding relationship between a QoS parameter and a DRX configuration, and the target DRX configuration corresponds to the first target;

Sidelink communications are performed based on the target DRX configuration.
The method of claim 1, wherein the first target comprises: one target address, multiple target addresses or terminal equipment.
The method according to claim 1 or 2, wherein the determining the target QoS parameters based on multiple groups of QoS parameters corresponding to the first target comprises:

Determine the target QoS parameters according to one or more of the following QoS parameters: priority level, packet error rate PER, packet delay budget PDB, maximum data burst volume MDBV, guaranteed traffic bit rate GFBR, maximum traffic bit rate MFBR, PC5 link aggregation maximum bit rate AMBR, minimum communication distance and PC5 interface quality of service identifier PQI, wherein the PQI is used to indicate the following QoS parameters: default priority level, PDB, PER, MDBV, GFBR, MFBR, Default AMBR and default sliding window.
The method according to claim 3, wherein the target QoS parameter is a set of QoS parameters corresponding to a target QoS flow in the first target; the target QoS flow is a set of QoS parameters included in the first target Among the multiple QoS flows, the QoS flow with the smallest priority, or the QoS flow with the smallest PER, or the QoS flow with the smallest PDB, or the QoS flow with the largest MDBV.
The method according to claim 3, wherein each parameter in the target QoS parameters is selected from a plurality of groups of QoS parameters corresponding to the plurality of QoS flows included in the first target.
The method according to any one of claims 1 to 5, wherein the target DRX configuration is a default DRX configuration or a public DRX configuration.
The method according to any one of claims 1 to 6, wherein the method further comprises:

First indication information is received, where the first indication information is used to indicate the first mapping relationship.
The method of claim 7, wherein the receiving the first indication information comprises:

The access layer receives the first indication information from the upper layer.
The method of claim 7, wherein the receiving the first indication information comprises:

The first indication information from the network device is received.
The method according to any one of 1 to 9, wherein the method further comprises:

The target DRX configuration is sent.
A DRX configuration method for discontinuous reception, comprising:

Determine a target service based on multiple sets of service quality QoS parameters corresponding to the first target, where the first target includes one or more services, and each service includes one or more QoS flows;

determining a target DRX configuration based on a second mapping relationship and the target service, where the second mapping relationship is used to indicate a corresponding relationship between a service and a DRX configuration, and the target DRX configuration corresponds to the first target;

Sidelink communications are performed based on the target DRX configuration.
The method of claim 11, wherein the first target comprises: one target address, multiple target addresses or terminal equipment.
The method according to claim 11 or 12, wherein the second mapping relationship is specifically used to indicate the corresponding relationship between the service type and the DRX configuration; and

The target DRX configuration is determined based on the second mapping relationship and the target service, including:

The target DRX configuration is determined based on the second mapping relationship and the service type of the target service.
The method of claim 13, wherein the second mapping relationship comprises a correspondence between a provider service identifier PSID and a DRX configuration, wherein the PSID is used to indicate the service type; and

The determining the target DRX configuration based on the second mapping relationship and the service type of the target service includes:

The target DRX configuration is determined based on the correspondence between the PSID and the DRX configuration, and the service type of the target service.
The method of claim 13, wherein the second mapping relationship comprises a corresponding relationship between an intelligent transportation system application identifier ITS-AID and a DRX configuration, and the ITS-AID is used to indicate the service type; and

The determining the target DRX configuration based on the second mapping relationship and the service type of the target service includes:

The target DRX configuration is determined based on the correspondence between the ITS-AID and the DRX configuration, and the service type of the target service.
The method according to any one of claims 11 to 15, wherein the determining the target service based on multiple groups of QoS parameters corresponding to the first target comprises:

Determine the target service according to one or more of the following QoS parameters: priority level, packet error rate PER, packet delay budget PDB, maximum data burst MDBV, guaranteed traffic bit rate GFBR, and maximum traffic bit rate MFBR , PC5 link aggregation maximum bit rate AMBR, minimum communication distance and PC5 interface quality of service identification PQI, wherein, the PQI is used to indicate the following QoS parameters: default priority level, PDB, PER, MDBV, GFBR, MFBR, default AMBR and default sliding window.
The method of claim 16, wherein the target service is a service corresponding to a target QoS flow included in the first target; the target QoS flow is the multiple QoS flows included in the first target Among the flows, the QoS flow with the smallest priority, or the QoS flow with the smallest PER, or the QoS flow with the smallest PDB, or the QoS flow with the largest MDBV.
The method of any one of claims 11 to 17, wherein the target DRX configuration is a default DRX configuration or a common DRX configuration.
The method according to any one of claims 11 to 18, wherein the method further comprises:

Second indication information is received, where the second indication information is used to indicate the second mapping relationship.
The method of claim 19, wherein the receiving the second indication information comprises:

The access layer receives the second indication information from the upper layer.
The method of claim 19, wherein the receiving the second indication information comprises:

The second indication information from the network device is received.
The method according to any one of claims 11 to 21, wherein the method further comprises:

The target DRX configuration is sent.
A DRX configuration method for discontinuous reception, comprising:

Receive a target DRX configuration, where the target DRX configuration is determined based on a first mapping relationship and a target quality of service QoS parameter; wherein the first mapping relationship is used to indicate the corresponding relationship between the QoS parameter and the DRX configuration, and the target QoS parameter is determined based on multiple groups of QoS parameters corresponding to the first target; the target DRX configuration corresponds to the first target, and the first target includes multiple QoS flows of the first terminal device;

Sidelink communications are performed based on the target DRX configuration.
The method of claim 23, wherein the first target comprises: one target address, multiple target addresses or terminal equipment.
The method according to claim 23 or 24, wherein the target QoS parameter is determined according to one or more of the following parameters: priority level, packet error rate PER, packet delay budget PDB, maximum data burst Quantity MDBV, Guaranteed Traffic Bit Rate GFBR, Maximum Traffic Bit Rate MFBR, PC5 Link Aggregation Maximum Bit Rate AMBR, Minimum Communication Distance and PC5 Interface Quality of Service Identifier PQI, where the PQI is used to indicate the following QoS parameters: Default priority Magnitude, PDB, PER, MDBV, GFBR, MFBR, Default AMBR, and Default Sliding Window.
A DRX configuration method for discontinuous reception, comprising:

Receive a target DRX configuration, where the target DRX configuration is determined based on a second mapping relationship and a target service; wherein the second mapping relationship is used to indicate a corresponding relationship between a service and a DRX configuration, and the target service is based on the first target The target DRX configuration corresponds to the first target, the first target includes one or more services of the first terminal device, and each service includes one or more QoS parameters flow;

Sidelink communications are performed based on the target DRX configuration.
The method of claim 26, wherein the first target comprises: one target address, multiple target addresses or terminal equipment.
The method according to claim 26 or 27, wherein the second mapping relationship is specifically used to indicate the corresponding relationship between the service type and the DRX configuration.
The method according to any one of claims 26 to 28, wherein the target service is determined according to one or more of the following QoS: priority level, packet error rate PER, packet delay budget PDB, maximum Data burst volume MDBV, guaranteed traffic bit rate GFBR, maximum traffic bit rate MFBR, PC5 link aggregation maximum bit rate AMBR, minimum communication distance and PC5 interface quality of service identifier PQI, where the PQI is used to indicate the following QoS parameters: Default priority level, PDB, PER, MDBV, GFBR, MFBR, default AMBR and default sliding window.
A communication device, characterized in that it includes:

a processing module, configured to determine target QoS parameters based on multiple sets of service quality QoS parameters corresponding to a first target, where the first target includes multiple QoS flows; and be configured to determine a target based on the first mapping relationship and the target QoS parameters DRX configuration, the first mapping relationship is used to indicate the corresponding relationship between the QoS parameter and the DRX configuration, and the target DRX configuration corresponds to the first target;

A transceiver module, configured to perform sidelink communication based on the target DRX configuration.
The apparatus of claim 30, wherein the first target comprises: one target address, multiple target addresses or terminal equipment.
The device according to claim 30 or 31, wherein the processing module is specifically used for:

Determine the target QoS parameters according to one or more of the following QoS parameters: priority level, packet error rate PER, packet delay budget PDB, maximum data burst volume MDBV, guaranteed traffic bit rate GFBR, maximum traffic bit rate MFBR, PC5 link aggregation maximum bit rate AMBR, minimum communication distance and PC5 interface quality of service identifier PQI, wherein the PQI is used to indicate the following QoS parameters: default priority level, PDB, PER, MDBV, GFBR, MFBR, Default AMBR and default sliding window.
The apparatus of claim 32, wherein the target QoS parameter is a set of QoS parameters corresponding to a target QoS flow in the first target; the target QoS flow is a set of QoS parameters included in the first target Among the multiple QoS flows, the QoS flow with the smallest priority, or the QoS flow with the smallest PER, or the QoS flow with the smallest PDB, or the QoS flow with the largest MDBV.
The apparatus of claim 32, wherein each parameter in the target QoS parameters is selected from a plurality of groups of QoS parameters corresponding to the plurality of QoS flows included in the first target, respectively.
The apparatus according to any one of claims 30 to 34, wherein the target DRX configuration is a default DRX configuration or a public DRX configuration.
The apparatus according to any one of claims 30 to 35, wherein the transceiver module is further configured to receive first indication information, where the first indication information is used to indicate the first mapping relationship.
The apparatus of claim 36, wherein the processing module is configured at an access layer of the apparatus, and is specifically configured to receive the first indication information from an upper layer of the apparatus.
The apparatus of claim 36, wherein the transceiver module is specifically configured to receive the first indication information from a network device.
The apparatus according to any one of claims 30 to 38, wherein the transceiver module is further configured to send the target DRX configuration.
A communication device, comprising:

The processing module is used to determine the target service based on multiple sets of service quality QoS parameters corresponding to the first target, the first target includes one or more services, and each service includes one or more QoS flows; The mapping relationship and the target service, determine the target DRX configuration, the second mapping relationship is used to indicate the corresponding relationship between the service and the DRX configuration, and the target DRX configuration corresponds to the first target;

A transceiver module, configured to perform sidelink communication based on the target DRX configuration.
The apparatus of claim 40, wherein the first target comprises: one target address, multiple target addresses or terminal equipment.
The apparatus according to claim 40 or 41, wherein the second mapping relationship is specifically used to indicate the corresponding relationship between the service type and the DRX configuration; and

The processing module is specifically configured to determine the target DRX configuration based on the second mapping relationship and the service type of the target service.
The apparatus of claim 42, wherein the second mapping relationship comprises a corresponding relationship between a provider service identifier PSID and a DRX configuration, wherein the PSID is used to indicate the service type; and

The processing module is specifically configured to determine the target DRX configuration based on the corresponding relationship between the PSID and the DRX configuration and the service type of the target service.
The apparatus according to claim 42, wherein the second mapping relationship comprises a corresponding relationship between an intelligent transportation system application identifier ITS-AID and a DRX configuration, and the ITS-AID is used to indicate the service type ;as well as

The processing module is specifically configured to determine the target DRX configuration based on the corresponding relationship between the ITS-AID and the DRX configuration and the service type of the target service.
The apparatus according to any one of claims 40 to 44, wherein the processing module is specifically configured to determine the target service according to one or more of the following QoS parameters: priority, packet error rate PER, Packet Delay Budget PDB, Maximum Data Burst MDBV, Guaranteed Traffic Bit Rate GFBR, Maximum Traffic Bit Rate MFBR, PC5 Link Aggregation Maximum Bit Rate AMBR, Minimum Communication Distance, and PC5 Interface Quality of Service Identifier PQI, where the PQI Used to indicate the following QoS parameters: Default Priority Level, PDB, PER, MDBV, GFBR, MFBR, Default AMBR, and Default Sliding Window.
The apparatus of claim 45, wherein the target service is a service corresponding to a target QoS flow included in the first target; the target QoS flow is the multiple QoS flows included in the first target Among the flows, the QoS flow with the smallest priority, or the QoS flow with the smallest PER, or the QoS flow with the smallest PDB, or the QoS flow with the largest MDBV.
The apparatus according to any one of claims 40 to 46, wherein the target DRX configuration is a default DRX configuration or a public DRX configuration.
The apparatus according to any one of claims 40 to 47, wherein the transceiver module is further configured to receive second indication information, where the second indication information is used to indicate the second mapping relationship.
The device of claim 48, wherein the transceiver module is configured at an access layer of the device, and is specifically configured to receive the second indication information from an upper layer of the device.
The apparatus of claim 48, wherein the transceiver module is specifically configured to receive the second indication information from a network device.
The apparatus according to any one of claims 40 to 50, wherein the transceiver module is further configured to send the target DRX configuration.
A communication device, characterized in that it includes:

A transceiver module, configured to receive a target DRX configuration, where the target DRX configuration is determined based on a first mapping relationship and a target quality of service QoS parameter; wherein the first mapping relationship is used to indicate a corresponding relationship between the QoS parameter and the DRX configuration, The target QoS parameter is determined based on multiple groups of QoS parameters corresponding to the first target; the target DRX configuration corresponds to the first target, and the first target includes multiple QoS flows of the first terminal device; and is used for Sidelink communications are performed based on the target DRX configuration.
The apparatus of claim 52, wherein the first target comprises: one target address, multiple target addresses or terminal equipment.
The apparatus according to claim 52 or 53, wherein the target QoS parameter is determined according to one or more of the following parameters: priority level, packet error rate PER, packet delay budget PDB, maximum data burst Quantity MDBV, Guaranteed Traffic Bit Rate GFBR, Maximum Traffic Bit Rate MFBR, PC5 Link Aggregation Maximum Bit Rate AMBR, Minimum Communication Distance and PC5 Interface Quality of Service Identifier PQI, where the PQI is used to indicate the following QoS parameters: Default priority Magnitude, PDB, PER, MDBV, GFBR, MFBR, Default AMBR, and Default Sliding Window.
A communication device, characterized in that it includes:

A transceiver module, configured to receive a target DRX configuration, where the target DRX configuration is determined based on a second mapping relationship and a target service; wherein, the second mapping relationship is used to indicate a correspondence between a service and a DRX configuration, and the target service is determined based on multiple sets of service quality QoS parameters corresponding to the first target, the target DRX configuration corresponds to the first target, the first target includes one or more services of the first terminal device, and each service includes one or more QoS flows; and for sidelink communication based on the target DRX configuration.
The apparatus of claim 55, wherein the first target comprises: one target address, multiple target addresses or terminal equipment.
The apparatus according to claim 55 or 56, wherein the second mapping relationship is specifically used to indicate the corresponding relationship between the service type and the DRX configuration.
The apparatus according to any one of claims 55 to 57, wherein the target service is determined according to one or more of the following QoS: priority level, packet error rate PER, packet delay budget PDB, maximum Data Burst MDBV, Guaranteed Traffic Bit Rate GFBR, Maximum Traffic Bit Rate MFBR, PC5 Link Aggregation Maximum Bit Rate AMBR, Minimum Communication Distance and PC5 Interface Quality of Service Identifier PQI, wherein the PQI is used to indicate the following QoS parameters: Default priority level, PDB, PER, MDBV, GFBR, MFBR, default AMBR and default sliding window.
A communication device, characterized by comprising a processor for executing computer instructions stored in a memory, so that the device executes the method according to any one of claims 1 to 10.
A communication device, characterized by comprising a processor for executing computer instructions stored in a memory, so that the device executes the method according to any one of claims 11 to 22.
A communication device, characterized by comprising a processor for executing computer instructions stored in a memory, so that the device executes the method according to any one of claims 23 to 25.
A communication device, characterized by comprising a processor for executing computer instructions stored in a memory, so that the device executes the method according to any one of claims 26 to 29.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions that, when the instructions are run on a computer, cause the computer to execute the method described in any one of claims 1 to 24 .
A computer program, characterized in that it comprises program code, when a computer runs the computer program, the program code executes the method according to any one of claims 1 to 24.