CN113727368A - Communication method and device - Google Patents

Communication method and device Download PDF

Info

Publication number
CN113727368A
CN113727368A CN202010724936.4A CN202010724936A CN113727368A CN 113727368 A CN113727368 A CN 113727368A CN 202010724936 A CN202010724936 A CN 202010724936A CN 113727368 A CN113727368 A CN 113727368A
Authority
CN
China
Prior art keywords
terminal device
configuration
information
radio bearer
configuration information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010724936.4A
Other languages
Chinese (zh)
Inventor
姚楚婷
徐海博
才宇
王君
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2021/078791 priority Critical patent/WO2021238318A1/en
Publication of CN113727368A publication Critical patent/CN113727368A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/02Arrangements for optimising operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/18Management of setup rejection or failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/19Connection re-establishment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/27Transitions between radio resource control [RRC] states

Abstract

The application relates to a communication method and device. The first terminal device obtains first configuration information, the first configuration information is used for the first terminal device to configure a first radio bearer, the first radio bearer is a radio bearer between the first terminal device and a second terminal device, and the second terminal device is a data sending end. And the first terminal equipment configures the first radio bearer according to the first configuration information. When the first radio bearer configuration fails, the first terminal device sends first configuration failure information to the network device. The relay terminal equipment does not need to send configuration failure information to the remote terminal equipment, and then the remote terminal equipment forwards the configuration failure information to the network through the relay terminal equipment, so that the forwarding process of the configuration failure information is reduced, and transmission resources are saved.

Description

Communication method and device
Cross Reference to Related Applications
The present application claims priority of chinese patent application entitled "a method of providing auxiliary information and UE" filed by the chinese intellectual property office of china at 25/5/2020, application No. 202010450671.3, the entire contents of which are incorporated herein by reference.
Technical Field
The present application relates to the field of communications technologies, and in particular, to a communication method and apparatus.
Background
In the vehicle to all (V2X) technology of the current New Radio (NR) system, a PC 5-Radio Resource Control (RRC) connection on the Sidelink (SL) is introduced, and two terminal devices can transmit information through the connection. For example, the terminal apparatus 1 as the transmitting end may request the base station serving the terminal apparatus 1 to obtain the configuration information of the SL between the terminal apparatus 1 and the terminal apparatus 2 before information is to be transmitted to the terminal apparatus 2 as the receiving end. The base station configures the terminal device 1 with a transmission configuration on SL and a common (common) configuration for configuring transmission and reception through RRC message of the Uu port. Terminal device 1, after receiving the transmission configuration and the common configuration, transmits the common configuration to terminal device 2 by on a PC5-RRC message, and terminal device 2 generates a reception configuration corresponding to the SL for terminal device 2 according to the common configuration.
Consider a scenario where terminal device 2 accesses the network through terminal device 1, i.e. information between terminal device 2 and the network needs to be relayed through terminal device 1. It is understood that the terminal device 2 is a remote terminal device, the terminal device 1 is a relay terminal device, and the terminal device 1 provides a relay service for the terminal device 2. Then, for the above configuration procedure, if the terminal device 1 fails to generate the reception configuration, since the terminal device 1 is the common configuration obtained from the terminal device 2, the terminal device 1 transmits the information of the failure in configuration to the terminal device 2, and then the terminal device 2 transmits the information of the failure in configuration to the terminal device 1, and the terminal device 1 forwards the information of the failure in configuration to the base station. Therefore, the process causes repeated transmission of information, and wastes transmission resources.
Disclosure of Invention
The embodiment of the application provides a communication method and a communication device, which are used for saving transmission resources.
In a first aspect, a first communication method is provided, the method including: obtaining first configuration information, where the first configuration information is used for a first terminal device to configure a first radio bearer, where the first radio bearer is a radio bearer between the first terminal device and a second terminal device, and the second terminal device is a data sending end; configuring the first radio bearer according to the first configuration information; and when the first radio bearer configuration fails, sending first configuration failure information to network equipment.
The method may be performed by a first communication device, which may be a communication apparatus or a communication device, e.g. a chip, capable of supporting the communication apparatus to implement the functionality required for the method. Illustratively, the first communication device is a terminal device, or a chip provided in the terminal device for implementing a function of the terminal device, or another component for implementing a function of the terminal device. In the following description, the first communication device is taken as an example of a terminal device, for example, a first terminal device.
In this embodiment of the present application, if a configuration failure occurs in a relay terminal device (for example, a terminal device) that provides a relay service for a remote terminal device (for example, a second terminal device), the relay terminal device may send first configuration failure information to a network device, that is, the relay terminal device does not need to send the first configuration failure information to the remote terminal device, and then the remote terminal device forwards the first configuration failure information to the network through the relay terminal device, which reduces a forwarding process of the first configuration failure information, thereby saving transmission resources.
With reference to the first aspect, in a first optional implementation manner of the first aspect, the sending, to the network device, the first configuration failure information includes:
sending an RRC message to a network device, wherein the RRC message comprises a first information element, the first configuration failure information occupies reserved bits in the first information element, and the first information element is used for indicating a failure reason.
The first information element may be an information element already in the RRC message, e.g. the first information element is an information element indicating the cause of the failure. The original information element in the RRC message is used for carrying the first configuration failure information, and no new information element needs to be added in the RRC message, so that the RRC message can be better compatible with the prior art. Or, the first information element may also be an additional information element in the RRC message, and the new information element is used to carry the first configuration failure information, so as to increase the identification degree of the first configuration failure information. As an alternative, the first configuration failure information may occupy reserved bits in the first information element. By this way, the meaning of other bits of the original cell does not need to be changed, and the compatibility with the prior art is facilitated.
With reference to the first aspect or the first optional implementation manner of the first aspect, in a second optional implementation manner of the first aspect, the method further includes:
and sending second configuration failure information to the second terminal equipment, wherein the second configuration failure information is used for indicating that the first terminal equipment fails to configure the first radio bearer.
In addition to sending the first configuration failure information to the network device, the first terminal device may also send the second configuration failure information to the second terminal device because the first configuration information is sent to the first terminal device by the second terminal device. After receiving the second configuration failure information from the first terminal device, the second terminal device can determine that the first terminal device fails to configure the first radio bearer, so that the second terminal device may temporarily communicate with the first terminal device without passing through the first radio bearer.
With reference to the first aspect or the first optional implementation manner of the first aspect or the second optional implementation manner of the first aspect, in a third optional implementation manner of the first aspect, the obtaining the first configuration information includes:
receiving the first configuration information from the second terminal device.
The network device may send the configuration information, for example, the fourth configuration information, to the second terminal device, and the second terminal device sends the first configuration information to the second terminal device, so that the network device is not required to send the configuration information to the first terminal device, which is beneficial to reducing the burden of the network device.
With reference to the third optional implementation manner of the first aspect, in a fourth optional implementation manner of the first aspect, the first configuration information includes a first common configuration, and the first common configuration includes one or more of the following: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Here, the information included in the first common configuration is only an example, and the information included in the first common configuration is not limited in the embodiment of the present application.
With reference to the first aspect or the first optional implementation manner of the first aspect or the second optional implementation manner of the first aspect, in a fifth optional implementation manner of the first aspect, the obtaining the first configuration information includes:
receiving second configuration information from the network device;
receiving first information from the second terminal device, where the first information includes an identifier of a logical channel corresponding to the first radio bearer;
And obtaining the first configuration information according to the second configuration information and the first information.
The network device may send configuration information, for example, second configuration information, to the first terminal device, and the second terminal device may determine information, such as an identifier of a logical channel corresponding to the first radio bearer, so that the first terminal device may obtain the first configuration information by integrating the information. In this way, the second configuration information is from the network device, so that if the second terminal device fails to configure the first radio bearer according to the first configuration information, the second terminal device may send the first configuration failure information to the network device, and the first configuration failure information may be regarded as response information of the second configuration information, which is more consistent with a general procedure.
With reference to the fifth optional implementation manner of the first aspect, in a sixth optional implementation manner of the first aspect, the first information is obtained by the second terminal device according to fourth configuration information from the network device, where the fourth configuration information is used by the second terminal device to configure the first radio bearer.
The network device may send, to the second terminal device, the second configuration information, and may also send, to the second terminal device, fourth configuration information, where the second terminal device may determine, according to the fourth configuration information, information such as an identifier of a logical channel of the first radio bearer. In this way, the network device can configure the first terminal device and the second terminal device, so that the configuration process is more uniform, the terminal device is not required to generate corresponding configuration information, and the requirement on the terminal device is lower.
With reference to the fifth optional implementation manner of the first aspect or the sixth optional implementation manner of the first aspect, in a seventh optional implementation manner of the first aspect, the first information further includes a QFI corresponding to the first radio bearer, and/or a correspondence between an identifier corresponding to the first radio bearer at the Uu port and an identifier corresponding to the PC5 port.
The content included in the first information is not limited in the embodiment of the present application, as long as the first terminal device can configure the first radio bearer according to the first information and the second configuration information.
With reference to the fifth optional implementation manner of the first aspect or the sixth optional implementation manner of the first aspect or the seventh optional implementation manner of the first aspect, in an eighth optional implementation manner of the first aspect, the second configuration information includes a receiving configuration and a second common configuration, where the receiving configuration includes a PDCP reordering timer, and the second common configuration includes one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Here, the information included in the receiving configuration and the second common configuration is only an example, and the information included in the receiving configuration and the second common configuration is not limited in the embodiments of the present application.
With reference to the first aspect, or the first optional implementation manner of the first aspect, or the second optional implementation manner of the first aspect, in a ninth optional implementation manner of the first aspect, before the obtaining the first configuration information, the method further includes:
receiving QoS information from the second terminal device, the QoS information indicating a QoS for a radio bearer requested to be configured between the second terminal device and the first terminal device;
and sending second information to the network equipment, wherein the second information is used for requesting to configure a radio bearer for bidirectional transmission between the second terminal equipment and the first terminal equipment, and the second information comprises the QoS information.
Generally, which terminal device determines that information needs to be sent to the peer, the terminal device may send information for requesting configuration of the first radio bearer to the network device. In this embodiment, the second terminal device should actually be a sender of information, that is, the second terminal device is to send information to the first terminal device. In this embodiment, it may be considered that the first terminal device regards the first terminal device as a sending end of the information by sending the second information to the network device, and then the network device sends the configuration information of the first radio bearer to the first terminal device. In this way, if the first terminal device fails to configure, the first terminal device may send information indicating that the configuration fails to configure to the network device, so that the execution of the whole process is more in line with the execution habit of the device. Since the second terminal device is the actual sender of the information, the QoS requirement of the second terminal device for the first radio bearer should be met. The second information may include QoS information from the second terminal device, and after receiving the QoS information, the network device may determine configuration information of the first radio bearer according to the QoS information, so that the configured first radio bearer can better meet the requirement of the second terminal device.
With reference to the ninth optional implementation manner of the first aspect, in a tenth optional implementation manner of the first aspect, the obtaining the first configuration information includes:
receiving the first configuration information from the network device.
Since the second terminal device requests the network device to configure the radio bearer, the network device may send the first configuration information directly to the second terminal device.
With reference to the ninth optional implementation manner of the first aspect or the tenth optional implementation manner of the first aspect, in an eleventh optional implementation manner of the first aspect, the first configuration information includes a first sending configuration and a first common configuration, wherein,
the first transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the first common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Here, the information included in the first transmission configuration and the first common configuration is only an example, and the embodiment of the present application does not limit the information included in the first transmission configuration and the first common configuration.
With reference to the tenth optional implementation manner of the first aspect or the eleventh optional implementation manner of the first aspect, in a twelfth optional implementation manner of the first aspect, the method further includes:
and sending third configuration information to the second terminal device, where the third configuration information is used for the second terminal device to configure the first radio bearer, and the third configuration information includes part of or all of the content of the first configuration information.
Since in this way the network device sends configuration information (e.g. the first configuration information) to the first terminal device. And the first radio bearer is a radio bearer between the first terminal device and the second terminal device, and the second terminal device needs to configure the first radio bearer. Therefore, the first terminal device may send the third configuration information to the second terminal device, so that the second terminal device configures the first radio bearer.
In a second aspect, a second communication method is provided, the method comprising: receiving second configuration failure information from a first terminal device, where the second configuration failure information is used to indicate that the first terminal device fails to configure a first radio bearer, the first radio bearer is a radio bearer between the first terminal device and a second terminal device, the first terminal device provides a relay service for the second terminal device, the first terminal device is a data receiving end of a data transmission process performed through the first radio bearer, and the second terminal device is a data sending end of the data transmission process; and not sending information for indicating that the first terminal equipment fails to configure the first radio bearer to network equipment.
The method may be performed by a second communication device, which may be a communication apparatus or a communication device, e.g. a chip, capable of supporting the communication apparatus to perform the functions required by the method. Illustratively, the second communication device is a terminal device, or a chip provided in the terminal device for implementing the function of the terminal device, or another component for implementing the function of the terminal device. In the following description, the second communication device is taken as the second terminal device for example.
In addition to sending the first configuration failure information to the network device, the first terminal device may also send the second configuration failure information to the second terminal device because the first configuration information is sent to the first terminal device by the second terminal device. After receiving the second configuration failure information from the first terminal device, the second terminal device can determine that the first terminal device fails to configure the first radio bearer, so that the second terminal device may temporarily communicate with the first terminal device without passing through the first radio bearer. In addition, after receiving the second configuration failure information, the second terminal device does not trigger forwarding of the second configuration failure information to the network device, so that repeated transmission of the configuration failure information is avoided.
With reference to the second aspect, in a first optional implementation manner of the second aspect, the method further includes:
receiving fourth configuration information from the network device, where the fourth configuration information is used by the second terminal device to configure the first radio bearer.
With reference to the first optional implementation manner of the second aspect, in a second optional implementation manner of the second aspect, the fourth configuration information includes a third sending configuration and a third common configuration, wherein,
the third transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the third common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
With reference to the first alternative implementation manner of the second aspect or the second alternative implementation manner of the second aspect, in a third alternative implementation manner of the second aspect, the method further includes:
selecting a logical channel for the first radio bearer;
and sending first configuration information to the first terminal device, where the first configuration information is used for the first terminal device to configure the first radio bearer, and the first configuration information includes an identifier of a logical channel corresponding to the first radio bearer.
With reference to the third optional implementation manner of the second aspect, in a fourth optional implementation manner of the second aspect, the first configuration information includes a first common configuration, and the first common configuration includes one or more of the following: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
With reference to the first alternative implementation manner of the second aspect or the second alternative implementation manner of the second aspect, in a fifth alternative implementation manner of the second aspect, the method further includes:
selecting a logical channel for the first radio bearer;
and sending first information to the first terminal equipment, wherein the first information comprises the identifier of the logical channel corresponding to the first radio bearer.
With reference to the fifth optional implementation manner of the second aspect, in a sixth optional implementation manner of the second aspect, the first information further includes a QFI corresponding to the first radio bearer, and/or a correspondence between an identifier corresponding to the first radio bearer at the Uu port and an identifier corresponding to the PC5 port.
With reference to the second aspect, in a seventh optional implementation manner of the second aspect, the method further includes:
Receiving third configuration information from the first terminal device, where the third configuration information is used by the second terminal device to configure the first radio bearer, the third configuration information includes partial content or all content of first configuration information, and the first configuration information is used by the first terminal device to configure the first radio bearer.
With reference to the seventh alternative embodiment of the second aspect, in an eighth alternative embodiment of the second aspect, the method further includes:
and sending QoS information to the first terminal equipment, wherein the QoS information is used for indicating the QoS of the radio bearer which is configured between the second terminal equipment and the first terminal equipment.
With reference to the second aspect or any optional implementation manner of the first optional implementation manner of the second aspect to the eighth optional implementation manner of the second aspect, in a ninth optional implementation manner of the second aspect, the second terminal device cannot communicate with the network device through the Uu port.
For example, the second terminal device does not set the Uu port, or the second terminal device is not in the coverage of the network device, and so on. Of course, this is only one application scenario, and even if the second terminal device can communicate with the network device through the Uu port, the technical solution of the embodiment of the present application can also be applied.
With regard to the technical effects brought about by the second aspect or various alternative embodiments of the second aspect, reference may be made to the introduction to the technical effects of the first aspect or the respective embodiments.
In a third aspect, a third method of communication is provided, the method comprising: receiving first configuration failure information from a first terminal device; determining that the first terminal device fails to configure a first radio bearer according to the first configuration failure information, where the first radio bearer is a radio bearer between the first terminal device and a second terminal device, the first terminal device provides a relay service for the second terminal device, the first terminal device is a data receiving end of a data transmission process performed through the first radio bearer, and the second terminal device is a data transmitting end of the data transmission process.
The method may be performed by a third communication device, which may be a communication apparatus or a communication device, such as a chip, capable of supporting a communication apparatus to implement the functions required by the method. Illustratively, the third communication device is a network device, or a chip provided in the network device for implementing the function of the network device, or other components for implementing the function of the network device. In the following description, the third communication device is taken as an example of a network device. Illustratively, the network device is an access network device.
With reference to the third aspect, in a first optional implementation manner of the third aspect, the receiving the first configuration failure information from the first terminal device includes:
receiving an RRC message from the first terminal equipment, wherein the RRC message comprises a first information element, the first configuration failure information occupies reserved bits in the first information element, and the first information element is used for indicating a failure reason.
With reference to the third aspect or the first optional implementation manner of the third aspect, in a second optional implementation manner of the third aspect, the method further includes:
and sending fourth configuration information to the second terminal equipment, wherein the fourth configuration information is used for the second terminal equipment to configure the first radio bearer.
With reference to the second optional implementation manner of the third aspect, in a third optional implementation manner of the third aspect, the fourth configuration information includes a third sending configuration and a third common configuration, where,
the third transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the third common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
With reference to the third aspect or the first optional implementation manner of the third aspect or the second optional implementation manner of the third aspect, in a fourth optional implementation manner of the third aspect, the method further includes:
and sending second configuration information to the first terminal equipment, wherein the second configuration information is used for the first terminal equipment to configure the first radio bearer.
With reference to the fourth optional implementation manner of the third aspect, in a fifth optional implementation manner of the third aspect, the second configuration information includes a receiving configuration and a second common configuration, where the receiving configuration includes a PDCP reordering timer, and the second common configuration includes one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
With reference to the third aspect or the first optional implementation manner of the third aspect, in a sixth optional implementation manner of the third aspect, the method further includes:
and receiving second information from the first terminal equipment, wherein the second information is used for requesting to configure the radio bearer for bidirectional transmission between the second terminal equipment and the first terminal equipment, and the second information comprises QoS information which is used for indicating the QoS of the radio bearer requested to be configured between the second terminal equipment and the first terminal equipment.
With reference to the sixth optional implementation manner of the third aspect, in a seventh optional implementation manner of the third aspect, the method further includes:
determining first configuration information according to the QoS information, wherein the first configuration information is used for the first terminal equipment to configure the first radio bearer;
and sending the first configuration information to the first terminal equipment.
With reference to the seventh optional implementation manner of the third aspect, in an eighth optional implementation manner of the third aspect, the first configuration information includes a first sending configuration and a first common configuration, wherein,
the first transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the first common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
With regard to the technical effects brought about by the third aspect or the various alternative embodiments of the third aspect, reference may be made to the introduction of the technical effects of the first aspect or the respective embodiments.
In a fourth aspect, a fourth communication method is provided, the method comprising: the method comprises the steps that a second terminal device determines that a link between a first terminal device and the second terminal device fails, and the second terminal device is not in a network coverage range; the second terminal device does not send information indicating a link failure to the network device.
The method may be performed by a fourth communication device, which may be a communication apparatus or a communication device, such as a chip, capable of supporting a communication apparatus to implement the functions required by the method. Illustratively, the fourth communication device is a terminal device, or a chip provided in the terminal device for implementing the function of the terminal device, or another component for implementing the function of the terminal device. In the following description, the fourth communication device is taken as the second terminal device as an example.
When determining that the sidelink fails, the second terminal device does not send information for indicating the link failure to the network device, so that the second terminal device does not need to generate the information for indicating the link failure, and the power consumption of the second terminal device is reduced. Moreover, since a problem has occurred in the sidelink between the first terminal device and the second terminal device, if the second terminal device sends information indicating a link failure to the first terminal device through the sidelink, the information may also be sent to the first terminal device in a failure.
With reference to the fourth aspect, in a first optional implementation manner of the fourth aspect, the method further includes:
And the second terminal equipment sends a request message to the first terminal equipment to request to reestablish the link.
For example, if the technical solution of the embodiment of the present application is applied to a scenario in which two terminal devices are directly connected, that is, not used in a relay scenario, the first terminal device and the second terminal device need to communicate normally. In this case, if the sidelink fails, the second terminal device may request to reestablish the sidelink, so that the first terminal device and the second terminal device can resume normal communication as much as possible.
With reference to the fourth aspect, in a second optional implementation manner of the fourth aspect, the first terminal device provides a relay service for the second terminal device, and the method further includes:
and the second terminal equipment reselects the terminal equipment capable of providing the relay service for the second terminal equipment.
For example, if the technical solution of the embodiment of the present application is applied to a relay scenario, for example, a first terminal device provides a relay service for a second terminal device. Then, if the sidelink between the first terminal device and the second terminal device fails, the first terminal device may further re-access the network device through other terminal devices, so that the second terminal device may reselect the terminal device capable of providing the relay service for the second terminal device, so that the second terminal device can resume communication as soon as possible.
In a fifth aspect, a communication device is provided, for example, the communication device is the first communication device as described above. The first communication device is configured to perform the method of the first aspect or any optional implementation manner of the first aspect. In particular, the first communication device may include means for performing the method in the first aspect or any optional implementation manner of the first aspect, for example, a processing means, and optionally, a transceiver means. For example, the transceiver module may include a transmitting module and a receiving module, and the transmitting module and the receiving module may be different functional modules, or may also be the same functional module, but can implement different functions. Illustratively, the first communication device is a communication device, or a chip or other component provided in the communication device. Illustratively, the communication device is a terminal device, such as a first terminal device. In the following, the first communication apparatus is taken as an example of the first terminal device. For example, the transceiver module may also be implemented by a transceiver, and the processing module may also be implemented by a processor (or a processing circuit). Alternatively, the sending module may be implemented by a sender, the receiving module may be implemented by a receiver, and the sender and the receiver may be different functional modules, or may also be the same functional module, but may implement different functions. If the first communication means is a communication device, the transceiver is implemented, for example, by an antenna, a feeder, a codec, etc. in the communication device. Alternatively, if the first communication device is a chip disposed in the communication apparatus, the transceiver (or the transmitter and the receiver) is, for example, a communication interface in the chip, and the communication interface is connected with a radio frequency transceiving component in the communication apparatus to realize transceiving of information through the radio frequency transceiving component. In the introduction process of the fifth aspect, the description is continued by taking the first communication apparatus as a first terminal device, and taking the processing module, the sending module, and the receiving module as an example. Wherein the content of the first and second substances,
The processing module is configured to obtain first configuration information, where the first configuration information is used for a first terminal device to configure a first radio bearer, the first radio bearer is a radio bearer between the first terminal device and a second terminal device, and the second terminal device is a data sending end;
the processing module is further configured to configure the first radio bearer according to the first configuration information;
the sending module is configured to send first configuration failure information to a network device when the processing module fails to configure the first radio bearer.
With reference to the fifth aspect, in a first optional implementation manner of the fifth aspect, the sending module is configured to send the first configuration failure information to the network device by:
sending an RRC message to a network device, wherein the RRC message comprises a first information element, the first configuration failure information occupies reserved bits in the first information element, and the first information element is used for indicating a failure reason.
With reference to the fifth aspect or the first optional implementation manner of the fifth aspect, in a second optional implementation manner of the fifth aspect, the sending module is further configured to send second configuration failure information to the second terminal device, where the second configuration failure information is used to indicate that the first terminal device fails to configure the first radio bearer.
With reference to the fifth aspect or the first optional implementation manner of the fifth aspect or the second optional implementation manner of the fifth aspect, in a third optional implementation manner of the fifth aspect, the processing module is configured to obtain the first configuration information by:
receiving the first configuration information from the second terminal device through the receiving module.
With reference to the third optional implementation manner of the fifth aspect, in a fourth optional implementation manner of the fifth aspect, the first configuration information includes a first common configuration, and the first common configuration includes one or more of the following: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
With reference to the fifth aspect or the first optional implementation manner of the fifth aspect or the second optional implementation manner of the fifth aspect, in a fourth optional implementation manner of the fifth aspect, the processing module is configured to obtain the first configuration information by:
receiving, by the receiving module, second configuration information from the network device;
receiving, by the receiving module, first information from the second terminal device, where the first information includes an identifier of a logical channel corresponding to the first radio bearer;
And obtaining the first configuration information according to the second configuration information and the first information.
With reference to the fifth optional implementation manner of the fifth aspect, in a sixth optional implementation manner of the fifth aspect, the first information is obtained by the second terminal device according to fourth configuration information from the network device, where the fourth configuration information is used by the second terminal device to configure the first radio bearer.
With reference to the fifth optional implementation manner of the fifth aspect or the sixth optional implementation manner of the fifth aspect, in a seventh optional implementation manner of the fifth aspect, the first information further includes a QFI corresponding to the first radio bearer, and/or a correspondence between an identifier corresponding to the first radio bearer at the Uu port and an identifier corresponding to the PC5 port.
With reference to the fifth optional implementation manner of the fifth aspect or the sixth optional implementation manner of the fifth aspect or the seventh optional implementation manner of the fifth aspect, in an eighth optional implementation manner of the fifth aspect, the second configuration information includes a receiving configuration and a second common configuration, where the receiving configuration includes a PDCP reordering timer, and the second common configuration includes one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
With reference to the fifth aspect or the first alternative implementation of the fifth aspect or the second alternative implementation of the fifth aspect, in a ninth alternative implementation of the fifth aspect,
the receiving module is further configured to receive QoS information from the second terminal device before the processing module obtains the first configuration information, where the QoS information is used to indicate a QoS of a radio bearer requested to be configured between the second terminal device and the first terminal device;
the sending module is further configured to send second information to the network device, where the second information is used to request configuration of a radio bearer for bidirectional transmission between the second terminal device and the first terminal device, and the second information includes the QoS information.
With reference to the ninth optional implementation manner of the fifth aspect, in a tenth optional implementation manner of the fifth aspect, the processing module is configured to obtain the first configuration information by:
receiving, by the receiving module, the first configuration information from the network device.
With reference to the ninth optional implementation manner of the fifth aspect or the tenth optional implementation manner of the fifth aspect, in an eleventh optional implementation manner of the fifth aspect, the first configuration information includes a first sending configuration and a first common configuration, wherein,
The first transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the first common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
With reference to the tenth optional implementation manner of the fifth aspect or the eleventh optional implementation manner of the fifth aspect, in a twelfth optional implementation manner of the fifth aspect, the sending module is further configured to send third configuration information to the second terminal device, where the third configuration information is used by the second terminal device to configure the first radio bearer, and the third configuration information includes a part of or all of content of the first configuration information.
With regard to the technical effects brought about by the fifth aspect or the various alternative embodiments of the fifth aspect, reference may be made to the introduction to the technical effects of the first aspect or the respective embodiments.
A sixth aspect provides a communication device, for example a second communication device as described above. The second communication device is configured to perform the method of the second aspect or any optional implementation manner of the second aspect. In particular, the second communication device may include means for performing the method in the second aspect or any optional implementation manner of the second aspect, for example, a processing means, and optionally, a transceiver means. For example, the transceiver module may include a transmitting module and a receiving module, and the transmitting module and the receiving module may be different functional modules, or may also be the same functional module, but can implement different functions. Illustratively, the second communication device is a communication device, or a chip or other component provided in the communication device. Illustratively, the communication device is a terminal device, such as a second terminal device. In the following, the second communication apparatus is taken as an example of the second terminal device. For example, the transceiver module may also be implemented by a transceiver, and the processing module may also be implemented by a processor (or a processing circuit). Alternatively, the sending module may be implemented by a sender, the receiving module may be implemented by a receiver, and the sender and the receiver may be different functional modules, or may also be the same functional module, but may implement different functions. If the second communication means is a communication device, the transceiver is implemented, for example, by an antenna, a feeder, a codec, etc. in the communication device. Alternatively, if the second communication device is a chip disposed in the communication apparatus, the transceiver (or the transmitter and the receiver) is, for example, a communication interface in the chip, and the communication interface is connected with a radio frequency transceiving component in the communication apparatus to realize transceiving of information through the radio frequency transceiving component. In the introduction process of the sixth aspect, the description is continued by taking the second communication apparatus as a second terminal device, and taking the processing module, the sending module, and the receiving module as an example. Wherein the content of the first and second substances,
The receiving module is configured to receive second configuration failure information from a first terminal device, where the second configuration failure information is used to indicate that the first terminal device fails to configure a first radio bearer, the first radio bearer is a radio bearer between the first terminal device and a second terminal device, the first terminal device provides a relay service for the second terminal device, the first terminal device is a data receiving end of a data transmission process performed through the first radio bearer, and the second terminal device is a data sending end of the data transmission process;
the sending module is configured to not send, to a network device, information indicating that the first radio bearer configuration by the first terminal device has failed.
With reference to the sixth aspect, in a first optional implementation manner of the sixth aspect, the receiving module is further configured to receive fourth configuration information from the network device, where the fourth configuration information is used by the second terminal device to configure the first radio bearer.
With reference to the first optional implementation manner of the sixth aspect, in a second optional implementation manner of the sixth aspect, the fourth configuration information includes a third sending configuration and a third common configuration, wherein,
The third transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the third common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
With reference to the first alternative embodiment of the sixth aspect or the second alternative embodiment of the sixth aspect, in a third alternative embodiment of the sixth aspect,
the processing module is configured to select a logical channel for the first radio bearer;
the sending module is further configured to send first configuration information to the first terminal device, where the first configuration information is used for the first terminal device to configure the first radio bearer, and the first configuration information includes an identifier of a logical channel corresponding to the first radio bearer.
With reference to the third optional implementation manner of the sixth aspect, in a fourth optional implementation manner of the sixth aspect, the first configuration information includes a first common configuration, and the first common configuration includes one or more of the following: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
With reference to the first alternative embodiment of the sixth aspect or the second alternative embodiment of the sixth aspect, in a fifth alternative embodiment of the sixth aspect,
the processing module is further configured to select a logical channel for the first radio bearer;
the sending module is further configured to send first information to the first terminal device, where the first information includes an identifier of a logical channel corresponding to the first radio bearer.
With reference to the fifth optional implementation manner of the sixth aspect, in a sixth optional implementation manner of the sixth aspect, the first information further includes a QFI corresponding to the first radio bearer, and/or a correspondence between an identifier corresponding to the first radio bearer at the Uu port and an identifier corresponding to the PC5 port.
With reference to the sixth aspect, in a seventh optional implementation manner of the sixth aspect, the receiving module is further configured to receive third configuration information from the first terminal device, where the third configuration information is used by the second terminal device to configure the first radio bearer, the third configuration information includes a part of or all of content of first configuration information, and the first configuration information is used by the first terminal device to configure the first radio bearer.
With reference to the seventh optional implementation manner of the sixth aspect, in an eighth optional implementation manner of the sixth aspect, the sending module is further configured to send, to the first terminal device, QoS information, where the QoS information is used to indicate a QoS for a radio bearer configured between the second terminal device and the first terminal device is requested.
With reference to the sixth aspect or any optional implementation manner of the first optional implementation manner to the eighth optional implementation manner of the sixth aspect, in a ninth optional implementation manner of the sixth aspect, the second terminal device cannot communicate with the network device through the Uu port.
With regard to the technical effects brought about by the sixth aspect or the various alternative embodiments of the sixth aspect, reference may be made to the introduction to the technical effects of the second aspect or the respective embodiments.
A seventh aspect provides a communication device, for example, the communication device is the third communication device as described above. The third communication device is configured to perform the method in the third aspect or any optional implementation manner of the third aspect. In particular, the third communication device may include a module for performing the method in any optional implementation manner of the third aspect or the third aspect, for example, a processing module, and optionally, a transceiver module. For example, the transceiver module may include a transmitting module and a receiving module, and the transmitting module and the receiving module may be different functional modules, or may also be the same functional module, but can implement different functions. Illustratively, the third communication device is a communication device, or a chip or other component provided in the communication device. Illustratively, the communication device is a network device. Illustratively, the network device is an access network device, such as a base station. For example, the transceiver module may also be implemented by a transceiver, and the processing module may also be implemented by a processor (or a processing circuit). Alternatively, the sending module may be implemented by a sender, the receiving module may be implemented by a receiver, and the sender and the receiver may be different functional modules, or may also be the same functional module, but may implement different functions. If the third communication means is a communication device, the transceiver is implemented, for example, by an antenna, a feeder, a codec, etc. in the communication device. Alternatively, if the third communication device is a chip disposed in the communication apparatus, the transceiver (or the transmitter and the receiver) is, for example, a communication interface in the chip, and the communication interface is connected with a radio frequency transceiving component in the communication apparatus to realize transceiving of information through the radio frequency transceiving component. In the introduction process of the seventh aspect, the processing module, the sending module, and the receiving module are taken as examples for introduction. Wherein the content of the first and second substances,
The receiving module is used for receiving first configuration failure information from first terminal equipment;
the processing module is configured to determine that the first terminal device fails to configure a first radio bearer according to the first configuration failure information, where the first radio bearer is a radio bearer between the first terminal device and a second terminal device, the first terminal device provides a relay service for the second terminal device, the first terminal device is a data receiving end of a data transmission process performed through the first radio bearer, and the second terminal device is a data sending end of the data transmission process.
With reference to the seventh aspect, in a first optional implementation manner of the seventh aspect, the receiving module is configured to receive the first configuration failure information from the first terminal device by:
receiving an RRC message from the first terminal equipment, wherein the RRC message comprises a first information element, the first configuration failure information occupies reserved bits in the first information element, and the first information element is used for indicating a failure reason.
With reference to the seventh aspect or the first optional implementation manner of the seventh aspect, in a second optional implementation manner of the seventh aspect, the sending module is configured to send fourth configuration information to the second terminal device, where the fourth configuration information is used by the second terminal device to configure the first radio bearer.
With reference to the second optional implementation manner of the seventh aspect, in a third optional implementation manner of the seventh aspect, the fourth configuration information includes a third sending configuration and a third common configuration, wherein,
the third transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the third common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
With reference to the seventh aspect or the first optional implementation manner of the seventh aspect or the second optional implementation manner of the seventh aspect, in a fourth optional implementation manner of the seventh aspect, the sending module is further configured to send second configuration information to the first terminal device, where the second configuration information is used by the first terminal device to configure the first radio bearer.
With reference to the fourth optional implementation manner of the seventh aspect, in a fifth optional implementation manner of the seventh aspect, the second configuration information includes a receiving configuration and a second common configuration, where the receiving configuration includes a PDCP reordering timer, and the second common configuration includes one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
With reference to the seventh aspect or the first optional implementation manner of the seventh aspect, in a sixth optional implementation manner of the seventh aspect, the receiving module is further configured to receive second information from the first terminal device, where the second information is used to request configuration of a radio bearer for bidirectional transmission between the second terminal device and the first terminal device, and the second information includes QoS information, where the QoS information is used to indicate that QoS of the radio bearer configured between the second terminal device and the first terminal device is requested.
With reference to the sixth alternative implementation manner of the seventh aspect, in the seventh alternative implementation manner of the seventh aspect,
the processing module is further configured to determine first configuration information according to the QoS information, where the first configuration information is used for configuring the first radio bearer by the first terminal device;
the sending module is further configured to send the first configuration information to the first terminal device.
With reference to the seventh optional implementation manner of the seventh aspect, in an eighth optional implementation manner of the seventh aspect, the first configuration information includes a first sending configuration and a first common configuration, wherein,
The first transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the first common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
With regard to the technical effects brought about by the seventh aspect or the various alternative embodiments of the seventh aspect, reference may be made to the introduction of the technical effects of the third aspect or the respective embodiments.
An eighth aspect provides a communication device, for example, the communication device is the fourth communication device as described above. The fourth communication device is configured to perform the method of the fourth aspect or any optional implementation manner of the fourth aspect. In particular, the fourth communication device may include a module for executing the method in any optional implementation manner of the fourth aspect or the fourth aspect, for example, a processing module, and optionally, a transceiver module. For example, the transceiver module may include a transmitting module and a receiving module, and the transmitting module and the receiving module may be different functional modules, or may also be the same functional module, but can implement different functions. Illustratively, the fourth communication device is a communication device, or a chip or other component disposed in the communication device. Illustratively, the communication device is a terminal device, for example, a second terminal device. For example, the transceiver module may also be implemented by a transceiver, and the processing module may also be implemented by a processor (or a processing circuit). Alternatively, the sending module may be implemented by a sender, the receiving module may be implemented by a receiver, and the sender and the receiver may be different functional modules, or may also be the same functional module, but may implement different functions. If the fourth communication means is a communication device, the transceiver is implemented, for example, by an antenna, a feeder, a codec, etc. in the communication device. Alternatively, if the fourth communication device is a chip disposed in the communication apparatus, the transceiver (or the transmitter and the receiver) is, for example, a communication interface in the chip, and the communication interface is connected to a radio frequency transceiving component in the communication apparatus to realize transceiving of information through the radio frequency transceiving component. In the introduction process of the eighth aspect, the processing module, the sending module, and the receiving module are taken as examples for introduction. Wherein the content of the first and second substances,
The processing module is configured to determine that a link between a first terminal device and a second terminal device fails, and the second terminal device is not within a network coverage range;
the sending module is configured to not send information indicating a link failure to the network device.
With reference to the eighth aspect, in a first optional implementation manner of the eighth aspect, the sending module is further configured to send a request message to the first terminal device to request to reestablish the link.
With reference to the eighth aspect, in a second optional implementation manner of the eighth aspect, the first terminal device provides a relay service for the second terminal device, and the processing module is further configured to reselect a terminal device capable of providing the relay service for the second terminal device.
A ninth aspect provides a communication device, for example a first communication device as described above. The communication device includes a processor (or processing circuitry) and a communication interface (or interface circuitry) that may be used to communicate with other devices or apparatuses. Optionally, a memory may also be included for storing the computer instructions. The processor and the memory are coupled to each other for implementing the method as described in the first aspect or in the various possible embodiments of the first aspect. Alternatively, the first communication device may not include the memory, and the memory may be located outside the first communication device. The processor, the memory and the communication interface are coupled to each other for implementing the method as described in the first aspect or in various possible embodiments of the first aspect. The processor, for example, when executing the computer instructions stored by the memory, causes the first communication device to perform the method of the first aspect or any one of the possible implementations of the first aspect. Illustratively, the first communication device is a communication device, or a chip or other component provided in the communication device. Illustratively, the communication device is a terminal device, such as a first terminal device.
Wherein, if the first communication means is a communication device, the communication interface is implemented, for example, by a transceiver (or a transmitter and a receiver) in the communication device, for example, the transceiver is implemented by an antenna, a feeder, a codec, and the like in the communication device. Or, if the first communication device is a chip disposed in the communication apparatus, the communication interface is, for example, an input/output interface, such as an input/output pin, of the chip, and the communication interface is connected to a radio frequency transceiving component in the communication apparatus to implement transceiving of information through the radio frequency transceiving component.
A tenth aspect provides a communication device, for example a second communication device as described above. The communication device includes a processor (or processing circuitry) and a communication interface (or interface circuitry) that may be used to communicate with other devices or apparatuses. Optionally, a memory may also be included for storing the computer instructions. The processor and the memory are coupled to each other for implementing the method as described in the second aspect or in various possible embodiments of the second aspect. Alternatively, the second communication device may not include a memory, and the memory may be located outside the second communication device. The processor, the memory and the communication interface are coupled to each other for implementing the method as described in the second aspect or in various possible embodiments of the second aspect. The processor, for example, when executing the computer instructions stored by the memory, causes the second communication device to perform the method of the second aspect or any one of the possible embodiments of the second aspect. Illustratively, the second communication device is a communication device, or a chip or other component provided in the communication device. Illustratively, the communication device is a terminal device, such as a second terminal device.
Wherein, if the second communication means is a communication device, the communication interface is implemented, for example, by a transceiver (or a transmitter and a receiver) in the communication device, for example, by an antenna, a feeder, a codec, etc. in the communication device. Or, if the second communication device is a chip disposed in the communication apparatus, the communication interface is, for example, an input/output interface, such as an input/output pin, of the chip, and the communication interface is connected to a radio frequency transceiving component in the communication apparatus to realize transceiving of information through the radio frequency transceiving component.
In an eleventh aspect, a communication device is provided, for example a third communication device as described above. The communication device includes a processor (or processing circuitry) and a communication interface (or interface circuitry) that may be used to communicate with other devices or apparatuses. Optionally, a memory may also be included for storing the computer instructions. The processor and the memory are coupled to each other for implementing the methods described in the third aspect or the various possible embodiments of the third aspect. Alternatively, the third communication device may not include a memory, and the memory may be located outside the third communication device. The processor, the memory and the communication interface are coupled to each other for implementing the methods described in the third aspect or the various possible embodiments of the third aspect. The processor, for example, when executing the computer instructions stored by the memory, causes the third communication device to perform the method of the third aspect or any one of the possible embodiments of the third aspect. Illustratively, the third communication device is a communication device, or a chip or other component provided in the communication device. Illustratively, the communication device is a network device. Illustratively, the network device is an access network device, such as a base station.
Wherein, if the third communication device is a communication device, the communication interface is implemented by, for example, a transceiver (or a transmitter and a receiver) in the communication device, for example, the transceiver is implemented by an antenna, a feeder, a codec, and the like in the communication device. Or, if the third communication device is a chip disposed in the communication apparatus, the communication interface is, for example, an input/output interface, such as an input/output pin, of the chip, and the communication interface is connected to a radio frequency transceiving component in the communication apparatus to implement transceiving of information through the radio frequency transceiving component.
In a twelfth aspect, a communication device is provided, for example, the fourth communication device as described above. The communication device includes a processor (or processing circuitry) and a communication interface (or interface circuitry) that may be used to communicate with other devices or apparatuses. Optionally, a memory may also be included for storing the computer instructions. The processor and the memory are coupled to each other for implementing the methods described in the above fourth aspect or the various possible embodiments of the fourth aspect. Alternatively, the fourth communication device may not include the memory, and the memory may be located outside the fourth communication device. The processor, the memory and the communication interface are coupled to each other for implementing the methods described in the above fourth aspect or the various possible embodiments of the fourth aspect. For example, the processor, when executing the computer instructions stored by the memory, causes the fourth communication device to perform the method of the fourth aspect or any one of the possible embodiments of the fourth aspect. Illustratively, the fourth communication device is a communication device, or a chip or other component disposed in the communication device. Illustratively, the communication device is a terminal device, such as a second terminal device.
Wherein, if the fourth communication device is a communication device, the communication interface is implemented by a transceiver (or a transmitter and a receiver) in the communication device, for example, the transceiver is implemented by an antenna, a feeder, a codec, and the like in the communication device. Or, if the fourth communication device is a chip disposed in the communication apparatus, the communication interface is, for example, an input/output interface, such as an input/output pin, of the chip, and the communication interface is connected to a radio frequency transceiving component in the communication apparatus to implement transceiving of information through the radio frequency transceiving component.
In a thirteenth aspect, there is provided a first communication system comprising the communication apparatus of the fifth aspect or the communication apparatus of the ninth aspect, comprising the communication apparatus of the sixth aspect or the communication apparatus of the tenth aspect, and comprising the communication apparatus of the seventh aspect or the communication apparatus of the eleventh aspect.
A fourteenth aspect provides a second communication system comprising the communication apparatus of the eighth aspect or the communication apparatus of the twelfth aspect.
In a fifteenth aspect, a computer-readable storage medium is provided, which is used to store a computer program, which, when run on a computer, causes the computer to perform the method of the first aspect or any one of the alternative embodiments of the first aspect.
In a sixteenth aspect, there is provided a computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of the second aspect or any one of the alternative embodiments of the second aspect.
A seventeenth aspect provides a computer-readable storage medium storing a computer program for causing a computer to perform the method of the third aspect or any one of the alternative embodiments of the third aspect when the computer program runs on the computer.
In an eighteenth aspect, there is provided a computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of the fourth aspect or any one of the alternative embodiments of the fourth aspect.
A nineteenth aspect provides a computer program product comprising instructions for storing a computer program which, when run on a computer, causes the computer to perform the method of the first aspect or any one of the alternative embodiments of the first aspect.
A twentieth aspect provides a computer program product comprising instructions for storing a computer program which, when run on a computer, causes the computer to perform the method of the second aspect or any one of the alternative embodiments of the second aspect.
A twenty-first aspect provides a computer program product comprising instructions for storing a computer program which, when run on a computer, causes the computer to perform the method of the third aspect or any one of the alternative embodiments of the third aspect.
In a twenty-second aspect, there is provided a computer program product comprising instructions for storing a computer program which, when run on a computer, causes the computer to perform the method of any one of the alternative embodiments of the fourth aspect or the fourth aspect described above.
In the embodiment of the application, the relay terminal device does not need to send the configuration failure information to the remote terminal device, and the remote terminal device forwards the configuration failure information to the network through the relay terminal device, so that the forwarding process of the configuration failure information is reduced, and the transmission resource is saved.
Drawings
FIG. 1A is a schematic view of V2X;
FIG. 1B is a schematic diagram of a mobile phone in communication with smart glasses via a sidelink;
fig. 2 is a schematic diagram of a terminal device providing a relay service for another terminal device;
fig. 3 is a flowchart of a network device providing configuration information for a remote terminal device in a relay scenario;
fig. 4 is a flowchart of a first communication method according to an embodiment of the present application;
fig. 5 is a flowchart of a second communication method provided in the embodiment of the present application;
fig. 6 is a flowchart of a third communication method provided in the embodiment of the present application;
fig. 7 is a flowchart of reporting to a network when a remote terminal device determines that a sidelink fails in a relay scenario;
fig. 8 is a flowchart of a fourth communication method provided in the embodiment of the present application;
fig. 9 is a schematic block diagram of a first terminal device according to an embodiment of the present application;
fig. 10 is a schematic block diagram of a second terminal device provided in an embodiment of the present application;
fig. 11 is a schematic block diagram of a network device provided in an embodiment of the present application;
fig. 12 is another schematic block diagram of a second terminal device according to an embodiment of the present application;
fig. 13 is a schematic block diagram of a communication device according to an embodiment of the present application;
Fig. 14 is another schematic block diagram of a communication device according to an embodiment of the present application;
fig. 15 is a further schematic block diagram of a communication device provided in an embodiment of the present application;
fig. 16 is a further schematic block diagram of a communication device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.
Hereinafter, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.
1) Terminal equipment, including equipment providing voice and/or data connectivity to a user, in particular, including equipment providing voice to a user, or including equipment providing data connectivity to a user, or including equipment providing voice and data connectivity to a user. For example, may include a handheld device having wireless connection capability, or a processing device connected to a wireless modem. The terminal device may communicate with a core network via a Radio Access Network (RAN), exchange voice or data with the RAN, or interact with the RAN. The terminal device may include a User Equipment (UE), a wireless terminal device, a mobile terminal device, a device-to-device communication (D2D) terminal device, a vehicle-to-all (V2X) terminal device, a machine-to-machine/machine-type communication (M2M/MTC) terminal device, an internet of things (IoT) terminal device, a subscription unit (subscriber unit), a subscription station (IoT), a mobile station (mobile station), a remote station (remote station), an access point (access point, AP), a remote terminal (remote), an access terminal (access terminal), a user terminal (user terminal), a user agent (user agent), or user equipment (user), etc. For example, mobile telephones (or so-called "cellular" telephones), computers with mobile terminal equipment, portable, pocket, hand-held, computer-included mobile devices, and the like may be included. For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and the like. Also included are constrained devices, such as devices that consume less power, or devices that have limited storage capabilities, or devices that have limited computing capabilities, etc. Examples of information sensing devices include bar codes, Radio Frequency Identification (RFID), sensors, Global Positioning Systems (GPS), laser scanners, and the like.
By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable equipment can also be called wearable smart device or intelligent wearable equipment etc. is the general term of using wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets, smart helmets, smart jewelry and the like for monitoring physical signs.
The various terminal devices described above, if located on a vehicle (e.g., placed in or installed in the vehicle), may be considered to be vehicle-mounted terminal devices, which are also referred to as on-board units (OBUs), for example.
In this embodiment, the terminal device may further include a relay (relay). Or, it is understood that any device capable of data communication with a base station may be considered a terminal device.
In the embodiment of the present application, the apparatus for implementing the function of the terminal device may be the terminal device, or may be an apparatus capable of supporting the terminal device to implement the function, for example, a chip system, and the apparatus may be installed in the terminal device. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices. In the technical solution provided in the embodiment of the present application, a device for implementing a function of a terminal is taken as an example of a terminal device, and the technical solution provided in the embodiment of the present application is described.
2) Network devices, including, for example, Access Network (AN) devices, such as base stations (e.g., access points), may refer to devices in AN access network that communicate with wireless terminal devices over one or more cells over the air, or, for example, a network device in vehicle-to-all (V2X) technology is a Road Side Unit (RSU). The base station may be configured to interconvert received air frames and IP packets as a router between the terminal device and the rest of the access network, which may include an IP network. The RSU may be a fixed infrastructure entity supporting the V2X application and may exchange messages with other entities supporting the V2X application. The network device may also coordinate attribute management for the air interface. For example, the network device may include an evolved Node B (NodeB) or eNB or e-NodeB in an LTE system or an LTE-a (long term evolution-advanced), or may also include a next generation Node B (gNB) in a 5th generation (5G) NR system (also referred to as an NR system) or may also include a Centralized Unit (CU) and a Distributed Unit (DU) in a Cloud access network (Cloud RAN) system, which is not limited in the embodiments.
The network device may further include a core network device, for example, including an access and mobility management function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), or the like in a 5G system, or including a Mobility Management Entity (MME) in a 4G system, or the like. In the following description of the embodiments of the present application, unless otherwise specified, all the network devices refer to access network devices.
In the embodiment of the present application, the apparatus for implementing the function of the network device may be a network device, or may be an apparatus capable of supporting the network device to implement the function, for example, a system on chip, and the apparatus may be installed in the network device. In the technical solution provided in the embodiment of the present application, a device for implementing a function of a network device is taken as an example of a network device, and the technical solution provided in the embodiment of the present application is described.
3) The terms "system" and "network" in the embodiments of the present application may be used interchangeably. "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple.
And, unless stated to the contrary, the embodiments of the present application refer to the ordinal numbers "first", "second", etc., for distinguishing a plurality of objects, and do not limit the size, content, sequence, timing, priority, degree of importance, etc., of the plurality of objects. For example, the first configuration information and the second configuration information are only for distinguishing different configuration information, and do not indicate a difference in information amount, content, priority, importance, or the like between the two pieces of configuration information.
The foregoing has described some of the noun concepts to which embodiments of the present application relate, and the following has described some features of the embodiments of the present application.
The sidelink refers to a transmission link between two terminal devices, for example, referring to fig. 1A, a schematic diagram of V2X, two vehicles may be regarded as two terminal devices, namely, terminal device 1 and terminal device 2, which may communicate via the sidelink, and the base station may allocate resources for the sidelink communication for the two terminal devices. Referring to fig. 1B, a schematic diagram of a mobile phone communicating with smart glasses such as Augmented Reality (AR)/Virtual Reality (VR) glasses through a sidelink is shown. Wherein, the terminal device (for example, the vehicle in fig. 1A, or the mobile phone or the smart glasses in fig. 1B) and the access network device (for example, the base station in fig. 1A or fig. 1B) communicate with each other through the Uu port.
In addition, consider a scenario in which the terminal device 2 accesses the network through the terminal device 1, that is, information between the terminal device 2 and the network needs to be relayed through the terminal device 1. It is understood that the terminal device 2 is a remote terminal device, the terminal device 1 is a relay terminal device, and the terminal device 1 provides a relay service for the terminal device 2. Relaying means that information sent by the terminal device 2 to the network is sent to the access network device via the terminal device 1, and information sent by the network to the terminal device 2 is also sent to the terminal device 2 via the terminal device 1. For example, the terminal device 2 is in an out of coverage (OOC) state, or the terminal device 2 is a terminal device having no Uu function (for example, the terminal device 2 is not provided with a Uu port). Reference may be made to fig. 2, which is a schematic illustration of this scenario. Fig. 2 includes a terminal device 1, a terminal device 2, an access network device, and a core network device, where the access network device is an access network device accessed by the terminal device 1, and the core network device is a core network device serving the access network device. The information between the terminal device 2 and the access network device can be relayed through the terminal device 1.
The access network device in fig. 2 is, for example, a base station. The access network device may correspond to different devices in different systems, for example, in the 4th generation (4G) system, the access network device may correspond to an eNB, and in the 5G system, the access network device in the 5G, for example, a gNB. Of course, the technical solution provided in the embodiment of the present application may also be applied to a future mobile communication system, and therefore, the access network device in fig. 2 may also correspond to a network device in the future mobile communication system. In fig. 2, the access network device is taken as a base station as an example, and actually, referring to the foregoing description, the access network device may also be an RSU or the like. The core network in fig. 2 is, for example, AMF, or may be another core network device.
In this scenario, if the terminal device 2 cannot communicate with the base station through the Uu port, for example, the terminal device 2 is in an OOC state, or the terminal device 2 does not set the Uu port, etc., the terminal device 2 may be configured by the terminal device 2 itself if the sidelink between the terminal device 2 and the terminal device 1 is to be configured. For example, the terminal device 2 may pre-store one or more sets of configurations, and the terminal device 2 may configure the sidelink according to the pre-stored set of configurations. However, this approach is not flexible enough, and the configuration pre-stored by the terminal device 2 may not meet the requirements of the current link. In this scenario, therefore, terminal device 2 may also be configured by the base station, and this configuration process is described below, and the flow of this process may refer to fig. 3.
S31, a PC 5-signal (S) connection is established between the terminal equipment 1 and the terminal equipment 2.
S32, the base station transmits the common configuration and the transmission configuration to the terminal device 2, and the terminal device 2 receives the transmission configuration and the common configuration from the base station. The transmission configuration and common configuration are configurations in which the terminal device 2 corresponds to the sidelink between the terminal device 2 and the terminal device 1.
For example, if terminal device 2 is to transmit information to terminal device 1, terminal device 2 may request the base station to download the configuration corresponding to the sidelink, and the base station may transmit the common configuration and the transmission configuration to terminal device 2.
S33, terminal device 2 sends the common configuration to terminal device 1, and terminal device 1 receives the common configuration from terminal device 2.
S34, the terminal device 1 fails to configure.
The terminal device 1 may generate a reception configuration corresponding to the sidelink from the received common configuration, where the terminal device 1 fails to generate the reception configuration.
S35, terminal device 1 sends configuration failure information to terminal device 2, and terminal device 2 receives configuration failure information from terminal device 1.
S36, terminal device 2 sends the information of failed configuration to the base station, and the base station receives the information of failed configuration from terminal device 2.
The terminal device 2 sends the information of failed configuration to the terminal device 1, and the terminal device 1 forwards the information of failed configuration to the base station.
It can be seen that, for the above configuration procedure, if the terminal device 2 fails to generate the received configuration, since the terminal device 2 is a common configuration obtained from the terminal device 1, the terminal device 2 is to send information of failed configuration to the terminal device 1, and then the terminal device 1 sends the information of failed configuration to the terminal device 2, and the terminal device 2 forwards the information of failed configuration to the base station. Therefore, the process causes repeated transmission of information, and wastes transmission resources.
In view of this, the technical solutions of the embodiments of the present application are provided. In the embodiment of the present application, if a configuration failure occurs in a relay terminal device that provides a relay service for a remote terminal device, the relay terminal device may send first configuration failure information to a network device, that is, the relay terminal device does not need to send the first configuration failure information to the remote terminal device, and then the remote terminal device forwards the first configuration failure information to the network through the relay terminal device, thereby reducing a forwarding process of the first configuration failure information and saving transmission resources.
The technical solution provided in the embodiment of the present application may be applied to a 4G system, for example, an LTE system, or may be applied to a 5G system, for example, an NR system, or may also be applied to a next generation mobile communication system or other similar communication systems, which is not limited specifically. In addition, the technical scheme provided by the embodiment of the application can be applied to a device-to-device (D2D) scene, such as an NR-D2D scene, or can be applied to a V2X scene, such as an NR-V2X scene, for example, can be applied to a vehicle networking, such as a V2X, a vehicle-to-vehicle (V2V), or can be applied to the fields of intelligent driving, auxiliary driving, or intelligent internet vehicles.
For an application scenario of the embodiment of the present application, reference may be made to fig. 2.
For example, a user may now own a wide variety of terminal devices, such as a cell phone, a smart watch, a smart bracelet, a smart wireless headset, or smart glasses, etc. In these terminal devices, the Uu port may not be provided in other terminal devices except the mobile phone, for example, a smart watch or smart glasses may not be provided, and these terminal devices without the Uu port may access the network through the mobile phone to perform network-controlled sidestream communication, or the mobile phone controls the communication of the terminal device in the sidestream link. If smart glasses are through carrying out the side bank communication with the cell-phone, the VR video on the cell-phone is watched to the messenger user on glasses, even the VR video in high in the clouds. If the intelligent wireless earphone is in side-line communication with the mobile phone, the user can listen to music on the mobile phone through the intelligent wireless earphone.
As another example, there may be scenarios where there is no network coverage, such as a basement scenario, where the network signal is insufficient to support communications. Then the terminal equipment in the basement can be connected with the network through the terminal equipment on the building to establish a communication link, thereby enlarging the coverage of the existing network.
The method provided by the embodiment of the application is described below with reference to the accompanying drawings. In various embodiments of the present application described below, the second terminal device is, for example, a terminal device that cannot communicate with the network device through the Uu port, for example, the second terminal device is not covered by the network device, or the Uu port is not set in the second terminal device.
The embodiment of the present application provides a first communication method, please refer to fig. 4, which is a flowchart of the method. In the following description, the method is applied to the network architecture shown in fig. 2 as an example. The scenario shown in fig. 2 is a relay scenario, or the embodiment of the present application may also be used in a scenario in which two terminal devices are directly connected, instead of the relay scenario, for example, if the first terminal device can communicate with the second terminal device, the second terminal device is in an OOC state, or the second terminal device is not provided with a Uu port, and the first terminal device is in an in-coverage (IC) state, the network device serving the first terminal device can provide configuration information for the second terminal device.
For ease of description, in the following, the method is performed by a network device and a terminal device as an example. Since the embodiment of the present application is applied to the network architecture shown in fig. 2 as an example. Therefore, the network device described below may be an access network device in the network architecture shown in fig. 2, the first terminal device described below may be the terminal device 1 in the network architecture shown in fig. 2, and the second terminal device described below may be the terminal device 2 in the network architecture shown in fig. 2.
S41, the first terminal device and the second terminal device establish a PC5-S connection. After establishing the PC5-S connection, the first terminal device and the second terminal device may communicate over a sidelink.
S42, the network device sends the fourth configuration information to the second terminal device, and the second terminal device receives the fourth configuration information from the network device accordingly.
Before performing S42, for example, the second terminal device is to send information to the first terminal device, the second terminal device may send a second request message to the network device to request the network device to configure a radio bearer between the first terminal device and the second terminal device. After receiving the second request message from the second terminal device, the network device may send fourth configuration information to the second terminal device, where the fourth configuration information is used to configure a radio bearer between the first terminal device and the second terminal device, and the radio bearer is referred to as a fourth radio bearer, for example. The fourth configuration information is a configuration of the second terminal device corresponding to the first radio bearer, or the second terminal device may configure the first radio bearer according to the fourth configuration information. The first radio bearer may be, for example, a sidelink data radio bearer (SLRB), or may also be a Signaling Control Channel (SCCH), or may also introduce an SL-Signaling Radio Bearer (SRB) between terminal devices, and the first radio bearer may also be an SL-SRB.
For example, the network device may send the fourth configuration information to the second terminal device through an RRC connection between the network device and the second terminal device. Alternatively, a dedicated radio bearer (for example, referred to as a second radio bearer) may be established in advance between the first terminal device and the second terminal device, and a dedicated radio bearer (for example, referred to as a third radio bearer) may be established between the first terminal device and the network device, where the second radio bearer is used for transmitting relay information of the second terminal device (i.e., information sent by the second terminal device to the network device, or information sent by the network device to the second terminal device), and the third radio bearer is also used for transmitting relay information of the second terminal device. The network device may also send the fourth configuration information to the first terminal device through the third radio bearer, and the first terminal device may determine, according to the third radio bearer, that the fourth configuration information needs to be forwarded to the second terminal device, and then the first terminal device may send the fourth configuration information to the second terminal device through the second radio bearer.
The fourth configuration information includes, for example, a transmission configuration (referred to as a third transmission configuration, for example) and a common configuration (referred to as a third common configuration, for example). The transmission configuration refers to a configuration related to a transmission procedure, and the common configuration refers to a configuration related to a transmission procedure and/or a reception procedure.
Wherein the third transmission configuration may include one or more of: packet Data Convergence Protocol (PDCP) discard timer (discard timer), robust header compression (RoHC) profile configuration, whether a header of a Service Data Adaptation Protocol (SDAP) is present (or information whether a header of the SDAP is present), mapping relation with a Qos Flow Identity (QFI) on the SL, or a transmission type (e.g., broadcast, unicast, or multicast), etc. For example, the third transmission configuration may include a PDCP discard timer; alternatively, the third transmission configuration may comprise a RoHC compression profile configuration; alternatively, the third sending configuration may include whether a header of the SDAP is present; alternatively, the third transmission configuration may include a mapping relationship with QFI on SL; alternatively, the third transmission configuration may comprise a transmission type (e.g., broadcast, unicast, or multicast); alternatively, the third sending configuration may include various combinations of the above configurations, for example, the third sending configuration may include PDCP discard timer, RoHC compression profile configuration, presence or absence of SDAP header, mapping relationship with QFI on SL, and sending type, etc. Of course, in addition to the above items, the third transmission configuration may also include other information, such as transmission side configuration information on the SDAP, or the PDCP, or the Radio Link Control (RLC), or the Medium Access Control (MAC), or the physical layer (PHY), or the like, or the third transmission configuration does not include any of the above items, but includes other information. The PDCP discard timer may be configured to determine timeliness of a Service Data Unit (SDU) of a sending side. And the RoHC compression profile configuration can be used for determining whether the transmitting side supports the compression configuration. The presence or absence of the SDAP header information may be used to determine SDAP-related configuration. The mapping relation with the QFI on the SL may be used for the transmitting side to determine the configuration corresponding to the traffic flow on the SL. The transmission type may be, for example, broadcast, unicast, multicast, or the like, and may be used for the transmission type configured by the transmitting side.
The third common configuration may include one or more of: sequence Number (SN) length of QFI, PDCP and Radio Link Control (RLC) corresponding to the SDAP, whether header compression is used, or Logical Channel ID (LCID). For example, the third common configuration may include the QFI corresponding to the SDAP; alternatively, the third common configuration may include Sequence Number (SN) lengths of the PDCP and RLC; alternatively, the third command configuration may include an LCID; alternatively, the third command configuration may include various combinations of the above configurations, for example, the third common configuration may include QFI corresponding to the SDAP, SN length of PDCP and RLC, LCID, and whether header compression is used, etc. Of course, in addition to the above items, the third common configuration may include other information, such as configuration information about the same on both sides of the SDAP, or PDCP, or RLC, or MAC, or PHY, or the like, or the third common configuration does not include any of the above items but includes other information. Wherein, the QFI corresponding to the SDAP can be used to indicate the QFI of the corresponding SDAP configuration. The SN length of the PDCP and RLC can be used to indicate the bit number occupied by the SN of the PDCP and RLC data packets.
And S43, the second terminal device configures the first radio bearer according to the fourth configuration information.
For example, the second terminal device configures the first radio bearer according to the third transmission configuration and the third common configuration. For example, the second terminal device may configure the transmission parameters of the first radio bearer according to the third transmission configuration and/or the third common configuration. If the first radio bearer is a bidirectional radio bearer, the second terminal device may further obtain a receiving configuration (for example, referred to as a fourth receiving configuration) of the second terminal device corresponding to the first radio bearer according to the third common configuration, and configure receiving parameters of the first radio bearer according to the fourth receiving configuration, so that the second terminal device can receive information from the first terminal device through the first radio bearer.
In addition, the first radio bearer needs to correspond to a corresponding logical channel in a Medium Access Control (MAC) layer, and which logical channel corresponds to can be determined by the second terminal device, so that the second terminal device can allocate a logical channel to the first radio bearer and determine a Logical Channel ID (LCID) of the logical channel. Alternatively, the logical channel corresponding to the first radio bearer may also be configured directly by the network device, for example, by the fourth configuration information.
For the fourth configuration information from the network device, the network device sends the number of the first radio bearer corresponding to the fourth configuration information together with the fourth configuration information on the Uu port. But for example the second terminal device may communicate with a plurality of terminal devices, and there may be more than one network device sending configuration information to the second terminal device (e.g. the second terminal device always obtains the corresponding sending configuration through the network device corresponding to the terminal device communicating with its PC5 port), or even if there is only one network device, the network device may be duplicated when numbering the radio bearers of different terminal devices communicating for the configured corresponding PC5 port on Uu port, e.g. for the second terminal device, the network device issues one configuration information, for another terminal device, e.g. the third terminal device, the network issues another configuration information, the two configuration information are used to configure two radio bearers for two different terminal devices, and the numbering set by the network device for the two radio bearers corresponding to the two configuration information may be the same, this can lead to confusion for the second terminal device; or, when the network device numbers different sidelink radio bearers of the configured terminal device on the Uu port, there may be duplication, for example, for a second terminal device, the network device issues two pieces of configuration information, where one piece of configuration information is used to configure a radio bearer for the second terminal device to directly communicate with a first terminal device, and the other piece of configuration information is used to configure a radio bearer for the second terminal device to connect to a network through the first terminal device, and numbers set by the network device for the two radio bearers corresponding to the two pieces of configuration information may be the same, which may cause confusion of the second terminal device. Therefore, after receiving the fourth configuration information, the second terminal device may set the number on the PC5 port for the first radio bearer corresponding to the fourth configuration information, that is, the radio bearer configured by the same configuration information corresponds to the number of the Uu port and the number of the PC5, and the two numbers correspond to each other. Of course, the second terminal device may not set the number on the PC5 port for the first radio bearer corresponding to the fourth configuration information, as long as the second terminal device can distinguish that different configuration information from the network device corresponds to different radio bearers.
S44, the second terminal device sends the first configuration information to the first terminal device, and accordingly, the first terminal device receives the first configuration information from the second terminal device.
The first configuration information is a configuration of the first terminal device corresponding to the first radio bearer, or the first terminal device may configure the first radio bearer according to the first configuration information.
The first configuration information includes, for example, a common configuration (e.g., referred to as a first common configuration), for example, the first common configuration is the same as the third common configuration, or the first common configuration is the third common configuration. As for the content included in the first common configuration, the foregoing description of the content included in the third common configuration may be referred to. In addition, the first configuration information may further include an LCID of a logical channel allocated by the second terminal device or the network device for the first radio bearer. And, the first configuration information may further include a number of the first radio bearer on the PC5 port, or a correspondence between the number of the first radio bearer on the PC5 port and the number of the first radio bearer on the Uu port.
Optionally, the second terminal device may further send the type information of the first radio bearer to the first terminal device, and then the first terminal device receives the type information from the second terminal device. The type information of the first radio bearer may indicate, for example, that the first radio bearer is an Acknowledged Mode (AM) or an Unacknowledged Mode (UM), or the type information of the first radio bearer may indicate that the first radio bearer is a unidirectional radio bearer or a bidirectional radio bearer, or the type information of the first radio bearer may indicate that the first radio bearer is an AM or an UM, and indicate that the first radio bearer is a unidirectional radio bearer or a bidirectional radio bearer.
Wherein, AM may indicate that the first radio bearer supports an automatic repeat-request (ARQ) protocol, and UM may indicate that the first radio bearer does not support the ARQ protocol. The unidirectional radio bearer means that the first radio bearer can only transmit in one direction, for example, only the second terminal device can send information to the first terminal device through the first radio bearer, but the first terminal device cannot send information to the second terminal device through the first radio bearer. The bidirectional radio bearer means that the first radio bearer can perform bidirectional transmission, for example, the second terminal device can send information to the first terminal device through the first radio bearer, and the first terminal device can also send information to the second terminal device through the first radio bearer.
S45, the first terminal device configures the first radio bearer according to the first configuration information.
For example, the first terminal device may generate a reception configuration, for example referred to as a first reception configuration, of the first terminal device corresponding to the first radio bearer according to the first common configuration included in the first configuration information. The first terminal device may configure reception parameters of the first radio bearer according to the first reception configuration such that the first terminal device is able to receive information from the second terminal device over the first radio bearer.
If the first terminal device fails to generate the first receiving configuration, or the first terminal device fails to configure the first radio bearer according to the first configuration information, S48 may be continuously performed; or, if the first terminal device successfully generates the first receiving configuration, or the first terminal device successfully configures the first radio bearer according to the first configuration information, and the first radio bearer is a unidirectional radio bearer, the procedure is ended; alternatively, if the first terminal device generates the first receiving configuration successfully, or the first terminal device configures the first radio bearer according to the first configuration information successfully, and the first radio bearer is a bidirectional radio bearer, S46 may be continuously performed.
S46, the first terminal device sends a third request message to the network device, and accordingly, the network device receives the third request message from the first terminal device. The third request message is used for requesting the first terminal device to correspond to the sending configuration of the first radio bearer.
Because the first terminal device only generates the first receiving configuration according to the first configuration information, if the first radio bearer is a bidirectional radio bearer, the first terminal device needs to obtain the sending configuration of the first terminal device corresponding to the first radio bearer, and therefore the first terminal device may request the network device to obtain the sending configuration of the first terminal device corresponding to the first radio bearer.
Optionally, the third request message may further include a QFI, which is, for example, a requirement of the second terminal device for quality of service (QoS) of the first radio bearer, and the network device may determine, according to the QFI, a transmission configuration of the first terminal device corresponding to the first radio bearer. The QFI is, for example, sent by the second terminal device to the first terminal device.
S47, the network device sends the first message to the first terminal device, and accordingly, the first terminal device receives the first message from the network device. The first message may comprise a transmission configuration of the first terminal device corresponding to the first radio bearer, for example referred to as the first transmission configuration.
For example, if the third request message includes the QFI, the first transmission configuration may be determined by the network device from the QFI. Of course, the network device may also refer to other factors when determining the first transmission configuration, and the embodiment of the present application is not limited.
After receiving the first transmission configuration, the first terminal device may configure the transmission parameter of the first radio bearer according to the first transmission configuration, so that the first terminal device may send information to the second terminal device through the first radio bearer, and thus the first radio bearer may have a bidirectional transmission function.
Wherein if the first radio bearer is a unidirectional radio bearer, S46 and S47 do not have to be performed, and thus S46 and S47 are optional steps, indicated by dashed lines in fig. 4.
S48, the first terminal device sends the first configuration failure information to the network device, and accordingly, the network device receives the first configuration failure information from the first terminal device. The first configuration failure information may indicate that the first terminal device failed to configure the first radio bearer.
For example, the first configuration failure information may be carried in an RRC message and sent to the network device, where the RRC message may reuse an existing RRC message, or may be an RRC message newly added in this embodiment of the present application and dedicated to sending the first configuration failure information. If the first configuration failure information is carried in the RRC message, the first configuration failure information may be carried by an existing information element in the RRC message, or a new information element may be added to the RRC message for carrying the first configuration failure information. For example, the first terminal device may send an RRC message to the network device, where the RRC message may include a first information element, and the first configuration failure information may occupy a bit (bit) in the first information element, or the first information element may carry the first configuration failure information, for example, the first information element may use one or more bits to carry the first configuration failure information. The first cell may be an existing cell in the RRC message, for example, the first cell is a cell for indicating a cause of failure, for example, the first cell is an sl-failure (failure) cell, and the first configuration failure information is carried by using the existing cell in the RRC message, so that a new cell does not need to be added to the RRC message, and the RRC message can be better compatible with the existing technology. Or, the first information element may also be an additional information element in the RRC message, and the new information element is used to carry the first configuration failure information, so as to increase the identification degree of the first configuration failure information.
As an alternative, the first configuration failure information may occupy a reserved bit in the first information element. For example, the first cell is an sl-failure cell, which may currently include 4 bits, 2 bits of which are occupied, where the 2 bits are used to indicate a Radio Link Failure (RLF) event and a configuration failure event, respectively, and the remaining 2 bits of the 4 bits are reserved bits. Then, the first configuration failure information may occupy one or two of the 2 reserved bits, for example, the first configuration failure information occupies one of the 2 reserved bits, if the bit takes the value of "1", it indicates that the terminal device has sent the first configuration failure information to the network device, and if the bit takes the value of "0", it indicates that the terminal device has not sent the first configuration failure information to the network device. By this way, the meaning of other bits of the original cell does not need to be changed, and the compatibility with the prior art is facilitated.
Alternatively, although the first cell may be an existing cell, the embodiments of the present application may also make some improvements to the existing cell. For example, the first cell is an sl-failure cell, which may currently include 4 bits, the embodiment of the present application may change the number of bits included in the cell, for example, the number of bits included in the cell is reduced to 2, 2 bits may correspond to 4 values (or 4 states), and each value may indicate one kind of information. For example, a value of "00" for the 2 bits may indicate an RLF event, a value of "01" may indicate a configuration failure event, the two events are existing events at present, and in addition, a value of "10" for the two bits may indicate first configuration failure information, that is, if the value of the two bits is "10", it indicates that the terminal device has sent the first configuration failure information to the network device. The state of these two bits with value "11" may continue to be reserved to indicate other information. By the method, the bit number of the existing cells can be reduced, and the signaling overhead is reduced.
Alternatively, if the first cell is an existing cell, the embodiment of the present application may also extend the bit number of the first cell, for example, one or more new bits are added to the first cell to carry the first configuration failure information.
Optionally, the first configuration failure information may further include information of the first radio bearer, where the information of the first radio bearer is, for example, a SL-DRB ID or a Uu DRB ID of the first radio bearer, or the information of the first radio bearer may also be an address of a terminal device corresponding to the first radio bearer on the sidelink, for example, a (layer 2, L2) destination address of the second terminal device.
In the embodiment of the present application, although the first configuration information is not sent by the network device to the first terminal device, but sent by the second terminal device to the first terminal device, if the first terminal device fails to configure, it may be specified that the first terminal device sends the first configuration failure information to the network device, so as to reduce the back-and-forth transmission of information.
S49, the first terminal device sends the second configuration failure information to the second terminal device, and accordingly, the second terminal device receives the second configuration failure information from the first terminal device. The second configuration failure information may indicate that the first terminal device failed to configure the first radio bearer.
In addition to sending the first configuration failure information to the network device, the first terminal device may also send the second configuration failure information to the second terminal device because the first configuration information is sent to the first terminal device by the second terminal device. After receiving the second configuration failure information from the first terminal device, the second terminal device can determine that the first terminal device fails to configure the first radio bearer, so that the second terminal device may temporarily communicate with the first terminal device without passing through the first radio bearer.
In addition, after receiving the second configuration failure information, the second terminal device does not trigger forwarding of the second configuration failure information to the network device, so that repeated transmission of the configuration failure information is avoided.
S48 may occur before S49, or S48 may occur after S49, or S48 and S49 may occur simultaneously.
Where S49 is an optional step, indicated by the dashed line in fig. 4.
In the embodiment of the application, if the first terminal device fails to configure, the first terminal device may send the first configuration failure information to the network device, that is, the first terminal device does not need to send the first configuration failure information to the second terminal device, and then the second terminal device forwards the first configuration failure information to the network through the first terminal device, so that a forwarding process of the first configuration failure information is reduced, and transmission resources are saved. And because the first configuration failure information does not need to be transmitted back and forth between the terminal devices, the transmission delay is also reduced.
In order to solve the same technical problem, the present embodiment provides a second communication method, please refer to fig. 5, which is a flowchart of the method. In the following description, the method is applied to the network architecture shown in fig. 2 as an example. The scenario shown in fig. 2 is a relay scenario, or the embodiment of the present application may also be used in a scenario in which two terminal devices are directly connected, instead of the relay scenario, for example, if the first terminal device can communicate with the second terminal device, the second terminal device is in an OOC state, or the second terminal device is not provided with a Uu port, and the first terminal device is in a network coverage state, the network device serving the first terminal device can provide configuration information for the second terminal device.
For ease of description, in the following, the method is performed by a network device and a terminal device as an example. Since the embodiment of the present application is applied to the network architecture shown in fig. 2 as an example. Therefore, the network device described below may be an access network device in the network architecture shown in fig. 2, the first terminal device described below may be the terminal device 1 in the network architecture shown in fig. 2, and the second terminal device described below may be the terminal device 2 in the network architecture shown in fig. 2.
S51, the first terminal device and the second terminal device establish a PC5-S connection. After establishing the PC5-S connection, the first terminal device and the second terminal device may communicate over a sidelink.
S52, the network device sends the fourth configuration information to the second terminal device, and the second terminal device receives the fourth configuration information from the network device accordingly.
The fourth configuration information includes, for example, a transmission configuration (referred to as a third transmission configuration, for example) and a common configuration (referred to as a third common configuration, for example). The transmission configuration refers to a configuration related to a transmission procedure, and the common configuration refers to a configuration related to a transmission procedure and/or a reception procedure. Optionally, if the first radio bearer is a bidirectional radio bearer, the fourth configuration information may further include a reception configuration (for example, referred to as a fourth reception configuration). The reception configuration refers to a configuration related to a reception procedure. For example, the fourth receive configuration may include a PDCP reordering timer (reordering timer), although other parameters may be included.
For more about S52, reference may be made to the description of S42 in the embodiment shown in fig. 4.
And S53, the second terminal equipment configures the first radio bearer.
For example, the second terminal device configures the first radio bearer according to the fourth configuration information. For example, the second terminal device may configure the transmission parameters of the first radio bearer according to the third transmission configuration and/or the third common configuration, so that the second terminal device can transmit information to the first terminal device over the first radio bearer. If the first radio bearer is a bidirectional radio bearer and the fourth configuration information further includes a fourth reception configuration, the second terminal device may further configure reception parameters of the first radio bearer according to the third common configuration and/or the fourth reception configuration, so that the second terminal device can receive information from the first terminal device through the first radio bearer.
In addition, the first radio bearer needs to correspond to the corresponding logical channel at the MAC layer, and which logical channel corresponds to can be determined by the second terminal device, so the second terminal device can allocate the logical channel for the first radio bearer and determine the LCID of the logical channel. Or, the first radio bearer may also be directly configured by the network device in a logical channel corresponding to the MAC layer, for example, the first radio bearer is sent to the second terminal device through the fourth configuration information.
In addition, after receiving the fourth configuration information, the second terminal device may set a number on the PC5 port for the first radio bearer corresponding to the fourth configuration information, that is, the radio bearer configured by the same configuration information corresponds to the number of the Uu port and the number of the PC5, and the two numbers correspond to each other. Of course, the second terminal device may not set the number on the PC5 port for the first radio bearer corresponding to the fourth configuration information, as long as the second terminal device can distinguish that different configuration information from the network device corresponds to different radio bearers.
Or, after receiving the fourth configuration information, if the second terminal device sets the number on the PC5 port for the first radio bearer, the second terminal device may also set the corresponding relationship between the QFI and the number of the first radio bearer on the PC5 port; alternatively, if the second terminal device does not set a number on the PC5 port for the first radio bearer, the second terminal device may also set a correspondence between the QFI and the number on the Uu port for the first radio bearer. The QFI is, for example, a QoS requirement of the second terminal device for the first radio bearer.
For more about S53, reference may be made to the description of S43 in the embodiment shown in fig. 4.
S54, the network device sends the second configuration information to the first terminal device, and accordingly, the first terminal device receives the second configuration information from the network device.
The second configuration information includes, for example, a reception configuration (referred to as a second reception configuration, for example) and a common configuration (referred to as a second common configuration, for example). The reception configuration refers to a configuration related to a reception procedure, and the common configuration refers to a configuration related to a transmission procedure and/or a reception procedure. For example, the second reception configuration may include a PDCP reordering timer (reordering timer), although other parameters may be included. Optionally, if the first radio bearer is a bidirectional radio bearer, the second configuration information may further include a transmission configuration (for example, referred to as a second transmission configuration).
In addition, the first radio bearer needs to correspond to a corresponding logical channel in the MAC layer, and may be sent by the second terminal device through the first information. Or, the first radio bearer may also be directly configured by the network device in a logical channel corresponding to the MAC layer, for example, the logical channel is sent to the first terminal device through the second configuration information.
Regarding more of S54, reference may be made to the description of S42 in the embodiment shown in fig. 4, and it is only necessary to replace "fourth configuration information" in S44 with "second configuration information", "third transmission configuration" with "second transmission configuration", and "third common configuration" with "second common configuration".
Wherein S52 may be performed before S54, or S52 may be performed after S54, or S52 may be performed simultaneously with S54.
S55, the second terminal device sends the first information to the first terminal device, and accordingly, the first terminal device receives the first information from the second terminal device.
The first information includes, for example, an LCID of a logical channel corresponding to the first radio bearer, where the LCID is determined in S53 by the second terminal device, or is used to indicate that the first radio bearer is configured completely, so as to avoid that the first terminal device and the second terminal device do not know whether the other terminal device is configured completely. Alternatively, the LCID corresponding to the first radio bearer may also be configured by the network device, for example, the network device may send the second configuration information to the first terminal device, and then the first information does not include the LCID. Optionally, the first information may further include a first corresponding relationship, or include a second corresponding relationship, or include the first corresponding relationship and the second corresponding relationship. The first corresponding relationship is, for example, the corresponding relationship between the number of the first radio bearer on the Uu port and the number of the first radio bearer on the PC5 port; the second corresponding relationship is, for example, a corresponding relationship between the QFI and the number of the first wireless bearer on the PC5 port, or a corresponding relationship between the QFI and the number of the first wireless bearer on the Uu port.
And S56, the first terminal equipment obtains the first configuration information according to the second configuration information and the first information.
For example, the first configuration information may include the second configuration information and the first information.
S57, the first terminal device configures the first radio bearer according to the first configuration information.
For example, the first terminal device may configure the transmission parameters of the first radio bearer according to the first common configuration and/or the first transmission configuration included in the first configuration information, so that the first terminal device can transmit information to the second terminal device through the first radio bearer. If the first configuration information further comprises the first reception configuration, the first terminal device may configure reception parameters of the first radio bearer according to the first reception configuration and/or the first common configuration, so that the first terminal device can receive information from the second terminal device through the first radio bearer.
If the first terminal equipment successfully configures the first radio bearer according to the first configuration information, the process is ended; alternatively, if the first terminal device fails to configure the first radio bearer according to the first configuration information, the step S58 is continuously performed.
S58, the first terminal device sends the first configuration failure information to the network device, and accordingly, the network device receives the first configuration failure information from the first terminal device. The first configuration failure information may indicate that the first terminal device failed to configure the first radio bearer.
In the embodiment of the application, since the second configuration information is sent by the network device to the first terminal device, if the first terminal device fails to configure, the first configuration failure information is equivalent to response information sent by the first terminal device to the network device, and the process is more natural and conforms to the execution habit of the device.
For more about S58, reference may be made to the description of S48 in the embodiment shown in fig. 4.
S59, the first terminal device sends the second configuration failure information to the second terminal device, and accordingly, the second terminal device receives the second configuration failure information from the first terminal device. The second configuration failure information may indicate that the first terminal device failed to configure the first radio bearer.
Although the second configuration information is not sent by the second terminal device to the first terminal device, but is sent by the network device to the first terminal device, if the first terminal device fails to configure, it may be specified that the first terminal device also sends the second configuration failure information to the second terminal device. After receiving the second configuration failure information from the first terminal device, the second terminal device can determine that the first terminal device fails to configure the first radio bearer, so that the second terminal device may temporarily communicate with the first terminal device without passing through the first radio bearer.
In addition, after receiving the second configuration failure information, the second terminal device does not trigger forwarding of the second configuration failure information to the network device, so that repeated transmission of the configuration failure information is avoided.
S58 may occur before S59, or S58 may occur after S59, or S58 and S59 may occur simultaneously.
Where S59 is an optional step, indicated by the dashed line in fig. 5.
In the embodiment of the application, if the first terminal device fails to configure, the first terminal device may send the first configuration failure information to the network device, that is, the first terminal device does not need to send the first configuration failure information to the second terminal device, and then the second terminal device forwards the first configuration failure information to the network through the first terminal device, so that a forwarding process of the first configuration failure information is reduced, and transmission resources are saved. And because the first configuration failure information does not need to be transmitted back and forth between the terminal devices, the transmission delay is also reduced. And the network device can send the configuration information corresponding to the first radio bearer to the two terminal devices respectively, and the terminal devices do not need to generate the configuration information additionally, so that the burden of the terminal devices is reduced, the application range of the method provided by the embodiment of the application is wider, and the method can be applied to more terminal devices with low cost.
In order to solve the same technical problem, the present embodiment provides a second communication method, please refer to fig. 6, which is a flowchart of the method. In the following description, the method is applied to the network architecture shown in fig. 2 as an example. The scenario shown in fig. 2 is a relay scenario, or the embodiment of the present application may also be used in a scenario in which two terminal devices are directly connected, instead of the relay scenario, for example, if the first terminal device can communicate with the second terminal device, the second terminal device is in an OOC state, or the second terminal device is not provided with a Uu port, and the first terminal device is in a network coverage state, the network device serving the first terminal device can provide configuration information for the second terminal device.
For ease of description, in the following, the method is performed by a network device and a terminal device as an example. Since the embodiment of the present application is applied to the network architecture shown in fig. 2 as an example. Therefore, the network device described below may be an access network device in the network architecture shown in fig. 2, the first terminal device described below may be the terminal device 1 in the network architecture shown in fig. 2, and the second terminal device described below may be the terminal device 2 in the network architecture shown in fig. 2.
S61, the first terminal device and the second terminal device establish a PC5-S connection. After establishing the PC5-S connection, the first terminal device and the second terminal device may communicate over a sidelink.
S62, the second terminal device sends the QoS information to the first terminal device, and accordingly, the first terminal device receives the QoS information from the second terminal device.
The QoS information may indicate a requirement of the second terminal device for QoS of the first radio bearer. The QoS information may include QFI, for example, or may also include other information.
For example, the second terminal device may transmit the QoS information to the first terminal device through a PC5-RRC message, or the second terminal device may transmit the QoS information to the first terminal device through another message.
S63, the first terminal device sends the second information to the network device, and accordingly, the network device receives the second information from the first terminal device. The second information may be used to request configuration of a radio bearer between the first terminal device and the second terminal device, and the radio bearer is a bidirectional radio bearer. This radio bearer is for example referred to as the first radio bearer. For the description of the implementation of the first radio bearer, etc., reference may be made to the relevant contents in the embodiment shown in fig. 4.
Generally, which terminal device determines that information needs to be sent to the peer, the terminal device may send information for requesting configuration of the first radio bearer to the network device. In this embodiment of the present application, actually, the second terminal device should be a sender of information, that is, the second terminal device is to send information to the first terminal device, as in the embodiment shown in fig. 4 or the embodiment shown in fig. 5, but both the embodiment shown in fig. 4 and the embodiment shown in fig. 5 are that the second terminal device sends a second request message to the network device to request the network device to configure the first radio bearer. In this embodiment, it may be considered that the first terminal device regards the first terminal device as a sending end of the information by sending the second information to the network device, and then the network device sends the configuration information of the first radio bearer to the first terminal device. In this way, if the first terminal device fails to configure, the first terminal device may send information indicating that the configuration fails to configure to the network device, so that the execution of the whole process is more in line with the execution habit of the device.
In this embodiment of the present application, the first terminal device makes the network device regard the first terminal device as a sending end of the information, when the network device sends the configuration information, the network device sends a sending configuration corresponding to the first radio bearer to the first terminal device, and the first terminal device configures the first radio bearer according to the sending configuration, so that the first terminal device can send the information to the second terminal device. In this embodiment of the present application, the second information needs to request to configure a bidirectional radio bearer, that is, the first radio bearer needs to be a radio bearer capable of performing bidirectional transmission, so that a requirement that the second terminal device sends information to the first terminal device through the first radio bearer can be met.
Optionally, the second information may include the QoS information, because the second terminal device is an actual information sender, the QoS requirement of the second terminal device for the first radio bearer should be used as a criterion. After receiving the QoS information, the network device may determine configuration information of the first radio bearer according to the QoS information, so that the configured first radio bearer can better meet the requirement of the second terminal device.
Optionally, the second information may further include information that the second terminal device is in an OOC state, or information that the second terminal device does not set the Uu port. When the second terminal device is in an OOC state or a Uu port is not set, the network where the second terminal device is located cannot configure a radio bearer for the second terminal device, and in this case, if the second terminal device can access the network where the first terminal device is located through the first terminal device, the network where the second terminal device is located can configure a radio bearer for the first terminal device, and the like. If it is determined that the second terminal device is in the OOC state or that the second terminal device does not set the Uu port, the first terminal device may send the second information to the access network device, and if it is determined that the second terminal device is not in the OOC state currently or that the second terminal device sets the Uu port, the first terminal device may not send the second information to the access network device, that is, if the second terminal device is not in the OOC state currently or that the second terminal device sets the Uu port, the network where the second terminal device is located may configure a radio bearer for the second terminal device, and the like. Or, in this embodiment of the present application, whether the second terminal device is currently in the OOC state or not, the first terminal device may send the second information to the access network device to request to configure the radio bearer. If this is the case, the second information may include information that the second terminal device is in the OOC state, or may not include information that the second terminal device is in the OOC state.
The second information may be Sidelink UE Information (SUI), for example, or other types of information.
And S64, the network equipment determines the first configuration information according to the second information. The first configuration information is configuration information of the first terminal device corresponding to the first radio bearer, or the first terminal device is capable of configuring the first radio bearer according to the first configuration information.
The first configuration information includes, for example, a transmission configuration (referred to as a first transmission configuration, for example) and a common configuration (referred to as a first common configuration, for example). As for the content included in the first transmission configuration, reference may be made to the description of the third transmission configuration in the embodiment shown in fig. 4, and as for the content included in the first common configuration, reference may be made to the description of the third common configuration in the embodiment shown in fig. 4.
Optionally, the first configuration information may further include a receiving configuration (for example, referred to as a first receiving configuration).
S65, the network device sends the first configuration information to the first terminal device, and accordingly, the first terminal device receives the first configuration information from the network device.
For example, the network device may send the first configuration information to the first terminal device via an RRC message.
S66, the first terminal device configures the first radio bearer according to the first configuration information.
For example, the first terminal device configures the first radio bearer according to the first transmission configuration and the first common configuration. For example, the first terminal device may configure the transmission parameters of the first radio bearer according to the first transmission configuration and/or the first common configuration, so that the first terminal device can transmit information to the second terminal device over the first radio bearer. Since the first radio bearer is a bidirectional radio bearer, if the first configuration information does not include the first receiving configuration, the first terminal device may further obtain the first receiving configuration according to the first common configuration, and configure the receiving parameters of the first radio bearer according to the first receiving configuration, so that the first terminal device can receive information from the second terminal device through the first radio bearer. Alternatively, if the first configuration information includes the first reception configuration, the first terminal device may configure the reception parameters of the first radio bearer according to the first reception configuration and/or the first common configuration, so that the first terminal device can receive information from the second terminal device through the first radio bearer.
If the first terminal device fails to configure the first radio bearer according to the first configuration information, S68 may be performed; alternatively, if the first terminal device successfully configures the first radio bearer according to the first configuration information, S67 may be performed; or, S67 is independent of whether the first terminal device is successfully configured, and S67 may be performed regardless of whether the first terminal device is successfully or unsuccessfully configured for the first radio bearer according to the first configuration information, and if this is the case, S66 may be performed before S67, or S66 may be performed after S67, or S66 may be performed simultaneously with S67.
S67, the first terminal device sends the third configuration information to the second terminal device, and accordingly, the second terminal device receives the third configuration information from the first terminal device. The third configuration information may be used by the second terminal device to configure the first radio bearer, or the second terminal device may configure the first radio bearer according to the third configuration information.
The third configuration information includes, for example, a part of or the entire content of the first configuration information. For example, the third configuration information may include the first common configuration, or the third configuration information may include the first common configuration and the first transmission configuration.
After receiving the third configuration information, the second terminal device may configure the first radio bearer according to the third configuration information. For example, if the third configuration information includes the first common configuration, the second terminal device may obtain a receiving configuration (for example, referred to as a third receiving configuration) corresponding to the first radio bearer by the second terminal device according to the first common configuration, and the second terminal device may configure receiving parameters of the first radio bearer according to the third receiving configuration, so that the second terminal device can receive information from the first terminal device through the first radio bearer. For another example, the third configuration information includes a first common configuration and a first sending configuration, and the second terminal device may obtain the first receiving configuration according to the first common configuration and configure the first radio bearer according to the first receiving configuration, and may also configure the sending parameters of the first radio bearer according to the first sending configuration, so that the second terminal device can send information to the first terminal device through the first radio bearer.
S68, the first terminal device sends the first configuration failure information to the network device, and accordingly, the network device receives the first configuration failure information from the first terminal device. The first configuration failure information may indicate that the first terminal device failed to configure the first radio bearer.
In the embodiment of the application, since the first configuration information is sent by the network device to the first terminal device, if the first terminal device fails to configure, the first configuration failure information is equivalent to response information sent by the first terminal device to the network device, and the first configuration failure information is more natural in flow and conforms to the execution habit of the device.
For more about S68, reference may be made to the description of S48 in the embodiment shown in fig. 4.
S69, the first terminal device sends the second configuration failure information to the second terminal device, and accordingly, the second terminal device receives the second configuration failure information from the first terminal device. The second configuration failure information may indicate that the first terminal device failed to configure the first radio bearer.
For example, if S67 is performed, S69 may be performed, and thus S69 is an optional step, indicated by a dotted line in fig. 6. Although the first configuration information is not sent by the second terminal device to the first terminal device, but sent by the network device to the first terminal device, if the first terminal device fails to configure, it may be specified that the first terminal device also sends the second configuration failure information to the second terminal device. After receiving the second configuration failure information from the first terminal device, the second terminal device can determine that the first terminal device fails to configure the first radio bearer, so that the second terminal device may temporarily communicate with the first terminal device without passing through the first radio bearer.
In addition, after receiving the second configuration failure information, the second terminal device does not trigger forwarding of the second configuration failure information to the network device, so that repeated transmission of the configuration failure information is avoided.
S68 may occur before S69, or S68 may occur after S69, or S68 and S69 may occur simultaneously.
In the embodiment of the application, if the first terminal device fails to configure, the first terminal device may send the first configuration failure information to the network device, that is, the first terminal device does not need to send the first configuration failure information to the second terminal device, and then the second terminal device forwards the first configuration failure information to the network through the first terminal device, so that a forwarding process of the first configuration failure information is reduced, and transmission resources are saved. And because the first configuration failure information does not need to be transmitted back and forth between the terminal devices, the transmission delay is also reduced. And the network equipment sends the first configuration information to the first terminal equipment, and the first terminal equipment sends the third configuration information to the second terminal equipment, so that the situation that the configuration information is transmitted back and forth between the terminal equipment can be avoided.
As described above, the terminal device configures the radio bearer and processes the radio bearer after a configuration failure occurs. Configuration failure can be considered one case of sidelink failure, which is yet another case, RLF.
For example, for a sidelink to which the ARQ mechanism applies, the second terminal device sends data to the first terminal device through the sidelink, and the first terminal device sends feedback information to the second terminal device after receiving the data from the second terminal device, where the feedback information may indicate that the data reception is successful or failed. Then, if the feedback information received by the second terminal device indicates that the corresponding data has failed to be received, the second terminal device may resend the data to the first terminal device through the sidelink, and the first terminal device may resend the feedback information to the second terminal device after receiving the data. If the retransmission times reach the maximum times limited by the ARQ mechanism and the data still fails to be transmitted, the second terminal device may consider that the RLF event occurs; alternatively, if the number of consecutive retransmissions of one or more data is a transmission failure when the maximum number of ARQ mechanisms is reached, the second terminal device may consider that an RLF event has occurred.
For another example, for a sidelink to which the ARQ mechanism is applied, the second terminal device sends data to the first terminal device through the sidelink, and after the first terminal device receives the data from the second terminal device, if the reception is successful, the first terminal device sends feedback information to the second terminal device, where the feedback information may indicate that the data reception is successful, and if the reception is unsuccessful, the first terminal device does not send the feedback information to the second terminal device. Then, if the second terminal device receives the feedback information, it indicates that the corresponding data reception is successful, and if the second terminal device does not receive the feedback information, it indicates that the corresponding data reception is failed. If the first terminal device fails to receive the data, the second terminal device can resend the data to the first terminal device through the side link, after the first terminal device receives the data, if the data is received successfully, feedback information is sent to the second terminal device, the feedback information can indicate that the data is received successfully, and if the data is received unsuccessfully, the feedback information is not sent to the second terminal device. If the second terminal device still does not receive the feedback information, the second terminal device resends the data to the first terminal device through the sidelink again, and so on until the first terminal device receives the data successfully, or until the retransmission times are equal to the maximum times limited by the ARQ mechanism. If the retransmission times reach the maximum times limited by the ARQ mechanism and the data still fails to be transmitted, the second terminal device may consider that the RLF event occurs; alternatively, if the number of consecutive retransmissions of one or more data is a transmission failure when the maximum number of ARQ mechanisms is reached, the second terminal device may consider that an RLF event has occurred.
Consider the scenario illustrated in fig. 2, where terminal device 1 provides a relay service for terminal device 2. For example, terminal device 2 is a data sending end, and terminal device 1 is a data receiving end, and refer to fig. 7, which is a processing flow of terminal device 2 after an RLF event occurs.
S71, a PC 5-signal (S) connection is established between the terminal equipment 1 and the terminal equipment 2.
S72, terminal device 1 determines that the sidelink between terminal device 1 and terminal device 2 has failed. For example, the terminal device 1 determines that an RLF event has occurred.
S73, terminal device 2 sends information of link failure to terminal device 1, so as to forward the information of link failure to the network device through terminal device 1.
The terminal device 2 needs to send the information of the link failure to the network device, but the communication between the terminal device 2 and the network device needs to be relayed through the terminal device 1, so the terminal device 2 sends the information of the link failure to the terminal device 1, and the terminal device 1 forwards the information of the link failure to the network device.
However, since an RLF event has occurred at this time, indicating that a problem has occurred in the sidelink between terminal device 1 and terminal device 2, and normal communication may not be possible, terminal device 1 may not receive information of a link failure from terminal device 2, and an "x" in fig. 7 indicates that S73 may have performed a failure, and terminal device 1 naturally cannot forward the information of the link failure to the network device. It can be seen that this results in the terminal device 2 generating information of the link failure, which additionally increases the power consumption of the terminal device 2.
In view of this, embodiments of the present application provide a fourth communication method, by which power consumption of a terminal device can be reduced. Please refer to fig. 8, which is a flowchart of the method. The method may be applied to the network architecture shown in fig. 2, or the method may also be applied to a network architecture in which two terminal devices are directly connected, that is, the first terminal device does not provide the relay service for the second terminal device, and the two terminal devices communicate through a sidelink. In the following description, the method is applied to the network architecture shown in fig. 2 as an example. The scenario shown in fig. 2 is a relay scenario, or the embodiment of the present application may also be used in a scenario in which two terminal devices are directly connected, instead of the relay scenario, for example, if the first terminal device can communicate with the second terminal device, the second terminal device is in an OOC state, or the second terminal device is not provided with a Uu port, and the first terminal device is in a network coverage state, the network device serving the first terminal device can provide configuration information for the second terminal device.
For ease of description, in the following, the method is performed by a network device and a terminal device as an example. Since the embodiment of the present application is applied to the network architecture shown in fig. 2 as an example. Therefore, the network device described below may be an access network device in the network architecture shown in fig. 2, the first terminal device described below may be the terminal device 1 in the network architecture shown in fig. 2, and the second terminal device described below may be the terminal device 2 in the network architecture shown in fig. 2.
S81, the first terminal device and the second terminal device establish a PC5-S connection. After establishing the PC5-S connection, the first terminal device and the second terminal device may communicate over a sidelink.
S82, the second terminal device determines that the sidelink between the first terminal device and the second terminal device fails, for example, the second terminal device determines that the sidelink has an RLF event.
In addition, the second terminal device is in an OOC state, or the second terminal device is not provided with a Uu port. If the second terminal device is in the coverage of the network device and the second terminal device has the Uu port, the second terminal device may send information indicating a link failure to the network device through the Uu port, and in this case, the technical solution provided in the embodiment of the present application may not be used. If the second terminal device is in the OOC state or the second terminal device is not provided with the Uu port, the two conditions can be applied to the technical solution provided by the embodiment of the present application as long as either or both of the two conditions are satisfied.
S83, the second terminal device does not send information indicating the link failure to the network device. The information indicating the link failure is, for example, a SL-RLF report.
That is, the second terminal device does not send information indicating a link failure to the network device when determining that the sidelink has failed, and therefore the second terminal device does not need to generate information indicating a link failure, thereby reducing power consumption of the second terminal device. Moreover, since a problem has occurred in the sidelink between the first terminal device and the second terminal device, if the second terminal device sends information indicating a link failure to the first terminal device through the sidelink, the information may also be sent to the first terminal device in a failure.
And S84, the second terminal equipment determines that the connection with the network equipment fails.
The second terminal device may determine that the connection with the network device has failed if it determines that the sidelink with the second terminal device has failed. Wherein S83 may be performed before S84, or S83 may be performed after S84, or S83 may be performed simultaneously with S84.
In addition, S84 may not be performed, but S85 or S86 to be described later may be performed, or none of S84 to S86 may be necessarily performed. Thus, S84-S86 are optional steps, represented by dashed lines in FIG. 8.
S85, the second terminal device sends the first request message to the first terminal device, and accordingly, the first terminal device receives the first request message from the second terminal device.
The first request message may be used to request that the sidelink be reestablished. For example, if the technical solution of the embodiment of the present application is applied to a scenario in which two terminal devices are directly connected, that is, not used in a relay scenario, the first terminal device and the second terminal device need to communicate normally. In this case, if the sidelink fails, the second terminal device may request to reestablish the sidelink, so that the first terminal device and the second terminal device can resume normal communication as much as possible.
And S86, the second terminal equipment reselects the terminal equipment capable of providing the relay service for the second terminal equipment.
For example, if the technical solution of the embodiment of the present application is applied to a relay scenario, for example, a first terminal device provides a relay service for a second terminal device. Then, if the sidelink between the first terminal device and the second terminal device fails, the first terminal device may also re-access the network device through other terminal devices, and thus the second terminal device may reselect a terminal device capable of providing the relay service for the second terminal device.
For example, the second terminal device may transmit a broadcast message requesting a relay service. If the terminal device receiving the broadcast message can provide the relay service for the second terminal device, the terminal device may send a response message to the second terminal device, and after receiving the response message from the other terminal device, the second terminal device may establish a sidelink with the terminal device, so as to access the network through the terminal device. If a plurality of terminal devices all send response messages to the second terminal device, the second terminal device may establish a sidelink with the terminal device that sent the first response message, for example, the response message that the second terminal device first received.
By the technical scheme provided by the embodiment of the application, the terminal equipment can be prevented from assembling useless SL-RLF reports as much as possible, air interface signaling is saved, and the method is a more effective exception handling mode.
The following describes an apparatus for implementing the above method in the embodiment of the present application with reference to the drawings. Therefore, the above contents can be used in the subsequent embodiments, and the repeated contents are not repeated.
Fig. 9 is a schematic block diagram of a communication device 900 according to an embodiment of the present application. Exemplarily, the communication apparatus 900 is, for example, a first terminal device 900. Illustratively, the first terminal device 900 is, for example, the first terminal device described in any one of the embodiments shown in fig. 4 to fig. 6.
The first terminal device 900 comprises a processing module 910 and a receiving module 930. Optionally, the first terminal device 900 may further include a sending module 920. Illustratively, the first terminal device 900 may be a terminal device, and may also be a chip applied in the terminal device or other combined devices, components, and the like having the above-mentioned first terminal device function. When the first terminal device 900 is a terminal device, the transmitting module 920 may be a transmitter, the transmitter may include an antenna, a radio frequency circuit, and the like, the receiving module 930 may be a receiver, the receiver may include an antenna, a radio frequency circuit, and the like, wherein the transmitter and the receiver may be different modules, respectively, or the transmitter and the receiver may be disposed in the same functional module, which may be called a transceiver, and the processing module 910 may be a processor (or processing circuit), such as a baseband processor, which may include one or more Central Processing Units (CPUs). When the first terminal device 900 is a component having the above-mentioned function of the first terminal device, the sending module 920 may be a radio frequency unit, and the receiving module may also be a radio frequency unit, wherein the transmitter and the receiver may be different modules respectively, or the transmitter and the receiver may be disposed in the same functional module, which may be a radio frequency unit, and the processing module 910 may be a processor (or a processing circuit), such as a baseband processor. When the first terminal device 900 is a chip system, the transmitting module 920 may be an output interface of a chip (e.g., a baseband chip), the receiving module 930 may be an input interface of the chip (or, if the input interface and the output interface may be the same interface, the transmitting module 920 and the receiving module 930 are considered to be the same functional module, i.e., an input-output interface of the chip), the processing module 910 may be a processor (or, a processing circuit) of the chip system, and the processor may include one or more central processing units. It should be understood that the processing module 910 in the embodiments of the present application may be implemented by a processor or a processor-related circuit component (or, a processing circuit), the receiving module 930 may be implemented by a transceiver or a transceiver-related circuit component, and the sending module 920 may be implemented by a transmitter or a transmitter-related circuit component.
For example, the processing module 910 may be used to perform all operations performed by the first terminal device in the embodiment shown in fig. 4 except transceiving operations, e.g., S41 and S45, and/or other processes for supporting the techniques described herein. The transmitting module 920 may be used to perform all of the transmitting operations performed by the first terminal device in the embodiment shown in fig. 4, e.g., S41, S46, S48, and S49, and/or other processes for supporting the techniques described herein. The receiving module 930 may be configured to perform all receiving operations performed by the first terminal device in the embodiment shown in fig. 4, e.g., S41, S44, and S47, and/or other processes for supporting the techniques described herein.
For another example, the processing module 910 may be used to perform all operations performed by the first terminal device in the embodiment shown in fig. 5 except transceiving operations, e.g., S51, S56, and S57, and/or other processes for supporting the techniques described herein. The transmitting module 920 may be used to perform all of the transmitting operations performed by the first terminal device in the embodiment shown in fig. 5, e.g., S51, S58, and S59, and/or other processes for supporting the techniques described herein. The receiving module 930 may be configured to perform all receiving operations performed by the first terminal device in the embodiment shown in fig. 5, such as S51, S54, and S55, and/or other processes for supporting the techniques described herein.
As another example, the processing module 910 may be used to perform all operations performed by the first terminal device in the embodiment shown in fig. 6, except transceiving operations, such as S61 and S66, and/or other processes for supporting the techniques described herein. The transmitting module 920 may be used to perform all transmitting operations performed by the first terminal device in the embodiment shown in fig. 6, e.g., S61, S63, S67, S68, and S69, and/or other processes for supporting the techniques described herein. The receiving module 930 may be configured to perform all receiving operations performed by the first terminal device in the embodiment shown in fig. 6, e.g., S61, S62, and S65, and/or other processes for supporting the techniques described herein.
In addition, the transmitting module 920 and the receiving module 930 may be one functional module, which can perform both the transmitting operation and the receiving operation, and may be referred to as a transceiver module, for example, the transceiver module may be used to perform all the transmitting operation and the receiving operation performed by the first terminal device in any one of the embodiments shown in fig. 4 to fig. 6, for example, the transceiver module may be considered as the transmitting module when performing the transmitting operation, and the transceiver module may be considered as the receiving module when performing the receiving operation; alternatively, the sending module 920 and the receiving module 930 may also be two functional modules, the transceiving module may also be regarded as a general term for the two functional modules, the sending module 920 is configured to complete the sending operation, for example, the sending module 920 may be configured to perform all sending operations performed by the first terminal device in any one of the embodiments shown in fig. 4 to fig. 6, and the receiving module 930 is configured to complete the receiving operation, for example, the receiving module 930 may be configured to perform all receiving operations performed by the first terminal device in any one of the embodiments shown in fig. 4 to fig. 6.
The processing module 910 is configured to obtain first configuration information, where the first configuration information is used for configuring a first radio bearer by a first terminal device 900, the first radio bearer is a radio bearer between the first terminal device 900 and a second terminal device, and the second terminal device is a data sending end;
a processing module 910, further configured to configure the first radio bearer according to the first configuration information;
a sending module 920, configured to send first configuration failure information to a network device when the processing module 910 fails to configure the first radio bearer.
As an optional implementation manner, the sending module 920 is configured to send the first configuration failure information to the network device by:
sending an RRC message to a network device, wherein the RRC message comprises a first information element, the first configuration failure information occupies reserved bits in the first information element, and the first information element is used for indicating a failure reason.
As an optional implementation manner, the sending module 920 is further configured to send second configuration failure information to the second terminal device, where the second configuration failure information is used to indicate that the first terminal device 900 fails to configure the first radio bearer.
As an optional implementation, the processing module 910 is configured to obtain the first configuration information by:
the first configuration information from the second terminal device is received by the receiving module 930.
As an optional implementation manner, the first configuration information includes a first common configuration, and the first common configuration includes one or more of the following: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
As an optional implementation, the processing module 910 is configured to obtain the first configuration information by:
receiving, by the receiving module 930, second configuration information from the network device;
receiving, by the receiving module 930, first information from the second terminal device, where the first information includes an identifier of a logical channel corresponding to the first radio bearer;
and obtaining the first configuration information according to the second configuration information and the first information.
As an optional implementation manner, the first information is obtained by the second terminal device according to fourth configuration information from the network device, and the fourth configuration information is used by the second terminal device to configure the first radio bearer.
As an optional implementation manner, the first information further includes a QFI corresponding to the first radio bearer, and/or a correspondence between an identifier corresponding to the first radio bearer at the Uu port and an identifier corresponding to the PC5 port.
As an optional implementation manner, the second configuration information includes a receiving configuration and a second common configuration, where the receiving configuration includes a PDCP reordering timer, and the second common configuration includes one or more of the following: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
As an alternative to the above-described embodiment,
a receiving module 930, further configured to receive QoS information from the second terminal device before the processing module 910 obtains the first configuration information, where the QoS information is used to indicate a QoS of a radio bearer requested to be configured between the second terminal device and the first terminal device 900;
the sending module 920 is further configured to send second information to the network device, where the second information is used to request to configure a radio bearer for bidirectional transmission between the second terminal device and the first terminal device 900, and the second information includes the QoS information.
As an optional implementation, the processing module 910 is configured to obtain the first configuration information by:
the first configuration information is received from the network device through the receiving module 930.
As an optional implementation manner, the first configuration information includes a first sending configuration and a first common configuration, wherein,
the first transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the first common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
As an optional implementation manner, the sending module 920 is further configured to send third configuration information to the second terminal device, where the third configuration information is used for the second terminal device to configure the first radio bearer, and the third configuration information includes a part of content or all content of the first configuration information.
Regarding other functions that can be implemented by the first terminal device 900, reference may be made to related descriptions of any one of the embodiments shown in fig. 4 to fig. 6, and details are not repeated.
Fig. 10 is a schematic block diagram of a communication device 1000 according to an embodiment of the present application. Exemplarily, the communication apparatus 1000 is, for example, a second terminal device 1000. Exemplarily, the second terminal device 1000 is, for example, the second terminal device described in any one of the embodiments shown in fig. 4 to fig. 6.
The second terminal device 1000 includes a transmitting module 1020 and a receiving module 1030. Optionally, the second terminal device may further include a processing module 1010. The second terminal device 1000 may be a terminal device, or may be a chip applied in the terminal device or other combined devices, components, and the like having the functions of the second terminal device. When the second terminal device 1000 is a terminal device, the transmitting module 1020 may be a transmitter, the transmitter may include an antenna, a radio frequency circuit, and the like, the receiving module 1030 may be a receiver, the receiver may include an antenna, a radio frequency circuit, and the like, wherein the transmitter and the receiver may be different modules, respectively, or the transmitter and the receiver may be disposed in the same functional module, which may be called a transceiver, and the processing module 1010 may be a processor (or processing circuit), such as a baseband processor, which may include one or more CPUs. When the second terminal device 1000 is a component having the functions of the second terminal device, the transmitting module 1020 may be a radio frequency unit, and the receiving module may also be a radio frequency unit, wherein the transmitter and the receiver may be different modules respectively, or the transmitter and the receiver may be disposed in the same functional module, which may be a radio frequency unit, and the processing module 1010 may be a processor (or a processing circuit), such as a baseband processor. When the second terminal device 1000 is a chip system, the transmitting module 1020 may be an output interface of a chip (e.g., a baseband chip), the receiving module 1030 may be an input interface of the chip (or, if the input interface and the output interface may be the same interface, the transmitting module 1020 and the receiving module 1030 are considered to be the same functional module, i.e., an input-output interface of the chip), the processing module 1010 may be a processor (or, a processing circuit) of the chip system, and the processor may include one or more central processing units. It should be understood that the processing module 1010 in the embodiments of the present application may be implemented by a processor or a processor-related circuit component (or, a processing circuit), the receiving module 1030 may be implemented by a transceiver or a transceiver-related circuit component, and the transmitting module 1020 may be implemented by a transmitter or a transmitter-related circuit component.
For example, the processing module 1010 may be used to perform all operations performed by the second terminal device in the embodiment shown in fig. 4 except transceiving operations, e.g., S41 and S43, and/or other processes for supporting the techniques described herein. The transmitting module 1020 may be used to perform all of the transmitting operations performed by the second terminal device in the embodiment shown in fig. 4, e.g., S41 and S44, and/or other processes for supporting the techniques described herein. The receiving module 1030 may be used to perform all receiving operations performed by the second terminal device in the embodiment shown in fig. 4, e.g., S41, S42, and S49, and/or other processes for supporting the techniques described herein.
As another example, the processing module 1010 may be used to perform all operations performed by the second terminal device in the embodiment shown in fig. 5 except transceiving operations, e.g., S51 and S53, and/or other processes for supporting the techniques described herein. The transmitting module 1020 may be used to perform all of the transmitting operations performed by the second terminal device in the embodiment shown in fig. 5, e.g., S51 and S55, and/or other processes for supporting the techniques described herein. The receiving module 1030 may be used to perform all receiving operations performed by the second terminal device in the embodiment shown in fig. 5, e.g., S51, S52, and S59, and/or other processes for supporting the techniques described herein.
As another example, the processing module 1010 may be used to perform all operations performed by the second terminal device in the embodiment shown in fig. 6, except for transceiving operations, such as S61, and/or other processes for supporting the techniques described herein. The transmitting module 1020 may be used to perform all of the transmitting operations performed by the second terminal device in the embodiment shown in fig. 6, e.g., S61 and S62, and/or other processes for supporting the techniques described herein. The receiving module 1030 may be used to perform all receiving operations performed by the second terminal device in the embodiment shown in fig. 6, e.g., S61, S67, and S69, and/or other processes for supporting the techniques described herein.
In addition, regarding the implementation manners of the transmitting module 1020 and the receiving module 1030, reference may be made to the introduction of the implementation manners of the transmitting module 920 and the receiving module 930.
A receiving module 1030, configured to receive second configuration failure information from a first terminal device, where the second configuration failure information is used to indicate that the first terminal device fails to configure a first radio bearer, where the first radio bearer is a radio bearer between the first terminal device and a second terminal device 1000, the first terminal device provides a relay service for the second terminal device 1000, the first terminal device is a data receiving end of a data transmission process performed through the first radio bearer, and the second terminal device 1000 is a data sending end of the data transmission process;
A sending module 1020, configured to not send, to a network device, information indicating that the first terminal device fails to configure the first radio bearer.
As an optional implementation manner, the receiving module 1030 is further configured to receive fourth configuration information from the network device, where the fourth configuration information is used by the second terminal device 1000 to configure the first radio bearer.
As an optional implementation manner, the fourth configuration information includes a third sending configuration and a third common configuration, wherein,
the third transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the third common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
As an alternative to the above-described embodiment,
a processing module 1010 configured to select a logical channel for the first radio bearer;
the sending module 1020 is further configured to send first configuration information to the first terminal device, where the first configuration information is used for the first terminal device to configure the first radio bearer, and the first configuration information includes an identifier of a logical channel corresponding to the first radio bearer.
As an optional implementation manner, the first configuration information includes a first common configuration, and the first common configuration includes one or more of the following: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
As an alternative to the above-described embodiment,
a processing module 1010 configured to select a logical channel for the first radio bearer;
the sending module 1020 is further configured to send first information to the first terminal device, where the first information includes an identifier of a logical channel corresponding to the first radio bearer.
As an optional implementation manner, the first information further includes a QFI corresponding to the first radio bearer, and/or a correspondence between an identifier corresponding to the first radio bearer at the Uu port and an identifier corresponding to the PC5 port.
As an optional implementation manner, the receiving module 1030 is further configured to receive third configuration information from the first terminal device, where the third configuration information is used by the second terminal device 1000 to configure the first radio bearer, the third configuration information includes a part of or all of content of first configuration information, and the first configuration information is used by the first terminal device to configure the first radio bearer.
As an optional implementation manner, the sending module 1020 is further configured to send QoS information to the first terminal device, where the QoS information is used to indicate that QoS of a radio bearer configured between the second terminal device 1000 and the first terminal device is requested.
As an alternative implementation, the second terminal device 1000 cannot communicate with the network device through the Uu port.
Regarding other functions that can be implemented by the second terminal device 1000, reference may be made to related descriptions of any one of the embodiments shown in fig. 4 to fig. 6, which are not repeated herein.
Fig. 11 is a schematic block diagram of a communication device 1100 provided in an embodiment of the present application. Illustratively, the communication apparatus 1100 is, for example, a network device 1100. Illustratively, the network device 1100 is, for example, the network device described in any one of the embodiments shown in fig. 4 to fig. 6.
Network device 1100 includes a processing module 1110 and a receiving module 1130. Optionally, the network device 1100 further includes a sending module 1120. Illustratively, the network device 1100 may be a network device (e.g., an access network device), a chip applied in the network device, or other combined devices, components, etc. having the functions of the network device. When the network device 1100 is a network device, the transmitting module 1120 may be a transmitter, the transmitter may include an antenna, a radio frequency circuit, and the like, the receiving module 1130 may be a receiver, the receiver may include an antenna, a radio frequency circuit, and the like, wherein the transmitter and the receiver may be different modules, respectively, or the transmitter and the receiver may be disposed in the same functional module, which may be called a transceiver, and the processing module 1110 may be a processor (or processing circuit), such as a baseband processor, which may include one or more CPUs therein. When the network device 1100 is a component having the above-mentioned network device function, the transmitting module 1120 may be a radio frequency unit, and the receiving module may also be a radio frequency unit, wherein the transmitter and the receiver may be different modules respectively, or the transmitter and the receiver may be disposed in the same functional module, which may be a radio frequency unit, and the processing module 1110 may be a processor (or a processing circuit), such as a baseband processor. When the network device 1100 is a chip system, the transmitting module 1120 may be an output interface of a chip (e.g., a baseband chip), the receiving module 1130 may be an input interface of the chip (or, if the input interface and the output interface may be the same interface, the transmitting module 1120 and the receiving module 1130 are considered to be the same functional module, i.e., an input-output interface of the chip), and the processing module 1110 may be a processor (or, a processing circuit) of the chip system, and the processor may include one or more central processing units. It is understood that the processing module 1110 in the embodiments of the present application may be implemented by a processor or a processor-related circuit component (or, a processing circuit), the receiving module 1130 may be implemented by a transceiver or a transceiver-related circuit component, and the transmitting module 1120 may be implemented by a transmitter or a transmitter-related circuit component.
For example, processing module 1110 may be used to perform all operations performed by the network device in the embodiment shown in fig. 4 except transceiving operations, such as operations to determine fourth configuration information, and/or other processes to support the techniques described herein. The transmitting module 1120 may be used to perform all of the transmitting operations performed by the network device in the embodiment shown in fig. 4, e.g., S42 and S47, and/or other processes for supporting the techniques described herein. The receiving module 1130 may be used to perform all receiving operations performed by the network device in the embodiment shown in fig. 4, such as S46 and S48, and/or other processes for supporting the techniques described herein.
As another example, processing module 1110 may be used to perform all operations performed by a network device in the embodiment shown in fig. 5 except transceiving operations, such as operations to determine fourth configuration information, and/or other processes to support the techniques described herein. The transmitting module 1120 may be used to perform all of the transmitting operations performed by the network device in the embodiment shown in fig. 5, e.g., S52 and S54, and/or other processes for supporting the techniques described herein. The receiving module 1130 may be used to perform all receiving operations performed by a network device in the embodiment shown in fig. 5, such as S58, and/or other processes for supporting the techniques described herein.
As another example, processing module 1110 may be used to perform all operations performed by a network device in the embodiment shown in fig. 6, except for transceiving operations, e.g., S64, and/or other processes for supporting the techniques described herein. The transmitting module 1120 may be used to perform all of the transmitting operations performed by the network device in the embodiment shown in fig. 6, e.g., S65, and/or other processes for supporting the techniques described herein. The receiving module 1130 may be used to perform all receiving operations performed by a network device in the embodiment shown in fig. 6, such as S63 and S68, and/or other processes for supporting the techniques described herein.
In addition, regarding the implementation of the transmitting module 1120 and the receiving module 1130, reference may be made to the description of the implementation of the transmitting module 920 and the receiving module 930.
The receiving module 1130 is configured to receive first configuration failure information from the first terminal device;
a processing module 1110, configured to determine that the first terminal device fails to configure a first radio bearer according to the first configuration failure information, where the first radio bearer is a radio bearer between the first terminal device and a second terminal device, the first terminal device provides a relay service for the second terminal device, the first terminal device is a data receiving end of a data transmission process performed through the first radio bearer, and the second terminal device is a data sending end of the data transmission process.
As an optional implementation manner, the receiving module 1130 is configured to receive the first configuration failure information from the first terminal device by:
receiving an RRC message from the first terminal equipment, wherein the RRC message comprises a first information element, the first configuration failure information occupies reserved bits in the first information element, and the first information element is used for indicating a failure reason.
As an optional implementation manner, the sending module 1120 is configured to send fourth configuration information to the second terminal device, where the fourth configuration information is used by the second terminal device to configure the first radio bearer.
As an optional implementation manner, the fourth configuration information includes a third sending configuration and a third common configuration, wherein,
the third transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the third common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
As an optional implementation manner, the sending module 1120 is configured to send second configuration information to the first terminal device, where the second configuration information is used for the first terminal device to configure the first radio bearer.
As an optional implementation manner, the second configuration information includes a receiving configuration and a second common configuration, where the receiving configuration includes a PDCP reordering timer, and the second common configuration includes one or more of the following: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
As an optional implementation manner, the receiving module 1130 is further configured to receive second information from the first terminal device, where the second information is used to request to configure a radio bearer for bidirectional transmission between the second terminal device and the first terminal device, and the second information includes QoS information, where the QoS information is used to indicate QoS of the radio bearer requested to be configured between the second terminal device and the first terminal device.
As an alternative to the above-described embodiment,
a processing module 1110, further configured to determine first configuration information according to the QoS information, where the first configuration information is used for configuring the first radio bearer by the first terminal device;
a sending module 1120, configured to send the first configuration information to the first terminal device.
As an optional implementation manner, the first configuration information includes a first sending configuration and a first common configuration, wherein,
The first transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the first common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
For other functions that can be implemented by the network device 1100, reference may be made to related descriptions of any one of the embodiments shown in fig. 4 to fig. 6, which are not repeated herein.
Fig. 12 is a schematic block diagram of a communication device 1200 according to an embodiment of the present application. Exemplarily, the communication apparatus 1200 is, for example, the second terminal device 1200. Illustratively, the second terminal device 1200 is, for example, the second terminal device described in the embodiment shown in fig. 8.
The second terminal device 1200 includes a transmitting module 1220 and a processing module 1210. Optionally, the second terminal device 1200 further includes a receiving module 1230. The second terminal device 1200 may be a terminal device, or may be a chip applied in the terminal device or other combined devices, components, and the like having the functions of the second terminal device. When the second terminal device 1200 is a terminal device, the transmitting module 1220 may be a transmitter, the transmitter may include an antenna, a radio frequency circuit, and the like, the receiving module 1230 may be a receiver, the receiver may include an antenna, a radio frequency circuit, and the like, wherein the transmitter and the receiver may be different modules, respectively, or the transmitter and the receiver may be disposed in the same functional module, which may be called a transceiver, and the processing module 1210 may be a processor (or processing circuit), such as a baseband processor, which may include one or more CPUs. When the second terminal device 1200 is a component having the functions of the second terminal device, the transmitting module 1220 may be a radio frequency unit, and the receiving module may also be a radio frequency unit, wherein the transmitter and the receiver may be different modules respectively, or the transmitter and the receiver may be disposed in the same functional module, which may be a radio frequency unit, and the processing module 1210 may be a processor (or processing circuit), such as a baseband processor. When the second terminal apparatus 1200 is a chip system, the transmitting module 1220 may be an output interface of a chip (e.g., a baseband chip), the receiving module 1230 may be an input interface of the chip (or, if the input interface and the output interface may be the same interface, the transmitting module 1220 and the receiving module 1230 are considered to be the same functional module, i.e., an input-output interface of the chip), the processing module 1210 may be a processor (or, a processing circuit) of the chip system, and the processor may include one or more central processing units. It is to be understood that the processing module 1210 in the embodiments of the present application may be implemented by a processor or a processor-related circuit component (or, a processing circuit), the receiving module 1230 may be implemented by a transceiver or a transceiver-related circuit component, and the sending module 1220 may be implemented by a transmitter or a transmitter-related circuit component.
For example, the processing module 1210 may be used to perform all operations performed by the second terminal device in the embodiment shown in fig. 8 except transceiving operations, such as S81, S82-S84, and S86, and/or other processes for supporting the techniques described herein. The transmitting module 1220 may be used to perform all of the transmitting operations performed by the second terminal device in the embodiment shown in fig. 8, e.g., S81 and S85, and/or other processes for supporting the techniques described herein. The receiving module 1230 may be configured to perform all receiving operations performed by the second terminal device in the embodiment shown in fig. 8, such as S81, and/or other processes for supporting the techniques described herein.
In addition, regarding the implementation of the transmitting module 1220 and the receiving module 1230, reference may be made to the description of the implementation of the transmitting module 920 and the receiving module 930.
The processing module 1210 is configured to determine that a link between a first terminal device and a second terminal device 1200 fails, and the second terminal device is not within a network coverage;
a sending module 1220, configured to not send information indicating a link failure to the network device.
As an optional implementation manner, the sending module 1220 is further configured to send a request message to the first terminal device to request to reestablish the link.
As an optional implementation manner, the first terminal device provides a relay service for the second terminal device 1200, and the processing module 1210 is further configured to reselect a terminal device capable of providing the relay service for the second terminal device 1200.
For other functions that can be implemented by the second terminal device 1200, reference may be made to the related description of the embodiment shown in fig. 8, and details are not repeated.
The embodiment of the application also provides a communication device, and the communication device can be terminal equipment or a circuit. The communication apparatus may be configured to perform the actions performed by the terminal device (e.g., the first device may be a terminal device) in the above-described method embodiments.
When the communication apparatus is a terminal device, fig. 13 shows a simplified structural diagram of the terminal device. For easy understanding and illustration, in fig. 13, the terminal device is exemplified by a mobile phone. As shown in fig. 13, the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input-output device. The processor is mainly used for processing communication protocols and communication data, controlling the terminal equipment, executing software programs, processing data of the software programs and the like. The memory is used primarily for storing software programs and data. The radio frequency circuit is mainly used for converting baseband signals and radio frequency signals and processing the radio frequency signals. The antenna is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are used primarily for receiving data input by a user and for outputting data to the user. It should be noted that some kinds of terminal devices may not have input/output devices.
When data needs to be sent, the processor performs baseband processing on the data to be sent and outputs baseband signals to the radio frequency circuit, and the radio frequency circuit performs radio frequency processing on the baseband signals and sends the radio frequency signals to the outside in the form of electromagnetic waves through the antenna. When data is sent to the terminal equipment, the radio frequency circuit receives radio frequency signals through the antenna, converts the radio frequency signals into baseband signals and outputs the baseband signals to the processor, and the processor converts the baseband signals into the data and processes the data. For ease of illustration, only one memory and processor are shown in FIG. 13. In an actual end device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be provided independently of the processor, or may be integrated with the processor, which is not limited in this embodiment.
In the embodiment of the present application, an antenna and a radio frequency circuit having a transceiving function may be regarded as a transceiving unit of a terminal device (the transceiving unit may be a functional unit, and the functional unit is capable of implementing a transmitting function and a receiving function, or the transceiving unit may also include two functional units, which are respectively a receiving unit capable of implementing a receiving function and a transmitting unit capable of implementing a transmitting function), and a processor having a processing function may be regarded as a processing unit of the terminal device. As shown in fig. 13, the terminal device includes a transceiving unit 1310 and a processing unit 1320. A transceiver unit may also be referred to as a transceiver, a transceiving device, etc. A processing unit may also be referred to as a processor, a processing board, a processing module, a processing device, or the like. Alternatively, a device for implementing the receiving function in the transceiving unit 1310 may be regarded as a receiving unit, and a device for implementing the transmitting function in the transceiving unit 1310 may be regarded as a transmitting unit, that is, the transceiving unit 1310 includes a receiving unit and a transmitting unit. A transceiver unit may also sometimes be referred to as a transceiver, transceiving circuitry, or the like. A receiving unit may also be referred to as a receiver, a receiving circuit, or the like. A transmitting unit may also sometimes be referred to as a transmitter, or a transmitting circuit, etc.
It should be understood that the transceiving unit 1310 may be configured to perform the transmitting operation and the receiving operation on the first terminal device side in the embodiment shown in fig. 4, and the processing unit 1320 is configured to perform other operations besides the transceiving operation on the first terminal device in the embodiment shown in fig. 4.
Alternatively, the transceiving unit 1310 may be configured to perform the transmitting operation and the receiving operation on the second terminal device side in the embodiment shown in fig. 4, and the processing unit 1320 is configured to perform other operations besides the transceiving operation on the second terminal device in the embodiment shown in fig. 4.
Alternatively, the transceiving unit 1310 may be configured to perform the transmitting operation and the receiving operation on the first terminal device side in the embodiment shown in fig. 5, and the processing unit 1320 is configured to perform other operations besides the transceiving operation on the first terminal device in the embodiment shown in fig. 5.
Alternatively, the transceiving unit 1310 may be configured to perform the transmitting operation and the receiving operation on the second terminal device side in the embodiment shown in fig. 5, and the processing unit 1320 is configured to perform other operations besides the transceiving operation on the second terminal device in the embodiment shown in fig. 5.
Alternatively, the transceiving unit 1310 may be configured to perform the transmitting operation and the receiving operation on the first terminal device side in the embodiment shown in fig. 6, and the processing unit 1320 is configured to perform other operations besides the transceiving operation on the first terminal device in the embodiment shown in fig. 6.
Alternatively, the transceiving unit 1310 may be configured to perform the transmitting operation and the receiving operation on the second terminal device side in the embodiment shown in fig. 6, and the processing unit 1320 is configured to perform other operations besides the transceiving operation on the second terminal device in the embodiment shown in fig. 6.
Alternatively, the transceiving unit 1310 may be configured to perform the transmitting operation and the receiving operation on the second terminal device side in the embodiment shown in fig. 8, and the processing unit 1320 is configured to perform other operations besides the transceiving operation on the second terminal device in the embodiment shown in fig. 8.
When the communication device is a chip-like device or circuit, the device may comprise a transceiver unit and a processing unit. The transceiver unit may be an input/output circuit and/or a communication interface; the processing unit is an integrated processor or microprocessor or integrated circuit.
When the communication device in this embodiment is a terminal device, reference may be made to the device shown in fig. 14. As an example, the device may perform functions similar to the processing module 910 of FIG. 9. For example, the processing module 910 in the above embodiments may be the processor 1410 in fig. 14, and performs the corresponding functions; the sending module 920 in the above embodiments may be the sending data processor 1420 in fig. 14, and performs corresponding functions; the receiving module 930 in the above embodiments may be the received data processor 1430 in fig. 14, and performs corresponding functions. For another example, the processing module 1010 in the above embodiments may be the processor 1410 in fig. 14, and performs the corresponding functions; the sending module 1020 in the above embodiments may be the sending data processor 1420 in fig. 14, and performs corresponding functions; the receiving module 1030 in the above embodiments may be the received data processor 1430 in fig. 14, and performs corresponding functions. As another example, the processing module 1210 in the above embodiments may be the processor 1410 in fig. 14, and performs corresponding functions; the sending module 1220 in the above embodiments may be the sending data processor 1420 in fig. 14, and performs the corresponding functions; the receiving module 1230 in the above embodiments may be the received data processor 1430 in fig. 14, and performs corresponding functions. Although fig. 14 shows a channel encoder and a channel decoder, it is understood that these blocks are not limitative and only illustrative to the present embodiment.
Fig. 15 shows another form of the present embodiment. The processing device 1500 includes modules such as a modulation subsystem, a central processing subsystem, and peripheral subsystems. The communication device in this embodiment may serve as a modulation subsystem therein. In particular, the modulation subsystem may include a processor 1503 and an interface 1504. The processor 1503 performs the functions of the processing module 910, and the interface 1504 performs the functions of the sending module 920 and the receiving module 930. Alternatively, the processor 1503 performs the functions of the processing module 1010, and the interface 1504 performs the functions of the sending module 1020 and the receiving module 1030. Alternatively, the processor 1503 performs the functions of the processing module 1210, and the interface 1504 performs the functions of the sending module 1220 and the receiving module 1230. As another variation, the modulation subsystem includes a memory 1506, a processor 1503, and a program stored in the memory 1506 and executable on the processor, and the processor 1503 executes the program to implement the method of the terminal device side in the above method embodiments. It should be noted that the memory 1506 may be non-volatile or volatile, and may be located within the modulation subsystem or within the processing device 1500, as long as the memory 1506 is connected to the processor 1503.
When the device in the embodiment of the present application is a network device, the device may be as shown in fig. 16. The apparatus 1600 includes one or more radio frequency units, such as a Remote Radio Unit (RRU) 1610 and one or more baseband units (BBUs) (also referred to as digital units, DUs) 1620. The RRU 1610 may be referred to as a transceiver module, which may include a transmitting module and a receiving module, or may be a module capable of performing transmitting and receiving functions. The transceiving module may correspond to the transmitting module 1120 and the receiving module 1130 in fig. 11. Alternatively, the transceiver module may also be referred to as a transceiver, a transceiver circuit, or a transceiver, etc., which may include at least one antenna 1611 and the rf unit 1612. The RRU 1610 portion is mainly used for transceiving radio frequency signals and converting the radio frequency signals into baseband signals, for example, for sending indication information to a terminal device. The BBU 1620 is mainly used for performing baseband processing, controlling a base station, and the like. The RRU 1610 and the BBU 1620 may be physically located together or physically located separately, that is, distributed base stations.
The BBU 1620 is a control center of the base station, and may also be referred to as a processing module, and may correspond to the processing module 1110 in fig. 11, and is mainly used for performing baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and the like. For example, the BBU (processing module) may be configured to control the base station to perform an operation procedure related to the network device in the foregoing method embodiment, for example, to generate the foregoing indication information.
In an example, the BBU 1620 may be formed by one or more boards, and the multiple boards may collectively support a radio access network of a single access system (e.g., an LTE network), or may respectively support radio access networks of different access systems (e.g., an LTE network, a 5G network, or other networks). BBU 1620 also includes a memory 1621 and a processor 1622. The memory 1621 is used to store the necessary instructions and data. The processor 1622 is configured to control the base station to perform necessary actions, for example, to control the base station to execute the operation procedure related to the network device in the above method embodiment. The memory 1621 and processor 1622 may serve one or more boards. That is, the memory and processor may be provided separately on each board. Multiple boards may share the same memory and processor. In addition, each single board can be provided with necessary circuits.
The embodiment of the application provides a first communication system. The first communication system may include the first terminal device according to any one of the embodiments shown in fig. 4 to 6, the second terminal device according to any one of the embodiments shown in fig. 4 to 6, and the network device according to any one of the embodiments shown in fig. 4 to 6. The first terminal device is, for example, the first terminal device 900 in fig. 9, the second terminal device is, for example, the second terminal device 1000 in fig. 10, and the network device is, for example, the network 1100 in fig. 11.
The embodiment of the application provides a second communication system. The first communication system may include the second terminal device according to the embodiment shown in fig. 8 described above. The second terminal device is, for example, the second terminal device 1200 in fig. 12.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a computer, the computer may implement the process related to the first terminal device in the embodiment shown in fig. 4 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a computer, the computer may implement the process related to the second terminal device in the embodiment shown in fig. 4 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a computer, the computer may implement the process related to the network device in the embodiment shown in fig. 4 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a computer, the computer may implement the process related to the first terminal device in the embodiment shown in fig. 5 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a computer, the computer may implement the process related to the second terminal device in the embodiment shown in fig. 5 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a computer, the computer may implement the process related to the network device in the embodiment shown in fig. 5 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a computer, the computer may implement the process related to the first terminal device in the embodiment shown in fig. 6 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a computer, the computer may implement the process related to the second terminal device in the embodiment shown in fig. 6 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a computer, the computer may implement the process related to the network device in the embodiment shown in fig. 6 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a computer, the computer may implement the process related to the second terminal device in the embodiment shown in fig. 8 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer program product, where the computer program is used to store a computer program, and when the computer program is executed by a computer, the computer may implement the flow related to the first terminal device in the embodiment shown in fig. 4 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer program product, where the computer program is used to store a computer program, and when the computer program is executed by a computer, the computer may implement the flow related to the second terminal device in the embodiment shown in fig. 4 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer program product, where the computer program is used to store a computer program, and when the computer program is executed by a computer, the computer may implement the process related to the network device in the embodiment shown in fig. 4 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer program product, where the computer program is used to store a computer program, and when the computer program is executed by a computer, the computer may implement the flow related to the first terminal device in the embodiment shown in fig. 5 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer program product, where the computer program is used to store a computer program, and when the computer program is executed by a computer, the computer may implement the flow related to the second terminal device in the embodiment shown in fig. 5 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer program product, where the computer program is used to store a computer program, and when the computer program is executed by a computer, the computer may implement the process related to the network device in the embodiment shown in fig. 5 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer program product, where the computer program is used to store a computer program, and when the computer program is executed by a computer, the computer may implement the flow related to the first terminal device in the embodiment shown in fig. 6 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer program product, where the computer program is used to store a computer program, and when the computer program is executed by a computer, the computer may implement the flow related to the second terminal device in the embodiment shown in fig. 6 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer program product, where the computer program is used to store a computer program, and when the computer program is executed by a computer, the computer may implement the process related to the network device in the embodiment shown in fig. 6 and provided by the foregoing method embodiment.
An embodiment of the present application further provides a computer program product, where the computer program is used to store a computer program, and when the computer program is executed by a computer, the computer may implement the flow related to the second terminal device in the embodiment shown in fig. 8 and provided by the foregoing method embodiment.
It should be understood that the processor mentioned in the embodiments of the present application may be a CPU, and may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It will also be appreciated that the memory referred to in the embodiments of the application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM).
It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, the memory (memory module) is integrated in the processor.
It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, some of the latter of the technical solutions of the present application may be fully embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the methods described in the embodiments of the present application. The computer readable storage medium can be any available medium that can be accessed by a computer. Taking this as an example but not limiting: a computer-readable medium may include a Random Access Memory (RAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a compact disk read-only memory (CD-ROM), a universal serial bus flash disk (universal serial bus flash disk), a removable hard disk, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
The above description is only for the specific implementation of the present application, but the scope of the embodiments of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the embodiments of the present application, and all the changes or substitutions should be covered by the scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.
In combination with the above, the present application also provides the following embodiments:
embodiment 1, a communication method, comprising:
obtaining first configuration information, where the first configuration information is used for a first terminal device to configure a first radio bearer, where the first radio bearer is a radio bearer between the first terminal device and a second terminal device, and the second terminal device is a data sending end;
configuring the first radio bearer according to the first configuration information;
and when the first radio bearer configuration fails, sending first configuration failure information to network equipment.
Embodiment 2, according to the method of embodiment 1, sending first configuration failure information to a network device, includes:
sending an RRC message to a network device, wherein the RRC message comprises a first information element, the first configuration failure information occupies reserved bits in the first information element, and the first information element is used for indicating a failure reason.
Embodiment 3, the method of embodiment 1 or embodiment 2, further comprising:
and sending second configuration failure information to the second terminal equipment, wherein the second configuration failure information is used for indicating that the first terminal equipment fails to configure the first radio bearer.
Embodiment 4, the method of any one of embodiments 1 to 3, wherein obtaining the first configuration information comprises:
receiving the first configuration information from the second terminal device.
Embodiment 5 the method of embodiment 4, wherein the first configuration information includes a first common configuration, the first common configuration including one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 6, the method of any of embodiments 1 to 3, wherein obtaining the first configuration information comprises:
receiving second configuration information from the network device;
receiving first information from the second terminal device, where the first information includes an identifier of a logical channel corresponding to the first radio bearer;
and obtaining the first configuration information according to the second configuration information and the first information.
Embodiment 7 and the method according to embodiment 6, wherein the first information is obtained by the second terminal device according to fourth configuration information from the network device, and the fourth configuration information is used by the second terminal device to configure the first radio bearer.
Embodiment 8, according to the method of embodiment 6 or embodiment 7, the first information further includes a QFI corresponding to the first radio bearer, and/or a correspondence between an identifier corresponding to the first radio bearer at the Uu port and an identifier corresponding to the PC5 port.
Embodiment 9, the method according to any of embodiments 6 to 8, wherein the second configuration information includes a receiving configuration and a second common configuration, the receiving configuration includes a PDCP reordering timer, and the second common configuration includes one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 10, the method according to any of embodiments 1 to 3, further comprising, before obtaining the first configuration information:
receiving QoS information from the second terminal device, the QoS information indicating a QoS for a radio bearer requested to be configured between the second terminal device and the first terminal device;
And sending second information to the network equipment, wherein the second information is used for requesting to configure a radio bearer for bidirectional transmission between the second terminal equipment and the first terminal equipment, and the second information comprises the QoS information.
Embodiment 11, the method of embodiment 10, wherein obtaining the first configuration information comprises:
receiving the first configuration information from the network device.
Embodiment 12 the method of embodiment 10 or embodiment 11, wherein the first configuration information comprises a first transmit configuration and a first common configuration, wherein,
the first transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the first common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 13, the method of embodiment 11 or embodiment 12, further comprising:
and sending third configuration information to the second terminal device, where the third configuration information is used for the second terminal device to configure the first radio bearer, and the third configuration information includes part of or all of the content of the first configuration information.
Embodiment 14, a communication method, comprising:
receiving second configuration failure information from a first terminal device, where the second configuration failure information is used to indicate that the first terminal device fails to configure a first radio bearer, the first radio bearer is a radio bearer between the first terminal device and a second terminal device, the first terminal device provides a relay service for the second terminal device, the first terminal device is a data receiving end of a data transmission process performed through the first radio bearer, and the second terminal device is a data sending end of the data transmission process;
and not sending information for indicating that the first terminal equipment fails to configure the first radio bearer to network equipment.
Embodiment 15, the method of embodiment 14, further comprising:
receiving fourth configuration information from the network device, where the fourth configuration information is used by the second terminal device to configure the first radio bearer.
Embodiment 16 the method of embodiment 15, wherein the fourth configuration information comprises a third transmit configuration and a third common configuration, wherein,
the third transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
The third common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 17, the method of embodiment 15 or embodiment 16, further comprising:
selecting a logical channel for the first radio bearer;
and sending first configuration information to the first terminal device, where the first configuration information is used for the first terminal device to configure the first radio bearer, and the first configuration information includes an identifier of a logical channel corresponding to the first radio bearer.
Embodiment 18, the method of embodiment 17, wherein the first configuration information comprises a first common configuration comprising one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 19, the method of embodiment 15 or embodiment 16, further comprising:
selecting a logical channel for the first radio bearer;
and sending first information to the first terminal equipment, wherein the first information comprises the identifier of the logical channel corresponding to the first radio bearer.
Embodiment 20, the method of embodiment 19, wherein the first information further includes a QFI corresponding to the first radio bearer, and/or a correspondence between an identifier corresponding to the first radio bearer at the Uu port and an identifier corresponding to the PC5 port.
Embodiment 21, the method of embodiment 14, further comprising:
receiving third configuration information from the first terminal device, where the third configuration information is used by the second terminal device to configure the first radio bearer, the third configuration information includes partial content or all content of first configuration information, and the first configuration information is used by the first terminal device to configure the first radio bearer.
Embodiment 22, the method of embodiment 21, further comprising:
and sending QoS information to the first terminal equipment, wherein the QoS information is used for indicating the QoS of the radio bearer which is configured between the second terminal equipment and the first terminal equipment.
Embodiment 23 and the method as in any one of embodiments 14 to 22, wherein the second terminal device is unable to communicate with the network device via the Uu port.
Embodiment 24, a method of communication, comprising:
receiving first configuration failure information from a first terminal device;
determining that the first terminal device fails to configure a first radio bearer according to the first configuration failure information, where the first radio bearer is a radio bearer between the first terminal device and a second terminal device, the first terminal device provides a relay service for the second terminal device, the first terminal device is a data receiving end of a data transmission process performed through the first radio bearer, and the second terminal device is a data transmitting end of the data transmission process.
Embodiment 25 and the method of embodiment 24, wherein receiving the first configuration failure information from the first terminal device includes:
receiving an RRC message from the first terminal equipment, wherein the RRC message comprises a first information element, the first configuration failure information occupies reserved bits in the first information element, and the first information element is used for indicating a failure reason.
Embodiment 26, the method of embodiment 24 or embodiment 25, further comprising:
and sending fourth configuration information to the second terminal equipment, wherein the fourth configuration information is used for the second terminal equipment to configure the first radio bearer.
Embodiment 27 the method of embodiment 26, wherein the fourth configuration information comprises a third transmit configuration and a third common configuration, wherein,
the third transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the third common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 28, the method of any of embodiments 24-26, further comprising:
And sending second configuration information to the first terminal equipment, wherein the second configuration information is used for the first terminal equipment to configure the first radio bearer.
Embodiment 29 the method of embodiment 28, wherein the second configuration information comprises a receive configuration and a second common configuration, wherein the receive configuration comprises a PDCP reordering timer, and wherein the second common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 30, the method of embodiment 24 or embodiment 25, further comprising:
and receiving second information from the first terminal equipment, wherein the second information is used for requesting to configure the radio bearer for bidirectional transmission between the second terminal equipment and the first terminal equipment, and the second information comprises QoS information which is used for indicating the QoS of the radio bearer requested to be configured between the second terminal equipment and the first terminal equipment.
Embodiment 31, the method of embodiment 30, further comprising:
determining first configuration information according to the QoS information, wherein the first configuration information is used for the first terminal equipment to configure the first radio bearer;
And sending the first configuration information to the first terminal equipment.
Embodiment 32 the method of embodiment 31, wherein the first configuration information comprises a first transmit configuration and a first common configuration, wherein,
the first transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the first common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 33, a method of communication, comprising:
the method comprises the steps that a second terminal device determines that a link between a first terminal device and the second terminal device fails, and the second terminal device is not in a network coverage range;
the second terminal device does not send information indicating a link failure to the network device.
Embodiment 34 the method of embodiment 33, further comprising:
and the second terminal equipment sends a request message to the first terminal equipment to request to reestablish the link.
Embodiment 35 and the method of embodiment 33, wherein the first terminal device provides the relay service to the second terminal device, and the method further comprises:
And the second terminal equipment reselects the terminal equipment capable of providing the relay service for the second terminal equipment.
Embodiment 36, a communication device, comprising:
a processing module, configured to obtain first configuration information, where the first configuration information is used for configuring a first radio bearer by the communication apparatus, where the first radio bearer is a radio bearer between the first terminal device and a second terminal device, and the second terminal device is a data sending end;
the processing module is further configured to configure the first radio bearer according to the first configuration information;
a sending module, configured to send first configuration failure information to a network device when the processing module fails to configure the first radio bearer.
Embodiment 37, the communications apparatus of embodiment 36, the sending module is configured to send the first configuration failure information to the network device by:
sending an RRC message to a network device, wherein the RRC message comprises a first information element, the first configuration failure information occupies reserved bits in the first information element, and the first information element is used for indicating a failure reason.
Embodiment 38, the communication apparatus according to embodiment 36 or embodiment 37, wherein the sending module is further configured to send second configuration failure information to the second terminal device, where the second configuration failure information is used to indicate that the communication apparatus fails to configure the first radio bearer.
Embodiment 39, the communication device according to any of embodiments 36 to 38, further comprising a receiving module, and the processing module is configured to obtain the first configuration information by:
receiving the first configuration information from the second terminal device through the receiving module.
Embodiment 40, the communication device of embodiment 39, wherein the first configuration information comprises a first common configuration comprising one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 41 the communication device according to any of embodiments 36 to 38, further comprising a receiving module, and the processing module is configured to obtain the first configuration information by:
receiving, by the receiving module, second configuration information from the network device;
receiving, by the receiving module, first information from the second terminal device, where the first information includes an identifier of a logical channel corresponding to the first radio bearer;
and obtaining the first configuration information according to the second configuration information and the first information.
Embodiment 42 and the communication apparatus according to embodiment 41, wherein the first information is obtained by the second terminal device according to fourth configuration information from the network device, and the fourth configuration information is used by the second terminal device to configure the first radio bearer.
Embodiment 43 the communication device of embodiment 41 or embodiment 42, wherein the first information further includes a QFI corresponding to the first radio bearer, and/or a correspondence between an identifier corresponding to the first radio bearer at the Uu port and an identifier corresponding to the PC5 port.
Embodiment 44, the communication apparatus according to any of embodiments 41 to 43, wherein the second configuration information comprises a receive configuration and a second common configuration, wherein the receive configuration comprises a PDCP reordering timer, and the second common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 45 the communication device of any of embodiments 36-38, further comprising a receiving module,
the receiving module is configured to receive QoS information from the second terminal device before the processing module obtains the first configuration information, where the QoS information is used to indicate a QoS of a radio bearer requested to be configured between the second terminal device and the communication apparatus;
The sending module is further configured to send second information to the network device, where the second information is used to request configuration of a radio bearer for bidirectional transmission between the second terminal device and the communication apparatus, and the second information includes the QoS information.
Embodiment 46 the communications apparatus of embodiment 45, wherein the processing module is configured to obtain the first configuration information by:
receiving the first configuration information from the network device.
Embodiment 47, the communication device of embodiment 45 or embodiment 46, the first configuration information comprising a first transmit configuration and a first common configuration, wherein,
the first transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the first common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 48, the communication apparatus according to embodiment 46 or embodiment 47, wherein the sending module is further configured to send third configuration information to the second terminal device, where the third configuration information is used by the second terminal device to configure the first radio bearer, and the third configuration information includes part of or all of the content of the first configuration information.
Embodiment 49, a communication device, comprising:
a receiving module, configured to receive second configuration failure information from a first terminal device, where the second configuration failure information is used to indicate that the first terminal device fails to configure a first radio bearer, the first radio bearer is a radio bearer between the first terminal device and the communication apparatus, the first terminal device provides a relay service for the communication apparatus, the first terminal device is a data receiving end of a data transmission process performed through the first radio bearer, and the communication apparatus is a data sending end of the data transmission process;
a sending module, configured to not send, to a network device, information indicating that the first radio bearer configuration by the first terminal device failed.
Embodiment 50 the communications apparatus according to embodiment 49, wherein the receiving module is further configured to receive fourth configuration information from the network device, and the fourth configuration information is used for the communications apparatus to configure the first radio bearer.
Embodiment 51 the communication device of embodiment 50, wherein the fourth configuration information comprises a third transmit configuration and a third common configuration, wherein,
The third transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the third common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 52, the communication device of embodiment 50 or embodiment 51, further comprising a processing module,
the processing module is configured to select a logical channel for the first radio bearer;
the sending module is further configured to send first configuration information to the first terminal device, where the first configuration information is used for the first terminal device to configure the first radio bearer, and the first configuration information includes an identifier of a logical channel corresponding to the first radio bearer.
Embodiment 53 the communications apparatus of embodiment 52, wherein the first configuration information comprises a first common configuration comprising one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 54, the communication device of embodiment 50 or embodiment 51, further comprising a processing module,
The processing module is configured to select a logical channel for the first radio bearer;
the sending module is further configured to send first information to the first terminal device, where the first information includes an identifier of a logical channel corresponding to the first radio bearer.
Embodiment 55, the communication device of embodiment 54, wherein the first information further includes a QFI corresponding to the first radio bearer, and/or a correspondence between an identifier corresponding to the first radio bearer at the Uu port and an identifier corresponding to the PC5 port.
Embodiment 56, the communications apparatus according to embodiment 49, wherein the receiving module is further configured to receive third configuration information from the first terminal device, where the third configuration information is used by the communications apparatus to configure the first radio bearer, the third configuration information includes part or all of content of first configuration information, and the first configuration information is used by the first terminal device to configure the first radio bearer.
Embodiment 57, the communications apparatus according to embodiment 56, the sending module is further configured to send QoS information to the first terminal device, the QoS information being used to indicate a QoS of a radio bearer requested to be configured between the communications apparatus and the first terminal device.
Embodiment 58 and the communications apparatus according to any of embodiments 49-57, wherein the communications apparatus is not capable of communicating with a network device via a Uu port.
Embodiment 59, a communication device, comprising:
a receiving module, configured to receive first configuration failure information from a first terminal device;
a processing module, configured to determine that the first terminal device fails to configure a first radio bearer according to the first configuration failure information, where the first radio bearer is a radio bearer between the first terminal device and a second terminal device, the first terminal device provides a relay service for the second terminal device, the first terminal device is a data receiving end of a data transmission process performed through the first radio bearer, and the second terminal device is a data sending end of the data transmission process.
Embodiment 60, the communications apparatus of embodiment 59, the receiving module is configured to receive the first configuration failure information from the first terminal device by:
receiving an RRC message from the first terminal equipment, wherein the RRC message comprises a first information element, the first configuration failure information occupies reserved bits in the first information element, and the first information element is used for indicating a failure reason.
Embodiment 61, the communication apparatus according to embodiment 59 or embodiment 60, further comprising a sending module, configured to send fourth configuration information to the second terminal device, where the fourth configuration information is used by the second terminal device to configure the first radio bearer.
Embodiment 62 the communication device of embodiment 61, the fourth configuration information comprising a third transmit configuration and a third common configuration, wherein,
the third transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
the third common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 63, the communication apparatus according to any of embodiments 59 to 61, further comprising a sending module, configured to send second configuration information to the first terminal device, where the second configuration information is used by the first terminal device to configure the first radio bearer.
Embodiment 64 the communications apparatus of embodiment 63, wherein the second configuration information comprises a receive configuration and a second common configuration, wherein the receive configuration comprises a PDCP reordering timer, and wherein the second common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 65, the communication apparatus according to embodiment 63 or embodiment 65, wherein the receiving module is further configured to receive second information from the first terminal device, the second information is used to request configuration of a radio bearer for bidirectional transmission between the second terminal device and the first terminal device, and the second information includes QoS information, and the QoS information is used to indicate that QoS of the radio bearer configured between the second terminal device and the first terminal device is requested.
Embodiment 66 the communication device of embodiment 65, further comprising a transmit module,
the processing module is further configured to determine first configuration information according to the QoS information, where the first configuration information is used for configuring the first radio bearer by the first terminal device;
the sending module is configured to send the first configuration information to the first terminal device.
Embodiment 67 the communications apparatus of embodiment 66, the first configuration information comprising a first transmit configuration and a first common configuration, wherein,
the first transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
The first common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
Embodiment 68, a communication device, comprising:
a processing module configured to determine that a link between a first terminal device and the communication apparatus fails and the communication apparatus is not within a network coverage range;
a sending module, configured to not send, to the network device, information indicating a link failure.
Embodiment 69, the communications apparatus according to embodiment 68, wherein the sending module is further configured to send a request message to the first terminal device to request to reestablish the link.
Embodiment 70, the method of embodiment 68, wherein the first terminal device provides the relay service for the communication apparatus, and the processing module is further configured to reselect a terminal device capable of providing the relay service for the communication apparatus.
Embodiment 71, a communication device, wherein the communication device comprises a processor and a transceiver (or a transmitter and a processor), the processor and the transceiver (or the transmitter and the processor) being coupled to be capable of performing the method as described in any one of embodiments 1 to 13, or to perform the method as described in any one of embodiments 14 to 23, or to perform the method as described in any one of embodiments 33 to 35.
Embodiment 72, a communication device, wherein the communication device comprises a processor and a transceiver (or a transmitter and a processor), the processor and the transceiver (or the transmitter and the processor) being coupled to be capable of performing the method as described in any of embodiments 24 to 32.
Embodiment 73, a chip comprising a processor, the processor being configured to perform the method of any one of embodiments 1 to 13 described above, or to perform the method of any one of embodiments 14 to 23, or to perform the method of any one of embodiments 33 to 35, when the processor executes instructions. The instructions may come from memory internal to the chip or from memory external to the chip. Optionally, the chip further comprises an input-output circuit.
Embodiment 74, a chip comprising a processor, the processor being configured to perform the method of any of embodiments 24 to 32 described above when the processor executes instructions. The instructions may come from memory internal to the chip or from memory external to the chip. Optionally, the chip further comprises an input-output circuit.
Embodiment 75, a communication system comprising a communication device as described in any of embodiments 36 to 48, comprising a communication device as described in any of embodiments 49 to 58, and comprising a communication device as described in any of embodiments 59 to 67.
Embodiment 76, a communication system, wherein the communication system comprises the communication device of any one of embodiments 68 to 70.
Embodiment 77, a computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of any one of embodiments 1 to 13, or to perform the method of any one of embodiments 14 to 23, or to perform the method of any one of embodiments 33 to 35.
Embodiment 78, a computer-readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of any one of embodiments 24 to 32.
Embodiment 79, a computer program product for storing a computer program which, when executed by a computer, the computer may implement the method of any one of embodiments 1 to 13, or the method of any one of embodiments 14 to 23, or the method of any one of embodiments 33 to 35.
Embodiment 80, a computer program product for storing a computer program which, when executed by a computer, the computer may implement the method of any of embodiments 24 to 32.
While the present application has been described in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art from a review of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Claims (25)

1. A method of communication, comprising:
obtaining first configuration information, where the first configuration information is used for a first terminal device to configure a first radio bearer, where the first radio bearer is a radio bearer between the first terminal device and a second terminal device, and the second terminal device is a data sending end;
configuring the first radio bearer according to the first configuration information;
and when the first radio bearer configuration fails, sending first configuration failure information to network equipment.
2. The method of claim 1, wherein sending the first configuration failure information to the network device comprises:
sending a Radio Resource Control (RRC) message to a network device, wherein the RRC message comprises a first information element, the first configuration failure information occupies a reserved bit in the first information element, and the first information element is used for indicating a failure reason.
3. The method according to claim 1 or 2, characterized in that the method further comprises:
and sending second configuration failure information to the second terminal equipment, wherein the second configuration failure information is used for indicating that the first terminal equipment fails to configure the first radio bearer.
4. The method according to any one of claims 1 to 3, wherein obtaining the first configuration information comprises:
receiving the first configuration information from the second terminal device.
5. The method of claim 4, wherein the first configuration information comprises a first common configuration, and wherein the first common configuration comprises one or more of: the service quality flow identifier QFI corresponding to the service data adaptation protocol SDAP, the packet data convergence protocol PDCP and the sequence number SN length of the radio link control RLC, or whether header compression is used.
6. The method according to any one of claims 1 to 3, wherein obtaining the first configuration information comprises:
receiving second configuration information from the network device;
receiving first information from the second terminal device, where the first information includes an identifier of a logical channel corresponding to the first radio bearer;
and obtaining the first configuration information according to the second configuration information and the first information.
7. The method of claim 5, wherein the first information is obtained by the second terminal device according to fourth configuration information from the network device, and wherein the fourth configuration information is used by the second terminal device to configure the first radio bearer.
8. The method according to any of claims 5 to 7, wherein the first information further comprises QFI corresponding to the first radio bearer and/or a correspondence between an identifier corresponding to the first radio bearer at Uu port and an identifier corresponding to PC5 port.
9. The method according to any of claims 5 to 7, wherein the second configuration information comprises a receiving configuration and a second common configuration, wherein the receiving configuration comprises a PDCP reordering timer, and wherein the second common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
10. The method according to any one of claims 1 to 3, further comprising, before obtaining the first configuration information:
receiving quality of service (QoS) information from the second terminal device, the QoS information indicating a QoS for a radio bearer requested to be configured between the second terminal device and the first terminal device;
and sending second information to the network equipment, wherein the second information is used for requesting to configure a radio bearer for bidirectional transmission between the second terminal equipment and the first terminal equipment, and the second information comprises the QoS information.
11. The method of claim 10, wherein obtaining the first configuration information comprises:
receiving the first configuration information from the network device.
12. The method according to claim 10 or 11, wherein the first configuration information comprises a first transmission configuration and a first common configuration, wherein,
the first transmission configuration comprises one or more of: a PDCP discard timer, RoHC compression profile configuration of robust packet header compression, whether the packet header of the SDAP appears, a mapping relation with QFI on a sidelink SL, or a sending type;
the first common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
13. The method according to any one of claims 11 to 12, further comprising:
and sending third configuration information to the second terminal device, where the third configuration information is used for the second terminal device to configure the first radio bearer, and the third configuration information includes part of or all of the content of the first configuration information.
14. A method of communication, comprising:
Receiving second configuration failure information from a first terminal device, where the second configuration failure information is used to indicate that the first terminal device fails to configure a first radio bearer, the first radio bearer is a radio bearer between the first terminal device and a second terminal device, the first terminal device provides a relay service for the second terminal device, the first terminal device is a data receiving end of a data transmission process performed through the first radio bearer, and the second terminal device is a data sending end of the data transmission process;
and not sending information for indicating that the first terminal equipment fails to configure the first radio bearer to network equipment.
15. The method of claim 14, further comprising:
receiving fourth configuration information from the network device, where the fourth configuration information is used by the second terminal device to configure the first radio bearer.
16. The method of claim 15, wherein the fourth configuration information comprises a third transmit configuration and a third common configuration, wherein,
the third transmission configuration comprises one or more of: PDCP abandon timer, RoHC compression profile configuration, whether the SDAP packet header appears, mapping relation with QFI on SL, or sending type;
The third common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
17. The method according to claim 15 or 16, characterized in that the method further comprises:
selecting a logical channel for the first radio bearer;
and sending first configuration information to the first terminal device, where the first configuration information is used for the first terminal device to configure the first radio bearer, and the first configuration information includes an identifier of a logical channel corresponding to the first radio bearer.
18. The method of claim 17, wherein the first configuration information comprises a first common configuration, and wherein the first common configuration comprises one or more of: QFI corresponding to SDAP, SN length of PDCP and RLC, or whether header compression is used.
19. The method according to claim 15 or 16, characterized in that the method further comprises:
selecting a logical channel for the first radio bearer;
and sending first information to the first terminal equipment, wherein the first information comprises the identifier of the logical channel corresponding to the first radio bearer.
20. The method according to claim 19, wherein the first information further comprises QFI corresponding to the first radio bearer, and/or a correspondence between an identifier corresponding to the first radio bearer at Uu port and an identifier corresponding to PC5 port.
21. The method of claim 14, further comprising:
receiving third configuration information from the first terminal device, where the third configuration information is used by the second terminal device to configure the first radio bearer, the third configuration information includes partial content or all content of first configuration information, and the first configuration information is used by the first terminal device to configure the first radio bearer.
22. The method of claim 21, further comprising:
and sending QoS information to the first terminal equipment, wherein the QoS information is used for indicating the QoS of the radio bearer which is configured between the second terminal equipment and the first terminal equipment.
23. The method according to any one of claims 14 to 22, wherein the second terminal device cannot communicate with the network device through the Uu port.
24. A communication device comprising a receiving module, a transmitting module and a processing module, the receiving module, the transmitting module and the processing module being coupled to be able to perform the method of any of claims 1 to 13 or to perform the method of any of claims 14 to 23.
25. A computer-readable storage medium, for storing a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 13 or causes the computer to perform the method of any one of claims 14 to 23.
CN202010724936.4A 2020-05-25 2020-07-24 Communication method and device Pending CN113727368A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/078791 WO2021238318A1 (en) 2020-05-25 2021-03-02 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010450671 2020-05-25
CN2020104506713 2020-05-25

Publications (1)

Publication Number Publication Date
CN113727368A true CN113727368A (en) 2021-11-30

Family

ID=78672254

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010724936.4A Pending CN113727368A (en) 2020-05-25 2020-07-24 Communication method and device

Country Status (2)

Country Link
CN (1) CN113727368A (en)
WO (1) WO2021238318A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023184116A1 (en) * 2022-03-28 2023-10-05 北京小米移动软件有限公司 Sidelink communication method and apparatus

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018171514A1 (en) * 2017-03-24 2018-09-27 华为技术有限公司 Method and device for information indication
CN110870360A (en) * 2017-05-08 2020-03-06 Lg电子株式会社 Method for performing V2X communication in wireless communication system and apparatus therefor

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108347772A (en) * 2017-01-25 2018-07-31 华为技术有限公司 Resource allocation methods and device
US11871378B2 (en) * 2018-11-01 2024-01-09 Lg Electronics Inc. Deactivation of configured grant and initiation of connection request upon detection of sidelink failure
CN116828634A (en) * 2019-12-02 2023-09-29 北京小米移动软件有限公司 Method and device for processing radio link failure and computer storage medium

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018171514A1 (en) * 2017-03-24 2018-09-27 华为技术有限公司 Method and device for information indication
CN108924962A (en) * 2017-03-24 2018-11-30 华为技术有限公司 The method and apparatus of information instruction
CN110870360A (en) * 2017-05-08 2020-03-06 Lg电子株式会社 Method for performing V2X communication in wireless communication system and apparatus therefor

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI (RAPPORTEUR): "R2-2002918 "Summary of [Post109e#54][V2X] RRC Open Issues"", 3GPP TSG_RAN\\WG2_RL2, no. 2, 18 April 2020 (2020-04-18), pages 2 *
HUAWEI (RAPPORTEUR): "R2-2004071 "Summary of offline discussion [AT109bis-e][701][V2X] RRC open issues and ASN.1 class2/3 issues"", 3GPP TSG_RAN\\WG2_RL2, no. 2, 1 May 2020 (2020-05-01), pages 2 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023184116A1 (en) * 2022-03-28 2023-10-05 北京小米移动软件有限公司 Sidelink communication method and apparatus

Also Published As

Publication number Publication date
WO2021238318A1 (en) 2021-12-02

Similar Documents

Publication Publication Date Title
CN112889258B (en) Communication method and device
CN112351403B (en) Communication method, SLRB establishment method and communication device
WO2022110168A1 (en) Communication configuration method and communication apparatus
CN113746585A (en) Time service method and communication device
WO2021000688A1 (en) Method and apparatus for transmitting and receiving capability information
WO2020216133A1 (en) Communication method and device
CN114157723B (en) Communication method and device
WO2021258766A1 (en) Method and device for configuring terminal device
CN113228717B (en) Communication method and device
CN111757293B (en) Communication method and communication device
CN112740826B (en) Capability reporting method and terminal equipment
CN113727368A (en) Communication method and device
CN113301606B (en) Communication method and device
WO2022104531A1 (en) Connection method and related apparatus
CN112399400B (en) Method and equipment for reporting UDC information by UE
CN112399477B (en) Communication method and device
US20220191951A1 (en) Method and apparatus for establishing radio bearer
WO2021134763A1 (en) Method, apparatus and device for recovering transmission
CN110831169B (en) Method and equipment for configuring carrier
CN114698145A (en) Method and device for transmitting data
CN113556709A (en) Communication method and device
CN111866963A (en) Communication method, communication device, computer storage medium, and communication system
CN114095978B (en) Method and device for configuring terminal device
CN112135329B (en) Parameter transmission method, device and system
WO2023185608A1 (en) Data transmission method and communication apparatus

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination