Information processing method, device and system

Abstract

A method is provided. The method is performed by a network function, the method comprising: the network function sending a request for at least one task and / or at least one task instance to a storage function network entity; the network function receives specifying information from the storage function network entity, where the specifying information is related to the at least one task and / or the at least one task instance. Accordingly, a method executed by a storage function (SF) is provided, the method comprising: the SF receiving a request from a first network function, the request aiming at at least one task and / or at least one task instance; and the SF sends specified information related to the at least one task and / or the at least one task instance to the first network function.

Description

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 586,622, 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 information processing, and 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 deprivation, 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 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 information processing.

[0008] According to a first aspect, a method is provided performed by a first network function (NF) network entity. The method includes: sending a request to the storage function network entity for at least one task and / or at least one task instance; and receiving specified information from the storage function network entity, the specified information relating to the at least one task and / or the at least one task instance, wherein each of the at least one task includes one or more task instances, in the event of a change in information related to the at least one task and / or the at least one task instance.

[0009] In this way, NF can dynamically subscribe to receive information about tasks and / or task instances of interest. Based on the received information, NF can determine whether and how to use the task and / or task instance (e.g., whether the task can solve certain problems, whether to use the task as a subtask to create a new task, avoid using deprecated tasks, use the task instance at the right time and in the right place, etc.).

[0010] In some embodiments, the at least one task is indicated by a task filter in the request and / or the specified information.

[0011] In some embodiments, the task filter includes one of the following: one or more task identifiers (IDs), each task ID identifying one of the at least one tasks; one or more service IDs, each service ID identifying a service corresponding to the at least one task; one or more service issue IDs, each service issue ID identifying a service issue corresponding to the at least one task; one or more application IDs, each application ID identifying an application corresponding to the at least one task; or one or more region IDs, each region ID identifying a region where the at least one task is valid.

[0012] In some embodiments, the at least one task is indicated by a first indication that indicates any task.

[0013] In some embodiments, the at least one task instance is identified by a task instance filter in the request and / or the specified information.

[0014] In some embodiments, the task instance filter includes one of the following: one or more task instance IDs, each task instance ID identifying a task instance among the at least one task instance; one or more task IDs, each task ID identifying a task among the at least one task, wherein for each task among the one or more tasks identified by the one or more task IDs, the one or more task instances of the task belong to the at least one task instance; task selection assistance information, wherein the at least one task instance is determined based on the task selection assistance information; one or more application service IDs or one or more application IDs identifying one or more applications, wherein the task instance associated with the one or more applications identified by the one or more application service IDs or the one or more application IDs belongs to the at least one task instance; or one or more region IDs, each region ID identifying a region in which one task instance among the at least one task instance is valid.

[0015] In some embodiments, the at least one task instance is indicated by a second indication that indicates any task instance.

[0016] In some embodiments, the at least one task includes at least one first task, and the specified information associated with the at least one task includes at least a portion of first descriptive information associated with the at least one first task; and / or the at least one task instance includes at least one first task instance, and the specified information associated with the at least one task instance includes at least a portion of second descriptive information associated with the at least one first task instance.

[0017] In some embodiments, the specified information associated with the at least one task indicates that the first description information associated with the at least one first task has been modified, and the at least a portion of the first description information includes the modified first description information; and / or the specified information associated with the at least one task instance indicates that the second description information associated with the at least one first task instance has been modified, and the at least a portion of the second description information includes the modified second description information.

[0018] In some embodiments, the at least one task includes at least one second task, and the specified information associated with the at least one task includes third descriptive information associated with the at least one second task; and / or the at least one task instance includes at least one second task instance, and the specified information associated with the at least one task instance includes fourth descriptive information associated with the at least one second task instance.

[0019] In some embodiments, the specified information associated with the at least one task indicates that the at least one second task has been created; and / or the specified information associated with the at least one task instance indicates that the at least one second task instance has been created.

[0020] In some embodiments, the at least one task includes at least one third task, and the specified information associated with the at least one task includes fifth descriptive information associated with the at least one third task; and / or the at least one task instance includes at least one third task instance, and the specified information associated with the at least one task instance includes sixth descriptive information associated with the at least one third task instance.

[0021] In some embodiments, the specified information associated with the at least one task indicates that the at least one third task has been deleted; and / or the specified information associated with the at least one task instance indicates that the at least one third task instance has been deleted.

[0022] In some embodiments, any one of the first description information associated with the at least one first task, the third description information associated with the at least one second task, and the fifth description information associated with the at least one third task includes at least one of the following: a task ID of the corresponding task; a time validity condition, wherein the time validity condition indicates when the corresponding task is valid; a spatial validity condition, wherein the spatial validity condition indicates where the corresponding task instance is valid; a reusability indicator, wherein the reusability indicator indicates whether the corresponding task is reusable; an application indicator, wherein the application indicator identifies one or more applications and indicates whether the corresponding task can support the one or more applications; interface information, wherein the interface information describes one or more interfaces through which the corresponding task can be accessed; the task intent of the corresponding task; application category information, wherein the application category information identifies one or more application categories associated with the corresponding task; a task specification, wherein the task specification specifies the networking logic between one or more computing blocks of the corresponding task for implementing the task intent; or one or more task parameters that the user of the corresponding task needs to specify, i.e., one or more task parameters specified by the user of the corresponding task.

[0023] In some embodiments, any one of the second description information associated with the at least one first task instance, the fourth description information associated with the at least one second task instance, and the sixth description information associated with the at least one third task instance includes at least one of the following: a task instance ID of the corresponding task instance; a task ID of the task associated with the corresponding task instance; instantiation information, wherein the instantiation information describes a computing block (CB) instance in the corresponding task instance; execution mode information, wherein the execution mode information describes the mode in which the task is executed on the corresponding task instance; authorization information, wherein the authorization information indicates at least one device that is allowed to access the corresponding task instance; a time validity condition, wherein the time validity condition indicates when the corresponding task instance is valid; a space validity condition, wherein the space validity condition indicates where the corresponding task instance is valid; and application information, wherein the application information indicates at least one application associated with the corresponding task instance, and for each application, the application information specifies at least one task parameter value.

[0024] In some embodiments, the method further includes: obtaining a change type corresponding to the specified information, wherein the change type includes any one of the following: a modification type, indicating that the first description information of the at least one first task and / or the second description information of the at least one first task instance has been modified; an addition type, indicating that the third description information of the at least one second task and / or the fourth description information of the at least one second task instance has been created; or a deletion type, indicating that the fifth description information of the at least one third task and / or the sixth description information of the at least one third task instance has been deleted.

[0025] In some embodiments, the deletion type includes a physical deletion type or a logical deletion type; the physical deletion type indicates that the fifth description information is removed from storage and the third task is unavailable, or the sixth description information is removed from storage and the third task instance is unavailable; the logical deletion indicates that the fifth description information is stored in storage and has been processed, and the third task is deprecated, or the sixth description information is stored in storage and has been processed, and the third task instance is deprecated.

[0026] In some embodiments, the request includes time information for indicating when to send the specified information.

[0027] In some embodiments, the time information includes one or more time intervals, each time interval being associated with a start time and / or an end time.

[0028] In some embodiments, the method further includes sending an indication to the storage function network entity, wherein the indication indicates whether the request corresponds to a one-time response or a series of responses.

[0029] In some embodiments, sending the request to the storage function network entity includes sending the request to the storage function network entity via a second network function.

[0030] In some embodiments, the request is a subscription request, and the response to the request is a notification.

[0031] In some embodiments, the specified information is related to the at least one task, and the storage function network entity is a first storage function network entity that stores task information; and / or the specified information is related to the at least one task instance, and the storage function network entity is a second storage function network entity that stores task instance information.

[0032] In some embodiments, the first storage function network entity and the second storage function network entity are the same network entity.

[0033] According to a second aspect, a method performed by a storage function (SF) is provided, the method comprising: receiving a request from a first network function, wherein the request is directed to at least one task and / or at least one task instance; and, in the event that information relating to the at least one task and / or the at least one task instance changes, sending specified information relating to the at least one task and / or the at least one task instance to the first network function.

[0034] In some embodiments, the method further includes: updating information related to the at least one task, wherein updating the information related to the at least one task includes at least one of the following: modifying at least a portion of first description information related to at least one first task; adding third description information related to at least one second task; or deleting fifth description information related to at least one third task.

[0035] In some embodiments, the method further includes: updating information related to the at least one task instance, wherein updating the information related to the at least one task instance includes at least one of the following: modifying at least a portion of second description information related to at least one first task instance; adding fourth description information related to at least one second task instance; or deleting sixth description information related to at least one third task instance.

[0036] In some embodiments, receiving the request from the first network function includes receiving the request from the first network function via a second network function.

[0037] In some embodiments, the specified information is related to the at least one task, and the storage function network entity is a first storage function network entity that stores task information; and / or the specified information is related to the at least one task instance, and the storage function network entity is a second storage function that stores task instance information.

[0038] According to a third aspect, an apparatus is provided, the apparatus comprising: at least one processor for executing computer program instructions stored in a memory, such that the apparatus implements the method according to the first aspect.

[0039] According to a fourth aspect, an apparatus is provided, the apparatus comprising: at least one processor for executing computer program instructions stored in a memory, such that the apparatus implements the method according to the second aspect.

[0040] According to a fifth aspect, a system is provided, the system comprising: the apparatus according to a third aspect and the apparatus according to a fourth aspect.

[0041] According to a sixth aspect, a computer-readable storage medium stores computer program instructions that, when executed by a computer's processing circuitry, cause the computer to perform the method according to the first aspect or the method according to the second aspect.

[0042] According to a seventh aspect, a computer program product having instructions that, when executed by a computer, cause the computer to perform the method according to a first aspect or the method according to a second aspect.

[0043] According to an eighth aspect, a chip system includes: a processing circuit and a storage medium, wherein the storage medium stores computer program instructions that, when executed by the processing circuit, cause the chip system to implement the method according to either the first or second aspect.

[0044] According to a ninth aspect, a chip is provided. The chip includes logic circuitry and a power supply circuit. The power supply circuitry supplies power to the logic circuitry. The logic circuitry is used to perform the method steps of the first aspect or any possible implementation thereof.

[0045] According to a tenth aspect, a computer device is provided. The computer device includes a memory and a processor. The memory is used to store a computer instruction set, which, when executed by the processor, performs method steps in the first aspect or any possible implementation thereof, or in the second aspect or any possible implementation thereof.

[0046] According to the eleventh aspect, a non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage medium includes computer software instructions that, when executed on a computer device, cause the computer device to perform method steps in the first aspect or any possible implementation thereof, or method steps in the second aspect or any possible implementation thereof.

[0047] The advantages of any of the designs in aspects two through seven can be found in aspect one or different designs of aspect one, and will not be repeated here.

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

[0049] 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 ED or device 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 The diagram illustrates a signaling diagram of subscription information related to a task or task instance according to some embodiments of the present invention; Figure 9 A flowchart illustrating a method performed by a network function (NF) entity according to some embodiments of the present invention is shown; Figure 10 A flowchart is shown illustrating a method performed by a storage function (SF) network entity according to some embodiments of the present invention; Figure 11 This is a schematic diagram of the structure of a network device according to some embodiments of the present invention. Detailed Implementation

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

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

[0052] It should be understood that although terms such as "first," "second," etc., preceding one or more nouns may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another and do not restrict the order of one or more nouns. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the embodiments. The term "and / or" as used herein includes any and all combinations of one or more of the listed terms.

[0053] As used in this document, “at least one of the following: ”, “at least one of ”, and similar wording mean at least one of these elements, or at least any two or more of these elements, or at least all of these elements, wherein the list of two or more elements is connected by “and” or “or”.

[0054] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein include the plural meaning. It should also be understood that the terms “comprising,” “including,” and / or “having” as used herein are used to indicate the presence of the said features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

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

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

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

[0058] 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 communication 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.

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

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

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

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

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

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

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

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

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

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

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

[0070] Figure 3An example of a device 310 is shown that wirelessly communicates 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) according to one embodiment. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0097] 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 for clarity, these are omitted.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0120] The services of data collection, data cleaning, data analysis, and data delivery are 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.).

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

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

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

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

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

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

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

[0128] Any pair of XaaS services in a 6G system can also be both a customer and a provider to each other. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0146] 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 concepts of the claimed subject matter and recognize that the application of these concepts is not specifically mentioned herein. It should be understood that these concepts and applications are within the scope of this invention and the appended claims.

[0147] The present invention provides systems, apparatus and methods for information processing (e.g., task templates, also known as task slice templates).

[0148] 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 used to solve one or more specific computational problems. CBs within a task correspond to computational steps defined for the task objective (i.e., solving one or more specific computational problems) and may be supported accordingly by services (e.g., in the form of tasks, data networks (DNs), or other tasks), referred to as work CBs (corresponding to services in the form of tasks), external CBs (corresponding to services in the form of data networks), or subtask CBs (corresponding to other tasks). Task management includes programming tasks, instantiating tasks, and implementing task objectives.

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

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

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

[0152] Application function (AF) 610. AF 610 can request the creation / update or removal of tasks, as described in this invention. For example, in this invention, creating a task means creating the task's description information. The description information can take any form, such as a task template. Details related to the task template will be further described below. Similarly, updating a task means updating the task's description information, for example, updating at least one element in the task's task template. Removing a task means removing the task's description information, i.e., the task's task template. 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.

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

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

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

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

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

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

[0159] The processing service function (PSF) 645 receives and processes data plane traffic. The PSF 645 can generate data plane traffic. The PSF 645 can transmit 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 analogous to user plane functions (UPFs) in 5G systems. Unless otherwise specified, PSF and PSF network entities are used interchangeably for ease of representation.

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

[0161] 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 can support different applications.

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

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

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

[0165] 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. For example, 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.

[0166] 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 CBID 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.

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

[0168] Applications are identified by an Application Service ID (ASID). ASIDs can be in the form of a DNN. A MIID can correspond to one or more ASIDs, indicating that the 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 some embodiments, applications are identified by an Application ID (AID).

[0169] 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 can identify the task instance based on the application's ASID. For example, if a pre-configured correspondence exists between task instances and application ASIDs, the MM framework can identify the task instance based on this correspondence. 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 an instance of the task identified in that list. For example, any task instance of any task identified in the list can be selected by the MM framework. 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.

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

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

[0172] As mentioned above, a task is associated with a task template that describes the task. For example, a task template includes one or more information elements, as shown in Table 1.

[0173] Table 1 Task Template

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

[0175] Time validity conditions. This information indicates when a task is valid or available (i.e., can be executed) 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 may also be associated with an end time. In some embodiments, each of the one or more time intervals or durations can be associated with a start time and / or an end time.

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

[0177] 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 also indicate, for example, 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.

[0178] Application Indicator. This information identifies one or more applications and indicates whether the task can support 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 means the task can support any application.

[0179] Interface Information. This information describes one or more interfaces through which a task can be accessed. This information 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.

[0180] Task intent information. This information describes the task's goal / intent, which can be achieved by the task through its execution. The task's goal can be described using application category information and service issue information.

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

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

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

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

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

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

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

[0188] The task instance information describes the instance of a task (i.e., the task instance). A task (i.e., a task instance) includes one or more information elements, as shown in Table 2.

[0189] Table 2 Task Instance Information

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

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

[0192] Instantiation information describes the CB instance in the task instance and is generated by MM.

[0193] This information includes a list of CBIIDs. Each CBIID identifies a CB instance, which corresponds to a CB in a task. For a 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.

[0194] Execution mode information describes the mode in which the task is executed on the task instance.

[0195] This information describes when (e.g., in the form of time of day, time of week, time of month, time of year, etc.) or under what conditions (e.g., in the form of event ID) task execution on a task instance should begin, pause, resume, stop, or terminate.

[0196] Authorization information indicates one or more devices that are allowed to access the task instance.

[0197] 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 allowed access to the task instance.

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

[0199] Spatial validity conditions. This information indicates where the task 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 PLMN IDs, or a list of one or more cell IDs, or a combination thereof, where each region ID identifies a geographic region.

[0200] Application information indicates a list of one or more applications associated with the task instance. This information may include a list of one or more ASIDs, each ASID identifying an application. For each application, this information also specifies one or more values ​​for one or more task parameters of the task. The one or more task parameters are specified in the task template associated with the task as described in Table 1. The one or more task parameters are one or more parameters associated with the task and related to the functionality / behavior of one or more CBs in the task.

[0201] The above reference Figure 6 and Figure 7 The structure of task management and some task-related concepts are described below. The process of subscribing to information related to a task or task instance will be described below.

[0202] In some embodiments, task-related descriptive information is stored in a first storage function. Task instance-related descriptive information is stored in a second storage function. The first and second storage functions can be the same or different storage functions. For example, a task template, which serves as task-related descriptive information, is stored in MDR615. Task instance information, which serves as task instance-related descriptive information, is stored in MIR620. It can be seen that in this example, the task template and task instance information are stored in different storage functions. In some cases, information changes may occur. Information change refers to a change in the information, which can be task-related descriptive information (e.g., task template) or task instance-related descriptive information (e.g., task instance information). Information change corresponds to adding, modifying, or deleting information. Furthermore, adding refers to adding one or more new information elements to the task template related to the task, or adding one or more new information elements to the task instance information related to the task instance. For example, the original task template does not include time validity conditions, and time validity conditions are added to the original task template. Similarly, the original task instance information does not include instantiation information, and instantiation information is subsequently generated and added to the task instance information. In the two examples above, information change corresponds to adding. In some cases, "adding" refers not only to adding new information elements to existing task templates or task instance information, but also to creating task templates or task instance information in a storage function. Modification refers to one or more changes related to one or more existing information elements in a task template or task instance information. For example, a task template associated with a task may include a reusability indicator. This reusability indicator could be modified from indicating that the task can be used as a CB in another task to indicating that the task cannot be used as a CB in another task. Similarly, task instance information associated with a task instance may include execution mode information, which could be modified from one mode of executing the task on the task instance to another mode of executing the task on the task instance. In the two examples above, the information changes correspond to modifications of the task and the task template, respectively. Deletion refers to removing at least a portion of a task template or task instance information. For example, a task-related deletion operation could include removing one or more information elements of a task template, or even removing the entire task template. Similarly, a task instance-related deletion operation could include removing one or more information elements of the task instance information, or even removing the entire task instance information. In some embodiments, if task information changes, deletion includes physical deletion or logical deletion. Physical deletion indicates that descriptive information associated with the task (e.g., the task template) is removed from storage. In other words, after physical deletion, the task is no longer available. That is, the status of a task corresponding to physical deletion is "task unavailable".Logical deletion indicates that the descriptive information associated with the task (i.e., the task template) is stored in storage and has been processed. In this case, the state of the task corresponding to logical deletion is that the task is deprecated. In other words, after logical deletion, the task template is still in storage, but the task is considered obsolete or deprecated, and a new task instance should not be created for the task. Similarly, deletion also includes physical deletion or logical deletion if the task instance information changes. Physical deletion indicates that the descriptive information associated with the task instance (e.g., task instance information) is removed from storage. In other words, after physical deletion, the task instance is no longer available. That is, the state of the task instance corresponding to physical deletion is that the task instance is unavailable. Logical deletion indicates that the descriptive information associated with the task instance (i.e., task instance information) is stored in storage and has been processed. In this case, the state of the task instance corresponding to logical deletion is that the task instance is deprecated. In other words, after logical deletion, the task instance information is still in storage, but the task instance is considered obsolete or deprecated, and a new CB instance should not be created for the task instance.

[0203] In some embodiments, an authorized NF can subscribe to receive notifications about changes to one or more information items associated with information of interest. The nature of the NF is not limited. An NF can be a control plane function, such as an MDR 615, MIR 620, MCF625, AF 610, or any other network entity. Depending on whether the information of interest is a task template or task instance information, notifications are sent from the corresponding storage function (i.e., MDR 615 or MIR 620), such as... Figure 6 As shown.

[0204] In some embodiments, a subscription indicates information of interest. When the information of interest is a task template, the information of interest is indicated by a task filter. That is, a task filter identifies one or more tasks of interest. The information of interest includes one or more task templates of the one or more tasks of interest identified by the task filter.

[0205] In some implementations, a task filter includes one or more task IDs, each task ID identifying a task in at least one task (i.e., each task ID identifies the task of interest). In other words, a task filter can be described using a list of one or more MIDs, each MID identifying a task as a task of interest. In some implementations, a task filter includes one or more service IDs, each service ID identifying a service corresponding to a task in at least one task (i.e., each service ID identifies a service corresponding to a task of interest). For example, the service identified by one or more service IDs is related to the task of interest; for instance, there is a correspondence between services and tasks, allowing the task to be determined based on the service ID and the correspondence. In other words, a task whose task intent matches one or more service IDs can be a task of interest. In some implementations, a task filter includes one or more service IDs, each service ID identifying a service issue corresponding to a task in at least one task (i.e., each service ID identifies a service issue corresponding to a task of interest). In this case, a task whose task intent matches one or more service IDs can be a task of interest. In some implementations, a task filter includes one or more application IDs, each application ID identifying an application corresponding to a task in at least one task (i.e., each application ID identifies an application corresponding to a task of interest). As described above, tasks of interest can provide services to applications, establishing a correspondence between tasks and applications. Therefore, tasks of interest can be determined based on application IDs. In other words, a task filter can be described using a list of one or more ASIDs or a list of one or more AIDs, and tasks associated with applications identified by the ASIDs or AIDs in the list are tasks of interest. In some implementations, the task filter includes one or more application category IDs, each identifying the application category corresponding to a task of interest. In other words, a task filter can be described using one or more application category IDs and / or application IDs and / or one or more service issue IDs and / or one or more service IDs. In this case, tasks whose task intent matches one or more application category IDs and / or one or more service issue IDs can be tasks of interest. The task intent of a task is described using a list of one or more application category IDs and / or a list of one or more service issue IDs (in short, one or more issue IDs), as described in the embodiments associated with Table 1.If a list of one or more application category IDs includes one of the application category IDs and / or if a list of one or more service issue IDs includes one of the service issue IDs, then the task intent matches one or more application category IDs and / or one or more service issue IDs. In some implementations, the task filter may include one or more region IDs, each region ID identifying at least one region where the task is valid. That is, the task filter may also be described using one or more regions of interest, each region of interest being identified by a region ID. In this case, tasks valid in one or more regions of interest can be tasks of interest.

[0206] In some embodiments, any task is a task of interest. For example, at least one (task of interest) can be indicated by a first indication that indicates any task. The first indication can take the form of a special task ID, a special service ID, a special application ID, or a special service issue ID. In some examples, a special task can be a virtual task rather than an actual task, and the virtual task ID indicates any task. Similarly, a special service can be a virtual service rather than an actual service, and the virtual service ID indicates any service corresponding to any task. A special application can be a virtual application rather than an actual application, and the virtual application ID indicates any application corresponding to any task. A special service issue can be a virtual service issue rather than a service issue, and the virtual service issue ID indicates any service issue corresponding to any task.

[0207] In some embodiments, when the information of interest is task instance information, the information of interest is indicated by a task instance filter. The task instance filter identifies one or more task instances of interest. The information of interest includes task instance information of the one or more task instances of interest identified by the task instance filter.

[0208] In some implementations, a task instance filter includes one or more task instance IDs, each task instance ID identifying one task instance from at least one task instance (i.e., each task instance ID identifies the task instance of interest). In other words, a task instance filter can be described using a list of one or more MIIDs, each MIID identifying a task instance as the task instance of interest. In some implementations, a task instance filter includes one or more task IDs, each task ID identifying one task from at least one task, and for each task identified by one or more task IDs, one or more task instances of said task belong to at least one task instance. In other words, the task instances of at least one task identified by one or more task IDs are the tasks of interest. That is, a task instance filter can be described using a list of one or more MIDs, each MID identifying a task, and instances of tasks identified by MIDs in the list are the task instances of interest. For example, a task instance filter includes MID 1. Then any instance of the task identified by MID 1 is a task instance of interest. In some implementations, a task instance filter includes MSAI, where the task instances of interest are determined according to the MSAI as described above. In other words, a task instance filter can be described using a list of one or more MSAIs, and task instances selected based on the MSAI in the list are the task instances of interest. In some implementations, a task instance filter includes one or more application service IDs or one or more application IDs that identify one or more applications, wherein task instances associated with the one or more applications identified by the one or more application service IDs or one or more application IDs belong to the at least one task instance. In other words, task instances associated with the one or more applications identified by the one or more application service IDs or one or more application IDs are task instances of interest. Alternatively, a task instance filter can be described using a list of one or more ASIDs or a list of one or more AIDs, and task instances associated with applications identified by the ASIDs or AIDs in the list are task instances of interest. In some implementations, a task instance filter includes one or more region IDs, each region ID identifying a region where at least one task instance is valid. In other words, a task instance filter can also be described using one or more regions of interest, each region of interest can be identified by a region ID. Task instances valid in the one or more regions of interest can be task instances of interest.

[0209] In some embodiments, any task instance is a task instance of interest. For example, at least one (task instance of interest) can be indicated by a second indication that indicates any task instance. The second indication may take the form of a special task instance ID, a special service ID, a special application ID, or a special service issue ID.

[0210] In some embodiments, the storage function notifies the NF of one or more information changes based on the subscription. For information changes, the notification indicates the type of change, such as addition, modification, or deletion. When the information of interest is a task template, the notification includes all or part of the task template content related to the information change, such as spatial validity conditions, temporal validity conditions, reusability indicators, interface information, task intent, application indicators, etc., as described in Table 1. When the information of interest is task instance information, the notification includes all or part of the task instance information related to the information change, as described in Table 2.

[0211] like Figure 8 As shown, the subscription-notification (notification-subscription) process includes some or all of the following steps: In step 810, NF 710 subscribes to receive notifications about information changes associated with one or more tasks of interest by sending a subscription request.

[0212] In some embodiments, as described above, NF 710 sends a request to storage function 720 (e.g., MDR 615 or MIR 620). The subscription request (in steps 810a, 810b, and 810c) indicates information of interest, including information related to a task or task instance. That is, NF 710 sends a request for at least one task and / or at least one task instance. As described above, when the information of interest is related to a task, the task is indicated by a task filter, which includes one of the following: one or more task IDs, each task ID identifying a task in at least one task; one or more service IDs, each service ID identifying a service corresponding to at least one task; one or more service issue IDs, each service issue ID identifying a service issue corresponding to at least one task; one or more application IDs, each application ID identifying an application corresponding to at least one task; one or more application category IDs, each application category ID identifying an application category corresponding to at least one task; or one or more region IDs, each region ID identifying a region where at least one task is valid. Details related to the task filter have been described above and will not be repeated here.

[0213] In some embodiments, as described above, when the information of interest is related to a task instance, the task instance is indicated by a task instance filter, which includes one of the following: one or more task instance IDs, each task instance ID identifying a task instance in at least one task instance; one or more task IDs, wherein the task instance of at least one task identified by the one or more task IDs belongs to at least one task instance; task selection assistance information, wherein at least one task instance is determined based on the task selection assistance information; one or more application service IDs or one or more application IDs, wherein the task instance associated with one or more applications identified by the one or more application service IDs or one or more application IDs belongs to at least one task instance; or one or more region IDs, each region ID identifying a region where at least one task instance is valid.

[0214] In some embodiments, the NF 710 sends subscription requests in two possible ways. However, this invention is not limited to these two implementations.

[0215] In one implementation, as shown in steps 810a and 810b, for example, when NF 710 is AF 610, NF 710 subscribes to notifications through another network entity (e.g., MEF 630). In this case, NF 710 sends a subscription request to MEF 630 (as shown in step 810a). Based on the subscription request, MEF 630 can subscribe to receive notifications from storage function 720. To do this, MEF 630 sends a subscription request to storage function 720 (as shown in step 810b). The subscription request sent from MEF 630 to storage function 720 (e.g., MDR 615) instructs MEF 630 to subscribe to notifications. The subscription request in step 810b includes the information from the subscription request in step 810a.

[0216] In some embodiments of the present invention, NF 710 is referred to as a first network function, and the "other network entity" as described above is referred to as a second network function. Furthermore, the second network function is not limited to MEF 630 in this invention.

[0217] In another implementation, as shown in step 810c, for example, when NF 710 is a policy control function (PCF), NF 710 can subscribe to notifications without involving MEF630. In this case, NF 710 sends a subscription request to storage function 720 (step 810c).

[0218] In this embodiment of the invention, steps 810a, 810b and 810c are collectively referred to as step 810.

[0219] In some embodiments, the request includes time information indicating when the specified information should be sent. For example, the time information includes one or more time intervals, each associated with a start time and / or an end time. That is, the subscription request (in steps 810a, 810b, and 810c) may include a time validity condition indicating when the subscription is valid (e.g., in terms of time). For example, the time validity condition may be represented by one or more time intervals or durations, each associated with a start time and / or also with an end time. Alternatively, the time validity condition may indicate that the subscription is valid at all times. A notification should be generated or sent to NF 710 only when the subscription is valid as indicated by the time validity condition. For example, the time validity condition may be represented by a time interval (e.g., “15:00-18:00”) that includes a start time and an end time and indicates that the subscription is valid only within that time interval.

[0220] In some embodiments, NF 710 also sends an indication to storage function 720, wherein the indication indicates whether the request corresponds to a one-time response or a continuous response. This indication can be included in the subscription request. In other words, the subscription request (in steps 810a, 810b, and 810c) can also indicate whether the subscription is for a one-time notification or for continuous notifications. If the subscription is for a one-time notification, NF 710 will receive the notification when storage function 720 responds to the request, as further described in step 820. If the subscription is for continuous notifications, NF 710 will continue to receive such notifications whenever the information of interest changes during the subscription's validity period. Note that when the subscription is for a one-time notification, the time validity condition is optional.

[0221] In step 820, the storage function 720 responds to the subscription request received in step 810 with a subscription response. The subscription response acknowledges receipt of the subscription request. The subscription response may include notification of the subscription.

[0222] In some embodiments, if a subscription request is received from MEF 630 as shown in step 810b, storage function 720 sends a subscription response to MEF 630 as shown in step 820a. In this case, as shown in step 820b, MEF 630 responds accordingly to NF 710's subscription request in step 810a. The response sent from MEF 630 to NF 710 includes the information from the subscription response. If a subscription request is received from NF 710 (as shown in step 810c), a subscription response is sent to NF 710 as shown in step 820c.

[0223] In step 830, storage function 720 updates (e.g., adds, modifies, or deletes) information in storage, resulting in one or more changes related to the information of interest identified in the subscription (i.e., the request in step 810).

[0224] Updating information in storage includes adding, modifying, and deleting information as described above, which will not be repeated here. Furthermore, information in storage can be updated according to actual needs. For example, information changes may occur based on requests from network entities. The order of steps 810, 820, and 830 is not limited to that in the embodiments of this invention. Figure 8 The order in which they appear.

[0225] In step 840, the storage function 720 sends a notification to the NF 710. Accordingly, the NF 710 receives the notification.

[0226] In some embodiments, storage function 720 sends a notification about information changes based on the subscription indicated in the subscription request (e.g., step 810b or 810c).

[0227] In some embodiments, if a subscription request is received from MEF 630 as shown in step 810b, storage function 720 sends a notification to MEF 630. In this case, MEF 630 correspondingly sends a notification to NF 710. The notification sent from MEF 630 to NF 710 includes information from the notification received by MEF 630 from storage function 720. If a subscription request is received from NF 710 (step 810c), a notification is sent to NF 710.

[0228] In some embodiments, NF 710 receives specified information from storage function 720, wherein the specified information relates to at least one task indicated by a task filter and / or at least one task instance indicated by a task instance filter in the subscription request as described above. For example, NF 710 receives specified information included in a notification.

[0229] In some embodiments, if at least one task indicated by the task filter in the subscription request includes at least one first task, wherein first description information associated with at least one first task (e.g., a task template as described in Table 1) has been modified, then the specified information associated with at least one first task includes at least a portion of the first description information associated with at least one first task, and the at least portion of the first description information includes the modified first description information. For example, a reusability indication associated with task A has been modified, and the specified information associated with task A includes the modified reusability indication.

[0230] Similarly, in some embodiments, if at least one task instance indicated by the task instance filter in the subscription request includes at least one first task instance, wherein second description information associated with at least one first task instance (e.g., task instance information as described in Table 2) has been modified, then the specified information associated with at least one first task instance includes at least a portion of the second description information, and at least a portion of the second description information includes the modified second description information. For example, execution mode information associated with task instance B has been modified, and the specified information associated with task instance B includes the modified execution mode information.

[0231] In some embodiments, if at least one task includes at least one second task that has already been created, the specified information associated with the at least one second task includes third descriptive information associated with the at least one second task (e.g., a task template as described in Table 1). For example, if a new task C is created, the information changes associated with task C include the task template associated with task C.

[0232] Similarly, in some embodiments, if at least one task instance includes at least one created second task instance, the specified information associated with at least one second task instance includes fourth descriptive information (e.g., task instance information) associated with at least one second task instance. For example, if a new task instance D is created, the information change associated with task instance D includes the task instance information associated with task instance D.

[0233] In some embodiments, if at least one task includes at least one deleted third task, the specified information associated with the at least one third task includes fifth descriptive information (e.g., a task template) associated with the at least one third task. For example, if task E has been deleted, information changes related to task E will occur. In this example, the specified information associated with task E includes the task template associated with task E.

[0234] Similarly, in some embodiments, if at least one task instance includes at least one deleted third task instance, the specified information associated with at least one third task instance includes sixth descriptive information (e.g., task instance information) associated with at least one third task instance. For example, if task instance F has been deleted, the specified information associated with task instance F includes the task template associated with task instance F as described in Table 1.

[0235] In some embodiments, any one of the second description information associated with at least one first task instance, the fourth description information associated with at least one second task instance, and the sixth description information (e.g., task instance information) associated with at least one third task instance includes at least one of the following: the task instance ID of the corresponding task instance; the task ID of the task associated with the corresponding task instance; instantiation information, wherein the instantiation information describes a computing block (CB) instance in the corresponding task instance; execution mode information, wherein the execution mode information describes the mode in which the task is executed on the corresponding task instance; authorization information, wherein the authorization information indicates at least one device that is allowed to access the corresponding task instance; time validity condition, wherein the time validity condition indicates when the corresponding task instance is valid; space validity condition, wherein the space validity condition indicates where the corresponding task instance is valid; and application information, wherein the application information indicates at least one application associated with the corresponding task instance, and for each application, the application information specifies at least one task parameter value.

[0236] In some embodiments, NF 710 also acquires the change type corresponding to the specified information. The change type may be included in the notification. For example, the change type includes any of the following: a modification type, indicating that at least one first description of a first task and / or at least one second description of a first task instance has been modified; an addition type, indicating that at least one third description of a second task and / or at least one fourth description of a second task instance has been created; or a deletion type, indicating that at least one fifth description of a third task (e.g., a task template) and / or at least one sixth description of a third task instance (e.g., task instance information) has been deleted.

[0237] In some embodiments, the deletion type includes a physical deletion type or a logical deletion type, wherein a physical deletion type indicates that: the fifth descriptive information (e.g., task template) is removed from storage and the third task is unavailable, or the sixth descriptive information (e.g., task instance information) is removed from storage and the third task instance is unavailable; a logical deletion indicates that: the fifth descriptive information (e.g., task template) is stored in storage and has been processed, and the third task is deprecated, or the sixth descriptive information (e.g., task instance information) is stored in storage and has been processed, and the third task instance is deprecated. In other words, in both cases where the information change is related to a task or a task instance, the deletion type includes the physical deletion type or logical deletion described above.

[0238] In some embodiments, if the subscription request includes a time validity condition, the storage function 720 performs step 840 only if the subscription is valid as indicated by the time validity condition. This step is optional when the subscription is for a one-time notification.

[0239] According to Figure 8 In the described embodiments, the NF can dynamically subscribe to receive information about tasks or task instances of interest. Based on the received information, the NF can determine whether to use the task or task instance and how to use it (e.g., whether the task can solve certain problems, whether to use the task as a subtask to create a new task, avoid using deprecated tasks, use the task instance at the right time and in the right place, etc.).

[0240] Figure 9 A flowchart of a method performed by a network function according to some embodiments of the present invention is shown; in step 910, the NF sends a request for at least one task and / or at least one task instance to a storage function network entity; in step 920, if information related to at least one task and / or at least one task instance changes, the NF receives specified information from the storage function network entity, wherein the specified information is related to at least one task and / or at least one task instance, each of the at least one task including one or more task instances.

[0241] Figure 10 A flowchart of a method performed by a storage function according to some embodiments of the present invention is shown. In step 1010, the SF receives a request from a first network function, wherein the request is directed to at least one task and / or at least one task instance; in step 1020, if information related to at least one task and / or at least one task instance changes, the SF sends specified information related to at least one task and / or at least one task instance to the first network function.

[0242] Some embodiments of the present invention provide a network device. The network device is used to perform some steps of the information processing method described in the above embodiments / implementations. For example... Figure 11 As shown, network device 1100 includes a processing module 1101 and a communication module 1102. The processing module 1101 is used to process data units / signals. The communication module 1102 is used to transmit (send) and / or receive data units / signals.

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

[0244] In some examples, network device 1100 corresponds to NF 710 and performs... Figure 8Steps 810, 820, and 840 of the method are described above. In this case, the communication module 1102 performs steps 810, 820, and 840.

[0245] In other examples, network device 1100 corresponds to NF 710 and performs... Figure 9 Steps 910 and 920 of the method are described above. In this case, the communication module 1102 performs steps 910 and 920.

[0246] In some other examples, network device 1100 corresponds to storage function 720 and performs... Figure 8 Steps 810, 820, 830, and 840 of the method. In this case, communication module 1102 performs steps 810, 820, and 840, and processing module 1101 performs step 830.

[0247] In some other examples, network device 1100 corresponds to storage function 720 and performs... Figure 10 Steps 1010 and 1020 of the method. In this case, communication module 1102 performs step 1010, and processing module 1101 performs step 1020.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0263] 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 methods of the invention.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0297] 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 executed by a first network function (NF) network entity, characterized in that, include: Send a request for at least one task and / or at least one task instance to the storage function network entity; In the event of a change in information relating to the at least one task and / or the at least one task instance, specified information is received from the storage function network entity, the specified information relating to the at least one task and / or the at least one task instance, each of the at least one task including one or more task instances.

2. The method according to claim 1, characterized in that, The at least one task is indicated by a task filter in the request and / or the specified information.

3. The method according to claim 2, characterized in that, The task filter includes one of the following: One or more task identifiers, each task ID identifying one of the at least one tasks; One or more service IDs, each service ID identifying a service corresponding to one of the at least one tasks; One or more service issue IDs, each service issue ID identifying a service issue corresponding to one of the at least one tasks; One or more application IDs, each application ID identifying an application corresponding to one of the at least one tasks; or One or more region IDs, each region ID identifying a region where one of the at least one tasks is valid.

4. The method according to claim 2 or 3, characterized in that, The at least one task is indicated by a first instruction indicating any task.

5. The method according to any one of claims 1 to 4, characterized in that, The at least one task instance is identified by the task instance filter in the request and / or the specified information.

6. The method according to claim 5, characterized in that, The task instance filter includes one of the following: One or more task instance IDs, each task instance ID identifying one of the at least one task instances; One or more task IDs, each task ID identifying one of the at least one tasks, and for each of the one or more tasks identified by the one or more task IDs, one or more task instances of the task belong to the at least one task instance; Task selection assistance information, wherein the at least one task instance is determined based on the task selection assistance information; Each of the following identifies one or more applications: one or more application service IDs or one or more application IDs, wherein the task instance associated with the one or more applications identified by the one or more application service IDs or the one or more application IDs belongs to the at least one task instance; or One or more region IDs, each region ID identifying a valid region for one of the at least one task instances.

7. The method according to claim 5 or 6, characterized in that, The at least one task instance is indicated by a second indication that indicates any task instance.

8. The method according to any one of claims 1 to 7, characterized in that, The at least one task includes at least one first task, and the specified information associated with the at least one task includes at least a portion of first descriptive information associated with the at least one first task; and / or The at least one task instance includes at least one first task instance, and the specified information associated with the at least one task instance includes at least a portion of the second descriptive information associated with the at least one first task instance.

9. The method according to claim 8, characterized in that, The specified information associated with the at least one task indicates that the first description information associated with the at least one first task has been modified, and the at least a portion of the first description information includes the modified first description information; and / or The specified information associated with the at least one task instance indicates that the second description information associated with the at least one first task instance has been modified, and the at least a portion of the second description information includes the modified second description information.

10. The method according to any one of claims 1 to 8, characterized in that, The at least one task includes at least one second task, and the specified information associated with the at least one task includes third descriptive information associated with the at least one second task; and / or The at least one task instance includes at least one second task instance, and the specified information associated with the at least one task instance includes fourth descriptive information associated with the at least one second task instance.

11. The method according to claim 10, characterized in that, The specified information associated with the at least one task indicates that the at least one second task has been created; and / or The specified information associated with the at least one task instance indicates that the at least one second task instance has been created.

12. The method according to any one of claims 1 to 11, characterized in that, The at least one task includes at least one third task, and the specified information associated with the at least one task includes fifth descriptive information associated with the at least one third task; and / or The at least one task instance includes at least one third task instance, and the specified information associated with the at least one task instance includes sixth descriptive information associated with the at least one third task instance.

13. The method according to claim 12, characterized in that, The specified information associated with the at least one task indicates that the at least one third task has been deleted; and / or The specified information associated with the at least one task instance indicates that the at least one third task instance has been deleted.

14. The method according to any one of claims 8 to 13, characterized in that, Any one of the first description information related to the at least one first task, the third description information related to the at least one second task, and the fifth description information related to the at least one third task includes at least one of the following elements: The task ID corresponding to the task; A time validity condition, wherein the time validity condition indicates when the corresponding task is valid; Spatial validity conditions, wherein the spatial validity conditions indicate where the corresponding task instance is valid; A reusability indicator, wherein the reusability indicator indicates whether the corresponding task is reusable; Application indication, wherein the application indication identifies one or more applications and indicates whether the corresponding task supports the one or more applications; Interface information, wherein the interface information describes one or more interfaces that can access the corresponding task; The task intent information of the corresponding task; Application category information, wherein the application category information identifies one or more application categories related to the corresponding task; Task specification, wherein the task specification defines the networking logic between one or more computing blocks for implementing the task intent of the corresponding task; or One or more task parameters specified by the user of the corresponding task.

15. The method according to any one of claims 8 to 14, characterized in that, Any one of the second description information associated with the at least one first task instance, the fourth description information associated with the at least one second task instance, and the sixth description information associated with the at least one third task instance includes at least one of the following elements: The corresponding task instance ID; The task ID associated with the corresponding task instance; Instantiation information, wherein the instantiation information describes the computation block CB instance in the corresponding task instance; Execution mode information, wherein the execution mode information describes the mode in which the task is executed on the corresponding task instance; Authorization information, wherein the authorization information indicates at least one device that is permitted to access the corresponding task instance; A time validity condition, wherein the time validity condition indicates when the corresponding task instance is valid; Spatial validity conditions, wherein the spatial validity conditions indicate where the corresponding task instance is valid; Application information, wherein the application information indicates at least one application associated with the corresponding task instance, and for each application, the application information specifies at least one task parameter value.

16. The method according to any one of claims 1 to 15, characterized in that, Also includes: Obtain the change type corresponding to the specified information, wherein the change type includes any one of the following: The modification type indicates that the first description information of the at least one first task and / or the second description information of the at least one first task instance has been modified; Add a type indicating that the third description information of the at least one second task and / or the fourth description information of the at least one second task instance has been created; or The deletion type indicates that the fifth description information of the at least one third task and / or the sixth description information of the at least one third task instance has been deleted.

17. The method according to claim 16, characterized in that, The deletion type includes physical deletion type or logical deletion type; The physical deletion type indicates either that the fifth description information is removed from storage and the third task is unavailable, or that the sixth description information is removed from storage and the third task instance is unavailable. The logical deletion instruction is as follows: the fifth description information is stored in storage and has been processed, and the third task is deprecated; or the sixth description information is stored in storage and has been processed, and the third task instance is deprecated.

18. The method according to any one of claims 1 to 17, characterized in that, The request includes time information indicating when the specified information should be sent.

19. The method according to claim 18, characterized in that, The time information includes one or more time intervals, each time interval being associated with a start time and / or an end time.

20. The method according to any one of claims 1 to 18, characterized in that, Also includes: Send an indication to the storage function network entity, wherein the indication indicates whether the request corresponds to a one-time response or a series of responses.

21. The method according to any one of claims 1 to 20, characterized in that, Sending the request to the storage function network entity includes: The request is sent to the storage function network entity via the second network function.

22. The method according to any one of claims 1 to 20, characterized in that, The request is a subscription request, and the response to the request is a notification.

23. The method according to any one of claims 1 to 22, characterized in that, The specified information is related to the at least one task, and the storage function network entity is a first storage function network entity that stores task information; and / or The specified information is related to the at least one task instance, and the storage function network entity is a second storage function network entity that stores task instance information.

24. The method according to any one of claims 1 to 23, characterized in that, The first storage function network entity and the second storage function network entity are the same network entity.

25. A method performed by a storage-functional SF network entity, characterized in that, include: Receive a request from a first network function network entity, wherein the request is directed to at least one task and / or at least one task instance; If information related to the at least one task and / or the at least one task instance changes, the specified information related to the at least one task and / or the at least one task instance is sent to the first network function network entity.

26. The method according to claim 25, characterized in that, Also includes: Updating information related to the at least one task, wherein updating the information related to the at least one task includes at least one of the following: Modify at least a portion of the first descriptive information related to at least one first task; Add third descriptive information related to at least one second task; or Delete the fifth descriptive information related to at least one third task.

27. The method according to claim 25 or 26, characterized in that, Also includes: Updating information related to the at least one task instance, wherein updating the information related to the at least one task instance includes at least one of the following: Modify at least a portion of the second description information associated with at least one first task instance; Add a fourth descriptive information related to at least one second task instance; or Delete the sixth description information associated with at least one third task instance.

28. The method according to any one of claims 25 to 27, characterized in that, Receiving the request from the first network function network entity includes: The request is received from the first network function network entity through the second network function network entity.

29. The method according to any one of claims 25 to 28, characterized in that, The specified information is related to the at least one task, and the storage function network entity is a first storage function network entity that stores task information; and / or The specified information is related to the at least one task instance, and the storage function network entity is a second storage function network entity that stores task instance information.

30. An apparatus, characterized in that, include: At least one processor is configured to execute computer program instructions stored in a memory, such that the apparatus implements the method according to any one of claims 1 to 24.

31. An apparatus, characterized in that, include: At least one processor is configured to execute computer program instructions stored in a memory, such that the apparatus implements the method according to any one of claims 25 to 29.

32. A system, characterized in that, include: The apparatus according to claim 30 and the apparatus according to claim 31.

33. 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 24 or claims 25 to 29.

34. 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 of any one of claims 1 to 24 or claims 25 to 29.

35. 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 24 or claims 25 to 29.

Images