Communication method, and apparatus

Abstract

Provided in the present application are a communication method, and an apparatus. The method comprises: a first terminal device receives a first message from an access network device, and after receiving data of a first radio bearer from a second terminal device, sends a second message to the second terminal device, the first message instructing the first terminal device to release configuration information of the first radio bearer, the configuration information being used for forwarding of data of the first radio bearer, the first radio bearer being a radio bearer between the second terminal device and the access network device, the second terminal device communicating with the access network device by means of the first terminal device, and the second message instructing to release a connection between the second terminal device and a first device, or the second message being used for instructing the state of the second terminal device to be switched from a connected state to an idle state or a deactivated state. The method can solve the problem of inconsistency of state understanding of a far-end terminal device and an access network device, so as to reduce power consumption of far-end terminal devices.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on August 25, 2023, with application number 202311086915.4 and application name “A Communication Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0004] In some application scenarios, relay technology is required, where one terminal device can assist another terminal device in communicating with the access network device. Specifically, a remote terminal device communicates with the access network device through the cooperation of a relay terminal device. In other application scenarios, multipath configuration may be required for the terminal device, where the remote terminal device can communicate with the access network device directly or through the cooperation of a relay terminal device.

[0005] The access network device sends a radio resource control (RCC) release message to the remote terminal device, indicating that the state of the remote terminal device has entered the RRC idle state or the RRC deactivated state from the RRC connected state. In the scenario where the RRC release message transmission fails, the access network device believes that the state of the remote terminal device has entered the RRC idle state or the RRC deactivated state, and releases the context information of the remote terminal device in the core network or base station. However, the state of the remote terminal device may remain in the RRC connected state. In other words, the access network side and the remote terminal side have inconsistent understandings of the state of the remote terminal device, which will lead to power consumption of the remote terminal device.

[0006] Summary of the Invention

[0007] The present application provides a communication method and apparatus, which can solve the problem of inconsistent understanding of the status of a remote terminal device between an access network side and a remote terminal side, thereby reducing the power consumption of the remote terminal device.

[0008] In the first aspect, an embodiment of the present application provides a communication method, which can be executed by a first terminal device or a module (such as a chip) applied to the first terminal device. Taking the first terminal device executing the method as an example, the method includes: the first terminal device receives a first message from an access network device, the first message is used to indicate the configuration information of releasing the first radio bearer; the configuration information is used for data forwarding of the first radio bearer; the first radio bearer is a radio bearer between a second terminal device and the access network device, and the second terminal device communicates with the access network device through the first terminal device; after receiving the data of the first radio bearer from the second terminal device, the first terminal device sends a second message to the second terminal device, the second message is used to indicate the release of the connection between the second terminal device and the first device, or the second message is used to indicate that the state of the second terminal device is switched from a connected state to an idle state or a deactivated state.

[0009] Through such a design, when the access network device side and the second terminal device side have inconsistent understandings of the status of the second terminal device, the second terminal device can be put into an idle state or a deactivated state, thereby reducing the power consumption of the Remote UE. Optionally, the first terminal device can also be replaced by a relay terminal device or a Relay UE, the second terminal device can also be replaced by a remote terminal device or a Remote UE, and the access network device can also be replaced by a network device or a base station.

[0010] In one possible design, after receiving data from the second terminal device on the first radio bearer, sending a second message to the second terminal device includes: continuously receiving N data packets from the second terminal device on the first radio bearer, performing packet loss processing on the N data packets, and sending the second message to the second terminal device; wherein N is an integer greater than 1. Optionally, the value of N is indicated by the access network device, or the value of N is preconfigured.

[0011] Such a design is consistent with the signaling interaction logic. The first terminal device actively triggers the release of the second terminal device after packet loss, so that the second terminal device can quickly enter the idle state or deactivated state.

[0012] In one possible design, the first message is also used to indicate that the access network device configures the state of the second terminal device to be idle or deactivated. Through such a design, the first terminal device can determine the state of the second terminal device configured by the access network device.

[0013] In one possible design, the second message includes a first identifier or a second identifier; wherein the first identifier indicates that the state of the second terminal device has switched from a connected state to an idle state, and the second identifier indicates that the state of the second terminal device has switched from a connected state to a deactivated state. With such a design, the target state of the second terminal device is clearly indicated, facilitating subsequent communication processing.

[0014] In one possible design, the configuration information indicates one or more of the following: identification information of the first radio bearer;

[0015] The identification information of the second terminal device; the mapping relationship between the first wireless bearer and the second terminal device; the mapping relationship between the first wireless bearer and the first bearer of the first communication link, the first communication link is the communication link between the first terminal device and the second terminal device; the mapping relationship between the first wireless bearer and the second bearer of the second communication link, the second communication link is the communication link between the first terminal device and the access network device. It can be understood that the wireless bearer between the second terminal device and the access network device can be one or more, and the first wireless bearer is any one of them. Through such a design, the configuration information of a specific wireless bearer can be released, and it can be applied to a variety of communication scenarios, which is more flexible.

[0016] In a second aspect, an embodiment of the present application provides a communication method, which can be executed by a second terminal device or a module (such as a chip) applied to the second terminal device. Taking the second terminal device executing the method as an example, the method includes: the second terminal device sends at least one data of a first wireless bearer to the first terminal device; the first wireless bearer is a wireless bearer between the second terminal device and the access network device, and the second terminal device communicates with the access network device through the first terminal device; the second terminal device receives a second message from the first terminal device, the second message indicates the release of the connection between the second terminal device and the first device, or the second message indicates that the state of the second terminal device is switched from a connected state to an idle state or a deactivated state.

[0017] In one possible design, after receiving the second message from the first terminal device, the second terminal device releases the connection between the second terminal device and the first terminal device.

[0018] In one possible design, after receiving the second message from the first terminal device, the second terminal device switches the state of the second terminal device from a connected state to an idle state or a deactivated state.

[0019] In one possible design, the second terminal device switches the state of the second terminal device from a connected state to an idle state or a deactivated state, including: if the second message includes a first identifier, switching the state of the second terminal device from a connected state to an idle state; or if the second message includes a second identifier, switching the state of the second terminal device from a connected state to a deactivated state.

[0020] In a third aspect, an embodiment of the present application provides a communication method, which can be executed by an access network device or a module (such as a chip) applied to the access network device. Taking the access network device executing the method as an example, the method includes: the access network device sends a third message to the second terminal device through the first terminal device, and the third message indicates that the state of the second terminal device is switched from the connected state to the idle state or the deactivated state; if the first information from the first terminal device is received, the access network device sends a fourth message to the first terminal device; wherein the first information includes the data of the second terminal device, or the first information is used to indicate that the connection between the first terminal device and the second terminal device has been released; the fourth message is used to indicate the release of the second terminal device.

[0021] Through such a design, after the access network device instructs to release the RRC connection of the second terminal device, in the scenario where data from the second terminal device or an indication that the connection between terminals has been released is received, the access network device releases the second terminal device through the first terminal device, facilitating the second terminal device to re-establish the RRC, thereby reducing the power consumption of the Remote UE. Optionally, the first terminal device can also be replaced by a relay terminal device or a Relay UE, the second terminal device can also be replaced by a remote terminal device or a Remote UE, and the access network device can also be replaced by a network device or a base station.

[0022] In one possible design, the fourth message is also used to indicate the release of configuration information of the first wireless bearer of the second terminal device, and the configuration information is used for data forwarding of the first wireless bearer; the first wireless bearer is a wireless bearer between the second terminal device and the access network device.

[0023] In one possible design, the fourth message is also used to instruct the access network device to configure the state of the second terminal device to be an idle state or a deactivated state.

[0024] In one possible design, the fourth message is also used to instruct the first terminal device to release the connection between the first terminal device and the second terminal device.

[0025] In one possible design, if the access network device does not receive the first information within a preset time period after sending the third message, the third message is resent to the second terminal device through the first terminal device.

[0026] In one possible design, when the first information indicates that the connection between the first terminal device and the second terminal device has been released, the first information is sidelink user information SUI.

[0027] In a fourth aspect, an embodiment of the present application provides a communication method, which can be executed by a second terminal device or a module (such as a chip) applied to the second terminal device. Taking the second terminal device executing the method as an example, the method includes: the second terminal device receives timing configuration information, and the timing configuration information indicates a first time period; if there is no data transmission on the first communication link and the third communication link during the first time period, the second terminal device can switch the state of the second terminal device from a connected state to an idle state or a deactivated state; wherein the first communication link is a communication link between the second terminal device and the first terminal device; and the third communication link is a communication link between the second terminal device and the access network device.

[0028] This design can be applied to multi-path relay scenarios. By introducing a timing mechanism, when the second terminal device has no data transmission after the timing times out, the second terminal device automatically enters the idle state or deactivated state, avoiding the problem of inconsistent states caused by the access network device failing to instruct the second terminal device to enter the idle state or deactivated state, and can reduce the energy consumption of the second terminal device. Optionally, the first terminal device can also be replaced by a relay terminal device or Relay UE, the second terminal device can also be replaced by a remote terminal device or Remote UE, and the access network device can also be replaced by a network device or base station.

[0029] In one possible design, no data transmission occurs on the first communication link, including no data transmission occurs on at least one channel between the second terminal device and the first terminal device. For example, the channels between the second terminal device and the first terminal device include a side control channel and / or a side traffic channel.

[0030] In one possible design, no data transmission occurs on the third communication link, including no data transmission occurs on at least one channel between the first terminal device and the access network device. For example, the channel between the first terminal device and the access network device includes one or more of a dedicated service channel, a dedicated control channel, a common control channel, and a multicast service channel.

[0031] In one possible design, before receiving the timing configuration information, the second terminal device may transmit data with the network device based on the first communication link and the second communication link, and transmit data with the access network device based on the third communication link. The second communication link is the communication link between the first terminal device and the access network device.

[0032] In the fifth aspect, an embodiment of the present application also provides a communication device, which can be used to execute the method of the first aspect. The device can be a first terminal device, or the device can be a component in the first terminal device (for example, a chip, or a chip system, or a circuit), or it can be a device that can be used in combination with the first terminal device.

[0033] In one possible implementation, the device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the first aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuits and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the method described in the first aspect or any possible implementation of the first aspect.

[0034] In the sixth aspect, an embodiment of the present application also provides a communication device, which can be used to execute the method of the second aspect. The device can be a second terminal device, or the device can be a component in the second terminal device (for example, a chip, or a chip system, or a circuit), or it can be a device that can be used in conjunction with the second terminal device.

[0035] In one possible implementation, the device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the second aspect. The module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the method described in the second aspect or any possible implementation of the second aspect.

[0036] In the seventh aspect, an embodiment of the present application also provides a communication device, which can be used to execute the method of the third aspect. The device can be an access network device, or the device can be a component in the access network device (for example, a chip, or a chip system, or a circuit), or it can be a device that can be used in conjunction with the access network device.

[0037] In one possible implementation, the device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the third aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuits and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the method described in the third aspect or any possible implementation of the third aspect.

[0038] In the eighth aspect, an embodiment of the present application also provides a communication device, which can be used to execute the method of the fourth aspect. The device can be a second terminal device, or the device can be a component in the second terminal device (for example, a chip, or a chip system, or a circuit), or it can be a device that can be used in combination with the second terminal device.

[0039] In one possible implementation, the device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the fourth aspect. The module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the method described in the fourth aspect or any possible implementation of the fourth aspect.

[0040] In the ninth aspect, an embodiment of the present application provides a device, which includes: at least one processor and a communication interface; wherein the communication interface is used to communicate with other devices; the processor is used to run a set of programs so that the device can implement the method provided in the above-mentioned first aspect or any possible implementation method thereof.

[0041] In the tenth aspect, an embodiment of the present application provides a device, which includes: at least one processor and a communication interface; wherein the communication interface is used to communicate with other devices; the processor is used to run a set of programs so that the device can implement the method provided in the above-mentioned second aspect or any possible implementation method thereof.

[0042] In the eleventh aspect, an embodiment of the present application provides a device, which includes: at least one processor and a communication interface; wherein the communication interface is used to communicate with other devices; the processor is used to run a set of programs so that the device can implement the method provided in the above-mentioned third aspect or any possible implementation method thereof.

[0043] In the twelfth aspect, an embodiment of the present application provides a device, which includes: at least one processor and a communication interface; wherein the communication interface is used to communicate with other devices; the processor is used to run a set of programs so that the device can implement the method provided in the above-mentioned fourth aspect or any possible implementation method thereof.

[0044] In the thirteenth aspect, an embodiment of the present application also provides a computer storage medium, which stores a software program. When the software program is read and executed by one or more processors, it can implement the method provided by the above-mentioned first aspect or any possible implementation method thereof, or implement the method provided by the above-mentioned second aspect or any possible implementation method thereof, or implement the method provided by the above-mentioned third aspect or any possible implementation method thereof, or implement the method provided by the above-mentioned fourth aspect or any possible implementation method thereof.

[0045] In the fourteenth aspect, an embodiment of the present application also provides a computer program product comprising instructions, which, when run on a computer, enables the execution of the method provided in the first aspect or any possible implementation thereof, or enables the execution of the method provided in the second aspect or any possible implementation thereof, or enables the execution of the method provided in the third aspect or any possible implementation thereof, or enables the execution of the method provided in the fourth aspect or any possible implementation thereof.

[0046] In a fifteenth aspect, an embodiment of the present application provides a communication system, comprising a first terminal device capable of implementing the method provided in the first aspect, a second terminal device capable of implementing the method provided in the second aspect, and an access network device; or,

[0047] comprising an access network device, a first terminal device, and a second terminal device capable of implementing the method provided in the third aspect above; or,

[0048] It includes a second terminal device, a first terminal device and an access network device that can implement the method provided by the fourth aspect above.

[0049] In the sixteenth aspect, an embodiment of the present application also provides a chip system, which includes a processor for supporting a first terminal device to implement the functions involved in the above-mentioned first aspect; or for supporting a second terminal device to implement the functions involved in the above-mentioned second aspect or fourth aspect; or for supporting an access network device to implement the functions involved in the above-mentioned third aspect.

[0050] In one possible design, the chip system further includes a memory for storing necessary program instructions and data for execution by the loading device. The chip system can be composed of a chip or include a chip and other discrete devices.

[0051] It should be noted that the technical effects that can be achieved by any possible implementation method of the above-mentioned fifth to sixteenth aspects or the fifth to sixteenth aspects can be correspondingly described with reference to the technical effects that can be achieved by any possible implementation method of the above-mentioned first to fourth aspects or the first to fourth aspects; they will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] FIG1 is a schematic diagram of the architecture of a communication system used in an embodiment of the present application;

[0053] Figure 2 is a schematic diagram of the communication architecture of SL U2NRelay;

[0054] Figure 3 is a schematic diagram of the L2 SL U2N Relay protocol stack;

[0055] Figure 4 is a schematic diagram of a multi-path relay communication architecture;

[0056] FIG5 is a schematic diagram of the protocol stack architecture of multi-path relay;

[0057] FIG6 is a flow chart of a communication method according to an embodiment of the present application;

[0058] FIG7 is a flow chart of a communication method according to an embodiment of the present application;

[0059] FIG8 is a flow chart of a communication method according to an embodiment of the present application;

[0060] FIG9 is a flow chart of a communication method according to an embodiment of the present application;

[0061] FIG10 is a schematic diagram of a structure of a communication device according to an embodiment of the present application;

[0062] FIG11 is one of the structural diagrams of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0063] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0064] The at least one (item) involved in the embodiments of the present application as follows indicates one (item) or more (items). More (items) refers to two (items) or more than two (items). "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. In addition, it should be understood that although the terms first, second, etc. may be used to describe each object in the embodiments of the present application, these objects should not be limited to these terms. These terms are only used to distinguish each object from each other.

[0065] The terms "including" and "having" and any variations thereof mentioned in the following description of the embodiments of the present application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes other steps or units that are not listed, or optionally includes other steps or units that are inherent to these processes, methods, products or devices. It should be noted that, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any method or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other methods or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way.

[0066] The technology provided in the embodiments of the present application can be applied to various communication systems. For example, the communication system can be a third generation (3G) communication system (such as evolved universal terrestrial radio access and NR dual connection (evolved universal terrestrial radio access, E-UTRA), universal mobile telecommunication system (UMTS)), fourth generation (4G) communication system (such as long term evolution (LTE) system), fifth generation (5G) communication system, world-wide interoperability for microwave access (WiMAX) or wireless local area network (WLAN) system, or a fusion system of multiple systems, or a future communication system, such as a sixth generation (6G) communication system. Among them, the 5G communication system can also be called a new radio (NR) system.

[0067] A network element in a communication system can send a signal to another network element or receive a signal from another network element. The signal may include information or data, etc. The network element may also be referred to as an entity, a network entity, a device, a communication device, a communication module, a node, a communication node, etc. The embodiments of the present application are described using a network element as an example. For example, a communication system may include at least one terminal device and at least one network device. The signal-sending network element may be a network device, and the signal-receiving network element may be a terminal device; or, the signal-sending network element may be a terminal device, and the signal-receiving network element may be a network device. In addition, it can be understood that if the communication system includes multiple terminal devices, multiple terminal devices can also send signals to each other, that is, the signal-sending network element and the signal-receiving network element may both be terminal devices.

[0068] Figure 1 is a schematic diagram of the architecture of the communication system used in the embodiment of the present application. The communication system 10 includes a wireless access network 100 and a core network 200. Optionally, the communication system 10 may also include the Internet 300. The wireless access network 100 includes at least one access network device, such as 110a and 110b in Figure 1, and also includes at least one terminal device, such as 120a-120j in Figure 1. 110a is a base station, 110b is a micro station, 120a, 120e, 120f and 120j are mobile phones, 120b is a car, 120c is a gas pump, 120d is a home access point (HAP) arranged indoors or outdoors, 120g is a laptop computer, 120h is a printer, and 120i is a drone. The same terminal device or access network device can provide different functions in different application scenarios. For example, in FIG1 , there are mobile phones 120 a , 120 e , 120 f , and 120 j . Mobile phone 120 a can access base station 110 a , connect to car 120 b , communicate directly with mobile phone 120 e , and access HAP. Mobile phone 120 b can access HAP and communicate directly with mobile phone 120 a . Mobile phone 120 f can be connected as micro station 110 b , connect to laptop computer 120 g , and connect to printer 120 h . Mobile phone 120 j can control drone 120 i .

[0069] The terminal device is connected to the access network device, which is in turn connected to the core network. The core network device and the access network device can be independent and distinct physical devices, or they can integrate the functions of the core network device and the logical functions of the access network device into the same physical device, or they can integrate some of the functions of the core network device and some of the functions of the access network device into one physical device. Terminal devices and access network devices can be connected to each other via wired or wireless means. Figure 1 is only a schematic diagram, and the communication system can also include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in Figure 1.

[0070] The access network device may be an entity on the network side for transmitting or receiving signals. The access network device may be an access device for a terminal device to access the wireless communication system in a wireless manner, such as a base station. The base station can broadly cover the following various names, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), access network equipment in open radio access network (O-RAN), relay station, access point, transmission point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, radio node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), radio head (RRH), central unit (CU), distributed unit (DU), radio unit (RU), centralized unit control plane (CU-CP) node, centralized unit user plane (CU-UP) node, positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The access network device can also refer to a communication module, a modem or a chip that is provided in the aforementioned device or apparatus. The access network device can also be a mobile switching center and a device to device (Device-to-Device, D2D), vehicle-to-everything (V2X), machine-to-machine (machine-to-machine, M2M) communication device that performs the base station function, a network side device in a 6G network, a device that performs the base station function in a future communication system, etc. The access network device can support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device.

[0071] The access network device in the embodiments of the present application may be an integrated base station, or may be a base station including a centralized unit (CU) and / or a distributed unit (DU). The CU may further be divided into a CU control plane (CU-CP) and a CU user plane (CU-UP). The CU of a base station may also be referred to as a gNB-CU, which may be divided into a gNB-CU-CP and a gNB-CU-UP. The DU of a base station may also be referred to as a gNB-DU. Optionally, the base station may further include an antenna unit (RU). Alternatively, the access network device may be a network element that has all or part of the functions of a base station, for example, a CU, DU, or RU. The CU and DU may be deployed separately, and the CU may further be divided into a CU-CP and a CU-UP. Alternatively, the access network device in the embodiments of the present application may also be an open radio access network (O-RAN) architecture, etc. The embodiments of the present application do not limit the specific deployment method of the access network device. Exemplarily, when the access network device is an O-RAN architecture, the access network device shown in the embodiment of the present application may be an access network device in the O-RAN, such as a combination of one or more of a CU, a DU, or an RU, or a module in the access network device. In the ORAN system, the CU may also be referred to as an open (O)-CU, the CU-CP may also be referred to as an O-CU-CP, the CU-UP may also be referred to as an O-CU-UP, and the RU may also be referred to as an O-RU.

[0072] In this application, the communication device used to implement the above-mentioned access network function can be an access network device, a network device having some of the access network functions, or a device capable of supporting the implementation of the access network function, such as a chip system, a hardware circuit, a software module, or a hardware circuit and a software module. The device can be installed in the access network device or used in combination with the access network device. In the method of this application, the communication device used to implement the access network device function is described as an access network device.

[0073] A terminal device can be an entity on the user side that receives or transmits signals, such as a mobile phone. A terminal device can be used to connect people, objects, and machines. A terminal device can communicate with one or more core networks via network devices. Terminal devices include handheld devices with wireless connectivity, other processing devices connected to a wireless modem, or in-vehicle devices. A terminal device can be portable, pocket-sized, handheld, built into a computer, or in-vehicle. Terminal device 120 can be widely used in various scenarios, such as cellular communications, device-to-device (D2D), vehicle-to-everything (V2X), end-to-end (P2P), machine-to-machine (M2M), machine-type communications (MTC), the Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, and more. Some examples of the terminal device 120 include: 3GPP standard user equipment (UE), fixed equipment, mobile equipment, handheld equipment, wearable equipment, cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers, smart books, vehicles, satellites, global positioning system (GPS) equipment, target tracking equipment, drones, helicopters, aircraft, ships, remote control equipment, smart home equipment, industrial equipment, personal communication service (PCS) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), wireless network cameras, tablet computers, handheld computers, mobile internet devices (MIDs), wearable devices such as smart watches, virtual reality (VR) equipment, augmented reality (AR) equipment, wireless terminals in industrial control, terminals in vehicle networking systems, wireless terminals in self-driving, wireless terminals in smart grids, wireless terminals in transportation safety, and smart cities. The terminal device can be a wireless device in the above scenarios or a device used to be set up in a wireless device, such as a communication module, modem, or chip in the above devices.A terminal device may also be referred to as a terminal, terminal device, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. A terminal device may also be a terminal device in a future wireless communication system. A terminal device may be used in a dedicated network device or a general-purpose device. The embodiments of this application do not limit the specific technology and specific device form used by the terminal device.

[0074] Alternatively, end devices can communicate with each other using sidelink signals. For example, as shown in FIG1 , cellular phone 120 a and car 120 b communicate with each other using sidelink signals. Cellular phone 120 a and smart home device 120 e communicate without relaying the communication signal through base station 110 b.

[0075] In this application, the communication device used to implement the functions of the terminal device can be a terminal device, or a terminal device with some of the functions of the above terminal devices, or a device that can support the implementation of the functions of the above terminal devices, such as a chip system, which can be installed in the terminal device or used in combination with the terminal device. In this application, the chip system can be composed of chips, or it can include chips and other discrete devices. In the technical solution provided in this application, the communication device is described as a terminal device as an example.

[0076] Access network equipment and terminal devices can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of access network equipment and terminal devices.

[0077] The roles of access network devices and terminal devices can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile access network device. For devices 120j accessing the wireless access network 100 via 120i, 120i is an access network device. However, for access network device 110a, 120i is a terminal device, meaning that communication between 110a and 120i occurs via a wireless air interface protocol. Of course, communication between 110a and 120i can also occur via an interface protocol between access network devices. In this case, 120i is also an access network device relative to 110a. Therefore, both access network devices and terminal devices can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be referred to as communication devices with access network device functionality, while 120a-120j in Figure 1 can be referred to as communication devices with terminal device functionality.

[0078] Access network devices and terminal devices, access network devices and access network devices, and terminal devices and terminal devices can communicate through authorized spectrum, unauthorized spectrum, or both. They can communicate through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz. The embodiments of the present application do not limit the spectrum resources used for wireless communications.

[0079] To facilitate understanding of the solutions in the embodiments of the present application, taking the access network device as a base station and the terminal device as a UE as an example, the nouns or terms involved in the embodiments of the present application are first explained below.

[0080] 1. Sidelink Communication

[0081] In a wireless communication system, data communication can be carried out between UEs through the network, or directly between UEs without the help of the network. The interface between UEs is called the PC5 interface, which is similar to the Uu interface between UEs and base stations. The link between UEs is called sidelink. A typical application scenario of sidelink communication is vehicle-to-everything (V2X). In the vehicle network, each vehicle is a UE, and data can be transmitted directly between UEs through sidelink without going through the network, which can effectively reduce communication delays. It is understandable that the side link can also be called side link, side link, side link, etc.

[0082] 2. Broadcast, unicast, and multicast on sidelink

[0083] Broadcast communication on the sidelink is similar to the base station broadcasting system information, that is, the UE sends broadcast service data without encryption. Any other UE within the effective reception range that is interested in the broadcast service can receive the broadcast service data.

[0084] Unicast communication on the sidelink is similar to data communication after a radio resource control (RRC) connection is established between a UE and a base station. It requires a unicast connection to be established between the two UEs. After the unicast connection is established, the two UEs can communicate data based on the negotiated identifier, and the data can be encrypted or unencrypted.

[0085] Multicast communication on the sidelink refers to communication between all UEs in a communication group. Any UE in the group can send or receive data for the multicast service.

[0086] The embodiments of the present application mainly focus on unicast communication on the sidelink. A unicast communication on the sidelink corresponds to a pair of source layer 2 identifiers (source L2 ID) and destination layer 2 identifiers (destination L2 ID). The subheader of each sidelink media access control protocol data unit (MAC PDU) generally contains the source L2 ID and destination L2 ID to enable data to be transmitted from the sending end to the correct receiving end.

[0087] 3. Radio Bearer (RB)

[0088] A radio bearer is a general term for a series of protocol entities and configurations allocated by a base station to a UE, including the packet data convergence protocol (PDCP) entity, the radio link control (RLC) protocol entity, the medium access control (MAC) protocol entity, and a series of resources allocated by the physical layer (PHY). Radio bearers are divided into data radio bearers (DRBs) and signaling radio bearers (SRBs). The former is used to carry data, and the latter is used to carry signaling messages. In a sidelink communication scenario, communication between UEs is carried out through sidelink radio bearers (SLRBs), which include sidelink DRBs and sidelink SRBs.

[0089] 4. RLC bearer

[0090] An RLC bearer refers to the protocol entities and configurations below the RLC layer. It is the lower layer of a radio bearer and includes a series of resources such as RLC protocol entities and logical channels. An RLC bearer is associated with a logical channel. Typically, an RLC bearer is associated with a PDCP entity, meaning that one RLC serves one radio bearer RB.

[0091] 5. Sidelink UE to Network Relay (also known as sidelink UE-to-Network Relay, SL UE-to-Network Relay, or SL U2N Relay)

[0092] SL U2N Relay (SL U2N Relay) is a technology in which a UE helps another UE communicate with a base station, also known as relay technology. Figure 2 shows the SL U2N Relay communication architecture. A remote UE (remote UE) communicates with a base station through the collaboration of a relay UE (relay UE). The remote UE and relay UE communicate via sidelink, the corresponding interface being called the PC5 interface. The relay UE and base station are directly connected, communicating through the Uu port.

[0093] Embodiments of the present application can be used in Layer 2 (L2) scenarios of SL U2N Relay, hereinafter referred to as L2 SL U2N Relay. Figure 3 is a schematic diagram of the protocol stack of L2SL U2N Relay. Data packets from the Remote UE are relayed below the PDCP layer of the Relay UE. That is, the Relay UE only maintains the relayed RLC bearer, including the RLC layer, MAC layer, and PHY layer. Therefore, there are end-to-end PDCP layers, SDAP layers, and RRC layers between the Remote UE and the base station, but no end-to-end RLC layers, MAC layers, and PHY layers.

[0094] PC5-S precedes the access stratum (AS), which includes the RRC / SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer. Specifically, UEs can add, modify, and delete (or release) PC5 links based on PC5-S signaling.

[0095] This protocol architecture adds a sidelink relay adaptation protocol (SRAP) layer between the RLC layer and the PDCP layer. The main function of the SRAP layer is the multiplexing and demultiplexing of radio bearers, that is, it supports the multiplexing of different radio bearers onto one RLC bearer and the corresponding demultiplexing process. The RLC bearer between the Remote UE and the Relay UE is called the PC5 Relay RLC channel / bearer, and the RLC bearer between the Relay UE and the base station is called the Uu Relay RLC channel / bearer. The base station will perform SRAP configuration for the Remote UE and the Relay UE. The SRAP configuration may include a mapping relationship between the Remote UE's SRB ID / DRB ID and the Uu Relay RLC channel / PC5 ​​Relay RLC channel, so that the Remote UE's data can be correctly relayed and forwarded through the Relay UE. Specifically, the base station configures the mapping relationship between the radio bearer (SRB or DRB) and the PC5 Relay RLC channel for the Remote UE, and configures the mapping relationship between the radio bearer of the Remote UE and the Uu / PC5 Relay RLC channel for the Relay UE.

[0096] During data transmission, using the above example, after the Remote UE's SRAP layer receives a PDCP PDU from the PDCP layer, it adds the Remote UE ID information and the radio bearer (SRB or DRB) ID information to the SRAP header, resulting in a data packet (or SRAP PDU) as shown in Table 1 below. When the Relay UE's adaptation layer receives a data packet from the PC5 Relay RLC channel, it can deliver it to the correct Uu Relay RLC channel based on the mapping relationship configured by the base station. After receiving a data packet from the Uu Relay RLC channel, the base station side delivers it to the corresponding PDCP layer for processing based on the Remote UE ID information and RB ID information in the SRAP header. The downlink data transmission process is similar to that of the uplink and will not be further described here.

[0097] Table 1

[0098] Among them, the Remote UE ID information may be the Local ID of the remote UE, and the Local ID is a UE identifier assigned by the base station to the Remote UE. For example, the Local ID is an identifier assigned by the base station to the Remote UE in the initial access process of the remote UE. After the remote UE and the selected relay UE establish a unicast connection, the relay UE sends an RRC message to the base station, such as a Sidelink User Information (SidelinkUEInformation, SUI) message. The SUI message carries the L2 ID of the remote UE, which is used to request the base station to assign a local ID to the remote UE.

[0099] The Local ID is used for uplink and downlink data transmission of the Remote UE. By adding this identifier in the SRAR header, the Relay UE and the base station can identify the Remote UE to which the data packet belongs.

[0100] 6. Multi-path relay (also known as multi-path relay)

[0101] The "path" in the embodiments of the present application refers to a communication path or a communication link.

[0102] As an evolution of SL U2N Relay, the 3rd Generation Partnership Project (3GPP) is researching a multi-path relay solution. Multiple direct links and multiple indirect links can be established between the Remote UE and the base station. Optionally, the direct link can be replaced by an indirect link, and the indirect link can be replaced by an indirect link. Figure 4 is a schematic diagram of the multi-path relay communication architecture. The Remote UE communicates with the base station through both a direct link and an indirect link. The Remote UE and the Relay UE are located within the cell coverage of the same base station. On the direct link, the Remote UE communicates directly with the base station through the Uu port. On the indirect link, the Remote UE communicates with the base station through the Relay UE. The Remote UE and the Relay UE can connect and communicate via a sidelink or a non-3GPP link. The Remote UE improves the throughput and reliability of data transmission and reception by simultaneously sending and receiving the same or different data on the two links.

[0103] Figure 5 is a schematic diagram of the protocol stack architecture for multi-path relay. Figure 5 (a) illustrates the protocol stack architecture based on L2 SL U2N Relay. The Remote UE and Relay UE were previously connected via sidelink. Therefore, this architecture builds on the L2 SL U2N Relay protocol stack architecture by adding a protocol stack for direct communication between the Remote UE and the base station. Figure 5 (b) illustrates the protocol stack architecture when the Remote UE and Relay UE are connected via a non-3GPP protocol stack. An adaptation layer exists between the Remote UE and Relay UE, and between the Relay UE and the base station. However, the SRAP layer can be either present or absent, depending on the Remote UE's bearer multiplexing requirements.

[0104] The embodiments of the present application take the case where the first terminal device indicates the Relay UE and the second terminal device indicates the Remote UE as an example, and provide some solutions for the situation where the Remote UE and the access network device have inconsistent understandings of the Remote UE's status.

[0105] FIG6 is a communication method provided in an embodiment of the present application, which can be applied to the communication architecture shown in FIG2 . When data is transmitted, the second terminal device communicates with the access network device through the first terminal device.

[0106] S601, the access network device sends a third message to the second terminal device through the first terminal device, and the third message indicates that the state of the second terminal device is switched from a connected state to an idle state or a deactivated state.

[0107] Specifically, the third message can be an RRC release message, which specifically indicates that the RRC state of the second terminal device is switched from the RRC connected state to the RRC idle state (RRC_IDLE) or the RRC deactivated state (RRC_INACTIVE). The third message can carry identification information of the second terminal device, such as the Local ID of the second terminal device.

[0108] In one possible scenario, the access network device sends the third message to the first terminal device; the first terminal device fails to forward the third message to the second terminal device, meaning the second terminal device does not receive the third message and remains connected; however, the first terminal device sends an acknowledgment (ACK) corresponding to the third message to the access network device, causing the access network device to mistakenly believe that the second terminal device has switched from connected to idle or deactivated. This situation results in inconsistent understanding of the second terminal device's status between the access network device and the second terminal device.

[0109] In another possible scenario, the access network device sends the third message to the first terminal device. The first terminal device fails to receive the third message and responds with a negative-acknowledgment (NACK) to the access network device. However, the access network device incorrectly decodes the NACK as an ACK, mistaking it for an ACK. This can lead to inconsistent understandings of the second terminal device's status between the access network device and the second terminal device.

[0110] Based on the above possible situations, if the access network device is a base station including a CU and a DU, or the access network device includes a first sub-access network device (CU), a second sub-access network device (DU), and a third sub-access network device (RU), the access network device sending the third message to the first terminal device may include: the CU generates a third message and sends it to the DU, and then the DU sends the third message to the first terminal device through the RU. If the access network device is a base station including a CU and a DU and the CU is separated into a CU-CP and a CU-UP, or the access network device includes a second sub-access network device (DU), a third sub-access network device (RU), a fourth sub-access network device (CU-CP), and a fifth sub-access network device (CU-UP), the access network device sending the third message to the first terminal device may include: the CU-CP generates a third message and sends it to the DU, and then the DU sends the third message to the first terminal device through the RU.

[0111] In one possible design, the access network device may trigger the first terminal device to release the configuration information related to the second terminal device if it receives an ACK in response to the second message after sending the third message. Alternatively, the access network device may not send the third message and directly trigger the first terminal device to release the configuration information related to the second terminal device. Based on this, it can be understood that step S601 is optional. S601 is indicated by a dotted line in Figure 6, indicating that S601 may or may not be executed.

[0112] Specifically, the access network device triggers the first terminal device to release the configuration information related to the second terminal, which can be implemented with reference to the following step S602.

[0113] S602: The access network device sends a first message to the first terminal device.

[0114] Among them, the first message instructs the first terminal device to release the configuration information of part or all of the radio bearers between the second terminal device and the access network device. It can be understood that the configuration information of a radio bearer is used for data forwarding of the radio bearer. The data of a radio bearer refers to the data transmitted on the radio bearer. For example, in the layer 2 (L2) scenario of SL U2N Relay, a data packet (SRAP PDU) may be transmitted on a radio bearer, and the data packet includes the identification information of the second terminal device (such as Local ID), the identification information of the radio bearer (RB ID) and the data.

[0115] In one possible implementation, if the access network device is a base station including a CU and a DU, or the access network device includes a first sub-access network device (CU), a second sub-access network device (DU), and a third sub-access network device (RU), the access network device sending the first message to the first terminal device may include: the CU generates a first message and sends it to the DU, and then the DU sends the first message to the first terminal device through the RU. In another possible implementation, if the access network device is a base station including a CU and a DU and the CU is separated into a CU-CP and a CU-UP, or the access network device includes a second sub-access network device (DU), a third sub-access network device (RU), a fourth sub-access network device (CU-CP), and a fifth sub-access network device (CU-UP), the access network device sending the first message to the first terminal device may include: the CU-CP generates a first message and sends it to the DU, and then the DU sends the first message to the first terminal device through the RU.

[0116] The embodiment of the present application is described below using the first message indicating the release of the first wireless bearer between the second terminal device and the access network device as shown in Figure 6 as an example.

[0117] In one possible implementation, the configuration information of the first radio bearer may include one or more of the following: identification information of the second terminal device; a mapping relationship between the first radio bearer and the second terminal device; a mapping relationship between the first radio bearer and the first bearer of the first communication link, where the first communication link is the communication link between the first terminal device and the second terminal device; a mapping relationship between the first radio bearer and the second bearer of the second communication link, where the second communication link is the communication link between the first terminal device and the access network device. Taking the aforementioned terminology as an example, the first radio bearer may be a DRB or an SRB, the configuration information of the first radio bearer is included in the adaptation layer (SRAP) configuration corresponding to the first radio bearer, the first bearer of the first communication link may be understood as a PC5 Relay RLC channel, and the second bearer of the second communication link may be understood as a Uu Relay RLC channel.

[0118] Optionally, the first message indicates that the radio bearer released by the first terminal device does not include SRB0, that is, the access network device can retain the mapping relationship between the Uu relay RLC channel and SRB0 between the relay UE and the base station. Among them, SRB0 is used to carry the first RRC message after the second terminal device accesses the network device through the first terminal device. Retaining the relevant configuration of SRB0 facilitates the subsequent rapid re-establishment of communication between the second terminal device and the access network device.

[0119] In one possible implementation, the first message may be an RRC reconfiguration message. The access network device may update the adaptation layer configuration of the first terminal device through the RRC reconfiguration message, such as adding, releasing (or deleting), or modifying the configuration information of the radio bearer in the adaptation layer configuration. The embodiment of the present application is described by taking the release of the configuration information of the first radio bearer as an example. Specifically, the access network device may include the identification information of the second terminal device (such as local ID, L2 ID) in the sl-L2RelayUE-Config information element included in the RRC reconfiguration and include the identification of the first radio bearer (such as SRB1) in the sl-MappingToReleaseList information element to indicate the release of the configuration information of the first radio bearer. In another possible implementation, the first message may be an RRC reconfiguration message, and the first message may include the release configuration of the second terminal device. For example, the access network device may specifically include the identification information of the second terminal device (such as local ID) and information for indicating that the first terminal device is allowed to release the second terminal device in the sl-RemoteUE-ToReleaseList of the sl-L2RelayUE-Config information element included in the RRC reconfiguration.

[0120] Additionally, the access network device may optionally instruct the access network device in the first message to configure the second terminal device to an idle state or a deactivated state. For example, the first message may carry a first identifier to instruct the access network device to configure the second terminal device to an idle state. In another example, the first message may carry a second identifier to instruct the access network device to configure the second terminal device to a deactivated state.

[0121] Furthermore, since the second terminal device has not actually entered the idle state or deactivated state, the second terminal device may continue to send data of one or more wireless bearers to the first terminal device. Taking the data transmission of the first wireless bearer as an example, the second terminal device can execute the following step S603.

[0122] S603, the second terminal device sends data of the first radio bearer to the first terminal device.

[0123] Specifically, the second terminal device sends data of the first radio bearer to the first terminal device based on the first bearer of the second communication link (such as PC5 Relay RLC channel).

[0124] Corresponding to the description in S602, it can be understood that there is a mapping relationship between the first wireless bearer and the first bearer. When the second terminal device sends the data of the first wireless bearer to the access network device, it first sends the data of the first wireless bearer to the first terminal device based on the first bearer. For example, the second terminal device sends a data packet based on the first bearer, and the data packet carries the identification information of the second terminal device, the identification information of the first wireless bearer and the data. The data in the data packet can be understood as the data of the first wireless bearer.

[0125] The first terminal device can then search for the configuration information of the first radio bearer from the configuration information of the second terminal device's radio bearer stored in the first terminal device based on the identification information of the second terminal device and the identification information of the first radio bearer carried in the received data packet. If the search is successful, the first terminal device can forward the data of the first radio bearer to the access network device based on the searched configuration information of the first radio bearer.

[0126] However, since the first terminal device has already released the configuration information for the first radio bearer in S602, the first terminal device will fail to search for the configuration information for the first radio bearer after receiving the data for the first radio bearer in S603, and thus the first terminal device cannot forward the data for the first radio bearer. In this case, the first terminal device may decide to release the connection between the first terminal device and the second terminal device after receiving the data for the first radio bearer.

[0127] In one possible design, the first terminal device may perform packet loss processing on the data received from the first radio bearer, and then release the connection between the first terminal device and the second terminal device. Specifically, the design may be implemented with reference to the following steps S604 and S605. In another possible design, the first terminal device directly releases the connection between the first terminal device and the second terminal device after receiving the data from the first radio bearer. Specifically, the design may be implemented with reference to step S605. It is understandable that S604 is an optional step, and S604 and S605 may be executed after executing S603, or S605 may be executed directly without executing S604 after executing S603. S604 is indicated by a dotted line in Figure 6.

[0128] S604, the first terminal device receives N data packets from the first radio bearer of the second terminal device, and performs packet loss processing on the N data packets.

[0129] In a possible implementation, N is 1, that is, when the first terminal device receives a data packet of the first wireless bearer, it performs packet loss processing on the data packet.

[0130] In another possible implementation, N is an integer greater than 1. For example, when the first terminal device receives N data packets of the first wireless bearer continuously, it performs packet loss processing on the N data packets. Optionally, the value of N may be indicated to the first terminal device by the access network device, or the value of N is pre-configured. Exemplarily, when the number of data packets received by the first terminal device on the first wireless bearer does not reach times, the first terminal device may save the received data of the first wireless bearer, and may also determine whether the access network device has new configuration information for the first wireless bearer; if the number of data packets received by the first terminal device on the first wireless bearer reaches N, and the first terminal device has not received new configuration information for the first wireless bearer, then the first terminal device performs packet loss processing on the N data packets.

[0131] The first terminal device may decide to release the second terminal device after packet loss processing, that is, after executing S604, it may continue to execute S605:

[0132] S605: The first terminal device sends a second message to the second terminal device.

[0133] Specifically, when the connection between the first terminal device and the second terminal device is a sidelink connection, the AS layer (or RRC layer) of the first terminal device decides to release the sidelink connection between the first terminal device and the second terminal device, and instructs the PC5-S layer to release the PC5 connection, that is, the PC5-S layer transmits the second message, or it can also be understood that the second message is a PC5-S message.

[0134] In one possible design, the second message indicates releasing the connection between the first terminal device and the second terminal device, that is, releasing the second terminal device. For example, the second message may be a PROSE DIRECT LINK RELEASE REQUEST message, specifically used to release the PC5 connection between the first terminal device and the second terminal device.

[0135] In another possible design, the second message indicates that the state of the second terminal device is switched from a connected state to an idle state or a deactivated state. For example, corresponding to the case in S602 where the access network device indicates in the first message that the access network device configures the state of the second terminal device to be an idle state or a deactivated state, the first terminal device may, based on the first message, instruct the second terminal device to switch from the connected state to the idle state or the deactivated state through the second message.

[0136] Optionally, the second message carries a first identifier to indicate that the state of the second terminal device is switched from a connected state to an idle state; or, the second message carries a second identifier to indicate that the state of the second terminal device is switched from a connected state to a deactivated state.

[0137] Furthermore, S606 in FIG6 also illustrates the operation of the second terminal device after receiving the second message, which is an optional step. S606 is illustrated by a dotted line in FIG6 .

[0138] S606: The second terminal device releases the connection between the first terminal device and the second terminal device, and / or switches from a connected state to an idle state or a deactivated state.

[0139] In a first possible design, if the second message indicates the release of the connection between the first terminal device and the second terminal device, the second terminal device can release the connection between the first terminal device and the second terminal device, perform RRC re-establishment to re-access the network, and based on the network's instructions (such as a new RRC release message), switch from the connected state to the idle state or the deactivated state.

[0140] In a second possible design, if the second message indicates to release the connection between the first terminal device and the second terminal device, the second terminal device can release the connection between the first terminal device and the second terminal device and directly switch from the connected state to the idle state or the deactivated state.

[0141] In a third possible design, if the second message indicates that the state of the second terminal device is switched from a connected state to an idle state or a deactivated state, for example, the second message includes a first identifier, the second terminal device can switch from a connected state to an idle state; if the second message includes a second identifier, the second terminal device can switch from a connected state to a deactivated state.

[0142] In a fourth possible design, if the second message indicates that the state of the second terminal device is switched from a connected state to an idle state or a deactivated state, the second terminal device can first release the connection with the first terminal device, and then switch from the connected state to the idle state or the deactivated state according to the identifier carried in the second message (such as the first identifier or the second identifier).

[0143] The above method provided in the embodiment of the present application, in a scenario where the access network device instructs the release of the Remote UE's RRC connection to fail, and the Remote UE still sends data to the Relay UE, the Relay UE releases the Remote UE in addition to data packet loss, so that the Remote UE can successfully re-establish the RRC and obtain the RRC release message, or the Relay UE instructs the Remote UE to enter an idle state or a deactivated state in addition to data packet loss, thereby reducing the power consumption of the Remote UE.

[0144] In addition, optionally, the solution can also be applied to other scenarios of updating the configuration information of the radio bearers in the Relay UE and the Remote UE. For example, the access network device instructs the Relay UE to release the configuration information of the first radio bearer, and the Relay UE releases the Remote UE after receiving data on the first radio bearer from the Remote UE and performing packet loss processing; or, the solution can also be applied to a scenario where the configuration information of the radio bearer in the Relay UE is erroneous, and the access network device instructs the Relay UE to release the configuration information of the first radio bearer, and the Relay UE releases the Remote UE after receiving data on the first radio bearer from the Remote UE and performing packet loss processing.

[0145] FIG7 is a communication method provided in an embodiment of the present application, which can be applied to the communication architecture shown in FIG2 . When transmitting data, the second terminal device communicates with the access network device through the first terminal device.

[0146] S701, the access network device sends a third message to the second terminal device through the first terminal device, and the third message indicates that the state of the second terminal device is switched from a connected state to an idle state or a deactivated state.

[0147] Specifically, S701 can be implemented with reference to S601, and this embodiment of the present application will not be elaborated on.

[0148] S702, the second terminal device sends data to the access network device through the first terminal device.

[0149] Specifically, there are one or more radio bearers between the second terminal device and the access network device, and the second terminal device can send data of at least one radio bearer through the first terminal device. The first terminal device stores the configuration information of all radio bearers of the second terminal device. Similar to the description in S602, the configuration information of a radio bearer is used for data forwarding of the radio bearer, and the data of a radio bearer refers to the data transmitted on the radio bearer. For example, in the layer 2 (L2) scenario of SL U2N Relay, a data packet (SRAP PDU) may be transmitted on a radio bearer, and the data packet includes the identification information of the second terminal device (such as Local ID), the identification information of the radio bearer (RB ID), and the data.

[0150] Among them, the configuration information of a wireless bearer of the second terminal device includes one or more of the following: identification information of the second terminal device; a mapping relationship between the wireless bearer and the second terminal device; a mapping relationship between the wireless bearer and the first bearer of the first communication link, where the first communication link is the communication link between the first terminal device and the second terminal device; a mapping relationship between the first wireless bearer and the second bearer of the second communication link, where the second communication link is the communication link between the first terminal device and the access network device.

[0151] Taking the example of the second terminal device sending the data of the first radio bearer to the access network device through the first terminal device as shown in S702 in Figure 7, first, the second terminal device sends the data of the first radio bearer to the first terminal device based on the first bearer. For example, the second terminal device sends a data packet based on the first bearer, and the data packet carries the identification information of the second terminal device, the identification information of the first radio bearer, and the data. The data in the data packet can be understood as the data of the first radio bearer. Then, the first terminal device can search for the configuration information of the first radio bearer from the configuration information of the radio bearer of the second terminal device stored in the first terminal device based on the identification information of the second terminal device and the identification information of the first radio bearer carried in the received data packet. Finally, the first terminal device can forward the data of the first radio bearer to the access network device based on the configuration information of the first radio bearer.

[0152] In one possible implementation, if the access network device is a base station including a CU and a DU, or the access network device includes a first sub-access network device (CU), a second sub-access network device (DU), and a third sub-access network device (RU), the access network device receives the data of the first radio bearer forwarded by the first terminal device, including: the DU receives the data of the first radio bearer forwarded by the first terminal device through the RU, and then the DU sends the data of the first radio bearer to the CU. In another possible implementation, if the access network device is a base station including a CU and a DU and the CU is separated into a CU-CP and a CU-UP, or the access network device includes a second sub-access network device (DU), a third sub-access network device (RU), a fourth sub-access network device (CU-CP), and a fifth sub-access network device (CU-UP), the access network device receives the data of the first radio bearer forwarded by the first terminal device, including: the DU receives the data of the first radio bearer forwarded by the first terminal device through the RU, and then the DU sends the data of the first radio bearer to the CU-UP.

[0153] After receiving data from the second terminal device, the access network device can determine that the access network device and the second terminal device have inconsistent understandings of the status of the second terminal device; further, the access network device can control the second terminal device to enter an idle state or a deactivated state through the first terminal device. For example, after executing S702, the access network device can execute the following step S703.

[0154] S703, the access network device sends a fourth message to the first terminal device.

[0155] The fourth message is used to instruct the first terminal device to release the second terminal device, and the fourth message may include identification information of the second terminal device.

[0156] Optionally, the fourth message may specifically instruct the first terminal device to release configuration information of some or all radio bearers of the second terminal device. The fourth message includes identification information of some or all radio bearers of the aforementioned second terminal device. Specifically, the fourth message in S703 can be implemented according to the first message described in S602, and this embodiment of the present application will not be described in detail.

[0157] Optionally, the fourth message may also be used to instruct the first terminal device to release the connection between the first terminal device and the second terminal device.

[0158] Optionally, the fourth message may also be used to instruct the access network device to configure the state of the second terminal device to be an idle state or a deactivated state. For example, the fourth message carries a first identifier to instruct the access network device to configure the state of the second terminal device to be an idle state. For another example, the fourth message carries a second identifier to instruct the access network device to configure the state of the second terminal device to be a deactivated state.

[0159] Furthermore, the first terminal device may trigger the second terminal device to enter an idle state or a deactivated state according to the fourth message. FIG7 shows, with dotted lines, optional steps S704 to S705 after the first terminal device receives the fourth message.

[0160] S704: The first terminal device sends a second message to the second terminal device.

[0161] The second message may be used to instruct the second terminal device to release the connection with the first terminal device, or the second message may be used to instruct the second terminal device to switch from a connected state to an idle state or a deactivated state. Specifically, S704 may be implemented according to the description in S605, and this embodiment of the application will not be described in detail.

[0162] S705: The second terminal device releases the connection between the first terminal device and the second terminal device, and / or switches from a connected state to an idle state or a deactivated state.

[0163] Specifically, step S705 can be implemented with reference to the description in S606, and this embodiment of the application will not be described in detail.

[0164] Alternatively, if the access network device does not receive data from the second terminal device within a preset time period after executing S701, i.e., sending the third message, the access network device may resend the third message to the second terminal device via the first terminal device. In one possible scenario, the second terminal device successfully receives the third message resent by the access network device and enters an idle state or a deactivated state. In another possible scenario, if the access network device still fails to resend the third message, steps S702 to S705 are continued.

[0165] The above method provided in the embodiment of the present application, in a scenario where the access network device indicates that the release of the Remote UE's RRC connection has failed and the Remote UE is still sending data to the access network device through the Relay UE, the access network device can release the Remote UE through the Relay UE, thereby facilitating the Remote UE to re-establish the RRC connection and successfully obtain the RRC release message, thereby reducing the power consumption of the Remote UE.

[0166] FIG8 is a communication method provided in an embodiment of the present application, which can be applied to the communication architecture as shown in FIG2 . When data is transmitted, the second terminal device communicates with the access network device through the first terminal device.

[0167] S801, the access network device sends a third message to the second terminal device through the first terminal device, and the third message indicates that the state of the second terminal device is switched from a connected state to an idle state or a deactivated state.

[0168] Specifically, the third message can be an RRC release message, which specifically indicates that the RRC state of the second terminal device is switched from the RRC connected state to the RRC idle state (RRC_IDLE) or the RRC deactivated state (RRC_INACTIVE). The third message can carry identification information of the second terminal device, such as the Local ID of the second terminal device.

[0169] In one possible implementation, if the access network device is a base station including a CU and a DU, or the access network device includes a first sub-access network device (CU), a second sub-access network device (DU), and a third sub-access network device (RU), the access network device sending the third message to the first terminal device may include: the CU generates a third message and sends it to the DU, and then the DU sends the third message to the first terminal device through the RU. In another possible implementation, if the access network device is a base station including a CU and a DU and the CU is separated into a CU-CP and a CU-UP, or the access network device includes a second sub-access network device (DU), a third sub-access network device (RU), a fourth sub-access network device (CU-CP), and a fifth sub-access network device (CU-UP), the access network device sending the third message to the first terminal device may include: the CU-CP generates a third message and sends it to the DU, and then the DU sends the third message to the first terminal device through the RU. S801 in Figure 8 illustrates a case where the second terminal device successfully receives the third message. In this case, the second terminal device can actively release the connection with the first terminal device, that is, after executing S801, execute the following step S802:

[0170] S802: The second terminal device instructs the first terminal device to release the connection between the first terminal device and the second terminal device.

[0171] Specifically, the second terminal device may send a PC5 release message to the first terminal device to instruct the release of the PC5 connection between the first terminal device and the second terminal device and the release of the underlying configuration, such as the release of the PC5 Relay RLC channel between the first terminal device and the second terminal device.

[0172] S803: The first terminal device notifies the access network device that the connection between the first terminal device and the second terminal device has been released.

[0173] Exemplarily, the first terminal device may send a sidelink UE information (SUI) message to the access network device, where the SUI message indicates that the connection between the first terminal device and the second terminal device has been released.

[0174] In one possible implementation, if the access network device is a base station including a CU and a DU, or the access network device includes a first sub-access network device (CU), a second sub-access network device (DU), and a third sub-access network device (RU), the access network device receives a SUI message from the first terminal device, including: the DU can receive the SUI message from the first terminal device through the RU, and then the DU sends the SUI message to the CU. In another possible implementation, if the access network device is a base station including a CU and a DU and the CU is separated into a CU-CP and a CU-UP, or the access network device includes a second sub-access network device (DU), a third sub-access network device (RU), a fourth sub-access network device (CU-CP), and a fifth sub-access network device (CU-UP), the access network device receives a SUI message from the first terminal device, including: the DU can receive the SUI message from the first terminal device through the RU, and then the DU sends the SUI message to the CU-CP. S804, based on the indication of S803, the access network device sends a fourth message to the first terminal device.

[0175] The fourth message instructs the first terminal device to release the second terminal device. Specifically, S804 can be implemented according to the description in S703, which will not be described in detail in this embodiment of the application.

[0176] Alternatively, if the access network device does not receive the SUI from the first terminal device within a preset time period after executing S801, i.e., sending the third message, the first terminal device may resend the third message to the second terminal device. Furthermore, in one possible scenario, if the second terminal device successfully receives the third message resent by the access network device, steps S802 to S804 may be continued.

[0177] In the above method provided in the embodiment of the present application, when the access network device indicates that the RRC connection of the Remote UE is released successfully, the Remote UE actively releases the connection between the Relay UE and the Remote UE, and the Relay UE uses the SUI to indicate to the access network device that the connection between the Relay UE and the Remote UE has been released, thereby completing the release of the radio bearer configuration information in the Relay UE, facilitating the Remote UE to re-establish the RRC, and reducing the power consumption of the Remote UE.

[0178] FIG9 is a communication method provided in an embodiment of the present application, which can be applied to the communication architecture shown in FIG4 .

[0179] When transmitting data, the second terminal device can communicate with the access network device through the first terminal device, and there is a non-direct link between the second terminal device and the access network device. For example, the second terminal device transmits data with the access network device based on the first communication link and the second communication link. The first communication link is the communication link between the second terminal device and the first terminal device, and the second communication link is the communication link between the first terminal device and the access network device; or, when transmitting data, the second terminal device can communicate directly with the access network device, that is, there is a direct link between the second terminal device and the access network device. For example, the second terminal device transmits data with the access network device based on the third communication link, and the third communication link is the communication link between the second terminal device and the access network device.

[0180] Specifically, the method shown in FIG9 may include the following steps.

[0181] S900, the access network device sends a third message to the second terminal device, where the third message indicates that the state of the second terminal device is switched from a connected state to an idle state or a deactivated state.

[0182] Specifically, the third message can be an RRC release message, which specifically indicates that the RRC state of the second terminal device is switched from the RRC connected state to the RRC idle state (RRC_IDLE) or the RRC deactivation state (RRC_INACTIVE). The third message can carry the identification information of the second terminal device, such as the Local ID of the second terminal device. In a possible implementation, the access network device can send the third message to the second terminal device based on a non-direct link, that is, through the first terminal device. For example, SRB1 is used as the wireless bearer for transmitting the third message (RRC release message). If the access network device configures the mapping relationship between SRB1 and the first communication link and the second communication link, for example, the access network device configures the mapping relationship between SRB1 and the first bearer (PC5Relay RLC channel) of the first communication link and the mapping relationship between SB1 and the second bearer (Uu Relay RLC channel) of the second communication link, then the access network device can send the third message to the second terminal device through the first terminal device.

[0183] In one possible implementation scenario, the access network device sends the third message to the first terminal device. The first terminal device fails to forward the third message to the second terminal device, meaning the second terminal device does not receive the third message and remains connected. However, the first terminal device sends an ACK for the third message to the access network device, causing the access network device to mistakenly believe that the second terminal device has switched from connected to idle or deactivated. This situation results in inconsistent understanding of the second terminal device's state between the access network device and the second terminal device, causing the second terminal device to remain in a connected state, resulting in unnecessary power consumption.

[0184] In another possible implementation scenario, the access network device sends the third message to the first terminal device. The first terminal device fails to receive the third message and responds with a NACK to the access network device. However, the access network device incorrectly decodes the NACK as an ACK, causing the access network device to mistakenly believe that the second terminal device has switched from a connected state to an idle state or a deactivated state. This situation can also lead to inconsistent understandings of the second terminal device's state between the access network device and the second terminal device, causing the second terminal device to remain in a connected state, resulting in unnecessary power consumption.

[0185] Based on the above possible situations, if the access network device is a base station including a CU and a DU, or the access network device includes a first sub-access network device (CU), a second sub-access network device (DU), and a third sub-access network device (RU), the access network device sending the third message to the first terminal device may include: the CU may generate a third message and send it to the DU, and then the DU sends the third message to the first terminal device through the RU. If the access network device is a base station including a CU and a DU and the CU is separated into a CU-CP and a CU-UP, or the access network device includes a second sub-access network device (DU), a third sub-access network device (RU), a fourth sub-access network device (CU-CP), and a fifth sub-access network device (CU-UP), the access network device sending the third message to the first terminal device may include: the CU-CP generates a third message and sends it to the DU, and then the DU sends the third message to the first terminal device through the RU.

[0186] In another possible implementation, the access network device may send the third message directly to the second terminal device based on the direct link. For example, if SRB1 is used as the radio bearer for transmitting the third message (RRC release message), and if the access network device configures a mapping relationship between SRB1 and the third communication link, such as configuring a mapping relationship between SRB1 and the third radio bearer (Uu Relay RLC channel) of the third communication link, the access network device may send the third message directly to the second terminal device.

[0187] In one possible implementation scenario, the access network device sends the third message to the second terminal device. The second terminal device receives the third message in error and sends a NACK in response to the third message to the access network device. However, the access network device incorrectly interprets the NACK sent by the second terminal device and receives an ACK. The access network device mistakenly believes that the second terminal device has switched from a connected state to an idle state or a deactivated state. This situation can also lead to inconsistent understanding of the second terminal device's state between the access network device and the second terminal device, causing the second terminal device to remain in a connected state, resulting in unnecessary power consumption.

[0188] Based on the above possible situations, if the access network device is a base station including a CU and a DU, or the access network device includes a first sub-access network device (CU), a second sub-access network device (DU), and a third sub-access network device (RU), the access network device sending the third message to the second terminal device may include: the CU may generate a third message and send it to the DU, and then the DU sends the third message to the second terminal device through the RU. If the access network device is a base station including a CU and a DU and the CU is separated into a CU-CP and a CU-UP, or the access network device includes a second sub-access network device (DU), a third sub-access network device (RU), a fourth sub-access network device (CU-CP), and a fifth sub-access network device (CU-UP), the access network device sending the third message to the second terminal device may include: the CU-CP generates a third message and sends it to the DU, and then the DU sends the third message to the second terminal device through the RU. In response to the above situation, the access network device may configure the second terminal device with timing configuration information for deciding the switching state, so as to reduce the time that the second terminal device remains in a connected state when no data transmission is performed, thereby reducing the power consumption of the second terminal device. In addition, in addition to configuring the timing configuration information for the above-mentioned situation, the embodiments of the present application can also configure the timing configuration in other scenarios where the power consumption of the second terminal device needs to be reduced. That is, it can be understood that S900 indicated by a dotted line in Figure 9 is an optional step. In one possible implementation, the access network device can execute S900 and then execute the following steps S901 to S902; in another possible implementation, the access network device may not execute S900, but directly execute the following steps S901 to S902 to realize the configuration and application of the timing configuration information.

[0189] S901, the access network device sends timing configuration information to the second terminal device.

[0190] Specifically, the timing configuration information indicates a first time period, and the timing configuration information may include indication information of a start time of the first time period and a duration of the first time period. The start time of the first time period may also be described as a timing start time.

[0191] In one possible design, the access network device may send timing configuration information to the second terminal device based on a non-direct link, that is, through the first terminal device, specifically including: the access network device sends timing configuration information to the first terminal device, and the first terminal device forwards the timing configuration information to the second terminal device. Wherein, if the access network device is a base station including a CU and a DU, the access network device sending the timing configuration information to the first terminal device may include: the CU may generate the timing configuration information and send it to the DU, and then the DU sends the timing configuration information to the first terminal device through the RU; or, if the access network device is a base station including a CU and a DU, and the CU is separated into a CU-CP and a CU-UP, the access network device sending the timing configuration information to the first terminal device may include: the CU-CP generates the timing configuration information and sends it to the DU, and then the DU sends the timing configuration information to the first terminal device through the RU.

[0192] In another possible design, the access network device may send timing configuration information directly to the second terminal device based on a direct link. If the access network device is a base station including a CU and a DU, or the access network device includes a first sub-access network device (CU), a second sub-access network device (DU), and a third sub-access network device (RU), the access network device sending the timing configuration information to the second terminal device may include: the CU may generate timing configuration information and send it to the DU, and then the DU sends the timing configuration information to the second terminal device through the RU. If the access network device is a base station including a CU and a DU and the CU is separated into a CU-CP and a CU-UP, or the access network device includes a second sub-access network device (DU), a third sub-access network device (RU), a fourth sub-access network device (CU-CP), and a fifth sub-access network device (CU-UP), the access network device sending the timing configuration information to the second terminal device may include: the CU-CP generates timing configuration information and sends it to the DU, and then the DU sends the timing configuration information to the second terminal device through the RU. Specifically, the timing can be set to start when the second terminal device has no data transmission, that is, the time when the second terminal device has no data transmission is used as the starting time of the first time period. The second terminal device not transmitting data includes the second terminal device not transmitting data on the first communication link and the third communication link, where data transmission includes sending and receiving data. Optionally, the timing configuration information sent by the access network device can be determined according to a Datainactivitytimer mechanism, and the first time period can also be described as a Datainactivitytimer.

[0193] Exemplarily, the second terminal device does not transmit data on the first communication link, specifically including the absence of data transmission on at least one channel between the second terminal device and the first terminal device. The data transmission includes uplink data transmission and downlink data transmission. The channel between the second terminal device and the first terminal device may be a logical channel, including a sidelink control channel (SCCH) and a sidelink traffic channel (STCH). Based on this, the absence of data transmission on at least one channel between the second terminal device and the first terminal device includes: the second terminal device does not receive data based on the SCCH between the first terminal device and the second terminal device; and / or the second terminal device does not receive data based on the STCH between the first terminal device and the second terminal device.

[0194] Exemplarily, the second terminal device does not transmit data on the third communication link, specifically including that there is no data transmission on at least one channel between the second terminal device and the access network device. The channel between the second terminal device and the access network device can be a logical channel, including a dedicated traffic channel (DTCH), a dedicated control channel (DCCH), a common control channel (CCCH), and a multicast / broadcast services traffic channel (MTCH). Based on this, the absence of data transmission on at least one channel between the second terminal device and the access network device includes one or more of the following: the second terminal device does not receive data (such as MAC SDU) based on the DTCH between the second terminal device and the access network device; the second terminal device does not receive data (such as MAC SDU) based on the DCCH between the second terminal device and the access network device; the second terminal device does not receive data (such as MAC SDU) based on the CCCH between the second terminal device and the access network device; the second terminal device does not receive data (such as MAC SDU) based on the MTCH between the second terminal device and the access network device; the second terminal device does not send data based on the DTCH between the second terminal device and the access network device; for example, the second terminal device does not send data based on the DCCH between the second terminal device and the access network device.

[0195] If the second terminal device still has no data transmission after the first time period, the second terminal device may enter an idle state or a deactivated state, and the second terminal device may execute the following step S902.

[0196] S902: If there is no data transmission on the first communication link and the third communication link within the first time period, the second terminal device switches the state of the second terminal device from a connected state to an idle state or a deactivated state.

[0197] For example, in the Datainactivitytimer mechanism, the situation where the second terminal device still has no data transmission after the first time period can be simply referred to as Datainactivitytimer timeout. The MAC of the second terminal device can indicate the Datainactivitytimer timeout to the upper layer, and then based on the Datainactivitytimer timeout, enter the RRC idle state from the RRC connected state.

[0198] Further optionally, if the second terminal device still has no data transmission after the first time period (or described as Datainactivitytimer timeout), the second terminal device can also execute step S903. The optional step S903 is indicated by a dotted line in Figure 9.

[0199] S903: If there is no data transmission on the first communication link and the third communication link within the first time period, the second terminal device releases the connection with the first terminal device.

[0200] Correspondingly, after releasing the connection between the first terminal device and the second terminal device, the first terminal device may also release part or all of the wireless bearer configuration information of the second terminal device stored in the first terminal device, thereby saving the communication overhead of the non-direct link.

[0201] The solution illustrated in Figure 9 can be applied in a multi-path relay scenario where the remote UE triggers a DataInactivityTimer when no data is being transmitted on the logical channels on Uu and PC5. When the DataInactivityTimer expires, the remote UE automatically enters the RRC IDLE state, thereby resolving the RRC state inconsistency issue between the remote UE and the base station and reducing unnecessary energy consumption by the remote UE.

[0202] The methods described in Figures 6 to 9 provided in the present application can be implemented independently or in combination, and the embodiments of the present application are not limited thereto. For example, Figures 7 and 8 are implemented together. From the perspective of the access network device, the access network device sends a third message to the second terminal device through the first terminal device, and the third message indicates that the state of the second terminal device is switched from a connected state to an idle state or a deactivated state; if the access network device receives the first message from the first terminal device, it sends a fourth message to the first terminal device. Wherein, corresponding to the case where the second terminal device fails to receive the third message in Figure 7, the first message includes the data of the second terminal device; or, corresponding to the case where the second terminal device successfully receives the third message in Figure 7, the first message is used to indicate that the connection between the first terminal device and the second terminal device has been released.

[0203] In the embodiments provided in the present application, the methods provided in the embodiments of the present application are introduced from the perspective of interaction between various devices. In order to implement the various functions in the methods provided in the embodiments of the present application, the first terminal device or the access network device or the second terminal device may include a hardware structure and / or a software module to implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether a function of the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

[0204] Based on the same concept, referring to FIG10 , an embodiment of the present application provides a communication device 1000, which includes a processing module 1001 and a communication module 1002. The communication device 1000 can be a terminal device, or a communication device applied to or used in conjunction with a terminal device, capable of implementing a communication method executed on the terminal device side; or the communication device 1000 can be an access network device, or a communication device applied to or used in conjunction with an access network device, capable of implementing a communication method executed on the access network device.

[0205] The communication module may also be referred to as a transceiver module, transceiver, transceiver, or transceiver device. The processing module may also be referred to as a processor, processing board, processing unit, or processing device. Optionally, the communication module is used to perform the sending and receiving operations on the terminal device side or the access network device side in the above method. The device in the communication module that implements the receiving function can be considered a receiving unit, and the device in the communication module that implements the sending function can be considered a sending unit. That is, the communication module includes a receiving unit and a sending unit.

[0206] When the communication device 1000 is applied to the first terminal device, the processing module 1001 can be used to implement the processing function of the first terminal device in any of the examples described in Figures 6 to 9, and the communication module 1002 can be used to implement the sending and receiving functions of the first terminal device in any of the examples described in Figures 6 to 9.

[0207] When the communication device 1000 is applied to a second terminal device, the processing module 1001 can be used to implement the processing function of the second terminal device in any of the examples described in Figures 6 to 9, and the communication module 1002 can be used to implement the transceiver function of the second terminal device in any of the examples described in Figures 6 to 9.

[0208] When the communication device 1000 is applied to the access network device side, the processing module 1001 can be used to implement the processing function of the access network device in any of the examples described in Figures 6 to 9, and the communication module 1002 can be used to implement the transceiver function of the access network device in any of the examples described in Figures 6 to 9.

[0209] In addition, it should be noted that in one possible design, the aforementioned communication module and / or processing module can be implemented through a virtual module. For example, the processing module can be implemented through a software functional unit or a virtual device, and the communication module can be implemented through a software function or a virtual device. In another possible design, the processing module or the communication module can also be implemented through a physical device. For example, if the device is implemented using a chip / chip circuit, the communication module can be an input / output circuit and / or a communication interface that performs input operations (corresponding to the aforementioned receiving operations) and output operations (corresponding to the aforementioned sending operations); the processing module is an integrated processor or microprocessor or integrated circuit.

[0210] The division of modules in the embodiments of the present application is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the various examples of the embodiments of the present application may be integrated into a single processor, or may exist physically separately, or two or more modules may be integrated into a single module. The integrated modules may be implemented in either hardware or software functional modules.

[0211] Based on the same technical concept, the embodiment of the present application further provides a communication device 1100. For example, the communication device 1100 can be a chip or a chip system. Optionally, in the embodiment of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices.

[0212] The communication device 1100 can be used to implement the functions of any network element in the communication system described in the above examples. The communication device 1100 may include at least one processor 1110. Optionally, the processor 1110 is coupled to a memory, and the memory may be located within the device; or the memory may be integrated with the processor; or the memory may be located outside the device. For example, the communication device 1100 may also include at least one memory 1120. The memory 1120 stores the necessary computer programs, computer programs or instructions and / or data for implementing any of the above examples; the processor 1110 may execute the computer program stored in the memory 1120 to complete the method in any of the above examples.

[0213] The communication device 1100 may also include a communication interface 1130, through which the communication device 1100 can exchange information with other devices. Exemplarily, the communication interface 1130 may be a transceiver, a circuit, a bus, a module, a pin, or another type of communication interface. When the communication device 1100 is a chip-type device or circuit, the communication interface 1130 in the device 1100 may also be an input-output circuit that can input information (or receive information) and output information (or send information). The processor is an integrated processor or microprocessor or integrated circuit or logic circuit, and the processor can determine output information based on the input information.

[0214] The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processor 1110 may operate in conjunction with the memory 1120 and the communication interface 1130. The specific connection medium between the processor 1110, memory 1120, and communication interface 1130 is not limited in the embodiments of the present application.

[0215] Optionally, referring to FIG11 , the processor 1110, the memory 1120, and the communication interface 1130 are interconnected via a bus 1140. The bus 1140 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, FIG11 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0216] In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams of the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods of the embodiments of the present application may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0217] In an embodiment of the present application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), such as a random-access memory (RAM). The memory is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory in the embodiment of the present application may also be a circuit or any other device that can implement a storage function, for storing program instructions and / or data.

[0218] In one possible implementation, the communication device 1100 can be applied to a first terminal device. Specifically, the communication device 1100 can be a first terminal device, or a device that can support the first terminal device and implement the functions of the first terminal device in any of the above-mentioned examples. The memory 1120 stores computer programs (or instructions) and / or data that implement the functions of the first terminal device in any of the above-mentioned examples. The processor 1110 can execute the computer program stored in the memory 1120 to complete the method executed by the first terminal device in any of the above-mentioned examples. When the communication device is applied to the first terminal device, the communication interface in the communication device 1100 can be used to interact with the access network device, send information to the access network device, or receive information from the access network device.

[0219] In one possible implementation, the communication device 1100 can be applied to a second terminal device. Specifically, the communication device 1100 can be a second terminal device, or a device that can support the second terminal device and implement the functions of the second terminal device in any of the examples mentioned above. The memory 1120 stores computer programs (or instructions) and / or data that implement the functions of the second terminal device in any of the above examples. The processor 1110 can execute the computer program stored in the memory 1120 to complete the method executed by the second terminal device in any of the above examples. If the communication device is applied to the second terminal device, the communication interface in the communication device 1100 can be used to interact with the first terminal device or the access network device, send information to the first terminal device or the access network device, or receive information from the first terminal device or the access network device.

[0220] In another possible implementation, the communication device 1100 can be applied to an access network device. Specifically, the communication device 1100 can be an access network device, or it can be a device that can support the access network device and implement the functions of the access network device in any of the above-mentioned examples. The memory 1120 stores computer programs (or instructions) and / or data that implement the functions of the access network device in any of the above-mentioned examples. The processor 1110 can execute the computer program stored in the memory 1120 to complete the method executed by the access network device in any of the above-mentioned examples. When the communication device is applied to an access network device, the communication interface in the communication device 1100 can be used to interact with a terminal device (such as a first terminal device or a second terminal device), send information to the terminal device, or receive information from the terminal device (such as a first terminal device or a second terminal device).

[0221] Since the communication device 1100 provided in this example can be applied to an access network device to implement the method executed on the access network device side, or applied to a first terminal device to implement the method executed by the first terminal device, or applied to a second terminal device to implement the method executed by the second terminal device, the technical effects that can be achieved can be referred to the above method examples and will not be repeated here.

[0222] The technical solutions provided in the embodiments of the present application can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a terminal device, an access network device, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium.

[0223] In the embodiments of the present application, under the premise that there is no logical contradiction, the examples can reference each other, for example, the methods and / or terms between method embodiments can reference each other, for example, the functions and / or terms between device embodiments can reference each other, for example, the functions and / or terms between device examples and method examples can reference each other.

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

Claims

1. A communication method, characterized in that: The method is applied to a first terminal device, comprising: receiving a first message from an access network device, where the first message is used to indicate configuration information of releasing a first radio bearer; the configuration information is used for data forwarding of the first radio bearer; the first radio bearer is a radio bearer between a second terminal device and the access network device, and the second terminal device communicates with the access network device through the first terminal device; After receiving data of the first wireless bearer from the second terminal device, a second message is sent to the second terminal device, wherein the second message is used to indicate the release of the connection between the second terminal device and the first device, or the second message is used to indicate that the state of the second terminal device is switched from a connected state to an idle state or a deactivated state.

2. The method according to claim 1, characterized in that After receiving the data of the first radio bearer from the second terminal device, sending a second message to the second terminal device includes: Continuously receiving N data packets of the first radio bearer from the second terminal device, and performing packet loss processing on the N data packets; wherein N is an integer greater than 1; Send the second message to the second terminal device.

3. The method according to claim 2, characterized in that The value of N is indicated by the access network device, or the value of N is pre-configured.

4. The method according to any one of claims 1 to 3, characterized in that: The first message is also used to instruct the access network device to configure the state of the second terminal device to be an idle state or a deactivated state.

5. The method according to any one of claims 1 to 4, characterized in that: The second message includes a first identifier or a second identifier; wherein the first identifier indicates that the state of the second terminal device is switched from a connected state to an idle state, and the second identifier indicates that the state of the second terminal device is switched from a connected state to a deactivated state.

6. A communication method, characterized in that: The method is applied to a second terminal device, comprising: Sending at least one data of a first radio bearer to a first terminal device; the first radio bearer is a radio bearer between a second terminal device and the access network device, and the second terminal device communicates with the access network device through the first terminal device; A second message is received from the first terminal device, where the second message indicates releasing the connection between the second terminal device and the first device, or the second message indicates switching the state of the second terminal device from a connected state to an idle state or a deactivated state.

7. The method according to claim 6, characterized in that After receiving the second message from the first terminal device, the method further includes: Release the connection between the second terminal device and the first terminal device.

8. The method according to claim 6 or 7, characterized in that After receiving the second message from the first terminal device, the method further includes: Switch the state of the second terminal device from a connected state to an idle state or a deactivated state.

9. The method according to claim 8, characterized in that Switching the state of the second terminal device from a connected state to an idle state or a deactivated state includes: If the second message includes the first identifier, switching the state of the second terminal device from a connected state to an idle state; If the second message includes a second identifier, the state of the second terminal device is switched from a connected state to a deactivated state.

10. A communication method, characterized in that: The method is applied to access network equipment, including: Sending a third message to the second terminal device through the first terminal device, wherein the third message indicates that the state of the second terminal device is switched from a connected state to an idle state or a deactivated state; If first information is received from the first terminal device, a fourth message is sent to the first terminal device; wherein the first information includes data of the second terminal device, or the first information is used to indicate that the connection between the first terminal device and the second terminal device has been released; and the fourth message is used to indicate the release of the second terminal device.

11. The method according to claim 10, characterized in that The fourth message is also used to indicate the release of configuration information of the first wireless bearer of the second terminal device, where the configuration information is used for data forwarding of the first wireless bearer; the first wireless bearer is a wireless bearer between the second terminal device and the access network device.

12. The method according to claim 10 or 11, characterized in that The fourth message is also used to instruct the first terminal device to release the connection between the first terminal device and the second terminal device.

13. The method according to any one of claims 10 to 12, characterized in that: The fourth message is also used to instruct the access network device to configure the state of the second terminal device to be an idle state or a deactivated state.

14. The method according to any one of claims 10 to 13, characterized in that: After sending the third message to the second terminal device through the first terminal device, the method further includes: If the first message is not received within a preset time period after the third message is sent, the third message is resent to the second terminal device via the first terminal device.

15. The method according to any one of claims 10 to 14, characterized in that: When the first information indicates that the connection between the first terminal device and the second terminal device has been released, the first information is sidelink user information SUI.

16. A communication method, characterized in that: The method is applied to a second terminal device, comprising: receiving timing configuration information, wherein the timing configuration information indicates a first time period; If there is no data transmission on the first communication link and the third communication link within the first time period, the state of the second terminal device is switched from a connected state to an idle state or a deactivated state; wherein the first communication link is the communication link between the second terminal device and the first terminal device; and the third communication link is the communication link between the second terminal device and the access network device.

17. The method according to claim 16, characterized in that There is no data transmission on the first communication link, including no data transmission on at least one channel between the second terminal device and the first terminal device.

18. The method according to claim 17, characterized in that The channels of the second terminal device and the first terminal device include a sideline control channel and / or a sideline service channel.

19. The method according to any one of claims 16 to 18, characterized in that: There is no data transmission on the third communication link, including no data transmission on at least one channel between the first terminal device and the access network device.

20. The method of claim 19, wherein: The channel between the first terminal device and the access network device includes one or more of a dedicated service channel, a dedicated control channel, a common control channel, and a multicast service channel.

21. The method according to any one of claims 16 to 20, characterized in that: Before receiving the timing configuration information, the method further includes: performing data transmission with the network device based on the first communication link and the second communication link, wherein the second communication link is a communication link between the first terminal device and the access network device; or, Data is transmitted with the access network device based on the third communication link.

22. A communication device, characterized in that: Comprising a module for executing the method as claimed in any one of claims 1 to 5, or a module for executing the method as claimed in any one of claims 6 to 9, or a module for executing the method as claimed in any one of claims 10 to 15, or a module for executing the method as claimed in any one of claims 16 to 21.

23. A communication device, characterized in that: The invention comprises a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or send signals from the processor to other communication devices other than the communication device, and the processor is used to implement the method as claimed in any one of claims 1 to 5, or implement the method as claimed in any one of claims 6 to 9, or implement the method as claimed in any one of claims 10 to 15, or implement the method as claimed in any one of claims 16 to 21 through a logic circuit or execution code instructions.

24. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a communication device, implements the method according to any one of claims 1 to 21.

25. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or an instruction, and when the computer program or the instruction is executed by the communication device, the method according to any one of claims 1 to 21 is implemented.

26. A chip system, characterized in that: include: A processor, wherein the processor is configured to execute the method according to any one of claims 1 to 21.

27. A communication system, characterized in that: include: A first terminal device, a second terminal device and an access network device; the first terminal device is used to implement the method described in any one of claims 1 to 5, the second terminal device is used to implement the method described in any one of claims 6 to 9 or the method described in any one of claims 16 to 21, and the access network device is used to implement the method described in any one of claims 10 to 15.

Images