Wireless communication method, terminal and network equipment

Abstract

The invention discloses a wireless communication method, a terminal and network equipment, and belongs to the technical field of communication, the wireless communication method of the embodiment of the invention comprises the steps that the terminal is configured with at least three cell groups CGs, and the method comprises the steps that under the condition that a first CG in the at least three CGs fails, the terminal determines a second CG according to a target reporting mode; the terminal reports failure information of the first CG through the second CG; wherein the target reporting mode comprises any one of the following modes: a first reporting mode: reporting failure information of the first CG through all other CGs except the first CG in the at least three CGs; in the second reporting mode, the failure information of the first CG is reported through one CG in all other CGs except the first CG in the at least three CGs. The method for reporting the CG failure information by the terminal in the multi-connection scene is provided, so that the abnormal link can be quickly recovered.

Description

Technical Field

[0001] This application belongs to the field of communication technologies, and particularly relates to a wireless communication method, a terminal, and a network device. Background Art

[0002] Dual connectivity (DC) technology provides resources of two network devices for a terminal, where one is called a Master Node (MN), and the other is called a Secondary Node (SN). For each network device, Carrier Aggregation (CA) technology can also be used to configure a series of serving cells controlled by the device for the terminal. These serving cells form a Cell Group (CG). Among them, the cell group controlled by the MN is the Master Cell Group (MCG), and the cell group controlled by the SN is the Secondary Cell Group (SCG). The multi-connectivity technology is similar to the dual-connectivity technology, and the difference is that the multi-connectivity technology provides resources of more than two network devices for the terminal.

[0003] Currently, in the dual-connectivity scenario, if any one of the Cell Groups (CGs) in the Master Cell Group (MCG) and the Secondary Cell Group (SCG) fails, the terminal can report the failure information of the failed CG through the other one of the MCG and the SCG to quickly recover the abnormal link.

[0004] In the multi-connectivity scenario, if a certain CG fails, how the terminal reports the failure information of the CG to quickly recover the abnormal link is a technical problem to be urgently solved in this application. Summary of the Invention

[0005] Embodiments of this application provide a wireless communication method, a terminal, and a network device, which can solve the technical problem of how the terminal reports the failure information of a certain CG to quickly recover the abnormal link in the multi-connectivity scenario.

[0006] In a first aspect, a wireless communication method is provided and executed by a terminal. The method includes: The terminal is configured with at least three Cell Groups (CGs). The method includes: when a first CG among at least three CGs fails, the terminal determines a second CG according to a target reporting method; the terminal reports the failure information of the first CG through the second CG;

[0007] Wherein, the target reporting method includes any one of the following:

[0008] The first reporting method: report the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0009] The second reporting method: report the failure information of the first CG through one CG among all other CGs except the first CG among at least three CGs.

[0010] In a second aspect, a wireless communication method is provided, which is executed by a network device. The method includes: the network device receives the failure information of the first CG reported by the terminal through the second CG; wherein, the terminal is configured with at least three cell groups (CGs), the first CG is the CG that fails among at least three CGs, and the second CG is determined by the terminal according to the target reporting method;

[0011] The target reporting method includes any one of the following:

[0012] The first reporting method: report the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0013] The second reporting method: report the failure information of the first CG through one CG among all other CGs except the first CG among at least three CGs.

[0014] In a third aspect, a wireless communication device is provided. The device is configured with at least three CGs. The device includes:

[0015] A processing module, configured to determine a second CG according to the target reporting method when the first CG among at least three CGs fails;

[0016] A communication module, configured to report the failure information of the first CG through the second CG;

[0017] Wherein, the target reporting method includes any one of the following:

[0018] The first reporting method: report the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0019] The second reporting method: report the failure information of the first CG through one CG among all other CGs except the first CG among at least three CGs.

[0020] In a fourth aspect, a wireless communication device is provided, including:

[0021] A communication module, configured to receive the failure information of the first CG reported by the terminal through the second CG;

[0022] Wherein, the terminal is configured with at least three cell groups (CGs), the first CG is the CG that fails among at least three CGs, and the second CG is determined by the terminal according to the target reporting method;

[0023] The target reporting method includes any one of the following:

[0024] The first reporting method: Report the failure information of the first CG through all the other CGs except the first CG among at least three CGs;

[0025] The second reporting method: Report the failure information of the first CG through one CG among all the other CGs except the first CG among at least three CGs.

[0026] In a fifth aspect, a terminal is provided, which includes a processor and a memory. The memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the method in the first aspect are implemented.

[0027] In a sixth aspect, a terminal is provided, including a processor and a communication interface. Wherein, the processor is used to determine a second CG according to the target reporting method when a failure occurs in the first CG among at least three CGs, and the communication interface is used to report the failure information of the first CG through the second CG.

[0028] Wherein, the target reporting method includes any one of the following:

[0029] The first reporting method: Report the failure information of the first CG through all the other CGs except the first CG among at least three CGs;

[0030] The second reporting method: Report the failure information of the first CG through one CG among all the other CGs except the first CG among at least three CGs.

[0031] In a seventh aspect, a network device is provided, which includes a processor and a memory. The memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the method in the second aspect are implemented.

[0032] In an eighth aspect, a network device is provided, including a processor and a communication interface. Wherein, the communication interface is used to receive the failure information of the first CG reported by the terminal through the second CG;

[0033] Wherein, the terminal is configured with at least three cell groups CG, the first CG is the CG that fails among at least three CGs, and the second CG is determined by the terminal according to the target reporting method;

[0034] The target reporting method includes any one of the following:

[0035] The first reporting method: Report the failure information of the first CG through all the other CGs except the first CG among at least three CGs;

[0036] Second reporting method: Report the failure information of the first CG through one of all the other CGs except the first CG among at least three CGs.

[0037] In a ninth aspect, a readable storage medium is provided, on which a program or instructions are stored. When the program or instructions are executed by a processor, the steps of the method in the first aspect are implemented, or the steps of the method in the second aspect are implemented.

[0038] In a tenth aspect, a wireless communication system is provided, including: a terminal and a network device. The terminal can be used to execute the steps of the method in the first aspect, and the network device can be used to execute the steps of the method in the second aspect.

[0039] In an eleventh aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run a program or instructions to implement the method in the first aspect, or to implement the method in the second aspect.

[0040] In a twelfth aspect, a computer program / program product is provided. The computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the wireless communication method in the first aspect.

[0041] In the embodiments of the present application, the terminal is configured with at least three CGs. The method includes: when a failure occurs in the first CG among at least three CGs, the terminal determines a second CG according to the target reporting method; the terminal reports the failure information of the first CG through the second CG; where the target reporting method includes any one of the following: First reporting method: Report the failure information of the first CG through all the other CGs except the first CG among at least three CGs; Second reporting method: Report the failure information of the first CG through one of all the other CGs except the first CG among at least three CGs. That is, a method for the terminal to report CG failure information in a multi-connection scenario is provided to quickly recover an abnormal link. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 is a schematic diagram of a multi-connection scenario provided by the embodiments of the present application;

[0043] Figure 2 is a schematic diagram of a bearer from the perspective of the network side;

[0044] Figure 3 is a schematic diagram of a bearer from the perspective of the terminal side;

[0045] Figure 4 is an interaction flowchart of a wireless communication method provided by the embodiments of the present application;

[0046] Figure 5It is a schematic diagram of a type A separation carrier provided by an embodiment of the present application;

[0047] Figure 6 It is another schematic diagram of a type A separation carrier provided by an embodiment of the present application;

[0048] Figure 7 It is a schematic diagram of a type B separation carrier provided by an embodiment of the present application;

[0049] Figure 8 It is another schematic diagram of a type B separation carrier provided by an embodiment of the present application;

[0050] Figure 9 It is a schematic diagram of a wireless communication device 900 provided by an embodiment of the present application;

[0051] Figure 10 It is a schematic diagram of a wireless communication device 1000 provided by an embodiment of the present application;

[0052] Figure 11 It is a schematic block diagram of a communication device provided by an embodiment of the present application;

[0053] Figure 12 It is a schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application;

[0054] Figure 13 It is a schematic diagram of the hardware structure of a network device for implementing an embodiment of the present application. Detailed implementation manners

[0055] Next, the technical solutions in the embodiments of the present application will be clearly described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0056] The terms "first", "second", etc. in the present application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are usually of the same type, and the number of objects is not limited. For example, the first object can be one or multiple. In addition, "or" in the present application means at least one of the connected objects. For example, "A or B" covers three scenarios, namely, Scenario 1: including A and not including B; Scenario 2: including B and not including A; Scenario 3: including both A and B. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0057] The term "indication" in this application can be either a direct indication (or an explicit indication) or an indirect indication (or an implicit indication). Among them, a direct indication can be understood as that the sender clearly informs the receiver of specific information, operations to be performed, or request results, etc. in the sent indication; an indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or makes a judgment and determines the operations to be performed or request results, etc. according to the judgment result.

[0058] It should be noted that the embodiments of this application relate to multi-connection technology. Among them, the multiple radio communication systems corresponding to multi-connection can adopt the same radio access technology (RAT), or can adopt different RATs. The embodiments of this application do not limit this. The radio communication system corresponding to each connection is not limited to the Long-Term Evolution (LTE) / LTE-Advanced (LTE-A) system, and can also be used in other radio communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, and can also be used in other systems and radio technologies. The following description describes the New Radio (NR) system for example purposes, and uses NR terms in most of the following descriptions, but these technologies can also be applied to systems other than the NR system, such as 6G communication systems.

[0059] Figure 1 is a schematic diagram of the multi-connection scenario provided by the embodiments of this application. As Figure 1 shown, the terminal 11 is connected to the first network device 12, the second network device 13, and the third network device 14.

[0060] The wireless communication system composed of the first network device 12 and the terminal 11, the wireless communication system composed of the second network device 13 and the terminal 11, and the wireless communication system composed of the third network device 14 and the terminal 11 may adopt the same RAT or different RATs, and the embodiments of the present application do not limit this. For example, the wireless communication system composed of the first network device 12 and the terminal 11 adopts LTE technology, the wireless communication system composed of the second network device 13 and the terminal 11 adopts NR technology, and the wireless communication system composed of the third network device 14 and the terminal 11 adopts LTE-A technology. For another example, the wireless communication systems composed of the first network device 12 and the terminal 11, the second network device 13 and the terminal 11, and the third network device 14 and the terminal 11 all adopt NR technology.

[0061] For any one of the first network device 12, the second network device 13, and the third network device 14, it may correspond to a CG. One of the CGs can be used as the MCG, and the remaining CGs can be used as SCGs. Multiple SCGs can be distinguished by their respective identifiers or names, etc. For example, the network configures one of the SCGs as the primary SCG, or the special SCG, or the default SCG, and the remaining SCGs as normal SCGs. For another example, the network configures multiple SCGs as the secondary CG, the third CG, and so on. In short, the embodiments of the present application do not limit how to model and distinguish between multiple CGs. For the convenience of description, the embodiments of the present application adopt a description method including one MCG and multiple SCGs.

[0062] Among them, the terminal 11 can be a mobile phone, a tablet personal computer, a laptop computer, a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device, a flight vehicle, a vehicle user equipment (VUE), a shipborne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, TVs, washing machines, or furniture, etc.), a game console, a personal computer (PC), an ATM, or a self-service machine, etc., which are terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart ankle chains, etc.), smart wristbands, smart clothing, etc. Among them, vehicle user equipment can also be referred to as vehicle terminals, vehicle controllers, vehicle modules, vehicle components, vehicle chips, or vehicle units, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application.

[0063] In some implementable manners, the first network device 12, the second network device 13, and the third network device 14 can be three different access network devices. The first network device 12, the second network device 13, and the third network device 14 all have user plane interfaces with the core network to receive data from the core network.

[0064] In some other realizable manners, the first network device 12, the second network device 13, and the third network device 14 may be three Distributed Units (DUs), and these DUs share a Central Unit (CU). Alternatively, one of the first network device 12, the second network device 13, and the third network device 14 is an access network device, and the other two network devices are two DUs, and these two DUs share a CU. For example, the first network device 12 is an access network device, and the second network device 13 and the third network device 14 may be two DUs connected to the same CU. Among them, in this realizable manner, the data from the core network first reaches the CU, and then the CU sends it to the corresponding DU, and there is no user plane interface between the DU and the core network.

[0065] Among them, the access network device may also be referred to as a Radio Access Network (RAN) device, a radio access network function, or a radio access network unit. The access network device may include a base station, a Wireless Local Area Network (WLAN) Access Point (AP), or a Wireless Fidelity (WiFi) node, etc. Among them, the base station may be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home Node B (HNB), home evolved Node B, Transmission Reception Point (TRP), or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to a specific technical term. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0066] It should be understood that Figure 1Shown is an example of a multi-connection scenario. In Figure 1 In the multi-connection scenario shown, there are three connections. In fact, the multi-connection scenario can include more connections. In short, the embodiments of the present application do not limit the multi-connection scenario.

[0067] Before introducing the technical solution of the present application, the relevant knowledge of the present application will be described below:

[0068] I. DC

[0069] DC technology provides resources of two network devices for the terminal. One is called MN, and the other is called SN. For each network device, CA technology can also be used to configure a series of serving cells controlled by the device for the terminal. These serving cells form a CG. Among them, the cell group controlled by MN is MCG, and the cell group controlled by SN is SCG. Each CG contains a special cell (Special Cell, SpCell) and a series of secondary cells (Secondary Cell, SCell). In MCG, the special cell is called the primary cell (Primary Cell, PCell), and in SCG, the special cell is called the primary-secondary cell (PrimarySecondary Cell, PSCell).

[0070] II. Release (R) 15 SCG failure information process

[0071] 1. When one of the following conditions is met and the transmissions of both MCG and SCG are not suspended, the terminal initiates the SCG failure information process to report the SCG failure information:

[0072] - SCG radio link failure;

[0073] - SCG synchronization reconfiguration failure;

[0074] - SCG configuration failure;

[0075] - Integrity check failure of Signalling Radio Bearer (SRB) 3.

[0076] 2. Once the SCG failure information process is initiated, the terminal performs the following steps:

[0077] - Suspend the SCG transmissions of all SRBs and Data Radio Bearers (DRBs);

[0078] - Reset the SCG Media Access Control (MAC);

[0079] - If T304 of the SCG is running, stop T304 of the SCG;

[0080] - If conditional PSCell change (CPC) is configured, stop the evaluation of CPC;

[0081] - Send SCG failure information.

[0082] 3. The SCG failure information will include the following information:

[0083] - SCG failure reason (failureType): The terminal needs to set a reasonable SCG failure reason according to the actual situation. The current SCG failure reasons include: {t310 termination (t310-Expiry), random access problem (randomAccessProblem), radio link control (RLC) layer reaches the maximum number of retransmissions (rlc-MaxNumRetx), SCG synchronization reset failure (synchReconfigFailureSCG), SCG reset failure (scg-ReconfigFailure), integrity check failure of SRB3 (srb3-IntegrityFailure), other cases in R16 (other-R16), spare case 1}

[0084] - Measurement results corresponding to the measurements configured in the measurement configuration (measConfig);

[0085] - Measurement results corresponding to the measurements configured by the SN.

[0086] III. R16 MCG failure information (failure information) procedure, also known as the MCG fast recovery (FastMCG recovery) procedure:

[0087] 1. When one of the following conditions is met, when the terminal detects a MCG radio link failure (RLF), the terminal triggers the MCG fast recovery procedure instead of triggering the radio resource control (RRC) RRC connection reestablishment procedure.

[0088] - The network configures the timer T316 for the terminal;

[0089] - The network configures split SRB1 and / or SRB3 for the terminal;

[0090] - After the security activation of the access stratum (AS) of the terminal and the establishment of SRB2 and at least one DRB.

[0091] 2. The terminal triggers the Fast MCG recovery process, that is, the terminal sends MCG failure information (Failure Information) to the MN through the SCG (split SRB1 or SRB3):

[0092] If the terminal sends the MCG failure information through SRB3, the terminal encapsulates the MCG failure information in the ULInformationTransferMRDC message container and sends it to the SN, and the SN forwards the MCG failure information in it to the MN after receiving it.

[0093] If the terminal sends the MCG failure information through Split SRB1, the terminal can send the MCG failure information on split SRB1. After sending the MCG failure information, the terminal starts T316 and performs the following operations:

[0094] - Suspend the transmission on all SRBs and DRBs of the MCG;

[0095] - Reset the MCG MAC;

[0096] - Save the current measurement configurations of the MN and the SN;

[0097] - Continue to perform measurements based on the configuration.

[0098] After receiving the MCG failure information, the MN can send an RRC reconfiguration (Reconfiguration) message or an RRC release (Release) message to the terminal, and this message is transparently transmitted to the terminal through the SN's DLInformationTransferMRDC. After the terminal receives the RRC release message, the terminal releases all radio bearers and configurations. During the running of T316, if the terminal receives the RRC reconfiguration from the MN, it stops T316 and resumes the transmission of the MCG. If T316 times out and the terminal does not receive the RRC reconfiguration from the MN, the terminal triggers the RRC connection reestablishment process and sets the reestablishment cause value to other failure reasons (otherFailure).

[0099] IV. R17 SCG activation / deactivation mechanism

[0100] R17 introduces the SCG activation / deactivation mechanism. When there is no data to be transmitted on the SCG, the terminal is currently overheated, or the terminal is for power saving purposes, the network side and the terminal side can initiate the SCG deactivation process. When these conditions change, the network side and the terminal side can initiate the SCG activation process again.

[0101] During the SCG deactivation, the terminal does not monitor the Physical Downlink Control Channel (PDCCH) on the SCG, nor does it have behaviors such as Physical Uplink Shared Channel (PUSCH) transmission and Sounding Reference Signal (SRS) transmission, so as to save the power consumption of the terminal.

[0102] In addition, during the SCG deactivation, the terminal may also perform Radio Resource Management (RRM) measurements, Radio Link Monitoring (RLM), and beam management of the SCG, so as to ensure that the SCG can work properly when it is activated.

[0103] V. Bearers in DC

[0104] It should be understood that in the embodiments of the present application, the RLC bearer is also referred to as RLC, RLC entity, etc., and the embodiments of the present application do not limit this. Among them, the RLC bearer includes the configurations of RLC and MAC.

[0105] It should be understood that in the embodiments of the present application, the Packet Data Convergence Protocol (PDCP) bearer is also referred to as PDCP, PDCP entity, etc., and the embodiments of the present application do not limit this.

[0106] It should be understood that in the embodiments of the present application, a certain RLC bearer corresponds (maps) to a certain CG, and is also referred to as the bearer being located in the CG, or the bearer being located in the network node corresponding to the CG. The embodiments of the present application do not limit this. In the embodiments of the present application, one RLC bearer corresponds to one RLC entity and one CG.

[0107] In DC, there are three types of radio bearers, including:

[0108] - MCG bearer: The RLC bearer (i.e., the RLC entity) corresponds to the radio bearer of the MCG;

[0109] - SCG bearer: The RLC bearer corresponds to the radio bearer of the SCG;

[0110] - Split bearer: It has two RLC bearers, and the two RLC bearers correspond to the radio bearers of the MCG and the SCG.

[0111] Among them, the above three types of radio bearers can be further divided into MN-terminated bearers and SN-terminated bearers according to the node to which the PDCP bearer belongs.

[0112] Figure 2 It is a schematic diagram of the bearer from the perspective of the network side. Figure 3 It is a schematic diagram of the bearer from the perspective of the terminal side.

[0113] MN-terminated MCG bearer: As Figure 2 shown, after the downlink data arrives at the User Plane Function (UPF) of the core network, it is sent from the core network to the MN. After being processed by the Service Data Adaptation Protocol (SDAP) and PDCP in the MN, it is sent to the terminal through the air interface resource configuration of the MN. Among them, the air interface resource configuration of the MN includes: MN RLC and MN MAC. Among them, MN RLC is also referred to as the MNRLC entity, MN RLC bearer, MCG RLC, MCG RLC entity, MCG RLC bearer. MN MAC is also referred to as the MN MAC entity, MN MAC bearer, MCG MAC, MCG MAC entity, MCG MAC bearer. As Figure 3 shown, after the terminal receives the data through the MCG MAC, it sequentially delivers it to the MCG RLC, PDCP, and SDAP for processing. Among them, the PDCP of the terminal corresponds to the PDCP of the MN.

[0114] MN-terminated SCG bearer: As Figure 2 shown, the difference between the MN-terminated SCG bearer and the MN-terminated MCG bearer is that after being processed by the SDAP and PDCP in the MN, the MN sends the PDCP data to the SN through the Xn interface, and then sends it to the terminal through the air interface resource configuration of the SN. Among them, the air interface resource configuration of the SN includes: SN RLC and SN MAC. Among them, SN RLC is also referred to as the SN RLC entity, SN RLC bearer, SCG RLC, SCG RLC entity, SCG RLC bearer. SN MAC is also referred to as the SN MAC entity, SN MAC bearer, SCG MAC, SCG MAC entity, SCG MAC bearer. As Figure 3 shown, after the terminal receives the data through the SCG MAC, it sequentially delivers it to the SCG RLC, PDCP, and SDAP for processing.

[0115] MN terminated split bearer: As Figure 2 shown, after the downlink data arrives at the UPF of the core network, it is sent by the core network to the MN. After being processed by the SDAP and PDCP in the MN, it is sent to the terminal through the air interface resource configuration between the MN and the SN. As Figure 3 shown, after the terminal receives the data through the MN MAC, it is delivered upward to the MN RCL. At the same time, after the terminal receives the data through the SCG MAC, it is delivered upward to the SCG RLC. The data will converge at the PDCP and then be delivered to the SDAP for processing.

[0116] SN terminated SCG bearer: As Figure 2 shown, after the downlink data arrives at the UPF of the core network, it is sent by the core network to the SN. After being processed by the SDAP and PDCP in the SN, it is sent to the terminal through the air interface resource configuration of the SN. As Figure 3 shown, after the terminal receives the data through the SN MAC, it is delivered upward to the SCG RLC, PDCP, and SDAP for processing in sequence. The PDCP of the terminal corresponds to the PDCP of the SN.

[0117] SN terminated MCG bearer: As Figure 2 shown, the difference between the SN terminated MCG bearer and the SN terminated SCG bearer is that: after being processed by the SDAP and PDCP in the SN, the SN sends the PDCP data to the MN through the Xn interface, and then it is sent to the terminal through the air interface resource configuration of the MN. As Figure 3 shown, after the terminal receives the data through the MCG MAC, it is delivered upward to the MCG RLC, PDCP, and SDAP for processing in sequence.

[0118] SN terminated split bearer: As Figure 2 shown, after the downlink data arrives at the UPF of the core network, it is sent by the core network to the SN. After being processed by the SDAP and PDCP in the SN, it is sent to the terminal through the air interface resource configuration between the MN and the SN. As Figure 3 shown, after the terminal receives the data through the MCG MAC, it is delivered upward to the MCG RLC. At the same time, after the terminal receives the data through the SCG MAC, it is delivered upward to the SCG RLC. The data will converge at the PDCP and then be delivered to the SDAP for processing.

[0119] VI. Multi-connection

[0120] On the one hand, multi-connection technology can aggregate the transmission resources of more than two network devices, make full use of the discretely distributed resources of the communication system, and improve the system capacity.

[0121] On the other hand, in order to improve system capacity, higher communication frequencies may be introduced into 6G communication systems. Although high-frequency signals have the advantage of large bandwidth, they also have significant disadvantages, namely unstable signal quality. High-frequency signals may experience a significant drop in quality when blocked by obstacles. Multi-connection technology, with multiple available transmission paths, is conducive to improving the stability of terminals under such high-frequency transmission.

[0122] As described above, in a multi-connection scenario, if a CG fails, how the terminal reports the failure information of the CG to quickly restore the abnormal link is a technical problem that needs to be urgently solved in this application.

[0123] In order to solve the above technical problems, an embodiment of the present application provides a method for a terminal to report CG failure information in a multi-connection scenario.

[0124] The wireless communication method provided in the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

[0125] Figure 4 An interactive flow chart of a wireless communication method provided in an embodiment of the present application, the method can be executed by a terminal and a network device, the terminal can be Figure 1 The terminal 11 in, but not limited to this. The network device can Figure 1 The first network device 12, the second network device 13 or the third network device 14 in the embodiment, but not limited thereto. , wherein the terminal is configured with at least three CGs, or the terminal is connected to at least three network devices, or the terminal is in a multi-connection scenario. Figure 4 As shown, the method may include:

[0126] S410: When a first CG among at least three CGs fails, the terminal determines a second CG according to a target reporting method;

[0127] S420: The terminal reports the failure information of the first CG to the network device corresponding to the first CG through the second CG.

[0128] The target reporting method includes any of the following:

[0129] The first reporting method: report the failure information of the first CG through all other CGs except the first CG among at least three CGs.

[0130] Second reporting method: Report the failure information of the first CG through one of all the other CGs except the first CG among at least three CGs.

[0131] In some implementable manners, the first CG may be an MCG or any one of the SCGs.

[0132] In some implementable manners, the situations where the first CG fails include at least one of the following, but are not limited thereto:

[0133] (1) Radio link failure of the first CG;

[0134] (2) Synchronization reconfiguration failure of the first CG;

[0135] (3) Configuration failure of the first CG;

[0136] (4) Integrity detection failure of the SRB corresponding to the first CG.

[0137] In some implementable manners, the SRB corresponding to the first CG includes at least one of the following, but are not limited thereto:

[0138] (1) The dedicated SRB that the first CG has;

[0139] (2) The target separation SRB that the first CG has.

[0140] In a multi-connection scenario, for any one CG, the dedicated SRB that the CG has means that both the PDCP bearer and the RLC bearer correspond to the CG.

[0141] For example, assume Figure 2 that the MN-terminated MCG bearer in [description] is the MN-terminated MCG SRB. Since both the PDCP bearer and the RLC bearer of this MN-terminated MCG SRB correspond to the MCG, therefore, this MN-terminated MCG SRB is the dedicated bearer of the MCG.

[0142] For another example, assume Figure 2 that the SN-terminated SCG bearer in [description] is the SN-terminated SCG SRB. Since both the PDCP bearer and the RLC bearer of this SN-terminated SCG SRB are in the SCG, therefore, this SN-terminated SCG SRB is the dedicated bearer of the SCG.

[0143] For another example, SRB3 is the SN dedicated signaling bearer in NR-DC, that is, the SRB3 is configured by the SN. From the perspective of the network side, the PDCP of the SRB3 is in the SN, and the RLC bearer / entity is in the SN. From the perspective of the terminal, the PDCP of the SRB3 corresponds to the SCG, and the RLC bearer / entity corresponds to the SCG.

[0144] Taking the example of a terminal configured with one MCG and two SCGs, the split bearer in the multi-connection scenario is described as follows:

[0145] Suppose the terminal is configured with MCG, SCG 1, and SCG 2. In this scenario, the split bearer can include two types:

[0146] Type A: The PDCP of this bearer corresponds to one network node and includes the following three RLC bearers: MN RLC bearer, SN1 RLC bearer, and SN2 RLC bearer. Or rather, the PDCP bearer of this Type A bearer corresponds to one network node, and the three legs of this Type A bearer are composed of the MN RLC bearer, SN1 RLC bearer, and SN2 RLC bearer.

[0147] Type B: The PDCP bearer of Type B corresponds to one network node and includes two of the following three RLC bearers: MN RLC bearer, SN1 RLC bearer, and SN2 RLC bearer. Or rather, the PDCP bearer of this Type B bearer corresponds to one network node, and the two legs of this Type B bearer are composed of two of the MN RLC bearer, SCG 1 RLC bearer, and SCG 2 RLC bearer.

[0148] Among them, the RLC bearer includes the configurations of RLC and MAC. These two types of split bearers can be further divided into MN-terminated split bearer, SN1-terminated split bearer, and SN2-terminated split bearer according to the node to which the PDCP bearer belongs.

[0149] In the multi-connection scenario, when the network configures a split bearer, the configuration of this split bearer includes at least one of the following:

[0150] - The type of this split bearer: Type A or Type B;

[0151] - When the type of this split bearer is Type B, the two associated legs, where the two legs can respectively correspond to two SNs, or one leg corresponds to MN, and the other leg corresponds to SN1 or SN2.

[0152] - The location where the PDCP bearer of this split bearer is located.

[0153] It should be noted that if the PDCP bearer of this split bearer belongs to a certain network node, then this split bearer is configured by this network node.

[0154] For example, Figure 5 is a schematic diagram of a type A separation load provided in an embodiment of the present application, wherein: Figure 5 An MN terminated separate bearer of type A, an SN1 terminated separate bearer of type A, and an SN2 terminated separate bearer of type A are shown respectively.

[0155] For example, Figure 6 is another type A separation load diagram provided in an embodiment of the present application, wherein: Figure 6 A MN terminated split bearer of type A and an SN1 terminated split bearer of type A are shown respectively.

[0156] For example, Figure 7 is a schematic diagram of a type B separation load provided in an embodiment of the present application, wherein: Figure 7 A MN terminated separate bearer of type B, a SN1 terminated separate bearer of type B, and a SN2 terminated separate bearer of type B are shown respectively.

[0157] For example, Figure 8 is another type B separation load diagram provided in an embodiment of the present application, wherein: Figure 8 A MN terminated split bearer of type B and an SN1 terminated split bearer of type B are shown respectively.

[0158] For example, a split SRB1 associated with SCG2 (split SRB1 with SCG2) has two RLC bearers, one of which corresponds to the MCG and the other corresponds to the SCG2. In addition, the PDCP bearer of the split SRB1 associated with SCG2 corresponds to the MCG.

[0159] For example, split SRB3 with SCG2 has two RLC bearers, one of which corresponds to SCG1 and the other corresponds to SCG2. In addition, the PDCP bearer of split SRB3 with SCG2 corresponds to SCG1.

[0160] In some implementations, the target separation SRB has at least two RLC bearers, one of which corresponds to the first CG.

[0161] In some possible implementations, the PDCP entity corresponding to the above-mentioned target separation SRB is located in the network node corresponding to the first CG.

[0162] In some implementations, the terminal may determine the second CG based solely on the target reporting method.

[0163] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2. SCG1 fails, and the terminal is configured to report failure information using the first reporting method. Based on this, the terminal can report the failure information of SCG1 through MCG and SCG1 simultaneously.

[0164] In some implementable ways, the terminal can determine the second CG according to the target reporting method and the target condition;

[0165] In some implementable ways, the second CG meets the target condition, and the target condition includes at least one of the following: but not limited to:

[0166] (1), The transmission is not in a suspended state;

[0167] (2), Is in an active state;

[0168] (3), Has an SRB;

[0169] (4), Is configured or allowed to report the failure information of the first CG.

[0170] In some implementable ways, the second CG having an SRB includes at least one of the following: but not limited to:

[0171] (1), The second CG has a dedicated SRB;

[0172] (2), The second CG has a first split SRB;

[0173] Among them, the first split SRB has at least two RLC bearers, and one of the RLC bearers corresponds to the second CG.

[0174] It should be understood that the explanation of the split SRB can refer to the above, and the embodiments of the present application will not elaborate on this.

[0175] In some implementable ways, the PDCP entity corresponding to the first split SRB is located in the MN or the SN corresponding to the first CG.

[0176] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2. SCG1 fails, and assume that the failure information of SCG1 is reported through SCG2. Then, the PDCP entity corresponding to the first split SRB of SCG2 is located in the MN or the SN1 corresponding to SCG1.

[0177] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2. SCG1 fails, and assume that the failure information of SCG1 is reported through MCG. Then, the PDCP entity corresponding to the first split SRB of MCG is located in the MN or the SN1 corresponding to SCG1.

[0178] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2. MCG fails, and assume that the failure information of MCG is reported through SCG1. Then, the PDCP entity corresponding to the first split SRB of SCG1 is located in the MN.

[0179] In some implementable manners, the terminal can receive first indication information; wherein, the second CG is configured or allowed to report the failure information of the first CG, including: the first indication information indicates that the second CG can report the failure information of the first CG; or, the first indication information indicates one or more CGs that can report the failure information, wherein the one or more CGs include the identifier of the second CG.

[0180] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2. SCG1 fails, and the terminal receives first indication information sent by the network device indicating that SCG2 can report the failure information of SCG1. Then, the terminal can report the failure information of SCG1 through SCG2.

[0181] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2. SCG1 fails, and assume that the target reporting manner is the first reporting manner. The terminal receives first indication information sent by the network device indicating that the CGs that can report the failure information are MCG and SCG2. Then, the terminal can report the failure information of SCG1 through MCG and SCG2 simultaneously.

[0182] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2. SCG1 fails, and assume that the target reporting manner is the second reporting manner. The terminal receives first indication information sent by the network device indicating that the CGs that can report the failure information are MCG and SCG2. Then, the terminal can report the failure information of SCG1 through MCG or SCG2.

[0183] From the perspective of the network side, the second CG is configured with enabling information for enabling the failure information reporting process, so that the second CG is configured or allowed to report the failure information of the first CG; or, the first CG is configured to use the second CG to report the failure information of the first CG, so that the second CG is configured or allowed to report the failure information of the first CG.

[0184] For example, assume that the terminal is connected to four CGs, including: MCG, SCG1, SCG2, and SCG3. SCG 2 is configured with 1-bit enabling information to enable the failure information reporting process. When SCG 1 or SCG 3 fails, the terminal can report the corresponding failure information through SCG 2.

[0185] For example, assume that the terminal is connected to four CGs, including: MCG, SCG1, SCG2, and SCG3. SCG 1 is configured to use SCG2 to report the failure information of SCG1. Or, the configuration information of SCG 1 includes Recovery leg = SCG2. Then, only when SCG 1 fails can the terminal report the failure information of SCG1 through SCG 2. When SCG3 fails, the failure information of SCG3 cannot be reported through SCG2 and can only notify MCG to report the failure information of SCG3.

[0186] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2. MCG fails, and SCG 1 is configured with enabling information to enable the failure information reporting process. SCG2 is not configured with this enabling information. Then, the terminal can only report the failure information of MCG through this SCG 1 and cannot report the failure information of MCG through SCG 2.

[0187] In some implementable ways, when the target reporting method is the second reporting method, the terminal can determine the second CG according to the priority rules between the second reporting method and at least three CGs.

[0188] In some implementable ways, the priority rules between at least three CGs include any one of the following, but are not limited to this:

[0189] (1) The priority rules between MCG and any SCG;

[0190] (2) The priority rules between each SCG;

[0191] (3) Determine the priority of at least three CGs according to the priority parameters of at least three CGs;

[0192] (4) Among at least three CGs, the higher the signal quality of the CG, the higher the corresponding priority;

[0193] (5) Among at least three CGs, the earlier the uplink resource acquisition time of the CG, the higher the corresponding priority.

[0194] The following explains the priority rule (1) between at least three CGs:

[0195] In some implementable ways, the priority rules between MCG and any SCG include any one of the following, but are not limited to this:

[0196] (1) The priority of MCG is higher than that of any SCG;

[0197] (2) The priority of MCG is lower than that of any SCG.

[0198] In some implementations, the priority rules between the MCG and any SCG are configured by the network side or predefined, and the embodiments of the present application do not limit this.

[0199] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that SCG1 fails. The network side allows SCG2 and MCG to report the failure information of SCG1. Since the priority of SCG2 is higher than that of MCG, based on this, the terminal can report the failure information of SCG1 through SCG2.

[0200] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that SCG1 fails. The network side allows MCG to report the failure information of SCG1, but does not allow SCG2 to report the failure information of SCG1. Based on this, the terminal can report the failure information of SCG1 through MCG.

[0201] The following describes the priority rules (2) among at least three CGs:

[0202] In some implementations, the priority rules among the respective SCGs include any one of the following, but are not limited thereto:

[0203] (1) Determine the priority of each SCG according to the identifier of each SCG;

[0204] (2) Determine the priority of each SCG according to the priority parameter of each SCG.

[0205] In some implementations, the priority rules among the respective SCGs are configured by the network side or predefined, and the embodiments of the present application do not limit this.

[0206] In some implementations, the priority parameters of the respective SCGs are configured by the network side or predefined, and the embodiments of the present application do not limit this.

[0207] For example, assume that the terminal is connected to four CGs, including: MCG, SCG1, SCG2, and SCG3, and assume that SCG1 fails. The network side allows SCG2 and SCG3 to report the failure information of SCG1. Assume that the smaller the identifier of the SCG, the higher its corresponding priority. Since the identifier of SCG2 is 2 and the identifier of SCG3 is 3, based on this, the priority of SCG2 is higher than that of SCG3. Based on this, the terminal can report the failure information of SCG1 through SCG2.

[0208] For example, assume that the terminal is connected to four CGs, including: MCG, SCG1, SCG2, and SCG3, and assume that SCG1 fails. The network side allows SCG2 and SCG3 to report the failure information of SCG1. Assume that the network side configures the priority of SCG3 to be higher than that of SCG2. Based on this, the terminal can report the failure information of SCG1 through SCG3.

[0209] The following provides an exemplary description of the reporting situation of failure information in combination with the priority rules between MCG and any SCG, as well as the priority rules between each SCG:

[0210] For example, assume that the terminal is connected to four CGs, including: MCG, SCG1, SCG2, and SCG3, and assume that SCG1 fails. The network side allows MCG, SCG2, and SCG3 to report the failure information of SCG1. Assume that the priority of any one SCG is higher than that of MCG, and the smaller the identifier of the SCG, the higher its corresponding priority. Based on this, the terminal can report the failure information of SCG1 through SCG2.

[0211] For example, assume that the terminal is connected to four CGs, including: MCG, SCG1, SCG2, and SCG3, and assume that SCG1 fails. The network side allows SCG2 and SCG3 to report the failure information of SCG1. Assume that the priority of any one SCG is higher than that of MCG, and the network side configures the priority of SCG3 to be higher than that of SCG2. Based on this, the terminal can report the failure information of SCG1 through SCG3.

[0212] The following describes the priority rule (3) between at least three CGs:

[0213] In some implementable manners, the priority parameters of at least three CGs are configured by the network side or predefined. The embodiments of the present application do not limit this.

[0214] For example, assume that the terminal is connected to four CGs, including: MCG, SCG1, SCG2, and SCG3, and assume that SCG1 fails. The network side allows SCG2 and SCG3 to report the failure information of SCG1. Assume that the network side configures the priority rule among MCG, SCG1, SCG2, and SCG3 as: SCG3 > SCG2 > SCG1 > MCG. Based on this, the terminal can report the failure information of SCG1 through SCG3.

[0215] The following describes the priority rule (3) between at least three CGs:

[0216] For example, assume that the terminal is connected to four CGs, including: MCG, SCG1, SCG2, and SCG3, and assume that SCG1 fails. The network side allows SCG2 and SCG3 to report the failure information of SCG1. Assume that the signal quality relationship among MCG, SCG1, SCG2, and SCG3 is: SCG3 > SCG2 > SCG1 > MCG. Based on this, the terminal can report the failure information of SCG1 through SCG3.

[0217] The following describes the priority rule (5) among at least three CGs:

[0218] In some implementable manners, the uplink resource is a PUSCH resource, but it is not limited thereto.

[0219] In some implementable manners, the terminal can simultaneously send the failure information of the failed CG to the lower layers of other CGs through the RRC layer. If the lower layer of another CG has an uplink resource that can transmit this failure information, it sends an indication message to the RRC layer of the terminal to indicate that it has an uplink resource for transmitting this failure information. Based on this, the terminal determines which CG's indication message is received first through the RRC layer, and determines that the priority of this CG is higher than that of other CGs.

[0220] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that SCG1 fails. The terminal simultaneously sends the failure information of SCG1 to the lower layers of the MN corresponding to MCG and SN2 corresponding to SCG 2 through the RRC layer. If the lower layer of MN or SN2 has an uplink resource that can transmit this failure information, it sends an indication message to the RRC layer of the terminal to indicate that it has an uplink resource for transmitting this failure information. Assume that the terminal first receives the indication message sent by MCG through the RRC layer, and determines that the priority of MCG is higher than that of SCG2. Based on this, the terminal can report the failure information of SCG1 through SCG2.

[0221] In some implementable manners, when the target reporting manner is the second reporting manner, the terminal can determine the second CG according to the second reporting manner and the target selection manner.

[0222] In some implementable manners, the target selection manner includes any one of the following, but is not limited thereto:

[0223] (1) Randomly select an SCG from other CGs except the first CG among the at least three CGs;

[0224] (2) Select the SCG with the highest signal quality from other CGs except the first CG among the at least three CGs;

[0225] (3) Select an SCG with available uplink resources from among the other CGs in the at least three CGs except the first CG;

[0226] (4) Select the SCG with the highest priority from among the other CGs in the at least three CGs except the first CG.

[0227] In some realizable ways, the other CGs in the at least three CGs except the first CG may be all the other CGs in the at least three CGs except the first CG.

[0228] In some realizable ways, the other CGs in the at least three CGs except the first CG may be the CGs in the at least three CGs except the first CG that meet the conditions met by the second CG above, and are also referred to as the CGs that are allowed to report failure information.

[0229] The following is an explanation of the target selection method (1):

[0230] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that SCG1 fails. The network side allows SCG2 and MCG to report the failure information of SCG1. Based on this, the terminal can randomly select one CG from MCG and SCG2 to report the failure information of SCG1.

[0231] The following is an explanation of the target selection method (2):

[0232] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that SCG1 fails. The network side allows SCG2 and MCG to report the failure information of SCG1, and the signal quality of SCG2 is higher than that of MCG. Based on this, the terminal can report the failure information of SCG1 through SCG2.

[0233] The following is an explanation of the target selection method (3):

[0234] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that SCG1 fails. The network side allows SCG2 and MCG to report the failure information of SCG1, and SCG2 has available uplink resources while MCG does not. Based on this, the terminal can report the failure information of SCG1 through SCG2.

[0235] In some realizable ways, if there are multiple CGs with available uplink resources among the other CGs in the at least three CGs except the first CG, then the terminal can randomly select one CG from these multiple CGs with available uplink resources, but is not limited to this.

[0236] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that SCG1 fails. The network side allows SCG2 and MCG to report the failure information of SCG1, and both SCG2 and MCG have available uplink resources. Based on this, the terminal can randomly select one of MCG and SCG2 to report the failure information of SCG1.

[0237] The following describes the target selection method (4):

[0238] In some implementable manners, the priorities of the other CGs except the first CG among the at least three CGs are configured by the network side or predefined, and the embodiments of the present application do not limit this.

[0239] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that MCG fails. The network side allows SCG2 and SCG1 to report the failure information of MCG, and the network side configures the priority of SCG1 to be higher than that of SCG2. Based on this, the terminal can report the failure information of MCG through SCG1.

[0240] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that MCG fails. The network side allows SCG2 and SCG1 to report the failure information of MCG, and SCG1 is configured as the default SCG, and the protocol stipulates that the priority of the default SCG is the highest. Based on this, the terminal can report the failure information of MCG through SCG1.

[0241] In some implementable manners, when the second CG is an SCG and the second CG has multiple SRBs, before the terminal reports the failure information of the first CG through the second CG, it further includes: the terminal selects at least one SRB according to the priority rules between the multiple SRBs. Based on this, the terminal can report the failure information of the first CG through at least one SRB of the second CG.

[0242] In some implementable manners, the priority rules between the multiple SRBs include at least one of the following, but are not limited thereto:

[0243] (1) The priority of the second split SRB of the second CG is higher than the priority of the third split SRB of the second CG;

[0244] (2) The priority of the second split SRB is higher than the priority of the dedicated SRB of the second CG;

[0245] (3) The priority of the third split SRB is higher than the priority of the dedicated SRB of the second CG;

[0246] Among them, the second split SRB has at least two RLC bearers, one of which corresponds to the second CG, and the PDCP bearer corresponding to the second split SRB is located in the SN corresponding to the first CG; the third split SRB has at least two RLC bearers, one of which corresponds to the second CG, and the PDCP bearer corresponding to the third split SRB is located in the MN.

[0247] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that SCG1 fails. The network side allows SCG2 to report the failure information of SCG1. Then, the priority relationship between the SRBs of SCG2 is as follows: Split SRB3 with SCG2 > Split SRB1 with SCG2 > SRB 5. Among them, Split SRB3 with SCG2 represents a split SRB of SCG2. This split SRB has at least two RLC bearers, one of which corresponds to SCG2, and the PDCP bearer corresponding to this split SRB is located in the SN1 corresponding to SCG1. Split SRB1 with SCG2 represents a split SRB of SCG2. This split SRB has at least two RLC bearers, one of which corresponds to SCG2, and the PDCP bearer corresponding to this split SRB is located in the MN corresponding to MCG. SRB 5 represents the dedicated bearer of SCG2.

[0248] In some implementable manners, when the target reporting method is the first reporting method and there are multiple second CGs, the failure information of the first CG reported by the multiple second CGs all carries the identifier corresponding to the failure information of the first CG. So that the network side can distinguish whether the multiple received failure information is the same failure information or different failure information.

[0249] In some implementable manners, when the target reporting method is the first reporting method, the terminal can report the failure information of the first CG by using the bearer combination of multiple second CGs.

[0250] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that MCG fails. Based on this, the terminal can report the failure information of the first CG through SCG1 and SCG2. The bearers of SCG1 and SCG2 are specifically as follows:

[0251] SCG1 bearer = {SRB3, split SRB 1 with SCG1};

[0252] SCG2 bearer = {SRB4, split SRB 1 with SCG2}.

[0253] split SRB 1 with SCG1 represents a split SRB of SCG1, which has at least two RLC bearers, one of which corresponds to SCG1, and the PDCP bearer corresponding to this split SRB is located in the MN corresponding to MCG.

[0254] split SRB 1 with SCG2 represents a split SRB of SCG2, which has at least two RLC bearers, one of which corresponds to SCG2, and the PDCP bearer corresponding to this split SRB is located in the MN corresponding to MCG.

[0255] There are four combinations of bearers for SCG1 and SCG2:

[0256] {SRB3, SRB4};

[0257] {SRB3, split SRB 1 with SCG2};

[0258] {split SRB 1 with SCG1, SRB4};

[0259] {split SRB 1 with SCG1, split SRB 1 with SCG2}.

[0260] In some implementable ways, when the terminal is configured with the first reporting method, the terminal uses the first reporting method as the target reporting method, but it is not limited to this.

[0261] Based on this, the network side does not need to additionally configure corresponding enabling information for each CG to indicate whether the CG can be used to report the failure information of other abnormal CGs.

[0262] In some implementable ways, when the terminal is not configured with the first reporting method, the terminal uses the second reporting method as the target reporting method, but it is not limited to this.

[0263] In some implementable ways, when the terminal is configured with the second reporting method, the terminal uses the second reporting method as the target reporting method, but it is not limited to this.

[0264] In some implementable ways, when the terminal is not configured with the second reporting method, the terminal uses the first reporting method as the target reporting method, but it is not limited to this.

[0265] In some implementable manners, when the terminal is configured with a first reporting manner and a second reporting manner, the terminal may receive indication information from the network side, and determine a target reporting manner based on the indication information, but this is not limited thereto. The indication information is used to indicate using the first reporting manner or the second reporting manner as the target reporting manner.

[0266] In some implementable manners, when the first CG is the MCG, if the terminal is configured with a terminal-level timer, when the terminal transmits failure information of the first CG, the terminal starts the terminal-level timer, and when the terminal-level timer expires, a RRC connection reestablishment process is triggered.

[0267] It should be understood that the terminal-level timer may also be started when the terminal generates failure information of the first CG. The embodiments of the present application do not limit the specific timing of the start condition of the terminal-level timer.

[0268] In some implementable manners, when the MCG transmission is restored, or when receiving a RRC reconfiguration carrying a synchronization reconfiguration or a handover command of the PCell, or when the terminal receives a RRC release message, or when initiating a RRC connection reestablishment process, the terminal-level timer stops running. The embodiments of the present application do not limit the specific timing of the stop condition of the terminal-level timer.

[0269] In some implementable manners, the terminal-level timer may be a T316 timer at the terminal level, but this is not limited thereto.

[0270] For example, in the case of a failure of the MCG, assuming that the terminal is configured with a T316 timer, no matter which SCG the terminal selects to report the failure information of the MCG, the terminal starts the T316 timer. When the T316 timer expires, the terminal triggers a RRC connection reestablishment process or initiates a RRC connection reestablishment.

[0271] In some implementable manners, when the first CG is the MCG, if the terminal is not configured with a terminal-level timer, when the first CG fails, the terminal triggers a RRC connection reestablishment process.

[0272] For example, in the case of a failure of the MCG, assuming that the terminal is not configured with a T316 timer, the terminal triggers a RRC connection reestablishment process or the terminal directly executes a RRC connection reestablishment process.

[0273] In some implementable manners, when the first CG is the MCG and the target reporting manner is the second reporting manner, if the terminal is configured with a timer associated with the second CG, when the terminal transmits failure information of the first CG, the terminal starts the timer associated with the second CG.

[0274] It should be understood that the timer associated with the second CG can also be started when the terminal generates a failure message for the first CG. The embodiments of the present application do not limit the specific timing of the start condition of the timer associated with the second CG.

[0275] In some implementable manners, when MCG transmission resumes, or when receiving an RRC reconfiguration carrying a synchronization reconfiguration or handover command for the PCell, or when the terminal receives an RRC release message, the timer associated with the second CG stops running. The embodiments of the present application do not limit the specific timing of the stop condition of this terminal-level timer.

[0276] It should be understood that the timer associated with the second CG is a CG-level timer. This CG-level timer can be a T316 timer at the CG level, but is not limited thereto. Or rather, each CG can correspond to a T316 timer.

[0277] In some implementable manners, when the timer associated with the second CG expires, the terminal triggers an RRC connection reestablishment procedure.

[0278] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that MCG fails. Assume that the terminal selects SCG1 to report the failure message of MCG. When the terminal transmits the failure message of MCG, the terminal starts the timer associated with SCG1. When this timer expires, the terminal triggers an RRC connection reestablishment procedure.

[0279] In some implementable manners, when the timer associated with the second CG expires, the terminal determines whether there are other CGs other than the second CG. If there are other CGs, the terminal reselects one CG among the other CGs and reports the failure message of the first CG through the reselected CG.

[0280] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that MCG fails. Assume that the terminal selects SCG1 to report the failure message of MCG. After the terminal generates the failure message of MCG, the terminal starts the timer associated with SCG1. When this timer expires, the terminal reselects SCG2 to report the failure message of MCG.

[0281] In some implementable manners, after the terminal reselects one CG among the other CGs, the terminal starts the timer associated with the reselected CG.

[0282] It should be understood that the embodiments of the present application do not limit the specific timing of the start condition of the timer associated with the reselected CG.

[0283] In some implementations, when MCG transmission resumes, or when an RRC reconfiguration carrying a synchronization reconfiguration or handover command for the PCell is received, or when the terminal receives an RRC release message, the timer associated with reselection of the CG stops running. Embodiments of the present application do not limit the specific timing of the stop condition of the timer associated with reselection of the CG.

[0284] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that the MCG fails. Assume that the terminal selects SCG1 to report the failure information of the MCG. When the terminal transmits the failure information of the MCG, the terminal starts a timer associated with SCG1. When this timer expires, the terminal reselects SCG2 to report the failure information of the MCG and starts a timer associated with SCG2. When this timer expires, the terminal has no available CG. In this case, the terminal triggers the RRC connection reestablishment process.

[0285] In some implementations, when the first CG is the MCG and the target reporting method is the first reporting method, when the terminal transmits the failure information of the first CG, the terminal starts timers corresponding to each of the other part or all of the CGs among the at least three CGs except the first CG; the terminal determines whether to trigger the RRC connection reestablishment process according to the timers corresponding to each of the other part or all of the CGs.

[0286] In some implementations, the timers corresponding to each of the other part or all of the CGs among the at least three CGs except the first CG may also be started when the terminal generates the failure information of the first CG. Embodiments of the present application do not limit the specific timing of the start condition of these timers.

[0287] In some implementations, for any one of the other part or all of the CGs among the at least three CGs except the first CG, when MCG transmission resumes, or when an RRC reconfiguration carrying a synchronization reconfiguration or handover command for the PCell is received, or when the terminal receives an RRC release message, the timer associated with this CG stops running. Embodiments of the present application do not limit the specific timing of the stop condition of these timers.

[0288] It should be understood that for any one of the other part or all of the CGs among the at least three CGs except the first CG, the timer corresponding to this CG is also referred to as the timer associated with this CG. Among them, the timer associated with this CG is a CG-level timer, and this CG-level timer may be a T316 timer at the CG level, but is not limited thereto. Or rather, each CG may correspond to a T316 timer.

[0289] In some implementable manners, among at least three CGs, other partial CGs except the first CG may be CGs that meet the above-mentioned target conditions among at least three CGs except the first CG, and are also referred to as CGs that are allowed to report failure information.

[0290] In some implementable manners, the terminal determines whether to trigger the RRC connection reestablishment process according to timers respectively corresponding to other partial or all CGs, including: the terminal determines whether to trigger the RRC connection reestablishment process according to the longest duration of timers respectively corresponding to other partial or all CGs.

[0291] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that MCG fails. Assume that the terminal selects SCG1 and SCG2 to report the failure information of MCG simultaneously. When the terminal transmits the failure information of MCG, the terminal starts a timer associated with SCG1 and a timer associated with SCG2. Assume that the duration of the timer associated with SCG1 is 5 ms, and the duration of the timer associated with SCG2 is 10 ms. Then when the timer associated with SCG2 exceeds 10 ms, the terminal triggers the RRC connection reestablishment process.

[0292] In some implementable manners, if there is no CG that meets the target conditions among at least three CGs, the terminal triggers the RRC connection reestablishment process.

[0293] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that MCG fails. Assume that the transmission of SCG1 is in a suspended state and SCG2 is in a deactivated state. Then the terminal triggers the RRC connection reestablishment process.

[0294] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1, and SCG2, and assume that MCG fails. Assume that the transmissions of both SCG1 and SCG2 are in suspended states. Then the terminal triggers the RRC connection reestablishment process.

[0295] An embodiment of the present application provides a wireless communication method. The terminal is configured with at least three CGs. The method includes: when the first CG among at least three CGs fails, the terminal determines a second CG according to a target reporting manner; the terminal reports the failure information of the first CG through the second CG; where the target reporting manner includes any one of the following: the first reporting manner: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs; the second reporting manner: reporting the failure information of the first CG through one CG among all other CGs except the first CG among at least three CGs. That is, a method for the terminal to report CG failure information in a multi-connection scenario is provided to quickly recover an abnormal link.

[0296] The wireless communication method provided by an embodiment of the present application may be executed by a wireless communication device. In the embodiments of the present application, taking the wireless communication device executing the wireless communication method as an example, the wireless communication device provided by the embodiments of the present application is described.

[0297] Figure 9 FIG. is a schematic diagram of a wireless communication device 900 provided by an embodiment of the present application. As Figure 9 described, the wireless communication device 900 is configured with at least three CGs. The wireless communication device 900 includes:

[0298] A processing module 910, configured to determine a second CG according to a target reporting method when a failure occurs in a first CG among at least three CGs;

[0299] A communication module 920, configured to report the failure information of the first CG through the second CG;

[0300] Wherein, the target reporting method includes any one of the following:

[0301] The first reporting method: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0302] The second reporting method: reporting the failure information of the first CG through one CG among all other CGs except the first CG among at least three CGs.

[0303] In some implementable manners, the processing module 910 is specifically configured to: determine the second CG according to the target reporting method and a target condition;

[0304] Wherein, the second CG satisfies the target condition, and the target condition includes at least one of the following:

[0305] The transmission is not in a suspended state;

[0306] Is in an active state;

[0307] Has an SRB;

[0308] Is configured or allowed to report the failure information of the first CG.

[0309] In some implementable manners, the second CG having an SRB includes at least one of the following:

[0310] The second CG has a dedicated SRB;

[0311] The second CG has a first split SRB;

[0312] Wherein, the first split SRB has at least two RLC bearers, and one of the RLC bearers corresponds to the second CG.

[0313] In some implementations, the PDCP entity corresponding to the first split SRB is located in the MN or the SN corresponding to the first CG.

[0314] In some implementations, the communication module 920 is further configured to receive first indication information.

[0315] Wherein, the second CG is configured or permitted to report the failure information of the first CG, including:

[0316] The first indication information indicates that the second CG can report the failure information of the first CG; or,

[0317] The first indication information indicates one or more CGs capable of reporting failure information, wherein the one or more CGs include the identifier of the second CG.

[0318] In some implementations, the situations where the first CG fails include at least one of the following:

[0319] Radio link failure of the first CG;

[0320] Synchronization reconfiguration failure of the first CG;

[0321] Configuration failure of the first CG;

[0322] Integrity check failure of the SRB corresponding to the first CG.

[0323] In some implementations, the processing module 910 is further configured to use the first reporting method as the target reporting method when the wireless communication device is configured with the first reporting method.

[0324] In some implementations, the processing module 910 is further configured to use the second reporting method as the target reporting method when the wireless communication device is not configured with the first reporting method.

[0325] In some implementations, when the target reporting method is the second reporting method, the processing module 910 is specifically configured to: determine the second CG according to the second reporting method and the priority rule among at least three CGs.

[0326] In some implementations, the priority rule among at least three CGs includes any one of the following:

[0327] The priority rule between the MCG and any SCG;

[0328] The priority rule among the respective SCGs;

[0329] Determine the priority of at least three CGs according to the priority parameters of at least three CGs;

[0330] Among at least three CGs, the higher the signal quality of a CG, the higher its corresponding priority;

[0331] Among at least three CGs, the earlier the uplink resource acquisition time of a CG, the higher its corresponding priority.

[0332] In some implementable manners, the priority rules between the MCG and any SCG or the priority rules between each SCG are configured or predefined by the network side.

[0333] In some implementable manners, the priority rules between each SCG include any one of the following:

[0334] Determine the priority of each SCG according to the identifier of each SCG;

[0335] Determine the priority of each SCG according to the priority parameter of each SCG.

[0336] In some implementable manners, when the target reporting mode is the first reporting mode and there are multiple second CGs, the failure information of the first CG reported by the multiple second CGs all carries the identifier corresponding to the failure information of the first CG.

[0337] In some implementable manners, when the second CG is an SCG and the second CG has multiple SRBs, the processing module 910 is further configured to: select at least one SRB according to the priority rules between the multiple SRBs.

[0338] In some implementable manners, the priority rules between the multiple SRBs include at least one of the following:

[0339] The priority of the second split SRB of the second CG is higher than the priority of the third split SRB of the second CG;

[0340] The priority of the second split SRB is higher than the priority of the dedicated SRB of the second CG;

[0341] The priority of the third split SRB is higher than the priority of the dedicated SRB of the second CG;

[0342] Wherein, the second split SRB has at least two RLC bearers, one of the RLC bearers corresponds to the second CG, and the PDCP bearer corresponding to the second split SRB is located in the SN corresponding to the first CG;

[0343] The third split SRB has at least two RLC bearers, one of the RLC bearers corresponds to the second CG, and the PDCP bearer corresponding to the third split SRB is located in the MN.

[0344] In some implementable manners, when the first CG is the MCG, the processing module 910 is further configured to: if the wireless communication device is configured with a terminal-level timer, start the terminal-level timer when the wireless communication device transmits the failure information of the first CG, and trigger an RRC connection reestablishment procedure when the terminal-level timer expires.

[0345] In some implementable manners, when the first CG is the MCG and the target reporting manner is the second reporting manner, the processing module 910 is further configured to: if the wireless communication device is configured with a timer associated with the second CG, start the timer associated with the second CG when the wireless communication device transmits the failure information of the first CG.

[0346] In some implementable manners, when the timer associated with the second CG expires, the processing module 910 is further configured to trigger an RRC connection reestablishment procedure, or, when the timer associated with the second CG expires, the processing module 910 is further configured to: determine whether there are other CGs in addition to the second CG, and if there are other CGs, reselect a CG from the other CGs and report the failure information of the first CG through the reselected CG.

[0347] In some implementable manners, the processing module 910 is further configured to: after reselecting a CG from the other CGs, start the timer associated with the reselected CG.

[0348] In some implementable manners, when the first CG is the MCG and the target reporting manner is the first reporting manner, the processing module 910 is further configured to: when the wireless communication device transmits the failure information of the first CG, start the timers respectively corresponding to the other part or all of the CGs except the first CG among at least three CGs; determine whether to trigger an RRC connection reestablishment procedure according to the timers respectively corresponding to the other part or all of the CGs.

[0349] In some implementable manners, the processing module 910 is further configured to: if there is no CG that meets the target condition among at least three CGs, trigger an RRC connection reestablishment procedure.

[0350] The wireless communication device in the embodiments of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal or other devices other than the terminal. Exemplarily, the terminal may include, but is not limited to, the types of the terminal 11 listed above, and other devices may be a server, a Network Attached Storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0351] The wireless communication device provided by the embodiments of the present application can implement Figure 4In the method embodiments shown, the various processes implemented by the terminal achieve the same technical effects. To avoid repetition, they will not be elaborated here.

[0352] Figure 10 FIG. is a schematic diagram of a wireless communication device 1000 provided by an embodiment of the present application. The wireless communication device 1000 includes:

[0353] A communication module 1010, configured to receive failure information of a first cell group (CG) reported by a terminal through a second CG;

[0354] Wherein, the terminal is configured with at least three cell groups (CGs), the first CG is the CG that fails among the at least three CGs, and the second CG is determined by the terminal according to a target reporting method;

[0355] The target reporting method includes any one of the following:

[0356] The first reporting method: reporting the failure information of the first CG through all other CGs except the first CG among the at least three CGs;

[0357] The second reporting method: reporting the failure information of the first CG through one CG among all other CGs except the first CG among the at least three CGs.

[0358] In some implementable manners, the second CG is determined by the terminal according to the target reporting method and a target condition;

[0359] Wherein, the second CG meets the target condition, and the target condition includes at least one of the following:

[0360] The transmission is not in a suspended state;

[0361] It is in an active state;

[0362] It has a signaling radio bearer (SRB);

[0363] It is configured or permitted to report the failure information of the first CG.

[0364] In some implementable manners, the second CG having an SRB includes at least one of the following:

[0365] The second CG has a dedicated SRB;

[0366] The second CG has a first split SRB;

[0367] Wherein, the first split SRB has at least two radio link control (RLC) bearers, and one of the RLC bearers corresponds to the second CG.

[0368] In some implementable manners, the packet data convergence protocol (PDCP) entity corresponding to the first split SRB is located in the master node (MN) or the serving network (SN) corresponding to the first CG.

[0369] In some implementable manners, the communication module 1010 is further configured to send first indication information.

[0370] Wherein, the second CG is configured or permitted to report the failure information of the first CG, including:

[0371] The first indication information indicates that the second CG can report the failure information of the first CG; or,

[0372] The first indication information indicates one or more CGs that can report the failure information, wherein the one or more CGs include the identifier of the second CG.

[0373] In some implementable manners, the situations where the first CG fails include at least one of the following:

[0374] Radio link failure of the first CG;

[0375] Synchronization reconfiguration failure of the first CG;

[0376] Configuration failure of the first CG;

[0377] Integrity detection failure of the SRB corresponding to the first CG.

[0378] In some implementable manners, when the target reporting manner is the second reporting manner, the second CG is determined by the terminal according to the target reporting manner and the priority rule among at least three CGs.

[0379] In some implementable manners, the priority rule among at least three CGs includes any one of the following:

[0380] The priority rule between the MCG and any SCG;

[0381] The priority rule among each SCG;

[0382] Determine the priority of at least three CGs according to the priority parameters of at least three CGs;

[0383] Among at least three CGs, the higher the signal quality of a CG, the higher its corresponding priority;

[0384] Among at least three CGs, the earlier the uplink resource acquisition time of a CG, the higher its corresponding priority.

[0385] In some implementable manners, the priority rule between the MCG and any SCG or the priority rule among each SCG is configured by the network side or predefined.

[0386] In some implementable manners, the priority rule among each SCG includes any one of the following:

[0387] Determine the priority of each SCG according to the identifier of each SCG;

[0388] Determine the priorities of each SCG according to the priority parameters of each SCG.

[0389] In some implementable manners, when the target reporting manner is the first reporting manner and there are multiple second CGs, the failure information of the first CG reported by the multiple second CGs all carries an identifier corresponding to the failure information of the first CG.

[0390] In some implementable manners, when the second CG is an SCG and the second CG has multiple SRBs, the priority rules among the multiple SRBs are used to select at least one SRB.

[0391] In some implementable manners, the priority rules among the multiple SRBs include at least one of the following:

[0392] The priority of the second split SRB of the second CG is higher than the priority of the third split SRB of the second CG;

[0393] The priority of the second split SRB is higher than the priority of the dedicated SRB of the second CG;

[0394] The priority of the third split SRB is higher than the priority of the dedicated SRB of the second CG;

[0395] Among them, the second split SRB has at least two RLC bearers, one of the RLC bearers corresponds to the second CG, and the PDCP bearer corresponding to the second split SRB is located in the SN corresponding to the first CG;

[0396] The third split SRB has at least two RLC bearers, one of the RLC bearers corresponds to the second CG, and the PDCP bearer corresponding to the third split SRB is located in the MN.

[0397] The wireless communication device in the embodiments of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a network device or other devices other than network devices. Exemplarily, the network device may include, but is not limited to, the above-listed first network device, second network device, and third network device, and other devices may be servers, NAS, etc., which are not specifically limited in the embodiments of the present application.

[0398] The wireless communication device provided by the embodiments of the present application can implement Figure 4 each process implemented by the network device in the method embodiment shown, and achieve the same technical effects. To avoid repetition, details are not described here again.

[0399] Figure 11 It is a schematic block diagram of a communication device provided by the embodiments of the present application; asFigure 11 As shown in the figure, an embodiment of the present application further provides a communication device 1100, including a processor 1101 and a memory 1102. A program or instruction that can run on the processor 1101 is stored on the memory 1102. For example, when the communication device 1100 is a terminal, when the program or instruction is executed by the processor 1101, it implements the above-mentioned Figure 4 each step executed by the terminal in the method embodiment shown, and can achieve the same technical effect. When the communication device 1100 is a network device, when the program or instruction is executed by the processor 1101, it implements the above-mentioned Figure 4 each step executed by the network device in the method embodiment shown, and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0400] An embodiment of the present application further provides a terminal, including a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run a program or instruction to implement the above-mentioned Figure 4 each step executed by the terminal in the method embodiment shown. This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment. Each implementation process and implementation manner of the above method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect. Specifically, Figure 12 It is a schematic hardware structure diagram of a terminal for implementing an embodiment of the present application.

[0401] The terminal 1200 includes, but is not limited to, at least some components such as a radio frequency unit 1201, a network module 1202, an audio output unit 1203, an input unit 1204, a sensor 1205, a display unit 1206, a user input unit 1207, an interface unit 1208, a memory 1209, and a processor 1210.

[0402] Those skilled in the art can understand that the terminal 1200 may further include a power source (such as a battery) for supplying power to each component. The power source can be logically connected to the processor 1210 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. Figure 12 The terminal structure shown in the figure does not limit the terminal. The terminal may include more or fewer components than shown in the figure, or combine some components, or have different component arrangements, which will not be elaborated here.

[0403] It should be understood that in the embodiments of the present application, the input unit 1204 may include a Graphics Processing Unit (GPU) 12041 and a microphone 12042. The GPU 12041 processes the image data of static pictures or videos obtained by an image capturing device (such as a camera) in the video capturing mode or the image capturing mode. The display unit 1206 may include a display panel 12061, and the display panel 12061 may be configured in the form of, for example, a liquid crystal display, an organic light emitting diode, etc. The user input unit 1207 includes at least one of a touch panel 12071 and other input devices 12072. The touch panel 12071 is also referred to as a touch screen. The touch panel 12071 may include two parts: a touch detection device and a touch controller. The other input devices 12072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be elaborated herein.

[0404] In the embodiments of the present application, after receiving downlink data from a network device, the radio frequency unit 1201 may transmit it to the processor 1210 for processing; in addition, the radio frequency unit 1201 may send uplink data to the network device. Generally, the radio frequency unit 1201 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0405] The memory 1209 can be used to store software programs or instructions as well as various data. The memory 1209 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data. Among them, the first storage area may store an operating system, application programs or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1209 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct rambus random access memory (DRRAM). The memory 1209 in the embodiments of the present application includes but is not limited to these and any other suitable types of memories.

[0406] The processor 1210 may include one or more processing units; optionally, the processor 1210 integrates an application processor and a modem processor. Among them, the application processor mainly processes operations related to the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above modem processor may not be integrated into the processor 1210.

[0407] Among them, the processor 1210 is used for: when the first CG among at least three CGs fails, the terminal determines the second CG according to the target reporting method;

[0408] The radio frequency unit 1201 is used to report the failure information of the first CG through the second CG;

[0409] Among them, the target reporting method includes any one of the following:

[0410] The first reporting method: report the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0411] The second reporting method: report the failure information of the first CG through one CG among all other CGs except the first CG among at least three CGs.

[0412] It can be understood that the implementation processes of the various implementation manners mentioned in this embodiment can refer to the relevant descriptions of the corresponding method embodiments on the terminal side and achieve the same or corresponding technical effects. To avoid repetition, they will not be elaborated here.

[0413] The embodiment of the present application further provides a network device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement Figure 4 each process implemented by the network device in the method embodiment shown. This network device embodiment corresponds to the method embodiment executed by the above network device. Each implementation process and implementation manner of the above method embodiment can be applied to this network device embodiment and can achieve the same technical effect.

[0414] Specifically, the embodiment of the present application further provides a network device. As Figure 13 shown, the network device 1300 includes: an antenna 131, a radio frequency device 132, a baseband device 133, a processor 134, and a memory 135. The antenna 131 is connected to the radio frequency device 132. In the uplink direction, the radio frequency device 132 receives information through the antenna 131 and sends the received information to the baseband device 133 for processing. In the downlink direction, the baseband device 133 processes the information to be sent and sends it to the radio frequency device 132. The radio frequency device 132 processes the received information and then sends it out through the antenna 131.

[0415] The method executed by the network device in the above embodiments can be implemented in the baseband device 133, and the baseband device 133 includes a baseband processor.

[0416] The baseband device 133 may include, for example, at least one baseband board, and multiple chips are provided on the baseband board. As Figure 13 shown, one of the chips is, for example, a baseband processor, which is connected to the memory 135 through a bus interface to call the program in the memory 135 and execute the operations of the network device shown in the above method embodiments.

[0417] The network device may further include a network interface 136, and this interface is, for example, a Common Public Radio Interface (CPRI).

[0418] Specifically, the network device 1300 according to an embodiment of the present invention further includes instructions or programs stored in the memory 135 and executable on the processor 134. The processor 134 invokes the instructions or programs in the memory 135 to execute Figure 4 the steps performed by the network device in the method embodiment shown, and achieves the same technical effects. To avoid repetition, they will not be elaborated here.

[0419] An embodiment of the present application further provides a readable storage medium, on which a program or instructions are stored. When the program or instructions are executed by a processor, the various processes of the method embodiment shown above are implemented Figure 4 and the same technical effects can be achieved. To avoid repetition, they will not be elaborated here.

[0420] Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes computer-readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disks or optical discs, etc. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0421] Another embodiment of the present application provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor is configured to run a program or instructions to implement the various processes of the method embodiment shown above Figure 4 and the same technical effects can be achieved. To avoid repetition, they will not be elaborated here.

[0422] It should be understood that the chip mentioned in the embodiment of the present application may also be referred to as a system-on-chip, system chip, chip system, or system-on-chip, etc.

[0423] Another embodiment of the present application provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the method embodiment shown above Figure 4 and the same technical effects can be achieved. To avoid repetition, they will not be elaborated here.

[0424] An embodiment of the present application further provides a wireless communication system, including: a terminal and a network device. The terminal can be used to execute the various processes corresponding to the target terminal in the method embodiment described above Figure 4 and the network device can be used to execute the various processes corresponding to the network device in the method embodiment described above. Figure 4 shown in the method embodiment.

[0425] It should be noted that, in this text, the term "comprising", "including" or any other variation thereof is intended to cover non-exclusive inclusion, such that a process, method, article or apparatus comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or apparatus. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising that element. In addition, it should be pointed out that the methods and apparatuses in the embodiments of the present application are not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in a reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0426] From the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions for causing a terminal or a network device to execute the methods described in the various embodiments of the present application.

[0427] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms of embodiments without departing from the purpose of the present application and the scope protected by the claims. These embodiments are all within the protection scope of the present application.

Claims

1. A wireless communication method, characterized in that The terminal is configured with at least three cell groups CG, and the method includes: When a failure occurs in a first CG among the at least three CGs, the terminal determines a second CG according to a target reporting manner; The terminal reports the failure information of the first CG through the second CG; Wherein, the target reporting manner includes any one of the following: The first reporting manner: reporting the failure information of the first CG through all other CGs among the at least three CGs except the first CG; The second reporting manner: reporting the failure information of the first CG through one CG among all other CGs among the at least three CGs except the first CG.

2. The method according to claim 1, wherein The terminal determines the second CG according to the target reporting manner, including: The terminal determines the second CG according to the target reporting manner and a target condition; Wherein, the second CG meets the target condition, and the target condition includes at least one of the following: The transmission is not in a suspended state; It is in an active state; It has a signaling radio bearer SRB; It is configured or allowed to report the failure information of the first CG.

3. The method according to claim 2, wherein The second CG having an SRB includes at least one of the following: The second CG has a dedicated SRB; The second CG has a first split SRB; Wherein, the first split SRB has at least two radio link control RLC bearers, and one RLC bearer corresponds to the second CG.

4. The method according to claim 3, wherein The PDCP entity corresponding to the first split SRB is located in the master node MN or the secondary node SN corresponding to the first CG.

5. The method according to any one of claims 2 - 4, characterized in that It further includes: The terminal receives first indication information; Wherein, the second CG being configured or allowed to report the failure information of the first CG includes: The first indication information indicates that the second CG can report the failure information of the first CG; or, The first indication information indicates one or more CGs capable of reporting failure information, wherein the one or more CGs include the identifier of the second CG.

6. The method according to any one of claims 1-5, characterized in that, The situation where the first CG fails includes at least one of the following: The radio link failure of the first CG; The synchronization reconfiguration failure of the first CG; The configuration failure of the first CG; The integrity detection failure of the SRB corresponding to the first CG.

7. The method according to any one of claims 1-6, characterized in that, It further includes: When the terminal is configured with the first reporting manner, the terminal uses the first reporting manner as the target reporting manner.

8. The method according to any one of claims 1 to 6, characterized in that It further includes: When the terminal is not configured with the first reporting manner, the terminal uses the second reporting manner as the target reporting manner.

9. The method according to any one of claims 1 to 8, characterized in that, When the target reporting manner is the second reporting manner, the terminal determines the second CG according to the target reporting manner, including: The terminal determines the second CG according to the second reporting manner and the priority rule among the at least three CGs.

10. The method according to claim 9, wherein The priority rule among the at least three CGs includes any one of the following: The priority rule between MCG and any SCG; The priority rule among each SCG; Determining the priority of the at least three CGs according to the priority parameters of the at least three CGs; Among the at least three CGs, the higher the signal quality of a CG, the higher its corresponding priority. Among the at least three CGs, the earlier the uplink resource acquisition time of a CG, the higher its corresponding priority.

11. The method according to claim 10, wherein The priority rule between the MCG and any SCG or the priority rules between the respective SCGs are configured by the network side or predefined.

12. The method according to claim 10 or 11, characterized in that, The priority rules between the respective SCGs include any of the following: Determine the priorities of the respective SCGs according to the identifiers of the respective SCGs. Determine the priorities of the respective SCGs according to the priority parameters of the respective SCGs.

13. The method according to any one of claims 1-8, characterized in that, When the target reporting mode is the first reporting mode and there are multiple second CGs, the failure information of the first CG reported by the multiple second CGs all carries the identifier corresponding to the failure information of the first CG.

14. The method according to any one of claims 1-13, characterized in that, When the second CG is an SCG and the second CG has multiple SRBs, before the terminal reports the failure information of the first CG through the second CG, it further includes: The terminal selects at least one SRB according to the priority rule between the multiple SRBs.

15. The method according to claim 14, wherein The priority rule between the multiple SRBs includes at least one of the following: The priority of the second split SRB of the second CG is higher than the priority of the third split SRB of the second CG. The priority of the second split SRB is higher than the priority of the dedicated SRB of the second CG. The priority of the third split SRB is higher than the priority of the dedicated SRB of the second CG. Among them, the second split SRB has at least two RLC bearers, one of the RLC bearers corresponds to the second CG, and the PDCP bearer corresponding to the second split SRB is located in the SN corresponding to the first CG. The third split SRB has at least two RLC bearers, one of the RLC bearers corresponds to the second CG, and the PDCP bearer corresponding to the third split SRB is located in the MN.

16. The method according to any one of claims 1 to 13, characterized in that, When the first CG is an MCG, the method further includes: If the terminal is configured with a terminal-level timer, when the terminal transmits the failure information of the first CG, the terminal starts the terminal-level timer, and when the terminal-level timer expires, triggers a radio resource control (RRC) connection reestablishment process.

17. The method according to any one of claims 1 to 12, characterized in that When the first CG is an MCG and the target reporting mode is the second reporting mode, the method further includes: If the terminal is configured with a timer associated with the second CG, when the terminal transmits the failure information of the first CG, the terminal starts the timer associated with the second CG.

18. The method according to claim 17, wherein It further includes: When the timer associated with the second CG expires, the terminal triggers an RRC connection reestablishment process, or, When the timer associated with the second CG expires, the terminal determines whether there are other CGs in addition to the second CG. If there are other CGs, the terminal reselects a CG among the other CGs and reports the failure information of the first CG through the reselected CG.

19. The method according to claim 18, characterized in that, After the terminal reselects a cell group (CG) among other CGs, the method further includes: The terminal starts a timer associated with the reselected CG.

20. The method according to any one of claims 1 - 8, 13, characterized in that, When the first CG is a master cell group (MCG) and the target reporting mode is the first reporting mode, the method further includes: When the terminal transmits failure information of the first CG, the terminal starts timers corresponding to each of the other part or all of the CGs among the at least three CGs except the first CG; The terminal determines whether to trigger an RRC connection reestablishment process according to the timers corresponding to each of the other part or all of the CGs.

21. The method according to claim 2, wherein Further includes: If there is no CG that meets the target condition among the at least three CGs, the terminal triggers an RRC connection reestablishment process.

22. A wireless communication method, characterized in that, Includes: The network device receives failure information of the first CG reported by the terminal through a second CG; Wherein, the terminal is configured with at least three cell groups (CGs), the first CG is the CG that fails among the at least three CGs, and the second CG is determined by the terminal according to the target reporting mode; The target reporting mode includes any one of the following: First reporting mode: Reporting failure information of the first CG through all the other CGs among the at least three CGs except the first CG; Second reporting mode: Reporting failure information of the first CG through one CG among all the other CGs among the at least three CGs except the first CG.

23. The method according to claim 22, wherein The second CG is determined by the terminal according to the target reporting mode and the target condition; Wherein, the second CG meets the target condition, and the target condition includes at least one of the following: The transmission is not in a suspended state; Is in an active state; Has a signaling radio bearer (SRB); Is configured or allowed to report failure information of the first CG.

24. The method according to claim 23, wherein The second CG having an SRB includes at least one of the following: The second CG has a dedicated SRB; The second CG has a first split SRB; Wherein, the first split SRB has at least two radio link control (RLC) bearers, and one of the RLC bearers corresponds to the second CG.

25. The method according to claim 24, wherein The packet data convergence protocol (PDCP) entity corresponding to the first split SRB is located in the master node (MN) or the secondary node (SN) corresponding to the first CG.

26. The method according to any one of claims 23 - 25, characterized in that Further includes: The network device sends first indication information; Wherein, the second CG being configured or allowed to report failure information of the first CG includes: The first indication information indicates that the second CG can report failure information of the first CG; or, The first indication information indicates one or more CGs that can report failure information, and the one or more CGs include the identifier of the second CG.

27. The method according to any one of claims 22-26, characterized in that, The situation where the first CG fails includes at least one of the following: Radio link failure of the first CG; Synchronization reconfiguration failure of the first CG; Configuration failure of the first CG; Integrity check failure of the SRB corresponding to the first CG.

28. The method according to any one of claims 22-27, characterized in that, When the target reporting mode is the second reporting mode, the second CG is determined by the terminal according to the target reporting mode and the priority rule among the at least three CGs.

29. The method according to claim 28, wherein The priority rule among the at least three CGs includes any one of the following: Priority rules between the MCG and any SCG; Priority rules between each SCG; Determine the priority of the at least three CGs according to the priority parameters of the at least three CGs; Among the at least three CGs, the higher the signal quality of a CG, the higher its corresponding priority; Among the at least three CGs, the earlier the uplink resource acquisition time of a CG, the higher its corresponding priority.

30. The method according to claim 29, characterized in that, The priority rules between the MCG and the any SCG or the priority rules between each SCG are configured by the network side or predefined.

31. The method according to claim 29 or 30, characterized in that, The priority rules between each SCG include any of the following: Determine the priority of each SCG according to the identifier of each SCG; Determine the priority of each SCG according to the priority parameters of each SCG.

32. The method according to any one of claims 22 - 27, characterized in that When the target reporting method is the first reporting method and there are multiple second CGs, the failure information of the first CG reported by the multiple second CGs all carries the identifier corresponding to the failure information of the first CG.

33. The method according to any one of claims 22-32, characterized in that, When the second CG is an SCG and the second CG has multiple SRBs, the priority rules between the multiple SRBs are used to select at least one SRB.

34. The method according to claim 33, wherein The priority rules between the multiple SRBs include at least one of the following: The priority of the second split SRB of the second CG is higher than the priority of the third split SRB of the second CG; The priority of the second split SRB is higher than the priority of the dedicated SRB of the second CG; The priority of the third split SRB is higher than the priority of the dedicated SRB of the second CG; Wherein, the second split SRB has at least two RLC bearers, one of the RLC bearers corresponds to the second CG, and the PDCP bearer corresponding to the second split SRB is located in the SN corresponding to the first CG; The third split SRB has at least two RLC bearers, one of the RLC bearers corresponds to the second CG, and the PDCP bearer corresponding to the third split SRB is located in the MN.

35. A wireless communication device, characterized in that, The device is configured with at least three CGs, and the device includes: A processing module, configured to determine a second CG according to a target reporting method when a first CG among the at least three CGs fails; A communication module, configured to report the failure information of the first CG through the second CG; Wherein, the target reporting method includes any of the following: The first reporting method: Report the failure information of the first CG through all other CGs among the at least three CGs except the first CG; The second reporting method: Report the failure information of the first CG through one CG among all other CGs except the first CG among the at least three CGs.

36. A wireless communication device, characterized in that, Includes: A communication module, configured to receive the failure information of the first CG reported by the terminal through the second CG; Wherein, the terminal is configured with at least three cell groups CGs, the first CG is the CG that fails among the at least three CGs, and the second CG is determined by the terminal according to the target reporting method; The target reporting method includes any of the following: The first reporting method: reporting the failure information of the first CG through all the other CGs among the at least three CGs except the first CG; The second reporting method: reporting the failure information of the first CG through one CG among all the other CGs among the at least three CGs except the first CG.

37. A terminal, characterized in that, It includes a processor and a memory, and the memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the wireless communication method according to any one of claims 1 to 21 are implemented.

38. A network device, characterized in that, It includes a processor and a memory, and the memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the wireless communication method according to any one of claims 22 to 34 are implemented.

39. A readable storage medium, characterized in that, A program or instruction is stored on the readable storage medium. When the program or instruction is executed by a processor, the wireless communication method according to any one of claims 1 to 21 is implemented, or the steps of the wireless communication method according to any one of claims 22 to 34 are implemented.

Images