WO2023122964A1

WO2023122964A1 - Message transmission method, related device, and medium

Info

Publication number: WO2023122964A1
Application number: PCT/CN2021/142104
Authority: WO
Inventors: 冷冰雪; 刘洋; 卢前溪; 范江胜
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-12-28
Filing date: 2021-12-28
Publication date: 2023-07-06

Abstract

Disclosed by embodiments of the present application are a message transmission method, related device, and medium, applied to a sidelink communication system; the method comprises: a first terminal determining a first message, the first message comprising: reporting reason information, the reporting reason information comprising reason information for generating PC5 RLF and/or reason information used for indicating a triggering resource configuration; the first terminal sending the first message to a network device. Using the embodiments of the present application facilitates improved reliability of data transmission in sidelink communication.

Description

Message transmission method, related equipment and medium

technical field

The present application relates to the technical field of communications, and in particular to a message transmission method, related equipment and media.

Background technique

In sidelink communication, the network configures sidelink parameters or resources for the terminal, so that the terminal can perform sidelink data transmission based on the sidelink parameters or resources. However, the inventor realized that when the network configures sidelink parameters or resources for the terminal, there are often unreasonable configurations of sidelink parameters or resources, resulting in poor reliability of terminal data transmission. For example, in the PC5 wireless link failure (Radio Link failure, RLF) triggering scenario, the network controls the triggering conditions of PC5 RLF by configuring PC5 configuration parameters. When PC5 RLF occurs, the terminal will disconnect from the peer terminal where RLF occurs. However, the PC5 configuration parameters may be set unreasonably, and at this time, the terminal may wrongly trigger RLF, resulting in unreliable triggering of RLF and unreliable data transmission. For another example, when the network schedules resources for sidelink data transmission for the terminal, it may schedule inappropriate resources for the terminal, such as too many scheduled retransmission resources lead to waste of resources or too few scheduled resources lead to transmission failure, etc. resulting in unreliable data transmission.

Contents of the invention

Embodiments of the present application provide a message transmission method, related equipment and media, which help to improve the reliability of data transmission in sidelink communication.

In the first aspect, the embodiment of the present application provides a message transmission method, which is applied to a sidelink communication system, and the method includes:

The first terminal determines a first message, where the first message includes: report cause information, where the report cause information includes cause information for occurrence of PC5RLF and/or cause information for indicating trigger resource configuration;

The first terminal sends the first message to a network device.

Optionally, the first message further includes any one or more of the following: link information of the sidelink between the first terminal and the second terminal, the link information used by the first terminal The channel busy rate CBR information of the resource pool, the first time information, the first location information, and the identifier of the second terminal.

Optionally, the link information includes any one or more of the following: reference signal received power RSRP, data packet transmission information; and/or, the first time information includes information measurement or data performed by the first terminal time information of the transmission; and/or, the first location information includes location information at which the first terminal performs information measurement or data transmission.

Optionally, the cause information of the occurrence of PC5 RLF includes any one or more of the following: the first terminal reaches the maximum number of retransmissions indicated by the radio link control RLC entity, and the first timer of the first terminal When timeout occurs, the first terminal reaches the maximum number of consecutive hybrid automatic repeat request HARQ discontinuous transmission DTX times indicated by the medium access control MAC entity, and the packet data aggregation protocol PDCP entity integrity check fails.

In a possible implementation manner, the first terminal sending the first message to the network device includes:

When PC5 RLF occurs, the first terminal sends the first message to the network device;

Wherein, the reported reason information includes the reason information of PC5 RLF.

Optionally, the reported reason information is used to indicate the reason information for triggering resource configuration, and the reason information includes any one or more of the following: remaining unused resource information, transmission failure information.

Optionally, the remaining unused resource information includes any one or more of the following: indication information indicating that there is an event of remaining unused resources, a first threshold, the number of remaining unused resources, the first terminal being in Discontinuously receive the time information of the DRX inactive state or the DRX active state, and the configuration resource information in the DRX inactive state.

Optionally, the transmission failure information includes any one or more of the following: indication information for indicating that a transmission failure event exists, a second threshold, and the number of transmission failures.

In a possible implementation manner, before the first terminal determines the first message, the method further includes:

When the first terminal receives the first resource configuration information sent from the network device, the first terminal sets the remaining unused resource counter and/or transmission failure counter to zero;

The first terminal performs data transmission with the second terminal according to the first resource configuration information.

When the count of the remaining unused resource counter reaches a first threshold, the first terminal sends the first message to a network device;

Wherein, the reason information includes the remaining unused resource information.

In a possible implementation, the method also includes:

When the first terminal receives the confirmation ACK message returned by the second terminal, the first terminal discards the remaining unused resources corresponding to the first resource configuration information, and controls the remaining unused resource counter to add one.

In a possible implementation, the method also includes:

When the configured resource indicated by the first resource configuration information is in the DRX inactive state, discard the configured resource, and control the remaining unused resource counter to add one.

When the count of the transmission failure counter reaches a second threshold, the first terminal sends the first message to a network device;

Wherein, the cause information includes the transmission failure information.

In a possible implementation, the method also includes:

When the first terminal receives the non-acknowledgement NACK message returned by the second terminal, and all configured resources indicated by the first resource configuration information are used, the first terminal controls the failure counter to add one.

In a possible implementation manner, after the first terminal sends the first message to the network device, the method further includes:

The first terminal receives PC5 configuration parameters from the network device, and detects PC5 RLF according to the PC5 configuration parameters; and/or,

The first terminal receives second resource configuration information from the network device, and performs data transmission with the second terminal according to the second resource configuration information.

In a second aspect, the embodiment of the present application provides a message transmission method, the method including:

The network device receives a first message from the first terminal, where the first message includes: report cause information, where the report cause information includes cause information for PC5 RLF and/or cause information for indicating trigger resource configuration;

The network device performs information configuration according to the first message.

The first message further includes any one or more of the following: link information of the sidelink between the first terminal and the second terminal, channel busy rate of the resource pool used by the first terminal CBR information, first time information, first location information, and an identifier of the second terminal.

Optionally, the remaining unused resource information includes any one or more of the following: indication information indicating that there is an event of remaining unused resources, a first threshold, the amount of the remaining unused resources, the first The terminal is in discontinuous reception of the time information of the DRX inactive state or the DRX active state, and the configuration resource information of the DRX inactive state.

In a possible implementation, the reported cause information includes the cause information of PC5 RLF; the network device performs information configuration according to the first message, including:

The network device determines PC5 configuration parameters according to the first message;

The method also includes:

The network device sends the PC5 configuration parameters to the first terminal.

In a possible implementation, before the network device receives the first message from the first terminal, the method further includes:

The network device sends first resource configuration information to the first terminal;

The network device performs information configuration according to the first message, including:

determining, by the network device, second resource configuration information according to the first message;

The method also includes:

The network device sends the second resource configuration information to the first terminal.

In a third aspect, the embodiment of the present application provides a terminal, the terminal has some or all functions for realizing the behavior of the terminal in the above method, such as the first terminal. Optionally, the terminal may realize the function through hardware, or execute corresponding software through hardware to realize the function. The hardware or software may include one or more units or modules corresponding to the functions described above.

For example, in a possible design, the terminal includes a processing unit and a communication unit. Wherein, the processing unit may be configured to support the terminal to perform corresponding functions in the above methods. The communication unit can be used to support communication between the terminal and other devices. Optionally, the terminal may further include a storage unit, and the storage unit may be coupled with the processing unit for storing necessary program instructions and data of the terminal, and the like. Optionally, the processing unit may be a processor, the communication unit may be a communication interface or a transceiver, and the storage unit may be a memory.

In a fourth aspect, the embodiment of the present application provides a network device, where the network device has some or all functions for realizing the behavior of the network device in the above method. Optionally, this function may be realized by hardware, or may be realized by executing corresponding software by hardware. The hardware or software may include one or more units or modules corresponding to the above functions.

For example, in a possible design, a network device includes a communication unit and a processing unit. Wherein, the processing unit may be configured to support the network device to perform corresponding functions in the above method, and the communication unit may be configured to support communication between the network device and other devices. Optionally, the network device may further include a storage unit, which may be coupled with the processing unit, and store necessary program instructions and data of the network device, and the like. Optionally, the processing unit may be a processor, the communication unit may be a communication interface or a transceiver, and the storage unit may be a memory.

In a fifth aspect, the embodiment of the present application provides a terminal, including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured by the processor Execute to realize some or all steps of the method in the first aspect of the embodiment of the present application.

In a sixth aspect, the embodiment of the present application provides a network device, including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be processed by the executed by a device to implement some or all of the steps of the method in the second aspect of the embodiment of the present application.

In the seventh aspect, the embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and the computer program causes the computer to execute the part described in the method of the first aspect of the embodiment of the present application or all steps.

In the eighth aspect, the embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and the computer program enables the computer to execute the part described in the method of the second aspect of the embodiment of the present application or all steps.

In a ninth aspect, the embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to enable the computer to execute the program as implemented in the present application. For example, part or all of the steps described in the method of the first aspect, or the computer program is operable to cause a computer to perform some or all of the steps described in the method of the second aspect of the embodiment of the present application. For example, the computer program product may be a software installation package.

In the solution provided by the embodiment of this application, the terminal can report to the network the cause information of some problems in the sidelink transmission process, such as the specific reason for the occurrence of PC5 RLF and/or the specific reason for indicating the triggering of resource configuration , which can help the network to configure information, such as adjusting sidelink parameters and/or resource allocation, etc., which helps to solve the problem of unreasonable information configuration due to the network's inability to perceive the transmission situation on the sidelink , which in turn helps to improve the reliability of data transmission.

Description of drawings

The drawings that need to be used in the description of the embodiments or the prior art will be introduced below.

FIG. 1 is a schematic structural diagram of a sidelink communication system provided by an embodiment of the present application;

Fig. 2a is a schematic diagram of a transmission resource acquisition method provided by an embodiment of the present application;

FIG. 2b is a schematic diagram of another transmission resource acquisition method provided by the embodiment of the present application;

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

Fig. 4 is a schematic flowchart of another message transmission method provided by the embodiment of the present application;

FIG. 5 is an interactive schematic diagram of a message transmission method provided by an embodiment of the present application;

Fig. 6 is an interactive schematic diagram of another message transmission method provided by the embodiment of the present application;

FIG. 7 is an interactive schematic diagram of another message transmission method provided by the embodiment of the present application;

Fig. 8a is an interactive schematic diagram of another message transmission method provided by the embodiment of the present application;

Fig. 8b is an interactive schematic diagram of another message transmission method provided by the embodiment of the present application;

FIG. 9 is an interactive schematic diagram of another message transmission method provided by the embodiment of the present application;

FIG. 10 is a schematic structural diagram of a terminal provided in an embodiment of the present application;

FIG. 11 is a schematic structural diagram of a network device provided by an embodiment of the present application;

FIG. 12 is a schematic structural diagram of another terminal provided by an embodiment of the present application;

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

Detailed ways

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

It can be understood that the technical solution of the present application may be specifically applied to a sidelink (Sidelink, SL) communication system, where the sidelink communication system includes at least two terminals. That is, the technical solution of the present application can be applied to any device-to-device communication scenario. For example, the sidelink communication system may be a Vehicle to Everything (V2X) communication system or other sidelink communication systems. Optionally, the V2X communication system can be vehicle to vehicle (vehicle to vehicle, V2V), vehicle to person (vehicle topedestrian, V2P), vehicle to network (vehicle to network, V2N), vehicle to infrastructure (vehicle to infrastructure, V2I) ) and other communication systems.

Please refer to FIG. 1 , which is a schematic structural diagram of a sidelink communication system provided by an embodiment of the present application. As shown in FIG. 1, the sidelink communication system includes at least two terminals. Exemplarily, as shown in FIG. 1, the sidelink communication system includes a first terminal and a second terminal, and the first terminal and the second terminal can communicate through the sidelink between the first terminal and the second terminal . Optionally, the sidelink communication system may further include network equipment, or the first terminal and/or the second terminal may communicate with the network equipment. The network device may communicate with a terminal such as the first terminal above through a downlink (Downlink, DL).

The sidelink communication system adopts a sidelink transmission technology based on device-to-device (D2D), which is different from the way communication data is received or sent by network devices such as base stations in traditional cellular systems. The sidelink communication system adopts terminal-to-terminal direct communication, which has higher spectral efficiency and lower transmission delay.

In the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP), D2D is divided into different stages for research. For example, in the long term evolution (Long Term Evolution, abbreviation: LTE), including several stages such as ProSe (Proximity based Service), V2X, wearable device (FeD2D). Among them, in the device-to-device communication in Rel-12/13, the ProSe scenario is studied, which is mainly aimed at public security services; in ProSe, the position of the resource pool in the time domain can be configured, such as the resource pool Discontinuously in the time domain, the terminal can discontinuously send or receive data on the sidelink, thereby achieving the effect of power saving. In Rel-14/15, the V2X system (or it can be called the Internet of Vehicles system) is researched on the scene of vehicle-to-vehicle communication, which is mainly oriented to the business of relatively high-speed mobile vehicle-to-vehicle and vehicle-to-person communication; in V2X, due to The vehicle system has a continuous power supply, so power efficiency is not the main issue, and the main concern is the delay of data transmission, so the system design requires the terminal equipment to perform continuous transmission and reception. In addition, in Rel-14, the FeD2D scenario where wearable devices access the network through mobile phones is studied, mainly for low-speed and low-power access scenarios; in FeD2D, a possible implementation method is that the network A device such as a base station can configure DRX parameters of a remote terminal through a relay terminal. As another example, in the fifth generation of mobile communication (the 5th Generation, 5G) such as new radio/new air interface (New Radio, NR), NR V2X has been studied, and NR V2X has been further expanded to single Broadcast and multicast scenarios, not limited to broadcast scenarios, it can study the application of V2X in these scenarios; in addition, in addition to the HARQ retransmission initiated by the terminal without feedback, NR V2X introduces feedback-based HARQ retransmission , not limited to unicast communication, but also multicast communication and so on.

For sidelink communication, 3GPP defines two modes to obtain transmission resources: the mode of network scheduling resources and the mode of terminal self-selecting resources. For example, in LTE, Mode 3 (Mode 3) is a mode for network scheduling resources, and Mode 4 (Mode 4) is a mode for terminals to independently select resources; for example, in NR, Mode 1 (Mode 1) is It is a mode of scheduling resources for the network. Mode 2 (Mode 2) is a mode in which terminals independently select resources. In the mode of network scheduling resources, the transmission resources of the terminal are allocated by network equipment such as the base station, that is, the network equipment schedules resources for the terminal, and the terminal performs data transmission on the sidelink according to the resources scheduled by the network equipment, as shown in Figure 2a Show. Optionally, the network device may allocate resources for single transmission to the terminal, or allocate resources for semi-static transmission to the terminal, which is not limited in this application. In the mode in which the terminal independently selects resources, the terminal can select a resource in the resource pool for data transmission, and the terminals can perform data transmission based on the resource independently selected by the terminal, as shown in Figure 2b.

For example, the mode of network scheduling resources, for example, the resource acquisition method of NR V2X Mode 1 may include dynamic authorization and configuration authorization. In the dynamic authorization mode, the network can allocate sidelink transmission resources for the terminal through downlink control information (DCI); in the configuration authorization mode, the network can configure sidelink configuration authorization transmission resources for the terminal, when the terminal is configured The sideline configuration authorizes transmission resources. When sideline data arrives, the terminal can use the sideline configuration authorization transmission resources to transmit the sideline data without re-applying for transmission resources from the network. It can be seen that the resource acquisition of configuration authorization This method helps to reduce the delay of sideline transmission. For example, based on the uplink (Uplink, UL) configuration authorization (Configured Grant, CG) mechanism in R16NRV2X, the sidelink configuration authorization (Sidelink CG, SL CG) can be introduced. Optionally, the sidelink configuration authorization transmission resource is a periodic transmission resource, and the way of configuring the authorization can be used for periodic sidelink data transmission, and can also be used for aperiodic sidelink data transmission.

In some embodiments, the network device can perform information configuration for the terminal, such as parameter configuration and/or resource configuration, and the like. For example, the above-mentioned first terminal may send a sidelink transmission resource request to the network device, and the network device may perform sidelink resource allocation for the first terminal based on the sidelink transmission resource request. For example, when the terminal has side data to send, the terminal can send a resource request to the network device, such as sending a scheduling request (Scheduling Request, SR) and a buffer status report (Buffer Status Report, BSR), and the network device can The BSR allocates sidelink transmission resources for it, and then the first terminal can perform sidelink communication based on the sidelink transmission resources allocated by the network device, such as sending data to the above-mentioned second terminal. As another example, the network device may configure parameters for indicating the triggering conditions of PC5 RLF for the first terminal, so that the first terminal may detect PC5 RLF based on the configured parameters when performing sidelink communication with the second terminal.

However, in a sidelink communication system, when the network configures sidelink parameters or resources for a terminal, there are often situations where the sidelink parameter or resource configuration is unreasonable. In this application, based on the idea of Mobility Robustness Optimization in the network, the terminal can help the network side to configure parameters by reporting to the network information reflecting whether the sidelink parameters or resource configuration is reasonable or resource configuration. For example, the terminal can send the cause information to the network device, including the cause information of PC5 RLF and/or the cause information indicating the triggering of resource configuration, so as to provide reference for the network device to configure parameters or resources, thereby improving the information configuration. Reliability, thereby helping to improve the reliability of data transmission.

It can be understood that the sidelink communication system may also be called a sidelink system, a sidelink system, a device-to-device communication system or other names, which are not limited in this application.

In this application, a network device can be an entity on the network side that is used to send or receive information, such as a base station, which can be used to communicate with one or more terminals, and can also be used to communicate with one or more The base station with some terminal functions performs communication (such as the communication between the macro base station and the micro base station). The base station can be an evolved base station (Evolutional Node B, eNB) in a Long Term Evolution (LTE) system, or a base station gNB in a 5G system or an NR system, etc., which are not listed here. Alternatively, the network device can also be a transmission point (transmission point, TP), an access point (Access Point, AP), a sending and receiving point (transmission and receiver point, TRP), a relay device, and a central unit (Central Unit, CU) , or other network devices with base station functions, etc., which are not limited in this application.

In this application, a terminal may be a device with a communication function, such as a vehicle-mounted device, a wearable device, a handheld device (such as a smart phone), and the like. The terminal can also be called other names, such as user equipment (User Equipment, UE), subscriber unit, mobile station (mobile station), mobile unit (mobile unit), terminal equipment, vehicle-mounted terminal, etc., which are not limited in this application.

It can be understood that the communication system shown in FIG. 1 is only an example and does not constitute a limitation to this application. Those skilled in the art know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided by this application The same applies to similar technical issues.

Please refer to FIG. 3 . FIG. 3 is a schematic flowchart of a message transmission method provided by an embodiment of the present application. The method in this embodiment can be applied to the above-mentioned sidelink communication system, where the sidelink communication system includes the first terminal and the second terminal, and can be specifically applied to the above-mentioned first terminal. As shown in Figure 3, the method may include the following steps 301-302:

301. The first terminal determines a first message, where the first message includes: report cause information, where the report cause information includes cause information for occurrence of PC5RLF and/or cause information for indicating triggering resource configuration.

Wherein, the first message may carry cause information of PC5 RLF, or, the first message may carry cause information for indicating trigger resource configuration, or, the first message may carry cause information of PC5 RLF and trigger resource information for indicating trigger resource configuration. Configured reason information. Optionally, the resource configuration involved in this application may be for any resource configuration scenario. For example, resource configuration may be a new configuration of resources or a reconfiguration of resources, which is not limited in this application.

It can be understood that the reason information of PC5 RLF occurrence can be used to indicate the specific reason for occurrence or triggering of PC5 RLF, and the reason information of triggering resource configuration can be used to indicate the specific reason of triggering resource configuration.

Optionally, the reason information for PC5 RLF may include any one or more of the following:

1) The first terminal reaches the maximum number of retransmissions, for example, the first terminal reaches the maximum number of retransmissions indicated by a radio link control (Radio Link Control, RLC) entity. That is, according to the indication from the sidelink RLC entity, the maximum number of retransmissions for a certain target terminal, such as the first terminal, has been reached.

2) The first timer of the first terminal times out. For example, the first timer may be T400, and the cause of PC5 RLF may be that T400 of a certain target terminal such as the first terminal expires.

3) The first terminal reaches the maximum number of consecutive Hybrid Automatic Repeat reQuest (HARQ) Discontinuous Transmission (DTX), such as reaching the maximum continuous transmission indicated by the Medium Access Control (MAC) entity HARQ DTX times.

4) The packet data convergence protocol (Packet Data Convergence Protocol, PDCP) entity integrity check fails, for example, according to the integrity check of a target terminal such as the SL-SRB2 or SL-SRB3 of the first terminal according to the sidelink PDCP entity Failure indication.

Optionally, the reason information used to indicate the triggering of resource configuration may include any one or more of the following: remaining unused resource information, transmission failure information. For example, the remaining unused resource information may include any one or more of the following: indication information for indicating that there is an event of remaining unused resources, quantity information of remaining unused resources, the first terminal is in Discontinuous Reception (Discontinuous Reception, Time information of DRX) inactive state and/or DRX active state, information of configuration resources in DRX inactive state, etc. The transmission failure information may include any one or more of the following: indication information for indicating that there is a transmission failure event, the number of transmission failures, and the like.

Further optionally, the first message may also include any one or more of the following: link information of the sidelink between the first terminal and the second terminal, channel information of the resource pool used by the first terminal Busy rate (channel busy ratio, CBR) information, first time information, first location information, and identification of the second terminal. It can be understood that there may be multiple second terminals in the sidelink communication system, that is, the first terminal may communicate with multiple second terminals, and the link information may include the first terminal and each second terminal. The link information of the sidelink between the terminals, the identifier of the second terminal may include identifiers of each second terminal.

Wherein, the link information of the sidelink may include any one or more of the following: link quality information such as reference signal received power, and parameters used to indicate data transmission conditions such as data packet transmission information. For example, the link quality information may include Sidelink Reference Signal Received Power (Sidelink Reference Signal Received Power, SL-RSRP), Sidelink Discovery Reference Signal Received Power (Sidelink Discovery Reference Signal Received Power, SD-RSRP) one or more of the . For another example, the data packet transmission information may include the average number of data packet transmissions (for example, a single success means that the average number of data packet transmissions is 1 time, and a retransmission is 2 times), the number of data packet transmissions per unit time, and other information. one or more of . Optionally, the link information may be obtained through measurement by the first terminal, or obtained through other methods, which is not limited in this application.

The first time information may include time information when the first terminal performs information measurement and/or data transmission, and/or the first location information may include location information when the first terminal performs information measurement and/or data transmission. Optionally, the information measurement may include the above-mentioned measurement of information such as link information and CBR information. For example, the first time information may include one or more of time stamp information of link information measurement and time stamp information of data transmission between the first terminal and the second terminal. For another example, the first location information may include one or more of location information of link information measurement and location information when the first terminal performs data transmission.

302. The first terminal sends the first message to the network device.

After determining the first message, the first terminal may report the first message to the network, for example, send the first message to a network device. The first terminal may report to the network device immediately after determining the first message, or report to the network device after a delay, which is not limited in this application.

In a possible implementation manner, the first terminal may send the first message to the network device when the PC5 RLF occurs. In this manner, the reported cause information carried in the first message may include the cause information of the occurrence of PC5 RLF. Optionally, the first message may also carry information indicating that there is a PC5 RLF event.

It can be understood that the first terminal may immediately send the first message to the network device when PC5 RLF occurs or is triggered, or send the first message when the first condition is met, which is not limited in this application. Optionally, the first condition may be one or more of conditions such as the first terminal receiving a network request and entering a connected state. For example, the first terminal may record relevant information when PC5 RLF occurs, and send the recorded relevant information to the network at a specific time. The relevant information may be one or more of the above information such as cause information, link information, resource pool information, first time information, first location information, and the identifier of the second terminal.

For example, the cause information of the occurrence of PC5 RLF indicates that the first terminal reaches the maximum number of retransmissions indicated by the RLC entity; for another example, the occurrence of the cause information of the PC5 RLF indicates that the first timer of the first terminal is overtime; for another example, the occurrence of the PC5 RLF The cause information of the RLF indicates that the first terminal has reached the maximum number of consecutive HARQDTX times indicated by the MAC entity; for another example, the cause information of the occurrence of the PC5 RLF indicates that the integrity check of the PDCP entity fails.

In a possible implementation manner, the first terminal may send a first message to the network device to request resource configuration. In this manner, the reporting cause information included in the first message may include cause information for indicating triggering resource configuration. For example, the first terminal may perform data transmission with the second terminal based on the first resource configuration information, and detect the data transmission situation, and send the first message to the network device based on the data transmission situation, for example, determine that the resource configuration is unreasonable based on the data transmission situation , send the first message to the network device. Optionally, the first resource configuration information may be configured by the network device for the terminal. In this manner, the reason information may include any one or more of the following: remaining unused resource information, transmission failure information.

It can be understood that the first terminal may immediately send the first message to the network device after obtaining the reason information indicating the triggering of resource configuration, or send the first message after the second condition is met. This application does not Do limited. Optionally, the second condition may be one or more of conditions such as the first terminal receiving a network request and entering a connected state. For example, the first terminal may record remaining unused resource information and/or transmission failure information, etc., and send the recorded information to the network when the second condition is met. Wherein, the above-mentioned first condition and the second condition may be the same or different.

Optionally, the first terminal may maintain a remaining unused resource counter and/or a transmission failure counter, and may determine the remaining unused resource information and/or transmission failure information according to the remaining unused resource counter and/or the transmission failure counter; Alternatively, the first terminal may also obtain the remaining unused resource information and/or transmission failure information through other methods, which are not limited in this application.

It can be understood that the above reason information may be indicated by an indicator, for example, the first message carries an indicator corresponding to the cause, and the indicators corresponding to different reasons are different; or, the specific reason may also be directly carried, for example, the first message carries Descriptive information of the specific reason; or, other ways may also be used to indicate the reason for reporting. This application does not limit the reason information for indicating PC5 RLF and/or the method for indicating the cause information for triggering resource configuration.

Optionally, the first message may be radio resource control (Radio Resource Control, RRC) signaling, or may also be medium access control (Medium Access Control, MAC) signaling, such as a media access layer control unit ( MAC Control Element, MAC CE) message, or other messages, which are not limited in this application.

In a possible implementation manner, the first terminal may also report Quality of Service (QoS) information to the network, such as carrying the QoS information in the first message and sending it to the network device, so that the network device can Information to adjust QoS related configurations. Optionally, the QoS information may include any one or more of the following: packet delay estimation (Packet Delay Budget, PDB) information, QoS priority, reliability information, and the like.

In the embodiment of this application, the idea of self-organizing network (Self-Organizing Network, SON) can be used for sidelink configuration, and the terminal reports to the network the cause information of some problems in the sidelink transmission process, For example, the specific reason for PC5 RLF and/or the specific reason for triggering resource configuration can be used to indicate the specific reason for triggering resource configuration, which can help the network adjust sidelink parameters and/or resource configuration, which helps to solve the problem that the network cannot perceive the sidelink The problem of unreasonable configuration due to the transmission status on the network, which in turn helps to improve the reliability of data transmission.

Please refer to FIG. 4 . FIG. 4 is a schematic flowchart of another message transmission method provided by an embodiment of the present application. The method in this embodiment can be applied to the above-mentioned network devices. As shown in Figure 4, the method may include the following steps 401-402:

401. The network device receives a first message from the first terminal, where the first message includes: report cause information, where the report cause information includes cause information for PC5 RLF occurrence and/or cause information for indicating triggering resource configuration.

Optionally, the reason information for PC5 RLF may include any one or more of the following: the first terminal reaches the maximum number of retransmissions indicated by the RLC entity, the first timer of the first terminal expires, and the first terminal reaches the MAC entity indication The maximum number of consecutive HARQ DTX times, PDCP entity integrity check fails. The reason information used to indicate the triggering of resource configuration may include any one or more of the following: remaining unused resource information, transmission failure information.

Optionally, the first message may also include any one or more of the following: link information of the sidelink link between the first terminal and the second terminal, CBR information of the resource pool used by the first terminal, The first time information, the first location information, and the identification of the second terminal.

For the description of the first message and the information it carries, reference may be made to the relevant description of the foregoing embodiment for details, and details are not repeated here.

402. The network device performs information configuration according to the first message.

Wherein, the information configuration may include parameter configuration, such as configuration of PC5 configuration parameters, and may also include resource configuration, such as resource reconfiguration, etc., which are not limited in this application.

For example, when the first message carries information about the cause of PC5 RLF, the network device can determine the PC5 configuration parameters based on the first message. Further, the network device may send the PC5 configuration parameters to the first terminal.

For another example, when the first message carries cause information for indicating triggering resource configuration, the network device may determine resource configuration information based on the first message. Further, the network device may send the resource configuration information to the first terminal. For example, the network device may send the first resource configuration information to the first terminal, and after receiving the first message carrying the cause information indicating triggering resource reconfiguration, determine the second resource configuration information according to the first message, and may Send the second resource configuration information to the first terminal.

In this embodiment of the present application, when the network device receives the first message from the first terminal carrying the cause information of PC5 RLF and/or the cause information indicating the triggering of resource configuration, according to the first message Perform information configuration, such as determining PC5 configuration parameters or performing resource configuration, etc., so that sidelink parameters and/or resource configuration can be adjusted based on the specific cause of the problem in the sidelink transmission process reported by the terminal, This helps to solve the problem of unreasonable configuration due to the inability of the network to perceive the transmission status on the sidelink, thereby helping to improve the reliability of data transmission.

Please refer to FIG. 5 . FIG. 5 is an interactive schematic diagram of a message transmission method provided by an embodiment of the present application. The method in this embodiment may be applied to the above-mentioned sidelink communication system, where the sidelink communication system includes a first terminal and a second terminal. This embodiment describes the parameter configuration in the PC5 RLF scenario. As shown in Figure 5, the method may include the following steps 501-504:

501. The first terminal sends a first message to the network device, where the first message includes cause information of PC5 RLF occurrence.

In a possible implementation, the first terminal may send the first message carrying the cause information of the PC5 RLF to the network device when the PC5 RLF occurs. The cause information of the PC5 RLF is used to indicate the specific reason for the occurrence or triggering of the PC5 RLF.

For example, the cause information of PC5 RLF can be used to indicate any one or more of the following reasons: the first terminal reaches the maximum number of retransmissions indicated by the RLC entity, the first timer of the first terminal expires, and the first terminal reaches the maximum number of retransmissions indicated by the MAC entity. The maximum number of consecutive HARQ DTX times, PDCP entity integrity check fails.

Optionally, the first terminal is in a connected state. Further optionally, the first message may be sidelink information such as sidelinkUEInformation, for example, the sl-FailureList IE in the information may be used to indicate the cause information of the occurrence of PC5 RLF.

502. The network device determines configuration parameters of PC5 according to the first message.

The network device may receive the first message from the first terminal, and may perform information configuration based on the first message, for example, determine PC5 configuration parameters based on the occurrence indicated by the first message or the specific reason for triggering the PC5 RLF. For example, the network device may modify the originally configured PC5 configuration parameters, such as increasing or decreasing the value of the original PC5 configuration parameters.

Optionally, the PC5 configuration parameter may be used to indicate the adjusted PC5 configuration parameter, or may be used to indicate the adjusted value of the PC5 configuration parameter, which is not limited in this application.

503. The network device sends PC5 configuration parameters to the first terminal.

504. The first terminal detects PC5 RLF according to the PC5 configuration parameter.

After the network device determines the PC5 configuration parameter, it can send the PC5 configuration parameter to the first terminal, and the first terminal can receive the PC5 configuration parameter from the network device. Optionally, the first terminal may also detect PC5 RLF according to the PC5 configuration parameter, that is, determine whether PC5 RLF occurs based on the PC5 configuration parameter.

In the embodiment of the present application, the first terminal can indicate the specific reason of PC5 RLF to the network device, so that the network device can determine the PC5 configuration parameters based on the specific reason of PC5 RLF, which helps to improve the PC5 configuration parameter setting. Rationality improves the reliability of PC5 RLF detection, thereby improving the reliability of data transmission.

Please refer to FIG. 6 in conjunction with FIG. 5 . FIG. 6 is an interactive schematic diagram of another message transmission method provided by an embodiment of the present application. In this embodiment, taking the terminal as a UE and UE1 reporting the cause information of PC5 RLF to the network (NW) as an example, the information configuration in the PC5 RLF scenario is exemplarily described. As shown in Figure 6, the method may include the following steps 601-604:

601. When PC5 RLF occurs, UE1 sends a first message to the NW, where the first message includes cause information of PC5 RLF occurrence.

Wherein, the first message may be used to help the network adjust configuration parameters of PC5. Optionally, PC5 configuration parameters may include any one or more of the following: first timer information such as T400, the maximum number of retransmissions indicated by RLC such as sl-maxRetxThreshold, and the maximum number of consecutive DTX times on the sidelink such as sl-MaxNumConsecutiveDTX .

For example, in this embodiment, the first message may include: the L2ID of all counterpart UEs such as UE2; the reason for PC5 RLF such as RLF_Cause; the link quality measurement value between UE1 and the counterpart UE such as UE2 (such as SL-RSRP and/or SD-RSRP); parameters reflecting data transmission conditions, such as data packet transmission information; resource pool CBR measurement value; time stamp information for performing measurement/data transmission; location-related information for performing measurement/data transmission. Optionally, the RLF_Cause may include any one or more of the following: MAC_DTX, RLC_Retx_max, PDCP_Intigrity, and ConfigFailure.

For example, MAC_DTX can be used to indicate: UE1 has reached the maximum number of consecutive HARQ DTX indicated by the MAC entity; RLC_Retx_max can be used to indicate: UE1 has reached the maximum number of retransmissions indicated by the sidelink RLC entity; PDCP_Intigrity can be used to indicate: sidelink The link PDCP entity indicates that the integrity check of SL-SRB2 or SL-SRB3 of UE1 fails; ConfigFailure can be used to indicate: the first timer such as T400 for UE1 is timed out. Optionally, the first message may also include one or more of the maximum number of consecutive HARQ DTXs indicated by the MAC entity, the maximum number of retransmissions indicated by the RLC entity, and the timing duration of the first timer such as T400.

Optionally, the first message may be RRC signaling, or MAC signaling such as MAC CE. For example, in this embodiment, the first message may be a BSR, or the first message may be carried in the BSR.

602. The NW determines PC5 configuration parameters according to the first message.

The NW can receive the first message. Optionally, the NW can comprehensively evaluate the cause of the RLF according to the received first message, and then determine the configuration parameters of the PC5 based on the cause. This can avoid the problem of wrongly triggering PLF caused by unreasonable configuration of PC5 configuration parameters. For example, it can help to avoid the occurrence of wrongly triggering RLF due to resource and priority issues, etc., when there is no problem with the link quality itself.

For example, if it is determined according to the first message that the link quality is good (for example, the link quality is greater than the quality threshold) and/or the resource pool CBR indicates that the congestion level is not high (for example, the CBR is lower than the busy rate threshold), and the reason for the occurrence of PC5 RLF is MAC_DTX, the possible reason is that the maximum number of consecutive HARQ DTX times, such as the value of sl-MaxNumConsecutiveDTX, is set too low. Therefore, the NW can increase the value corresponding to the maximum number of consecutive HARQ DTX times, for example, the value of sl-MaxNumConsecutiveDTX can be increased according to the preset increment. Optionally, in this scenario, the PC5 configuration parameter can be used to indicate the adjusted maximum number of consecutive HARQ DTX times such as the value of sl-MaxNumConsecutiveDTX, or can be used to indicate the adjusted value such as the preset increase.

As another example, if the link quality is good (for example, the link quality is greater than the quality threshold) and the first message indicates that PC5 RLF occurs because T400 times out, it may be that the setting time of T400 is relatively short, so the NW can increase the timing of T400 Duration, such as increasing the timing duration of T400 according to the preset duration. Optionally, in this scenario, the PC5 configuration parameter may be used to indicate information about the second timer, for example, indicate the adjusted timing duration of T400, or may be used to indicate an adjusted value such as the preset duration.

603. The NW sends PC5 configuration parameters to UE1.

After the NW determines the configuration parameters of PC5 based on the first message, it may send the configuration parameters of PC5 to UE1. Optionally, the PC5 configuration parameter may be carried in a reconfiguration message.

604. UE1 detects PC5 RLF based on the PC5 configuration parameter.

UE1 can receive the PC5 configuration parameters from the NW, and then use the PC5 configuration parameters, that is, the new configuration, for sidelink transmission, for example, use the PC5 configuration parameters for PC5 RLF determination.

In the embodiment of this application, UE1 can indicate the specific reason of PC5 RLF to NW when PC5 RLF is triggered, and then NW can determine PC5 configuration parameters based on the specific reason of PC5 RLF, such as adjusting the timer and adjusting the maximum continuous DTX times, etc., UE1 can make RLF judgment based on the adjusted PC5 configuration parameters, which helps to improve the rationality of PC5 configuration parameter settings, thereby improving the reliability of PC5 RLF judgment and data transmission reliability.

Please refer to FIG. 7 . FIG. 7 is an interactive schematic diagram of another message transmission method provided by the embodiment of the present application. The method in this embodiment can be applied to the above-mentioned sidelink communication system. This embodiment describes resource configuration in a scenario where a terminal reports cause information used to indicate triggering resource configuration. As shown in Figure 7, the method may include the following steps 701-708:

701. The network device sends first resource configuration information to a first terminal.

702. The first terminal sets the remaining unused resource counter and/or the transmission failure counter to zero.

It can be understood that the first terminal may only maintain the remaining unused resource counter, or may only maintain the transmission failure counter, or may maintain the remaining unused resource counter and the transmission failure counter at the same time, which is not limited in this application. Optionally, there may be one or more remaining unused resource counters maintained by the first terminal, and one or more transmission failure counters maintained.

Optionally, the configured resource indicated by the first resource configuration information may be a periodic resource or an aperiodic resource, which is not limited in this application.

703. The first terminal performs data transmission with the second terminal according to the first resource configuration information.

In this embodiment, the network may schedule sidelink resources for the terminal, for example, the network device may configure first resource configuration information for the first terminal, and send the first resource configuration information to the first terminal. The first terminal may receive the network configuration resource scheduling, and then may perform sidelink transmission according to the network configuration resource scheduling such as the first resource configuration information. In addition, after receiving the first resource configuration information, the first terminal may also reset the maintained remaining unused resource counter and/or transmission failure counter to zero, so as to correct the remaining unused resource information based on the sidelink transmission situation , transmission failure information and other information for statistics.

704. The first terminal determines a first message, where the first message includes remaining unused resource information and transmission failure information.

705. The first terminal sends the first message to the network device.

The first terminal may control the counting of the remaining unused resource counter and/or the transmission failure counter based on the data transmission status obtained through data transmission based on the first resource configuration information, and then determine whether the resource configuration is reasonable based on the counter counting information. When it is determined that the resource configuration is unreasonable, the first terminal may send a first message to the network device, where the first message carries cause information for indicating that the resource configuration is triggered, to indicate a specific reason for triggering the resource configuration, such as the existence of remaining resources, There are transmission failures and so on.

For example, the first terminal may send the first message to the network device when the count of the remaining unused resource counter reaches the first threshold. The first message may carry remaining unused resource information. Optionally, when controlling the remaining unused resource counter based on the data transmission obtained through data transmission based on the first resource configuration information, the remaining unused resource may be controlled when the first terminal receives the ACK message returned by the second terminal Incrementing the counter by one; as another example, when the configured resource indicated by the first resource configuration information is in the DRX inactive state, control the remaining unused resource counter to be increased by one. Further optionally, when receiving the ACK message returned by the second terminal, the remaining unused resources corresponding to the first resource configuration information may also be discarded, and/or, when the configuration resources indicated by the first resource configuration information are in DRX inactive state, the configuration resource is discarded.

Wherein, the remaining unused resource information may include any one or more of the following: indication information for indicating that there is an event of remaining unused resources, the first threshold, quantity information of remaining unused resources, the first terminal being in DRX inactive time information in the DRX active state and/or in the DRX active state, information about configuration resources in the DRX inactive state, and so on. For example, the indication information may be bit information, for example, 1 indicates that there is an event of unused remaining resources, so as to indicate that there are too many scheduled resources or unreasonable resource scheduling.

In another example, the first terminal may send the first message to the network device when the count of the transmission failure counter reaches the second threshold. The first message may carry transmission failure information. When the data transmission situation obtained by performing data transmission based on the first resource configuration information controls the counting of the transmission failure counter, the NACK message returned by the second terminal may be received, and the configuration resources indicated by the first resource configuration information are all used , control the input failure counter to add one.

Optionally, the transmission failure information may include any one or more of the following: indication information for indicating that a transmission failure event exists, the second threshold, and the number of transmission failures. For example, the indication information may be bit information, such as indicating that there is a transmission failure event through 0, to indicate a transmission failure situation, for example, it may be that the scheduled resources are too few.

Further optionally, the first message may also include any one or more of the following: link information of the sidelink between the first terminal and the second terminal, CBR of the resource pool used by the first terminal information, the first time information, the first location information, the identification of the second terminal, and so on. For details, reference may be made to related descriptions of the foregoing embodiments, and details are not repeated here.

Wherein, the first threshold and/or the second threshold may be configured for the network, or may also be pre-configured, or may also be configured for the terminal. For example, the first threshold may be configured by other terminals except the first terminal and/or the first terminal. The present application makes no limitation on the configuration manner of the first threshold and/or the second threshold.

706. The network device determines second resource configuration information according to the first message.

707. The network device sends the second resource configuration information to the first terminal.

The network device may receive the first message from the first terminal, and may perform resource configuration based on the first message, for example, determine second resource configuration information. For example, when the first message carries remaining unused resource information, it may indicate that there are remaining unused resources, and there may be more scheduled resources or unreliable scheduled resources. If it is determined according to the first message that there are many retransmission resources corresponding to the first resource configuration information, resulting in waste of resources, the network device can reduce the scheduled resources, such as reducing retransmission resources, to obtain the second resource configuration information; if according to the first message If it is determined that the configuration corresponding to the first resource configuration information is unreliable, for example, some or all of the configured resources are in the DRX inactive state, the network device can reschedule other resources to obtain the second resource configuration information. As another example, when the first message carries transmission failure information, it may indicate that there is a transmission failure, which may be due to fewer resources scheduled. For example, the first resource configuration information corresponds to fewer retransmission resources, and the network device can increase the number of scheduled resources. Resources, such as adding retransmission resources, to obtain second resource configuration information. After determining the second resource configuration information, the network device may send the second resource configuration information to the first terminal.

Optionally, the increased or decreased resource quantity may be associated with remaining unused resource information, such as the remaining unused resource quantity, or may be associated with transmission failure information, such as the number of transmission failures. For example, the greater the number of remaining unused resources, the greater the number of reduced resources; and for example, the greater the number of transmission failures, the greater the number of increased resources, etc., which are not listed here.

708. The first terminal may perform data transmission with the second terminal according to the second resource configuration information.

The first terminal may receive second resource configuration information from the network device. Optionally, after receiving the second resource configuration information, the first terminal may also perform data transmission with the second terminal according to the second resource configuration information.

It can be understood that the configured resources indicated by the first resource configuration information and the second resource configuration information are side link resources.

In the embodiment of the application, the first terminal may indicate the specific reason for triggering resource configuration to the network device, such as carrying remaining unused resource information and/or transmission failure information in the first message, so that the network device can trigger resource configuration based on the Resource allocation is performed for specific reasons, which helps to improve the reliability of resource allocation, thereby improving the reliability of data transmission.

Please refer to FIG. 8a in conjunction with FIG. 7 . FIG. 8a is an interactive schematic diagram of another message transmission method provided by an embodiment of the present application. In this embodiment, taking the terminal as a UE, UE1 reports resource configuration information to the network (NW) as remaining unused resource information as an example, and reports the resource configuration to the terminal to indicate the specific reason for triggering resource configuration. Give an exemplary description. As shown in Figure 8a, the method may include the following steps 8101-8109:

8101. The NW sends first resource configuration information to UE1.

8102. UE1 sets the remaining unused resource counter to zero.

8103. UE1 sends data to UE2 according to the first resource configuration information.

UE1 may receive first resource configuration information, that is, receive network configuration resource scheduling, and may transmit sidelink data according to the configured resources indicated by the first resource configuration information. Further, UE1 maintains a remaining unused resource counter, and may set the remaining unused resource counter to zero after receiving the first resource configuration information.

In this embodiment, it is assumed that the configuration resources indicated by the first resource configuration information include 3 resources, of which 1 is a new transmission resource and 2 are retransmission resources. UE1 can perform sidelink communication with UE2 based on these configured resources.

8104. UE2 returns a response message to UE1. For example, the response message is an ACK message or a NACK message.

UE1 may send data to UE2 based on the configured resources indicated by the first resource configuration information. UE2 can receive the data sent by UE1, and return a response message to UE1 according to the reception situation. If the reception is successful, UE2 may feed back an ACK message to UE1, and if the reception fails, UE2 may feed back a NACK message to UE1.

8105. When UE1 receives the ACK message returned by UE2, discard the remaining unused resources corresponding to the first resource configuration information, and control the remaining unused resource counter to add one.

If the ACK is received, UE1 may discard the remaining retransmission resources for the MAC PDU, that is, discard the remaining resources of the configured resources indicated by the first resource configuration information, and add one to the remaining unused resource counter. For example, if ACK is received for 1 newly transmitted resource, the remaining 2 retransmitted resources can be discarded, and the remaining unused resource counter is incremented by one; If an ACK is received, the remaining 1 retransmission resource can be discarded, and the remaining unused resource counter is incremented by one. Optionally, the number of remaining unused resources may also be recorded, that is, the number of discarded remaining unused resources such as retransmission resources.

8106. When the count of the remaining unused resources counter reaches a corresponding counting threshold, UE1 sends the first message to the network device, where the first message includes information about remaining unused resources.

That is to say, UE1 may send a first message to the network when the remaining unused resource counter reaches a corresponding counting threshold, such as a first threshold, such as a set threshold N, such as sending a retune resource request report such as a BSR, to indicate There are cases where remaining resources are not used. Optionally, the remaining unused resource information may include any one or more of the following: indication information indicating that there is an event of remaining unused resources, the counting threshold such as threshold N, the number of remaining unused resources and other information. Further optionally, the first message may also include sidelink link information between UE1 and each other UE, CBR information of the resource pool used by UE1, time information for performing measurement/data transmission by UE1, UE1 One or more items of location information for performing measurement/data transmission, identification lists of all counterpart UEs, and the like.

For example, the first message may include the following content: L2ID of UE2; Cause value: used to indicate the reason for triggering resource reconfiguration, such as remaining unused resource counter=N; link quality measurement value between UE1 and UE2 (such as SL -RSRP and/or SD-RSRP) list; CBR measurement value of the resource pool used; time stamp information for performing measurement/data transmission; location-related information for performing measurement/data transmission; parameters reflecting data transmission conditions such as data packet transmission information.

8107. The NW determines the second resource configuration information according to the first message.

8108. The NW sends the second resource configuration information to the UE1.

The network may reschedule sidelink resources for UE1 according to the content reported by UE1, that is, determine the second resource configuration information, and may send the second resource configuration information to UE1.

When the NW receives the remaining unused resource information, it indicates that there are remaining unused resources in the configuration resources of UE1, and there may be more scheduled resources. In this way, resource scheduling can be re-scheduled, such as reducing retransmission resources, which helps to avoid resource waste.

For example, assuming that the first message includes a counting threshold such as the threshold N, or indicates that the number of remaining unused resources reaches the corresponding counting threshold, it can indicate that the retransmission resources corresponding to the first resource configuration information are more, resulting in waste of resources, then NW can Reduce scheduled resources, such as reducing retransmission resources, to obtain second resource configuration information.

For another example, assuming that the first message includes the number of remaining unused resources, indicating that the first resource configuration information corresponds to more retransmission resources, the NW may reduce scheduled resources, such as reducing retransmission resources, to obtain the second resource configuration information. Optionally, the NW may determine the reduced number of scheduled resources according to the number of remaining unused resources. For example, the more remaining unused resources, the more scheduling resources will be reduced; and if the number of remaining unused resources is greater than or equal to the third threshold, reduce the first number of retransmission resources, and when the number of remaining unused resources is less than the third threshold, The second number of retransmission resources is reduced, and the first number is greater than the second number.

8109. UE1 performs data transmission with UE2 according to the second resource configuration information.

UE1 may receive second resource configuration information from the network device, and then may perform sidelink communication with UE2 according to configured resources indicated by the second resource configuration information.

In the embodiment of the application, UE1 can maintain the count of the remaining unused resource counter based on the response message from the peer UE, and send the first message carrying the remaining unused resource information to the NW when the corresponding threshold is reached, to indicate the triggering of resource configuration. The specific reason is that the NW can perform resource allocation based on the remaining unused resource information, which helps to avoid resource waste, improve the reliability of resource allocation, and further improve the reliability of data transmission.

Please refer to FIG. 8b in combination with FIG. 7 . FIG. 8b is an interactive schematic diagram of another message transmission method provided by the embodiment of the present application. In this embodiment, taking the terminal as a UE, UE1 reports resource configuration information to the network (NW) as remaining unused resource information as an example, and reports the resource configuration to the terminal to indicate the specific reason for triggering resource configuration. Give an exemplary description. As shown in Figure 8b, the method may include the following steps 8201-8207:

8201. The NW sends first resource configuration information to UE1.

8202. UE1 sets the remaining unused resource counter to zero.

8203. UE1 sends data to UE2 according to the first resource configuration information.

8204. When the configured resource indicated by the first resource configuration information is in the DRX inactive state, discard the configured resource, and control the remaining unused resource counter to add one.

UE1 may receive first resource configuration information, that is, receive network configuration resource scheduling, and may transmit sidelink data according to the configured resources indicated by the first resource configuration information. Further, UE1 may maintain a remaining unused resource counter, and may set the remaining unused resource counter to zero after receiving the first resource configuration information.

Further, UE1 may determine the state of the configuration resource scheduled by the first resource configuration information. If a certain configuration resource is in the DRX inactive state, that is, UE1 is in the DRX inactive state at the transmission time of the configuration resource, the configuration resource may be discarded, and the remaining Increment the resource counter by one. That is, if no target address is in the DRX active state at the time domain position of the scheduled resource, discard the remaining resources for the MAC PDU, and add one to the remaining unused resource counter.

Optionally, the configured resources indicated by the first resource configuration information may be periodic resources or aperiodic resources. When counting, it can be counted for a single configuration resource, or it can be counted for a cycle of configuration resources, which is not limited in this application. In this embodiment, it is assumed that the configuration resources indicated by the first resource configuration information include 3 resources, of which 1 is a new transmission resource and 2 are retransmission resources. For example, in a possible implementation, counting can be performed for a single configured resource. For example, if the newly transmitted resource is in the DRX inactive state, the newly transmitted resource can be discarded, and the counter is incremented by one; UE1 transmits normally with UE2 on the first retransmitted resource data, the second retransmission resource is also in the DRX inactive state, the second retransmission resource can be discarded, and the counter is incremented by one. As another example, in a possible implementation, it is possible to count the configured resources for a period. For example, if the newly transmitted resource is in the DRX inactive state, the newly transmitted resource can be discarded; UE1 transmits data normally with UE2 on the first retransmitted resource , the second retransmission resource is also in the DRX inactive state, the second retransmission resource can be discarded, and the counter is incremented by one, that is, the counter is incremented by one in this cycle.

8205. When the count of the remaining unused resources counter reaches a corresponding counting threshold, UE1 sends the first message to the network device, where the first message includes information about remaining unused resources.

That is to say, UE1 may send a first message to the network when the remaining unused resource counter reaches a corresponding counting threshold, such as the first threshold or other thresholds, such as the set threshold N, such as sending a resource readjustment request report, to Indicates that there are remaining unused resources. Optionally, the remaining unused resource information may include any one or more of the following: indication information indicating that there is an event of remaining unused resources, the first threshold such as threshold N, the number of remaining unused resources, the first The terminal is in the DRX inactive state and/or the time information of the DRX active state, the configuration resource information in the DRX inactive state, etc. Further optionally, the first message may also include sidelink link information between UE1 and each other UE, CBR information of the resource pool used by UE1, time information for performing measurement/data transmission by UE1, UE1 One or more of information such as location information for performing measurement/data transmission, an identification list of all counterpart UEs, etc., will not be described in detail here.

For example, the first message may include the following content: L2ID of UE2; Cause value: used to indicate the reason for triggering resource reconfiguration, such as remaining unused resource counter=N; link quality measurement value between UE1 and UE2 (such as SL -RSRP and/or SD-RSRP) list; CBR measurement value of the resource pool used; time stamp information for performing measurement/data transmission; location-related information for performing measurement/data transmission; parameters reflecting data transmission conditions such as data packet transmission information. Optionally, the first message may also include any one or more of the following: UE1 is in the DRX inactive state and/or time information of the DRX active state, and information about configuration resources in the DRX inactive state.

8206. The NW determines the second resource configuration information according to the first message.

8207. The NW sends the second resource configuration information to the UE1.

When the NW receives the remaining unused resource information, it indicates that there are remaining unused resources in the configuration resources of UE1, and there may be more scheduled resources or unreliable scheduled resources.

For example, assume that the first message includes information about configuration resources in the DRX inactive state, such as the number of configuration resources in the DRX inactive state. After receiving the first message, the NW can determine that the configuration resource corresponding to the first resource configuration information is unreliable based on the configuration resource information in the DRX inactive state, resulting in waste of resources, and then the network device can reschedule new resources to obtain Second resource configuration information.

For another example, assume that the first message includes time information when UE1 is in the DRX inactive state, and information about configuration resources in the DRX inactive state. After receiving the first message, the NW can determine that the configuration resources corresponding to the first resource configuration information are unreliable based on the information about the configuration resources in the DRX inactive state, and then the network device can reschedule new resources, for example, based on UE1 being in DRX The time information in the inactive state is used to schedule new resources for UE1, and the new resources are not in the DRX inactive state of UE1, so as to obtain the second resource configuration information. Or when subsequently scheduling resources for UE1, resource configuration may be performed based on time information when UE1 is in the DRX inactive state to obtain second resource information. This helps to improve the reliability of scheduled resources.

8208. UE1 performs data transmission with UE2 according to the second resource configuration information.

UE1 may receive second resource configuration information from the network device, and then may perform sidelink communication with UE2 according to the second resource configuration information.

It can be understood that the remaining unused resource counter in this embodiment and the remaining unused resource counter in the above embodiment shown in FIG. 8a may be the same counter or different counters. In some embodiments, if it is the same counter, the remaining unused resource counter can be counted only based on the ACK message returned by the peer UE, or can be counted only based on whether the resource is in the DRX inactive state, or both cases can be counted at the same time , for example, when the sum of the counts of the two cases reaches the first threshold, the first message is reported. Optionally, in some embodiments, different counters can also be used for the two, and each remaining unused resource counter counts and reports its own scenario, for example, the remaining unused resource counter 1 is based on the ACK message returned by the opposite UE Statistics, and report the first message when the corresponding counting threshold is reached; the remaining unused resource counter 2 performs statistics based on whether the resource is in the DRX inactive state, and reports the first message when the corresponding counting threshold is reached, and the corresponding counting thresholds of the two can be the same It can also be different.

In the embodiment of the application, UE1 can maintain the count of the remaining unused resource counter based on whether the configured resource is in the inactive state, and send the first message carrying the information of the remaining unused resource to the NW when the corresponding threshold is reached, to indicate the trigger resource The specific reasons for the configuration enable the NW to perform resource configuration based on the remaining unused resource information, which helps to improve the reliability of resource configuration and thus the reliability of data transmission.

Please refer to FIG. 9 in conjunction with FIG. 7 . FIG. 9 is an interactive schematic diagram of another message transmission method provided by an embodiment of the present application. In this embodiment, taking the terminal as a UE, and UE1 reporting the cause information of resource configuration to the network (NW) as transmission failure information as an example, the resource configuration in the scenario where the terminal reports a specific reason for triggering resource configuration is given as an example. sexual description. As shown in Figure 9, the method may include the following steps 901-909:

901. The NW sends first resource configuration information to UE1.

902. UE1 sets the transmission failure counter to zero.

903. UE1 performs data transmission with UE2 according to the first resource configuration information.

UE1 may receive first resource configuration information, that is, receive network configuration resource scheduling, and may transmit sidelink data according to the configured resources indicated by the first resource configuration information. Further, UE1 maintains a transmission failure counter, and may set the transmission failure counter to zero after receiving the first resource configuration information.

In this embodiment, it is assumed that the configuration resources indicated by the first resource configuration information include three resources, one of which is a new transmission resource and two are retransmission resources, and the configuration resources indicated by the first resource configuration information may be periodic resource. UE1 can perform sidelink communication with UE2 based on these configured resources.

904. UE2 returns a response message to UE1. For example, the response message is an ACK message or a NACK message.

905. When the UE1 receives the NACK message returned by the UE2, and all configured resources indicated by the first resource configuration information are used, control the transmission failure counter to add one.

If UE1 receives the NACK message returned by UE2, and all the resources for the MAC PDU have been used up, the transmission failure counter is incremented by one; that is, if a NACK is received, and the configuration resource indicated by the first resource configuration information is as above 1 Both the new transmission resources and the retransmission resources are used up, and the transmission failure counter is incremented by one.

906. When the count of the transmission failure counter reaches the second threshold, UE1 sends the first message to the network device, where the first message includes transmission failure information.

That is to say, when the transmission failure counter reaches the second threshold, such as the set threshold M, UE1 may send the first message to the network, such as sending a retune resource request report, to indicate that there is a transmission failure. Optionally, the transmission failure information may include any one or more of the following: indication information for indicating that there is a transmission failure event, information such as the second threshold such as a threshold M, and times of transmission failures. Further optionally, the first message may also include sidelink link information between UE1 and each other UE, CBR information of the resource pool used by UE1, time information for performing measurement/data transmission by UE1, UE1 One or more items of location information for performing measurement/data transmission, identification lists of all counterpart UEs, and the like.

For example, the first message may include the following content: L2ID of UE2; Cause value: used to indicate the reason for triggering resource reconfiguration, such as transmission failure counter=M; link quality measurement value between UE1 and UE2 (such as SL-RSRP and/or SD-RSRP) list; the resource pool CBR measurement value used; time stamp information for performing measurement/data transmission; location-related information for performing measurement/data transmission; parameters reflecting data transmission conditions such as data packet transmission information.

907. The NW determines the second resource configuration information according to the first message.

908. The NW sends the second resource configuration information to the UE1.

When the NW receives the transmission failure information, it indicates that there is a transmission failure in the configured resources of UE1, and the scheduled resources may be unreliable or less. For example, if the first message includes the second threshold such as the threshold M and transmission failure event indication information, the NW may increase scheduled resources, such as increase retransmission resources, to obtain the second resource configuration information. Thus, the first message includes the number of transmission failures, and the NW can increase the scheduled resources to obtain the second resource configuration information. Optionally, the NW can determine the scheduled resources in combination with the number of transmission failures. For example, the more times of transmission failures, the more resources are added; for another example, when the number of transmission failures is greater than the failure times threshold, new resources can be scheduled , and can increase scheduling resources, such as increasing retransmission resources.

909. UE1 performs data transmission with UE2 according to the second resource configuration information.

In the embodiment of the application, UE1 can maintain the count of the transmission failure counter based on the response message from the peer UE, and send the first message carrying the transmission failure information to the NW when the corresponding threshold is reached, to indicate the specific reason for triggering resource configuration, so that The NW can configure resources based on the transmission failure information, which helps to avoid waste of resources, improves the reliability of resource allocation, and thus improves the reliability of data transmission.

It can be understood that the thresholds involved in this application may be configured by the network, pre-configured, or configured by the terminal, which is not limited in this application.

It can be understood that the above method embodiments are all illustrations of the message transmission method of the present application, and the descriptions of each embodiment have different emphases. For the parts not described in detail in a certain embodiment, you can refer to the relevant descriptions of other embodiments.

Please refer to FIG. 10 , which is a schematic structural diagram of a terminal provided by an embodiment of the present application. As shown in FIG. 10, the terminal 1000 may include: a processor 1010, a memory 1020, a communication interface 1030, and one or more programs 1021, wherein the one or more programs 1021 are stored in the memory 1020, and configured to be executed by the processor 1010. The terminal is applicable to a sidelink communication system, and the sidelink communication system includes a first terminal and a second terminal. Wherein, the program includes instructions for executing some or all steps of the above message transmission method, such as instructions for some or all steps performed by the first terminal, and the processor 1010 may call the one or more programs to perform the above message transmission Some or all steps of the method. For example, the processor 1010 may call the one or more programs to perform the following steps:

Determine the first message, where the first message includes: report cause information, where the report cause information includes cause information for PC5 wireless link failure RLF and/or cause information for indicating triggering resource configuration;

Call the communication interface 1030 to send the first message to the network device.

In a possible implementation manner, when the processor 1010 executes the sending the first message to the network device, it is specifically used to:

When PC5 RLF occurs, send the first message to network equipment;

In a possible implementation, before the first terminal determines the first message, the processor 1010 is further configured to execute:

When receiving the first resource configuration information sent from the network device, set the remaining unused resource counter and/or the transmission failure counter to zero;

performing data transmission with the second terminal according to the first resource configuration information.

In a possible implementation, the processor 1010 may also be configured to execute:

When receiving the confirmation ACK message returned by the second terminal, discard the remaining unused resources corresponding to the first resource configuration information, and control the remaining unused resource counter to add one.

sending the first message to a network device when the count of the transmission failure counter reaches a second threshold;

Wherein, the cause information includes the transmission failure information.

When the non-acknowledgment NACK message returned by the second terminal is received, and the configuration resources indicated by the first resource configuration information are all used, control the failure counter to add one.

In a possible implementation manner, after the first terminal sends the first message to the network device, the processor 1010 is further configured to execute:

Invoke the communication interface 1030 to receive PC5 configuration parameters from the network device, and detect PC5 RLF according to the PC5 configuration parameters; and/or,

Calling the communication interface 1030 to receive second resource configuration information from the network device, and perform data transmission with the second terminal according to the second resource configuration information.

Please refer to FIG. 11 , which is a schematic structural diagram of a network device provided by an embodiment of the present application. As shown in FIG. 11 , the network device 1100 may include: a processor 1110, a memory 1120, a communication interface 1130, and one or more programs 1121, wherein the one or more programs 1121 are stored in the memory 1120, And configured to be executed by the processor 1110. Wherein, the program includes instructions for executing some or all steps of the above-mentioned message transmission method, such as instructions for some or all steps performed by a network device, and the processor 1110 may call the one or more programs to execute the above-mentioned message transmission method some or all of the steps. For example, the processor 1110 may call the one or more programs to perform the following steps:

Invoking the communication interface 1130 to receive a first message from the first terminal, the first message includes: report cause information, the report cause information includes cause information of PC5 wireless link failure RLF and/or is used to indicate trigger resource configuration reason information;

Perform information configuration according to the first message.

Optionally, the first message further includes any one or more of the following: link information of the sidelink between the first terminal and the second terminal, resource pool used by the first terminal The CBR information of the channel busy rate, the first time information, the first location information, and the identifier of the second terminal.

In a possible implementation, the reported cause information includes the cause information of PC5 RLF; when the processor 1110 executes the information configuration according to the first message, it can be specifically used for:

Determine PC5 configuration parameters according to the first message;

Processor 1110 can also be used to perform:

Invoking the communication interface 1130 to send the PC5 configuration parameters to the first terminal.

In a possible implementation, before the network device receives the first message from the first terminal, the processor 1110 is further configured to execute:

calling the communication interface 1130 to send the first resource configuration information to the first terminal;

When the processor 1110 performs the information configuration according to the first message, it may be specifically used for:

determining second resource configuration information according to the first message;

The processor 1110 can also be used to perform:

Invoking the communication interface 1130 to send the second resource configuration information to the first terminal.

The foregoing mainly introduces the solution of the embodiment of the present application from the perspective of interaction between various network elements. It can be understood that, in order to realize the above functions, the terminals and network devices include corresponding hardware structures and/or software modules for performing various functions. The embodiment of the present application may divide the functional units of the terminal and the network device according to the above method examples. For example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The above-mentioned integrated units can be implemented not only in the form of hardware, but also in the form of software program modules. It should be noted that the division of units in the embodiment of the present application is schematic, and is only a logical function division, and there may be another division manner in actual implementation.

Referring to FIG. 12 , FIG. 12 shows another possible structural diagram of the terminal involved in the foregoing embodiment. Referring to FIG. 12 , the terminal 1200 may include: a processing unit 1201 and a communication unit 1202 . Wherein, these units can perform the corresponding functions of the terminal in the above method example. For example, the processing unit 1201 is configured to control and manage actions of the terminal. The communication unit 1202 may be used to support communication between the terminal and other devices, such as communication with network devices. Optionally, the terminal may further include a storage unit 1203, configured to store program codes and data of network devices.

Wherein, the processing unit 1201 may be a processor or a controller or a software module, such as a central processing unit (Central Processing Unit, CPU), a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit ( Application-Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, a combination of one or more microprocessors, a combination of DSP and a microprocessor, and so on. The communication unit 1202 may be a transceiver, a communication interface, a transceiver circuit, a radio frequency chip, etc., and the storage unit 1203 may be a memory.

When the processing unit 1201 is a processor, the communication unit 1202 is a communication interface, and the storage unit 1203 is a memory, the terminal involved in this embodiment of the present application may be the terminal shown in FIG. 10 .

Optionally, the terminal may implement some or all of the steps performed by the terminal, such as the first terminal, in the methods in the above embodiments shown in FIG. 3 to FIG. 9 through the above units. It should be understood that the embodiments of the present application are device embodiments corresponding to the method embodiments, and the descriptions of the method embodiments are also applicable to the embodiments of the present application, and details are not repeated here.

Referring to FIG. 13 , FIG. 13 shows another possible structural diagram of the network device involved in the foregoing embodiment. Referring to FIG. 13 , the network device 1300 may include: a communication unit 1301 and a processing unit 1302 . Wherein, these units may perform corresponding functions of the network device in the above method example. For example, the processing unit 1302 is configured to control and manage actions of network devices. The communication unit 1301 may be used to support communication between the network device and other devices, for example, communication with a terminal. Optionally, the network device may further include a storage unit 1303, configured to store program codes and data of the network device.

Wherein, the processing unit 1302 may be a processor or a controller or a software module, the communication unit 1301 may be a transceiver, a communication interface, a transceiver circuit, a radio frequency chip, etc., and the storage unit 1303 may be a memory, which will not be described here.

When the processing unit 1302 is a processor, the communication unit 1301 is a communication interface, and the storage unit 1303 is a memory, the network device involved in this embodiment of the present application may be the network device shown in FIG. 11 .

Optionally, the network device may use the above units to implement some or all of the steps performed by the network device in the methods in the embodiments shown in FIGS. 3 to 9 above. It should be understood that the embodiments of the present application are device embodiments corresponding to the method embodiments, and the descriptions of the method embodiments are also applicable to the embodiments of the present application, and details are not repeated here.

The present application also provides a communication system, which includes the above-mentioned terminal and/or network device. Optionally, the system may further include other devices that interact with the foregoing network elements in the solutions provided in the embodiments of the present application. The network device and/or the terminal may execute some or all of the steps in the methods in the above embodiments shown in FIG. 3 to FIG. 9 . For details, reference may be made to relevant descriptions of the above embodiments, and details are not repeated here.

The embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein when the computer program is executed by a processor, the above-mentioned method can be implemented Part or all of the steps described for the terminal or network device in the example.

The embodiment of the present application also provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to enable the computer to perform the method described in the above-mentioned embodiment Part or all of the steps described in the terminal or network device. For example, the computer program product may be a software installation package.

The steps of the methods or algorithms described in connection with the disclosure of this application can be implemented in the form of hardware, or can be implemented in the form of a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read Only Memory, ROM), erasable programmable read-only memory ( Erasable Programmable ROM, EPROM), Electrically Erasable Programmable Read-Only Memory (Electrically EPROM, EEPROM), registers, hard disk, removable hard disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be a component of the processor. The processor and storage medium can be located in the ASIC. In addition, the ASIC may be located in a communication device such as a terminal or a network device. Of course, the processor and the storage medium may also exist in the communication device as discrete components.

It can be understood that the first, second and various numbers mentioned herein are only for convenience of description, and are not used to limit the scope or sequence of the embodiments of the present application. The term "and/or" in this article is used to describe the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which may represent three situations: A exists alone, B exists alone, and A exists simultaneously and B. The character "/" in this article can indicate that the contextual objects are an "or" relationship.

Those skilled in the art should be aware that, in the above one or more examples, the functions described in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center via wired (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (Digital Video Disc, DVD)), or a semiconductor medium (for example, a solid state disk (Solid State Disk, SSD) )wait.

Claims

A message transmission method, characterized in that it is applied to a sidelink communication system, the sidelink communication system includes a first terminal and a second terminal, and the method includes:

The first terminal determines a first message, where the first message includes: report cause information, where the report cause information includes cause information for PC5 wireless link failure RLF and/or cause information for indicating triggering resource configuration;

The first terminal sends the first message to a network device.
The method according to claim 1, wherein the first message further includes any one or more of the following: link information of the sidelink between the first terminal and the second terminal , channel busy rate CBR information of the resource pool used by the first terminal, first time information, first location information, and an identifier of the second terminal.
The method according to claim 2, wherein the link information includes any one or more of the following: reference signal received power (RSRP), data packet transmission information; and/or, the first time information includes the Time information for performing information measurement or data transmission by the first terminal; and/or, the first location information includes location information for performing information measurement or data transmission by the first terminal.
The method according to any one of claims 1-3, wherein the first terminal sending the first message to the network device includes:

When PC5 RLF occurs, the first terminal sends the first message to the network device;

Wherein, the reported reason information includes the reason information of PC5 RLF.
The method according to claim 4, wherein the cause information of the occurrence of PC5 RLF includes any one or more of the following: the first terminal reaches the maximum number of retransmissions indicated by the radio link control RLC entity, and the The first timer of the first terminal expires, the first terminal reaches the maximum number of consecutive hybrid automatic repeat request HARQ discontinuous transmission DTX times indicated by the medium access control MAC entity, and the packet data aggregation protocol PDCP entity integrity check fails .
The method according to any one of claims 1-3, wherein the reported cause information is used to indicate cause information triggering resource configuration, and the cause information includes any one or more of the following: remaining unused resources information, transmission failure information.
The method according to claim 6, wherein the remaining unused resource information includes any one or more of the following: indication information for indicating that there is an event of remaining unused resources, a first threshold, and remaining unused resources , the time information that the first terminal is in the discontinuous reception DRX inactive state or the DRX active state, and the configuration resource information in the DRX inactive state.
The method according to claim 6, wherein the transmission failure information includes any one or more of the following: indication information for indicating that there is a transmission failure event, a second threshold, and the number of transmission failures.
The method according to claim 6, wherein before the first terminal determines the first message, the method further comprises:

When the first terminal receives the first resource configuration information sent from the network device, the first terminal sets the remaining unused resource counter and/or transmission failure counter to zero;

The first terminal performs data transmission with the second terminal according to the first resource configuration information.
The method according to claim 9, wherein the first terminal sending the first message to the network device includes:

When the count of the remaining unused resource counter reaches a first threshold, the first terminal sends the first message to a network device;

Wherein, the reason information includes the remaining unused resource information.
The method according to claim 9 or 10, characterized in that the method further comprises:

When the first terminal receives the confirmation ACK message returned by the second terminal, the first terminal discards the remaining unused resources corresponding to the first resource configuration information, and controls the remaining unused resource counter to add one.
The method according to claim 9 or 10, characterized in that the method further comprises:

When the configured resource indicated by the first resource configuration information is in the DRXinactive state, the first terminal discards the configured resource, and controls the remaining unused resource counter to add one.
The method according to claim 9, wherein the first terminal sending the first message to the network device includes:

When the count of the transmission failure counter reaches a second threshold, the first terminal sends the first message to a network device;

Wherein, the cause information includes the transmission failure information.
The method according to any one of claims 9-13, wherein the method further comprises:

When the first terminal receives the non-acknowledgement NACK message returned by the second terminal, and all configured resources indicated by the first resource configuration information are used, the first terminal controls the failure counter to add one.
The method according to claim 1, wherein after the first terminal sends the first message to the network device, the method further comprises:

The first terminal receives PC5 configuration parameters from the network device, and detects PC5 RLF according to the PC5 configuration parameters; and/or,

The first terminal receives second resource configuration information from the network device, and performs data transmission with the second terminal according to the second resource configuration information.
A message transmission method, characterized in that, comprising:

The network device receives a first message from the first terminal, where the first message includes: report cause information, where the report cause information includes cause information for PC5 wireless link failure RLF and/or is used to indicate a reason for triggering resource configuration information;

The network device performs information configuration according to the first message.
The method according to claim 16, wherein the first message further includes any one or more of the following: link information of the sidelink link between the first terminal and the second terminal, and The channel busy rate CBR information of the resource pool used by the first terminal, the first time information, the first location information, and the identifier of the second terminal.
The method according to claim 17, wherein the link information includes any one or more of the following: reference signal received power (RSRP), data packet transmission information; and/or, the first time information includes the Time information for performing information measurement or data transmission by the first terminal; and/or, the first location information includes location information for performing information measurement or data transmission by the first terminal.
According to the method according to any one of claims 16-18, the cause information of the occurrence of PC5 RLF includes any one or more of the following: the first terminal reaches the maximum number of retransmissions indicated by the radio link control RLC entity, The first timer of the first terminal expires, the first terminal reaches the maximum number of consecutive hybrid automatic repeat request HARQ discontinuous transmission DTX times indicated by the medium access control MAC entity, and the packet data aggregation protocol PDCP entity integrity check fail.
The method according to any one of claims 16-18, wherein the reported cause information is used to indicate cause information triggering resource configuration, and the cause information includes any one or more of the following: remaining unused resources information, transmission failure information.
The method according to claim 20, wherein the remaining unused resource information includes any one or more of the following: indication information for indicating that there is an event of remaining unused resources, a first threshold, the remaining unused resources Using the number of resources, the first terminal is in the discontinuous reception of time information of the DRX inactive state or the DRX active state, and is in the DRX inactive state of configuring resource information.
The method according to claim 20 or 21, wherein the transmission failure information includes any one or more of the following: indication information for indicating that there is a transmission failure event, a second threshold, and the number of transmission failures.
The method according to claim 16, wherein the reported cause information includes the cause information of PC5 RLF; the network equipment carries out information configuration according to the first message, including:

The network device determines PC5 configuration parameters according to the first message;

The method also includes:

The network device sends the PC5 configuration parameters to the first terminal.
The method according to claim 16, wherein before the network device receives the first message from the first terminal, the method further comprises:

The network device sends first resource configuration information to the first terminal;

The network device performs information configuration according to the first message, including:

determining, by the network device, second resource configuration information according to the first message;

The method also includes:

The network device sends the second resource configuration information to the first terminal.
A terminal, characterized in that it is applied to a sidelink communication system, includes: a processing unit and a communication unit;

The processing unit is configured to determine the first message, the first message includes: report cause information, the report cause information includes cause information of PC5 wireless link failure RLF and/or is used to indicate the reason for triggering resource configuration information;

The communication unit is configured to send the first message to a network device.
A network device, characterized in that the network device includes a communication unit and a processing unit;

The communication unit is configured to receive a first message from the first terminal, the first message includes: report cause information, the report cause information includes cause information of PC5 RLF and/or is used to indicate trigger resource configuration cause information;

The processing unit is configured to perform information configuration according to the first message.
A terminal, characterized in that it includes a processor, a memory, a communication interface, and one or more programs, the one or more programs are stored in the memory and configured to be executed by the processor to Realize the method as described in any one of claims 1-15.
A network device, characterized in that it includes a processor, a memory, a communication interface, and one or more programs, the one or more programs are stored in the memory and configured to be executed by the processor, To realize the method as described in any one of claims 16-24.
A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1-15 is implemented.
A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 16-24 is implemented.