Communication method and device

Abstract

The invention relates to a communication method and device. The method comprises the following steps that: terminal equipment establishes RRC (Radio Resource Control) connection with first access network equipment; when the RRC connection fails, the first access network equipment can record first information of the RRC connection failure and send the first information to the terminal equipment; wherein the first information can assist the terminal equipment or a server corresponding to the terminal equipment in accurately positioning the problem of RRC failure, and further, communication between the terminal equipment and the first access network equipment is optimized.

Description

TECHNICAL FIELD

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

[0002] In a wireless communication system, a terminal device and a first access network device can establish an RRC connection; the terminal device and the first access network device can transmit control signaling and / or data information by using the RRC connection. At present, some phenomena may cause the RRC connection to fail, for example, RRC connection release. How the terminal device side acquires the related information of the RRC connection failure recorded by the network side to assist the terminal device side in locating the problem of the RRC connection failure is a research direction. SUMMARY

[0003] Embodiments of the present application provide a communication method and device, so that the terminal device can acquire the first information related to the RRC connection failure recorded by the network side, thereby assisting the terminal device in locating the problem of the RRC connection failure.

[0004] In a first aspect, a communication method is provided. The execution subject of the method is a terminal device, or a module, unit or component (for example, a chip, a chip system, a circuit, a processor, or other etc.) applied in the terminal device, and the method comprises: establishing a radio resource control (RRC) connection with a first access network device; and receiving first information from the first access network device or a second access network device, the first information being information of an RRC connection failure, and the first information comprising: a type of the RRC connection failure, and / or a cause of the RRC connection failure.

[0005] Through the above design, the network side can record the first information related to the RRC connection failure and send it to the terminal device to assist the terminal device in accurately locating the problem of the RRC connection failure, thereby quickly and efficiently solving the problem of the RRC connection failure and optimizing the performance of the terminal device in the network.

[0006] In a possible implementation manner, the type of the RRC connection failure comprises: the RRC connection failure being an abnormal RRC connection failure; or the RRC connection failure being a non-abnormal RRC connection failure.

[0007] Through the above design, the first access network device records the type of the RRC connection failure and sends it to the terminal device; and the terminal device can determine whether the RRC connection failure is caused by an abnormality or a non-abnormality according to the type of the RRC connection failure. If the RRC connection failure is caused by a non-abnormality, the terminal device side does not need to blindly perform retesting and problem locating, thereby saving the power consumption of the terminal device.

[0008] In one possible implementation, the reason for the RRC connection failure includes at least one of the following: the first access network device's radio link fails (RLF); the first access network device experiences network congestion; the first access network device is unable to correctly decode the uplink signaling of the terminal device; the first access network device does not receive a Protocol Data Unit (PDU) session resource establishment request sent by the core network device; or, the first access network device fails to configure the RRC for the terminal device.

[0009] Through the above design, the first access network device records the reason for the RRC connection failure and sends the reason for the RRC connection failure to the terminal device; the terminal device can locate the problem of the RRC connection failure based on the reason for the RRC connection failure and quickly and efficiently resolve the problem that caused the RRC connection failure.

[0010] In one possible implementation, the RRC connection failure is a failure of the first access network device to configure the RRC of the terminal device. The first information includes at least one of the following indication information: the version or index of the capability information of the terminal device, a first frequency band combination, or a first RRC configuration. The first frequency band combination is included in the capability information of the terminal device, and the RRC configuration is an incremental configuration based on the first RRC configuration.

[0011] In one possible implementation, the first information further includes: indication information that the RRC connection failure is related to the network side and / or the terminal device side. For example, this indication information is a first indication information used to indicate that the RRC connection failure is related to the network side. In one understanding, "the RRC connection failure is related to the network side" can be understood as: the RRC connection failure is caused by a network-side issue, or the problem causing the RRC connection failure only involves the network side and not the terminal device side, or the problem causing the RRC connection failure does not involve the interoperability between the terminal device side and the network side. Alternatively, a second indication information is used to indicate that the RRC connection failure is related to the terminal device side. In one understanding, "the RRC connection failure is related to the terminal device side" can be understood as: the RRC connection failure is caused by a terminal device side issue, or the problem causing the RRC connection failure only involves the terminal device side and not the network side, or the problem causing the RRC connection failure does not involve the interoperability between the terminal device side and the network side. Alternatively, a third indication information is used to indicate that the RRC connection failure is related to both the terminal device side and the network side. In one understanding, an RRC connection failure related to both the terminal device and the network can be interpreted as: the RRC connection failure is caused by a common reason on both the terminal device and the network side; or the problem causing the RRC connection failure involves both the terminal device and the network side; or the problem causing the RRC connection failure involves inter-operability between the terminal device and the network side.

[0012] Through the above design, the first access network device records the cause of the RRC connection failure as being on the network side and / or the terminal device side, and sends the recorded relevant information to the terminal device side. Based on the above information, the terminal device side can determine whether the RRC connection failure is caused by a problem on the terminal device side, a problem on the network side, or a problem caused by both the terminal device side and the network side, thus enabling the terminal device side to perform targeted optimizations. For example, if the RRC connection failure is caused by a problem on the network side alone, the terminal device side does not need to blindly retest and locate the problem, but waits for the network side to optimize and update; or, if the RRC connection failure is caused by the terminal device side, or if the RRC connection failure is caused by a problem caused by both the terminal device side and the network side, the terminal device side needs to further perform self-testing and review to determine the cause of the RRC connection failure, and then perform subsequent optimizations and upgrades.

[0013] In one possible implementation, receiving the first information from the first access network device includes: receiving an RRC release message from the first access network device, the RRC release message including the first information, the RRC release message being used to release the RRC connection, and the terminal device entering an RRC non-connected state from an RRC connected state.

[0014] In one possible implementation, receiving the first information from the second access network device includes: receiving an RRC reconfiguration message from the second access network device, the RRC reconfiguration message including the first information.

[0015] In one possible implementation, the method further includes sending a request message to the first access network device or the second access network device, the request message being used to request the first information.

[0016] In one possible implementation, the first information further includes: time information of the RRC connection failure, and / or area information of the RRC connection failure.

[0017] In one possible implementation, the area information of the RRC connection failure includes: the identifier of the first access network device, and / or the identifier of the manufacturer to which the first access network device belongs.

[0018] Secondly, as a counterpart to the first aspect, and with the beneficial effects described in the first aspect, a communication method is provided. The execution subject of this method is a first access network device, or a module, unit, or component (e.g., chip, chip system, circuit, processor, or others) applied in the first access network device. The method includes: establishing a Radio Resource Control (RRC) connection with a terminal device; and sending first information to the terminal device or a second access network device. The first information is information indicating that the RRC connection has failed. The first information includes: the type of RRC connection failure and / or the reason for the RRC connection failure.

[0019] In one possible implementation, the type of RRC connection failure includes: the RRC connection failure is caused by an anomaly; or, the RRC connection failure is caused by a non-anomaly.

[0020] In one possible implementation, the reason for the RRC connection failure includes at least one of the following: the first access network device's radio link fails (RLF); the first access network device experiences network congestion; the first access network device is unable to correctly decode the uplink signaling of the terminal device; the first access network device does not receive a Protocol Data Unit (PDU) session resource establishment request sent by the core network device; or, the first access network device fails to configure the RRC for the terminal device.

[0021] In one possible implementation, the RRC connection failure is a failure of the first access network device to configure the RRC of the terminal device. The first information includes at least one of the following indication information: the version or index of the capability information of the terminal device, a first frequency band combination, or a first RRC configuration. The first frequency band combination is included in the capability information of the terminal device, and the RRC configuration is an incremental configuration based on the first RRC configuration.

[0022] In one possible implementation, the first information further includes: the RRC connection failure is indication information related to the network side and / or the terminal device side.

[0023] In one possible implementation, sending the first information to the terminal device includes: sending an RRC release message to the terminal device, the RRC release message including the first information, the RRC release message being used to release the RRC connection, and the terminal device entering an RRC non-connection state from an RRC connected state.

[0024] In one possible implementation, the method further includes: receiving request information from the terminal device, the request information being used to request the first information.

[0025] In one possible implementation, the first information further includes: time information of the RRC connection failure, and / or area information of the RRC connection failure.

[0026] In one possible implementation, the area information of the RRC connection failure includes: the identifier of the first access network device, and / or the identifier of the manufacturer to which the first access network device belongs.

[0027] Thirdly, as a counterpart to the first aspect, with beneficial effects as described in the first aspect, a communication method is provided. The execution subject of this method is a second access network device, or a module, unit, or component (e.g., chip, chip system, circuit, processor, or others) applied in the second access network device. The method includes: receiving first information from a first access network device, wherein the first information is information about a Radio Resource Control (RRC) connection failure, the RRC connection being an RRC connection between a terminal device and the first access network device, and the first information includes: the type of the RRC connection failure and / or the reason for the RRC connection failure; and sending the first information to the terminal device.

[0028] In one possible implementation, the type of RRC connection failure includes: the RRC connection failure is caused by an anomaly; or, the RRC connection failure is caused by a non-anomaly.

[0029] In one possible implementation, the reason for the RRC connection failure includes at least one of the following: the first access network device's radio link fails (RLF); the first access network device experiences network congestion; the first access network device is unable to correctly decode the uplink signaling of the terminal device; the first access network device does not receive a Protocol Data Unit (PDU) session resource establishment request sent by the core network device; or, the first access network device fails to configure the RRC for the terminal device.

[0030] In one possible implementation, the RRC connection failure is a failure of the first access network device to configure the RRC of the terminal device. The first information includes at least one of the following indication information: the version or index of the capability information of the terminal device, a first frequency band combination, or a first RRC configuration. The first frequency band combination is included in the capability information of the terminal device, and the RRC configuration is an incremental configuration based on the first RRC configuration.

[0031] In one possible implementation, the first information further includes: the RRC connection failure is indication information related to the network side and / or the terminal device side.

[0032] In one possible implementation, sending the first information to the terminal device includes: sending an RRC reconfiguration message to the terminal device, the RRC reconfiguration message including the first information.

[0033] In one possible implementation, the method further includes: receiving request information from the terminal device, the request information being used to request the first information.

[0034] In one possible implementation, the first information further includes: time information of the RRC connection failure, and / or area information of the RRC connection failure.

[0035] In one possible implementation, the area information of the RRC connection failure includes: the identifier of the first access network device, and / or the identifier of the manufacturer to which the first access network device belongs.

[0036] Fourthly, a communication method is provided, wherein the execution subject of the method is a terminal device, or a module, unit, or component (e.g., a chip, chip system, circuit, processor, or others) applied in the terminal device, comprising: sending capability information of the terminal device; receiving first information from a first access network device, wherein the first information is information indicating that the first access network device failed to parse the capability information of the terminal device, and the first information includes: specific information of the parsing failure, and / or the type of the parsing failure.

[0037] Through the above design, the terminal device reports its capability information, the first access network device obtains the capability information of the terminal device, and when the first access network device fails to parse the capability information of the terminal device, the first access network device records the first information related to the parsing failure and sends it to the terminal device to assist the terminal device in locating the problem of the failure to parse the capability information of the terminal device and optimize the process of the terminal device reporting capability information.

[0038] In one possible implementation, the specific information regarding the parsing failure includes at least one of the following: indication information of the frequency band combination for which the first access network device failed to parse, the frequency band combination being included in the capability information of the terminal device; indication information of the code stream for which the first access network device failed to parse, the code stream being the code stream corresponding to the capability information of the terminal device; or, indication information of the information element or field for which the first access network device failed to parse, the information element or field being included in the capability information of the terminal device.

[0039] In one possible implementation, the types of parsing failures include: the first access network device failing to parse all of the capability information of the terminal device; or, the first access network device failing to parse part of the capability information of the terminal device.

[0040] In one possible implementation, the first information further includes: indication information related to the parsing failure on the network side and / or the terminal device side.

[0041] In one possible implementation, receiving the first information from the first access network device includes: receiving a Radio Resource Control (RRC) release message or an RRC reconfiguration message from the first access network device, wherein the RRC release message or the RRC reconfiguration message includes the first information; or, receiving capability query information from the first access network device, wherein the capability query message is used to instruct the terminal device to report the capability information of the terminal device, and the capability query information includes the first information.

[0042] In one possible implementation, the method further includes: sending request information to the first access network device, the request information being used to request the first information.

[0043] In one possible implementation, the first information further includes: the time information of the parsing failure, and / or the region information of the parsing failure.

[0044] In one possible implementation, the area information where the parsing failed includes: the identifier of the first access network device, and / or the identifier of the manufacturer to which the first access network device belongs.

[0045] Fifthly, a communication method is provided, wherein the execution subject of the method is a first access network device, or a module, unit, or component (e.g., chip, chip system, circuit, processor, or others) applied in the first access network device, comprising: acquiring capability information of a terminal device; sending first information to the terminal device, wherein the first information is information indicating that the first access network device failed to parse the capability information of the terminal device, and the first information includes: specific information of the parsing failure, and / or the type of the parsing failure.

[0046] In one possible implementation, the specific information regarding the parsing failure includes at least one of the following: indication information of the frequency band combination for which the first access network device failed to parse, the frequency band combination being included in the capability information of the terminal device; indication information of the code stream for which the first access network device failed to parse, the code stream being the code stream corresponding to the capability information of the terminal device; or, indication information of the information element or field for which the first access network device failed to parse, the information element or field being included in the capability information of the terminal device.

[0047] In one possible implementation, the types of parsing failures include: the first access network device failing to parse all of the capability information of the terminal device; or, the first access network device failing to parse part of the capability information of the terminal device.

[0048] In one possible implementation, the first information further includes: indication information related to the parsing failure on the network side and / or the terminal device side.

[0049] In one possible implementation, sending first information to the terminal device includes: sending a Radio Resource Control (RRC) release message or an RRC reconfiguration message to the terminal device, wherein the RRC release message or the RRC reconfiguration message includes the first information; or, sending capability query information to the terminal device, wherein the capability query message is used to instruct the terminal device to report its capability information, and the capability query information includes the first information.

[0050] In one possible implementation, the method further includes: receiving request information from the terminal device, the request information being used to request the first information.

[0051] In one possible implementation, the first information further includes: the time information of the parsing failure, and / or the region information of the parsing failure.

[0052] In one possible implementation, the area information where the parsing failed includes: the identifier of the first access network device, and / or the identifier of the manufacturer to which the first access network device belongs.

[0053] Sixthly, an apparatus is provided capable of implementing the methods of the first or fourth aspect described above. For example, the apparatus includes modules, units, or components corresponding to the methods described in the first aspect. The modules, units, or components may be implemented in hardware, software, or a combination of hardware and software.

[0054] In one design, the device includes a unit that performs the methods described in the first or fourth aspect above.

[0055] In one design, the device includes a processor for implementing the methods of the first or fourth aspect described above. Optionally, the device further includes a memory, with the processor coupled to the memory, the processor executing computer programs or instructions stored in the memory, causing the device to implement the methods of the first or fourth aspect described above.

[0056] In one design, the device includes a processor and an interface circuit. The interface circuit is used to receive signals from other devices outside the device and transmit them to the processor, or to send signals from the processor to other devices outside the device. The processor implements the methods of the first or fourth aspect described above through logic circuits or executing code instructions.

[0057] In one design, the device may be the first device, or a module, unit, or component (e.g., a chip, chip system, circuit, or processor, etc.) that corresponds one-to-one with the first device to perform the methods / operations / steps / actions described in the first aspect, or a device that can be used in conjunction with the first device.

[0058] A seventh aspect provides an apparatus capable of implementing the methods of the second or fifth aspect described above. For example, the apparatus includes modules, units, or components corresponding to the methods described in the second or fifth aspect. The modules, units, or components may be implemented in hardware, software, or a combination of hardware and software.

[0059] In one design, the device includes a unit that performs the methods described in the second or fifth aspect above.

[0060] In one design, the device includes a processor for implementing the methods of the second or fifth aspect described above. Optionally, the device further includes a memory, with the processor coupled to the memory, the processor executing computer programs or instructions stored in the memory, causing the device to implement the methods of the second or fifth aspect described above.

[0061] In one design, the device includes a processor and an interface circuit, the interface circuit being used to receive signals from other devices outside the device and transmit them to the processor or to send signals from the processor to other devices outside the device, the processor being used to implement the methods of the second or fifth aspect described above through logic circuits or executing code instructions.

[0062] In one design, the device may be a second device, or a module, unit, or component (e.g., a chip, chip system, circuit, or processor, etc.) that corresponds one-to-one with the methods / operations / steps / actions described in the second or fifth aspect of the second device, or a device that can be used in conjunction with the second device.

[0063] Eighthly, an apparatus is provided capable of implementing the method of the third aspect described above. For example, the apparatus includes modules, units, or components that perform the method described in the third aspect. Specifically, the modules, units, or components may be implemented in hardware, software, or a combination of hardware and software.

[0064] In one design, the device includes a unit that performs the method described in the third aspect.

[0065] In one design, the device includes a processor for implementing the method of the third aspect described above. Optionally, the device further includes a memory, with the processor coupled to the memory, the processor executing a computer program or instructions stored in the memory, such that the device implements the method of the third / sixth aspect described above.

[0066] In one design, the device includes a processor and an interface circuit. The interface circuit is used to receive signals from other devices outside the device and transmit them to the processor, or to send signals from the processor to other devices outside the device. The processor implements the method of the third aspect described above through logic circuits or executing code instructions.

[0067] In one design, the device may be a third device, or a module, unit, or component (e.g., a chip, chip system, circuit, or processor, etc.) that corresponds one-to-one with the method / operation / step / action described in the third aspect within the third device, or it may be compatible with the second device.

[0068] Ninth aspect, a computer-readable storage medium is provided that stores a computer program or instructions, which, when executed on a computer, cause the computer to implement the methods of any one of the first to fifth aspects described above.

[0069] In a tenth aspect, a computer program product is provided, comprising a computer program or instructions that, when executed by a computer, cause the methods of any one of the first to fifth aspects to be performed.

[0070] Eleventhly, a chip is provided, including a processor for implementing the methods of any one of the first to fifth aspects described above. Optionally, the chip further includes a memory, the processor being coupled to the memory, the processor being configured to execute computer programs or instructions stored in the memory, such that the chip implements the methods of any one of the first to fifth aspects described above.

[0071] In a twelfth aspect, a communication system is provided, comprising: a first communication device and a second communication device; wherein the first communication device is used to implement the method of the first aspect; the second communication device is used to implement the method of the second aspect; optionally, it further comprises a third communication device, which is used to implement the method of the third aspect. Alternatively, the first communication device is used to implement the method of the fourth aspect; and the second communication device is used to implement the method of the fifth aspect. Attached Figure Description

[0072] Figure 1 A schematic diagram of the communication system provided in the embodiments of this application;

[0073] Figure 2 A schematic diagram of the ORAN system provided in the embodiments of this application;

[0074] Figure 3 A schematic diagram of the access network device provided in the embodiments of this application;

[0075] Figure 4 , Figure 5 , Figure 6 and Figure 7 A flowchart provided for the implementation of this application;

[0076] Figure 8 and Figure 9 This is a schematic diagram of the device provided in an embodiment of this application. Detailed Implementation

[0077] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings. The specific operating methods and functional descriptions in the method embodiments can also be applied to the device embodiments or system embodiments.

[0078] In this application, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship; in the formulas of this application, the character " / " indicates that the preceding and following related objects have a "division" relationship. "Including at least one of A, B, or C" or similar expressions can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C, where A, B, and C can be singular or plural.

[0079] In the embodiments of this application, the various numerical designations are used for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the process numbers does not imply the order of execution; the execution order of each process should be determined by its function and internal logic. The ordinal numbers such as "first" and "second" used in the embodiments of this application are used to distinguish multiple objects and do not limit the size, order, timing, priority, or importance of the multiple objects. In the description of the embodiments of this application, "at a certain time, some operations are performed" can be replaced with "after a certain time, some operations are performed." For example, "when the first access network device determines that the RRC connection has failed, it records the first information related to the RRC connection failure" can be replaced with "after the first access network device determines that the RRC connection has failed, it records the first information related to the RRC connection failure." Similarly, "after a certain time, some operations are performed" can also be replaced with "at a certain time, some operations are performed." For example, the following text, "After receiving the RRC release message, the terminal device releases the RRC connection between itself and the first access network device", can be replaced with: "When the terminal device receives the RRC release message, it releases the RRC connection between itself and the first access network device".

[0080] Figure 1 A possible, non-limiting system schematic diagram is shown. For example... Figure 1 As shown, the communication system 1000 includes a radio access network (RAN) 100 and a core network (CN) 200. Optionally, the communication system 1000 also includes an Internet 300.

[0081] RAN100 includes at least one RAN node (such as...) Figure 1 110a and 110b (collectively referred to as 110) and at least one terminal device (such asFigure 1 RAN100, denoted as RAN100, comprises RAN nodes 120a-120j, collectively referred to as RAN120. RAN100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment. Figure 1 (not shown in the image), etc.

[0082] Terminal device 120 is connected to RAN node 110 wirelessly. RAN node 110 is connected to core network 200 wirelessly or via wired connection. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0083] RAN100 can be used for cellular systems related to the 3rd generation partnership project (3GPP), such as 4th generation (4G). th generation, 4G), fifth generation (5 th RAN100 can be a generation (5G) mobile communication system, or a future-oriented evolution system (such as future communication networks). RAN100 can also be an open access network (openRAN, O-RAN, or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN100 can also be a communication system that integrates two or more of the above systems.

[0084] RAN node 110, forming part of the communication system, assists terminal devices in achieving wireless access. Multiple RAN nodes 110 in the communication system 1000 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal device 120 are relative, for example... Figure 1 The network element 120i can be a helicopter or a drone, and it can be configured as a mobile base station. For terminal devices 120j that access RAN100 through the network element 120i, the network element 120i is a base station; but for base station 110a, the network element 120i is a terminal device.

[0085] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future communication network, or an access node in a WiFi system, etc. Figure 1 110a), micro base stations or indoor stations (such as Figure 1 The RAN node can be a relay node or donor node (as described in 110b), or a radio controller in a CRAN scenario. Optionally, the RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application embodiment can be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in this application embodiment can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions.

[0086] In another possible scenario, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each implementing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0087] It is understood that CU (or CU-CP and CU-UP), DU, or RU may have different names in different systems, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called an open-CU (open-CU, O-CU), DU can also be called an open-DU (open-DU, O-DU), CU-CP can also be called an open-CU-CP (open-CU-CP, O-CU-CP), CU-UP can also be called an open-CU-UP (open-CU-UP, O-CU-UP), and RU can also be called an open-RU (open RU, O-RU). For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in the embodiments of this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0088] Terminal device 120 is a device with wireless transceiver capabilities. Terminal device 120 can also be referred to as terminal equipment, user equipment (UE), mobile station, mobile terminal device, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. This application embodiment does not limit the device form of the terminal device.

[0089] RAN node 110 and terminal device 120 can be fixed or mobile. RAN node 110 and terminal device 120 can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed in the air on aircraft, balloons, and satellites. This application embodiment does not limit the application scenarios of RAN node 110 and terminal device 120. RAN node 110 and terminal device 120 can be deployed in the same or different scenarios. For example, RAN node 110 and terminal device 120 can be deployed simultaneously on land; or RAN node 110 can be deployed on land and terminal device 120 can be deployed on water, etc., and so on.

[0090] RAN node 110 and terminal device 120 can communicate via licensed spectrum, unlicensed spectrum, or both simultaneously. For example, RAN node 110 and terminal device 120 can communicate via spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0091] RAN node 110 and terminal equipment 120 may sometimes be referred to as communication devices, for example Figure 1 Network elements 110a and 110b can be understood as communication devices with base station functions; for example, the communication device can be a base station, or a module, unit, or component applied to a base station (e.g., a chip, chip system, processor, circuit, or others). The chip system consists of chips and may also include chips and other discrete devices. Network elements 120a-120j can be understood as communication devices with terminal equipment functions; for example, the communication device can be a terminal device, or a module, unit, or component applied to a terminal device.

[0092] The solution in this application embodiment can be applied to Figure 1 The communication system 1000 shown can correspond to a terrestrial network (TN). Alternatively, the solution of this embodiment can also be applied to a non-terrestrial network (NTN). In an NTN communication system, Figure 1 In this context, "RAN node" can be replaced with "satellite and ground station." Satellites are deployed in space, while ground stations are deployed on the ground. A ground station can be understood as a base station deployed on the ground, and it can also be called a gateway station (GW). The link between the satellite and the terminal equipment is called the user link, the link between the satellite and the ground station is called the feeder link, and the link between different satellites is called the inter-satellite link. Satellite operating modes include transparent and regenerative.

[0093] When the satellite operates in transparent transmission mode, it has signal relay capabilities, and the ground station possesses all or part of the functions of a base station; the ground station can be considered a base station. It is understood that a ground station can be a single device (e.g., a macro base station or a micro base station), or it can consist of multiple RAN nodes (e.g., CU and DU) implementing the corresponding functions; see the preceding explanation for details. Alternatively,

[0094] When a satellite operates in regenerative mode, it has the ability to process digital signals and possesses all or part of the functions of a base station; thus, the satellite can be considered a base station. Furthermore, regenerative mode can be further subdivided into: all base station functions are deployed on the satellite, referred to as "all base station functions (e.g., CU and DU) on satellite"; or, some base station functions are deployed on the satellite, referred to as "partial base station functions (e.g., DU) on satellite," while the remaining base station functions (e.g., CU) are implemented at the ground station.

[0095] Satellites and ground stations are sometimes referred to as communication devices. For example, a satellite can be understood as a communication device with satellite functions, and a ground station can be understood as a communication device with ground station functions.

[0096] It is understood that in the TN communication system, the RAN node is used to help terminal devices achieve wireless access, and it can also be referred to in other different ways, such as RAN entity, ORAN device, access node, access network device, etc.; in the NTN communication system, satellites and ground stations help terminal devices achieve wireless access. In the following description of the embodiments of this application, unless otherwise specified, the nodes or devices that help terminal devices achieve wireless access will be described as "access network devices".

[0097] It is understood that, in the embodiments of this application, the functions of the access network device can also be executed by modules, units, or components (such as chips) within the access network device, or by a control subsystem that includes the functions of the access network device. This control subsystem, including the functions of the access network device, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal device can also be executed by modules, units, or components (such as chips or modems) within the terminal device, or by a device that includes the functions of the terminal device.

[0098] Figure 2 A schematic diagram of a possible, non-limiting ORAN system is shown. (e.g.) Figure 2 As shown, the ORAN system includes: core network equipment, access network equipment, and terminal equipment. The access network equipment communicates with the core network equipment via a backhaul link and with the terminal equipment via an air interface.

[0099] The access network equipment includes BBUs and RUs. A BBU communicates with at least one RU via a fronthaul link. The BBU and RU may or may not be co-located. Specifically, the BBU communicates with core network equipment via a backhaul link, and the RU communicates with terminal equipment via an air interface. A BBU includes at least one CU and at least one DU, which can communicate via at least one midhaul link.

[0100] Figure 3 This diagram illustrates a possible, non-limiting, node function partitioning and protocol layer structure for an access network device. It is understood that the access network device adopts an ORAN architecture and can also be referred to as an ORAN device, used to enable wireless access for terminal devices.

[0101] It is understandable that communication between access network devices and terminal devices follows a certain protocol layer structure. This protocol layer structure can include a control plane protocol layer structure and a user plane protocol layer structure. For example, the control plane protocol layer structure can include the functions of protocol layers such as the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the media access control (MAC) layer, and the physical layer. For example, the user plane protocol layer structure can include the functions of protocol layers such as the PDCP layer, the RLC layer, the MAC layer, and the physical layer. In one possible implementation, a service data adaptation protocol (SDAP) layer can also be included above the PDCP layer.

[0102] like Figure 3 As shown, the access network equipment includes logical nodes such as CU, DU, and RU. The CU can connect to the core network via an interface, for example, an E2 interface. Optionally, the CU may have some core network functions. The CU can control at least one DU, and the CU can connect to the DU via an interface, for example, an F1 interface. Further, the control plane (CP) interface can be called F1-C, and the user plane (UP) interface can be called F1-U. The DU can control at least one RU, and the DU can connect to the RU via an interface, for example, a fronthaul interface.

[0103] 1. CU

[0104] A CU can be a logical node that carries the RRC layer, SDAP layer, PDCP layer, and other control functions of access network equipment. In other words, a CU can implement the functions of the RRC layer, SDAP layer, PDCP layer, and certain control functions.

[0105] Furthermore, CU can be broken down into CU-CP and CU-UP. (See reference...) Figure 3The CU-CP is a logical node that carries the control plane (control plane part of PDCP, PDCP-C) of the RRC and PDCP layers, and is used to implement the control plane functions of the CU. The CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function network elements, such as the access and mobility management function (AMF) in a 5G communication system. (Continue to refer to...) Figure 3 The CU-UP is a logical node that carries the data plane (user plane part of PDCP, PDCP-U) layer of the SDAP and PDCP layers, and is used to implement the user plane functions of the CU. The CU-UP can interact with network elements in the core network used to implement user plane functions, such as the user plane function (UPF) in a 5G communication system.

[0106] 2. DU

[0107] A DU can be a logical node that carries the RLC layer, MAC layer, higher physical layer (Higher PHY) layer, and other functions. For example, the higher physical layer may include some of the processing functions of the PHY layer, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation. In other words, a DU can implement the functions of the RLC layer, MAC layer, higher physical layer, and other functions.

[0108] It is understood that the above CU and DU configurations are merely examples, and the functions of the CU and DU can be configured as needed. For instance, the CU or DU can be configured to have more protocol layer functions, or it can be configured to have only some protocol layer processing functions. For example, some functions of the RLC layer and the protocol layer functions above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of the CU or DU can be divided according to service type or other system requirements, such as by latency, placing functions that need to meet low latency requirements in the DU and functions that do not need to meet such latency requirements in the CU.

[0109] 3. RU

[0110] An RU can be a logical node that carries both lower physical layer (PHY) and radio frequency (RF) chain processing. For example, the lower physical layer includes some of the processing functions of the physical layer, such as fast Fourier transform (FFT), inverse fast Fourier transform (IFFT), digital beamforming, and filtering. In other words, an RU can implement both physical layer and RF functions.

[0111] In one possible implementation, the RU can be a 3GPP transmission reception point (TRP), a remote radio head (RRH), or other similar entity. The RU communicates with one or more terminal devices via a wireless link.

[0112] DU and RU can be co-located or not, without restriction. (See reference...) Figure 3 The interaction between the DU and RU can include the O-RAN control user and synchronization (CUS-Plane) and the O-RAN management plane (M-Plane). The O-RAN CUS plane can be simply referred to as the CUS plane, and the O-RAN management plane as the management plane. Further, the CUS plane can be divided into a control plane (C-Plane) and a user plane (U-Plane). Optionally, the control plane refers to the real-time control plane between the DU and RU. The management plane refers to the non-real-time management operations between the DU and RU.

[0113] Reference Figure 3 The DU and RU exchange control plane and user plane information via the lower-layer split-control, user, and synchronization (LLS-CUS) interface through the fronthaul link. Furthermore, the LLS-CUS interface may include an LLS-C interface corresponding to the control plane and an LLS-U interface corresponding to the user plane. The DU and RU exchange management plane information through the LLS-M interface of the fronthaul link. (See reference...) Figure 3 It can also be connected to an external management system via the LLS-M interface.

[0114] It is understandable that DUs and RUs can cooperate to implement physical layer functions. A DU can be connected to one or more RUs. The functions of DUs and RUs can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the physical layer, and an RU can be configured to implement lower-level functions in the physical layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer may include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions may include another portion of the physical layer's functions that are closer to the mid-RF side.

[0115] In a wireless communication system, a Recurrent Control (RRC) connection can be established between a terminal device and a first access network device, and communication can be conducted based on this established RRC connection. For example, the terminal device and the first access network device can use the established RRC connection to transmit control signaling and / or data information. In one possible implementation, the aforementioned RRC connection may fail. When an RRC connection failure occurs, how to locate the problem and optimize the communication between the terminal device and the first access network device is a research direction. In one approach, personnel can simulate the communication environment of the terminal device, test the terminal device under this environment, obtain test logs, and locate the RRC connection failure based on the test logs. However, RRC connection failures may be caused by reasons on the terminal device side, the network side, or a combination of both. Furthermore, for some RRC connection failures, the terminal device side may not obtain the corresponding information. It can be seen that locating the RRC connection failure solely based on the test logs recorded by the terminal device side may lead to inaccurate problem identification.

[0116] In view of the above, embodiments of this application provide a communication method and apparatus. In the method: a terminal device establishes an RRC connection with a first access network device; when the RRC connection fails, the first access network device can record first information of the RRC connection failure and send the first information to the terminal device; wherein, the first information can assist the terminal device or the server corresponding to the terminal device in more accurately locating the problem of the RRC failure, thereby optimizing the communication between the terminal device and the first access network device.

[0117] In the various flowcharts of the embodiments of this application, the executing entity can be a terminal device, an access network device, or a module, unit, or component (e.g., a chip, chip system, processor, circuit, or others) within the terminal device or access network device. The following description uses terminal devices and access network devices as examples of executing entities. When the executing entity is a module, unit, or component within the terminal device / access network device, receiving / transmitting can be understood as input / output; that is, the module communicates with other modules or components of the terminal device or access network device. Furthermore, the processing performed by a single executing entity can also be divided among multiple executing entities, which can be logically and / or physically separated. For example, the processing performed by the access network device can be divided among at least one of CU, DU, RU, etc.

[0118] Example 1

[0119] In Embodiment 1, an RRC connection can be established between the first access network device and the terminal device. When the RRC connection fails, the first access network device can record first information related to the RRC connection failure. The first access network device can directly send the first information to the terminal device; or, the first access network device can send the first information to a second access network device, which then sends the first information to the terminal device. Figure 4 As shown, a flowchart is provided, including:

[0120] Step 410: The terminal device establishes an RRC connection with the first access network device.

[0121] For example, the terminal device sends an RRC setup request message to the first access network device; after receiving the RRC setup request message, the first access network device sends an RRC setup message to the terminal device; after receiving the RRC setup message, the terminal device sends an RRC setup complete message to the first access network device; and an RRC connection is successfully established between the terminal device and the first access network device.

[0122] In one possible implementation, after a successful RRC connection is established between the terminal device and the first access network device, if the RRC connection fails, the first access network device may record information related to the RRC connection failure (i.e., first information). In one case, as described in step 420a, the first access network device sends the first information to the terminal device. Alternatively, in another case, as described in steps 420b and 430b, the first access network device sends the first information to the second access network device, and the second access network device forwards the first information to the terminal device.

[0123] Step 420a: The first access network device sends first information to the terminal device, and the terminal device receives the first information from the first access network device.

[0124] In one possible implementation, the first access network device may send dedicated signaling to the terminal device. This dedicated signaling includes first information, which may be RRC signaling, such as an RRC release message. For example, the first access network device may send an RRC release message to the terminal device, which includes the first information. After receiving the RRC release message, the terminal device releases its RRC connection with the first access network device. The terminal device then transitions from an RRC connected state to (or switches to) an RRC disconnected state. For example, the RRC disconnected state may be an RRC idle state or an RRC inactive state. Alternatively, the aforementioned dedicated signaling may be any other RRC message besides the RRC release message, without limitation.

[0125] It is understandable that the first access network device can proactively send first information to the terminal device. For example, when an RRC connection fails, the first access network device can record first information related to the RRC connection failure and send the first information to the terminal device. Alternatively, the first access network device can send first information to the terminal device based on a request from the terminal device. For example, the terminal device sends a request to the first access network device, which requests the first information; upon receiving the request, the first access network device sends the first information to the terminal device based on the request. There are no restrictions on when the terminal device sends the request information. For example, the terminal device can send the request information to the first access network device when it determines that its RRC connection with the first access network device has failed, without any restriction.

[0126] Step 420b: The first access network device sends first information to the second access network device, and the second access network device receives the first information from the first access network device.

[0127] In one possible implementation, the terminal device may send an RRC reconstruction request to the second access network device. The second access network device determines the first access network device based on the information included in the RRC reconstruction request. The second access network device may request first information from the first access network device. The first access network device sends the first information to the second access network device. For the specific process, please refer to the description of steps 530b to 580b in Example 1 below.

[0128] Step 430b: The second access network device sends the first information to the terminal device, and the terminal device receives the first information from the second access network device.

[0129] In one possible implementation, the second access network device may send an RRC message to the terminal device, the RRC message including the first information. This RRC message may be an RRC reconfiguration message or other RRC messages, without limitation.

[0130] It is understood that the second access network device may proactively send the first information to the terminal device, or the second access network device may send the first information to the terminal device upon receiving a request from the terminal device. For example, the terminal device may send a request message to the second access device, which requests the first information; upon receiving the request message, the second access network device may send the first information to the terminal device.

[0131] In one possible implementation, when the terminal device receives the first information, it can locate the RRC failure based on the first information and optimize the communication between the terminal device and the first access network device. Alternatively, the terminal device can forward the first information to its server, which can then analyze the RRC connection failure based on the first information. Alternatively, either the first or second access network device can directly send the first information to the terminal device's server, without restriction.

[0132] In one possible implementation, the first information includes at least one of the following: the type of RRC connection failure, the reason for the RRC connection failure, indication information indicating that the RRC connection failure is related to the network side and / or the terminal device side, time information of the RRC connection failure, area information of the RRC connection failure, or a first parameter, etc. For example, in one possible implementation, the first information includes at least one of the following:

[0133] 1. Types of RRC connection failures.

[0134] For example, the types of RRC connection failures include: RRC connection failures caused by an anomaly; or RRC connection failures not caused by an anomaly. For example, an RRC connection failure caused by an anomaly can be understood as: an anomaly occurs during the communication between the terminal device and the first access network device, which leads to the RRC connection failure. For anomaly-induced RRC connection failures, please refer to the explanations of the reasons (3) and (4) below. An RRC connection failure not caused by an anomaly can be understood as: an RRC connection failure occurs during the normal communication between the terminal device and the first access network device, and this RRC connection failure is not due to an anomaly. For anomaly-induced RRC connection failures, please refer to the explanations of the reasons (1) and (2) below.

[0135] In one interpretation, the first access network device records the type of RRC connection failure and sends this type of failure to the terminal device. This has the following advantages: Based on the type of RRC connection failure, the terminal device can determine whether the failure was caused by an anomaly or a non-anomaly. If it was caused by a non-anomaly, the terminal device does not need to blindly perform retesting and problem localization, thus saving power consumption.

[0136] In one possible implementation, the first information includes a bit that can be called the RRC connection failure type-related bit. When this bit takes the first value, it indicates that the RRC connection failure is due to an anomaly; when the bit takes the second value, it indicates that the RRC connection failure is not due to an anomaly. For example, the first value can be 1 and the second value can be 0, or vice versa; there are no restrictions.

[0137] 2. Reasons for RRC connection failure. The reasons for RRC connection failure include at least one of the following:

[0138] (1) Radio link failure (RLF) of the first access network device.

[0139] For example, the RLC of the first access network device fails, or the first access network device fails to receive uplink data packets on the scheduled uplink resources multiple times in a row.

[0140] (2) Network congestion of the first access network device.

[0141] For example, the number of connected terminal devices connected to the first access network device exceeds the maximum number of terminal devices that the first access network device can accommodate.

[0142] (3) The first access network device is unable to correctly decode (or parse) the uplink signaling of the terminal device.

[0143] In one possible implementation, an RRC connection is successfully established between the first access network device and the terminal device. The terminal device sends uplink signaling to the first access network device over this RRC connection. For example, this uplink signaling can be uplink control signaling, such as uplink control information (UCI). The first access network device may be unable to correctly decode (or parse) the terminal device's uplink signaling. Here, the aforementioned uplink signaling can also be replaced with / understood as: physical uplink control channel (PUCCH), or the format of the physical uplink control channel. The inability to correctly decode the uplink signaling may be due to a misalignment in the understanding of the uplink control channel (PUCCH) format between the first access network device and the terminal device. For example, the terminal device sends uplink signaling according to a first format PUCCH, while the first access network device parses the uplink signaling according to a second format PUCCH. In this case, the first access network device can record the first information. Furthermore, optionally, the first information may also include the format used by the first access network device when parsing the uplink signaling (i.e., the second format), or it can be understood as the format that the first access network device believes the terminal device should use when sending the uplink signaling (i.e., the first access network device believes the terminal device should use the second format).

[0144] (4) The first access network device did not receive a protocol data unit (PDU) session resource establishment request sent by the core network device.

[0145] It is understandable that the "PDU session resource establishment request" mentioned above is used to request resources from the first access network device to establish a PDU session, and there is no restriction on the name of this request. For example, as technology and / or standards evolve, this request may also be called by other names, such as the first request.

[0146] In one possible implementation, after a successful RRC connection is established between the terminal device and the first access network device, the terminal device sends a PDU session establishment request to the core network device. This request is used to request the establishment of a PDU session. Upon receiving the PDU session establishment request, the core network device instructs the first access network device to establish the resources for the PDU session. In one scenario, after a successful RRC connection is established between the first access network device and the terminal device, the first access network device does not receive the PDU session resource establishment request sent by the core network. It is understood that the first access network device's failure to receive the aforementioned PDU session resource establishment request may be due to various reasons, such as core network anomalies, and / or interface anomalies between the core network device and the first access network device, all of which may cause the first access network device to fail to receive the PDU session resource establishment request.

[0147] (5) The first access network device failed to configure the RRC of the terminal device.

[0148] For example, after a successful RRC connection is established between the terminal device and the first access network device, the first access device can send an RRC configuration to the terminal device to configure the aforementioned RRC connection. One specific implementation of the aforementioned RRC connection failure is: RRC configuration failure. For details regarding RRC configuration failure, please refer to Example 2 in Embodiment 1.

[0149] In one interpretation, the first access network device records the reason for the RRC connection failure and sends the reason for the RRC connection failure to the terminal device. This has the following beneficial effects: the terminal device can locate the problem of the RRC connection failure based on the reason for the RRC connection failure and quickly and efficiently resolve the problem that caused the RRC connection failure.

[0150] 3. Indication information used to indicate that the RRC connection failure is related to the network side and / or the terminal device side. For example, this indication information may be:

[0151] The first indication information is used to indicate that the RRC connection failure is related to the network side. In one interpretation, "the RRC connection failure is related to the network side" can be understood as: the RRC connection failure is caused by a network-side issue, or the problem causing the RRC connection failure only involves the network side and not the terminal device side, or the problem causing the RRC connection failure does not involve interoperability between the terminal device side and the network side.

[0152] The second indication information is used to indicate that the RRC connection failure is related to the terminal device side. In one interpretation, "the RRC connection failure is related to the terminal device side" can be understood as: the RRC connection failure is caused by a problem on the terminal device side, or the problem causing the RRC connection failure only involves the terminal device side and not the network side, or the problem causing the RRC connection failure does not involve the interoperability between the terminal device side and the network side.

[0153] The third indication information is used to indicate whether the RRC connection failure is related to both the terminal device side and the network side. In one interpretation, "the RRC connection failure is related to both the terminal device side and the network side" can be understood as: the RRC connection failure is caused by a common reason on both the terminal device side and the network side; or, the problem causing the RRC connection failure involves both the terminal device side and the network side; or, the problem causing the RRC connection failure involves inter-operability between the terminal device side and the network side.

[0154] In one interpretation, the first access network device records the cause of the RRC connection failure as being on the network side and / or the terminal device side, and sends the recorded relevant information to the terminal device side. This has the following beneficial effects: Based on the above information, the terminal device side can determine whether the RRC connection failure was caused by a problem on the terminal device side, a problem on the network side, or a problem caused by both the terminal device side and the network side. This allows the terminal device side to perform targeted optimizations. For example, if the RRC connection failure is caused by a problem solely on the network side, the terminal device side does not need to blindly retest and locate the problem, but can wait for optimization updates from the network side. Alternatively, if the RRC connection failure is caused by the terminal device side, or if it is caused by a problem caused by both the terminal device side and the network side, the terminal device side needs to further perform self-testing and review to determine the cause of the RRC connection failure and then perform subsequent optimizations and upgrades.

[0155] 4. Time information of RRC connection failure.

[0156] In one interpretation, the time information of RRC connection failure can refer to the moment when the RRC connection failure occurred, or a period of time, etc. It should be noted that in Example 1 of Embodiment 1 below, the occurrence of the first event can lead to RRC connection failure (i.e., RRC release). Or, broadly speaking, RRC connection failure includes the first event. That is to say, when the first event occurs, it can be considered that the RRC connection has failed. In this case, the time information of RRC connection failure can refer to the time information of the first event, such as the moment when the first event occurred, or the period of time during which the first event occurred, etc.

[0157] 5. Information on areas where RRC connection failed.

[0158] For example, this area information could refer to the cell identifier, RAN notification area (RNA) identifier, tracking area (TA) identifier, or the identifier of the access network device corresponding to the RRC connection failure (i.e., the identifier of the first access device), and / or the identifier of the vendor to which the first access network device belongs. Sending the identifier of the vendor to which the first access network device belongs to the terminal device has the following advantages: the terminal device can align and discuss with the vendor to which the first access network device belongs, locate the problem of the RRC failure, and optimize the communication between the terminal device and the access network device of that vendor.

[0159] It should be noted that in Example 1 of Embodiment 1 below, the area information of the RRC connection failure can specifically be the area information corresponding to the first event, such as the cell identifier, RNA identifier, TA identifier, or the identifier of the access network device corresponding to the first event (i.e., the identifier of the first access device), and / or the identifier of the manufacturer to which the first access network device belongs, etc.

[0160] In one possible implementation, when the RRC connection failure is due to an anomaly, the first access network device further determines that the anomaly is related to the terminal device and / or the network side, and indicates this to the terminal device. For example, the first information includes the type of RRC connection failure; when the RRC connection failure is due to an anomaly, the first information may also include indication that the RRC connection failure is related to the terminal device and / or the network side. Alternatively, when the RRC connection failure is not due to an anomaly, the first information may not include the aforementioned indication information.

[0161] 6. First parameter

[0162] When an RRC connection failure is due to an RRC configuration failure, the first information includes a first parameter, which is a parameter related to the RRC configuration. For example, the first parameter may indicate at least one of the following: the version or index of the terminal device's capability information, a first frequency band combination, or a first RRC configuration. It is understood that the concept of a "first parameter" may be omitted for ease of description. For example, when an RRC connection failure is due to an RRC configuration failure, the first information may indicate at least one of the following: the version or index of the terminal device's capability information, a first frequency band combination, or a first RRC configuration, where the first frequency band combination is included in the terminal device's capability information, and the RRC configuration is an incremental configuration based on the first RRC configuration.

[0163] In one possible implementation, an RRC connection failure can be either an RRC release or the release of the RRC connection itself. It is understood that the first access network device can instruct the terminal device to release the RRC connection, or the terminal device can actively release the RRC connection; there are no restrictions. An RRC connection can be established between the terminal device and the first access network device. When the first access network device releases the RRC connection, it can record first information and send it to the terminal device. This first information can be understood as information related to the RRC release. Alternatively, more broadly, when the first access network device detects a first event, it can be considered that the RRC connection has failed. The terminal device can record first information related to the first event and send it to the terminal device, as explained in Example 1 below.

[0164] In another possible implementation, an RRC connection failure could be described as an RRC configuration failure. In some descriptions, an RRC configuration failure could be described as an RRC reconfiguration failure or an RRC recovery failure. For example, when the first access network device fails to configure its RRC connection with the terminal device, the first access network device can record first information related to the RRC configuration failure and send this first information to the terminal device, as detailed in Example 2 below.

[0165] Example 1

[0166] like Figure 5 As shown in the figure, this application provides a flowchart, including:

[0167] Step 510: Establish an RRC connection between the terminal device and the first access network device.

[0168] The process of establishing an RRC connection between the terminal device and the first access network device can be referred to... Figure 4 Explanation of step 410.

[0169] Step 520: The first access network device records the first information.

[0170]

Scenario 1

[0171] The first access network device records the first information, and the first access network device sends the first information to the terminal device.

[0172] For example, an RRC connection is successfully established between the first access network device and the terminal device: the first access network device detects an event (which can be referred to as the first event):

[0173] In one interpretation, the first event does not lead to the release of the aforementioned RRC connection. For example, when the first access network device detects the first event, it does not release the RRC connection. The first access network device records the first information. In the RRC connection state, the first access network device sends RRC signaling including the first information to the terminal device. For example, the first information includes at least one of the following: the type of the first event (e.g., whether the first event is caused by an anomaly or not), indication information of the first event, indication information that the first event is related to the network side and / or the terminal device side (e.g., the first event is caused by a reason on the network side and / or the terminal device side), time information of the first event, or area information of the first event, etc.

[0174] In another interpretation, the first event causes the release of the aforementioned RRC connection. For example, when the first access network device detects the first event, it decides to release the aforementioned RRC connection. Here, the first event can also be referred to as the reason for releasing the RRC connection. The first access device records first information, and sends an RRC release message including the first information to the terminal device. When the terminal device receives the RRC release message, it releases the RRC connection, and the terminal device transitions from an RRC connected state to an RRC disconnected state. This application embodiment focuses on describing the process of this interpretation; please refer to the description in step 530a.

[0175] Step 530a: The first access network device sends an RRC release message to the terminal device. The terminal device receives the RRC release message from the first access network device. The RRC release message includes first information.

[0176] In the event that the aforementioned first event causes the RRC connection to be released, the first information includes at least one of the following: the type of RRC connection failure, the reason for the RRC connection failure (such as the first event), indication information indicating that the RRC connection failure is related to the network side and / or the terminal device, the time information of the RRC connection failure, or the area information of the RRC connection failure. For the function of each piece of information contained in each piece of information, please refer to [reference needed]. Figure 4 The explanation provided is as follows. It is understood that in this context, "RRC connection failure" specifically refers to RRC release. Therefore, the description of "RRC connection failure" above can be replaced with "RRC release." For example, the first information includes at least one of the following: the type of RRC release, the reason for the RRC release (such as a first event), indication information indicating that the RRC release is related to the network side and / or the terminal side, the time information of the RRC release, or the area information of the RRC release, etc.

[0177] Alternatively, in a broader sense, the occurrence of the first event can be considered an RRC connection failure, without specifying whether the first event actually caused the RRC connection failure. Specifically, when the first access network device detects the first event, it can record the first information and send it to the terminal device. For example... Figure 4The description states that the first information includes at least one of the following: the type of RRC connection failure, the reason for the RRC connection failure, indication information indicating that the RRC connection failure is related to the network side and / or the terminal device side, the time information of the RRC connection failure, or the area information of the RRC connection failure. In this case, "RRC connection failure" can be replaced with "first event". For example, the first information includes at least one of the following: the type of the first event (e.g., the first event is caused by an anomaly, or by a non-anomaly), the indication information of the first event, indication information indicating that the first event is related to the network side and / or the terminal device side (e.g., the first event is caused by a reason on the network side and / or the terminal side), the time information of the first event, or the area information of the first event, etc.

[0178]

Scenario 2

[0179] The first access network device sends the first information to the terminal device through the second access network device. For example, the first access network device sends the first information to the second access network device, and the second access network device forwards the first information to the terminal device.

[0180] For example, if an RRC connection is successfully established between the first access network device and the terminal device: the first access network device detects a first event and records the first information. There is no restriction on whether this first event triggers the release of the RRC connection. If the terminal device actively disconnects the RRC connection with the first access network device, triggering the RRC reconstruction process, and then establishes an RRC connection with the second access network device, the second access network device can obtain the first information from the first access network device and send it to the terminal device. For example:

[0181] Before the terminal device receives the first information from the first access network device, the terminal device triggers the RRC reconstruction process. For example, due to poor downlink channel quality, an RLF occurs on the terminal device side, and the terminal device disconnects its RRC connection with the first access network device. The terminal device then sends an RRC reconstruction request to the second access network device. This RRC reconstruction request includes at least: the terminal device's identifier, the physical cell identifier (PCI) of the cell where the RRC connection failed, and security verification information. This security verification information can be a short MAC-I used for access stratum (AS) security verification. The second access network device determines the first access network device based on the PCI of the cell where the RRC connection failed. The second access network device sends a context request message for the terminal device to the first access network device, which carries the terminal device's context identifier. The first access network device determines the context of the corresponding terminal device based on the terminal device's context identifier. If the first access network device passes the security verification, it responds to the request message by sending the terminal device's context to the second access network device. In this embodiment, the context of the terminal device sent by the first access network device to the second access network device carries first information. See steps 530b to 580b below for details.

[0182] Step 530b: The terminal device sends an RRC reconstruction request to the second access network device. The second access network device receives the RRC reconstruction request from the terminal device. The RRC reconstruction request is used to request the establishment of an RRC connection between the terminal device and the second access network device.

[0183] For example, the RRC reconstruction request includes the terminal device's identifier, the PCI of the cell where it was camped when the RRC connection failed, and security verification information. The second access network device can determine the first access network device based on the PCI of the cell where it was camped when the RRC connection failed.

[0184] Step 540b: The second access network device sends a request message to the first access network device. The first access network device receives the request message from the second access network device. This request message is used to request the context of the terminal device.

[0185] For example, the request information includes an identifier of the terminal device context requested by the second access network device. The first access network device determines the context of the corresponding terminal device based on this identifier, and in step 550b, the first access network device sends the context of the corresponding terminal device to the second access network device. However, in this embodiment, the context of the terminal device also carries first information recorded by the first access network device.

[0186] Step 550b: The first access network device sends the context of the terminal device to the second access network device, and the second access network device receives the context of the terminal device from the first access network device. The context of the terminal device includes the first information.

[0187] It is understood that the second access network device can obtain the first information within the context of the terminal device. The second access network device can send the first information to the terminal device. In this embodiment, there are no restrictions on the method by which the second access network device sends the first information to the terminal device. For example, in one possible implementation, after the RRC reconstruction between the second access network device and the terminal device is completed, the second access network device sends the first information to the terminal device. Further, the terminal device may carry request information for requesting the first information in the RRC reconstruction completion message sent to the second access network device. When the second access network device receives the request information, it sends the first information to the terminal device, specifically referring to steps 560b to 580b below.

[0188] Step 560b: The second access network device sends an RRC reconstruction to the terminal device, and the terminal device receives the RRC reconstruction from the second access network device.

[0189] Step 570b: The terminal device sends an RRC reconstruction completion message to the second access network device. The second access network device receives the RRC reconstruction completion message from the terminal device. The RRC reconstruction completion message includes request information, which is used to request the first information.

[0190] In particular, after steps 560b and 570b, the RRC reconstruction between the terminal device and the second access network device is completed, and the RRC connection between the terminal device and the second access network device is successfully established.

[0191] Step 580b: The second access device sends the first information to the terminal device, and the terminal device receives the first information from the second access network device.

[0192] For example, the second access network device sends an RRC reconfiguration message to the terminal device. The RRC reconfiguration message includes first information and is used to configure the RRC connection between the second access network device and the terminal device.

[0193] In one possible implementation, the second access network device and the first access network device can be the same access network device. For example, if the terminal device experiences an RRC failure in cell 1 of the first access network device, the terminal device selects cell 2, whose signal quality meets the S criterion, to trigger RRC reconstruction. Cell 2 belongs to the first access network device. In this case, Figure 5The description of "second access network device" in the process can be replaced with "first access network device". Furthermore, since in this case, there is no need to transmit the first information between the two access network devices, Figure 5 Steps 540b and 550b do not need to be executed in the process; that is, steps 540b and 550b are optional.

[0194] Understandably, in scenario 2, there is no restriction on whether the first event leads to the release of the RRC. For example, when the first access network device detects the first event, it does not release the RRC connection, but records the first information related to the first event. At this time, the terminal actively disconnects from the first access network device and initiates the RRC reconstruction process to establish an RRC connection with the second access network device. When the second access network device receives the RRC reconstruction request from the terminal device, it requests the first information from the first access network device and sends the first information to the terminal device. In this case, the first information includes at least one of the following: the type of the first event (e.g., whether the first event is caused by an anomaly or not), the indication information of the first event, the indication information that the first event is related to the network side and / or the terminal device side (e.g., the first event is caused by a reason on the network side and / or the terminal side), the time information of the first event, or the area information of the first event, etc.

[0195] Alternatively, in scenario 2, when the first access network device detects the first event, it decides to release the RRC connection. The first access network device records the first event and / or first information related to the RRC release. Afterwards, the first access network device may send an RRC release message to the terminal device. However, if the terminal device actively disconnects the RRC connection with the first access network device and establishes an RRC connection with the second access network device before receiving the RRC release message, the second access network device can obtain the first information from the first access network device and send it to the terminal device. In this case, the first information includes at least one of the following: the type of RRC release, the reason for the RRC release (such as the first event), indication information related to the network side and / or the terminal side, the time information of the RRC release, or the area information of the RRC release, etc.

[0196] In one understanding, RRC connection failure can be interpreted as RRC release or the release of an RRC connection. It can also be understood broadly as the occurrence of a first event (such as an RRC link anomaly, like a network-side RLF or network device failure to resolve uplink signaling). In the following description, using RRC connection failure as an example of RRC release or the release of an RRC connection, the process of the embodiments of this application will be illustrated:

[0197] Example 1: The first event is the first access network device RLF.

[0198] For example, an RRC connection is successfully established between the terminal device and the first access network device. The first access network device experiences an RLF (Restricted Link Default), and decides to release the RRC connection with the terminal device. The first access network device records the first information. The first access network device sends the first information to the terminal device. (The rest of the text appears to be unrelated and likely refers to a different scenario.) Figure 5 In step 530a, the first access network device may send an RRC release message to the terminal device, the RRC release message including the first information. Alternatively, as... Figure 5 In steps 530b to 580b, the first access network device sends first information to the second access network device, and the second access network device sends first information to the terminal device.

[0199] In Example 1, the first information includes at least one of the following: the type of RRC release and / or the reason for the RRC release. Specifically, the type of RRC release can be: an RRC connection caused by a non-conductive error, and the reason for the RRC release can be: a first access network device RLF. Furthermore, the first information also includes: the time information of the RRC release, and / or the area information of the RRC release. The time information of the RRC release can be specifically the time information of the first access network device sending the RLF, and the area information of the RRC release can be specifically the area information of the first access network device where the RLF occurred.

[0200] Example 2: The first event is network congestion in the first access network device.

[0201] An RRC connection is successfully established between the terminal device and the first access network device. Due to network congestion on the first access network device, it decides to release the RRC connection with the terminal device. The first access network device records first information and sends an RRC release message to the terminal device, which includes the first information. Alternatively, the first access network device may send the first information to the terminal device through a second access network device.

[0202] In Example 2, the first information includes at least one of the following: the type of RRC release and / or the reason for the RRC release. Specifically, the type of RRC release can be: an RRC release due to non-abnormal circumstances; the reason for the RRC release can be: network congestion of the first access network device. Furthermore, the first information also includes: the time information of the RRC release, and / or the area information of the RRC release. The time information of the RRC release can be specifically the time information of network congestion of the first access network device, and the area information of the RRC release can be specifically the area information of network congestion of the first access network device.

[0203] Example 3: The first event is that the first access network device cannot correctly decode (or parse) the uplink signaling of the terminal device.

[0204] For example, an RRC connection is successfully established between the terminal device and the first access network device. The terminal device uses this RRC connection to send uplink signaling to the first access network device. The first access network device cannot correctly decode the uplink signaling and decides to release the RRC connection. The first access network device records first information and sends this first information to the terminal device. One possible approach is that the first access network device sends an RRC release message including the first information to the terminal device, or the first access network device sends the first information to the terminal device through a second access network device.

[0205] In Example 3, the first information includes at least one of the following: the type of RRC release, the reason for the RRC release, and indication information indicating that the RRC release is related to the terminal device side and / or the network side. Specifically, the type of RRC release is: RRC release due to an anomaly. The reason for the RRC release is: the first access network device cannot correctly decode the uplink signaling. In one understanding, the above indication information is specifically used to indicate that the RRC release is related to the terminal device side. For example, the above indication information is specifically the second indication information. For example, if the first access network device cannot correctly decode the uplink signaling sent by the terminal device, the first access network device may consider that the cause of the problem is on the terminal device side, such as the terminal device not sending the uplink signaling in accordance with the predefined or network-configured uplink signaling format, thus causing the first access network device to be unable to correctly decode the uplink signaling. Or, in another understanding, the above indication information is specifically used to indicate that the RRC release is jointly related to the network side and the terminal device side. For example, the above indication information can be the third indication information. For example, the first access network device believes that because the format of the uplink signaling is not aligned between the terminal device and the first access network device, the first access network device cannot decode the uplink signaling sent by the terminal device. For example, the terminal device encapsulates the uplink signaling according to format A, while the first access network device decapsulates it according to format B, resulting in the first access network device being unable to correctly decode the uplink signaling. Furthermore, the first information also includes: the time information of the RRC release, and / or the area information of the RRC release.

[0206] In one scenario, the uplink signaling can be feedback from the terminal device regarding the success of downlink transmission. For example, the uplink signaling may include an acknowledgement (ACK) or a negative acknowledgement (NACK). ACK indicates successful downlink transmission, while NACK indicates downlink transmission failure. If the first access network device cannot correctly decode the uplink signaling, it cannot obtain confirmation of successful downlink data packet transmission, potentially leading to a large number of retransmissions of successfully transmitted data packets to the terminal device. Therefore, in this case, the first access network device can record first information and send it to the terminal device. The terminal device can then use this first information to determine the cause of the problem, thereby resolving the issue of a large number of retransmissions of successfully transmitted data packets due to the first access network device's inability to decode the uplink signaling. Alternatively, in another scenario, the uplink signaling may be a scheduling request (SR) from the terminal device. Upon receiving the SR, the first access network device can schedule the terminal device accordingly. If the first access network device fails to correctly decode the uplink signaling, it may be unable to obtain the SR (Search Service Request) from the terminal device, thus failing to fulfill the terminal device's scheduling request. In this case, the first access network device can record the first information and send it to the terminal device. The terminal device can then use this first information to determine the cause of the problem and fulfill its scheduling request. Alternatively, in another scenario, the uplink signaling is channel state information (CSI), used to indicate the channel characteristics of the communication link. The first access network device can select an appropriate modulation and coding scheme in the next scheduling based on the CSI fed back by the terminal device to ensure transmission reliability. If the first access network device fails to correctly decode the CSI, it will be unable to schedule data correctly according to the channel state. For example, if the modulation and coding scheme chosen by the first access network device is too aggressive, it may cause bit errors and packet errors; conversely, if the chosen modulation and coding scheme is too conservative, a high data rate cannot be achieved. In short, this will affect the user experience during communication. In this case, the first access network device can record the first information and send it to the terminal device. The terminal device can then use this first information to determine the cause of the problem, ensuring smooth CSI feedback and guaranteeing the user experience.

[0207] In the above scenario, if the terminal device and the first access network device do not have a consistent understanding of the PUCCH format carrying uplink signaling, it will severely affect the communication quality on the RRC link. Therefore, by recording the first information and sending it to the terminal device, the first access network device can help the terminal device quickly locate the cause of the problem and thus perform targeted optimization.

[0208] Example 4: The first event is that the first access network device does not receive a PDU session resource establishment request sent by the core network device.

[0209] For example, after a terminal device successfully establishes an RRC connection with a first access network device, if the first access network device does not receive a PDU session resource establishment request from the core network device, the first access network device decides to release the RRC connection. The first access network device records first information and sends an RRC release message including the first information to the terminal device, or the first access network device sends the first information to the terminal device through a second access network device.

[0210] In Example 4, the first information includes at least one of the following: the type of RRC release, the reason for the RRC release, and indication information indicating that the RRC release is related to the terminal device and / or the network side. Specifically, the type of RRC release is: RRC release due to an anomaly. The reason for the RRC release is: the first access network device did not receive the PDU session resource establishment request sent by the core network device. In one understanding, the above indication information is specifically used to indicate that the RRC release is related to the network side. For example, the above indication information is specifically the first indication information. For example, the RRC release is caused by a network-side issue. Thus, when the terminal device receives the above indication information, it can determine that the RRC release is caused by the network side, and the terminal device does not need to blindly perform retesting and problem localization; it can simply wait for the network side's optimization and update.

[0211] For example, after a successful RRC connection is established between a terminal device and a first access network device: the terminal device sends a PDU session establishment request to the core network device. This request is used to establish a PDU session for data transmission by the terminal device. Upon receiving the PDU session establishment request, the core network device can send a PDU session resource establishment request to the first access network device. This request is used to request the resources of the first access network device to establish the PDU session. In one scenario, an anomaly occurs in the core network and / or an interface anomaly occurs between the core network and the first access network device. This results in the first access network device not receiving the PDU session resource establishment request from the core network after a successful RRC connection is established between the terminal device and the first access network device. In this case, the first access network device may mistakenly believe that the terminal device has no communication needs, causing it to release the RRC connection after a period of time. Therefore, in this embodiment of the application, when the first access network device and the terminal device successfully establish an RRC connection, and the first access network device does not receive a PDU session resource establishment request sent by the core network device, the first access network device decides to release the RRC between itself and the terminal device. The first access network device can record the first information and send the recorded first information to the terminal device so that the terminal device can locate the problem of the RRC release.

[0212] Through the above design, the network side can record information related to anomalies occurring during communication and send it to the terminal device. This assists the terminal device in accurately locating RRC release issues, thereby quickly and efficiently resolving abnormal scenarios and optimizing the terminal device's performance under network conditions. For example, based on the RRC release type included in the first message sent by the network device, the terminal device can determine whether the RRC release is caused by an anomaly or not. Furthermore, based on the indication information included in the first message sent by the network device, the terminal device can determine whether the RRC release is caused by a problem on the terminal device side and / or the network side, thus allowing for targeted optimization of the communication process. For instance, if the RRC release is caused by a network-only issue, the terminal device does not need to blindly retest and locate the problem but can simply wait for network-side optimization updates. Alternatively, if the RRC release is due to a single terminal device or interoperability issues between the terminal device and the network device, the terminal device needs to perform further self-testing and review, or collaborate with the network device manufacturer to negotiate on the issue of the first information record, determine how to align the understanding between the network and terminal sides, and perform subsequent optimizations and updates to avoid interoperability problems, etc.

[0213] Example 2

[0214] like Figure 6 As shown in the figure, this application provides a flowchart, including:

[0215] Step 610: The terminal device establishes an RRC connection with the first access network device.

[0216] The process of establishing an RRC connection between the terminal device and the first access network device can be referred to... Figure 4 Explanation of step 410.

[0217] Step 620: The first access network device sends RRC configuration to the terminal device, and the terminal device receives the RRC configuration from the first access network device.

[0218] In one understanding, RRC configuration can be interpreted as configuring the aforementioned RRC connection. RRC configuration may include the configuration of the radio bearer, measurement settings, and communication resources for the RRC connection. RRC configuration can be carried in an RRC reconfiguration message or an RRC resume message.

[0219] Step 630: The terminal device determines that the RRC configuration failed.

[0220] For example, if a terminal device receives an RRC configuration but cannot comply with it to communicate with the first access network device, the RRC configuration is considered to have failed. This failure to comply with the RRC configuration could mean either failing to comply with a portion of the RRC configuration or failing to comply with all of the RRC configuration to communicate with the first access network device. It is understood that the RRC configuration can be carried in an RRC reconfiguration message or an RRC recovery message. An RRC configuration failure can be described as / replaced with an RRC reconfiguration failure, or it can be described as an RRC recovery failure.

[0221] Step 640: The first access network device records the first information.

[0222] The first access network device determines that the RRC configuration of the terminal device has failed, and the first access network device may record the first information. This application embodiment does not limit the process by which the first access network device determines that the RRC reconfiguration has failed. For example, if the first access network device does not receive a corresponding successful response (such as an RRC reconfiguration completion message) within a first time period after sending the RRC configuration, it considers the RRC configuration to have failed.

[0223] In one possible implementation, when the first access network device fails to configure the RRC of the terminal device, the terminal device can trigger an RRC reconstruction. For example, the terminal device sends an RRC reconstruction request to the second access network device. Upon receiving the RRC reconstruction request, the second access network device requests the context of the terminal device from the first access network device. The first access network device sends the context of the terminal device to the second access network device, which includes first information recorded by the first access network device. Then, the second access network device sends the first information to the terminal device. For example, after the RRC reconstruction between the second access network device and the terminal device is completed, the second access network device sends the first information to the terminal device. The RRC reconstruction process between the second access network device and the terminal device includes: the second access network device sending an RRC reconstruction request to the terminal device, and the terminal device sending an RRC reconstruction completion message to the second access network device. Further, the RRC reconstruction completion message sent by the terminal device to the second access network device includes request information for requesting the first information. Upon receiving this request information, the second access network device sends the first information to the terminal device. See steps 650 to 6010 below for details.

[0224] Step 650: The terminal device sends an RRC reconstruction request to the second access network device, and the second access network device receives the RRC reconstruction request from the terminal device.

[0225] For example, the RRC reconstruction request includes the identifier of the terminal device, the PCI of the cell where the terminal device camped when the RRC reconfiguration failed, and verification information. The second access network device determines the first access network device based on the PCI included in the RRC reconstruction request and requests the context of the terminal device from the first access network device.

[0226] Step 660: The second access network device sends a request for context information of the terminal device to the first access network device, and the first access network device receives the request for context information of the terminal device from the second access network device.

[0227] Step 670: The first access network device sends the context of the terminal device to the second access network device, and the second access network device receives the context of the terminal device from the first access network device. The context of the terminal device includes the first information.

[0228] Step 680: The second access network device sends an RRC reconstruction to the terminal device, and the terminal device receives the RRC reconstruction from the second access network device.

[0229] Step 690: The terminal device sends an RRC reconstruction completion message to the second access network device, and the second access network device receives the RRC reconstruction completion message from the terminal device; optionally, the RRC reconstruction completion message includes request information for requesting the first information.

[0230] Step 6010: The second access network device sends the first information to the terminal device, and the terminal device receives the first information from the second access network device.

[0231] For example, the second access network device sends an RRC reconfiguration message to the terminal device. The RRC reconfiguration message includes first information and is used to configure the RRC connection between the second access network device and the terminal device.

[0232] In one possible implementation, the first access network device and the second access network device can be the same access network device. Figure 6 In the process, all descriptions of "second access network device" can be replaced with "first access network device." There is no need for the two access network devices to transmit initial information. Figure 6 The process does not require the execution of steps 660 and 670; that is, steps 660 and 670 are optional.

[0233] In Example 2, in one possible implementation, the first information is used to indicate at least one of the following: the version or index of the capability information of the terminal device, a first frequency band combination, or a first RRC configuration, wherein the first frequency band combination is included in the capability information of the terminal device, and the RRC configuration is an incremental configuration based on the first RRC configuration.

[0234] In one possible implementation, the capability information of the terminal device can be simply referred to as capability information, which is reported by the terminal device. For example, the terminal device can report capability information multiple times, and each version of the capability information has a corresponding index or identifier. For instance, the index / version of the capability information reported by the terminal device for the first time is 0, the index / version of the capability information reported for the second time is 1, and so on. Each time the terminal device reports capability information, the index / version of the corresponding capability information increases by 1.

[0235] In this scenario, before step 620, the following steps may also be included: the terminal device sends capability information, and the first access network device obtains the capability information. For example, the terminal device may send capability information to the first access network device, and the first access network device may receive capability information from the terminal device. Alternatively, the terminal device may report capability information to other devices, and the first access network device obtains the terminal device's capability information through these other devices. These other devices can be core network devices or other access network devices besides the first access network device, without limitation. It is understood that the capability information reported by the terminal device includes a sample or index corresponding to that capability information. The first access network device may perform RRC configuration based on a certain version of capability information reported by the terminal device. When RRC configuration fails, the first access network device records first information, for example, the first information includes the version or index of the capability information of the terminal device to which the current RRC configuration is applied or referenced, and indicates this to the terminal device. The terminal device can specifically determine which version of capability information it reported may have a problem, thus causing the current RRC configuration to fail.

[0236] In another possible implementation, the capability information reported by the terminal device includes a list of frequency band combinations supported by the terminal device. This list includes at least one frequency band combination, and each frequency band combination includes at least one frequency band. The terminal device can report the capabilities it supports for each frequency band combination at a granular level. In another possible implementation, the first access network device determines a frequency band combination (which can be referred to as the first frequency band combination) from the capability information reported by the terminal device. The first access network device can perform RRC configuration based on the first frequency band combination (which can also be understood as based on the capabilities of the first frequency band combination). If the RRC configuration fails, the first access network device can record first information, such as information about the first frequency band combination corresponding to the current RRC configuration, and indicate this to the terminal device. It is understood that the first information can specifically indicate the frequency bands included in the first frequency band combination, or it can indicate the identifier or index of the first frequency band combination, which can indicate the position of the first frequency band combination in the frequency band combination list. For example, the index of the frequency band combination that is first in the list of frequency band combinations is 1, the index of the second one is 2, and so on. Based on the indication of the first information, the terminal device can determine which specific frequency band combination in the terminal device's capability information may have a problem, thus causing the current RRC configuration to fail.

[0237] In another possible implementation, the first access network device can use incremental (delta) configuration when performing RRC configuration. The first access network device provides first configuration parameters that differ from the baseline configuration through incremental configuration. Configuration parameters identical to the baseline configuration do not need to be re-indicated to the terminal device. This approach reduces signaling overhead, improves compatibility, and lowers the probability of configuration errors. For example, the first access network device obtains the baseline configuration and determines the first configuration parameters based on it. These first configuration parameters can be understood as the configuration parameters that differ between the current RRC configuration and the baseline configuration. The first access network device sends the first configuration parameters to the terminal device. It is understood that the RRC configuration in step 620 above specifically refers to the first configuration parameters. These first configuration parameters can be carried in an RRC reconfiguration message or an RRC recovery message. When the current RRC configuration fails, the first access network device can record first information, which includes the aforementioned baseline configuration (which can be called the first RRC configuration), and instruct the terminal device on the aforementioned baseline configuration. The terminal device can then determine which specific baseline configuration might have a problem, leading to the current RRC configuration failure.

[0238] It is understood that the aforementioned baseline configuration can come from the first access network device or from other access network devices. In one possible implementation, during a handover scenario, when the source access network device determines to handover the terminal device to the target access network device, the source access network device can send a handover request message to the target access network device. This handover request message may include the source access network device's RRC configuration (baseline configuration). The target access network device can perform incremental configuration based on the RRC configuration provided by the source access network device. In this case, the source access network device's RRC configuration can serve as the baseline configuration, and the first access network device is the target access network device. In response to the handover request, the target access network device sends a handover request acknowledgement message to the source access network device. This message may carry the target access network device's RRC configuration for the terminal device. This RRC configuration is used for communication between the terminal device and the target access network device. The source access network device forwards the target access network device's RRC configuration to the terminal device, for example, by sending it to the terminal device via an RRC reconfiguration message. When the RRC configuration from the target access network (first access network device) fails, the target access network device records the first information, which includes the baseline configuration used by the target access network device, and sends the first information to the terminal device. The process of sending the first information to the terminal device can be referred to the description of steps 650 to 6010.

[0239] In one possible scenario, when a terminal device in an RRC inactive state requests the restoration of an RRC connection from a first access network device, the RRC restoration message sent by the first access network device to the terminal device includes an RRC configuration, which is an incremental configuration based on the configuration of the terminal device in the previous RRC connected state. In another possible implementation, the first access network device requests the terminal device's context information from the access network device (also known as the anchor access network device) where the terminal device previously resided in the RRC connected state to obtain the configuration from that previous RRC connected state. In this case, the configuration from the previous RRC connected state is the baseline configuration. When the terminal device experiences an RRC restoration failure with the first access network device, the first access network device records first information, including the baseline configuration used by the first access network device, and sends the first information to the terminal device. The process of sending the first information to the terminal device can be referred to the descriptions of steps 650 to 6010.

[0240] Optionally, the first information may also include at least one of the following: the type of RRC connection failure, the reason for the RRC connection failure, indication information indicating that the RRC connection failure is related to the network side and / or the terminal device side, the time information of the RRC connection failure, and the area information of the RRC connection failure. It is understood that in Example 2, the RRC connection failure specifically refers to an RRC configuration failure; therefore, in Example 2, "RRC connection failure" can be replaced with "RRC configuration failure." For example, the first information may also include at least one of the following: the type of RRC configuration failure, the reason for the RRC configuration failure, indication information indicating that the RRC configuration failure is related to the network side and / or the terminal device side, the time information of the RRC configuration failure, and the area information of the RRC configuration failure.

[0241] It is understandable that the types of RRC configuration failures mentioned above can be specifically defined as: RRC configuration failures caused by an anomaly; the reasons for RRC configuration failures can be specifically defined as: RRC configuration failures; RRC configuration failures can be caused by network-side issues, terminal device-side issues, or a combination of terminal device-side and network-side issues. Therefore, the above indication information can be specifically defined as first indication information, second indication information, or third indication information, without limitation. The time information of RRC configuration failures can be specifically defined as: the time information when the RRC configuration failure occurred, which can refer to a specific moment or a period of time, etc. The area information of RRC configuration failures can refer to the area where the RRC configuration failure occurred, for example, the identifier of the access network device corresponding to the RRC configuration failure (i.e., the identifier of the first access network device), and / or the identifier of the vendor corresponding to the first access network device, etc.

[0242] Understandably, in Figure 6In the process: the first access network device fails to configure RRC on the terminal device, and records the first information related to the RRC configuration failure; the first access network device sends the first information to the second access network device, and the second access network device sends the first information to the terminal device. Alternatively, the first access network device can directly send the first information to the terminal device, for example, the first access network device sends an RRC release message to the terminal device, which includes the first information.

[0243] Through the above design, in the scenario where the first access network device fails to configure RRC for the terminal device, the first access network device can record first information related to the RRC configuration failure. After the terminal device re-establishes an RRC connection with the second access network device, the first information is sent to the terminal device, thereby assisting the terminal device in locating the problem of RRC configuration failure. For example, if the first information includes indication information of a first frequency band combination, the terminal device can determine that the first access network device used the first frequency band combination for RRC configuration, and that the RRC configuration failed. The terminal device can then narrow down the scope of the anomaly, determining that the first frequency band combination in the terminal device's capability information is abnormal, and further analyze the capabilities in the first frequency band combination to locate the problem of RRC configuration failure. Alternatively, when the terminal device determines that the first frequency band combination is abnormal, the terminal device can proactively request the network side to update the terminal device's capability information. The updated capability information may not include the aforementioned first frequency band combination to avoid the recurrence of RRC configuration failure. Alternatively, the terminal device can fall back to single-carrier capabilities or fall back to capabilities of a certain baseline configuration to avoid compatibility issues between the terminal device and the network.

[0244]

Example 2

[0245] The difference between Embodiment 2 and Embodiment 1 is as follows: In Embodiment 1, when the RRC connection between the terminal device and the first access network device fails, the first access network device records the first information of the RRC connection failure and sends the first information to the terminal device to assist the terminal device in locating the RRC failure problem; in Embodiment 2, the terminal device reports its capability information, the first access network device obtains the terminal device's capability information, and when the first access network device fails to parse the terminal device's capability information, the first access network device records the first information related to the parsing failure and sends it to the terminal device to assist the terminal device in locating the problem of the parsing failure of the terminal device's capability information and optimize the process of the terminal device reporting capability information. Figure 7 As shown, a flowchart is provided, including:

[0246] Step 710: The terminal device sends its capability information, and the first access network device obtains the terminal device's capability information.

[0247] The capability information of the terminal device can be simply referred to as capability information. For example, in one possible implementation, the terminal device reports its capability information to a first access network device, and the first access network device receives the capability information from the terminal device. Specifically, the first access network device may send a UE capability enquiry to the terminal device, and when the terminal device receives this enquiry, it reports its capability information to the first access network device. It is understandable that... Figure 7 The flowchart mainly describes this implementation method.

[0248] In another possible implementation, after the terminal device registers with the core network for the first time, the terminal device reports its capability information to other access network devices. These other access network devices forward the information to the core network, which stores the capability information. The first access network device then obtains the terminal device's capability information from the core network or from other access network devices.

[0249] In one understanding, the capabilities of a terminal device can refer to its wireless capabilities, or its access layer (AS) capabilities. Since different manufacturers and models of terminal devices have different capabilities, the terminal device needs to report its supported capabilities to the network. The network side then configures and schedules the terminal device correctly and appropriately based on this information to enable communication.

[0250] Optionally, in step 720: the first access network device fails to parse the capability information of the terminal device, and the first information is recorded.

[0251] In one possible implementation, if the first access network device fails to parse all capability information of the terminal device, the first access network device records the first information. Alternatively, if the first access network device fails to parse some capability information of the terminal device, the first access network device records the first information. For example, if the first access network device fails to parse a portion of the frequency band combination, some information elements, or fields in the capability information of the terminal device, the first access network device may record the first information. Regarding the content included in the first information, please refer to the description below. In one description, the above "parse failure" can be replaced with: reception failure, decoding failure, interpretation failure, or decryption failure, etc.

[0252] Step 730: The first access network device sends first information to the terminal device, and the terminal device receives the first information from the first access network device.

[0253] The process of the first access network device sending the first information to the terminal device is illustrated by the following two examples:

[0254] Example 1: The first access network device can send an RRC message to the terminal device, which includes first information. This RRC message can be an RRC release message, an RRC reconfiguration message, or other RRC messages, without restriction.

[0255] For example, before step 710, an RRC connection is established between the terminal device and the first access network device. This process can be referred to... Figure 4 The following is an explanation of step 410. Afterwards, the terminal device, based on this RRC connection, reports its capability information to the first access network device. If the first access network device fails to parse the capability information reported by the terminal device, it records the first piece of information.

[0256] In one possible implementation, if the first access network device fails to resolve the capability information of the terminal device, it can release the RRC connection. The first access network device can send an RRC release message to the terminal device, which includes the first information. Upon receiving the RRC release message, the terminal device releases its RRC connection with the first access network device. The terminal device then transitions from an RRC connected state to an RRC disconnected state.

[0257] In another possible implementation, although the first access network device fails to parse the capability information of the terminal device (e.g., the first access network device fails to parse part of the capability information of the terminal device), the first access network device does not release the RRC connection. The first access network device can send first information to the terminal device in the RRC connected state. For example, in the RRC connected state, the first access network device sends an RRC reconfiguration message, or other RRC message, to the terminal device, and this RRC reconfiguration message, or other RRC message, includes the first information.

[0258] Example 2: The first access network device can send capability query information to the terminal device. The capability query message is used to instruct the terminal device to report the capability information of the terminal device. The capability query information includes first information.

[0259] For example, if the first access network device fails to parse the capability information reported by the terminal device, it sends a capability query message to the terminal device. Upon receiving the capability query message, the terminal device reports the capability information to the first access network device again. For instance, if the first access network device fails to parse the capability information previously reported by the terminal device, the terminal device can report capability information different from the previous version. Alternatively, the terminal device can update its capability information based on information such as the frequency band combination, information element, or field that failed to parse, included in the first information. For example, it can update the aforementioned frequency band combination, information element, or field that failed to parse correctly, so that the first access network device can parse it correctly. Furthermore, the terminal device reports the updated terminal device capability information to the first access network device.

[0260] It is understandable that the first access network device may proactively send the first information to the terminal device, or the first access network device may send the first information to the terminal device based on a request received from the terminal device. For example, the terminal device may send a request message to the first access network device, which is used to request the first information; upon receiving the request message, the first access network device may send the first information to the terminal device.

[0261] In one possible implementation, the first information includes at least one of the following:

[0262] 1. Detailed information about the parsing failure.

[0263] (1) Indication information of the frequency band combination that the first access network device failed to resolve, which is included in the capability information of the terminal device.

[0264] For example, the capability information reported by the terminal device includes a list of frequency band combinations, which includes at least one frequency band combination, and each frequency band combination includes at least one frequency band. Specifically, for each frequency band combination, the terminal device reports the capability information it supports. When the first access network device receives the capability information from the terminal device, it obtains the list of frequency band combinations included in the capability information and parses the capability information for each frequency band combination in the list. When the first access network device fails to parse a certain frequency band combination, it can record first information, such as indication information of the failed-to-parse frequency band combination, for example, the frequency bands included in the failed-to-parse frequency band combination, or the identifier or index of the failed-to-parse frequency band combination. The identifier or index of the frequency band combination can be referred to in Example 2 of Embodiment 1; and the aforementioned failed-to-parse frequency band combination is indicated to the terminal device.

[0265] In one interpretation, the first access network device may discard frequency band combinations that failed to resolve, or consider such frequency band combinations to be ineffective. A frequency band combination that failed to resolve can be understood as either a discarded frequency band combination or an ineffective frequency band combination.

[0266] The first access network device sends an indication message to the terminal device indicating that the frequency band combination has failed to be resolved. This has the following beneficial effects: the terminal device can know which specific frequency band combination has a problem in the capability information reported by the terminal device, and thus optimize or improve that frequency band combination, reducing the probability of future resolution failures.

[0267] (2) Indication information of the code stream that the first access network device failed to parse, wherein the code stream is the code stream corresponding to the capability information of the terminal device.

[0268] In one interpretation, the terminal device can encode its capability information to form a corresponding bitstream; the terminal device then sends the corresponding bitstream to the first access network device. When the first access network device fails to parse the bitstream, it can record first information, such as the length of the failed bitstream and / or the starting position of the failed bitstream, and indicate this information to the terminal device.

[0269] In one interpretation, the first access network device may discard a bitstream that failed to be parsed, or consider the bitstream that failed to be parsed to be invalid. A bitstream that failed to be parsed can be understood as either a discarded bitstream or an invalid bitstream.

[0270] The first access network device sends information about the failed parsing of the bitstream to the terminal device, which has the following advantages: The terminal device can know which bitstream in the bitstream corresponding to the terminal device's capability information failed to be parsed. When the terminal device reports its capability information again, it can only report the bitstream that failed to be parsed, avoiding the repeated reporting of the successfully parsed bitstream.

[0271] (3) Indication information of information elements or fields that the first access network device failed to parse, wherein the information elements or fields are contained in the capability information of the terminal device.

[0272] In one interpretation, the capability information reported by the terminal device includes at least one information element (IE) or field. When the first access network device fails to parse a certain information element or field in the capability information of the terminal device, the first access network device may record first information, such as information about the failed information element or field, for example, an identifier of the failed information element or codeword. This identifier may be the name of the failed information element or field, or the identifier of the parent information element or field of the failed information element or field, or the identifier of the frequency band combination in which the failed information element or field is located, etc., and indicate this to the terminal device.

[0273] The first access network device sends information such as the cell or field that failed to be resolved to the terminal device, which has the following beneficial effects: The terminal device can know which cell or field in the capability information reported by the terminal device has a problem, so as to optimize and improve that cell or field and reduce the probability of future resolution failures.

[0274] 2. Types of parsing failures.

[0275] The types of parsing failures can be: all capability information reported by the first access network device to the terminal device fails to be parsed; or, part of the capability information reported by the first access network device to the terminal device fails to be parsed.

[0276] In one interpretation, terminal devices report their capability information at the granularity of frequency band combinations. When a first access network device fails to resolve a portion of the frequency band combinations, it is considered that the resolution of the capability information reported by the terminal device has partially failed. This portion of the frequency band combinations refers to a subset of frequency band combinations in the frequency band combination list. For example, if the terminal device's reported capability information includes a frequency band combination list containing 5 frequency band combinations, and the first access network device fails to resolve all 5 frequency band combinations, it is considered that the resolution of the capability information reported by the terminal device has completely failed. Alternatively, if the first access network device fails to resolve only a portion of the 5 frequency band combinations, it is considered that the resolution of the capability information reported by the terminal device has partially failed.

[0277] In one interpretation, the failure of the first access network device to partially parse the capability information of the terminal device can be understood as: the first access network device discarding part of the terminal device's capabilities, or the first access network device not applying all of the terminal device's capabilities, or the first access network device truncating the bitstream corresponding to the terminal device's capabilities, or the first access network device only activating part of the terminal device's capabilities, etc.

[0278] 3. Indication information used to indicate that the resolution failure is related to the network side and / or the terminal device side. For example, the indication information specifically includes:

[0279] (1) First indication information, the first indication information is used to indicate the reason on the network side that caused the failure to parse the capability information of the terminal device.

[0280] In one interpretation, network-side reasons causing the failure to resolve terminal device capability information can be understood as a single network-related issue that does not involve the terminal device itself, or the interoperability between the network and the terminal device. For example, network-side reasons causing the failure to resolve terminal device capability information could include: insufficient network storage capacity leading to truncation of the bitstream corresponding to the capability information reported by the terminal device, resulting in the first access network device only resolving a portion of the terminal device's capability information.

[0281] (2) Second indication information, which is used to indicate the reason on the terminal device side that caused the failure to parse the terminal device's capability information.

[0282] In one interpretation, a failure to parse the capability information of a terminal device due to a problem on the terminal device side can be understood as a single issue caused by the terminal device itself, without involving the network side or interoperability between the network side and the terminal device side. For example, if the first access network device fails to parse a certain information element or field in the capability information of the terminal device, the first access network device may assume that the terminal device did not encapsulate the information element or field according to a predefined or configured format, causing the first access network device to fail to parse that information element or field.

[0283] (3) Third indication information, which is used to indicate the common reasons on both the network side and the terminal device side that caused the failure to parse the capability information of the terminal device.

[0284] In one interpretation, a failure to parse the capability information of a terminal device due to a shared reason on both the network and terminal device sides can be understood as a parsing failure caused by interoperability between the network and terminal device sides. For example, if the formats of a certain information element or field in the capability information of the terminal device are misaligned between the terminal device side and the network side, the first access network device may fail to parse that information element or field.

[0285] The first access network device sends the reason for the resolution failure—specifically, whether it's caused by the network side or the terminal device side—to the terminal device. This has the following beneficial effects: The terminal device can learn the reason for the resolution failure. For example, if the reason is due to the terminal device, the terminal device can optimize and / or update its capability information. Alternatively, if the reason is due to the network side, the terminal device doesn't need to blindly optimize and update; it can simply wait for the network side to update. Or, if the reason is due to interaction between the network side and the terminal device side, the terminal device and the network side can interact to pinpoint the resolution failure problem.

[0286] 4. Parse the time information of the failure.

[0287] For example, the time information of the parsing failure is specifically: the time information of the failure of the first access network device to parse the capability information of the terminal device, which is specifically a certain moment or a certain time period.

[0288] 5. Information about the area that failed to be parsed.

[0289] For example, the area information that failed to be resolved specifically includes: when the first access network device fails to resolve the capability information of the terminal device, the area information that failed to be resolved, such as the identifier of the cell that failed to be resolved, or the TA identifier, or the RNA identifier. Alternatively, the identifier of the access network device that failed to be resolved, i.e., the identifier of the first access network device, and / or the identifier of the manufacturer corresponding to the first access network device.

[0290] It is understandable that, in the above Figure 7In the process: the first access network device directly sends the first information to the terminal device. In one scenario, it can also be: the first access network device sends the first information to the second access network device, and the second access network device sends the first information to the terminal device. For example, an RRC connection is successfully established between the first access network device and the terminal device; the terminal device reports its capability information to the first access network device, the first access network device fails to parse the capability information, and records the first information. The terminal device actively disconnects the RRC connection with the first access network device. For example, due to poor downlink channel quality on the terminal device side, an RLF occurs on the terminal device side, and the terminal device actively disconnects the RRC connection with the first access network device. The terminal device sends an RRC reconstruction request to the second access network device. When the second access network device receives the RRC reconstruction request, it requests the context of the terminal device from the first access network device. The context of the terminal device includes the first information recorded by the first access network device. The second access network device sends an RRC reconstruction request to the terminal device, and the terminal device sends an RRC reconstruction completion message to the second access network device. At this time, an RRC connection is successfully established between the second access network device and the terminal device. Optionally, the RRC reconstruction completion includes request information for requesting the first information. The second access network device sends an RRC message to the terminal device, which includes the first information. For example, this RRC message can be an RRC reconfiguration message or other RRC messages, without limitation. The above process is similar to... Figure 5 The process of the second access network device sending the first information to the terminal device is similar; please refer to [link / reference]. Figure 5 Explanation of steps 530b to 580b.

[0291] In one scenario, a terminal device reports its capability information to a first access network device, which then parses this information. If the first access network device fails to parse all of the terminal device's capability information, the first information sent by the first access network device to the terminal device includes an indication of complete parsing failure. Alternatively, the first information may include a parsing failure type, specifically, "complete parsing failure." Furthermore, the first information may also include at least one of the following: indications related to the network side and / or the terminal device side, time information indicating the parsing failure, or area information indicating the parsing failure. Understandably, since the first access network device fails to parse all capability information of the terminal device—for example, if the first access network device fails to parse all frequency band combinations included in the frequency band combination list in the capability information of the terminal device—the first access network device does not need to further indicate the specific information of the parsing failure to the terminal device. When the terminal device receives the indication information that all parsing has failed, the terminal device can naturally determine that all of its reported capability information has failed to parse. For example, if all frequency band combinations included in the capability information reported by the terminal device have failed to parse, there is no need to further indicate each of the aforementioned failed frequency band combinations to the terminal device.

[0292] In another scenario, the terminal device reports its capability information to the first access network device. The first access network device fails to parse part of the terminal device's capability information; for example, it fails to parse a portion of the frequency band combinations or a portion of the information cells or fields in the terminal device's capability information. In this case, the first information sent by the first access network device to the terminal device includes: an indication of partial parsing failure, and specific information about the parsing failure. For example, the specific information about the parsing failure may be an indication of the failed frequency band combinations, a failed code stream, or a failed information cell or field, as described above. Furthermore, the first information also includes at least one of the following: an indication indicating that the parsing failure is related to the network side and / or the terminal device side, time information about the parsing failure, or area information about the parsing failure.

[0293] Through the above design, the terminal device reports its capability information. When the first access network device fails to resolve the terminal device's capability information, the first access network device records the first information related to the resolution failure and sends the first information to the terminal device. The first information can help the terminal device locate the problem of the resolution failure. For example, based on the first information, the terminal device can determine that the RRC was released because the network side failed to resolve the terminal device's capability information. Alternatively, when the network side can correctly resolve part of the terminal device's capability information but does not release the RRC connection, the terminal device can learn from the first information that the network side failed to resolve all of the terminal device's capability information. Furthermore, it can determine which frequency band combinations, information elements, or fields caused the failure, thereby optimizing and improving the corresponding frequency band combinations, information elements, or fields, reducing the probability of future terminal device capability information resolution failures, improving the compatibility between the terminal device and the network side, and enhancing the communication performance of both the terminal device and the network side.

[0294] It is understood that the "first access network device" and "second access network device" in the embodiments of this application can adopt an ORAN architecture, and the access network device can include logical nodes such as CU, DU, and RU. For example, the CU and / or DU in the first access network device can record first information and send the first information to the terminal device through the RU; or, the first information can be sent to the second access network device through a corresponding interface, which can be an Xn interface. For example, the CU and / or DU in the second access network device can receive the first information and send the first information to the terminal device through the RU. Further, the CU can be divided into CU-CP and CU-UP. Specifically, the CU-CP can perform the action of recording the first information.

[0295] In the embodiments provided above, the methods provided by the embodiments of this application are described from the perspective of the interaction between the terminal device, the first access network device, and the second access network device. To implement the functions of the methods provided by the embodiments of this application, the terminal device, the first access network device, or the second access network device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the design constraints of the specific application of the technical solution.

[0296] Based on the same concepts as the above-described method embodiments Figure 8 and Figure 9This is a schematic diagram of the possible communication devices provided in the embodiments of this application. These communication devices can realize the functions implemented by the terminal device, the first access network device, or the second access network device in the above method embodiments, and therefore may achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device may be a terminal device, a first access network device, or a second access network device, or a unit, module, or component (such as a chip, chip system, circuit, processor, or others) applied in the terminal device, the first access network device, or the second access network device. In the following description, the term "unit" is used as an example. For example, in the following description, the communication device includes a processing unit and a transceiver unit as an example. The processing unit in the following description can also be replaced by: processing module or processing component, etc. The transceiver unit can also be replaced by: transceiver unit or transceiver component. For example, the transceiver component may refer to a communication module.

[0297] like Figure 8 As shown, the communication device 8000 includes a processing unit 8010 and a transceiver unit 8020. The communication device 8000 is used to implement the above-mentioned... Figure 4 , Figure 5 , Figure 6 or Figure 7 The functions of the terminal equipment, the first access network equipment, or the second access network equipment.

[0298] Optionally, the transceiver unit 8020 may also be referred to as an output unit, an interface unit, or a communication unit, etc. In one possible implementation, the transceiver unit 8020 includes at least one of a transmitting unit or a receiving unit. The transmitting unit and the receiving unit may be integrated together, or they may be two independent units, etc.

[0299] In one possible implementation, the communication device 8000 is used to implement... Figure 4 , Figure 5 or Figure 6 Functions, such as:

[0300] When the communication device 8000 is used to implement Figure 4 , Figure 5 or Figure 6 Specifically, the functions of the terminal device are as follows: a processing unit 8010, used to establish a Radio Resource Control (RRC) connection with a first access network device; and a transceiver unit 8020, used to receive first information from the first access network device or a second access network device, wherein the first information is information about the failure of the RRC connection, and the first information includes: the type of the RRC connection failure, and / or the reason for the RRC connection failure.

[0301] In one possible implementation, the type of RRC connection failure includes: the RRC connection failure is caused by an anomaly; or, the RRC connection failure is caused by a non-anomaly.

[0302] In one possible implementation, the reason for the RRC connection failure includes at least one of the following: the first access network device's radio link fails (RLF); the first access network device experiences network congestion; the first access network device is unable to correctly decode the uplink signaling of the terminal device; the first access network device does not receive a Protocol Data Unit (PDU) session resource establishment request sent by the core network device; or, the first access network device fails to configure the RRC for the terminal device.

[0303] In one possible implementation, the RRC connection failure is a failure of the first access network device to configure the RRC of the terminal device. The first information includes at least one of the following indication information: the version or index of the capability information of the terminal device, a first frequency band combination, or a first RRC configuration. The first frequency band combination is included in the capability information of the terminal device, and the RRC configuration is an incremental configuration based on the first RRC configuration.

[0304] In one possible implementation, the first information further includes: the RRC connection failure is indication information related to the network side and / or the terminal device side.

[0305] In one possible implementation, receiving the first information from the first access network device includes: receiving an RRC release message from the first access network device, the RRC release message including the first information, the RRC release message being used to release the RRC connection, and the terminal device entering an RRC non-connected state from an RRC connected state.

[0306] In one possible implementation, receiving the first information from the second access network device includes: receiving an RRC reconfiguration message from the second access network device, the RRC reconfiguration message including the first information.

[0307] In one possible implementation, the transceiver unit 8020 is further configured to send request information to the first access network device or the second access network device, the request information being used to request the first information.

[0308] In one possible implementation, the first information further includes: time information of the RRC connection failure, and / or area information of the RRC connection failure.

[0309] In one possible implementation, the area information of the RRC connection failure includes: the identifier of the first access network device, and / or the identifier of the manufacturer to which the first access network device belongs.

[0310] When the communication device 8000 is used to implement Figure 4 , Figure 5 or Figure 6 The specific functions of the first access network device are as follows:

[0311] The processing unit 8010 is used to establish a Radio Resource Control (RRC) connection with the terminal device; the transceiver unit 8020 is used to send first information to the terminal device or the second access network device, the first information being information about the failure of the RRC connection, the first information including: the type of the RRC connection failure, and / or the reason for the failure of the RRC connection.

[0312] In one possible implementation, the type of RRC connection failure includes: the RRC connection failure is caused by an anomaly; or, the RRC connection failure is caused by a non-anomaly.

[0313] In one possible implementation, the reason for the RRC connection failure includes at least one of the following: the first access network device's radio link fails (RLF); the first access network device experiences network congestion; the first access network device is unable to correctly decode the uplink signaling of the terminal device; the first access network device does not receive a Protocol Data Unit (PDU) session resource establishment request sent by the core network device; or, the first access network device fails to configure the RRC for the terminal device.

[0314] In one possible implementation, the RRC connection failure is a failure of the first access network device to configure the RRC of the terminal device. The first information includes at least one of the following indication information: the version or index of the capability information of the terminal device, a first frequency band combination, or a first RRC configuration. The first frequency band combination is included in the capability information of the terminal device, and the RRC configuration is an incremental configuration based on the first RRC configuration.

[0315] In one possible implementation, the first information further includes: the RRC connection failure is indication information related to the network side and / or the terminal device side.

[0316] In one possible implementation, sending the first information to the terminal device includes: sending an RRC release message to the terminal device, the RRC release message including the first information, the RRC release message being used to release the RRC connection, and the terminal device entering an RRC non-connection state from an RRC connected state.

[0317] In one possible implementation, the transceiver unit 8020 is further configured to: receive request information from the terminal device, the request information being used to request the first information.

[0318] In one possible implementation, the first information further includes: time information of the RRC connection failure, and / or area information of the RRC connection failure.

[0319] In one possible implementation, the area information of the RRC connection failure includes: the identifier of the first access network device, and / or the identifier of the manufacturer to which the first access network device belongs.

[0320] When the communication device 8000 is used to implement Figure 4 , Figure 5 or Figure 6 The specific functions of the second access network device are as follows:

[0321] The transceiver unit 8020 is configured to receive first information from the first access network device, the first information being information about a Radio Resource Control (RRC) connection failure, wherein the RRC connection is an RRC connection between the terminal device and the first access network device, and the first information includes: the type of the RRC connection failure, and / or the reason for the RRC connection failure; the transceiver unit 8020 is also configured to send the first information to the terminal device.

[0322] In one possible implementation, the type of RRC connection failure includes: the RRC connection failure is caused by an anomaly; or, the RRC connection failure is caused by a non-anomaly.

[0323] In one possible implementation, the reason for the RRC connection failure includes at least one of the following: the first access network device's radio link fails (RLF); the first access network device experiences network congestion; the first access network device is unable to correctly decode the uplink signaling of the terminal device; the first access network device does not receive a Protocol Data Unit (PDU) session resource establishment request sent by the core network device; or, the first access network device fails to configure the RRC for the terminal device.

[0324] In one possible implementation, the RRC connection failure is a failure of the first access network device to configure the RRC of the terminal device. The first information includes at least one of the following indication information: the version or index of the capability information of the terminal device, a first frequency band combination, or a first RRC configuration. The first frequency band combination is included in the capability information of the terminal device, and the RRC configuration is an incremental configuration based on the first RRC configuration.

[0325] In one possible implementation, the first information further includes: the RRC connection failure is indication information related to the network side and / or the terminal device side.

[0326] In one possible implementation, sending the first information to the terminal device includes: sending an RRC reconfiguration message to the terminal device, the RRC reconfiguration message including the first information.

[0327] In one possible implementation, the transceiver unit 8020 is further configured to receive request information from the terminal device, the request information being used to request the first information.

[0328] In one possible implementation, the first information further includes: time information of the RRC connection failure, and / or area information of the RRC connection failure.

[0329] In one possible implementation, the area information of the RRC connection failure includes: the identifier of the first access network device, and / or the identifier of the manufacturer to which the first access network device belongs.

[0330] In another possible implementation, the communication device 8000 is used to implement... Figure 7 Functions, such as:

[0331] When the communication device 8000 is used to implement Figure 7 The specific functions of the terminal device are as follows:

[0332] Processing unit 8010 is used to acquire capability information of terminal device; transceiver unit 8020 is used to send capability information of terminal device; transceiver unit 8020 is also used to receive first information from first access network device, the first information being information that the first access network device failed to parse the capability information of terminal device, the first information including: specific information of the parsing failure, and / or the type of parsing failure.

[0333] In one possible implementation, the specific information regarding the parsing failure includes at least one of the following: indication information of the frequency band combination for which the first access network device failed to parse, the frequency band combination being included in the capability information of the terminal device; indication information of the code stream for which the first access network device failed to parse, the code stream being the code stream corresponding to the capability information of the terminal device; or, indication information of the information element or field for which the first access network device failed to parse, the information element or field being included in the capability information of the terminal device.

[0334] In one possible implementation, the types of parsing failures include: the first access network device failing to parse all of the capability information of the terminal device; or, the first access network device failing to parse part of the capability information of the terminal device.

[0335] In one possible implementation, the first information further includes: indication information related to the parsing failure on the network side and / or the terminal device side.

[0336] In one possible implementation, receiving the first information from the first access network device includes: receiving a Radio Resource Control (RRC) release message or an RRC reconfiguration message from the first access network device, wherein the RRC release message or the RRC reconfiguration message includes the first information; or, receiving capability query information from the first access network device, wherein the capability query message is used to instruct the terminal device to report the capability information of the terminal device, and the capability query information includes the first information.

[0337] In one possible implementation, the transceiver unit 8020 is further configured to send request information to the first access network device, the request information being used to request the first information.

[0338] In one possible implementation, the first information further includes: the time information of the parsing failure, and / or the region information of the parsing failure.

[0339] In one possible implementation, the area information where the parsing failed includes: the identifier of the first access network device, and / or the identifier of the manufacturer to which the first access network device belongs.

[0340] When the communication device 8000 is used to implement Figure 7 The specific functions of the first access network device are as follows:

[0341] The processing unit 8010 is used to acquire the capability information of the terminal device; the transceiver unit 8020 is used to send first information to the terminal device, the first information being information about the first access network device's failure to parse the capability information of the terminal device, the first information including: specific information about the parsing failure, and / or the type of the parsing failure.

[0342] In one possible implementation, the specific information regarding the parsing failure includes at least one of the following: indication information of the frequency band combination for which the first access network device failed to parse, the frequency band combination being included in the capability information of the terminal device; indication information of the code stream for which the first access network device failed to parse, the code stream being the code stream corresponding to the capability information of the terminal device; or, indication information of the information element or field for which the first access network device failed to parse, the information element or field being included in the capability information of the terminal device.

[0343] In one possible implementation, the types of parsing failures include: the first access network device failing to parse all of the capability information of the terminal device; or, the first access network device failing to parse part of the capability information of the terminal device.

[0344] In one possible implementation, the first information further includes: indication information related to the parsing failure on the network side and / or the terminal device side.

[0345] In one possible implementation, sending first information to the terminal device includes: sending a Radio Resource Control (RRC) release message or an RRC reconfiguration message to the terminal device, wherein the RRC release message or the RRC reconfiguration message includes the first information; or, sending capability query information to the terminal device, wherein the capability query message is used to instruct the terminal device to report its capability information, and the capability query information includes the first information.

[0346] In one possible implementation, the transceiver unit 8020 is further configured to receive request information from the terminal device, the request information being used to request the first information.

[0347] In one possible implementation, the first information further includes: the time information of the parsing failure, and / or the region information of the parsing failure.

[0348] In one possible implementation, the area information where the parsing failed includes: the identifier of the first access network device, and / or the identifier of the manufacturer to which the first access network device belongs.

[0349] It is understood that the division of units in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. In addition, the functional units in this application embodiment can be integrated into a physical device (e.g., in a processor), or each functional unit can be a separate physical device, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional module, etc.

[0350] like Figure 9 As shown, the communication device 9000 includes a processor 9010 and an interface circuit 9020. The processor 9010 and the interface circuit 9020 are coupled to each other. It is understood that the interface circuit 9020 can be a transceiver or an input / output interface. Optionally, the communication device 9000 may also include a memory 9030 for storing instructions executed by the processor 9010, or storing input data required by the processor 9010 to execute instructions, or storing data generated after the processor 9010 executes instructions.

[0351] When communication device 9000 is used to achieve Figure 4 , Figure 5 , Figure 6 or Figure 7 In the method shown, the processor 9010 is used to implement the functions of the processing unit 8010, and the interface circuit 9020 is used to implement the functions of the transceiver unit 8020.

[0352] When the aforementioned communication device is a chip applied to a terminal device, the chip implements the functions of the terminal device in the above method embodiments. The chip receives information sent to the terminal device by the first access network device or the second access network device through other modules (such as a radio frequency module or antenna) in the terminal device; or, the chip sends information to other modules (such as a radio frequency module or antenna) in the terminal device, which is information sent by the terminal device to the first access network device or the second access network device.

[0353] When the aforementioned communication device is a module applied to a first access network device or a second access network device, the module implements the functions of the first access network device or the second access network device in the above method embodiments. Taking the first access network device as an example: the module receives information from other modules (such as radio frequency modules or antennas) in the first access network device, and this information is sent by the terminal device to the first access network device; or, the module sends information to other modules (such as radio frequency modules or antennas) in the first access network device, and this information is sent by the first access network device to the terminal device. Here, the module of the first access network device can be a chip of the first access network device, or a DU or other modules. Here, the DU can be a DU under the O-RAN architecture.

[0354] This application also provides a communication device, which includes a processor for implementing the above-described embodiments. Figure 4 , Figure 5 , Figure 6 or Figure 7 The communication device includes the functions of a terminal device, a first access network device, or a second access network device. Optionally, the communication device further includes a memory, a processor coupled to the memory, and the processor executing computer programs or instructions stored in the memory to implement the above-mentioned functions. Figure 4 ,Figure 5 , Figure 6 or Figure 7 The communication device may include the functions of a terminal device, a first access network device, or a second access network device. Optionally, the communication device may be a chip or a chip system.

[0355] This application also provides a communication device, including a processor and an interface circuit. The interface circuit is used to receive signals from other devices outside the device and transmit them to the processor, or to send signals from the processor to other devices outside the device. The processor implements the above through logic circuits or executable code instructions. Figure 4 , Figure 5 , Figure 6 or Figure 7 The functions of the terminal equipment, the first access network equipment, or the second access network equipment.

[0356] This application also provides a computer-readable storage medium storing instructions, which may also be referred to as computer programs, computer program code, etc. These instructions, when executed on a computer, cause the computer to perform the aforementioned... Figure 4 , Figure 5 , Figure 6 or Figure 7 The functions of the terminal equipment, the first access network equipment, or the second access network equipment.

[0357] This application also provides a computer program product, including a computer program or instructions, which, when run on a computer, implement the above-described functionality. Figure 4 , Figure 5 , Figure 6 or Figure 7 Figure 4 Figure 5 Figure 6 Figure 7 Figure 4 Figure 5 Figure 6 Figure 7 Figure 4 Figure 5 Figure 6 Figure 7 Figure 4 Figure 5 Figure 6 Figure 7 Figure 4 Figure 5 Figure 6 Figure 7 Figure 4 Figure 5 Figure 6 Figure 7 Figure 4 Figure 5 Figure 6 Figure 7 Figure 4 Figure 5 Figure 6 Figure 7 Figure 4 Figure 5 Figure 6 Figure 7 Figure 4 Figure 5 Figure 6 Figure 7 Figure 4 Figure 5 Figure 6 Figure 7 Figure 4 Figure 5 Figure 6 Figure 7 Figure The functions of the terminal equipment, the first access network equipment, or the second access network equipment.

[0358] It is understood that the processor in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0359] The memory in the embodiments of this application may be random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), register, hard disk, portable hard disk, CD-ROM, or any other form of storage medium known in the art.

[0360] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and the storage medium can reside in an ASIC.

[0361] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. This computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0362] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

Claims

1. A communication method characterized by comprising: The method is applied to a terminal device or a chip of the terminal device, and includes: establishing a radio resource control (RRC) connection with a first access network device; receiving first information from the first access network device or a second access network device, the first information being information about a failure of the RRC connection, and the first information including: a type of the failure of the RRC connection, and / or a cause of the failure of the RRC connection.

2. The method of claim 1, wherein, The type of the failure of the RRC connection includes: the failure of the RRC connection being an abnormality-caused failure of the RRC connection; or the failure of the RRC connection being a non-abnormality-caused failure of the RRC connection.

3. The method of claim 1 or 2, wherein, The cause of the failure of the RRC connection includes at least one of: a radio link failure (RLF) of the first access network device; network congestion of the first access network device; the first access network device failing to correctly decode uplink signaling of the terminal device; the first access network device failing to receive a protocol data unit (PDU) session resource establishment request sent by a core network device; or the first access network device failing to perform RRC configuration on the terminal device.

4. The method of any one of claims 1 to 3, wherein, The failure of the RRC connection is the failure of the first access network device to perform RRC configuration on the terminal device, and the first information includes indication information of at least one of the following: a version or an index of capability information of the terminal device, a first frequency band combination included in the capability information of the terminal device, or a first RRC configuration, the RRC configuration being an incremental configuration based on the first RRC configuration.

5. The method of any one of claims 1 to 4, wherein, The first information further includes indication information about the failure of the RRC connection being related to a network side and / or a terminal device side.

6. The method of any one of claims 1 to 5, wherein, The receiving of the first information from the first access network device includes: receiving an RRC release message from the first access network device, the RRC release message including the first information, the RRC release message being used to release the RRC connection, and the terminal device entering an RRC idle state from an RRC connected state.

7. The method of any one of claims 1 to 5, wherein, The receiving of the first information from the second access network device includes: receiving an RRC reconfiguration message from the second access network device, the RRC reconfiguration message including the first information.

8. The method of any one of claims 1 to 7, wherein, Further including: sending request information to the first access network device or the second access network device, the request information being used to request the first information.

9. The method of any one of claims 1 to 8, wherein, The first information further includes: time information of the failure of the RRC connection, and / or area information of the failure of the RRC connection.

10. The method of claim 9, wherein, The area information of the failure of the RRC connection includes: an identifier of the first access network device, and / or an identifier of a vendor to which the first access network device belongs.

11. A communication method, comprising: The method is applied to a first access network device or a chip of the first access network device, and includes: establishing a radio resource control (RRC) connection with a terminal device; sending first information to the terminal device or a second access network device, the first information being information about a failure of the RRC connection, and the first information including: a type of the failure of the RRC connection, and / or a cause of the failure of the RRC connection.

12. The method of claim 11, wherein, The type of the RRC connection failure comprises: the RRC connection failure is an abnormal RRC connection failure; or the RRC connection failure is a non-abnormal RRC connection failure.

13. The method of claim 11 or 12, wherein, The cause of the RRC connection failure comprises at least one of: Radio link failure (RLF) of the first access network device; Network congestion of the first access network device; The first access network device fails to correctly decode uplink signaling of the terminal device; The first access network device fails to receive a protocol data unit (PDU) session resource establishment request sent by a core network device; or The first access network device fails to perform RRC configuration on the terminal device.

14. The method of any one of claims 11 to 13, wherein, The RRC connection failure is that the first access network device fails to perform RRC configuration on the terminal device, and the first information comprises at least one of the following: indication information of version or index of capability information of the terminal device, a first frequency band combination contained in the capability information of the terminal device, or a first RRC configuration based on an incremental configuration of the first RRC configuration. The first information further comprises: indication information related to a network side and / or the terminal device side.

15. The method of any one of claims 11 to 14, wherein, The first information is sent to the terminal device by:

16. The method of any one of claims 11 to 15, wherein, sending an RRC release message to the terminal device, wherein the RRC release message comprises the first information, and the RRC release message is used to release the RRC connection, and the terminal device enters an RRC non-connected state from an RRC connected state. Further comprising:

17. The method of any one of claims 11 to 16, wherein, receiving request information from the terminal device, wherein the request information is used to request the first information. The first information further comprises: time information of the RRC connection failure, and / or area information of the RRC connection failure.

18. The method of any one of claims 11 to 17, wherein, The area information of the RRC connection failure comprises: an identifier of the first access network device, and / or an identifier of a vendor to which the first access network device belongs.

19. The method of claim 18, wherein, The method is applied to a second access network device or a chip of the second access network device, and comprises:

20. A method of communication, comprising: receiving first information from a first access network device, wherein the first information is information of a radio resource control (RRC) connection failure, the RRC connection is an RRC connection between a terminal device and the first access network device, and the first information comprises: a type of the RRC connection failure, and / or a cause of the RRC connection failure; sending the first information to the terminal device. The type of the RRC connection failure comprises: the RRC connection failure is an abnormal RRC connection failure; or the RRC connection failure is a non-abnormal RRC connection failure.

21. The method of claim 20, wherein, The cause of the RRC connection failure comprises at least one of:

22. The method of claim 20 or 21, wherein, Radio link failure (RLF) of the first access network device; Network congestion of the first access network device; The first access network device fails to correctly decode uplink signaling of the terminal device; The first access network device fails to receive a protocol data unit (PDU) session resource establishment request sent by a core network device; or The first access network device fails to perform RRC configuration on the terminal device. ​ 23. The method of any one of claims 20 to 22, wherein, The RRC connection failure is an RRC configuration failure of the first access network device to the terminal device, and the first information comprises indication information of at least one of the following: a version or index of capability information of the terminal device, a first frequency band combination contained in the capability information of the terminal device, or a first RRC configuration, wherein the RRC configuration is an incremental configuration based on the first RRC configuration.

24. The method of any one of claims 20 to 23, wherein, The first information further comprises indication information that the RRC connection failure is related to a network side and / or a terminal device side.

25. The method of any one of claims 20 to 24, wherein, The first information is sent to the terminal device by: sending an RRC reconfiguration message to the terminal device, wherein the RRC reconfiguration message comprises the first information.

26. The method of any one of claims 20 to 25, wherein, Further comprising: receiving request information from the terminal device, wherein the request information is used to request the first information.

27. The method of any one of claims 20 to 26, wherein, The first information further comprises time information of the RRC connection failure and / or area information of the RRC connection failure.

28. The method of claim 27, wherein, The area information of the RRC connection failure comprises an identifier of the first access network device and / or an identifier of a vendor to which the first access network device belongs.

29. A communications device, characterized by The communication apparatus comprises units for implementing the method according to any one of claims 1 to 10.

30. A communications device, characterized by The communication apparatus comprises a processor configured to cause the communication apparatus to perform the method according to any one of claims 1 to 10.

31. A communications device, characterized by The communication apparatus comprises units for implementing the method according to any one of claims 11 to 19.

32. A communications device, characterized by The communication apparatus comprises a processor configured to cause the communication apparatus to perform the method according to any one of claims 11 to 19.

33. A communications device, characterized by The communication apparatus comprises units for implementing the method according to any one of claims 20 to 28.

34. A communications device, characterized by The communication apparatus comprises a processor configured to cause the communication apparatus to perform the method according to any one of claims 20 to 28.

35. A computer readable storage medium, characterized in that, The computer readable storage medium stores instructions, and when the instructions are executed, the communication apparatus performs the method according to any one of claims 1 to 10, or performs the method according to any one of claims 11 to 19, or performs the method according to any one of claims 20 to 28.

36. A computer program product, characterised in that, The computer program product comprises instructions, and when the instructions are executed, the communication apparatus performs the method according to any one of claims 1 to 10, or performs the method according to any one of claims 11 to 19, or performs the method according to any one of claims 20 to 28.

Images