CN115567952A

CN115567952A - Configuration method, device and computer readable storage medium

Info

Publication number: CN115567952A
Application number: CN202110750491.1A
Authority: CN
Inventors: 赵亚利
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2021-07-02
Filing date: 2021-07-02
Publication date: 2023-01-03
Also published as: WO2023274017A1

Abstract

The present application relates to the field of communications technologies, and in particular, to a configuration method, a device, and a computer-readable storage medium. The method comprises the following steps: the terminal sends indication information to the network equipment, wherein the indication information is used for assisting the network equipment to determine whether SL DRX and/or SL DTX configuration needs to be carried out on the terminal. The network equipment receives indication information from the terminal; and the network equipment determines whether the SL DRX and/or SL DTX configuration needs to be carried out on the terminal or not according to the indication information.

Description

Configuration method, device and computer readable storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a configuration method, a device, and a computer-readable storage medium.

Background

For multicast and broadcast of direct communication, whether or not to use the direct communication link Discontinuous Reception (SL DRX) and/or the direct communication link Discontinuous Reception (SL DTX) depends on a transmitting terminal (UE). For example, if the sending UE determines that the data to be sent is for a UE that supports SL DRX/SL DTX and a UE that does not support SL DRX/SL DTX at the same time, the SL DRX/SL DTX may not be used; SL DRX/SL DTX may be used if the sending UE determines that the data currently being sent is for only UEs that support SL DRX/SL DTX.

Since whether to use SL DRX/SL DTX depends on the sending UE and the network does not know, for the UE to be in a Radio Resource Control (RRC) connected state and sent using a direct communication interface in a Resource allocation mode of network scheduling, the network device cannot accurately determine the Active Time (Active Time) of the UE on the direct communication interface, and thus cannot perform appropriate scheduling.

Disclosure of Invention

Embodiments of the present application provide a configuration method, a device, and a computer-readable storage medium, which are used to solve a problem in the prior art that a network side cannot know whether to use SL DRX/SL DTX, so that the network side cannot perform appropriate scheduling.

In a first aspect, an embodiment of the present application provides a configuration method, where the method includes:

the terminal sends indication information to the network equipment, and the indication information is used for assisting the network equipment to determine whether the terminal needs to be subjected to SL DRX and/or SL DTX configuration.

In a possible embodiment, the indication information includes any one of:

tx profile, which is configured by a terminal high layer to a terminal low layer;

first information, the first information indicates a protocol version used by the terminal under the condition of SL data transmission, and/or whether the terminal supports SL DRX and/or SL DTX under the condition of SL data transmission;

second information indicating a protocol version used in a case where the terminal performs SL data transmission for each target address, and/or whether or not SL DRX and/or SL DTX is supported in a case where the terminal performs SL data transmission for each target address;

third information, the third information indicates a protocol version used by the terminal in the case of transmitting SL data to the data corresponding to each QoS profile or QoS profile list of each target address, and/or whether SL DRX and/or SL DTX is supported in the case of transmitting SL data to the data corresponding to each QoS profile or QoS profile list of each target address;

fourth information, which indicates a protocol version used by the terminal in a case of performing SL data transmission on data corresponding to each QoS profile or QoS profile list, and/or whether SL DRX and/or SL DTX is supported by the terminal in a case of performing SL data transmission on data corresponding to each QoS profile or QoS profile list;

the protocol version comprises a first protocol version and a second protocol version, and the SL DRX and/or the SL DTX are/is supported under the condition that the terminal uses the first protocol version, and the SL DRX and/or the SL DTX are/is not supported under the condition that the terminal uses the second protocol version.

In one possible embodiment, tx profile is used to indicate any of the following:

the corresponding relation between the SL service of the terminal and the protocol version, and/or whether the SL service of the terminal supports SL DRX and/or SL DTX;

the protocol version used under the condition that the terminal sends SL data, and/or whether the terminal supports SL DRX and/or SL DTX under the condition that the terminal sends SL data;

a protocol version used in the case of the terminal transmitting SL data to each destination address, and/or whether SL DRX and/or SL DTX is supported in the case of the terminal transmitting SL data to each destination address;

the protocol version used by the terminal under the condition of transmitting the SL data to the data corresponding to each QoS profile or QoS profile list of each target address, and/or whether the terminal supports SL DRX and/or SL DTX under the condition of transmitting the SL data to the data corresponding to each QoS profile or QoS profile list of each target address.

In a possible implementation, the identification of the QoS profile in the indication information includes any one of the following:

PQI corresponding to QoS profile;

under the condition that the terminal carries out SL DRX and/or SL DTX on the QoS profile according to the SIB, determining the serial number of the QoS profile according to the sequence of the QoS profile in the SIB;

the number of QoS profile indicated in SIB or dedicated signalling received by the terminal from the network device.

In one possible implementation, the sending the indication information to the network device includes:

sending indication information to network equipment through a first signaling;

wherein the first signaling comprises any one of:

SidelinkUEInformation；

RRC signaling;

MAC CE。

the indication information is transmitted to the network device after the Tx profile received by the lower layer of the terminal from the upper layer of the terminal.

In a second aspect, an embodiment of the present application provides a configuration method, where the method includes:

the network equipment receives indication information from the terminal;

and the network equipment determines whether the SL DRX and/or SL DTX configuration needs to be carried out on the terminal or not according to the indication information.

In a possible embodiment, the indication information includes any one of:

tx profile, wherein the Tx profile is configured to a terminal lower layer by a terminal upper layer;

first information, the first information indicates a protocol version used in the case of the terminal performing SL data transmission, and/or whether SL DRX and/or SL DTX is supported in the case of the terminal performing SL data transmission;

fourth information indicating a protocol version used in a case where the terminal performs SL data transmission on data corresponding to each QoS profile or QoS profile list, and/or whether SL DRX and/or SL DTX is supported in a case where the terminal performs SL data transmission on data corresponding to each QoS profile or QoS profile list;

a protocol version used in the case of the terminal performing SL data transmission, and/or whether or not the terminal supports SL DRX and/or SL DTX in the case of the terminal performing SL data transmission;

In a possible implementation, the identification of the QoS profile in the indication information includes any one of the following items:

a proximity service quality identifier PQI corresponding to QoS profile;

under the condition that the terminal carries out SL DRX and/or SL DTX on the QoS profile according to a system information block SIB, determining the number of the QoS profile according to the sequence of the QoS profile in the SIB;

In one possible implementation, receiving the indication information from the terminal includes:

receiving indication information from a terminal through first signaling;

wherein the first signaling comprises any one of:

SidelinkUEInformation；

RRC signaling;

MAC CE。

in a possible embodiment, determining whether SL DRX and/or SL DTX configuration needs to be performed for the terminal according to the indication information includes any one of:

when the terminal is determined to need to carry out SL DRX and/or SL DTX when SL data transmission is carried out according to the indication information, carrying out SL DRX and/or SL DTX configuration on the terminal;

when the terminal determines that SL DRX and/or SL DTX are needed when SL data transmission is carried out on the first target address according to the indication information, carrying out SL DRX and/or SL DTX configuration on the first target address;

when determining that SL DRX and/or SL DTX are/is needed when the terminal sends SL data aiming at the first QoS profile of the first target address or the data corresponding to the QoS profile list according to the indication information, carrying out SL DRX and/or SL DTX configuration on the first QoS profile of the first target address of the terminal or the logic channel of the first QoS profile or QoS profile list belonging to the first target address of the terminal;

when determining that SL DRX and/or SL DTX are needed to be performed when the terminal performs SL data transmission for data corresponding to the first QoS profile or QoS profile list according to the indication information, performing SL DRX and/or SL DTX configuration on the first QoS profile or QoS profile list of the terminal or a logic channel of the first QoS profile or QoS profile list belonging to the terminal;

when the terminal is determined not to need to carry out SL DRX and/or SL DTX when SL data transmission is carried out according to the indication information, the terminal is not configured with SL DRX and/or SL DTX;

when the terminal does not need to carry out SL DRX and/or SL DTX when the terminal is determined to carry out SL data transmission aiming at the first target address according to the indication information, the first target address is not subjected to SL DRX and/or SL DTX configuration;

and when determining that the terminal does not need to perform SL DRX and/or SL DTX when performing SL data transmission for the first QoS profile of the first target address or the data corresponding to the QoS profile list according to the indication information, not performing SL DRX and/or SL DTX configuration on the first QoS profile of the first target address of the terminal or the logic channel of the first QoS profile or QoS profile list belonging to the first target address of the terminal.

And when determining that the SL DRX and/or SL DTX do not need to be performed when the terminal performs SL data transmission for the data corresponding to the first QoS profile or the QoS profile list according to the indication information, not performing SL DRX and/or SL DTX configuration on the first QoS profile or the QoS profile list of the terminal or a logical channel of the first QoS profile or the QoS profile list belonging to the terminal.

In a third aspect, an embodiment of the present application provides a terminal, including a first memory, a first transceiver, a first processor:

a first memory for storing a computer program; a first transceiver for transceiving data under the control of the first processor; a first processor for reading the computer program in the first memory and performing the configuration method of the first aspect.

The terminal comprises a first transceiver and a second transceiver, wherein the first transceiver is used for sending indication information to the network equipment by the terminal, and the indication information is used for assisting the network equipment to determine whether the SL DRX and/or the SL DTX configuration of the terminal is needed.

In a possible embodiment, the indication information includes any one of:

first information indicating a protocol version used in the case of the terminal performing SL data transmission, and/or whether SL DRX and/or SL DTX is supported in the case of the terminal performing SL data transmission;

third information, the third information indicates a protocol version used by the terminal in a case of performing SL data transmission on data corresponding to each QoS profile or QoS profile list of each target address, and/or whether SL DRX and/or SL DTX is supported in a case of performing SL data transmission on data corresponding to each QoS profile or QoS profile list of each target address;

PQI corresponding to QoS profile;

sending indication information to network equipment through a first signaling;

wherein the first signaling comprises any one of:

SidelinkUEInformation；

RRC signaling;

MAC CE。

in one possible implementation, the first transceiver is further configured to:

In a fourth aspect, an embodiment of the present application provides a network device, including a second memory, a second transceiver, a second processor:

a second memory for storing a computer program; a second transceiver for transceiving data under the control of the second processor; a second processor for reading the computer program in the second memory and performing the configuration method as in the second aspect.

A second transceiver for the network device to receive the indication information from the terminal;

and the second processor is used for determining whether the terminal needs to be subjected to SL DRX and/or SL DTX configuration by the network equipment according to the indication information.

In a possible embodiment, the indication information includes any one of:

the protocol version used by the terminal under the condition of sending SL data to the data corresponding to each QoS profile or QoS profile list of each target address, and/or whether the terminal supports SL DRX and/or SL DTX under the condition of sending SL data to the data corresponding to each QoS profile or QoS profile list of each target address.

a proximity service quality identification (PQI) corresponding to the QoS profile;

the number of QoS profile indicated in the SIB or dedicated signaling received by the terminal from the network device.

receiving indication information from a terminal through first signaling;

wherein the first signaling comprises any one of:

SidelinkUEInformation；

RRC signaling;

MAC CE。

in one possible implementation, the second processor is further configured to any one of:

when the SL data transmission of the terminal is determined according to the indication information and under the condition that SL DRX and/or SL DTX are needed, the terminal is configured with the SL DRX and/or the SL DTX;

when determining that SL DRX and/or SL DTX are needed when the terminal sends SL data to the first target address according to the indication information, carrying out SL DRX and/or SL DTX configuration on the first target address;

when determining that SL DRX and/or SL DTX are needed to be performed when the terminal performs SL data transmission on the first QoS profile of the first target address or the data corresponding to the QoS profile list according to the indication information, performing SL DRX and/or SL DTX configuration on the first QoS profile or QoS profile list or a logic channel belonging to the first QoS profile or QoS profile list;

and under the condition that the SL DRX and/or SL DTX needs to be carried out when the terminal determines to carry out SL data transmission on the data corresponding to the first QoS profile or the QoS profile list according to the indication information, carrying out SL DRX and/or SL DTX configuration on the first QoS profile or the QoS profile list of the terminal or the logic channel of the first QoS profile or the QoS profile list belonging to the terminal.

when the fact that the terminal does not need to carry out SL DRX and/or SL DTX when the terminal is determined to carry out SL data transmission on the first target address according to the indication information is determined, the first target address is not subjected to SL DRX and/or SL DTX configuration;

and under the condition that the SL DRX and/or SL DTX do not need to be carried out when the terminal determines that the SL data transmission is carried out on the data corresponding to the first QoS profile or the QoS profile list of the first target address according to the indication information, the SL DRX and/or SL DTX configuration is not carried out on the first QoS profile or the QoS profile list or the logic channel belonging to the first QoS profile or the QoS profile list.

And when determining that the terminal does not need to perform SL DRX and/or SL DTX when performing SL data transmission on the data corresponding to the first QoS profile or the QoS profile list according to the indication information, not performing SL DRX and/or SL DTX configuration on the first QoS profile or the QoS profile list of the terminal or a logic channel of the first QoS profile or the QoS profile list belonging to the terminal.

In a fifth aspect, an embodiment of the present application provides a terminal, including:

and the sending unit is used for sending indication information to the network equipment by the terminal, wherein the indication information is used for assisting the network equipment to determine whether the SL DRX and/or SL DTX configuration needs to be carried out on the terminal.

In a possible embodiment, the indication information includes any one of:

second information indicating a protocol version used in a case where the terminal transmits SL data to each destination address, and/or whether or not SL DRX and/or SL DTX is supported when the terminal transmits SL data to each destination address;

a protocol version used in the case that the terminal performs SL data transmission for each target address, and/or whether SL DRX and/or SL DTX is supported in the case that the terminal performs SL data transmission for each target address;

PQI corresponding to QoS profile;

sending indication information to the network equipment through a first signaling;

wherein the first signaling comprises any one of:

SidelinkUEInformation；

RRC signaling;

MAC CE。

in a possible implementation, the sending unit is further configured to:

In a sixth aspect, an embodiment of the present application provides a network device, including:

a receiving unit, configured to receive, by a network device, indication information from a terminal;

and the determining unit is used for determining whether the terminal needs to be subjected to SL DRX and/or SL DTX configuration according to the indication information by the network equipment.

In one possible embodiment, the indication information includes any one of:

PQI corresponding to QoS profile;

In one possible implementation, receiving indication information from a terminal includes:

receiving indication information from a terminal through first signaling;

wherein the first signaling comprises any one of:

SidelinkUEInformation；

RRC signaling;

MAC CE。

in a possible embodiment, the determining unit is further configured to any one of:

when determining that SL DRX and/or SL DTX are/is needed to be performed when the terminal performs SL data transmission on data corresponding to the first QoS profile or the QoS profile list of the first target address according to the indication information, performing SL DRX and/or SL DTX configuration on the first QoS profile or the QoS profile list of the first target address of the terminal or a logic channel of the first QoS profile or the QoS profile list belonging to the first target address of the terminal;

when the SL DRX and/or SL DTX configuration is not needed to be carried out on the first target address when the terminal is determined to carry out SL data transmission on the first target address according to the indication information, the SL DRX and/or SL DTX configuration is not carried out on the first target address;

and when determining that the terminal does not need to perform SL DRX and/or SL DTX when performing SL data transmission on the first QoS profile of the first target address or the data corresponding to the QoS profile list according to the indication information, not performing SL DRX and/or SL DTX configuration on the first QoS profile of the first target address of the terminal or the logic channel of the first QoS profile or QoS profile list belonging to the first target address of the terminal.

In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored, and the computer program is configured to enable a computer to execute the configuration method of the first aspect, or configured to enable a processor to execute the configuration method of the second aspect.

In the embodiment of the application, the terminal assists the network device to determine whether the terminal needs to be subjected to the SL DRX and/or SL DTX configuration through the indication information, and in this way, the network device performs the SL DRX and/or SL DTX configuration for the terminal, so that the network device can be ensured to know the activation time of the direct communication interface of the terminal, thereby more reasonably scheduling the direct communication interface resources and improving the utilization rate of the direct communication interface resources.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

FIG. 1a is a block diagram of a conventional cellular network communication system;

FIG. 1b is a schematic diagram of DRX;

FIG. 1c is a block diagram of a direct communication system;

FIG. 2 is a schematic flow chart of a method provided in an embodiment of the present application;

FIG. 3 is a second flowchart of a method provided by an embodiment of the present application;

fig. 4 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a network device according to an embodiment of the present application;

fig. 6 is a second schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 7 is a second schematic structural diagram of a network device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be implemented, for example, in sequences other than those illustrated or described herein. Moreover, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

In the embodiment of the present application, the term "and/or" describes an association relationship of associated objects, and means that there may be three relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. In the embodiments of the present application, the term "plurality" means two or more, and other terms are similar thereto.

In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

To better understand the solution of the embodiments of the present application, the following is first introduced:

1. cellular network communication

As shown in fig. 1a, in conventional cellular network communication, uplink and downlink data and control information are transmitted between a terminal and a network side device through a Uu interface.

2. DRX mechanism for Uu interface of cellular communication system

In a mobile communication system based on a shared channel, transmission of uplink and downlink data is controlled by a base station scheduler, and when the scheduler determines to schedule a user, the scheduler informs a terminal of what resource to transmit or receive data on through a control channel. The terminal (UE) monitors the control channel, and when the terminal detects that the terminal contains the scheduling information of the terminal, the terminal completes the transmission (uplink) or the reception (downlink) of the data according to the indication on the control channel. In the active state, since the terminal does not determine when the eNB schedules it, a common working mode is that the terminal continuously monitors the control channel and parses each subframe containing its downlink scheduling control channel to determine whether it is scheduled. The working mode can obtain higher efficiency under the condition that the terminal has larger data volume and is likely to be frequently scheduled. However, for some services, the frequency of arrival of data is low, resulting in a small number of times that the terminal is scheduled, which will undoubtedly increase its power consumption if the terminal is still continuously listening to the control channel. In order to solve the problem of power consumption, the cellular network communication system adopts a DRX operation mode, in which the terminal periodically monitors the control channel, thereby achieving the purpose of power saving.

The basic principle of DRX is shown in fig. 1 b. Wherein the On duration represents a time period for the UE to monitor the control channel, and the radio frequency channel is opened and continuously monitors the control channel; at other times except the On duration, the UE is in Sleep state, the radio link is closed, and the UE does not monitor the control channel any more, so as to achieve the purpose of saving power. The On Duration is a periodic occurrence (Cycle), and the specific period is realized by the eNB configuration.

The DRX mechanism of cellular networks takes into account the arrival model of data traffic, i.e. the arrival of data packets is bursty (it can be understood that once a data packet arrives, more packets arrive in a shorter time in succession). In order to adapt to the service arrival characteristics, various timers are adopted in the LTE DRX process and are combined with the HARQ process so as to achieve better power saving performance.

DRX-related timer:

(1) drx-onDurationTimer the time the UE periodically wakes up to listen to the control channel, as shown in FIG. 1 b.

(2) Short DRX cycle Timer: for better matching with the data service arrival characteristics, the cellular network communication system supports the configuration of two DRX cycles: long cycle and short cycle. The on duration timers of the two cycles are the same, but the sleep time is different. In the short cycle, the sleep time is relatively shorter and the UE can listen to the control channel again faster. The Long cycle is necessarily configured and is the initial state of the DRX process; the short cycle is optional. The short DRX cycle timer sets the time for which the short cycle is to be used. After the Short cycle timer times out, the UE will use the Long cycle.

(3) drx-inactivytytimer: after configuring DRX, when the UE receives the control signaling for HARQ initial transmission within a Time allowed to monitor the control channel (Active Time), the UE starts the timer, and before the timer expires, the UE continuously monitors the control channel. If the UE receives the control signaling of the HARQ initial transmission before the drx-inactivity timer is overtime, the drx-inactivity timer is terminated and restarted.

(4) HARQ RTT Timer: the method is divided into drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerUL, and aims to ensure that the UE does not monitor a control channel before the next retransmission arrives, so as to achieve better power saving effect. The following behavior example, the first symbol after PUCCH transmission for UE-related processes starts, and this timer will be turned on. If the data in the corresponding HARQ process is not successfully decoded after the previous HARQ transmission (the UE feeds back NACK), after the DL HARQ RTT Timer is overtime, the UE opens drx-retransmission TimerDL. If the data in the corresponding HARQ process is decoded successfully after the previous HARQ transmission (the UE feeds back ACK), after the expiration of the drx-HARQ-RTT-TimerDL timer, the UE does not start drx-retransmission TimerDL. If only drx-HARQ-RTT-TimerDL is currently running, the UE does not monitor the control channel.

(5) HARQ transmission Timer: classified as drx-retransmission timerdl or drx-retransmission timerll. In the following example, during the running of the DL HARQ retransmission Timer, the UE monitors the control signaling and waits for the retransmission scheduling of the corresponding HARQ process.

Active time definition under DRX:

through the above process, it can be seen that any one of the On duration Timer, HARQ transmission Timer, and Inactivity Timer is running, and the UE will monitor the control channel. The Time when the UE listens to the control channel is also called Active Time. Active Time in the LTE system is affected by other factors besides DRX timer, and Active Time of LTE Rel-8 UE includes the following Time:

(1) Time of run of drx-onDurationTimer or drx-InactivetyTimer or drx-RecransmissionTimerDL or drx-RecransmissionTimeUL or ra-ContentionResolutionTimer;

(2) After the UE sends an uplink Scheduling Request (SR), waiting for a time for the base station to send a Physical Downlink Control Channel (PDCCH);

(3) After receiving a Random Access Response (RAR), the non-contention Random Access UE waits for a time of a PDCCH scheduled by a Cell Radio Network Temporary Identifier (C-RNTI).

3. Direct communication

As shown in fig. 1c, direct communication refers to a manner in which neighboring terminals can perform data transmission through a direct communication link (also referred to as Sidelink) in a short range. The wireless interface to which the sildelink link corresponds is referred to as a direct communication interface, also referred to as a sildelink interface.

The direct communication interface supports three transmission types: unicast, multicast, and broadcast. Multicast and broadcast may be referred to collectively as multicast.

The direct communication interface resource allocation mode is divided into two types:

(1) Resource allocation pattern for network scheduling (also referred to as mode 1): the network equipment allocates resources used for transmitting the direct communication interface data to the terminal;

(2) Terminal-selected resource allocation mode (also called mode 2): i.e. the terminal selects the direct communication transmission resource from a pool of resources available to the direct communication interface on its own.

According to the current mechanism, whether to use SL DRX/DTX depends on sending UE e for direct communication multicast and broadcast, and the network does not know, so for a UE in RRC connected state and sending UE using the direct communication interface of the resource allocation mode (mode 1) of network scheduling, the network device cannot accurately determine the Active Time of the UE on the direct communication interface, so as to perform proper scheduling. This problem needs to be solved, and no relevant solution exists at present.

Embodiments of the present application are described below with reference to the accompanying drawings.

The configuration method, the terminal and the network device provided by the embodiment of the application can be applied to a wireless communication system as shown in fig. 1. The terminal may be a User Equipment (UE), for example: the terminal side Device may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), or a Wearable Device (Wearable Device), and it should be noted that a specific type of the user terminal is not limited in this embodiment of the application. The network device may be a base station of 5G and later protocol versions (e.g., a gNB, a 5G NR NB), or a base station in other communication systems, and in the embodiment of the present application, the specific type of the network device is not limited.

It should be noted that, the scenario addressed by the embodiment of the present application is a direct communication multicast and broadcast scenario.

Referring to fig. 2, an embodiment of the present application provides a configuration method, where an execution subject of the method is a terminal, and the method includes:

step 201: the terminal sends indication information to the network equipment;

in this embodiment of the present application, the indication information is used to assist the network device to determine whether to perform SL DRX and/or SL DTX configuration on the terminal, specifically, the terminal may report a protocol version used by the terminal to the network device through the indication information, and the network device determines whether the terminal supports SL DRX and/or SL DTX through the protocol version used by the terminal, for example: the protocol versions comprise a first protocol version (such as 3GPP Rel-17) _ and a second protocol version (such as 3GPP Rel-16), wherein the terminal supports SL DRX and/or SL DTX when using the first protocol version, and does not support SL DRX and/or SL DTX when using the second protocol version; or, the terminal may also directly report whether or not it supports SL DRX and/or SL DTX to the network device through the indication information.

In the embodiment of the application, the terminal assists the network device to determine whether the terminal needs to be configured with the SL DRX and/or the SL DTX through the indication information, and in this way, the network device performs the SL DRX and/or the SL DTX configuration for the terminal, so that the network device can be ensured to know the activation time of the direct communication interface of the terminal, thereby more reasonably scheduling the direct communication interface resources and improving the utilization rate of the direct communication interface resources.

In one possible embodiment, the indication information includes any one of:

(A) Transmit configuration (Tx profile); it should be noted that the Tx profile is specifically configured by the higher layer of the terminal to the lower layer of the terminal.

(B) The first information indicates a protocol version used under the condition that the terminal carries out SL data transmission, namely implicitly indicates whether the terminal supports SL DRX and/or SL DTX or not through the used protocol version; and/or whether the terminal supports SL DRX and/or SL DTX under the condition that the terminal carries out SL data transmission, namely directly and explicitly indicating whether the terminal supports SL DRX and/or SL DTX;

(C) Second information, the second information indicates the protocol version used in the case that the terminal transmits the SL data to each target address, that is, the second information implicitly indicates whether the terminal supports SL DRX and/or SL DTX by the protocol version used; and/or whether the terminal supports SL DRX and/or SL DTX when the terminal performs SL data transmission for each target address, i.e., whether the terminal supports SL DRX and/or SL DTX is directly explicitly indicated;

it should be noted that the target address refers to an address of an opposite terminal performing SL communication with the terminal, and it can be understood that the terminal can know addresses of all opposite terminals performing SL communication with the terminal in advance, that is, all target addresses, and then indicate, through the second information, a protocol version used when each target address in all the target addresses performs SL data transmission, and/or whether SL DRX and/or SL DTX is supported.

(D) Third information, the third information indicates a protocol version used by the terminal under the condition that the terminal performs SL data transmission on each QoS profile of each target address or data corresponding to the QoS profile list, namely, the third information implicitly indicates whether the terminal supports SL DRX and/or SL DTX through the used protocol version; and/or whether the terminal supports SL DRX and/or SL DTX under the condition that the terminal sends SL data to each QoS profile of each target address or the data corresponding to the QoS profile list, namely directly and explicitly indicating whether the terminal supports the SL DRX and/or the SL DTX;

it should be noted that the destination address refers to an address of a peer terminal performing SL communication with the terminal, and it is understood that the terminal can know addresses of all peer terminals performing SL communication with the terminal in advance, that is, all destination addresses. In addition, for the direct communication interface, the direct communication service is generated by the terminal at a high level, the service can be divided into different QoS flows according to different QoS of the service, each QoS flow corresponds to different QoS profiles, and a group of QoS profile combinations can form a QoS profile list. Here, the protocol version used for SL data transmission per QoS profile or QoS profile list per destination address of the terminal and/or whether SL DRX and/or SL DTX is supported may be indicated by the third information.

(E) Fourth information, the fourth information indicates a protocol version used by the terminal in the case of sending SL data for each QoS profile or data corresponding to the QoS profile list, that is, implicitly indicates whether the terminal supports SL DRX and/or SL DTX by the protocol version used; and/or whether the terminal supports the SL DRX and/or the SL DTX under the condition that the terminal sends the SL data to the data corresponding to each QoS profile or each QoS profile list, namely directly and explicitly indicating whether the terminal supports the SL DRX and/or the SL DTX;

it should be noted that, for the direct communication interface, the direct communication service is generated by the terminal at a high level, and the service may be divided into different QoS flows according to different QoS of the service, where each QoS flow corresponds to a different QoS profile, and a QoS profile list may be formed by a group of QoS profile combinations. Here, the terminal may be instructed through the fourth information about a protocol version used when transmitting SL data per QoS profile or QoS profile list, and/or whether SL DRX and/or SL DTX is supported.

It is to be understood that (B) to (E) above are granularities for different SL DRX and/or SL DTX.

(1) The corresponding relation between the SL service of the terminal and the protocol version, and/or whether the SL service of the terminal supports SL DRX and/or SL DTX;

(2) The protocol version used under the condition that the terminal sends SL data, and/or whether the terminal supports SL DRX and/or SL DTX under the condition that the terminal sends SL data;

(3) A protocol version used in the case of the terminal transmitting SL data to each destination address, and/or whether SL DRX and/or SL DTX is supported in the case of the terminal transmitting SL data to each destination address;

(4) The protocol version used by the terminal under the condition of transmitting the SL data to the data corresponding to each QoS profile or QoS profile list of each target address, and/or whether the terminal supports SL DRX and/or SL DTX under the condition of transmitting the SL data to the data corresponding to each QoS profile or QoS profile list of each target address.

In this embodiment of the application, when the Tx profile is carried in the indication information, the Tx profile may be used to indicate the content indicated by the first information, the second information, or the third information.

(1) A proximity service quality identifier (ProSe QoS indicator, PQI) corresponding to QoS profile;

(2) Under the condition that the terminal carries out SL DRX and/or SL DTX on the QoS profile according to the SIB, the serial number of the QoS profile is determined according to the sequence of the QoS profile in the SIB, namely the serial number of the QoS profile or the QoS profile list is implicitly determined according to the sequence of the QoS profile or the QoS profile list in the SIB;

(3) The number of the QoS profile indicated in the System Information Block (SIB) or the dedicated signaling received by the terminal from the network device, that is, the network explicitly configures a number for each QoS profile or QoS profile list through the SIB or the dedicated signaling.

In this embodiment of the present application, for the case that the content of the indication information is (D), the QoS profile needs to be identified, and the network device is made to know which QoS profile is specific through the identification, and the determination of the specific identification may adopt the above 3 manners.

In one possible implementation, the sending the indication information to the network device includes: sending indication information to the network equipment through a first signaling;

wherein the first signaling comprises any one of:

(1) SidelinkUEinformation, namely, the indication information is carried in the existing SidelinkUEinformation signaling;

(2) RRC signaling, that is, a new RRC signaling is introduced to carry the indication information;

(3) The Media Access Control Element (MAC CE) introduces a new MAC CE to carry the indication information.

In one possible implementation, the sending the indication information to the network device includes: the indication information is transmitted to the network device after the Tx profile received by the lower layer of the terminal from the upper layer of the terminal.

In the embodiment of the present application, a precondition for sending the indication information is that a lower layer of the terminal receives Tx profile configured by a higher layer of the terminal.

Referring to fig. 3, an embodiment of the present application provides a configuration method, where an execution subject of the method is a network device, and the method includes:

step 301: the network equipment receives indication information from the terminal;

step 302: the network equipment determines whether the terminal needs to be subjected to SL DRX and/or SL DTX configuration or not according to the indication information;

in this embodiment of the present application, the indication information is used to assist the network device to determine whether to perform SL DRX and/or SL DTX configuration on the terminal, specifically, the terminal may report a protocol version used by the terminal to the network device through the indication information, and the network device determines whether the terminal supports SL DRX and/or SL DTX through the protocol version used by the terminal, for example: the protocol version comprises a first protocol version and a second protocol version, the terminal supports SL DRX and/or SL DTX when using the first protocol version, and the terminal does not support SL DRX and/or SL DTX when using the second protocol version; or, the terminal may also directly report whether the terminal supports SL DRX and/or SL DTX to the network device through the indication information.

In a possible embodiment, the indication information includes any one of:

(A) Tx profile, which is configured by the terminal high layer to the terminal low layer;

(B) First information indicating a protocol version used in the case of the terminal performing SL data transmission, and/or whether SL DRX and/or SL DTX is supported in the case of the terminal performing SL data transmission;

(C) Second information indicating a protocol version used in a case where the terminal performs SL data transmission for each target address, and/or whether or not SL DRX and/or SL DTX is supported in a case where the terminal performs SL data transmission for each target address;

(D) Third information, the third information indicates a protocol version used by the terminal in the case of transmitting SL data to the data corresponding to each QoS profile or QoS profile list of each target address, and/or whether SL DRX and/or SL DTX is supported in the case of transmitting SL data to the data corresponding to each QoS profile or QoS profile list of each target address;

(E) Fourth information indicating a protocol version used in a case where the terminal performs SL data transmission on data corresponding to each QoS profile or QoS profile list, and/or whether SL DRX and/or SL DTX is supported in a case where the terminal performs SL data transmission on data corresponding to each QoS profile or QoS profile list;

(2) A protocol version used in the case of the terminal performing SL data transmission, and/or whether or not the terminal supports SL DRX and/or SL DTX in the case of the terminal performing SL data transmission;

(3) A protocol version used in the case that the terminal performs SL data transmission for each target address, and/or whether SL DRX and/or SL DTX is supported in the case that the terminal performs SL data transmission for each target address;

(1) PQI corresponding to QoS profile;

(2) Under the condition that the terminal carries out SL DRX and/or SL DTX on the QoS profile according to the SIB, determining the serial number of the QoS profile according to the sequence of the QoS profile in the SIB;

(3) The number of QoS profile indicated in SIB or dedicated signalling received by the terminal from the network device.

In one possible implementation, receiving the indication information from the terminal includes: receiving indication information from a terminal through first signaling;

wherein the first signaling comprises any one of:

(1)SidelinkUEInformation；

(2) RRC signaling;

(3)MAC CE。

in a possible implementation manner, determining whether SL DRX and/or SL DTX configuration needs to be performed on the terminal according to the indication information includes any one of the following:

(1) When the SL data transmission of the terminal is determined according to the indication information and under the condition that SL DRX and/or SL DTX are needed, the terminal is configured with the SL DRX and/or the SL DTX;

the embodiments of the present application address the case where the content of the instruction information is (a) or (B) described above.

It can be understood that the SL DRX and/or SL DTX needs to be performed when the terminal determines to perform SL data transmission according to the indication information, specifically, the indication information may indicate that the terminal uses the first protocol version when performing SL data transmission, or the indication information directly indicates that the terminal supports SL DRX and/or SL DTX when performing SL data transmission.

(2) When determining that SL DRX and/or SL DTX are needed when the terminal sends SL data to the first target address according to the indication information, carrying out SL DRX and/or SL DTX configuration on the first target address;

the embodiments of the present application address the case where the content of the instruction information is (a) or (C) described above.

It can be understood that the terminal reports, through the indication information, the protocol version used when each target address in all target addresses performs SL data transmission or whether SL DRX and/or SL DTX is supported, so that all target addresses include a target address that needs to perform SL DRX and/or SL DTX and a target address that does not need to perform SL DRX and/or SL DTX, and the first target address is the target address that needs to perform SL DRX and/or SL DTX.

(3) When determining that SL DRX and/or SL DTX are needed to be performed when the terminal performs SL data transmission on the first QoS profile of the first target address or the data corresponding to the QoS profile list according to the indication information, performing SL DRX and/or SL DTX configuration on the first QoS profile or QoS profile list or a logic channel belonging to the first QoS profile or QoS profile list;

the embodiments of the present application address the case where the content of the instruction information is (a) or (D) described above.

It can be understood that the terminal reports, through the indication information, the protocol version used when the terminal performs SL data transmission through all QoS profiles of each target address or each QoS profile or QoS profile list in the QoS profile list or whether SL DRX and/or SL DTX is supported, so that the QoS profile or QoS profile list that needs to perform SL DRX and/or SL DTX and the QoS profile or QoS profile list that does not need to perform SL DRX and/or SL DTX are included in all QoS profile or QoS profile lists, and the first QoS profile or QoS profile list is the QoS profile or QoS profile list that needs to perform SL DRX and/or SL DTX.

The specific configuration mode for configuring the terminal with the SL DRX and/or the SL DTX depends on the granularity of the SL DRX and/or the SL DTX, for example: the network device may determine its corresponding SL DRX and/or SL DTX based on each QoS profile or QoS profile list under each direct communication destination address, and configure to the terminal.

(4) When determining that SL DRX and/or SL DTX are/is needed when the terminal sends SL data aiming at the data corresponding to the first QoS profile or the QoS profile list according to the indication information, carrying out SL DRX and/or SL DTX configuration on the first QoS profile or the QoS profile list of the terminal or a logic channel of the first QoS profile or the QoS profile list belonging to the terminal;

the embodiments of the present application address the case where the content of the instruction information is (a) or (E) described above.

It can be understood that, what the terminal reports through the indication information is a protocol version used when the terminal performs SL data transmission or whether the terminal supports SL DRX and/or SL DTX in each QoS profile or QoS profile list in all QoS profile or QoS profile lists, and therefore, the QoS profile or QoS profile list that needs to perform SL DRX and/or SL DTX and the QoS profile or QoS profile list that does not need to perform SL DRX and/or SL DTX may be included in all QoS profile or QoS profile lists, and the first QoS profile or QoS profile list is the QoS profile or QoS profile list that needs to perform SL DRX and/or SL DTX.

(5) When the terminal is determined not to need to carry out SL DRX and/or SL DTX when SL data transmission is carried out according to the indication information, the terminal is not configured with SL DRX and/or SL DTX;

It can be understood that the SL DRX and/or SL DTX is not required to be performed when the terminal determines to perform SL data transmission according to the indication information, and specifically, the indication information may indicate that the second protocol version is used when the terminal determines to perform SL data transmission, or the indication information directly indicates that the terminal does not support the SL DRX and/or SL DTX when the terminal performs SL data transmission.

(6) When determining that the terminal does not need to perform SL DRX and/or SL DTX when performing SL data transmission on the first target address according to the indication information, not performing SL DRX and/or SL DTX configuration on the first target address;

(7) And when determining that the terminal does not need to perform SL DRX and/or SL DTX when performing SL data transmission on the first QoS profile of the first target address or the data corresponding to the QoS profile list according to the indication information, not performing SL DRX and/or SL DTX configuration on the first QoS profile or QoS profile list or the logic channel belonging to the first QoS profile or QoS profile list.

(8) And when determining that the SL DRX and/or SL DTX do not need to be performed when the terminal performs SL data transmission for the data corresponding to the first QoS profile or the QoS profile list according to the indication information, not performing SL DRX and/or SL DTX configuration on the first QoS profile or the QoS profile list of the terminal or a logical channel of the first QoS profile or the QoS profile list belonging to the terminal.

The configuration method provided by the present application is described below with reference to specific embodiments:

example 1: the content indicated by the indication information is "protocol version used by the terminal for transmitting the direct communication interface data";

step 1: the UE high layer configures Tx profile to the UE low layer;

the Tx profile indicates a protocol version used when the terminal performs direct communication interface data transmission. Tx profile indicates the protocol version used by the terminal for data transmission through the direct communication interface, and if Tx profile indicates the second protocol version, the terminal needs to use the second version compatible mode for data transmission, i.e. the terminal cannot use SL DRX and/or SL DTX. If the Tx profile indicates the first protocol version, the terminal may use the first protocol version mode for data transmission, i.e., the terminal may use SL DRX and/or SL DTX.

Step 2: the UE determines the content of the indication information;

specifically, the UE determines the indication information in two ways:

(1) Directly using Tx profile acquired by terminal from high layer as indication information

(2) The terminal extracts only "the protocol version used by the terminal for transmitting the direct communication interface data" from the Tx profile, and uses the extracted protocol version as the indication information.

And 3, step 3: the terminal sends indication information to the network equipment;

specifically, the precondition for sending the indication information may be one of the following conditions:

(1) If the SidelinkUEinformation is used for carrying, multiplexing the transmission condition of the existing SidelinkUEinformation;

(2) And receiving the Tx profile configuration of the high layer, and generating the indication information according to the Tx profile by the terminal, so that the indication information can be sent.

(3) Depending on the terminal implementation.

The signaling indicating the use of information may be one or a combination of the following:

(1) Carried by SidelinkUEinformation;

(2) Introducing new RRC signaling;

(3) New MAC CEs are introduced.

And 4, step 4: the network receives the indication information and configures the SL DRX and/or the SL DTX for the terminal according to the indication information

If the content indicated by the indication information acquired by the network device is "the protocol version used by the terminal for sending the data of the direct communication interface":

(1) If the network equipment determines that the protocol version used by the terminal for the direct communication interface data transmission is the second protocol version according to the indication information, the network equipment does not allow the configuration of the SL DRX and/or the SL DTX for the terminal.

(2) If the network device determines that the protocol version used by the terminal for sending the direct communication interface data is the first protocol version according to the indication information, the network device allows configuring the SL DRX and/or the SL DTX for the terminal, where the specific configuration manner depends on the granularity of the SL DTX/DRX, for example, the network device may determine and configure the corresponding SL DRX and/or SL DTX to the terminal based on each QoS profile or QoS profile list at each direct communication destination address.

Example 2: the content indicated by the indication information is "a protocol version used when the terminal performs direct communication interface data transmission for each target address";

step 1: the UE high layer configures Tx profile to the UE low layer;

the Tx profile indicates a protocol version used when the terminal performs direct communication interface data transmission for each target address. The Tx profile may indicate a Release protocol version used by the terminal to transmit the direct communication data for each target address, and if the Tx profile indicates that the target address 1 corresponds to the second protocol version, the terminal needs to use the second protocol version compatible mode to transmit data when the direct communication interface transmits data for the target address 1, that is, the terminal cannot use SL DRX and/or SL DTX. If the indication of the target address 2 in the Tx profile indicates the first protocol version correspondingly, the terminal may use the first protocol version mode for data transmission when the direct communication interface transmits data for the target address 2, that is, the terminal may use SL DRX and/or SL DTX.

And 2, step: the UE determines the content of the indication information;

specifically, the UE determines the indication information in two ways:

(1) Directly taking Tx profile acquired by a terminal from a high layer as indication information

(2) The terminal extracts only "the protocol version used when the terminal performs direct communication interface data transmission for each destination address" from the Tx profile, and uses this as the indication information.

(3) Depending on the terminal implementation.

(1) Carried by SidelinkUEinformation;

(2) Introducing new RRC signaling;

(4) New MAC CEs are introduced.

And 4, step 4: the network receives the indication information and performs SL DRX and/or SL DTX configuration on the terminal according to the indication information;

the content indicated by the indication information acquired by the network device is "protocol version used by the terminal for transmitting data of the direct communication interface to each destination address":

(1) If the network equipment determines that the protocol version used by the terminal for the direct communication interface data transmission aiming at a specific target address is the second protocol version according to the indication information, the network equipment does not allow the SL DRX and/or the SL DTX to be configured for the specific direct communication target address of the terminal.

(2) If the network device determines that the "protocol version used by the terminal for sending the direct communication interface data to a specific target address" is the first protocol version according to the indication information, the network device allows configuring the SL DRX and/or the SL DTX for the specific direct communication target address of the terminal, where the specific configuration manner depends on the granularity of the SL DTX/DRX, for example, the network device may determine its corresponding SL DRX and/or SL DTX based on each QoS profile or QoS profile list under the specific target address and configure the SL DRX and/or SL DTX to the terminal.

Example 3: the content indicated by the indication information is "a protocol version used by the terminal for sending direct communication interface data for each QoS profile of each target address or data corresponding to the QoS profile list";

step 1: the UE high layer configures Tx profile to the UE low layer;

the Tx profile indicates the protocol version used by the terminal when the terminal performs direct communication interface data transmission aiming at each QoS profile of each target address or the data corresponding to the QoS profile list. If the Tx profile indicates that the QoS profile list 1 (specifically, PQI list) under the direct communication interface 1 corresponds to the second protocol version, the terminal needs to use the second protocol version compatible mode to transmit data when the direct communication interface transmits the data belonging to the logical channel of the QoS profile list 1 to the target address 1, that is, the terminal cannot use SL DRX and/or SL DTX. If the Tx profile indicates that the QoS profile list 2 (specifically, PQI list) under the direct communication interface 1 corresponds to the first protocol version, the terminal needs to use the first protocol version mode to transmit data when the direct communication interface transmits data belonging to the logical channel of the QoS profile list 2 for the target address 1, that is, the terminal cannot use SL DRX and/or SL DTX.

Step 2: UE determines content of indication information

Specifically, the UE determines the indication information in two ways:

(2) The terminal extracts only the protocol version used by the terminal for direct communication interface data transmission for each QoS profile of each target address or the data corresponding to the QoS profile list from the Tx profile, and uses the protocol version as the indication information.

The QoS profile is identified in the following ways:

(1) Directly using the number of QoS profile (i.e., PQI) as an identifier;

(2) When the DRX configuration corresponding to the QoS profile or the QoS profile list is configured according to the SIB, the number of the QoS profile or the QoS profile list is implicitly determined according to the sequence of the QoS profile or the QoS profile list appearing in the SIB;

(3) The network configures a number explicitly for each QoS profile or QoS profile list through SIB or dedicated signaling.

And 3, step 3: the terminal sends indication information to the network equipment

(3) The newly arrived QoS flow belongs to a new QoS profile or a QoS profile list;

(4) The QoS flow attributed to a certain QoS profile or all QoS flows attributed to a certain QoS profile list end data transmission;

(5) Whether any one QoS profile or QoS profile list uses SL DRX and/or a state of SL DTX changes;

(6) Depending on the terminal implementation.

(1) Carried by SidelinkUEinformation;

(2) Introducing new RRC signaling;

(3) New MAC CEs are introduced.

And 4, step 4: the network receives the indication information and performs scheduling according to the indication information

If the content indicated by the indication information acquired by the network device is "the protocol version used by the terminal for sending the data of the direct communication interface according to each QoS profile of each target address or the data corresponding to the QoS profile list":

(1) If the network device determines that the protocol version used by the terminal for directly sending the data of the communication interface aiming at the certain QoS profile or the data corresponding to the QoS profile list under the certain specific target address is the second protocol version according to the indication information, the network device does not allow the configuration of SL DRX and/or SL DTX for the QoS profile or the QoS profile list under the specific target address of the terminal or the logical channel belonging to the QoS profile or the QoS profile list.

(2) If the network device determines that the protocol version used by the terminal for directly sending the data of the communication interface aiming at a certain QoS profile or the data corresponding to the QoS profile list under a certain specific target address is the first protocol version according to the indication information, the network device allows configuring SL DRX and/or SL DTX for the QoS profile or the QoS profile list under the specific target address of the terminal or the logic channel belonging to the QoS profile or the QoS profile list.

Referring to fig. 4, the present embodiment provides a terminal, which includes a first memory 401, a first transceiver 402, a first processor 403, a user interface 404:

a first transceiver 402 for receiving and transmitting data under the control of a first processor 403.

Where, in fig. 4, the bus architecture may include any number of interconnected buses and bridges, in particular one or more processors represented by the first processor 403 and various circuits of the memory represented by the first memory 401 linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The first transceiver 402 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over transmission media including wireless channels, wired channels, fiber optic cables, and the like. For different user devices, the user interface 404 may also be an interface capable of interfacing externally to a desired device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The first processor 403 is responsible for managing the bus architecture and general processing, and the first memory 401 may store data used by the first processor 403 when performing operations.

Alternatively, the first processor 403 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

A first processor 403 for reading the computer program in the first memory 401 and executing the configuration method as shown in fig. 2:

a first transceiver 402, configured to send, by the terminal, indication information to the network device, where the indication information is used to assist the network device in determining whether SL DRX and/or SL DTX configuration needs to be performed for the terminal.

In a possible embodiment, the indication information includes any one of:

PQI corresponding to QoS profile;

wherein the first signaling comprises any one of:

SidelinkUEInformation；

RRC signaling;

MAC CE。

in one possible implementation, the first transceiver 402 is further configured to:

Referring to fig. 5, an embodiment of the present application provides a network device, which includes a second memory 501, a second transceiver 502, a second processor 503:

a second transceiver 502 for receiving and transmitting data under the control of a second processor 503.

Where in fig. 5 the bus architecture may comprise any number of interconnected buses and bridges, in particular one or more processors represented by the second processor 503 and various circuits of the memory represented by the second memory 501 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The second transceiver 502 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium including wireless channels, wired channels, fiber optic cables, and the like. The second processor 503 is responsible for managing the bus architecture and general processing, and the second memory 501 may store data used by the second processor 503 when performing operations.

The second processor 503 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also be a multi-core architecture.

A second processor 503 for reading the computer program in the second memory 501 and executing the configuration method shown in fig. 3:

a second transceiver 502 for the network device to receive indication information from the terminal;

a second processor 503, configured to the network device, determine whether SL DRX and/or SL DTX configuration needs to be performed on the terminal according to the indication information.

In one possible embodiment, the indication information includes any one of:

receiving indication information from a terminal through first signaling;

wherein the first signaling comprises any one of:

SidelinkUEInformation；

RRC signaling;

MAC CE。

when determining that SL DRX and/or SL DTX are/is needed to be performed when the terminal performs SL data transmission for the first QoS profile of the first target address or the data corresponding to the QoS profile list according to the indication information, performing SL DRX and/or SL DTX configuration on the first QoS profile or QoS profile list or the logic channel belonging to the first QoS profile or QoS profile list;

when the SL data transmission of the terminal is determined according to the indication information and under the condition that the SL DRX and/or the SL DTX are not needed, the SL DRX and/or the SL DTX configuration is not carried out on the terminal;

and under the condition that the SL DRX and/or SL DTX configuration is not needed when the terminal determines to transmit SL data aiming at the first QoS profile of the first target address or the data corresponding to the QoS profile list according to the indication information, the SL DRX and/or SL DTX configuration is not carried out on the first QoS profile or the QoS profile list or the logic channel belonging to the first QoS profile or the QoS profile list.

Referring to fig. 6, a terminal 600 according to an embodiment of the present application includes:

a sending unit 601, configured to send, by the terminal, indication information to the network device, where the indication information is used to assist the network device in determining whether SL DRX and/or SL DTX configuration needs to be performed on the terminal.

In one possible embodiment, the indication information includes any one of:

PQI corresponding to QoS profile;

wherein the first signaling comprises any one of:

SidelinkUEInformation；

RRC signaling;

MAC CE。

in a possible implementation, the sending unit is further configured to:

It should be noted that the obtaining unit may also be a transceiver unit, the determining unit may also be a processing unit, or other units capable of completing the technical solutions provided in the present application, and details are not repeated here, the determining unit and the obtaining unit are only names started for the descriptive purpose, and in an actual process, the device may be a combination of multiple units, or a part of a certain unit.

The division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The scope of the methods and apparatus of the embodiments of the present application is not limited to the performance of functions in the order shown or discussed, but may include the performance of functions in a substantially simultaneous manner or in an inverted order depending on the functionality involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Referring to fig. 7, an embodiment of the present application provides a network device 700, including:

a receiving unit 701, configured to receive, by a network device, indication information from a terminal;

a determining unit 702, configured to, by the network device, determine whether SL DRX and/or SL DTX configuration needs to be performed on the terminal according to the indication information.

In a possible embodiment, the indication information includes any one of:

PQI corresponding to QoS profile;

receiving indication information from a terminal through first signaling;

wherein the first signaling comprises any one of:

SidelinkUEInformation；

RRC signaling;

MAC CE。

when the terminal is determined to need to carry out SL DRX and/or SL DTX when carrying out SL data transmission aiming at the first target address according to the indication information, carrying out SL DRX and/or SL DTX configuration on the first target address;

It should be noted that the sending unit may also be a radio frequency unit, or other units capable of completing the technical solutions provided by the present application, and details are not described herein again, the sending unit is only a name given by a descriptive party, and in an actual process, the sending unit may be a combination of multiple units, or a part of a certain unit.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a processor readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

The embodiment of the application also provides a terminal, which comprises a transceiver and a processor;

a transceiver for receiving and transmitting data under the control of the processor.

The transceiver may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium including wireless channels, wired channels, fiber optic cables, and the like. The processor may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also have a multi-core architecture.

The processor is configured to perform the configuration method at the terminal side as described above, and is not described herein again.

The embodiment of the application also provides a network device, which comprises a transceiver and a processor;

The processor is configured to execute the configuration method of the network device side as described above, and details are not described herein.

The embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface and the processor coupling, the processor is configured to run a program or an instruction, implement the above-mentioned each process based on the PUSCH retransmission method embodiment, and can achieve the same technical effect, and for avoiding repetition, the details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc. An embodiment of the present application provides a computer-readable storage medium, which stores a computer program for causing a computer to execute the configuration method shown in fig. 2 or causing a processor to execute the configuration method shown in fig. 3.

The computer-readable storage medium can be any available medium or data storage device that can be accessed by a computer, including but not limited to magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid State Disks (SSDs)), etc.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present invention also provide a computer program product stored in a non-volatile storage medium, the computer program product being configured to be executed by at least one processor to implement the steps of the method described above.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method of configuration, the method comprising:

the terminal sends indication information to the network equipment, wherein the indication information is used for assisting the network equipment to determine whether SL DRX and/or SL DTX configuration needs to be carried out on the terminal.

2. The method according to claim 1, wherein the indication information comprises any one of:

sending and configuring Tx profile, wherein the Tx profile is configured to a terminal lower layer by a terminal upper layer;

first information indicating a protocol version used in a case where the terminal performs SL data transmission, and/or whether SL DRX and/or SL DTX is supported in the case where the terminal performs SL data transmission;

third information, the third information indicates a protocol version used by the terminal in a case where the terminal performs SL data transmission on data corresponding to each QoS profile or QoS profile list configured for each QoS of each target address, and/or whether SL DRX and/or SL DTX is supported in a case where the terminal performs SL data transmission on data corresponding to each QoS profile or QoS profile list of each target address;

fourth information, which indicates a protocol version used by the terminal in a case where the terminal performs SL data transmission on data corresponding to each QoS profile or QoS profile list, and/or whether SL DRX and/or SL DTX is supported by the terminal in a case where the terminal performs SL data transmission on data corresponding to each QoS profile or QoS profile list;

the protocol version comprises a first protocol version and a second protocol version, the SL DRX and/or the SL DTX are/is supported under the condition that the terminal uses the first protocol version, and the SL DRX and/or the SL DTX are/is not supported under the condition that the terminal uses the second protocol version.

3. The method of claim 2, wherein the Tx profile is used to indicate any of:

a protocol version used in the case that the terminal performs SL data transmission, and/or whether the terminal supports SL DRX and/or SL DTX in the case that the terminal performs SL data transmission;

a protocol version used in the case that the terminal performs SL data transmission to each target address, and/or whether SL DRX and/or SL DTX is supported in the case that the terminal performs SL data transmission to each target address;

the protocol version used by the terminal under the condition of transmitting SL data to the data corresponding to each QoS profile or QoS profile list of each target address, and/or whether SL DRX and/or SL DTX is supported under the condition of transmitting SL data to the data corresponding to each QoS profile or QoS profile list of each target address by the terminal.

4. The method according to claim 2, wherein the identification of the QoS profile in the indication information includes any one of:

the QoS profile corresponds to a proximity service quality identification (PQI);

under the condition that the terminal carries out SL DRX and/or SL DTX on the QoS profile according to a system information block SIB, determining the number of the QoS profile according to the sequence of the QoS profile appearing in the SIB;

the number of the QoS profile indicated in the SIB or dedicated signaling received by the terminal from the network device.

5. The method of claim 1, wherein sending the indication information to the network device comprises:

sending the indication information to the network equipment through first signaling;

wherein the first signaling comprises any one of:

direct communication terminal information SidelinkUEinformation;

radio resource control, RRC, signaling;

the medium access control element MAC CE.

6. The method of claim 2, wherein sending the indication information to the network device comprises:

and after the Tx profile received by the lower layer of the terminal from the upper layer of the terminal, sending the indication information to a network device.

7. A method of configuration, the method comprising:

the network equipment receives indication information from the terminal;

and the network equipment determines whether the terminal needs to be subjected to SL DRX and/or SL DTX configuration or not according to the indication information.

8. The method according to claim 7, wherein the indication information comprises any one of:

second information indicating a protocol version used in a case where the terminal performs SL data transmission for each target address, and/or whether SL DRX and/or SL DTX is supported in a case where the terminal performs SL data transmission for each target address;

third information, which indicates a protocol version used by the terminal in a case where the terminal performs SL data transmission on data corresponding to each QoS profile or QoS profile list of each target address, and/or whether SL DRX and/or SL DTX is supported in a case where the terminal performs SL data transmission on data corresponding to each QoS profile or QoS profile list of each target address;

the protocol version comprises a first protocol version and a second protocol version, the SL DRX and/or the SL DTX are supported under the condition that the terminal uses the first protocol version, and the SL DRX and/or the SL DTX are not supported under the condition that the terminal uses the second protocol version.

9. The method of claim 8, wherein the Tx profile is used to indicate any of the following:

a protocol version used in a case where the terminal transmits SL data to each target address, and/or whether or not the terminal supports SL DRX and/or SL DTX in a case where the terminal transmits SL data to each target address;

10. The method according to claim 8, wherein the identification of the QoS profile in the indication information includes any one of:

11. The method of claim 7, wherein the receiving indication information from the terminal comprises:

receiving the indication information from the terminal through first signaling;

wherein the first signaling comprises any one of:

SidelinkUEInformation；

RRC signaling;

MAC CE。

12. the method of claim 8,

the determining whether the terminal needs to be configured with the SL DRX and/or the SL DTX according to the indication information includes any one of:

when the terminal is determined to need to carry out SL DRX and/or SL DTX when carrying out SL data transmission aiming at a first target address according to the indication information, carrying out SL DRX and/or SL DTX configuration on the first target address;

when determining that SL DRX and/or SL DTX are/is required to be performed when the terminal performs SL data transmission for data corresponding to a first QoS profile or QoS profile list of a first target address according to the indication information, performing SL DRX and/or SL DTX configuration on a first QoS profile or QoS profile list of the first target address of the terminal or a logical channel of the first QoS profile or QoS profile list belonging to the first target address of the terminal;

when determining that SL DRX and/or SL DTX are/is required to be performed when the terminal performs SL data transmission for data corresponding to a first QoS profile or QoS profile list according to the indication information, performing SL DRX and/or SL DTX configuration on the first QoS profile or QoS profile list of the terminal or a logic channel of the first QoS profile or QoS profile list belonging to the terminal;

when the terminal is determined not to need to carry out SL DRX and/or SL DTX when SL data transmission is carried out according to the indication information, the terminal is not subjected to SL DRX and/or SL DTX configuration;

when the terminal determines that SL data transmission aiming at a first target address is not needed according to the indication information, the first target address is not configured with SL DRX and/or SL DTX;

when determining that SL DRX and/or SL DTX do not need to be performed when the terminal performs SL data transmission for data corresponding to a first QoS profile or a QoS profile list of a first target address according to the indication information, not performing SL DRX and/or SL DTX configuration on the first QoS profile or QoS profile list of the first target address of the terminal or a logical channel of the first QoS profile or QoS profile list belonging to the first target address of the terminal;

and when determining that SL DRX and/or SL DTX do not need to be performed when the terminal performs SL data transmission on data corresponding to a first QoS profile or a QoS profile list according to the indication information, not performing SL DRX and/or SL DTX configuration on the first QoS profile or QoS profile list of the terminal or a logic channel of the first QoS profile or QoS profile list belonging to the terminal.

13. A terminal comprising a first memory, a first transceiver, a first processor:

the first memory for storing a computer program; the first transceiver is used for transceiving data under the control of the first processor; the first processor for reading the computer program in the first memory and executing the configuration method of any one of claims 1 to 7.

14. A network device comprising a second memory, a second transceiver, a second processor:

the second memory for storing a computer program; the second transceiver is used for transceiving data under the control of the second processor; the second processor for reading the computer program in the second memory and executing the configuration method of any of claims 8 to 12.

15. A terminal, comprising:

a sending unit, configured to send, by a terminal, indication information to a network device, where the indication information is used to assist the network device in determining whether SL DRX and/or SL DTX configuration needs to be performed on the terminal.

16. A network device, comprising:

and the determining unit is used for determining whether the terminal needs to be subjected to SL DRX and/or SL DTX configuration by the network equipment according to the indication information.

17. A computer-readable storage medium, characterized in that it stores a computer program for causing a computer to execute the configuration method of any one of claims 1 to 7 or for causing the processor to execute the configuration method of any one of claims 8 to 12.