Communication method and device

Abstract

The invention provides a communication method and device, and the method comprises the steps: a first terminal device receives a first message from an access network device, and transmits a second message to a second terminal device after receiving the data of a first radio bearer from the second terminal device. Wherein the first message instructs the first terminal device to release configuration information of 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 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 message indicates to release the connection between the second terminal device and the first device, or the second message is used for indicating that the state of the second terminal device is switched from the connection state to the idle state or the deactivation state. According to the method, the problem that the state understanding of the remote terminal equipment and the state understanding of the access network equipment are inconsistent can be solved, and the power consumption of the remote terminal equipment is reduced.

Description

Technical Field

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

[0002] In some application scenarios, relay technology is required, that is, a terminal device can assist another terminal device to communicate with the access network device. Specifically, the remote terminal device communicates with the access network device through the cooperation of the relay terminal device. In other application scenarios, it may be necessary to configure multipath for the terminal device, that is, the remote terminal device can communicate with the access network device directly or through the cooperation of the relay terminal device.

[0003] 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 changes from the RRC connected state to the RRC idle state or the RRC deactivated 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 the base station, while the state of the remote terminal device may remain in the RRC connected state, that is, 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. Summary of the invention

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

[0005] 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 wireless bearer; the configuration information is used for data forwarding of the first wireless bearer; the first wireless bearer is a wireless 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 wireless 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.

[0006] Through such a design, when the access network device side and the second terminal device side have inconsistent understandings of the state of the second terminal device, the second terminal device can be put into an idle state or a deactivated state, which can reduce 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.

[0007] In one possible design, after receiving 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, 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.

[0008] Such a design is in line 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.

[0009] In a 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 an idle state or a deactivated state. Through such a design, the first terminal device can determine the state of the second terminal device configured by the access network device.

[0010] 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 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. With such a design, the target state of the second terminal device switching is clearly indicated, which facilitates subsequent communication processing.

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

[0012] 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 being 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 being 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 may 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.

[0013] In the 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, and 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.

[0014] In a 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.

[0015] 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.

[0016] 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.

[0017] 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.

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

[0019] In a 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.

[0020] 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.

[0021] In a 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.

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

[0023] In a 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.

[0024] 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.

[0025] Such a design can be applied to multi-path relay scenarios. By introducing a timing mechanism, the second terminal device can enter an idle state or a deactivated state automatically when the timing times out and there is no data transmission from the second terminal device. This avoids the problem of inconsistent states caused by the failure of the access network device to instruct the second terminal device to enter an idle state or a deactivated state, thereby reducing the energy consumption of the second terminal device. 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.

[0026] In one possible design, 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. 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.

[0027] In one possible design, 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. 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.

[0028] In one possible design, before receiving the timing configuration information, the second terminal device may perform data transmission with the network device based on the first communication link and the second communication link, and perform data transmission 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.

[0029] 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.

[0030] In one possible implementation, the device may include a module or unit corresponding to the method / operation / step / action described in the first aspect, and the module or unit may be a hardware circuit, or 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 first aspect or any possible implementation of the first aspect.

[0031] 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 combination with the second terminal device.

[0032] In one possible implementation, the device may include a module or unit corresponding to the method / operation / step / action described in the second aspect, and the module or unit may be a hardware circuit, or 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.

[0033] 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 may be an access network device, or the device may be a component in the access network device (for example, a chip, or a chip system, or a circuit), or may be a device that can be used in combination with the access network device.

[0034] In one possible implementation, the device may include a module or unit corresponding to the method / operation / step / action described in the third aspect, and the module or unit may be a hardware circuit, or 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 third aspect or any possible implementation of the third aspect.

[0035] 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.

[0036] In one possible implementation, the device may include a module or unit corresponding to the method / operation / step / action described in the fourth aspect, and the module or unit may be a hardware circuit, or 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.

[0037] 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.

[0038] 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.

[0039] 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 third aspect or any possible implementation method thereof.

[0040] 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.

[0041] In the thirteenth aspect, the embodiments of the present application also provide 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 first aspect or any possible implementation method thereof, or implement the method provided by the second aspect or any possible implementation method thereof, or implement the method provided by the third aspect or any possible implementation method thereof, or implement the method provided by the fourth aspect or any possible implementation method thereof.

[0042] In the fourteenth aspect, the embodiments of the present application also provide a computer program product comprising instructions, which, when executed on a computer, enables the method provided by the first aspect or any possible implementation method thereof to be executed, or enables the method provided by the second aspect or any possible implementation method thereof to be executed, or enables the method provided by the third aspect or any possible implementation method thereof to be executed, or enables the method provided by the fourth aspect or any possible implementation method thereof to be executed.

[0043] In a fifteenth aspect, an embodiment of the present application provides a communication system, including 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,

[0044] 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,

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

[0046] 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.

[0047] In a possible design, the chip system further includes a memory, which is used to store necessary program instructions and data executed by the loading device. The chip system can be composed of chips or include chips and other discrete devices.

[0048] 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 referred 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

[0049] Figure 1 A schematic diagram of the architecture of a communication system used in an embodiment of the present application;

[0050] Figure 2 The communication architecture diagram of SL U2NRelay is shown below;

[0051] Figure 3 The diagram is a protocol stack diagram of L2 SL U2N Relay;

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

[0053] Figure 5 This is a schematic diagram of the protocol stack architecture of multi-path relay;

[0054] Figure 6 One of the flow charts of the communication method provided in the embodiment of the present application;

[0055] Figure 7 One of the flow charts of the communication method provided in the embodiment of the present application;

[0056] Figure 8 One of the flow charts of the communication method provided in the embodiment of the present application;

[0057] Fig. 9 One of the flow charts of the communication method provided in the embodiment of the present application;

[0058] Fig.10 One of the structural schematic diagrams of the communication device provided in the embodiment of the present application;

[0059] Fig.11 This is one of the structural diagrams of the communication device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0060] 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.

[0061] The at least one (item) involved in the embodiments of the present application as follows indicates one (item) or more (items). More than one (item) 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 related objects before and after 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.

[0062] 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 comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes other steps or units that are not listed, or optionally also includes other steps or units 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 represent examples, illustrations or explanations. 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 manner.

[0063] 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 (e.g., 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 (e.g., long term evolution (LTE) system), fifth generation (5G) communication system, worldwide 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.

[0064] 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 network element is used as an example for description in the embodiments of the present application. For example, a communication system may include at least one terminal device and at least one network device. The network element that sends the signal may be a network device, and the network element that receives the signal may be a terminal device; or, the network element that sends the signal may be a terminal device, and the network element that receives the signal 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 network element that sends the signal and the network element that receives the signal can both be terminal devices.

[0065] Figure 1 The communication system 1000 includes a wireless access network 100 and a core network 200. Optionally, the communication system 1000 may also include the Internet 300. The wireless access network 100 includes at least one access network device, such as Figure 1 110a and 110b in the embodiment, and further comprising at least one terminal device, such as Figure 1120a-120j in the figure. 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 station, 120d is a home access point (HAP) arranged indoors or outdoors, 120g is a laptop, 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, Figure 1 The mobile phones in the figure are 120a, 120e, 120f and 120j. The mobile phone 120a can access the base station 110a, connect to the car 120b, communicate directly with the mobile phone 120e and access the HAP. The mobile phone 120b can access the HAP and communicate directly with the mobile phone 120a. The mobile phone 120f can be connected to the micro station 110b, connect to the laptop computer 120g, connect to the printer 120h, and the mobile phone 120j can control the drone 120i.

[0066] The terminal equipment is connected to the access network equipment, and the access network equipment is connected to the core network. The core network equipment and the access network equipment can be independent and different physical devices, or the functions of the core network equipment and the logical functions of the access network equipment can be integrated on the same physical device, or the functions of some core network equipment and some access network equipment can be integrated on one physical device. Terminal equipment and terminal equipment, as well as access network equipment and access network equipment can be connected to each other by wire or wireless means. Figure 1 This is just a schematic diagram. The communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices. Figure 1 Not drawn in.

[0067] 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 (transmitting and receiving point, TRP), transmission point (transmitting point, TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless 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 (radio unit, RU), centralized unit control plane (CUcontrol plane, CU-CP) node, centralized unit user plane (CU 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 may also refer to a communication module, a modem or a chip used to be arranged in the aforementioned device or apparatus. The access network device may also be a mobile switching center and a device to device (Device-to-Device, D2D), vehicle external connection (vehicle-to-everything, V2X), a device that performs the base station function in machine-to-machine (machine-to-machine, M2M) communication, a network side device in a 6G network, and a device that performs the base station function in a future communication system. 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 equipment form adopted by the access network device.

[0068] The access network device in the embodiment 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 also be divided into a CU control plane (CU-CP) and a CU user plane (CU-UP). The CU of the base station may also be referred to as a gNB-CU, the gNB-CU may be divided into a gNB-CU-CP and a gNB-CU-UP, and the DU of the base station may also be referred to as a gNB-DU. Optionally, the base station may also include an antenna unit (radio unit, RU). Alternatively, the access network device may be a network element having all or part of the functions of a base station, for example, the access network device is a CU, DU or RU; wherein the CU and DU may be deployed separately, and the CU may also be divided into a CU-CP and a CU-UP. Alternatively, the access network device in the embodiment of the present application may also be an open radio access network (O-RAN) architecture, etc. The embodiment of the present application does 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 a RU, or a module in the access network device. In the ORAN system, the CU may also be referred to as an open (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.

[0069] In the present application, the communication device used to implement the above access network function can be an access network device, or a network device with some functions of accessing the network, 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 plus a software module, which can be installed in the access network device or used in combination with the access network device. In the method of the present application, the communication device used to implement the access network device function is an access network device for example.

[0070] The terminal device can be an entity on the user side for receiving or transmitting signals, such as a mobile phone. The terminal device can be used to connect people, objects and machines. The terminal device can communicate with one or more core networks through a network device. The terminal device includes a handheld device with a wireless connection function, other processing devices connected to a wireless modem, or a vehicle-mounted device. The terminal device can be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device. The terminal device 120 can be widely used in various scenarios, such as cellular communication, device-to-device D2D, vehicle-to-all V2X, end-to-end P2P, machine-to-machine M2M, machine type communication MTC, Internet of Things IOT, virtual reality VR, augmented reality AR, industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, drone, robot, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, etc. Some examples of the terminal device 120 are: user equipment (UE) of 3GPP standard, fixed equipment, mobile equipment, handheld equipment, wearable equipment, cellular phone, smart phone, session initiation protocol (SIP) phone, laptop computer, personal computer, smart book, vehicle, satellite, global positioning system (GPS) equipment, target tracking equipment, drone, helicopter, aircraft, ship, remote control equipment, smart home equipment, industrial equipment, personal communication service (PCS) phone, wireless local loop (WLL) station, personal digital assistant (PDA), wireless network camera, tablet computer, PDA, mobile internet device (MID), wearable equipment such as smart watch, virtual reality (VR) equipment, augmented reality (AR) equipment, wireless terminal in industrial control, terminal in Internet of Vehicles system, wireless terminal in self-driving, wireless terminal in smart grid, wireless terminal in transportation safety, smart city, etc. The terminal device 120 may be a wireless device in the above scenarios or a device used to be set in a wireless device, for example, a communication module, a modem or a chip in the above devices.The terminal device may also be referred to as a terminal, terminal equipment, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device may also be a terminal device in a future wireless communication system. The terminal device may be used in a dedicated network device or a general device. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal device.

[0071] Optionally, terminal devices may communicate with each other using sidelink signals. Figure 1 As shown, the cell phone 120a and the car 120b communicate with each other using a sidelink signal. The cell phone 120a and the smart home device 120e communicate with each other without relaying the communication signal through the base station 110b.

[0072] In the present application, the communication device used to implement the functions of the terminal device can be a terminal device, or a terminal device having 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 the present application, the chip system can be composed of chips, or it can include chips and other discrete devices. In the technical solution provided in the present application, the communication device is described as a terminal device as an example.

[0073] The access network equipment and terminal equipment can be fixed or movable. The access network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on airplanes, balloons and artificial satellites in the air. The embodiments of the present application do not limit the application scenarios of the access network equipment and terminal equipment.

[0074] The roles of access network devices and terminal devices can be relative, for example, Figure 1 The helicopter or drone 120i in the figure can be configured as a mobile access network device. For those 120j that access the wireless access network 100 through 120i, 120i is an access network device; but for the access network device 110a, 120i is a terminal device, that is, 110a and 120i communicate through the wireless air interface protocol. Of course, 110a and 120i can also communicate through the interface protocol between access network devices. At this time, relative to 110a, 120i is also an access network device. Therefore, access network devices and terminal devices can be collectively referred to as communication devices. Figure 1 110a and 110b in the figure may be referred to as communication devices having access network device functions. Figure 1120a-120j in the figure can be called communication devices with terminal equipment functions.

[0075] Access network devices and terminal devices, access network devices and access network devices, and terminal devices and terminal devices can communicate through authorized spectrum, unlicensed spectrum, or both; 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 communication.

[0076] To facilitate understanding of the solution of 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.

[0077] 1. Sidelink Communication

[0078] In a wireless communication system, UEs can communicate data through the network, or they can communicate directly with each other 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 UEs can directly transmit data through sidelink without going through the network, which can effectively reduce communication delays. It can be understood that the side link can also be called a side link, a sidelink, or a side link.

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

[0080] Broadcast communication on the sidelink is similar to the base station broadcasting system information, that is, the UE sends broadcast service data to the outside without encryption, and any other UE within the effective receiving range can receive the broadcast service data if it is interested in the broadcast service.

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

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

[0083] 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 identifier (source L2 ID) and destination layer-2 identifier (destination layer-2 identifier, destination L2 ID). The subheader of each sidelink media access control layer data protocol unit (MAC PDU) generally contains the source L2 ID and the destination L2 ID so that data can be transmitted from the sending end to the correct receiving end.

[0084] 3. Radio Bearer (RB)

[0085] Radio bearer is a general term for a series of protocol entities and configurations allocated by the base station to the 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 (DRB) and signaling radio bearers (SRB). The former is used to carry data, and the latter is used to carry signaling messages. In the sidelink communication scenario, communication between UEs is carried out through sidelink radio bearers (SLRB), including sidelink DRB and sidelink SRB.

[0086] 4. RLC bearer

[0087] RLC bearer refers to the protocol entity and configuration below the RLC layer, which is the lower layer part of the radio bearer, including a series of resources such as RLC protocol entity and logical channel. One RLC bearer is associated with one logical channel. Usually, one RLC bearer is associated with one PDCP entity, that is, one RLC serves one radio bearer RB.

[0088] 5. Sidelink UE to Network Relay (also called sidelinkUE-to-Network Relay, SLUE-to-Network Relay or SL U2N Relay)

[0089] SL U2N Relay is a technology in which a UE helps another UE to communicate with a base station, also known as relay technology. Figure 2 The figure is a schematic diagram of the communication architecture of SL U2N Relay. The remote UE communicates with the base station through the cooperation of the relay UE. The remote UE and the relay UE communicate through the sidelink. The corresponding interface is called the PC5 interface. The relay UE and the base station are directly connected, that is, they communicate through the Uu port.

[0090] The embodiments of the present application may be used in a layer 2 (L2) scenario of SL U2N Relay, hereinafter referred to as L2 SL U2N Relay. Figure 3 The figure is a diagram of the protocol stack of L2SL U2NRelay. The data packets of 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 there are no end-to-end RLC layers, MAC layers, and PHY layers.

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

[0092] 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 the 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.

[0093] During the data transmission process, taking the above behavior as an example, after the SRAP layer of the Remote UE receives the PDCP PDU from the PDCP layer, it will add the Remote UE ID information and the ID information of the radio bearer (SRB or DRB) in the SRAP header, and obtain the data packet (or SRAP PDU) shown in Table 1 below. After the adaptation layer of the Relay UE receives the data packet from the PC5 Relay RLC channel, it can be delivered to the correct Uu Relay RLC channel according to the mapping relationship configured by the base station. After the base station side receives the data packet from the UuRelay RLC channel, it will be delivered to the corresponding PDCP layer for processing according to the Remote UE ID information and RB ID information in the SRAP header. The data transmission process in the downlink direction is similar to that in the uplink direction, and will not be repeated here.

[0094] Table 1

[0095]

[0096] Among them, the Remote UE ID information can be the Local ID of the remote UE, and the Local ID is the UE identifier assigned by the base station to the Remote UE. For example, the Local ID is the 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.

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

[0098] 6. Multi-path relay (also called multi-path relay)

[0099] The “path” in the embodiments of the present application refers to a communication path or a communication link.

[0100] As an evolution of SL U2N Relay, the 3rd generation partnership project (3GPP) is studying a multi-path relay solution, where multiple direct links and multiple indirect links can be established between the Remote UE and the base station. Optionally, the direct link can also be replaced by an indirect link, and the indirect link can also be replaced by an indirect link. Figure 4 The figure is a schematic diagram of the multi-path Relay communication architecture. The Remote UE communicates with the base station through a direct link and an indirect link at the same time. The Remote UE and the Relay UE are located in the cell coverage of the same base station. On the direct link, the Remote UE communicates with the base station directly 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 be connected and communicated through the sidelink, or through a non-3GPP link. The Remote UE improves the throughput and reliability of data reception and transmission by sending and receiving the same or different data on two links at the same time.

[0101] Figure 5 The following is a diagram of the protocol stack architecture of multi-path relay. Figure 5 (a) is a schematic diagram of a protocol stack architecture based on L2 SL U2N Relay. The Remote UE and the Relay UE were previously connected via a sidelink. Therefore, this architecture adds a protocol stack for direct communication between the Remote UE and the base station on the basis of the L2SL U2N Relay protocol stack architecture. Figure 5 (b) is the protocol stack architecture when the Remote UE and the Relay UE are connected via a non-3GPP connection, wherein there is an adaptation layer between the Remote UE and the Relay UE, and between the Relay UE and the base station, but for the SRAP layer, there may be an SRAP layer or there may not be an SRAP layer, depending on the specific requirements of the Remote UE bearer multiplexing.

[0102] 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 status of the Remote UE.

[0103] Figure 6 A communication method provided in an embodiment of the present application can be applied to Figure 2 The illustrated communication architecture, when data is transmitted, the second terminal device communicates with the access network device through the first terminal device.

[0104] 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.

[0105] Specifically, the third message may 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 may carry identification information of the second terminal device, such as the LocalID of the second terminal device.

[0106] 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, that is, the second terminal device does not receive the third message and continues to maintain the connected state; but the first terminal device sends confirmation information (acknowledgement, ACK) corresponding to the third message to the access network device, and the access network device mistakenly believes that the second terminal device has entered the connected state and switched to the idle state or deactivated state. Such a situation leads to inconsistent understanding of the state of the second terminal device between the access network device side and the second terminal device side.

[0107] 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 replies a negative acknowledgement (NACK) to the access network device, but the access network device incorrectly decodes the NACK as an ACK, and the access network device mistakenly believes that the second terminal device has switched from the connected state to the idle state or the deactivated state. Such a situation will also lead to inconsistent understanding of the state of the second terminal device between the access network device side and the second terminal device side.

[0108] 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.

[0109] In a possible design, the access network device may trigger the first terminal device to release the configuration information related to the second terminal device when receiving an ACK in response to the second message after sending the third message; or 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 S601 is an optional step. Figure 6 The S601 is indicated by a dotted line, indicating that S601 may be executed or may not be executed.

[0110] 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.

[0111] S602, the access network device sends a first message to the first terminal device.

[0112] 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 SLU2N 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.

[0113] 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.

[0114] The embodiment of the present application is described below using an example in which a first message indicates the release of a first wireless bearer between a second terminal device and an access network device.

[0115] In a 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, the first communication link being 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, the second communication link being the communication link between the first terminal device and the access network device. Taking the aforementioned terminology introduction 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.

[0116] Optionally, the first message indicates that the wireless 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 second terminal device to quickly re-establish communication with the access network device.

[0117] In a 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 takes the release of the configuration information of the first radio bearer as an example to illustrate. 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 RRCreconfiguration 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 (such as local ID) of the second terminal device in the sl-RemoteUE-ToReleaseList of the sl-L2RelayUE-Config information element included in the RRC reconfiguration, as well as information for indicating that the first terminal device is allowed to release the second terminal device.

[0118] In addition, optionally, the access network device may also indicate 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. For example, the first message carries a first identifier to indicate that the access network device configures the state of the second terminal device to be an idle state. For another example, the first message carries a second identifier to indicate that the access network device configures the state of the second terminal device to be a deactivated state.

[0119] Furthermore, since the second terminal device has not actually entered the idle state or the 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 may execute the following step S603.

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

[0121] 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).

[0122] 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, the data of the first wireless bearer is first sent 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.

[0123] Then, the first terminal device can search for the configuration information of the first wireless bearer from the configuration information of the wireless bearer of the second terminal device stored in the first terminal device according to the identification information of the second terminal device carried in the received data packet and the identification information of the first wireless bearer. If the search is successful, the first terminal device can forward the data of the first wireless bearer to the access network device according to the configuration information of the first wireless bearer.

[0124] However, since the first terminal device has completed the release of the configuration information of the first radio bearer in S602, after the first terminal device receives the data of the first radio bearer in S603, it will find that the configuration information of the first radio bearer fails to be searched, so the first terminal device cannot forward the data of the first radio bearer. In this case, the first terminal device can decide to release the connection between the first terminal device and the second terminal device after receiving the data of the first radio bearer.

[0125] In one possible design, the first terminal device may perform packet loss processing on the data received from the first wireless 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, after receiving the data from the first wireless bearer, the first terminal device directly releases the connection between the first terminal device and the second terminal device. 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 in Figure 6 Indicated by dotted line.

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

[0127] 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 included in the data packet.

[0128] In another possible implementation, N is an integer greater than 1, such as 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.

[0129] 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:

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

[0131] 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.

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

[0133] 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 a connected state to an idle state or a deactivated state through the second message.

[0134] 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.

[0135] further, Figure 6 S606 also illustrates the operation of the second terminal device after receiving the second message, as an optional step. Figure 6 S606 is indicated by a dotted line.

[0136] 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.

[0137] 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.

[0138] 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 may 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.

[0139] In a third possible design, if the second message indicates that the state of the second terminal device switches 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.

[0140] In a fourth possible design, if the second message indicates that the state of the second terminal device switches from a connected state to an idle state or a deactivated state, the second terminal device may 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 an identifier carried in the second message (such as the first identifier or the second identifier).

[0141] 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 fails, 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.

[0142] In addition, optionally, the scheme can also be applied to other scenarios of updating the configuration information of the radio bearers in the Relay UE and the Remote UE. Exemplarily, 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 the data of the first radio bearer from the Remote UE and performing packet loss processing; or, the scheme can also be applied to the 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 the data of the first radio bearer from the Remote UE and performing packet loss processing.

[0143] Figure 7 A communication method provided in an embodiment of the present application can be applied to Figure 2 The illustrated communication architecture, when data is transmitted, the second terminal device communicates with the access network device through the first terminal device.

[0144] 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.

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

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

[0147] 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.

[0148] 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, the first communication link being 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, the second communication link being the communication link between the first terminal device and the access network device.

[0149] Taking the example of the second terminal device sending the data of the first wireless bearer to the access network device through the first terminal device, first, the second terminal device 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. Then, the first terminal device can search for the configuration information of the first wireless bearer from the configuration information of the wireless bearer of the second terminal device stored in the first terminal device according to the identification information of the second terminal device and the identification information of the first wireless bearer carried in the received data packet. Finally, the first terminal device can forward the data of the first wireless bearer to the access network device according to the configuration information of the first wireless bearer.

[0150] 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 wireless bearer forwarded by the first terminal device, including: the DU receives the data of the first wireless bearer forwarded by the first terminal device through the RU, and then the DU sends the data of the first wireless 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 wireless bearer forwarded by the first terminal device, including: the DU receives the data of the first wireless bearer forwarded by the first terminal device through the RU, and then the DU sends the data of the first wireless bearer to the CU-UP.

[0151] After receiving the 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.

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

[0153] 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.

[0154] Optionally, the fourth message may specifically instruct the first terminal device to release configuration information of some or all of the radio bearers of the second terminal device. The fourth message includes identification information of some or all of the radio bearers of the aforementioned second terminal device. Specifically, the first message described in S602 may be used to implement the fourth message in S703, which is not described in detail in this embodiment of the present application.

[0155] 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.

[0156] Optionally, the fourth message may also be used to indicate that the access network device configures 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 indicate that the access network device configures the state of the second terminal device to be an idle state. For another example, the fourth message carries a second identifier to indicate that the access network device configures the state of the second terminal device to be a deactivated state.

[0157] 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. Figure 7 The dotted lines in FIG. 7 illustrate optional steps S704 to S705 after the first terminal device receives the fourth message.

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

[0159] 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 present application will not be described in detail.

[0160] 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.

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

[0162] In addition, optionally, if the access network device does not receive data from the second terminal device within a preset time after executing S701, i.e. sending the third message, the third message may be resent to the second terminal device through the first terminal device. Then, 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, the third message resent by the access network device still fails, and steps S702 to S705 are continued.

[0163] 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 still sends data to the access network device through the Relay UE, the access network device can release the Remote UE through the Relay UE, so that the Remote UE can re-establish the RRC to successfully obtain the RRC release message, thereby reducing the power consumption of the Remote UE.

[0164] Figure 8 A communication method provided in an embodiment of the present application can be applied to Figure 2 The illustrated communication architecture, when data is transmitted, the second terminal device communicates with the access network device through the first terminal device.

[0165] 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.

[0166] Specifically, the third message may 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 may carry identification information of the second terminal device, such as the LocalID of the second terminal device.

[0167] 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. Figure 8 S801 in the figure 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, the following step S802 is executed:

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

[0169] 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.

[0170] 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.

[0171] 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.

[0172] 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.

[0173] The fourth message indicates that the first terminal device releases the second terminal device. Specifically, S804 may be implemented according to the description in S703, which will not be described in detail in the embodiment of the present application.

[0174] In addition, optionally, if the access network device does not receive the SUI from the first terminal device within a preset time after executing S801, i.e. sending the third message, the third message may be resent to the second terminal device through the first terminal device. In a possible scenario, the second terminal device successfully receives the third message resent by the access network device, and then continues to execute steps S802 to S804.

[0175] 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 wireless 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.

[0176] Fig. 9 A communication method provided in an embodiment of the present application can be applied to Figure 4 Schematic communication architecture.

[0177] When data is transmitted, 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, and 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 data is transmitted, the second terminal device can directly communicate 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.

[0178] Specifically, Fig. 9 The illustrative method may include the following steps.

[0179] 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.

[0180] Specifically, the third message may be an RRC release message, and the RRC release message 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 may carry identification information of the second terminal device, such as the LocalID of the second terminal device. In a possible implementation, the access network device may send the third message to the second terminal device based on a non-direct link, i.e., through the first terminal device. For example, if 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 (PC5 Relay 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 may send the third message to the second terminal device through the first terminal device.

[0181] In one possible scenario of this implementation, 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, that is, the second terminal device does not receive the third message and continues to maintain the connected state; but the first terminal device sends an ACK corresponding to the third message to the access network device, and the access network device mistakenly believes that the second terminal device has entered the connected state and switched to the idle state or deactivated state. Such a situation leads to inconsistent understanding of the state of the second terminal device between the access network device side and the second terminal device side, and the second terminal device continues to maintain the connected state, causing unnecessary power consumption.

[0182] In another possible scenario of this implementation, the access network device sends the third message to the first terminal device; the first terminal device fails to receive the third message and replies NACK to the access network device, but the access network device incorrectly decodes the NACK as ACK, and the access network device mistakenly believes that the second terminal device has switched from the connected state to the idle state or the deactivated state. Such a situation will also lead to inconsistent understanding of the state of the second terminal device between the access network device side and the second terminal device side, and the second terminal device continues to maintain the connected state, causing unnecessary power consumption.

[0183] 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.

[0184] In another possible implementation, the access network device can directly send the third message 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 the mapping relationship between SRB1 and the third communication link, such as the access network device configures the mapping relationship between SRB1 and the third radio bearer (Uu Relay RLC channel) of the third communication link, then the access network device can directly send the third message to the second terminal device.

[0185] In one possible scenario of this implementation, 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 to the access network device in response to the third message; but the access network device interprets the NACK sent by the second terminal device in error and obtains an ACK; the access network device mistakenly believes that the second terminal device has entered the connected state and switched to the idle state or deactivated state. Such a situation will also lead to inconsistent understanding of the state of the second terminal device between the access network device side and the second terminal device side, and the second terminal device continues to maintain the connected state, causing unnecessary power consumption.

[0186] Based on the above possible situations, if the access network device is a base station including CU and 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 CU and DU and the CU is separated into CU-CP and 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 view of the above situation, the access network device may configure the timing configuration information for deciding the switching state to the second terminal device, so as to reduce the time that the second terminal device maintains the connection state without data transmission, thereby reducing the power consumption of the second terminal device. In addition to configuring the timing configuration information for the above situation, the embodiment 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: Fig. 9 S900 indicated by a dotted line is an optional step. In one possible implementation, the access network device may execute S900 and then execute the following steps S901 to S902. In another possible implementation, the access network device may not execute S900 and directly execute the following steps S901 to S902 to implement the configuration and application of the timing configuration information.

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

[0188] 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.

[0189] 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 the 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.

[0190] In another possible design, the access network device may directly send the timing configuration information to the second terminal device based on the direct link. Wherein, 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 the 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 the 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, it can be set to start the timing 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 has no data transmission including the second terminal device not performing data transmission on the first communication link and the third communication link, and data transmission includes sending and receiving data. Optionally, the timing configuration information sent by the access network device can be determined according to the Datainactivitytimer mechanism, and the first time period can also be described as Datainactivitytimer.

[0191] Exemplarily, the second terminal device does not perform data transmission on the first communication link, specifically including that there is no data transmission on at least one channel between the second terminal device and the first terminal device. Among them, data transmission includes uplink data transmission and downlink data transmission. The channel between the second terminal device and the first terminal device can 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.

[0192] Exemplarily, the second terminal device does not perform data transmission 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, there is no data transmission on at least one channel between the second terminal device and the access network device, including 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.

[0193] 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.

[0194] S902: If there is no data transmission on the first communication link and the second 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.

[0195] Exemplarily, in the Datainactivitytimer mechanism, the situation in which the second terminal device still has no data transmission after the first time period has passed can be 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.

[0196] 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 may further perform step S903, Fig. 9 The optional step S903 is indicated by a dotted line.

[0197] 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.

[0198] 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.

[0199] Fig. 9 The above scheme can be applied to the multi-path relay scenario, when the remote UE does not transmit data on the logical channels on Uu and PC5, and the decision triggers the Datainactivitytimer. When the Datainactivitytimer times out, the remote UE automatically enters the RRC IDLE state, thereby solving the problem of inconsistent RRC states between the remote UE and the base station side, and reducing unnecessary energy consumption of the remote UE.

[0200] The above application provides Figure 6 to Figure 9 The methods described can be implemented independently or in combination, and the embodiments of the present application are not limited thereto. Figure 7 and Figure 8In combination, 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 the connected state to the idle state or the deactivated state; if the access network device receives the first information from the first terminal device, it sends a fourth message to the first terminal device. Figure 7 In the case where the second terminal device fails to receive the third message, the first information includes data of the second terminal device; or corresponding to Figure 7 In the case where the second terminal device successfully receives the third message, the first information is used to indicate that the connection between the first terminal device and the second terminal device has been released.

[0201] In the embodiments provided by the present application, the methods provided by the embodiments of the present application are introduced from the perspective of interaction between various devices. In order to implement the functions in the methods provided by 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.

[0202] Based on the same idea, see Fig.10 , the 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 a terminal device or used in combination with a terminal device, and capable of implementing a communication method executed by the terminal device side; or, the communication device 1000 can be an access network device, or a communication device applied to an access network device or used in combination with an access network device, and capable of implementing a communication method executed by the access network device.

[0203] The communication module may also be referred to as a transceiver module, a transceiver, a transceiver, or a transceiver device, etc. The processing module may also be referred to as a processor, a processing board, a processing unit, or a processing device, etc. Optionally, the communication module is used to perform the sending operation and the receiving operation on the terminal device side or the access network device side in the above method, and the device used to implement the receiving function in the communication module may be regarded as a receiving unit, and the device used to implement the sending function in the communication module may be regarded as a sending unit, that is, the communication module includes a receiving unit and a sending unit.

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

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

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

[0207] In addition, it should be noted that, in one possible design, the aforementioned communication module and / or processing module may be implemented through a virtual module, for example, the processing module may be implemented through a software function unit or a virtual device, and the communication module may be implemented through a software function or a virtual device. In another possible design, the processing module or the communication module may also be implemented through a physical device, for example, if the device is implemented using a chip / chip circuit, the communication module may be an input / output circuit and / or a communication interface, performing 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.

[0208] The division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each example of the embodiments of the present application may be integrated into a processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0209] Based on the same technical concept, the embodiment of the present application also 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.

[0210] 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.

[0211] The communication device 1100 may also include a communication interface 1130, and the communication device 1100 may exchange information with other devices through the communication interface 1130. Exemplarily, the communication interface 1130 may be a transceiver, a circuit, a bus, a module, a pin, or other types of communication interfaces. 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, which may input information (or receive information) and output information (or send information), and the processor may be an integrated processor or a microprocessor or an integrated circuit or a logic circuit, and the processor may determine the output information based on the input information.

[0212] The coupling in the embodiment 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 cooperate with the memory 1120 and the communication interface 1130. The specific connection medium between the above-mentioned processor 1110, the memory 1120 and the communication interface 1130 is not limited in the embodiment of the present application.

[0213] Optional, see Fig.11 The processor 1110, the memory 1120 and the communication interface 1130 are connected to each other via a bus 1040. The bus 1040 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.11 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0214] 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 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 method of the embodiment applied in conjunction with the embodiment of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0215] In the 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.

[0216] 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 performed by the first terminal device in any of the above-mentioned examples. If 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.

[0217] In a 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 above-mentioned examples. The memory 1120 stores a computer program (or instruction) and / or data that implements the functions of the second 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 second terminal device in any of the above-mentioned examples. If the communication device is applied to a 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.

[0218] 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 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 a computer program (or instruction) and / or data that implements 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).

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

[0220] The technical solution provided in the embodiment of the present application can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it 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 process or function described in the embodiment of the present application is generated in whole or in part. The computer may 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 may 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 may be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrated. 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, etc.

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

[0222] Obviously, those skilled in the art can 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 also 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