Method, device and system for managing task instances

Abstract

A method is provided. The method comprises the steps that first task instance information about a first task instance of a first task is obtained, and the first task instance information comprises at least one of the following items: a task instance identifier (MIID) which identifies the first task instance; a task identifier (MID), which is used for identifying the first task, and a task identifier (MID), which is used for identifying the first task; instantiation information describing at least one computing block (CB) instance in the first task instance; execution mode information describing a mode of executing the first task on the first task instance; the authorization information indicates a plurality of devices allowed to access the first task instance; a time validity condition indicating when the first task instance is valid; a spatial validity condition indicating where the first task instance is valid; or application information, the application information indicating at least one application associated with the first task instance and specifying a value of a task parameter associated with the at least one application; and sending a first request to a task open function (MEF) network entity, the first request including the first task instance information, and the first request indicating management related to the first task instance.

Description

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 586,636, filed September 29, 2023, the entire disclosure of which is incorporated herein by reference. Technical Field

[0002] This invention relates generally to the field of wireless communication, and more particularly to a method, apparatus, and system for managing mission instances, as well as a computer-readable storage medium. Background Technology

[0003] With the development of communication technologies, numerous new trends will drive the design of next-generation wireless networks. These trends may include, for example, the widespread deployment of new network infrastructure capabilities (e.g., cloud-native / friendly infrastructure); new (relatively) mature technologies that have made significant progress and have a major impact on society and human life (e.g., large-scale AI models, data privacy, blockchain, etc.); or new applications and services that are widely used in industrial / commercial sectors and by individual users (e.g., AI services, data (sensing) services, digital world services, etc.). Furthermore, more globalized / open / collaborative operations (i.e., more open and collaborative operating methods) are becoming common practice in many fields.

[0004] New expectations and stricter requirements for future networks have also driven a rethinking and development of next-generation wireless networks. These requirements may include privacy and trustworthiness, standardization and simplification, and rapid deployment.

[0005] All of the above factors have driven the research on sixth-generation (6G) network architecture.

[0006] The purpose of describing this background information is to disclose information that the applicant believes may be relevant to the present invention, and it is not intended to acknowledge, nor should it be construed as, any of the foregoing information constituting prior art in relation to the present invention. Summary of the Invention

[0007] This invention provides a method and apparatus for managing task instances.

[0008] According to a first aspect, a method is provided. The method is performed by an application function (AF). The method includes: obtaining first task instance information about a first task instance of a first task, wherein the first task instance information includes at least one of the following elements: a mission instance identifier (MIID) identifying the first task instance; a mission identifier (MID) identifying the first task; instantiation information describing at least one compute block (CB) instance in the first task instance; execution mode information describing a mode for executing the first task on the first task instance; authorization information indicating multiple devices allowed to access the first task instance; a time validity condition indicating when the first task instance is valid; a spatial validity condition indicating where the first task instance is valid; or application information, wherein the application information indicates at least one application associated with the first task instance and specifies values ​​of task parameters associated with the at least one application; and sending a first request to a mission exposure function (MEF) network entity, wherein the first request includes the first task instance information and indicates management related to the first task instance.

[0009] In some embodiments, the management includes: creating a first task instance, the first task instance being created for a first application associated with the first task; the first task instance information includes at least one of a first MID identifying the first task, a first application ID identifying the first application, or an application service ID identifying a service provided by the first application.

[0010] In some embodiments, the first task instance information may further include a first MIID that identifies the first task instance.

[0011] In some embodiments, the method further includes: receiving a first response from the MEF network entity, the first response indicating that the first request has been rejected; the first response further includes a reason for rejection, wherein the reason includes that the first task does not support the first application.

[0012] In some embodiments, the first request indicates that at least one element of the first task instance information of the first task be modified.

[0013] The first beneficial effect is that the AF provides the system (e.g., MEF network entities) with task instance information associated with the task and requests the system to create a task instance for the task. The system will then generate a task instance for the task based on the AF's request. Therefore, it supports AFs with lower capabilities, and the task instances can be managed by the system.

[0014] According to a second aspect, a method is provided. The method is performed by an application function (AF), and includes: sending a fourth request to a mission exposure function (MEF) network entity, wherein the fourth request includes mission selection assistance information (MSAI) for identifying a second mission instance of a second mission and instructing the removal of the second mission instance of the second mission; and receiving a fourth response from the MEF network entity, wherein the fourth response indicates that the second mission instance has been removed.

[0015] In some embodiments, the fourth response includes at least one of an application ID that identifies the application associated with the second task instance or an application service ID that identifies the application associated with the second task instance and the MSAI.

[0016] The second beneficial effect is that the AF provides the system (e.g., MEF network entities) with task instance information associated with the task instance and requests the system to delete the task instance for the task. Therefore, it supports AFs with lower capabilities, and task instances can be managed by the system.

[0017] According to a third aspect, a method is provided. The method is performed by a Mission Exposure Function (MEF) network entity, the method comprising: receiving a first request from an Application Function (AF) network entity, wherein the first request indicates management related to a first mission instance of a first task, and the first request includes first mission instance information about the first mission instance, wherein the first mission instance information includes at least one of the following: a mission instance identifier (MIID) identifying the first mission instance; a mission identifier (MID) identifying the first task; instantiation information describing at least one CB instance in the first mission instance; execution mode information describing a mode for executing the first task on the first mission instance; authorization information indicating multiple devices allowed to access the first mission instance; a time validity condition indicating when the first mission instance is valid; a spatial validity condition indicating where the first mission instance is valid; or application information, wherein the application information indicates at least one application associated with the first mission instance and specifies values ​​of task parameters associated with the at least one application; and obtaining second mission instance information about the first mission instance, wherein the second mission instance information is generated based on the first mission instance information.

[0018] In some embodiments, the management includes: creating a first task instance, the first task instance being created for a first application associated with the first task; the first task instance information includes at least one of a first MID identifying the first task, a first application ID identifying the first application, or an application service ID identifying a service provided by the first application.

[0019] In some embodiments, the first task instance information may further include a first MIID that identifies the first task instance.

[0020] In some embodiments, if the first MIID is not included in the first task instance information, then the first MIID is generated.

[0021] In some embodiments, the method further includes: obtaining mission information about the first mission from a mission data repository (MDR), wherein the mission information includes an application indication indicating at least one application associated with the first mission; and verifying whether the first mission supports the first application based on at least one of the first application ID or the application service ID and the application indication.

[0022] In some embodiments, if the first task does not support the first application, a first response is sent to the AF network entity, wherein the first response indicates that the first request has been rejected.

[0023] In some embodiments, the first response also indicates the reason for rejecting the first request.

[0024] In some embodiments, if the first task supports the first application and the first task instance information does not include the instantiation information, then the at least one computing block (CB) instance is created for the first task instance.

[0025] In some embodiments, creating the at least one CB instance for the first task instance includes: sending a second request to a service control function (SCF) network entity, wherein the second request includes a CB identifier (CBID) that identifies the CB and instructs / indicates / requests the SCF network entity to create a CB instance for the CB; and receiving a second response from the SCF network entity, wherein the second response indicates that the CB instance has been created.

[0026] In some embodiments, the first task includes a task CB, the SCF network entity includes a first SCF network entity, and sending the second request to the SCF network entity includes: sending the second request to the first SCF network entity, wherein the second request includes a task CB identifier (CBID) that identifies the task CB, and instructing / requesting the first SCF network entity to create a task CB instance for the task CB; receiving a second response from the first SCF network entity, wherein the second response indicates that the task CB instance has been created.

[0027] In some embodiments, the second response includes a CB instance identifier (CBIID) that identifies the working CB instance, the working CBIID being generated by the first SCF network entity.

[0028] In some embodiments, the first task includes a sub-mission CB, the SCF network entity includes a second SCF network entity, and sending the second request to the SCF network entity includes: sending the second request to the second SCF network entity, wherein the second request includes a sub-mission CB identifier (CBID) that identifies the sub-mission CB, and instructing / requesting the second SCF network entity to create a sub-mission CB instance for the sub-mission CB; receiving the second response from the second SCF network entity, wherein the second response indicates that the sub-mission CB instance has been created.

[0029] In some embodiments, the method further includes: sending a third request to a mission control function (MCF) network entity, wherein the third request instructs / requests the MCF network entity to establish a communication tunnel between CB instances created for the first mission instance; and receiving a third response from the MCF network entity, wherein the third response indicates that the communication tunnel has been created.

[0030] In some embodiments, the second task instance information includes at least one of the following: the first MIID, the job CBID, the job CBIID, the subtask CBID, or the subtask CBIID.

[0031] In some embodiments, the method further includes sending the second mission instance information to a mission instance repository (MIR) network entity.

[0032] In some embodiments, the method further includes sending a first response to the AF network entity, wherein the first response indicates that the first request has been accepted, and the first response includes mission selection assistance information (MSAI) for selecting the first task instance.

[0033] In some embodiments, the management includes: modifying at least one element of the first task instance information of the first task instance.

[0034] The third beneficial effect is that the AF provides the system (e.g., MEF network entities) with task instance information associated with the task and requests the system to create a task instance for the task. The system will then generate a task instance for the task based on the AF's request. Therefore, it supports AFs with lower capabilities, and task instances can be managed by the system.

[0035] According to a fourth aspect, a method is provided. The method is performed by a mission exposure function (MEF) network entity, and the method includes: receiving a fourth request from an application function (AF) network entity, wherein the fourth request includes mission selection assistance information (MSAI) for identifying a second mission instance of a second mission and instructing the removal of the second mission instance of the second mission; obtaining mission instance information associated with the second mission instance; if the second mission is being executed on the second mission instance, terminating the execution of the second mission through a first mission control function (MCF) network entity; and removing at least one computing block (CB) instance of the second mission instance based on the mission instance information.

[0036] In some embodiments, obtaining the mission instance information associated with the second mission instance includes: sending a second mission instance ID (MIID) identifying the second mission instance to a mission instance repository (MIR) network entity; and receiving the mission instance information from the MIR network entity.

[0037] In some embodiments, the method further includes: sending the second MIID to a target network entity; receiving information identifying the first MCF from the target network entity, wherein the information identifying the first MCF is determined based on the second MIID.

[0038] In some embodiments, removing the at least one CB instance of the second task instance includes: sending a fifth request to a service control function (SCF) network entity, wherein the fifth request includes a CB instance identifier (CBIID) that identifies the CB instance, the CBIID being included in the task instance information, the fifth request requesting the SCF network entity to remove the CB instance; and receiving a fifth response from the SCF network entity, wherein the fifth response indicates that the CB instance has been removed.

[0039] In some embodiments, the fifth response includes the CBIID.

[0040] In some embodiments, the at least one CB instance includes a working CB instance, the SCF network entity includes a third SCF network entity, and removing the at least one CB instance of the second task instance includes: sending the fifth request to the third SCF network entity, wherein the fifth request includes a working CBIID identifying the working CB instance, and the fifth request requests the third SCF network entity to remove the working CB instance; and receiving the fifth response from the third SCF network entity, wherein the fifth response indicates that the working CB instance has been removed.

[0041] In some embodiments, the at least one CB instance includes a subtask CB instance, the SCF network entity includes a fourth SCF network entity, and removing the at least one CB instance of the second task instance includes: sending the fifth request to the fourth SCF network entity, wherein the fifth request includes a subtask CBIID identifying the subtask CB instance, and the fifth request requests the fourth SCF network entity to remove the subtask CB instance; and receiving the fifth response from the fourth SCF network entity, wherein the fourth response indicates that the subtask CB instance has been removed.

[0042] In some embodiments, the method further includes: releasing communication resources associated with the second task instance via a second MCF.

[0043] In some embodiments, the method further includes: sending a sixth request to the MIR network entity, wherein the sixth request includes the second MIID and requests the MIR network entity to remove the task instance information; and receiving a sixth response from the MIR network entity, wherein the sixth response confirms that the task instance information has been removed.

[0044] The fourth beneficial effect is that the AF provides the system (e.g., MEF network entities) with task instance information associated with the task instance and requests the system to delete the task instance for the task. Therefore, it supports AFs with lower capabilities, and task instances can be managed by the system.

[0045] According to a fifth aspect, a method is provided performed by a service control function (SCF) network entity, the method comprising: receiving a second request from a mission exposure function (MEF) network entity, wherein the second request includes a computing block identifier (CBID) identifying a computing block (CB) and instructing / requesting the creation of a CB instance for the CB; and sending a second response to the MEF network entity, wherein the second response indicates that the CB instance has been created.

[0046] In some embodiments, the CB instance identifier (CBIID) that identifies the CB instance is included in the second request or generated by the SCF network entity.

[0047] In some embodiments, the method further includes: creating a CB instance based on information describing the composition and function of the CB, wherein the information corresponds to the CBID.

[0048] In some embodiments, creating the CB instance includes sending the CBIID to a first work resource network entity assigned to the CB instance, wherein the CBIID is used to indicate the first work resource network entity.

[0049] In some embodiments, the method further includes sending association information to the first work resource network entity, wherein the association information indicates that the first work resource is associated with a second work resource network entity allocated to the CB instance.

[0050] In some embodiments, the associated information includes the resource ID or network address of the second working resource network entity.

[0051] In some embodiments, creating the CB instance further includes sending a registration request to a network repository function (NRF) network entity, wherein the registration request includes the resource ID and / or network address of the first working resource network entity, the CB ID, and the association information.

[0052] In some embodiments, the CB includes a work CB and / or a subtask CB.

[0053] The fifth beneficial effect is that the AF provides the system (e.g., MEF network entities) with task instance information associated with the task and requests the system to create a task instance for the task. The system will then generate a task instance for the task based on the AF's request. Therefore, it supports AFs with lower capabilities, and task instances can be managed by the system.

[0054] According to a sixth aspect, a method is provided performed by a service control function (SCF) network entity, the method comprising: receiving a fifth request from a mission exposure function (MEF) network entity, wherein the fifth request includes a CB instance identifier (CBIID) identifying a computing block (CB) instance, and the fifth request instructs / requests the SCF network entity to remove the CB instance; and sending a fifth response to the MEF network entity, wherein the fifth response indicates that the CB instance has been removed.

[0055] In some embodiments, the fifth response includes the CBIID.

[0056] In some embodiments, the method further includes: releasing the work resource network entity associated with the CB instance to remove the CB instance.

[0057] In some embodiments, releasing the Work Resource Network entity includes sending the CBIID to the Work Resource Network entity, wherein the CBIID is used to instruct the Work Resource Network entity to release from the CB instance.

[0058] In some embodiments, the method further includes sending a deregistration request, including the CBIID, to the NRF.

[0059] In some embodiments, the CB instance includes a work CB instance and / or a subtask CB instance.

[0060] The sixth beneficial effect is that the AF provides the system (e.g., MEF network entities) with task instance information associated with the task instance and requests the system to delete the task instance for the task. Therefore, it supports AFs with lower capabilities, and task instances can be managed by the system.

[0061] According to a seventh aspect, a method is provided performed by a mission control function (MCF) network entity, the method comprising: receiving a third request from a mission exposure function (MEF) network entity, wherein the third request instructs / requests the MCF network entity to establish a communication tunnel between CB instances created for a first mission instance; and sending a third response to the MEF network entity, wherein the third response indicates that the communication tunnel has been created.

[0062] In some embodiments, the method further includes: determining how one or more processing service functions (PSFs) belonging to different CB instances should interconnect; and configuring the communication tunnel between the one or more PSFs and one or more GWs.

[0063] The seventh beneficial effect is that the AF provides the system (e.g., MEF network entities) with task instance information associated with the task and requests the system to create a task instance for the task. The system will then generate a task instance for the task based on the AF's request. Therefore, it supports AFs with lower capabilities, and task instances can be managed by the system.

[0064] According to an eighth aspect, a method is provided performed by a mission control function (MCF) network entity, the method comprising: receiving a termination request from a mission exposure function (MEF) network entity, wherein the termination request includes a second mission instance ID (MIID) identifying a second mission instance of a second mission, and instructing / requesting the MEF network entity to terminate the execution of the second mission instance; and sending a termination response to the MEF network entity, wherein the termination response indicates that the execution of the second mission has been terminated.

[0065] The eighth benefit is that the AF provides the system (e.g., MEF network entities) with task instance information associated with the task instance and requests the system to delete the task instance for the task. Therefore, it supports AFs with lower capabilities, and task instances can be managed by the system.

[0066] According to a ninth aspect, an apparatus is provided, the apparatus comprising: at least one processor, wherein the at least one processor is coupled to a memory storing computer program instructions such that the apparatus implements the method according to a first aspect or a second aspect.

[0067] According to a tenth aspect, an apparatus is provided, the apparatus comprising: at least one processor, wherein the at least one processor is coupled to a memory storing computer program instructions such that the apparatus implements the method according to any one of the third or fourth aspects.

[0068] According to the eleventh aspect, an apparatus is provided, the apparatus comprising: at least one processor, wherein the at least one processor is coupled to a memory storing computer program instructions, such that the apparatus implements the method according to the fifth or sixth aspect.

[0069] According to the twelfth aspect, an apparatus is provided, the apparatus comprising: at least one processor, wherein the at least one processor is coupled to a memory storing computer program instructions, such that the apparatus implements the method according to the seventh or eighth aspect.

[0070] According to a thirteenth aspect, a system is provided, the system comprising: the apparatus according to a ninth aspect, the apparatus according to a tenth aspect, the apparatus according to an eleventh aspect, and the apparatus according to a twelfth aspect.

[0071] According to the fourteenth aspect, a computer-readable storage medium is provided, the computer-readable storage medium storing computer program instructions, which, when executed by a computer's processing circuitry, cause the computer to perform the method according to any one of the first, second, third, fourth, fifth, sixth, seventh, or eighth aspects.

[0072] According to the fifteenth aspect, a computer program product is provided, the computer program product having instructions that, when executed by a computer, cause the computer to perform the method according to any one of the first, second, third, fourth, fifth, sixth, seventh, or eighth aspects.

[0073] According to a sixteenth aspect, a chip system is provided, comprising: a processing circuit and a storage medium, wherein the storage medium stores computer program instructions, which, when executed by the processing circuit, cause the chip system to implement the method according to the first aspect, second aspect, third aspect, fourth aspect, fifth aspect, sixth aspect, seventh aspect, or eighth aspect.

[0074] The advantages of any of the designs in aspects nine through sixteen can be found in aspects one through eight, and will not be repeated here.

[0075] Based on the implementation methods provided in the above aspects, the present invention can provide more implementation methods through further combinations. Attached Figure Description

[0076] Figure 1 This illustrates a communication environment in which embodiments of the present invention can be implemented; Figure 2 This illustrates another communication environment in which embodiments of the present invention can be implemented; Figure 3 An apparatus is shown that enables wireless communication with at least one of two devices in a communication system according to some embodiments of the present invention; Figure 4 This is a block diagram of an electronic device (ED) or apparatus according to some embodiments of the present invention; Figure 5 The conceptual structure of a 6G system according to some embodiments of the present invention is shown; Figure 6 A task management architecture according to an embodiment of the present invention is shown; Figure 7 This illustrates the process of NE accessing the application; Figure 8 A signaling diagram for creating a task instance is shown according to some embodiments of the present invention; Figure 9 A signaling diagram illustrating the removal of task instance information according to some embodiments of the present invention is shown; Figure 10 A flowchart is shown of a method performed by an application function (AF) network entity according to some embodiments of the present invention; Figure 11 Another flowchart of a method performed by an application function (AF) network entity according to some embodiments of the present invention is shown; Figure 12 A flowchart is shown of a method performed by a mission exposure function (MEF) network entity according to some embodiments of the present invention; Figure 13 Another flowchart of a method performed by a MEF network entity according to some embodiments of the present invention is shown; Figure 14 A flowchart is shown of a method performed by a service control function (SCF) network entity according to some embodiments of the present invention; Figure 15 Another flowchart of a method performed by an SCF network entity according to some embodiments of the present invention is shown; Figure 16A flowchart is shown of a method performed by a mission control function (MCF) network entity according to some embodiments of the present invention; Figure 17 A flowchart of a method performed by an MCF network entity according to some embodiments of the present invention is shown; Figure 18 This is a schematic diagram of the structure of a network device according to some embodiments of the present invention. Detailed Implementation

[0077] The principles of the present invention will now be described in conjunction with embodiments thereof. It should be understood that these embodiments are described merely to illustrate and assist those skilled in the art in understanding and implementing the invention, and do not impose any limitations on the scope of the invention. The embodiments described herein can be implemented in various ways other than those described below.

[0078] In this invention, references to "an embodiment," "an embodiment," "an exemplary embodiment," "some embodiments," etc., indicate that the described embodiments may include specific features, structures, or characteristics, but not every embodiment needs to include specific features, structures, or characteristics. Furthermore, these phrases do not necessarily refer to the same embodiment. Moreover, when a specific feature, structure, or characteristic is described in connection with an embodiment, it should be understood that, whether explicitly described or not, those skilled in the art will recognize how such features, structures, or characteristics can be combined with other embodiments to achieve the desired effect.

[0079] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long-Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), and Narrow Band Internet of Things (NB-IoT). Furthermore, communication between terminal devices and network devices within a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), sixth-generation (6G) communication protocols and / or any other currently known or future protocols. Embodiments of this invention can be applied to various communication systems. Given the rapid development of communication, future communication technologies and systems embodying this invention will inevitably emerge in the future. The scope of this invention should not be limited to the system described above.

[0080] As used in this document, the term "network device" refers to a node in a communication network through which terminal devices access the network and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR NB (also known as gNB), Remote Radio Unit (RRU), radio header (RH), remote radio head (RRH), relay, integrated access and backhaul (IAB) node, low-power nodes such as femtoseconds and picoseconds, and non-terrestrial network (NTN) or non-terrestrial network devices such as satellite network equipment, low earth orbit (LEO) satellites and geosynchronous earth orbit (GEO) satellites, and spacecraft network equipment, depending on the terminology and technology used. In some embodiments, the radio access network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB host node. The IAB node includes a mobile terminal (IAB-MT) portion that behaves similarly to a UE facing the parent node, and the DU portion of the IAB node that behaves similarly to a base station facing the next-hop IAB node.

[0081] The term "terminal equipment" refers to any terminal device capable of wireless communication. By way of example and not limitation, terminal equipment may also be referred to as communication equipment, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to: mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (e.g., digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, customer-premises equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronic devices, and devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile termination (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0082] Figure 1 An exemplary communication environment in which exemplary embodiments of the present invention can be implemented is shown. Reference Figure 1This diagram, provided as an illustrative example and not as limiting, provides a simplified schematic of a communication system (also referred to as a computing and communication environment) 100. The communication system 100 (which may be a wireless system) includes a radio access network (RAN) 120. RAN 120 may be a next-generation (e.g., sixth-generation, 6G, or later) radio access network, or a traditional (e.g., 5G, 4G, 3G, or second-generation, 2G) radio access network. One or more electronic devices (EDs) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (generally referred to as ED 110) may interconnect with each other or be connected to one or more network nodes (170a and 170b, generally referred to as 170) in the radio access network 120. A core network 130 may be part of the communication system 100 and may depend on or be independent of the radio access technology used in the communication system 100. The communication system 100 may also include a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.

[0083] Generally, communication system 100 enables multiple wireless or wired units to transmit data and other content. Communication system 100 can provide voice, data, video, and / or text content through broadcasting, multicast, ensemble broadcasting, unicast, etc. Furthermore, communication system 100 can 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). These services and / or applications can be mobile broadband (MBB) services, ultra-reliable low-latency communication (URLLC) services, or machine-type communication (MTC) services.

[0084] The communication system 100 can operate by sharing resources such as carrier spectrum bandwidth among its constituent components.

[0085] Figure 2 Another exemplary communication environment in which exemplary embodiments of the present invention can be implemented is shown.

[0086] Communication system 100 may include terrestrial communication systems 120a / 120b and / or non-terrestrial communication system 120c. Communication system 100 can provide high availability and robustness through the joint operation of terrestrial communication systems 120a / 120b and non-terrestrial communication system 120c. For example, integrating non-terrestrial communication system 120c (or components thereof) into terrestrial communication systems 120a / 120b can create a multi-layered heterogeneous network. Heterogeneous networks can achieve better overall performance through efficient multi-link joint operation, more flexible function sharing, and faster physical layer link switching between terrestrial and non-terrestrial networks.

[0087] The terrestrial communication system 120a / 120b and the non-terrestrial communication system 120c can be regarded as subsystems of the communication system.

[0088] Communication system 100 may include ED 110a, ED 110b, ED 110c, ED 110d (generally referred to as ED 110) and RAN 120a and RAN 120b. Additionally, communication system 100 may include a non-terrestrial communication network 120c. Communication system 100 may also include one or more of the following: core network 130, public switched telephone network (PSTN) 140, Internet 150, and other networks 160. RAN 120a and RAN 120b include corresponding RAN nodes such as base stations (BS) 170a and 170b, which are generally referred to as terrestrial transmit and receive points (T-TRP) 170a and 170b (generally referred to as T-TRP 170). In one implementation, the non-terrestrial communication network 120c includes RAN nodes such as access nodes (base stations) 172, which can generally be referred to as a non-terrestrial transmit and receive point (NT-TRP) 172. Based on the similarity of the reference numerals, it can be inferred that the non-terrestrial communication network 120c can be considered a radio access network sharing common operational characteristics with RAN 120a and RAN 120b. In another implementation, 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 NTN device acts as a transport layer device, and the at least one corresponding terrestrial network device acts as a RAN node, communicating with ED 110 through the NTN device. Additionally, an NTN gateway (i.e., a terrestrial network device) may also exist on the ground as a transport layer device communicating with the NTN device, and the RAN node communicates with ED 110 through the NTN device and the NTN gateway. In some embodiments, the NTN gateway and the RAN node may reside in the same device.

[0089] Alternatively or additionally, any ED 110 can be used to connect, access, or communicate with any T-TRP 170a, T-TRP 170b, and NT-TRP 172, the Internet 150, the core network 130, the PSTN 140, other networks 160, or any combination thereof. In some examples, ED 110a can communicate uplink (UL) and / or downlink (DL) with T-TRP 170a via terrestrial air interface 190a. In some examples, ED 110a, ED 110b, ED 110c, and ED 110d can also communicate directly with each other via one or more sidelink (SL) air interfaces 190b. In some examples, ED 110d can communicate uplink and / or downlink with NT-TRP 172 via non-terrestrial air interface 190c.

[0090] Air interfaces 190a and 190b can use similar communication technologies, such as any suitable wireless access technology. For example, communication system 100 can implement one or more channel access methods in air interfaces 190a and 190b, 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), or single-carrier FDMA (SC-FDMA) (also known as discrete Fourier transform spread OFDMA (DFT-s-OFDMA)). Air interfaces 190a and 190b can utilize other higher-dimensional signal spaces, which may involve combinations of orthogonal and / or non-orthogonal dimensions.

[0091] The non-terrestrial air interface 190c enables communication between the ED 110d and one or more NT-TRP 172s via a wireless link or simply through a link. In some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection for multicast transmission between a group of ED 110s and one or more NT-TRP 172s.

[0092] RAN 120a and RAN 120b communicate with core network 130 to provide various services, such as voice, data, and other services, to ED 110a, ED 110b, and ED 110c. RAN 120a and RAN 120b and / or core network 130 may communicate directly or indirectly 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 use the same radio access technology as RAN 120a and / or RAN 120b. Core network 130 may also serve as a gateway access between (i) RAN 120a and RAN 120b and / or ED 110a, ED 110b, and ED 110c and (ii) other networks (e.g., PSTN 140, Internet 150, and other networks 160). Additionally, some or all of ED 110a, ED 110b, and ED 110c may include the ability to communicate with different wireless networks via different wireless links using different wireless technologies and / or protocols. ED 110a, ED 110b, and ED 110c may communicate with a service provider or exchange (not shown) via a wired communication channel and with the Internet 150, rather than wirelessly (or also wirelessly). PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include a network of computers and / or subnets (intranets) and incorporate protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). ED 110a, ED 110b, and ED 110c may be multimode devices capable of operating according to multiple wireless access technologies and include multiple transceivers required to support these technologies.

[0093] Additionally, the communication system 100 may include a sensing agent (not shown) to manage sensing data from ED 110 and / or T-TRP 170a, T-TRP 170b and / or NT-TRP 172. In one implementation, the sensing agent resides within T-TRP 170 and / or NT-TRP 172. In another implementation, the sensing agent is a separate node with an interface for communicating with core network 130 and / or RAN 120 (e.g., T-TRP 170a, T-TRP 170b and / or NT-TRP 172).

[0094] Figure 3An example of a device 310 is shown, according to one embodiment, for wirelessly communicating with at least one of two devices (e.g., device 320a and device 320b, referred to as device 320) in a communication system (e.g., communication system 100). Device 310 may be a UE (e.g., Figure 1 or Figure 2 ED 110 in the example). Device 320a can be a terrestrial network device (e.g., such as ED 110). Figure 2 As shown in T-TRP 170a and T-TRP 170b, device 320b can be a non-terrestrial network device (e.g., such as...). Figure 2 (NT-TRP 172 shown). However, this is not a necessary condition. For example, according to the invention, device 320a can be NT-TRP, 320b can be T-TRP, and both devices 320a and 320b can be either T-TRP or NT-TRP. ED 110 is described below as an example of device 310, T-TRP 170 is described as an example of device 320a, and NT-TRP 172 is described as an example of device 320a. Although there is only one device 310, one device 320a, and one device 320b, note that the number of devices 310 (e.g., ED 110) can be one or more, and the number of devices 320a and / or 320b can be one or more. For example, an ED110 can be served by only one T-TRP 170 (or one NT-TRP 172), 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-TRP 172.

[0095] The ED 110 is used to connect people, objects, and machines. It can be widely used in various scenarios, including cellular communication, 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), digital twins, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, and mobility.

[0096] Each ED 110 represents any suitable end-user equipment for wireless operation and may include (or may be referred to as, but is not limited to): user equipment / device (UE), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), MTC equipment, personal digital assistant (PDA), smartphone, laptop, computer, tablet, wireless sensor, consumer electronics, smart book, vehicle, car, truck, bus, train, or IoT device, wearable device such as a watch, a pair of glasses, a head-mounted device, industrial equipment, or devices within the aforementioned devices (e.g., communication modules, modems, or chips), or any device including the aforementioned devices. Next-generation ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs, hereinafter referred to as T-TRP 170. Also in Figure 3 As shown, the non-terrestrial (NT) device is referred to below 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 used in response to one or more of the following: connectivity availability and connectivity necessity.

[0097] like Figure 3As shown, ED 110 includes at least one processor 210. Only one processor 210 is shown in the figure to avoid clutter. ED 110 may also include a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is shown in the figure to avoid clutter. Alternatively, one, some, or all of the antennas 204 may be panels. The transmitter 201 and receiver 203 may, for example, be integrated as a transceiver. The transceiver is used to modulate data or other content for transmission by at least one antenna 204 or via a network interface controller (NIC). The transceiver is also used to demodulate data or other content received by at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and / or for processing signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure for transmitting and / or receiving wireless or wired signals. ED 110 may include at least one memory 208. For simplicity, only transmitter 201, receiver 203, processor 210, memory 208 and antenna 204 are shown, but ED 110 may include one or more other components.

[0098] Memory 208 stores instructions. Memory 208 may also store data used, generated, or collected by ED 110. For example, memory 208 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein and executed by one or more processing units (e.g., processor 210). Each memory 208 includes any suitable one or more volatile and / or non-volatile storage and retrieval devices. Any suitable type of memory may be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, or on-processor cache.

[0099] ED 110 may also include one or more input / output devices (not shown) or interfaces (e.g., Figure 1 (A wired interface connected to the Internet 150). Input / output devices or interfaces support interaction with users or other devices on the network. Each input / output device or interface includes any suitable structure for providing or receiving information from the user and / or for network interface communication. Suitable structures include, for example, speakers, microphones, keypads, keyboards, displays, touchscreens, etc.

[0100] Processor 210 performs (or controls ED 110 to perform) operations described herein as being performed by ED 110, as shown below and in other parts of the invention. For example, processor 210 performs or controls ED 110 to perform the following operations: receive a transport block (TB), use resources for decoding one TB of the received TB, release resources for decoding another TB of the received TB, and / or receive configuration information for configuration resources. Specifically, operations may include transmission-related operations for preparing uplink transmissions to NT-TRP 172 and / or T-TRP 170, operations related to processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170, and operations related to processing sidelink transmissions to and from another ED 110. Processing operations related to preparing uplink transmissions may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. Processing operations related to downlink transmissions may include transmit / receive beamforming, modulation / demodulation, and encoding / decoding symbols. According to embodiments, downlink transmissions may be received by receiver 203, possibly using receive beamforming, and processor 210 may extract signaling from the downlink transmissions (e.g., by detecting and / or decoding signaling). Examples of signaling may be reference signals transmitted by NT-TRP 172 and / or T-TRP 170. In some embodiments, processor 210 implements transmit beamforming and / or receive beamforming based on beam direction indications received from T-TRP 170, such as beam angle information (BAI). In some embodiments, processor 210 may perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as operations related to detecting synchronization sequences, decoding, and acquiring system information. In some embodiments, processor 210 may perform channel estimation, for example, using reference signals received from NT-TRP 172 and / or T-TRP 170.

[0101] Processor 210 may be part of transmitter 201 and / or receiver 203, but is not shown in the figures. Memory 208 may be part of processor 210, but is not shown in the figures.

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

[0103] In some embodiments, ED 110 may be a device (also referred to as a component) such as a communication module, modem, chip, or chipset, including at least one processor 210 and an interface or at least one pin. In this scenario, transmitter 201 and receiver 203 may be replaced by an interface or at least one pin, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., a chip, memory, or bus). Therefore, sending information to NT-TRP 172 and / or T-TRP 170 and / or another ED 110 can be referred to as sending information to an interface or at least one pin, or as sending information to NT-TRP 172 and / or T-TRP 170 and / or another ED 110 via an interface or at least one pin, while receiving information from NT-TRP 172 and / or T-TRP 170 and / or another ED 110 can be referred to as receiving information from an interface or at least one pin, or as receiving information from NT-TRP 172 and / or T-TRP 170 and / or another ED 110 via an interface or at least one pin. This information may include control signaling and / or data.

[0104] like Figure 3As shown, the T-TRP 170 includes at least one processor 260. Only one processor 260 is shown in the figure to avoid clutter. The T-TRP 170 may also include at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown in the figure to avoid clutter. Alternatively, one, some, or all of the antennas 256 may be a panel. The transmitter 252 and receiver 254 may be integrated as a transceiver. The T-TRP 170 may also include at least one memory 258. The T-TRP 170 may also include a scheduler 253. For simplicity, only the transmitter 252, receiver 254, processor 260, memory 258, antenna 256, and scheduler 253 are shown, but the T-TRP may include one or more other components.

[0105] In some embodiments, the T-TRP 170 may be referred to by other names, such as: base station, base transceiver station (BTS), wireless base station, network node, network device, network-side device, transmit / receive node, Node B, evolved NodeB (eNodeB or eNB), femtocell, next-generation NodeB (gNB), transmission point (TP), site controller, access point (AP), wireless router, relay station, ground node, ground network device, ground base station, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The T-TRP 170 can be a macro base station (BS), micro BS, relay node, host node, etc., or a combination thereof. T-TRP 170 may refer to the aforementioned device or a component within the aforementioned device (e.g., a communication module, modem, or chip).

[0106] In some embodiments, the various parts of T-TRP 170 can be distributed. For example, some modules of T-TRP 170 may be located remotely from the device housing the antenna 256 of T-TRP 170 and may be coupled to the device housing the antenna 256 via a communication link (not shown), sometimes referred to as a fronthaul, such as a 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 ED 110 location determination, resource allocation (scheduling), message generation, and encoding / decoding, which are not necessarily part of the device housing the antenna 256 of T-TRP 170. These modules may also be coupled to other T-TRPs. In some embodiments, T-TRP 170 may actually be multiple T-TRPs operating together to serve ED 110 using methods such as cooperative multicast.

[0107] Processor 260 performs various operations, including those related to: preparing transmissions for downlink transmission to ED 110, processing uplink transmissions received from ED 110, preparing transmissions for backhaul transmission to T-TRP 170 and / or NT-TRP 172, and processing transmissions received from T-TRP 170 and / or NT-TRP 172 via backhaul. Processing operations related to preparing transmissions for downlink or backhaul transmission may include encoding, modulation, precoding (e.g., multiple-input multiple-output (MIMO) precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing received uplink transmissions or transmissions received via backhaul may include receive beamforming, demodulating received symbols, and decoding received symbols. Processor 260 may also perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as generating the contents of a synchronization signal block (SSB) and generating system information. In some embodiments, processor 260 also generates beam direction indications, such as BAI, which can be scheduled for transmission by scheduler 253. Processor 260 performs other network-side processing operations described herein, such as determining the location of ED 110 and the location for deploying NT-TRP 172. In some embodiments, processor 260 may generate signaling, for example, for configuring one or more parameters of ED 110 and / or one or more parameters of NT-TRP 172. Any signaling generated by processor 260 is transmitted by transmitter 252.

[0108] Scheduler 253 may be coupled to or integrated into processor 260. Scheduler 253 may be included in T-TRP 170 or may operate separately from T-TRP 170. Scheduler 253 may schedule uplink, downlink, lateral link, and / or backhaul transmissions, including issuing scheduling grants and / or configuring unscheduled (e.g., "configured grants") resources.

[0109] Memory 258 is used to store information and optional data. Memory 258 stores instructions and data used, generated, or collected by T-TRP 170. For example, memory 258 may store software instructions or modules that implement some or all of the functions and / or embodiments described herein and are executed by processor 260.

[0110] Processor 260 may be part of transmitter 252 and / or receiver 254, but is not shown in the figure. Similarly, processor 260 may implement scheduler 253, but is not shown in the figure. Memory 258 may be part of processor 260, but is not shown in the figure.

[0111] The processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 can each be implemented by the same or different one or more processors, which execute instructions stored in memory (e.g., memory 258). Alternatively, some or all of the processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 can be implemented using dedicated circuitry such as a programmable FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC.

[0112] When T-TRP 170 is a device (also referred to as a component) such as a 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, transmitter 252 and receiver 254 can be replaced by an interface or at least one pin, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., a chip, memory, or bus). Therefore, sending information to NT-TRP 172 and / or T-TRP 170 and / or ED110 can be referred to as sending information to an interface or at least one pin, while receiving information from NT-TRP 172 and / or T-TRP 170 and / or ED 110 can be referred to as receiving information from an interface or at least one pin. This information may include control signaling and / or data.

[0113] Although the NT-TRP 172 is shown as an example of a drone only, the NT-TRP 172 can be implemented in any suitable non-terrestrial form, such as satellites and high-altitude platforms, including international mobile communication base stations and unmanned aerial vehicles. Furthermore, in some embodiments, the NT-TRP 172 may be referred to by other names, such as non-terrestrial node, non-terrestrial network device, or non-terrestrial base station.

[0114] like Figure 3 As shown, the T-TRP 170 may also include at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown in the figure to avoid clutter. Alternatively, one, some, or all of the antennas 256 may be a panel. The transmitter 252 and receiver 254 may be integrated as a transceiver. The T-TRP 170 may also include at least one memory 258. The T-TRP 170 may also include a scheduler 253. For simplicity, only the transmitter 252, receiver 254, processor 260, memory 258, antenna 256, and scheduler 253 are shown, but the T-TRP may include one or more other components.

[0115] like Figure 3 As shown, the NT-TRP 172 includes at least one processor 276. Only one processor 276 is shown in the figure to avoid clutter. 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 shown in the figure to avoid clutter. Alternatively, one, some, or all of the antennas may be panels. The transmitter 272 and receiver 274 may be integrated as a transceiver. The NT-TRP 172 may also include at least one memory 278. The NT-TRP 172 may also include a scheduler. For simplicity, only the transmitter 272, receiver 274, processor 276, memory 278, and antenna 280 are shown, but the NT-TRP may include one or more other components.

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

[0117] Memory 278 is used to store information and optional data. Memory 258 stores instructions and data used, generated, or collected by NT-TRP 172. For example, memory 278 may store software instructions or modules that implement some or all of the functions and / or embodiments described herein and are executed by processor 276.

[0118] Processor 276 may be part of transmitter 272 and / or receiver 274, but is not shown in the figure. Memory 278 may be part of processor 276, but is not shown in the figure.

[0119] The processing components of processor 276, transmitter 272, and receiver 274 can each be implemented by the same or different one or more processors, which execute instructions stored in memory (e.g., memory 278). Alternatively, some or all of the processing components of processor 276, transmitter 272, and receiver 274 can be implemented using dedicated circuitry such as a programmable FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC. In some embodiments, NT-TRP 172 can actually be multiple NT-TRPs operating together to serve ED 110 via cooperative multicast or similar methods.

[0120] When NT-TRP 172 is a device within a machine (e.g., a communication module, modem, chip, or chipset), it includes at least one processor and an interface or at least one pin. In this scenario, transmitter 272 and receiver 257 can be replaced by an interface or at least one pin, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., a chip, memory, or bus). Therefore, sending information to T-TRP 170 and / or another NT-TRP 172 and / or ED 110 can be referred to as sending information to an interface or at least one pin, while receiving information from T-TRP 170 and / or another NT-TRP 172 and / or ED 110 can be referred to as receiving information from an interface or at least one pin. This information may include control signaling and / or data.

[0121] It should be noted that "TRP" as used in this article can refer to either T-TRP or NT-TRP. T-TRP can also be called terrestrial network TRP (TN TRP), and NT-TRP can also be called non-terrestrial network TRP (NTN TRP). T-TRP 170, NT-TRP 172, and / or ED 110 may include other components, but these are omitted for clarity.

[0122] It should be noted that, for simplicity, the term "signaling" used in this document can also be referred to as control signaling, control message, control information, or message. Signaling between a BS (e.g., network node 170) and a terminal or sensing device (e.g., ED 110), or between different terminals or sensing devices (e.g., between ED 110i and ED 110j), can be carried in physical layer signaling (also known as dynamic signaling) and transmitted in the physical layer control channel. For the downlink, physical layer signaling can be referred to as downlink control information (DCI) transmitted in the physical downlink control channel (PDCCH). For the uplink, physical layer signaling can be referred to as uplink control information (UCI) transmitted in the physical uplink control channel (PUCCH). For sidelinks, signaling between different terminals or sensing devices (e.g., between ED 110i and ED110j) can be referred to as sidelink control information (SCI) transmitted in the physical sidelink control channel (PSCCH). This signaling can be carried in higher-layer (e.g., above the physical layer) signaling and transmitted in physical layer data channels, such as the physical downlink shared channel (PDSCH) for downlink signaling, the physical uplink shared channel (PUSCH) for uplink signaling, and the physical sidelink shared channel (PSSCH) for sidelink signaling. Higher-layer signaling can also be referred to as static or semi-static signaling. Higher-layer signaling can be radio resource control (RRC) protocol signaling or media access control-control element (MAC-CE) signaling. Signaling can be included in a combination of physical layer signaling and higher layer signaling.

[0123] It should be noted that in this invention, when "information" is different from "message", the information can be carried in a single message or in more than one single message.

[0124] Figure 4 This is an exemplary block diagram of a device or apparatus according to an exemplary embodiment of the present invention. One or more steps of the method provided in this invention can be performed by corresponding units or modules in the device or apparatus (e.g., ED 110, T-TRP 170, or NT-TRP 172). For example, a signal can be transmitted by a transmitting unit or transmitting module 420. A signal can be received by a receiving unit or receiving module 430. A signal can be processed by a processing unit or processing module 440. Other steps can be performed by an artificial intelligence (AI) or machine learning (ML) module 450.

[0125] like Figure 4 As shown, the device or apparatus may also include an operating system module 410 (e.g., an embedded operating system, firmware, etc.). The corresponding units or modules may be implemented using hardware, one or more components or devices executing software, or a combination thereof. For example, one or more of these units or modules may be circuits such as integrated circuits. Examples of integrated circuits include programmable FPGAs, GPUs, or ASICs. For example, one or more of these units or modules may be logic, such as logical functions executed by circuits, by a portion of an integrated circuit, or by software instructions executed by a processor. It should be understood that if these modules are implemented, for example, using software executed by a processor, the processor may retrieve these modules, in whole or in part, as needed, individually or collectively for processing, in one or more instances, and these modules themselves may include instructions for further deployment and instantiation.

[0126] Further details regarding ED 110, T-TRP 170, and NT-TRP 172 are known to those skilled in the art. Therefore, these details are omitted herein.

[0127] As mentioned above, emerging trends have driven research into 6G network architecture. The 6G network architecture needs to support new 6G services that can be developed / deployed by third parties. The proposed 6G network architecture needs to include a more open ecosystem to allow access to technically capable third parties. The proposed 6G network architecture also needs to achieve better trust management.

[0128] Figure 5 An exemplary conceptual structure of a 6G system according to some exemplary embodiments of the present invention is shown.

[0129] The proposed 6G system architecture is defined as supporting 6GXaaS services through technologies such as network function virtualization and network slicing. The 6G system architecture leverages service-based interactions between 6G services.

[0130] 6G systems utilize a service-based architecture and the XaaS concept. XaaS services in 6G systems are divided into three layers.

[0131] The infrastructure layer 510 includes the infrastructure that supports 6G services. This includes wireless network (RAN, CN) infrastructure 511 and 512, cloud / data center infrastructure 514, satellite network 513, storage / database infrastructure 515, and sensing networks, etc. This infrastructure can be provided by a single provider or by multiple providers.

[0132] Each infrastructure can have its own control and management functions (referred to as C / M functions) for infrastructure management. Each of these infrastructures is a type of Infrastructure as a Service.

[0133] The Control and Management (C / M) layer 520 includes control and management services for the 6G system. These services are developed and deployed using slicing technology and leveraging the resources provided by the Infrastructure layer 510. The 6G services in the Control and Management (C / M) layer are as follows: Resource Management (RM) as a Service 521 provides lifecycle management capabilities for various slices and the ability to allocate over-the-air resources to wireless devices.

[0134] 6G tasks are defined as services provided to customers by the 6G system. A task can be a type of service provided by a single 6G XaaS service, or it can be a type of service that requires the coordinated support of multiple XaaS services.

[0135] Mission Management (MM) as a Service (522) provides the capability to program the provision of XaaS services in the service layer to provide mission services.

[0136] The Confederation Network (CONET) as a Service 525 provides the capability for multiple partners to jointly deliver 6G services. This capability is provided through the formation of the consortium, mutual authentication and authorization among partners, and the recording and retrospective negotiation protocols for selected operations performed by partners, with the aim of ensuring a trusted environment for the operation of 6G systems.

[0137] Service Provisioning Management (SPM) provides a capability to control and manage a customer's 6G service access and provide the requested services. This capability can be provided between any pair of XaaS service providers and customers using unified mutual authentication, authorization and policies, key management, QoS guarantees, and billing. Customers include not only end customers in the physical world but also digital representatives in the digital world.

[0138] Connectivity Management (CM) as a Service 524 utilizes 5G connectivity management capabilities, but extends to include the digital world.

[0139] Protocol as a Service (PAS) 526 provides the ability to design custom protocol stacks for services that are identified by the interface.

[0140] Protocol stacks can be predefined for selection on demand, or they can be designed on demand.

[0141] Cybersecurity 527 as a Service provides infrastructure owners with the ability to detect potential security risks to their infrastructure.

[0142] XaaS services in C / M layer 520 support control and management of the 6G system itself, and can also provide support to vertical sectors upon request. For example, RM services can provide air resource management services to the RAN, and can also provide services to vertical sectors, enabling them to allocate air resources to their end customers. XaaS in C / M layer 520 can be deployed using slicing technology.

[0143] Service layer 530 includes 6G services that provide services to customers. In the 6G system conceptual architecture: The AI ​​service is represented as NET4AI as a Service 531. The Artificial Intelligence Service provides AI capabilities that support a wide range of AI applications.

[0144] The service of data collection, data cleaning, data analysis, and data delivery is represented as data analytics and manage (DAM) as a service. This service provides the ability to manage the lifecycle of statistical data, which includes the acquisition, de-identification, analysis, and delivery of data (information statistics from any type of sensor, device, network function, etc.).

[0145] The data storage and sharing service is represented as NET4Data as a Service 532, which provides the ability to reliably store and share data under the control of the data owner, in accordance with the regulations of recognized authorities regarding the control of the identified data.

[0146] The provision of services for the digital world is represented as NET4DW as a Service 535. Digital world services provide the ability to build, control, and manage the digital world. The digital world is defined as the digital realization of the physical world.

[0147] The 6G blockchain service is represented as NET4BC as a service 534. The 6G connectivity service is represented as NET4Con as a service. This service provides the capability to support 6G blockchain services.

[0148] Enhanced connectivity services, such as network for connectivity (NET4CON) service 536.

[0149] This service provides the ability to exchange messages and data between new 6G services.

[0150] All XaaS services in this layer are developed and deployed using resources provided within the infrastructure and leveraging network function virtualization and slicing technologies. The capabilities of each 6G service are provided by its control and management functions, as well as service-specific data processing capabilities.

[0151] In addition to supporting 6G XaaS services at the service layer, the 6G system also leverages the 5G system to provide vertical services. The difference between 6G XaaS services and those in other vertical sectors is that vertical sectors are purely customer-facing and require other XaaS services to operate, with each XaaS service providing its capabilities to the 6G customer.

[0152] Any pair of XaaS services in a 6G system can also be each other's customers and providers. For example, an infrastructure owner provides its resources to XaaS services in Service Layer 530 and C / M Layer 520; RM services may require the capabilities provided by NET4AI 531, DAM 533, and NET4DW 535 for managing their vertical slice resources; CONET service 525 and NET4Data service 532 may require the capabilities provided by NET4BC 534 for operation.

[0153] Key concepts of 6G systems include: - Basic XaaS services are defined by decoupling comprehensive service types into basic XaaS services. Basic XaaS services provide the unique capability to implement specific types of services such as NET4AI service 531, NET4DW service 535, DAM service 533, NET4Data service 532, blockchain service 534, and task management service 522.

[0154] - Allows multiple partners to jointly operate the 6G system.

[0155] - Define the data plane of the 6G system, which includes the data plane processing functions of XaaS services. Programming the interconnection of these functions through the task management service 522 can support various customized customer services.

[0156] -Simplify the 6G system architecture by categorizing basic control and management services and combining them into basic XaaS services in the control and management (C / M) layer 520.

[0157] - Define the C / M plane of the 6G system. The C / M plane includes the C / M function in the XaaS service and may include 5G CP (e.g., AMF), depending on the implementation scheme.

[0158] - Define the Basic Architecture Structure (BAS). BAS is a unified basic structure with a minimum number of interfaces, independent of infrastructure type.

[0159] - Use the BAS concept to simplify the standardization, development and deployment of 6G systems, while supporting various infrastructure deployment scenarios.

[0160] - Adapt to various deployment scenarios by applying BAS or a subset thereof to the infrastructure based on the infrastructure network's capabilities, capacity, and requirements.

[0161] -Utilize the concept of service-based interface (SBI) and apply SBI interaction in the 6G C / M plane and 6G data plane.

[0162] -Simplify the SBI interface by introducing a trusted GW in the data plane and C / M plane of the 6G system.

[0163] From the perspective of 6G system operation, trustworthiness can be improved by introducing the CONET capability, NET4BC capability, and anonymity service provided by the trusted GW in the C / M plane and data plane of the 6G system.

[0164] - From the perspective of protecting end-customer privacy, trustworthiness is enhanced through unified mutual authentication, IDM, data cleansing, and other services provided by SPM, DAM, and 6G blockchain services.

[0165] -Simplify roaming management of wireless devices in the physical and digital worlds through unified certification that includes all participating partners and customers.

[0166] - By defining multiple architectural schemes, it supports multiple development paths from 5G systems to 6G systems without having to spend too much effort on introducing the BAS concept.

[0167] - By leveraging the advantages of SBA and its additional features, backward compatibility is supported. 5G users can use 6G systems to access 5G services.

[0168] - By implementing the concept of anonymous service provision in the trusted GW of 6G C / M plane and 6G data plane, future expansion is supported by adding new XaaS services, while minimizing the impact on standardization and deployment.

[0169] For illustrative purposes, specific exemplary embodiments will be explained in more detail below with reference to the accompanying drawings and the above-described system, core network, ED, and TRP.

[0170] The embodiments described herein illustrate information sufficient to practice the claimed subject matter and explain methods for practicing such subject matter. Upon reading the following description with reference to the accompanying drawings, those skilled in the art will understand the concept of the claimed subject matter and recognize that the application of these concepts is not specifically set forth herein. It should be understood that these concepts and applications are within the scope of the invention and the appended claims.

[0171] The present invention provides systems, apparatus and methods for managing tasks (e.g., task templates, also known as task slice templates).

[0172] In this invention, a task aims to achieve a specified objective, referred to as a task objective, which may include at least one of the following: (1) providing PDU connectivity, and (2) optionally, providing data processing. When the task objective includes providing data processing, the task objective is associated with one or more specific computational problems, and providing data processing means solving one or more specific computational problems. In this case, the task includes one or more computing blocks (CBs) and is associated with a networking process between CBs for solving one or more specific computational problems. A CB within a task corresponds to a computational step defined for the task objective (i.e., solving one or more specific computational problems) and may accordingly be supported by a service (e.g., in the form of a job, a data network (DN), or another task), referred to as a job CB (corresponding to a service in the form of a job), an external CB (corresponding to a service in the form of a data network), or a subtask CB (corresponding to another task). Task management includes programming the task, instantiating the task, and implementing the task objective.

[0173] A task slice is a logical network that provides specific capabilities and characteristics in terms of networking and computation (including storage) for a task. A task slice (CB) corresponds to a subnet of the task slice (called a CB subnet). The CB subnet provides the computational functionality to implement the corresponding computational steps for the task objective. A task slice instance includes a set of network function instances and the required resources (e.g., computation, storage, and network resources) and computational logic (e.g., in terms of parameter configuration); these three elements constitute the deployed task slice. Task services are services between a network entity (NE) (e.g., a UE or AS) and a DN that achieve the task objective (also known as task execution). A task session refers to the association between an NE and a DN, providing task services with the support of task slice instances.

[0174] Unless otherwise specified, "task" and "task slice" are used interchangeably for ease of representation; similarly, "CB" and "CB subnet" are used interchangeably. When a task is instantiated, a task slice instance is created for that task. Therefore, a task slice instance is considered an instance of the task. For each CB within a task, the task instance includes an instance of that CB. If the CB is a working CB, the CB instance resides in the XaaS service module (or, for simplicity, a service module) that supports that working CB; if the CB is an external CB, the CB instance resides in the corresponding DN; if the CB is a subtask CB, the CB instance is an instance of the task corresponding to that CB. A task can have multiple instances. When a CB instance is stateless, it can be shared by multiple task instances. Similarly, when a task instance is stateless, it can be shared (i.e., supported) by multiple applications. A task instance is stateless if and only if it does not contain any stateful CB instances.

[0175] Figure 6 The task management architecture of this invention is illustrated. For example... Figure 6 As shown, architecture 600 includes multiple network functions: AF610, MDR 615, MIR 620, MCF 625, MEF 630, SCF 635, TCF 640, and PSF 645. In some embodiments, any two or more of the above network functions can be integrated into a single network function. For example, MIR 620 and MDR 615 are integrated together. The following will describe... Figure 6 The network functions shown.

[0176] Application function (AF) 610. AF 610 can request the creation / update or removal of task instances, as described in this invention. For example, in this invention, creating a task instance means creating descriptive information about the task instance (also called task instance information). The task instance information can take any form, such as a task instance template. Further details related to the task instance information will be described below. Similarly, updating a task instance means updating the task instance information, such as updating at least one element in the task instance information. Removing a task instance means removing the descriptive information of the task instance, i.e., the task instance information. The nature of the AF is not limited. That is, any network entity can act as an AF. Unless otherwise specified, AF and AF network entity are used interchangeably for ease of representation.

[0177] Mission data repository (MDR) 615. MDR 615 stores mission templates. As described above, a mission template is a form of descriptive information related to a mission. Table 1 below describes the contents of the mission templates. MDR receives mission templates from MEF 630. MEF 630 may receive a portion of the mission template from AF 610 and a portion of the mission template from one or more SCFs. In some embodiments, MDR 615 provides the mission specification or mission template from the mission template to MCF 625 upon request from an MCF. MDR 615 may also provide the mission intent from the mission template to AF 610 via MEF 630, for example, upon subscription or request from AF 610. Unless otherwise specified, MDR and MDR network entity are used interchangeably for ease of representation.

[0178] Mission instance repository (MIR) 620. MIR 620 stores mission instance information. This information describes instances of missions. Unless otherwise specified, MIR and MIR network entities are used interchangeably for ease of representation.

[0179] The Mission Control Function (MCF) 625 controls and coordinates mission execution on mission instances, including starting, pausing, resuming, stopping, and terminating mission execution. The MCF 625 starts, pauses, resumes, stops, or terminates mission execution based on requests from devices or AFs, or on specific events such as time events. The MCF 625 is responsible for establishing data plane paths between one or more CB instances within a mission instance and between mission participants (e.g., UEs) and one or more CB instances to facilitate mission execution. When coordinating mission execution, the MCF 625 triggers one or more executions of one or more CBs of the mission at appropriate times and coordinates access to mission execution by mission participants (e.g., devices). The MCF 625 can control mission execution in conjunction with relevant MM policies, which can be pre-configured at the MCF 625 or obtained by the MCF 625 from another control plane entity. Before terminating mission execution, the mission context related to the mission execution is maintained in both the control plane and data plane. In the absence of ambiguity, MCF and MCF network entity are used interchangeably for ease of representation, unless otherwise specified.

[0180] The Mission Exposure Function (MEF) 630 exposes MM capabilities (services) to the Application Firewall (AF) and authenticates / authorizes AF MM capability requests. Through the MEF, authorized AFs can influence the system's MM decisions. The MEF performs information mapping or parsing on information received from or sent to the AF. Possible information mapping includes mapping external task IDs to internal task IDs, mapping external device IDs to internal device IDs, etc. Possible information parsing includes resolving task intents into task specifications. Unless otherwise specified, the MEF and MEF network entity are used interchangeably for ease of representation.

[0181] Service Control Function (SCF) 635. SCF 635 assists MEF 630 in resolving task intent into task specifications. SCF 635 is also responsible for preparing resources within the corresponding service module, such as one or more control plane resources (TCF) and data plane resources (PSF). During task execution, the prepared resources are used to support the task's execution within the service module. Unless otherwise specified, SCF and SCF network entity are used interchangeably for ease of representation.

[0182] Task control function (TCF) 640. TCF 640 controls and coordinates the execution of tasks, including starting, stopping, and terminating task execution. TCF 640 starts, stops, or terminates task execution as part of task execution based on requests from MCF 625. MCF 625 notifies TCF 640 that a network entity (e.g., a device) is accessing / participating in task execution. Accordingly, TCF 640 can invite the network entity to access / participate in task execution at appropriate times (e.g., when task resources are ready), whereby the network entity can provide data to support task execution or receive data related to task execution. Before terminating task execution, the task context related to the task execution is maintained in the control plane and data plane of the service module. Unless otherwise specified, TCF and TCF network entity are used interchangeably for ease of representation.

[0183] The processing service function (PSF) 645 receives and processes data plane traffic. The PSF 645 can generate data plane traffic. The PSF 645 can send its received (possibly processed) or generated data plane traffic to other PSFs, DNs 660, or UEs 650 through one or more data plane gateways (also known as data gateways, GWs) 655. Data plane gateways are similar to user plane functions (UPFs) in 5G systems.

[0184] Figure 7 The process of NE access application is illustrated. For example... Figure 7 As shown, process 700 involves tasks (slices), task (slice) instances, task sessions, applications, and task execution.

[0185] An application residing in a DN can be a client of a task, providing application services to its users through task execution. A task can support more than one application. Tasks support applications through task instances. A task can act as an application, directly providing application services to application users; in this case, the application is considered to reside within the task. Authorized NEs use task sessions to access applications; these sessions are specific to the DN where the application resides and are supported by task instances. When an application resides within a task, the DN is an abstract DN corresponding to the task. A task instance can be used to support more than one application. Different instances of a task may support different applications.

[0186] exist Figure 7In this example, task (slice) 710 includes three types of task blocks (CBs): job CBs (subnets) 711, subtask CBs (subnets) 712, and external CBs (subnets) 713. To support one or more applications, task (slice) 710 needs to be instantiated as one or more task (slice) instances. In other words, tasks (slices) are instantiated as one or more task (slice) instances to support one or more applications. Figure 7 As can be seen, task (slice) 710 is instantiated as task (slice) instance 720. The task (slice) instance is used for the execution of task (slice) 710. Accordingly, task (slice) instance 720 includes: work CB (subnet) instance 721 corresponding to work CB (subnet) 711, subtask CB (subnet) instance 722 corresponding to subtask CB (subnet) 722, and external CB (subnet) instance 723 corresponding to external CB (subnet) 713. It is understood that task (slice) 710 can also be instantiated as other task (slice) instances. Furthermore, NE 730 accesses the application located in DN 740 through task (slice) instance 720.

[0187] To support an application using task instances as described above, a task session must be established on the task instance. During task session establishment, both the data plane (e.g., one or more data plane paths between one or more CB instances) and the control plane (e.g., one or more MCF 625s and one or more TCF 640s) are configured for the task session. After the task session is established, application-related data traffic can flow through the task instance and be processed under the coordination of the MM framework according to the task-related networking logic (if any). The process of coordinating data flow and processing is called task execution.

[0188] A task session is associated with one or more data sessions on the device. Each data session corresponds to a CB instance within a task instance, and the CB instance corresponds to the task's access point. When a task session is used to access an application, the device interacts with one or more corresponding CB instances using one or more data sessions. Interaction with one or more CB instances involves data traffic and control signals and is part of the task execution associated with the task session.

[0189] exist Figure 7 In the example, a task session is established on task (slice) instance 720. Furthermore, the task session is associated with one or more data sessions. In this example, the task session is associated with a data session between NE 730 and work CB (subnet) instance 721, and another data session between NE 730 and subtask CB (subnet) instance 722, as shown below. Figure 7The solid line with double arrows indicates this. It can be understood that a data session can exist between the NE 730 and the external CB (subnet) instance, but... Figure 7 Not shown in the diagram. Furthermore, applications located in DN 740 can obtain support from task (slice) instances; for example, a subtask CB instance 722 has a session with DN 740, and an external CB instance 723 has another session with DN 740, such as... Figure 7 The dashed line with double arrows is shown in the middle.

[0190] Tasks are identified by a Mission ID (MID). The MID can take the form of a network slice ID. An MID can be associated with one or more CB IDs (CBIDs), each CB ID identifying a CB within a task. When a CB is an external CB, the CBID identifying that CB can take the form of a DNN. When a CB is a subtask CB, the CBID identifying that CB can take the form of a MID. For example, when a task does not include a CB, the MID may not be associated with any CBID.

[0191] An instance of a task is identified by a Mission Instance ID (MIID). The MIID can take the form of a Network Slice Instance ID. An MIID can be associated with one or more CB Instance IDs (CBIIDs). Each of the one or more CBIIDs identifies a CB instance within the task instance. A CB instance is an instance of a CB within a task. When a CB is a subtask CB, the CBIID can take the form of an MIID. For example, when a task does not include a CB, the MIID may not be associated with any CBIID.

[0192] An application is identified by an Application ID (AID), and the services provided by the application are identified by an Application Service ID (ASID). ASIDs can be in the form of a Data Network Neural Network (DNN). A MIID can correspond to one or more ASIDs, indicating that a task instance identified by the MIID is associated with one or more applications identified by one or more ASIDs (i.e., used to support one or more applications identified by one or more ASIDs). In embodiments of this invention, both AID and ASID can identify an application. That is, ASID and AID are equivalent in this invention.

[0193] During the establishment of a task session for an application, a task instance associated with the application is selected. The selection of the task instance can be pre-configured or dynamically determined within the MM framework. In the former case, the MM framework identifies the task instance based on the application's ASID. In the latter case, the MM framework also uses Mission Selection Assistance Information (MSAI) to identify and select the task instance. MSAI can include a list of one or more MIDs or a list of one or more MIIDs. When the MSAI includes a list of one or more MIDs, the MM framework selects the instance of the task identified in that list. When the MSAI includes a list of one or more MIIDs, the MM framework selects the task instance identified in that list. Therefore, a task session can be globally identified using a combination of the application's ASID and the task instance's MIID.

[0194] A task session is established upon a request from an authorized device or AF. When requesting the establishment of a task session, the device or AF provides an ASID and MSAI. At the device, the task session is locally identified using a mission session ID (MSID), which is associated with a task session context. The task session context may include one or more data session IDs (DSIDs), each DSID identifying a data session associated with a working CB instance or DN CB instance (also known as an external CB instance) within the task instance. The task session context may also include one or more MSIDs, each MSID identifying a task session corresponding to a subtask CB instance within the task instance.

[0195] Of the identifiers mentioned above, MSID, DSID, and ASID are understandable to the device. MID and CBID can be embedded in or mapped to other information such as MSAI, and are not directly understandable to the device. MIID and CBIID are network-side concepts and are not visible to the device.

[0196] Task instance information describes an instance of a task (i.e., a task instance). Task instance information includes one or more information elements, as shown in Table 1.

[0197] Table 1 Task Instance Information

[0198] Each of the above information elements in the task information is described in detail below: MIID identifies the task instance. This information can be in the form of a network slice instance ID. Please refer to the previous description for details.

[0199] MID identifies the task. This information can be in the form of a network slice ID. This information can be included in the MIID. Please refer to the preceding description for details.

[0200] Instantiation information, describing the CB instance within the task instance, is generated by the MM. This information includes a list of CBIIDs. Each CBIID identifies a CB instance, which corresponds to a CB within the task. For each CB instance, this information includes a list of one or more CBIAIs, each CBIAI identifying the access point of the CB instance. If two CB instances are to interconnect (e.g., as described in the task information associated with the task), this information may also indicate how the two CB instances interconnect, for example, by including a list of one or more tunnel information entries, where each tunnel information entry corresponds to a tunnel between the access point of one CB instance and the access point of another CB instance. Tunnel information may include, for example, a tunnel ID, a tunnel endpoint ID, and a tunnel protocol ID.

[0201] Execution mode information describes the mode in which tasks are executed on a task instance. This information describes when (e.g., a time of day, a day of the week, a week of the month, a month of the year, etc.) or under what conditions (e.g., in the form of an event ID) task execution on the task instance should begin, pause, resume, stop, or terminate. MCF can obtain execution mode information from MIR as part of the task instance information, and based on this execution mode information, MCF can begin, pause, resume, stop, or terminate task execution when coordinating task execution.

[0202] Authorization information indicates one or more devices permitted to access the task instance. This information may include a list of one or more IDs or network addresses, each ID or network address identifying a device or group of devices. This information may include one or more wildcards. Devices identified in this information, or devices belonging to the device groups identified in this information, are considered permitted to access the task instance.

[0203] Time validity conditions. This information indicates when a task instance is valid or available (e.g., in terms of time). Time validity conditions can be represented by one or more time intervals or durations, each associated with a start time and possibly an end time.

[0204] Spatial validity conditions. This information indicates where a mission instance is valid or available. Spatial validity conditions can be represented by a list of one or more region IDs, a list of one or more Public Land Mobile Network IDs (PLMN IDs), or a list of one or more cell IDs, or a combination thereof, where each region ID identifies a geographic area.

[0205] Application information indicates a list of one or more applications associated with a task instance. This information may include a list of one or more ASIDs, each ASID identifying an application. For each application, the information also specifies one or more values ​​for one or more task parameters of the task. The one or more task parameters are parameters associated with the task and related to the functionality / behavior of one or more task blocks within the task. In this invention, application information may also be referred to as application indication.

[0206] The above reference Figure 6 and Figure 7 This section describes the structure of task instance management and some related concepts. The process of managing task instances will be described below.

[0207] In some embodiments, AF 610 may request management of task instances. For example, AF 610 may send a request to MEF 630 to obtain task instance information about a task instance. The request sent by AF 610 includes descriptive information about the task instance and indicates management related to the task instance. For ease of description and to distinguish between different task instances (e.g., task instances to be created and task instances to be removed), the task instance to be managed (e.g., task instances to be updated or created) is also referred to as the first task instance, and the descriptive information is referred to as first task instance information.

[0208] In some embodiments, the first task instance information may be a part of the entire task instance information of the first task instance. In other words, the first task instance information includes at least one element from the entire task instance information described in Table 1. For example, the first task instance information includes any one or more of the following: a mission instance identifier (MIID) that identifies the first task instance; a mission identifier (MID) that identifies the first task; instantiation information that describes at least one CB instance in the first task instance; execution mode information that describes the mode in which the first task is executed on the first task instance; authorization information that indicates multiple devices allowed to access the first task instance; time validity conditions that indicate when the first task instance is valid; spatial validity conditions that indicate where the first task instance is valid; and application information that indicates at least one application associated with the first task instance and specifies the values ​​of task parameters associated with at least one application. Furthermore, the application information may also include corresponding metadata describing the use of the task parameters.

[0209] In some embodiments, management related to the first task instance includes modifying at least one element of the first description information of the first task instance (e.g., at least one element of the task instance information). For example, changing the time validity condition from one time interval (or duration) to another time interval (or duration). Another example is changing the execution mode information from one mode to another.

[0210] In some embodiments, management related to the first task instance includes: creating a first task instance for a first application associated with the first task, for example, generating second description information based on first description information. For example, the first description information includes the first MID of the first task but does not include instantiation information. In other words, the first description information does not include information describing at least one CB instance in the first task instance. In this case, the MEF generates instantiation information. Furthermore, the MEF generates second description information including instantiation information. The process of generating the second description information will be described in further detail below. The MEF can create at least one CB instance through one or more SCFs, as described below.

[0211] The following is for reference. Figure 8 , Figure 8 Signaling diagram 800 is shown for creating / updating task instances according to some embodiments of the present invention. Signaling diagram 800 relates to AF 610, MDR 615, MIR 620, MCF 625, MEF 630, SCF 635, and NET4CON 536. Figure 8 In this context, SCF 635 represents an XaaS service. The nature of AF 610 is not limited. In some embodiments, any network entity, such as a CPF, AS, or device, can act as an AF.

[0212] like Figure 8 As shown, when AF 610 requests the creation of an instance of a task (e.g., the first task as described above) for an application (i.e., to support the application), task instance information (or at least a portion of the task instance information as shown in Table 1) is provided from AF 610 and stored in MDR 615. Task instance information is associated with an instance of a task. The process of creating a task instance includes one or more of the following steps: In step 810, AF 610 requests the creation of a task instance for the application by sending an AF request to MEF 630. Accordingly, MEF 630 receives the AF request from AF 610.

[0213] In some embodiments, the AF request includes an AF service identifier, which may be associated with or correspond to a contract (e.g., a contract between the system and a party represented by the AF or a party that owns / operates / manages the AF), and is used by MEF 630 to authorize the AF request. Additionally, the AF request includes task instance information. The task instance information includes at least one of a MID identifying the task and an ASID identifying the application (e.g., in the form of a DNN). Alternatively or additionally, the task instance information may include an application ID identifying the application. Alternatively or additionally, the task instance information may include a MIID identifying an instance of the task to be created (i.e., the task instance). The contents of the task instance information are further described in Table 1.

[0214] In this invention, the AF request in steps 810 to 860 is also referred to as the first request. In steps 810 to 860, the instance to be created is also referred to as the first task instance, and the task associated with the instance to be created is also referred to as the first task. The application for which the instance is created is also referred to as the first application. Furthermore, the task instance information included in the AF request is also referred to as the first task instance information.

[0215] In other words, in step 810, AF 610 sends a first request to MEF 630, which instructs management related to a first task instance of the first task (the management in step 810 corresponds to the creation of the first task instance), and the first request includes first task instance information about the first task instance. Furthermore, the first task instance information may include at least one of the information elements described in Table 1. When the AF request instructs the creation of the first task instance, the first task instance information includes at least one of a first MID identifying the first task, a first application ID identifying the first application, or an application service ID identifying a service provided by the first application.

[0216] In some embodiments, the first mission instance information may further include a first mission instance ID (MIID) that identifies the first mission instance.

[0217] In step 820, the MEF 630 verification task is used.

[0218] In some embodiments, the MEF 630 verifies that the task can support the application based on local configuration or by using the MDR 615. For example, the MEF 630 obtains the task template associated with the task from the MDR 615.

[0219] The task template includes one or more information elements, as shown in Table 2.

[0220] Table 2 Task Template

[0221] Each of the above information elements in the task template is described in detail below: MID identifies the task. This information can be in the form of a network slice ID. Please refer to the previous description for details.

[0222] Time validity conditions. This information indicates when a task is valid or available (i.e., can be executed), for example, in terms of time. Time validity conditions can be represented by one or more time intervals or durations, each of which is associated with a start time and / or may also be associated with an end time.

[0223] Spatial validity conditions. This information indicates where the task is valid or available (i.e., can be executed). Spatial validity conditions can be represented by a list of one or more region IDs, a list of one or more PLMN IDs, or a list of one or more cell IDs, or a combination thereof, where each region ID identifies a geographic region.

[0224] Reusability Indicator. This information indicates whether a task is reusable, that is, whether the task can be reused as a CB in another task. If the task is reusable, this information can, for example, indicate who can reuse the task through a list including one or more identifiers and / or one or more wildcards. This information can indicate that the task can be used by any entity. When no reusability indicator is present, it indicates that the task is not reusable.

[0225] Application Indicator. This information identifies one or more applications and indicates whether the task supports those applications. One or more applications can be identified using one or more ASIDs and / or a list of one or more wildcards. This information can indicate that the task can support any application. If no application indicator is present, it indicates that the task can support any application.

[0226] Interface Information. This information describes one or more interfaces through which a task can be accessed, and is generated by the MM. For an interface or a group of interfaces, the interface information may include an ID or name identifying the interface or group of interfaces, and indicating whether the interface or group of interfaces is one or more inbound interfaces or one or more outbound interfaces. Inbound interfaces are provided by the task, while outbound interfaces are provided by the network entity (e.g., device, AS, or NF) accessing the task.

[0227] Task Intent. This information describes the objective of the task, which can be achieved by the task through its execution. The objective of the task can be described using application category information and service issue information.

[0228] Application category information, for example, identifies one or more application categories related to the task through a list including one or more application category IDs. Service issue information, for example, identifies one or more service issues related to the task through a list including one or more issue IDs.

[0229] Task intents can also identify the target service, for example, by including a service ID. One or more application categories and one or more service issues identified in the task intent are associated with the target service.

[0230] Task Specification. This information specifies the networking logic between one or more building blocks of a task used to achieve the task objectives indicated in the task intent. This information may also indicate whether the task is a stateless task.

[0231] The task specification includes component information, workflow information, and access point information, which will be described further below. Any of these items is optional.

[0232] Composition information identifies one or more task blocks (CBs) for a task, and if the task includes multiple CBs, specifies one or more interconnections between the multiple CBs. For each CB, composition information may also indicate one or more associated task parameters. For a working CB, composition information (e.g., using a module ID) indicates the corresponding supporting service module. For an external CB, composition information (e.g., using a DNN) indicates the corresponding supporting DN. For a subtask CB, composition information (e.g., using a MID) indicates the corresponding task. When specifying an interconnection between two CBs, this information can describe the interface between the two CBs. For a CB, composition information can indicate whether the CB is a stateless CB.

[0233] Workflow information specifies the networking logic between CBs identified in the composition information, such as the order or timing of CBs. This information can indicate which CB(s) comes after or before which other CB(s).

[0234] Access point information specifies one or more access points for a task, each access point being a task's CB and identified by a CBID. When specifying an access point, this information may, for example, indicate one or more interfaces associated with that access point as described in the interface information by including one or more IDs or names that identify one or more interfaces.

[0235] In some embodiments, the MEF 630 can interact with the MDR 615 to obtain a task template or an application indication within the task template. For example, the MEF 630 sends a MID to the MDR 615. The MDR 615 uses the MID to identify the task template and, in response, sends the application indication (or the entire task template including the application indication) from the task template to the MEF 630. In this way, the MEF 630 verifies that the task supports the application based on the application indication and the AID.

[0236] As described above, the task is also referred to as the first task. Accordingly, in this step, MEF 630 obtains task information (i.e., the task template as described above) about the first task from MDR 615. Referring to Table 2 as described above, the task information includes an application indication indicating at least one application associated with the first task. Thus, MEF 630 verifies whether the first task supports the first application based on at least one of the first application ID or application service ID and the application indication, wherein the first application ID or application service ID is included in the first task instance information (i.e., the task instance information carried in the first request) as described above. For example, if the application indication indicates at least one application that corresponds to the first application ID or application service ID, then the first task is considered to support the first application. Otherwise, the first task is considered not to support the first application.

[0237] Optionally, if the verification fails, the MEF 630 sends a response to the AF 610 to reject the AF request, and the process ends. The response may include a reason value or code indicating why the AF request was rejected.

[0238] In this invention, this response is also referred to as the first response to the first request. That is, if the first task does not support the first application, which means that the verification failed, the MEF 630 sends a first response to the AF 610, wherein the first response indicates that the first request has been rejected.

[0239] In some embodiments, the first response also indicates a reason for rejecting the first request. For example, the reason might be that the first task does not support the first application.

[0240] In some embodiments, if the first task supports the first application, this indicates that the AF request has been verified, and if the first task instance information (i.e., the information included in the AF request) does not include instantiation information describing at least one CB instance in the first task instance, then the MEF 630 creates at least one computing block (CB) instance for the first task instance. Specifically, the MEF 630 interacts with the SCF 635 to create at least one CB instance. In one implementation, the MEF 630 sends a request to the SCF 635. In this invention, this request is also referred to as a second request, which includes a CB identifier (CBID) that identifies the CB and instructs / requests the SCF network entity to create a CB instance for the CB.

[0241] In some embodiments, the first task includes one or more job CBs and / or one or more subtask CBs. Accordingly, one or more job CB instances and / or one or more subtask CB instances are created.

[0242] The process of creating a working CB instance will be described in more detail below.

[0243] In step 830, MEF 630 generates a MIID to identify the task instance. This step is optional if the task instance information carried in the AF request already includes the MIID.

[0244] In this invention, since the MIID is used to identify the first task instance, the MIID is also called the first MIID.

[0245] In step 840, MEF 630 creates a working CB instance (also known as a CB instance).

[0246] This step is optional if the task (i.e., the first task as described above) does not include work CB.

[0247] In some embodiments, for each work CB of a task identified in the task template and supported by the XaaS service, the MEF 630 interacts with the SCF 635 to create a CB instance for the work CB. The SCF 635 is selected from the SCFs associated with the XaaS service. The CB instance includes work resources (i.e., one or more TCFs, one or more PSFs) allocated to the CB instance and is part of the task instance. The SCF 635 selects work resources from the resources associated with the XaaS service; each work resource may be identified by a resource ID (e.g., TCF ID or PSF ID) or a network address (e.g., IP address or Ethernet address). In this invention, work resources are also referred to as work resource network entities. One or more work resource network entities are allocated to the CB instance. Thus, the CB instance includes the work resource network entities, and tasks associated with the task instance can be executed through the work resource network entities.

[0248] Specifically, step 840 may include at least one of the following sub-steps: In step 8401, MEF 630 sends a CB instance creation request to SCF 635. Accordingly, SCF 635 receives the request. This request includes the CBID, which identifies the CB.

[0249] In some embodiments, the request may include a CBIID that identifies the CB instance and is generated by the MEF 630. In some embodiments, the request may not include a CBIID, which may be generated by the SCF 635.

[0250] In this invention, the CB instance creation request is also referred to as the second request. To easily distinguish between different SCFs used to create work CB instances and subtask CB instances, the SCF used to generate the work CB is also referred to as the first SCF. That is, in this step, the MEF 630 sends a second request to the first SCF. The second request includes a work CB identifier (CBidentifier, CBID) that identifies the work CB and instructs / requests the first SCF to create a work CB instance for the work CB.

[0251] Understandably, if multiple working CB instances need to be created, the MEF 630 can interact with different SCFs to create multiple working CB instances. For example, the MEF 630 can interact with SCF 1 to create one working CB instance and with SCF 2 to create another working CB instance.

[0252] In step 8402, SCF 635 creates a CB instance (i.e., a working CB instance of a working CB).

[0253] For example, upon receiving a CB instance creation request, the SCF 635 creates a CB instance based on information describing the composition and function of the CB, where this information corresponds to the CBID. This information is obtained from the task information, for example, from the task template described in Table 2.

[0254] In some embodiments, if the CB instance creation request (i.e., the second request) does not include a CBIID for identifying the CB instance, the SCF 635 generates a CBIID for identifying the CB instance as described above.

[0255] In some embodiments, the SCF 635 configures a CB instance by configuring each working resource in the CB instance.

[0256] For example, SCF 635 sends a CBIID to the first working resource (network entity) in a CB instance, where the CBIID indicates that the first working resource (network entity) is assigned to the CB instance. Here, the first working resource (network entity) refers to any working resource (network entity) in the CB instance, such as a PSF or TCF.

[0257] In other words, when configuring a working resource (i.e., PSF or TCF) in a CB instance, the SCF 635 provides the working resource with a CBIID (provided by the MEF 630 in step 8401, or generated by the SCF 635), indicating that the working resource is assigned to the CB instance (identified by the CBIID).

[0258] Optionally, the SCF 635 can send association information to the first working resource, wherein the association information indicates that the first working resource is associated with a second working resource within the CB instance. Furthermore, the association information may include the resource ID or network address of the second working resource. Here, the second working resource refers to a working resource that is different from the first working resource in the CB instance.

[0259] In other words, when configuring working resources (i.e., PSFs or TCFs) in a CB instance, the SCF 635 can provide association information indicating that a working resource is associated with one or more other working resources (e.g., one or more TCFs or one or more PSFs) within the CB instance. The association information may include one or more resource IDs or one or more network addresses of the other working resources. The association between two working resources, PSF and TCF, indicates that the PSF can be controlled or managed by the TCF, for example, for tunnel endpoint configuration as described in step 860.

[0260] In some embodiments, after configuring the working resources as described above, the SCF 635 can register the working resources with the network repository function (NRF).

[0261] In one implementation, the SCF 635 sends a registration request to the NRF, wherein the registration request includes the resource ID and / or network address, CBID, and association information of the first working resource. In other words, the SCF 635 sends registration information to the NRF, wherein the registration information includes the resource ID and / or network address, CBID, and association information of the working resource (e.g., the first working resource).

[0262] In another implementation, the work resource performs self-registration with the NRF. In other words, alternatively, after being configured by SCF 635 as described above, the work resource performs self-registration with the NRF. For example, the work resource sends registration information to the NRF itself.

[0263] Accordingly, the NRF stores the registration information of the working resource, whether the registration information is received from the SCF 635 or from the working resource, and associates the registration information with the working resource's configuration file (e.g., by storing the registration information as part of the working resource's configuration file).

[0264] In step 8403, SCF 635 sends a CB instance creation response. SCF 635 responds to MEF 630 with the CB instance creation response. This response is sent to MEF 630 and indicates that the CB instance has been created. The CB instance creation response may include the CBIID generated by SCF 635 in step 8402.

[0265] In this invention, since the CB instance creation response is a response to the CB instance creation request, and the CB instance creation request is referred to as the second request, the CB instance creation response in step 8403 is also referred to as the second response.

[0266] The process of creating a job CB instance was described above in step 840. In some cases, a task (i.e., the first task) may also include at least one subtask CB. In these cases, at least one subtask CB instance corresponding to at least one subtask CB is created. Therefore, step 850 is as follows.

[0267] In step 850, MEF 630 creates a subtask CB instance.

[0268] This step is optional if the task (i.e., the first task) does not include subtask CB.

[0269] In some embodiments, since a subtask CB corresponds to a task, creating a subtask CB instance is equivalent to creating at least one CB instance for a task instance. Therefore, for each subtask CB of a task identified in the task information, the MEF630 generates a subtask instance ID and recursively performs steps 830 to 860 using the subtask instance ID to create the subtask instance. In other words, if the first task instance includes a subtask CB instance, creating a subtask CB instance may include creating at least one job CB instance and / or one or more other subtask CB instances.

[0270] In some embodiments, the subtask instance ID may include the subtask CBID and the first MIID.

[0271] The present invention does not limit the execution order of steps 840 and 850.

[0272] After creating one or more CB instances for the first task instance, further perform step 860, as described below.

[0273] In step 860, MEF 630 establishes communication resources for the task instance (i.e., the first task instance).

[0274] In some embodiments, MEF 630 selects MCF 625 and requests MCF 625 to establish a communication tunnel between the CB instances created for the task instance in steps 840 and 850. This step is optional.

[0275] In one implementation, MEF 630 sends a request (also referred to as a third request in this invention) to MCF 625, wherein the third request instructs / requests MCF 625 to establish a communication tunnel between CB instances that have been created for the first task instance.

[0276] As requested by MEF 630, MCF 625 determines how PSFs belonging to different CB instances should interconnect (e.g., via which data GWs) and configures communication tunnels between the PSFs and one or more data GWs. For example, if the tunnel has an endpoint at the PSF, MCF 625 uses the TCF associated with the PSF to configure the tunnel endpoint at the PSF. If the tunnel has an endpoint at a data GW, MCF 625 can either configure the tunnel endpoint at the data GW directly or use the NET4CON service 536 to configure the tunnel endpoint at the data GW.

[0277] After the communication tunnel is established, the MCF 625 can send a response (also referred to as a third response in this invention) to the MEF 630. Accordingly, the MEF 630 receives a response from the MCF 625, the third response indicating that the communication tunnel has been established.

[0278] The above describes the creation of a job CB instance and a subtask CB instance. In some embodiments, the first task instance may further include an external CB instance to be created. In this case, the MEF 625 can interact with the AF to create the external CB instance. The AF is associated with the external CB and can communicate with... Figure 8 The AF in them is different.

[0279] In step 870, MEF 630 updates (adds) the task instance information.

[0280] In some embodiments, MEF 630 can generate instantiation information based on the CB instance generated through steps 840 to 860. For example, the instantiation information describes the CB instance and includes at least one of the following: a first MIID, a job CBID, a job CBIID, a subtask CBID, or a subtask CBIID. In some embodiments, MEF 630 generates second task instance information. The second task instance information is associated with and corresponds to the first task instance information. The second task instance information may include the first task instance information (or a portion of the first task instance information). The second task instance information also includes instantiation information. In some embodiments, MEF 630 generates second task instance information by updating the first task instance information, the updated first task instance information being the second task instance information. When updating the first task instance information, MEF 630 may insert / add additional information to the first task instance information, wherein the additional information may include, for example, instantiation information.

[0281] In some embodiments, the MEF 630 sends second task instance information to the MIR 620. Accordingly, the MIR 620 stores the second task instance information. The second task instance information is associated with the first task instance, as described above. If the MIR 620 has not yet stored the task instance information of the first task instance, the second task instance information will be stored as the task instance information of the first task instance. If the MIR 620 has already stored the task instance information of the first task instance, this storage will update the content of the task instance information with the content of the second task instance information.

[0282] In other words, in this step, MEF 630 stores the second task instance information in MIR 620. For example, if the MIID is not already included in the first task instance information (e.g., if the MIID is generated by MEF 630 in step 830), MEF 630 includes the MIID in the second task instance information before storing it in MIR 620. In this step, for a CBIID (identifying a job CB instance or subtask CB instance), MEF 630 stores the corresponding CBID and possibly the corresponding MID in MIR 620. This information is associated with the CBIID and included in the second task instance information.

[0283] In step 880, MEF 630 responds to AF 610's AF request. This response is sent to AF 610 and indicates that the AF request is accepted. The response includes an MSAI, which can be used to select a task instance. In this response, MSAI may include MID and / or MIID.

[0284] In this invention, since the response corresponds to the AF request, which is also referred to as the first request, the response here is also called the first response. The first response indicates that the first request has been accepted. Furthermore, the first response includes mission selection assistance information (MSAI) for selecting a first task instance.

[0285] Please note that in this invention, if the AF request fails the verification in step 820, the MEF 630 sends a first response indicating that the AF request has been rejected. If the AF request passes the verification in step 820, the MEF 630 sends a first response indicating that the AF request has been accepted.

[0286] In combination Figure 8 In the described embodiment, task instances of a task can be dynamically created based on a request from AF 610.

[0287] The above reference Figure 8 The process of creating a task instance has been described. The process of removing a task instance will be described below.

[0288] Figure 9 It shows according to Figure 7 The signaling diagram shown illustrates the architecture for removing task instance information. Signaling diagram 900 involves AF610, MDR 615, MIR 620, MCF 625, MEF 630, SCF 635, and NET4CON 536. Figure 8In this context, SCF 635 represents an XaaS service. The nature of AF 610 is not limited. In some embodiments, any network entity, such as a CPF, AS, or device, can act as an AF.

[0289] like Figure 9 As shown, an authorized AF can request the removal of instances of tasks created or used to support an application. When a task instance (i.e., a task instance) is removed, the task instance information associated with the task instance is removed from the MIR 620. Figure 9 The document illustrates the process for removing task instance information, assuming that the MEF 630 can identify whether a task is currently executing on a task instance. This process includes one or more of the following steps: In step 910, AF 610 sends an AF request to MEF 630 to remove the task instance. Accordingly, MEF 630 receives the AF request from AF 610.

[0290] In some embodiments, the AF request includes an MSAI, which can be used to identify an instance of the task (i.e., a task instance). The AF request may also include an ASID, which identifies the application associated with the task instance.

[0291] In this invention, to facilitate the distinction between the AF request in step 810 and the AF request in step 910, the AF requests in steps 910 to 990 are also referred to as the fourth request. The instances to be removed in steps 910 to 990 are also referred to as second task instances. The tasks associated with the instances to be removed in steps 910 to 990 are also referred to as second tasks.

[0292] That is, in step 910, AF 610 sends a fourth request to MEF 630, wherein the fourth request includes an MSAI for identifying the second task instance of the second task and instructs the removal of the second task instance of the second task.

[0293] In step 920, MEF 630 responds to AF 610. This response is sent to AF 610 and acknowledges receipt of the AF request. This step is optional.

[0294] In step 930, MEF 630 obtains task instance information associated with the second task instance.

[0295] In some embodiments, MEF 630 uses MSAI and / or ASID to identify the second task instance. MEF 630 obtains task instance information associated with the second task instance from MIR 620 by providing the MIID identifying the second task instance to MIR 620, and receives the task instance information from MIR 620 in response. The MIID identifying the second task instance is determined based on MSAI and / or ASID.

[0296] In this invention, the MIID that identifies the second task instance as described above is also called the second MIID. That is, the MEF 630 sends the second MIID to the MIR 620, and the MIR 620 sends the task instance information associated with the second task instance to the MEF 630. Accordingly, the MEF 630 receives the task instance information from the MIR 620.

[0297] In step 940, MEF 630 terminates task execution.

[0298] In some embodiments, if a second task is being executed on a second task instance, the MEF 630 terminates the execution of the second task via the MCF. In this invention, the MCF is also referred to as the first MCF.

[0299] In some embodiments, MEF 630 sends a second MIID to a target network entity, and MEF 630 receives information identifying a first MCF from the target network entity. The information identifying the first MCF can be determined by the target network entity based on the second MIID. For example, the target network entity maintains a mapping between the information identifying the first MCF and the second MIID, and after receiving the second MIID from MEF 630, identifies the information identifying the first MCF based on this mapping and sends the information identifying the first MCF to the MEF.

[0300] In other words, if a second task is being executed on a second task instance, the MEF 630 terminates the execution of the second task via the first MCF 625. The MCF 625 can be an MCF that manages task execution and is selected using a MIID. For example, the target network function stores a mapping between MCFs 625 and MIIDs, and the MEF 630 interacts with the target network function to select an MCF 625. For example, the MEF 630 can send a message including the MIID to the target network function, and the target network function can respond to the MEF 630 by sending information identifying the first MCF (e.g., an MCF ID or network address).

[0301] In some embodiments, after task execution has terminated, the MEF 630 removes at least one CB instance of the second task instance based on the task instance information.

[0302] In one implementation, MEF 630 sends a CB instance removal request to SCF, wherein the CB instance removal request includes a CBIID that identifies the CB instance. The CBIID is included in the task instance information as described in step 930, and the CB instance removal request requests SCF to remove the CB instance.

[0303] In this invention, the CB instance removal request is also referred to as the fifth request.

[0304] In some embodiments, the CB instance to be removed can be a working CB instance or a subtask CB instance. The procedures for removing a working CB instance and removing a subtask CB instance are described below.

[0305] In step 950, MEF 630 removes the working CB instance. This step is optional if the second task does not include a working CB.

[0306] For each working CB instance in the second task instance identified in the task instance information, MEF 630 interacts with SCF 635 to remove the working CB instance. The working CB instance corresponds to an XaaS service. SCF 635 is selected from the SCFs associated with the XaaS service.

[0307] Specifically, step 950 includes at least one of the following sub-steps: In step 9501, MEF 630 sends a CB instance removal request to SCF 635. The CB instance removal request includes the CBIID that identifies the CB instance. MEF 630 obtains the CBIID from the task instance information.

[0308] In this invention, the CB instance removal request is also referred to as the fifth request, as described above. Furthermore, the SCF in step 950 is also referred to as the third SCF, to distinguish it from the one mentioned above. Figure 8 The SCF described in [the document] is used to create CB instances.

[0309] In step 9502, after receiving the CB instance removal request, SCF 635 removes the CB instance by releasing the working resources associated with the CB instance (i.e., one or more PSFs and one or more TCFs).

[0310] In some embodiments, for a working resource, the SCF 635 sends a CBIID to the working resource, which is used to indicate that the working resource is released from the CB instance.

[0311] For example, when releasing a working resource (i.e., a PSF or TCF) associated with a CB instance, the SCF 635 provides the working resource with a CBIID, indicating that the working resource is released from the CB instance identified by the CBIID. Accordingly, the working resource removes information related to the CB instance from its local configuration, such as association information describing the association between the working resource and other working resources associated with the CB instance, tunnel endpoint information related to the CB instance, and stops processing data related to the CB instance.

[0312] In some embodiments, the SCF 635 can also deregister the working resources associated with the CB instance to the C / M GW.

[0313] In one implementation, SCT 635 sends a deregistration request, including the CBIID, to the NRF (e.g., the NRF mentioned in the description associated with step 8402, e.g., related to the registration of work resources). Upon this request, the NRF removes all registration information associated with the CBIID.

[0314] Alternatively, in another implementation, each work resource performs self-deregistration with the NRF after being released by the SCF 635 as described above. For example, the work resource sends a deregistration request to the NRF including its CBIID, and the NRF removes only the work resource's registration information associated with its CBIID based on the request.

[0315] In step 9503, SCF 635 responds to MEF 630 with a CB instance removal response. The CB instance removal response is sent to MEF 630, indicating that the CB instance has been removed. The CB instance removal response may include a CBIID.

[0316] In this invention, the CB instance removal response is also referred to as the fifth response.

[0317] In step 960, MEF 630 removes the subtask CB instance.

[0318] This step is optional if the task (i.e., the first task) does not include subtask CB.

[0319] In some embodiments, since a subtask CB corresponds to a task, removing a subtask CB instance is equivalent to removing at least one CB instance from the task instance. That is, each subtask CB instance in a task instance is a task instance, and its corresponding CBIID is in the form of a MIID. For each subtask CB instance in the task instance identified in the task instance information, MEF 630 recursively performs steps 930 to 960 using the corresponding CBIID to remove the subtask CB instance.

[0320] When the subtask CB instance is removed, the MEF 630 can interact with the SCF, which is also referred to as the fourth SCF in this invention. The fourth SCF may be different from or the same as the third SCF described above.

[0321] Note that steps 950 and 960 can be executed in parallel.

[0322] In step 970, MEF 630 releases the communication resources associated with the task instance via the MCF. The MCF can be the MCF that manages task execution and is selected using the MIID. The MCF in this step is also referred to as the second MCF in this invention. The MCF in step 940 and the MCF in this step can be the same MCF. That is, the second MCF can be the same as the first MCF.

[0323] In some embodiments, MEF 630 requests MCF 625 to release communication resources. In one implementation, MEF 630 sends a termination request to a second MCF, wherein the termination request includes a second MIID identifying the second task instance and instructs / requests MEF 630 to terminate the execution of the second task instance. Upon MEF 630's request, MCF 625 releases the communication tunnel associated with the task instance. If the tunnel has an endpoint at PSF, the MCF uses the TCF associated with the PSF to release the tunnel endpoint at the PSF. If the tunnel has an endpoint at data GW, MCF 625 can either directly configure the data GW to release the tunnel endpoint or use the NET4CON service to release the tunnel endpoint at the data GW.

[0324] In addition, the second MCF sends a termination response to the MEF 630, which indicates that the execution of the second task has been terminated.

[0325] In step 980, MEF 630 updates (removes) the task instance information.

[0326] In some embodiments, MEF 630 requests MIR 620 to remove task instance information from MIR 620 by sending a MIID. In this invention, this request is also referred to as the sixth request. Upon receiving this request, MIR 620 uses the MIID to identify the task instance information and deletes the task instance information from storage. MIR 620 responds to MEF 630, confirming that the task instance information has been removed. In this invention, this response is also referred to as the sixth response.

[0327] In step 990, MEF 630 notifies AF 610 that the task has been removed. The notification sent to AF 610 may include MASI and ASID.

[0328] In this invention, since the notification corresponds to the AF request, which is also referred to as the fourth request in step 910, the notification is also referred to as the fourth response.

[0329] Note that if step 920 is not performed, this notification is used as a response to the AF request.

[0330] In combination Figure 9In the described embodiment, task instances of a task can be dynamically removed based on a request from the AF.

[0331] Figure 10 A flowchart of a method performed by an AF network entity according to some embodiments of the present invention is shown. In step 1010, AF 610 obtains first mission instance information about a first mission instance of a first task, wherein the first mission instance information includes at least one of the following: a mission instance identifier (MIID) identifying the first mission instance; a mission identifier (MID) identifying the first task; instantiation information describing at least one CB instance in the first mission instance; execution mode information describing the mode of executing the first task on the first mission instance; authorization information indicating multiple devices allowed to access the first mission instance; time validity conditions indicating when the first mission instance is valid; spatial validity conditions indicating where the first mission instance is valid; or application information, wherein the application information indicates at least one application associated with the first mission instance and specifies the values ​​of mission parameters associated with at least one application; in step 1020, AF 610 sends a first request to a mission exposure function (MEF) network entity, wherein the first request includes the first mission instance information and indicates management related to the first mission instance.

[0332] Figure 11 Another flowchart of a method performed by an AF network entity according to some embodiments of the present invention is shown. In step 1110, AF 610 sends a fourth request to Mission Open Function (MEF) network entity 630, wherein the fourth request includes mission selection assistance information (MSAI) for identifying a second mission instance of a second mission and instructs the removal of the second mission instance of the second mission; in step 1120, AF 610 receives a fourth response from MEF network entity 630, wherein the fourth response indicates that the second mission instance has been removed.

[0333] Figure 12A flowchart of a method performed by a MEF network entity according to some embodiments of the present invention is shown. In step 1210, MEF 630 receives a first request from Application Function (AF) network entity 610, wherein the first request indicates management related to a first task instance of a first task, and the first request includes first task instance information about the first task instance, wherein the first task instance information includes at least one of the following: a task instance identifier (MIID) identifying the first task instance; a task identifier (MID) identifying the first task; instantiation information describing at least one CB instance in the first task instance; execution mode information describing the mode of executing the first task on the first task instance; authorization information indicating multiple devices allowed to access the first task instance; a time validity condition indicating when the first task instance is valid; a spatial validity condition indicating where the first task instance is valid; or application information, wherein the application information indicates at least one application associated with the first task instance and specifies values ​​of task parameters associated with at least one application; in step 1320, MEF 630 obtains second task instance information about the first task instance, wherein the second task instance information is generated based on the first task instance information.

[0334] Figure 13 Another flowchart of a method performed by a MEF network entity according to some embodiments of the present invention is shown. In step 1310, MEF 630 receives a fourth request from an Application Function (AF) network entity, wherein the fourth request includes Task Selection Assist Information (MSAI) for identifying a second task instance of a second task and instructing the removal of the second task instance of the second task; in step 1320, MEF 630 obtains task instance information associated with the second task instance; if the second task is being executed on the second task instance, MEF 630 terminates the execution of the second task through a First Task Control Function (MCF) network entity; based on the task instance information, MEF 630 removes at least one computing block (CB) instance of the second task instance.

[0335] Figure 14 A flowchart of a method performed by an SCF network entity according to some embodiments of the present invention is shown. In step 1410, SCF 635 receives a second request from Mission Open Function (MEF) network entity 630, wherein the second request includes a computing block identifier (CBID) identifying a computing block (CB) and instructs / requests the creation of a CB instance; SCF 635 sends a second response to MEF network entity 630, wherein the second response indicates that the CB instance has been created.

[0336] Figure 15 Another flowchart of a method performed by an SCF network entity according to some embodiments of the present invention is shown. In step 1510, the SCF receives a fifth request from a Mission Open Function (MEF) network entity, wherein the fifth request includes a CB instance identifier (CBIID) that identifies a compute block (CB) instance, and the fifth request instructs / requests the SCF network entity to remove the CB instance; in step 1520, the SCF sends a fifth response to the MEF network entity, wherein the fifth response indicates that the CB instance has been removed.

[0337] Figure 16 A flowchart of a method performed by an MCF network entity according to some embodiments of the present invention is shown. In step 1610, the MCF receives a third request from a Mission Open Function (MEF) network entity, wherein the third request instructs / requests the MCF network entity to establish a communication tunnel between CB instances created for a first mission instance; in step 1620, the MCF sends a third response to the MEF network entity, wherein the third response indicates that the communication tunnel has been created.

[0338] Figure 17 A flowchart of a method performed by an MCF network entity according to some embodiments of the present invention is shown. In step 1710, the MCF receives a termination request from a Mission Open Function (MEF) network entity, wherein the termination request includes a Second Task Instance ID (MIID) identifying a second task instance of a second task, and instructs / requests the MEF network entity to terminate the execution of the second task instance; in step 1720, the MCF sends a termination response to the MEF network entity, wherein the termination response indicates that the execution of the second task has been terminated.

[0339] Some embodiments of the present invention provide a network device. The network device 1600 is used to perform some steps of the task instance management method described in the above embodiments / implementations. For example... Figure 18 As shown, network device 1600 includes a processing module 1601 and a communication module 1602. The processing module 1601 is used to process data units / signals. The communication module 1602 is used to transmit (send) and / or receive data units / signals.

[0340] For example, communication module 1602 may include one or more communication interfaces. Communication module 1602 may be a transceiver module for implementing send and / or receive functions. In this case, communication module 1602 may be an input / output interface or a transceiver.

[0341] In some examples, network device 1600 corresponds to AF 610 and performs... Figure 8Steps 810 and 880 of the method are described above. In this case, the communication module 1602 performs steps 810 and 880.

[0342] In other examples, network device 1600 corresponds to AF 610 and performs... Figure 10 Steps 1010 and 1020 of the method. In this case, communication module 1602 executes step 1020, and processing module 1601 executes step 1010.

[0343] In some other examples, network device 1600 corresponds to AF 610 and performs... Figure 9 Steps 910, 920, and 990 of the method are described. In this case, the communication module 1602 performs steps 910, 920, and 990.

[0344] In some other examples, network device 1600 corresponds to AF 610 and performs... Figure 11 Steps 1110 and 1120 of the method are described above. In this case, the communication module 1602 performs steps 1110 and 1120.

[0345] In some other examples, network device 1600 corresponds to MEF 630 and performs... Figure 8 Steps 810, 820, 830, 8401, 8403, 850, 860, 870, and 880 of the method. In this case, communication module 1602 performs steps 810, 8401, 8403, and 880, and processing module 1601 performs steps 820, 830, 850, 860, and 870.

[0346] In some other examples, network device 1600 corresponds to MEF 630 and performs... Figure 12 Steps 1210 and 1220 of the method. In this case, communication module 1602 performs step 1210, and processing module 1601 performs step 1220.

[0347] In some other examples, network device 1600 corresponds to MEF 630 and performs... Figure 9 Steps 910, 920, 930, 940, 9501, 9503, 960, 970, 980, and 990 of the method. In this case, the communication module 1602 performs steps 910, 920, 9501, 9503, and 990.

[0348] In some other examples, network device 1600 corresponds to MEF 630 and performs... Figure 13 Steps 1310, 1320, 1330, and 1340 of the method. In this case, the communication module 1602 performs step 1310.

[0349] In some other examples, network device 1600 corresponds to SCF 635 and performs... Figure 8 Steps 8401, 8402, 8403, and 860 of the method. In this case, the communication module 1602 performs steps 8401 and 8403, and the processing module 1601 performs steps 8402 and 860.

[0350] In some other examples, network device 1600 corresponds to SCF 635 and performs... Figure 14 Steps 1410 and 1420 of the method are described above. In this case, the communication module 1602 performs steps 1410 and 1420.

[0351] In some other examples, network device 1600 corresponds to SCF 635 and performs... Figure 9 Steps 9501, 9502, 9503, and 970 of the method are described. In this case, the communication module 1602 performs steps 9501 and 9503.

[0352] In some other examples, network device 1600 corresponds to SCF 635 and performs... Figure 15 Steps 1510 and 1520 of the method are described above. In this case, the communication module 1602 performs steps 1510 and 1520.

[0353] It should be noted that the details can be found in the description above, and will not be repeated here.

[0354] In some embodiments, the network device 1600 further includes a memory module 1603 for storing program instructions and / or data. The processing module 1601 can read the program instructions and / or data stored in the memory module 1603 to implement the above-described method.

[0355] It should be noted that the beneficial effects of the network device are the same as those of the task management method described in the above embodiments, and will not be repeated here.

[0356] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When the above embodiments are implemented by software programs, the software programs can be implemented, in whole or in part, in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the computer instructions generate a portion of the processes or functions provided in all the embodiments of the present invention. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or any other programmable device. Computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, computer instructions can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave) methods. A computer-readable storage medium can be any available medium accessible to a computer, or a server, data center, or any other data storage device that includes one or more available media. The available media can be magnetic media (e.g., floppy disks, magnetic disks, or magnetic tapes), optical media (e.g., digital versatile disks (DVDs)), or semiconductor media (e.g., solid-state drives (SSDs)).

[0357] Through the description of the above embodiments, those skilled in the art will clearly recognize that, for the sake of convenience and brevity, the above functional module division is only used as an example. In practical applications, the above functions can be assigned to different functional modules as needed. That is, the internal structure of the device can be divided into different functional modules to perform all or part of the above functions. The specific working process of the above system, device, and module can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0358] In the several embodiments provided in this invention, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the above device embodiments are merely exemplary. For example, the division of functional modules is only a logical functional division. In actual implementation, there may be other division methods. For example, in some embodiments, multiple devices or components may be merged or integrated into another system, or some features may be ignored or not performed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or modules, and may be an electrical connection, a mechanical connection, or other forms of connection.

[0359] Modules described as individual components may or may not be physically separate, and components shown as modules may or may not be physical modules. That is, they may be located in one place or distributed across multiple network modules. Some or all modules can be selected according to actual needs to achieve the purpose of the solution in the embodiments.

[0360] In the embodiments of the present invention, the functional modules can be integrated into a single processing module; the module can also be a separate physical module; or two or more modules can be integrated into a single module. The integrated module can be implemented in hardware or as a software functional module.

[0361] If the integrated module is implemented as a software functional module and sold or used as an independent product, the integrated module can be stored in a readable storage medium. Based on this understanding, the technical solution of this invention, or all or part of the technical solution, can essentially be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this invention. The storage medium includes various types of media capable of storing program code, such as flash memory (USB flash drive), portable hard drives, read-only memory (ROM), random-access memory (RAM), magnetic disks, or optical disks.

[0362] Some embodiments of the present invention provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium). This computer-readable storage medium stores program instructions that, when executed on a network device / second task management device, cause the network device / second task management device to perform one or more steps of the task management method as described in any of the above embodiments.

[0363] For example, computer-readable storage media include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical disks (e.g., compact disks (CDs) or DVDs), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, memory sticks, or key drives). The various computer-readable storage media described in embodiments of this invention can represent one or more devices and / or other machine-readable storage media for storing information. The term "computer-readable storage medium" can include, but is not limited to, wireless channels and various other media capable of storing, including, and / or carrying instructions and / or data.

[0364] Some embodiments of the present invention also provide a computer program product. This computer program product includes program instructions carried on a non-transitory computer-readable storage medium. When executed on a network device / second task management device, the computer program instructions cause the network device / second task management device to perform one or more steps of the task management method as described in the above embodiments.

[0365] The beneficial effects of computer-readable storage media and computer program products are the same as those of the task management methods described in the above embodiments, and will not be repeated here.

[0366] The above description is merely a specific implementation of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications or substitutions falling within the technical scope of the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

[0367] In some aspects of the invention, a computer program comprising instructions is provided. When executed by a processor, these instructions cause the processor to implement the method of the invention.

[0368] In some aspects of the invention, a non-transitory computer-readable medium is provided that stores instructions which, when executed by a processor, cause the processor to implement the method of the invention.

[0369] In some aspects of the present invention, a device / chipset system is provided, comprising components (e.g., at least one processor) for implementing the methods implemented by a UE (or at a UE) of the present invention. The device / chipset system may be a network entity as shown in the present invention, such as an AF, PCF, TCF, device (i.e., terminal device), or a module / component within a network entity. Specifically, at least one processor may execute instructions stored in a computer-readable medium to implement the described methods.

[0370] In some aspects of the invention, a system is provided that includes at least two of the network entities described above (e.g., AF, PCF, TCF, device) shown in the invention.

[0371] In some aspects of the present invention, a method is provided that is performed by a system comprising at least two of the network entities described above as shown in the present invention.

[0372] Please note that the two or more network entities shown in this invention can reside within a physical network entity or be implemented as a single functional entity. In this case, the interaction between the two or more network entities described above may not be required, i.e., one or more corresponding steps can be omitted (one or more corresponding steps are optional).

[0373] Please note that although two or more network entities are shown in this invention, for the exemplary embodiments of this invention, only one network entity may be sufficient. For example, in Figure 7 In the example shown, from the AF's perspective, only AF requests and responses are needed. AF cannot see the operations performed by other network entities (e.g., steps 3 through 5) (or the operations performed by other network entities may be transparent to AF).

[0374] The solutions described in this invention are applicable to next-generation (e.g., sixth generation, 6G or higher) networks, or traditional (e.g., 5G, 4G, 3G or 2G) networks.

[0375] It should be understood that any module, component, or device disclosing executable instructions herein may include or otherwise access one or more non-transitory computer / processor-readable storage media for storing 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 tape cassettes, magnetic tape, disk storage, or other magnetic storage devices; compact disc read-only memory (CD-ROM), digital video disc or digital versatile disc (i.e., DVD), Blu-ray disc™, or other optical storage devices; volatile and non-volatile, removable and non-removable media, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, or other storage technologies implemented in any method or technology. Any such non-transitory computer / processor storage medium may be part of a device or apparatus, or may be accessed or connected to a device or apparatus. Computer / processor-readable / executable instructions used to implement the methods, applications, or modules described herein may be stored by such non-transitory computer / processor-readable storage media or otherwise preserved.

[0376] It should be noted that the message in this invention can be replaced with information, which can be carried in a single message or in more than one single message.

[0377] The terms “device” and “equipment” are used interchangeably.

[0378] In this invention, when used in conjunction with the term "comprising" in the claims and / or specification, the word "a" may mean "one," but it also has the same meaning as "one or more," "at least one," and "one or more," unless otherwise expressly stated. Similarly, the word "another" may mean at least a second or more, unless otherwise expressly stated.

[0379] In this invention, when used before the same term (e.g., ED or operational step), the words "first," "second," etc., do not imply an order or sequence of the terms. For example, without specific indication, "first ED" and "second ED" refer to two different EDs; similarly, without specific indication, "first step" and "second step" refer to two different operational steps, but this does not mean that the first step must occur before the second step. The actual order depends on the logic of the two steps.

[0380] The terms “coupling” or “connection” as used herein may have several different meanings depending on the context in which they are used. For example, the terms “coupling” or “connection” as used herein may mean that two elements or devices are directly connected to each other or connected to each other via mechanical elements through one or more intermediate elements or devices, depending on the specific context.

[0381] Please note that the expression "at least one of A or B" used in this document is interchangeable with the expression "A and / or B". This expression refers to a list in which you can choose either A or B, or A and B. Similarly, the expression "at least one of A, B, or C" used in this document is interchangeable with "A and / or B and / or C" or "A, B, and / or C". This refers to a list in which you can choose: A or B or C, or A and B, or A and C, or B and C, or all of A, B, and C. The same principle applies to longer lists with the same format.

[0382] This invention includes various embodiments, not only method embodiments but also other embodiments, such as apparatus embodiments and embodiments related to non-transitory computer-readable storage media. Embodiments may individually or in combination include the features disclosed herein.

[0383] The terms “receive,” “detect,” and “decode” as used herein may have several different meanings depending on the context in which they are used. For example, without specific indication, the term “receive” may mean that information (e.g., DCI or MAC-CE, RRC signaling, or TB) has been successfully received by the receiving node, meaning that the receiving side correctly detected and decoded the information. In this scenario, “receive” can include both “detect” and “decode,” or it may mean the same thing; for example, “receive paging” means that the paging was correctly decoded and successfully retrieved, and correspondingly, “received paging” means that the receiving side did not detect and / or decode the paging. For example, “not received paging” means that the receiving side attempted to detect and / or decode the paging but failed to retrieve it. The term “receive” may sometimes mean that a signal has arrived at the receiving side, but this does not necessarily mean that the information in the signal has been correctly detected and decoded. In this case, the receiving side needs to detect and decode the signal to obtain the information carried in the signal. In this scenario, “receive,” “detect,” and “decode” may represent different processes by which the receiving side obtains information. Although the invention has referenced illustrative embodiments, it is not intended to be interpreted in a limiting sense. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of the invention, will be apparent to those skilled in the art upon reference to this specification. When combining two or more embodiments, not all features of the embodiments to be combined are necessary for the combination.

[0384] Alternatively or additionally, features disclosed herein in the context of any particular embodiment may be implemented in other embodiments. For example, alternatively or additionally, method embodiments may be implemented in apparatus, system, and / or computer program product embodiments. Furthermore, although embodiments have been described primarily in the context of methods and apparatus, other implementations are contemplated, such as instructions stored on one or more non-transitory computer-readable media. Such media may store programs or instructions to perform any of the methods consistent with the present invention.

Claims

1. A method performed by an application function (AF) network entity, characterized in that, The method includes: Obtain first task instance information about the first task instance, wherein the first task instance information includes at least one of the following elements: The task instance identifier MIID identifies the first task instance; The task identifier MID identifies the first task; Instantiation information, describing at least one computation block CB instance in the first task instance; Execution mode information, describing the mode in which the first task is executed on the first task instance; Authorization information, indicating which devices are permitted to access the first task instance; The time validity condition indicates when the first task instance is valid; Spatial validity conditions indicate where the first task instance is valid; or Application information, wherein the application information indicates at least one application associated with the first task instance and specifies the value of the task parameter associated with the at least one application; Send a first request to the MEF network entity for the mission openness function, wherein the first request includes the first mission instance information and indicates management related to the first mission instance.

2. The method according to claim 1, characterized in that, The management includes: creating a first task instance, wherein the first task instance is created for a first application associated with the first task; The first task instance information includes at least one of the following: a first MID that identifies the first task, a first application ID that identifies the first application, or an application service ID that identifies the service provided by the first application.

3. The method according to claim 2, characterized in that, The first task instance information also includes a first MIID that identifies the first task instance.

4. The method according to any one of claims 1 to 3, characterized in that, Also includes: Receive a first response from the MEF network entity, wherein the first response indicates that the first request has been rejected; the first response includes a reason for rejection, wherein the reason includes that the first task does not support the first application.

5. The method according to any one of claims 1 to 4, characterized in that, The first request instructs modification of at least one element among the elements included in the first task instance information.

6. A method performed by an application function (AF) network entity, characterized in that, The method includes: A fourth request is sent to the MEF network entity for the mission openness function, wherein the fourth request includes Mission Selection Assistance Information (MSAI) for identifying a second mission instance of the second mission; A fourth response is received from the MEF network entity, wherein the fourth response indicates that the second task instance has been removed.

7. The method according to claim 6, characterized in that, The fourth response includes at least one of the following: an application ID that identifies the application associated with the second task instance or an application service ID that identifies the application associated with the second task instance, and the MSAI.

8. A method executed by a Task Open Function (MEF) network entity, characterized in that, The method includes: Receive a first request from an Application Function (AF) network entity, wherein the first request indicates management related to a first task instance of a first task, and the first request includes first task instance information about the first task instance, wherein the first task instance information includes at least one of the following elements: The task instance identifier MIID identifies the first task instance; The task identifier MID identifies the first task; Instantiation information, describing at least one computation block CB instance in the first task instance; Execution mode information, describing the mode in which the first task is executed on the first task instance; Authorization information, indicating which devices are permitted to access the first task instance; The time validity condition indicates when the first task instance is valid; Spatial validity conditions indicate where the first task instance is valid; or Application information, wherein the application information indicates at least one application associated with the first task instance and specifies the value of the task parameter associated with the at least one application; Obtain second task instance information about the first task instance, wherein the second task instance information is generated based on the first task instance information.

9. The method according to claim 8, characterized in that, The management includes: creating a first task instance, wherein the first task instance is created for a first application associated with the first task; The first task instance information includes at least one of the following: a first MID that identifies the first task, a first application ID that identifies the first application, or an application service ID that identifies the service provided by the first application.

10. The method according to claim 9, characterized in that, The first task instance information also includes a first MIID that identifies the first task instance.

11. The method according to claim 9, characterized in that, Also includes: If the first task instance information does not include a first MIID that identifies the first task instance, then the first MIID is generated.

12. The method according to any one of claims 9 to 11, characterized in that, Also includes: Obtain task information about the first task from the task data repository MDR, wherein the task information includes application indications indicating at least one application associated with the first task; Verify whether the first task supports the first application based on at least one of the first application ID or the application service ID and the application indication.

13. The method according to claim 12, characterized in that, Also includes: If the first task does not support the first application, a first response is sent to the AF network entity, wherein the first response indicates that the first request has been rejected.

14. The method according to claim 13, characterized in that, The first response also indicates the reason for rejecting the first request.

15. The method according to any one of claims 9 to 14, characterized in that, Also includes: If the first task supports the first application, and the first task instance information does not include the instantiation information, then the at least one CB instance is created.

16. The method according to claim 15, characterized in that, Creating the at least one CB instance includes: Send a second request to the Service Control Function (SCF) network entity, wherein the second request includes a CB identifier (CBID) that identifies the CB, and instructs the SCF network entity to create a CB instance for the CB; Receive a second response from the SCF network entity, wherein the second response indicates that the CB instance has been created.

17. The method according to claim 16, characterized in that, The first task includes a work CB, the SCF network entity includes a first SCF network entity, and sending the second request to the SCF network entity includes: Send the second request to the first SCF network entity, wherein the second request includes a work CB identifier (CBID) that identifies the work CB, and instructs the first SCF network entity to create a work CB instance for the work CB; Receive the second response from the first SCF network entity, wherein the second response indicates that the working CB instance has been created.

18. The method according to claim 17, characterized in that, The second response includes a Work CB Instance Identifier (CBIID) that identifies the work CB instance, the work CBIID being generated by the first SCF network entity.

19. The method according to any one of claims 15 to 18, characterized in that, The first task includes a subtask CB, the SCF network entity includes a second SCF network entity, and sending the second request to the SCF network entity includes: Send the second request to the second SCF network entity, wherein the second request includes a subtask CB identifier CBID that identifies the subtask CB, and instructs the second SCF network entity to create a subtask CB instance for the subtask CB; Receive the second response from the second SCF network entity, wherein the second response indicates that the subtask CB instance has been created.

20. The method according to any one of claims 15 to 19, characterized in that, Also includes: Send a third request to the Task Control Function (MCF) network entity, wherein the third request instructs the MCF network entity to establish a communication tunnel between CB instances that have been created for the first task instance; Receive a third response from the MCF network entity, wherein the third response indicates that the communication tunnel has been created.

21. The method according to any one of claims 15 to 20, characterized in that, The second task instance information includes at least one of the following: the first MIID, the job CBID, the job CBIID, the subtask CBID, or the subtask CBIID.

22. The method according to claim 21, characterized in that, Also includes: Send the second task instance information to the task instance repository MIR network entity.

23. The method according to claim 22, characterized in that, Also includes: Send a first response to the AF network entity, wherein the first response indicates that the first request has been accepted, and the first response includes Task Selection Assist Information (MSAI) for selecting the first task instance.

24. The method according to claim 23, characterized in that, The management includes: modifying at least one element of the first task instance information of the first task instance.

25. A method executed by the Task Exposure Function (MEF), characterized in that, The method includes: Receive a fourth request from the Application Function (AF) network entity, wherein the fourth request includes Task Selection Assistance Information (MSAI) for identifying a second task instance of the second task and instructing the removal of the second task instance of the second task; Obtain the task instance information associated with the second task instance; If the second task is being executed on the second task instance, the execution of the second task is terminated through the first task control function MCF network entity; Based on the task instance information, remove at least one compute block CB instance of the second task instance.

26. The method according to claim 25, characterized in that, Obtaining the task instance information associated with the second task instance includes: Send a second task instance identifier (MIID) that identifies the second task instance to the task instance repository MIR network entity; Receive the task instance information from the MIR network entity.

27. The method according to claim 26, characterized in that, Also includes: Send the second MIID to the target network entity; Receive information identifying the first MCF from the target network entity, wherein the information identifying the first MCF is determined based on the second MIID.

28. The method according to claim 27, characterized in that, Removing at least one CB instance from the second task instance includes: A fifth request is sent to the Service Control Function (SCF) network entity, wherein the fifth request includes a CB instance identifier (CBIID) that identifies the CB instance, the CBIID being included in the task instance information, and the fifth request requests the SCF network entity to remove the CB instance; A fifth response is received from the SCF network entity, wherein the fifth response indicates that the CB instance has been removed.

29. The method according to claim 28, characterized in that, The fifth response includes the CBIID.

30. The method according to claim 28 or 29, characterized in that, The at least one CB instance includes a working CB instance, the SCF network entity includes a third SCF network entity, and removing the at least one CB instance of the second task instance includes: The fifth request is sent to the third SCF network entity, wherein the fifth request includes a work CBIID that identifies the work CB instance, and the fifth request requests the third SCF network entity to remove the work CB instance; Receive the fifth response from the third SCF network entity, wherein the fifth response indicates that the working CB instance has been removed.

31. The method according to claim 28 or 29, characterized in that, The at least one CB instance includes a subtask CB instance, the SCF network entity includes a fourth SCF network entity, and removing the at least one CB instance of the second task instance includes: The fifth request is sent to the fourth SCF network entity, wherein the fifth request includes a subtask CBIID that identifies the subtask CB instance, and the fifth request requests the fourth SCF network entity to remove the subtask CB instance; Receive the fifth response from the fourth SCF network entity, wherein the fourth response indicates that the subtask CB instance has been removed.

32. The method according to any one of claims 25 to 31, characterized in that, Also includes: Release the communication resources associated with the second task instance through the second MCF.

33. The method according to any one of claims 25 to 32, characterized in that, Also includes: A sixth request is sent to the task instance repository MIR network entity, wherein the sixth request includes the second MIID and requests the MIR network entity to remove the task instance information; A sixth response is received from the MIR network entity, wherein the sixth response confirms that the task instance information has been removed.

34. A method performed by a Service Control Function (SCF) network entity, characterized in that, The method includes: Receive a second request from the Mission Open Function (MEF) network entity, wherein the second request includes a compute block identifier (CBID) that identifies a compute block (CB) and instructs that a CB instance be created for the CB; A second response is sent to the MEF network entity, wherein the second response indicates that the CB instance has been created.

35. The method according to claim 34, characterized in that, Also includes: The CB instance identifier CBIID that identifies the CB instance is included in the second request or generated by the SCF network entity.

36. The method according to claim 35, characterized in that, Also includes: The CB instance is created based on information describing the composition and function of the CB, wherein the information corresponds to the CBID.

37. The method according to claim 35 or 36, characterized in that, Creating the CB instance includes: Send the CBIID to the first work resource network entity, wherein the CBIID indicates that the first work resource network entity is assigned to the CB instance.

38. The method according to claim 37, characterized in that, Also includes: Send association information to the first work resource network entity, wherein the association information indicates that the first work resource network entity is associated with a second work resource network entity allocated to the CB instance.

39. The method according to claim 38, characterized in that, The associated information includes the resource ID or network address of the second working resource network entity.

40. The method according to any one of claims 36 to 39, characterized in that, Creating the CB instance also includes: Send a registration request to the Network Repository Function (NRF) network entity, wherein the registration request includes the resource ID and / or network address of the first working resource network entity, the CBID, and the association information.

41. The method according to any one of claims 36 to 40, characterized in that, The CB includes a work CB and / or a subtask CB.

42. A method performed by a Service Control Function (SCF) network entity, characterized in that, The method includes: A fifth request is received from the Mission Open Function (MEF) network entity, wherein the fifth request includes a CB instance identifier (CBIID) that identifies a compute block (CB) instance, and the fifth request instructs the SCF network entity to remove the CB instance; A fifth response is sent to the MEF network entity, wherein the fifth response indicates that the CB instance has been removed.

43. The method according to claim 42, characterized in that, The fifth response includes the CBIID.

44. The method according to claim 42 or 43, characterized in that, Also includes: Release the work resource network entity associated with the CB instance to remove the CB instance.

45. The method according to claim 44, characterized in that, Releasing the aforementioned work resource network entity includes: Send the CBIID to the Work Resource Network entity, wherein the CBIID is used to instruct the Work Resource Network entity to release from the CB instance.

46. ​​The method according to any one of claims 42 to 45, characterized in that, The method further includes: Send a deregistration request, including the CBIID, to the Network Repository Function (NRF).

47. The method according to any one of claims 42 to 46, characterized in that, The CB instance includes a working CB instance and / or a subtask CB instance.

48. A method executed by a task control function (MCF) network entity, characterized in that, The method includes: Receive a third request from the Mission Open Function (MEF) network entity, wherein the third request instructs the MCF network entity to establish a communication tunnel between CB instances that have been created for the first mission instance; A third response is sent to the MEF network entity, wherein the third response indicates that the communication tunnel has been created.

49. The method according to claim 48, characterized in that, Also includes: Determine how one or more processing service functions (PSFs) belonging to different CB instances should interconnect; Configure the communication tunnel between the one or more PSFs and one or more GWs.

50. A method executed by a task control function (MCF) network entity, characterized in that, The method includes: Receive a termination request from the Mission Open Function (MEF) network entity, wherein the termination request includes a second task instance identifier (MIID) that identifies a second task instance of a second task, and instructs the MEF network entity to terminate the execution of the second task instance. Send a termination response to the MEF network entity, wherein the termination response indicates that the execution of the second task has been terminated.

51. An apparatus, characterized in that, include: At least one processor, wherein the at least one processor is coupled to a memory storing computer program instructions, which, when executed by the at least one processor, cause the apparatus to perform the method according to any one of claims 1 to 5 or claims 6 and 7.

52. An apparatus, characterized in that, include: At least one processor, wherein the at least one processor is coupled to a memory storing computer program instructions, which, when executed by the at least one processor, cause the apparatus to perform the method according to any one of claims 8 to 24 or claims 25 to 33.

53. An apparatus, characterized in that, include: At least one processor coupled to a memory storing computer program instructions, which, when executed by the at least one processor, cause the apparatus to perform the method according to any one of claims 34 to 41 or 42 to 47.

54. An apparatus, characterized in that, include: At least one processor coupled to a memory storing computer program instructions, which, when executed by the at least one processor, cause the apparatus to perform the method according to any one of claims 48 and 49 or claim 50.

55. A system, characterized in that, include: The apparatus according to claim 51, the apparatus according to claim 52, and the apparatus according to claim 53; The apparatus according to claim 54.

56. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by the processing circuitry of a computer, cause the computer to perform the method according to any one of claims 1 to 5, 6 and 7, 8 to 24, 25 to 33, 34 to 41, 42 to 47, 48 and 49, or 50.

57. A computer program product, characterized in that, The computer program product has instructions that, when executed by a computer, cause the computer to perform the method according to any one of claims 1 to 5, 6 and 7, 8 to 24, 25 to 33, 34 to 41, 42 to 47, 48 and 49, or 50.

58. A chip system, characterized in that, The system includes processing circuitry and a storage medium, wherein the storage medium stores computer program instructions that, when executed by the processing circuitry, cause the chip system to implement the method according to any one of claims 1 to 5, 6 and 7, 8 to 24, 25 to 33, 34 to 41, 42 to 47, 48 and 49, or 50.

Images