WO2022151262A1 - 非连续接收配置方法、通信装置及通信*** - Google Patents
非连续接收配置方法、通信装置及通信*** Download PDFInfo
- Publication number
- WO2022151262A1 WO2022151262A1 PCT/CN2021/071917 CN2021071917W WO2022151262A1 WO 2022151262 A1 WO2022151262 A1 WO 2022151262A1 CN 2021071917 W CN2021071917 W CN 2021071917W WO 2022151262 A1 WO2022151262 A1 WO 2022151262A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- target
- drx configuration
- qos
- service
- terminal device
- Prior art date
Links
- 230000006854 communication Effects 0.000 title claims abstract description 225
- 238000004891 communication Methods 0.000 title claims abstract description 223
- 238000000034 method Methods 0.000 title claims abstract description 189
- 238000013507 mapping Methods 0.000 claims abstract description 150
- 238000012545 processing Methods 0.000 claims description 33
- 238000004590 computer program Methods 0.000 claims description 18
- 230000002776 aggregation Effects 0.000 claims description 13
- 238000004220 aggregation Methods 0.000 claims description 13
- 230000006870 function Effects 0.000 description 28
- 230000005540 biological transmission Effects 0.000 description 23
- 230000011664 signaling Effects 0.000 description 19
- 230000008569 process Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 13
- 238000005516 engineering process Methods 0.000 description 7
- 230000003993 interaction Effects 0.000 description 6
- 230000009471 action Effects 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 4
- 238000013461 design Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012935 Averaging Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000007423 decrease Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000009472 formulation Methods 0.000 description 2
- 239000000203 mixture Substances 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 102100022734 Acyl carrier protein, mitochondrial Human genes 0.000 description 1
- 101000678845 Homo sapiens Acyl carrier protein, mitochondrial Proteins 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 230000002194 synthesizing effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- 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.
- signaling and data transmission can be performed between terminal equipment and terminal equipment through a sidelink (SL).
- SL sidelink
- This manner of transmission over the sidelink may be referred to as sidelink communication.
- 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.
- SCI sidelink control information
- 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.
- 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).
- a terminal device such as the first terminal device exemplified below
- a component such as the first terminal device configured in the terminal device (such as the first terminal device).
- a chip, a chip system, etc. are executed, which is not limited in this embodiment of the present application.
- 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.
- 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.
- multiple QoS flows in the first target can all perform sidelink communication based on the DRX configuration.
- 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.
- 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 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.
- 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.
- 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 (max 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.
- 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 (max flow bit rate, MFBR), PC5 link
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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).
- a terminal device such as the first terminal device in the following example
- a component such as the first terminal device configured in the terminal device (such as the first terminal device).
- a chip, a chip system, etc. are executed, which is not limited in this embodiment of the present application.
- 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.
- 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.
- multiple QoS flows in the first target can all perform sidelink communication based on the DRX configuration.
- 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.
- 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 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.
- 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.
- 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.
- 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.
- provider service identifier provider service identifier
- 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.
- an intelligent traffic system application identifier intelligent traffic system application identifier
- DRX configuration where the ITS-AID is used to indicate the service type
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- the implementation complexity is low.
- 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.
- 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).
- a terminal device such as the second terminal device exemplified below
- a component such as the second terminal device configured in the terminal device (such as the second terminal device).
- a chip, a chip system, etc. are executed, which is not limited in this embodiment of the present application.
- 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.
- 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.
- 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.
- the first target includes: one target address, multiple target addresses or terminal devices.
- 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.
- 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.
- 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.
- 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.
- the first target includes: one target address, multiple target addresses or terminal devices.
- the second mapping relationship is specifically used to indicate the corresponding relationship between the service type and the DRX configuration.
- 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.
- the target DRX configuration may be a default DRX configuration or a public DRX configuration.
- the default DRX configuration or the public DRX configuration can be configured. as the target DRX configuration.
- 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.
- 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.
- the communication device further includes a memory.
- the communication device further includes a communication interface, and the processor is coupled to the communication interface.
- the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.
- 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.
- the communication system further includes a network device.
- 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 .
- 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.
- a computer program also referred to as code, or instruction
- 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.
- FIGS. 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
- FIG. 7 is a schematic flowchart of a DRX configuration method provided by an embodiment of the present application.
- FIG. 8 is a schematic flowchart of a DRX configuration method provided by another embodiment of the present application.
- 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.
- 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).
- NSA non-standalone
- SA independent network
- 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.
- vehicle to X vehicle to X
- V2X vehicle Communication with infrastructure
- V2P vehicle and pedestrian
- V2N vehicle and network
- 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.
- eNB evolved Node B
- RNC radio network controller
- Node B Node B
- BSC base station controller
- base transceiver station base transceiver station
- BTS home base station
- home base station for example, home evolved NodeB, or home Node B, HNB
- 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.
- 5G such as NR
- a gNB in the system or a transmission point (TRP or TP)
- TRP or TP transmission point
- TRP or TP transmission point
- TP transmission point
- a network node of a transmission point such as a baseband unit (BBU), or a distributed unit (distributed unit, DU), etc.
- BBU baseband unit
- DU distributed unit
- 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.
- 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.
- RRC radio resource control
- service data service data adaptation protocol
- SDAP adaptation protocol
- PDCP packet data convergence protocol
- the DU can be responsible for handling physical layer protocols and real-time services.
- radio link control radio link control
- MAC media access control
- PHY physical (physical, PHY) layer
- 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.
- high-level signaling such as RRC layer signaling, also It can be considered to be sent by DU, or sent by DU+AAU.
- the network device may be a device including one or more of a CU node, a DU node, and an AAU node.
- 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.
- RAN radio access network
- CN core network
- 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.
- a macro base station for example, a macro eNB or a macro gNB, etc.
- 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
- 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.
- user equipment user equipment
- UE user equipment
- 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.
- 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
- 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.
- 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.
- the terminal device may also be a terminal device in an Internet of things (Internet of things, IoT) system.
- IoT Internet of things
- 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.
- NB narrow band
- UE and terminal device are used interchangeably, and the meanings expressed by the two are the same.
- 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.
- V2X A typical application scenario for sidelink communication is 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.
- 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.
- 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 .
- 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 .
- terminal device 121, terminal device 122 and terminal device 123 are all located outside the coverage of the network device 110 .
- 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.
- 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.
- resources preconfigured by the network device such as a resource pool
- 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.
- UE-to-network relay such as UE-to-network relay
- 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 .
- a UE may be referred to as a relay UE (relay UE) for short
- UE-to-network relay UE-to-network relay
- remote end UE remote end UE
- 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.
- 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.
- 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.
- UE-to-UE relay eg, UE-to-UE relay
- a UE-to-UE relay scenario may include at least 3 UEs, and at least one of them can serve as a relay UE.
- 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).
- 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.
- the sidelink communication can support unicast communication, multicast communication and broadcast communication.
- unicast communication may refer to transmitting signaling and/or data to a device.
- 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.
- 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.
- 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.
- 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.
- QoS flow is a QoS differentiation granularity in a protocol data unit (protocol data unit, PDU) session.
- PDU protocol data unit
- QoS Flow identifier QFI
- a PDU session can include multiple QoS flows, but the QFI of each QoS flow is different.
- 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.
- 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.
- 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).
- a destination address may include one or more QoS flows, corresponding to one or more sets of QoS parameters.
- a standard PQI may correspond to a set of QoS characteristics.
- the corresponding relationship between the PQI and the QoS feature may be specifically determined by the corresponding relationship predefined in the protocol.
- 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.
- 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.
- the 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.
- the direct mentioned here is relative to the QoS feature corresponding to the PQI configured through 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.
- 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.
- QoS parameters priority level, PDB, PER, resource type, MDBV, and sliding window.
- a corresponding default priority level is configured in the PQI of a QoS flow
- 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.
- 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.
- the default priority level in the PQI may be used.
- 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.
- 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.
- SCI sidelink control information
- the transmitting UE may not need to send data, which greatly increases the power consumption of the receiving UE.
- 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.
- 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.
- 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.
- 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).
- 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.
- the on time and off time of the DRX can be determined.
- the SL DRX configuration is included in an RRC message, a SIB message or a preconfigured message.
- the SL DRX configuration is included in the resource pool configuration.
- 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.
- the on time shown in FIG. 5 may specifically refer to the time when any one of onDurationTimer and InactivityTimer runs.
- 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).
- the SL DRX configuration may correspond to a resource pattern.
- Figure 6 shows the SL DRX configuration corresponding to the resource pattern.
- 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
- 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.
- the SL DRX configuration may be included in a resource pool configuration.
- a resource pool configuration may include one or more resource modes.
- Each resource mode can correspond to one SL DRX configuration.
- 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).
- 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.
- 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.
- 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. .
- the present application provides a DRX configuration method in order to achieve a balance between QoS performance and energy saving.
- the DRX configuration is related to 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.
- 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.
- 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 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.
- 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.
- the terminal device 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.
- SIB system information block
- 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.
- 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.
- 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.
- 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. .
- 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
- the second terminal device is a terminal device that performs sidelink communication with the first terminal device.
- 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.
- the method 700 may include steps 710 to 740 . Each step in the method 700 will be described in detail below.
- the first terminal device determines target QoS parameters based on multiple sets of QoS parameters corresponding to the first target.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- the first target may include one or more QoS flows.
- 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.
- the first target may be a collective term for multiple QoS flows.
- 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.
- 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. .
- 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.
- 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.
- 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 .
- 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.
- the first terminal device is a receiving terminal device
- the second terminal device is an originating terminal device.
- 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).
- the target QoS parameter corresponding to the first target may be determined by the second terminal device.
- the first terminal device is a receiving terminal device
- the second terminal device is an originating terminal device.
- the target QoS parameter can be determined through the following two possible implementation manners.
- the target QoS parameter may be a set of QoS parameters corresponding to the target QoS flow in the first target.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- the QoS flow with the smallest PER and the largest MDBV may be used as the target QoS flow.
- the QoS flow with the smallest PDB or the largest MDBV among the multiple QoS flows can be further determined as: Target QoS flow.
- the QoS flow with the smallest PDB or the smallest PER among the multiple QoS flows may be further determined as Target QoS flow.
- 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.
- QoS flow 1 is finally determined as the target QoS flow.
- 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.
- QoS flow 1 is finally determined as the target QoS flow.
- 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.
- QoS flow 1 is finally determined as the target QoS flow.
- the QoS flow with the smallest PDB or the largest MDBV among the multiple QoS flows can be determined as the target QoS flow. .
- 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.
- 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.
- the QoS flow with the smallest priority among the multiple QoS flows can be 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
- the 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.
- 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.
- 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.
- 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.
- QoS parameters such as GFBR, MFBR, PC5 link AMBR, range, MDBV, etc.
- GFBR GFBR
- MFBR MFBR
- PC5 link AMBR range
- MDBV MDBV
- 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.
- the QoS parameters such as priority level, PDB, PER, GFBR, MFBR, PC5 link AMBR, range, and MDBV
- the QoS parameters such as priority level, PDB, PER, GFBR, MFBR, PC5 link AMBR, range, and MDBV
- the value directly configured in the QoS parameters can be used to cover the same PQI corresponding The value of the item parameter.
- 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.
- 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.
- 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.
- 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.
- the first target includes three QoS flows, namely QoS flow 1, QoS flow 2, and QoS flow 3.
- the default priority level in the PQI of QoS flow 1 is the smallest
- the GFBR of QoS flow 2 is the largest
- 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.
- the first target includes four QoS flows, namely, QoS flow 1, QoS flow 2, QoS flow 3, and QoS flow 4.
- QoS flow 1 has the smallest priority level
- QoS flow 2 has the smallest PDB
- QoS flow 2 has the smallest PDB
- Flow 3 has the largest GFBR
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- the QoS parameters corresponding to the target DRX configuration may be a subset of the above-mentioned target QoS parameters.
- the target QoS parameter may be the same as the set of QoS parameters in the first mapping relationship.
- the target QoS parameters include PQI, priority level, PER, PDB, MDBV, and GFBR
- the set of QoS parameters indicated in the first mapping relationship includes PQI, priority level, PER, PDB, MDBV, and GFBR.
- 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.
- 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.
- 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.
- the same set of QoS parameters as the target QoS parameters may be preferentially selected to determine the target DRX configuration.
- 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.
- 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.
- 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.
- 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.
- 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.
- RRC radio resource control
- SIB system information block
- the first indication information may be carried in the RRC message received from the network device.
- 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.
- OOC out-of-coverage
- the second possible situation is that the first indication information may be received from other terminal devices.
- 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.
- 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.
- the first terminal device is a receiving terminal device
- the second terminal device is an originating terminal device.
- 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.
- 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.
- the first terminal device does not find a corresponding relationship matching the target QoS parameter from the first mapping relationship.
- the first terminal device may use the default DRX configuration or the public DRX configuration as the target DRX configuration.
- 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.
- the target DRX configuration corresponds to the first target.
- the first target may include a target address, multiple target addresses, or a terminal device.
- the target DRX configuration may correspond to one target address, or multiple target addresses or one terminal device.
- 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.
- the DRX configurations of multiple QoS flows on the sidelink corresponding to the same target address are the same.
- multiple QoS flows in the target addresses can all perform sidelink communication based on the target DRX configuration.
- the DRX configurations of multiple QoS flows corresponding to multiple destination addresses on the sidelink are the same.
- multiple QoS flows in all target addresses of the first terminal device may perform sidelink communication based on the target DRX configuration.
- the DRX configurations of the multiple QoS flows corresponding to the first terminal device on the sidelink are the same.
- 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.
- 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.
- step 730 the first terminal device performs sidelink communication based on the target DRX configuration.
- communication may include sending or receiving.
- 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.
- the first terminal device may perform sidelink communication with the second terminal device based on the target DRX configuration.
- 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.
- the first terminal equipment 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.
- 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.
- 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.
- 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.
- the reliability of transmission can be guaranteed, thereby ensuring better QoS performance.
- 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.
- multiple QoS flows in the first target can all perform sidelink communication based on the DRX configuration.
- 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.
- 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.
- an embodiment of the present application further provides a DRX configuration 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.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- the first target may include one or more QoS.
- 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.
- 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.
- the first target may be a collective term for multiple QoS flows.
- 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.
- 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.
- 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.
- the first terminal device is a receiving terminal device
- the second terminal device is an originating terminal device.
- 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).
- the target service corresponding to the first target may be determined by the second terminal device.
- the first terminal device is a receiving terminal device
- the second terminal device is an originating terminal device.
- 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.
- QoS parameters priority level, PER, PDB, MDBV, GFBR, MFBR, PC5 link AMBR, range, and PQI.
- the first terminal device may select the service corresponding to the target QoS flow as the target service.
- the target QoS flow may be determined based on a certain QoS parameter of the multiple QoS flows in the first target.
- 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 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.
- 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.
- 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.
- 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.
- 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.
- the QoS flow with the smallest PDB or the largest MDBV among the multiple QoS flows can be further determined as: Target QoS flow.
- the QoS flow with the smallest PDB or the smallest PER among the multiple QoS flows may be further determined as Target QoS flow.
- 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.
- the first target includes business 1, business 2, and business 3.
- 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
- the 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- the second mapping relationship may be specifically used to indicate the corresponding relationship between the service type and the DRX configuration.
- 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.
- 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.
- 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.
- the second terminal device sends the second indication information.
- the second indication information may be carried in, for example, an RRC message, an SIB message, or a pre-configuration message.
- the second indication information may be carried in the RRC message received from the network device.
- the second indication information may be carried in the SIB message received from the network device.
- 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.
- 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.
- the first terminal device is a receiving terminal device
- 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.
- 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.
- the first terminal device may use the preconfigured default DRX configuration or the public DRX configuration as the target DRX configuration.
- 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.
- the target DRX configuration corresponds to the first target.
- the target DRX configuration corresponds to the first target.
- 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.
- 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.
- 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.
- step 840 the first terminal device performs sidelink communication based on the target DRX configuration.
- 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.
- 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.
- multiple QoS flows in the first target can all perform sidelink communication based on the DRX configuration.
- 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.
- 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.
- QoS parameters or service types may not be available.
- 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.
- step 910 the first terminal device sends a direct communication request (direct communication request, DCR) message to the second terminal device.
- DCR direct communication request
- 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.
- step 930 the first terminal device sends a direct security mode complete message to the second terminal device.
- step 940 the second terminal device sends a direct command accept message to the first terminal device.
- a unicast connection is established between the first terminal device and the second terminal device.
- 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.
- 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.
- 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 .
- step 1010 the first terminal device acquires one or more DRX configurations.
- 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.
- 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.
- the first mapping relationship may be used to indicate the corresponding relationship between the QoS parameters and the DRX configuration
- 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.
- 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.
- 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 first RRC reconfiguration complete sidelink (RRCReconfigurationCompleteSidelink) message after the direct connection communication is established between the terminal devices.
- 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.
- the first terminal device may determine the first DRX configuration corresponding to the first message through the following five possible implementation manners:
- 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.
- the first DRX configuration may correspond to the QoS parameter (or service type) corresponding to the first message.
- 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.
- the QoS parameters (or service types) corresponding to different first messages may be different.
- the QoS parameters (or service types) corresponding to the DCR message and the security setup command message are different.
- 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.
- 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.
- the first terminal device determines the default DRX configuration or the common DRX configuration as the first DRX configuration.
- each resource pool may include a corresponding default DRX configuration or a common DRX configuration
- 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.
- 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.
- 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.
- the first terminal device may trigger to use the default DRX configuration or the public DRX configuration to send or receive the first message.
- the first terminal device 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.
- the first terminal device 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.
- 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.
- mapping relationship between the pre-configured V2X service type and the layer 2 identifier.
- 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.
- 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.
- 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).
- the first terminal device may start or restart the first timer each time a direct connection communication request message is sent or received.
- the first terminal device may stop the first timer every time the first RRCReconfigurationSidelink message is sent or received.
- the first terminal device determines the dedicated DRX configuration as the first SL DRX configuration.
- each resource pool may include a corresponding dedicated DRX configuration, which may be dedicated to the transmission of the first message.
- the first terminal device may use the corresponding dedicated DRX configuration in the resource pool to send or receive the first message.
- 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.
- 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.
- the first terminal device may trigger the use of the dedicated DRX configuration to send or receive the first message.
- the first terminal device may trigger the use of a dedicated DRX configuration to send or receive the first message.
- the first terminal device may trigger the use of the dedicated DRX configuration to send or receive the first message.
- the first terminal device 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. .
- 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.
- 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).
- the first terminal device may start or restart the first timer every time it sends or receives a unicast connection establishment request message.
- the first terminal device may stop the first timer every time the first RRCReconfigurationSidelink message is sent or received.
- 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.
- 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.
- 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.
- 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 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.
- 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.
- 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.
- descriptions of the same or similar situations are omitted for brevity.
- 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.
- the first DRX configuration may be a union of one or more DRX configurations obtained in advance.
- 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.
- 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.
- the first terminal device may send or receive the first message with the second terminal device based on the target DRX configuration.
- 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.
- 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.
- 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.
- 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.
- the communication apparatus 1100 may include a transceiver module 1110 and a processing module 1120 .
- 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.
- 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 .
- 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.
- the first target includes: one target address, multiple target addresses or terminal devices.
- 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.
- 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.
- 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.
- the target DRX configuration is a default DRX configuration or a public DRX configuration.
- 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 .
- the transceiver module 1110 can also be used to send the target DRX configuration.
- 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 .
- 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.
- the first target includes: one target address, multiple target addresses or terminal devices.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- the target DRX configuration is the default DRX configuration or the public DRX configuration.
- 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 .
- the transceiver module 1110 can also be used to send the target DRX configuration.
- 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 .
- 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.
- 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.
- 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.
- the first DRX configuration is a default DRX configuration or a public DRX configuration.
- the first DRX configuration is a dedicated DRX configuration.
- the first DRX configuration is a DRX configuration with the highest QoS requirement among one or more DRX configurations acquired by the apparatus 1100 .
- the highest QoS requirements include one or more of the following: minimum priority level, minimum PER, minimum PDB, and maximum MDBV.
- the first DRX configuration is a union of one or more DRX configurations acquired by the apparatus 1100 .
- 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.
- the transceiver module 1110 can be used to perform steps 730 and 740 in the above method 700 .
- 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.
- the transceiver module 1110 can be used to perform steps 830 and 840 in the above method 800 .
- 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.
- the transceiver module 1110 can be used to perform step 1030 in the above method 1000 .
- the transceiver module 1100 may be configured to send or receive the first message based on the first DRX configuration.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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 .
- 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.
- 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.
- 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 .
- the terminal device 1300 includes a processor 1301 and a transceiver 1302 .
- the terminal device 1300 further includes a memory 1303 .
- 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.
- 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.
- 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.
- 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 .
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
- 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.
- 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.
- 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.
- 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.
- the present application further provides a communication system, where the communication system may include the aforementioned first terminal device and the second terminal device.
- 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.
- software 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.
- 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.
- the embodiments may refer to each other.
- the methods and/or terms between the method embodiments may refer to each other, such as the functions and/or the device embodiments.
- terms may refer to each other, eg, functions and/or terms between an apparatus embodiment and a method embodiment may refer to each other.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请提供了一种DRX配置方法、通信装置和通信***。该方法包括:基于第一目标包括的多个QoS流对应的多组QoS参数,确定目标QoS参数;基于第一映射关系和目标QoS参数,确定目标DRX配置,该第一映射关系可用于指示QoS参数与DRX配置的对应关系,该目标DRX配置可对应于第一目标;基于该目标DRX配置进行侧行链路通信。其中,第一目标包括:一个目标地址、多个目标地址或终端设备。也即,多个QoS流可以基于相同的目标DRX配置进行侧行链路通信。用于确定目标DRX配置的目标QoS参数是根据多组QoS参数确定的,兼顾了QoS需求。因此,可以在QoS表现和节能省电之间获得平衡。
Description
本申请涉及通信领域,更为具体地,涉及一种非连续接收配置方法、通信装置及通信***。
目前,在有些通信***中,如第五代移动通信***(5th generation wireless system,5G)中,终端设备与终端设备之间可以通过侧行链路(sidelink,SL)进行信令和数据的传输。这种通过侧行链路来进行传输的方式可以称为侧行链路通信。
为了获得较优的业务质量(quality of service,QoS)表现,如较高的传输可靠性,终端设备之间可以基于相同的非连续接收(discontinuous reception,DRX)配置进行侧行链路通信。发端终端设备和收端终端设备可以在相同的时段内发送和接收控制信息,如侧行链路控制信息(sidelink control information,SCI),以进行正常通信;并可以在相同的时段内关闭射频(radio frequency,RF)通道,不进行控制信息的发送和接收,以达到节能省电的效果。
然而,如何对收发两端的终端设备进行DRX配置,以获得QoS表现和节能省电之间的平衡,是一项亟待解决的技术问题。
发明内容
本申请提供了一种DRX配置方法、通信装置及通信***,以期获得QoS表现和节能省电之间的平衡。
第一方面,本申请提供了一种DRX配置方法,该方法可以由终端设备执行(如下文示例的第一终端设备),也可以由配置在终端设备(如第一终端设备)中的部件(如,芯片、芯片***等)执行,本申请实施例对此不作限定。
示例性地,该方法包括:基于第一目标对应的多组QoS参数,确定目标QoS参数,所述第一目标包括多个QoS流;基于第一映射关系和所述目标QoS参数,确定目标DRX配置,所述第一映射关系用于指示QoS参数与DRX配置的对应关系,所述目标DRX配置对应于所述第一目标;基于所述目标DRX配置进行侧行链路通信。
基于上述技术内容,第一终端设备可以根据第一目标对应的多组QoS参数确定目标QoS参数,进而根据目标QoS参数,以及QoS参数与DRX配置的对应关系,确定目标DRX配置。由此,第一目标中的多个QoS流均可以基于该DRX配置进行侧行链路通信。如此一来,第一终端设备中的多个QoS流可以基于相同的DRX配置开启和关闭射频通道,从而在一定程度上可以避免第一终端设备在射频通道的开、关之间的切换频率,降低处理复杂度,节能省电。并且,由于是基于目标QoS参数而确定的目标DRX配置,目标QoS参数又是基于上述第一目标对应的多组QoS参数确定的,因此所确定的目标DRX配置在一定程度上能够满足QoS需求,使得该第一终端设备具 有较优的QoS表现,由此,可以获得QoS表现和节能省电之间的平衡。
结合第一方面,在某些可能的实现方式中,所述第一目标包括:一个目标地址、多个目标地址或终端设备。
其中,终端设备具体可以是指一个终端设备的所有目标地址。故,第一目标对应一个终端设备具体可以是指第一目标对应一个终端设备的所有目标地址。
多个目标地址具体可以是指一个终端设备的多个目标地址,例如可以是该终端设备的所有目标地址中的部分。故,第一目标对应多个目标地址具体可以是指第一目标对应一个终端设备的部分目标地址。
由于每个目标地址可以包括一个或多个QoS流,故第一目标可以包括一个或多个QoS流。也即,第一终端设备可以针对一个或多个QoS流来配置DRX。由此,第一终端设备可以基于较QoS流更大的粒度来维护一套DRX配置,从而可以降低实现复杂度。
结合第一方面,在某些可能的实现方式中,该方法还包括:根据以下一项或多项QoS参数,确定所述目标QoS参数:优先级量级(priority level)、包错误率(packet error rate,PER)、包时延预算(packet delay budget,PDB)、最大数据突发量(maximum data burst volume,MDBV)、保证流量比特率(guaranteed flow bit rate,GFBR)、最大流量比特率(maximum flow bit rate,MFBR)、PC5链路聚合最大比特率(PC5 link aggregate maximum bit rate,PC5Link-AMBR)、最小通信距离(range)和PC5接口5G业务质量标识(PC55G QoS identifier,PQI),其中,所述PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR和默认滑动窗口(averaging window)。
下文提供了确定目标QoS参数的两种可能的实现方式。
在第一种可能的实现方式中,所述目标QoS参数是所述第一目标中的目标QoS流对应的一组QoS参数;所述目标QoS流是所述第一目标包括的所述多个QoS流中,优先级量级最小的QoS流、或PER最小的QoS流、或PDB最小的QoS流、或MDBV最大的QoS流。
即,第一终端设备可以将第一目标中的多个QoS流中QoS要求较高的一个QoS流对应的QoS参数作为目标QoS参数,来确定目标DRX配置。因此有利于获得较优的QoS表现。并且,基于目标QoS参数确定的目标DRX配置可对应于第一目标,也即对应于第一目标中的QoS流。也即,可基于较QoS流更大的粒度来维护一套DRX配置,实现复杂度较低。
在第二种可能的实现方式中,所述目标QoS参数中的每项参数分别是从所述第一目标包括的所述多个QoS流对应的多组QoS参数中选择得到的。
即,第一终端设备可以针对每项参数分别选择一个QoS要求较高的值来作为目标QoS参数中的一项,进而确定目标DRX配置。因此有利于获得较优的QoS表现。并且,基于目标QoS参数确定的目标DRX配置可对应于第一目标,也即对应于第一目标中的QoS流。也即,可基于较QoS流更大的粒度来维护一套DRX配置,实现复杂度较低。
结合第一方面,在某些可能的实现方式中,该方法还包括:接收第一指示信息,该第一指示信息用于指示所述第一映射关系。
第一种可能的情况是,该第一指示信息可以是网络设备发送的。所述接收第一指 示信息,包括:接收来自网络设备的第一指示信息。
第二种可能的情况是,该第一指示信息可以是其他终端设备(如,第二终端设备)发送的。所述接收第一指示信息,包括:接收来自第二终端设备的第一指示信息。
第三种可能的情况是,所述接收第一指示信息,包括:接入层接收来自上层的第一指示信息。
第一终端设备可以基于接收到的第一指示信息确定第一映射关系,进而确定与目标QoS参数对应的目标DRX配置。
结合第一方面,在某些可能的实现方式中,该方法还包括:发送所述目标DRX配置。
第一终端设备可以将确定好的目标DRX配置发送给第二终端设备,以便与第二终端设备对齐DRX配置。由此,第一终端设备和第二终端设备可以基于相同的DRX配置进行侧行链路通信。由于该目标DRX配置对应于第一目标,第一目标可以包括多个QoS流,从而可以在QoS表现和节能省电之间获得平衡。
第二方面,本申请提供了一种DRX配置方法,该方法可以由终端设备执行(如下文示例的第一终端设备),也可以由配置在终端设备(如第一终端设备)中的部件(如,芯片、芯片***等)执行,本申请实施例对此不作限定。
示例性地,该方法包括:基于第一目标对应的多组QoS参数,确定目标业务,所述第一目标包括一个或多个业务,每个业务包括一个或多个QoS流;基于第二映射关系和所述目标业务,确定目标DRX配置,所述第二映射关系用于指示业务与DRX配置的对应关系,所述目标DRX配置对应于所述第一目标;基于所述目标DRX配置进行侧行链路通信。
基于上述技术内容,第一终端设备可以根据第一目标对应的多组QoS参数确定目标业务,进而根据目标业务,以及业务与DRX配置的对应关系,确定目标DRX配置。由此,第一目标中的多个QoS流均可以基于该DRX配置进行侧行链路通信。如此一来,第一终端设备中的多个QoS流可以基于相同的DRX配置开启和关闭射频通道,从而在一定程度上可以避免第一终端设备在射频通道的开、关之间的切换频率,降低处理复杂度,节能省电。并且,由于是基于目标QoS参数而确定的目标DRX配置,目标QoS参数又是基于上述第一目标对应的多组QoS参数确定的,因此所确定的目标DRX配置在一定程度上能够满足QoS需求,使得该第一终端设备具有较优的QoS表现,由此,可以获得QoS表现和节能省电之间的平衡。
结合第二方面,在某些可能的实现方式中,所述第一目标包括:一个目标地址、多个目标地址或终端设备。
其中,终端设备具体可以是指一个终端设备的所有目标地址。故,第一目标对应一个终端设备具体可以是指第一目标对应一个终端设备的所有目标地址。
多个目标地址具体可以是指一个终端设备的多个目标地址,例如可以是该终端设备的所有目标地址中的部分。故,第一目标对应多个目标地址具体可以是指第一目标对应一个终端设备的部分目标地址。
由于每个目标地址可以包括一个或多个QoS流,故第一目标可以包括一个或多个QoS流。也即,第一终端设备可以针对一个或多个QoS流来配置DRX。由此,第一终端设备可以基于较QoS流更大的粒度来维护一套DRX配置,从而可以降低实现复杂度。
结合第二方面,在某些可能的实现方式中,所述第二映射关系具体用于指示业务类型与DRX配置的对应关系;以及该方法还包括:基于所述第二映射关系和所述目标业务的业务类型,确定所述目标DRX配置。
一示例,所述第二映射关系包括提供商业务标识符(provider service identifier,PSID)与DRX配置的对应关系,所述PSID用于指示所述业务类型;以及该方法还包括:基于所述PSID与DRX配置的对应关系,以及所述目标业务的业务类型,确定所述目标DRX配置。
另一示例,所述第二映射关系包括智能交通***应用标识符(intelligent traffic system application identifier,ITS-AID)与DRX配置的对应关系,所述ITS-AID用于指示所述业务类型;以及该方法还包括:基于所述ITS-AID与DRX配置的对应关系,以及所述目标业务的业务类型,确定所述目标DRX配置。
应理解,一种业务类型可对应于一个DRX配置,多种业务类型也可对应于一个DRX配置。本申请实施例对此不作限定。
还应理解,业务类型与DRX配置的对应关系仅为业务与DRX配置的对应关系的一种可能的形式,不应对本申请构成任何限定。此外,上文列举的用于指示业务类型的PSID和ITS-AID仅为示例,不应对本申请构成任何限定。
结合第二方面,在某些可能的实现方式中,该方法还包括:根据以下一项或多项QoS参数,确定所述目标业务:优先级量级、包错误率PER、包时延预算PDB、最大数据突发量MDBV、保证流量比特率GFBR、最大流量比特率MFBR、PC5链路聚合最大比特率AMBR、最小通信距离和PC5接口业务质量标识PQI,其中,所述PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR和默认滑动窗口。
由于第一终端设备可基于多个QoS流对应的多组QoS参数确定一个目标业务,例如针对一个目标地址、多个目标地址或一个终端设备对应的多组QoS参数确定一个目标业务,从而可以在后续确定目标DRX配置时基于较QoS流更大的粒度来配置DRX。
结合第二方面,在某些可能的实现方式中,该方法还包括:所述目标业务是所述第一目标包括的目标QoS流对应的业务;所述目标QoS流是所述第一目标包括的所述多个QoS流中,优先级量级最小的QoS流、或PER最小的QoS流、或PDB最小的QoS流、或MDBV最大的QoS流。
即,第一终端设备可以将第一目标中的多个QoS流中QoS要求较高的一个QoS流对应的业务作为目标业务,并基于该目标业务来确定目标DRX配置。一方面有利于获得较优的QoS表现;另一方面,由于目标DRX配置可对应于第一目标,也即对应于第一目标中的QoS流,也即,可基于较QoS流更大的粒度来维护一套DRX配置,实现复杂度较低。
结合第二方面,在某些可能的实现方式中,该方法还包括:接收第二指示信息,该第二指示信息用于指示所述第二映射关系。
第一种可能的情况是,该第二指示信息可以是网络设备发送的。所述接收第二指示信息,包括:接收来自网络设备的第二指示信息。
第二种可能的情况是,该第二指示信息可以是其他终端设备(如,第二终端设备) 发送的。所述接收第二指示信息,包括:接收来自第二终端设备的第二指示信息。
第三种可能的情况是,所述接收第二指示信息,包括:接入层接收来自上层的第二指示信息。
第二终端设备可以基于接收到的第二指示信息确定第二映射关系,进而确定与目标业务对应的目标DRX配置。
第三方面,本申请提供了一种DRX配置方法,该方法可以由终端设备执行(如下文示例的第二终端设备),也可以由配置在终端设备(如第二终端设备)中的部件(如,芯片、芯片***等)执行,本申请实施例对此不作限定。
示例性地,该方法包括:接收目标DRX配置,所述目标DRX配置是基于第一映射关系和目标业务质量QoS参数确定的;其中,所述第一映射关系用于指示QoS参数与DRX配置的对应关系,所述目标QoS参数是基于第一目标对应的多组QoS参数确定的;所述目标DRX配置对应于所述第一目标,所述第一目标包括第一终端设备的多个QoS流;基于所述目标DRX配置进行侧行链路通信。
基于上述技术内容,第二终端设备可以不需要自行确定目标DRX配置,而可直接从对端(如,第一终端设备)接收目标DRX配置,并基于该目标DRX配置与对端进行侧行链路通信。
结合第三方面,在某些可能的实现方式中,所述第一目标包括:一个目标地址、多个目标地址或终端设备。
结合第三方面,在某些可能的实现方式中,所述目标QoS参数根据以下一项或多项参数确定:优先级量级、包错误率PER、包时延预算PDB、最大数据突发量MDBV、保证流量比特率GFBR、最大流量比特率MFBR、PC5链路聚合最大比特率AMBR、最小通信距离和PC5接口业务质量标识PQI,其中,所述PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR和默认滑动窗口。
第三方面中的某些可能的实现方式与第一方面中的某些可能的实现方式相对应,可参看第一方面中的相关描述,为了简洁,此处不再赘述。
第四方面,本申请提供了一种非连续接收DRX配置方法,该方法可以由终端设备执行(如下文示例的第一终端设备),也可以由配置在终端设备(如第一终端设备)中的部件(如,芯片、芯片***等)执行,本申请实施例对此不作限定。
示例性地,该方法包括:接收目标DRX配置,所述目标DRX配置是基于第二映射关系和目标业务确定的;其中,所述第二映射关系用于指示业务与DRX配置的对应关系,所述目标业务是基于第一目标对应的多组业务质量QoS参数确定的,所述目标DRX配置对应于所述第一目标,所述第一目标包括第一终端设备的一个或多个业务,每个业务包括一个或多个QoS流;基于所述目标DRX配置进行侧行链路通信。
基于上述技术内容,第二终端设备可以不需要自行确定目标DRX配置,而可直接从对端(如,第一终端设备)接收目标DRX配置,并基于该目标DRX配置与对端进行侧行链路通信。
结合第四方面,在某些可能的实现方式中,所述第一目标包括:一个目标地址、多个目标地址或终端设备。
结合第四方面,在某些可能的实现方式中,所述第二映射关系具体用于指示业务 类型与DRX配置的对应关系。
结合第四方面,在某些可能的实现方式中,所述目标业务根据以下一项或多项QoS确定:优先级量级、包错误率PER、包时延预算PDB、最大数据突发量MDBV、保证流量比特率GFBR、最大流量比特率MFBR、PC5链路聚合最大比特率AMBR、最小通信距离和PC5接口业务质量标识PQI,其中,所述PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR和默认滑动窗口。
第四方面中的某些可能的实现方式与第二方面中的某些可能的实现方式相对应,可参看第二方面中的相关描述,为了简洁,此处不再赘述。
结合第一方面至第四方面,在某些可能的实现方式中,所述目标DRX配置可以为默认DRX配置或公共DRX配置。
例如,在第一终端设备从第一映射关系中未找到与目标QoS参数匹配的对应关系或第二映射关系中并未找到与目标业务匹配的对应关系时,可以将默认DRX配置或公共DRX配置作为目标DRX配置。
第五方面,本申请提供了一种通信装置,该装置包括用于实现第一方面至第四方面和第一方面至第四方面中任一种可能实现方式中的DRX配置方法的各个模块或单元。应理解,所述各个模块或单元可通过执行计算机程序来实现相应的功能。
第六方面,本申请提供了一种通信装置,该装置包括处理器。该处理器与存储器耦合,可用于执行存储器中的计算机程序,以实现第一方面至第四方面和第一方面至第四方面中任一种可能实现方式中的DRX配置方法。可选地,该通信装置还包括存储器。可选地,该通信装置还包括通信接口,处理器与通信接口耦合。示例性地,通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。
第七方面,本申请提供了一种通信***,该通信***包括上述第一至第四方面及第一至第四方面的任一种可能实现方式中的第一终端设备和第二终端设备。可选地,该通信***还包括网络设备。
第八方面,本申请提供了一种芯片,所述芯片与存储器相连,用于读取并执行所述存储器中存储的软件程序,以实现上述第一至第四方面及第一至第四方面的任一种可能实现方式中的方法。
第九方面,本申请提供了一种计算机可读存储介质,所述计算机存储介质上存储有计算机程序(也可以称为代码,或指令),当所述计算机程序在被处理器运行时,使得上述第一方面至第四方面和第一方面至第四方面中任一种可能实现方式中的方法被执行。
第十方面,本申请提供了一种计算机程序产品。所述计算机程序产品包括:计算机程序(也可以称为代码,或指令),当所述计算机程序被运行时,使得上述第一方面至第四方面和第一方面至第四方面中任一种可能实现方式中的方法被执行。
应当理解的是,本申请的第五方面至第十方面与本申请的第一方面至第四方面的技术方案相对应,各方面及对应的可行实施方式所取得的有益效果相似,此处不再赘述。
图1至图3是适用于本申请实施例提供的DRX配置方法的通信***的示意图;
图4是目标地址、业务和QoS流的关系的示意图;
图5和图6是DRX的示意图;
图7是本申请实施例提供的DRX配置方法的示意性流程图;
图8是本申请另一实施例提供的DRX配置方法的示意性流程图;
图9是直连通信建立流程的示意图;
图10是本申请又一实施例提供的DRX配置方法的示意性流程图;
图11和图12是本申请实施例提供的通信装置的示意性框图;
图13是本申请实施例提供的终端设备的结构示意图。
下面将结合附图,对本申请中的技术方案进行描述。
本申请提供的技术方案可以应用于各种通信***,例如:第五代(5th generation,5G)移动通信***或新无线接入技术(new radio access technology,NR)。其中,5G移动通信***可以包括非独立组网(non-standalone,NSA)和/或独立组网(standalone,SA)。
本申请提供的技术方案还可以应用于机器类通信(machine type communication,MTC)、机器间通信长期演进技术(Long Term Evolution-machine,LTE-M)、设备到设备(device-to device,D2D)网络、机器到机器(machine to machine,M2M)网络、物联网(internet of things,IoT)网络或者其他网络。其中,IoT网络例如可以包括车联网。其中,车联网***中的通信方式统称为车到其他设备(vehicle to X,V2X,X可以代表任何事物)***,例如,该V2X可以包括:车辆到车辆(vehicle to vehicle,V2V)通信,车辆与基础设施(vehicle to infrastructure,V2I)通信、车辆与行人之间的通信(vehicle to pedestrian,V2P)或车辆与网络(vehicle to network,V2N)通信等。
本申请提供的技术方案还可以应用于未来的通信***,如第六代移动通信***等。本申请对此不作限定。
本申请实施例中,网络设备可以是任意一种具有无线收发功能的设备。网络设备包括但不限于:演进型节点B(evolved Node B,eNB)、无线网络控制器(radio network controller,RNC)、节点B(Node B,NB)、基站控制器(base station controller,BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如,home evolved NodeB,或home Node B,HNB)、基带单元(baseband unit,BBU),无线保真(wireless fidelity,WiFi)***中的接入点(access point,AP)、无线中继节点(radio relay node,RRN)、无线回传节点、传输点(transmission point,TP)或者发送接收点(transmission and reception point,TRP)等,还可以为5G,如,NR,***中的gNB,或,传输点(TRP或TP),5G***中的基站的一个或一组(包括多个天线面板)天线面板,或者,还可以为构成gNB或传输点的网络节点,如基带单元(BBU),或,分布式单元(distributed unit,DU)等。
在一些部署中,gNB可以包括集中式单元(centralized unit,CU)和DU。gNB还可以包括有源天线单元(active antenna unit,AAU)。CU实现gNB的部分功能,DU实现gNB的部分功能,比如,CU可以负责处理非实时协议和服务,如,可以实现无 线资源控制(radio resource control,RRC)层、业务数据自适应协议(service data adaptation protocol,SDAP)层和/或分组数据汇聚层协议(packet data convergence protocol,PDCP)层的功能。DU可以负责可以处理物理层协议和实时服务。例如可以实现无线链路控制(radio link control,RLC)层、媒体接入控制(media access control,MAC)层和物理(physical,PHY)层的功能。一个DU可以仅连接到一个CU或者连接到多个CU,而一个CU可以连接到多个DU,CU与DU之间可以通过F1接口进行通信。AAU可以实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会被递交至PHY层从而变成PHY层的信息,或者,由PHY层的信息转变而来,因而,在这种架构下,高层信令,如RRC层信令,也可以认为是由DU发送的,或者,由DU+AAU发送的。
可以理解的是,网络设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外,可以将CU划分为接入网(radio access network,RAN)中的网络设备,也可以将CU划分为核心网(core network,CN)中的网络设备,本申请对此不做限定。
网络设备为小区提供服务,终端设备通过网络设备分配的传输资源(例如,频域资源,或者说,频谱资源)与小区进行通信,该小区可以属于宏基站(例如,宏eNB或宏gNB等),也可以属于小小区(small cell)对应的基站,这里的小小区可以包括:城市小区(metro cell)、微小区(micro cell)、微微小区(pico cell)、毫微微小区(femto cell)等,这些小小区具有覆盖范围小、发射功率低等特点,适用于提供高速率的数据传输服务。
在本申请实施例中,终端设备也可以称为用户设备(user equipment,UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。
终端设备可以是一种向用户提供语音/数据连通性的设备,例如,具有无线连接功能的手持式设备、车载设备等。目前,一些终端的举例可以为:手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑(如笔记本电脑、掌上电脑等)、移动互联网设备(mobile internet device,MID)、虚拟现实(virtual reality,VR)设备、增强现实(augmented reality,AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol,SIP)电话、无线本地环路(wireless local loop,WLL)站、个人数字助理(personal digital assistant,PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备,5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network,PLMN)中的终端设备等。
其中,可穿戴设备也可以称为穿戴式智能设备,是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称,如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上,或是整合到用户的衣服或配件的一种便携式设备。可穿 戴设备不仅仅是一种硬件设备,更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能,例如:智能手表或智能眼镜等,以及只专注于某一类应用功能,需要和其它设备如智能手机配合使用,如各类进行体征监测的智能手环、智能首饰等。
此外,终端设备还可以是物联网(Internet of things,IoT)***中的终端设备。IoT是未来信息技术发展的重要组成部分,其主要技术特点是将物品通过通信技术与网络连接,从而实现人机互连,物物互连的智能化网络。IoT技术可以通过例如窄带(narrow band,NB)技术,做到海量连接,深度覆盖,终端省电。
应理解,本申请对于网络设备和终端设备的具体形式均不作限定。
另外,在本申请实施例中,UE和终端设备交替使用,二者所表达的含义是相同的。
在无线通信***中,终端设备之间可以通过侧行链路进行通信。通过侧行链路通信的终端设备之间的接口可以称为PC5接口。
侧行链路通信的一个典型应用场景是V2X。在V2X中,每个车可以视为一个终端设备,终端设备之间可以通过侧行链路直接进行数据传输,而不需要经过网络,这样可以有效地减少通信时延。
图1是适用于本申请实施例的通信方法的通信***的一示意图。图1所示的通信***100可以包括至少一个网络设备和多个终端设备,例如图1中所示的网络设备110、终端设备121至123。网络设备110和各终端设备121至123可分别通过无线空口通信,终端设备121至123之间可以通过车用无线通信技术通信。例如,终端设备121与终端设备122之间也可以相互通信,终端设备121与终端设备123之间也可以相互通信,终端设备122与终端设备123之间也可以相互通信。
需要说明的是,图1所示的通信***100中,终端设备121至123中的一个或多个可以位于网络设备110的覆盖范围内,终端设备121至123中的一个或多个也可以位于网络设备110的覆盖范围外。例如,终端设备121、终端设备122、终端设备123可以都位于网络设备110的覆盖范内;或者,终端设备121位于网络设备110的覆盖范围内,终端设备122和终端设备123位于网络设备110的覆盖范围外;或者,终端设备121和终端设备122位于网络设备110的覆盖范围内,终端设备123位于网络设备110的覆盖范围外;或者,终端设备123位于网络设备110的覆盖范围内,终端设备121和终端设备122位于网络设备110的覆盖范围外;又或者,终端设备121、终端设备122和终端设备123都位于网络设备110的覆盖范围外。为了简洁,这里不一一列举。
应理解,图1仅为示例,示出了一个网络设备和三个终端设备。但这不应对本申请构成任何限定。该通信***100还可以包括更多的网络设备,也可以包括更多或更少的终端设备。本申请实施例对此不作限定。
在图1所示的通信***100中,终端设备可以基于网络设备调度的资源进行侧行链路通信,也可以基于自主竞争的方式,从网络设备预先配置的资源(如资源池(resource pool))中选择未被占用的资源进行侧行链路通信。本申请实施例对此不作限定。
图2是适用于本申请实施例的通信方法的通信***的另一示意图。图2所示的通 信***200是UE到网络的中继(如UE-to-network relay)场景下的通信***。
如图2所示,该通信***200可以包括网络设备210、可实现UE到网络的中继(UE-to-network relay)的UE(可简称为中继UE(relay UE))220、远端UE(remote UE)230。应理解,
在图2中,中继UE 220可以直接与网络设备210通信,远端UE 230可以基于中继UE 220提供的中继服务与网络设备210通信。应理解,远端UE 230与中继UE 220之间的通信接口可以为PC5接口,远端UE 230可通过PC5接口与中继UE 220通信。因此,中继UE 220与远端UE 230之间的通信也可以称为侧行链路通信。
需要说明的是,如果一个UE可以成功建立与中继UE之间的PC5链路,该UE就可以被认为是远端UE。远端UE可能处于无线接入网的覆盖范围内,也可能处于无线接入网的覆盖范围外,本申请实施例对此不作限定。
图3是适用于本申请实施例的通信方法的通信***的又一示意图。图3所示的通信***300是UE到UE的中继(如UE-to-UE relay)场景下的通信***。
UE到UE的中继场景中可以包括至少3个UE,其中至少有一个可以作为中继的UE。如图3所示,通信***300中可以包括至少3个UE,如图中的UE 310、UE 320和UE 330。其中,UE 320为中继UE,UE 310可以直接与中继UE 320通信,UE 330也可以直接与中继UE 320通信,UE 310与UE 330可以基于中继UE 320提供的中继服务进行通信。其中,UE 310例如可以是源UE(source UE),UE 330例如可以是目标UE(target UE)。
应理解,UE 310与UE 320之间的通信接口可以为PC5接口,UE 310可通过PC5接口与UE 320通信。UE 320与UE 330之间的通信接口也可以为PC5接口,UE 320可通过PC5接口与UE 330通信。因此,UE 310与UE 320之间的通信、UE 320与UE 330之间的通信也可以称为侧行链路通信。
应理解,上文结合图1至图3所描述的通信***只是示例性的,不应对本申请实施例构成任何限定。
需要说明的是,侧行链路通信可以支持单播通信、组播通信和广播通信。
其中,单播通信可以是指,将信令和/或数据传输给一个设备。在侧行链路通信中,终端设备之间可以基于单播连接进行通信。该单播连接可以唯一关联一个源层2标识(source layer 2 identifier,source L2 ID)和目标层2标识(destination L2 ID)。
组播通信可以是指,将信令和/或数据同时传输给一组设备。在侧行链路通信中,一个组可以关联一个组标识,上层(如V2X层)可以将该组标识递交到接入层(access stratum,AS),接入层可以将该组标识转换为对应的目标层2标识。或者,当上层没有提供组标识时,接入层也可以基于预先配置的V2X业务类型(service type)与层2标识(L2 ID)的映射关系,确定该组播对应的目标层2标识。换言之,目标层2标识可用于标识一个组。
广播通信可以是指,目的地址为通信***中所有设备的一种传输设备。应理解,这里所述的所有设备也是限定在一个范围之中的;例如,所述的所有设备为对该广播通信业务感兴趣的设备。一个广播通信可对应于一个业务。目标层2标识可以基于预先配置的V2X业务类型与层2标识的映射关系来确定。
为便于理解本申请实施例,首先对本申请中涉及到的术语作简单说明。
1、目标地址(destination):在单播通信中,目标地址可用于标识一个接收UE;在组播通信中,目标地址可用于标识一个组;在广播通信中,目标地址可用于标识一个业务。可以理解,目标地址可以是目标层2标识。或者说,目标层2标识是目标地址的一例。
2、业务质量(quality of service,QoS)流(QoS flow)与QoS参数:QoS流是协议数据单元(protocol data unit,PDU)会话中的一种QoS区分粒度。在5G***中,一个QoS流标识(QoS Flow identifier,QFI)可用于标识一条QoS流。一个PDU会话中可以包括多条QoS流,但每条QoS流的QFI都是不同的。
在本申请实施例中,一个目标地址可以包括一个或多个业务(service),一个业务可以包括一个或多个QoS流。图4示出了目标地址、业务和QoS流的关系。如图所示,一个目标地址可以包括一个或多个业务。每个业务可以包括一个或多个QoS流。
例如在图4中,目标地址1包括3个业务,分别为业务1、业务2和业务3。业务1包括4个业务质量流,分别为业务质量流1、业务质量流2、业务质量流3、业务质量流4;业务2包括2个业务质量流,分别为业务质量流5和业务质量流6;业务3包括1个业务质量流,即,业务质量流7。
每个QoS流可以关联(或者说,对应)一组QoS参数。每个QoS流所关联的QoS参数例如可以由终端设备的上层(比如V2X层)确定,或者也可以从对端的终端设备获取,比如通过PC5-RRC消息或PC5-S消息获取。这里,对端的终端设备具体可以是指与该终端设备进行侧行链路通信的终端设备。
每组QoS参数可以包括如下一项或多项:PC5接口QoS流标识(PC5 QoS flow identifier,PFI)、PC5接口5G业务质量标识(PC5 5QI,PQI)、保证流量比特率(guaranteed flow bit rate,GFBR)、最大流量比特率(maximum flow bit rate,MFBR)、PC5链路聚合最大比特率(PC5 link aggregate maximum bit rate,PC5Link-AMBR)、最小通信距离(range)、资源类型(resource type)、优先级量级(priority level)、包时延预算(packet delay budget,PDB)、包错误率(packet error rate,PER)、滑动窗口(averaging window)和最大数据突发量(maximum data burst volume,MDBV)。因此,一个目标地址可以包括一个或多个QoS流,对应于一组或多组QoS参数。
应理解,标准的PQI可以与一组QoS特征对应。具体地,PQI与QoS特征的对应关系具体可通过协议中预定义的对应关系确定。例如,一个PQI可用于指示默认优先级量级、资源类型、PDB、PER、默认滑动窗口、默认MDBV中的一种或多种。每个QoS流对应的QoS参数可以由标准的PQI映射得到,也可以直接配置。本申请实施例对此不作限定。可以理解,QoS参数包括QoS特征。下文中为便于区分和说明,将通过PQI来配置的与该PQI对应的QoS参数称为QoS特征,也可以称为PQI对应的QoS特征,以便于和除PQI配置的QoS参数之外的其他QoS参数区分。
需要说明的是,在一组QoS参数中,除了可以通过PQI来配置对应的默认优先级等级、PDB、PER、资源类型、默认MDBV、默认滑动窗口等QoS特征,还可以在QoS参数中直接配置优先级等级、PDB、PER、资源类型、MDBV、滑动窗口中的一项或多项。这里所说的直接,是相对于通过PQI来配置的与该PQI对应的QoS特征。或者说,这组QoS参数除了包括PQI对应的QoS特征之外,还可以包括优先级等级、PDB、PER、资源类型、MDBV、滑动窗口中的一项或多项参数。
换言之,一组QoS参数中可能同时配置以下一项或多项参数的两个值:优先级量级、PDB、PER、资源类型、MDBV和滑动窗口。在一组QoS参数中对同一项参数配置两个值时,可以以QoS参数中包括的值(也即通过QoS参数直接配置的值)为准,而将在PQI对应配置的同一项参数的值覆盖。
举例而言,在某个QoS流的PQI中配置了对应的默认优先级量级,而该QoS流的QoS参数也包括优先级量级。因此,对该QoS流可能配置两个优先级量级,一个是PQI对应的默认优先级量级,另一个是QoS参数中直接配置的优先级量级。此情况下,该QoS流的优先级量级以QoS参数中直接配置的值为准,该优先级量级可以覆盖PQI中的默认优先级量级。相反,如果该QoS流的QoS参数中不直接包括优先级量级,但包括PQI,则可采用PQI中的默认优先级量级。
可以理解,这里的“配置”,也可以替换为“包括”、“指示”等。
3、PC5接口:在3GPP中定义的终端设备到终端设备的直接通信接口,可以用于支持任意两个终端设备在预设范围内通过直连链路进行数据传输。基于PC5接口的连接可以称为PC5连接或侧行连接。基于PC5接口的链路可以称为PC5链路或侧行链路。
应理解,PC5接口是终端设备到终端设备的直接通信接口的一种可能的命名,不应对本申请构成任何限定。本申请并不排除在未来的协议中定义其他接口来实现与PC5接口相同或相似功能的可能。
终端设备可以监听侧行链路控制信息(sidelink control information,SCI),以收听可能的发端UE发送的消息。但实际情况是,大部分时间内,发端UE可能并没有发送数据的需求,这大大增加了收端UE的功耗。从节能角度出发,一种非连续接收DRX机制被引入,发端UE和收端UE之间可以基于相同的DRX配置进行侧行链路通信。发端UE和收端UE可以在相同的时段内发送和接收控制信息,如SCI或者物理侧行链路控制信道(physical sidelink control channel,PSSCH),以进行正常通信;并可以在相同的时段内关闭射频(radio frequency,RF)通道,不进行控制信息的发送和接收,以达到节能省电的效果。由于应用于终端设备之间的侧行链路通信,故该DRX配置具体为SL DRX配置。
图5示出了SL DRX配置的一例。如图5所示,发端UE可以在开(on)时刻发送控制信息,在关(off)时刻不发送控制信息;收端UE可以在on时刻监听控制信息,在off时刻不监听控制信息。在一种可能的设计中,SL DRX配置可以包括以下一种或多种定时器:开持续时间定时器(onDurationTimer)、未激活定时器(InactivityTimer)、重传定时器(RetransmissionTimer)、混合自动重传请求(hybrid automatic repeat request,HARQ)-往返时间(round trip time,RTT)-定时器(Timer)以及短周期定时器(shortCycleTimer)等。可选地,SL DRX配置还可以包括时隙偏移(SlotOffset)、长周期起始偏移(LongCycleStartOffset)、短周期(ShortCycle)和长周期(LongCycle)等参数中的一种或多种。
结合图5来看,图5中所示的on时刻也可以用激活时间(active time)表示,on时刻具体可以是指以下任意一个定时器运行的时刻:onDurationTimer、RetransmissionTimer和InactivityTimer,除去on时刻之外的时刻可以为off时刻。换 言之,基于上述onDurationTimer、RetransmissionTimer和InactivityTimer的定时器的运行时刻,便可以确定DRX的on时刻和off时刻。
可选地,该SL DRX配置包含在RRC消息、SIB消息或预配置消息中。
可选地,该SL DRX配置包含在资源池配置中。示例性地,一个资源池配置中可以包括一个或多个SL DRX配置,每个SL DRX配置可以包括以下一项或多项:onDurationTimer、InactivityTimer、SlotOffset、LongCycleStartOffset、ShortCycle和LongCycle等。在这种情况下,图5所示的on时刻具体可以是指onDurationTimer和InactivityTimer中的任意一个定时器运行的时刻。
进一步可选地,资源池配置中还包括一组或多组QoS参数与SL DRX配置的映射关系(即,下文所述的第一映射关系)或业务与SL DRX配置的映射关系(即,下文所述的第二映射关系)。
在另一种可能的设计中,SL DRX配置可以与资源模式(resource pattern)对应。图6示出了与资源模式对应的SL DRX配置。如图6所示,资源模式可以将资源池中的资源分为DRX资源和非DRX资源。其中,DRX资源可对应于图5中的on时刻,非DRX资源可对应于图中的off时刻。基于该资源模式对应的SL DRX配置进行侧行链路通信的终端设备可以在该资源模式中的DRX资源上进行数据的发送或接收,在资源模式中的非DRX资源上不进行数据的发送或接收。
可选地,该SL DRX配置可以包含在资源池(resource pool)配置中。
示例性地,一个资源池配置中可以包括一种或多种资源模式。每种资源模式可以对应一种SL DRX配置。
进一步可选地,资源池配置中还包括一组或多组QoS参数与SL DRX配置的映射关系(即,下文所述的第一映射关系)或业务与SL DRX配置的映射关系(即,下文所述的第二映射关系)。应理解,上文所述的SL DRX配置中的具体内容以及包含DRX配置的信令仅为示例,不应对本申请构成任何限定。本申请对于SL DRX配置的具体方式不作限定。
由于本申请实施例所涉及的DRX配置均为SL DRX配置,为方便说明,下文将SL DRX配置简称为DRX配置。
每个终端设备都可以与一个或多个终端设备通信,从而每个终端设备可以对应于一个或多个目标地址。前已述及,每个目标地址可以包括一个或多个QoS流。而DRX配置与QoS参数是相关的;示例性地,不同的QoS参数表示的不同QoS需求,如时延、可靠性等,不同的QoS需求对应的DRX配置(对应的on时刻的长度和周期等)可以是不同的。如果终端设备针对每个QoS流进行DRX配置,终端设备若基于每个QoS流对应的DRX配置,可能会在射频通道的开、关之间不停切换,并不一定真正达到节能省电的效果。
有鉴于此,本申请提供一种DRX配置方法,以期获得QoS表现和节能省电之间的平衡。
前已述及,DRX配置与QoS参数是相关的,基于DRX配置与QoS参数的相关性,本申请实施例提出了如下技术方案:基于多个QoS流来确定一组目标QoS参数,并基于QoS参数与DRX配置的映射关系和该目标QoS参数,确定目标DRX配置。该目标DRX配置可用于该多个QoS流的传输。
进一步地,如前文结合图4的描述可知,业务与QoS流是相关的,每个业务可以包括一个或多个QoS流,而每个QoS流又可以对应于一组QoS参数,因此DRX配置与业务也是相关的。基于DRX配置与业务的相关性,本申请实施例还提出了如下技术方案:基于多个QoS流来确定一个目标业务,并基于业务与DRX配置的映射关系和该目标业务,确定目标DRX配置。该目标DRX配置可用于该多个QoS流的传输。
下面将结合附图对本申请实施例提供的技术方案做详细说明。
为便于理解,在介绍本申请实施例之前,先做出如下几点说明。
第一,“基于”,也可以替换为“根据”、“参考”、“按照”等。
第二,第一、第二以及各种数字编号仅为描述方便进行的区分,并不用来限制本申请实施例的范围。例如,区分不同的指示信息、不同的终端设备等。
第三,“当……时”、“在……的情况下”、“若”以及“如果”等描述均指在某种客观情况下设备(如,终端设备或者网络设备)会做出相应的处理,并非是限定时间,且也不要求设备(如,终端设备或者网络设备)在实现时一定要有判断的动作,也不意味着存在其它限定。
第四,“默认(default)”,也可以替换为“缺省”。
第五,“包括”,也可以替换为“关联”、“对应”等。
第六,“预先配置”可以通过在设备(例如,终端设备等)中(如,在设备的芯片中)预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现,也可以通过信令预配置,比如其他设备(例如,网络设备等)通过信令预配置等方式来实现,本申请对于其具体的实现方式不做限定。
示例性地,当终端设备处于RRC连接态或时,可以通过RRC专用信令来进行预先配置;当终端设备处于RRC空闲态或非激活态时,可以通过***信息块(system information block,SIB)消息来进行预先配置;当终端设备处于覆盖范围外(out of coverage,OOC)时,可以通过网络设备预先发送的消息,如核心网设备预先发送的预配置消息进行预先配置。
预先配置的内容可以包括以下一项或多项:第一映射关系、第二映射关系、V2X业务类型与层2标识的映射关系、默认DRX配置或公共DRX配置,以及专用DRX配置等。
第七,本申请实施例中涉及到终端设备的上层与接入层之间的交互。其中,上层具体可以是指V2X层或PC5-S层。
下文将结合附图对本申请实施例提供的DRX配置方法做详细说明。在下文实施例中,不失一般性,以第一终端设备确定目标DRX配置为例来描述了各个实施例。可以理解,第二终端设备也可以基于下文实施例所提供的方法来确定目标DRX配置,本申请实施例对此不作限定。
为便于理解,各实施例示出了第一终端设备与第二终端设备之间的交互,但这不应对本申请构成任何限定。第一终端设备可以在确定了目标DRX配置后与第二终端设备交互,也可以在确定目标DRX配置的过程中与第二终端设备交互,但目标DRX配置的确定仍由第一终端设备来执行。
此外,该第一终端设备和第二终端设备例如可以是图1至图3所示的通信***中可进 行侧行链路通信的终端设备。其中,第一终端设备可用于执行下述的DRX配置方法,第二终端设备是与第一终端设备进行侧行链路通信的终端设备。应理解,各附图仅为示例,不应对各个步骤的执行主体构成任何限定。只要能够通过运行记录有本申请实施例的提供的方法的代码的程序,以根据本申请实施例提供的方法,便可以作为本申请实施例提供的方法的执行主体。例如,下文实施例所示的第一终端设备也可以替换为该第一终端设备中的部件,比如芯片、芯片***或其他能够调用程序并执行程序的功能模块。第二终端设备也可以替换为该第二终端设备中的部件,比如芯片、芯片***或其他能够调用程序并执行程序的功能模块等。
图7是本申请实施例提供的非连续接收DRX配置方法700的示意性流程图。图7所示的方法700示出了基于QoS参数与DRX配置的映射关系进行DRX配置的流程。
如图7所示,该方法700可以包括步骤710至步骤740。下面对方法700中的各个步骤做详细说明。
在步骤710中,第一终端设备基于第一目标对应的多组QoS参数,确定目标QoS参数。
这里,第一目标包括:一个目标地址、多个目标地址(也可以称为,一组目标地址)或一个终端设备(如,第一终端设备)。
其中,一个终端设备具体可以是指一个终端设备的所有目标地址。故,第一目标对应一个终端设备具体可以是指第一目标对应一个终端设备的所有目标地址。
多个目标地址具体可以是指一个终端设备的多个目标地址,例如可以是该终端设备的所有目标地址中的部分。故,第一目标对应多个目标地址具体可以是指第一目标对应一个终端设备的部分目标地址。
如前所述,多个目标地址也可以称为一组目标地址。一组目标地址例如可以通过对第一终端设备的目标地址进行分组而得到。本申请实施例对于分组的具体方式不作限定。一示例,该一组目标地址可以是第一终端设备的上层确定的,上层可进一步将该一组目标地址对应的多个目标地址通知给接入层。另一示例,该一组目标地址也可以是第一终端设备的接入层确定的。第一终端设备的上层或接入层例如可以通过设备发现(discovery)过程或直连通信流程获取该一组目标地址对应的多个目标地址。
前已述及,在单播通信中,目标地址可用于标识一个对端终端设备(发送或接收终端设备),故第一目标可以对应于与第一终端设备进行侧行链路通信的一个对端终端设备或多个对端终端设备;在组播通信中,目标地址可用于标识一个组,故第一目标可对应于接收第一终端设备的组播业务的一个或多个组的终端设备;在广播通信中,目标地址可用于标识一个业务,故第一目标可对应于接收该第一终端设备的一个或多个广播业务的终端设备。
基于上文对目标地址与QoS流间关系的描述可知,第一目标可以包括一个或多个QoS流。在本申请实施例中,第一目标包括多个QoS流。该多个QoS流例如可以是一个目标地址中的多个QoS流,也可以是多个目标地址中的多个QoS流,还可以是一个终端设备中的多个QoS流。
因此,第一目标可以是对多个QoS流的统称。在另一种表述中,第一目标可以替换为多个QoS流。步骤710也可以表述为:第一终端设备基于多个QoS流对应的多组QoS参 数,确定目标QoS参数。
每个QoS流对应一组QoS参数。如前所述,每组QoS参数可以包含以下一项或多项:PQI、优先级量级、PER、PDB、MDBV、GFBR、MFBR、PC5链路AMBR、range、资源类型、滑动窗口和PFI等。
基于上文所述的第一目标与QoS流的关系以及QoS流与QoS参数的对应关系可知,第一目标对应的多组QoS参数可以是,一个目标地址包括的多个QoS流对应的多组QoS参数,或多个目标地址包括的多个QoS流对应的多组QoS参数,或第一终端设备中的多个QoS流对应的多组QoS参数。
第一终端设备可以先获取该第一目标中的多个QoS流的信息,再基于该多个QoS流对应的多组QoS参数,确定出目标QoS参数。其中,所述多个QoS流的信息用于指示该多个QoS流。目标QoS参数可以包括如下一项或多项:PQI、优先级量级(priority level)、PER、PDB、MDBV、GFBR、MFBR、PC5链路AMBR、range、资源类型和滑动窗口。
第一终端设备可以通过如下方式确定目标QoS参数。
在一种实现方式中,第一终端设备的上层可以将第一目标包括的多个QoS流的信息发送给AS层,AS层可以根据该多个QoS流对应的多组QoS参数确定目标QoS参数。
在另一种实现方式中,第一终端设备可以通过对端(如第二终端设备)发送的PC5-RRC消息或者PC5-S消息获取该第一目标包括的多个QoS流对应的多组QoS参数,进而根据该多组QoS参数确定目标QoS参数。可选地,第一终端设备是收端终端设备,第二终端设备是发端终端设备。
在又一种实现方式中,第一终端设备可以通过对端(如第二终端设备)发送的PC5-RRC消息或者PC5-S消息直接获取第一目标对应的目标QoS参数。换言之,该第一目标对应的目标QoS参数可以是由第二终端设备确定的。可选地,第一终端设备是收端终端设备,第二终端设备是发端终端设备。
示例性地,目标QoS参数可以通过如下两种可能的实现方式来确定。
在第一种可能的实现方式中,目标QoS参数可以是第一目标中的目标QoS流对应的一组QoS参数。示例性地,第一终端设备可以从多个QoS流中确定目标QoS流,进而将目标QoS流对应的QoS参数作为目标QoS参数。
目标QoS流可以基于第一目标中多个QoS流的某一项QoS参数来确定。
可选地,目标QoS流可以是:第一目标包括的多个QoS流中优先级量级最小的QoS流、或第一目标包括的多个QoS流中PDB最小的QoS流、或第一目标包括的多个QoS流中PER最小的QoS流、或第一目标包括的多个QoS流中MDBV最大的QoS流、或第一目标包括的多个QoS流中GFBR最大的QoS流、或第一目标包括的多个QoS流中MFBR最大的QoS流、或第一目标包括的多个QoS流中PC5链路AMBR最大的QoS流、或第一目标包括的多个QoS流中range最大的QoS流等。
目标QoS流也可以基于第一目标中多个QoS流的多项QoS参数来确定。
可选地,目标QoS流可以是第一目标包括的多个QoS流中满足以下至少两项的QoS流:优先级量级最小、PER最小、PDB最小,以及MDBV最大。
一示例,如果第一目标中存在多个QoS流,优先级量级相同且最小,则可以将该多个QoS流中PDB最小、或PER最小、或MDBV最大的QoS流确定为目标QoS流。
例如,QoS流1与QoS流2的优先级量级相同且最小,QoS流1的PDB比QoS流2的PDB小,则最终确定QoS流1为目标QoS流。
另一示例,如果第一目标中存在多个QoS流,优先级量级相同且最小,PDB相同且最小,则可进一步将该多个QoS流中PER最小、或MDBV最大的QoS流确定为目标QoS流。
例如,QoS流1、QoS流2与QoS流3的优先级量级相同且最小,PDB相同且最小,则可进一步比较QoS流1、QoS流2与QoS流3的PER或MDBR。比如,可将QoS流1、QoS流2与QoS流3中PER最小的QoS流作为目标QoS流。又比如,可将QoS流1、QoS流2与QoS流3中PER最小且MDBV最大的QoS流作为目标QoS流。
又一示例,如果第一目标中存在多个QoS流,优先级量级相同且最小,PER相同且最小,则可进一步将该多个QoS流中PDB最小、或MDBV最大等的QoS流确定为目标QoS流。
再一示例,如果第一目标中存在多个QoS流,优先级量级相同且最小,MDBV相同且最大,则可进一步将该多个QoS流中PDB最小、或PER最小等的QoS流确定为目标QoS流。
与上文示例相似,如果第一目标中存在多个QoS流,PER相同且最小,可以将该多个QoS流中优先级量级最小的QoS流、或PDB最小的QoS流、或MDBV最大的QoS流确定为目标QoS流。
例如,QoS流1与QoS流2的PER相同且最小,QoS流1的优先级量级比QoS流2的优先级量级小,则最终确定QoS流1为目标QoS流。
如果第一目标中存在多个QoS流,PDB相同且最小,可以将该多个QoS流中优先级量级最小的QoS流、或PER最小的QoS流、或MDBV最大的QoS流确定为目标QoS流。
例如,QoS流1与QoS流2的PDB相同且最小,QoS流1的优先级量级比QoS流2的优先级量级小,则最终确定QoS流1为目标QoS流。
如果第一目标中存在多个QoS流,MDBV相同且最大,可以将该多个QoS流中优先级量级最小的QoS流、或PDB最小的QoS流、或PER最小的QoS流确定为目标QoS流。
例如,QoS流1与QoS流2的MDBV相同且最大,QoS流1的优先级量级比QoS流2的优先级量级小,则最终确定QoS流1为目标QoS流。
进一步地,如果第一目标中存在多个QoS流,PER相同且最小,优先级量级相同且最小,则可将该多个QoS流中PDB最小、或MDBV最大的QoS流确定为目标QoS流。
如果第一目标中存在多个QoS流,PDB相同且最小,优先级量级相同且最小,则可将该多个QoS流中PER最小、或MDBV最大等的QoS流确定为目标QoS流。
如果第一目标中存在多个QoS流,MDBV相同且最大,优先级量级相同且最小, 则可将该多个QoS流中PER最小、或PDB最小等的QoS流确定为目标QoS流。
如果第一目标中存在多个QoS流,PER相同且最小,PDB相同且最小,MDBV相同且最大,则可将该多个QoS流中优先级量级最小的QoS流为目标QoS流。
基于上文示例,还可以类推出更多种可能的情况,为了简洁,这里不一一列举。
应理解,上文的多个示例仅为便于理解而示出,不应对本申请构成任何限定。第一终端设备在确定目标QoS流时,可以根据预先定义的某一项或多项QoS参数来确定目标QoS流。这里所述的预先定义的某一项或多项QoS参数例如可以由网络设备预先通过信令通知(例如,RRC专用信令、SIB消息、预配置消息等),也可以由与第一终端设备进行侧行链路通信的终端设备(比如,第二终端设备)预先通过信令(例如,PC5-RRC消息、PC5-S消息等)通知,或者,还可以是协议预定义的,本申请实施例对此不作限定。
在第二种可能的实现方式中,目标QoS参数中的每项QoS参数分别是从上述第一目标包括的多个QoS流对应的多组QoS参数中选择的。示例性地,第一终端设备可以基于每一项QoS参数,从多个QoS流对应的多组QoS参数中选择出一个参数作为目标QoS参数中的一项。
如果每个QoS流对应的QoS参数中包括PQI,则目标QoS参数中的PQI可以将第一目标包含的多个QoS流对应的多组QoS参数中默认优先级量级最小、或PDB最小、或PER最小的PQI确定为目标QoS参数中的PQI。
除了PQI之外,其他QoS参数,如GFBR、MFBR、PC5链路AMBR、range、MDBV等可以分别从该多个QoS流对应的QoS参数中选择。
例如,可以将该多个QoS流对应的多组QoS参数中GFBR的最大值、MFBR的最大值、PC5链路AMBR的最大值、range的最大值、MDBV的最大值分别确定为目标QoS参数中的GFBR、MFBR、PC5Link-AMBR、range、MDBV。
前已述及,如果在该多组QoS参数中,某一项或多项QoS参数(如,优先级量级、PDB、PER、GFBR、MFBR、PC5链路AMBR、range和MDBV中的一项或多项)既包含在PQI中,又直接包含在QoS参数中,也即,对部分QoS参数配置了两个值在这种情况下,QoS参数中直接配置的值可用于覆盖PQI对应的同一项参数的值。则在确定目标QoS参数时,针对目标QoS参数中的PQI,可以根据PQI中未被覆盖的参数来选择。比如,PQI中的默认优先级量级被覆盖,但PDB、PER、默认MDBV、默认滑动窗口和资源类型均未被覆盖,则在该多组QoS参数包含的多个PQI中,可以根据PDB、PER、默认MDBV和默认滑动窗口中的一项或多项参数来选择一个PQI作为目标QoS参数中的PQI。比如,选择PDB最小的PQI,或选择PER最小的PQI,或选择PDB和PER最小的PQI等。而未被包含在PQI中的QoS参数和PQI中被覆盖的那一项或多项参数,均可以从第一目标包含的多个QoS流对应的多组QoS参数中选择。比如,对于优先级量级,可以从多组QoS参数中选择优先级量级最小的作为目标QoS参数中的优先级量级。
如果每个QoS流对应的QoS参数不包括PQI,则目标QoS参数中的每一项参数也可以分别从第一目标包含的多个QoS流对应的多组QoS参数中选择。
例如,可以将该多组QoS参数中优先级量级的最小值、PER的最小值、PDB的最 小值、GFBR的最大值、MFBR的最大值、PC5链路AMBR的最大值、range的最大值、MDBR的最大值分别确定为目标QoS参数中的优先级量级、PER、PDB、GFBR、MFBR、PC5Link-AMBR、range、MDBV。
比如,第一目标包括3个QoS流,分别是QoS流1、QoS流2和QoS流3,其中,QoS流1的PQI中默认优先级量级最小,QoS流2的GFBR最大,QoS流3的MFBR最大,则目标QoS参数可以包括:QoS流1的PQI,QoS流2的GFBR,以及QoS流3的MFBR。
又比如,第一目标包括4个QoS流,分别是QoS流1、QoS流2、QoS流3和QoS流4,其中,QoS流1的优先级量级最小,QoS流2的PDB最小,QoS流3的GFBR最大,QoS流14的MFBR最大,则目标QoS参数可以包括:QoS流1的优先级量级,QoS流2的PDB,QoS流3的GFBR,以及QoS流4的MFBR。可以看到,在第二种实现方式中,目标QoS参数可以是综合第一目标中的多个QoS流对应的多组QoS参数而确定的。
应理解,上文仅为便于理解,结合不同的实现方式示例了目标QoS参数所包含的各项参数,但这不应对本申请构成任何限定。本申请实施例包含但不限于此。
从上文对目标QoS参数的确定可以看到,本申请实施例中针对多个QoS流确定一组目标QoS参数,例如针对一个目标地址、多个目标地址或一个终端设备对应的多个QoS流确定一组目标QoS参数,从而可以在后续确定目标DRX配置时基于较QoS流更大的粒度来配置DRX。也就是说,第一终端设备可以基于较QoS流更大的粒度来维护一套DRX配置。
其中,一个目标地址的粒度小于多个目标地址,多个目标地址的粒度小于一个终端设备。基于一个目标地址来配置DRX相对于基于多个目标地址来配置DRX而言,前者的实现复杂度更高;基于多个目标地址来配置DRX相对于基于一个终端设备来配置DRX而言,前者的实现复杂度更高。换言之,随着粒度的逐渐增大,实现复杂度逐渐降低。
需要说明的是,对于第一目标仅包括一个QoS流的情况,由于一个QoS流可对应一组QoS参数,故该组QoS流便是该第一目标的目标QoS参数。第一终端设备也可以按照下文步骤720至步骤740所描述的流程来确定目标DRX配置,并基于目标DRX配置进行侧行链路通信。
在步骤720中,基于第一映射关系和目标QoS参数,确定目标DRX配置。
其中,该第一映射关系可用于指示QoS参数与DRX配置的对应关系。
在本申请实施例中,QoS参数与DRX配置的对应关系例如可以是至少一组QoS参数与至少一个DRX配置的对应关系。一个DRX配置可对应于一组QoS参数,也可以对应于多组QoS参数。
需要说明的是,该第一映射关系所指示的QoS参数与DRX配置的对应关系中,所述目标DRX配置对应的QoS参数可以是上述目标QoS参数的子集。
例如,目标QoS参数可以与第一映射关系中的一组QoS参数相同。比如,目标QoS参数包括PQI、优先级量级、PER、PDB、MDBV、GFBR,第一映射关系中所指示的一组QoS参数包括PQI、优先级量级、PER、PDB、MDBV、GFBR。
又例如,目标QoS参数可以包括第一映射关系中的一组QoS参数,或者说,第一映射关系中的一组QoS参数可以是目标QoS参数中的部分参数。比如,目标QoS参数包括PQI、优先级量级、PER、PDB、MDBV、GFBR、MFBR,第一映射关系中所指示的一组QoS参数包括优先级量级、PER、PDB、MDBV、GFBR。
应理解,无论是目标QoS参数可以与第一映射关系中的一组QoS参数相同,还是目标QoS参数可以包括第一映射关系中的一组QoS参数,都可以认为在该第一映射关系可以找到一组QoS参数与目标QoS参数匹配,也即可以找到与该目标QoS参数对应的目标DRX配置。
还应理解,当第一映射关系中存在多组QoS参数,都是目标QoS参数的子集时,可优先选择与目标QoS参数相同的一组QoS参数来确定目标DRX配置。
下文中,“匹配”可以是指第一映射关系指示的至少一组QoS参数中,存在一组QoS参数是上述目标QoS参数的子集。即,目标QoS参数与第一映射关系中的一组QoS参数相同,或,目标QoS参数包括第一映射关系中的一组QoS参数。与之相对,“不匹配”可以是指第一映射关系中的任意一组QoS参数都不是上述目标QoS参数的子集。
在本申请实施例中,第一映射关系可以由第一终端设备自行确定,也可以从其他设备接收,还可以从第一终端设备的上层接收。
可选地,在步骤720之前,该方法还包括:第一终端设备接收第一指示信息,该第一指示信息用于指示第一映射关系。
第一种可能的情况是,该第一指示信息可以是从网络设备接收到的。上述第一终端设备接收第一指示信息具体可以包括:第一终端设备接收来自网络设备的第一指示信息。
示例性地,该第一指示信息例如可以携带在无线资源控制(radio resource control,RRC)消息、***信息块(system information block,SIB)消息或预配置消息中。当第一终端设备处于RRC连接态时,该第一指示信息可以携带在从网络设备接收到的RRC消息中。当第一终端设备处于RRC空闲态或非激活态时,该第一指示信息可以携带在从网络设备接收到的SIB消息中。当第一终端设备处于覆盖范围外(OOC)态时,该第一至少信息可以携带在从网络设备接收到的预配置消息中
第二种可能的情况是,该第一指示信息可以是从其他终端设备接收到的。例如,第一终端设备通过接收对端(第二终端设备)发送的PC5-RRC消息或PC5-S消息获取该第一指示信息,该第一指示信息用于指示第一映射关系。相应地,第二终端设备发送该第一指示信息。
第二终端设备可以自行配置该第一映射关系,并将配置好的第一映射关系发送给第一终端设备。可选地,第一终端设备是收端终端设备,第二终端设备是发端终端设备。
第三种可能的情况是,该第一指示信息可以是第一终端设备的接入层从上层(如V2X或PC5-S层)接收到的。上述第一终端设备接收第一指示信息具体可以包括:第一终端设备的接入层接收来自上层的第一指示信息,该第一指示信息用于指示第一映射关系。
第一终端设备的上层可自行配置该第一映射关系,并将配置好的第一映射关系下发至AS层。
应理解,上文列举的几种第一终端设备获取第一指示信息的方式仅为示例,不应对本申请构成任何限定。
除了上述第一映射关系中所指示的对应于不同QoS参数的DRX配置之外,该目标DRX配置还可以是默认(default)DRX配置或公共(common)DRX配置。在使用默认DRX配置或公共DRX配置的情况下,可以认为该目标DRX配置不关联QoS参数。
一种可能的情况是,第一终端设备从第一映射关系中并未找到与目标QoS参数匹配的对应关系。此情况下,第一终端设备可以将默认DRX配置或公共DRX配置作为目标DRX配置。
当然,使用默认DRX配置或公共DRX配置作为目标DRX配置并不限于上述情况。例如,后文的方法1000中示出了在直连通信建立过程中使用默认DRX配置或公共DRX配置的情况。
在本申请实施例中,目标DRX配置对应于第一目标。如前所述,第一目标可以包括一个目标地址、多个目标地址或一个终端设备。换言之,目标DRX配置可对应于一个目标地址,或多个目标地址或一个终端设备。
具体而言,当目标DRX配置对应于一个目标地址时,该目标地址中的多个QoS流均可以基于该目标DRX配置进行侧行链路通信。换言之,侧行链路上的对应于同一个目标地址的多个QoS流的DRX配置是相同的。
当目标DRX配置对应于多个目标地址时,这些目标地址中的多个QoS流均可以基于该目标DRX配置进行侧行链路通信。换言之,侧行链路上的对应于多个目标地址的多个QoS流的DRX配置是相同的。
当目标DRX配置对应于第一终端设备时,该第一终端设备的所有目标地址中的多个QoS流均可以基于该目标DRX配置进行侧行链路通信。换言之,侧行链路上的对应于该第一终端设备的多个QoS流的DRX配置是相同的。
基于上文对目标DRX配置的确定,第一终端设备可以针对第一目标中的多个QoS流配置相同的DRX,从而使得该第一终端设备中的多个QoS流可以基于相同的DRX配置开启和关闭射频通道,从而在一定程度上可以避免第一终端设备在射频通道的开、关之间的切换频率,降低处理复杂度,节能省电。并且,由于是基于目标QoS参数而确定的目标DRX配置,目标QoS参数又是基于上述第一目标对应的多组QoS参数确定的,因此所确定的目标DRX配置在一定程度上能够满足QoS需求,使得该第一终端设备具有较优的QoS表现。
在步骤730中,第一终端设备基于目标DRX配置进行侧行链路通信。
应理解,对于第一终端设备而言,通信可以包括发送或接收。换言之,第一终端设备可以是发端终端设备,也可以是收端终端设备。本申请实施例对此不作限定。
示例性地,该第一终端设备可以基于该目标DRX配置与第二终端设备进行侧行链路通信。
当第一终端设备为发端终端设备时,第二终端设备可以是与第一终端设备进行单 播通信的收端终端设备,也可以是与第一终端设备进行组播通信的一组收端终端设备中的一个,还可以是通信***中接收广播业务的一个收端终端设备。
当第一终端设备为收端终端设备时,第一终端设备可以是与第二终端设备进行单播通信的收端终端设备,也可以是与第二终端设备进行组播通信中的一组收端终端设备中的一个,还可以是通信***中接收该第二终端设备的广播业务的一个收端终端设备。
可选地,在步骤730之前,该方法700还包括:步骤740,第一终端设备向第二终端设备发送目标DRX配置。相应地,第二终端设备接收该目标DRX配置。
第一终端设备例如可以通过PC5-S、PC5-RRC、SL MAC层控制元素(control element,CE)、SL-SIB等信令向第二终端设备发送该目标DRX配置。该目标DRX配置例如可以通过单播、多播或广播的方式来发送。本申请实施例对于携带目标DRX配置的信令以及发送该信令的方式均不作限定。
由此,第一终端设备和第二终端设备便可以基于同一个DRX配置(即,目标DRX配置)进行侧行链路通信。二者可以在相同的时刻进行发送和接收,在相同的时刻关闭射频通道,停止发送和接收。从而可以保证传输的可靠性,从而保证较优的QoS表现。
在本申请实施例中,第一终端设备可以根据第一目标对应的多组QoS参数确定目标QoS参数,进而根据目标QoS参数,以及QoS参数与DRX配置的对应关系,确定目标DRX配置。由此,第一目标中的多个QoS流均可以基于该DRX配置进行侧行链路通信。如此一来,第一终端设备中的多个QoS流可以基于相同的DRX配置开启和关闭射频通道,从而在一定程度上可以避免第一终端设备在射频通道的开、关之间的切换频率,降低处理复杂度,节能省电。并且,由于是基于目标QoS参数而确定的目标DRX配置,目标QoS参数又是基于上述第一目标对应的多组QoS参数确定的,因此所确定的目标DRX配置在一定程度上能够满足QoS需求,使得该第一终端设备具有较优的QoS表现,由此,可以获得QoS表现和节能省电之间的平衡。
除了上文结合图7描述的DRX配置方法之外,本申请实施例还提供了一种DRX配置方法。该方法中,第一终端设备可以基于目标业务来确定目标DRX配置,为DRX配置提供更灵活的配置方式。下面将结合图8对来说明该方法。
图8是本申请另一实施例提供的DRX配置方法的示意性流程图。图8所示的方法800示出了基于业务与DRX配置的映射关系进行DRX配置的流程。
如图8所示,该方法800基于业务与DRX的映射关系进行实现,可以包括步骤810至步骤840。下面对方法800中的各个步骤做详细说明。
在步骤810中,基于第一目标对应的多组QoS参数,确定目标业务。
其中,第一目标包括:一个目标地址、多个目标地址(也可以称为,一组目标地址)或终端设备(如,第一终端设备)。
其中,一个终端设备具体可以是指一个终端设备的所有目标地址。故,第一目标对应一个终端设备具体可以是指第一目标对应一个终端设备的所有目标地址。
多个目标地址具体可以是指一个终端设备的多个目标地址,例如可以是该终端设备的所有目标地址中的部分。故,第一目标对应多个目标地址具体可以是指第一目标对应一个 终端设备的部分目标地址。
如前所述,多个目标地址也可以称为一组目标地址。一组目标地址例如可以通过对第一终端设备的目标地址进行分组而得到。本申请实施例对于分组的具体方式不作限定。一示例,该一组目标地址可以是第一终端设备的上层确定的,上层可进一步将该一组目标地址对应的多个目标地址通知给接入层。另一示例,该一组目标地址也可以是第一终端设备的接入层确定的。第一终端设备的上层或接入层例如可以通过设备发现(discovery)过程或直连通信流程获取该一组目标地址对应的多个目标地址。
前已述及,在单播通信中,目标地址可用于标识一个对端终端设备(发送或接收终端设备),故第一目标可以对应于与第一终端设备进行侧行链路通信的一个对端终端设备或多个对端终端设备;在组播通信中,目标地址可用于标识一个组,故第一目标可对应于接收第一终端设备的组播业务的一个或多个组的终端设备;在广播通信中,目标地址可用于标识一个业务,故第一目标可对应于接收该第一终端设备的一个或多个广播业务的终端设备。
基于上文对目标地址与QoS流间关系的描述可知,第一目标可以包括一个或多个QoS。在本申请实施例中,第一目标包括多个QoS流。该多个QoS流可以是一个目标地址中的多个QoS流,也可以是多个目标地址中的多个QoS流,还可以是一个终端设备中的多个QoS流。基于上文所述的第一目标与QoS流的关系以及QoS流与QoS参数的对应关系可知,第一目标对应的多组QoS参数可以是,一个目标地址包括的多个QoS流对应的多组QoS参数,或多个目标地址包括的多个QoS流对应的多组QoS参数,或第一终端设备中的多个QoS流对应的多组QoS参数。
因此,第一目标可以是对多个QoS流的统称。在另一种表述中,第一目标可以替换为多个QoS流。步骤810也可以表述为:第一终端设备基于多个QoS流对应的多组QoS参数,确定目标业务。
第一终端设备可以先获取该第一目标中的多个QoS流的信息,再基于该多个QoS流对应的多组QoS参数确定出目标业务。
第一终端设备可以通过如下方式确定目标业务。
在一种实现方式中,第一终端设备的上层可以将第一目标包括的多个QoS流的信息发送给接入层,接入层可以根据该多个QoS流对应的多组QoS参数确定目标业务。其中,所述多个QoS流的信息用于指示该多个QoS流。
在另一种实现方式中,第一终端设备可以通过对端(如第二终端设备)发送的PC5-RRC消息或者PC5-S消息获取该第一目标包括的多个QoS流对应的多组QoS参数,进而根据该多组QoS参数确定目标业务。可选地,第一终端设备是收端终端设备,第二终端设备是发端终端设备。
在又一种实现方式中,第一终端设备可以通过对端(如第二终端设备)发送的PC5-RRC消息或者PC5-S消息获取第一目标对应的目标业务。换言之,该第一目标对应的目标业务可以是由第二终端设备确定的。可选地,第一终端设备是收端终端设备,第二终端设备是发端终端设备。
示例性地,第一终端设备可以基于以下一项或多项QoS参数,确定目标业务:优先级量级、PER、PDB、MDBV、GFBR、MFBR、PC5链路AMBR、range和PQI。
在一种可能的实现方式中,第一终端设备可以选择目标QoS流对应的业务为目标业务。
目标QoS流可以基于第一目标中多个QoS流的某一项QoS参数来确定。
可选地,目标QoS流可以是:第一目标包括的多个QoS流中优先级量级最小的QoS流、或第一目标包括的多个QoS流中PDB最小的QoS流、或第一目标包括的多个QoS流中PER最小的QoS流、或第一目标包括的多个QoS流中MDBV最大的QoS流、或第一目标包括的多个QoS流中GFBR最大的QoS流、或第一目标包括的多个QoS流中MFBR最大的QoS流、或第一目标包括的多个QoS流中PC5链路AMBR最大的QoS流、或第一目标包括的多个QoS流中range最大的QoS流等。
比如,第一目标包括业务1、业务2和业务3。业务1中的某个QoS流的优先级量级是业务1、2、3所包括的多个QoS流中最小的QoS流,则可将该业务1确定为目标业务。
目标QoS流也可以基于第一目标中多个QoS流的多项QoS参数来确定。
可选地,目标QoS流可以是第一目标包括的多个QoS流中满足以下至少两项的QoS流:优先级量级最小、PER最小、PDB最小,以及MDBV最大。
一示例,如果第一目标中存在多个QoS流,优先级量级相同且最小,则可以将该多个QoS流中PDB最小、或PER最小、或MDBV最大的QoS流确定为目标QoS流。
另一示例,如果第一目标中存在多个QoS流,优先级量级相同且最小,PDB相同且最小,则可进一步将该多个QoS流中PER最小、或MDBV最大的QoS流确定为目标QoS流。
又一示例,如果第一目标中存在多个QoS流,优先级量级相同且最小,PER相同且最小,则可进一步将该多个QoS流中PDB最小、或MDBV最大等的QoS流确定为目标QoS流。
再一示例,如果第一目标中存在多个QoS流,优先级量级相同且最小,MDBV相同且最大,则可进一步将该多个QoS流中PDB最小、或PER最小等的QoS流确定为目标QoS流。
比如,第一目标包括业务1、业务2和业务3。业务1和业务2中存在多个QoS流,优先级量级相同且最小,但是业务1中的一个QoS流的PER比业务2中任意一个QoS流的PER更小,则可将业务1确定为该第一目标的目标业务。
又比如,第一目标包括业务1、业务2和业务3。业务2和业务3中存在多个QoS流,PER相同且最小,但是业务2中的一个QoS流的优先级量级比业务3中任意一个QoS流的优先级量级更小,则可将业务2确定为该第一目标的目标业务。
基于上文示例,还可以类推出更多种可能的情况,为了简洁,这里不一一列举。
应理解,上文的多个示例仅为便于理解而示出,不应对本申请构成任何限定。第一终端设备在确定目标QoS流时,可以根据预先定义的某一项或多项QoS参数来确定目标QoS流。这里所述的预先定义的某一项或多项QoS参数例如可以由网络设备预先通过信令通知(例如,RRC专用信令、SIB消息、预配置消息等),也可以由与第一终端设备进行侧行链路通信的终端设备(比如,第二终端设备)预先通过信令(例如,PC5-RRC消息、PC5-S消息等)通知,或者,还可以是协议预定义的,本申请实施例对此不作限定。
第一终端设备可以基于目标QoS流确定目标业务。目标业务可以是目标QoS流所 对应的业务,或者说,目标业务可以是目标QoS流所属的业务。以图4所示的业务与QoS流的关系为例,假设目标QoS流为图4中的QoS流1,则目标业务为业务1;假设目标QoS流为图4中的QoS流7,则目标业务为业务3。
从上文对目标业务的确定可以看到,本申请实施例中基于多个QoS流对应的多组QoS参数确定一个目标业务,例如基于一个目标地址、多个目标地址或一个终端设备对应的多组QoS参数确定一个目标业务,从而可以在后续确定目标DRX配置时基于较QoS流更大的粒度来配置DRX。也就是说,第一终端设备可以基于较QoS流更大的粒度来维护一套DRX配置。
其中,一个目标地址的粒度小于多个目标地址,多个目标地址的粒度小于一个终端设备。基于一个目标地址来配置DRX相对于基于多个目标地址来配置DRX而言,前者的实现复杂度更高;基于多个目标地址来配置DRX相对于基于一个终端设备来配置DRX而言,前者的实现复杂度更高。换言之,随着粒度的逐渐增大,实现复杂度逐渐降低。
需要说明的是,对于第一目标仅包括一个QoS流的情况,由于QoS流包含在业务中,该业务便是第一目标的目标业务。第一终端设备也可以按照下文步骤820至步骤840所描述的流程来确定目标DRX配置,并基于目标DRX配置进行侧行链路通信。
在步骤820中,基于第二映射关系和目标业务,确定目标DRX配置。
其中,该第二映射关系可用于指示业务与DRX配置的对应关系。
作为示例而非限定,该第二映射关系具体可用于指示业务类型与DRX配置的对应关系。与此对应,基于第二映射关系和目标业务而确定的目标DRX配置是与目标业务的业务类型对应的DRX配置。
其中,业务类型例如可以通过PSID或者ITS-AID来具体标识。因此,第二映射关系具体可以是PSID与DRX配置的对应关系,或者也可以是ITS-AID与DRX配置的对应关系。
在本申请实施例中,第二映射关系可以由第一终端设备自行确定,也可以从其他设备接收,还可以从第一终端设备的上层接收。本申请实施例对此不作限定。
可选地,在步骤820之前,该方法还包括:第一终端设备接收第二指示信息,该第二指示信息用于指示第二映射关系。
第一种可能的情况是,该第二指示信息可以是从网络设备接收到的。上述第一终端设备接收第二指示信息具体可以包括:第一终端设备接收来自网络设备的第二指示信息,该第二指示信息用于指示第二映射关系。相应地,第二终端设备发送该第二指示信息。
示例性地,该第二指示信息例如可以携带在RRC消息、SIB消息或预配置消息中。当第一终端设备处于RRC连接态时,该第二指示信息可以携带在从网络设备接收到的RRC消息中。当第一终端设备处于RRC空闲态或去激活态时,该第二指示信息可以携带在从网络设备接收到的SIB消息中。当第一终端设备处于OOC态时,该第二指示信息可以携带在从网络设备接收到的预配置消息中。
第二种可能的情况是,该第一指示信息可以是从第二终端设备接收到的。上述第一终端设备接收第二指示信息具体可以包括:第一终端设备接收来自对端(如第二终端设备)的第二指示信息,该第二指示信息用于指示第二映射关系。相应地,第二终 端设备发送该第二指示信息。
第二终端设备可以自行配置该第二映射关系,并将配置好的第二映射关系发送给第一终端设备。可选地,第一终端设备是收端终端设备,第二终端设备是发端终端设备。
第三种可能的情况是,该第二指示信息可以是第一终端设备的接入层从上层接收到的。上述第一终端设备接收第二指示信息具体可以包括:第一终端设备的接入层接收来自上层的第二指示信息,该第一指示信息用于指示第一映射关系。
第一终端设备的V2X层可自行配置该第二映射关系,并将配置好的第二映射关系下发至接入层。
应理解,上文列举的几种第一终端设备获取第一指示信息的方式仅为示例,不应对本申请构成任何限定。
除了上述第二映射关系中所指示的对应于不同业务的DRX配置之外,该目标DRX配置还可以是默认DRX配置或公共DRX配置。在使用默认DRX配置或公共DRX配置的情况下,可以认为该目标DRX配置不关联业务。
一种可能的情况是,第一终端设备从第二映射关系中并未找到与目标业务匹配的对应关系。此情况下,第一终端设备可以将预配置的默认DRX配置或公共DRX配置作为目标DRX配置。
当然,使用默认DRX配置或公共DRX配置作为目标DRX配置并不限于上述情况。例如,后文的方法1000中示出了在直连通信建立过程中使用默认DRX配置或公共DRX配置的情况。
在本申请实施例中,目标DRX配置对应于第一目标。关于目标DRX配置与第一目标的对应关系可参看上文方700中的详细说明,为了简洁,此处不再赘述。
基于上文对目标DRX配置的确定,第一终端设备可以针对第一目标中的多个QoS流配置相同的DRX,从而使得该第一终端设备中的多个QoS流可以基于相同的DRX配置开启和关闭射频通道,从而在一定程度上可以避免第一终端设备在射频通道的开、关之间的切换频率,降低处理复杂度,节能省电。并且,由于是基于目标QoS参数而确定的目标DRX配置,目标QoS参数又是基于上述第一目标对应的多组QoS参数确定的,因此所确定的目标DRX配置在一定程度上能够满足QoS需求,使得该第一终端设备具有较优的QoS表现。
在步骤830中,第一终端设备向第二终端设备发送目标DRX配置。相应地,第二终端设备接收该目标DRX配置。
在步骤840中,第一终端设备基于目标DRX配置进行侧行链路通信。
应理解,步骤830和步骤840可参看上文方法700中的步骤740和步骤730的相关描述,为了简洁,此处不再赘述。
在本申请实施例中,第一终端设备可以根据第一目标对应的多组QoS参数确定目标业务,进而根据目标业务,以及业务与DRX配置的对应关系,确定目标DRX配置。由此,第一目标中的多个QoS流均可以基于该DRX配置进行侧行链路通信。如此一来,第一终端设备中的多个QoS流可以基于相同的DRX配置开启和关闭射频通道,从而在一定程度上可以避免第一终端设备在射频通道的开、关之间的切换频率,降低 处理复杂度,节能省电。并且,由于是基于目标QoS参数而确定的目标DRX配置,目标QoS参数又是基于上述第一目标对应的多组QoS参数确定的,因此所确定的目标DRX配置在一定程度上能够满足QoS需求,使得该第一终端设备具有较优的QoS表现,由此,可以获得QoS表现和节能省电之间的平衡。
上文结合图7和图8详细说明了用于侧行链路通信的DRX配置的具体过程。但在有些情况下,QoS参数或业务类型可能无法获取到。例如,在直连通信建立之前,终端设备可能还未配置QoS参数或业务类型。
图9示出了直连通信建立流程。图9示出了第一终端设备与第二终端设备建立直连通信的具体流程。应理解,该直连通信建立流程用于单播通信的建立。
在步骤910中,第一终端设备向第二终端设备发送直连通信请求(direct communication request,DCR)消息。第二终端设备接收该DCR消息。
在步骤920中,响应于该DCR消息,第二终端设备向第一终端设备发送直连安全建立命令(direct security mode command)消息。第一终端设备接收该安全建立命令消息。
在步骤930中,第一终端设备向第二终端设备发送直连安全建立完成(direct security mode complete)消息。
在步骤940中,第二终端设备向第一终端设备发送直连通信接受(direct command accept)消息。
由此,第一终端设备与第二终端设备之间建立起单播连接。在上述流程所列举的PC5-S消息或PC5-RRC消息中,并没有直接对应的QoS参数或者业务类型。在未配置QoS参数或业务类型的情况下,第一终端设备可能还无法按照上文所述的基于第一映射关系或第二映射关系来确定目标DRX配置的方法,来确定用于该单播连接的目标DRX配置。也就是说,建立单播连接的终端设备之间在完成单播DRX协商之前可能无法对齐DRX配置,这可能会步导致上述消息无法被接收到,进而导致单播连接建立失败以及单播连接配置失败,最终影响侧行链路的通信质量。
鉴于此,本申请实施例还提供了一种DRX配置方法,以期在未配置QoS参数或业务类型的情况下,在需要建立直连通信的终端设备之间对齐DRX配置。
下面将结合图10来描述本申请实施例提供的DRX配置方法。应理解,图10所示的实施例虽然示出了第一终端设备执行DRX配置方法的过程,但这不应对本申请构成任何限定。第二终端设备也可用于执行下述的DRX配置方法,本申请实施例对此不作限定。
图10是本申请又一实施例提供的DRX配置方法的示意性流程图。如图10所示,该方法1000可以包括步骤1010至步骤1030。
在步骤1010中,第一终端设备获取一个或多个DRX配置。
第一终端设备例如可以通过RRC消息、或SIB消息、或预配置消息、或PC5-RRC消息、或PC5-S消息或终端设备的上层或协议预定义获取一个或多个DRX配置。该一个或多个DRX配置可以理解为是预先配置的一个或多个可选的DRX配置,第一终端设备可以基于此来确定合适的DRX配置用于当前的直连通信建立流程。
可选地,该方法1000具体包括:第一终端设备获取第一映射关系或第二映射关系, 该第一映射关系或第二映射关系用于指示一个或多个DRX配置。
如前所述,第一映射关系可用于指示QoS参数与DRX配置的对应关系,第二映射关系可用于指示业务与DRX配置的对应关系。第一终端设备获取第一映射关系,也即,第一终端设备获取QoS参数与DRX配置的对应关系。第一终端设备获取第二映射关系,也即,第二终端设备获取业务与DRX配置的对应关系。基于对第一映射关系或第二映射关系的获取,第一终端设备可以获取上述一个或多个DRX配置。
在步骤1020中,第一终端设备确定第一消息对应的第一DRX配置。
其中,第一消息可以是DRX配置协商完成前的任一PC5-S消息或PC5-RRC消息。该第一消息例如可以包括以下消息中的一种或多种:直连通信请求消息、直连安全建立命令消息、直连安全建立完成消息、直连通信接受消息、设备发现(discovery)过程中的通知(announcement)消息、设备发现过程中的问询(solicitation)消息、设备发现过程中的问询消息的响应(response)消息、UE能力查询侧行链路(UECapabilityEnquirySidelink)消息、UE能力通知侧行链路(UECapabilityInformationSidelink)消息、该第一终端设备与第二终端设备之间自建立直连通信之后的第一条RRC重配置侧行链路(RRCReconfigurationSidelink)消息、该第一终端设备与第二终端设备之间自建立直连通信之后的第一条RRC重配置完成侧行链路(RRCReconfigurationCompleteSidelink)消息。
应理解,下文中涉及的第一终端设备发送或接收到的第一条RRCReconfigurationSidelink消息或第一条RRCReconfigurationCompleteSidelink消息具体可以是指第一终端设备与第二终端设备建立直连通信之后的第一条RRCReconfigurationSidelink消息或第一条RRCReconfigurationCompleteSidelink消息。
可以理解,“直连通信”,也可以替换为“单播连接”。第一终端设备可以通过如下五种可能的实现方式来确定第一消息对应的第一DRX配置:
方式一、
第一终端设备可以先确定第一消息对应的QoS参数(或业务类型),进而可以根据第一消息对应的QoS参数(或业务类型)进一步确定出其对应的第一SL DRX配置。换言之,第一DRX配置可以与第一消息对应的QoS参数(或业务类型)相对应。
示例性地,第一消息对应的QoS参数(或业务类型)可以通过协议预定义,或者,也可以从网络设备接收,如通过RRC消息、SIB消息或预配置消息等,还可以从第一终端设备的上层获取,还可以从对端第一终端设备接收,如通过PC5RRC消息或PC5-S消息等。可以理解,不同的第一消息对应的QoS参数(或业务类型)可以是不同的。例如,DCR消息和安全建立命令消息对应的QoS参数(或业务类型)是不同的。
基于第一消息对应的QoS参数(或业务类型)确定第一DRX配置的具体过程例如可以参看上文结合图7或图8所示的实施例,即,第一终端设备可以基于第一消息对应的QoS参数和第一映射关系确定第一DRX配置,或者,也可以基于第一消息对应的业务类型和第二映射关系确定第一DRX配置。为了简洁,此处对该具体过程不再赘述。
可选地,第一DRX配置为组播或广播对应的DRX配置。也就是说,该第一DRX配置也可用于组播通信或广播通信。
方式二、
第一终端设备将默认DRX配置或公共DRX配置确定为第一DRX配置。
示例性地,每个资源池都可以包括对应的默认DRX配置或公共DRX配置,第一终端设备可以在资源池中使用对应的默认DRX配置或公共DRX配置,进行第一消息的发送或接收。
可以理解,使用该默认DRX配置或公共DRX配置进行第一消息的发送或接收具体可以是指,使用该默认DRX配置或公共DRX配置对应的资源进行第一消息的发送或接收。这里,默认DRX配置或公共DRX配置对应的资源具体可以是指,用于侧行链路上的发送或接收的资源。默认DRX配置或公共DRX配置对应的资源例如可以是图6中所示的DRX资源,或者说,或者也可以是对应于图5所示的on时刻的资源。可以理解,该资源是资源池中的部分资源。
可选地,第一终端设备在发送或接收到直连通信请求消息之后,可以触发使用默认DRX配置或公共DRX配置进行第一消息的发送或接收。进一步可选地,第一终端设备在被上层配置允许发送或接收直连通信请求消息的情况下,可以触发使用默认DRX配置或公共DRX配置进行第一消息的发送或接收。进一步可选地,第一终端设备在对第一消息的目标层2标识或目标层2标识对应的业务感兴趣的情况下,可以触发使用默认DRX配置或公共DRX配置进行第一消息的发送或接收。应理解,目标层2标识对应的业务可以根据前文所述的预先配置的V2X业务类型与层2标识的映射关系来确定。下文中为了简洁,省略对相同或相似情况的说明。
可选地,第一终端设备可以在发送或接收到第一条RRCReconfigurationSidelink消息之后、或第一终端设备在完成单播SL DRX配置协商完成之后,触发停止使用默认DRX配置或公共DRX配置进行第一消息的发送或接收。
可选地,第一终端设备在发送或接收到直连通信请求消息的情况下,启动第一定时器,第一终端设备在第一定时器运行的时刻使用该默认DRX配置或公共DRX配置进行第一消息的发送或接收,第一终端设备在第一定时器超时或者停止运行的时刻停止使用该默认DRX配置或公共DRX配置进行第一消息的发送或接收。其中,第一定时器可以由协议预定义、或由网络设备配置、或由其他终端设备(比如第二终端设备)配置。
可选地,第一终端设备可以在每次发送或者接收到直连通信请求消息的情况下,启动或重启该第一定时器。
可选地,第一终端设备可以在每次发送或接收到第一条RRCReconfigurationSidelink消息的情况下,停止该第一定时器。
方式三、
第一终端设备将专用DRX配置确定为第一SL DRX配置。
示例性地,每个资源池都可以包括对应的专用DRX配置,该专用DRX配置可专门用于第一消息的传输。换言之,第一终端设备在资源池中可以使用对应的专用DRX配置进行第一消息的发送或接收。
可以理解,使用该专用DRX配置进行第一消息的发送或接收具体可以是指,使用该专用DRX配置对应的DRX资源进行第一消息的发送或接收。这里,专用DRX配 置对应的资源具体可以是指,用于侧行链路上的发送或接收的资源。专用DRX配置对应的资源例如可以是图6中所示的DRX资源,或者说,或者也可以是对应于图5所示的on时刻的资源。可以理解,该资源是资源池中的部分资源。
可选地,第一终端设备在发送或接收到单播连接建立请求消息之后,可以触发使用专用DRX配置进行第一消息的发送或接收。进一步可选地,第一终端设备在被上层配置允许发送或接收直连通信请求消息的情况下,可以触发使用专用DRX配置进行第一消息的发送或接收。进一步可选地,第一终端设备在对第一消息的目标层2标识或目标层2标识对应的业务感兴趣的情况下,可以触发使用专用DRX配置进行第一消息的发送或接收。
可选地,第一终端设备在发送或接收到第一条RRCReconfigurationSidelink消息之后、或第一终端设备在完成单播SL DRX配置协商完成之后,触发停止使用专用DRX配置进行第一消息的发送或接收。
可选地,第一终端设备在发送或接收到直连通信请求消息的情况下,启动第一定时器,第一终端设备在第一定时器运行的时刻使用该专用DRX配置进行第一消息的发送或接收,第一终端设备在第一定时器超时或者停止运行的时刻停止使用该专用DRX配置进行第一消息的发送或接收。其中,第一定时器可以由协议预定义、或由网络设备配置、或由其他终端设备(比如第二终端设备)配置。
可选地,第一终端设备可以在每次发送或者接收到单播连接建立请求消息的情况下都会启动或重启该第一定时器。
可选地,第一终端设备可以在每次发送或接收到第一条RRCReconfigurationSidelink消息的情况下,停止该第一定时器。
方式四、
第一终端设备可以将步骤1010中第一终端设备获取的一个或多个DRX配置中QoS要求最高的DRX配置确定为第一DRX配置。换言之,该第一DRX配置是预先获取到的一个或多个DRX配置中QoS要求最高的DRX配置。
其中,QoS要求最高例如可以包括以下一项或多项:优先级量级最小、PER最小、PDB最小,以及MDBV最大。
也就是说,该第一DRX配置可以是多个DRX配置所对应的一组或多组QoS参数中QoS要求最高的一组QoS参数所对应的DRX配置。各DRX配置对应的QoS参数可以根据上文所述的第一映射关系来确定。
示例性地,第一DRX配置为第一消息发送或接收对应的资源池中包括的一个或多个DRX配置所对应的一组或多组QoS参数中,QoS要求最高的一组QoS参数所对应的DRX配置。
第一终端设备例如可以在步骤1010中获取上述一个或多个DRX配置,如,通过获取第一映射关系来获取该一个或多个DRX配置。由于在步骤1010中已经对获取DRX配置的具体方式做了详细说明,为了简洁,此处不再赘述。
需要说明的是,第一消息发送或接收对应的资源池可以是指第一终端设备选择的用于发送第一消息的发送资源池或用于接收第一消息的接收资源池。本申请对于第一终端设备选择资源池的具体方式不作限定。下文中为了简洁,省略对相同或相似情况 的说明。
方式五、
第一终端设备将第一终端设备在步骤1010中获取到的一个或多个DRX配置的并集确定为第一DRX配置。换言之,该第一DRX配置可以是预先获取到的一个或多个DRX配置的并集。
示例性地,第一SL DRX配置为第一消息发送或接收对应的资源池中包括的多个DRX配置的并集。可以理解,第一终端设备可以在对应资源池包括的多个DRX配置对应的每个资源上进行第一消息的发送或接收。
在步骤1030中,第一终端设备基于第一DRX配置进行第一消息的发送或接收。
第一终端设备在第一DRX配置对应的侧行链路资源上进行第一消息的发送或接收。
示例性地,该第一终端设备可以基于该目标DRX配置与第二终端设备进行第一消息的发送或接收。
应理解,在完成了单播连接建立流程之后,第一终端设备可以基于上文提供的方法700或方法800中的DRX配置方法,确定用于侧行链路通信的目标DRX配置。
在本申请实施例中,第一终端设备在直连通信建立阶段,可以先确定该阶段中的第一消息对应的第一DRX配置,进而基于第一DRX配置进行第一消息的发送或接收,因此,建立单播连接的终端设备之间可以在完成单播DRX协商前对齐DRX配置,以便于单播连接得以成功建立,为后续的侧行链路通信提供支持,从而有利于提高侧行链路的通信质量。
应理解,上述本申请提供的实施例中,从第一终端设备和第二终端设备之间交互的角度、以及第一终端设备与网络设备之间交互的角度对本申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能,网络设备和终端设备可以包括硬件结构和/或软件模块,以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬件结构、软件模块、还是硬件结构加软件模块的方式来执行,取决于技术方案的特定应用和设计约束条件。
以下,将结合图11至图13详细说明本申请实施例提供的通信装置。
图11为本申请实施例提供的通信装置1100的示意性框图。应理解,该通信装置1100可以对应于上述方法实施例中的第一终端设备或第二终端设备,并且可以用于执行上述方法实施例中第一终端设备或第二终端设备执行的各个步骤。
如图11所示,该通信装置1100可以包括收发模块1110和处理模块1120。
可选地,该装置1100可对应于图7、图8和图10所示实施例中的第一终端设备,可以包括第一终端设备执行的方法的模块。
具体地,当该装置1100用于执行图7中第一终端设备执行的方法时,该收发模块1110可用于执行上文方法700中的步骤730和步骤740。该处理模块1120可用于执行方法700中的步骤710和步骤720。
示例性地,该收发模块1110可用于基于第一目标对应的多组QoS参数,确定目标QoS参数;该第一目标包括多个QoS流;基于第一映射关系和目标QoS参数,确定目标DRX配置,该第一映射关系用于指示QoS参数与DRX配置的对应关系;该收 发模块1110可用于基于目标DRX配置进行侧行链路通信。
可选地,该第一目标包括:一个目标地址、多个目标地址或终端设备。
可选地,该处理模块1120可用于根据以下一项或多项QoS参数,确定所述目标QoS参数:优先级量级、PER、PDB、MDBV、GFBR、MFBR、PC5链路AMBR、range和PQI,其中,所述PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR和默认滑动窗口。
下文提供了用于确定目标QoS参数的两种可能的实现方式。
在第一种可能的实现方式中,目标QoS参数是第一目标中的目标QoS流对应的一组QoS参数;所述目标QoS流是所述第一目标包括的所述多个QoS流中,优先级量级最小的QoS流、或PER最小的QoS流、或PDB最小的QoS流、或MDBV最大的QoS流。
在第二种可能的实现方式中,目标QoS参数中的每项参数分别是从所述第一目标包括的所述多个QoS流对应的多组QoS参数中选择得到的。
可选地,所述目标DRX配置为默认DRX配置或公共DRX配置。
可选地,该收发模块1110还可用于接收第一指示信息,所述第一指示信息用于指示所述第一映射关系。
第一种可能的情况是,该第一指示信息是由网络设备发送的。该收发模块1110可用于实现接收来自网络设备的第一指示信息。
第二种可能的情况是,该第一指示信息是由第二终端设备发送的。该收发模块1110可用于实现接收来自第二终端设备的第一指示信息。
第三种可能的情况是,该第一指示信息是由该装置1100的上层发送给接入层的。该收发模块1110可配置于该装置1100的接入层,具体可用于实现接收来自该装置1100的上层的第一指示信息。
可选地,该收发模块1110还可用于发送目标DRX配置。
当该装置1100用于执行图8中第一终端设备执行的方法时,该收发模块1110可用于执行上文方法800中的步骤830和步骤840。该处理模块1120可用于执行方法800中的步骤810和步骤820。
示例性地,该处理模块1120可用于基于第一目标对应的多组QoS参数,确定目标业务,该第一目标包括一个或多个业务,每个业务包括一个或多个QoS流;该处理模块1120还用于基于第二映射关系和所述目标业务,确定目标DRX配置,所述第二映射关系用于指示业务与DRX配置的对应关系,所述目标DRX配置对应于所述第一目标;该收发模块1110可用实现基于所述目标DRX配置进行侧行链路通信。
可选地,该第一目标包括:一个目标地址、多个目标地址或终端设备。
可选地,该第二映射关系具体用于指示业务类型与DRX配置的对应关系;该处理模块1120具体可用于实现基于所述第二映射关系和所述目标业务的业务类型,确定所述目标DRX配置。
一示例,所述第二映射关系包括PSID与DRX配置的对应关系,该PSID用于指示业务类型;以及该处理模块1120具体可用于基于PSID与DRX配置的对应关系,以及目标业务的业务类型,确定目标DRX配置。
另一示例,所述第二映射关系包括ITS-AID与DRX配置的对应关系,该ITS-AID用于指示业务类型;该处理模块1120具体可用于实现基于ITS-AID与DRX配置的对应关系,以及目标业务的业务类型,确定目标DRX配置。
可选地,该处理模块1120具体可用于根据以下一项或多项QoS参数,确定目标业务:优先级量级、PER、PDB、MDBV、GFBR、MFBR、PC5链路聚合最大比特率AMBR、range和PQI,其中,PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR和默认滑动窗口。
在一种可能的实现方式中,目标业务是第一目标包括的目标QoS流对应的业务;目标QoS流是第一目标包括的所述多个QoS流中,优先级量级最小的QoS流、或PER最小的QoS流、或PDB最小的QoS流、或MDBV最大的QoS流。
可选地,目标DRX配置为默认DRX配置或公共DRX配置。
可选地,该收发模块1110还可用于接收第二指示信息,所述第二指示信息用于指示所述第二映射关系。
第一种可能的情况是,该第二指示信息是由网络设备发送的。该收发模块1110可用于实现接收来自网络设备的第二指示信息。
第二种可能的情况是,该第二指示信息是由第二终端设备发送的。该收发模块1110可用于实现接收来自第二终端设备的第二指示信息。
第三种可能的情况是,该第二指示信息是由该装置1100的上层发送给接入层的。该收发模块1110可配置于该装置1100的接入层,具体可用于实现接收来自该装置1100的上层的第二指示信息。
可选地,该收发模块1110还可用于发送目标DRX配置。
当该装置1100用于执行图10中第二终端设备执行的方法时,该收发模块1110可用于执行上文方法1000中的步骤1030。该处理模块1120可用于执行方法1000中的步骤1010和步骤1020。
示例性地,该处理模块1120可用于获取一个或多个DRX配置;并可用于确定第一消息对应的第一DRX配置;该收发模块1110可用于基于第一DRX配置进行第一消息的发送或接收。
可选地,该第一DRX配置是与第一消息对应的QoS参数对应的DRX配置,该第一消息的QoS参数是预先配置的,或,协议预定义的。
可选地,该第一DRX配置是与第一消息对应的业务类型对应的DRX配置,该第一消息对应的业务类型是预先配置的,或,协议预定义的。
可选地,该第一DRX配置是默认DRX配置或公共DRX配置。
可选地,该第一DRX配置是专用DRX配置。
可选地,该第一DRX配置是装置1100获取的一个或多个DRX配置中QoS要求最高的DRX配置。其中,QoS要求最高包括以下一项或多项:优先级量级最小、PER最小、PDB最小,以及MDBV最大。
可选地,第一DRX配置是装置1100获取的一个或多个DRX配置的并集。
可选地,该装置1100可对应与图7、图8和图10所示实施例中的第二终端设备,可以包括第二终端设备执行的方法的模块。
具体地,当该装置1100用于执行图7中第二终端设备执行的方法时,该收发模块1110可用于执行上文方法700中的步骤730和步骤740。
示例性地,收发模块1100可用于接收目标DRX配置,该目标DRX配置是基于第一映射关系和目标QoS参数确定的;其中,第一映射关系用于指示QoS参数与DRX配置的对应关系,该目标QoS参数是基于第一目标对应的多组QoS参数确定的;该目标DRX配置对应于第一目标,该第一目标包括第一终端设备的多个QoS流;收发模块1100还用于基于该目标DRX配置进行侧行链路通信。
当该装置1100用于执行图8中第二终端设备执行的方法时,该收发模块1110可用于执行上文方法800中的步骤830和步骤840。
示例性地,收发模块1100可用于接收目标DRX配置,该目标DRX配置是基于第二映射关系和目标业务确定的;其中,该第二映射关系用于指示业务与DRX配置的对应关系,该目标业务是基于第一目标对应的多组QoS参数确定的,该目标DRX配置对应于第一目标,该第一目标包括第一终端设备的一个或多个业务,每个业务包括一个或多个QoS流;收发模块1100还可用于基于该目标DRX配置进行侧行链路通信。
当该装置1100用于执行图10中第二终端设备执行的方法时,该收发模块1110可用于执行上文方法1000中的步骤1030。
示例性地,该收发模块1100可用于基于第一DRX配置进行第一消息的发送或接收。
应理解,当装置1100对应于第二终端设备时,对各术语的相关说明可参看上文中装置1100对应于第一终端设备时的相关描述,为了简洁,此处不再重复。
应理解,本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。另外,在本申请各个实施例中的各功能模块可以集成在一个处理器中,也可以是单独物理存在,也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。
图12是本申请实施例提供的通信装置的另一示意性框图。如图12所示,如图12所示,该通信装置1200包括至少一个处理器1210,用于实现本申请实施例提供的方法中第一终端设备的功能。
示例性地,若通信装置1200对应于上述方法700实施例中的第一终端设备,处理器1210可用于基于第一目标对应的多组QoS参数,确定目标QoS参数,所述第一目标包括多个QoS流;并可用于基于第一映射关系和目标QoS参数,确定目标DRX配置。具体参见方法示例中的详细描述,此处不做赘述。
示例性地,若通信装置1200对应于上述方法800实施例中的第一终端设备,处理器1210可用于基于第一目标对应的多组QoS参数,确定目标业务,所述第一目标包括一个或多个业务,每个业务包括一个或多个QoS流;并可用于基于第二映射关系和所述目标业务,确定目标DRX配置。具体参见方法示例中的详细描述,此处不做赘述。
示例性地,若通信装置1200对应于上述方法1000实施例中的第一终端设备,处理器1210可用于获取一个或多个DRX配置;并可用于确定第一消息对应的第一DRX配置。具体参见方法示例中的详细描述,此处不做赘述。
通信装置1200还可以包括至少一个存储器1220,用于存储程序指令和/或数据。存储器1220和处理器1210耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接,可以是电性,机械或其它的形式,用于装置、单元或模块之间的信息交互。处理器1210可能和存储器1220协同操作。处理器1210可能执行存储器1220中存储的程序指令。所述至少一个存储器中的至少一个可以包括于处理器中。
通信装置1200还可以包括通信接口1230。其中,该通信接口1230可以是收发器、接口、总线、电路或者能够实现收发功能的装置。该通信接口1230用于通过传输介质和其它设备进行通信,从而用于通信装置1200中的装置可以和其它设备进行通信。示例性地,其它设备可以是第二终端设备或网络设备。处理器1210利用通信接口1230收发数据,并用于实现图7、图8和图10对应的实施例中第一终端设备所执行的方法。
本申请实施例中不限定上述处理器1210、存储器1220以及通信接口1230之间的具体连接介质。本申请实施例在图12中以存储器1220、处理器1210以及通信接口1230之间通过总线1240连接,总线在图12中以粗线表示,其它部件之间的连接方式,仅是进行示意性说明,并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示,图12中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
图13是本申请实施例提供的终端设备的结构示意图。该终端设备可应用于如图1、图2、图3所示的***中。如图13所示,该终端设备1300包括处理器1301和收发器1302。可选地,该终端设备1300还包括存储器1303。其中,处理器1301、收发器1302和存储器1303之间可以通过内部连接通路互相通信,传递控制和/或数据信号,该存储器1303用于存储计算机程序,该处理器1301用于从该存储器1303中调用并运行该计算机程序,以控制该收发器1302收发信号。可选地,终端设备1300还可以包括天线1304,用于将收发器1302输出的上行数据或上行控制信令通过无线信号发送出去。
上述处理器1301可以和存储器1303可以合成一个处理装置,处理器1301用于执行存储器1303中存储的程序代码来实现上述功能。具体实现时,该存储器1303也可以集成在处理器1301中,或者独立于处理器1301。该处理器1301可以与图11中的处理模块1120或图12中的处理器1210对应。
上述收发器1302可以与图11中的收发模块1120或图12中的通信接口1230对应。收发器1202可以包括接收器(或称接收机、接收电路)和发射器(或称发射机、发射电路)。其中,接收器用于接收信号,发射器用于发射信号。
可选地,上述终端设备1300还可以包括电源1305,用于给终端设备1300中的各种器件或电路提供电源。
除此之外,为了使得该终端设备设备的功能更加完善,该终端设备1300还可以包括输入单元1306、显示单元1307、音频电路1308、摄像头1309和传感器1310等中的一个或多个,所述音频电路还可以包括扬声器1308a、麦克风1308b等。
应理解,图13所示的终端设备1300能够实现图7、图8和图10所示方法实施例中涉及第一终端设备的各个过程。终端设备1300中的各个模块的操作和/或功能,分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述,为避免重复,此处适当省略详细描述。
当终端设备1300用于执行上文方法实施例中涉及第一终端设备的操作流程时,处理器1301可以用于执行前面方法实施例中描述的由第一终端设备内部实现的动作,而收发器1302可以用于执行前面方法实施例中描述的第一终端设备基于目标DRX配置进行侧行链路通信的动作。具体请见前面方法实施例中的描述,此处不再赘述。
当终端设备1300用于执行上文方法实施例中涉及第二终端设备的操作流程时,处理器1301可以用于执行前面方法实施例中描述的由第二终端设备内部实现的动作,而收发器1302可以用于执行前面方法实施例中描述的第二终端设备基于目标DRX配置进行侧行链路通信的动作。具体请见前面方法实施例中的描述,此处不再赘述。
在本申请实施例中,处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件,可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中,存储器可以是非易失性存储器,比如硬盘(hard disk drive,HDD)或固态硬盘(solid-state drive,SSD)等,还可以是易失性存储器(volatile memory),例如随机存取存储器(random-access memory,RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置,用于存储程序指令和/或数据。
根据本申请实施例提供的方法,本申请还提供一种计算机程序产品,该计算机程序产品包括:计算机程序代码,当该计算机程序代码在计算机上运行时,使得该计算机执行图7、图8和图10所示实施例中第一终端设备执行的方法或第二终端设备执行的方法。
根据本申请实施例提供的方法,本申请还提供一种计算机可读存储介质,该计算机可读存储介质存储有程序代码,当该程序代码在计算机上运行时,使得该计算机执行图7、图8和图10所示实施例中第一终端设备执行的方法或第二终端设备执行的方法。
根据本申请实施例提供的方法,本申请还提供一种通信***,该通信***可以包括前述的第一终端设备和第二终端设备。可选地,该通信***还可以包括前述的网络设备。
本申请实施例提供的技术方案可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时,全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、终端设备或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line,DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机可以存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如,软盘、硬盘、磁带)、光介质(例如,数字视频光盘(digital video disc,DVD))、或者半导体介质等。
在本申请实施例中,在无逻辑矛盾的前提下,各实施例之间可以相互引用,例如方法实施例之间的方法和/或术语可以相互引用,例如装置实施例之间的功能和/或术语可以相互引用,例如装置实施例和方法实施例之间的功能和/或术语可以相互引用。
显然,本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样,倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。
Claims (64)
- 一种非连续接收DRX配置方法,其特征在于,包括:基于第一目标对应的多组业务质量QoS参数,确定目标QoS参数,所述第一目标包括多个QoS流;基于第一映射关系和所述目标QoS参数,确定目标DRX配置,所述第一映射关系用于指示QoS参数与DRX配置的对应关系,所述目标DRX配置对应于所述第一目标;基于所述目标DRX配置进行侧行链路通信。
- 如权利要求1所述的方法,其特征在于,所述第一目标包括:一个目标地址、多个目标地址或终端设备。
- 如权利要求1或2所述的方法,其特征在于,所述基于第一目标对应的多组QoS参数,确定目标QoS参数,包括:根据以下一项或多项QoS参数,确定所述目标QoS参数:优先级量级、包错误率PER、包时延预算PDB、最大数据突发量MDBV、保证流量比特率GFBR、最大流量比特率MFBR、PC5链路聚合最大比特率AMBR、最小通信距离和PC5接口业务质量标识PQI,其中,所述PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR和默认滑动窗口。
- 如权利要求3所述的方法,其特征在于,所述目标QoS参数是所述第一目标中的目标QoS流对应的一组QoS参数;所述目标QoS流是所述第一目标包括的所述多个QoS流中,优先级量级最小的QoS流、或PER最小的QoS流、或PDB最小的QoS流、或MDBV最大的QoS流。
- 如权利要求3所述的方法,其特征在于,所述目标QoS参数中的每项参数分别是从所述第一目标包括的所述多个QoS流对应的多组QoS参数中选择得到的。
- 如权利要求1至5中任一项所述的方法,其特征在于,所述目标DRX配置为默认DRX配置或公共DRX配置。
- 如权利要求1至6中任一项所述的方法,其特征在于,所述方法还包括:接收第一指示信息,所述第一指示信息用于指示所述第一映射关系。
- 如权利要求7所述的方法,其特征在于,所述接收第一指示信息,包括:接入层接收来自上层的所述第一指示信息。
- 如权利要求7所述的方法,其特征在于,所述接收第一指示信息,包括:接收来自网络设备的所述第一指示信息。
- 如1至9中任一项所述的方法,其特征在于,所述方法还包括:发送所述目标DRX配置。
- 一种非连续接收DRX配置方法,其特征在于,包括:基于第一目标对应的多组业务质量QoS参数,确定目标业务,所述第一目标包括一个或多个业务,每个业务包括一个或多个QoS流;基于第二映射关系和所述目标业务,确定目标DRX配置,所述第二映射关系用于指示业务与DRX配置的对应关系,所述目标DRX配置对应于所述第一目标;基于所述目标DRX配置进行侧行链路通信。
- 如权利要求11所述的方法,其特征在于,所述第一目标包括:一个目标地址、多个目标地址或终端设备。
- 如权利要求11或12所述的方法,其特征在于,所述第二映射关系具体用于指示业务类型与DRX配置的对应关系;以及所述基于第二映射关系和所述目标业务,确定目标DRX配置,包括:基于所述第二映射关系和所述目标业务的业务类型,确定所述目标DRX配置。
- 如权利要求13所述的方法,其特征在于,所述第二映射关系包括提供商业务标识符PSID与DRX配置的对应关系,所述PSID用于指示所述业务类型;以及所述基于所述第二映射关系和所述目标业务的业务类型,确定所述目标DRX配置,包括:基于所述PSID与DRX配置的对应关系,以及所述目标业务的业务类型,确定所述目标DRX配置。
- 如权利要求13所述的方法,其特征在于,所述第二映射关系包括智能交通***应用标识符ITS-AID与DRX配置的对应关系,所述ITS-AID用于指示所述业务类型;以及所述基于所述第二映射关系和所述目标业务的业务类型,确定所述目标DRX配置,包括:基于所述ITS-AID与DRX配置的对应关系,以及所述目标业务的业务类型,确定所述目标DRX配置。
- 如权利要求11至15中任一项所述的方法,其特征在于,所述基于第一目标对应的多组QoS参数,确定目标业务,包括:根据以下一项或多项QoS参数,确定所述目标业务:优先级量级、包错误率PER、包时延预算PDB、最大数据突发量MDBV、保证流量比特率GFBR、最大流量比特率MFBR、PC5链路聚合最大比特率AMBR、最小通信距离和PC5接口业务质量标识PQI,其中,所述PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR和默认滑动窗口。
- 如权利要求16所述的方法,其特征在于,所述目标业务是所述第一目标包括的目标QoS流对应的业务;所述目标QoS流是所述第一目标包括的所述多个QoS流中,优先级量级最小的QoS流、或PER最小的QoS流、或PDB最小的QoS流、或MDBV最大的QoS流。
- 如权利要求11至17中任一项所述的方法,所述目标DRX配置为默认DRX配置或公共DRX配置。
- 如权利要求11至18中任一项所述的方法,其特征在于,所述方法还包括:接收第二指示信息,所述第二指示信息用于指示所述第二映射关系。
- 如权利要求19所述的方法,其特征在于,所述接收第二指示信息,包括:接入层接收来自上层的所述第二指示信息。
- 如权利要求19所述的方法,其特征在于,所述接收第二指示信息,包括:接收来自网络设备的所述第二指示信息。
- 如权利要求11至21中任一项所述的方法,其特征在于,所述方法还包括:发送所述目标DRX配置。
- 一种非连续接收DRX配置方法,其特征在于,包括:接收目标DRX配置,所述目标DRX配置是基于第一映射关系和目标业务质量QoS参数确定的;其中,所述第一映射关系用于指示QoS参数与DRX配置的对应关系,所述目标QoS参数是基于第一目标对应的多组QoS参数确定的;所述目标DRX配置对应于所述第一目标,所述第一目标包括第一终端设备的多个QoS流;基于所述目标DRX配置进行侧行链路通信。
- 如权利要求23所述的方法,其特征在于,所述第一目标包括:一个目标地址、多个目标地址或终端设备。
- 如权利要求23或24所述的方法,其特征在于,所述目标QoS参数根据以下一项或多项参数确定:优先级量级、包错误率PER、包时延预算PDB、最大数据突发量MDBV、保证流量比特率GFBR、最大流量比特率MFBR、PC5链路聚合最大比特率AMBR、最小通信距离和PC5接口业务质量标识PQI,其中,所述PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR和默认滑动窗口。
- 一种非连续接收DRX配置方法,其特征在于,包括:接收目标DRX配置,所述目标DRX配置是基于第二映射关系和目标业务确定的;其中,所述第二映射关系用于指示业务与DRX配置的对应关系,所述目标业务是基于第一目标对应的多组业务质量QoS参数确定的,所述目标DRX配置对应于所述第一目标,所述第一目标包括第一终端设备的一个或多个业务,每个业务包括一个或多个QoS流;基于所述目标DRX配置进行侧行链路通信。
- 如权利要求26所述的方法,其特征在于,所述第一目标包括:一个目标地址、多个目标地址或终端设备。
- 如权利要求26或27所述的方法,其特征在于,所述第二映射关系具体用于指示业务类型与DRX配置的对应关系。
- 如权利要求26至28中任一项所述的方法,其特征在于,所述目标业务根据以下一项或多项QoS确定:优先级量级、包错误率PER、包时延预算PDB、最大数据突发量MDBV、保证流量比特率GFBR、最大流量比特率MFBR、PC5链路聚合最大比特率AMBR、最小通信距离和PC5接口业务质量标识PQI,其中,所述PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR和默认滑动窗口。
- 一种通信装置,其特征在于,包括:处理模块,用于基于第一目标对应的多组业务质量QoS参数,确定目标QoS参数,所述第一目标包括多个QoS流;并用于基于第一映射关系和所述目标QoS参数,确定目标DRX配置,所述第一映射关系用于指示QoS参数与DRX配置的对应关系,所述目标DRX配置对应于所述第一目标;收发模块,用于基于所述目标DRX配置进行侧行链路通信。
- 如权利要求30所述的装置,其特征在于,所述第一目标包括:一个目标地址、多个目标地址或终端设备。
- 如权利要求30或31所述的装置,其特征在于,所述处理模块具体用于:根据以下一项或多项QoS参数,确定所述目标QoS参数:优先级量级、包错误率PER、包时延预算PDB、最大数据突发量MDBV、保证流量比特率GFBR、最大流量比特率MFBR、PC5链路聚合最大比特率AMBR、最小通信距离和PC5接口业务质量标识PQI,其中,所述PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR和默认滑动窗口。
- 如权利要求32所述的装置,其特征在于,所述目标QoS参数是所述第一目标中的目标QoS流对应的一组QoS参数;所述目标QoS流是所述第一目标包括的所述多个QoS流中,优先级量级最小的QoS流、或PER最小的QoS流、或PDB最小的QoS流、或MDBV最大的QoS流。
- 如权利要求32所述的装置,其特征在于,所述目标QoS参数中的每项参数分别是从所述第一目标包括的所述多个QoS流对应的多组QoS参数中选择得到的。
- 如权利要求30至34中任一项所述的装置,其特征在于,所述目标DRX配置为默认DRX配置或公共DRX配置。
- 如权利要求30至35任一项所述的装置,其特征在于,所述收发模块还用于接收第一指示信息,所述第一指示信息用于指示所述第一映射关系。
- 如权利要求36所述的装置,其特征在于,所述处理模块配置于所述装置的接入层,具体用于接收来自所述装置的上层的所述第一指示信息。
- 如权利要求36所述的装置,其特征在于,所述收发模块具体用于接收来自网络设备的所述第一指示信息。
- 如权利要求30至38任一项所述的装置,其特征在于,所述收发模块还用于发送所述目标DRX配置。
- 一种通信装置,其特征在于,包括:处理模块,用于基于第一目标对应的多组业务质量QoS参数,确定目标业务,所述第一目标包括一个或多个业务,每个业务包括一个或多个QoS流;并用于基于第二映射关系和所述目标业务,确定目标DRX配置,所述第二映射关系用于指示业务与DRX配置的对应关系,所述目标DRX配置对应于所述第一目标;收发模块,用于基于所述目标DRX配置进行侧行链路通信。
- 如权利要求40所述的装置,其特征在于,所述第一目标包括:一个目标地址、多个目标地址或终端设备。
- 如权利要求40或41所述的装置,其特征在于,所述第二映射关系具体用于指示业务类型与DRX配置的对应关系;以及所述处理模块具体用于,基于所述第二映射关系和所述目标业务的业务类型,确定所述目标DRX配置。
- 如权利要求42所述的装置,其特征在于,所述第二映射关系包括提供商业务标识符PSID与DRX配置的对应关系,所述PSID用于指示所述业务类型;以及所述处理模块具体用于,基于所述PSID与DRX配置的对应关系,以及所述目标 业务的业务类型,确定所述目标DRX配置。
- 如权利要求42所述的装置,其特征在于,所述所述第二映射关系包括智能交通***应用标识符ITS-AID与DRX配置的对应关系,所述ITS-AID用于指示所述业务类型;以及所述处理模块具体用于,基于所述ITS-AID与DRX配置的对应关系,以及所述目标业务的业务类型,确定所述目标DRX配置。
- 如权利要求40至44任一项所述的装置,其特征在于,所述处理模块具体用于,根据以下一项或多项QoS参数,确定所述目标业务:优先级、包错误率PER、包时延预算PDB、最大数据突发量MDBV、保证流量比特率GFBR、最大流量比特率MFBR、PC5链路聚合最大比特率AMBR、最小通信距离和PC5接口业务质量标识PQI,其中,所述PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR和默认滑动窗口。
- 如权利要求45所述的装置,其特征在于,所述目标业务是所述第一目标包括的目标QoS流对应的业务;所述目标QoS流是所述第一目标包括的所述多个QoS流中,优先级量级最小的QoS流、或PER最小的QoS流、或PDB最小的QoS流、或MDBV最大的QoS流。
- 如权利要求40至46任一项所述的装置,其特征在于,所述目标DRX配置为默认DRX配置或公共DRX配置。
- 如权利要求40至47任一项所述的装置,其特征在于,所述收发模块还用于接收第二指示信息,所述第二指示信息用于指示所述第二映射关系。
- 如权利要求48所述的装置,其特征在于,所述收发模块配置于所述装置的接入层,具体用于接收来自所述装置的上层的所述第二指示信息。
- 如权利要求48所述的装置,其特征在于,所述收发模块具体用于接收来自网络设备的所述第二指示信息。
- 如权利要求40至50任一项所述的装置,其特征在于,所述收发模块还用于发送所述目标DRX配置。
- 一种通信装置,其特征在于,包括:收发模块,用于接收目标DRX配置,所述目标DRX配置是基于第一映射关系和目标业务质量QoS参数确定的;其中,所述第一映射关系用于指示QoS参数与DRX配置的对应关系,所述目标QoS参数是基于第一目标对应的多组QoS参数确定的;所述目标DRX配置对应于所述第一目标,所述第一目标包括第一终端设备的多个QoS流;并用于基于所述目标DRX配置进行侧行链路通信。
- 如权利要求52所述的装置,其特征在于,所述第一目标包括:一个目标地址、多个目标地址或终端设备。
- 如权利要求52或53所述的装置,其特征在于,所述目标QoS参数根据以下一项或多项参数确定:优先级量级、包错误率PER、包时延预算PDB、最大数据突发量MDBV、保证流量比特率GFBR、最大流量比特率MFBR、PC5链路聚合最大比特率AMBR、最小通信距离和PC5接口业务质量标识PQI,其中,所述PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR 和默认滑动窗口。
- 一种通信装置,其特征在于,包括:收发模块,用于接收目标DRX配置,所述目标DRX配置是基于第二映射关系和目标业务确定的;其中,所述第二映射关系用于指示业务与DRX配置的对应关系,所述目标业务是基于第一目标对应的多组业务质量QoS参数确定的,所述目标DRX配置对应于所述第一目标,所述第一目标包括第一终端设备的一个或多个业务,每个业务包括一个或多个QoS流;并用于基于所述目标DRX配置进行侧行链路通信。
- 如权利要求55所述的装置,其特征在于,所述第一目标包括:一个目标地址、多个目标地址或终端设备。
- 如权利要求55或56所述的装置,其特征在于,所述第二映射关系具体用于指示业务类型与DRX配置的对应关系。
- 如权利要求55至57中任一项所述的装置,其特征在于,所述目标业务根据以下一项或多项QoS确定:优先级量级、包错误率PER、包时延预算PDB、最大数据突发量MDBV、保证流量比特率GFBR、最大流量比特率MFBR、PC5链路聚合最大比特率AMBR、最小通信距离和PC5接口业务质量标识PQI,其中,所述PQI用于指示以下QoS参数:默认优先级量级、PDB、PER、MDBV、GFBR、MFBR、默认AMBR和默认滑动窗口。
- 一种通信装置,其特征在于,包括处理器,所述处理器用于执行存储器中存储的计算机指令,使得所述装置执行如权利要求1至10中任一项所述的方法。
- 一种通信装置,其特征在于,包括处理器,所述处理器用于执行存储器中存储的计算机指令,使得所述装置执行如权利要求11至22中任一项所述的方法。
- 一种通信装置,其特征在于,包括处理器,所述处理器用于执行存储器中存储的计算机指令,使得所述装置执行如权利要求23至25中任一项所述的方法。
- 一种通信装置,其特征在于,包括处理器,所述处理器用于执行存储器中存储的计算机指令,使得所述装置执行如权利要求26至29中任一项所述的方法。
- 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质中存储有计算机指令,当该指令在计算机上运行时,使得计算机执行权利要求1至24中任一项所述的方法。
- 一种计算机程序,其特征在于,包括程序代码,当计算机运行所述计算机程序时,所述程序代码执行如权利要求1至24中任一项所述的方法。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2021/071917 WO2022151262A1 (zh) | 2021-01-14 | 2021-01-14 | 非连续接收配置方法、通信装置及通信*** |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2021/071917 WO2022151262A1 (zh) | 2021-01-14 | 2021-01-14 | 非连续接收配置方法、通信装置及通信*** |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022151262A1 true WO2022151262A1 (zh) | 2022-07-21 |
Family
ID=82446750
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2021/071917 WO2022151262A1 (zh) | 2021-01-14 | 2021-01-14 | 非连续接收配置方法、通信装置及通信*** |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2022151262A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2024028517A1 (en) * | 2022-08-05 | 2024-02-08 | Sony Group Corporation | Methods for configuring sidelink discontinuous reception of a remote wireless device, a related relay wireless device and a related remote wireless device |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111294899A (zh) * | 2019-06-19 | 2020-06-16 | 展讯通信(上海)有限公司 | 用于drx的不活动定时器控制方法及装置、存储介质、终端、基站 |
WO2021002723A1 (ko) * | 2019-07-04 | 2021-01-07 | 엘지전자 주식회사 | 무선통신시스템에서 사이드링크 drx에 관련된 ue의 동작 방법 |
-
2021
- 2021-01-14 WO PCT/CN2021/071917 patent/WO2022151262A1/zh active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111294899A (zh) * | 2019-06-19 | 2020-06-16 | 展讯通信(上海)有限公司 | 用于drx的不活动定时器控制方法及装置、存储介质、终端、基站 |
WO2021002723A1 (ko) * | 2019-07-04 | 2021-01-07 | 엘지전자 주식회사 | 무선통신시스템에서 사이드링크 drx에 관련된 ue의 동작 방법 |
Non-Patent Citations (1)
Title |
---|
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on architecture enhancements for 3GPP support of advanced Vehicle-to-Everything (V2X) services; Phase 2 (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.776, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V1.0.0, 30 November 2020 (2020-11-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 29, XP051961755 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2024028517A1 (en) * | 2022-08-05 | 2024-02-08 | Sony Group Corporation | Methods for configuring sidelink discontinuous reception of a remote wireless device, a related relay wireless device and a related remote wireless device |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10091636B2 (en) | Probe messaging for direct link connections | |
WO2018137364A1 (zh) | 数据发送方法、数据发送终端以及基站 | |
WO2022104542A1 (zh) | 无线通信方法和通信装置 | |
WO2021239064A1 (zh) | 通信方法及装置 | |
WO2022000336A1 (zh) | 信息传输方法、装置、通信设备及存储介质 | |
CN113228717A (zh) | 一种通信方法及装置 | |
WO2022151262A1 (zh) | 非连续接收配置方法、通信装置及通信*** | |
US20230337319A1 (en) | Methods, devices, and systems for configuring sidelink drx | |
WO2024032260A1 (zh) | 一种通信方法、装置、存储介质以及芯片*** | |
US20230199908A1 (en) | Methods, devices, and systems for configuring sidelink drx | |
WO2022160205A1 (zh) | 一种数据传输方法、终端设备和网络设备 | |
WO2022006852A1 (zh) | 无线通信方法、终端设备和网络设备 | |
WO2014121679A1 (zh) | 一种设备到设备通信数据传输方法、***和用户设备 | |
WO2023015573A1 (zh) | 通信方法、设备及存储介质 | |
WO2023274042A1 (zh) | 一种通信的方法、装置和*** | |
WO2024027615A1 (zh) | 一种通信方法,通信装置及通信*** | |
WO2023050404A1 (zh) | 资源配置方法、设备及存储介质 | |
WO2022067807A1 (zh) | 通信方法和通信装置 | |
WO2024120176A1 (zh) | 一种通信方法、装置及*** | |
WO2024060239A1 (zh) | 通信方法、装置、设备、存储介质及程序产品 | |
WO2023221059A1 (zh) | 无线通信方法、装置、设备、存储介质及程序产品 | |
WO2024001897A1 (zh) | 通信方法和装置 | |
TWI833316B (zh) | 通信方法、裝置、電腦可讀存儲介質、電腦程式產品以及通信系統 | |
US20230044660A1 (en) | Methods and devices for selecting radio bearer mode for multicast broadcast services | |
WO2021138879A1 (zh) | 一种节能参数配置方法及其装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21918470 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 21918470 Country of ref document: EP Kind code of ref document: A1 |