Apparatus and method of data pipeline failure recovery

Abstract

A method of data pipeline failure recovery performed by a data pipeline coordinator includes establishing a data pipeline with a first path comprising a plurality of data pipeline contributors, receiving, from a data pipeline contributor, a failure report indicating a data pipeline failure, and selecting at least one candidate data pipeline contributor to replace at least one failed data pipeline contributor.

Description

Atty. Dkt. No. 10085-01-0186-PCTAPPARATUS AND METHOD OF DATA PIPELINE FAILURE RECOVERYCROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application No. 63 / 728,085, entitled “METHOD AND APPARATUS FOR DATA PIPELINE FAILURE RECOVERY,” filed on December 4, 2024, the entire disclosure of which is hereby incorporated by reference in their entirety.TECHNICAL FIELD

[0002] The present disclosure relates to the field of communication systems, and more particularly, to apparatuses and methods of data pipeline failure recovery.BACKGROUND

[0003] In sixth generation (6G) communication systems, a data plane is introduced to enable trusted data collection, storage, access, and sharing across distributed network environments. To support these operations, a new network element referred to as a data plane access controller (DPAC) has been proposed. The DPAC may function as a management or control entity that interfaces between the 6G core network and the data plane infrastructure, performing tasks such as data collection, identity verification, processing, and interaction with data storage facilities.

[0004] Within this framework, a data pipeline is utilized to provide efficient and automated data flow across multiple network entities. A data pipeline includes data sources, contributors, and receivers that cooperatively perform data acquisition, transformation, and delivery. However, during operation, some data pipeline nodes may become unavailable or experience degraded performance. As a result, data pipeline failure recovery is required to dynamically reconfigure the pipeline by selecting alternative nodes or paths, ensuring stable performance and continuity of data services in 6G networks.

[0005] Therefore, there is a need for apparatuses and methods of data pipeline failure recovery.SUMMARY

[0006] An object of the present disclosure is to propose apparatuses and methods of data pipeline failure recovery, which can solve issues in the prior art and other issues and / or provide stable performance and continuity of data services.

[0007] In a first aspect of the present disclosure, a method of data pipeline mobility management performed by a data pipeline coordinator includes establishing a data pipeline with a first path including a plurality of data pipeline contributors, receiving, from a data pipeline contributor, aAtty. Dkt. No. 10085-01-0186-PCT failure report indicating a data pipeline failure, and selecting at least one candidate data pipeline contributor to replace at least one failed data pipeline contributor.

[0008] In a second aspect of the present disclosure, a data pipeline coordinator includes a controller and a receiver. The controller is configured to establish a data pipeline with a first path including a plurality of data pipeline contributors, the receiver is configured to receive, from a data pipeline contributor, a failure report indicating a data pipeline failure, and the controller is further configured to select at least one candidate data pipeline contributor to replace at least one failed data pipeline contributor.

[0009] In a third aspect of the present disclosure, a data pipeline coordinator includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The data pipeline coordinator is configured to perform the above method.

[0010] In a fourth aspect of the present disclosure, a method of data pipeline mobility management performed by a data pipeline contributor includes participating in a data pipeline with a first path including a plurality of data pipeline contributors, detecting that a data pipeline failure has occurred, and initiating a recovery process to switch the data pipeline from the first path to a second path.

[0011] In a fifth aspect of the present disclosure, a data pipeline contributor includes a controller and a detector. The controller is configured to participate in a data pipeline with a first path including a plurality of data pipeline contributors, the detector is configured to detect that a data pipeline failure has occurred, and the controller is further configured to initiate a recovery process to switch the data pipeline from the first path to a second path.

[0012] In a sixth aspect of the present disclosure, a data pipeline contributor includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The data pipeline contributor is configured to provide the above method.

[0013] In a seventh aspect of the present disclosure, a non-transitory machine-readable storage medium has stored thereon instructions that, when executed by a computer, cause the computer to perform the above method.

[0014] In an eighth aspect of the present disclosure, a chip includes a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the above method.

[0015] In a ninth aspect of the present disclosure, a computer readable storage medium, in which a computer program is stored, causes a computer to execute the above method.

[0016] In a tenth aspect of the present disclosure, a computer program product includes a computer program, and the computer program causes a computer to execute the above method.Atty. Dkt. No. 10085-01-0186-PCT

[0017] In an eleventh aspect of the present disclosure, a computer program causes a computer to execute the above method.BRIEF DESCRIPTION OF DRAWINGS

[0018] In order to illustrate the embodiments of the present disclosure or related art more clearly, the following figures will be described in the embodiments are briefly introduced. It is obvious that the drawings are merely some embodiments of the present disclosure, a person having ordinary skill in this field can obtain other figures according to these figures without paying the premise.

[0019] FIG. l is a block diagram of an architecture of 6G data plane according to an embodiment of the present disclosure.

[0020] FIG. 2 is a block diagram of a data pipeline in 6G data plane according to an embodiment of the present disclosure.

[0021] FIG. 3 is a block diagram of one or more data pipeline contributors and a data pipeline coordinator according to an embodiment of the present disclosure.

[0022] FIG. 4A is a block diagram of a data pipeline coordinator according to an embodiment of the present disclosure.

[0023] FIG. 4B is a block diagram of a data pipeline coordinator according to an embodiment of the present disclosure.

[0024] FIG. 5 is a flowchart illustrating a method of data pipeline failure recovery performed by a data pipeline coordinator according to an embodiment of the present disclosure.

[0025] FIG. 6A is a block diagram of a data pipeline contributor according to an embodiment of the present disclosure.

[0026] FIG. 6B is a block diagram of a data pipeline contributor according to an embodiment of the present disclosure.

[0027] FIG. 7 is a flowchart illustrating a method of data pipeline failure recovery performed by a data pipeline contributor according to an embodiment of the present disclosure.

[0028] FIG. 8 is a block diagram of an example of data pipeline topology according to an embodiment of the present disclosure.

[0029] FIG. 9 is a flowchart illustrating a data pipeline failure recovery by a data pipeline coordinator according to an embodiment of the present disclosure.

[0030] FIG. 10 is a flowchart illustrating a data pipeline failure recovery by a data pipeline contributor according to an embodiment of the present disclosure.

[0031] FIG. 11 is a block diagram of an example of a computing device according to an embodiment of the present disclosure.Atty. Dkt. No. 10085-01-0186-PCT

[0032] FIG. 12 is a block diagram of a communication system according to an embodiment of the present disclosure.DETAILED DESCRIPTION OF EMBODIMENTS

[0033] Embodiments of the present disclosure are described in detail with the technical matters, structural features, achieved objects, and effects with reference to the accompanying drawings as follows. Specifically, the terminologies in the embodiments of the present disclosure are merely for describing the purpose of the certain embodiment, but not to limit the disclosure.

[0034] The technical solutions of the embodiments of the present disclosure can be applied to various communication systems, such as a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) system, a general packet radio service (GPRS), a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a new radio (NR) system, an evolution system of a NR system, a LTE-based access to unlicensed spectrum (LTE-U) system, a NR-based access to unlicensed spectrum (NR-U) system, an universal mobile telecommunication system (UMTS), a global interoperability for microwave access (WiMAX) communication system, wireless local area networks (WLAN), wireless fidelity (Wi-Fi), a 5th generation (5G) system (may also be called a new radio (NR) system), a 6th generation (6G) system, or other communication systems, etc.

[0035] Optionally, a user equipment (UE) mentioned in the embodiments of the present application may refer to an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal may be a cellular radio telephone, a cordless telephone, a session initiation protocol (SIP) telephone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication functions, a computing device, other processing devices coupled with a wireless modem, an in- vehicle device, a wearable device, a terminal device in a future 5G network, a terminal device in a future evolved public land mobile network (PLMN), etc.

[0036] Optionally, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where the licensed spectrum can also be considered an unshared spectrum.

[0037] 6G data plane and its associated data pipeline design have been proposed. An architecture of 6G data plane is illustrated in FIG. 1. To ensure the 6G data plane can support trusted dataAtty. Dkt. No. 10085-01-0186-PCT collection, storage, access, and sharing, a new network element called data plane access controller (DP AC) is proposed. It may also be referred to as the data plane management network element, data plane interface, data plane control network element, etc. The 6G data plane architecture introduces a new network element, the DP AC, to enable trusted data collection, storage, access, and sharing.

[0038] The functionalities supported by this network element can either be implemented by enhancing the existing data collection and coordination function (DCCF) or as a completely new network element. The DP AC will serve as the interface between the 6G network's data and the data plane infrastructure, with at least one of the following key functions: 1. Data collection. 2. Management and verification of data source and data consumer IDs. 3. Data processing and sharing. 4. Interaction with data plane storage facilities to store or retrieve data. For example, a data transaction request occurs when a data source or data consumer interacts with the DP AC for services such as data storage or retrieval. 5. Data tracking support. The DP AC functions as an interface between the 6G network and the data plane infrastructure, providing capabilities such as data collection, identity management, data processing and sharing, storage interaction, and data tracking.

[0039] When the core network’ s data plane collects data from a UE, the UE acts as the data source, engaging in a data transaction with the core network’s data plane. The UE sends a data transaction request to the DP AC, carrying the data source ID, raw data, and metadata. Upon receiving the request, DP AC verifies the data source ID. If verification is successful, it forwards the data source ID, raw data, and metadata to the data plane storage facility. When a UE acts as a data source, the UE sends a data transaction request with its ID, raw data, and metadata to the DP AC, which verifies the ID and forwards the information to the data plane storage facility.

[0040] To enable flexible and efficient data management, the data plane adopts a distributed architecture. This allows data sources to connect to a data plane closer to them, thereby reducing data transmission latency.

[0041] FIG. 2 illustrates a data pipeline in 6G data plane. The data pipeline is a series of data processing steps combined to facilitate data flow. Data is collected from a source and sent to the next node for processing, where it is handled and then forwarded to the subsequent node, enabling on-the-fly data processing. FIG. 2 illustrates a 6G data pipeline that enables continuous data flow through sequential processing steps from source to subsequent nodes for real-time data handling.

[0042] FIG. 2 illustrates that an operation of the data pipeline is like an assembly line in manufacturing. It simplifies data management processes, improves data processing efficiency, and ensures data integrity. In the data pipeline, the output of one network entity’s data processingAtty. Dkt. No. 10085-01-0186-PCT serves as the input for the next, allowing for a smooth and automated workflow throughout the pipeline. FIG. 2 illustrates that the 6G data pipeline operates like a manufacturing assembly line, simplifying data management, enhancing processing efficiency, and ensuring data integrity through an automated workflow between sequential network entities.

[0043] Components of the data pipeline may include at least one of the followings:

[0044] 1. Data sources: the starting point of the pipeline, responsible for collecting raw data. A single pipeline can include multiple data sources, enabling diverse data services.

[0045] 2. Pipeline contributors: these entities process the data provided by the sources. Examples of processing include compression, normalization, and Al-based data processing. The processed data is then passed to the next node in the pipeline.

[0046] 3. Data Receivers: the endpoint of the pipeline, where the fully processed data is received. No further processing is performed at this stage.

[0047] The data pipeline includes data sources that collect raw data, pipeline contributors that process the data, and data receivers that obtain the final processed output. The pipeline supports different types of data, such as continuous data, intermittent data, and batch data. All aspects of the pipeline, including node selection, pipeline establishment, allocation of data processing strategies, and data routing topology design, are managed by the DP AC as previously described. This structure ensures the efficient and systematic operation of the data pipeline. The DP AC manages all aspects of the data pipeline, including node selection, establishment, processing strategy allocation, and routing design, to efficiently handle continuous, intermittent, and batch data in a systematic manner.

[0048] Once a data pipeline is established, data can flow seamlessly within it. However, during the pipeline's execution, data sources or contributors may become unavailable or fail to meet the pipeline's performance requirements. In such cases, the pipeline may dynamically select new data sources and contributors, a process referred to as data pipeline failure recovery. The at least one of following aspects of data pipeline failure recovery have been proposed: 1. A monitoring mechanism that evaluates the data pipeline based on end-to-end delay and throughput. 2. A monitoring mechanism that evaluates each individual data pipeline contributor’s KIP’s and KPI reporting. 3. A mechanism that handles data pipeline failure. 4. A mechanism that manages data pipeline mobility. Once a data pipeline is established, it can dynamically perform failure recovery to maintain performance and continuity by monitoring end-to-end metrics, individual contributor KPIs, and handling failures through adaptive reconfiguration mechanisms.

[0049] Some embodiments of the present disclosure propose an exemplary technique to select alternative contributors to replace one or more data pipeline contributors when the one or moreAtty. Dkt. No. 10085-01-0186-PCT data pipeline contributors fail to meet performance requirements or become unavailable, ensuring the continuation of the data pipeline's functionality. Some embodiments of the disclosure propose a technique for selecting alternative contributors to replace failed or underperforming ones, ensuring continuous data pipeline operation.

[0050] FIG. 3 illustrates that, in some embodiments, one or more data pipeline contributors 10 and a data pipeline coordinator 20 of communication in a communication network system 30 (e.g., 6G system) according to an embodiment of the present disclosure are provided. The communication network system 30 includes the one or more data pipeline contributors 10 and the data pipeline coordinator 20. The one or more data pipeline contributors 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12 and the transceiver 13. The data pipeline coordinator 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22 and the transceiver 23. The processor 11 or 21 may be configured to implement proposed functions, procedures and / or methods described in this description. Layers of radio interface protocol may be implemented in the processor 11 or 21. The memory 12 or 22 is operatively coupled with the processor 11 or 21 and stores a variety of information to operate the processor 11 or 21. The transceiver 13 or 23 is operatively coupled with the processor 11 or 21, and the transceiver 13 or 23 transmits and / or receives a radio signal.

[0051] The processor 11 or 21 may include application-specific integrated circuit (ASIC), other chipset, logic circuit and / or data processing device. The memory 12 or 22 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and / or other storage device. The transceiver 13 or 23 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in the memory 12 or 22 and executed by the processor 11 or 21. The memory 12 or 22 can be implemented within the processor 11 or 21 or external to the processor 11 or 21 in which case those can be communicatively coupled to the processor 11 or 21 via various means as is known in the art.

[0052] In some embodiments, the processor 21 is configured to establish a data pipeline with a first path including a plurality of data pipeline contributors, the transceiver 23 is configured to receive, from the data pipeline contributor 10, a failure report indicating a data pipeline failure, and the processor 21 is further configured to select at least one candidate data pipeline contributor to replace at least one failed data pipeline contributor. This can solve issues in the prior art and other issues and / or provide stable performance and continuity of data services.

[0053] In some embodiments, the processor 11 is configured to participate in a data pipeline with a first path including a plurality of data pipeline contributors, the processor 11 is configured toAtty. Dkt. No. 10085-01-0186-PCT detect that a data pipeline failure has occurred, and the processor 11 is further configured to initiate a recovery process to switch the data pipeline from the first path to a second path. This can solve issues in the prior art and other issues and / or provide stable performance and continuity of data services.

[0054] FIG. 4A illustrates an example of a data pipeline coordinator 400A according to an embodiment of the present application. The data pipeline coordinator 400A is configured to implement some embodiments of the disclosure. Some embodiments of the disclosure may be implemented into the data pipeline coordinator 400A using any suitably configured hardware and / or software. The data pipeline coordinator 400A includes a controller 401A and a receiver 402A. The controller 401 A is configured to establish a data pipeline with a first path including a plurality of data pipeline contributors, the receiver 402 A is configured to receive, from a data pipeline contributor, a failure report indicating a data pipeline failure, and the controller 401A is further configured to select at least one candidate data pipeline contributor to replace at least one failed data pipeline contributor. This can solve issues in the prior art and other issues and / or provide stable performance and continuity of data services.

[0055] FIG. 4B illustrates an example of a data pipeline coordinator 400B according to an embodiment of the present disclosure. The data pipeline coordinator 400B is configured to implement some embodiments of the disclosure. Some embodiments of the disclosure may be implemented into the data pipeline coordinator 400B using any suitably configured hardware and / or software. The data pipeline coordinator 400B may include a memory 40 IB, a transceiver 402B, and a processor 403B coupled to the memory 40 IB and the transceiver 402B. The processor 403B may be configured to implement proposed functions, procedures and / or methods described in this description. Layers of radio interface protocol may be implemented in the processor 403B. The memory 40 IB is operatively coupled with the processor 403B and stores a variety of information to operate the processor 403B. The transceiver 402B is operatively coupled with the processor 403B, and the transceiver 402B transmits and / or receives a radio signal. The processor 403B may include application-specific integrated circuit (ASIC), other chipset, logic circuit and / or data processing device. The memory 40 IB may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and / or other storage device. The transceiver 402B may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in the memory 40 IB and executed by the processor 403B. The memory 40 IB can be implemented within the processor 403B or external to the processor 403B in which case those can be communicatively coupled to the processor 403B via various means as is known in the art.Atty. Dkt. No. 10085-01-0186-PCT

[0056] In some embodiments, the processor 403B is configured to establish a data pipeline with a first path including a plurality of data pipeline contributors, the transceiver 402B is configured to receive, from the data pipeline contributor 10, a failure report indicating a data pipeline failure, and the processor 403B is further configured to select at least one candidate data pipeline contributor to replace at least one failed data pipeline contributor. This can solve issues in the prior art and other issues and / or provide stable performance and continuity of data services.

[0057] FIG. 5 is an example of a method 500 of data pipeline failure recovery performed by a data pipeline coordinator according to an embodiment of the present disclosure. The method 500 of data pipeline failure recovery performed by the data pipeline coordinator is configured to implement some embodiments of the disclosure. Some embodiments of the disclosure may be implemented into the method 500 of data pipeline failure recovery performed by the data pipeline coordinator using any suitably configured hardware and / or software. In some embodiments, the method 500 of data pipeline failure recovery performed by the data pipeline coordinator includes: an operation 502, establishing a data pipeline with a first path including a plurality of data pipeline contributors, an operation 504, receiving, from a data pipeline contributor, a failure report indicating a data pipeline failure, and an operation 506, selecting at least one candidate data pipeline contributor to replace at least one failed data pipeline contributor. This can solve issues in the prior art and other issues and / or provide stable performance and continuity of data services.

[0058] In some embodiments, the failure report includes at least one of a data pipeline identifier, a data pipeline path index, a failure cause, a measured key performance indicator (KPI), or a timestamp. In some embodiments, the method further includes determining, based on a previously stored pipeline topology information, a second path for the data pipeline. In some embodiments, the previously stored pipeline topology information includes at least one candidate data pipeline contributor, the at least one candidate data pipeline contributor has at least one performance metric including at least one of a latency, a throughput, a computing resource, or an energy efficiency. In some embodiments, the method further includes transmitting, to the at least one candidate data pipeline contributor, a data pipeline establishment request message. The method may determine a new data pipeline path using stored topology information that identifies candidate contributors with performance metrics, and send establishment requests to selected candidates based on received failure reports.

[0059] In some embodiments, the method further includes receiving, from the at least one candidate data pipeline contributor, a data pipeline establishment response message to confirm an establishment of a second path for the data pipeline. In some embodiments, the method further includes updating, by the data pipeline coordinator, a data pipeline path table to indicate that a failed data pipeline path is ineligible. In some embodiments, selecting the at least one candidate data pipeline contributor is performed based on a recovery process initiated by the data pipeline coordinator. In some embodiments, the recovery process includes negotiating, with the at least one candidate data pipeline contributor, to establish a second path for the data pipeline. In someAtty. Dkt. No. 10085-01-0186-PCT embodiments, the method further includes notifying at least one data pipeline contributor of a second path for the data pipeline for continuing data pipeline execution. The method enables the data pipeline coordinator to confirm new path establishment, update path records, negotiate recovery with candidate contributors, and notify involved nodes to ensure continued pipeline execution.

[0060] FIG. 6A illustrates an example of a data pipeline contributor 600A according to an embodiment of the present application. The data pipeline contributor 600A is configured to implement some embodiments of the disclosure. Some embodiments of the disclosure may be implemented into the data pipeline contributor 600A using any suitably configured hardware and / or software. The data pipeline contributor 600A includes a controller 601A and a detector 602A. The controller 601 A is configured to participate in a data pipeline with a first path including a plurality of data pipeline contributors, the detector 602 A is configured to detect that a data pipeline failure has occurred, and the controller 601A is further configured to initiate a recovery process to switch the data pipeline from the first path to a second path. This can solve issues in the prior art and other issues and / or provide stable performance and continuity of data services.

[0061] FIG. 6B illustrates an example of a data pipeline contributor 600B according to an embodiment of the present disclosure. The data pipeline contributor 600B is configured to implement some embodiments of the disclosure. Some embodiments of the disclosure may be implemented into the data pipeline contributor 600B using any suitably configured hardware and / or software. The data pipeline contributor 600B may include a memory 60 IB, a transceiver 602B, and a processor 603B coupled to the memory 60 IB and the transceiver 602B. The processor 603B may be configured to implement proposed functions, procedures and / or methods described in this description. Layers of radio interface protocol may be implemented in the processor 603B. The memory 60 IB is operatively coupled with the processor 603B and stores a variety of information to operate the processor 603B. The transceiver 602B is operatively coupled with the processor 603B, and the transceiver 602B transmits and / or receives a radio signal. The processor 603B may include application-specific integrated circuit (ASIC), other chipset, logic circuit and / or data processing device. The memory 60 IB may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and / or other storage device. The transceiver 602B may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in the memory 60 IB and executed by the processor 603B. The memory 60 IB can be implemented within the processor 603B or external to the processor 603B in which case those can be communicatively coupled to the processor 603B via various means as is known in the art.

[0062] In some embodiments, the processor 603B is configured to participate in a data pipeline with a first path including a plurality of data pipeline contributors, the processor 603B isAtty. Dkt. No. 10085-01-0186-PCT configured to detect that a data pipeline failure has occurred, and the processor 603B is further configured to initiate a recovery process to switch the data pipeline from the first path to a second path. This can solve issues in the prior art and other issues and / or provide stable performance and continuity of data services. This can solve issues in the prior art and other issues and / or provide stable performance and continuity of data services.

[0063] FIG. 7 is an example of a method 700 of data pipeline failure recovery performed by a data pipeline contributor according to an embodiment of the present disclosure. The method 700 of data pipeline failure recovery performed by the data pipeline contributor is configured to implement some embodiments of the disclosure. Some embodiments of the disclosure may be implemented into the method 700 of data pipeline failure recovery performed by the data pipeline contributor using any suitably configured hardware and / or software. In some embodiments, the method 700 of data pipeline failure recovery performed by the data pipeline contributor includes: an operation 702, participating in a data pipeline with a first path including a plurality of data pipeline contributors, an operation 704, detecting that a data pipeline failure has occurred, and an operation 706, initiating a recovery process to switch the data pipeline from the first path to a second path. This can solve issues in the prior art and other issues and / or provide stable performance and continuity of data services.

[0064] In some embodiments, detecting the data pipeline failure includes determining that at least one performance metric fails to meet a configured threshold. In some embodiments, the performance metric includes at least one of a latency, a throughput, or an available computing power. In some embodiments, the method further includes transmitting, to at least one candidate data pipeline contributor, a candidate path request message including an information regarding a data pipeline requirement. In some embodiments, the method further includes receiving, from the at least one candidate data pipeline contributor, a candidate path response message confirming a path switch. In some embodiments, the candidate data pipeline contributor has a same previous- hop node and next-hop node as a failed data pipeline contributor. The method allows a data pipeline contributor to detect performance degradation based on thresholded metrics, request and confirm a path switch with a candidate contributor having the same adjacent nodes to maintain pipeline continuity.

[0065] In some embodiments, the method further includes notifying a previous-hop data pipeline contributor of a path switch. In some embodiments, the method further includes notifying a data pipeline coordinator of a path switch for synchronization of pipeline topology information. In some embodiments, when no suitable candidate data pipeline contributor is found, the data pipeline contributor reports a failure to the data pipeline coordinator to trigger the recovery process. In some embodiments, the recovery process is executed based on pre-stored candidate data pipeline paths received from the data pipeline coordinator during a pipeline establishment. The method includes notifying upstream contributors and the coordinator of a path switch, or reporting failure to trigger recovery based on pre-stored candidate paths provided during pipeline establishment.Atty. Dkt. No. 10085-01-0186-PCT

[0066] Exemplary Technical Solutions:

[0067] FIG. 8 is an example of data pipeline topology according to an embodiment of the present disclosure. FIG. 8 illustrates in the following example topology of a data pipeline, data sources (A, B, C), data operation nodes (D, E, F, G, H, I), and data sink (K) are all data pipeline contributor candidates for a service flow requested by a customer. FIG. 8 illustrates an example data pipeline topology in which data sources (A, B, C), operation nodes (D to I), and a data sink (K) serve as contributor candidates for a customer-requested service flow.

[0068] In some techniques, the data pipeline coordinator may select the data pipeline contributor for the requested service flow. Example of topology of data pipeline contributor candidate is illustrated in the following table 1.

[0069] Table 1 : Example of topology of data pipeline contributor candidate.

[0070] Assume the data pipeline coordinator determines the following data pipeline contributor and the path are possible by considering the data pipeline requirements and each candidate’ s KPI’ s, for example, latency, throughput, computing resources, energy efficiency, data size, etc. Each eligible data pipeline path has an ID and a priority with 0 as the highest priority. The data pipeline coordinator selects possible contributor paths based on requirements and candidate KPIs such as latency, throughput, computing resources, energy efficiency, and data size, assigning each path an ID and priority, with 0 as the highest. Example of data pipeline contributor and path is illustrated in the following table 2.

[0071] Table 2: Example of data pipeline contributor and path.Atty. Dkt. No. 10085-01-0186-PCT

[0072] Assume data pipeline path 1, i.e. B-D-H-K, is selected, the data pipeline coordinator notifies the involved contributor to start data pipeline execution. From now on, data pipeline failure recovery and failure recovery are required to maintain data pipeline operation continuity. When data pipeline path 1 (B-D-H-K) is selected, the coordinator instructs the contributors to begin execution, after which failure recovery and failure recovery ensure operational continuity.

[0073] In some embodiments, in a data pipeline failure recovery mechanism, when a data pipeline contributor detects a failure on data pipeline execution, data pipeline failure recovery may be performed. There can be at least one of the following solutions:

[0074] Failure recovery by the data pipeline coordinator: In this solution, the involved data pipeline contributor will report data pipeline failure to the data pipeline coordinator. Then the coordinator may negotiate with other contributor candidates to establish a new path. This solution is called global recovery. In this global recovery solution, the data pipeline coordinator restores operation by receiving a failure report and negotiating with alternative contributors to establish a new path.

[0075] Failure recovery by the local data pipeline contributor: In this solution, the data pipeline contributors involved may negotiate with each other to establish a new path and then notify the data pipeline coordinator. This solution requires the data pipeline coordinator to share the possible pipeline path to the contributor, so the failed contributor can directly communicate with other candidates for the new path. This solution is called local recovery. In this local recovery solution, data pipeline contributors directly negotiate to form a new path using coordinator-provided path information and then notify the coordinator of the recovery.

[0076] FIG. 9 illustrates a data pipeline failure recovery by a data pipeline coordinator according to an embodiment of the present disclosure. FIG. 9 illustrates that, in some embodiments, the data pipeline failure recovery by the data pipeline coordinator includes at least one of the following operations:

[0077] 1. The data pipeline coordinator notifies data source B for data pipeline establishment.

[0078] 2. The data pipeline coordinator notifies data operation D for data pipeline establishment.

[0079] 3. The data pipeline coordinator notifies data operation H for data pipeline establishment.

[0080] 4. Data pipeline with path B-D-H-K is established and starts execution.

[0081] 5. Data operation D detects a failure of data pipeline. The failure causes can be at least one of the followings.

[0082] a. Data operation D does not have enough computing power.

[0083] b. The delay of the previous hop (B-D) is too large.

[0084] c. The throughput of the previous hop (B-D) is not sufficient.Atty. Dkt. No. 10085-01-0186-PCT

[0085] d. other KPI’s.

[0086] 6. Data operation D reports data pipeline failure report message the data pipeline coordinator. In this message, the following information can be included: the data pipeline ID, the data pipeline path index, the failure cause, the measured KPI’s quantities, e.g. delay, the available computing power, etc., and time stamp of the failure.

[0087] 7. The data pipeline coordinator uses its previous knowledge to find an alternative path for this data pipeline. Or, if there is no previous knowledge, the data pipeline coordinator may start a new data pipeline contributor selection process to find new contributors. The data pipeline coordinator updates its pipeline path information to mark B-D-H-K as ineligible path.

[0088] 8. The coordinator decides data operation E can be a new candidate for pipeline contributor and sends data pipeline establishment request.

[0089] 9. Data operation E accepts the request and sends data pipeline establishment response to the coordinator.

[0090] 10. The coordinator decides data operation I can be a new candidate for pipeline contributor and sends data pipeline establishment request.

[0091] 11. Data operation I may accept the request and send data pipeline establishment response to the coordinator.

[0092] 12. The data pipeline coordinator notifies data operation E for data pipeline establishment.

[0093] 13. The data pipeline coordinator notifies data operation I for data pipeline establishment.

[0094] 14. Data pipeline with path B-E-I-K is established and starts execution.

[0095] In some embodiments, the data pipeline coordinator restores operation by receiving a failure report, selecting new contributors (E and I), establishing a replacement path (B-E-I-K), and resuming data pipeline execution.

[0096] FIG. 10 illustrates a data pipeline failure recovery by a data pipeline contributor according to an embodiment of the present disclosure. FIG. 10 illustrates that, in some embodiments, the data pipeline failure recovery by the data pipeline contributor includes at least one of the following operations:

[0097] 1. The data pipeline coordinator notifies data source B for data pipeline establishment. In the message, alternative data pipeline paths are also included.

[0098] 2. The data pipeline coordinator notifies data operation D for data pipeline establishment. In the message alternative data pipeline paths are also included.

[0099] 3. The data pipeline coordinator notifies data operation H for data pipeline establishment. In the message alternative data pipeline paths are also included.

[0100] 4. Data pipeline with path B-D-H-K is established and starts execution.

[0101] 5. Data operation D detects a failure of data pipeline. The failure causes can be at least one of the followings:

[0102] a. Data operation D does not have enough computing power.Atty. Dkt. No. 10085-01-0186-PCT

[0103] b. The delay of the previous hop (B-D) is too large.

[0104] c. The throughput of the previous hop (B-D) is not sufficient.

[0105] d. other KPI’s.

[0106] 6. According to the received alternative pipeline paths, data operation D selects data operation E as an alternative to continue supporting the current data pipeline execution.

[0107] a. In this solution, the data pipeline contributor is only allowed to select an alternative that has the same previous-hop and next-hop nodes. In this example, contributor E has previous- hop node B and next-hop node H.

[0108] b. If data operation D cannot find an alternative, it may report the failure to the data pipeline coordinator. The global recovery solution in the previous section will be used.

[0109] 7. Data operation D sends the alternative path request message to data operation E to request path switch. In this message, the data pipeline requirement at data operation D is included to assist data operation E to decide.

[0110] 8. Data operation E sends the alternative path response message to data operation D to confirm path switch.[OHl] 9. Data operation D notifies data source B about path switch.

[0112] 10. Data pipeline path (B-E-H-K) starts execution.

[0113] 11.Data operation D notifies the data pipeline coordinator about the path switch.

[0114] 12.Data operation E notifies the data pipeline coordinator about the path switch.

[0115] 13. The data pipeline coordinator updates the data pipeline path table to reflect the change. The data pipeline coordinator can also re-select pipeline contributors.

[0116] In some embodiments, a local recovery process is performed where the data pipeline contributor D detects a failure, selects an alternative contributor E with the same adjacent nodes based on pre-received path information, exchanges path switch messages, notifies the source B and coordinator, and establishes a new operational path (B-E-H-K) to maintain pipeline continuity.

[0117] Commercial interests for some embodiments are as follows. 1. Solve issues in the prior art and other issues. 2. Provide stable performance and continuity of data services. 3. Provide a good communication performance. 4. Provide high reliability. Some embodiments of the present disclosure can be used in many applications. Some embodiments of the present disclosure are used by chipset vendors, video system development vendors, automakers including cars, trains, trucks, buses, bicycles, moto-bikes, helmets, and etc., drones (unmanned aerial vehicles), smartphone makers, communication devices for public safety use, AR. / VR. / MR. device maker for example gaming, conference / seminar, education purposes. Some embodiments of the present disclosure are a combination of “techniques / processes” that can be adopted in video standards to create an end product. Some embodiments of the present disclosure propose technical mechanisms. The at least one proposed solution, method, system, and apparatus of some embodiments of the present disclosure may be used for current and / or new / future standards regarding communication systems such as a UE, a base station, and / or a communication system. Compatible products follow at leastAtty. Dkt. No. 10085-01-0186-PCT one proposed solution, method, system, and apparatus of some embodiments of the present disclosure. The proposed solution, method, system, and apparatus are widely used in a UE, a base station, and / or a communication system. With the implementation of the at least one proposed solution, method, system, and apparatus of some embodiments of the present disclosure, at least one modification to methods and apparatus of wireless communication are considered for standardizing.

[0118] In some embodiments, a network function includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The network function is configured to perform the above method. In some embodiments, a core network element includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The core network element is configured to provide the above method. In some embodiments, a non-transitory machine- readable storage medium has stored thereon instructions that, when executed by a computer, cause the computer to perform the above method. In some embodiments, a chip includes a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the above method. In some embodiments, a computer readable storage medium, in which a computer program is stored, causes a computer to execute the above method. In some embodiments, a computer program product includes a computer program, and the computer program causes a computer to execute the above method. In some embodiments, a computer program causes a computer to execute the above method.

[0119] In some embodiments, a network function or a core network element may be implemented using a computing platform such as the example computing device 1100 illustrated in FIG. 11 or the communication system 1200 illustrated in FIG. 12. As shown in FIG. 11, the computing device 1100 may include a processor 1112, memory 1114, and input / output (VO) interfaces 1118 coupled via a bus 1116. The processor 1112 may execute program code stored in the memory 1114 to perform one or more methods described above with respect to FIG. 1 to FIG. 10. The memory 1114 may be a non-transitory computer-readable medium storing instructions that, when executed, enable NAS message handling, partial decoding, SRB-based routing, or collaboration with the AMF. In some cases, the program code may be stored on a separate computer-readable storage medium or integrated within the device as a computer program product. As shown in FIG. 12, the communication system 1200 may include RF circuitry 1210, baseband circuitry 1220, application circuitry 1230, and memory / storage 1240, among other components such as display 1250, camera 1260, sensor 1270, and I / O interface 1280. The application circuitry 1230 and baseband circuitry 1220 may be configured to execute program instructions and perform processing functions related to NAS signaling, including determining the destination core network function, managing signaling bearers, and communicating with the AMF. These components may be integrated into a mobile or edge device, supporting edge-cloud deployment as described in earlier embodiments. The hardware and software integration in such devices enables flexible and efficient execution of the NAS message distribution mechanisms disclosed herein.Atty. Dkt. No. 10085-01-0186-PCT

[0120] FIG. 11 is an example of a computing device 1100 according to an embodiment of the present disclosure. Any suitable computing device can be used for performing the operations described herein. For example, FIG. 11 illustrates an example of the computing device 1100 that can implement some embodiments of FIG. 1 to FIG. 10 using any suitably configured hardware and / or software. In some embodiments, the computing device 1100 can include a processor 1112 that is communicatively coupled to a memory 1114 and that executes computer-executable program code and / or accesses information stored in the memory 1114. The processor 1112 may include a microprocessor, an application-specific integrated circuit (“ASIC”), a state machine, or other processing device. The processor 1112 can include any of a number of processing devices, including one. Such a processor can include or may be in communication with a computer-readable medium storing instructions that, when executed by the processor 1112, cause the processor to perform the operations described herein.

[0121] The memory 1114 can include any suitable non-transitory computer-readable medium. The computer-readable medium can include any electronic, optical, magnetic, or other storage device capable of providing a processor with computer-readable instructions or other program code. Non-limiting examples of a computer-readable medium include a magnetic disk, a memory chip, a read-only memory (ROM), a random access memory (RAM), an application specific integrated circuit (ASIC), a configured processor, optical storage, magnetic tape or other magnetic storage, or any other medium from which a computer processor can read instructions. The instructions may include processor-specific instructions generated by a compiler and / or an interpreter from code written in any suitable computer-programming language, including, for example, C, C++, C#, visual basic, java, python, perl, javascript, and actionscript.

[0122] The computing device 1100 can also include a bus 1116. The bus 1116 can communicatively couple one or more components of the computing device 1100. The computing device 1100 can also include a number of external or internal devices such as input or output devices. For example, the computing device 1100 is illustrated with an input / output (“VO”) interface 1118 that can receive input from one or more input devices 1120 or provide output to one or more output devices 1122. The one or more input devices 1120 and one or more output devices 1122 can be communicatively coupled to the I / O interface 1118. The communicative coupling can be implemented via any suitable manner (e.g., a connection via a printed circuit board, connection via a cable, communication via wireless transmissions, etc.). Non-limiting examples of input devices 1120 include a touch screen (e g., one or more cameras for imaging a touch area or pressure sensors for detecting pressure changes caused by a touch), a mouse, a keyboard, or any other device that can be used to generate input events in response to physical actions by a user of a computing device. Non-limiting examples of output devices 1122 include a liquid crystal display (LCD) screen, an external monitor, a speaker, or any other device that can be used to display or otherwise present outputs generated by a computing device.Atty. Dkt. No. 10085-01-0186-PCT

[0123] The computing device 1100 can execute program code that configures the processor 1112 to perform one or more of the operations described above with respect to some embodiments of FIG. 1 to FIG. 10. The program code may be resident in the memory 1114 or any suitable computer-readable medium and may be executed by the processor 1112 or any other suitable processor.

[0124] The computing device 1100 can also include at least one network interface device 1124. The network interface device 1124 can include any device or group of devices suitable for establishing a wired or wireless data connection to one or more data networks 1128. Non limiting examples of the network interface device 1124 include an Ethernet network adapter, a modem, and / or the like. The computing device 1100 can transmit messages as electronic or optical signals via the network interface device 1124.

[0125] FIG. 12 is a block diagram of an example of a communication system 1200 according to an embodiment of the present disclosure. Embodiments described herein may be implemented into the communication system 1200 using any suitably configured hardware and / or software. FIG. 12 illustrates the communication system 1200 including a radio frequency (RF) circuitry 1210, a baseband circuitry 1220, an application circuitry 1230, a memory / storage 1240, a display 1250, a camera 1260, a sensor 1270, and an input / output (VO) interface 1280, coupled with each other at least as illustrated.

[0126] The application circuitry 1230 may include a circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and dedicated processors, such as graphics processors, application processors. The processors may be coupled with the memory / storage and configured to execute instructions stored in the memory / storage to enable various applications and / or operating systems running on the system. The communication system 1200 can execute program code that configures the application circuitry 1230 to perform one or more of the operations described above with respect to some embodiments of FIG. 1 to FIG. 10. The program code may be resident in the application circuitry 1230 or any suitable computer-readable medium and may be executed by the application circuitry 1230 or any other suitable processor.

[0127] The baseband circuitry 1220 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include a baseband processor. The baseband circuitry may handle various radio control functions that may enable communication with one or more radio networks via the RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuitry may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with an evolved universal terrestrial radio access network (EUTRAN) and / or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry is configured toAtty. Dkt. No. 10085-01-0186-PCT support radio communications of more than one wireless protocol may be referred to as multimode baseband circuitry.

[0128] In various embodiments, the baseband circuitry 1220 may include circuitry to operate with signals that are not strictly considered as being in a baseband frequency. For example, in some embodiments, baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency. The RF circuitry 1210 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. In various embodiments, the RF circuitry 1210 may include circuitry to operate with signals that are not strictly considered as being in a radio frequency. For example, in some embodiments, RF circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.

[0129] In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to some embodiments of FIG. 1 to FIG. 10 may be embodied in whole or in part in one or more of the RF circuitry, the baseband circuitry, and / or the application circuitry. As used herein, “circuitry” may refer to, be part of, or include an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and / or a memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and / or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, some or all of the constituent components of the baseband circuitry, the application circuitry, and / or the memory / storage may be implemented together on a system on a chip (SOC). The memory / storage 1240 may be used to load and store data and / or instructions, for example, for system. The memory / storage for one embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM)), and / or non-volatile memory, such as flash memory.

[0130] In various embodiments, the VO interface 1280 may include one or more user interfaces designed to enable user interaction with the system and / or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface. In various embodiments, the sensor 1270 may include one or more sensing devices to determine environmental conditions and / or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interactAtty. Dkt. No. 10085-01-0186-PCT with, the baseband circuitry and / or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite.

[0131] In various embodiments, the display 1250 may include a display, such as a liquid crystal display and a touch screen display. In various embodiments, the communication system 1200 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, an AR / VR glasses, etc. In various embodiments, system may have more or less components, and / or different architectures. Where appropriate, methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

[0132] A person having ordinary skill in the art understands that each of the units, algorithm, and operations described and disclosed in the embodiments of the present disclosure are realized using electronic hardware or combinations of software for computers and electronic hardware. Whether the functions run in hardware or software depends on the condition of application and design requirement for a technical plan. A person having ordinary skill in the art can use different ways to realize the function for each specific application while such realizations should not go beyond the scope of the present disclosure. It is understood by a person having ordinary skill in the art that he / she can refer to the working processes of the system, device, and unit in the above-mentioned embodiment since the working processes of the above-mentioned system, device, and unit are basically the same. For easy description and simplicity, these working processes will not be detailed.

[0133] It is understood that the disclosed system, device, and method in the embodiments of the present disclosure can be realized with other ways. The above-mentioned embodiments are exemplary only. The division of the units is merely based on logical functions while other divisions exist in realization. It is possible that a plurality of units or components are combined or integrated in another system. It is also possible that some characteristics are omitted or skipped. On the other hand, the displayed or discussed mutual coupling, direct coupling, or communicative coupling operate through some ports, devices, or units whether indirectly or communicatively by ways of electrical, mechanical, or other kinds of forms.

[0134] The units as separating components for explanation are or are not physically separated. The units for display are or are not physical units, that is, located in one place or distributed on a plurality of network units. Some or all of the units are used according to the purposes of the embodiments. Moreover, each of the functional units in each of the embodiments can be integrated in one processing unit, physically independent, or integrated in one processing unit with two or more than two units.

[0135] If the software function unit is realized and used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical plan proposed by the present disclosure can be essentially or partially realized as the form of a software product. Or, one part of the technical plan beneficial to the conventional technology can be realized as theAtty. Dkt. No. 10085-01-0186-PCT form of a software product. The software product in the computer is stored in a storage medium, including a plurality of commands for a computational device (such as a personal computer, a server, or a network device) to run all or some of the operations disclosed by the embodiments of the present disclosure. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other kinds of media capable of storing program codes.

[0136] While the present disclosure has been described in connection with what is considered the most practical and preferred embodiments, it is understood that the present disclosure is not limited to the disclosed embodiments but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.

Claims

Atty. Dkt. No. 10085-01-0186-PCTWhat is claimed is:

1. A method of data pipeline failure recovery performed by a data pipeline coordinator, comprising: establishing a data pipeline with a first path comprising a plurality of data pipeline contributors; receiving, from a data pipeline contributor, a failure report indicating a data pipeline failure; and selecting at least one candidate data pipeline contributor to replace at least one failed data pipeline contributor.

2. The method of claim 1, wherein the failure report comprises at least one of: a data pipeline identifier, a data pipeline path index, a failure cause, a measured key performance indicator (KPI), or a timestamp.

3. The method of claim 1, further comprising determining, based on a previously stored pipeline topology information, a second path for the data pipeline.

4. The method of claim 3, wherein the previously stored pipeline topology information comprises at least one candidate data pipeline contributor, the at least one candidate data pipeline contributor has at least one performance metric comprising at least one of a latency, a throughput, a computing resource, or an energy efficiency.

5. The method of claim 1, further comprising transmitting, to the at least one candidate data pipeline contributor, a data pipeline establishment request message.

6. The method of claim 5, wherein further comprising receiving, from the at least one candidate data pipeline contributor, a data pipeline establishment response message to confirm an establishment of a second path for the data pipeline.

7. The method of claim 1, further comprising updating, by the data pipeline coordinator, a data pipeline path table to indicate that a failed data pipeline path is ineligible.

8. The method of claim 1, wherein selecting the at least one candidate data pipeline contributor is performed based on a recovery process initiated by the data pipeline coordinator.

9. The method of claim 8, wherein the recovery process comprises negotiating, with the at least one candidate data pipeline contributor, to establish a second path for the data pipeline.

10. The method of claim 1, further comprising notifying at least one data pipeline contributor of a second path for the data pipeline for continuing data pipeline execution.

11. A method of data pipeline failure recovery performed by a data pipeline contributor, comprising: participating in a data pipeline with a first path comprising a plurality of data pipeline contributors; detecting that a data pipeline failure has occurred; and initiating a recovery process to switch the data pipeline from the first path to a second path.

12. The method of claim 11, wherein detecting the data pipeline failure comprises determining that at least one performance metric fails to meet a configured threshold.Atty. Dkt. No. 10085-01-0186-PCT13. The method of claim 12, wherein the performance metric comprises at least one of a latency, a throughput, or an available computing power.

14. The method of claim 11, further comprising transmitting, to at least one candidate data pipeline contributor, a candidate path request message comprising an information regarding a data pipeline requirement.

15. The method of claim 14, further comprising receiving, from the at least one candidate data pipeline contributor, a candidate path response message confirming a path switch.

16. The method of claim 11, wherein the candidate data pipeline contributor has a same previous- hop node and next-hop node as a failed data pipeline contributor.

17. The method of claim 11, further comprising notifying a previous-hop data pipeline contributor of a path switch.

18. The method of claim 11, further comprising notifying a data pipeline coordinator of a path switch for synchronization of pipeline topology information.

19. The method of claim 11, wherein when no suitable candidate data pipeline contributor is found, the data pipeline contributor reports a failure to the data pipeline coordinator to trigger the recovery process.

20. The method of claim 11, wherein the recovery process is executed based on pre-stored candidate data pipeline paths received from the data pipeline coordinator during a pipeline establishment.

21. A data pipeline coordinator, comprising: a controller configured to establish a data pipeline with a first path comprising a plurality of data pipeline contributors; and a receiver configured to receive, from a data pipeline contributor, a failure report indicating a data pipeline failure, wherein the controller is further configured to select at least one candidate data pipeline contributor to replace at least one failed data pipeline contributor.

22. A data pipeline coordinator, comprising: a memory; a transceiver; and a processor coupled to the memory and the transceiver; wherein the data pipeline coordinator is configured to perform the method of any one of claims 1 to 10.

23. A data pipeline contributor, comprising: a controller configured to participate in a data pipeline with a first path comprising a plurality of data pipeline contributors; and a detector configured to detect that a data pipeline failure has occurred, wherein the controller isAtty. Dkt. No. 10085-01-0186-PCT further configured to initiate a recovery process to switch the data pipeline from the first path to a second path.

24. A data pipeline contributor, comprising: a memory; a transceiver; and a processor coupled to the memory and the transceiver; wherein the data pipeline contributor is configured to perform the method of any one of claims 11 to 20.

Images