Communication method and related device

Abstract

The invention relates to the technical field of wireless communication, in particular to a communication method and a related device. The method comprises the following steps: a first network element determines a second network element under the condition that a first business process fails unexpectedly; wherein the second network element is a standby network element of the first network element, and the reasons of the unexpected failure do not include an exception specified by a protocol and a custom exception. And the first network element migrates the first service process to the second network element to instruct a subsequent process of the first service process to be initiated through the second network element. By adopting the method provided by the invention, the service time delay of the first service process can be reduced.

Description

Technical Field

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

[0002] The service process initiated by the terminal device may use some functional network elements in the core network. For example, the registration service of the terminal device, the establishment of the protocol data unit (PDU) initiated by the terminal device, or the service cell switching of the terminal device may use the access and mobility management function (AMF) network element and the session management function (SMF) network element in the core network.

[0003] In order to ensure the reliable implementation of business processes, the prior art proposes a disaster recovery networking solution for the core network. When a business process fails, if an abnormality is detected in the business path corresponding to the business process through an abnormality detection mechanism such as a heartbeat message detection mechanism or a link detection mechanism, the business process can be re-initiated on the backup business path through the disaster recovery networking solution to achieve failure recovery of the business process. It should be understood that in an embodiment of the present application, the business path of the business process may include network elements and communication links used in the implementation of the business process, and the abnormality in the business path includes abnormalities in the network elements in the business path and / or abnormalities in the communication links in the business path. However, there may also be abnormalities on the business path that cannot be detected by the existing abnormality detection mechanism, so based on the existing failure recovery process, the business process will be initiated again on the business path with such abnormalities, which will cause the continuous failure of the business process and affect the user experience of the terminal device. Summary of the invention

[0004] In order to solve the above problems, the present application provides a communication method and related devices. The communication method provided by the present application can avoid the continuous failure of business processes caused by anomalies that cannot be detected by the existing anomaly detection mechanism, reduce business delays and improve the user experience of terminal devices.

[0005] In a first aspect, the present application provides a communication method. The method may be performed by a first network element, or may be performed by a component of the first network element (e.g., a processor, a chip, or a chip system, etc.). It should be understood that the first network element may be a network element in a core network and is associated with a first service process.

[0006] The method may include: when an unexpected failure occurs in a first service process, the first network element determines a second network element. The second network element is a backup network element of the first network element, and the cause of the unexpected failure does not include an exception specified by the protocol and a custom exception. The first network element migrates the first service process to the second network element to indicate that a subsequent process of the first service process is initiated through the second network element.

[0007] It should be understood that in the embodiments of the present application, unexpected failure can also be understood as a failure caused by an unexpected exception, and an unexpected exception refers to an exception other than the exception specified in the protocol and the custom exception.

[0008] In the above implementation, when the first service process fails and the reason for the failure does not include the exception specified by the protocol and the custom exception, the first network element will migrate the first service process to the standby second network element to indicate that the subsequent process of the first service process is initiated through the second network element. This method can prevent the first service process from being repeatedly initiated on the first network element where an unexpected failure has occurred, thereby avoiding the continuous failure of the first service process, reducing service delays and improving the user experience of terminal devices.

[0009] In conjunction with the first aspect, in a possible implementation, the first network element migrating the first service process to the second network element may include: when the service failure of the first network element is restored in a redirection mode, the first network element sends a first request message to the second network element. The first request message is used to provide the second network element with the session information that has been generated corresponding to the first service process, and the generated session information is used for failure recovery of the first service process.

[0010] Optionally, the first network element receives a first response message corresponding to the first request message from the second network element, wherein the first response message is used to indicate that the first request message is correctly received.

[0011] In the above implementation, when the service failure is restored in a redirection mode, the first network element can provide the second network element with the session information corresponding to the first service process, so as to realize the migration of the first service process to the second network element. The method is simple and easy to implement, which can not only ensure the efficiency of failure recovery of the first service process, but also make the communication method provided by the present application applicable to the scenario where the service failure is restored in a redirection mode.

[0012] In combination with the first aspect, in a possible implementation, the first request message includes at least one of the following: N1 interface information between the terminal device that initiates the first business process and the first network element, terminal device context information of the first business process, or first information, wherein the first information is used to indicate that the first business process is migrated from the first network element to the second network element due to an unexpected failure.

[0013] In combination with the first aspect, in a possible implementation, the first network element migrates the first business process to the second network element, including: when the service failure of the first network element is recovered by rerouting, the first network element sends a second request message to the network device to migrate the first business process to the second network element, wherein the second request message is used to instruct the network device to reroute the first business process to the second network element.

[0014] In the above implementation, when the service failure is restored in a rerouting manner, the first network element can instruct the network device to reroute the first service process to the second network element, so as to realize the migration of the first service process to the second network element. The method is simple and easy to implement, which can not only ensure the efficiency of failure recovery of the first service process, but also make the communication method provided by the present application applicable to the scenario where the service failure is restored in a rerouting manner.

[0015] In combination with the first aspect, in a possible implementation, the second request message includes at least one of the following: N1 interface information between the terminal device that initiates the first service process and the first network element, and identification information of the second network element.

[0016] In combination with the first aspect, in a possible implementation, when the first network element sends the first request message or the second request message, the first service process may be an initial registration process of the terminal device. In this case, the first network element may be an access and mobility management function network element to which the terminal device is connected before an unexpected failure of the first service process occurs, and the second network element may be an access and mobility management function network element that is a backup of the first network element.

[0017] In combination with the first aspect, in a possible implementation, migrating the first service process to the second network element includes: the first network element sends a third request message to the second network element to migrate the first service process to the second network element. The third request message is used to instruct the second network element to rebuild session information of the first service process.

[0018] In the above implementation, the first network element can directly instruct the second network element to rebuild the session information of the first service flow through the third request message to achieve the migration of the first service flow to the second network element. The method is simple and easy to implement, and can ensure the efficiency of failure recovery of the first service flow.

[0019] In combination with the first aspect, in a possible implementation, the third request message includes: identification information of the network device, identification information of the next generation application protocol corresponding to the terminal device that initiates the first service process, or the first information. The first information is used to indicate that the first service process is migrated from the first network element to the second network element due to an unexpected failure.

[0020] Optionally, the identification information of the network device may be a global unified radio access network identification of the network device associated with the first service process. The next generation application protocol identification information corresponding to the terminal device may be a next generation radio access network application protocol identification (ie, NG-RAN application protocol ID, abbreviated as NGAP ID) of the terminal device.

[0021] In combination with the first aspect, in a possible implementation, when the first network element sends the third request message, the first service process may be a protocol data unit session establishment process or a service cell switching process. In this case, the first network element may be an access and mobility management function network element to which the terminal device is connected before the unexpected failure of the first service process occurs, and the second network element may be an access and mobility management function network element that is a standby of the first network element.

[0022] In combination with the first aspect, in a possible implementation, the method may further include: when the first business process fails, obtaining a failure reason value. When it is determined according to the failure reason value that the reason for the failure of the first business process does not include an exception specified in the protocol and a custom exception, it is determined that the failure of the first business process is an unexpected failure.

[0023] In a second aspect, the present application provides a communication method. The method may be performed by a second network element, or may be performed by a component of the second network element (e.g., a processor, a chip, or a chip system, etc.). It should be understood that the second network element is a backup network element of the first network element, and the first network element is a network element in the core network and is associated with the first service process.

[0024] The method includes: when an unexpected failure occurs in a first business process on a first network element and the first network element is migrated to a second network element, if the first business process fails again on the second network element, the second network element determines whether the reoccurring failure is an unexpected failure. The cause of the unexpected failure does not include exceptions specified in the protocol and custom exceptions. When the second network element determines that the reoccurring failure is an unexpected failure, if it is determined that the first time interval between the two unexpected failures of the first business process on the first network element and the second network element is less than or equal to the time interval threshold, the second network element will no longer migrate the first business process to the first network element.

[0025] It should be understood that in the embodiments of the present application, unexpected failures can also be understood as failures caused by unexpected exceptions, and unexpected exceptions refer to exceptions other than exceptions specified in the protocol and custom exceptions. Optionally, in the embodiments of the present application, unexpected exceptions include, but are not limited to: network element internal logic processing exceptions, application software defects, transmission packet loss, and system probabilistic processing failures of the communication system.

[0026] In the above implementation, when the first service process fails unexpectedly at both the first network element and the second network element, and the time interval between the two unexpected failures is less than or equal to the time interval threshold, the second network element will not migrate the first service process to the first network element again. In the case where the abnormality of the first network element has not been recovered, the use of this solution can avoid the continuous failure of the first service process caused by the first service process switching back and forth between the first network element and the second network element (which can also be understood as ping-pong switching), and avoid the additional load brought to the first network element and the second network element by ping-pong switching.

[0027] In combination with the second aspect, in a possible implementation, the method may further include: when the first time interval is greater than a time interval threshold, migrating the first service process to the first network element.

[0028] In the above implementation, when the time interval between two unexpected failures is greater than the time interval threshold, the first business process is allowed to be migrated to the first network element again. This can avoid the situation where the first network element has returned to normal but the first business process has not been switched back, thereby improving the flexibility and practicality of the communication method provided in this application.

[0029] In combination with the second aspect, in a possible implementation, the method further includes: the second network element receives a first request message from the first network element. The first request message is used to provide the second network element with the generated session information corresponding to the first business process to achieve the migration of the first business process to the second network element, and the generated session information is used for failure recovery of the first business process. In this case, the above-mentioned first time interval is the time interval between the first moment of receiving the first request message and the second moment of the unexpected failure occurring again on the second network element.

[0030] In the above implementation, the first time interval is set to the difference between the time when the first request message used to migrate the first business process to the second network element is received and the time when an unexpected failure occurs again on the second network element. The solution is simple and easy to implement, and can ensure the efficiency of failure recovery of the first business process.

[0031] In combination with the second aspect, in a possible implementation, the first request message includes at least one of the following: N1 interface information between the terminal device that initiates the first business process and the first network element, terminal device context information of the first business process, or first information, wherein the first information is used to indicate that the first business process is migrated from the first network element to the second network element due to an unexpected failure.

[0032] In conjunction with the second aspect, in a possible implementation, the method further includes: the second network element receives a third request message from the first network element to implement migration of the first service process to the second network element, wherein the third request message is used to instruct the second network element to rebuild session information of the first service process. In this case, the first time interval is a time interval between a third moment of receiving the third request message and a second moment of an unexpected failure occurring again on the second network element.

[0033] In the above implementation, the first time interval is set to the difference between the time when the third request message used to migrate the first business process to the second network element is received and the time when an unexpected failure occurs again on the second network element. The solution is simple and easy to implement, and can ensure the efficiency of failure recovery of the first business process.

[0034] In conjunction with the second aspect, in a possible implementation, the third request message includes: identification information of the network device, next generation application protocol identification information corresponding to the terminal device that initiates the first service process, or first information. The first information is used to indicate that the first service process is migrated from the first network element to the second network element due to an unexpected failure.

[0035] In a third aspect, the present application provides a communication method. The method may be performed by a third network element, or may be performed by a component of the third network element (eg, a processor, a chip, or a chip system, etc.). It should be understood that the third network element may be a network element in the core network.

[0036] The method includes: a third network element determines that an unexpected failure occurs in a first service request initiated to a fourth network element. The cause of the unexpected failure does not include an exception specified in a protocol and a custom exception. The third network element adjusts the number of service requests initiated to the fourth network element according to a service request success rate between the fourth network element and the third network element. The number of service requests initiated to the fourth network element is positively correlated with the service request success rate.

[0037] Here, the unexpected failure of the first service request initiated to the fourth network element can also be understood as the unexpected abnormality of the service path between the third network element and the fourth network element, and can also be understood as the unexpected abnormality of the fourth network element or the communication link between the third network element and the fourth network element. Among them, the unexpected abnormality refers to other abnormalities except the abnormalities specified in the protocol and the custom abnormalities.

[0038] In the above implementation, when the first service request initiated to the fourth network element fails unexpectedly, the third network element dynamically adjusts the number of service requests initiated to the fourth network element according to the service request success rate between the fourth network element and the third network element, so that the number of service requests initiated to the fourth network element is positively correlated with the service request success rate, that is, the higher the service request success rate, the more service requests that can be initiated, and the lower the service request success rate, the fewer service requests that can be initiated. In this way, the impact of unexpected anomalies on the service path between the third network element and the third network element on the service request initiated by the third network element to the fourth network element can be reduced, and the success rate of the service requests can be improved.

[0039] In combination with the third aspect, in a possible implementation method, the third adjusts the number of service requests initiated to the fourth network element according to the service request success rate between the fourth network element and the third network element, including: when the service request success rate between the fourth network element and the third network element is less than the first success rate threshold and greater than the second success rate threshold, the third network element adjusts the number of service requests initiated to the fourth network element according to the positive correlation with the service request success rate.

[0040] In the above implementation, only when the service request success rate between the fourth network element and the third network element is less than the first success rate threshold and greater than the second success rate threshold, the number of service requests initiated to the fourth network element is adjusted according to the positive correlation with the service request success rate. This can ensure that the number of service requests initiated to the fourth network element will not be too small, thereby ensuring the effective use of the service path between the fourth network element and the third network element.

[0041] In conjunction with the third aspect, in a possible implementation manner, the third network element adjusts the number of service requests initiated to the fourth network element according to a positive correlation relationship between the service request success rates, including:

[0042] When the service request success rate decreases from the first success rate threshold to the second success rate threshold, the number of service requests initiated to the fourth network element is reduced. When the service request success rate increases from the second success rate threshold to the first success rate threshold, the number of service requests initiated to the fourth network element is increased.

[0043] In combination with the third aspect, in a possible implementation method, the number of service requests initiated to the fourth network element is adjusted according to the service request success rate between the fourth network element and the third network element, including: when the service request success rate between the fourth network element and the third network element is less than the second success rate threshold, the third network element will adjust the number of service requests initiated to the fourth network element to the minimum number of service requests.

[0044] In the above implementation, when the service request success rate between the fourth network element and the third network element is less than the second success rate threshold, it means that there are major problems in the service path between the fourth network element and the third network element. At this time, only the minimum number of service requests is guaranteed, which can minimize the impact of unexpected exceptions on service requests.

[0045] In combination with the third aspect, in a possible implementation method, the number of service requests initiated to the fourth network element is adjusted according to the service request success rate between the fourth network element and the third network element, including: when the service request success rate between the fourth network element and the third network element is equal to or greater than the first success rate threshold, the number of service requests initiated to the fourth network element is not restricted.

[0046] In the above implementation, when the service request success rate between the fourth network element and the third network element is greater than the first success rate threshold, it means that the reliability of the service path between the fourth network element and the third network element is relatively high. At this time, the number of service requests initiated to the fourth network element is not restricted, and the utilization rate of the service path can be guaranteed.

[0047] In combination with the third aspect, in a possible implementation, the method also includes: when the service request success rate between the fourth network element and the third network element changes from greater than the first success rate threshold to less than the first success rate threshold, the third network element sends second information to the operation and maintenance center, wherein the second information is used to indicate that there is an abnormality in the service path between the fourth network element and the third network element.

[0048] In conjunction with the third aspect, in a possible implementation manner, the method further includes: when the service request success rate between the fourth network element and the third network element changes from less than the first success rate threshold to greater than or equal to the first success rate threshold, the third network element sends third information to the operation and maintenance center. The third information is used to indicate that the service path between the fourth network element and the third network element has returned to normal.

[0049] In the above implementation, the third network element may report the actual status of the service path between the fourth network element and the third network element to the operation and maintenance center according to the service request success rate, which may facilitate resource scheduling of the communication system.

[0050] In combination with the third aspect, in a possible implementation, the method also includes: the third network element sends a second service request to the fifth network element, wherein the second service request is a service request that is reduced in the process of adjusting the number of service requests initiated to the fourth network element.

[0051] In a fourth aspect, the present application provides a communication device, which includes various modules or units for executing the communication method provided by any aspect of the first to third aspects above or any possible implementation of any aspect.

[0052] In a fifth aspect, the present application provides a computer program product, which includes instructions. When the instructions are executed on a computer, the computer executes the communication method provided by any one of the first to third aspects or any possible implementation of any one of the aspects.

[0053] In a sixth aspect, the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed, it executes the communication method provided by any aspect of the first to third aspects above or any possible implementation of any aspect.

[0054] In a seventh aspect, the present application provides a communication device, at least one processor and a memory. The memory is used to store a computer program. The processor is used to execute the computer program stored in the memory, so that the communication device performs the communication method provided by any aspect of the first to third aspects or any possible implementation of any aspect.

[0055] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0056] It should be understood that the relevant data interaction process, such as sending information, can be a process of outputting information from a processor, and receiving information can be a process of receiving information by a processor. Specifically, the data output by the processor can be output to a transmitter, and the input data received by the processor can come from a receiver. Among them, the transmitter and the receiver can be collectively referred to as a transceiver.

[0057] In an eighth aspect, the present application provides a chip, the chip comprising at least a processor. The processor is used to execute computer execution instructions so that a device equipped with the chip executes the communication method provided by any aspect of the first to third aspects or any possible implementation of any aspect.

[0058] In conjunction with the eighth aspect, in a possible implementation, the chip may further include an interface circuit. The interface circuit is used to receive computer execution instructions and transmit them to the processor.

[0059] In a ninth aspect, the present application provides a communication system. The communication system may include the terminal device, the first network element, and the second network element as described above. The terminal device is used to initiate the first service process as described above, the first network element is used to execute the communication method provided by the first aspect or any possible implementation of the first aspect, and the second network element is used to execute the communication method provided by the second aspect or any possible implementation of the second aspect.

[0060] In a tenth aspect, the present application provides a communication system. The communication system may include the third network element and the fourth network element described above. The third network element is used to execute the communication method provided by the third aspect or any possible implementation of the third aspect, and the fourth network element is used to process the service request sent by the third network element. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Figure 1 It is a schematic diagram of the architecture of a communication system provided by the present application;

[0062] Figure 2 It is a schematic diagram of a communication scenario provided by this application;

[0063] Figure 3 This is another communication scenario schematic diagram provided by this application;

[0064] Figure 4 It is a flow chart of a communication method provided by the present application;

[0065] Figure 5 It is another flow chart of a communication method provided by the present application;

[0066] Figure 6 It is another flow chart of a communication method provided by the present application;

[0067] Figure 7 This is a flowchart of failure recovery of an initial registration process provided by this application;

[0068] Figure 8 This is a flowchart of failure recovery of a PDU session establishment process provided by the present application;

[0069] Fig. 9 This is another communication method provided by the present application - a flow chart;

[0070] Fig.10 It is a structural schematic diagram of a communication device provided by the present application;

[0071] Fig.11 It is a structural schematic diagram of another communication device provided by the present application;

[0072] Fig.12 This is a structural diagram of another communication device provided by the present application. DETAILED DESCRIPTION

[0073] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the accompanying drawings provided in the embodiments of the present application.

[0074] It should be understood that the technical solution provided in the embodiments of the present application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) system or new radio (NR), in addition, it can also be applicable to the use of subsequent evolution systems, such as sixth generation communication systems and even more advanced seventh generation communication systems.

[0075] The following is an illustrative example of a communication system to which the technical solution provided in this application is applicable.

[0076] See also Figure 1 , Figure 1 Schematic diagram of the architecture of a communication system provided by the present application. The communication method provided by the present application is applicable to the communication system. Figure 1 As shown, the communication system may include a radio access network (RAN) 100 and a core network (CN) 130. The RAN 100 includes at least one RAN node (e.g. Figure 1 110a and 110b) and at least one terminal (such as Figure 1 RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment ( Figure 1 The terminal is connected to the RAN node in a wireless manner. The RAN node is connected to the core network 130 in a wireless or wired manner. The core network device in the core network 130 and the RAN node in the RAN 100 can be different physical devices, or the same physical device that integrates the core network logical function and the radio access network logical function.

[0077] RAN 100 may be a cellular system related to the 3rd Generation Partnership Project (3GPP), for example, a 5G mobile communication system or a future-oriented evolution system. RAN 100 may also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (cloud radio access network, CRAN), or a wireless fidelity (wireless fidelity, WiFi) system. RAN 100 may also be a communication system that integrates two or more of the above systems.

[0078] exist Figure 1 In the communication system shown, the RAN node, which may also be sometimes referred to as an access network device, a network device, a RAN entity or an access node, etc., constitutes a part of the communication system to help the terminal achieve wireless access. The multiple RAN nodes in the communication system can be nodes of the same type or nodes of different types. In some scenarios, the roles of the RAN node and the terminal are relative, for example, Figure 1 The network element 120i may be a helicopter or a drone, which may be configured as a mobile base station. For the terminals 120j that access the RAN 100 through the network element 120i, the network element 120i is a base station. However, for the base station 110a, the network element 120i is a terminal. RAN nodes and terminals are sometimes referred to as communication devices, for example Figure 1 The network elements 110a and 110b may be understood as communication devices having base station functions, and the network elements 120a-120j may be understood as communication devices having terminal functions.

[0079] In one possible scenario, a RAN node may 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 mobile communication system, or an access node in a WiFi system. A RAN node may be a macro base station (e.g. Figure 1 110a in), micro base stations or indoor stations (such as Figure 1110b in the figure), a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, the RAN node may also be a server, a wearable device, a vehicle or an on-board device, etc. For example, the access network device in the vehicle to everything (V2X) technology may be a road side unit (RSU). All or part of the functions of the RAN node in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The RAN node may also be provided with a communication module, circuit or chip that performs corresponding communication functions. The RAN node may also be configured with program instructions for performing corresponding communication functions and corresponding program instructions. The RAN node in the present application may also be a logical node, a logical module or software that can implement all or part of the functions of the RAN node.

[0080] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH).

[0081] exist Figure 1In the communication system shown, the terminal (i.e., terminal) can be a device or module that accesses the above communication system and has corresponding communication functions. The terminal can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. The terminal can be widely used in various scenarios, for example, device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a mechanical arm, a smart home device, a transport vehicle with wireless communication function, a communication module, etc. The embodiments of the present application do not limit the device form of the terminal. The terminal is usually provided with a communication module, a circuit or a chip that performs the corresponding communication function. The terminal is also configured with program instructions for performing the corresponding communication function.

[0082] In addition, the core network 130 mainly includes one or more of the following: user plane function (UPF) network element, data network (DN), session management function network element, registration function network element, policy control function (PCF) network element, short message service function (SMSF) network element, selection function network element, identification storage function network element and unified data management (UDM) network element. It should be understood that there are interfaces between the network elements to achieve distributed connection. For example, the network architecture can be a network architecture after the introduction of RAN service, and the interfaces between the RAN equipment and each network element can all be service interfaces.

[0083] To facilitate understanding of the functions of the network architecture, the functions of each network element are briefly described below.

[0084] The user plane functional network element is mainly responsible for processing user messages, such as forwarding, billing, etc. It can serve as the anchor point for the protocol data unit (PDU) session (i.e., PDU session) connection, that is, it can serve as the PDU session anchor (PSA), responsible for filtering UE10 data messages, data transmission or forwarding, rate control, generating billing information, user plane session quality of service (QoS) processing, uplink transmission authentication, transmission level verification, downlink data packet caching and downlink data notification triggering, etc. The user plane functional network element can also serve as a branch point for multi-homed PDU sessions.

[0085] Data network is a network that provides data transmission services for users, such as Internet protocol (IP) Multimedia service (IMS), Internet, etc. Data network can include application server (AS), which is a software framework that provides an environment for application running, and is used to provide security, data, transaction support, load balancing and large distributed system management services for application. Terminal devices obtain application messages by communicating with application servers.

[0086] The session management function network element is mainly responsible for all control plane functions of session management of terminal devices, including selection and control of user plane function network elements, IP address allocation and management, session QoS management, obtaining policy and charging control (PCC) policies from the policy control function network element, etc. The session management function network element also serves as the termination point of the session management part in the non-access stratum (NAS) message.

[0087] The registration function network element may be used to provide access and authentication functions for the terminal device. Exemplarily, the registration function network element may include an access and mobility management function network element.

[0088] The policy control function network element has the function of providing policy rules to the control plane functional entity.

[0089] The SMS function network element is responsible for processing SMS services in the network, such as SMS registration and deregistration, SMS forwarding, SMS call caching, etc.

[0090] The selection function network element can be used to select a core network element for a terminal device. Specifically, the core network elements in the network can be registered with the selection function network element, and then the selection function network element can select a target core network element for the terminal device from the registered core network elements. The selection function network element can also obtain the contract data of the terminal device from the unified data management network element, and then select the target core network element for the terminal device based on the information registered with the core network element and the contract data. Exemplarily, the selection function network element may include a network function repository function (NFR) network element.

[0091] The identification storage function network element can be used to store the correspondence between the temporary identification and the permanent identification of the terminal device, wherein after the network function registration function network element obtains the correspondence between the temporary identification and the permanent identification of the terminal device, the correspondence between the temporary identification and the permanent identification of the terminal device can be stored in the identification storage function network element. Exemplarily, the identification storage function network element can be a unified database network element.

[0092] The unified data management network element is mainly responsible for the contract data management of terminal devices, including the storage and management of terminal device identification, access authorization of terminal devices, etc.

[0093] It should be noted that the naming of each network element in the core network in the embodiment of the present application is exemplary and not limiting. With the evolution of technology, entities with corresponding functions of each network element may also adopt other naming methods, and there is no specific limitation on this. For example, for access and mobility management network elements, they may be named access management function network element, mobility management function network element, registration management function network element, etc.

[0094] See also Figure 2 , Figure 2 This is a schematic diagram of a communication scenario provided by this application, and a communication method provided by this application is applicable to this scenario. Figure 2 As shown, the scenario may include a terminal device, a network device on the wireless access network side, and a first network element and a second network element on the core network side. In an embodiment of the present application, the first network element may be a core network element for storing a terminal device context of the terminal device or for managing access and mobility of the terminal device. Exemplarily, the first network element may be an access and mobility management function network element. The second network element is a backup network element of the first network element. Optionally, the second network element and the first network element may be located at different sites.

[0095] Among them, the terminal device, the network device, the first network element and the second network element can work together to implement the various steps of the communication method provided in this application. For specific implementation, please refer to the corresponding description below.

[0096] See also Figure 3 , Figure 3 This is another communication scenario diagram provided by the present application, and another communication method provided by the present application is applicable to this scenario. Figure 3 As shown, the scenario may include a third network element and a fourth network element on the core network side. In the embodiment of the present application, the third network element and the fourth network element may be any two network elements on the core network side that have a communication connection, such as the third network element may be an access and mobility management function network element, and the fourth network element may be a session management function network element.

[0097] Among them, the third network element and the fourth network element can also work together to implement the various steps of the communication method provided in this application. For specific implementation, please refer to the corresponding description below.

[0098] here, Figure 2 or Figure 3 The description of the terminal equipment, network equipment and each network element involved can be found in Figure 1 The relevant description in the communication system shown will not be repeated here.

[0099] The previous article is based on Figure 1-Figure 3 The communication system and communication scenario to which the communication method provided in this application is applicable are described below. Figure 1-Figure 3 The content shown describes in detail the implementation process of the communication method provided by this application.

[0100] Example 1

[0101] In the actual communication process, there may be some exceptions other than the exceptions specified in the protocol and the custom exceptions on the service path corresponding to the service process, which may also cause the service process to fail. For example, there may be exceptions such as internal processing logic exceptions of the network element or application defects (i.e., software bugs) in the service path, which may also cause the service process to fail. However, since the existing exception detection mechanism cannot detect such exceptions, spare network elements or spare communication links will not be used to implement failure recovery of the service process. Therefore, based on the existing failure recovery process, the service process will be initiated again on the service path with such exceptions, which will cause the continuous failure of the service process and affect the user experience of the terminal device.

[0102] Based on this, the technical problem to be solved by this application is: how to avoid the continuous failure of business processes caused by anomalies that cannot be detected by existing anomaly detection mechanisms.

[0103] To solve this problem, this application provides a communication method. Figure 4 , Figure 4 This is a flow chart of a communication method provided by this application. Figure 4 As shown, the method comprises the following steps:

[0104] S401, when an unexpected failure occurs in a first service process, the first network element determines a second network element, where the cause of the unexpected failure does not include an exception specified by the protocol and a user-defined exception.

[0105] In some feasible implementations, the first network element may determine the second network element when determining that the first business process has an unexpected failure. The second network element is a backup network element for the first network element. The causes of the above-mentioned unexpected failure do not include exceptions specified in the protocol and custom exceptions. In other words, the unexpected failure is a failure caused by an unexpected exception, and the unexpected exception is an exception other than the exception specified in the protocol and the custom exception.

[0106] It should be understood that in the embodiments of the present application, the exceptions specified in the protocol and the custom exceptions are usually exceptions that cannot be recovered by switching the service path. Exemplarily, the exceptions specified in the protocol include, but are not limited to: the reasons that may cause the failure of the service process specified in the current communication protocol and the future communication protocol, such as arrears, contract restrictions, etc. Custom exceptions mainly refer to the reasons that may cause the failure of the service process that can be flexibly configured by the user, such as the lack of support for the Internet Protocol version 6 (IPv6) access type, etc.

[0107] It should be noted that, in the embodiment of the present application, the unexpected failure of the first business process may refer to the failure caused by the unexpected anomaly of the network element or communication link associated with the first business process. Alternatively, the unexpected failure of the first business process may also refer to the unexpected anomaly on the business path corresponding to the first business process. Here, the business path corresponding to the first business process may include the network elements and communication links associated with the first business process. It should be understood that in the embodiment of the present application, the network elements or communication links associated with the first business process refer to the network elements and communication links required to be used in the implementation of the first business process, and these network elements and communication links are used to implement the operations such as sending and receiving request messages and response messages involved in the first business process and processing request messages and response messages.

[0108] In addition, in the embodiment of the present application, since the event of the unexpected failure of the first business process is determined by the first network element, it can also be expressed as the unexpected failure of the first business process on the first network element. It should be understood that the unexpected failure of the first business process on the first network element described in the present application does not mean that the unexpected exception that causes the unexpected failure must occur on the first network element, but may also occur on other network elements associated with the first business process and interacting with the first network element, and may also occur on the communication link between other network elements associated with the first business process and interacting with the first network element and the first network element.

[0109] Optionally, in an embodiment of the present application, unexpected anomalies include, but are not limited to: internal logic processing anomalies of network elements, application software defects, transmission packet loss, system probabilistic processing failure of the communication system, etc.

[0110] In one possible implementation, when the first network element determines that the first business process has failed, the corresponding failure reason value may be obtained. Then, the first network element may determine whether the failure reason value is a failure reason value corresponding to the exceptions specified in the protocol and the custom exceptions. If the first network element determines that the failure reason value is a failure reason value corresponding to the exceptions specified in the protocol and the custom exceptions, it is determined that the first business process failed due to the exceptions specified in the protocol or the custom exceptions, and the existing failure recovery solution may be used to perform failure recovery of the first business process. If the first network element determines that the failure reason value is not a failure reason value corresponding to the exceptions specified in the protocol and the custom exceptions, it may be determined that the first business process failed due to other exceptions other than the exceptions specified in the protocol and the custom exceptions, that is, it is determined that an unexpected failure has occurred in the first business process.

[0111] Optionally, the failure reason value of the first service process may be included in a message received by the first network element indicating that the first service process has failed. Exemplarily, the message may be a request timeout message received from network element A after the first network element sends a service request associated with the first service process to a certain network element (here, network element A is assumed to be for easy distinction).

[0112] In a possible implementation, after determining that an unexpected failure occurs in the first service process, the first network element may determine a target network element set, wherein the target network element set may include one or more backup network elements of the first network element, and then the first network element may select a second network element from the one or more backup network elements.

[0113] Optionally, the first network element may randomly select the second network element from the one or more backup network elements, or may select the second network element based on the usage of these backup network elements. This application does not limit the specific implementation process of the first network element selecting the second network element from these one or more backup network elements.

[0114] Optionally, the above-mentioned target network element set can be provided by the network registration function network element to the first network element during the network function discovery phase, or can be determined by the first network element based on sub-local configuration information. This application does not impose any specific restrictions on this.

[0115] S402: The first network element migrates the first service process to the second network element to indicate that a subsequent process of the first service process is initiated through the second network element.

[0116] In some feasible implementations, after determining that an unexpected failure occurs in the first service process, the first network element may migrate the first service process to the second network element to indicate that a subsequent process of the first service process is initiated through the second network element. In other words, the first network element may migrate the first service process to the second network element so that the second network element replaces the first network element in executing the processing of requests and responses related to the first service process.

[0117] In the above implementation, when the first service process fails and the reason for the failure does not include the exception specified by the protocol and the custom exception, the first network element will migrate the first service process to the standby second network element to indicate that the subsequent process of the first service process is initiated through the second network element. This method can prevent the first service process from being repeatedly initiated on the first network element where an unexpected failure has occurred, thereby avoiding the continuous failure of the first service process, reducing service delays and improving the user experience of terminal devices.

[0118] Regarding the process of migrating the first service process from the first network element to the second network element, the present application provides multiple possible implementation methods, which will be described below respectively.

[0119] First, the implementation method of business process migration:

[0120] See also Figure 5 , Figure 5 This is another flow chart of a communication method provided by this application. Figure 5 As shown, step S402 may include the following steps:

[0121] S4021, when the service failure of the first network element is restored to the redirection mode, the first network element sends a first request message to the second network element, the first request message is used to provide the second network element with the session information that has been generated corresponding to the first service process. The second network element receives the first request message accordingly.

[0122] In some possible implementations, after determining that an unexpected failure occurs in the first business process, the first network element may obtain a business recovery method of the first network element. In the case of determining that the business failure recovery of the first network element is a redirection method, it may generate and send a first request message to the second network element to achieve the migration of the first business process to the second network element. Among them, the first request message is used to provide the second network element with the already generated session information corresponding to the first business process, and the already generated session information can be used for the subsequent failure recovery of the second network element to execute the first business process. It should be understood that the above-mentioned already generated session information refers to the session information associated with the first business process generated by the first network element in the process of executing the first business process. Accordingly, the second network element can receive the first request message and obtain the above-mentioned already generated session information. Further, the second network element can replace the first network element to continue to execute the unfinished operation of the first business process.

[0123] In one possible implementation, the first request message includes at least one of the following: N1 interface information between the terminal device that initiates the first business process and the first network element, terminal device context information of the first business process, or first information, wherein the first information is used to indicate that the first business process is migrated from the first network element to the second network element due to an unexpected failure. In other words, the first information is used to indicate that the terminal device that initiates the first business process switches to the second network element due to an unexpected failure in the first business process, and the cause of the unexpected failure does not include exceptions specified in the protocol and custom exceptions. In other words, the first information is used to indicate that the first business process fails due to an unexpected exception other than exceptions specified in the protocol and custom exceptions, and is migrated from the first network element to the second network element.

[0124] Optionally, the N1 interface message between the terminal device initiating the first service flow and the first network element may be transmitted via an N1 interface container message (ie, n1_message_container). The terminal device context information of the terminal device initiating the first service flow may be transmitted via a registration context container message (ie, registration_ctxt_container).

[0125] Optionally, the first information may be a specific bit in the first request message, and the value of the bit is a preset value. Exemplarily, the first information may be the first idle bit or the last idle bit of the first request message, and the value of the idle bit is 1.

[0126] Optionally, the first request message is referred to as an N1 message notification request corresponding to the first service flow. Exemplarily, the first request message can be expressed as Namf_communication_N1message_notify_request.

[0127] Optional, such as Figure 5 As shown, after step S4021, the method may further include the following steps:

[0128] S4022: The second network element sends a first response message to the first network element to indicate that the first request message is correctly received. Correspondingly, the first network element receives the first response message.

[0129] In actual implementation, after correctly receiving the first request message, the second network element may send a first response message to the first network element to indicate that the first request message has been correctly received. Correspondingly, after receiving the first response message, the first network element can determine that the second network element has correctly received the first request message.

[0130] Optionally, the first request message may be referred to as an N1 message notification response corresponding to the first service flow. Exemplarily, the first request message may be expressed as Namf_communication_N1message_notify_response.

[0131] In the above implementation, when the service failure is restored in a redirection mode, the first network element can provide the second network element with the session information corresponding to the first service process, so as to realize the migration of the first service process to the second network element. The method is simple and easy to implement, which can not only ensure the efficiency of failure recovery of the first service process, but also make the communication method provided by the present application applicable to the scenario where the service failure is restored in a redirection mode.

[0132] Method 2 for implementing the first business process migration:

[0133] like Figure 5 As shown, step S402 may also include the following steps:

[0134] S4023: When the service failure of the first network element is restored in a rerouting manner, a second request message is sent to the network device, the second request message is used to instruct the network device to reroute the first service flow to the second network element. Correspondingly, the second network element receives the second request message.

[0135] In some feasible implementations, after determining that an unexpected failure occurred in the first business process, the first network element may obtain a business recovery method for the first network element. When it is determined that the business failure recovery of the first network element is a rerouting method, it may generate and send a second request message to the network device to implement the migration of the first business process to the second network element. The second request message is used to instruct the network device to reroute the first business process to the second network element. Here, the above-mentioned first business process is initiated by the terminal device to the first network element through the network device, and the relevant information of the first business process is forwarded by the network device between the terminal device and the first network element.

[0136] Correspondingly, the network device may receive the second request message, and determine to reroute the first service process to the second network element according to the second request message.

[0137] In an optional implementation, the second request message includes at least one of the following: N1 interface information between the terminal device that initiates the first service process and the first network element, and identification information of the second network element.

[0138] Optionally, the N1 interface information between the terminal device that initiates the first service process and the first network element may be transmitted via a next generation (NG) application protocol message.

[0139] Optional, such as Figure 5 As shown, after step S4023, the method may further include the following steps:

[0140] S4024, the network device initiates a first service process to the second network element.

[0141] After receiving the second request message, the network device may determine that the first service flow needs to be rerouted to the second network element. Then, the network device may initiate the first service flow to the second network element so that the second network element re-initiates the subsequent flow of the first service flow.

[0142] In the above implementation, when the service failure is restored in a rerouting manner, the first network element can instruct the network device to reroute the first service process to the second network element, so as to realize the migration of the first service process to the second network element. The method is simple and easy to implement, which can not only ensure the efficiency of failure recovery of the first service process, but also make the communication method provided by the present application applicable to the scenario where the service failure is restored in a rerouting manner.

[0143] First business process migration implementation method 3:

[0144] like Figure 5 As shown, step S402 may further include the following steps:

[0145] S4025, the first network element sends a third request message to the second network element, where the third request message is used to instruct the second network element to reestablish session information of the first service flow. Correspondingly, the second network element receives the third request message.

[0146] In some possible implementations, after determining that an unexpected failure occurred in the first business process, the first network element may send a third request message to the second network element. The third request message is used to instruct the second network element to rebuild the session information of the first business process. It can also be said that the third request message is used to send the session information of the terminal device that initiated the first business process and the relevant information generated when the first network element executes the first business process to the second network element, so that the second network element can subsequently replace the first network element to continue to execute the above-mentioned first business process. Correspondingly, the second network element can receive the third request message and determine to rebuild the session information of the first business process.

[0147] In one possible implementation, the third request message includes: identification information of the network device, next generation application protocol identification information corresponding to the terminal device that initiated the first business process, or the first information. The first information is used to indicate that the first business process is migrated from the first network element to the second network element due to an unexpected failure. In other words, the first information is used to indicate that the terminal device that initiated the first business process switches to the second network element due to an unexpected failure of the first business process, and the cause of the unexpected failure does not include exceptions specified in the protocol and custom exceptions. In other words, the first information is used to indicate that the first business process fails due to unexpected exceptions other than exceptions specified in the protocol and custom exceptions, and is migrated from the first network element to the second network element.

[0148] Optionally, the identification information of the network device may be a global unified radio access network identification of the network device associated with the first service process. The next generation application protocol identification information corresponding to the terminal device may be a next generation radio access network application protocol identification (ie, NG-RAN application protocol ID, abbreviated as NGAP ID) of the terminal device.

[0149] Optionally, the first information may be a specific bit in the first request message, and the value of the bit is a preset value. Exemplarily, the first information may be the first idle bit or the last idle bit of the first request message, and the value of the idle bit is 1.

[0150] Optionally, the third request message may also be referred to as an N1 message notification request corresponding to the first service flow. Exemplarily, the first request message may be expressed as Namf_communication_N1message_notify_request.

[0151] Optional, such as Figure 5As shown, after step S4025, the method may further include the following steps:

[0152] S4026, the second network element initiates a terminal device context modification process to the network device so that the terminal device switches to the second network element.

[0153] After reconstructing the session information of the first service process, the second network element may initiate a terminal device context modification process to the network device, so that the terminal device that initiated the first service process is switched from the first network element to the second network element. In other words, the terminal device no longer implements the first service process through the first network element, but implements the first service process through the second network element.

[0154] Optionally, the second network element may send a terminal device context modification request to the network device. Accordingly, the network device receives the terminal device context modification request and feeds back a terminal device context modification response to the second network element, indicating that it correctly receives the terminal device context modification request. Further, after receiving the terminal device context modification response, the second network element may send an update instruction of the first business process to the terminal device that initiates the first business process, indicating that the subsequent process of the first business process is executed by the second network element. Accordingly, the terminal device may receive the update instruction of the first business process, and after completing the update of the first business process, it will feed back an update completion message of the first business process to the second network element. After receiving the update completion message of the first business process, the second network element may feed back a second response message for the third request message to the first network element, so as to indicate that the first business process has been migrated from the first network element to the second network element through the second response message. Accordingly, the first network element may receive the second response message, and determine that the migration of the first business process is completed according to the second response message.

[0155] Optionally, after the first service process is migrated from the first network element to the second network element, the first network element may update the relevant information of the second network element to its peripheral functional network elements, including but not limited to: a session management functional network element, a unified data management network element, a policy control functional network element, etc. associated with the first network element.

[0156] In the above implementation, the first network element can directly instruct the second network element to rebuild the session information of the first service flow through the third request message to achieve the migration of the first service flow to the second network element. The method is simple and easy to implement, and can ensure the efficiency of failure recovery of the first service flow.

[0157] It should be noted that, combined with Figure 4 or Figure 5 In the communication method shown in the figure, when the first network element and the second network element are each other's backup network elements, after the first service process is migrated from the first network element to the second network element due to an expected failure, if the first service process fails again unexpectedly on the second network element, according to Figure 4 or Figure 5 According to the communication method shown, the first service process will be migrated to the first network element again. However, if the unexpected exception on the first network element has not been restored, the first service process will be migrated to the second network element again. Similarly, if the unexpected exception on the second network element has not been restored, the first service process will be migrated to the first network element again. This will cause the first service process to repeatedly switch between the first network element and the second network element in a short period of time, that is, forming a ping-pong switching effect, which will bring additional processing loads to the first network element and the second network element.

[0158] To resolve this issue, see Figure 6 , Figure 6 This is another flow chart of a communication method provided by this application. Figure 6 As shown, the method may also include the following steps:

[0159] S403: If the first service process fails again, the second network element determines whether the failure that occurs again is an unexpected failure.

[0160] In some possible implementations, when a first business process unexpectedly fails on a first network element and is migrated from the first network element to a second network element, if the first business process fails again on the second network element, the second network element determines whether the repeated failure is an unexpected failure.

[0161] Exemplarily, when the second network element determines that the first business process has failed again, it can obtain the failure reason value for the second failure. Then, the second network element can determine whether the failure reason value is the failure reason value corresponding to the exceptions and custom exceptions specified in the protocol. If the second network element determines that the failure reason value is the failure reason value corresponding to the exceptions and custom exceptions specified in the protocol, it is determined that the first business process failed due to the exceptions specified in the protocol or the custom exceptions, and the existing failure recovery plan can be used to recover the failure of the first business process. If the second network element determines that the failure reason value is not the failure reason value corresponding to the exceptions and custom exceptions specified in the protocol, it can be determined that the first business process has failed unexpectedly again.

[0162] S404: When the reoccurring failure is an unexpected failure, if the second network element determines that the first time interval between two unexpected failures of the first business process on the first network element and the second network element is less than or equal to the time interval threshold, the first business process will no longer be migrated to the first network element.

[0163] In some possible implementations, when the failure of the first business process that occurs again is an unexpected failure, if the second network element determines that the first time interval between the two unexpected failures of the first business process that occurred on the first network element and the second network element is less than or equal to the time interval threshold, the first business process will no longer be migrated to the first network element. It should be noted here that the unexpected failure of the first business process that occurs in the first network element is the unexpected failure determined by the first network element in step S401 above, and the unexpected failure of the first business process that occurs in the second network element is the unexpected failure determined by the second network element in step S403 above, and the first time interval is the interval between the occurrence times of the two unexpected failures.

[0164] In the above implementation, when the first service process fails unexpectedly at both the first network element and the second network element, and the time interval between the two unexpected failures is less than or equal to the time interval threshold, the second network element will not migrate the first service process to the first network element again. When the first network element's abnormality is not recovered, this solution can avoid the continuous failure of the first service process caused by the first service process switching back and forth between the first network element and the second network element (i.e., ping-pong switching), and avoid the additional processing load caused by the ping-pong switching to the first network element and the second network element.

[0165] In a possible implementation, when the first network element adopts implementation 1 of the first service process migration, the first time interval is the time interval between the first moment of receiving the first request message and the second moment of the unexpected failure occurring again on the second network element. That is, when the second network element receives the first request message and determines that the first request message includes the first information, the first moment of receiving the first request message can be determined as the moment of the unexpected failure of the first service process occurring in the first network element. Then, the second network element can determine the difference between the second moment of the unexpected failure occurring again on the second network element and the first moment as the first time interval.

[0166] In the above implementation, the first time interval is set to the difference between the time when the first request message used to migrate the first business process to the second network element is received and the time when an unexpected failure occurs again on the second network element. The solution is simple and easy to implement, and can ensure the efficiency of failure recovery of the first business process.

[0167] In another possible implementation, when the first network element adopts implementation 3 of the first service process migration, the first time interval is the time interval between the third moment of receiving the third request message and the second moment of the unexpected failure occurring again on the second network element. That is, when the second network element receives the third request message and determines that the third request message includes the first information, the third moment of receiving the third request message may be determined as the moment of the unexpected failure of the first service process occurring in the first network element. Then, the second network element may determine the difference between the second moment of the unexpected failure occurring again on the second network element and the third moment as the first time interval.

[0168] In the above implementation, the first time interval is set to the difference between the time when the third request message used to migrate the first business process to the second network element is received and the time when an unexpected failure occurs again on the second network element. The solution is simple and easy to implement, and can ensure the efficiency of failure recovery of the first business process.

[0169] It should be understood that the above description of the method for the second network element to determine the first time interval is merely exemplary. In actual implementation, the second network element may also use other methods to determine the first time interval, and this application does not impose any specific restrictions on this.

[0170] Optionally, the method may further include the following steps:

[0171] S405, when the reoccurring failure is an unexpected failure, if the second network element determines that the first time interval between two unexpected failures of the first business process occurring on the first network element and the second network element is greater than the time interval threshold, the first business process is migrated to the first network element.

[0172] In some possible implementations, when the reoccurring failure is an unexpected failure, if the second network element determines that the first time interval between two unexpected failures of the first service process occurring on the first network element and the second network element is greater than the time interval threshold, the first service process may be migrated to the first network element. Here, the specific implementation process of the second network element migrating the first service process to the first network element is similar to the implementation process of the first network element migrating the first service process to the second network element described above, and can be described together in the description of step S402 above, and will not be repeated here.

[0173] In the above implementation, when the time interval between two unexpected failures is greater than the time interval threshold, the first business process is allowed to be migrated to the first network element again. This can avoid the situation where the first network element has returned to normal but the first business process has not been switched back, thereby improving the flexibility and practicality of the communication method provided in this application.

[0174] It should be noted that, in a possible implementation, the first service process may be an initial registration process initiated by a terminal device. In this case, the first network element may be an access and mobility management function network element (here it is assumed to be the first AMF network element) to which the terminal device is connected before an unexpected failure of the first service process occurs, and the second network element may be an access and mobility management function network element (here it is assumed to be the second AMF network element) that is a backup for the first network element. It should be understood that in the case where the first service process may be an initial registration process initiated by a terminal device, the first network element may adopt the implementation method 1 of the first service process migration or the implementation method 2 of the first service process migration described above.

[0175] The following will take the initial registration process initiated by the terminal device as an example to exemplify the implementation process of the communication method provided in this application.

[0176] See also Figure 7 , Figure 7 This is a flowchart of a failed recovery process of an initial registration process provided by this application. Figure 7 As shown, the failure recovery process may include the following steps:

[0177] S701, the terminal device initiates the initial registration process of the terminal device to the first AMF network element through the network device.

[0178] The specific process may include a security management process, a process for obtaining contract data, and a process for obtaining a session management policy. The specific implementation of these processes can be found in the corresponding implementation of the existing initial registration process, and this application will not go into details here.

[0179] S702, the first AMF network element selects the first PCF network element and sends an access management policy control creation request to the first PCF network element.

[0180] In the process of obtaining the session management policy, the first AMF network element can select the first PCF network element and send an access management policy control creation request to the first PCF network element to request the first PCF network element to provide a session management policy.

[0181] S703, when the first PCF network element is unable to respond to the access management policy control creation request, the first AMF network element sends a message timeout information to the first AMF network element. Correspondingly, the first AMF network element receives the message timeout information.

[0182] After the first PCF network element receives the access management policy control creation request from the first AMF network element, if it determines that it cannot respond to the request, it can send a message timeout information to the first AMF network element.

[0183] S704, the first AMF network element determines that the initial registration process fails unexpectedly and selects the second AMF network element.

[0184] If the first AMF network element receives message timeout information from the first PCF network element, it can be determined that the first PCF network element cannot respond to the access management policy control creation request, and then it can be determined that the initial registration process has failed. Further, the first AMF network element can determine whether the reason for the failure of the initial registration process is a protocol predefined exception or a custom exception. If it is determined to be no, it can be determined that the initial registration process has an unexpected failure. Further, the first AMF network element can select a spare second AMF network element.

[0185] When the service fails and is restored to redirection mode, perform the following steps:

[0186] S705: When the service failure is restored to redirection mode, the first AMF network element sends a first request message to the second AMF network element.

[0187] When the first AMF network element determines that its service failure is restored in a redirection mode, it can send a first request message to the second AMF network element. Here, the first request message can also be called an N1 interface message notification request, that is, Namf_communication_N1message_notify_request. The first request message may include the following items: an N1 interface container message, a registration context container message of the terminal device, and the first information described above. Among them, the N1 interface container message is used to transmit the N1 interface information between the terminal device and the first AMF network element, and the registration context container message can be used to transmit the registration context information related to the terminal device.

[0188] S706, the second AMF network element sends a first response message to the first AMF network element.

[0189] When the second AMF network element correctly receives the first request message, it can send a first response message to the first AMF network element. Accordingly, the first AMF receives the first response message, that is, it determines that the second AMF has correctly received the first request message. Here, the first response message can also be called N1 interface message notification response, that is, Namf_communication_N1message_notify_response.

[0190] When the service fails and the rerouting mode is used, perform the following steps:

[0191] S707, the first AMF network element sends a second request message to the network device.

[0192] When the first AMF network element determines that its service failure is restored to the rerouting mode, it can send a second request message to the network device. Here, the first request message can also be called rerouting non-access stratum (NAS), that is, reroute_NAS_request. The second request message may include the following items: the next generation application protocol message and the identification information of the second AMF network element. Among them, the next generation application protocol message is used to transmit the N1 interface information between the terminal device and the first AMF network element.

[0193] S708, the network device sends a registration request to the second AMF network element.

[0194] After receiving the above-mentioned second request message, the network device can determine the second AMF network element according to the second request message, and send a registration request (i.e., registration request) to the second AMF network element.

[0195] After step S706 or step S708, perform the following steps:

[0196] S709, the second AMF network element re-initiates the subsequent registration process.

[0197] After the initial registration process is migrated to the second AMF network element, the second AMF network element can re-initiate the subsequent registration process of the initial registration process to complete the failure recovery of the initial registration process.

[0198] S710, the second AMF network element sends a registration acceptance message to the terminal device.

[0199] After the second AMF network element re-initiates the subsequent registration process, it can also send a registration acceptance message to the terminal device to notify the terminal device that it has re-initiated the initial registration process.

[0200] Through the above implementation, it is possible to avoid the situation where the initial registration process fails unexpectedly and the initial registration process is repeatedly initiated on the first AMF network element where the unexpected failure has occurred. This can avoid the continuous failure of the initial registration process and reduce the service delay of the initial registration process.

[0201] In a possible implementation, the first service process may be a service process initiated by the terminal device after the initial registration, such as PDU session establishment and service cell switching. In this case, the first network element may be the access and mobility management function network element (here it is assumed to be the first AMF network element) to which the terminal device is connected before the unexpected failure of the first service process, and the second network element may be the access and mobility management function network element (here it is assumed to be the second AMF network element) that is a backup for the first network element. It should be understood that in this case, the first network element may adopt the implementation method 3 of the first service process migration described above.

[0202] The following will take the PDU session establishment process after the terminal device completes registration as an example to exemplify the implementation process of the communication method provided in this application.

[0203] See also Figure 8 , Figure 8 This is a flowchart of a failure recovery process of a PDU session establishment process provided by this application. Figure 8 As shown, the failure recovery process may include the following steps:

[0204] S801, the terminal device initiates a PDU session establishment process to the first AMF network element through the network device.

[0205] The specific process may include establishing a session management context, acquiring a session management policy, and other processes. The specific implementation of these processes can be found in the corresponding implementation in the existing PDU session establishment process, and this application will not go into details here.

[0206] S802, the first SMF network element sends a PDU session establishment rejection to the first AMF network element.

[0207] In the process of acquiring the session management policy, if the PDU session establishment process fails, the first SMF network element may send a PDU session establishment rejection (i.e., PDU session establishment reject) to the first AMF network element. Correspondingly, if the first AMF network element receives the PDU session establishment rejection from the first SMF network element, it can be determined that the PDU session establishment process has failed.

[0208] S803, the first AMF network element determines that an unexpected failure occurs in the PDU session establishment process and selects a second AMF network element.

[0209] When the first AMF network element determines that the PDU session establishment process has failed, it can determine whether the cause of the failure of the PDU session establishment process is a protocol predefined exception or a custom exception. If it is determined to be no, it can be determined that the PDU session establishment process has an unexpected failure. Furthermore, the first AMF network element can select a spare second AMF network element.

[0210] S804, the first AMF network element sends a third request message to the second AMF network element.

[0211] When the first AMF network element determines that an unexpected failure occurs in the PDU session establishment process, the third request message may be sent to the second AMF network element. Here, the third request message may also be referred to as an N1 interface message notification request, i.e., Namf_communication_N1message_notify_request. The third request message may include the following items: identification information of the network device, next-generation application protocol identification information corresponding to the terminal device that initiates the PDU session establishment process, or the first information. Among them, the identification information of the network device may be the global unified wireless access network identification of the network device. The next-generation application protocol identification information corresponding to the terminal device may be the NGAP ID of the terminal device.

[0212] S805, the second AMF network element sends a terminal device context modification request to the network device.

[0213] After receiving the above-mentioned third request message, the second AMF network element may send a terminal device context modification request (i.e., UE context modification request) to the network device to trigger the network device to update the terminal device context information of the terminal device.

[0214] S806, the network device sends a terminal device context modification response to the second AMF network element.

[0215] After correctly receiving the terminal device context modification request, the network device may send a terminal device context modification response (i.e., UE context modification response) to the second AMF network element to notify it that the terminal device context modification request has been received.

[0216] S807, the second AMF network element sends a registration update indication to the terminal device.

[0217] After correctly receiving the terminal device context modification request, the network device may also send a registration update indication to the terminal device to instruct the terminal device to complete the registration update.

[0218] S808, the terminal device sends a registration update success indication to the second AMF network element.

[0219] After completing the registration update, the terminal device can send a registration update success indication to the second AMF network element.

[0220] S809, the second AMF network element sends a second response message to the first AMF network element.

[0221] After receiving the registration update success indication from the terminal device, the second AMF network element can determine that the terminal device has completed the registration update. In this case, the second AMF network element can send a second response message to the first AMF network element to notify the first AMF network element that the PDU session establishment process has been migrated to the second network element.

[0222] S810, the first AMF network element notifies its surrounding network elements that the PDU session establishment process has been migrated to the second AMF network element.

[0223] After receiving the second response message from the second AMF network element, the first AMF network element notifies its surrounding network elements that the PDU session establishment process has been migrated to the second AMF network element.

[0224] Through the above implementation, it is possible to avoid the situation where, in the event of an unexpected failure in the PDU session establishment process, the PDU session establishment process is repeatedly initiated on the first AMF network element where the unexpected failure has occurred. This can avoid the continuous failure of the PDU session establishment process and reduce the service delay of the PDU session establishment process.

[0225] Example 2

[0226] In the process of a network element in the core network (for the convenience of explanation, it is assumed to be the third network element here) initiating a service request to another network element (for the convenience of explanation, it is assumed to be the fourth network element here), when an unexpected failure occurs in a service request, it indicates that there is an unexpected abnormality in the service path between the third network element and the fourth network element (the service path includes the third network element, the fourth network element, and the communication link between the third network element and the third network element). If the unexpected abnormality persists, the success rate of the service request initiated by the third network element to the fourth network element will continue to decrease, which will seriously affect the implementation of the service process associated with the third network element and the fourth network element.

[0227] To solve this problem, the present application provides another communication method. It should be noted that the communication method is applicable to the case where there is service interaction between the third network element and the fourth network element, and the third network element can send service requests corresponding to different service processes to the fourth network element. Fig. 9 , Fig. 9 This is another communication method provided by the present application - a flow chart. Fig. 9 As shown, the communication method may include the following steps:

[0228] S901: The third network element determines that an unexpected failure occurs in a first service request initiated to a fourth network element.

[0229] In some feasible implementations, in the process of the third network element initiating multiple service requests to the fourth network element, when the third network element determines that the first service request initiated by it to the fourth network element fails, the third network element may further determine whether the first service request fails unexpectedly. Among them, the cause of the unexpected failure does not include exceptions specified in the protocol and custom exceptions. In other words, the unexpected failure is a failure caused by an unexpected exception, and the unexpected exception is other exceptions other than the exceptions specified in the protocol and the custom exceptions. It should be understood that in the embodiments of the present application, the exceptions specified in the protocol and the custom exceptions are usually exceptions that cannot be recovered by switching the service path. Exemplarily, the exceptions specified in the protocol include but are not limited to: reasons that may cause the failure of the business process specified in the current communication protocol and future communication protocols, such as arrears, contract restrictions, etc. Custom exceptions mainly refer to the reasons that can be flexibly configured by users that may cause the failure of the business process, such as unsupported IPv6 access types, etc.

[0230] It should also be noted that, in the embodiment of the present application, the unexpected anomaly that causes the unexpected failure of the first service request may occur on the fourth network element, or may occur on the communication link between the third network element and the fourth network element, and the present application does not impose specific restrictions on this. In addition, the unexpected failure of the first service request initiated to the fourth network element can be understood as an unexpected anomaly in the service path between the third network element and the fourth network element.

[0231] In a possible implementation, when the third network element determines that the first service request fails, the corresponding failure reason value may be obtained. Then, the third network element may determine whether the failure reason value is a failure reason value corresponding to an exception specified in the protocol and a custom exception. If the third network element determines that the failure reason value is not a failure reason value corresponding to an exception specified in the protocol and a custom exception, it may be determined that the first service request failed due to an exception other than an exception specified in the protocol and a custom exception, that is, it is determined that an unexpected failure occurred in the first service request.

[0232] S902: The third network element adjusts the number of service requests initiated to the fourth network element according to the success rate of service requests between the fourth network element and the third network element.

[0233] In some feasible implementations, when it is determined that the first service request has an unexpected failure, the third network element may adjust the number of service requests initiated to the fourth network element according to the service request success rate between the fourth network element and the third network element. Among them, the number of service requests initiated by the third network element to the fourth network element is positively correlated with the service request success rate between the fourth network element and the third network element. In other words, the number of service requests initiated by the third network element to the fourth network element will increase with the increase of the service request success rate, and will also decrease with the decrease of the service request success rate. It can also be said that the higher the service request success rate between the fourth network element and the third network element, the more service requests initiated by the third network element to the fourth network element, and the lower the service request success rate between the fourth network element and the third network element, the fewer service requests initiated by the third network element to the fourth network element.

[0234] In the above implementation, when the first service request initiated to the fourth network element fails unexpectedly, the third network element dynamically adjusts the number of service requests initiated to the fourth network element according to the service request success rate between the fourth network element and the third network element, so that the number of service requests initiated to the fourth network element is positively correlated with the service request success rate, that is, the higher the service request success rate, the more service requests that can be initiated, and the lower the service request success rate, the fewer service requests that can be initiated. In this way, the impact of unexpected anomalies on the service path between the third network element and the third network element on the service request initiated by the third network element to the fourth network element can be reduced, and the success rate of the service requests can be improved.

[0235] In a first possible implementation method, when the service request success rate between the fourth network element and the third network element is less than the first success rate threshold and greater than the second success rate threshold, the third network element may adjust the number of service requests initiated to the fourth network element according to the positive correlation with the service request success rate.

[0236] In the above implementation, only when the service request success rate between the fourth network element and the third network element is less than the first success rate threshold and greater than the second success rate threshold, the number of service requests initiated to the fourth network element is adjusted according to the positive correlation with the service request success rate. This can ensure that the number of service requests initiated to the fourth network element will not be too small, thereby ensuring the effective use of the service path between the fourth network element and the third network element.

[0237] Optionally, when the service request success rate between the fourth network element and the third network element is less than the first success rate threshold and greater than the second success rate threshold, the third network element may first obtain the first mapping relationship. The first mapping relationship is used to indicate different numbers of service requests corresponding to different service request success rates, and the two are positively correlated.

[0238] For example, the first mapping relationship may indicate that the service request success rate and the number of service requests satisfy the following formula (1):

[0239] Q=K*S(1)

[0240] Wherein, Q is the number of service requests, K is a preset positive integer, and the value of K is greater than 1, and S is the success rate of the service requests.

[0241] For another example, the first mapping relationship may indicate multiple different service request success rate ranges, and the number of service requests corresponding to each service request success rate range in these multiple service request success rate ranges. Moreover, the service request success rate range with a larger upper limit value has a larger number of service requests corresponding to it. Exemplarily, the first mapping relationship may indicate six service request success rate ranges: (0.8, 0.9], (0.7, 0.8], (0.6, 0.7], (0.5, 0.6], (0.4, 0.5], (0.3, 0.4], and the corresponding numbers of service requests are 50, 45, 40, 35, 30, and 25, respectively.

[0242] It should be understood that the above description of the first mapping relationship is only exemplary. In actual implementation, the first mapping relationship may also be implemented in other possible ways, as long as the service request success rate is positively correlated with the corresponding number of service requests.

[0243] Furthermore, the third network element can determine the number of service requests that are positively correlated with it based on the above-mentioned first mapping relationship and the service request success rate between the fourth network element and the third network element, and determine the number of service requests as the number of service requests initiated by the third network element to the fourth network element, thereby adjusting the number of service requests initiated to the fourth network element according to the positive correlation with the service request success rate.

[0244] For example, assuming that the service request success rate between the fourth network element and the third network element is 75%, and the value of K in the above formula (1) is 100, then according to the above formula (1), the third network element can determine that the number of service requests initiated to the fourth network element is 75. Further, assuming that the service request success rate between the fourth network element and the third network element is reduced to 70%, then according to the above formula (1), the third network element can determine that the number of service requests initiated to the fourth network element is 70.

[0245] Optionally, since the service request success rate changes dynamically, it may increase or decrease. Therefore, the third network element may also gradually reduce the number of service requests initiated to the fourth network element when it is determined that the service request success rate decreases from the first success rate threshold to the second success rate threshold. For example, when the third network element determines that the service request success rate continues to decrease from the first success rate threshold to the second success rate threshold, the number of service requests initiated to the fourth network element may be reduced by a fixed value at fixed intervals. For another example, the third network element may reduce the number of service requests initiated to the fourth network element by a fixed value each time it determines that the service request success rate decreases from the first success rate threshold to the second success rate threshold. It should be understood that in the process of reducing the service request success rate from the first success rate threshold to the second success rate threshold, the third network element may also use other methods to reduce the number of service requests initiated to the fourth network element. This application does not impose specific restrictions on this.

[0246] Correspondingly, the third network element may also gradually increase the number of service requests initiated to the fourth network element when determining that the service request success rate increases from the second success rate threshold to the first success rate threshold. For example, when the third network element determines that the service request success rate continues to increase from the second success rate threshold to the first success rate threshold, the number of service requests initiated to the fourth network element may be increased by a fixed value at fixed intervals. For another example, the third network element may increase the number of service requests initiated to the fourth network element by a fixed value each time it determines that the service request success rate increases from the second success rate threshold to the first success rate threshold. It should be understood that in the process of increasing the service request success rate from the second success rate threshold to the first success rate threshold, the third network element may also use other methods to increase the number of service requests initiated to the fourth network element, and the present application does not impose specific restrictions on this.

[0247] In a second possible implementation, when the service request success rate between the fourth network element and the third network element is less than the second success rate threshold, the third network element may adjust the number of service requests initiated to the fourth network element to the minimum number of service requests. It should be understood that the value of the minimum number of service requests involved in the present application can be determined according to actual application requirements, and the present application does not impose specific restrictions on this. In addition, the minimum number of service requests is usually less than the number of service requests when the service request success rate is less than the first success rate threshold and greater than the second success rate threshold.

[0248] In the above implementation, when the service request success rate between the fourth network element and the third network element is less than the second success rate threshold, it means that there are major problems in the service path between the fourth network element and the third network element. At this time, only the minimum number of service requests is guaranteed, which can minimize the impact of unexpected exceptions on service requests.

[0249] In a third possible implementation, when the service request success rate between the fourth network element and the third network element is equal to or greater than the first success rate threshold, the third network element does not limit the number of service requests initiated to the fourth network element. That is, when the service request success rate between the fourth network element and the third network element is equal to or greater than the first success rate threshold, the third network element can initiate a service request to the fourth network element according to actual service requirements without additional restrictions on the number of service requests initiated to the fourth network element.

[0250] In the above implementation, when the service request success rate between the fourth network element and the third network element is greater than the first success rate threshold, it means that the reliability of the service path between the fourth network element and the third network element is relatively high. At this time, the number of service requests initiated to the fourth network element is not restricted, and the utilization rate of the service path can be guaranteed.

[0251] In some possible implementations, when the service request success rate between the fourth network element and the third network element changes from being greater than the first success rate threshold to being less than the first success rate threshold, the third network element may send second information to an operation and maintenance center (OMC), wherein the second information is used to indicate that an abnormality exists in the service path between the fourth network element and the third network element. That is, when the service request success rate between the fourth network element and the third network element changes from being greater than the first success rate threshold to being less than the first success rate threshold, the third network element may report the occurrence of an unexpected abnormality to the operation and maintenance center through the second information.

[0252] Optionally, when the service request success rate between the fourth network element and the third network element changes from less than the first success rate threshold to greater than or equal to the first success rate threshold, the third network element may further send third information to the operation and maintenance center. The third information is used to indicate that the service path between the fourth network element and the third network element has returned to normal. That is, when the service request success rate between the fourth network element and the third network element changes from greater than the second success rate threshold to equal to or greater than the first success rate threshold, the third network element may report to the operation and maintenance center through the third information that the unexpected abnormality has been restored.

[0253] In the above implementation, the third network element may report the actual status of the service path between the fourth network element and the third network element to the operation and maintenance center according to the service request success rate, which may facilitate resource scheduling of the communication system.

[0254] In some possible implementations, the third network element also sends a second service request to the fifth network element. The second service request is a service request that is reduced in the process of adjusting the number of service requests initiated to the fourth network element, and the fifth network element and the fourth network element are different network elements. That is to say, in the process of adjusting the number of service requests initiated to the fourth network element according to the service request success rate between the fourth network element and the third network element, if the second service request needs to be initiated by the third network element, but the number of service requests initiated by the third network element to the fourth network element has reached the limit value, the third network element can initiate the above-mentioned second service request to the fifth network element other than the fourth network element. It can also be said that the third network element can send the service request that is limited due to the service request success rate to the fifth network element other than the fourth network element.

[0255] In the above implementation, the third network element may send the second service request that is limited due to the service request success rate to other network elements, so that these limited service requests can be processed in time, thereby achieving the effect of reducing service delay.

[0256] It should be supplemented that, in the present embodiment, the third network element and the fourth network element may be any two network elements in the core network that have service paths. For example, the third network element may be an AMF network element, and the fourth network element may be an SMF network element. For another example, the third network element may be an AMF network element, and the fourth network element may be a PCF network element. In addition, the first service request may be a service request corresponding to a service process associated with the third network element and the fourth network element. Exemplarily, the first service request may be some service requests in the initial registration process initiated by the terminal device, or some service requests in the PDU session establishment process initiated by the terminal device, or some service requests in the service cell switching process of the terminal device. The present application does not limit the specific implementation of the first service request.

[0257] Above, combined Figures 1 to 9 The communication method provided by the embodiment of the present application is described in detail. Figures 10 to 12 The communication device provided in the embodiment of the present application is described in detail. It should be understood that the description of the embodiment of the communication device corresponds to the description of the embodiment of the communication method, so the parts not described in detail can refer to the previous method embodiment.

[0258] See also Fig.10 , Fig.10 Schematic diagram of the structure of a communication device provided by this application. Fig.10 As shown, the communication device 100 may include a transceiver unit 101 and a processing unit 102. Here, the transceiver unit 101 may also be referred to as a transceiver module, and the processing unit 102 may also be referred to as a processing module.

[0259] In some feasible implementations, the communication device 100 may correspond to Figures 4 to 8 The first network element in the method shown, or a component (such as a circuit, a processor, a chip or a chip system) configured in the first network element. The communication device 100 may include a method for implementing Figures 4 to 8 The communication method executed by the first network element shown in the figure corresponds to a module, unit or means, which can be implemented by hardware, software, or by hardware executing corresponding software. The software or hardware includes one or more modules or units corresponding to the above functions.

[0260] In a specific implementation, the transceiver unit 101 is used to send perception auxiliary data to at least one first terminal device and at least one first network device. The perception auxiliary data can be used for transmission and / or measurement of perception signals. The at least one first terminal device is managed by the at least one first network device, and the at least one first network device serves the first network element. The transceiver unit 101 is used to receive N1 perception measurement information from the at least one first terminal device. Among them, the N1 perception measurement information can be obtained based on the above perception signal measurement. The perception signal can be sent by at least one first network device and received by at least one first terminal device. Among them, N1 is a positive integer greater than or equal to 1. The processing unit 102 is used to determine the perception result of the object to be perceived based on the N1 perception measurement information.

[0261] Exemplarily, the processing unit 102 is used to determine the second network element when an unexpected failure occurs in the first business process. The second network element is a backup network element of the first network element, and the cause of the unexpected failure does not include exceptions specified by the protocol and custom exceptions. The processing unit 102 is used to migrate the first business process to the second network element through the transceiver unit 101 to indicate that the subsequent process of the first business process is initiated through the second network element.

[0262] Exemplarily, when the service failure is restored in a redirection mode, the transceiver unit 101 is used to send a first request message to the second network element. The first request message is used to provide the second network element with the generated session information corresponding to the first service process, and the generated session information is used for failure recovery of the first service process.

[0263] Exemplarily, the first request message includes at least one of the following: N1 interface information between the terminal device that initiates the first business process and the first network element, terminal device context information of the first business process, or first information, wherein the first information is used to indicate that the first business process is migrated from the first network element to the second network element due to an unexpected failure.

[0264] Exemplarily, when a service failure is recovered by rerouting, the transceiver unit is used to send a second request message to the network device to migrate the first service process to the second network element, wherein the second request message is used to instruct the network device to reroute the first service process to the second network element.

[0265] Exemplarily, the second request message includes at least one of the following: N1 interface information between the terminal device that initiates the first service process and the first network element, and identification information of the second network element.

[0266] Exemplarily, the transceiver unit 101 is used to send a third request message to the second network element to migrate the first service process to the second network element, wherein the third request message is used to instruct the second network element to rebuild the session information of the first service process.

[0267] Exemplarily, the third request message includes: identification information of the network device, next generation application protocol identification information corresponding to the terminal device initiating the first service process, or first information, wherein the first information is used to indicate that the first service process is migrated from the first network element to the second network element due to unexpected failure.

[0268] Exemplarily, the processing unit 102 is used to: when the first business process fails, obtain a failure reason value, and when it is determined according to the failure reason value that the reason for the failure of the first business process does not include an exception specified in the protocol and a custom exception, determine that the failure of the first business process is an unexpected failure.

[0269] In some feasible implementations, the communication device 100 may correspond to Figures 4 to 8 The second network element in the method shown, or a component (such as a circuit, a processor, a chip or a chip system) configured in the second network element. The communication device 100 may include a method for implementing Figures 4 to 8 The communication method executed by the second network element shown in the figure corresponds to a module, unit or means, which can be implemented by hardware, software, or by hardware executing corresponding software. The software or hardware includes one or more modules or units corresponding to the above functions.

[0270] In a specific implementation, when an unexpected failure occurs in a first business process on a first network element and the process is migrated from the first network element to a second network element, if the first business process fails again on the second network element, the processing unit 102 is used to determine whether the reoccurring failure is an unexpected failure. The cause of the unexpected failure does not include exceptions specified in the protocol and custom exceptions. When the processing unit 102 determines that the reoccurring failure is an unexpected failure, if the processing unit 102 determines that the first time interval between the two unexpected failures of the first business process on the first network element and the second network element is less than or equal to the time interval threshold, the processing unit 102 no longer migrates the first business process to the first network element through the transceiver unit 101.

[0271] Exemplarily, when the first time interval is greater than the time interval threshold, the processing unit 102 migrates the first service process to the first network element through the transceiver unit 101 .

[0272] Exemplarily, the transceiver unit 101 is used to receive a first request message from a first network element. The first request message is used to provide the second network element with the generated session information corresponding to the first business process to achieve the migration of the first business process to the second network element, and the generated session information is used for failure recovery of the first business process. In this case, the first time interval is the time interval between the first moment of receiving the first request message and the second moment of an unexpected failure occurring again on the second network element.

[0273] Exemplarily, the first request message includes at least one of the following: N1 interface information between the terminal device that initiates the first business process and the first network element, terminal device context information of the first business process, or first information, wherein the first information is used to indicate that the first business process is migrated from the first network element to the second network element due to an unexpected failure.

[0274] Exemplarily, the transceiver unit 101 is used to receive a third request message from the first network element to implement the migration of the first service process to the second network element, wherein the third request message is used to instruct the second network element to rebuild the session information of the first service process. In this case, the first time interval is the time interval between the third moment of receiving the third request message and the second moment of the unexpected failure occurring again on the second network element.

[0275] Exemplarily, the third request message includes: identification information of the network device, next generation application protocol identification information corresponding to the terminal device initiating the first service process, or first information, wherein the first information is used to indicate that the first service process is migrated from the first network element to the second network element due to unexpected failure.

[0276] In some feasible implementations, the communication device 100 may also correspond to Fig. 9The third network element in the method shown, or a component (such as a circuit, a processor, a chip or a chip system) configured in the third network element. The communication device 100 may include a method for implementing Figures 4 to 8 The communication method executed by the third network element shown in the figure corresponds to a module, unit or means, which can be implemented by hardware, software, or by hardware executing corresponding software. The software or hardware includes one or more modules or units corresponding to the above functions.

[0277] In a specific implementation, the processing unit 102 is used to determine that an unexpected failure occurs in the first service request initiated to the fourth network element. The cause of the unexpected failure does not include an exception specified in the protocol and a custom exception. The processing unit 102 is used to adjust the number of service requests initiated to the fourth network element according to the service request success rate between the fourth network element and the third network element. The number of service requests initiated to the fourth network element is positively correlated with the service request success rate.

[0278] Exemplarily, when the service request success rate between the fourth network element and the third network element is less than the first success rate threshold and greater than the second success rate threshold, the processing unit 102 is used to adjust the number of service requests initiated to the fourth network element according to the positive correlation between the service request success rate.

[0279] Exemplarily, when the service request success rate decreases from the first success rate threshold to the second success rate threshold, the processing unit 102 is used to reduce the number of service requests initiated to the fourth network element. When the service request success rate increases from the second success rate threshold to the first success rate threshold, the processing unit 102 is used to increase the number of service requests initiated to the fourth network element.

[0280] Exemplarily, when the service request success rate between the fourth network element and the third network element is less than the second success rate threshold, the processing unit 102 is configured to adjust the number of service requests initiated to the fourth network element to the minimum number of service requests.

[0281] Exemplarily, when the service request success rate between the fourth network element and the third network element is equal to or greater than the first success rate threshold, the processing unit 102 does not limit the number of service requests initiated to the fourth network element.

[0282] Exemplarily, when the service request success rate between the fourth network element and the third network element changes from greater than the first success rate threshold to less than the first success rate threshold, the transceiver unit 101 is used to send second information to the operation and maintenance center, wherein the second information is used to indicate that there is an abnormality in the service path between the fourth network element and the third network element.

[0283] Exemplarily, when the service request success rate between the fourth network element and the third network element changes from less than the first success rate threshold to greater than or equal to the first success rate threshold, the transceiver unit 101 is used to send third information to the operation and maintenance center. The third information is used to indicate that the service path between the fourth network element and the third network element has returned to normal.

[0284] Exemplarily, the transceiver unit 101 is used to send a second service request to the fifth network element, wherein the second service request is a service request that is reduced in the process of adjusting the number of service requests initiated to the fourth network element.

[0285] It is understandable that, in order to implement the functions in the above embodiments, the first network element, the second network element or the third network element described above includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware, software, or a combination of hardware and software. Whether a function is executed in the form of hardware, software, or computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0286] See also Fig.11 , Fig.11 is a schematic diagram of the structure of another communication device provided by the present application. The communication device 110 can be used Figures 4 to 9 The operations performed by the first network element, the second network element or the third network element in the sensing method shown. Alternatively, the communication device 110 may be Figures 4 to 9 The first network element, the second network element or the third network element in the communication method shown. The communication device 110 includes: a processor 111.

[0287] Optionally, the communication device may further include a memory 112 .

[0288] The memory 112 is used to store relevant instructions and data. The memory 112 stores the following elements, executable modules or data structures, or their subsets, or their extended sets:

[0289] Operation instructions: include various operation instructions, used to implement various operations.

[0290] Operating system: includes various system programs used to implement various basic businesses and handle hardware-based tasks.

[0291] Fig.11 Only one memory is shown in the figure, of course, the memory can also be set to multiple as needed.

[0292] Optionally, the communication device 110 may further include a transceiver 114. The transceiver 114 may be a communication module or a transceiver circuit. Figures 4 to 9 The message or information sending and receiving operations involved in the method shown.

[0293] The processor 111 may be a controller, a general processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The processor 111 may also be a combination that implements a computing function, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

[0294] Optionally, the communication device may further include a bus system 113. In a specific application, the various components of the communication device 110 are coupled together via the bus system 113, wherein the bus system 113 may include a power bus, a control bus, and a status signal bus in addition to a data bus. However, for the sake of clarity, Fig.11 In FIG. 1 , various buses are labeled as bus system 113. For convenience of representation, Fig.11 The drawing is only schematic.

[0295] In a specific implementation, the communication device 110 may execute Figures 4 to 9 The steps of the method performed by the first network element, the second network element or the third network element in the communication method shown. Specifically, when the communication device 110 is used to implement the above Figures 4 to 9 When each step in the communication method is executed by the first network element, the second network element or the third network element, the processor 111 can be used to implement the function of the above-mentioned processing unit 102, and the transceiver 114 is used to implement the function of the above-mentioned transceiver unit 101.

[0296] It should be noted that in practical applications, the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application may be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in a decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0297] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rateSDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (directrambus RAM, DR RAM). It should be noted that the memory described in the embodiments of the present application is intended to include but is not limited to these and any other suitable types of memory.

[0298] The present application also provides a computer-readable medium on which a computer program is stored, which, when executed by a computer, implements the above Figures 4 to 9 The communication method shown includes steps of the method executed by the first network element, the second network element or the third network element.

[0299] The present application also provides a computer program product, which, when executed by a computer, implements the above Figures 4 to 9 The communication method shown includes steps of the method executed by the first network element, the second network element or the third network element.

[0300] The present application also provides a chip, comprising at least a processor. The processor is used to execute computer execution instructions so that a device equipped with the chip can implement the above Figures 4 to 9 The communication method shown includes steps of the method executed by the first network element, the second network element or the third network element.

[0301] Optionally, the chip may further include an interface circuit, which is used to receive computer execution instructions and transmit them to the processor.

[0302] The present application also provides a chip system, which includes a processor for supporting a device equipped with the chip system to implement the above Figures 4 to 9 The steps of the method performed by the first network element, the second network element or the third network element in the communication method shown. For example, generating or processing the data and / or information involved in the above method. In one possible design, the chip system also includes a memory, and the memory is used to store program instructions and data necessary for the data sending device. The chip system can be composed of a chip, and can also include a chip and other discrete devices.

[0303] See also Fig.12 , Fig.12 1 is a schematic diagram of the structure of another communication device provided by the present application. The communication device 120 may include a processor 121 and an interface circuit 122. The interface circuit 122 may be used to receive signals from other communication devices outside the communication device 120 and transmit them to the processor or send signals from the processor to other communication devices outside the communication device 120. The processor 121 may be used to implement the perception method described in the above embodiment through a logic circuit or by executing a computer program or instruction.

[0304] In some possible designs, the communication device 120 may be the above Figures 4 to 9 The first network element, the second network element or the third network element in the communication method shown, or a device including the first network element, the second network element or the third network element mentioned above, or a device included in the first network element, the second network element or the third network element mentioned above, such as a chip system.

[0305] The present application also provides a communication system. The communication system may include the terminal device, the network device, the first network element and the second network element as described above. These entities work together to achieve Figures 4 to 8 The communication method shown.

[0306] The present application also provides a communication system. The communication system may include the third network element and the fourth network element mentioned above. These entities work together to achieve Fig. 9 The communication method shown.

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

[0308] In the various embodiments of the present application, unless otherwise specified or provided for in any logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

[0309] The terms "component", "module", "system", etc. used in this specification are used to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, or a computer. By way of illustration, both applications running on a computing device and a computing device can be components. One or more components may reside in a process or an execution thread, and a component may be located on a computer or distributed between two or more computers. In addition, these components may be executed from various computer-readable media having various data structures stored thereon. Components may communicate, for example, through local or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, or a network, such as the Internet interacting with other systems through signals).

[0310] It should be understood that the "embodiment" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, the various embodiments in the entire specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner.

[0311] It should be understood that in the embodiments of the present application, the numbers "first", "second"... are only for distinguishing different objects, such as distinguishing different network devices, and do not constitute a limitation on the scope of the embodiments of the present application. The embodiments of the present application are not limited to this.

[0312] It should also be understood that in the present application, "when", "if" and "if" all mean that the network element will take corresponding actions under certain objective circumstances, and do not limit the time, nor do they require the network element to have a judgment action when implementing it, nor do they mean that there are other limitations.

[0313] It should also be understood that in each embodiment of the present application, "A corresponds to B" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0314] It should also be understood that the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0315] The meaning of expressions similar to "the project includes one or more of the following: A, B, and C" in this application, unless otherwise specified, generally means that the project can be any of the following: A; B; C; A and B; A and C; B and C; A, B and C; A and A; A, A and A; A, A and B; A, A and C, A, B and B; A, C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B and C. The above is an example of three elements, A, B and C, to illustrate the optional items of the project. When it is expressed as "the project includes at least one of the following: A, B, ..., and X", that is, when there are more elements in the expression, the items that can be applied to the project can also be obtained according to the above rules.

[0316] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0317] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0318] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0319] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0320] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0321] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories ROM, random access memories RAM, magnetic disks or optical disks.

[0322] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, characterized in that: Applied to a first network element, the method includes: In the case where an unexpected failure occurs in the first service process, determining a second network element, wherein the second network element is a backup network element of the first network element, and the cause of the unexpected failure does not include an exception specified by the protocol and a user-defined exception; The first service process is migrated to the second network element to indicate that a subsequent process of the first service process is initiated through the second network element.

2. The method according to claim 1, characterized in that The migrating the first service process to the second network element includes: In the case where the service failure of the first network element is recovered in a redirection manner, a first request message is sent to the second network element to migrate the first service process to the second network element, wherein the first request message is used to provide the second network element with the already generated session information corresponding to the first service process, and the already generated session information is used for failure recovery of the first service process.

3. The method according to claim 2, characterized in that The first request message includes at least one of the following: N1 interface information between the terminal device that initiates the first business process and the first network element, terminal device context information of the first business process, or first information, wherein the first information is used to indicate that the first business process is migrated from the first network element to the second network element due to the unexpected failure.

4. The method according to any one of claims 1 to 3, characterized in that: The migrating the first service process to the second network element includes: In the event that the service failure of the first network element is recovered by rerouting, a second request message is sent to the network device to migrate the first service process to the second network element, wherein the second request message is used to instruct the network device to reroute the first service process to the second network element.

5. The method according to claim 4, characterized in that The second request message includes at least one of the following: N1 interface information between the terminal device that initiates the first service process and the first network element, and identification information of the second network element.

6. The method according to claim 1 or 2, characterized in that: The migrating the first service process to the second network element includes: A third request message is sent to the second network element to migrate the first service process to the second network element, wherein the third request message is used to instruct the second network element to rebuild the session information of the first service process.

7. The method according to claim 6, characterized in that The third request message includes at least one of the following: identification information of the network device, next-generation application protocol identification information corresponding to the terminal device that initiates the first business process, and first information, wherein the first information is used to indicate that the first business process is migrated from the first network element to the second network element due to the unexpected failure.

8. A communication method, characterized in that: Applied to a second network element, the method comprises: In the case where an unexpected failure occurs in a first service process on a first network element and the first network element is migrated to the second network element, if the first service process fails again on the second network element, determining whether the failure that occurs again is the unexpected failure, wherein the cause of the unexpected failure does not include exceptions specified in the protocol and user-defined exceptions; In the case where the reoccurring failure is the unexpected failure, if the first time interval between the two unexpected failures of the first business process on the first network element and the second network element is less than or equal to the time interval threshold, the first business process will no longer be migrated to the first network element.

9. The method according to claim 8, characterized in that The method further comprises: When the first time interval is greater than the time interval threshold, the first service process is migrated to the first network element.

10. The method according to claim 8 or 9, characterized in that: The method further comprises: receiving a first request message from a first network element, wherein the first request message is used to provide the second network element with the generated session information corresponding to the first service process, so as to implement the migration of the first service process to the second network element, and the generated session information is used for failure recovery of the first service process; The first time interval is a time interval between a first moment of receiving the first request message and a second moment of the unexpected failure occurring again on the second network element.

11. The method according to claim 10, characterized in that The first request message includes at least one of the following: N1 interface information between the terminal device that initiates the first business process and the first network element, terminal device context information of the first business process, or first information, wherein the first information is used to indicate that the first business process is migrated from the first network element to the second network element due to the unexpected failure.

12. The method according to claim 8 or 9, characterized in that: The method further comprises: receiving a third request message from the first network element to implement migration of the first service process to the second network element, wherein the third request message is used to instruct the second network element to rebuild session information of the first service process; The first time interval is a time interval between a third moment when the third request message is received and a second moment when the unexpected failure occurs again on the second network element.

13. The method according to claim 12, characterized in that The third request message includes at least one of the following: identification information of the network device, next-generation application protocol identification information corresponding to the terminal device that initiates the first business process, and first information, wherein the first information is used to indicate that the first business process is migrated from the first network element to the second network element due to the unexpected failure.

14. A communication method, characterized in that: Applied to a third network element, the method includes: Determining that an unexpected failure occurs in the first service request initiated to the fourth network element, wherein the cause of the unexpected failure does not include an exception specified by the protocol and a user-defined exception; The number of service requests initiated to the fourth network element is adjusted according to the service request success rate between the fourth network element and the third network element, wherein the number of service requests initiated to the fourth network element is positively correlated with the service request success rate.

15. The method according to claim 14, characterized in that The adjusting the number of service requests initiated to the fourth network element according to the service request success rate between the fourth network element and the third network element includes: When the service request success rate between the fourth network element and the third network element is less than a first success rate threshold and greater than a second success rate threshold, the number of service requests initiated to the fourth network element is adjusted according to the positive correlation relationship between the service request success rates.

16. The method according to claim 14 or 15, characterized in that The adjusting the number of service requests initiated to the fourth network element according to the service request success rate between the fourth network element and the third network element includes: When the service request success rate between the fourth network element and the third network element is less than a second success rate threshold, the number of service requests initiated to the fourth network element is adjusted to a minimum number of service requests.

17. The method according to any one of claims 14 to 16, characterized in that: The adjusting the number of service requests initiated to the fourth network element according to the service request success rate between the fourth network element and the third network element includes: When the service request success rate between the fourth network element and the third network element is equal to or greater than the first success rate threshold, the number of service requests initiated to the fourth network element is not limited.

18. The method according to any one of claims 14 to 17, characterized in that: The method further comprises: When the service request success rate between the fourth network element and the third network element changes from greater than the first success rate threshold to less than the first success rate threshold, second information is sent to the operation and maintenance center, wherein the second information is used to indicate that there is an abnormality in the service path between the fourth network element and the third network element.

19. The method according to any one of claims 14 to 18, characterized in that: The method further comprises: When the service request success rate between the fourth network element and the third network element changes from less than the first success rate threshold to greater than or equal to the first success rate threshold, third information is sent to the operation and maintenance center, wherein the third information is used to indicate that the service path between the fourth network element and the third network element has returned to normal.

20. A communication device, characterized in that: The communication device includes: a module or a unit for implementing the communication method according to any one of claims 1 to 7, any one of claims 8 to 13, and any one of claims 14 to 19.

21. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed, the communication method according to any one of claims 1 to 7, any one of claims 8 to 13, and any one of claims 14 to 19 is implemented.

22. A chip, characterized in that: Including processors; The processor is used to execute computer-executable instructions so that the device equipped with the chip executes the communication method according to any one of claims 1 to 7, any one of claims 8 to 13, and any one of claims 14 to 19.

23. The chip according to claim 22, characterized in that: The chip further comprises an interface circuit, wherein the interface circuit is used for receiving the computer execution instruction and transmitting the instruction to the processor.

24. A computer program product, wherein the computer program product is executed by a computer to execute the communication method according to any one of claims 1 to 7, any one of claims 8 to 13, and any one of claims 14 to 19.

25. A communication device, characterized in that: include: at least one processor and memory; The memory is used to store computer programs; The processor is configured to execute the computer program stored in the memory so that the communication device executes the communication method according to any one of claims 1 to 7, any one of claims 8 to 13, and any one of claims 14 to 19.

Images