WO2025091738A1

WO2025091738A1 - Method, apparatus and readable storage medium for communication

Info

Publication number: WO2025091738A1
Application number: PCT/CN2024/080858
Authority: WO
Inventors: Weisen SHI; Xu Li; Chenchen YANG; Hang Zhang
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2023-10-30
Filing date: 2024-03-08
Publication date: 2025-05-08
Anticipated expiration: 2026-04-30

Abstract

The disclosure relates to the wireless communication field, and discloses a method, apparatus and readable storage medium for communication. In this method, MM can send request to TCF based on performance information of each TE, or on request sent by MC, to manage the ME process. The request from MM to TCF can be state create request, state cancel request, pause request, resume request, rollback request, or terminate request, etc. For example, in the ME process, if the data corresponding to one TE is contaminated, MM can send a rollback request to the TE, to roll back to the point when the data was not contaminated. For another example, in the ME process, if the computing resources are insufficient, MM can send a pause request to pause the ME process after the current TE is finished. In this way, mission execution can be completed successfully. And at the same time, the accuracy of mission execution results as well as the efficiency of mission execution will also be improved.

Description

METHOD, APPARATUS AND READABLE STORAGE MEDIUM FOR COMMUNICATION

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to, and claims priority to: United States provisional patent application Serial No. 63/594,054, entitled “Method, Apparatus and System for Mission Execution Scheduling and State Management” , filed on October 30, 2023, the entire contents of both of which are incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates to wireless communication field, and in particular to a method, apparatus and readable storage medium for communication.

BACKGROUND

In the field of wireless communication technology, 5th Generation Mobile Communication Technology (5G) has been widely used because of its characteristics of “ultra-high speed, ultra-low delay, ultra-large connection” . 5G system architecture includes a control plane and a user plane. The control plane is used to control the data transmission path and bear control signaling, etc. The user plane function in the user plane is mainly responsible for the routing and forwarding of packets and business identification.

However, the use of 5G system architecture is limited. For example, based on the above content, 5G system architecture in the actual application process, is only responsible for data transmission and forwarding operations, rather than data computing and other data processing operations. Therefore, a new system architecture is needed to solve the above technical problems.

SUMMARY

The following examples pertain to embodiments described throughout this disclosure.

In the first aspect, described may include a first apparatus, comprising: at least one processor, wherein the at least one processor is configured to: receive a first request from mission customer in a communication system, or generate the first request based on task execution performance information from a plurality of task control functions in the communication system, wherein the communication system is used to execute a first mission, and one of the plurality of task control functions is used to manage execution of at least one task of the first mission; send a second request to a first task control function in the plurality of task control functions, wherein the first task control function is used to manage a first task execution of the execution of at least one task, and the second request indicates the first request.

In one or more possible implementations, the second request is state create request, state cancel request, pause request, resume request, rollback request, or terminate request; and the second request includes a first task execution identifier of the first task execution.

Illustratively, MM may send the second request to first task control function (TCF) according to the first request, and the first request can be received from mission customer (MC) or generate by MM according to task execution performance. That is to say, MM takes the role of managing the mission execution (ME) . For example, if during the process of ME, the data is contaminated, MM can manage the ME by sending pause request to indicate the pausing of the ME, thus avoiding low ME efficiency because of the contaminated data. Therefore, the ME efficiency can be ensured and improved.

In one or more possible implementations, the at least one processor is further configured to: receive second request response from the first task control function, wherein the second request response indicates completion of the second request and includes the first task execution identifier.

In the second aspect, described may include a second apparatus, comprising: at least one processor, wherein the at least one processor is configured to: receive a second request from mission management used to execute a first mission including at least one task in a communication system; execute the second request, wherein the second request includes a first task execution identifier of a first task execution corresponding to a first task in the at least one task; send second request response including the first task execution identifier to the mission management.

In one or more possible implementations, the first task execution corresponds to first task execution information including the first task execution identifier, first task execution results, and first task execution parameters including first task execution information save mode and location of the first task execution results.

Please note that after the first TCF receives the second request from MM, it can execute the second request. For example, if the second request indicates that the first TCF pauses the ME, the first TCF may pause the ME. What’s more, the second request can be state create request, state cancel request, pause request, resume request, rollback request, or terminate request.

In one or more possible implementations, the second request is a state create request, and execute the second request comprises: saving the first task execution information.

Please note that a state may be created after a task execution (TE) is finished, and creating a state means that the TE information may be saved and the TE information may be the first TE information. That is to say, only when the first TE information is saved, the state can be created successfully.

In one or more possible implementations, saving the first task execution information comprises: sending first task execution results save request to a first terminal processing service function, wherein the first task execution results save request includes first task execution results saving location information, and the first terminal processing service function is used to perform the first task execution; receiving first task execution results save request response from the first terminal processing service function, wherein the first task execution results save request response informs completion of saving the first task execution results; saving the first task execution identifier and the first task execution parameters, wherein the first task execution information save mode is state mode.

In FIG. 6, the first terminal processing service function (the first terminal PSF) of TE A1 is PSF3, and the first terminal PSF of TE B1 is PSF5. If TCF2 wants to save the TE B1 information, it may send request to PSF5, requesting PSF5 to save the TE B1 results. In addition, TCF2 may also save the ID of the TE B1 and set the TE B1 information save mode as state mode. By doing so, the state can be created, making the ME more efficient.

In one or more possible implementations, the second request is a state cancel request, and execute the second request comprises: releasing the first task execution information.

Please note that cancelling a state means that the TE information may be released. In FIG. 7, if state 2 needs to be cancelled, the TE B1 information may be released.

In one or more possible implementations, releasing the first task execution information comprises: sending first task execution results release request to a first terminal processing service function, wherein the first task execution results release request includes first task execution results saving location information; receiving first task execution results release request response from the first terminal processing service function, wherein the first task execution results release request response informs completion of releasing the first task execution results; releasing the first task execution parameters.

In FIG. 6 and FIG. 7, if TCF2 wants to cancel state 2, it may send request to PSF5, requesting PSF5 to release the TE B1 results. In addition, TCF2 may also release the TE B1 parameters such as TE B1 information save mode and location of the TE B1 results. By doing so, the state can be cancelled.

In one or more possible implementations, the second request is a pause request; and execute the second request comprises: saving the first task execution information; sending first task execution results forward suspending request to a first terminal processing service function, to inform the first terminal processing service function suspend forwarding the first task execution results.

Illustratively, in FIG. 6, if ME is paused after TE B1 is finished, TCF2 may send request to PSF5 for informing PSF5 to save the TE B1 information. In addition, TCF2 may also send TE B1 results forward suspending request to PSF5, for informing PSF5 suspend forwarding the TE B1 results. By doing so, if the resource is not enough for executing the mission, ME can be paused, avoiding running out of computing resources during ME.

In one or more possible implementations, saving the first task execution information comprises: sending first task execution results save request to the first terminal processing service function, wherein the first task execution results save request includes first task execution results saving location information, and the first terminal processing service function is used to perform the first task execution; receiving first task execution results save request response from the first terminal processing service function, wherein the first task execution results save request response informs completion of saving the first task execution results; saving the first task execution identifier and the first task execution parameters, wherein the first task execution information save mode is pause mode when the first task execution information save mode isn’ t save mode.

Please note that only when the first task execution information save mode (e.g. TE B1 information save mode) isn’ t save mode, the TE B1 information save mode may be set as pause mode when ME is paused after TE B1 is finished. That is to say, if the TE B1 information save mode is save mode, the TE B1 information save mode may not be set as pause mode even when ME is paused after TE B1 is finished. Because if the TE B1 information save mode is pause mode, when ME is resumed, the TE B1 information may be released, while if the TE B1 information save mode is state mode, the TE B1 information will be saved throughout the ME process. By setting the first task execution information save mode, the releasing and saving of the first task execution information can be distinguished effectively, thus improving the ME efficiency.

In one or more possible implementations, the second request is a resume request; and execute the second request comprises: loading the first task execution information; sending first task execution results forwarding request to a first terminal processing service function, to inform the first terminal processing service function forward the first task execution results; releasing the first task execution information when the first task execution information save mode is pause mode.

Based on above description, if the TE B1 information save mode is pause mode, after ME is resumed, TCF2 may send request to PSF5 for informing PSF5 to load previously saved TE B1 information. After PSF5 has loaded the TE B1 information, PSF5 can forward the TE B1 results to its next PSF. What’s more, after PSF5 has loaded the TE B1 information, TCF2 may also inform PSF5 to release previously saved TE B1 information. That is to say, the TE B1 information may not be stored after ME is resumed.

In one or more possible implementations, loading the first task execution information comprises: loading the first task execution parameters; sending first task execution results load request to the first terminal processing service function, wherein the first task execution results load request includes the first task execution results saving location information; receiving first task execution results load request response from the first terminal processing service function, wherein the first task execution results load request response informs completion of loading the first task execution results.

In one or more possible implementations, releasing the first task execution information when the first task execution information save mode is pause mode comprises: sending first task execution results release request to the first terminal processing service function, wherein the first task execution results release request includes the first task execution results saving location information; receiving first task execution results release request response from the first terminal processing service function, wherein the first task execution results release request response informs completion of releasing the first task execution results; releasing the first task execution parameters.

Please note that the TE B1 information includes TE B1 results and TE B1 parameters. So if TCF2 wants to release TE B1 information, it may inform PSF5 to release TE B1 results, and then it may also release TE B1 parameters such as TE B1 information save mode and TE B1 results saving location. By doing so, after ME is resumed, the TE B1 information is released, saving the storage space for information in ME process.

In one or more possible implementations, the second request is a rollback request; and execute the second request comprises: loading the first task execution information.

Illustratively, if there is TE B1 error information, and there is state 1 after TE A1 is finished, MM may manage the ME to rollback to state 1. By doing so, ME can be rollbacked to state 1 whose TE A1 information is normal, avoiding affecting results of mission because of TE B1’s error. Thus, the ME efficiency and accuracy can be improved.

In one or more possible implementations, loading the first task execution information comprises: loading the first task execution parameters; sending first task execution results load request to a first terminal processing service function, wherein the first task execution results load request includes the first task execution results saving location information; receiving first task execution results load request response from the first terminal processing service function, wherein the first task execution results load request response informs completion of loading the first task execution results.

Please note that the TE A1 results have been saved because there is state 1 after TE A1, so TCF1 may inform PSF3 to load previously saved TE A1 results. And the mission can be re-executed from state 1 again.

In one or more possible implementations, the second request is a terminate request including first task execution termination conditions; and execute the second request comprises: sending a first terminal processing service function execution terminate request to a first terminal processing service function, wherein the first terminal processing service function execution terminate request includes identifier of the first terminal processing service function and terminate conditions, and the first terminal processing service function is used to perform the first task execution; receiving first terminal processing service function execution terminate request response informing completion of first terminal processing service function execution termination and first terminal processing service function resource release; releasing first task management resources including computing resources of the first task execution.

In the third aspect, described may include a third apparatus, comprising: at least one processor, wherein the at least one processor is configured to: accept a third request from a first task control function in a communication system, wherein the communication system is used to manage execution of a first mission and the first task control function is used to manage a first task corresponding to the first mission; execute the third request; send third request response to the first task control function.

Please note that the third apparatus may be the first terminal processing service function mentioned above. After the first terminal processing service function receives the third request, it can execute the third request. For example, the third request may be the first TE results save request, the first TE results release request, the first TE results forward suspending request, the first TE results forwarding request, the first TE results load request, and the first terminal PSF execution terminate request.

In one or more possible implementations, the third request is first task execution results save request; and execute the third request, comprises: saving first task execution results of the first task after completing the first task.

In one or more possible implementations, the third request is first task execution results release request; and execute the third request, comprises: releasing first task execution results of the first task.

In one or more possible implementations, the third request is first task execution results forward suspending request; and execute the third request, comprises: suspending forwarding first task execution results of the first task after completing the first task.

In one or more possible implementations, the third request is first task execution results forwarding request, and execute the third request, comprises: forwarding first task execution results of the first task after completing the first task.

In one or more possible implementations, the third request is first task execution results load request; and execute the third request, comprises: loading first task execution results of the first task after completing the first task.

In one or more possible implementations, the third request is first terminal processing service function execution terminate request, and execute the third request, comprises: terminating first terminal processing service function execution and releasing first terminal processing service function resource.

In the fourth aspect, described may include a method, comprising: receiving a first request, by a first apparatus, from mission customer in a communication system, or generate the first request based on task execution performance information from a plurality of task control functions in the communication system, wherein the communication system is used to execute a first mission, and one of the plurality of task control functions is used to manage execution of at least one task of the first mission; sending a second request, by the first apparatus, to a first task control function in the plurality of task control functions, wherein the first task control function is used to manage a first task execution of the execution of at least one task, and the second request indicates the first request.

In one or more possible implementations, the method further comprising: receiving second request response, by the first apparatus, from the first task control function, wherein the second request response indicates completion of the second request and includes the first task execution identifier.

In the fifth aspect, described may include a method, comprising: receiving a second request, by a second apparatus, from mission management used to execute a first mission including at least one task in a communication system; executing the second request, by the second apparatus, wherein the second request includes a first task execution identifier of a first task execution corresponding to a first task in the at least one task; sending second request response, by the second apparatus, including the first task execution identifier to the mission management.

In one or more possible implementations, the second request is a state create request, and executing the second request comprises: saving the first task execution information.

In one or more possible implementations, the second request is a state cancel request, and executing the second request comprises: releasing the first task execution information.

In one or more possible implementations, releasing the first task execution information comprises: sending first task execution results release request to a first terminal processing service function, wherein the first task execution results release request includes the first task execution results saving location information; receiving first task execution results release request response from the first terminal processing service function, wherein the first task execution results release request response informs completion of releasing the first task execution results; releasing the first task execution parameters.

In one or more possible implementations, the second request is a pause request; and executing the second request comprises: saving the first task execution information; sending first task execution results forward suspending request to a first terminal processing service function, to inform the first terminal processing service function suspend forwarding the first task execution results.

In one or more possible implementations, the second request is a resume request; and executing the second request comprises: loading the first task execution information; sending first task execution results forwarding request to a first terminal processing service function, to inform the first terminal processing service function forward the first task execution results; releasing the first task execution information when the first task execution information save mode is pause mode.

In one or more possible implementations, the second request is a rollback request; and executing the second request comprises: loading the first task execution information.

In one or more possible implementations, the second request is a terminate request including first task execution termination conditions; and executing the second request comprises: sending a first terminal processing service function execution terminate request to a first terminal processing service function, wherein the first terminal processing service function execution terminate request includes identifier of the first terminal processing service function and terminate conditions, and the first terminal processing service function is used to perform the first task execution; receiving first terminal processing service function execution terminate request response informing completion of first terminal processing service function execution termination and first terminal processing service function resource release; releasing first task management resources including computing resources of the first task execution.

In the sixth aspect, described may include a method, comprising: accepting a third request, by a third apparatus, from a first task control function in a communication system, wherein the communication system is used to manage execution of a first mission and the first task control function is used to manage a first task corresponding to the first mission; executing the third request, by the third apparatus; sending third request response, by the third apparatus, to the first task control function.

In one or more possible implementations, the third request is first task execution results save request; and executing the third request, comprises: saving first task execution results of the first task after completing the first task.

In one or more possible implementations, the third request is first task execution results release request; and executing the third request, comprises: releasing the first task execution results of the first task.

In one or more possible implementations, the third request is first task execution results forward suspending request; and executing the third request, comprises: suspending forwarding first task execution results of the first task after completing the first task.

In one or more possible implementations, the third request is first task execution results forwarding request, and executing the third request, comprises: forwarding first task execution results of the first task after completing the first task.

In one or more possible implementations, the third request is first task execution results load request; and executing the third request, comprises: loading first task execution results of the first task after completing the first task.

In one or more possible implementations, the third request is first terminal processing service function execution terminate request, and executing the third request, comprises: terminating first terminal processing service function execution and releasing first terminal processing service function resource.

In the seventh aspect, described may include a machine-readable storage medium storing instructions, wherein when the instructions are executed by one or more processors of a machine, the instructions cause the machine to execute the method mentioned in the fourth, fifth and sixth aspects above.

The beneficial effects of the fourth aspect to the seventh aspect can be referred to that of the first aspect to the third aspect, which will not be described in detail herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a first schematic structural diagram of a communication system 100 according to some examples of the present disclosure.

FIG. 2 shows a second schematic structural diagram of a communication system 100 according to some examples of the present disclosure.

FIG. 3 shows a schematic diagram of communication between apparatus 310 and apparatus 320 in a communication system 100 according to some examples of the present disclosure.

FIG. 4 shows a schematic diagram of modules in each apparatus of a communication system 100 according to some examples of the present disclosure.

FIG. 5 shows a schematic structural diagram of a 6G communication system according to some examples of the present disclosure.

FIG. 6 shows a schematic structural diagram of system for mission execution management according to some examples of the present disclosure.

FIG. 7 shows a schematic diagram of a ME process including three ME states according to some examples of the present disclosure.

FIG. 8 shows a schematic structural diagram of a ME state changing method in ME process according to some examples of the present disclosure.

FIG. 9 shows a schematic flow diagram of a ME process management according to some examples of the present disclosure.

FIG. 10 shows a schematic flow diagram of ME state creation procedure according to some examples of the present disclosure.

FIG. 11 shows a schematic flow diagram of ME state cancel procedure according to some examples of the present disclosure.

FIG. 12 shows a schematic flow diagram of ME rollback control procedure according to some examples of the present disclosure.

FIG. 13 shows a schematic flow diagram of ME pause control procedure according to some examples of the present disclosure.

FIG. 14 shows a schematic flow diagram of ME resume control procedure according to some examples of the present disclosure.

FIG. 15 shows a schematic flow diagram of ME termination procedure according to some examples of the present disclosure.

FIG. 16 shows a schematic flow diagram of saving TE info procedure according to some examples of the present disclosure.

FIG. 17 shows a schematic flow diagram of loading saved TE info procedure according to some examples of the present disclosure.

FIG. 18 shows a schematic flow diagram of releasing saved TE info procedure according to some examples of the present disclosure.

FIG. 19 shows a schematic block diagram of an apparatus according to some examples of the present disclosure.

DETAILED DESCRIPTION

Illustrative embodiments of the present disclosure include, but are not limited to, a method, apparatus and readable storage medium for communication.

Based on above contents, the application of 5G system architecture is limited. Therefore many new trends will trigger the consideration and design of 6G/future wireless networks:

New network infrastructure capability, e.g., cloud natured/friendly infrastructures that are broadly deployed.

New (relative) matured techniques, e.g., AI large scale models, Data de-privacy, Block chain, etc. that have made significant progresses and significantly impact on the entire society and human life.

New apps and services, e.g., AI services, Data (sensing) service, Digital world service, etc. that are broadly applied in industry/business and used by individual customers.

More global/open/collaborative operation trend, i.e., a more open and more collaborative operation mode are becoming common practice in many fields.

New expectation and stricter requirements on future networks also drive rethinking and development of new generation of wireless networks. These requirements include

Privacy and trustworthiness, etc.

Simplified standardization

Rapid deployment

Etc.

All of the above drives 6G network architecture research work.

Our proposed 6G network architecture (X-centric) are

SBA (XaaS (X as a service) service) based

Cloud-native

Requirements to 6G System network architecture design:

The proposed 6G network architecture needs to support new 6G services which could be developed/deployed by 3rd parties.

The proposed 6G network architecture needs to embrace more open ecosystem to open door to technical capable 3rd parties.

The proposed 6G network architecture needs to enable better trustworthiness management.

Solutions to enable above requirements are needed.

When a device accesses an application through a communication system, e.g. the 5G system or future 6G system, the communication system connects the device to an application location, a network location where the application is located, through a data plane path. The application location correspondings to an application server hosting or running the application. When the device accesses the application, the device communicates with the application server through the data plane path. There may be more than one application location. When multiple devices access the application, the communication system may connect the multiple devices to different application locations.

This background information is provided to reveal information believed by the applicant to be of possible relevance to the present disclosure. No admission is necessarily intended, nor should be construed, that any of the preceding information constitutes prior art against the present disclosure.

In the following description, reference is made to the accompanying figures, which form part of the present disclosure, and which show, by way of illustration, specific aspects of the present disclosure or specific aspects in which the present disclosure may be used. It is understood that one aspect of the present disclosure may be used in other aspects and include structural or logical changes not depicted in the figures. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims.

To assist in understanding the present disclosure, examples of wireless communication systems and devices are described below.

Referring to FIG. 1, as an illustrative example without limitation, a simplified schematic illustration of a communication system is provided. The communication system 100 (which may be a wireless system) comprises a radio access network 120. The radio access network (RAN) 120 may be a next generation (e.g. sixth generation (6G) or later) radio access network, or a legacy (e.g. 5G, 4G, 3G or 2nd generation (2G) ) radio access network. One or more communication electronic device (ED) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (generically referred to as 110) may be interconnected to one another or connected to one or more network nodes (170a, 170b, generically referred to as 170) in the radio access network 120. A core network 130 may be a part of the communication system and may be dependent or independent of the radio access technology used in the communication system 100. The communication system 100 may also comprise a public switched telephone network (PSTN) 140, the internet 150, and other networks 160.

In general, the communication system 100 enables multiple wireless or wired elements to communicate data and other content. The communication system 100 may provide content, such as voice, data, video, and/or text, via broadcast, multicast, groupcast, unicast, etc. And the communication system 100 may provide a wide range of communication services and applications (such as earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery and mobility, etc. ) The services and/or applications may be mobile broadband (MBB) services, ultra-reliable low-latency communication (URLLC) services, or machine type communication (MTC) services.

The communication system 100 may operate by sharing resources, such as carrier spectrum bandwidth, between its constituent elements.

FIG. 2 illustrates more detailed example for communication system 100.

The communication system 100 may include a terrestrial communication system and/or a non-terrestrial communication system. The communication system 100 may provide a high degree of availability and robustness through a joint operation of a terrestrial communication system and a non-terrestrial communication system. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can result in what may be considered a heterogeneous network comprising multiple layers. The heterogeneous network may achieve better overall performance through efficient multi-link joint operation, more flexible functionality sharing, and faster physical layer link switching between terrestrial networks and non-terrestrial networks.

The terrestrial communication system and the non-terrestrial communication system could be considered sub-systems of the communication system.

Same as in the example shown in FIG. 1, in the example shown in FIG. 2, the communication system 100 may include ED 110a, 110b, 110c, 110d (generically referred to as ED 110) , and RAN 120a, 120b. In addition, the communication system 100 may also include a non-terrestrial communication network 120c. The communication system 100 may also include one or more of a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. The RANs 120a, 120b include respective RAN nodes such as base stations (BSs) 170a, 170b, which may be generically referred to as terrestrial transmit and receive points (T-TRPs) 170a, 170b. In one implementation, the non-terrestrial communication network 120c includes a RAN node such as an access node (or base station) 172, which may be generically referred to as a non-terrestrial transmit and receive point (NT-TRP) 172. As may be surmised on the basis of similarity in reference numerals, the non-terrestrial communication network 120c may be considered to be a radio access network, with operational aspects in common with the RANs 120a, 120b. In another implementations, the non-terrestrial communication network 120c may include at least one non-terrestrial network (NTN) device and at least one corresponding terrestrial network device, wherein the at least one non-terrestrial network device works as a transport layer device and the at least one corresponding terrestrial network device works as a RAN node, which communicates with the ED via the non-terrestrial network device. In addition, there may be a NTN gateway in the ground (i.e., referred as a terrestrial network device) also as a transport layer device to communication with both the NTN device, and the RAN node communicates with the ED via the NTN device and the NTN gateway. In some implementations, the NTN gateway and the RAN node may be located in the same device.

Any ED 110 may be alternatively or additionally configured to interface, access, or communicate with any T-TRP 170a, 170b and NT-TRP 172, the Internet 150, the core network 130, the PSTN 140, the other networks 160, or any combination of the preceding. In some examples, ED 110a may communicate an uplink (UL) and/or downlink (DL) transmission over a terrestrial air interface 190a with T-TRP 170a. In some examples, the EDs 110a, 110b, 110c, and 110d may also communicate directly with one another via one or more sidelink (SL) air interfaces 190b. In some examples, ED 110d may communicate an uplink and/or downlink transmission over a non-terrestrial air interface 190c with NT-TRP 172.

An air interface (e.g., 190a, 190b, 190c) generally includes a number of components and associated parameters that collectively specify how a transmission is to be sent and/or received over a wireless communications link between two or more communicating devices. For example, an air interface may include one or more components defining the waveform (s) , frame structure (s) , multiple access scheme (s) , protocol (s) , coding scheme (s) and/or modulation scheme (s) for conveying information (e.g., data) over a wireless communications link. The wireless communications link may support a link (e.g., a “Uu” link) between a radio access network (e.g., RAN 120) and user equipment (e.g., ED 110) and/or the wireless communications link may support a link (e.g., a “LS” ) between device (e.g., ED 110a) and device (e.g., ED 110b) , such as between two user equipments, and/or the wireless communications link may support a link between a non-terrestrial (NT) -communication network (e.g, RAN 120c) and user equipment (e.g., ED 110d) . The following are some examples for the above components.

A waveform component may specify a shape and form of a signal being transmitted. Waveform options may include orthogonal multiple access waveforms and non-orthogonal multiple access waveforms. Non-limiting examples of such waveform options include orthogonal frequency division multiplexing (OFDM) , discrete Fourier transform spread OFDM (DFT-OFDM) , filtered OFDM (f-OFDM) , time windowing OFDM, filter bank multicarrier (FBMC) , universal filtered multicarrier (UFMC) , generalized frequency division multiplexing (GFDM) , wavelet packet modulation (WPM) , faster than Nyquist (FTN) waveform and low peak to average power ratio waveform (low peak-to-average power ratio (PAPR) WF) .

A frame structure component may specify a configuration of a frame or group of frames. The frame structure component may indicate one or more of a time, frequency, pilot signature, code, subcarrier spacing, cyclic prefix length or other parameter of the frame or group of frames. More details of frame structure will be discussed hereinafter.

A multiple access scheme component may specify multiple access technique options, including technologies defining how communicating devices share a common physical channel, such as: code division multiple access (CDMA) , space division multiple access (SDMA) , time division multiple access (TDMA) , frequency division multiple access (FDMA) , orthogonal FDMA (OFDMA) , single-carrier FDMA (SC-FDMA) which is also known as discrete Fourier transform spread OFDMA (DFT-s-OFDMA) , low density signature multicarrier CDMA (LDS-MC-CDMA) ; non-orthogonal multiple access (NOMA) ; pattern division multiple access (PDMA) ; lattice partition multiple access (LPMA) ; resource spread multiple access (RSMA) ; and sparse code multiple access (SCMA) . Furthermore, multiple access technique options may include: scheduled access vs. non-scheduled access, also known as grant-free access; non-orthogonal multiple access vs. orthogonal multiple access, e.g., via a dedicated channel resource (e.g., no sharing between multiple communicating devices) ; contention-based shared channel resources vs. non-contention-based shared channel resources; and cognitive radio-based access. The air interfaces 190a and 190b may utilize other higher dimension signal spaces, which may involve a combination of orthogonal and/or non-orthogonal dimensions.

A coding and modulation component may specify how information being transmitted may be encoded/decoded and modulated/demodulated for transmission/reception purposes. Coding may refer to methods of error detection and forward error correction. Non-limiting examples of coding options include turbo trellis codes, turbo product codes, fountain codes, low-density parity check codes and polar codes. Modulation may refer, simply, to the constellation (including, for example, the modulation technique and order) , or more specifically to various types of advanced modulation methods such as hierarchical modulation and low PAPR modulation.

The air interfaces 190a and 190b may use similar communication technology, such as any suitable radio access technology.

The non-terrestrial air interface 190c can enable communication between the ED 110d and one or multiple NT-TRPs 172 via a wireless link or simply a link. For some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of EDs 110 and one or multiple NT-TRPs 172 for multicast transmission.

The RANs 120a and 120b are in communication with the core network 130 to provide the EDs 110a 110b, and 110c with various services such as voice, data, and other services. The RANs 120a and 120b and/or the core network 130 may be in direct or indirect communication with one or more other RANs (not shown) , which may or may not be directly served by core network 130, and may or may not employ the same radio access technology as RAN 120a, RAN 120b or both. The core network 130 may also serve as a gateway access between (i) the RANs 120a and 120b or EDs 110a 110b, and 110c or both, and (ii) other networks (such as the PSTN 140, the Internet 150, and the other networks 160) . In addition, some or all of the EDs 110a 110b, and 110c may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies and/or protocols. Instead of wireless communication (or in addition thereto) , the EDs 110a 110b, and 110c may communicate via wired communication channels to a service provider or switch (not shown) , and to the Internet 150. PSTN 140 may include circuit switched telephone networks for providing plain old telephone service (POTS) . Internet 150 may include a network of computers and subnets (intranets) or both, and incorporate protocols, such as internet protocol (IP) , transmission control protocol (TCP) , user datagram protocol (UDP) . EDs 110a 110b, and 110c may be multimode devices capable of operation according to multiple radio access technologies, and incorporate multiple transceivers necessary to support such.

In addition, the communication system 100 may comprising a sensing agent (not shown in the figure) to manage the sensed data from ED110 and or the T-TRP 170 and/or NT-TRP 172. In one implementation, the sensing agent is located in the T-TRP 170 and/or NT-TRP 172. In another implementation, the sensing agent is a separate node which has interface to communicate with the core network 130 and/or the RAN 120 (e.g., the T-TRP 170 and/or NT-TRP 172) .

FIG. 3 illustrates example of an Apparatus 310 wirelessly communicating with at least one of two apparatuses (e.g., Apparatus 320a and Apparatus 320b, referred as Apparatus 320) in a communication system, e.g., the communication system 100, according to one embodiment. The Apparatus 310 may be a UE (e.g., ED 110 in FIG. 3) . The Apparatus 320a may be a terrestrial network device (e.g., T-TRP 170 as shown in FIG. 3) , and Apparatus 320b may be a non-terrestrial network device (e.g., NT-TRP 172 as shown in FIG. 3) . However, this is not necessary. For example, Apparatus 320a may be a NT-TRP, and 320b may be a T-TRP, both Apparatus 320a and 320b may be T-TRPs or NT-TRPs, according to present disclosure. In the following, the ED 110 as an example of the Apparatus 310 is described, and T-TRP 170 as an example of Apparatus 320a is described, and NT-TRP 172 as an example of Apparatus 320a is described. Although only one Apparatus 310, one Apparatus 320a and one Apparatus 320b Please note that the number of Apparatus 310 (e.g. ED 110) could be one or more, and the number of Apparatus 320a and/or 320b could be one or more. For example, one ED110 may be served by only one T-TRP 170 (or one NT-TRP172) , by more than one T-TRP 170, by more than one NT-TRP 172, or by one or more T-TRP 170 and one or more NT-TRP172.

The ED 110 is used to connect persons, objects, machines, etc. The ED 110 may be widely used in various scenarios including, for example, cellular communications, device-to-device (D2D) , vehicle to everything (V2X) , peer-to-peer (P2P) , machine-to-machine (M2M) , MTC, internet of things (IoT) , virtual reality (VR) , augmented reality (AR) , mixed reality (MR) , metaverse, digital twin, industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, etc.

Each ED 110 represents any suitable end user device for wireless operation and may include such devices (or may be referred to but not limited to) as a user equipment/device (UE) , a wireless transmit/receive unit (WTRU) , a mobile station, a fixed or mobile subscriber unit, a cellular telephone, a station (STA) , a MTC device, a personal digital assistant (PDA) , a smartphone, a laptop, a computer, a tablet, a wireless sensor, a consumer electronics device, a smart book, a vehicle, a car, a truck, a bus, a train, or an IoT device, wearable devices (such as a watch, a pair of glasses, head mounted equipment, etc. ) , an industrial device, or an apparatus in (e.g. communication module, modem, or chip) or comprising the forgoing devices, among other possibilities. Future generation EDs 110 may be referred to using other terms. The base station 170a and 170b is a T-TRP and will hereafter be referred to as T-TRP 170. Also shown in FIG. 3, a non-terrestrial (NT) device will hereafter be referred to as NT-TRP 172. Each ED 110 connected to T-TRP 170 and/or NT-TRP 172 can be dynamically or semi-statically turned-on (i.e., established, activated, or enabled) , turned-off (i.e., released, deactivated, or disabled) and/or configured in response to one of more of: connection availability and connection necessity.

As shown in FIG. 3, the ED 110 include at least one processor 210. Only one processor 210 is illustrated to avoid congestion in the drawing. The ED 110 may further include a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas 204 may alternatively be panels. The transmitter 201 and the receiver 203 may be integrated, e.g. as a transceiver. The transceiver is configured to modulate data or other content for transmission by at least one antenna 204 or network interface controller (NIC) . The transceiver is also configured to demodulate data or other content received by the at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and/or processing signals received wirelessly or by wire. Each antenna 204 includes any suitable structure for transmitting and/or receiving wireless or wired signals. The ED 110 may include at least one memory 208. Only the transmitter 201, receiver 203, processor 210, memory 208, and antenna 204 is illustrated for simplicity, but the ED 110 may include one or more other components.

The memory 208 stores instructions. The memory 208 may also stores data used, generated, or collected by the ED 110. For example, the memory 208 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by one or more processing unit (s) (e.g., a processor 210) . Each memory 208 includes any suitable volatile and/or non-volatile storage and retrieval device (s) . Any suitable type of memory may be used, such as random access memory (RAM) , read only memory (ROM) , hard disk, optical disc, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, on-processor cache, and the like.

The ED 110 may further include one or more input/output devices (not shown) or interfaces (such as a wired interface to the Internet 150 in FIG. 1) . The input/output devices or interfaces permit interaction with a user or other devices in the network. Each input/output device or interface includes any suitable structure for providing information to or receiving information from a user, and/or for network interface communications. Suitable structures include, for example, a speaker, microphone, keypad, keyboard, display, touch screen, etc.

The processor 210 performs (or controlling the ED110 to perform) operations described herein as being performed by the ED110. As illustrated below and elsewhere in the present disclosure. For example, the processor 210 performs or controls the ED110 to perform receiving transport blocks (TBs) , using a resource for decoding of one of the received TBs, releasing the resource for decoding of another of the received TBs, and/or receiving configuration information configuring a resource. In details, the operation may include those operations related to preparing a transmission for uplink transmission to the NT-TRP 172 and/or the T-TRP 170; those operations related to processing downlink transmissions received from the NT-TRP 172 and/or the T-TRP 170; and those operations related to processing sidelink transmission to and from another ED 110. Processing operations related to preparing a transmission for uplink transmission may include operations such as encoding, modulating, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulating and decoding received symbols. Processing operations related to processing sidelink transmissions may include operations such as transmit/receive beamforming, modulating/demodulating and encoding/decoding symbols. Depending upon the embodiment, a downlink transmission may be received by the receiver 203, possibly using receive beamforming, and the processor 210 may extract signaling from the downlink transmission (e.g. by detecting and/or decoding the signaling) . An example of signaling may be a reference signal transmitted by the NT-TRP 172 and/or by the T-TRP 170. In some embodiments, the processor 210 implements the transmit beamforming and/or the receive beamforming based on the indication of beam direction, e.g. beam angle information (BAI) , received from the T-TRP 170. In some embodiments, the processor 210 may perform operations relating to network access (e.g. initial access) and/or downlink synchronization, such as operations relating to detecting a synchronization sequence, decoding and obtaining the system information, etc. In some embodiments, the processor 210 may perform channel estimation, e.g. using a reference signal received from the NT-TRP 172 and/or from the T-TRP 170.

Although not illustrated, the processor 210 may form part of the transmitter 201 and/or part of the receiver 203. Although not illustrated, the memory 208 may form part of the processor 210.

The processor 210, the processing components of the transmitter 201, and the processing components of the receiver 203 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory (e.g. in the memory 208) . Alternatively, some or all of the processor 210, the processing components of the transmitter 201, and the processing components of the receiver 203 may each be implemented using dedicated circuitry, such as a programmed field-programmable gate array (FPGA) , an application-specific integrated circuit (ASIC) , or a hardware accelerator such as a graphics processing unit (GPU) or an artificial intelligence (AI) accelerator.

In some implementations, the ED 110 may be an apparatus (also called component) for example, communication module, modem, chip, or chipset, it includes at least one processor 210, and an interface or at least one pin. In this scenario, the transmitter 201 and receiver 203 may be replaced by the interface or at least one pin, wherein the interface or at least one pin is to connect the apparatus (e.g., chip) and other apparatus (e.g., chip, memory, or bus) . Accordingly, the transmitting information to the NT-TRP 172 and/or the T-TRP 170 and/or another ED 110 may be referred as transmitting information to the interface or at least one pin, or as transmitting information to the NT-TRP 172 and/or the T-TRP 170 and/or another ED 110 via the interface or at least one pin, and receiving information from the NT-TRP 172 and/or the T-TRP 170 and/or another ED 110 may be referred as receiving information from the interface or at least one pin, or as receiving information from the NT-TRP 172 and/or the T-TRP 170 and/or another ED 110 via the interface or at least one pin. The information may include control signaling and/or data. For other nodes/entities in this disclosure, similar rule applies.

As shown in FIG. 3, the T-TRP 170 include at least one processor 260. Only one processor 260 is illustrated to avoid congestion in the drawing. The T-TRP 170 may further include at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas 256 may alternatively be panels. The transmitter 252 and the receiver 254 may be integrated as a transceiver. The T- TRP 170 may further include at least one memory 258. The T-TRP 170 may further include scheduler 253. Only the transmitter 252, receiver 254, processor 260, memory 258, antenna 256 and scheduler 253 are illustrated for simplicity, but the T-TRP may include one or more other components.

The T-TRP 170 may be known by other names in some implementations, such as a base station, a base transceiver station (BTS) , a radio base station, a network node, a network device, a device on the network side, a transmit/receive node, a Node B, an evolved NodeB (eNodeB or eNB) , a Home eNodeB, a next Generation NodeB (gNB) , a transmission point (TP) , a site controller, an access point (AP) , a wireless router, a relay station, a terrestrial node, a terrestrial network device, a terrestrial base station, a base band unit (BBU) , a remote radio unit (RRU) , an active antenna unit (AAU) , a remote radio head (RRH) , a central unit (CU) , a distributed unit (DU) , a positioning node, among other possibilities. The T-TRP 170 may be a macro base station (BS) , a pico BS, a relay node, a donor node, or the like, or combinations thereof. The T-TRP 170 may refer to the forgoing devices or refer to apparatus (e.g. a communication module, a modem, or a chip) in the forgoing devices.

In some embodiments, the parts of the T-TRP 170 may be distributed. For example, some of the modules of the T-TRP 170 may be located remote from the equipment that houses the antennas 256 for the T-TRP 170, and may be coupled to the equipment that houses the antennas 256 over a communication link (not shown) sometimes known as front haul, such as common public radio interface (CPRI) . Therefore, in some embodiments, the term T-TRP 170 may also refer to modules on the network side that perform processing operations, such as determining the location of the ED 110, resource allocation (scheduling) , message generation, and encoding/decoding, and that are not necessarily part of the equipment that houses the antennas 256 of the T-TRP 170. The modules may also be coupled to other T-TRPs. In some embodiments, the T-TRP 170 may actually be a plurality of T-TRPs that are operating together to serve the ED 110, e.g. through the use of coordinated multipoint transmissions.

The processor 260 performs operations including those related to: preparing a transmission for downlink transmission to the ED 110, processing an uplink transmission received from the ED 110, preparing a transmission for backhaul transmission to the T-TRP 170 and/or NT-TRP 172, and processing a transmission received over backhaul from the T-TRP 170 and/or NT-TRP 172. Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulating, precoding (e.g. multiple input multiple output (MIMO) precoding) , transmit beamforming, and generating symbols for transmission. Processing operations related to processing received transmissions in the uplink or over backhaul may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols. The processor 260 may also perform operations relating to network access (e.g. initial access) and/or downlink synchronization, such as generating the content of synchronization signal blocks (SSBs) , generating the system information, etc. In some embodiments, the processor 260 also generates an indication of beam direction, e.g. BAI, which may be scheduled for transmission by a scheduler 253. The processor 260 performs other network-side processing operations described herein, such as determining the location of the ED 110, determining where to deploy the NT-TRP 172, etc. In some embodiments, the processor 260 may generate signaling, e.g. to configure one or more parameters of the ED 110 and/or one or more parameters of the NT-TRP 172. Any signaling generated by the processor 260 is sent by the transmitter 252.

The scheduler 253 may be coupled to the processor 260 or integrated in the processor 260. The scheduler 253 may be included within or operated separately from the T-TRP 170. The scheduler 253 may schedule uplink, downlink, sidelink, and/or backhaul transmissions, including issuing scheduling grants and/or configuring scheduling-free (e.g., “configured grant” ) resources.

The memory 258 is configured to store information, and optionally data. The memory 258 stores instructions and data used, generated, or collected by the T-TRP 170. For example, the memory 258 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by the processor 260.

Although not illustrated, the processor 260 may form part of the transmitter 252 and/or part of the receiver 254. Also, although not illustrated, the processor 260 may implement the scheduler 253. Although not illustrated, the memory 258 may form part of the processor 260.

The processor 260, the scheduler 253, the processing components of the transmitter 252, and the processing components of the receiver 254 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory, e.g. in the memory 258. Alternatively, some or all of the processor 260, the scheduler 253, the processing components of the transmitter 252, and the processing components of the receiver 254 may be implemented using dedicated circuitry, such as a programmed FPGA, a hardware accelerator (e.g., a GPU or AI accelerator) , or an ASIC.

When the T-TRP 170 is an apparatus (also called as component) , for example, communication module, modem, chip, or chipset in a device, it includes at least one processor, and an interface or at least one pin. In this scenario, the transmitter 252 and receiver 254 may be replaced by the interface or at least one pin, wherein the interface or at least one pin is to connect the apparatus (e.g., chip) and other apparatus (e.g., chip, memory, or bus) . Accordingly, the transmitting information to the NT-TRP 172 and/or the T-TRP 170 and/or ED 110 may be referred as transmitting information to the interface or at least one pin, and receiving information from the NT-TRP 172 and/or the T-TRP 170 and/or ED 110 may be referred as receiving information from the interface or at least one pin. The information may include control signaling and/or data.

Although the NT-TRP 172 is illustrated as a drone only as an example, the NT-TRP 172 may be implemented in any suitable non-terrestrial form, such as satellites and high altitude platforms, including international mobile telecommunication base stations and unmanned aerial vehicles, for example. Also, the NT-TRP 172 may be known by other names in some implementations, such as a non-terrestrial node, a non-terrestrial network device, or a non-terrestrial base station.

As shown in FIG. 3, The T-TRP 170 may further include at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas 256 may alternatively be panels. The transmitter 252 and the receiver 254 may be integrated as a transceiver. The T-TRP 170 may further include at least one memory 258. The T-TRP 170 may further include scheduler 253. Only the transmitter 252, receiver 254, processor 260, memory 258, antenna 256 and scheduler 253 are illustrated for simplicity, but the T-TRP may include one or more other components.

As shown in FIG. 3, the NT-TRP 172 include at least one processor 276. Only one processor 276 is illustrated to avoid congestion in the drawing. The NT-TRP 172 may include a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas may alternatively be panels. The transmitter 272 and the receiver 274 may be integrated as a transceiver. The NT-TRP 172 may further include at least one memory 278. The NT-TRP 172 may further include scheduler. Only the transmitter 272, receiver 274, processor 276, memory 278, antenna 280 are illustrated for simplicity, but the NT-TRP may include one or more other components.

The NT-TRP 172 include a processor 276 for performing operations including those related to: preparing a transmission for downlink transmission to the ED 110, processing an uplink transmission received from the ED 110, preparing a transmission for backhaul transmission to T-TRP 170 and/or another NT-TRP 172, and processing a transmission received over backhaul from the T-TRP 170 and/or another NT-TRP 172. Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulating, precoding (e.g. MIMO precoding) , transmit beamforming, and generating symbols for transmission. Processing operations related to processing received transmissions in the uplink or over backhaul may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols. In some embodiments, the processor 276 implements the transmit beamforming and/or receive beamforming based on beam direction information (e.g. BAI) received from the T-TRP 170. In some embodiments, the processor 276 may generate signaling, e.g. to configure one or more parameters of the ED 110. In some embodiments, the NT-TRP 172 implements physical layer processing, but does not implement higher layer functions such as functions at the medium access control (MAC) or radio link control (RLC) layer. As this is only an example, more generally, the NT-TRP 172 may implement higher layer functions in addition to physical layer processing.

The memory 278 is configured to store information and optionally data. The memory 258 stores instructions and data used, generated, or collected by the NT-TRP 172. For example, the memory 278 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by the processor 276.

Although not illustrated, the processor 276 may form part of the transmitter 272 and/or part of the receiver 274. Although not illustrated, the memory 278 may form part of the processor 276.

The processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory, e.g. in the memory 278. Alternatively, some or all of the processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 may be implemented using dedicated circuitry, such as a programmed FPGA, a hardware accelerator (e.g., a GPU or AI accelerator) , or an ASIC. In some embodiments, the NT-TRP 172 may actually be a plurality of NT-TRPs that are operating together to serve the ED 110, e.g. through coordinated multipoint transmissions.

When the NT-TRP 172 is an apparatus (e.g. communication module, modem, chip, or chipset) in a device, it includes at least one processor, and an interface or at least one pin. In this scenario, the transmitter 272 and receiver 257 may be replaced by the interface or at least one pin, wherein the interface or at least one pin is to connect the apparatus (e.g., chip) and other apparatus (e.g., chip, memory, or bus) . Accordingly, the transmitting information to the T-TRP 170 and/or another NT-TRP 172 and/or ED 110 may be referred as transmitting information to the interface or at least one pin, and receiving information from the T-TRP 170 and/or another NT-TRP 172 and/or ED 110 may be referred as receiving information from the interface or at least one pin. The information may include control signaling and/or data.

Note that “TRP” , as used herein, may refer to a T-TRP or a NT-TRP. A T-TRP may alternatively be called a terrestrial network TRP ( “TN TRP” ) and a NT-TRP may alternatively be called a non-terrestrial network TRP ( “NTN TRP” ) . The T-TRP 170, the NT-TRP 172, and/or the ED 110 may include other components, but these have been omitted for the sake of clarity.

Note that “signaling” , as used herein, may alternatively be called control signaling, control message, control information, or message for simplicity. Signaling between a BS (e.g., the network node 170) and a terminal or sensing device (e.g., ED 110) , or signaling between different terminal or sensing device (e.g., between ED 110i and ED110j) may be carried in physical layer signaling (also called as dynamic signaling) , which is transmitted in a physical layer control channel. For downlink the physical layer signaling may be known as downlink control information (DCI) which is transmitted in a physical downlink control channel (PDCCH) . For uplink, the physical layer signaling may be known as uplink control information (UCI) which is transmitted in a physical uplink control channel (PUCCH) . For sidelink, signaling between different terminal or sensing device (e.g., between ED 110i and ED110j) may be known as sidelink control information (SCI) which is transmitted in a physical sidelink control channel (PSCCH) . Signaling may be carried in a higher-layer (e.g., higher than physical layer) signaling, which is transmitted in a physical layer data channel, e.g. in a physical downlink shared channel (PDSCH) for downlink signaling, in a physical uplink shared channel (PUSCH) for uplink signaling, and in a physical sidelink shared channel (PSSCH) for sidelink signaling. Higher-layer signaling may also called static signaling, or semi-static signaling. Higher-layer signaling may be radio resource control (RRC) protocol signaling or media access control –control element (MAC-CE) signaling. Signaling may be included in a combination of physical layer signaling and higher layer signaling.

It should be noted that in present disclosure, “information” , when different from “message” , may be carried in one single message, or be carried in more than one separate message.

One or more steps of the methods provided in this disclosure herein may be performed by corresponding units or modules, according to FIG. 4. FIG. 4 illustrates units or modules in a device or apparatus, such as in the ED 110, in the T-TRP 170, or in the NT-TRP 172. For example, a signal may be transmitted by a transmitting unit or by a transmitting module. A signal may be received by a receiving unit or by a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by an artificial intelligence (AI) or machine learning (ML) module. The respective units or modules may be implemented using hardware, one or more components or devices that execute software, or a combination thereof. For instance, one or more of the units or modules may be a circuit such as an integrated circuit. Examples of an integrated circuit includes a programmed FPGA, a GPU, or an ASIC. For instance, one or more of the units or modules may be logical such as a logical function performed by a circuit, by a portion of an integrated circuit, or by software instructions executed by a processor. It will be appreciated that where the modules are implemented using software for execution by a processor for example, the modules may be retrieved by a processor, in whole or part as needed, individually or together for processing, in single or multiple instances, and that the modules themselves may include instructions for further deployment and instantiation. For other nodes/entities in this disclosure, similar units or modules applies.

Additional details regarding the EDs 110, the T-TRP 170, and the NT-TRP 172 are known to those of skill in the art. As such, these details are omitted here.

The proposed 6G System architecture is defined to support 6G XaaS services by using techniques such as Network Function Virtualization and Network Slicing. The 6G System architecture utilizes service-based interactions between 6G services.

The 6G System leverages service-based architecture and XaaS concept. XaaS services in the 6G System are categorized into three layers. The 6G System conceptual structure is shown in FIG. 5.

Infrastructure Layer includes infrastructures supporting 6G services. Among them are wireless networks (RAN, CN) infrastructures, Cloud/data center infrastructures, satellite networks, storage/database infrastructures, and sensing networks, and etc. These infrastructures can be provided by a single provider or by multiple providers.

Each of the infrastructures could have its control and management functions, denoted as C/M functions, for infrastructure management. Each of these infrastructures is one type of Infrastructure as a Service.

Control and Management (C/M) layer includes control and management services of the 6G System. They are developed and deployed by using slicing techniques and utilizing resource provided by infrastructure layer. 6G services in Control and Management (C/M) layer are:

Resource Management (RM) as a Service provides a capability of life-cycle management of a variety of slices and over-the-air resource assignment to wireless devices.

A 6G mission is defined as a service provided to customers by the 6G System. A mission can be a type of services which is provided by a single 6G XaaS service or a type of services that needs contributions from multiple XaaS services.

Mission Management (MM) as a Service provides a capability to program provisioning of XaaS services at Service Layer to provide mission services.

Confederation Network (CONET) as a Service provides a capability to enable multiple partners jointly provide 6G services. This capability is provided by confederation formation, mutual authentication, mutual authorization among partners and negotiation of agreement on recording and retracing of selected actions performed by partners, in order to assure a trustworthy environment of 6G System operations.

Service Provisioning Management (SPM) as a Service provides a capability of control and management of 6G service access by customers and provisioning of requested services. The capability is provided by unified mutual authentication, authorization and policy, key management, QoS assurance and charging between any pair of XaaS service provider and customer. The customers include end-customers not only in physical world, but also digital representatives in digital world.

Connectivity Management (CM) as a Service leverages 5G connectivity management functions, but with extension to include digital world.

Protocol as a Service provides a capability to design service customized protocol stacks for identified interfaces.

The protocol stacks could be pre-defined for on-demand selection, or could be on-demand designed.

Network Security as a Service provides a capability for owners of infrastructures to detect potential security risks of their infrastructures.

XaaS services in C/M Layer support control and management of the 6G System itself and also provide support to verticals if requested. One example is that RM service can serve RAN for over-the-air resource management and can also provide service to a vertical for the vertical’s over-the-air resource allocation to its end-customers. The XaaS in C/M layer can be deployed by using slicing technique.

Service Layer includes 6G services which provide services to customers. In the 6G System conceptual structure:

AI service is denoted as NET4AI as a Service. Artificial Intelligence service provides AI capability to support a variety of AI applications.

Service of data collection, data sanitization, data analysis and data delivery are denoted as data analytics and management (DAM) as a Service, this service provides a capability of lifecycle management of statistic data, including acquisition, de-privatization, analysis and delivery of data which are information statistic data from any types of sensors, devices, network functions, and etc.

Service of storage and sharing of data is denoted as NET4Data as a Service, this service provides a capability to trustworthily storage and share data under the control of owners of data and following recognized authorities’ regulations on control of identified data.

Service to provide digital world is denoted as NET4DW as a Service, Digital World service provides a capability to construct, control and manage digital world. Digital world is defined as digital realization of physical world.

6G block chain service is denoted as NET4BC as a Service. 6G connectivity service is denoted as NET4Con as a Service. This service provides a capability to support 6G block chain services.

Enhanced connectivity service, e.g., network for connectivity (NET4CON) as a service. This service provides a capability to support exchange of messages and data among new 6G services.

All XaaS services at this Layer are developed and deployed by using resource provided in infrastructure and utilizing Network Function Virtualization and Slicing techniques. The capability of each of 6G services is provided by its control and management functions and service specific data process functions.

In addition to support 6G XaaS services at Service Layer, 6G System leverages 5G System for provisioning of vertical services. The difference between 6G XaaS services and other verticals are that a vertical is a pure customer which needs other XaaS services to enable its operation, while each of XaaS services provide their capabilities to 6G customers.

Any pair of XaaS services of the 6G System could also be mutual customer and provider of each other. Some of example are that an infrastructure owner provides its resource to XaaS services in Service Layer and C/M Layer; RM services may need the capabilities provided by NET4AI, DAM and NET4DW for its resource management for vertical slicing; CONET service and NET4Data service may need the capability provided by NET4BC for their operation.

The key concepts of 6G System includes:

Define Basic XaaS Services by decoupling comprehensive types of services into basic XaaS services. A basic XaaS service provides unique capability to enable a specific type of service, such as NET4AI service, NET4DW service, DAM service, NET4Data service, Block chain service, mission management service, etc.

Allow joint operation of the 6G System by multiple partners.

Define Data Plane of the 6G System which includes processing functions of data plane of XaaS services. Programing the interconnection of these functions, by mission management service, enables to support a variety of customized customer services.

Simplify 6G System architecture by categorizing basic control services and management services and combining them as basic XaaS services in Control and Management (C/M) Layer.

Define C/M Plane of the 6G System which includes C/M functions in XaaS services and may include 5G control plane (CP) (e.g., AMF) depending on implementation options.

Define Basic Architecture Structure (BAS) which is a unified basic structure with minimized number of interfaces and is independent of types of infrastructures.

Simplify standardization, development and deployment of the 6G System using the BAS concept, while supporting a variety of infrastructure deployment scenarios.

Adapt to a variety of deployment scenarios by applying the BAS or a subset of it to infrastructures based on capability, capacity and requirement of the infrastructure networks.

Leverage SBI interface concept and apply SBI interaction in both 6G C/M plane and 6G data plane.

Simplify service based Interface (SBI) interfaces by introducing trustworthy GWs in Data Plane and C/M Plane of the 6G System.

Improve trustworthiness from perspectives of operation of the 6G System by introducing CONET capability, NET4BC capability and anonymous service provisioning provided by the trustworthy GWs in the C/M plane and data plane of the 6G System.

Improve trustworthiness from perspective of end customer privacy protection by unified mutual authentication, ID management (IDM) , data sanitization and etc. provided by SPM service, DAM service and 6G Block Chain service.

Simplify roaming management of wireless devices, in physical world and digital world, by unified authentication including all participated partners and customers.

Support multiple development paths from 5G System to 6G System by defining multiple architecture options without incurring much efforts due to the introduction of the BAS concept.

Support backward compatibility by utilizing benefits of SBA and its add-on feature. 5G users can use the 6G System to access 5G services.

Support future extension by adding new XaaS services with minimized impact on standardization and deployment, due to the introduced anonymous service provisioning concept implemented in trustworthy GWs in 6G C/M plane and in 6G data plane.

The system performs ME (mission execution) management provided in this disclosure using an architecture illustrated in FIG. 6. The architecture includes a number of network functions: mission customer, MM (mission management) , TCF (task control function) , and PSF (processing service function) . Please note that the apparatus, units and modules shown in FIG. 3 and FIG. 4 may also applied for MM, TCF, and PSF.

Each function involved in FIG. 6 will be described in the following contents.

Mission customer (MC) : An authorized network entity, e.g. an application function (AF) , a device, or a network function, can send a request to the MM to request a ME. The authorized network entity is referred to as mission customer (MC) .

Mission management (MM) : The MM includes control/management plane (CP) functions to manage/coordinate one or multiple ME (s) . The MM controls and coordinates an ME over an instance of the mission, including starting, pausing, resuming, stopping, terminating the ME. The MM starts, pauses, resumes, stops or terminates the ME according to a request (e.g. from a MC) or upon certain event (e.g. a time event) . The MM is responsible for establishing data plane paths among CB instance (s) within the mission instance and between mission participants (e.g. UEs) and the CB instance (s) for the mission execution. When coordinating the mission execution, the MM triggers execution (s) of the CB (s) of the mission at right time and coordinates access of mission participants, e.g. devices, to the mission execution. The MM may control the mission execution with respect to relevant MM polices, which can be pre-configured at the MM or obtained by the MM from another control plane entity. Mission context related to the ME is maintained in the CP and in the DP before the ME is terminated.

Task control function (TCF) : The TCF controls and coordinates a TE, including starting, stopping, and terminating the TE. The TCF starts, stops or terminates the TE as part of a ME according to request (s) from the MM. The TCF is informed by the MM that a network entity, e.g. a device, is accessing/participating the TE. The TCF can accordingly invite the network entity at right time, e.g. when task resources are ready, to access/participate the TE, wherein the network entity may provide data to support the task execution or receives data related to the TE. Task context related to the TE is maintained in the CP of the service module and in the DP of the service module before the task execution is terminated.

Processing service function (PSF) : The PSF receives and processes DP traffic. The PSF may generate data plane traffic. The PSF may transmit its received data plane traffic (possibly after processing) or generated data plane traffic to other PSFs or the DN or the UE via one or multiple data plane gateways, a. k. a. data gateways (data GWs) , which are similar to UPFs (user plane functions) in the 5G system.

A mission is to achieve a designated goal, known as mission goal, which includes 1) providing protocol data unit (PDU) connectivity and optionally 2) providing data processing. When the mission goal includes providing data processing, the mission goal is associated with specific computational problem (s) , and providing data processing refers to solving the specific computational problem (s) . In this case, the mission includes one or multiple computing blocks (CBs) and is associated with a networking procedure among the CBs for solving the specific computational problem (s) . A CB within the mission corresponds to a defined computational step toward the mission goal (i.e. solving the specific computational problem (s) ) and may be supported by a service (in the form of a task) , a data network (DN) , or another mission; accordingly, the CB is referred to as a task CB, an external CB or a sub-mission CB. Mission management includes programming a mission, instantiating a mission and achieving a mission goal.

A mission slice is a logical network that provides specific capabilities and characteristics in networking and computing (including storage) for a mission. A CB within the mission corresponds to a subnet, referred to as CB subnet, of the mission slice. The CB subnet provides computing functionalities of achieving the corresponding computational step toward the mission goal. A mission slice instance incudes a set of network function instances and the required resources (e.g. computing, storage, and networking resources) and computing logic (e.g. in terms of parameter configuration) which form a deployed mission slice. A mission service is a service that provides achieving of a mission goal, a. k. a. executing of a mission, between a network entity (NE) , e.g. a UE or an AS, and a DN. A mission session refers to an association between an NE and a DN, providing a mission service with support from a mission slice instance.

Without ambiguity, mission and mission slice are used interchangeably for ease of presentation unless clarified; likewise, CB and CB subnet are used interchangeably. When a mission is instantiated, a mission slice instance is created for the mission. The mission slice instance is thus considered an instance of the mission. For each CB within the mission, the mission instance includes an instance of the CB. If the CB is a task CB, the CB instance is located in a XaaS service module (or, a service module for simplicity) supporting the task CB; if the CB is an external CB, the CB instance is located in the respective DN; if the CB is a sub-mission CB, the CB instance is an instance of a mission corresponding to the CB. The mission can have multiple instances. A CB instance may be shared by multiple mission instances when the CB instance is stateless. Likewise, a mission instance may be shared by (i.e. support) multiple applications when the mission instance is stateless. A mission instance is stateless if and only if the mission instance does not include stateful CB instances.

An application located in a DN can be a customer of a mission and provide an application service to its users by making use of an execution of the mission. The mission can support more than one application. A mission supports an application through a mission instance. A mission can act as an application and natively provides an application service to the application users; in this case, the application is considered located in the mission. An authorized NE uses a mission session to access the application, the mission session targeting a DN where the application is located and being supported by an instance of the mission. When the application is located in the mission, the DN is an abstract DN and corresponds to the mission. The mission instance can be used to support more than one application. Different applications may be supported by different instances of a mission.

To support an application through a mission instance as described above, a mission session must be established over the mission instance. During the establishment of the mission session, both the data plane (e.g. data plane path (s) across CB instance (s) ) and the control plane (e.g. MCF (s) and TCF (s) ) are configured for the mission session.

After the mission session establishment, data traffic related to the application can flow through the mission instance and be processed under the coordination of the MM framework, according to a networking logic (if any) associated to the mission. The process of coordinating the data flow and processing is referred to as mission execution (ME) process (or ME in short) . A ME comprises one or multiple task execution (s) (TEs) according to the networking logic (if any) associated to the mission. A TE is referred to as the execution of a CB comprising one or multiple execution (s) of data plane (DP) computing/processing function (s) according to pre-defined execution dependency and/or logic (if any) associated to the CB.

Based on above contents, the architecture in FIG. 6 will be described in detail in the following contents.

In FIG. 6, MM is used to control the execution of a mission. This embodiment does not restrict the type of mission. For example, a mission can be an image processing task, an autopilot task, etc. MM can split a mission into multiple tasks and control three TCFs to execute corresponding task by sending request to TCFs to execute the mission. As shown in FIG. 6, each TCF is used to manage at least one task execution. After receiving request from MM, each TCF controls respective PSF to execute data processing corresponding to each task. When all tasks are completed, the mission is also completed.

For example, in FIG. 6, MM controls TCF1, TCF2, and TCF3 respectively. TCF1 is used to control three PSFs in series to execute task A1 (task A. 1 execution) ; TCF2 is used to control two PSFs in series to execute task B 1 (task B. 1 execution) ; in addition, TCF2 is also used to execute task B2 (task B. 2 execution) by controlling one PSF; TCF3 is used to control two PSFs in parallel and then in series with another PSF to execute task C 1 (task C. 1 execution) .

Please note that, after the data processing process of PSF3 corresponding to TCF1 is completed, the results will be sent to PSF4 corresponding to TCF2 by PSF3. PSF4 do its data processing based on the results of PSF3, and then send its results to PSF5, and so on, until the data processing process of PSF9 of TCF3 is completed. At this point, the execution of task A1, task B1, Task B2, task C1 is finished of three TCFs, and the execution of mission (mission execution) is finished. Illustratively, the ME process in FIG. 6 includes task A. 1 execution (TE A1) , Task B. 1 execution (TE B1) , Task B. 2 execution (TE B2) , and Task C. 1 execution (TE C1) .

Please note that this embodiment does not limit the number of TCF controlled by a MM, the number of TCF can be determined according to the mission. In addition, the TCF in FIG. 6 can be used to execute one task (Task A. 1) , but also can be used to perform other tasks which are not shown in the figure. What’s more, the number of PSF corresponding to each task and the connection way between PSFs are both unlimited. In FIG. 6, the MM is responsible for execution of only one mission, but the number of mission managed by MM is not limited. For example, a MM can also be responsible for more than one mission.

Based on the system architecture shown in FIG. 6 above, in addition to assigning task to each TCF to execute the mission, MM can also coordinate the ME process, to ensure that the ME can be completed successfully. If MM does not coordinate the ME process, accuracy of the results after ME is finished will be low, thus resulting in lower execution efficiency.

For example, in FIG. 6, if PSF4 is contaminated during data processing process, the results of PSF4 based on the contaminated data are less accurate. If MM does not coordinate the ME process in this case, less accurate PSF4 results will be sent to PSF5. And then, PSF5 will continue to do its data processing based on less accurate PSF4 results, and so on, until the end of ME, which will make the results of mission executed less accurate.

Therefore, in order to solve the above technical problems, the present disclosure provides a method of communication. In this method, MM can determine the management method of the ME, according to request of MC, or information of TE sent by the each TCF. By doing so, ME can be accurate and efficient. For example, MM can receive first request from MC or generate first request based on the information sent by each TCF for each TE. MM can then send the second request to the corresponding TCF (for example, the first task control function) to tell TCF to execute the corresponding second request.

The first request and the second request can be the same or different. When they are different, the second request can be used to indicate the first request. For example, if MM receives first request from MC and first request indicates terminating ME process, then the first request can include the ID of MM and the commands used to indicate the termination of ME process. However, after MM receives the first request, if MM determines that TE B1 is currently executed, MM can send a second request to the TCF2 corresponding to TE B1, instructing TCF2 to terminate the TE process after TE B1 is finished. At this point, the second request can include the ID of TCF2 and the commands used to indicate the termination of the ME process.

In some embodiments, the second request from MM to TCF can be state create request, state cancel request, pause request, resume request, rollback request, or terminate request. Correspondingly, dring ME process, the ME process may need the following dynamic ME management methods, such as methods on ME state creation/cancel, ME scheduling including ME pause control and ME resume control, ME rollback control, and ME termination.

Above several ME management method will be described in the following contents.

ME state creation/cancel: during the ME process, the MM may trigger creating a ME state at the current or upcoming intermediate point/event of the ME, and saving the associated ME state info after all composing TE (s) of the created ME state are completed. The MM may also trigger canceling any completed state (s) of the ME during the ME process to delete the saved ME state info associated to those completed state (s) . Details of the ME state creation procedure and ME state cancel procedure are described in following contents.

ME rollback control: during the ME process, the MM may trigger switching the ME to a target (ME) state, and resuming the ME from the target state. The target state must be a completed state of the ME process. Details of the ME rollback control procedure are described in following contents.

Switching the ME to a target (ME) state can be understood as making ME rollback to previous point/state of the ME process (e.g., from 70%of ME process rollbacks to 50%of ME process) . The reason to rollback a ME process can be the failure of on-going TE (s) (which may be caused by resource outage or data contamination) .

ME termination: Terminate (or stop) a ME process and release resources. The reason to terminate a ME process can be completion of the ME or requested by the mission customer.

During the ME process, the MM may trigger switching the ME to the (ME) terminate state according to a request (e.g. from the MC) or upon certain event (e.g. a ME termination condition happens) . The terminate state is a special state in which the ME termination procedure will be conducted/executed to terminate the ME process and release resources allocated to the ME process. Any ME process has a terminate state, and the ME process in terminate state cannot transit to other ME state (s) . Details of the ME termination procedure are described in following contents.

The ME termination condition, for example, can be that all tasks of the mission have been finished. And, the released resources can refer to PSF results generated in the ME process.

ME scheduling: When multiple ME (s) co-exist in the network with limited resource, the MM may need to schedule/coordinate them by: 1) Pause a ME: temporarily save the ME intermediate results and suspend the ME process, which may save more resources to other co-exist ME (s) . 2) Resume a ME: resume a paused ME with the saved intermediate results.

During the ME process, the MM may trigger switching the ME from an upcoming state (original state) to a (ME) pause state (a. k. a. ME pause control) , or switching a paused ME (i.e., a ME in pause state) to the original state (a. k. a. ME resume control) . The pause state is a special state which can only transit to the associated original state from which the ME process was switched. In a pause state, the ME process will stop any TE (s) , which can save pre-allocated resources for other on-going ME (s) managed by the same MM. Therefore, the ME scheduling procedures (including ME pause control and ME resume control) may allow the MM to schedule multiple MEs which share the same network resources. Details of the ME scheduling procedures are described in following contents.

Based on the previous content, the procedure of ME state creation/cancel, ME rollback control, ME termination, and ME scheduling are all related to ME state. The definition of ME state and the relationship between ME state and ME rollback control, ME termination and ME scheduling will be described in detail.

Mission execution (ME) state: A ME state (or mission state) describes an intermediate point/event of a ME process. One ME may include zero to multiple ME state (s) which are pre-determined in the mission template/parameters or determined by controller (s) which manage/control the ME process. In a ME process, one ME state can be uniquely described a set of completed TE (s) involved in the ME. By describing the ME process as a directed graph in which each edge represents a data session between CB (s) and each node represents a TE, one ME state can correspond to a CUT of the directed graph where the node (s) in the source part of the cut represent all completed TE (s) when the ME process reaches the ME state, and the node (s) in the sink part of the cut represents all un-triggered/incomplete TE (s) when the ME process reaches the ME state. The TE (s) in the source part which are connected with cut edge (s) is defined as the composing TE (s) of the ME state. A ME state cannot be defined at any intermediate point (s) /event (s) of/within a TE of the ME process, which means the ME state can only cut the ME process with TE granularity. FIG. 7 shows an example ME process comprising three ME states, i.e., state 1, state 2 and state 3. The composing TE of state 1 is TE A1; the composing TEs of state 2 are TE A1 and TE B1; the composing TEs of state 3 are TE A1 and TE B2.

One ME state is associated with a set of ME state info, including at least one of:

ME state ID/name.

Taking the contents shown in FIG. 7 as an example, the ID of state1, state2, and state3 need to be distinguished to determine different ME states based on different IDs.

TE ID/name of each composing TE of the ME state.

Taking state 2 in FIG. 7 as an example, composing TE of state 2 consists of TE A1 and TE B1, so it is necessary to distinguish the ID of TE A1 and TE B1 to determine different TEs according to the different IDs.

In addition, ME state info can also include composing TE info of composing T E. The contents of composing TE info will be described in detail below, which will not be described herein.

Each TE of the ME process may include one or more DP computing/processing function (s) (i.e., DP func. shown in the figure) .

Please note that the role of DP func. in FIG. 7 is the same as that of PSF in FIG. 6.

Each TE of a ME process is associated with a set of TE info, including at least one of:

A TE ID/name: a unique identifier of the TE. The TE ID should be different from the ID of CB instance (CBI) which conducts the TE, because the controller of the CBI may manage multiple TEs (CBI executions) associated with different MEs. In some embodiments, the TE ID can be a tuple composed by (mission session ID, ID of the CBI conducting the TE) .

Illustratively, TE A1, TE B1, TE B2, and TE C1 in FIG. 7 can have different IDs respectively.

TE results: the DP output of the TE, which should be forwarded to the next TE according to the execution dependency and/or logic (if any) associated to the ME process.

In FIG. 7, after DP func. 5 finished its data processing, TE B1 results can be obtained, and then DP func. 5 can send TE B1 results to the corresponding DP func. 6 for next TE (TE B2) .

TE parameters: TE info save mode (pause mode or state mode) ; optionally address/location of saved TE results data; optionally TE result forwarding info (e.g., ID (s) of data session (s) to target CBI (s) ) , etc.

Illustratively, after the DP function completes the corresponding TE, the DP function can store TE results locally or in an external database. Therefore, address/location of saved TE results data can be included in TE parameters.

There are two TE info save modes:

State mode: The state mode indicates that the TE is a composing TE of a ME state, and the TE info of a composing TE is permanently saved for the ME state during the whole ME process. The TE info can only be released/deleted after the ME is completed or terminated.

Pause mode: The pause mode indicates that the TE info is temporally saved for ME pause behavior, not for a composing TE of a ME state. The temporally saved TE info will be automatically released after the completion of the ME pause behavior.

The ME state (s) of a ME process can be either pre-determined in the mission template/parameters or be created (by controller (s) of the ME process) during the ME process.

It is understood that the TE info save mode of composing TE is always state mode, no matter which method ME state (s) is determined based on. In other words, the information of composing TE contained in the ME state (s) based on above two methods will be stored permanently until the mission is completed.

For an on-going ME process, the pre-determined or created ME state whose composing TE (s) are all completed are referred to as completed state; the pre-determined or created ME state whose composing TE (s) include un-triggered/incomplete TE (s) are referred to as upcoming state.

During the execution of a mission session, i.e., the ME process, the MM may initiate control behaviors/procedures to control the transitions between ME states.

FIG. 8 shows the state transition diagram of a ME process. In FIG. 8, the ME process includes n ME states which are represented by “ME state 1” , “ME state 2” , …, “ME state n” , respectively. “1-T” , “2-T” , and “n-T” represent the ME termination which switch the ME from state 1, state 2, and state n to the terminate state, respectively. “1-P” , “2-P” , and “n-P” represent the ME pause control which switch the ME from state 1, state 2, and state n to the pause state, respectively, and “1-R” , “2-R” , and “n-R” represent the ME resume control which switch the paused ME from pause state to state 1, state 2, and state n, respectively. “2b1” , “nb2” , and “nb1” represent the ME rollback control which switch the ME from state 2 to state 1, from state n to state 2, and from state n to state 1, respectively.

To determine the ME state management behavior (s) to be conducted during the ME process, an ME state management decision scheme should be applied by the MM. FIG. 9 shows the workflow of a ME state management decision scheme:

900: ME monitoring.

During a ME process, the MM keeps monitoring the following info of the ME:

Reported by TCF (s) : TE complete indicator; TE status info (percentage of the progress of the TE) , TE error info (indicating failure of a TE) , resource consumption rate (on PSF (s) and TCF) info.

ME management request from the mission customer (e.g., ME terminate request) .

901: ME terminate condition (s) meet?

At any intermediate point/event of the ME process, the MM may check if any ME terminate conditions were met. The ME termination conditions may include: 1) Receiving ME terminate request from mission customer; 2) the MM decides to terminate the ME according to monitored info in step 900 (e.g., no available resources for the ME) . If ME termination condition is met, 905 will be conducted. ME termination procedure will be performed. If no ME termination condition was met, the MM further checks whether ME rollback condition (s) were met in step 902.

902: ME rollback condition (s) meet?

The MM may check if any ME rollback condition (s) were met. The ME rollback conditions may include: 1) Receiving TE error info from any TCF (s) and the ME has at least one completed state. If ME rollback condition is met, 906 will be conducted. ME rollback procedure will be performed. If no ME rollback condition were met, the MM further checks whether ME scheduling is required in step 903.

In addition, the ME rollback conditions can also include receiving ME terminate request from mission customer (MC) . For example, TE error info can be information that indicates that the TE process cannot continue, such as insufficient resources for the TE process, contaminated data involved in the TE process, etc.

903: ME scheduling required?

The MM may check if any ME scheduling conditions were met. The ME scheduling conditions include: 1) the MM decides to pause the ME (or resume the paused ME) according to monitored resource consumption rate info from TCFs of the ME and other ME (s) .

2) Receiving ME pause request (or ME resume the paused ME) from mission customer.

A scheduling algorithm may be applied by the MM to make the ME scheduling decision. If ME scheduling condition is met, 907 will be conducted. ME pause procedure or ME resume procedure will be performed. If no ME scheduling condition was met, the MM further checks whether ME state creation/cancel is required in step 904.

904: ME state creation/cancel decision?

The MM may determine whether to execute ME state creation/cancel procedures according to monitored ME info (e.g., create a state if the on-going TE progress very slow and/or consuming intensive resources; cancel an old state if can be replaced by a newly created state) . If the decision is yes, ME state creation procedure or ME state cancel procedure (908) will be performed. If the decision is no, the MM keeps executing step 900 to monitoring the info of ME process.

The ME state management decision scheme is disclosed to determine when and which ME state management methods, i.e., ME termination, ME rollback control, ME scheduling, and ME state creation/cancel, should be executed.

For illustrative purposes, specific example embodiments will now be explained in greater detail in conjunction with the figures and above mentioned system, ED and TRP and network nodes.

The embodiments set forth herein represent information sufficient to practice the claimed subject matter and illustrate ways of practicing such subject matter. Upon reading the following description in light of the accompanying figures, those of skill in the art will understand the concepts of the claimed subject matter and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.

In the following, different methods inlcuded in ME state management will be described.

ME state creation/cancel

FIG. 10 shows the ME state creation procedure, which includes:

1001: The MM initiates ME state info. In details, the MM determines the composing TE (s) of the ME state to be created.

This application embodiment does not restrict how MM determines to create an ME state. For example, MM can decide to create ME state based on the task execution performance information sent to MM by each TCF. In addition, it can also receive request from MC, such as ME state create request 1 (as an example of first request) , wherein MC instructs MM to create ME state.

In either case, MM can perform this step 1001 once it determines to create an ME state.

If the MM has the TE info of a determined composing TE (e.g., the TE has been selected as the composing TE of other created ME state (s) ) , it means the TE info has been saved. The MM can add the TE info into the ME state info to be created.

For a determined composing TE which is on-going or not stated, the MM can trigger executing step 1002-1004 to save its TE info after the TE completed.

Taking FIG. 7 as an example, if MM wants to create state 2 after TE B1 is finished and determines that composing TEs of state 2 is TE A1 and TE B1, since information about TE A1 is already stored when state 1 is created, information about TE A1 can be obtained directly. In addition, because the TE B1 process is not yet finished, MM can save the information of TE B1 after the TE B1 process is finished based on the following steps 1002-1004.

For a completed TE whose TE info has not been saved, it cannot be selected as a composing TE of the ME state to be created.

Taking FIG. 7 above as an example, if MM wants to create state 2 after TE B1 is finished and determines that composing TEs of state 2 is TE A1 and TE B1, however, if the information of TE A1 is not stored after the TE A1 is finished, the information of TE A1 cannot be obtained at this time, state 2 cannot be created.

1002: ME state create request 2 from MM to TCF (of the target TE) : request the TCF to save TE info for a target TE which is on-going or not start. The ME state create request may include an identifier of the target TE, which may be 1) a MM assigned TE ID; 2) a tuple composed by (mission session ID, ID of the CB running the target TE) .

Illustratively, ME state create request 2 could serve as an example of second request. In this embodiment, first request and second request can be the same or different, which is not limited in this embodiment. For example, after the MM receives or generates a first request, it can process the first request and then send the processed first request (e.g. second request) to the corresponding TCF. Take that MC sends the first request to MM as an example, the first request may contain ID of MM and contents of the request, such as the request to create state. But after MM receives the first request, it may send the second request to the corresponding TCF. For example, the second request can include ID of TE and contents of the request.

As in previous example, if MM wants to save information of TE B1 after the TE B1 process is finished, MM can send a state create request to TCF2 (as an example of first task control function) corresponding to TE B1 (as an example of first task execution) , to request TCF2 save TE B1 information (as an example of first task execution information) after TE B1 is finished.

Identifier of TE B1 (as an example of a first task execution identifier) can be included in the state create request, such as the ID assigned from MM to TE B1. In addition, the identifier of TE B1 can also consist of the ID of the mission session and the ID of the computing module that executes TE B1.

1003: The TCF triggers to save TE info. According to the received ME state create request in step 1002, the TCF triggers the save TE info procedure to save the TE info of the target TE after the target TE completed. In the TE parameters, the TE info save mode should be set as “state mode” .

The TE information save mode corresponding to composing TE of ME state can be “state mode” . For example, if state 2 is created after TE B1 is finished, the information save mode of TE B1 can be set as “state mode” (as an example of first task execution information save mode) . In addition, the details of the save TE info procedure triggered by the TCF will be described later and will not be covered here.

1004: ME state create request 2 response from TCF to MM: inform the MM about the completion of saving TE info of the target TE. The ME state create request response may include the TCF assigned TE ID if no MM assigned TE ID is provided in step 1002. This step is optional.

Illustratively, ME state create request response can be used as an example of second request response.

In step 1001, if the composing TE included in the ME state to be created is already included in the previously created ME state, this means that the TE information for composing TE in the ME state has already been stored. In this case, MM does not need to perform steps 1002, 1003, and 1004. That is to say, steps 1002, 1003, and 1004 are optional.

1005: MM finalizes ME state info. After receiving the ME state create request response in step 1004, the MM saves TE ID of the target TE into the ME state info of the ME to be created. After TE ID (s) of all determined composing TE (s) have been received by MM, the MM finalizes the ME state info, and marks the ME state as the created state.

FIG. 11 shows the ME state cancel procedure, which includes:

1101: MM deletes the ME state information. MM can cancel a pre-determined or created ME state by deleting the associated ME state info and the ME state ID/name.

The conditions that MM decide to cancel ME state include, but are not limited to, limited storage space for ME state information. This embodiment does not restrict the way that MM decides to cancel the ME state. For example, MM can decide to cancel ME state based on the task execution performance information that each TCF sends to MM, and can also receive request from the MC. For example, MM receives ME state cancel request 1 (as an example of first request) from MC.

In either case, MM can perform this step 1101 after it has determined to cancel ME state.

For each composing TE of a cancelled ME state, the MM may optionally trigger step 1102-1104 to delete the TE info of the composing TE.

In FIG. 7, if MM wants to delete the corresponding information of state 2, the MM can, for example, delete the ID of state 2, and delete composing TE (TE A1and TE B1) information (as an example of first task execution information) of state 2.

1102: TE info release request from MM to TCF (of the composing TE) : request the TCF to delete the TE info of the composing TE. The TE ID must be included in the TE info release request. This step is optional.

It is understandable that TE info release request could serve as an example of second request.

Illustratively, MM determines to delete information of state 2, confirm the TE A1is not the composing TE of other states, MM can send a TE B1 info release request to TCF2 to request that TCF2 release TE B1 information. Therefore, ID of TE B1 (as an example of the first task execution identifier) can be included in the TE B1 info release request sent by the MM. In addition, since TE A1 is also composing TE of state 1, there is no need to delete TE A1 information.

1103: After receiving the TE info release request in step 1102, the TCF triggers the release saved TE info procedure to delete the TE info of the composing TE. This step is optional.

For example, when TCF2 receives a TE B1 info release request from MM, TCF2 can trigger the process of releasing TE B1 information. The information for TE B1 can be TE B1 results (as an example of first task execution results) and so on. In addition, the release saved TE Info procedure triggered by the TCF will be described in detail in a later section, which will not be described herein.

1104: TE info release request response from TCF to MM: inform the MM that the TE info of the composing TE has been deleted. This step is optional.

It should be understood that the TE info release request response can include the TE ID of a TE that has been deleted, such as the ID of TE B1. After MM receives all the TE IDs of TEs that need to be released, it can confirm that the corresponding ME state information has been released.

The ME state creation procedure and the ME state cancel procedure are disclosed to enable the dynamic creation and deleting of a ME state during the ME process.

ME rollback control

FIG. 12 shows the ME rollback control procedure, which includes:

1201: MM determines target ME state. In details, a completed state as the target state to rollback the ME.

This embodiment does not restrict how MM determines the rollback procedure. For example, MM can decide the rollback procedure based on the task execution performance information sent to MM by each TCF, and it can also receive request from MC, for example, ME rollback request 1 (as an example of first request) , instructing MM to rollback ME.

In either case, after MM determines the rollback procedure, it can perform this step 1201.

The target ME state to roll back to may be a finished state. In FIG. 7, for example, when state 1 is already established, MM can decide to roll back to state 1 after TE B1 is over. At this point, target ME state is state 1.

1202: ME rollback request 2 from MM to TCF (of the composing TE of the target state) : request the TCF to load saved TE info of the composing TE of the target state (target composing TE) . The ME rollback request may include the TE ID of the target composing TE. This design is to prevent leaking the ME level information to the TE level. For each target composing TE of the target state, this request should be sent to its TCF.

It is understandable that ME rollback request 2 could serve as an example of second request. In this embodiment, first request and second request can be the same or different.

Illustratively, the state which ME rolls back to can be a previously established state. Take FIG. 7 as an example, if the current TE B1 is completed, but MM decides to roll back to state 1 in FIG. 7, and state 1 includes composing TE A1, then MM can send ME rollback request 2 to TCF1. ID of TE A1 can be included in the ME rollback request 2. By doing so, MM sends ME rollback request 2 to TCF1 to request TCF load previously saved TE A1 information.

1203: According to the ME rollback request received in step 1202, the TCF triggers the load saved TE info procedure to load the TE info of the target composing TE.

Illustratively, based on the description in step 1202 above, TCF1 can load previously saved TE A1 information after receiving the ME rollback request 2 from MM. In addition, details of the load saved TE info procedure triggered by the TCF will be described later.

1204: ME rollback request 2 response from TCF to MM: inform the MM about the completion of load saved TE info of the target composing TE. The ME rollback control procedure can be completed after the ME rollback request response (s) of all target composing TE (s) have been received by the MM.

It can be understood that the ME rollback request response can be an example of second request response.

The TE ID of the TE that has been loaded with information can be included in the ME rollback request response, such as the TE ID that can represent TE A1. After MM receives the TE ID of all the TEs whose information needs to be loaded, MM can learn about that the corresponding ME state (for example, state 1) information has been loaded. The ME process can then start with the current ME state 1.

The ME rollback control procedure is disclosed to enable rollback the ME process from the current point/state to a previous point/state of the ME process.

ME scheduling

ME scheduling may include ME pause control procedure and ME resume control procedure.

FIG. 13 shows the ME pause control procedure, which includes:

1301: ME pause request 1 from MM to TCF (of the TE to be paused) : request the TCF to save TE info for a TE to be paused which is on-going or not start. The ME pause request may include an identifier of the TE to be paused, which can be 1) a MM assigned TE ID; 2) a tuple composed by (mission session ID, ID of the CB running the TE to be paused) .

Illustratively, ME pause request 1 can serve as an example of second request. This embodiment does not limit how MM determines to suspend ME. For example, MM can decide to suspend ME based on the task execution performance information sent to MM by each TCF, and it can also receive request from MC, for example, ME state cancel request 2 (as an example of first request) , instructing MM to suspend ME.

In an exemplary embodiment, MM can decide to suspend the ME process at which point. It can be understood that the ME process can only be paused after a TE is finished, which means that the ME process cannot be paused during the TE process in this application.

In FIG. 7, if MM decides to pause ME after TE B1 is finished, then MM can send a pause request 1 to TCF2 corresponding to TE B1. This embodiment does not restrict the timing of a pause request 1 from MM to TCF2. For example, MM can send a pause request 1 to TCF2 during the process of TE B1, MM can also send a pause request 1 to TCF2 before TE B1 is executed.

In addition to the identifier indicating the pause request, the pause request 1 can also include the identifier of TE to be paused, such as ID of TE. TE ID can be pre-assigned by the MM for each TE, and TE ID can also consist of the mission session ID and the ID of CB running the TE. This embodiment does not limit the type of identifier of TE to be paused, as long as different TEs can be distinguished.

1302: According to the received ME pause request 1 in step 1301, the TCF triggers the save TE info procedure to save the TE info of the TE to be paused after its completion. In the TE parameters, the TE info save mode should be set as “pause mode” . In some embodiments, if the TE info save mode has been set as “state mode” (which means the TE to be paused is a rollbacked TE) , the TCF will not modify the mode to “pause mode” to prevent mistakenly deleting the TE info in ME resume procedure.

Since not after each TE is finished, there will be a corresponding state, not every TE information will be stored. Therefore, for the TE whose information is not stored, if MM decides to suspend the ME process after the TE is finished, the TE information will be temporarily stored, and the TE info save mode will be set as “pause mode” . The purpose of temporarily storing TE information is that when MM decides to resume the ME process, MM can continue to execute subsequent ME processes based on the stored TE information. When a ME process is resumed, the stored information about the TE will be deleted (or released) .

In other embodiments, if MM decides to perform a pause operation after TE process is finished, but the TE info save mode has already been set as “state mode” , the TE info save mode will not be changed as “pause mode” at this time, in case the TE information is deleted after the ME process is resumed.

In FIG. 7, TE A1 is composing TE of state 1, so after the process of TE A1 is finished, TE A1 information will be stored permanently and TE A1 information save mode will be set as “state mode” . For example, if the ME process is rolled back from state 2 to state 1 (where the TE A1 information save mode is “state mode” ) , but if MM decides to pause the ME process after rollback procedure to state 1, since TE A1 information save mode is already set as “state mode, ” so it will not be set as “pause mode” again.

For another example, if there is no state 1 after TE A1 is finished, TE A1 info is not stored after TE A1 is finished. If MM request to pause the ME process after TE A1 is finished, TE A1 info will be temporarily stored, and the TE A1 info save mode will be set as “pause mode” .

In addition, the details of the save TE info procedure triggered by the TCF will be described later and will not be covered here.

1303: ME pause request 1 response from TCF to MM: inform the MM about the completion of saving TE info of the TE to be paused. The ME pause request response may include the TCF assigned TE ID if no MM assigned TE ID is provided in step 1301.

Illustratively, the ME pause request 1 response can be used as an example of a second request response.

If in step 1301 above, ME pause request 1 includes the TE ID of the TE that needs to be paused after the process is finished, and the TE ID is assigned by MM, then in this step, the ME pause request 1 response can include the TE ID assigned by MM. If in step 1301, the MM-assigned TE ID is not included in the ME pause request 1, then TCF can assign the TE ID to the TE that has been paused, and then send the TE ID to MM. In addition, if in step 1301 the TE ID consists of mission session ID and ID of the CB running the TE to be paused, then TCF can also send the above TE ID to MM, which is not restricted in this embodiment.

1304: After completing the save TE info procedure, the TCF may suspend the TE results forwarding behavior of the TE to be paused. After the TE results forwarding behavior (s) of ALL on-going TE (s) of the ME have been suspended, the ME pause control procedure is completed.

Illustratively, after the TE A1 information is stored, TCF1 can suspend sending the TE A1 results to the corresponding DP function of TCF2. For example, TCF1 can send first task execution results forward suspending request (as an example of first task execution results forward suspending request) to PSF3 (as an example of first terminal processing service function) .

FIG. 14 shows the ME resume control procedure, which includes:

1401: ME resume request 1 from MM to TCF (of the paused TE to be resumed) : request the TCF to load saved TE info for a paused TE. The ME resume request may include the TE ID of the TE to be resumed. This request should be sent to TCF (s) of all paused TE (s) of the ME.

It is understandable that ME resume request 1 could be an example of second request. This embodiment does not limit the way MM determines to resume ME. For example, MM can decide to resume ME based on the task execution performance information sent to MM by each TCF, and it can also receive request from the MC, for example, ME resume request 2 (as an example of first request) instructing MM to resume ME.

1402: After receiving the ME resume request 1 in step 1401, the TCF triggers the load saved TE info procedure to load the TE info of the paused TE and resume the TE results forwarding behavior of the paused TE.

For example, taking that ME is paused after TE A1 is finished and the TE A1 info save mode is “pause mode” as an example, after MM sends ME resume request 1 to TCF1, TCF1 can first load the previously saved TE info. TCF1 will then resume the ME process, which means that TCF1 will resume the operation of sending the TE A1 results to the corresponding DP function 4 of TE B1 so that the ME process continues.

1403: The TCF triggers to release saved TE info. Only if the TE info save mode of the paused TE is “pause mode” , the TCF may further trigger release saved TE info procedure to delete the TE info of the paused TE after step 1402 completed. This step is optional.

In this step, TCF deletes the TE information after M process is resumed as long as the TE info save mode is “pause mode” . That is to say, TCF will not delete the TE information after M process is resumed when the TE info save mode is “state mode” . Therefore, this step is optional.

For example, when after the TE A1 process is finished, the ME process is paused in FIG. 7, and the information save mode of TE A1 is “pause mode” , TCF1 may first load the TE A1 info after receiving a ME resume request 1, to resume the ME process. Then, TCF1 can delete the TE A1 info.

1404: ME resume request 1 response from TCF to MM: inform the MM about the completion of resuming the paused TE. After the ALL paused TE (s) of the ME have been resumed, the ME resume control procedure is completed.

It is understandable that ME resume request 1response could be an example of a second request response. For example, after TCF1 deletes TE A1info, it can tell MM that all ME process has been resumed, wherein the ME resume request 1response can include the ID of TE A1 from TCF 1 to MM.

The ME pause control procedure and the ME resume control procedure are disclosed to enable the pause/resume of a ME process, which further enable the scheduling of multiple ME (s) sharing/co-existing on the same network resources.

ME termination

FIG. 15 shows the ME termination procedure, which includes:

1501: Customer triggered ME terminate request from MC to MM: trigger a ME termination procedure by the MC. This step can be bypassed if the ME termination procedure is triggered by the MM after all TE (s) involved in the ME have been completed. The customer triggered ME terminate request may include: 1) Identifier of the ME process, e.g., mission session ID; 2) ME termination conditions, e.g., scheduled ME termination time, ID/description of the resource to be released. This step is optional.

It is understandable that ME terminate request could be an example of first request. This case of the MC sending an ME terminate request to MM is used to indicate that MC needs to terminate the ME process under certain conditions, such as a shortage of computing resources, rather than the ME process having been completed. That is, after the ME process has been finished, MM will send the terminate request directly to each TCF instead of the MC. Therefore, this step is optional.

ME terminate request from MC can include the ID of ME, since there may be multiple MEs for a single MM. In addition, ME terminate request can also include termination conditions for ME, such as the termination time of the ME and a description of the resource information to be deleted.

1502: TE termination: MM request the TCF (s) of all TE (s) involved in the ME to terminate the TE (s) and release associated resources. In some embodiments, the TE termination procedure can be executed by the MM after the completion of each TE. The TE termination procedure includes:

In some embodiments, after MM receives the ME terminate request sent by MC, it can send a terminate request to each TCF to request TCF terminate each TE and release the associated resource information. In other embodiments, MM may also send a terminate request to each TCF to terminate each TE and release the associated resource information after all TEs have been finished. In either case, the termination procedure for each TE includes the following steps:

1502.1: TE terminate request from MM to TCF: trigger the TE termination procedure. The TE terminate request may include: 1) Identifier of the TE to be terminated (e.g., TE ID, or (Mission session ID + ID of the CBI running the TE) ) ; 2) TE termination conditions, e.g., scheduled TE termination time, ID/description of the resource to be released.

It is understandable that TE terminate request could be an example of second request. MM sends a terminate request to each TCF, which can include, termination conditions, and the identifier of the TE to be terminated, such as TE ID.

As shown in FIG. 6, MM can send a terminate request to TCF1, requesting TE A1 termination; MM can also send a terminate request to TCF2, requesting TE B1 and TE B2 termination; MM can also send a terminate request to TCF3, request TE C1 to termination.

1502.2: PSF exec. terminate request from TCF to PSF: After receiving the TE terminate request, the TCF sends PSF exec. terminate request to PSF (s) involved in the TE to terminate their execution. The PSF exec. terminate request may include: 1) Identifier of the PSF (e.g., PSF ID; 2) PSF exec. termination conditions, e.g., scheduled termination time, ID/description of the resource to be released.

Since the TE is achieved by PSF, TCF can send a terminate request to the PSF corresponding to each TE. When PSF receives the terminate request, it can perform the termination procedure.

As shown in FIG. 6, TCF1 sends PSF exec. terminate request (as an example of first terminal processing service function execution terminate request) to the PSF3 corresponding to TE A1, so the terminate request can include the ID of PSF3. TCF2 sends a terminate request to PSF5 corresponding to TE B1, so the terminate request can include the ID of PSF5. In addition, TCF2 also sends a terminate request to PSF6 corresponding to TE B2, so the terminate request may include the ID of PSF6. TCF3 sends a terminate request to PSF9 corresponding to TE C1, so the terminate request may include the ID of PSF9.

1502.3: According to the PSF exec. terminate request received in step 1502.2, each PSF terminates its execution and releases the resources.

Illustratively, the released resources can be computing results of PSFs.

1502.4: PSF exec. terminate request response from PSF to TCF: inform the TCF about the completion of the PSF exec. termination.

Illustratively, PSF exec. terminate request response can include the ID of the PSF. For example, PSF3 sends PSF3 exec. terminate request response (as an example of first terminal processing service function execution terminate request response) to TCF1 to notify PSF3 has terminated its process.

1502.5: After all PSF executions related to the TE have been terminated, the TCF releases the task management resources (e.g., the computing/communication resources) related to the TE.

After TCF receives IDs of respective PSF, it knows that the corresponding TE has been terminated. In FIG. 6, when TCF1 receives the ID of PSF3, it can confirm that TE A1 has been terminated. Then, TCF1 can release related task management resources, such as communication interface information of TCF1 and the corresponding PSF. The principle of TCF2 and TCF3 releasing resources are the same, which will not be described herein.

1502.6: TE terminate request response from TCF to MM: indicate the completion of the TE termination procedure.

Please note that TE terminate request response could be an example of a second request response.

Each TCF (TCF1, TCF2, and TCF3 in FIG. 6) can include the IDs of each TE in the TE terminate request response to MM. For example, TCF1 sends the ID of TE A1 to MM, TCF2 sends the ID of TE B1 and TE B2 to MM, and TCF3 sends the ID of TE C1 to MM.

1503: MM performs ME related resource release. After all TE termination procedures have completed, the MM releases the mission management resources (e.g., the computing/communication resources) related to the ME.

After MM receives the IDs corresponding to TE A1, TE B1, TE B2, and TCF3, it determines that the ME process has been terminated. At this point, MM can release the relevant mission management resources, such as the communication interface information between MM and the corresponding TCF.

1504: Customer trigger ME terminate request response from MM to MC: inform the MC about the completion of ME termination. This step can be bypassed if the ME termination is triggered by the MM. This step is optional.

As described in step 1501 above, if the ME terminate request is sent by the MC to MM, then in this step, MM can send a terminate request response to MC to inform termination of ME.

The ME termination procedure is disclosed to enable termination of a ME process and release the ME process related resources.

In addition, the procedure provides a method of TE info management. The benefits of disclosing the TE info management method is to enable the basic sub-procedures, i.e., save TE info, load saved TE info, and delete saved TE info, which are involved in the ME state management procedures disclosed in previous enbodiments.

The ME state management procedures may include three basic TE info management procedures, i.e., save TE info procedure, load saved TE info procedure, and release saved TE info procedure.

Save TE info: FIG. 16 shows the save TE info procedure which is used to save the TE info of a target TE. The save TE info procedure must be triggered by the TCF in the ME state creation procedure and ME pause control procedure before the on-going target TE completed. The following step 1601 –1604 in save TE info procedure must be executed after the target TE completed:

1601: TE result save request from TCF to related PSF (s) (e.g., the PSF (s) outputting/generating the TE result) : request related PSF (s) to save generated TE result. The TE result save request may include: TE results saving location info (e.g., address (es) of the related PSF (s) , or address/location of external dataset) .

In an illustrative embodiment, TCF can send TE results save request to relevant PSF during the creation process of the ME state, requesting save TE results of composing TEs corresponding to the created ME state. TE results save request may include the save location of the TE results, such as PSF or external database, which is not restricted by this embodiment.

Take storing TE result in a PSF as an example, in FIG. 6, for example, TCF1 (as an example of first task control function) can send TE A1 results save request (as an example of first task execution results save request) to PSF3 (as an example of first terminal processing service function) , request that TE A1 results (as an example of first task execution results) be stored in PSF3. In addition, TE A1 results save request can include TE A1 results saving location info (as an example of first task execution results saving location information) .

1602: After the PSF execution completed (i.e., the TE result has been generated) , the related PSF (s) save the generated TE result locally or in external dataset according to the received TE results saving location info in step 1601.

1603: TE result save request response from related PSF (s) to TCF: inform the TCF about the completion of the TE result saving.

Taking PSF3 storing TE A1 results in FIG. 6 as an example, after PSF3 saves the TE A1 results, PSF3 can send a TE A1 results save request response (as an example of first task execution results save request response) to TCF1. The TE A1 results save request response may include the corresponding ID of TE A1 to indicate that the TE A1 results has been saved.

1604: After receiving the TE result save request response in step 1603, the TCF assign a unique TE ID for the saved TE results (if no TE ID has been assigned to the target TE) , determines the associated TE parameters, and saves the TE ID and TE parameters locally. After step 1604 completed, the TE info of the target TE has been saved and the target TE turns to be a saved TE.

For example, after TCF1 receives a TE A1 results save request response, it can save the ID of TE A1 (as an example of first task execution identifier) and TE A1 parameters (as an example of first task execution parameters) .

The TE info save mode in the associated TE parameters should be determined according to the type of ME state management procedure which involves the save TE info procedure, i.e., in ME state creation procedure, the TE info save mode is set to state mode; in ME pause control procedure, the TE info save mode is set to pause mode.

Please note that during ME pausing process, if the TE info save mode has been set as “state mode” , then the TE info save mode will not be changed to “pause mode” . The reasons for this have already been described above and will not be repeated here.

If external dataset is selected by the TCF to store the TE result (in step 1601) , the ID/address of the external dataset must be saved in the TE parameters in step 1604.

Load saved TE info: FIG. 17 shows the load saved TE info procedure which is used to load the TE info of a saved TE in the ME. The load saved TE info procedure can be triggered by the TCF during the ME resume control and ME rollback control procedures. Before executing the load saved TE info procedure, a target TE ID must be provided to TCF to identify the saved TE whose TE info shall be loaded. The load saved TE info procedure include:

1701: According to the target TE ID, the TCF loads the saved TE parameters associated to the target TE ID.

As mentioned above, TE parameters include the TE info save mode, such as “state mode” and “pause mode” ; address/location of saved TE results data, TE results forwarding info, and so on. For example, TCF1 (as an example of first task control function) can load TE A1 parameters (as an example of first task execution parameters) .

1702: TE result load request from TCF to related PSF (s) (e.g., the PSF (s) saving the TE result) : request related PSF (s) to load the saved TE result associated with the target TE ID. The target TE ID and (opt. ) ID/address of the external dataset which saved the TE result can be included in the TE result load request.

Take TCF1 in FIG. 6 loading the results of TE A1 (as an example of TE A1 results) as an example, since PSF3 (as an example of first terminal processing service function) already saves the results of TE A1, so TCF1 can send the TE A1 results load request (as an example of the first task execution results load request) to PSF3. For example, if PSF3 saves the results of TE A1 in PSF3, then the TE A1 results load request can include the ID of TE A1 (as an example of a first task execution identifier) . If PSF3 saves the results of TE A1 in an external database, then in addition to including the ID of TE A1, the TE A1 results load request can also include the ID or address of the external database (as an example of first task execution results saving location information) .

1703: After receiving the TE result load request in step 1702, the related PSF (s) load the saved TE result according to the target TE ID and (opt. ) ID/address of the external dataset which saved the TE result provided in the TE request load request.

For example, after PSF3 receives TE A1 results load request from TCF1, it either loads the results of TE A1 from PSF3 or obtains the results of TE A1 from the external database.

1704: TE result load request response from related PSF (s) to TCF: inform the TCF about the completion of the TE result load.

Illustratively, once PSF3 has loaded the results of TE A1, it can send the TE A1 results load request response (as an example of the first task execution results load request response) to TCF1. The TE A1 results load request response can include the ID of TE A1.

1705: After receiving the TE result load request response in step 1704, the TCF and the related PSF (s) may forward the loaded TE result to the target CB (s) according to the ME process logic/dependency, which resumes the ME process.

As shown in FIG. 6, TCF1 can first controls PSF3 to load previously save TE A1 results when ME process is needed to be resumed. After PSF3 finishes loading, ME process can start to be resumed, which means that TCF1 can control PSF3 to send TE A1 results to CB of PSF4. For example, TCF1 can send TE A1results forwarding request (as an example of the first task execution results forwarding request) to PSF3.

If MM decides to roll back the ME process to the point when TE A1 is finished, it means that the TE A1 results has been saved by PSF3. At which point, TCF1 can control the PSF3 to load previously saved TE A1 results. And then the ME process can continue by sending TE A1 results to CB of PSF4.

Release saved TE info: FIG. 18 shows the release saved TE info procedure which is used to delete the TE info of a saved TE in the ME (to release storage resources) . The release saved TE info procedure can be triggered by the TCF during the ME resume control and ME state cancel procedures. Before executing the release saved TE info procedure, a target TE ID must be provided to TCF to identify the saved TE whose TE info shall be deleted.

In the ME resume procedure, MM can send the TE ID of the target TE to tell TCF the TE whose results needs to be deleted. If the TE info save mode is “state mode” , TE info cannot be deleted. If the TE info save mode is “pause mode” , TE info can be deleted. For example, after TCF receives the TE ID sent by MM, it can directly delete the TE info corresponding to the TE ID.

The release saved TE info procedure include:

1801: TE result release request from TCF to related PSF (s) (e.g., the PSF (s) saving the TE result) : request related PSF (s) to release the saved TE result associated with the target TE ID. The target TE ID and (opt. ) ID/address of the external dataset which saved the TE result can be included in the TE result release request.

For example, in FIG. 6, if TCF1 wants to delete the results of TE A1, TCF1 can send a TE A1 results release request to PSF3 because PSF3 already saves the results of TE A1. For example, if PSF3 saves the results of TE A1 in PSF3, the TE A1 results release request can include the ID of TE A1. If PSF3 saves the results of ET A1 in an external database, the TE A1 results release request may include the ID or address of the external database in addition to the ID of TE A1.

1802: After receiving the TE result release request in step 1801, the related PSF (s) delete the saved TE result according to the target TE ID and (opt. ) ID/address of the external dataset which saved the TE result provided in the TE request load request.

For example, after PSF3 receives the TE A1 results release request from TCF1 (as a first task execution results release request) , PSF3 either deletes the TE A1 results from PSF3 or deletes the TE A1 results from an external database.

1803: TE result release request response from related PSF (s) to TCF: inform the TCF about the completion of the TE result delete.

Illustratively, after PSF3 deletes TE A1 results, it can send TE A1 result release request response (as an example of first task execution results release request response) to TCF1. The response can include ID of TE A1.

1804: After receiving the TE result release request response in step 1803, the TCF deletes the saved TE parameters associated to the target TE ID. After step 1804 completed, the TE info of the target TE has been deleted.

In the communication method provided in this disclosure, MM can send requests to TCF based on the performance information of each TE, or on request sent by MC, to manage the ME process. The request from MM to TCF can be state create request, state cancel request, pause request, resume request, rollback request, or terminate request, etc. In this way, mission execution can be completed successfully. And at the same time, the accuracy of mission execution results as well as the efficiency of mission execution will also be improved.

Illustratively, referring to FIG. 19, FIG. 19 shows a schematic block diagram of an apparatus according to some embodiments of this disclosure. The apparatus 1000 includes a processor 1010. The processor 1010 is coupled to a memory 1020. The memory 1020 is configured to store a computer program or instructions and/or data. The processor 1010 is configured to execute the computer program or instructions and/or data stored in the memory 1020, so that the methods in the foregoing method embodiments are executed.

In some embodiments, the apparatus 1000 includes one or more processors 1010.

In some embodiments, as shown in FIG. 19, the apparatus 1000 may further include the memory 1020.

In some embodiments, the apparatus 1000 may include one or more memories 1020.

In some embodiments, the memory 1020 may be integrated with the processor 1010, or disposed separately from the processor 1010.

In some embodiments, as shown in FIG. 19, the apparatus 1000 may further include a communication interface 1030, and the communication interface 1030 is configured to communicate with other apparatus/chips/device/chipset. For example, the processor 1010 is configured to receive a signal across a receiver or transmit a signal across a transmitter based on the communication interface 1030. For another example, the processor 1010 may store data to a memory or read data from a memory based on the communication interface 1030.

In some embodiments, the detail description of processor 1010 may refer to the aforementioned processor 210/260/276.

In some embodiments, the detail description of memory 1020 may refer to the aforementioned memory 208/258/278.

In some embodiments, the apparatus 1000 may comprise more modules.

In some embodiments, the apparatus 1000 might be a chip or a chipset.

In some aspects of the present disclosure, there is provided an apparatus/chipset system comprising means (e.g., at least one processor) to implement a method implemented by (or at) a UE of the present disclosure. The apparatus/chipset system may be the UE (that is, a terminal device) or a module/component in the UE. In details, the at least one processor may execute instructions stored in a computer-readable medium to implement the method.

In some aspects of the present disclosure, there is provided an apparatus/chipset system comprising means (e.g., at least one processor) to implement the method implemented by (or at) a network device (e.g., base station) of the present disclosure. The apparatus/chipset system may be the network device or a module/component in the network device. In details, the at least one processor may execute instructions stored in a computer-readable medium to implement the method. In some aspects of the present disclosure, there is provided a system comprising at least one of an apparatus in (or at) a UE of the present disclosure, or an apparatus in (or at) a network device of the present disclosure.

In some aspects of the present disclosure, there is provided a method performed by a system comprising at least one of an apparatus in (or at) a UE of the present disclosure, and an apparatus in (or at) a network device of the present disclosure.

In some aspects of the present disclosure, there is provided an apparatus/chipset system comprising means (e.g., at least one processor) to implement a method implemented by (or at) a UE of the present disclosure. The apparatus/chipset system may be a network entity illustrated in this disclosure, e.g., AF, TCF, Device (that is, a terminal device) or a module/component in the network entity. In details, the at least one processor may execute instructions stored in a computer-readable medium to implement the method.

In some aspects of the present disclosure, there is provided a system comprising at least two of the mentioned network entities e.g., AF, TCF, Device illustrated in this disclosure.

In some aspects of the present disclosure, there is provided a method performed by a system comprising at least two of the mentioned network entities illustrated in this disclosure.

Please note that two or more of the network entities illustrated in this disclosure may be located in in physical network entity, or to be implemented as a single function entity. In this case, the interaction between the two or more of the mentioned network entities may be not needed, i.e., the corresponding step (s) may be ignored (optional) .

Please note that although two or more network entities are illustrated in this disclosure, only one of them may be enough for an example solution in this disclosure. For example, in the example shown in FIG. 10, from MM side, only an ME state create request and response are needed. For operations executed by other network entities (e.g., step 1003) , the MM does not see it (or they may be transparent to the MM) .

In some aspects of the present disclosure, there is provided a computer program comprising instructions. The instructions, when executed by a processor, may cause the processor to implement a method of the present disclosure.

In some aspects of the present disclosure, there is provided a non-transitory computer-readable medium storing instructions, the instructions, when executed by a processor, may cause the processor to implement a method of the present disclosure.

The solutions described in the disclosure is applicable to a next generation (e.g. sixth generation (6G) or later) network, or a legacy (e.g. 5G, 4G, 3G or 2G) network.

It will be appreciated that any module, component, or device disclosed herein that executes instructions may include, or otherwise have access to, a non-transitory computer/processor readable storage medium or media for storage of information, such as computer/processor readable instructions, data structures, program modules and/or other data. A non-exhaustive list of examples of non-transitory computer/processor readable storage media includes magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, optical disks such as compact disc read-only memory (CD-ROM) , digital video discs or digital versatile discs (i.e., DVDs) , Blu-ray Disc^TM, or other optical storage, volatile and non-volatile, removable and non-removable media implemented in any method or technology, random-access memory (RAM) , read-only memory (ROM) , electrically erasable programmable read-only memory (EEPROM) , flash memory or other memory technology. Any such non-transitory computer/processor storage media may be part of a device/apparatus or accessible or connectable thereto. Computer/processor readable/executable instructions to implement a method, an application or a module described herein may be stored or otherwise held by such non-transitory computer/processor readable storage media.

It could be noted that the message in the disclosure could be replaced with information, which may be carried in one single message, or be carried in more than one separate message.

Without special noting, the terms “apparatus” and “device” are used exchangeable, and the terms “identity” and “identifier” are sued exchangeable.

In the disclosure, the word “a” or “an” when used in conjunction with the term “comprising” or “including” in the claims and/or the specification may mean “one” , but it is also consistent with the meaning of “one or more” , “at least one” , and “one or more than one” unless the content clearly dictates otherwise. Similarly, the word “another” may mean at least a second or more unless the content clearly dictates otherwise.

In the disclosure, the words “first” , “second” , etc., when used before a same term (e.g., ED, or an operating step) does not mean an order or a sequence of the term. For example, the “first ED” and the “second ED” , means two different EDs without specially indicated, and similarly, the “first step” and the “second step” means two different operating steps without specially indicated, but does not mean the first step have to happen before the second step. The real order depends on the logic of the two steps.

The terms “coupled” , “coupling” or “connected” as used herein can have several different meanings depending on the context in which these terms are used. For example, as used herein, the terms coupled, coupling, or connected can indicate that two elements or devices are directly connected to one another or connected to one another through one or more intermediate elements or devices via a mechanical element depending on the particular context. The present disclosure encompasses various embodiments, including not only method embodiments, but also other embodiments such as apparatus embodiments and embodiments related to non-transitory computer readable storage media.

Although this disclosure refers to illustrative embodiments, this is not intended to be construed in a limiting sense. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of the disclosure, will be apparent to persons skilled in the art upon reference to the description.

Features disclosed herein in the context of any particular embodiments may also or instead be implemented in other embodiments. Method embodiments, for example, may also or instead be implemented in apparatus, system, and/or computer program product embodiments. In addition, although embodiments are described primarily in the context of methods and apparatus, other implementations are also contemplated, as instructions stored on one or more non-transitory computer-readable media, for example. Such media could store programming or instructions to perform any of various methods consistent with the present disclosure.

Definitions of acronyms &glossaries
User Equipment           UE
Data Network             DN
Quality of Service       QoS
Radio Access Network     RAN
Control plane            CP
Data plane               DP
Network function         NF
Application server       AS
X as a service           XaaS
Control and management plane   C/M plane
Core Network             CN
Identifier               ID
Application Function     AF
Artificial Intelligence  AI
Processing Service Function PSF
Task Control Function       TCF
Mission Management         MM
Computing Block            CB
Computing block instance   CBI
Computing Block ID         CBID
Mission Selection Assistance ID   MSAI
Mission execution          ME
Task execution             TE
Mission customer           MC

Claims

A first apparatus, comprising:

at least one processor, wherein the at least one processor is configured to:

receive a first request from mission customer in a communication system, or generate the first request based on task execution performance information from a plurality of task control functions in the communication system, wherein the communication system is used to execute a first mission, and one of the plurality of task control functions is used to manage execution of at least one task of the first mission;

send a second request to a first task control function in the plurality of task control functions, wherein the first task control function is used to manage a first task execution of the execution of at least one task, and the second request indicates the first request.
The first apparatus of claim 1, wherein the second request is state create request, state cancel request, pause request, resume request, rollback request, or terminate request; and

the second request includes a first task execution identifier of the first task execution.
The first apparatus of claim 2, wherein the at least one processor is further configured to:

receive a second request response from the first task control function, wherein the second request response indicates completion of the second request and includes the first task execution identifier.
A second apparatus, comprising:

at least one processor, wherein the at least one processor is configured to:

receive a second request from mission management used to execute a first mission including at least one task in a communication system;

execute the second request, wherein the second request includes a first task execution identifier of a first task execution corresponding to a first task in the at least one task;

send a second request response including the first task execution identifier to the mission management.
The second apparatus of claim 4, wherein the first task execution corresponds to first task execution information including the first task execution identifier, first task execution results, and first task execution parameters including first task execution information save mode and location of the first task execution results.
The second apparatus of claim 5, wherein the second request is a state create request, and execute the second request comprises:

saving the first task execution information.
The second apparatus of claim 6, wherein saving the first task execution information comprises:

sending first task execution results save request to a first terminal processing service function, wherein the first task execution results save request includes first task execution results saving location information, and the first terminal processing service function is used to perform the first task execution;

receiving first task execution results save request response from the first terminal processing service function, wherein the first task execution results save request response informs completion of saving the first task execution results;

saving the first task execution identifier and the first task execution parameters, wherein the first task execution information save mode is state mode.
The second apparatus of claim 5, wherein the second request is a state cancel request, and execute the second request comprises:

releasing the first task execution information.
The second apparatus of claim 8, wherein releasing the first task execution information comprises:

sending first task execution results release request to a first terminal processing service function, wherein the first task execution results release request includes first task execution results saving location information;

receiving first task execution results release request response from the first terminal processing service function, wherein the first task execution results release request response informs completion of releasing the first task execution results;

releasing the first task execution parameters.
The second apparatus of claim 5, wherein the second request is a pause request; and execute the second request comprises:

saving the first task execution information;

sending first task execution results forward suspending request to a first terminal processing service function to inform the first terminal processing service function suspend forwarding the first task execution results.
The second apparatus of claim 10, wherein saving the first task execution information comprises:

sending first task execution results save request to the first terminal processing service function, wherein the first task execution results save request includes first task execution results saving location information, and the first terminal processing service function is used to perform the first task execution;

receiving first task execution results save request response from the first terminal processing service function, wherein the first task execution results save request response informs completion of saving the first task execution results;

saving the first task execution identifier and the first task execution parameters, wherein the first task execution information save mode is pause mode when the first task execution information save mode isn’t save mode.
The second apparatus of claim 5, wherein the second request is a resume request; and execute the second request comprises:

loading the first task execution information;

sending first task execution results forwarding request to a first terminal processing service function, to inform the first terminal processing service function forward the first task execution results;

releasing the first task execution information when the first task execution information save mode is pause mode.
The second apparatus of claim 12, wherein loading the first task execution information comprises:

loading the first task execution parameters;

sending first task execution results load request to the first terminal processing service function, wherein the first task execution results load request includes the first task execution results saving location information;

receiving first task execution results load request response from the first terminal processing service function, wherein the first task execution results load request response informs completion of loading the first task execution results.
The second apparatus of claim 12, wherein releasing the first task execution information when the first task execution information save mode is pause mode comprises:

sending first task execution results release request to the first terminal processing service function, wherein the first task execution results release request includes the first task execution results saving location information;

receiving first task execution results release request response from the first terminal processing service function, wherein the first task execution results release request response informs completion of releasing the first task execution results;

releasing the first task execution parameters.
The second apparatus of claim 5, wherein the second request is a rollback request; and execute the second request comprises:

loading the first task execution information.
The second apparatus of claim 15, wherein loading the first task execution information comprises:

loading the first task execution parameters;

sending first task execution results load request to a first terminal processing service function, wherein the first task execution results load request includes the first task execution results saving location information;

receiving first task execution results load request response from the first terminal processing service function, wherein the first task execution results load request response informs completion of loading the first task execution results.
The second apparatus of claim 5, wherein the second request is a terminate request including first task execution termination conditions; and execute the second request comprises:

sending a first terminal processing service function execution terminate request to a first terminal processing service function, wherein the first terminal processing service function execution terminate request includes identifier of the first terminal processing service function and terminate conditions, and the first terminal processing service function is used to perform the first task execution;

receiving first terminal processing service function execution terminate request response informing completion of first terminal processing service function execution termination and first terminal processing service function resource release;

releasing first task management resources including computing resources of the first task execution.
A third apparatus, comprising:

at least one processor, wherein the at least one processor is configured to:

accept a third request from a first task control function in a communication system, wherein the communication system is used to manage execution of a first mission and the first task control function is used to manage a first task corresponding to the first mission;

execute the third request;

send third request response to the first task control function.
The third apparatus of claim 18, wherein the third request is first task execution results save request; and

execute the third request, comprises:

saving first task execution results of the first task after completing the first task.
The third apparatus of claim 18, wherein the third request is first task execution results release request; and

execute the third request, comprises:

releasing first task execution results of the first task.
The third apparatus of claim 18, wherein the third request is first task execution results forward suspending request; and

execute the third request, comprises:

suspending forwarding first task execution results of the first task after completing the first task.
The third apparatus of claim 18, wherein the third request is first task execution results forwarding request, and

execute the third request, comprises:

forwarding first task execution results of the first task after completing the first task.
The third apparatus of claim 18, wherein the third request is first task execution results load request; and

execute the third request, comprises:

loading first task execution results of the first task after completing the first task.
The third apparatus of claim 18, wherein the third request is first terminal processing service function execution terminate request, and

execute the third request, comprises:

terminating first terminal processing service function execution and releasing first terminal processing service function resource.
A communication method, comprising:

receiving a first request, by a first apparatus, from mission customer in a communication system, or generate the first request based on task execution performance information from a plurality of task control functions in the communication system, wherein the communication system is used to execute a first mission, and one of the plurality of task control functions is used to manage execution of at least one task of the first mission;

sending a second request, by the first apparatus, to a first task control function in the plurality of task control functions, wherein the first task control function is used to manage a first task execution of the execution of at least one task, and the second request indicates the first request.
The method of claim 25, wherein the second request is state create request, state cancel request, pause request, resume request, rollback request, or terminate request; and

the second request includes a first task execution identifier of the first task execution.
The method of claim 26, further comprising:

receiving a second request response, by the first apparatus, from the first task control function, wherein the second request response indicates completion of the second request and includes the first task execution identifier.
A communication method, comprising:

receiving a second request, by a second apparatus, from mission management used to execute a first mission including at least one task in a communication system;

executing the second request, by the second apparatus, wherein the second request includes a first task execution identifier of a first task execution corresponding to a first task in the at least one task;

sending second request response, by the second apparatus, including the first task execution identifier to the mission management.
The method of claim 28, wherein the first task execution corresponds to first task execution information including the first task execution identifier, first task execution results, and first task execution parameters including first task execution information save mode and location of the first task execution results.
The method of claim 29, wherein the second request is a state create request, and executing the second request comprises:

saving the first task execution information.
The method of claim 30, wherein saving the first task execution information comprises:

sending first task execution results save request to a first terminal processing service function, wherein the first task execution results save request includes first task execution results saving location information, and the first terminal processing service function is used to perform the first task execution;

receiving first task execution results save request response from the first terminal processing service function, wherein the first task execution results save request response informs completion of saving the first task execution results;

saving the first task execution identifier and the first task execution parameters, wherein the first task execution information save mode is state mode.
The method of claim 29, wherein the second request is a state cancel request, and executing the second request comprises:

releasing the first task execution information.
The method of claim 32, wherein releasing the first task execution information comprises:

sending first task execution results release request to a first terminal processing service function, wherein the first task execution results release request includes the first task execution results saving location information;

receiving first task execution results release request response from the first terminal processing service function, wherein the first task execution results release request response informs completion of releasing the first task execution results;

releasing the first task execution parameters.
The method of claim 29, wherein the second request is a pause request; and executing the second request comprises:

saving the first task execution information;

sending first task execution results forward suspending request to a first terminal processing service function, to inform the first terminal processing service function suspend forwarding the first task execution results.
The method of claim 34, wherein saving the first task execution information comprises:

sending first task execution results save request to the first terminal processing service function, wherein the first task execution results save request includes first task execution results saving location information, and the first terminal processing service function is used to perform the first task execution;

receiving first task execution results save request response from the first terminal processing service function, wherein the first task execution results save request response informs completion of saving the first task execution results;

saving the first task execution identifier and the first task execution parameters, wherein the first task execution information save mode is pause mode when the first task execution information save mode isn’t save mode.
The method of claim 29, wherein the second request is a resume request; and executing the second request comprises:

loading the first task execution information;

sending first task execution results forwarding request to a first terminal processing service function, to inform the first terminal processing service function forward the first task execution results;

releasing the first task execution information when the first task execution information save mode is pause mode.
The method of claim 36, wherein loading the first task execution information comprises:

loading the first task execution parameters;

sending first task execution results load request to the first terminal processing service function, wherein the first task execution results load request includes the first task execution results saving location information;

receiving first task execution results load request response from the first terminal processing service function, wherein the first task execution results load request response informs completion of loading the first task execution results.
The method of claim 36, wherein releasing the first task execution information when the first task execution information save mode is pause mode comprises:

sending first task execution results release request to the first terminal processing service function, wherein the first task execution results release request includes the first task execution results saving location information;

receiving first task execution results release request response from the first terminal processing service function, wherein the first task execution results release request response informs completion of releasing the first task execution results;

releasing the first task execution parameters.
The method of claim 29, wherein the second request is a rollback request; and executing the second request comprises:

loading the first task execution information.
The method of claim 39, wherein loading the first task execution information comprises:

loading the first task execution parameters;

sending first task execution results load request to a first terminal processing service function, wherein the first task execution results load request includes the first task execution results saving location information;

receiving first task execution results load request response from the first terminal processing service function, wherein the first task execution results load request response informs completion of loading the first task execution results.
The method of claim 29, wherein the second request is a terminate request including first task execution termination conditions; and executing the second request comprises:

sending a first terminal processing service function execution terminate request to a first terminal processing service function, wherein the first terminal processing service function execution terminate request includes identifier of the first terminal processing service function and terminate conditions, and the first terminal processing service function is used to perform the first task execution;

receiving first terminal processing service function execution terminate request response informing completion of first terminal processing service function execution termination and first terminal processing service function resource release;

releasing first task management resources including computing resources of the first task execution.
A communication method, comprising:

accepting a third request, by a third apparatus, from a first task control function in a communication system, wherein the communication system is used to manage execution of a first mission and the first task control function is used to manage a first task corresponding to the first mission;

executing the third request, by the third apparatus;

sending a third request response, by the third apparatus, to the first task control function.
The method of claim 42, wherein the third request is first task execution results save request; and

executing the third request, comprises:

saving first task execution results of the first task after completing the first task.
The method of claim 42, wherein the third request is first task execution results release request; and

executing the third request, comprises:

releasing the first task execution results of the first task.
The method of claim 42, wherein the third request is first task execution results forward suspending request; and

executing the third request, comprises:

suspending forwarding first task execution results of the first task after completing the first task.
The method of claim 42, wherein the third request is first task execution results forwarding request, and

executing the third request, comprises:

forwarding first task execution results of the first task after completing the first task.
The method of claim 42, wherein the third request is first task execution results load request; and

executing the third request, comprises:

loading first task execution results of the first task after completing the first task.
The method of claim 42, wherein the third request is first terminal processing service function execution terminate request, and

executing the third request, comprises:

terminating first terminal processing service function execution and releasing first terminal processing service function resource.
A machine-readable storage medium storing instructions, wherein when the instructions are executed by one or more processors of a machine, the instructions cause the machine to execute the method of any one of claims 25 to 48.