Configuration method, device, and computer-readable storage medium

Abstract

The present application relates to the field of communications technology, and more particularly to a configuration method, device, and computer-readable storage medium. The method includes: a terminal sending indication information to a network device, the indication information being used to assist the network device in determining whether SL DRX and / or SL DTX configuration is required for the terminal; the network device receiving the indication information from the terminal; and determining, based on the indication information, whether SL DRX and / or SL DTX configuration is required for the terminal.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a configuration method, device, and computer-readable storage medium. Background Art

[0002] For direct communication multicast and broadcast, whether to use direct communication link discontinuous reception (SL DRX) and / or direct communication link discontinuous reception (SL DTX) depends on the transmitting terminal (UE). For example, if the transmitting UE determines that the data to be transmitted is for both UEs that support SL DRX / SL DTX and UEs that do not support SL DRX / SL DTX, SL DRX / SL DTX may not be used. If the transmitting UE determines that the data to be transmitted is only for UEs that support SL DRX / SL DTX, SL DRX / SL DTX may be used.

[0003] Since whether to use SL DRX / SL DTX depends entirely on the sending UE and the network is not aware of it, for the UE that is in the Radio Resource Control (RRC) connection state and uses the direct communication interface sending UE in the network-scheduled resource allocation mode, the network equipment cannot accurately determine the UE's activation time (Active Time) on the direct communication interface, and thus cannot perform appropriate scheduling. Summary of the Invention

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

[0005] In a first aspect, an embodiment of the present application provides a configuration method, the method comprising:

[0006] The terminal sends 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.

[0007] In a possible implementation, the indication information includes any one of the following:

[0008] Tx profile, which is configured by the terminal upper layer to the terminal lower layer;

[0009] First information, where the first information indicates a protocol version used when the terminal performs SL data transmission, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0010] second information, where the second information indicates a protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0011] third information, where the third information indicates a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address;

[0012] Fourth information, the fourth information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list;

[0013] The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SLDTX are not supported.

[0014] In one possible implementation, the Tx profile is used to indicate any of the following:

[0015] The correspondence between the terminal's SL service and the protocol version, and / or whether the terminal's SL service supports SL DRX and / or SL DTX;

[0016] The protocol version used when the terminal performs SL data transmission, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0017] The protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0018] The protocol version used when the terminal sends SL data for each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal sends SL data for each QoS profile or QoS profile list for each target address.

[0019] In a possible implementation manner, the identifier of the QoS profile in the indication information includes any one of the following:

[0020] PQI corresponding to the QoS profile;

[0021] When the terminal performs SL DRX and / or SL DTX for the QoS profile according to the SIB, the QoS profile number is determined according to the order in which the QoS profile appears in the SIB;

[0022] The QoS profile number indicated in the SIB or dedicated signaling received by the terminal from the network device.

[0023] In a possible implementation, sending instruction information to the network device includes:

[0024] Sending instruction information to the network device through the first signaling;

[0025] The first signaling includes any one of the following:

[0026] SidelinkUEInformation;

[0027] RRC signaling;

[0028] MAC CE.

[0029] In a possible implementation, sending instruction information to the network device includes:

[0030] After the lower layer of the terminal receives the Tx profile from the upper layer of the terminal, it sends indication information to the network device.

[0031] In a second aspect, an embodiment of the present application provides a configuration method, the method comprising:

[0032] The network device receives instruction information from the terminal;

[0033] The network device determines whether it is necessary to perform SL DRX and / or SL DTX configuration on the terminal according to the indication information.

[0034] In a possible implementation, the indication information includes any one of the following:

[0035] Tx profile, which is configured by the terminal upper layer to the terminal lower layer;

[0036] First information, where the first information indicates a protocol version used when the terminal performs SL data transmission, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission;

[0037] second information, where the second information indicates a protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0038] third information, where the third information indicates a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address;

[0039] Fourth information, the fourth information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list;

[0040] The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SLDTX are not supported.

[0041] In one possible implementation, the Tx profile is used to indicate any of the following:

[0042] The correspondence between the terminal's SL service and the protocol version, and / or whether the terminal's SL service supports SL DRX and / or SL DTX;

[0043] The protocol version used when the terminal performs SL data transmission, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0044] The protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0045] The protocol version used when the terminal sends SL data for each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal sends SL data for each QoS profile or QoS profile list for each target address.

[0046] In a possible implementation manner, the identifier of the QoS profile in the indication information includes any one of the following:

[0047] The proximity service quality indicator (PQI) corresponding to the QoS profile;

[0048] When the terminal performs SL DRX and / or SL DTX for the QoS profile according to the system information block SIB, the QoS profile number is determined according to the order in which the QoS profile appears in the SIB;

[0049] The QoS profile number indicated in the SIB or dedicated signaling received by the terminal from the network device.

[0050] In a possible implementation, receiving indication information from a terminal includes:

[0051] receiving indication information from a terminal through a first signaling;

[0052] The first signaling includes any one of the following:

[0053] SidelinkUEInformation;

[0054] RRC signaling;

[0055] MAC CE.

[0056] In a possible implementation, 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:

[0057] When it is determined according to the indication information that SL DRX and / or SL DTX needs to be performed when the terminal performs SL data transmission, performing SL DRX and / or SL DTX configuration on the terminal;

[0058] When it is determined according to the indication information that SLDRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the first target address, perform SL DRX and / or SL DTX configuration on the first target address;

[0059] When it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the data corresponding to the first QoS profile or QoS profile list of the first target address, SL DRX and / or SL DTX configuration is performed on the first QoS profile or QoS profile list of the first target address of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the first target address of the terminal;

[0060] When it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the data corresponding to the first QoS profile or QoS profile list, SLDRX and / or SL DTX configuration is performed on the first QoS profile or QoS profile list of the terminal or on the logical channel belonging to the first QoS profile or QoS profile list of the terminal;

[0061] When it is determined according to the instruction information that SL DRX and / or SL DTX is not required when the terminal performs SL data transmission, SL DRX and / or SL DTX configuration is not performed on the terminal;

[0062] When it is determined according to the instruction information that the terminal does not need to perform SLDRX and / or SL DTX when performing SL data transmission for the first target address, SL DRX and / or SL DTX configuration is not performed on the first target address;

[0063] When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal sends SL data corresponding to the first QoS profile or QoS profile list of the first target address, SL DRX and / or SL DTX are not configured for the first QoS profile or QoS profile list of the first target address of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the first target address of the terminal.

[0064] When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal sends SL data for the data corresponding to the first QoS profile or QoS profile list, SL DRX and / or SL DTX configuration is not performed for the first QoS profile or QoS profile list of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the terminal.

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

[0066] The first memory is used to store computer programs; the first transceiver is used to send and receive data under the control of the first processor; the first processor is used to read the computer program in the first memory and execute the configuration method as described in the first aspect.

[0067] The first transceiver is used for the terminal to send 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.

[0068] In a possible implementation, the indication information includes any one of the following:

[0069] Tx profile, which is configured by the terminal upper layer to the terminal lower layer;

[0070] First information, where the first information indicates a protocol version used when the terminal performs SL data transmission, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission;

[0071] second information, where the second information indicates a protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0072] third information, where the third information indicates a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address;

[0073] The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SLDTX are not supported.

[0074] In one possible implementation, the Tx profile is used to indicate any of the following:

[0075] The correspondence between the terminal's SL service and the protocol version, and / or whether the terminal's SL service supports SL DRX and / or SL DTX;

[0076] The protocol version used when the terminal performs SL data transmission, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0077] The protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0078] The protocol version used when the terminal sends SL data for each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal sends SL data for each QoS profile or QoS profile list for each target address.

[0079] In a possible implementation manner, the identifier of the QoS profile in the indication information includes any one of the following:

[0080] PQI corresponding to the QoS profile;

[0081] When the terminal performs SL DRX and / or SL DTX for the QoS profile according to the SIB, the QoS profile number is determined according to the order in which the QoS profile appears in the SIB;

[0082] The QoS profile number indicated in the SIB or dedicated signaling received by the terminal from the network device.

[0083] In a possible implementation, sending instruction information to the network device includes:

[0084] Sending instruction information to the network device through the first signaling;

[0085] The first signaling includes any one of the following:

[0086] SidelinkUEInformation;

[0087] RRC signaling;

[0088] MAC CE.

[0089] In a possible implementation manner, the first transceiver is further configured to:

[0090] After the lower layer of the terminal receives the Tx profile from the upper layer of the terminal, it sends indication information to the network device.

[0091] In a fourth aspect, an embodiment of the present application provides a network device, characterized in that it includes a second memory, a second transceiver, and a second processor:

[0092] The second memory is used to store computer programs; the second transceiver is used to send and receive data under the control of the second processor; the second processor is used to read the computer program in the second memory and execute the configuration method as described in the second aspect.

[0093] A second transceiver is used for the network device to receive indication information from the terminal;

[0094] The second processor is configured to determine, by the network device, whether it is necessary to perform SL DRX and / or SL DTX configuration on the terminal according to the indication information.

[0095] In a possible implementation, the indication information includes any one of the following:

[0096] Tx profile, which is configured by the terminal upper layer to the terminal lower layer;

[0097] First information, where the first information indicates a protocol version used when the terminal performs SL data transmission, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission;

[0098] second information, where the second information indicates a protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0099] third information, where the third information indicates a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address;

[0100] The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SLDTX are not supported.

[0101] In one possible implementation, the Tx profile is used to indicate any of the following:

[0102] The correspondence between the terminal's SL service and the protocol version, and / or whether the terminal's SL service supports SL DRX and / or SL DTX;

[0103] The protocol version used when the terminal performs SL data transmission, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0104] The protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0105] The protocol version used when the terminal sends SL data for each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal sends SL data for each QoS profile or QoS profile list for each target address.

[0106] In a possible implementation manner, the identifier of the QoS profile in the indication information includes any one of the following:

[0107] The proximity service quality indicator (PQI) corresponding to the QoS profile;

[0108] When the terminal performs SL DRX and / or SL DTX for the QoS profile according to the SIB, the QoS profile number is determined according to the order in which the QoS profile appears in the SIB;

[0109] The QoS profile number indicated in the SIB or dedicated signaling received by the terminal from the network device.

[0110] In a possible implementation, receiving indication information from a terminal includes:

[0111] receiving indication information from a terminal through a first signaling;

[0112] The first signaling includes any one of the following:

[0113] SidelinkUEInformation;

[0114] RRC signaling;

[0115] MAC CE.

[0116] In one possible implementation, the second processor is further configured to:

[0117] When it is determined according to the indication information that SL DRX and / or SL DTX needs to be performed when the terminal performs SL data transmission, performing SL DRX and / or SL DTX configuration on the terminal;

[0118] When it is determined according to the indication information that SL DRX and / or SL DTX needs to be performed when the terminal performs SL data transmission to the first target address, perform SL DRX and / or SL DTX configuration on the first target address;

[0119] When it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission on the data corresponding to the first QoS profile or QoS profile list of the first target address, SL DRX and / or SL DTX configuration is performed on the first QoS profile or QoS profile list or the logical channel belonging to the first QoS profile or QoS profile list;

[0120] When it is determined according to the indication information that SL DRX and / or SL DTX are required when the terminal sends SL data for the data corresponding to the first QoS profile or QoS profile list, SLDRX and / or SL DTX are configured for the first QoS profile or QoS profile list of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the terminal.

[0121] When it is determined according to the instruction information that SL DRX and / or SL DTX is not required when the terminal performs SL data transmission, SL DRX and / or SL DTX configuration is not performed on the terminal;

[0122] When it is determined according to the instruction information that the terminal does not need to perform SL DRX and / or SL DTX when performing SL data transmission to the first target address, SL DRX and / or SL DTX configuration is not performed on the first target address;

[0123] When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal sends SL data corresponding to the first QoS profile or QoS profile list of the first target address, SL DRX and / or SL DTX are not configured for the first QoS profile or QoS profile list or the logical channel belonging to the first QoS profile or QoS profile list.

[0124] When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal sends SL data for the data corresponding to the first QoS profile or QoS profile list, SL DRX and / or SL DTX configuration is not performed for the first QoS profile or QoS profile list of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the terminal.

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

[0126] The sending unit is used for the terminal to send 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 is required for the terminal.

[0127] In a possible implementation, the indication information includes any one of the following:

[0128] Tx profile, which is configured by the terminal upper layer to the terminal lower layer;

[0129] First information, where the first information indicates a protocol version used when the terminal performs SL data transmission, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission;

[0130] second information, where the second information indicates a protocol version used when the terminal sends SL data to each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal sends SL data to each target address;

[0131] third information, where the third information indicates a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address;

[0132] The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SLDTX are not supported.

[0133] In one possible implementation, the Tx profile is used to indicate any of the following:

[0134] The correspondence between the terminal's SL service and the protocol version, and / or whether the terminal's SL service supports SL DRX and / or SL DTX;

[0135] The protocol version used when the terminal performs SL data transmission, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0136] The protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0137] The protocol version used when the terminal sends SL data for each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal sends SL data for each QoS profile or QoS profile list for each target address.

[0138] In a possible implementation manner, the identifier of the QoS profile in the indication information includes any one of the following:

[0139] PQI corresponding to the QoS profile;

[0140] When the terminal performs SL DRX and / or SL DTX for the QoS profile according to the SIB, the QoS profile number is determined according to the order in which the QoS profile appears in the SIB;

[0141] The QoS profile number indicated in the SIB or dedicated signaling received by the terminal from the network device.

[0142] In a possible implementation, sending instruction information to the network device includes:

[0143] Sending instruction information to the network device through the first signaling;

[0144] The first signaling includes any one of the following:

[0145] SidelinkUEInformation;

[0146] RRC signaling;

[0147] MAC CE.

[0148] In a possible implementation manner, the sending unit is further configured to:

[0149] After the lower layer of the terminal receives the Tx profile from the upper layer of the terminal, it sends indication information to the network device.

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

[0151] A receiving unit, configured for the network device to receive instruction information from a terminal;

[0152] The determining unit is used for the network device to determine whether SL DRX and / or SLDTX configuration is required for the terminal according to the indication information.

[0153] In a possible implementation, the indication information includes any one of the following:

[0154] Tx profile, which is configured by the terminal upper layer to the terminal lower layer;

[0155] First information, where the first information indicates a protocol version used when the terminal performs SL data transmission, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission;

[0156] second information, where the second information indicates a protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0157] third information, where the third information indicates a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address;

[0158] The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SLDTX are not supported.

[0159] In one possible implementation, the Tx profile is used to indicate any of the following:

[0160] The correspondence between the terminal's SL service and the protocol version, and / or whether the terminal's SL service supports SL DRX and / or SL DTX;

[0161] The protocol version used when the terminal performs SL data transmission, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0162] The protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0163] The protocol version used when the terminal sends SL data for each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal sends SL data for each QoS profile or QoS profile list for each target address.

[0164] In a possible implementation manner, the identifier of the QoS profile in the indication information includes any one of the following:

[0165] PQI corresponding to the QoS profile;

[0166] When the terminal performs SL DRX and / or SL DTX for the QoS profile according to the SIB, the QoS profile number is determined according to the order in which the QoS profile appears in the SIB;

[0167] The QoS profile number indicated in the SIB or dedicated signaling received by the terminal from the network device.

[0168] In a possible implementation, receiving indication information from a terminal includes:

[0169] receiving indication information from a terminal through a first signaling;

[0170] The first signaling includes any one of the following:

[0171] SidelinkUEInformation;

[0172] RRC signaling;

[0173] MAC CE.

[0174] In a possible implementation manner, the determining unit is further configured to perform any of the following:

[0175] When it is determined according to the indication information that SL DRX and / or SL DTX needs to be performed when the terminal performs SL data transmission, performing SL DRX and / or SL DTX configuration on the terminal;

[0176] When it is determined according to the indication information that SL DRX and / or SL DTX needs to be performed when the terminal performs SL data transmission to the first target address, perform SL DRX and / or SL DTX configuration on the first target address;

[0177] When it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission on the data corresponding to the first QoS profile or QoS profile list of the first target address, SL DRX and / or SL DTX configuration is performed on the first QoS profile or QoS profile list of the first target address of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the first target address of the terminal;

[0178] When it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the data corresponding to the first QoS profile or QoS profile list, SLDRX and / or SL DTX configuration is performed on the first QoS profile or QoS profile list of the terminal or on the logical channel belonging to the first QoS profile or QoS profile list of the terminal;

[0179] When it is determined according to the instruction information that SL DRX and / or SL DTX is not required when the terminal performs SL data transmission, SL DRX and / or SL DTX configuration is not performed on the terminal;

[0180] When it is determined according to the instruction information that the terminal does not need to perform SL DRX and / or SL DTX when performing SL data transmission to the first target address, SL DRX and / or SL DTX configuration is not performed on the first target address;

[0181] When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal sends SL data corresponding to the first QoS profile or QoS profile list of the first target address, SL DRX and / or SL DTX are not configured for the first QoS profile or QoS profile list of the first target address of the terminal or the logical channel of the first QoS profile or QoS profile list of the first target address of the terminal.

[0182] When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal sends SL data for the data corresponding to the first QoS profile or QoS profile list, SL DRX and / or SL DTX configuration is not performed for the first QoS profile or QoS profile list of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the terminal.

[0183] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program is used to enable a computer to execute the configuration method of the first aspect, or to enable a processor to execute the configuration method of the second aspect.

[0184] In an embodiment of the present application, the terminal assists the network device in determining whether SLDRX and / or SL DTX configuration is required for the terminal through indication information. In this manner, the network device performs SL DRX and / or SL DTX configuration for the terminal, which can ensure that the network device can know the activation time of the terminal's direct communication interface, thereby more reasonably scheduling the direct communication interface resources and improving the utilization rate of the direct communication interface resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0185] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0186] Figure 1a is a structural diagram of a traditional cellular network communication system;

[0187] Figure 1b Schematic diagram of the principle of DRX;

[0188] Figure 1c It is a structural diagram of the direct communication system;

[0189] Figure 2 One of the method flow diagrams provided in the embodiment of the present application;

[0190] Figure 3 The second flowchart of the method provided in the embodiment of the present application;

[0191] Figure 4 One of the structural diagrams of the terminal provided in the embodiment of the present application;

[0192] Figure 5 One of the structural diagrams of the network device provided in the embodiment of the present application;

[0193] Figure 6 The second structural diagram of the terminal provided in the embodiment of the present application;

[0194] Figure 7 This is the second structural diagram of the network device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0195] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0196] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein, for example, are implemented in a sequence other than those illustrated or described herein. In addition, the terms "comprise" and "have" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or that are inherent to these processes, methods, products or devices.

[0197] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship. In the embodiments of this application, the term "plurality" refers to two or more, and other quantifiers are similar.

[0198] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0199] To better understand the solutions of the embodiments of the present application, the following contents are first introduced:

[0200] 1. Cellular network communication

[0201] like Figure 1a As shown, in traditional cellular network communications, uplink and downlink data and control information are transmitted between the terminal and the network side device through the Uu interface.

[0202] 2. DRX mechanism of the Uu interface of the cellular communication system

[0203] In a mobile communication system based on shared channels, the transmission of uplink and downlink data is controlled by the base station scheduler. When the scheduler determines to schedule a user, it notifies the user terminal via the control channel which resources to use to send or receive data. The user terminal (UE) monitors the control channel. When it detects scheduling information for its own user, it transmits (uplink) or receives (downlink) data according to the instructions on the control channel. In the active state, because the user terminal cannot determine when the eNB will schedule it, a common operating mode is for the user terminal to continuously monitor the control channel, parsing each subframe containing its downlink scheduling control channel to determine whether it is scheduled. This operating mode is highly efficient when the user terminal has large data volumes and is likely to be frequently scheduled. However, for some services, data arrival frequency is low, resulting in a low number of scheduled users. If the user terminal continues to monitor the control channel continuously, power consumption will undoubtedly increase. To address power consumption issues, cellular network communication systems use the DRX mode. In this mode, the user terminal periodically monitors the control channel, thereby saving power.

[0204] The basic principle of DRX is as follows Figure 1b The On duration represents the time period during which the UE monitors the control channel. During this period, the RF channel is open and continuously monitors the control channel. During other times outside the On duration, the UE is in the Sleep state, its RF link is shut down, and it no longer monitors the control channel to save power. The On Duration occurs periodically (Cycle), and the specific period is configured by the eNB.

[0205] The DRX mechanism in cellular networks takes into account the arrival pattern of data services, namely, the bursty arrival of data packets (which means that once a data packet arrives, a large number of packets arrive in a short period of time). To accommodate this arrival pattern, the LTE DRX process uses multiple timers and integrates them with the HARQ process to achieve better power conservation.

[0206] DRX related timers:

[0207] (1) drx-onDurationTimer: The time for UE to wake up periodically to monitor the control channel, such as Figure 1b shown.

[0208] (2) Short DRX cycle timer: In order to better match the characteristics of data service arrival, the cellular network communication system supports the configuration of two DRX cycles: long cycle and short cycle. The on duration timer of the two cycles is the same, but the sleep time is different. In the short cycle, the sleep time is relatively shorter, and the UE can monitor the control channel again more quickly. The long cycle must be configured and is the initial state of the DRX process; the short cycle is optional. The short DRX cycle timer sets the duration of the short cycle. After the short cycle timer times out, the UE will use the long cycle.

[0209] (3) drx-InactivityTimer: When DRX is configured, this timer is started when the UE receives control signaling for HARQ initial transmission within the time allowed to monitor the control channel (Active Time). The UE continuously monitors the control channel until the timer expires. If the UE receives control signaling for HARQ initial transmission before the drx-InactivityTimer expires, the drx-InactivityTimer is terminated and restarted.

[0210] (4) HARQ RTT Timer: It is divided into drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerUL. Its purpose is to make it possible for the UE not to monitor the control channel before the next retransmission, so as to achieve better power saving. Taking the following behavior as an example, this timer will be started when the first symbol after the PUCCH transmission of the UE-related process is started. If the data in the corresponding HARQ process is not successfully decoded after the previous HARQ transmission (UE feedback NACK), after the DL HARQ RTT Timer expires, the UE starts drx-RetransmissionTimerDL. If the data in the corresponding HARQ process is successfully decoded after the previous HARQ transmission (UE feedback ACK), after the drx-HARQ-RTT-TimerDL timer expires, the UE does not start drx-RetransmissionTimerDL. If only drx-HARQ-RTT-TimerDL is currently running, the UE does not monitor the control channel.

[0211] (5) HARQ retransmission timer: It is divided into drx-RetransmissionTimerDL or drx-RetransmissionTimerUL. The following behavior is an example. During the DL HARQ retransmission timer, the UE monitors the control signaling and waits for the retransmission schedule of the corresponding HARQ process.

[0212] Active time definition under DRX:

[0213] The above process shows that if any of the On Duration Timer, HARQ Retransmission Timer, and Inactivity Timer is running, the UE will monitor the control channel. The time the UE monitors the control channel is also called the Active Time. In the LTE system, the Active Time is affected by factors other than the DRX timer. The Active Time of LTE Rel-8 UEs includes the following:

[0214] (1) The duration of the drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or ra-ContentionResolutionTimer;

[0215] (2) The time it takes for the UE to wait for the base station to send the Physical Downlink Control Channel (PDCCH) after sending an uplink scheduling request (SR);

[0216] (3) Non-contention random access: The time a UE waits for the PDCCH scheduled by the Cell Radio Network Temporary Identifier (C-RNTI) after receiving the Random Access Response (RAR).

[0217] 3. Direct communication

[0218] like Figure 1cAs shown, direct communication refers to a method in which adjacent terminals can transmit data over a short distance via a direct communication link (also called a Sidelink). The wireless interface corresponding to the Sidelink link is called a direct communication interface, also called a Sidelink interface.

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

[0220] There are two direct communication interface resource allocation modes:

[0221] (1) Network scheduling resource allocation mode (also called mode 1): the network device allocates resources for direct communication interface data transmission to the terminal;

[0222] (2) Terminal-selected resource allocation mode (also called mode 2): The terminal selects direct communication transmission resources from the resource pool available on the direct communication interface.

[0223] Under the current mechanism, whether to use SL DRX / DTX for direct communication multicast and broadcast depends on the transmitting UE, which is unknown to the network. Therefore, for UEs in RRC Connected state and using the direct communication interface in network-scheduled resource allocation mode (Mode 1), the network equipment cannot accurately determine the UE's active time on the direct communication interface to perform appropriate scheduling. This problem needs to be addressed, but no solution is currently available.

[0224] The following describes embodiments of the present application in conjunction with the accompanying drawings.

[0225] The configuration method, terminal and network device provided in the embodiment of the present application can be applied to the wireless communication system shown in Figure 1. The terminal can be a user equipment (UE), for example, a mobile phone, a tablet 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 other terminal-side devices. It should be noted that the specific type of the user terminal is not limited in the embodiment of the present application. The above-mentioned network device can be a base station of 5G and later protocol versions (for example, gNB, 5G NR NB), or a base station in other communication systems. The specific type of the network device is not limited in the embodiment of the present application.

[0226] It should be noted that the scenarios targeted by the embodiments of the present application are direct communication multicast and broadcast scenarios.

[0227] See also Figure 2 , an embodiment of the present application provides a configuration method, the execution subject of the method is a terminal, and the method includes:

[0228] Step 201: The terminal sends instruction information to the network device;

[0229] In an embodiment of the present application, the indication information is used to assist the network device in determining whether it is necessary to perform SL DRX and / or SL DTX configuration on the terminal. Specifically, the terminal can report the protocol version used by itself to the network device through the indication information. For example, 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 includes a first protocol version (such as 3GPP Rel-17) and a second protocol version (such as 3GPP Rel-16). When the terminal uses the first protocol version, it supports SL DRX and / or SL DTX, and when the terminal uses the second protocol version, it does not support SL DRX and / or SL DTX; alternatively, the terminal can also directly report whether it supports SL DRX and / or SL DTX to the network device through the indication information.

[0230] In an embodiment of the present application, the terminal assists the network device in determining whether SLDRX and / or SL DTX configuration is required for the terminal through indication information. In this manner, the network device performs SL DRX and / or SL DTX configuration for the terminal, which can ensure that the network device can know the activation time of the terminal's direct communication interface, thereby more reasonably scheduling the direct communication interface resources and improving the utilization rate of the direct communication interface resources.

[0231] In a possible implementation, the indication information includes any one of the following:

[0232] (A) Transmit configuration (Tx profile); It should be noted that the Tx profile is specifically configured by the upper layer of the terminal to the lower layer of the terminal.

[0233] (B) first information, where the first information indicates the protocol version used when the terminal performs SL data transmission, i.e., implicitly indicates whether the terminal supports SL DRX and / or SL DTX through the used protocol version; and / or, directly and explicitly indicates whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0234] (C) second information, where the second information indicates a protocol version used when the terminal performs SL data transmission for each target address, i.e., implicitly indicates whether the terminal supports SL DRX and / or SL DTX through the used protocol version; and / or, directly and explicitly indicates whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0235] It should be noted that the above-mentioned target address refers to the address of the opposite terminal that conducts SL communication with the terminal. It can be understood that the terminal can know in advance the addresses of all opposite terminals that conduct SL communication with it, that is, all target addresses, and then use the second information to indicate the protocol version used for each of all target addresses when sending SL data, and / or whether SL DRX and / or SL DTX are supported.

[0236] (D) third information, the third information indicating the protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list for each target address, that is, implicitly indicating 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 when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list for each target address, that is, directly and explicitly indicating whether the terminal supports SL DRX and / or SL DTX;

[0237] It should be noted that the above-mentioned target address refers to the address of the opposite terminal that performs SL communication with the terminal. It can be understood that the terminal can know in advance the addresses of all opposite terminals that perform SL communication with it, that is, all target addresses. In addition, for the direct communication interface, the direct communication service is generated by the terminal high layer. According to the different QoS of the service, the service can be divided into different QoS flows, each QoS flow corresponds to a different QoS profile, and a group of QoS profile combinations can constitute a QoS profile list. Here, the third information can be used to indicate the protocol version used for SL data transmission for each QoS profile or QoS profile list under each target address of the terminal, and / or whether SL DRX and / or SL DTX are supported.

[0238] (E) fourth information, the fourth information indicating the protocol version used when the terminal performs SL data transmission for the data corresponding to each QoS profile or QoS profile list, that is, implicitly indicating whether the terminal supports SL DRX and / or SL DTX through the used protocol version; and / or, directly and explicitly indicating whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for the data corresponding to each QoS profile or QoS profile list;

[0239] It should be noted that for direct communication interfaces, direct communication services are generated by the terminal's upper layer. Depending on the QoS of the service, the service can be divided into different QoS flows. Each QoS flow corresponds to a different QoS profile, and a group of QoS profiles can be combined to form a QoS profile list. The fourth information can indicate the protocol version used by each QoS profile or QoS profile list of the terminal for SL data transmission, and / or whether SL DRX and / or SL DTX are supported.

[0240] The above-mentioned protocol versions include a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SLDTX are not supported.

[0241] It can be understood that the above (B) to (E) are for different granularities of SL DRX and / or SL DTX.

[0242] In one possible implementation, the Tx profile is used to indicate any of the following:

[0243] (1) The correspondence between the terminal's SL service and the protocol version, and / or whether the terminal's SL service supports SL DRX and / or SL DTX;

[0244] (2) the protocol version used when the terminal performs SL data transmission, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0245] (3) the protocol version used when the terminal sends SL data for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal sends SL data for each target address;

[0246] (4) The protocol version used when the terminal performs SL data transmission for the data corresponding to each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SLDTX are supported when the terminal performs SL data transmission for the data corresponding to each QoS profile or QoS profile list for each target address.

[0247] In the embodiment of the present application, when the Tx profile is carried in the indication information, the Tx profile can be used to indicate the content indicated by the first information, the second information or the third information.

[0248] In a possible implementation manner, the identifier of the QoS profile in the indication information includes any one of the following:

[0249] (1) ProSe QoS Indentifier (PQI) corresponding to the QoS profile;

[0250] (2) When the terminal performs SL DRX and / or SL DTX for a QoS profile according to the SIB, the QoS profile number is determined according to the order in which the QoS profiles appear in the SIB, that is, the QoS profile or QoS profile list number is implicitly determined by the order in which the QoS profile or QoS profile list appears in the SIB;

[0251] (3) The QoS profile number indicated in the System Information Block (SIB) or 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 dedicated signaling.

[0252] In the embodiment of the present application, when the indication information content is (D), the QoS profile needs to be identified so that the network device can know which specific QoS profile it is. The specific identification can be determined using the above three methods.

[0253] In a possible implementation, sending the indication information to the network device includes: sending the indication information to the network device through first signaling;

[0254] The first signaling includes any one of the following:

[0255] (1) SidelinkUEInformation, that is, the indication information is carried in the existing SidelinkUEInformation signaling;

[0256] (2) RRC signaling, that is, introducing a new RRC signaling to carry the indication information;

[0257] (3) Media Access Control Element (MAC CE), that is, a new MAC CE is introduced to carry the indication information.

[0258] In a possible implementation, sending the indication information to the network device includes: sending the indication information to the network device after the lower layer of the terminal receives the Tx profile from the upper layer of the terminal.

[0259] In the embodiment of the present application, a prerequisite for sending the indication information is that the terminal lower layer receives the Tx profile configured by the terminal upper layer.

[0260] See also Figure 3 , an embodiment of the present application provides a configuration method, the execution subject of the method is a network device, and the method includes:

[0261] Step 301: The network device receives instruction information from the terminal;

[0262] Step 302: The network device determines whether SL DRX and / or SL DTX configuration needs to be performed on the terminal according to the indication information;

[0263] In an embodiment of the present application, the indication information is used to assist the network device in determining whether it is necessary to perform SL DRX and / or SL DTX configuration on the terminal. Specifically, the terminal can report the protocol version used by itself to the network device through the indication information. For example, 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 includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, it supports SL DRX and / or SL DTX, and when the terminal uses the second protocol version, it does not support SL DRX and / or SL DTX; alternatively, the terminal can also directly report whether it supports SL DRX and / or SL DTX to the network device through the indication information.

[0264] In an embodiment of the present application, the terminal assists the network device in determining whether SLDRX and / or SL DTX configuration is required for the terminal through indication information. In this manner, the network device performs SL DRX and / or SL DTX configuration for the terminal, which can ensure that the network device can know the activation time of the terminal's direct communication interface, thereby more reasonably scheduling the direct communication interface resources and improving the utilization rate of the direct communication interface resources.

[0265] In a possible implementation, the indication information includes any one of the following:

[0266] (A) Tx profile: This Tx profile is configured by the terminal's upper layer to the terminal's lower layer.

[0267] (B) first information, the first information indicating a protocol version used when the terminal performs SL data transmission, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission;

[0268] (C) second information, the second information indicating a protocol version used when the terminal performs SL data transmission for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for each target address;

[0269] (D) third information, the third information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list for each target address;

[0270] (E) fourth information, the fourth information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list;

[0271] The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SLDTX are not supported.

[0272] In one possible implementation, the Tx profile is used to indicate any of the following:

[0273] (1) The correspondence between the terminal's SL service and the protocol version, and / or whether the terminal's SL service supports SL DRX and / or SL DTX;

[0274] (2) the protocol version used when the terminal performs SL data transmission, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0275] (3) the protocol version used when the terminal sends SL data for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal sends SL data for each target address;

[0276] (4) The protocol version used when the terminal performs SL data transmission for the data corresponding to each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SLDTX are supported when the terminal performs SL data transmission for the data corresponding to each QoS profile or QoS profile list for each target address.

[0277] In a possible implementation manner, the identifier of the QoS profile in the indication information includes any one of the following:

[0278] (1) PQI corresponding to the QoS profile;

[0279] (2) When the terminal performs SL DRX and / or SL DTX for the QoS profile according to the SIB, the QoS profile number is determined according to the order in which the QoS profile appears in the SIB;

[0280] (3) The QoS profile number indicated in the SIB or dedicated signaling received by the terminal from the network device.

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

[0282] The first signaling includes any one of the following:

[0283] (1)SidelinkUEInformation;

[0284] (2)RRC signaling;

[0285] (3)MAC CE.

[0286] In a possible implementation, 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:

[0287] (1) When it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission, SL DRX and / or SL DTX configuration is performed on the terminal;

[0288] The embodiment of the present application is directed to the case where the content of the indication information is (A) or (B) above.

[0289] It can be understood that, according to the indication information, it is determined that the terminal needs to perform SL DRX and / or SL DTX when sending SL data. Specifically, the indication information may indicate that the terminal uses the first protocol version when sending SL data, or the indication information directly indicates that the terminal supports SL DRX and / or SL DTX when sending SL data.

[0290] (2) when it is determined according to the indication information that SLDRX and / or SL DTX need to be performed when the terminal performs SL data transmission to the first target address, SL DRX and / or SL DTX configuration is performed on the first target address;

[0291] The embodiment of the present application is directed to the case where the content of the indication information is (A) or (C) above.

[0292] It can be understood that what the terminal reports through the indication information is the protocol version used for each target address among all target addresses when sending SL data or whether SL DRX and / or SL DTX is supported. Therefore, all target addresses will include target addresses that require SL DRX and / or SL DTX and target addresses that do not require SL DRX and / or SL DTX. The above-mentioned first target address is the target address that requires SL DRX and / or SL DTX.

[0293] (3) when it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission on the data corresponding to the first QoS profile or QoS profile list of the first target address, SL DRX and / or SL DTX configuration is performed on the first QoS profile or QoS profile list or the logical channel belonging to the first QoS profile or QoS profile list;

[0294] The embodiment of the present application is directed to the case where the content of the indication information is (A) or (D) above.

[0295] It can be understood that what the terminal reports through the indication information is the protocol version used when sending SL data or whether SL DRX and / or SL DTX is supported for each QoS profile or QoS profile list in all QoS profiles or QoS profile lists of each target address. Therefore, all QoS profiles or QoS profile lists will include QoS profiles or QoS profile lists that require SL DRX and / or SL DTX, as well as QoS profiles or QoS profile lists that do not require SLDRX and / or SL DTX. The above-mentioned first QoS profile or QoS profile list is a QoS profile or QoS profile list that requires SL DRX and / or SL DTX.

[0296] The specific configuration method of performing SL DRX and / or SL DTX configuration on the terminal depends on the granularity of SL DRX and / or SLDTX. For example, the network device can determine the corresponding SL DRX and / or SL DTX based on each QoS profile or QoS profile list under each direct communication target address, and configure it to the terminal.

[0297] (4) when it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the data corresponding to the first QoS profile or QoS profile list, SL DRX and / or SL DTX configuration is performed on the first QoS profile or QoS profile list of the terminal or on the logical channel belonging to the first QoS profile or QoS profile list of the terminal;

[0298] The embodiments of the present application are directed to situations where the content of the indication information is (A) or (E) above.

[0299] It can be understood that what the terminal reports through the indication information is the protocol version used when sending SL data or whether SL DRX and / or SL DTX is supported for each QoS profile or QoS profile list in all QoS profiles or QoS profile lists. Therefore, all QoS profiles or QoS profile lists will include QoS profiles or QoS profile lists that require SLDRX and / or SL DTX, as well as QoS profiles or QoS profile lists that do not require SL DRX and / or SL DTX. The above-mentioned first QoS profile or QoS profile list is a QoS profile or QoS profile list that requires SL DRX and / or SL DTX.

[0300] (5) when it is determined according to the indication information that SL DRX and / or SL DTX are not required when the terminal is performing SL data transmission, SL DRX and / or SL DTX configuration is not performed on the terminal;

[0301] The embodiment of the present application is directed to the case where the content of the indication information is (A) or (B) above.

[0302] It can be understood that, according to the indication information, it is determined that the terminal does not need to perform SL DRX and / or SL DTX when sending SL data. Specifically, the indication information may indicate that the second protocol version is used when the terminal sends SL data, or the indication information directly indicates that the terminal does not support SL DRX and / or SL DTX when sending SL data.

[0303] (6) when it is determined according to the indication information that SLDRX and / or SL DTX is not required when the terminal performs SL data transmission to the first target address, SL DRX and / or SL DTX configuration is not performed on the first target address;

[0304] The embodiment of the present application is directed to the case where the content of the indication information is (A) or (C) above.

[0305] (7) When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal performs SL data transmission on the data corresponding to the first QoS profile or QoS profile list of the first target address, SL DRX and / or SL DTX configuration is not performed on the first QoS profile or QoS profile list or the logical channel belonging to the first QoS profile or QoS profile list.

[0306] The embodiment of the present application is directed to the case where the content of the indication information is (A) or (D) above.

[0307] (8) When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal sends SL data for the data corresponding to the first QoS profile or QoS profile list, SL DRX and / or SL DTX configuration is not performed for the first QoS profile or QoS profile list of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the terminal.

[0308] The embodiments of the present application are directed to situations where the content of the indication information is (A) or (E) above.

[0309] The configuration method provided by this application is described below with reference to specific embodiments:

[0310] Example 1: The content indicated by the instruction information is "the protocol version used by the terminal when sending data through the direct communication interface";

[0311] Step 1: The UE upper layer configures the Tx profile to the UE lower layer;

[0312] The Tx profile indicates the protocol version used by the terminal when sending data via the direct communication interface. If the Tx profile indicates the second protocol version, the terminal must use the second-version compatibility mode for data transmission, meaning it cannot use SL DRX and / or SL DTX. If the Tx profile indicates the first protocol version, the terminal can use the first protocol version mode for data transmission, meaning it can use SL DRX and / or SL DTX.

[0313] Step 2: The UE determines the content of the indication information;

[0314] Specifically, the UE determines the indication information in two ways:

[0315] (1) Directly use the Tx profile obtained by the terminal from the upper layer as the indication information

[0316] (2) The terminal extracts only the "protocol version used by the terminal when sending data on the direct communication interface" from the Tx profile and uses it as the indication information.

[0317] Step 3: The terminal sends instruction information to the network device;

[0318] Specifically, the prerequisite for sending the indication information may be one of the following:

[0319] (1) If SidelinkUEInformation is used to carry the information, the existing SidelinkUEInformation transmission conditions are reused;

[0320] (2) After receiving the Tx profile configuration from the upper layer and generating indication information based on the Tx profile, the terminal can start sending.

[0321] (3) Depends on terminal implementation.

[0322] The signaling used for the indication information may be one or a combination of the following:

[0323] (1) Carried by SidelinkUEInformation;

[0324] (2) Introducing new RRC signaling;

[0325] (3) Introduce new MAC CE.

[0326] Step 4: The network receives the instruction information and configures the terminal for SL DRX and / or SL DTX according to the instruction information.

[0327] If the instruction information obtained by the network device indicates the protocol version used by the terminal when sending data through the direct communication interface:

[0328] (1) If the network device determines, based on the indication information, that the "protocol version used by the terminal when sending data on the direct communication interface" is the second protocol version, the network device is not allowed to configure SL DRX and / or SL DTX for the terminal.

[0329] (2) If, based on the indication information, the network device determines that the "protocol version used by the terminal when sending data on the direct communication interface" is the first protocol version, the network device allows the configuration of SL DRX and / or SL DTX for the terminal. The specific configuration method depends on the granularity of SL DTX / DRX. For example, the network device can determine the corresponding SL DRX and / or SL DTX based on each QoS profile or QoS profile list under each direct communication target address, and configure it to the terminal.

[0330] Example 2: The content indicated by the instruction information is "the protocol version used by the terminal when sending direct communication interface data for each target address";

[0331] Step 1: The UE upper layer configures the Tx profile to the UE lower layer;

[0332] The Tx profile indicates the protocol version used by the terminal when sending data through the direct communication interface for each target address. The Tx profile can indicate the Release protocol version used by the terminal to send direct communication data for each target address. For example, if the Tx profile indicates that target address 1 corresponds to the second protocol version, then the terminal needs to use the second protocol version compatible mode to send data when sending data for target address 1 through the direct communication interface, that is, the terminal cannot use SL DRX and / or SL DTX. If the Tx profile indicates that target address 2 corresponds to the first protocol version, then the terminal can use the first protocol version mode to send data when sending data for target address 2 through the direct communication interface, that is, the terminal can use SL DRX and / or SL DTX.

[0333] Step 2: The UE determines the content of the indication information;

[0334] Specifically, the UE determines the indication information in two ways:

[0335] (1) Directly use the Tx profile obtained by the terminal from the upper layer as the indication information

[0336] (2) The terminal extracts only the “protocol version used by the terminal when sending data on the direct communication interface for each target address” from the Tx profile and uses it as the indication information.

[0337] Step 3: The terminal sends instruction information to the network device;

[0338] Specifically, the prerequisite for sending the indication information may be one of the following:

[0339] (1) If SidelinkUEInformation is used to carry the information, the existing SidelinkUEInformation transmission conditions are reused;

[0340] (2) After receiving the Tx profile configuration from the upper layer and generating indication information based on the Tx profile, the terminal can start sending.

[0341] (3) Depends on terminal implementation.

[0342] The signaling used for the indication information may be one or a combination of the following:

[0343] (1) Carried by SidelinkUEInformation;

[0344] (2) Introducing new RRC signaling;

[0345] (4) Introduce new MAC CE.

[0346] Step 4: The network receives the instruction information and performs SL DRX and / or SL DTX configuration on the terminal according to the instruction information;

[0347] The instruction information obtained by the network device indicates the protocol version used by the terminal when sending data through the direct communication interface for each target address:

[0348] (1) If the network device determines, based on the indication information, that the protocol version used by the terminal when sending direct communication interface data for a specific target address is the second protocol version, the network device is not allowed to configure SL DRX and / or SL DTX for the specific direct communication target address of the terminal.

[0349] (2) If, based on the indication information, the network device determines that the "protocol version used by the terminal when sending direct communication interface data for a specific target address" is the first protocol version, the network device allows SL DRX and / or SL DTX to be configured for the specific direct communication target address of the terminal. The specific configuration method depends on the granularity of SL DTX / DRX. For example, the network device can determine the corresponding SLDRX and / or SL DTX based on each QoS profile or QoS profile list under the specific target address, and configure it to the terminal.

[0350] Example 3: The content indicated by the indication information is "the protocol version used by the terminal when sending data corresponding to each QoS profile or QoS profile list of each target address through the direct communication interface";

[0351] Step 1: The UE upper layer configures the Tx profile to the UE lower layer;

[0352] The Tx profile indicates the protocol version used by the terminal when sending data on the direct communication interface corresponding to each QoS profile or QoS profile list for each target address. If the Tx profile indicates that the QoS profile list 1 (specifically, it can be the PQI list) under the direct communication interface 1 corresponds to the second protocol version, then when the terminal sends data on the logical channel belonging to the QoS profile list 1 under the direct communication interface for the target address 1, it is necessary to use the second protocol version compatible mode to send data, that is, the terminal cannot use SL DRX and / or SL DTX. If the Tx profile indicates that the QoS profile list 2 (specifically, it can be the PQI list) under the direct communication interface 1 corresponds to the first protocol version, then when the terminal sends data on the logical channel belonging to the QoS profile list 2 under the direct communication interface for the target address 1, it is necessary to use the first protocol version mode to send data, that is, the terminal cannot use SL DRX and / or SL DTX.

[0353] Step 2: UE determines the content of the indication information

[0354] Specifically, the UE determines the indication information in two ways:

[0355] (1) Directly use the Tx profile obtained by the terminal from the upper layer as the indication information

[0356] (2) The terminal extracts only the "protocol version used by the terminal when sending data corresponding to each QoS profile or QoS profile list of each target address through the direct communication interface" from the Tx profile and uses it as the indication information.

[0357] QoS profiles can be identified in the following ways:

[0358] (1) Directly use the QoS profile number (i.e., PQI) as the identifier;

[0359] (2) When configuring the DRX configuration corresponding to a QoS profile or QoS profile list according to the SIB, the order in which the QoS profile or QoS profile list appears in the SIB implicitly determines the number of the QoS profile or QoS profile list;

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

[0361] Step 3: The terminal sends instruction information to the network device

[0362] Specifically, the prerequisite for sending the indication information may be one of the following:

[0363] (1) If SidelinkUEInformation is used to carry the information, the existing SidelinkUEInformation transmission conditions are reused;

[0364] (2) After receiving the Tx profile configuration from the upper layer and generating indication information based on the Tx profile, the terminal can start sending.

[0365] (3) The newly arrived QoS flow belongs to the new QoS profile or QoS profile list;

[0366] (4) The QoS flow belonging to a certain QoS profile or all QoS flows belonging to a certain QoS profile list terminate data transmission;

[0367] (5) Whether any QoS profile or QoS profile list uses SL DRX and / or the status of SL DTX changes;

[0368] (6) Depends on terminal implementation.

[0369] The signaling used for the indication information may be one or a combination of the following:

[0370] (1) Carried by SidelinkUEInformation;

[0371] (2) Introducing new RRC signaling;

[0372] (3) Introduce new MAC CE.

[0373] Step 4: The network receives the instruction information and performs scheduling according to the instruction information

[0374] If the instruction information obtained by the network device indicates "the protocol version used by the terminal when sending data corresponding to each QoS profile or QoS profile list for each target address through the direct communication interface":

[0375] (1) If the network device determines, based on the indication information, that the protocol version used by the terminal when sending data on the direct communication interface corresponding to a QoS profile or a QoS profile list under a specific target address is the second protocol version, the network device shall not configure SL DRX and / or SL DTX for the QoS profile or QoS profile list under the specific target address of the terminal or the logical channel belonging to the QoS profile or QoS profile list.

[0376] (2) If, based on the indication information, the network device determines that the "protocol version used by the terminal when sending data on the direct communication interface corresponding to a QoS profile or QoS profile list under a specific target address" is the first protocol version, the network device allows the configuration of SL DRX and / or SL DTX for the QoS profile or QoS profile list under the specific target address of the terminal or the logical channel belonging to the QoS profile or QoS profile list.

[0377] See also Figure 4 The embodiment of the present application provides a terminal, including a first memory 401, a first transceiver 402, a first processor 403, and a user interface 404:

[0378] The first transceiver 402 is configured to receive and send data under the control of the first processor 403 .

[0379] Among them, Figure 4 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by the first processor 403 and the memory represented by the first memory 401. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and therefore will not be described further herein. The bus interface provides an interface. The first transceiver 402 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. For different user devices, the user interface 404 may also be an interface capable of connecting external or internal devices as required, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

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

[0381] Optionally, 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.

[0382] The first processor 403 is configured to read the computer program in the first memory 401 and execute the following Figure 2 The configuration method shown:

[0383] The first transceiver 402 is used for the terminal to send 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.

[0384] In a possible implementation, the indication information includes any one of the following:

[0385] Tx profile, which is configured by the terminal upper layer to the terminal lower layer;

[0386] First information, where the first information indicates a protocol version used when the terminal performs SL data transmission, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission;

[0387] second information, where the second information indicates a protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0388] third information, where the third information indicates a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address;

[0389] Fourth information, the fourth information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list;

[0390] The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SLDTX are not supported.

[0391] In one possible implementation, the Tx profile is used to indicate any of the following:

[0392] The correspondence between the terminal's SL service and the protocol version, and / or whether the terminal's SL service supports SL DRX and / or SL DTX;

[0393] The protocol version used when the terminal performs SL data transmission, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0394] The protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0395] The protocol version used when the terminal sends SL data for each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal sends SL data for each QoS profile or QoS profile list for each target address.

[0396] In a possible implementation manner, the identifier of the QoS profile in the indication information includes any one of the following:

[0397] PQI corresponding to the QoS profile;

[0398] When the terminal performs SL DRX and / or SL DTX for the QoS profile according to the SIB, the QoS profile number is determined according to the order in which the QoS profile appears in the SIB;

[0399] The QoS profile number indicated in the SIB or dedicated signaling received by the terminal from the network device.

[0400] In a possible implementation, sending instruction information to the network device includes:

[0401] Sending instruction information to the network device through the first signaling;

[0402] The first signaling includes any one of the following:

[0403] SidelinkUEInformation;

[0404] RRC signaling;

[0405] MAC CE.

[0406] In a possible implementation manner, the first transceiver 402 is further configured to:

[0407] After the lower layer of the terminal receives the Tx profile from the upper layer of the terminal, it sends indication information to the network device.

[0408] See also Figure 5 , an embodiment of the present application provides a network device, including a second memory 501, a second transceiver 502, and a second processor 503:

[0409] The second transceiver 502 is configured to receive and send data under the control of the second processor 503 .

[0410] Among them, Figure 5 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by the second processor 503 and the memory represented by the second memory 501. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The second transceiver 502 may be a plurality of components, i.e., including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, 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.

[0411] 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). The processor may also adopt a multi-core architecture.

[0412] The second processor 503 is used to read the computer program in the second memory 501 and execute the following Figure 3 The configuration method shown:

[0413] The second transceiver 502 is used for the network device to receive indication information from the terminal;

[0414] The second processor 503 is configured to determine, by the network device, whether it is necessary to perform SL DRX and / or SL DTX configuration on the terminal according to the indication information.

[0415] In a possible implementation, the indication information includes any one of the following:

[0416] Tx profile, which is configured by the terminal upper layer to the terminal lower layer;

[0417] First information, where the first information indicates a protocol version used when the terminal performs SL data transmission, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission;

[0418] second information, where the second information indicates a protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0419] third information, where the third information indicates a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address;

[0420] Fourth information, the fourth information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list;

[0421] The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SLDTX are not supported.

[0422] In one possible implementation, the Tx profile is used to indicate any of the following:

[0423] The correspondence between the terminal's SL service and the protocol version, and / or whether the terminal's SL service supports SL DRX and / or SL DTX;

[0424] The protocol version used when the terminal performs SL data transmission, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0425] The protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0426] The protocol version used when the terminal sends SL data for each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal sends SL data for each QoS profile or QoS profile list for each target address.

[0427] In a possible implementation manner, the identifier of the QoS profile in the indication information includes any one of the following:

[0428] The proximity service quality indicator (PQI) corresponding to the QoS profile;

[0429] When the terminal performs SL DRX and / or SL DTX for the QoS profile according to the SIB, the QoS profile number is determined according to the order in which the QoS profile appears in the SIB;

[0430] The QoS profile number indicated in the SIB or dedicated signaling received by the terminal from the network device.

[0431] In a possible implementation, receiving indication information from a terminal includes:

[0432] receiving indication information from a terminal through a first signaling;

[0433] The first signaling includes any one of the following:

[0434] SidelinkUEInformation;

[0435] RRC signaling;

[0436] MAC CE.

[0437] In one possible implementation, the second processor is further configured to:

[0438] When it is determined according to the indication information that SL DRX and / or SL DTX needs to be performed when the terminal performs SL data transmission, performing SL DRX and / or SL DTX configuration on the terminal;

[0439] When it is determined according to the indication information that SLDRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the first target address, perform SL DRX and / or SL DTX configuration on the first target address;

[0440] When it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the data corresponding to the first QoS profile or QoS profile list of the first target address, SL DRX and / or SL DTX configuration is performed on the first QoS profile or QoS profile list or the logical channel belonging to the first QoS profile or QoS profile list;

[0441] When it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the data corresponding to the first QoS profile or QoS profile list, SLDRX and / or SL DTX configuration is performed on the first QoS profile or QoS profile list of the terminal or on the logical channel belonging to the first QoS profile or QoS profile list of the terminal;

[0442] When it is determined according to the instruction information that SL DRX and / or SL DTX is not required when the terminal performs SL data transmission, SL DRX and / or SL DTX configuration is not performed on the terminal;

[0443] When it is determined according to the instruction information that the terminal does not need to perform SLDRX and / or SL DTX when performing SL data transmission for the first target address, SL DRX and / or SL DTX configuration is not performed on the first target address;

[0444] When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal sends SL data corresponding to the first QoS profile or QoS profile list for the first target address, SL DRX and / or SL DTX are not configured for the first QoS profile or QoS profile list or the logical channel belonging to the first QoS profile or QoS profile list.

[0445] When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal sends SL data for the data corresponding to the first QoS profile or QoS profile list, SL DRX and / or SL DTX configuration is not performed for the first QoS profile or QoS profile list of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the terminal.

[0446] See also Figure 6 In an embodiment of the present application, a terminal 600 includes:

[0447] The sending unit 601 is configured for the terminal to send 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.

[0448] In a possible implementation, the indication information includes any one of the following:

[0449] Tx profile, which is configured by the terminal upper layer to the terminal lower layer;

[0450] First information, where the first information indicates a protocol version used when the terminal performs SL data transmission, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission;

[0451] second information, where the second information indicates a protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0452] third information, where the third information indicates a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address;

[0453] Fourth information, the fourth information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list;

[0454] The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SLDTX are not supported.

[0455] In one possible implementation, the Tx profile is used to indicate any of the following:

[0456] The correspondence between the terminal's SL service and the protocol version, and / or whether the terminal's SL service supports SL DRX and / or SL DTX;

[0457] The protocol version used when the terminal performs SL data transmission, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0458] The protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0459] The protocol version used when the terminal sends SL data for each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal sends SL data for each QoS profile or QoS profile list for each target address.

[0460] In a possible implementation manner, the identifier of the QoS profile in the indication information includes any one of the following:

[0461] PQI corresponding to the QoS profile;

[0462] When the terminal performs SL DRX and / or SL DTX for the QoS profile according to the SIB, the QoS profile number is determined according to the order in which the QoS profile appears in the SIB;

[0463] The QoS profile number indicated in the SIB or dedicated signaling received by the terminal from the network device.

[0464] In a possible implementation, sending instruction information to the network device includes:

[0465] Sending instruction information to the network device through the first signaling;

[0466] The first signaling includes any one of the following:

[0467] SidelinkUEInformation;

[0468] RRC signaling;

[0469] MAC CE.

[0470] In a possible implementation manner, the sending unit is further configured to:

[0471] After the lower layer of the terminal receives the Tx profile from the upper layer of the terminal, it sends indication information to the network device.

[0472] It should be noted that the above-mentioned acquisition unit can also be a transceiver unit, and the above-mentioned determination unit can also be a processing unit, or other units that can complete the technical solution provided by this application. They will not be repeated here. The determination unit and the acquisition unit are just names given for the convenience of description. In the actual process, the device can be a combination of multiple units, or a part of a certain unit. The embodiment of this application does not limit this. As long as the related functions it performs are similar to those of this unit, it belongs to the scope of protection of this application.

[0473] The division of units in the embodiments of the present application is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0474] The scope of the methods and apparatus in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved. For example, the described methods may be performed in an order different from 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.

[0475] See also Figure 7 , an embodiment of the present application provides a network device 700, including:

[0476] Receiving unit 701, configured for the network device to receive indication information from the terminal;

[0477] The determining unit 702 is configured for the network device to determine whether it is necessary to perform SL DRX and / or SL DTX configuration on the terminal according to the indication information.

[0478] In a possible implementation, the indication information includes any one of the following:

[0479] Tx profile, which is configured by the terminal upper layer to the terminal lower layer;

[0480] First information, where the first information indicates a protocol version used when the terminal performs SL data transmission, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission;

[0481] second information, where the second information indicates a protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0482] third information, where the third information indicates a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list of each target address;

[0483] Fourth information, the fourth information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list;

[0484] The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SLDTX are not supported.

[0485] In one possible implementation, the Tx profile is used to indicate any of the following:

[0486] The correspondence between the terminal's SL service and the protocol version, and / or whether the terminal's SL service supports SL DRX and / or SL DTX;

[0487] The protocol version used when the terminal performs SL data transmission, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission;

[0488] The protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address;

[0489] The protocol version used when the terminal sends SL data for each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal sends SL data for each QoS profile or QoS profile list for each target address.

[0490] In a possible implementation manner, the identifier of the QoS profile in the indication information includes any one of the following:

[0491] PQI corresponding to the QoS profile;

[0492] When the terminal performs SL DRX and / or SL DTX for the QoS profile according to the SIB, the QoS profile number is determined according to the order in which the QoS profile appears in the SIB;

[0493] The QoS profile number indicated in the SIB or dedicated signaling received by the terminal from the network device.

[0494] In a possible implementation, receiving indication information from a terminal includes:

[0495] receiving indication information from a terminal through a first signaling;

[0496] The first signaling includes any one of the following:

[0497] SidelinkUEInformation;

[0498] RRC signaling;

[0499] MAC CE.

[0500] In a possible implementation manner, the determining unit is further configured to perform any of the following:

[0501] When it is determined according to the indication information that SL DRX and / or SL DTX needs to be performed when the terminal performs SL data transmission, performing SL DRX and / or SL DTX configuration on the terminal;

[0502] When it is determined according to the indication information that SLDRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the first target address, perform SL DRX and / or SL DTX configuration on the first target address;

[0503] When it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the data corresponding to the first QoS profile or QoS profile list of the first target address, SL DRX and / or SL DTX configuration is performed on the first QoS profile or QoS profile list or the logical channel belonging to the first QoS profile or QoS profile list;

[0504] When it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the data corresponding to the first QoS profile or QoS profile list, SLDRX and / or SL DTX configuration is performed on the first QoS profile or QoS profile list of the terminal or on the logical channel belonging to the first QoS profile or QoS profile list of the terminal;

[0505] When it is determined according to the instruction information that SL DRX and / or SL DTX is not required when the terminal performs SL data transmission, SL DRX and / or SL DTX configuration is not performed on the terminal;

[0506] When it is determined according to the instruction information that the terminal does not need to perform SLDRX and / or SL DTX when performing SL data transmission for the first target address, SL DRX and / or SL DTX configuration is not performed on the first target address;

[0507] When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal sends SL data corresponding to the first QoS profile or QoS profile list for the first target address, SL DRX and / or SL DTX are not configured for the first QoS profile or QoS profile list or the logical channel belonging to the first QoS profile or QoS profile list.

[0508] When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal sends SL data for the data corresponding to the first QoS profile or QoS profile list, SL DRX and / or SL DTX configuration is not performed for the first QoS profile or QoS profile list of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the terminal.

[0509] The scope of the methods and apparatus in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved. For example, the described methods may be performed in an order different from 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.

[0510] It should be noted that the above-mentioned sending unit can also be a radio frequency unit, or other units that can complete the technical solution provided by this application. They will not be repeated here. The sending unit is just a name given for the convenience of description. In the actual process, the device can be a combination of multiple units, or a part of a certain unit. The embodiment of this application does not limit this. As long as the related functions it performs are similar to those of this unit, it falls within the scope of protection of this application.

[0511] It should be noted that the division of units in the embodiments of the present application is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0512] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0513] The embodiment of the present application further provides a terminal, including a transceiver and a processor;

[0514] A transceiver is used to receive and send data under the control of the processor.

[0515] A transceiver can be multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, or an optical cable. A processor can 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). The processor can also adopt a multi-core architecture.

[0516] The above-mentioned processor is used to execute the terminal side configuration method as described above, which will not be repeated here.

[0517] The embodiment of the present application further provides a network device, including a transceiver and a processor;

[0518] A transceiver is used to receive and send data under the control of the processor.

[0519] A transceiver can be multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, or an optical cable. A processor can 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). The processor can also adopt a multi-core architecture.

[0520] The above-mentioned processor is used to execute the configuration method on the network device side as described above, which will not be repeated here.

[0521] An embodiment of the present application also provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned PUSCH-based repeated transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0522] It should be understood that the chip mentioned in the embodiment of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip. The embodiment of the present application provides a computer-readable storage medium, which stores a computer program for causing a computer to execute Figure 2 The configuration method shown, or for causing the processor to execute Figure 3 The configuration method shown.

[0523] Computer-readable storage media can be any available media or data storage devices that can be accessed by a computer, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor memories (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid-state drives (SSDs), etc.).

[0524] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) that contain computer-usable program code.

[0525] An embodiment of the present invention further provides a computer program product, which is stored in a non-volatile storage medium and configured to be executed by at least one processor to implement the steps of the method described above.

[0526] The present application is described with reference to the flowchart and / or block diagram of the method, device (system), and computer program product according to the embodiment of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, and the combination of the process and / or box in the flowchart and / or block diagram can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processing machine or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the function specified in one process or multiple processes in the flowchart and / or one box or multiple boxes in the block diagram.

[0527] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0528] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0529] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A configuration method, characterized in that: The method comprises: The terminal sends 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; The instruction information includes any one of the following: Send configuration Tx profile, the Tx profile is configured by the terminal high layer to the terminal low layer; First information, where the first information indicates a protocol version used when the terminal performs SL data transmission; or, the first information indicates a protocol version used when the terminal performs SL data transmission, and whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission; second information indicating a protocol version used when the terminal performs SL data transmission for each target address, and / or indicating whether SLDRX and / or SL DTX are supported when the terminal performs SL data transmission for each target address; third information, the third information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each quality of service configuration QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list for each target address; fourth information, the fourth information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list; The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SL DTX are not supported.

2. The method according to claim 1, characterized in that The Tx profile is used to indicate any of the following: The correspondence 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; a protocol version used when the terminal performs SL data transmission, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission; a protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address; The protocol version used when the terminal sends SL data for each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SLDTX are supported when the terminal sends SL data for each QoS profile or QoS profile list for each target address.

3. The method according to claim 1, characterized in that The identifier of the QoS profile in the indication information includes any one of the following: A proximity service quality identifier (PQI) corresponding to the QoS profile; In a case where the terminal performs SL DRX and / or SL DTX for the QoS profile according to a system information block (SIB), the QoS profile number is determined according to the order in which the QoS profile appears in the SIB; The number of the QoS profile indicated in the SIB or dedicated signaling received by the terminal from the network device.

4. The method according to claim 1, wherein The sending of instruction information to the network device includes: Sending the indication information to the network device through a first signaling; The first signaling includes any one of the following: Direct communication terminal information SidelinkUEInformation; Radio Resource Control (RRC) signaling; Media Access Control Unit MAC CE.

5. The method according to claim 1, wherein The sending of instruction information to the network device includes: After the lower layer of the terminal receives the Tx profile from the upper layer of the terminal, the lower layer of the terminal sends the indication information to the network device.

6. A configuration method, characterized in that: The method comprises: The network device receives instruction information from the terminal; The network device determines, according to the indication information, whether it is necessary to perform SL DRX and / or SL DTX configuration on the terminal; The instruction information includes any one of the following: Tx profile, which is configured by the terminal upper layer to the terminal lower layer; First information, where the first information indicates a protocol version used when the terminal performs SL data transmission; or, the first information indicates a protocol version used when the terminal performs SL data transmission, and whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission; second information indicating a protocol version used when the terminal performs SL data transmission for each target address, and / or indicating whether SLDRX and / or SL DTX are supported when the terminal performs SL data transmission for each target address; third information, the third information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list for each target address; fourth information, the fourth information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list; The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SL DTX are not supported.

7. The method according to claim 6, characterized in that The Tx profile is used to indicate any of the following: The correspondence 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; a protocol version used when the terminal performs SL data transmission, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission; a protocol version used when the terminal performs SL data transmission for each target address, and / or whether the terminal supports SL DRX and / or SL DTX when the terminal performs SL data transmission for each target address; The protocol version used when the terminal sends SL data for each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SLDTX are supported when the terminal sends SL data for each QoS profile or QoS profile list for each target address.

8. The method according to claim 6, characterized in that The identifier of the QoS profile in the indication information includes any one of the following: A proximity service quality identifier (PQI) corresponding to the QoS profile; When the terminal performs SL DRX and / or SL DTX for the QoS profile according to a system information block (SIB), the QoS profile number is determined according to the order in which the QoS profile appears in the SIB; The number of the QoS profile indicated in the SIB or dedicated signaling received by the terminal from the network device.

9. The method according to claim 6, characterized in that The receiving instruction information from the terminal includes: receiving the indication information from the terminal through first signaling; The first signaling includes any one of the following: SidelinkUEInformation; RRC signaling; MAC CE.

10. The method according to claim 6, characterized in that The determining, according to the indication information, whether it is necessary to perform SL DRX and / or SL DTX configuration on the terminal includes any one of the following: When it is determined according to the indication information that SL DRX and / or SL DTX needs to be performed when the terminal performs SL data transmission, performing SL DRX and / or SL DTX configuration on the terminal; When it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the first target address, perform SL DRX and / or SL DTX configuration on the first target address; When it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the data corresponding to the first QoS profile or QoS profile list of the first target address, SL DRX and / or SLDTX configuration is performed on the first QoS profile or QoS profile list of the first target address of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the first target address of the terminal; When it is determined according to the indication information that SL DRX and / or SL DTX need to be performed when the terminal performs SL data transmission for the data corresponding to the first QoS profile or QoS profile list, performing SL DRX and / or SL DTX configuration on the first QoS profile or QoS profile list of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the terminal; When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal performs SL data transmission, not performing SL DRX and / or SL DTX configuration on the terminal; When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal performs SL data transmission for the first target address, SL DRX and / or SL DTX configuration is not performed on the first target address; When it is determined according to the indication information that SL DRX and / or SL DTX are not required when the terminal performs SL data transmission for the data corresponding to the first QoS profile or QoS profile list of the first target address, SL DRX and / or SLDTX configuration is not performed for the first QoS profile or QoS profile list of the first target address of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the first target address of the terminal; When it is determined according to the indication information that SL DRX and / or SL DTX is not required when the terminal sends SL data for the data corresponding to the first QoS profile or QoS profile list, SL DRX and / or SL DTX configuration is not performed for the first QoS profile or QoS profile list of the terminal or the logical channel belonging to the first QoS profile or QoS profile list of the terminal.

11. A terminal, characterized in that: The device comprises a first memory, a first transceiver, and a first processor: The first memory is used to store a computer program; the first transceiver is used to send and receive data under the control of the first processor; the first processor is used to read the computer program in the first memory and execute the configuration method according to any one of claims 1 to 5.

12. A network device, characterized in that: including a second memory, a second transceiver, and a second processor: The second memory is used to store a computer program; the second transceiver is used to send and receive data under the control of the second processor; the second processor is used to read the computer program in the second memory and execute the configuration method according to any one of claims 6 to 10.

13. A terminal, characterized in that: include: A sending unit, configured for a terminal to send indication information to a network device, wherein 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; The instruction information includes any one of the following: Send configuration Tx profile, the Tx profile is configured by the terminal high layer to the terminal low layer; First information, where the first information indicates a protocol version used when the terminal performs SL data transmission; or, the first information indicates a protocol version used when the terminal performs SL data transmission, and whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission; second information indicating a protocol version used when the terminal performs SL data transmission for each target address, and / or indicating whether SLDRX and / or SL DTX are supported when the terminal performs SL data transmission for each target address; third information, the third information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each quality of service configuration QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list for each target address; fourth information, the fourth information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list; The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SL DTX are not supported.

14. A network device, characterized in that: include: A receiving unit, configured for the network device to receive instruction information from a terminal; A determination unit is used for the network device to determine whether it is necessary to perform SL DRX and / or SL DTX configuration on the terminal according to the indication information. The instruction information includes any one of the following: Tx profile, which is configured by the terminal upper layer to the terminal lower layer; First information, where the first information indicates a protocol version used when the terminal performs SL data transmission; or, the first information indicates a protocol version used when the terminal performs SL data transmission, and whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission; second information indicating a protocol version used when the terminal performs SL data transmission for each target address, and / or indicating whether SLDRX and / or SL DTX are supported when the terminal performs SL data transmission for each target address; third information, the third information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list for each target address, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list for each target address; fourth information, the fourth information indicating a protocol version used when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list, and / or whether SL DRX and / or SL DTX are supported when the terminal performs SL data transmission for data corresponding to each QoS profile or QoS profile list; The protocol version includes a first protocol version and a second protocol version. When the terminal uses the first protocol version, SL DRX and / or SL DTX are supported. When the terminal uses the second protocol version, SL DRX and / or SL DTX are not supported.

15. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the configuration method according to any one of claims 1 to 5, or to execute the configuration method according to any one of claims 6 to 10.

Images