A communication method, device and communication system for vehicle communication service

Abstract

The present application provides a communication device, method and communication system for a vehicle communication (V2X) service, the device comprising a first communication unit, the first communication unit: detecting a radio link failure (Radio Link Failure) of the side link; and notifying the network device through a side link user equipment information (Sidelink UE Information) message that a radio link failure has occurred in all side links of the terminal device.

Description

Technical Field

[0001] The present application relates to the field of communications. Background Art

[0002] Vehicle communication services are denoted as V2X services. V2X services may include various types, such as vehicle-to-vehicle (V2V) communication services, vehicle-to-infrastructure (V2I) communication services, vehicle-to-pedestrian (V2P) communication services, etc.

[0003] V2X services can be provided through the PC5 interface and / or the Uu interface. V2X services transmitted through the PC5 interface can be provided by V2X sidelink communication, which is a communication method in which terminal devices can communicate with each other directly through the PC5 interface.

[0004] It should be noted that the above introduction to the technical background is only for the convenience of providing a clear and complete description of the technical solutions of the present application and for the convenience of understanding by those skilled in the art. It cannot be considered that the above technical solutions are well known to those skilled in the art simply because they are described in the background technology section of the present application. Summary of the invention

[0005] In the prior art, for unicast links, radio link monitoring (RLM) on the PC5 interface (also called sidelink) is supported. By performing radio link monitoring on the side link, it can be detected whether a radio link failure (RLF) occurs in the side link.

[0006] The inventor of the present application discovered that, in the prior art, when wireless link failure occurs in all side links of a terminal device, how to notify the network device in a manner that occupies less wireless resources is a problem that needs to be solved.

[0007] An embodiment of the present application provides a communication method, device and communication system for a vehicle communication service. In the method, a terminal device notifies a network device through a sidelink user equipment information (Sidelink UE Information) message that a wireless link failure has occurred in all side links of the terminal device. Thus, the network device can be notified that a wireless link failure has occurred in all side links of the terminal device in a manner that occupies less wireless resources.

[0008] According to a first aspect of an embodiment of the present application, a communication device for a vehicle communication (V2X) service is provided, which is applied to a terminal device, and the device includes a first communication unit, which: detects a radio link failure (Radio Link Failure) of the side link; and notifies the network device through a side link user equipment information (Sidelink UE Information) message that a radio link failure has occurred in all side links of the terminal device.

[0009] According to a second aspect of an embodiment of the present application, a communication device for a vehicle communication (V2X) service is provided, which is applied to a network device, and the device includes a second communication unit, wherein the second communication unit receives a notification from the terminal device via a sidelink user equipment information (Sidelink UE Information) message that wireless link failures have occurred in all side links of the terminal device.

[0010] According to a third aspect of an embodiment of the present application, a communication system is provided, which includes a terminal device and a network device. The terminal device includes the communication device as described in the first aspect of the above embodiment, and the network device includes the communication device as described in the second aspect of the above embodiment.

[0011] The beneficial effect of the embodiments of the present application is that the terminal device notifies the network device through the sidelink user equipment information (Sidelink UEInformation) message that all side links of the terminal device have experienced wireless link failures, thereby being able to notify the network device that all side links of the terminal device have experienced wireless link failures in a manner that occupies less wireless resources.

[0012] With reference to the following description and accompanying drawings, the specific embodiments of the present application are disclosed in detail, indicating the way in which the principles of the present application can be adopted. It should be understood that the embodiments of the present application are not limited in scope. Within the scope of the terms of the appended claims, the embodiments of the present application include many changes, modifications and equivalents.

[0013] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0014] It should be emphasized that the term “include / comprises” when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The elements and features described in one figure or one implementation of the present application embodiment may be combined with the elements and features shown in one or more other figures or implementations. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one implementation.

[0016] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0017] Figure 1 is a schematic diagram of the communication system of the present application;

[0018] Figure 2 is a schematic diagram of a communication method for a vehicle-to-everything (V2X) service according to a first aspect of an embodiment of the present application;

[0019] Figure 3 It is a schematic diagram of a wireless link failure in a side link between terminal devices;

[0020] Figure 4 is another schematic diagram of a wireless link failure occurring in a side link between terminal devices;

[0021] Figure 5 is a schematic diagram of a communication method according to a second aspect of an embodiment of the present application;

[0022] Figure 6 It is a schematic diagram of the mapping relationship between the destination identifier in the user equipment information and the destination index in the cache status report;

[0023] Figure 7 is another schematic diagram of the mapping relationship between the destination identifier in the user equipment information and the destination index in the cache status report;

[0024] Figure 8 is a schematic diagram of a communication method for a vehicle communication (V2X) service according to a third aspect of an embodiment of the present application;

[0025] Fig. 9 is a schematic diagram of a communication method according to a fourth aspect of an embodiment of the present application;

[0026] Fig.10 is a schematic diagram of a communication method for a vehicle communication (V2X) service according to a fifth aspect of an embodiment of the present application;

[0027] Fig.11 is a schematic diagram of a communication method according to a sixth aspect of an embodiment of the present application;

[0028] Fig.12 is a schematic diagram of a communication method for a vehicle communication (V2X) service in a seventh aspect of an embodiment of the present application;

[0029] Fig.13 is another schematic diagram of a communication method for a vehicle-to-everything (V2X) service according to a seventh aspect of an embodiment of the present application;

[0030] Fig.14 is a schematic diagram of a communication method according to a seventh aspect of an embodiment of the present application;

[0031] Fig.15 is another schematic diagram of the communication method according to the seventh aspect of the embodiments of the present application;

[0032] Fig.16 is a schematic diagram of a communication method for a vehicle communication (V2X) service according to a ninth aspect of an embodiment of the present application;

[0033] Fig.17 is a schematic diagram of a communication method according to a tenth aspect of an embodiment of the present application;

[0034] Fig.18 is a schematic diagram of a communication device according to a twelfth aspect of an embodiment of the present application;

[0035] Fig.19 is another schematic diagram of the communication device according to the twelfth aspect of the embodiments of the present application;

[0036] Fig. 20 is another schematic diagram of the communication device according to the twelfth aspect of the embodiments of the present application;

[0037] Fig.21 is another schematic diagram of the communication device according to the twelfth aspect of the embodiments of the present application;

[0038] Fig. 22 is another schematic diagram of the communication device according to the twelfth aspect of the embodiments of the present application;

[0039] Fig.23 is another schematic diagram of the communication device according to the twelfth aspect of the embodiments of the present application;

[0040] Fig.24 is a schematic diagram of a communication device according to the thirteenth aspect of an embodiment of the present application;

[0041] Fig.25 is another schematic diagram of the communication device according to the thirteenth aspect of the embodiments of the present application;

[0042] Fig.26 is another schematic diagram of the communication device according to the thirteenth aspect of the embodiments of the present application;

[0043] Fig. 27 is another schematic diagram of the communication device according to the thirteenth aspect of the embodiments of the present application;

[0044] Fig.28 is another schematic diagram of the communication device according to the thirteenth aspect of the embodiments of the present application;

[0045] Fig.29 is another schematic diagram of the communication device according to the thirteenth aspect of the embodiments of the present application;

[0046] Fig.30 is a schematic diagram of the structure of a terminal device according to a fourteenth aspect of an embodiment of the present application;

[0047] Fig.31 It is a schematic diagram of the structure of the network device of the fifteenth aspect of the embodiment of the present application. DETAILED DESCRIPTION

[0048] The foregoing and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are specifically disclosed, which show some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents falling within the scope of the attached claims. Various embodiments of the present application are described below in conjunction with the accompanying drawings. These embodiments are exemplary only and are not limitations of the present application.

[0049] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements in terms of title, but do not indicate the spatial arrangement or temporal order of these elements, etc., and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0050] In the embodiments of the present application, the singular forms "a", "the", etc. include plural forms and should be broadly understood as "a kind" or "a type" rather than being limited to the meaning of "one"; in addition, the term "the" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. In addition, the term "according to" should be understood as "at least in part according to...", and the term "based on" should be understood as "at least in part based on...", unless the context clearly indicates otherwise.

[0051] In an embodiment of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed ​​Packet Access (HSPA, High-Speed ​​Packet Access), etc.

[0052] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, new wireless (NR, New Radio), etc., and / or other communication protocols currently known or to be developed in the future.

[0053] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device. The network device may include, but is not limited to, the following devices: a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), and the like.

[0054] Among them, base stations may include but are not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB) and 5G base station (gNB), etc., and may also include remote radio heads (RRH, Remote Radio Head), remote radio units (RRU, Remote Radio Unit), relays or low-power nodes (such as femto, pico, etc.). And the term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographical area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0055] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. The terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and the like.

[0056] Among them, the terminal device may include but is not limited to the following devices: cellular phone, personal digital assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, cordless phone, smart phone, smart watch, digital camera, etc.

[0057] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measuring, such as but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device to device (D2D) terminal, machine to machine (M2M) terminal, and the like.

[0058] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0059] Figure 1 is a schematic diagram of the communication system of the present application, schematically illustrating a situation taking a terminal device and a network device as an example, such as Figure 1 As shown, the communication system 100 may include a network device 101 and a plurality of terminal devices 102. The plurality of terminal devices are, for example, a terminal device 1021, a terminal device 1022, a terminal device 1023, and a terminal device 1024.

[0060] In the embodiment of the present application, existing services or services that can be implemented in the future can be carried out between the network device 101 and the terminal device 102. For example, these services include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0061] The terminal device 102 may send data to the network device 101 and receive feedback information from the network device 101. The network device 101 may also send data to one or more terminal devices 102 and receive feedback information sent by the terminal devices 102.

[0062] In addition, the terminal device 102 may send a V2X service-related message to one or more other terminal devices 102, or the terminal device 102 may receive a V2X service-related message from another terminal device 102, wherein the V2X service-related message may be sent or received in a unicast, multicast or broadcast manner. For example, the terminal device 1021 sends a V2X service-related message to the terminal device 1022, or the terminal device 1021 receives a V2X service-related message from the terminal device 1022; for another example, the terminal device 1021 sends a V2X service-related message to the terminal device 1022, the terminal device 1023 and the terminal device 1024.

[0063] First aspect of the embodiment

[0064] A first aspect of an embodiment of the present application provides a communication method, which can be executed by a terminal device, and the terminal device can be, for example, Figure 1 Terminal device 1021.

[0065] Figure 2 is a schematic diagram of a communication method for a vehicle communication (V2X) service according to a first aspect of an embodiment of the present application, such as Figure 2 As shown, the method includes:

[0066] Operation 201: The terminal device detects that a radio link failure occurs in the edge link.

[0067] Operation 202: The terminal device notifies the network device through a sidelink user equipment information (Sidelink UE Information) message that radio link failures occur in all side links of the terminal device.

[0068] According to the first aspect of an embodiment of the present application, a terminal device notifies a network device through a sidelink user equipment information (Sidelink UEInformation) message that a radio link failure has occurred in all side links of the terminal device. Thus, the network device can be notified that a radio link failure has occurred in all side links of the terminal device in a manner that occupies fewer wireless resources.

[0069] Figure 3 This is a schematic diagram of a wireless link failure in a side link between terminal devices. Figure 3 As shown, side link communication is performed between terminal device 1021 and terminal device 1022, and there may be multiple logical connections (logic connection) between terminal device 1021 and terminal device 1022, each logical connection is, for example, a PC5-radio resource control connection (PC5-RRCconnection) or a PC5 unicast link (unicast link).

[0070] Each logical connection is identified by a pair of source identifier and destination identifier. For example, logical connection 31 is identified by source identifier 1 in terminal device 1021 and destination identifier A in terminal device 1022, and logical connection 32 is identified by source identifier 2 in terminal device 1021 and destination identifier B in terminal device 1022. Logical connection 31 and logical connection 32 can be unicast communication modes, that is, data is sent from source identifiers 1 and 2 to destination identifiers A and B.

[0071] exist Figure 3 In the figure, only the side link communication between terminal device 1021 and terminal device 1022 is shown, and the communication between terminal device 1021 and other terminal devices is the same as that between terminal device 1021 and other terminal devices. Figure 3 Similar. In addition, Figure 3 Only the case where the number of logical connections is 2 is shown, but the embodiments of the present application are not limited thereto, and the number of logical connections may be more than 3.

[0072] In this application, if Figure 3 As shown, the terminal device 1021 can communicate with the network device 101. For example, the terminal device 1021 can send a sidelink user equipment information (Sidelink UE Information) message to the network device 101, and the terminal device 1021 can receive configuration information and / or control information from the network device 101.

[0073] exist Figure 2In operation 201, the terminal device 1021 may detect whether a radio link failure (RadioLink Failure) occurs in the side link. For example, the terminal device 1021 detects whether a radio link failure (RadioLink Failure) occurs in the logical connections 31 and 32.

[0074] In the present application, each logical connection has a corresponding relationship with the destination identifier. Therefore, a wireless link failure in the logical connection can also be referred to as a wireless link failure in the destination identifier or a wireless link failure in the side link to the destination identifier. In the embodiments of the present application, these three statements have the same meaning.

[0075] In at least one embodiment, when a radio link failure is detected, the terminal device 1021 may report to the network device 101. The terminal device 1021 may notify the network device 101 of the radio link failure in the following manner: Mode 1: notifying which logical connections have radio link failure in a sidelink user equipment information (Sidelink UE Information) message, for example, the sidelink user equipment information message includes a destination identifier for the radio link failure, wherein the destination identifier may be represented in the sidelink user equipment information message as destination L2 id, destination ID, or destination Identity, etc. Mode 2: notifying the remaining logical connections excluding the logical connection having radio link failure in a sidelink user equipment information (Sidelink UE Information) message, for example, the sidelink user equipment information message includes the remaining destination identifiers excluding the destination identifier for the radio link failure, wherein the destination identifier may be represented in the sidelink user equipment information message as destination L2 id, destination ID, or destination Identity, etc.

[0076] Figure 4 is another schematic diagram of a wireless link failure in a side link between terminal devices. Figure 4 As shown, wireless link failures occur in both logical connections 31 and 32 between terminal device 1021 and terminal device 1022, that is, wireless link failures occur in all side links between terminal device 1021 and terminal device 1022.

[0077] In the case where radio link failure occurs in all side links between terminal device 1021 and terminal device 1022: if method one is used for notification, the side link user equipment information message needs to include all destination identifiers where radio link failure occurs, and the signaling overhead of the side link user equipment information message is large; if method two is used for notification, since there are no remaining destination identifiers, it is difficult to perform notification that matches method two.

[0078] According to the first aspect of the embodiment of the present application, in operation 202, the terminal device 1021 can separately notify the situation where radio link failure occurs in all side links through the side link user equipment information message. After receiving the message from the terminal device 1021, the network device 101 can determine that radio link failure occurs in all side links of the terminal device. Therefore, there is no need to list all destination identifiers where radio link failure has occurred in the user equipment information message, thereby reducing signaling overhead.

[0079] Next, a specific implementation of operation 202 is described.

[0080] In the first implementation mode, whether a side link transmission resource request list (sl-TxResourceReqList) field appears in the side link user equipment information message is used to notify whether radio link failure occurs in all side links.

[0081] When the terminal device 1021 notifies the network device 101 of the wireless link failure through method 2, the side link user equipment information message will contain a side link send resource request list (sl-TxResourceReqList) field, which lists the remaining destination identifiers excluding the destination identifier where the wireless link failure occurred.

[0082] For example, the type of the side link transmit resource request list (sl-TxResourceReqList) field is the side link transmit resource request list (SL-TxResourceReqList), in which one or more side link transmit resource request elements (SL-TxResourceReq) are listed, and the content of the side link transmit resource request element may include information such as the side link destination identifier (sl-DestinationIdentity), the side link propagation type (sl-CastType) and the quality of service (QoS).

[0083] In implementation mode 1, when terminal device 1021 detects that wireless link failures occur in all side links between terminal device 1021 and terminal device 1022, terminal device 1021 sends a side link user device information message to network device 101, and the side link transmission resource request list (sl-TxResourceReqList) field does not appear in the side link user device information message.

[0084] For example, an example of the first embodiment is shown in Table 1 below.

[0085] Table 1:

[0086]

[0087] In implementation mode 2, when wireless link failure occurs in all side links of terminal device 1021, the content of the side link transmission resource request list (sl-TxResourceReqList) field in the side link user equipment information message sent by terminal device 1021 to network device 101 is empty.

[0088] The difference between implementation mode 2 and implementation mode 1 is that in implementation mode 2, a side link transmission resource request list (sl-TxResourceReqList) field appears in the side link user equipment information message, but the content of the side link transmission resource request list (sl-TxResourceReqList) field is empty.

[0089] Among them, in implementation mode 2, the content of the side link transmission resource request list (sl-TxResourceReqList) field of the side link user equipment information message is empty, which means that the number of side link transmission resource request elements (SL-TxResourceReq) in the side link transmission resource request list (SL-TxResourceReqList) of the side link user equipment information message is 0.

[0090] That is to say, when the terminal device 1021 notifies the network device 101 of the wireless link failure through method 2, the number of side link resource request elements (SL-TxResourceReq) in the side link resource request list (SL-TxResourceReqList) is at least one, and in implementation mode 2 of the present application, the number of side link resource request elements (SL-TxResourceReq) in the side link resource request list (SL-TxResourceReqList) can be 0, and the number of side link resource request elements (SL-TxResourceReq) being 0 indicates that wireless link failure has occurred in all side links of the terminal device 1021.

[0091] For example, an example of the second implementation is shown in Table 2 and Table 3 below.

[0092] Table 2:

[0093]

[0094] Table 3:

[0095]

[0096] In implementation mode three, when wireless link failure occurs in all side links of terminal device 1021, the content of the side link sending resource request element (SL-TxResourceReq) in the side link sending resource request list (SL-TxResourceReqList) field of the link user equipment information message is empty.

[0097] Among them, the content of the side link send resource request element (SL-TxResourceReq) is empty, which means that the content of the side link send resource request element does not contain information such as the side link destination identifier (sl-DestinationIdentity) or the side link transmission type (sl-CastType) or the quality of service (QoS).

[0098] For example, in implementation mode three, when wireless link failure occurs in all side links of the terminal device 1021, the side link sending resource request list (sl-TxResourceReqList) field of the link user equipment information message may still have at least one side link sending resource request element (SL-TxResourceReq), but the content of each side link sending resource request element (SL-TxResourceReq) is empty.

[0099] For example, an example of implementation mode 3 is shown in Table 4 below.

[0100] Table 4:

[0101]

[0102] In the fourth embodiment, the side link user equipment information message may include indication information for indicating that radio link failure occurs in all side links of the terminal device 1021. For example, the indication information may have 1 bit, and when radio link failure occurs in all side links of the terminal device 1021, the indication information may take a first value, so that the network device 101 may determine that radio link failure occurs in all side links of the terminal device 1021 according to the value of the indication information.

[0103] For example, an example of implementation mode 4 is shown in Table 5 below, that is, indication information as shown in Table 5 is added to the edge link user equipment information message.

[0104] Table 5:

[0105]

[0106] According to the first aspect of the embodiment of the present application, the terminal device notifies the network device through a sidelink user equipment information (Sidelink UEInformation) message that all side links of the terminal device have experienced a radio link failure, thereby being able to notify the network device that all side links of the terminal device have experienced a radio link failure in a manner that occupies less radio resources. The network device can determine that all side links of the terminal device 1021 have experienced a radio link failure by receiving a sidelink user equipment information (Sidelink UEInformation) message sent by the terminal device, thereby reducing the allocation of dedicated side link radio resources, thereby improving the utilization of radio resources.

[0107] Second aspect of the embodiment

[0108] A second aspect of the present application provides a communication method, which corresponds to the method performed by the terminal device of the first aspect of the embodiment. The method can be performed by a network device, which can be, for example, Figure 1 network device 101.

[0109] Figure 5 FIG. 1 is a schematic diagram of a communication method according to the second aspect of an embodiment of the present application. Figure 5 As shown, the method includes:

[0110] Operation 501: A network device receives a notification from a terminal device via a sidelink user equipment information (Sidelink UE Information) message that radio link failures occur in all side links of the terminal device.

[0111] In operation 501, the network device 101 may receive a sidelink UE Information message from the terminal device 1021. Thus, the network device 101 may determine that all sidelinks of the terminal device 1021 have radio link failures based on the sidelink UE Information message.

[0112] In one embodiment, when radio link failure occurs in all side links of the terminal device 1021, the side link transmit resource request list (sl-TxResourceReqList) field of the side link user equipment information message does not appear in the side link user equipment information message.

[0113] In another embodiment, when all side links of the terminal device have a radio link failure, the content of the side link transmission resource request list (sl-TxResourceReqList) field of the side link user equipment information message is empty. The content of the side link transmission resource request list (sl-TxResourceReqList) field of the side link user equipment information message is empty, which means that the number of elements (SL-TxResourceReq) in the side link transmission resource request list (SL-TxResourceReqList) of the side link user equipment information message is 0.

[0114] In another embodiment, when all side links of the terminal device have radio link failures, the content of the element (SL-TxResourceReq) in the side link transmission resource request list (sl-TxResourceReqList) field of the side link user equipment information message is empty. The content of the element (SL-TxResourceReq) is empty, which means that the content of the element (SL-TxResourceReq) does not contain information such as the side link destination identifier (sl-DestinationIdentity) or the side link propagation type (sl-CastType) or the quality of service (QoS).

[0115] In another embodiment, the side link user equipment information message contains indication information for indicating that all side links of the terminal device have experienced a radio link failure. For example, the indication information may have 1 bit. When all side links of the terminal device 1021 have experienced a radio link failure, the indication information may take a first value.

[0116] Therefore, the network device 101 can determine that all side links of the terminal device 1021 have wireless link failures based on the value of the indication information.

[0117] According to the second aspect of the embodiment of the present application, the network device receives a notification from the terminal device through a sidelink UEInformation message that all side links of the terminal device have experienced a radio link failure, thereby being able to notify the network device that all side links of the terminal device have experienced a radio link failure in a manner that occupies fewer radio resources. In addition, when the network device determines that all side links of the terminal device have experienced a radio link failure, the allocation of dedicated side link radio resources can be reduced, thereby improving the utilization of radio resources.

[0118] The third aspect of the embodiment

[0119] A third aspect of the embodiments of the present application provides a communication method, which can be executed by a terminal device, and the terminal device can be, for example, Figure 1 Terminal device 1021.

[0120] The communication method of the third aspect of the embodiment of the present application involves determining the mapping relationship between the destination identifier in the side link user equipment information message and the destination index in the side link cache status report.

[0121] Figure 6 It is a schematic diagram of the mapping relationship between the destination identifier in the user equipment information and the destination index in the cache status report. Figure 6 As shown, when there is no radio link failure in the side link of the terminal device 1021, the destination identifier in the side link user equipment information message sent by the terminal device 1021 is, for example, identifier 1 (ID1), identifier 2 (ID2), identifier 3 (ID3), and identifier 4 (ID4). The destination index (destination index) in the side link buffer status report (SL BSR) sent by the terminal device 1021 to the network device 101 is, for example, index 1 (Index1), index 2 (Index 2), index 3 (Index3), and index 4 (Index 4). Figure 6 As shown, ID1, ID2, ID3, and ID4 correspond to Index1, Index2, Index3, and Index4, respectively.

[0122] Figure 7 FIG. 4 is another schematic diagram of the mapping relationship between the destination identifier in the user equipment information and the destination index in the cache status report. Figure 7 As shown, in the case of a radio link failure (Radio Link Failure) of the side link of the terminal device 1021, for example, a radio link failure occurs in the destination identifier 2 (ID2), and the destination identifier of the radio link failure does not need to correspond to the destination index, so, Figure 6 The mapping relationship shown will be changed. Therefore, it is necessary to redefine the mapping relationship between the destination identifier and the destination index, so as to facilitate the allocation of side link communication resources by the network device 101 to the terminal device.

[0123] Figure 8 is a schematic diagram of a communication method for a vehicle communication (V2X) service according to a third aspect of an embodiment of the present application, such as Figure 8 As shown, the method includes:

[0124] Operation 801: The terminal device 1021 sends a sidelink user equipment information (Sidelink UEInformation) message to the network device 101; and

[0125] Operation 802: The terminal device 1021 determines a mapping relationship between a destination identifier and a destination index in an edge link cache status report.

[0126] In an embodiment of the present application, in operation 801, when the terminal device 1021 detects a radio link failure (Radio Link Failure) in the side link, it can use method 1 to notify the network device 101 of the radio link failure, that is, the side link user equipment information (Sidelink UE Information) message sent by the terminal device 1021 to the network device 101 can include a destination identifier of the radio link failure.

[0127] In operation 802, the terminal device 1021 may determine a mapping relationship between the remaining destination identifiers after excluding the destination identifiers for which a radio link failure has occurred and the destination indexes in the edge link cache status report.

[0128] Next, a specific implementation of operation 802 is described.

[0129] In implementation mode 1, the terminal device 1021 may map the remaining destination identifiers with the destination index in the edge link cache status report according to a predetermined rule.

[0130] The mapping according to the predetermined rule may be any one of the following schemes 1 to 4:

[0131] Solution 1: According to the order of the destination identifiers in the previous side link user equipment information message, after removing the destination identifier where the radio link failure (Radio Link Failure) occurred, the destination identifiers are mapped in sequence with the destination indexes in the side link cache status report. For example, the order of the destination identifiers in the previous side link user equipment information message is identifier 1 (ID1), identifier 2 (ID2), identifier 3 (ID3), and identifier 4 (ID4). After removing the destination identifier 2 where the radio link failure (Radio Link Failure) occurred, the remaining destination identifiers are identifier 1 (ID1), identifier 3 (ID3), and identifier 4 (ID4). The remaining destination identifiers are mapped in sequence with the destination indexes in the side link cache status report, that is, identifier 1 (ID1), identifier 3 (ID3), and identifier 4 (ID4) are mapped with index 1 (Index1), index 2 (Index2), and index 3 (Index3), respectively;

[0132] Solution 2: Map the destination identifiers to the destination indexes in the edge link cache status report in order from large to small or from small to large. For example, Figure 7 The remaining destination identifiers shown in are mapped with the destination indexes in the edge link cache status report in order from large to small (for example, identifier 4 (ID4), identifier 3 (ID3), identifier 1 (ID1)) or in order from small to large (for example, identifier 1 (ID1), identifier 3 (ID3), identifier 4 (ID4)), that is, identifier 4 (ID4), identifier 3 (ID3), identifier 1 (ID1) are mapped with index 1 (Index1), index 2 (Index 2), and index 3 (Index 3) respectively, or identifier 1 (ID1), identifier 3 (ID3), and identifier 4 (ID4) are mapped with index 1 (Index1), index 2 (Index 2), and index 3 (Index 3) respectively;

[0133] Solution 3: The destination index is the same as the predetermined bit in the destination identifier. The destination identifier is mapped to the destination index according to the predetermined bit in the destination identifier. For example, the destination identifier may have 24 bits, the destination index may have 3 bits, and the destination index may be the same as the lower 3 bits or the upper 3 bits of the destination identifier, that is, Index 1 (Index1), Index 2 (Index2), Index 3 (Index 3), and Index 4 (Index 4) are the lower 3 bits or the upper 3 bits of ID 1 (ID1), ID 2 (ID2), ID 3 (ID3), and ID 4 (ID4), respectively. In the event of a radio link failure in ID 2, Index 1 (Index1), Index 3 (Index 3), and Index 4 (Index 4) are mapped to ID 1 (ID1), ID 3 (ID3), and ID 4 (ID4), respectively, according to the destination index and the lower 3 bits or the upper 3 bits in the destination identifier.

[0134] Solution 4: After filling the last destination identifier to the position of the destination identifier where a radio link failure (Radio Link Failure) occurred, the destination identifiers are mapped with the destination indexes in sequence. For example, the last destination identifier 4 is filled to the position of identifier 2, and then the destination identifiers are mapped with the destination indexes in sequence, that is, identifier 1 (ID1), identifier 4 (ID4), and identifier 3 (ID3) are mapped with index 1 (Index1), index 2 (Index 2), and index 3 (Index 3), respectively.

[0135] In implementation mode 2, terminal device 1021 can map the remaining destination identifiers with the destination index in the edge link cache status report according to the configuration message sent by network device 101. The configuration message can be used to configure the mapping relationship between the destination identifier and the destination index in the edge link cache status report.

[0136] In implementation mode 3, the terminal device 1021 can independently determine the mapping relationship between the remaining destination identifiers and the destination index in the edge link cache status report.

[0137] In the third implementation mode, Figure 8 As shown, the method may also include:

[0138] Operation 803: The terminal device sends a message for reporting a mapping relationship between a destination identifier and a destination index in an edge link cache status report to the network device.

[0139] Through operation 803, the mapping relationship determined by the terminal device may be reported to the network device, so that the network device and the terminal device can obtain the same mapping relationship.

[0140] According to the third aspect of the embodiment of the present application, when a wireless link failure occurs in the side link of a terminal device, the mapping relationship between the remaining destination identifier and the destination index in the side link cache status report can be determined without modifying the content of the side link cache status report, and the network device and the terminal device have the same understanding of the mapping relationship, thereby facilitating the network device to allocate appropriate side link communication resources to the terminal device.

[0141] Fourth aspect of the embodiment

[0142] A fourth aspect of the present application provides a communication method, which corresponds to the method performed by the terminal device of the third aspect of the embodiment. The method can be performed by a network device, which can be, for example, Figure 1 network device 101.

[0143] Fig. 9 Schematic diagram of the communication method according to the fourth aspect of the embodiment of the present application. Fig. 9 As shown, the method includes:

[0144] Operation 901: The network device receives a sidelink UE Information message; and

[0145] Operation 902: The network device determines a mapping relationship between a destination identifier and a destination index in an edge link cache status report.

[0146] In implementation mode 1, the network device 101 may map the remaining destination identifiers with the destination indexes in the edge link cache status report according to a predetermined rule.

[0147] The mapping according to the predetermined rule may be any one of the following schemes 1 to 4:

[0148] Solution 1: According to the order of the destination identifiers in the previous side link user equipment information message, remove the destination identifiers where the radio link failure has occurred (Radio Link Failure) and then map them with the destination indexes in the side link cache status report in sequence;

[0149] Solution 2: Map the destination identifiers with the destination indexes in the edge link cache status report in order from large to small or from small to large;

[0150] Solution 3: The destination index is the same as the predetermined bit in the destination identifier, and the destination identifier is mapped to the destination index according to the destination index and the predetermined bit in the destination identifier;

[0151] Solution 4: After filling the last destination identifier to the position of the destination identifier where the radio link failure (Radio Link Failure) occurs, the destination identifiers are mapped with the destination indexes in sequence.

[0152] For detailed description of the above-mentioned schemes 1 to 4, please refer to the relevant description of the third aspect of the embodiments of the present application.

[0153] In the second implementation mode, the network device 101 determines the mapping relationship between the remaining destination identifiers and the destination indexes in the edge link cache status report.

[0154] In the second implementation mode, Fig. 9 As shown, the method also includes:

[0155] Operation 903: The network device sends a message for configuring a mapping relationship between a destination identifier and a destination index in an edge link cache status report to the terminal device.

[0156] Through operation 903, the network device 101 can send the mapping relationship determined by the network device 101 to the terminal device 1021 as configuration information, so that the network device and the terminal device can obtain the same mapping relationship.

[0157] In implementation mode 3, the network device may determine the mapping relationship based on a message received from the terminal device for reporting the mapping relationship between the destination identifier and the destination index in the side link buffer status report, wherein the message may be, for example, a side link user equipment information (Sidelink UE Information) message.

[0158] Fifth aspect of the embodiment

[0159] A fifth aspect of the embodiments of the present application provides a communication method, which can be executed by a terminal device, and the terminal device can be, for example, Figure 1 Terminal device 1021.

[0160] The communication method of the fifth aspect of the embodiments of the present application involves determining a manner of notifying a network device of a wireless link failure.

[0161] Fig.10 is a schematic diagram of a communication method for a vehicle communication (V2X) service according to a fifth aspect of an embodiment of the present application, such as Fig.10 As shown, the method includes:

[0162] Operation 1001: When a radio link failure occurs, the terminal device sends a destination identifier indicating that the radio link failure has occurred to the network device or sends the remaining destination identifiers excluding the destination identifier indicating that the radio link failure has occurred to the network device according to a resource allocation method.

[0163] According to the fifth aspect of the embodiment of the present application, it is possible to determine whether to use method one or method two to report the wireless link failure to the network device based on the resource allocation method. Thus, an appropriate method can be used for reporting, thereby reducing the overhead of the side link user equipment information message and avoiding the complexity of the side link cache status report.

[0164] In at least one embodiment, when the resource allocation mode is that the network device allocates resources (e.g., mode-1 resource allocation mode), the terminal device sends the remaining destination identifiers excluding the destination identifier where the radio link failure occurs to the network device, that is, the terminal device notifies the network device of the radio link failure using mode 2. Thus, the remaining destination identifiers can be easily matched with the destination index in the edge link cache status report.

[0165] In at least one embodiment, when the resource allocation mode is that the terminal device allocates resources (e.g., mode-2 resource allocation mode), the terminal device sends the destination identifier indicating that a radio link failure has occurred to the network device, that is, the terminal device notifies the network device of the radio link failure using mode 1. Thus, the overhead of the side link user equipment information message can be reduced.

[0166] In at least one embodiment, the terminal device 1021 can set the resource allocation mode according to the configuration information sent by the network device 101. For example, if the terminal device 1021 uses one resource allocation mode, all the purpose identifiers of the terminal device 1021 correspond to the same resource allocation mode, that is, resources are allocated by the terminal device or by the network device; if the terminal device 1021 uses two resource allocation modes, the terminal device 1021 can set the resource allocation mode of some purpose identifiers to be allocated by the network device, and set the resource allocation mode of other purpose identifiers to be allocated by the terminal device according to the configuration information.

[0167] Further, when the terminal device 1021 sets the resource allocation mode according to the configuration information sent by the network device 101, it can determine whether to report the wireless link failure to the network device in mode 1 or mode 2 according to the resource allocation mode. For example, for the purpose identifiers to which resources are allocated by the network device, the wireless link failure of these purpose identifiers is reported in mode 2; for the purpose identifiers to which resources are allocated by the terminal device, the wireless link failure of these purpose identifiers is reported in mode 1.

[0168] In at least one embodiment, the resource allocation mode corresponding to the purpose identifier can be determined by the terminal device 1021. For example, if the terminal device 1021 uses one resource allocation mode, all the purpose identifiers of the terminal device 1021 correspond to the same resource allocation mode, that is, the resources are allocated by the terminal device or by the network device; if the terminal device 1021 uses two resource allocation modes, the terminal device 1021 can independently determine to set the resource allocation mode of some purpose identifiers to be allocated by the network device, and set the resource allocation mode of other purpose identifiers to be allocated by the terminal device.

[0169] Further, when the resource allocation mode is determined, the terminal device 1021 can determine whether to report the wireless link failure to the network device in mode 1 or mode 2 according to the resource allocation mode. For example, for the purpose identifiers to which resources are allocated by the network device, the wireless link failure of these purpose identifiers is reported in mode 2; for the purpose identifiers to which resources are allocated by the terminal device, the wireless link failure of these purpose identifiers is reported in mode 1.

[0170] like Fig.10 As shown, in the case where the resource allocation mode is determined by the terminal device 1021, the method may further include:

[0171] Operation 1002: The terminal device reports a resource allocation method corresponding to the destination identifier to the network device.

[0172] In operation 1002, the terminal device may report a resource allocation method corresponding to a destination identifier to a network device via a side link user equipment information message.

[0173] According to the fifth aspect of the embodiment of the present application, it is possible to determine whether to use method one or method two to report the wireless link failure to the network device based on the resource allocation method. Thus, an appropriate method can be used for reporting, thereby reducing the overhead of the side link user equipment information message and avoiding the complexity of the side link cache status report.

[0174] Sixth aspect of the embodiment

[0175] A sixth aspect of the present application provides a communication method, which corresponds to the method performed by the terminal device of the fifth aspect of the embodiment. The method can be performed by a network device, which can be, for example, Figure 1 network device 101.

[0176] Fig.11 Schematic diagram of the communication method according to the sixth aspect of the embodiment of the present application. Fig.11 As shown, the method includes:

[0177] Operation 1101, in the event of a radio link failure, according to a resource allocation method corresponding to the terminal device, the network device receives a destination identifier of the radio link failure from the terminal device or receives remaining destination identifiers excluding the destination identifier of the radio link failure from the terminal device.

[0178] In operation 1101, when the resource allocation mode is that resources are allocated by the network device (eg, mode-1 resource allocation mode), the network device receives the remaining destination identifiers excluding the destination identifier where a radio link failure occurs from the terminal device.

[0179] In operation 1101, when the resource allocation method is that resources are allocated by the terminal device (for example, mode-2 resource allocation method), the network device receives a destination identifier indicating that a radio link failure has occurred from the terminal device.

[0180] In at least one embodiment, the resource allocation mode of the terminal device can be determined by the network device, and the configuration information for configuring the resource allocation mode can be sent to the terminal device. For example, if the terminal device 1021 uses a resource allocation mode, the configuration information can configure all the purpose identifiers of the terminal device 1021 to correspond to the same resource allocation mode, that is, the resources are allocated by the terminal device or the network device; if the terminal device 1021 uses two resource allocation modes, the network device 101 can configure the resource allocation mode of some purpose identifiers to be allocated by the network device, and configure the resource allocation mode of other purpose identifiers to be allocated by the terminal device.

[0181] In at least one embodiment, the resource allocation mode of the terminal device may be determined by the terminal device, and the network device receives information sent by the terminal device for notifying the resource allocation mode. For example, the information for notifying the resource allocation mode may be sent to the network device via an edge link user equipment information message.

[0182] Furthermore, when the terminal device 1021 determines the resource allocation mode according to the configuration information or autonomously, it can determine whether to report the wireless link failure to the network device in mode 1 or mode 2 according to the resource allocation mode. For example, for the purpose identifiers to which resources are allocated by the network device, the wireless link failure of these purpose identifiers is reported in mode 2; for the purpose identifiers to which resources are allocated by the terminal device, the wireless link failure of these purpose identifiers is reported in mode 1.

[0183] According to the sixth aspect of the embodiment of the present application, it is possible to determine whether to use method one or method two to report the wireless link failure to the network device based on the resource allocation method. Thus, an appropriate method can be used for reporting, thereby reducing the overhead of the side link user equipment information message and avoiding the complexity of the side link cache status report.

[0184] Seventh aspect of the embodiment

[0185] A seventh aspect of the embodiments of the present application provides a communication method, which can be executed by a terminal device, and the terminal device can be, for example, Figure 1 Terminal device 1021.

[0186] The communication method of the seventh aspect of the embodiment of the present application involves how to reduce the signaling overhead of the side link user equipment information message.

[0187] In the seventh aspect of the embodiment of the present application, the terminal device can correspond the purpose identifier with the first index based on configuration information or autonomous determination, and send the first index in a subsequent side link user equipment information message to replace the corresponding purpose identifier, thereby reducing the signaling overhead of the side link user equipment information message.

[0188] Fig.12 is a schematic diagram of a communication method for a vehicle communication (V2X) service according to a seventh aspect of an embodiment of the present application, such as Fig.12 As shown, the method includes:

[0189] Operation 1201: The terminal device receives a radio resource control (RRC) message sent by the network device, where the radio resource control (RRC) message is used to configure a first index for a destination identifier in a sidelink user equipment information (Sidelink UEInformation) message that has been sent by the terminal device; and

[0190] Operation 1202: The terminal device sends a sidelink user equipment information (Sidelink UE Information) message including the first index corresponding to the destination identifier.

[0191] exist Fig.12In the method, the terminal device determines the correspondence between the purpose identifier and the first index according to the configuration information of the network device (ie, the wireless resource control message).

[0192] Fig.13 is another schematic diagram of a communication method for a vehicle communication (V2X) service according to a seventh aspect of an embodiment of the present application, such as Fig.13 As shown, the method includes:

[0193] Operation 1301: The terminal device determines a correspondence between a destination identifier and a first index; and

[0194] Operation 1302: The terminal device sends a sidelink user equipment information (Sidelink UE Information) message containing the first index corresponding to the destination identifier to the network device.

[0195] exist Fig.13 In the method, the terminal device autonomously determines the correspondence between the destination identifier and the first index.

[0196] like Fig.13 As shown, the method also includes:

[0197] Operation 1303: The terminal device sends a message notifying the corresponding relationship between the destination identifier and the first index to the network device.

[0198] According to operation 1303, when the correspondence between the destination identifier and the first index is determined by the terminal device, the correspondence may be notified to the network device, so that the network device may be aware of the correspondence.

[0199] In a seventh aspect of an embodiment of the present application, a destination index (destination index) corresponding to each destination identifier in a side link buffer status report (SL BSR) may be the same as or different from the first index.

[0200] According to the seventh aspect of the embodiment of the present application, the terminal device can correspond the purpose identifier to the first index based on configuration information or autonomous determination, and send the first index in a subsequent side link user equipment information message to replace the corresponding purpose identifier, thereby reducing the signaling overhead of the side link user equipment information message.

[0201] Eighth aspect of the embodiment

[0202] The eighth aspect of the embodiment of the present application provides a communication method, which corresponds to the method performed by the terminal device of the seventh aspect of the embodiment. The method can be performed by a network device, which can be, for example, Figure 1 network device 101.

[0203] Fig.14 Schematic diagram of the communication method according to the seventh aspect of the embodiment of the present application. Fig.14 As shown, the method includes:

[0204] Operation 1401: The network device receives a sidelink UE Information message sent by the terminal device; and

[0205] Operation 1402: The network device sends a side link related configuration message to the terminal device, where the configuration message includes a correspondence between a destination identifier in the side link user equipment information message and a first index.

[0206] In operation 1401, a network device receives a side link user equipment information message sent by a terminal device, where the side link user equipment information message includes a destination identifier.

[0207] In operation 1402, the network device can set the correspondence between the purpose identifier and the first index for the purpose identifier in the received side link user equipment information message, generate a configuration message based on the correspondence, and send the configuration message to the terminal device, whereby the terminal device can determine the correspondence between the purpose identifier and the first index based on the configuration message.

[0208] In addition, after the terminal device determines the correspondence between the destination identifier and the first index, when sending the side link user equipment information message, the first index corresponding to the destination identifier may be included in the side link user equipment information message. Fig.14 As shown, the method may also include:

[0209] Operation 1403: The network device receives a sidelink user equipment information (Sidelink UE Information) message including a first index corresponding to a destination identifier from a terminal device.

[0210] exist Fig.14 In the method shown, the terminal device determines the correspondence between the destination identifier and the first index according to the configuration information sent by the network device. The present application is not limited thereto, and the terminal device may also autonomously determine the correspondence between the destination identifier and the first index.

[0211] Fig.15 FIG. 1 is another schematic diagram of the communication method according to the seventh aspect of the embodiment of the present application. Fig.15 As shown, the method includes:

[0212] Operation 1501: A network device receives a sidelink UE Information message sent by a terminal device, where the sidelink UE Information message includes a correspondence between a destination identifier and a first index; and

[0213] Operation 1502: Receive a sidelink UE Information message containing the first index corresponding to the destination identifier from the terminal device.

[0214] exist Fig.15 In the method shown, the terminal device autonomously determines the correspondence between the destination identifier and the first index, and notifies the network device of the correspondence via a side link user equipment information message.

[0215] In operation 1502, the side link user equipment information message sent by the terminal device may not include a destination identifier, but may include a first index corresponding to the destination identifier, thereby reducing the signaling overhead of the side link user equipment information message.

[0216] In an eighth aspect of an embodiment of the present application, a destination index (destination index) corresponding to each destination identifier in a side link buffer status report (SL BSR) may be the same as or different from the first index.

[0217] According to the eighth aspect of the embodiment of the present application, the network device can be configured or notified of the correspondence between the destination identifier and the first index, and the subsequent side link user equipment information message includes the first index to replace the corresponding destination identifier, thereby reducing the signaling overhead of the side link user equipment information message.

[0218] Ninth aspect of the embodiment

[0219] A ninth aspect of the embodiments of the present application provides a communication method, which can be executed by a terminal device, and the terminal device can be, for example, Figure 1 Terminal device 1021.

[0220] The ninth aspect of the communication method of the embodiment of the present application relates to how to reduce the signaling overhead of the side link user equipment information message.

[0221] Fig.16 is a schematic diagram of a communication method for a vehicle communication (V2X) service according to a ninth aspect of an embodiment of the present application, such as Fig.16 As shown, the method includes:

[0222] Operation 1601, sending a sidelink UE Information message to a network device. When the propagation type (CastType) and / or the quality of service (QoS) corresponding to the destination identifier in the sidelink UE Information message do not change, a field for indicating the propagation type corresponding to the destination identifier and / or a field for indicating the quality of service corresponding to the destination identifier do not appear in the sidelink UE Information message.

[0223] The field used to indicate the propagation type corresponding to the destination identifier may be represented as sl-CastType, for example.

[0224] According to the ninth aspect of the embodiment of the present application, the signaling overhead of the side link user equipment information message can be reduced.

[0225] Tenth aspect of the embodiment

[0226] The tenth aspect of the embodiment of the present application provides a communication method, which corresponds to the method performed by the terminal device of the ninth aspect of the embodiment. The method can be performed by a network device, which can be, for example, Figure 1 network device 101.

[0227] Fig.17 1 is a schematic diagram of a communication method according to the tenth aspect of an embodiment of the present application. Fig.17 As shown, the method includes:

[0228] Operation 1701: receiving a sidelink user equipment information (Sidelink UE Information) message from a terminal device, wherein, when a propagation type (CastType) and / or a quality of service (QoS) corresponding to a destination identifier in the sidelink user equipment information (Sidelink UE Information) message do not change, a field for indicating the propagation type corresponding to the destination identifier and / or a field for indicating the quality of service corresponding to the destination identifier do not appear in the sidelink user equipment information message.

[0229] The field used to indicate the propagation type corresponding to the destination identifier may be represented as sl-CastType, for example.

[0230] According to the tenth aspect of the embodiment of the present application, the signaling overhead of the side link user equipment information message can be reduced.

[0231] Twelfth Aspect of the Embodiments

[0232] The twelfth aspect of the embodiment of the present application provides at least one communication device, which is applied to a terminal device and corresponds to the methods of the first, third, fifth, seventh, and ninth aspects of the embodiment, respectively. Since the principle of solving the problem by the communication device is similar to the methods of the first, third, fifth, seventh, and ninth aspects of the embodiment, its specific implementation can refer to the implementation of the methods of the first, third, fifth, seventh, and ninth aspects of the embodiment, and the same contents will not be repeated.

[0233] Fig.18 is a schematic diagram of a communication device according to the twelfth aspect of an embodiment of the present application, such as Fig.18 As shown, the device 180 includes: a first communication unit 181. The first communication unit 181 can implement Figure 2 The method shown. Fig.18 For detailed instructions, please refer to Figure 2 A description of each step.

[0234] Fig.19 is another schematic diagram of the communication device according to the twelfth aspect of the embodiment of the present application, such as Fig.19 As shown, the device 190 includes: a third communication unit 191. The third communication unit 191 can be implemented Figure 8 The method shown. Fig.19 For detailed instructions, please refer to Figure 8 A description of each step.

[0235] Fig. 20 is another schematic diagram of the communication device according to the twelfth aspect of the embodiment of the present application, such as Fig. 20 As shown, the device 200 includes: a fifth communication unit 201. The fifth communication unit 201 can be implemented Fig.10 The method shown. Fig. 20 For detailed instructions, please refer to Fig.10 A description of each step.

[0236] Fig.21 is another schematic diagram of the communication device according to the twelfth aspect of the embodiment of the present application, such as Fig.21 As shown, the device 210 includes: a seventh communication unit 211. The seventh communication unit 211 can implement Fig.12 The method shown. Fig.21 For detailed instructions, please refer to Fig.12 A description of each step.

[0237] Fig. 22 is another schematic diagram of the communication device according to the twelfth aspect of the embodiment of the present application, such as Fig. 22 As shown, the device 220 includes: an eighth communication unit 221. The eighth communication unit 221 can implement Fig.13 The method shown. Fig. 22For detailed instructions, please refer to Fig.13 A description of each step.

[0238] Fig.23 is another schematic diagram of the communication device according to the twelfth aspect of the embodiment of the present application, such as Fig.23 As shown, the device 230 includes: an eleventh communication unit 231. The eleventh communication unit 231 can implement Fig.16 The method shown. Fig.23 For detailed instructions, please refer to Fig.16 A description of each step.

[0239] Thirteenth Aspect of the Embodiment

[0240] The thirteenth aspect of the embodiment of the present application also provides at least one communication device, which is applied to a network device and corresponds to the methods of the second, fourth, sixth, eighth, and tenth aspects of the embodiment, respectively. Since the principle of solving the problem by the communication device is similar to the methods of the second, fourth, sixth, eighth, and tenth aspects of the embodiment, its specific implementation can refer to the implementation of the methods of the second, fourth, sixth, eighth, and tenth aspects of the embodiment, and the same contents will not be repeated.

[0241] Fig.24 is a schematic diagram of a communication device according to the thirteenth aspect of an embodiment of the present application, such as Fig.24 As shown, the device 240 includes: a second communication unit 241. The second communication unit 241 can implement Figure 5 The method shown. Fig.24 For detailed instructions, please refer to Figure 2 A description of each step.

[0242] Fig.25 is another schematic diagram of the communication device according to the thirteenth aspect of the embodiment of the present application, such as Fig.25 As shown, the device 250 includes: a fourth communication unit 251. The fourth communication unit 251 can be implemented Fig. 9 The method shown. Fig.25 For detailed instructions, please refer to Fig. 9 A description of each step.

[0243] Fig.26 is another schematic diagram of the communication device according to the thirteenth aspect of the embodiment of the present application, such as Fig.26 As shown, the device 260 includes: a sixth communication unit 261. The sixth communication unit 261 can implement Fig.11 The method shown. Fig.26 For detailed instructions, please refer to Fig.11 A description of each step.

[0244] Fig. 27is another schematic diagram of the communication device according to the thirteenth aspect of the embodiment of the present application, such as Fig. 27 As shown, the device 270 includes: a ninth communication unit 271. The ninth communication unit 271 can implement Fig.14 The method shown. Fig. 27 For detailed instructions, please refer to Fig.14 A description of each step.

[0245] Fig.28 is another schematic diagram of the communication device according to the thirteenth aspect of the embodiment of the present application, such as Fig.28 As shown, the device 280 includes: a tenth communication unit 281. The tenth communication unit 281 can implement Fig.15 The method shown. Fig.28 For detailed instructions, please refer to Fig.15 A description of each step.

[0246] Fig.29 is another schematic diagram of the communication device according to the thirteenth aspect of the embodiment of the present application, such as Fig.29 As shown, the device 290 includes: a twelfth communication unit 291. The twelfth communication unit 291 can be implemented Fig.17 The method shown. Fig.29 For detailed instructions, please refer to Fig.17 A description of each step.

[0247] Fourteenth Aspect of the Embodiments

[0248] A fourteenth aspect of the embodiment provides a terminal device.

[0249] Fig.30 Schematic diagram of the terminal device in the embodiment of the present application. Fig.30 As shown, the terminal device 3000 may include: a central processing unit (CPU) 3001 and a memory 3002; the memory 3002 is coupled to the central processing unit 3001. The memory 3002 may store various data; in addition, it may store a data processing program, and execute the program under the control of the central processing unit 3001 to instruct the terminal device according to the received signaling.

[0250] In one implementation, the functions of each device in the twelfth aspect of the embodiment may be integrated into the central processor 3001 of the terminal device 3000. The central processor 3001 may be configured to implement the methods of the first, third, fifth, seventh, and ninth aspects of the embodiment.

[0251] For example, the central processor 3001 can be configured to perform control so that the terminal device 3000 executes the methods of the first, third, fifth, seventh, and ninth aspects.

[0252] In addition, other configuration methods of the central processor 3001 can refer to the methods in the first, third, fifth, seventh and ninth aspects, which will not be repeated here.

[0253] In another implementation, each device in the twelfth aspect of the embodiment may be configured separately from the central processor 3001. For example, each device in the twelfth aspect of the embodiment may be configured as a chip connected to the central processor 3001, such as Fig.30 The units shown implement the functions of the various devices in the twelfth aspect of the embodiment through the control of the central processor 3001. In addition, the terminal device 3000 may also have an input unit 3002, a communication module 3003, a power supply 3004 and a display 3005.

[0254] Fifteenth Aspect of the Embodiments

[0255] A fifteenth aspect of the embodiment provides a network device.

[0256] Fig.31 Schematic diagram of the network device structure of the embodiment of the present invention. Fig.31 As shown, the network device 3100 may include: a central processing unit (CPU) 3101 and a memory 3102; the memory 3102 is coupled to the central processing unit 3101. The memory 3102 may store various data; in addition, it may store a data processing program, and execute the program under the control of the central processing unit 3101.

[0257] In one implementation, the functions of each device in the thirteenth aspect of the embodiment may be integrated into the central processor 3101. The central processor 3101 may be configured to implement the methods of the second, fourth, sixth, eighth, and tenth aspects of the embodiment.

[0258] For example, the central processor 3101 may be configured to perform control so that the network device 3100 executes the methods of the second, fourth, sixth, eighth, and tenth aspects of the embodiments.

[0259] In addition, other configuration methods of the central processor 3101 can refer to the second, fourth, sixth, eighth, and tenth methods of the embodiment, which will not be repeated here.

[0260] In another implementation, each device in the thirteenth aspect of the embodiment may be configured separately from the central processor 3101. For example, each device in the thirteenth aspect of the embodiment may be configured as a chip connected to the central processor 3101, such as Fig.31 The units shown implement the functions of the various devices in the thirteenth aspect of the embodiment through the control of the central processing unit 3101.

[0261] In addition, if Fig.31As shown, the network device 3100 may also include: a transceiver 3103 and an antenna 3104, etc.; wherein the functions of the above components are similar to those of the prior art and are not described in detail here. It is worth noting that the network device 3100 does not necessarily have to include Fig.31 In addition, the network device 3100 may also include Fig.31 For components not shown, reference may be made to the prior art.

[0262] Fifteenth Aspect of the Embodiments

[0263] The fifteenth aspect of the embodiment provides a communication system, which at least includes the apparatus of the twelfth aspect of the embodiment and the apparatus of the twelfth aspect of the embodiment. The contents of the twelfth aspect and the thirteenth aspect of the embodiment are combined here and will not be repeated here.

[0264] An embodiment of the present invention also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a communication device or terminal device or network device of a vehicle communication (V2X) service to execute a communication method of a vehicle communication (V2X) service as described in a corresponding embodiment.

[0265] An embodiment of the present invention also provides a computer-readable program, wherein when the program is executed in a communication device or terminal device or network device of a vehicle communication (V2X) service, the program enables the communication device or terminal device or network device of the vehicle communication (V2X) service to execute the communication method of the vehicle communication (V2X) service of the corresponding embodiment.

[0266] The above devices and methods of the present invention can be implemented by hardware, or by hardware combined with software. The present invention relates to such a computer-readable program, which, when executed by a logic component, enables the logic component to implement the above-mentioned devices or components, or enables the logic component to implement the above-mentioned various methods or steps. The present invention also relates to a storage medium for storing the above-mentioned program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0267] Each processing method in each device described in conjunction with the embodiments of the present invention may be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams in the accompanying drawings and / or one or more combinations of functional block diagrams may correspond to various software modules of a computer program flow or to various hardware modules. These software modules may correspond to the various steps shown in the method of the present application, respectively. These hardware modules may be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0268] The software module may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in a memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (e.g., a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0269] For one or more of the functional block diagrams and / or one or more combinations of the functional block diagrams, it can be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in the present application. For one or more of the functional block diagrams and / or one or more combinations of the functional block diagrams, it can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0270] The present invention has been described above in conjunction with specific embodiments, but it should be clear to those skilled in the art that these descriptions are exemplary and are not intended to limit the scope of protection of the present invention. Those skilled in the art can make various modifications and variations to the present invention based on the principles of the present invention, and these modifications and variations are also within the scope of the present invention.

[0271] This application also provides the following notes:

[0272] 1. A communication device for a vehicle-to-everything (V2X) service, applied to a terminal device, the device comprising a first communication unit, wherein the first communication unit:

[0273] Detecting a radio link failure (Radio Link Failure) of the side link; and

[0274] The network device is notified via a sidelink UE Information message that radio link failures occur in all side links of the terminal device.

[0275] 2. The device as described in Note 1, wherein:

[0276] In the case where all side links of the terminal device fail in wireless link failure,

[0277] The side link transmit resource request list (sl-TxResourceReqList) field of the side link user equipment information message does not appear in the side link user equipment information message.

[0278] 3. The device as described in Note 1, wherein:

[0279] In the case where all side links of the terminal device fail in wireless link failure,

[0280] The content of the side link transmit resource request list (sl-TxResourceReqList) field of the side link user equipment information message is empty.

[0281] 4. The device as described in Note 3, wherein:

[0282] The content of the side link transmission resource request list (sl-TxResourceReqList) field of the side link user equipment information message is empty, which means:

[0283] The number of elements in the side link transmission resource request list (SL-TxResourceReqList) of the side link user equipment information message is 0.

[0284] 5. The device as described in Note 1, wherein:

[0285] In the case where all side links of the terminal device fail in wireless link failure,

[0286] The content of the elements in the side link transmit resource request list (sl-TxResourceReqList) field of the side link user equipment information message is empty.

[0287] 6. The device as described in Note 5, wherein:

[0288] The content of the element being empty means that the content of the element does not contain side link destination identification (sl-DestinationIdentity) or side link cast type (sl-CastType) or quality of service (QoS) information.

[0289] 7. The device as described in Note 1, wherein:

[0290] The side link user equipment information message contains indication information for indicating that radio link failure occurs in all side links of the terminal device.

[0291] 8. A communication device for a vehicle-to-everything (V2X) service, applied to a network device, the device comprising a second communication unit, wherein the second communication unit:

[0292] All side links of the terminal device that receive notification from the terminal device via a sidelink user equipment information (Sidelink UE Information) message experience radio link failure.

[0293] 9. The device as described in Supplement 8, wherein:

[0294] In the case where all side links of the terminal device fail in wireless link failure,

[0295] The side link transmit resource request list (sl-TxResourceReqList) field of the side link user equipment information message does not appear in the side link user equipment information message.

[0296] 10. The device as described in Supplement 8, wherein:

[0297] In the case where all side links of the terminal device fail in wireless link failure,

[0298] The content of the side link transmit resource request list (sl-TxResourceReqList) field of the side link user equipment information message is empty.

[0299] 11. The device as described in Note 10, wherein:

[0300] The content of the side link transmission resource request list (sl-TxResourceReqList) field of the side link user equipment information message is empty, which means:

[0301] The number of elements in the side link transmission resource request list (SL-TxResourceReqList) of the side link user equipment information message is 0.

[0302] 12. The device as described in Supplement 8, wherein:

[0303] In the case where all side links of the terminal device fail in wireless link failure,

[0304] The content of the elements in the side link transmit resource request list (sl-TxResourceReqList) field of the side link user equipment information message is empty.

[0305] 13. The device as described in Note 12, wherein:

[0306] The content of the element being empty means that the content of the element does not contain side link destination identification (sl-DestinationIdentity) or side link cast type (sl-CastType) or quality of service (QoS) information.

[0307] 14. The device as described in Supplementary Note 8, wherein:

[0308] The side link user equipment information message contains indication information for indicating that radio link failure occurs in all side links of the terminal device.

[0309] 15. A communication device for a vehicle-to-everything (V2X) service, applied to a terminal device, the device comprising a third communication unit, the third communication unit:

[0310] Sending a sidelink UE Information message to a network device; and

[0311] Determine the mapping relationship between the destination identifier and the destination index in the edge link cache status report.

[0312] 16. The device as described in Note 15, wherein:

[0313] Determining the mapping relationship between the destination identifier and the destination index in the edge link cache status report includes:

[0314] According to the order of the destination identifiers in the previous side link user equipment information message, remove the destination identifiers where the radio link failure (Radio Link Failure) has occurred and then map them with the destination indexes in the side link cache status report in sequence; or

[0315] Mapping the destination identifiers in order from largest to smallest or from smallest to largest with the destination indexes in the edge link cache status report; or

[0316] The destination index is the same as the predetermined bit in the destination identifier, and the destination identifier is mapped to the destination index according to the destination index and the predetermined bit in the destination identifier; or

[0317] After the last destination identifier is filled to the position of the destination identifier where the radio link failure (Radio Link Failure) occurs, the destination identifiers are mapped with the destination indexes in sequence.

[0318] 17. The device as described in Note 15, wherein:

[0319] Determining the mapping relationship between the destination identifier and the destination index in the edge link cache status report includes:

[0320] The terminal device determines the above-mentioned corresponding relationship according to a message received from the network device for configuring a mapping relationship between a destination identifier and a destination index in an edge link cache status report.

[0321] 18. The device as described in Note 15, wherein:

[0322] The third communication unit also:

[0323] A message for reporting a mapping relationship between a destination identifier and a destination index in an edge link cache status report is sent to a network device.

[0324] 19. A communication device for a vehicle-to-everything (V2X) service, applied to a network device, the device comprising a fourth communication unit, the fourth communication unit:

[0325] receiving a sidelink UE Information message; and

[0326] Determine the mapping relationship between the destination identifier and the destination index in the edge link cache status report.

[0327] 20. The device as described in Note 19, wherein:

[0328] Determining the mapping relationship between the destination identifier and the destination index in the edge link cache status report includes:

[0329] According to the order of the destination identifiers in the previous side link user equipment information message, remove the destination identifiers where the radio link failure (Radio Link Failure) has occurred and then map them with the destination indexes in the side link cache status report in sequence; or

[0330] Mapping the destination identifiers in order from largest to smallest or from smallest to largest with the destination indexes in the edge link cache status report; or

[0331] The destination index is the same as the predetermined bit in the destination identifier, and the destination identifier is mapped to the destination index according to the destination index and the predetermined bit in the destination identifier; or

[0332] After the last destination identifier is filled to the position of the destination identifier where the radio link failure (Radio Link Failure) occurs, the destination identifiers are mapped with the destination indexes in sequence.

[0333] 21. The device as described in Note 19, wherein:

[0334] The fourth communication unit also:

[0335] A message for configuring a mapping relationship between a destination identifier and a destination index in an edge link cache status report is sent to a terminal device.

[0336] 22. The device as described in Note 19, wherein:

[0337] Determining the mapping relationship between the destination identifier and the destination index in the edge link cache status report includes:

[0338] The network device determines the mapping relationship according to a message received from the terminal device for reporting the mapping relationship between the destination identifier and the destination index in the edge link cache status report.

[0339] 23. A communication device for a vehicle-to-everything (V2X) service, applied to a terminal device, the device comprising a fifth communication unit, the fifth communication unit:

[0340] In the event of a radio link failure, a destination identifier indicating that the radio link failure has occurred is sent to the network device, or remaining destination identifiers excluding the destination identifier indicating that the radio link failure has occurred are sent to the network device according to the resource allocation method.

[0341] 24. The device as described in Note 23, wherein:

[0342] In the case where the resource allocation method is that the network device allocates resources,

[0343] The fifth communication unit sends the remaining destination identifiers excluding the destination identifier in which the wireless link failure occurs to the network device.

[0344] 25. The device as described in Note 23, wherein:

[0345] In the case where the resource allocation mode is that the terminal device allocates resources,

[0346] The fifth communication unit sends the destination identifier indicating that a wireless link failure has occurred to the network device.

[0347] 26. The device according to any one of Notes 23 to 25, wherein:

[0348] The fifth communication unit also sets a resource allocation method according to the configuration information sent by the network device.

[0349] 27. The device according to any one of Notes 35 to 25, wherein:

[0350] The fifth communication unit also determines a resource allocation method corresponding to the destination identifier.

[0351] 28. The device as described in Note 27, wherein:

[0352] The fifth communication unit also reports the resource allocation method corresponding to the destination identifier to the network device.

[0353] 29. A communication device for a vehicle-to-everything (V2X) service, applied to a network device, the device comprising a sixth communication unit, the sixth communication unit:

[0354] In the event of a radio link failure, based on the resource allocation method corresponding to the terminal device, the sixth communication unit receives a destination identifier of the radio link failure from the terminal device or receives the remaining destination identifiers excluding the destination identifier of the radio link failure from the terminal device.

[0355] 30. The device as described in Note 29, wherein:

[0356] In the case where the resource allocation method is that the network device allocates resources,

[0357] The sixth communication unit receives, from the terminal device, remaining destination identifiers excluding the destination identifier in which a radio link failure occurs.

[0358] 31. The device as described in Note 29, wherein:

[0359] In the case where the resource allocation mode is that the terminal device allocates resources,

[0360] The sixth communication unit receives the destination identifier indicating that a wireless link failure has occurred from the terminal device.

[0361] 32. The device according to any one of Notes 29 to 31, wherein:

[0362] The sixth communication unit also sends configuration information for configuring a resource allocation method to the terminal device.

[0363] 33. The device according to any of Notes 29 to 31, wherein:

[0364] The sixth communication unit also receives information from the terminal device for reporting the resource allocation method corresponding to the purpose identifier.

[0365] 34. A communication device for a vehicle-to-everything (V2X) service, applied to a terminal device, the device comprising a seventh communication unit, the seventh communication unit:

[0366] Receiving a radio resource control (RRC) message sent by a network device, where the radio resource control message is used to configure a first index for a destination identifier in a sidelink user equipment information (Sidelink UE Information) message that has been sent by the terminal device; and

[0367] Send a sidelink user equipment information (SidelinkUE Information) message including the first index corresponding to the destination identifier.

[0368] 35. A vehicle communication (V2X) service device, applied to a terminal device, the device comprising an eighth communication unit, the eighth communication unit:

[0369] Determine a correspondence between the destination identifier and the first index; and

[0370] Send a sidelink user equipment information (Sidelink UE Information) message containing the first index corresponding to the destination identifier to the network device.

[0371] 36. The device according to Note 35, wherein the seventh communication unit or the eighth communication unit further comprises:

[0372] A message notifying the corresponding relationship is sent to the network device.

[0373] 37. The device according to any one of Notes 34 to 36, wherein:

[0374] The destination index corresponding to each destination identifier in the side link buffer status report (SL BSR) is the same as or different from the first index.

[0375] 38. A communication device for a vehicle-to-everything (V2X) service, applied to a network device, the device comprising a ninth communication unit, the ninth communication unit:

[0376] The network device receives a sidelink user equipment information (Sidelink UEInformation) message sent by the terminal device; and

[0377] The network device sends a side link related configuration message to the terminal device, where the configuration message includes a correspondence between a destination identifier in the side link user equipment information message and a first index.

[0378] 39. The device according to supplementary note 38, wherein the ninth communication unit further comprises:

[0379] Receive sidelink user equipment information (Sidelink UE Information) including the first index corresponding to the destination identifier from the terminal device.

[0380] 40. A vehicle-to-everything (V2X) service device, applied to a network device, the device comprising a tenth communication unit, the tenth communication unit:

[0381] Receiving a sidelink UE Information message sent by a terminal device, wherein the sidelink UE Information message includes a correspondence between a destination identifier and a first index; and

[0382] Receive sidelink terminal device information (Sidelink UE Information) containing the first index corresponding to the destination identifier from the terminal device.

[0383] 41. The device according to any one of Notes 38 to 40, wherein:

[0384] The destination index corresponding to each destination identifier in the side link buffer status report (SL BSR) is the same as or different from the first index.

[0385] 42. A communication device for a vehicle-to-everything (V2X) service, applied to a terminal device, the device comprising an eleventh communication unit, the eleventh communication unit:

[0386] A sidelink UE Information message is sent to a network device, wherein, when a propagation type (CastType) and / or a quality of service (QoS) corresponding to a destination identifier in the sidelink UE Information message do not change, a field for indicating the propagation type corresponding to the destination identifier and / or a field for indicating the quality of service corresponding to the destination identifier do not appear in the sidelink UE Information message.

[0387] 43. A communication device for a vehicle-to-everything (V2X) service, applied to a network device, the device comprising a twelfth communication unit, the twelfth communication unit:

[0388] A sidelink UE Information message is received from a terminal device, wherein, when a propagation type (CastType) and / or a quality of service (QoS) corresponding to a destination identifier in the sidelink UE Information message do not change, a field for indicating the propagation type corresponding to the destination identifier and / or a field for indicating the quality of service corresponding to the destination identifier do not appear in the sidelink UE Information message.

Claims

1. A communication device for a vehicle-to-everything (V2X) service, applied to a terminal device, the device comprising a first communication unit, wherein the first communication unit: Detecting a radio link failure (Radio Link Failure) on the edge link; and Notify the network device of a radio link failure in the side link of the terminal device through a side link UE Information message, in, In the case where all side links of the terminal device fail in wireless link failure, The side link transmit resource request list (sl-TxResourceReqList) field of the side link user equipment information message does not appear in the side link user equipment information message.

2. The device according to claim 1, wherein: The side link user equipment information message contains indication information for indicating that radio link failure occurs in all side links of the terminal device.

3. The device according to claim 1, wherein: The side link user equipment information message includes a destination identifier of the side link where the radio link failure occurs.

4. The device according to claim 1, wherein: The side link user equipment information message includes a destination identifier of the side link, but does not include a destination identifier of the side link where a radio link failure occurs.

5. A communication device for a vehicle-to-everything (V2X) service, applied to a network device, the device comprising a second communication unit, wherein the second communication unit: The terminal device notified by the terminal device through a sidelink UE Information message that a radio link failure occurs in the sidelink of the terminal device, in, In the case where all side links of the terminal device fail in wireless link failure, The side link transmit resource request list (sl-TxResourceReqList) field of the side link user equipment information message does not appear in the side link user equipment information message.

6. The device according to claim 5, wherein: The side link user equipment information message contains indication information for indicating that radio link failure occurs in all side links of the terminal device.

7. The device according to claim 5, wherein: The side link user equipment information message includes a destination identifier of the side link where the radio link failure occurs.

8. The device according to claim 5, wherein: The side link user equipment information message includes a destination identifier of the side link, but does not include a destination identifier of the side link where a radio link failure occurs.

Images