Communication method and apparatus

Abstract

A communication method and apparatus. The method comprises: when an anomaly occurs in a communication process between a network device and a terminal device, the network device may record information (referred to as anomaly information) corresponding to the anomaly; and the network device may send the recorded anomaly information to the terminal device, for example, the network device may directly send the anomaly information to the terminal device, or the network device may send the anomaly information to the terminal device by means of other network devices. The anomaly information recorded on a network side can assist a terminal device or a server corresponding to the terminal device in accurately and efficiently locating problems and faults occurring in a communication process, thereby optimizing the operating performance of the terminal device during the communication process.

Description

A communication method and apparatus

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202410986481.1, filed on July 22, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] In existing technologies, terminal devices encounter various problems and faults during network communication. Staff can analyze and process the logs recorded by the terminal devices corresponding to these problems and faults to determine the causes and resolve the faults, thereby improving the communication performance of the terminal devices. However, since the logs recorded by the terminal devices only reflect problems on the terminal device side, relying solely on these logs to locate and resolve problems becomes extremely difficult. Therefore, how terminal devices can obtain abnormal information recorded by the network side during network communication is a research direction. Summary of the Invention

[0005] A communication method and apparatus are provided to enable a terminal device to obtain abnormal information of the terminal device recorded by the network side, thereby assisting in determining the cause of the terminal device's fault or abnormality, which is beneficial for optimizing and upgrading the communication process of the terminal device.

[0006] In a first aspect, 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: establishing a communication connection with a first network device; receiving abnormal information from the first network device, wherein the abnormal information is a first abnormal information or a second abnormal information, wherein the first abnormal information is information indicating an abnormality in the communication process between the first network device and the first terminal device, and the second abnormal information is information indicating an abnormality in the communication process between a second network device and the first terminal device, wherein the abnormal information includes at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality.

[0007] Through the above design, the network can assist terminal devices in recording anomalies that occur during communication. Based on the network-side records, terminal devices can accurately locate problems within the network, thereby quickly and efficiently resolving abnormal scenarios and optimizing the performance of terminal devices within the network. For example, the anomaly information recorded by the network can assist in optimizing, upgrading, and modifying terminal device communication, thus preventing similar problems from occurring in subsequent scenarios.

[0008] In one possible implementation, the first exception information is recorded by the first network device, and the second exception information is recorded by the second network device.

[0009] In one possible implementation, the abnormal information is the first abnormal information: the first network device is a first core network device or a first access network device.

[0010] Through the above design, the first network device can record abnormal information during its communication with the first terminal device, and send the corresponding abnormal information, namely the first abnormal information, to the first terminal device, thereby assisting the terminal device in locating the problems that occur in the network.

[0011] In one possible implementation, the abnormal information is the second abnormal information: the first network device is a first core network device, the second network device is a second core network device, or the first core network device is connected to a second access network device; or the first network device is a third access network device, and the second network device is a fourth access network device.

[0012] Through the above design, the second network device can record abnormal information during its communication with the first terminal device, and send the corresponding abnormal information to the second network device, which then sends the second abnormal information to the first terminal device, thereby assisting the terminal device in locating the problem that occurred in the network.

[0013] In one possible implementation, the first abnormal information or the second abnormal information is paging failure information; wherein, the first abnormal information is information indicating that the first network device failed to paging the first terminal device, or, the second network device is the last serving access network device of the first terminal device in the Radio Resource Control (RRC) connected state, and the second abnormal information is information indicating that the last serving access network device failed to paging the first terminal device.

[0014] With the above design, when paging of the first terminal device fails, the first core network device or the last serving access network device can record the paging failure information and send the corresponding paging failure information to the first terminal device, thereby enabling the first terminal device or the corresponding server to analyze and process the paging failure information in order to optimize the network performance of the first terminal device.

[0015] In one possible implementation, the paging failure information includes at least one of the following: the identifier of the first terminal device, the time information of the paging failure, or the area information of the paging failure.

[0016] In one possible implementation, the method further includes: sending a first request, the first request including first information, the first information being used to request the network side to record abnormal information during the communication process between the first terminal device and the network.

[0017] In one possible implementation, the first information includes: information on the first terminal device's ability to receive abnormal information recorded by the network side, and / or, information on the first terminal device requesting the network side to record abnormal information.

[0018] In one possible implementation, the method further includes: receiving a first response in response to the first request, the first response including second information, the second information being used to instruct the network side to enable recording of abnormal information during the communication process between the first terminal device and the network.

[0019] In one possible implementation, the method further includes sending a second request to the first network device, the second request being used to request the first network device to send the abnormal information.

[0020] With the above design, when the first terminal device experiences or detects an anomaly, it can send a second request to the first network device to request the anomaly information recorded by the network side. This allows the first terminal device to obtain the anomaly information in real time, analyze the cause of the problem in a timely manner, and prioritize the network communication performance of the first terminal device.

[0021] Secondly, regarding the first network device side corresponding to the first aspect, with reference to the description of the first aspect, a communication method is provided. The execution subject of the method is the first network device, or a module, unit, or component applied in the first network device, including: establishing a communication connection with a first terminal device; sending abnormal information to the first terminal device, wherein the abnormal information is a first abnormal information or a second abnormal information, wherein the first abnormal information is information indicating an abnormality in the communication process between the first network device and the first terminal device, and the second abnormal information is information indicating an abnormality in the communication process between the second network device and the first terminal device, wherein the abnormal information includes at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality.

[0022] In one possible implementation, the first exception information is recorded by the first network device, and the second exception information is recorded by the second network device.

[0023] In one possible implementation, the abnormal information is the first abnormal information: the first network device is a first core network device or a first access network device.

[0024] In one possible implementation, the abnormal information is the second abnormal information: the first network device is a first core network device, the second network device is a second core network device, or the first core network device is connected to a second access network device; or the first network device is a third access network device, and the second network device is a fourth access network device.

[0025] In one possible implementation, the abnormal information is the second abnormal information, and the method further includes receiving the second abnormal information from the second network device.

[0026] In one possible implementation, the method further includes sending third information to the second network device, the third information being used to instruct the second network device to record abnormal information during the communication process between the second network device and the first terminal device.

[0027] In one possible implementation, the first abnormal information or the second abnormal information is paging failure information; wherein, the first abnormal information is information indicating that the first network device failed to paging the first terminal device, or, the second network device is the last serving access network device of the first terminal device in the Radio Resource Control (RRC) connected state, and the second abnormal information is information indicating that the last serving access network device failed to paging the first terminal device.

[0028] In one possible implementation, the paging failure information includes at least one of the following: the identifier of the first terminal device, the time information of the paging failure, or the area information of the paging failure.

[0029] In one possible implementation, the method further includes: receiving a first request from the first terminal device, the first request including first information, the first information being used to request the network side to record abnormal information during the communication process between the first terminal device and the network.

[0030] In one possible implementation, the first information includes: information on the first terminal device's ability to receive abnormal information recorded by the network side, and / or, information on the first terminal device's request for the network side to record abnormal information.

[0031] In one possible implementation, the method further includes: sending a first response to the first terminal device, the first response being a response to the first request, the first response including second information, the second information being used to instruct the network side to enable recording of abnormal information during the communication process between the first terminal device and the network.

[0032] In one possible implementation, the method further includes: receiving a second request from the first terminal device, the second request being used to request the first network device to send the abnormal information.

[0033] Thirdly, regarding the second network device side corresponding to the first aspect, with reference to the description of the first aspect, a communication method is provided. The execution subject of the method is the second network device, or a module, unit, or component applied in the second network device, including: sending second abnormal information to the first network device. The second abnormal information is information indicating that an abnormality has occurred in the communication process between the second network device and the first terminal device. The second abnormal information includes at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality.

[0034] In one possible implementation, the second anomaly information is recorded by the second network device.

[0035] In one possible implementation: the first network device is a first core network device, the second network device is a second core network device, or the first core network device is connected to a second access network device; or the first network device is a third access network device, and the second network device is a fourth access network device.

[0036] In one possible implementation, the second abnormal information is paging failure information; wherein, the second network device is the last serving access network device of the first terminal device in the Radio Resource Control (RRC) connected state, and the second abnormal information is information indicating that the last serving access network device failed to paging the first terminal device.

[0037] In one possible implementation, the paging failure information includes at least one of the following: the identifier of the first terminal device, the time information of the paging failure, or the area information of the paging failure.

[0038] In one possible implementation, the method further includes: receiving third information from the first network device, the third information being used to instruct the second network device to record abnormal information during the communication process between the second network device and the first terminal device.

[0039] In one possible implementation, the method further includes receiving fourth or fifth information from a third network device, wherein the fourth or fifth information is used to instruct the second network device to record abnormal information during the communication process between the second network device and the first terminal device.

[0040] In one possible implementation, the method further includes: receiving a first request from the first terminal device, the first request including first information, the first information being used to request the network side to record abnormal information during the communication process between the first terminal device and the network.

[0041] In one possible implementation, the first information includes: information on the first terminal device's ability to receive abnormal information recorded by the network side, and / or, information on the first terminal device's request for the network side to record abnormal information.

[0042] In one possible implementation, the method further includes: sending a first response to the first terminal device, the first response being a response to the first request, the first response including second information, the second information being used by the network side to enable recording of abnormal information during the communication process between the first terminal device and the network.

[0043] Fourthly, a communication method is provided, wherein the execution subject of the method is a server, or a module, unit, or component applied in the server, comprising: receiving abnormal information from a first network device, wherein the abnormal information is a first abnormal information or a second abnormal information, wherein the first abnormal information is information indicating an abnormality in the communication process between the first network device and a first terminal device, and the second abnormal information is information indicating an abnormality in the communication process between a second network device and the first terminal device, wherein the abnormal information includes at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality.

[0044] Through the above design, the first network device sends the abnormal information recorded on the network side to the server corresponding to the terminal device through other interfaces besides the air interface. The server corresponding to the terminal device then performs unified analysis and processing of the abnormal information, saving air interface transmission resources. Furthermore, in Embodiment 2, the terminal device does not need to have the function of processing and analyzing abnormal information. The network side can record the abnormal information of any terminal device and send it to the server of the terminal device for analysis and / or processing, reducing the implementation complexity on the terminal device side.

[0045] In one possible implementation, the first abnormal information or the second abnormal information is paging failure information; wherein, the first abnormal information is information indicating that the first network device failed to paging the first terminal device, or, the second network device is the last serving access network device of the first terminal device in the Radio Resource Control (RRC) connected state, and the second abnormal information is information indicating that the last serving access network device failed to paging the first terminal device.

[0046] In one possible implementation, the paging failure information includes at least one of the following: the identifier of the first terminal device, the time information of the paging failure, or the area information of the paging failure.

[0047] Fifthly, regarding the first network device side corresponding to the fourth aspect, with reference to the description of the fourth aspect, a communication method is provided. The execution subject of the method is the first network device, or it is applied to a module, unit, or component in the first network device, including: recording first abnormal information, wherein the first abnormal information is information about an abnormality that occurs during communication between the first network device and the first terminal device; wherein the first abnormal information includes at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality.

[0048] In one possible implementation, the first abnormal information is paging failure information; wherein, the first abnormal information is information indicating that the first network device failed to paging the first terminal device.

[0049] In one possible implementation, the paging failure information includes at least one of the following: the identifier of the first terminal device, the time information of the paging failure, or the area information of the paging failure.

[0050] Sixthly, regarding the second network device side corresponding to the fourth aspect, with reference to the description of the fourth aspect, a communication method is provided. The execution subject of the method is the second network device, or it is applied to a module, unit, or component in the second network device, including: recording second abnormal information, the second abnormal information being information about an abnormality occurring during the communication process between the second network device and the first terminal device; wherein, the second abnormal information includes at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality.

[0051] In one possible implementation, the second abnormal information includes: paging failure information; wherein, the second network device is the last serving access network device of the first terminal device in the Radio Resource Control (RRC) connected state, and the second abnormal information is information indicating that the last serving access network device failed to paging the first terminal device.

[0052] In one possible implementation, the paging failure information includes at least one of the following: the identifier of the first terminal device, the time information of the paging failure, or the area information of the paging failure.

[0053] In a seventh aspect, an apparatus is provided capable of implementing the method of the first aspect described above. For example, the apparatus includes modules, units, or components that perform the method described in the first aspect. Specifically, 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 method described in the first aspect.

[0055] In one design, the device includes a processor for implementing the method of the first 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, such that the device implements the method of the first 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 method of the first 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] Eighthly, an apparatus is provided capable of implementing the methods described in the second / fifth aspects above. For example, the apparatus includes modules, units, or components corresponding to the methods described in the second / fifth aspects above. Specifically, 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 / fifth aspects.

[0060] In one design, the device includes a processor for implementing the methods of the second / fifth aspects 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, such that the device implements the methods of the second / fifth aspects 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 / fifth aspects 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 / fifth aspects in the second device, or a device that can be used in conjunction with the second device.

[0063] Ninthly, an apparatus is provided capable of implementing the methods of the third / sixth aspects described above. For example, the apparatus includes modules, units, or components corresponding to the methods described in the third / sixth aspects. 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 methods described in the third / sixth aspect above.

[0065] In one design, the device includes a processor for implementing the methods of the third / sixth 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, such that the device implements the methods of the third / sixth aspect described above.

[0066] 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 third / sixth 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.) corresponding one-to-one with the method / operation / step / action described in the third / sixth aspect of the third device, or a device that can be used in conjunction with the second device.

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

[0069] In one design, the device includes a unit that performs the method described in the fourth aspect above.

[0070] In one design, the device includes a processor for implementing the method of the 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, such that the device implements the method of the fourth aspect described above.

[0071] 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 fourth aspect described above through logic circuits or executing code instructions.

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

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

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

[0075] In a thirteenth aspect, 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.

[0076] In a fourteenth aspect, a communication system is provided, comprising: a first communication device and a second communication device; further comprising: a third 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, the third communication device 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; the second communication device is used to implement the method of the fifth aspect; optionally, the third communication device is used to implement the method of the sixth aspect. Attached Figure Description

[0077] Figure 1 is a schematic diagram of the communication system provided in an embodiment of this application;

[0078] Figure 2 is a schematic diagram of the ORAN system provided in an embodiment of this application;

[0079] Figure 3 is a schematic diagram of the access network equipment provided in an embodiment of this application;

[0080] Figures 4, 5 and 6 are schematic flowcharts of the communication method provided in this application;

[0081] Figures 7 and 8 are paging diagrams provided in the embodiments of this application;

[0082] Figure 9 is a schematic diagram of the architecture provided in an embodiment of this application;

[0083] Figures 10 and 11 are schematic diagrams of the structure of the device provided in the embodiments of this application. Detailed Implementation

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

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

[0086] 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, performing some operations under "a condition" can be replaced with performing some operations after "a condition". For example, recording the abnormal information of the first terminal device when receiving the instruction of the third information can be replaced with recording the abnormal information of the first terminal device after receiving the instruction of the third information.

[0087] Figure 1 illustrates a possible, non-limiting system diagram. As shown in Figure 1, 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.

[0088] RAN100 includes at least one RAN node (110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal device (120a-120j in Figure 1, collectively referred to as 120). RAN100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1).

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

[0090] 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 a future communication network). RAN100 can also be an open access network (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.

[0091] 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, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminal devices 120j accessing RAN 100 through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal device.

[0092] 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. A RAN node can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, a RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment 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 through software functions running on hardware, or through 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.

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

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

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

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

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

[0098] RAN node 110 and terminal equipment 120 are sometimes referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functions. For instance, this 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 instance, this communication device can be a terminal equipment, or a module, unit, or component applied to a terminal equipment.

[0099] The solution of this application embodiment can be applied to the communication system 1000 shown in Figure 1, which can correspond to a terrestrial network (TN). Alternatively, the solution of this application embodiment can also be applied to a non-terrestrial network (NTN). In the NTN communication system, the "RAN node" in Figure 1 can be replaced by "satellite and ground station". The satellite is deployed in space, and the ground station is deployed on the ground. The ground station can be understood as a base station deployed on the ground, and 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. The satellite's operating modes include transparent and regenerative.

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

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

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

[0103] 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".

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

[0105] Figure 2 illustrates a possible, non-limiting ORAN system. As shown in Figure 2, 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.

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

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

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

[0109] As shown in Figure 3, 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 possess 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.

[0110] 1. CU

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

[0112] Furthermore, the CU can be divided into CU-CP and CU-UP. Referring to Figure 3, CU-CP is a logical node carrying the control plane (control plane part of PDCP, PDCP-C) of the RRC and PDCP layers, used to implement the CU's control plane functions. 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. Continuing to refer to Figure 3, CU-UP is a logical node carrying the data plane (user plane part of PDCP, PDCP-U) of the SDAP and PDCP layers, used to implement the CU's user plane functions. 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.

[0113] 2. DU

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

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

[0116] 3. RU

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

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

[0119] The DU and RU can be co-located or non-co-located, without restriction. Referring to Figure 3, the O-RAN control user and synchronization (CUS-Plane) and management plane (M-Plane) can be included between the DU and RU. The O-RAN CUS plane can be simply referred to as the CUS plane, and the O-RAN management plane can be simply referred to 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.

[0120] Referring to Figure 3, the DU and RU exchange control plane and user plane information via the lower-layer split CUS-Plane (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. Referring to Figure 3, the LLS-M interface can also connect to an external management system.

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

[0122] During communication, terminal devices encounter various problems and faults. A common solution is as follows: Staff simulate the terminal device's communication environment and test it under this environment, obtaining test logs. Based on the test logs, problems are located, and the terminal device's communication is optimized and / or upgraded. However, since the test logs on the terminal device side only reflect problems on that side, some problems and faults may not be caused by the terminal device itself. For example, they might be caused by the network side, or by a combination of both. Furthermore, the terminal device may not be aware of some problems and faults, such as missed paging. Therefore, some problems and faults cannot be identified based solely on the terminal device's test logs. Additionally, the solution of simulating the terminal device's communication environment for testing also suffers from high costs and long processing times. It can be seen that relying solely on the test logs recorded on the terminal device side may result in inaccurate problem and fault location and low efficiency in problem-solving.

[0123] In view of the above, embodiments of this application provide a communication method and apparatus. In this method: when an anomaly occurs during communication between a network device and a terminal device, the network device can record information corresponding to the anomaly (hereinafter referred to as an anomaly information); the network device can send the recorded anomaly information to the terminal device; for example, the network device can directly send the anomaly information to the terminal device, or the network device can send the anomaly information to the terminal device through other network devices. The anomaly information recorded on the network side can assist the terminal device or the server corresponding to the terminal device in accurately and efficiently locating problems and faults occurring during communication, thereby optimizing the working performance of the terminal device during communication.

[0124] In the various flowcharts of the embodiments of this application, the executing entity can be a terminal, a network device (access network device or core network device), or a module, unit, or component (e.g., chip, chip system, processor, circuit, or others) within the terminal or network device. The following description uses a terminal and a network device as examples of executing entities. When the executing entity is a module, unit, or component within the terminal / network device, receiving / transmitting can be understood as input / output, that is, the module communicates with other modules or components of the terminal or 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 an access network device can be divided among at least one of a CU, DU, RU, etc.

[0125] Example 1

[0126] Figure 4 is a schematic interactive diagram of the communication method 4000 provided in an embodiment of this application. It is understood that steps 410 and 420 are only for illustrating the process of the communication method 4000 and should not be construed as limiting the method 4000. Steps 410 and 420 can be broken down into more steps or combined into fewer steps, and the order of steps 410 and 420 is not limited.

[0127] Step 410: The first terminal device establishes a communication connection with the first network device.

[0128] The first network device can be a core network device or an access network device. When the first network device is a core network device, the process of establishing a communication connection between the first terminal device and the first network device includes: the first terminal device establishing an RRC connection with the access network device connected to the core network device, and the first terminal device receiving abnormal information sent by the core network device through the access network device. Alternatively, when the first network device is an access network device, the process of establishing a communication connection between the first terminal and the first network device includes: the first terminal device establishing an RRC connection with the access network device, and the first terminal device receiving abnormal information sent by the access network device.

[0129] Step 420: The first network device sends an error message, and the first terminal device receives the error message.

[0130] In the description of the embodiments of this application, abnormal information can be replaced by: abnormal log, fault information, fault log, failure information, or failure log, etc. Abnormal information includes at least one of the following:

[0131] 1. Identification of the first terminal device.

[0132] The identifier of the first terminal device is used to identify the first terminal device. For example, the identifier of the first terminal device can be a globally unique identifier, such as the International Mobile Subscriber Identity (IMSI). Alternatively, the identifier of the first terminal device can be a temporary identifier of the terminal device, such as the Temporary Mobile Subscriber Identity (TMSI).

[0133] 2. Information on the cause of the anomaly.

[0134] In the description of the embodiments of this application, the cause information of the anomaly can be replaced with the type and category of the anomaly. The cause information of the anomaly is used to indicate what type / category of anomaly occurred in the first terminal device during communication. For example, a non-access stratum (NAS) anomaly, or an access stratum anomaly; for example, a core network anomaly, or an access network anomaly; for example, a NAS connection anomaly, or an RRC connection anomaly. Furthermore, when scenarios such as RRC connection establishment / reconstruction failure, RRC connection reconfiguration failure, RRC connection recovery failure, handover failure, wireless link failure, or paging failure occur, the network device records the cause of the aforementioned anomaly / failure.

[0135] It is understandable that core network devices can record anomaly information related to non-access network layers. For example, the connection between the core network device and the first terminal device is a NAS connection: when the NAS of the first terminal device experiences an anomaly, the core network device can record the information corresponding to the NAS anomaly. Access network devices can record anomaly information related to the access layer. For example, the connection between the access network device and the first terminal device is called an RRC connection: when the RRC connection of the first terminal device experiences an anomaly, the access network device can record the anomaly information corresponding to the RRC connection. When the first terminal device is in the RRC idle state, the core network device initiates a paging of the first terminal device: if the paging of the first terminal device fails, the core network device records the information corresponding to the paging failure, which can be called paging failure information. Alternatively, when the first terminal device is in the RRC inactive state, the last serving access network device initiates a paging of the first terminal device: if the paging of the first terminal device fails, the last serving access network device can record or collect the information corresponding to the paging failure.

[0136] 3. Abnormal time information.

[0137] The specific time information of the anomaly refers to the time when the first terminal device experienced an anomaly. For example, the time information could refer to a specific moment, such as at time A, the first terminal device experienced an anomaly. Alternatively, the time information could refer to a time period, such as during time period B, the first terminal device experienced an anomaly. Or, the time information could refer to a time range, such as between time C and time D, the first terminal device experienced an anomaly, etc.

[0138] 4. Abnormal area information.

[0139] The abnormal area information can refer to the area where the first terminal device is camped when the abnormality occurs. For example, the identifier of the access network device camped when the first terminal device is camped, or the identifier of the cell camped when the first terminal device is camped, such as the physical cell identifier (PCI), or the radio access network notification area (RNA) or tracking area (TA) where the first terminal device is camped when the abnormality occurs.

[0140] Understandably, the first network device can record, store, and maintain the correspondence between the terminal device's identifier and abnormal information. The first network device then sends the abnormal information to the corresponding terminal device.

[0141] The abnormal information includes first abnormal information and / or second abnormal information. In the description of the embodiments of this application, the abnormal information includes at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality. Specifically, the first abnormal information and / or the second abnormality includes at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality.

[0142] It is understood that the first abnormal information may be information indicating an abnormality in the communication process between the first network device and the first terminal device. Optionally, the first abnormal information is recorded by the first network device. The second abnormal information is information indicating an abnormality in the communication process between the second network device and the first terminal device. Optionally, the second abnormal information is recorded by the second network device. It is understood that an abnormality in the communication process between the first network device or the second network device and the first terminal device can specifically refer to an abnormality occurring during the transmission of uplink and / or downlink information between the first network device or the second network device and the first terminal device. The scenarios for this abnormality may include scenarios where an abnormality occurs when paging the first terminal device, for example, the paging of the first terminal device fails.

[0143] In this application embodiment, the solution of this application embodiment is described in conjunction with the following two scenarios:

[0144] Scenario 1: The first network device sends the first abnormal information, and the first terminal device receives the first abnormal information. In this case, the "abnormal information" in the process of Figure 4 specifically refers to the "first abnormal information".

[0145] For example, when an anomaly occurs during communication between the first network device and the first terminal device, the first network device records the information corresponding to the anomaly (referred to as the first anomaly information) and sends the first anomaly information to the first terminal device.

[0146] In one possible implementation, the first network device can be a first core network device. For example, when an anomaly occurs during communication between the first core network device and the first terminal device, the first core network device records the first anomaly information corresponding to the anomaly. The first core network device sends the first anomaly information to the first terminal device. For example, the first anomaly information can be carried in a NAS message or an RRC message. In a paging scenario, the first anomaly information can be paging failure information, as explained in Figure 7 below.

[0147] In another possible implementation, the first network device can be a first access network device. For example, when an anomaly occurs during communication between the first access network device and the first terminal device, the first access network device records the first anomaly information corresponding to the anomaly. The first access network device sends the first anomaly information to the first terminal device. For example, the first anomaly information can be carried in an RRC message.

[0148] Scenario 2: The second network device sends a second abnormality message, the first network device receives the second abnormality message, and the first network device forwards the second abnormality message to the first terminal device, which then receives the second abnormality message. Furthermore, the first network device can also send its recorded first abnormality message to the first terminal device. In this case, the "abnormality message" in the flowchart of Figure 4 can be replaced with "second abnormality message," or "second abnormality message and first abnormality message."

[0149] For example, when an anomaly occurs during communication between the second network device and the first terminal device, the second network device records the information corresponding to the anomaly (referred to as the second anomaly information), and sends the second anomaly information to the first network device, which in turn sends the second anomaly information to the first terminal device. Further, optionally, the first network device may also send its own recorded first anomaly information to the first terminal device.

[0150] In one possible implementation, the first network device is a first core network device, and the second network device is a second core network device. For example, when an anomaly occurs during communication between the second core network device and the first terminal device, the second core network device records the second anomaly information corresponding to the anomaly. The second core network device can send the second anomaly information to the first core network device through a corresponding interface. The first core network device sends anomaly information including the second anomaly information to the first terminal device. Further, when an anomaly occurs during communication between the first core network device and the first terminal device, the first core network device can record the first anomaly information corresponding to the anomaly. The anomaly information sent by the first core network device to the first terminal device also includes the first anomaly information. For example, the anomaly information can be carried in a NAS message or an RRC message.

[0151] In another possible implementation, the first network device is a first core network device, and the second network device is a second access network device connected to the first core network device. An interface, such as an NG interface, exists between the first core network device and the second access network device. When an exception occurs during communication between the second access network device and the first terminal device, the second access network device records the corresponding second exception information. The second access network device sends the second exception information to the first core network device through the corresponding interface. The first core network device sends exception information, including the second exception information, to the first terminal device. Furthermore, this exception information also includes the first exception information recorded by the first core network device. For example, the exception information can be carried in a NAS message or an RRC message. For details on this implementation, please refer to Figure 5 below.

[0152] In another possible implementation, the first network device is a third access network device, and the second network device is a fourth access network device. An interface exists between the third and fourth access network devices, such as an Xn interface. When an exception occurs during communication between the fourth access network device and the first terminal device, the fourth access network device records the second exception information corresponding to the exception. The fourth access network device sends the second exception information to the third access network device through the corresponding interface. The third access network device sends exception information including the second exception information to the first terminal device. Further, this exception information also includes the first exception information recorded by the third access network device. For example, the exception information can be carried in an RRC message. For this implementation, please refer to Figure 6 below. In a paging scenario, the second exception information is paging failure information, as described in Figure 8 below.

[0153] The following continues to explain step 420 in the flowchart of Figure 4, the process by which the first network device sends an exception message to the first terminal device:

[0154] In one possible implementation, the first network device may proactively send exception information to the first terminal device. For example, the first network device may send exception information to the terminal device upon detecting an anomaly in the first terminal device or upon receiving second exception information from the second network device. Alternatively, the first network device may periodically send exception information to the first terminal device, without limitation. Alternatively, upon receiving a request (which may be called a second request) from the first terminal device, the first network device may send exception information to the first terminal device based on the second request. For example, the first terminal device may send a second request to the first network device, requesting the first network device to send exception information. Upon receiving the second request, the first network device sends exception information to the first terminal device. For example, if an anomaly occurs in the first terminal device, it sends the second request to the first network device.

[0155] The following describes the process by which the first network device and the second network device enable (or activate) the recording of abnormal information from the first terminal device:

[0156] In one possible implementation, the first terminal device may send a request (referred to as a first request) to a first network device and / or a second network device to request the network side to record abnormal information during the communication process between the first terminal device and the network. Upon receiving the first request, the network-side device performs the operation of recording the abnormal information during the communication process of the first terminal device. Then, through step 420, the abnormal information recorded by the network side is sent to the first terminal device. For example, before step 420, the method may further include: the first terminal device sending a first request, which includes first information used to request the network side to record abnormal information during the communication process between the first terminal device and the network. For example, the first information may specifically include: the first terminal device's ability to receive the abnormal information recorded by the network side, and / or, the first terminal device's request information for the network side to record the abnormal information, etc. Further, optionally, the first terminal device receives a first response, which responds to the first request. The first response includes second information used to instruct the network side to enable ("enable" can also be replaced by: start, support, allow, agree, confirm, etc.) the recording of abnormal information during the communication process between the first terminal device and the network. It is understandable that enabling the recording of abnormal information during the communication process between the first terminal device and the network on the network side can be replaced by: the network side turning on a switch to record abnormal information of the first terminal device, or the network side enabling the feature to record abnormal information of the first terminal device, or the network side supporting the function of recording abnormal information of the first terminal device. The following three examples illustrate this:

[0157] Example 1: A first terminal device sends a first request to a first network device. Upon receiving the first request, the first network device allows or agrees to the request, that is, agrees to record the abnormal information of the first terminal device. The first network device may send a first response to the first terminal device, which is used to notify the first terminal device that the first network device allows or agrees to record the abnormal information of the first terminal device.

[0158] Further, optionally, the first network device may also send third information to the second network device, which instructs the second network device to record abnormal information during communication between the second network device and the first terminal device. Optionally, the description of the third information may also be replaced with: the third information instructs the second network device to enable recording of abnormal information of the first terminal device; or, the third information instructs the second network device to enable recording of abnormal information of the first terminal device; or, the third information instructs the second network device to turn on the switch for recording abnormal information of the first terminal device; or, the third information instructs the second network device to turn on the switch for recording abnormal information of the first terminal device; or, the third information instructs the second network device to enable the characteristic of recording abnormal information of the first terminal device; or, the third information instructs the second network device to enable the characteristic of recording abnormal information of the first terminal device, etc. In one possible implementation, the third information includes the identifier of the first terminal device, and is used to instruct the second network device which terminal devices' abnormal information to record. That is, the first terminal device sends a first request to the first network device to request the network side to record the first terminal device's abnormal information. The first network device records the first abnormal information of the first terminal device according to the first request. The first network device also instructs the second network device to record the first terminal device's abnormal information. In a typical application scenario, the first network device can be a first core network device, and the second network device can be a second access network device connected to the first core network device, as can be seen in the explanation of step 530 in the process of Figure 5 below.

[0159] Example 2: A first terminal device sends a first request to a second network device. Upon receiving the first request, the second network device allows or agrees to the request, i.e., agrees to record the abnormal information of the first terminal device. The second network device may send a first response to the first terminal device, which notifies the first terminal device that the second network device allows or agrees to record the abnormal information of the first terminal device. It is understood that the second network device may send its recorded second abnormal information to the first network device, and the first network device may forward the second abnormal information to the first terminal device. Alternatively, the second network device may directly send the second abnormal information to the first terminal device, etc., without restriction. Alternatively, a third network device may send fourth / fifth information to the second network device, which instructs the second network device to record abnormal information during the communication process between the second network device and the first terminal device. For example, in a scenario where an access network device initiates a paging process: the third network device can be a core network device, and the second network device is the access network device corresponding to the RNA or the last serving access network device: the core network device sends the fourth information to the access network device corresponding to the RNA or the last serving access network device respectively; or, the third network device is the last serving access network device, and the second network device is the access network device corresponding to the RNA: the last serving access network device sends the fifth information to the access network device corresponding to the RNA, as detailed in Figure 8.

[0160] Example 3: Examples 1 and 2 above can be combined. The first terminal device sends a first request to both the first and second network devices, requesting them to record any abnormal information during the communication process between the first terminal device and the network. The first network device agrees to the first request and sends a first response to the first terminal device. The first network device records the abnormal information (first abnormal information) that occurred during the communication process of the first terminal device. The first network device sends the first abnormal information to the first terminal device. The second network device agrees to the first request and sends a first response to the first terminal device. The second network device records the abnormal information (second abnormal information) that occurred during the communication process of the first terminal device. The second network device sends the second abnormal information to the first network device, and the first network device forwards the second abnormal information to the first terminal device. Alternatively, the second network device can directly send the second abnormal information to the first terminal device, without restriction.

[0161] In the above scheme, the first terminal device can be any terminal device. That is, any terminal device that wants to obtain abnormal information recorded by the network side can send a first request to request the network side to start recording its abnormal information. Alternatively, the first terminal device can be a specific terminal (or a special terminal). In this method, the specific terminal device collects the abnormal information recorded by the network side. For example, the terminal device manufacturer specifies that a specific test terminal device should be used to collect abnormal information. In this case, the first terminal device is a terminal device with a special user identity, or the first terminal device can access the first network device using a specific key. When the first network device detects the access of the specific terminal device, it can actively enable the recording of the abnormal information of that specific terminal device.

[0162] Optionally, in step 420, when the first terminal device receives the abnormal information, it has the following two processing methods:

[0163] 1) The first terminal device analyzes and processes the abnormal information for subsequent optimization or upgrades of the communication of the first terminal device.

[0164] 2) The first terminal device sends the abnormal information to the server corresponding to the first terminal device. The server analyzes and processes the abnormal information in a unified manner for subsequent optimization or upgrade of the terminal device's communication.

[0165] In one possible implementation, the first network device is a first core network device, and the second network device is a second access network device connected to the first core network device. The process in Figure 4 is illustrated below:

[0166] For example, a first terminal device may send a first request to a first core network device, which requests the network side to record abnormal information of the first terminal device. The first core network device agrees to or allows the request of the first terminal device and sends a first response to the first terminal device. When an abnormality occurs during communication between the first terminal device and the first core network device, the first core network device records the information corresponding to the abnormality (referred to as first abnormality information). The first core network device sends the recorded first abnormality information to the first terminal device. Optionally, the second network device may be a second access network device connected to the first core network device. After receiving the first request and / or sending the first response, the first core network device may also: send third information to the second access network device, which instructs the second access network device to record abnormal information during communication between the second access network device and the first terminal device. The second access network device records the abnormal information during its communication with the first terminal device (referred to as second abnormality information), and sends the second abnormality information to the first core network device, which then sends the second abnormality information to the first terminal device, as shown in Figure 5.

[0167] Figure 5 is a schematic interactive diagram of the communication method 5000 provided in an embodiment of this application. It is understood that steps 510 to 580 are only for illustrating the process of the communication method 5000 and should not be construed as limiting the method 5000. Steps 510 to 580 can be broken down into more steps or combined into fewer steps, and the order of steps 510 to 580 is not limited.

[0168] Step 510: The first terminal device sends a first request, and the first core network device receives the first request.

[0169] Step 520: The first core network device sends a first response, and the first terminal device receives the first response.

[0170] Optionally, the first core network device can be an access and mobility function (AMF) network element, such as an AMF network element in a 5G system. The AMF network element is responsible for mobility management in the mobile network, such as location updates for terminal devices, network registration for terminal devices, or handover of terminal devices.

[0171] In one possible implementation, during the process of the first terminal device accessing the first core network device: the first request sent by the first terminal device includes first information, which requests the network side to record abnormal information during the communication process between the first terminal device and the network. The specific content of the first information can be found in the preceding description. In response to the first request, the first core network device sends a first response to the terminal device. The first response includes second or fifth information. The second information instructs the network side to enable recording of abnormal information during the communication process between the first terminal device and the network device, and the fifth information instructs the network side not to enable recording of abnormal information during the communication process between the first terminal device and the network device. For example, the second or fifth information can be represented by 1 bit of binary data, such as the second information represented by binary data "1" and the fifth information represented by binary data "0," etc., without limitation. Alternatively, if the first core network device agrees to or allows the recording of abnormal information of the first terminal device, the first core network device sends a first response to the first terminal device; otherwise, it does not send a first response to the first terminal device. In this case, there is no limitation on whether the first response includes the second information.

[0172] In another possible implementation, the first terminal device is a specific terminal device. When the first core network device detects the access of the first terminal device, it can proactively enable the recording of abnormal information of the first terminal device. For example, during the process of the first terminal device accessing the first core network device: the first request sent by the first terminal device carries the identifier of the first terminal device. Based on the identifier of the first terminal device carried in the first request, the first core network device can determine that the first terminal device is a specific terminal, thereby enabling the network side to record the abnormal information of the first terminal device. And / or, the first request sent by the first terminal device is encrypted using a specific key. During the process of decrypting the first request, the first core network device can determine that the first terminal device is a specific terminal device, thereby enabling the network side to record the abnormal information of the first terminal device.

[0173] Optionally, the first request can be a registration request, and the first response can be a registration response. Alternatively, the first request and the first response can be other messages, without restriction. For example, the first request and the first response can be other messages from the first terminal device during the access phase of the first core network device.

[0174] In this embodiment, when the first core device allows or agrees to record abnormal information of the first terminal device: when an abnormality occurs during communication between the first terminal device and the first core network device, the first core network device can record the information corresponding to the abnormality, i.e., the first abnormality information. The first core network device then sends the recorded first abnormality information to the first terminal device.

[0175] Optionally, the process in Figure 5 may further include steps 530 to 550: The first core network device sends third information to the second access network device connected to it, instructing the second access network device to record the abnormal information of the first terminal device. When an abnormality occurs during communication between the first terminal device and the second access network device, the second access network device records the information corresponding to the abnormality, referred to as the second abnormal information. The second access network device can send the recorded second abnormal information to the first core network device, and the first core network device forwards the second abnormal information to the first terminal device.

[0176] Step 530: The first core network device sends third information to the second access network device connected to it, and the second access network device receives the third information.

[0177] For example, the third information includes the identifier of the first terminal device. The first core network device instructs the second access network device to record the abnormal information of the first terminal device through the third information. When / after receiving the third information, the second access network device records the abnormal information of the first terminal device according to the identifier of the first terminal device carried in the third information.

[0178] Step 540: When an abnormality occurs during the communication between the first terminal device and the second access network device, the second access network device records the second abnormality information corresponding to the abnormality.

[0179] For example, the second access network device can record abnormal information related to the access layer of the first terminal device. The abnormal information recorded by the second access network device may include: an RRC connection abnormality of the first terminal device, and / or, a paging failure of the first terminal device, etc. Optionally, regarding the paging failure of the first terminal device recorded by the second access network device, the paging of the first terminal device may be initiated by the second access network device. Optionally, the second abnormal information includes at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality, etc.

[0180] Step 550: The second access network device sends the second abnormal information, and the first core network device receives the second abnormal information.

[0181] Step 560: When an anomaly occurs during the communication between the first terminal device and the first core network device, the first core network device records the first anomaly information corresponding to the anomaly.

[0182] For example, the first core network device can record non-access stratum related anomaly information of the first terminal device. The first anomaly information recorded by the first core network device may be: NAS anomaly of the first terminal device, and / or paging failure of the first terminal device, etc. Optionally, for the paging failure recorded by the first core network device, the paging of the first terminal device may be initiated by the first core network device. Optionally, the first anomaly information includes at least one of the following: the identifier of the first terminal device, the cause information of the anomaly, the time information of the anomaly, or the area information of the anomaly, etc.

[0183] In one possible implementation, the first core network device may proactively send first and / or second anomaly information to the first terminal device. Alternatively, the first terminal device may send a second request to the first core network device, requesting the first core network device to send anomaly information. Upon receiving the second request, the first core network device sends the anomaly information to the first terminal device.

[0184] Optionally, in step 570: the first terminal device sends a second request, and the first core network device receives the second request.

[0185] Step 580: The first core network device sends an abnormality message, and the first terminal device receives the abnormality message.

[0186] The abnormal information includes first abnormal information and / or second abnormal information. For example, after the first terminal device successfully connects to the first core network device, the first core network device sends abnormal information to the first terminal device. For example, when the first terminal device establishes an RRC connection with an access network device connected to the first core network device, the first core network device sends abnormal information to the first terminal device through that access network device.

[0187] In one possible implementation, the exception information can be carried in a NAS message. For example, a first core network device sends a NAS message containing exception information. An access network device connected to the first core network device can then forward the NAS message to a first terminal device. Alternatively, the exception information can be carried in an RRC message. For example, the first core network device sends a message containing a container carrying an RRC message. When the access network device connected to the first core network device receives this message, it parses the message to obtain the RRC message carried in the container. The access network device then sends an RRC message containing exception information to the first terminal device.

[0188] In one possible implementation, the first core network device may use a separate billing mechanism for the first terminal device. For example, separate billing may be performed for the first core network device recording and sending first abnormal information, and / or separate billing may be performed for the second access network device recording and sending second abnormal information.

[0189] Understandably, in the process shown in Figure 5: the second access network device records the second anomaly information and sends it to the first core network device through the interface between the second access network device and the first core network device. The first core network device then sends the second anomaly information to the first terminal device. For example, the interface between the second access network device and the first core network device can be an NG interface. Alternatively, the second access network device can directly send the second anomaly information to the first terminal device through a corresponding interface. For example, the interface between the second access network device and the first terminal device can be an air interface. For instance, after the first terminal device connects to the second access network device, for example, after the first terminal device establishes an RRC connection with the second access network device, the second access network device can send the second anomaly information to the first terminal device through the air interface.

[0190] In the above design, the network can assist terminal devices in recording anomalies that occur during communication. Based on the network-side records, terminal devices can accurately locate problems within the network, thereby quickly and efficiently resolving abnormal scenarios and optimizing terminal device performance within the network. For example, the anomaly information recorded by the network can assist in optimizing, upgrading, and modifying terminal device communication, thus preventing similar problems from recurring in the same scenario. Furthermore, when the first terminal device experiences an anomaly, the anomaly information recorded by the network device can be transmitted in real time via the air interface. Through analysis and processing of the anomaly information, the cause of the anomaly in the first terminal device within the network can be determined more quickly, and optimization can be implemented.

[0191] In one possible implementation, taking the first network device as a third access network device and the second network device as a fourth access network device as an example, the process in Figure 4 is explained as follows:

[0192] A first terminal device connects to a fourth access network device. For example, the first terminal device establishes an RRC connection with the fourth access network device. When an anomaly occurs during communication between the fourth access network device and the first terminal device, the fourth access network device records the information corresponding to the anomaly, referred to as the second anomaly information. Due to movement of the first terminal device or an RRC connection anomaly, the first terminal device disconnects its RRC connection with the fourth access network device. The first terminal device then establishes an RRC connection with a third access network device. The fourth access network device sends the second anomaly information to the third access network device through a corresponding interface (e.g., the Xn interface). Further, when an anomaly occurs during communication between the first terminal device and the third access network device, the third access network device records the information corresponding to the anomaly, referred to as the first anomaly information. When the first terminal device normally connects to the third access network device, the third access network device sends an anomaly information to the first terminal device, including the first anomaly information and / or the second anomaly information.

[0193] Figure 6 is a schematic interactive diagram of the communication method 6000 provided in an embodiment of this application. It is understood that steps 600a to 650 are merely illustrative of the communication method 6000 and should not be construed as limiting the method. Steps 600a to 650 can be broken down into more steps or combined into fewer steps, and the order of steps 600a to 650 is not restricted.

[0194] Step 610: When an anomaly occurs during the communication between the first terminal device and the fourth access network device, the fourth access network device records the second anomaly information corresponding to the anomaly.

[0195] For example, when the first terminal device establishes an RRC connection with the fourth access network device, if an anomaly occurs during the communication between the first terminal device and the fourth access network device, the fourth access network device records the information corresponding to the anomaly, which is called the second anomaly information. The content of the second anomaly information can be seen in Figure 5.

[0196] Step 620: The fourth access network device sends the second abnormal information, and the third access network device receives the second abnormal information.

[0197] For example, the first terminal device disconnects its RRC connection from the fourth access network device and establishes an RRC connection with the third access network device. The fourth access network device can send the recorded second exception information of the first terminal device to the third access network device through a corresponding interface, which could be an Xn interface. The third access network device can save this second exception information. The third access network device can be understood as the access network device that will successfully establish an RRC connection again after the first terminal device experiences an exception on the fourth access network device.

[0198] In one possible implementation, the third access network device can send the second anomaly information to the first terminal device. Alternatively, while the first terminal device is residing on the third access network device, if an anomaly occurs during the communication process between the first terminal device and the third access network device, the third access network device can record the information corresponding to the anomaly, referred to as the first anomaly information. Therefore, the process in Figure 6 may also include:

[0199] Optionally, in step 630: when an abnormality occurs during the communication between the first terminal device and the third access network device, the third access network device records the first abnormality information corresponding to the abnormality.

[0200] For example, when an RRC connection exists between the first terminal device and the third access network device: when an anomaly occurs during communication between the first terminal device and the third access network device, the third access network device records the information corresponding to the anomaly, referred to as the first anomaly information. The content of the first anomaly information can be seen in Figure 5. The difference is that in the flowchart of Figure 6, the first anomaly information is access layer-related anomaly information recorded by the access network device (i.e., the third access network device), while in the flowchart of Figure 5, the first anomaly information is non-access layer-related anomaly information recorded by the core network device (the first core network device).

[0201] Optionally, in step 640: the first terminal device sends a second request, and the third access network device receives the second request.

[0202] The second request is used to request the third access network device to send abnormal information, which includes first abnormal information and / or second abnormal information.

[0203] Step 650: The third access network device sends an abnormal message, and the first terminal device receives the abnormal message.

[0204] For example, the anomaly information can be carried in an RRC message. That is, the third access network device can send an RRC message to the first terminal device, and the RRC message includes the anomaly information. Specifically, the third access network device can proactively send the anomaly information to the first terminal device, or the third access network device can send the anomaly information to the first terminal device when it receives a third request from the first terminal device.

[0205] In one possible implementation, the first terminal device may send a first request to both the third access network device and the fourth access network device, requesting them to record the abnormal information of the first terminal device. Further, in response to the first request, the third access network device and the fourth access network device may each send a first response to the first terminal device, instructing either the third or fourth access network device to enable recording the abnormal information of the first terminal device. Alternatively, in another possible implementation, the first terminal device may send a first request to a core network device connected to both the third and fourth access network devices. The core network device may send third information to both the third and fourth access network devices, instructing either the third or fourth access network device to enable recording the abnormal information of the first terminal device. Upon receiving the instruction in the third information, the third and fourth access network devices record the abnormal information of the first terminal device. Optionally, in response to the first request, the core network device may send a first response to the first terminal device, instructing the network side to enable recording the abnormal information of the first terminal device. Of course, after receiving the first request, the core network device can also perform the operation of recording the abnormal information of the first terminal device. That is to say, before step 610, it also includes:

[0206] Step 600a: The first terminal device sends a first request, and the core network device receives the first request. The first request includes first information, which is used to request the network side to record abnormal information during the communication process between the first terminal device and the network.

[0207] Step 600b: The core network device sends a first response, and the first terminal device receives the first response. The first response includes second information, which is used to instruct the network side to enable recording of abnormal information during the communication process between the first terminal device and the network.

[0208] Step 600c: The core network equipment sends third information to the third access network equipment and the fourth access network equipment respectively.

[0209] Accordingly, the third access network device receives third information, which is used to instruct the third access network device to record abnormal information during its communication with the first terminal device; the fourth access network device receives third information, which is used to instruct the fourth access network device to record abnormal information during its communication with the first terminal device.

[0210] It is understandable that there are interfaces, such as NG interfaces, between the core network equipment and the third and fourth access network equipment. Through the NG interface, the core network equipment sends third information to the third or fourth access network equipment. There is also an interface, such as the Xn interface, between the third and fourth access network equipment. Through the Xn interface, the fourth access network equipment sends the recorded second anomaly information to the third access network equipment.

[0211] Understandably, in the scheme shown in Figure 6, the fourth access network device records the second abnormal information of the first terminal device and sends the recorded second abnormal information to the third access network device, which then sends the second abnormal information to the first terminal device. Alternatively, in another scheme, the core network device collects the abnormal information of the first terminal device recorded by each access network device. For example, the third and fourth access network devices respectively send their recorded abnormal information to the connected core network device, which then sends the corresponding abnormal information to the first terminal device; or, the fourth access network device can send its recorded second abnormal information to the third access network device, which then sends the second abnormal information to the core network device; of course, the third access network device can also send its recorded first abnormal information to the core network device. The core network device then sends the abnormal information, including the second and / or first abnormal information, to the first terminal device.

[0212] In one possible implementation, in a paging scenario, the first or second exception message is a paging failure message:

[0213] Wherein, the first abnormal information is information indicating that the first network device failed to page the first terminal device, or, the second network device is the last serving access network device of the first terminal device in RRC connected state, and the second abnormal information is information indicating that the last serving access network device failed to page the first terminal device. The paging failure information includes at least one of the following: the identifier of the first terminal device, the time information of the paging failure, or the area information of the paging failure. Optionally, the paging failure information may explicitly or implicitly indicate that the cause / type of the abnormal information is a paging failure. When the paging failure information explicitly indicates that the cause / type of the abnormal information is a paging failure, the paging failure information further includes: the cause / type of the abnormality is a paging failure. Alternatively, the paging failure information includes a paging failure information element (IE), and the IE includes at least one of the following: the identifier of the first terminal device, the time information of the paging failure, or the area information of the paging failure. The content included in the IE may implicitly indicate that the type / cause of the abnormal information is a paging failure.

[0214] First, let's introduce the scenario where the first abnormal information is a paging failure message: The first network device can be the first core network device. The first core network device initiates a paging request for the first terminal device in the RRC idle state. When the paging of the first terminal device fails, the first core network device records the paging failure information of the first terminal device, which is simply referred to as the paging failure message. The first core network device then sends the paging failure message to the first terminal device.

[0215] Figure 7 is a schematic interactive diagram of the communication method 7000 provided in an embodiment of this application. It is understood that steps 700 to 760 are merely illustrative of the communication method 7000 and should not be construed as limiting the method. Steps 700 to 760 can be broken down into more steps or combined into fewer steps, and the order of steps 700 and 760 is not restricted.

[0216] Step 700: When a downlink service arrives at the first terminal device in the RRC idle state, the first core network device triggers a paging of the first terminal device, and the paging of the first terminal device fails.

[0217] For example, when a first terminal device registers with the network, the core network device can assign at least one Tracking Area Identity (TA) to the first terminal device. Each TA corresponds to an identifier, which can be called a Tracking Area Identity (TAI). The at least one TA assigned to the first terminal device forms a list, which can be called the TAI list. The TAI list includes the TAIs of at least one TA, and each TA includes one or more cells. The core network device can page the first terminal device through one or more cells within the TAI list area. For example, the core network triggers the corresponding access network device to send a paging message in one or more cells to page the first terminal device. There are no restrictions on the process by which the core network device pages the first terminal device according to the TAI list. For example, the core network device can page the first terminal device based on a portion of the TA area corresponding to the TAI list. If paging fails, the paging range is expanded to the remaining TA area corresponding to the TAI list. Alternatively, the core network device can page the first terminal device within the entire TA area corresponding to the TAI list.

[0218] Step 710: The first core network device records the paging failure information for the first terminal device, which can be called paging failure information.

[0219] In this embodiment of the application, if an access network device does not receive a response from a first terminal device when sending a paging message, it considers the paging to have failed. For example, for a first terminal device in an RRC idle state, it can send an RRC establishment request upon receiving a paging message. If the access network device does not receive the RRC establishment request from the first terminal device, it considers the paging of the first terminal device to have failed.

[0220] If one or more access network devices fail to page the first terminal device, the core network device may record the paging failure information corresponding to the first terminal device. This paging failure information includes: the identifier of the first terminal device, the time of the paging failure, or the area information of the paging failure. The time of the paging failure may specifically be the exact moment, time period, or time range at which the paging of the first terminal device failed. The area information of the paging failure may include at least one of the following: the identifier of the access network device that failed to page the first terminal device, the cell identifier (e.g., cell PCI) of the first terminal device that failed to page the first terminal device, or the TA area of ​​the paging failure. It is understood that the TA area can be represented by a TA ID, or by a list of cells included in the TA.

[0221] In one possible implementation, after the first terminal device establishes (or successfully completes) an RRC connection with an access network device connected to the first core network device, the first core network device can send paging failure information corresponding to the first terminal device to the access network device, which then sends the paging failure information recorded by the first core network device to the first terminal device. For example, the first core network device sends a NAS message carrying the paging failure information corresponding to the first terminal device. After receiving the NAS message, the access network device forwards the NAS message to the first terminal device. Alternatively, the first core network device can send a message to the access network device, for example, as shown in Figure 7, this message could be an initial context setup request carrying the paging failure information corresponding to the first terminal device. The access network device then sends an RRC message to the first terminal device, carrying the paging failure information corresponding to the first terminal device. For example, as shown in Figure 7, this RRC message could be an RRC reconfiguration message, etc. Specifically, the process shown in Figure 7 also includes:

[0222] Step 720: The first terminal device establishes an RRC connection with an access network device connected to the core network device.

[0223] For example, as shown in Figure 7, the process of establishing an RRC connection includes: the first terminal device sending an RRC setup request to the access network device; the access network device sending an RRC setup request to the first terminal device; and the first terminal device sending an RRC setup complete request to the access network device. After the above process, an RRC connection between the first terminal device and the access network device can be established.

[0224] Step 730: The access network device sends initial UE message to the first core network device.

[0225] Step 740: The first core network device sends an initial context establishment request to the access network device, which includes paging failure information corresponding to the first terminal device.

[0226] Step 750: The access network device sends an RRC reconfiguration to the first terminal device, which includes paging failure information corresponding to the first terminal device.

[0227] Step 760: The first terminal device sends an RRC reconfiguration complete message to the access network device.

[0228] In one possible implementation, the first terminal device can analyze and process the paging failure information recorded by the first core network device to optimize its network performance. For example, based on the paging failure information recorded by the first core network device, the first terminal device can determine at what time and in which cell the first core network device failed to paging it. Furthermore, the first terminal device can record its camping area and time information during the RRC disconnected state, such as the time, time period, or time range recorded, and the identifier of the cell it camped in, such as the cell PCI. The first terminal device compares its locally recorded information with the paging failure information recorded by the first core network device to determine the time and cell of the missed paging. For example, if the first core network device sends a paging message in cell Y at time X to paging the first terminal device, and the first terminal device is within the coverage area of ​​cell Y at time X but does not receive the corresponding paging message, then a missed paging of the first terminal device in cell Y at time X is defined. Further, the network performance of the first terminal device can be optimized based on the missed paging situation. For example, the reasons for missed paging can be analyzed. For instance, the missed paging may be due to insufficient coverage of cell Y, link failure between the first terminal device and cell Y, poor wireless channel status between the first terminal device and cell Y, or low power of the first terminal device in receiving paging messages. Then, the above problems can be optimized and / or resolved to improve the network performance of the first terminal device.

[0229] In one possible implementation, the first core network device can use a conventional paging method to page the first terminal device: Based on the identifier of the first terminal device, the location of the paging occasion (PO) is calculated. A paging message is sent at the corresponding PO location. The first terminal device anticipates or believes that the first core network device is using paging enhancement technology to page it: In paging enhancement technology, the first core network device sends a paging early indication (PEI) to the first terminal device before sending the paging message. The first terminal device will only receive the paging message at the corresponding PO location upon receiving the PEI. Because the first core network device uses the conventional paging method to page the first terminal device, while the first terminal device anticipates that the first core network device is using paging enhancement technology to page it, the first terminal device will not receive the paging message at the corresponding PO location due to the failure to receive the PEI, thus causing the paging of the first terminal device to fail. In the above scenario, the paging failure information recorded by the first core network device may also include: whether the first core network device applied traditional paging (or, in other words, whether the first core network device applied paging advance indication or paging enhancement, or in other words, whether the first core network device applied traditional paging, or paging advance indication or paging enhancement, etc.). For example, this information is indicated by 1 bit. When the bit is set to 1, it indicates that the first core network device applied traditional paging. When it is set to 0, it indicates that the first core network device applied paging advance indication or paging enhancement, etc.

[0230] The following describes a scenario where the second abnormal information is paging failure information: The first network device is the serving access network device of the first terminal device, and the second network device is the last serving access network device of the first terminal device in the RRC connected state. For example, the last serving access network device can be the last serving base station (last serving gNB). The last serving access network device can initiate paging of the first terminal device in the RRC deactivated state. When paging of the first terminal device fails, the last serving access network device can record the paging failure information of the first terminal device. Furthermore, the access network device in the RNA region corresponding to the first terminal device in the RRC deactivated state also records the paging failure information of the first terminal device and sends it to the last serving access network device. The last serving access network device sends the paging failure information of the first terminal device to the current serving access network device of the first terminal device. The current serving access network device of the first terminal device sends the paging failure information of the first terminal device to the first terminal device. In one possible implementation, the last serving access network device and the current serving access network device of the first terminal device can also be the same access network device. In this case, the third and fourth access network devices mentioned above are the same access network device. For example, when the first terminal device in the RRC deactivated state establishes or restores an RRC connection, the access network device that established or restored the RRC connection happens to be the last access network device. In this case, the last access network device can directly send the paging failure message recorded by the first terminal device to the first terminal device.

[0231] Figure 8 is a schematic interactive diagram of the communication method 8000 provided in an embodiment of this application. It is understood that steps 800 to 8011 are merely illustrative of the communication method 8000 and should not be construed as limiting the method. Steps 800 to 8011 can be broken down into more steps or combined into fewer steps, and the order of steps 800 and 8011 is not restricted.

[0232] Optionally, in step 800: the core network device sends the fourth information, and the access network device receives the fourth information.

[0233] For example, the core network equipment can be an AMF network element, and the access network equipment receiving the fourth information can include the last serving access network equipment of the first terminal equipment and / or the access network equipment corresponding to the RAN. The fourth information is used to instruct the access network equipment to record abnormal information during the communication process between the access network equipment and the first terminal equipment. The fourth information includes the identifier of the first terminal equipment. For example, the identifier of the first terminal equipment can be its TMSI, IMEI, etc. In a paging scenario, when the access network equipment fails to paging the first terminal equipment, it can be considered that an abnormality has occurred during the communication process between the access network equipment and the first terminal equipment. The access network equipment can record the information corresponding to the paging failure, which is called paging failure information.

[0234] Step 810: The core network equipment sends downlink data or signaling related to the first terminal equipment, and finally the serving access network equipment receives the downlink data or signaling related to the first terminal equipment.

[0235] For example, the last serving access network device receives downlink data related to the first terminal device from a UPF network element, or receives signaling related to the first terminal device from an AMF network element. The AMF or UPF network element stores information about the last serving access network device of the first terminal device. Therefore, when the AMF or UPF network element receives downlink data or signaling from the first terminal device, it sends the downlink data or signaling to the last serving access network device. It can be understood that the last serving access network device switches the first terminal device from an RRC connected state to an RRC deactivated state, and / or, before the terminal is in the RRC deactivated state, the last access network device is the last access network device that RRC-connected the first terminal device.

[0236] In one possible implementation, in step 800, the core network device sends a fourth message to the last serving access network device, instructing the last serving access network device to record the abnormal information of the first terminal device. Alternatively, in step 810, the core network device may also send a fourth message to the last serving access network device, which instructs the last serving access network device to record abnormal information during the communication process between the last serving access network device and the first terminal device. For example, in a paging scenario, the last serving access network device may record paging abnormal information of the first terminal device. For example, the fourth message may be carried in the downlink data or signaling related to the first terminal device.

[0237] Step 820: The last service access network device triggers a paging of the first terminal device.

[0238] For example, when the first terminal device enters the RRC deactivation state, the last serving access network device indicates the RNA to the first terminal device: for example...

[0239] The RNA can indicate a list of cells corresponding to the access network device (RNA), or indicate one or more RAN areas. A RAN area can be a TA or a subset of TAs. RAN areas can be indicated by TA codes, or by a combination of TA codes and RAN area codes. The last serving access network device can initiate paging of the first terminal device based on the RNA. For example, the last serving access network device can send a paging message to the access network device corresponding to the RNA to notify the access network device corresponding to the RNA to page the first terminal device. It is understood that an interface can exist between the last serving access network device and the access network device corresponding to the RNA; this interface can be an Xn interface.

[0240] In one possible implementation, in step 800, the core network device sends a fourth message to the access network device corresponding to the RNA, the fourth message instructing the access network device corresponding to the RNA to record the abnormal information of the first terminal device. Alternatively, in step 830, the last serving access network device further sends a fifth message to the access network device corresponding to the RNA, the fifth message including the identifier of the first terminal device, the fifth message instructing the access network device corresponding to the RNA to record abnormal information during its communication with the first terminal device, or the fifth message instructing the access network device corresponding to the RNA to enable recording the abnormal information of the first terminal device.

[0241] In a paging scenario, the access network device corresponding to the RNA can record paging failure information for the first terminal device, referred to as paging failure information. This fourth information includes the identifier of the first terminal device. For example, the identifier of the first terminal device is the I-RNTI of the first terminal device, which is used to identify the first terminal in the paging process of the RAN. It can be understood that the last serving access network device can send the paging message and the fourth information separately to the access network device corresponding to the RNA, or the fourth information can be carried in the paging message without restriction. In the process shown in Figure 8, the example of carrying the fourth information in the paging message is illustrated.

[0242] Step 830: Finally, the access network device sends a paging message, and the access network device corresponding to RNA receives the paging message. Optionally, the paging message includes fourth information.

[0243] Step 840: Finally, the service access network device and the access network device corresponding to the RNA page the first terminal device.

[0244] Step 850: When the last service access network and the access network device corresponding to RNA fail to page the first terminal device, they record the paging failure information for the first terminal device, referred to as the paging failure information.

[0245] For example, the last serving access network device (LSB) or the access network device corresponding to the RNA can send a paging message, which includes the identifier of the first terminal device. If the LSB or the access network device corresponding to the RNA does not receive a response from the first terminal device after sending the paging message, it considers the paging of the first terminal device to have failed. For example, if the first terminal device is paged, the first terminal device sends an RRC resume request to the LSB. In this embodiment, if the LSB or the access network device corresponding to the RNA does not receive an RRC resume request from the first terminal device after sending the paging message, it considers the paging of the first terminal device to have failed. The LSB or the access network device corresponding to the RAN can record the paging failure information for the first terminal device. Alternatively, the LSB can determine whether a paging failure has occurred. If an access network device corresponding to the RAN does not receive a response from the first terminal device after paging the first terminal device, it can send a corresponding indication to the LSB. When all access network devices corresponding to the RNA triggered by the last serving access network device send the corresponding indication, the last serving access network device determines that paging of the first terminal device has failed and records the paging failure information. For example, the paging failure information includes at least one of the following: the identifier of the first terminal device that failed paging, the time information of the paging failure, or the area information of the paging failure, such as the identifier of the cell where the paging failure occurred, the identifier of the RNA that failed paging, the TAI of the paging failure, etc.

[0246] Step 860: The access network device corresponding to RNA sends a paging failure message, and finally the serving access network device receives the paging failure message.

[0247] Step 870: The final service access network device collects and stores the paging failure information of the first terminal device.

[0248] It is understood that the paging failure information of the first terminal device collected and stored by the last serving access network device includes: information on the last serving access network device's paging failure to the first terminal device, and information on the paging failure of the access network device corresponding to the RNA to the first terminal device. For example, the last serving access network device stores the paging failure information of the first terminal device within the context of the first terminal device.

[0249] In one possible implementation, when a first terminal device in an RRC deactivated state accesses an access network device, this access network device can be called the serving access network device. Finally, the serving access network device can send paging failure information from the first terminal device to itself. For example, as shown in Figure 8, the serving access network device carries paging failure information in the context retrieval response of the first terminal device. The serving access network device sends paging failure information to the first terminal device. For example, after the serving access network device restores the RRC connection, the serving access network device sends a paging failure message to the first terminal device. For example, as shown in Figure 8, the serving access network device carries paging failure information in the RRC connection restoration message, or, after the RRC connection is restored, the serving access network device carries the paging failure message in the RRC configuration message. Referring to Figure 8, as follows:

[0250] Step 880: The first terminal device sends an RRC connection restoration request, and the serving access network device receives the RRC connection restoration request.

[0251] In one possible scenario, when the first terminal device is in an uplink service or data transmission state, the first terminal device in the RRC deactivated state can actively initiate an RRC connection recovery request to restore the RRC connection of the first terminal device.

[0252] Step 890: The service access network device sends a context retrieval request, and finally the access network device receives the context retrieval request.

[0253] Step 8010: The final access network device sends a context retrieval response, and the serving access network device receives the context retrieval response, which includes paging failure information.

[0254] Step 8011: The service access network device sends an RRC connection restoration message, and the first terminal device receives the RRC connection restoration message, which includes paging failure information.

[0255] By combining locally recorded information such as the camping area and camping time with paging failure information recorded by the network side, the first terminal device can determine that a missed paging has occurred. Furthermore, the first terminal device can determine in which area and at what time the missed paging occurred, further optimizing the list of cells to prioritize camping in the non-connectivity state, or determining whether the missed paging was due to channel conditions or insufficient received power.

[0256] In one possible implementation, if the last serving access network device and the access network device corresponding to the RNA do not have an Xn interface, the Xn interface is missing, or the Xn interface is faulty or abnormal, the last serving access network device will be unable to trigger RAN paging to that access network device.

[0257] In this scenario, the paging failure information recorded by the last serving access network device includes at least one of the following: an Xn interface malfunction or no Xn interface, the identifier of the access network device with an Xn interface malfunction (or no Xn interface), or the identifier of the cell managed by that access network device. Thus, after the network side sends the paging failure information to the first terminal device (or the server of the first terminal device), the first terminal device or the corresponding server can determine the area where paging failures may have occurred. One possible implementation is that the first terminal device can mark the cells where paging failures occurred, for example, by marking them as blacklisted cells, to avoid missing paging attempts due to residing on these cells in a disconnected state.

[0258]

Example 2

[0259] The difference between Embodiment 2 and Embodiment 1 is that in Embodiment 1, the abnormal information of the first terminal device recorded by the first network device and / or the second network device is sent to the first terminal device via the air interface. In Embodiment 2, the abnormal information of the first terminal device recorded by the first network device and / or the second network device is sent to the server of the first terminal device via other interfaces.

[0260] In one possible implementation, a first network device and / or a second network device record anomaly information of the first terminal device and send it to a data center (DC). Optionally, the DC is deployed by the operator and can be a network element within the core network or a network element outside the core network, without restriction. The DC sends the anomaly information of the first terminal device recorded on the network side to the server corresponding to the first terminal device; for example, the server can be a cloud-hosted router (CHR) server. The CHR server is used to perform anomaly information analysis. Further, the first terminal device sends the locally recorded anomaly information to the CHR server.

[0261] In one possible implementation, as shown in Figure 9, the specific process includes:

[0262] 1. The first network device records the first abnormal information of the first terminal device.

[0263] For example, the first abnormal information is information about an abnormality that occurred during the communication between the first network device and the first terminal device; optionally, the first abnormal information includes at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality.

[0264] 2. The second network device records the second abnormal information of the first terminal device, and the second network device sends the second abnormal information to the first network device.

[0265] For example, the second abnormal information is information about an abnormality occurring during the communication process between the second network device and the first terminal device; optionally, the second abnormal information includes at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality.

[0266] In one possible implementation, the first terminal device sends a first request to a first network device and / or a second network device. The first request includes first information, which requests the network side to record abnormal information during the communication process between the first terminal device and the network. Optionally, further, in response to the first request, the first network device and / or the second network device sends a first response to the first terminal device. The first response includes third information, which instructs the network side to enable the recording of abnormal information during the communication process between the first terminal device and the network.

[0267] For example, the first network device is a first core network device, and the second network device is a second core network device; or, the first network device is a first core network device, and the second network device is a second access network device connected to the first core network device. Alternatively, the first network device is a third access network device, and the second network device is a fourth access network device. A typical application scenario is: a first terminal device sends a first request to the first core network device; optionally, the first core network device sends a first response to the first terminal device. Further, the first core network device sends third information to the second access network device, the third information being used to instruct the second access network device to record any abnormal information during its communication with the first terminal device.

[0268] 3. The first network device sends abnormal information, and the DC receives abnormal information. The abnormal information includes the first abnormal information and / or the second abnormal information.

[0269] It is understood that the embodiments of this application have the following two scenarios: Scenario 1: The first network device records the first abnormal information, and the abnormal information sent by the first network device to the DC includes the first abnormal information. Scenario 2: The second network device records the second abnormal information, and the second network device sends the second abnormal information to the first network device, and the abnormal information sent by the first network device to the DC includes the second abnormal information. Further, the first network device records the first abnormal information, and the abnormal information sent by the first network device to the DC also includes the first abnormal information. Optionally, the abnormal information includes at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality.

[0270] 4. The DC sends an error message, and the server receives the error message.

[0271] For example, when the DC receives anomaly information from the first network device, it determines the vendor of the first terminal device based on the identifier of the first terminal device included in the anomaly information, such as the IMSI of the first terminal device. The DC obtains the Internet Protocol (IP) address corresponding to the vendor's server and sends the anomaly information of the first terminal device recorded on the network side to the corresponding server.

[0272] 5. The server analyzes and processes the abnormal information recorded on the network side.

[0273] In one possible implementation, the first terminal device can send locally recorded anomaly information to the server. The server analyzes and compares the anomaly information recorded locally by the first terminal device with the anomaly information recorded on the network side to determine the cause of the anomaly or fault. Furthermore, the communication of the first terminal device is optimized and / or upgraded.

[0274] In one possible implementation, the solution of Embodiment 2 can be applied to a scenario of paging a terminal device. For example, either the first abnormal information or the second abnormal information is paging failure information; wherein, the first abnormal information is information indicating that the first network device failed to paging the first terminal device, or, the second network device is the last serving access network device of the first terminal device in RRC connection state, and the second abnormal information is information indicating that the last serving access network device failed to paging the first terminal device. Optionally, the paging failure information includes at least one of the following: the identifier of the first terminal device, the time information of the paging failure, or the area information of the paging failure.

[0275] In one possible implementation, in Embodiment 1, the first network device can send abnormal information to the first terminal device in real time. For example, when the first network device detects an abnormality in the first terminal device, it records the corresponding abnormal information and sends it to the first terminal device in real time. Alternatively, when the first terminal device detects an abnormality, it can request the corresponding abnormal information from the first network device in real time. In Embodiment 2, abnormal information can be sent to the server non-real-time or offline. For example, if the server performs an abnormal information analysis once a month, the first network device can upload the collected abnormal information once a month.

[0276] Through the above design, abnormal information recorded on the network side is sent to the server corresponding to the terminal device via other interfaces besides the air interface. The server corresponding to the terminal device then performs unified analysis and processing of the abnormal information, saving air interface transmission resources. Furthermore, in Embodiment 2, the terminal device does not need to have abnormal information processing and analysis functions. The network side can record abnormal information from any terminal device and send it to the terminal device's server for analysis and / or processing, reducing the implementation complexity on the terminal device side.

[0277] It is understood that the "first network device" and "second network device" in the embodiments of this application can be access network devices. Optionally, the access network device can adopt an ORAN architecture, and the access network device can include logical nodes such as CU, DU, and RU. When the second network device is an access network device, the CU and / or DU can record second abnormal information and send the second abnormal information to the first network device through the corresponding interface. When the first network device is an access network device, the CU and / or DU can record first abnormal information and send the abnormal information including the first abnormal information and / or the second abnormal information to the first terminal device through the RU. Further, the CU can be split into CU-CP and CU-UP. Specifically, the CU-CP can perform the recording of the first abnormal information or the second abnormal information.

[0278] In the embodiments provided above, the methods provided by the embodiments of this application have been described from the perspective of the interaction between the first terminal device, the first network device, and the second network device. To implement the functions of the methods provided by the embodiments of this application, the first terminal device, the first network device, or the second 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.

[0279] Based on the same conceptual framework as the above-described method embodiments, Figures 10 and 11 are schematic diagrams of possible communication devices provided in the embodiments of this application. These communication devices can implement the functions of terminal devices or network devices in the above-described method embodiments, and therefore may achieve the beneficial effects of the above-described method embodiments. In the embodiments of this application, the communication device may be a terminal device or a network device, or a unit, module, or component (such as a chip, chip system, circuit, processor, or others) applied in a terminal device or network device. In the following description, the term "unit" will be used as an example. For example, in the following description, the communication device will be described as including a processing unit and a transceiver unit. The processing unit in the following description may also be replaced by: a processing module or a processing component, etc. The transceiver unit may also be replaced by: a transceiver unit or a transceiver component. For example, a transceiver component may refer to a communication module.

[0280] As shown in Figure 10, the communication device 10000 includes a processing unit 1010 and a transceiver unit 1020. The communication device 10000 is used to implement the functions of the first terminal device or the first network device in Figure 4 above.

[0281] Optionally, the transceiver unit 1020 may also be referred to as an output unit, an interface unit, or a communication unit, etc. In one possible implementation, the transceiver unit 1020 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.

[0282] When the communication device 10000 is used to implement the function of the first terminal device in Figure 4, specifically: the processing unit 1010 is used to establish a communication connection with the first network device; the transceiver unit 1020 is used to receive abnormal information from the first network device, the abnormal information being either first abnormal information or second abnormal information, the first abnormal information being information indicating an abnormality in the communication process between the first network device and the first terminal device, and the second abnormal information being information indicating an abnormality in the communication process between the second network device and the first terminal device, the abnormal information including at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality.

[0283] In one possible implementation, the first exception information is recorded by the first network device, and the second exception information is recorded by the second network device.

[0284] In one possible implementation, the abnormal information is the first abnormal information: the first network device is a first core network device or a first access network device.

[0285] In one possible implementation, the abnormal information is the second abnormal information: the first network device is a first core network device, the second network device is a second core network device, or the first core network device is connected to a second access network device; or the first network device is a third access network device, and the second network device is a fourth access network device.

[0286] In one possible implementation, the first abnormal information or the second abnormal information is paging failure information; wherein, the first abnormal information is information indicating that the first network device failed to paging the first terminal device, or, the second network device is the last serving access network device of the first terminal device in the Radio Resource Control (RRC) connected state, and the second abnormal information is information indicating that the last serving access network device failed to paging the first terminal device.

[0287] In one possible implementation, the paging failure information includes at least one of the following: the identifier of the first terminal device, the time information of the paging failure, or the area information of the paging failure.

[0288] In one possible implementation, the method further includes: sending a first request, the first request including first information, the first information being used to request the network side to record abnormal information during the communication process between the first terminal device and the network.

[0289] In one possible implementation, the first information includes: information on the first terminal device's ability to receive abnormal information recorded by the network side, and / or, information on the first terminal device requesting the network side to record abnormal information.

[0290] In one possible implementation, the method further includes: receiving a first response in response to the first request, the first response including second information, the second information being used to instruct the network side to enable recording of abnormal information during the communication process between the first terminal device and the network.

[0291] In one possible implementation, the method further includes sending a second request to the first network device, the second request being used to request the first network device to send the abnormal information.

[0292] When the communication device 10000 is used to implement the function of the first network device in Figure 4, specifically: the processing unit 1010 is used to establish a communication connection with the first terminal device; the transceiver unit 1020 is used to send abnormal information to the first terminal device. The abnormal information is either a first abnormal information or a second abnormal information. The first abnormal information is information indicating that an abnormality occurred during the communication process between the first network device and the first terminal device. The second abnormal information is information indicating that an abnormality occurred during the communication process between the second network device and the first terminal device. The abnormal information includes at least one of the following: the identifier of the first terminal device, the cause information of the abnormality, the time information of the abnormality, or the area information of the abnormality.

[0293] In one possible implementation, the first exception information is recorded by the first network device, and the second exception information is recorded by the second network device.

[0294] In one possible implementation, the abnormal information is the first abnormal information: the first network device is a first core network device or a first access network device.

[0295] In one possible implementation, the abnormal information is the second abnormal information: the first network device is a first core network device, the second network device is a second core network device, or the first core network device is connected to a second access network device; or the first network device is a third access network device, and the second network device is a fourth access network device.

[0296] In one possible implementation, the abnormal information is the second abnormal information, and the method further includes receiving the second abnormal information from the second network device.

[0297] In one possible implementation, the method further includes sending third information to the second network device, the third information being used to instruct the second network device to record abnormal information during the communication process between the second network device and the first terminal device.

[0298] In one possible implementation, the first abnormal information or the second abnormal information is paging failure information; wherein, the first abnormal information is information indicating that the first network device failed to paging the first terminal device, or, the second network device is the last serving access network device of the first terminal device in the Radio Resource Control (RRC) connected state, and the second abnormal information is information indicating that the last serving access network device failed to paging the first terminal device.

[0299] In one possible implementation, the paging failure information includes at least one of the following: the identifier of the first terminal device, the time information of the paging failure, or the area information of the paging failure.

[0300] In one possible implementation, the method further includes: receiving a first request from the first terminal device, the first request including first information, the first information being used to request the network side to record abnormal information during the communication process between the first terminal device and the network.

[0301] In one possible implementation, the first information includes: information on the first terminal device's ability to receive abnormal information recorded by the network side, and / or, information on the first terminal device's request for the network side to record abnormal information.

[0302] In one possible implementation, the method further includes: sending a first response to the first terminal device, the first response being a response to the first request, the first response including second information, the second information being used to instruct the network side to enable recording of abnormal information during the communication process between the first terminal device and the network.

[0303] In one possible implementation, the method further includes: receiving a second request from the first terminal device, the second request being used to request the first network device to send the abnormal information.

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

[0305] As shown in Figure 11, the communication device 1100 includes a processor 1110 and an interface circuit 1120. The processor 1110 and the interface circuit 1120 are coupled to each other. It is understood that the interface circuit 1120 can be a transceiver or an input / output interface. Optionally, the communication device 1100 may also include a memory 1130 for storing instructions executed by the processor 1110, or storing input data required by the processor 1110 to execute instructions, or storing data generated after the processor 1110 executes instructions.

[0306] When the communication device 1100 is used to implement the method shown in FIG4, the processor 1110 is used to implement the function of the processing unit 1010, and the interface circuit 1120 is used to implement the function of the transceiver unit 1020.

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

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

[0309] This application embodiment also provides a communication device, which includes a processor for implementing the functions of the first terminal device or the first network device in FIG4. Optionally, the communication device further includes a memory, with the processor coupled to the memory. The processor is used to execute computer programs or instructions stored in the memory to implement the functions of the first terminal device or the first network device in FIG4. Optionally, the communication device may be a chip or a chip system.

[0310] This application embodiment 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 is used to implement the functions of the first terminal device or the first network device in FIG4 above through logic circuits or execution code instructions.

[0311] 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 functions of the first terminal device or the first network device shown in FIG4.

[0312] This application also provides a computer program product, including a computer program or instructions, which, when run on a computer, implement the functions of the first terminal device or the first network device in FIG4 above.

[0313] It is understood that the processor in the embodiments of this application can 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 can be a microprocessor or any conventional processor.

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

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

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

[0317] 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: Comprising: establishing a communication connection with a first network device; receiving exception information from the first network device, the exception information being first exception information or second exception information, the first exception information being information of an exception occurring in a communication process between the first network device and a first terminal device, the second exception information being information of an exception occurring in a communication process between a second network device and the first terminal device, the exception information comprising at least one of the following: an identifier of the first terminal device, cause information of the exception, time information of the exception, or area information of the exception.

2. The method of claim 1, wherein, The first exception information is recorded by the first network device, and the second exception information is recorded by the second network device.

3. The method of claim 1 or 2, wherein, The exception information is the first exception information: The first network device is a first core network device or a first access network device.

4. The method of claim 1 or 2, wherein, The exception information is the second exception information: The first network device is a first core network device, and the second network device is a second core network device, or the first core network device is connected to a second access network device; or the first network device is a third access network device, and the second network device is a fourth access network device.

5. The method of any one of claims 1 to 4, wherein, The first exception information or the second exception information is paging failure information; The first network device is the last serving access network device of the first terminal device in a radio resource control (RRC) connected state, and the second exception information is information of paging failure of the first terminal device by the last serving access network device.

6. The method of claim 5, wherein, The paging failure information comprises at least one of the following: an identifier of the first terminal device, time information of paging failure, or area information of paging failure.

7. The method of any one of claims 1 to 6, wherein, Further comprising: sending a first request, the first request comprising first information, the first information being used to request the network side to record exception information in a communication process between the first terminal device and the network.

8. The method of claim 7, wherein, The first information comprises: capability information of the first terminal device supporting receiving exception information recorded by the network side, and / or request information of the first terminal device requesting the network side to record exception information.

9. The method of claim 7 or 8, wherein, Further comprising: receiving a first response, the first response being in response to the first request, the first response comprising second information, the second information being used to indicate that the network side enables recording of exception information in a communication process between the first terminal device and the network.

10. The method of any one of claims 1 to 9, wherein, Further comprising: sending a second request to the first network device, the second request being used to request the first network device to send the exception information.

11. A communication method, comprising: Comprising: establishing a communication connection with a first terminal device; sending, to the first terminal device, exception information, the exception information being first exception information or second exception information, the first exception information being information about an exception occurring in a communication process between the first network device and the first terminal device, the second exception information being information about an exception occurring in a communication process between the second network device and the first terminal device, the exception information including at least one of the following: an identifier of the first terminal device, cause information of the exception, time information of the exception, or area information of the exception.

12. The method of claim 11, wherein, The first exception information is recorded by the first network device, and the second exception information is recorded by the second network device.

13. The method of claim 11 or 12, wherein, The exception information is the first exception information. The first network device is a first core network device or a first access network device.

14. The method of claim 11 or 12, wherein, The exception information is the second exception information. The first network device is a first core network device, and the second network device is a second core network device, or the first core network device is connected to a second access network device, or the first network device is a third access network device, and the second network device is a fourth access network device.

15. The method of claim 11, 12 or 14, wherein, The exception information is the second exception information, and further includes: receiving the second exception information from the second network device.

16. The method of claim 15, wherein, Further includes: sending, to the second network device, third information, the third information being used to instruct the second network device to record exception information in a communication process between the second network device and the first terminal device.

17. The method of any one of claims 11 to 16, wherein, The first exception information or the second exception information is paging failure information. The first exception information is information about paging failure of the first terminal device by the first network device, or the second network device is a last serving access network device of the first terminal device in a radio resource control (RRC) connected state, and the second exception information is information about paging failure of the first terminal device by the last serving access network device.

18. The method of claim 17, wherein, The paging failure information includes at least one of the following: an identifier of the first terminal device, time information of the paging failure, or area information of the paging failure.

19. The method of any one of claims 11 to 18, wherein, Further includes: receiving a first request from the first terminal device, the first request including first information, the first information being used to request a network side to record exception information in a communication process between the first terminal device and the network.

20. The method of claim 19, wherein, The first information includes: capability information of the first terminal device supporting reception of the exception information recorded by the network side, and / or request information of the first terminal device requesting the network side to record exception information.

21. The method of claim 19 or 20, wherein, Further includes: sending a first response to the first terminal device, the first response being a response to the first request, the first response including second information, the second information being used to instruct the network side to enable recording of exception information in a communication process between the first terminal device and the network.

22. The method of any one of claims 11 to 21, wherein, Further includes: receiving a second request from the first terminal device, the second request being used to request the first network device to send the exception information.

23. A communications device, characterized by The unit is used to implement the method in any one of claims 1 to 10.

24. A communications device, characterized by comprising a processor configured to cause the communication device to perform the method of any one of claims 1 to 10.

25. A communications device, characterized by comprising means for implementing the method of any one of claims 11 to 22.

26. A communications device, characterized by comprising a processor configured to cause the communication device to perform the method of any one of claims 11 to 22.

27. A computer readable storage medium, characterized in that, The computer readable storage medium has stored thereon instructions which, when executed by a communication device, cause the communication device to perform the method of any one of claims 1 to 10, or to perform the method of any one of claims 11 to 22.

28. A computer program product, characterised in that, The computer program product comprises instructions which, when executed by a communication device, cause the communication device to perform the method of any one of claims 1 to 10, or to perform the method of any one of claims 11 to 22.

Images