Equipment, method and device for controlling function relocation and readable storage medium

Abstract

An apparatus, method, apparatus, and readable storage medium are described for controlling function relocation wherein, according to one embodiment, the apparatus includes a processor coupled with a memory storing computer program code, in one embodiment, a system includes computer program code to cause a first device to perform the following: for a first task executed by a first task control function (TCF), determining that the first TCF is to be replaced by a second TCF, where the first TCF and the second TCF are managed by mission management (MM), and for a second task executed by the first TCF, determining that the first TCF is to be replaced by the second TCF, where the first TCF and the second TCF are managed by the MM. And transmitting, to the first TCF, a first synchronization request including information of the second TCF for requesting the first TCF to transmit task execution (TE) information to the second TCF, the TE information including execution information of the first task executed by the first TCF. Therefore, the relocation from the o-TCF to the n-TCF is realized.

Description

[0001] Cross-references to related applications

[0002] This application relates to and claims priority to U.S. Provisional Patent Application No. 63 / 594,060, filed October 30, 2023, entitled “Method, Apparatus, and System control function re-location,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] This invention relates to the field of communication technology, and more particularly to devices, methods, apparatuses, and readable storage media for control function relocation. Background Technology

[0004] With the transformation and evolution of wireless networks, communication networks are trending towards a completely new architecture. For example, 6G networks will provide new network infrastructure, such as widely deployed cloud infrastructure, and new processing technologies, such as large-scale artificial intelligence models, data privacy protection, and blockchain.

[0005] The proposed 6G network can execute missions to provide services to users, such as executing missions requested by an application to provide services to the application's users. Each mission can be divided into at least one task, and during mission execution (ME), a task control function (TCF) can control and coordinate task execution (TE). However, the TCF may need to be relocated. For example, as the volume of mission content increases, the computing / communication resources on the network entity embedding the TCF may no longer be sufficient to support TE management, thus the TCF may need to be replaced by a new TCF. Summary of the Invention

[0006] To address the aforementioned issues, devices, methods, apparatuses, and readable storage media for control function relocation are described, wherein relocation from o-TCF to n-TCF is achieved.

[0007] According to a first aspect, a first device is described, comprising: at least one processor coupled to at least one memory storing computer program code; wherein, when the computer program code is executed by the at least one processor, the first device causes the following operations: for a first task executed by a first task control function (TCF), determining that the first TCF will be replaced by a second TCF, wherein the first TCF and the second TCF are managed by mission management (MM); sending a first synchronization request to the first TCF including information of the second TCF to request the first TCF to send task execution (TE) information to the second TCF, wherein the TE information includes execution information of the first task executed by the first TCF.

[0008] According to some embodiments, the first task may include one or more tasks executed by the first TCF. When a TCF needs to be relocated, during a switch from the first TCF to the second TCF, the MM can trigger synchronization between the first and second TCFs to transfer the first task to the second TCF. Therefore, the second TCF can manage the execution of the first task to achieve a successful relocation from the first TCF to the second TCF.

[0009] In one possible implementation of the first aspect, when the computer program code is executed by the at least one processor, the first device is also caused to perform the following operations: send a first update request to the first TCF including the information of the second TCF to request that the TCF for managing the processing service function (PSF) be updated from the first TCF to the second TCF.

[0010] In one possible implementation of the first aspect, the information of the second TCF includes at least one of an identifier (ID), a name, a location, and a validity period.

[0011] In one possible implementation of the first aspect, when the computer program code is executed by the at least one processor, the first device is also caused to perform the following operations: send a configuration request to the second TCF, the configuration request including information about the first TCF and a first synchronization rule.

[0012] In one possible implementation of the first aspect, the information of the first TCF includes at least one of the first TCF's ID, name, and location.

[0013] In one possible implementation of the first aspect, the first synchronization rule includes a first interface and first establishment information for synchronizing the second TCF.

[0014] In one possible implementation of the first aspect, the first synchronization request is further configured to request the first TCF to send a pause request to the PSF managed by the first TCF, wherein the pause request instructs the PSF to pause the process of the first task.

[0015] In one possible implementation of the first aspect, when the computer program code is executed by the at least one processor, the first device is also caused to perform the following operation: receive a relocation completion notification from the second TCF.

[0016] In one possible implementation of the first aspect, when the computer program code is executed by the at least one processor, the first device is also caused to perform the following operations: in response to the relocation completion notification, send a release request to the first TCF, wherein the release request is used to request the first TCF to delete local settings and release storage and computing resources.

[0017] In one possible implementation of the first aspect, when the computer program code is executed by the at least one processor, the first device is further configured to perform the following operations: send a subscription request to a network repository function (NRF) to request the NRF to send information about available TCFs to the MM, wherein the NRF receives the information about available TCFs from XaaS; receive the information about available TCFs from the NRF; and the at least one memory and the computer program code are configured, together with the at least one processor, to further configure the first device to determine the second TCF by: determining the second TCF from available TCFs.

[0018] In one possible implementation of the first aspect, the NRF is configured to receive a registration request for a new TCF from a service control function (SCF), update the information about available TCFs based on the registration request for the new TCF, and receiving the information about available TCFs from the NRF includes receiving the information about the new TCF from the NRF.

[0019] In one possible implementation of the first aspect, the subscription request includes at least one of TCF subscription functionality, information about SCF services, and update time.

[0020] In one possible implementation of the first aspect, the registration request includes at least one of the following: TCF name, TCF location, TCF resources, TCF interface, and information about the PSF managed by the TCF.

[0021] According to a second aspect, a second device is described, comprising: at least one processor coupled to at least one memory storing computer program code; wherein, when the computer program code is executed by the at least one processor, the second device causes: receiving a first synchronization request from the MM including information of a second TCF; and in response to the first synchronization request, sending TE information to the second TCF, wherein the TE information includes execution information of a first task performed by the first TCF.

[0022] In one possible implementation of the second aspect, when the computer program code is executed by the at least one processor, the second device further causes: to receive a first update request from the MM including the information of the second TCF; and to update the TCF of the managing processing service function (PSF) from the first TCF to the second TCF.

[0023] In one possible implementation of the second aspect, the at least one memory and the computer program code are configured, together with the at least one processor, to further enable the second device to update the relevant TCF by: in response to the first update request, sending a second update request to the PSF managed by the first TCF, wherein the second update request includes information about the second TCF, and the second update request is used to request the PSF managed by the first TCF to update the TCF managing the processing service function (PSF) from the first TCF to the second TCF.

[0024] In one possible implementation of the second aspect, the first synchronization request further includes a second synchronization rule, the second synchronization rule including a second interface and second setup information for synchronizing the second TCF, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to also enable the second device to send the TE information by sending the TE information to the second TCF through the second interface based on the second setup information for synchronization.

[0025] In one possible implementation of the second aspect, when the computer program code is executed by the at least one processor, the second device further causes the second device to send a pause request to the PSF managed by the first TCF, wherein the pause request instructs the PSF managed by the first TCF to pause the first task.

[0026] In one possible implementation of the second aspect, when the computer program code is executed by the at least one processor, the second device further causes: receiving a release request from the MM; deleting local settings and releasing storage and computing resources; and sending a response to the release request to the MM to confirm completion of deleting the local settings and releasing the storage and computing resources.

[0027] According to a third aspect, a third device is described, comprising: at least one processor coupled to at least one memory storing computer program code; wherein, when the computer program code is executed by the at least one processor, the third device causes the third device to: receive TE information from a first TCF, wherein the TE information includes execution information of a first task executed by the first TCF; and, based on the TE information, execute the first task via a PSF managed by a second TCF.

[0028] In one possible implementation of the third aspect, the at least one memory and the computer program code are configured, together with the at least one processor, to also enable the third device to perform the first task by performing the first task via the PSF, wherein the associated TCF of the PSF is updated from the first TCF to the second TCF based on the TE information.

[0029] In one possible implementation of the third aspect, when the computer program code is executed by the at least one processor, the third device further causes the third device to: receive a configuration request from the MM, the configuration request including information of the first TCF and a first synchronization rule.

[0030] In one possible implementation of the third aspect, the information of the first TCF includes at least one of the first TCF's ID, name, and location.

[0031] In one possible implementation of the third aspect, the first synchronization rule includes a first interface and first establishment information for synchronizing the second TCF.

[0032] In one possible implementation of the third aspect, the at least one memory and the computer program code are configured, together with the at least one processor, to enable the third device to receive the configuration request by receiving the configuration request from the MM through the first interface based on the first establishment information for synchronization.

[0033] In one possible implementation of the third aspect, when the computer program code is executed by the at least one processor, the third device also sends a relocation completion notification to the MM.

[0034] According to the fourth aspect, a method applied to an MM is described, comprising: determining a first TCF to be relocated and a second TCF to replace the first TCF; sending a first synchronization request to the first TCF managed by the MM, including the information of the second TCF, to request the first TCF to send the task execution (TE) information to the second TCF, wherein the TE information includes execution information of a first task executed by the first TCF.

[0035] In one possible implementation of the fourth aspect, the method further includes: sending a first update request to the first TCF, including the information of the second TCF, to request that the TCF of the managing processing service function (PSF) be updated from the first TCF to the second TCF.

[0036] In one possible implementation of the fourth aspect, the information of the second TCF includes at least one of ID, name, location, and validity period.

[0037] In one possible implementation of the fourth aspect, the method further includes: sending a configuration request to the second TCF, the configuration request including information of the first TCF and a first synchronization rule.

[0038] In one possible implementation of the fourth aspect, the information of the first TCF includes at least one of the first TCF's ID, name, and location.

[0039] In one possible implementation of the fourth aspect, the first synchronization rule includes a first interface and first establishment information for synchronizing the second TCF.

[0040] In one possible implementation of the fourth aspect, the first synchronization request is further configured to request the first TCF to send a pause request to the PSF managed by the first TCF, wherein the pause request instructs the PSF managed by the first TCF to pause the first task.

[0041] In one possible implementation of the fourth aspect, the method further includes: receiving a relocation completion notification from the second TCF.

[0042] In one possible implementation of the fourth aspect, the method further includes: in response to the relocation completion notification, sending a release request to the first TCF, wherein the release request is used to request the first TCF to delete local settings and release storage and computing resources.

[0043] In one possible implementation of the fourth aspect, the method further includes: sending a subscription request to a network repository function (NRF) to request the NRF to send information about available TCFs to the MM, wherein the NRF receives the information about available TCFs from XaaS; receiving the information about available TCFs from the NRF; and determining the second TCF from the available TCFs.

[0044] In one possible implementation of the fourth aspect, the NRF is used to receive a registration request for a new TCF from a service control function (SCF), and update the information about available TCFs based on the registration request for the new TCF. Receiving the information about available TCFs from the NRF includes receiving the information about the new TCF from the NRF.

[0045] In one possible implementation of the fourth aspect, the subscription request includes at least one of TCF subscription functionality, information about SCF services, and update time.

[0046] In one possible implementation of the fourth aspect, the registration request includes at least one of the following: TCF name, TCF location, TCF resources, TCF interface, and information about the PSF managed by the TCF.

[0047] According to a fifth aspect, a method for use with a first TCF is described, comprising: receiving a first synchronization request from an MM including information of a second TCF; and in response to the first synchronization request, sending TE information to the second TCF, wherein the TE information includes execution information of a first task performed by the first TCF.

[0048] In one possible implementation of the fifth aspect, the method further includes: receiving from the MM a first update request including the information of the second TCF; and updating the associated TCF of the PSF managed by the first TCF from the first TCF to the second TCF.

[0049] In one possible implementation of the fifth aspect, updating the related TCF of the PSF managed by the first TCF to the second TCF includes: in response to the first update request, sending a second update request to the PSF managed by the first TCF, wherein the second update request includes information about the second TCF, and the second update request is used to request the PSF managed by the first TCF to update the related TCF to the second TCF.

[0050] In one possible implementation of the fifth aspect, the first synchronization request further includes the second synchronization rule, which includes a second interface and second establishment information for synchronizing the second TCF. Sending TE information to the second TCF includes: sending the TE information to the second TCF through the second interface based on the second establishment information for synchronization.

[0051] In one possible implementation of the fifth aspect, the method further includes: sending a pause request to the PSF managed by the first TCF, wherein the pause request instructs the PSF managed by the first TCF to pause the first task.

[0052] In one possible implementation of the fifth aspect, the method further includes: receiving a release request from the MM; deleting local settings and releasing storage and computing resources.

[0053] According to a sixth aspect, a method for use with a second TCF is described, comprising: receiving TE information from a first TCF, wherein the TE information includes execution information of a first task performed by the first TCF; and performing the first task through a PSF managed by the second TCF based on the TE information.

[0054] In one possible implementation of the sixth aspect, performing the first task includes: performing the first task through the PSF, wherein the relevant TCF of the PSF is updated from the first TCF to the second TCF based on the TE information.

[0055] In one possible implementation of the sixth aspect, the method further includes: receiving a configuration request from the MM, the configuration request including information of the first TCF and a first synchronization rule.

[0056] In one possible implementation of the sixth aspect, the information of the first TCF includes at least one of the first TCF's ID, name, and location.

[0057] In one possible implementation of the sixth aspect, the first synchronization rule includes a first interface and first establishment information for synchronizing the second TCF.

[0058] In one possible implementation of the sixth aspect, receiving TE information from the first TCF includes: receiving the configuration request from the MM through the first interface based on the first establishment information for synchronization.

[0059] In one possible implementation of the sixth aspect, the method further includes: sending a relocation completion notification to the MM.

[0060] According to a seventh aspect, a first apparatus for use in an MM is described, comprising a module for: determining a first TCF to be relocated and a second TCF for replacing the first TCF; sending a first synchronization request to the first TCF managed by the MM, including the information of the second TCF, to request the first TCF to send the task execution (TE) information to the second TCF, wherein the TE information includes execution information of a first task executed by the first TCF.

[0061] According to the eighth aspect, a second apparatus for use with a first TCF is described, comprising a module for: receiving a first synchronization request from an MM including information of the second TCF; and in response to the first synchronization request, sending TE information to the second TCF, wherein the TE information includes execution information of a first task performed by the first TCF.

[0062] According to the ninth aspect, a third device for use with a second TCF is described, comprising a module for: receiving TE information from a first TCF, wherein the TE information includes execution information of a first task performed by the first TCF; and performing the first task via a PSF managed by the second TCF based on the TE information.

[0063] According to a tenth aspect, a computer-readable medium is described, comprising program instructions for causing a device to perform at least one of the described methods.

[0064] In an eleventh aspect, a chip is provided. The chip includes at least one processing circuitry for performing the methods of any of the foregoing aspects or any possible implementation thereof.

[0065] According to a twelfth aspect, a communication system is described, comprising an MM, a first TCF, and a second TCF, wherein the MM is configured to: determine a first TCF to be relocated and a second TCF to replace the first TCF; send a first synchronization request, including information of the second TCF, to the first TCF managed by the MM, requesting the first TCF to send task execution (TE) information to the second TCF, wherein the TE information includes execution information of a first task executed by the first TCF; the first TCF is configured to: receive the first synchronization request, including information of the second TCF, from the MM; and, in response to the first synchronization request, send TE information to the second TCF, wherein the TE information includes execution information of the first task executed by the first TCF; the second TCF is configured to: receive TE information from the first TCF, wherein the TE information includes execution information of the first task executed by the first TCF; and, based on the TE information, execute the first task through a PSF managed by the second TCF. Attached Figure Description

[0066] The foregoing overview and the following detailed description of exemplary embodiments will be more readily understood when read in conjunction with the accompanying drawings. For illustrative purposes, the drawings illustrate currently preferred details according to some embodiments. However, the description is not limited to the precise arrangements and arrangements shown.

[0067] Figure 1 Schematic diagrams of some example communication systems are shown.

[0068] Figure 2 Schematic diagrams of some example communication systems are shown.

[0069] Figure 3 A schematic diagram of a device 310, provided by some examples, for wireless communication with at least one of two devices is shown.

[0070] Figure 4 Schematic diagrams of units or modules in some example devices or apparatuses are shown.

[0071] Figure 5 The diagram shows some examples of 6G systems.

[0072] Figure 6 Schematic diagrams of some example systems provided for control function relocation are shown.

[0073] Figure 7 Schematic flowcharts of control function relocation methods provided in some examples are shown.

[0074] Figure 8Schematic flowcharts of control function relocation methods provided in some examples are shown.

[0075] Figure 9 Schematic structural diagrams of some example devices are shown. Detailed Implementation

[0076] The illustrative embodiments described include, but are not limited to, devices, methods, apparatus, and readable storage media for control function relocation.

[0077] Many new trends will trigger considerations and designs for 6G / future wireless networks:

[0078] - New network infrastructure capabilities, such as widely deployed cloud-native / friendly infrastructure.

[0079] - New (relatively) mature technologies, such as large-scale AI models, data privacy, and blockchain, have made significant progress and have had a major impact on society and human life as a whole.

[0080] - New applications and services, such as AI services, data (sensing) services, digital world services, etc., are widely used in industries / businesses and by individual customers.

[0081] - A more globalized / open / collaborative operating trend, namely, more open and collaborative operating models are becoming prevalent in many fields.

[0082] New expectations and more stringent requirements for future networks have also driven a rethinking and development of next-generation wireless networks. These requirements include:

[0083] - Privacy and trustworthiness, etc.

[0084] - Simplified standardization

[0085] - Rapid deployment

[0086] -wait.

[0087] All of these factors have driven the research on 6G network architecture.

[0088] The proposed 6G network architecture (centered on X) is as follows:

[0089] -Based on SBA (XaaS service)

[0090] -Cloud Native

[0091] Requirements for 6G system network architecture design:

[0092] - The proposed 6G network architecture needs to support new 6G services, which can be developed / deployed by third parties.

[0093] - The proposed 6G network architecture needs to embrace a more open ecosystem and be open to third parties with strong technical capabilities.

[0094] - The proposed 6G network architecture needs to achieve better trust management.

[0095] A solution that meets the above requirements is needed.

[0096] When a device accesses an application through a communication system (such as a 5G system or a future 6G system), the communication system connects the device to the application location (i.e., the network location where the application resides) via a data plane path. The application location corresponds to the application server that hosts or runs the application. When a device accesses an application, it communicates with the application server via the data plane path. There may be more than one application location. When multiple devices access an application, the communication system can connect multiple devices to different application locations.

[0097] This background information is provided to disclose information that the applicant believes may be relevant to the present invention. It is not intended to acknowledge, nor should it be interpreted, that any of the foregoing information constitutes prior art to the present invention.

[0098] In the following description, reference is made to the accompanying drawings, which form part of this invention and are illustrated by way of explanation, showing specific aspects of the invention or in which specific aspects of the invention may be used. It should be understood that one aspect of the invention may be used in other aspects and may include structural or logical variations not depicted in the drawings. Therefore, the following detailed description should not be construed in a limiting sense, and the scope of the invention is defined by the appended claims.

[0099] To aid in understanding the present invention, examples of wireless communication systems and devices are described below.

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

[0101] Generally, communication system 100 enables multiple wireless or wired components to transmit data and other content. Communication system 100 can provide content such as voice, data, video, and / or text through broadcasting, multicasting, unicasting, etc. Communication system 100 can provide a wide range of communication services and applications (e.g., earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery and mobility, etc.). Services and / or applications may be mobile broadband (MBB) services, ultra-reliable low-latency communication (URLLC) services, or machine-type communication (MTC) services.

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

[0103] Figure 2 A more detailed example of the communication system 100 is shown.

[0104] Communication system 100 may include terrestrial communication systems and / or non-terrestrial communication systems. Communication system 100 can provide high availability and robustness through the joint operation of terrestrial and non-terrestrial communication systems. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can enable a heterogeneous network comprising multiple layers. 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.

[0105] Terrestrial communication systems and non-terrestrial communication systems can be considered as subsystems of a communication system.

[0106] and Figure 1 The example shown is the same, in Figure 2In the example shown, communication system 100 may include ED 110a, 110b, 110c, 110d (generally referred to as ED 110) and RAN 120a, 120b. Furthermore, communication system 100 may also include a non-terrestrial communication network 120c. Communication system 100 may also include one or more of a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. RAN 120a, 120b include corresponding RAN nodes, such as base stations (BS) 170a and 170b, which may generally be referred to as terrestrial transmit and receive points (T-TRP) 170a and 170b. In one implementation, non-terrestrial communication network 120c includes RAN nodes, such as access nodes (or base stations) 172, which may generally be referred to as non-terrestrial transmit and receive points (NT-TRP) 172. As can be inferred from the similarities in the reference numerals, the non-terrestrial communication network 120c can be considered a radio access network, operating in the same manner as RANs 120a and 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 operates as a transport layer device, and the at least one corresponding terrestrial network device operates as a RAN node, which communicates with the ED through the NTN device. Furthermore, an NTN gateway may also exist on the ground (i.e., referred to as the terrestrial network device), communicating with the NTN device as a transport layer device, and the RAN node communicates with the ED through both the NTN device and the NTN gateway. In some implementations, the NTN gateway and the RAN node may reside in the same device.

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

[0108] An air interface (e.g., 190a, 190b, 190c) typically includes numerous components and associated parameters that collectively specify how transmissions are sent and / or received over a wireless communication link between two or more communication devices. For example, an air interface may include one or more waveforms, one or more frame structures, one or more multiple access schemes, one or more protocols, one or more coding schemes, and / or one or more modulation schemes defining the transmission of information (e.g., data) over the wireless communication link. A wireless communication link may support a link between a radio access network (e.g., RAN 120) and a user equipment (e.g., ED 110) (e.g., a “Uu” link), and / or a wireless communication link may support a link between a device (e.g., ED 110a) and a device (e.g., ED 110b) (e.g., a “LS” link), such as a link between two user equipments, and / or a wireless communication link may support a link between a non-terrestrial (NT) communication network (e.g., RAN 120c) and a user equipment (e.g., ED 110d). Some examples of the aforementioned components are given below.

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

[0110] The frame structure component can specify the configuration of a frame or frame group. The frame structure component can indicate one or more of the following parameters: frame time, frequency, pilot signature, code, subcarrier spacing, cyclic prefix length, or other parameters. Further details about the frame structure will be discussed below.

[0111] The multiple access scheme component can specify multiple access technology options, including technologies that define how communication devices share the common physical channel, such as: code division multiple access (CDMA), space division multiple access (SDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA) (also known as discrete Fourier transform spread OFDMA (DFT-s-OFDMA)), low-density signature multicarrier CDMA (LDS-MC-CDMA); non-orthogonal multiple access (NOMA); pattern division multiple access (PDMA); lattice partition multiple access (LPMA); and resource spread multiple access. Multiple access technologies include sparse code multiple access (SCMA) and non-scheduled access (also known as unlicensed access); non-orthogonal multiple access and orthogonal multiple access, for example, through dedicated channel resources (e.g., not shared between multiple communication devices); contention-based shared channel resources and non-contention-based shared channel resources; and cognitive radio-based access. Air interfaces 190a and 190b can utilize other high-dimensional signal spaces, which may involve combinations of orthogonal and / orthogonal dimensions.

[0112] The coding and modulation components specify how the transmitted information is encoded / decoded and modulated / demodulated for transmission / reception. Encoding can refer to methods of error detection and forward error correction. Non-limiting examples of coding options include turbo lattice codes, turbo product codes, fountain codes, low-density parity-check codes, and polar codes. Modulation can simply refer to constellations (including, for example, modulation techniques and orders), or more specifically to various types of advanced modulation methods, such as layered modulation and low PAPR modulation.

[0113] The 190a and 190b air interfaces can use similar communication technologies, such as any suitable wireless access technology.

[0114] 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 a link. For 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.

[0115] RANs 120a and 120b communicate with core network 130 to provide various services, such as voice, data, and other services, to EDs 110a, 110b, and 110c. RANs 120a and 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 RANs 120a, RAN 120b, or both. Core network 130 may also act as a gateway access between (i) RANs 120a and 120b and / or EDs 110a, 110b, and 110c, and between (ii) other networks (e.g., PSTN 140, Internet 150, and other networks 160). Furthermore, some or all of ED110a, 110b, and 110c may include the ability to communicate with different wireless networks via different wireless links using different wireless technologies and / or protocols. Instead of wireless communication (or other than wireless communication), ED 110a, 110b, and 110c may also communicate with service providers or exchanges (not shown) via wired communication channels and with the Internet 150. 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 (internal networks) and incorporate protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). ED 110a, 110b, and 110c may be multimode devices capable of operating according to multiple wireless access technologies and include multiple transceivers required to support these technologies.

[0116] In addition, the communication system 100 may include a sensing agent (not shown) to manage sensing data from ED 110 and / or T-TRP 170 and / or NT-TRP 172. In one implementation, the sensing agent is located in 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 170 and / or NT-TRP 172).

[0117] Figure 3An example of a device 310 provided in an embodiment for wirelessly communicating with at least one of two devices (e.g., device 320a and device 320b, referred to as device 320) in a communication system (e.g., communication system 100). Device 310 may be a UE (e.g., Figure 3 ED 110 in the example). Device 320a can be a terrestrial network device (e.g., such as ED 110). Figure 3 The T-TRP 170 shown), device 320b can be a non-terrestrial network device (e.g., such as...). Figure 3 (NT-TRP 172 shown). However, this is not mandatory. For example, according to the present invention, device 320a can be NT-TRP, device 320b can be T-TRP, and both devices 320a and 320b can be either T-TRP or NT-TRP. In the following description, ED 110 is used as an example of device 310, T-TRP 170 as an example of device 320a, and NT-TRP 172 as an example of device 320b. Although only one device 310, one device 320a, and one device 320b are shown, it should be noted 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 ED 110 can be served by only one T-TRP 170 (or one NT-TRP 172), or by more than one T-TRP 170, or by more than one NT-TRP 172, or by one or more T-TRP 170 and one or more NT-TRP 172.

[0118] 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), metaverse, 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, etc.

[0119] Each ED 110 represents any end-user equipment suitable for wireless operation and may include (or be referred to as, but 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, smartbook, vehicle, automobile, truck, bus, train, or IoT device, wearable device (e.g., watch, glasses, head-mounted device, etc.), industrial equipment, or devices comprising or including the foregoing (e.g., communication module, modem, or chip), etc. Future generations of ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs and will be referred to as T-TRP 170 below. Figure 3 As shown, the non-terrestrial (NT) device will be referred to as NT-TRP 172 below. Each ED 110 connected to T-TRP 170 and / or NT-TRP 172 can be dynamically or semi-statically turned on (i.e., established, activated, or enabled), turned off (i.e., released, deactivated, or disabled), and / or configured in response to one or more of connectivity availability and connectivity necessity.

[0120] like Figure 3As shown, ED 110 includes at least one processor 210. Only one processor 210 is shown in the figure to avoid congestion. 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 congestion. One, some, or all of the antennas 204 may also be panels. For example, transmitter 201 and receiver 203 may be integrated as a transceiver. The transceiver is used to modulate data or other content for transmission by at least one antenna 204 or a network interface controller (NIC). The transceiver is also used to demodulate data or other content received through 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.

[0121] Memory 208 stores instructions. Memory 208 may also store data used, generated, or acquired 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 can 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, on-processor cache, etc.

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

[0123] Processor 210 performs (or controls ED 110 to perform) operations described herein as being performed by ED 110, as shown below and elsewhere in the invention. For example, processor 210 performs or controls ED 110 to perform the following operations: receive a transport block (TB), decode one of the received TBs using resources, release resources to decode another of the received TBs, and / or receive configuration information for configuring resources. Specifically, the operations may include operations related to preparing for 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 for 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 operations such as 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 (e.g., beam angle information (BAI)) received from T-TRP 170. 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 using reference signals received from NT-TRP 172 and / or T-TRP 170.

[0124] Although not shown, processor 210 may form part of transmitter 201 and / or receiver 203. Although not shown, memory 208 may form part of processor 210.

[0125] The processing components of processor 210, transmitter 201, and receiver 203 may be implemented by the same or different 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 accelerators such as graphics processing units (GPUs) or artificial intelligence (AI) accelerators.

[0126] In some implementations, ED 110 may be a device (also called a component), such as a communication module, modem, chip, or chipset, which includes at least one processor 210 and an interface or at least one pin. In this scenario, the transmitter 201 and receiver 203 may be replaced by 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. 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. Information may include control signaling and / or data. Similar rules apply to other nodes / entities in this invention.

[0127] 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 congestion. 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 congestion. One, some, or all of the antennas 256 may also be panels. 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 in the figure, but the T-TRP may include one or more other components.

[0128] The T-TRP 170 may be known by other names in some implementations, such as base station, base-transceiver station (BTS), wireless base station, network node, network device, network-side device, transmit / receive node, NodeB, evolved NodeB (eNodeB or eNB), home eNodeB, 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), pico BS, relay node, host node, or a combination thereof. T-TRP 170 may refer to the aforementioned device or a component of the aforementioned device (e.g., a communication module, modem, or chip).

[0129] In some embodiments, the portions of T-TRP 170 may 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) (e.g., a common public radio interface, CPRI) sometimes referred to as a fronthaul. Therefore, in some embodiments, the term T-TRP 170 may also refer to modules on the network side that perform processing operations such as determining the location of ED 110, resource allocation (scheduling), message generation, and encoding / decoding; these modules 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 that operate together to provide services such as coordinated multicast to ED 110.

[0130] The operations performed by processor 260 include 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 via backhaul from T-TRP 170 and / or NT-TRP 172. Processing operations related to preparing transmissions for downlink or backhaul transmission may include operations such as encoding, modulation, precoding (e.g., multiple-input multiple-output (MIMO) precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in the uplink or via backhaul may include operations such as 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, that 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, determining the deployment location of NT-TRP 172, etc. In some embodiments, processor 260 may generate signaling, such as 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.

[0131] Scheduler 253 may be coupled to or integrated into processor 260. Scheduler 253 may be included within 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 authorizations and / or configuring unscheduled (e.g., "configuration authorization") resources.

[0132] Memory 258 is used to store information, and optionally data. Memory 258 stores instructions and data used, generated, or acquired by T-TRP 170. For example, memory 258 may store software instructions or modules executed by processor 260 for implementing some or all of the functions and / or embodiments described herein.

[0133] Although not shown, processor 260 may form part of transmitter 252 and / or receiver 254. Furthermore, although not shown, processor 260 may implement scheduler 253. Although not shown, memory 258 may form part of processor 260.

[0134] The processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 may be implemented by the same or different 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 may be implemented using dedicated circuitry, such as a programmable FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC.

[0135] 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, 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., chips, memory, or buses). 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, and 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. The information may include control signaling and / or data.

[0136] Although the NT-TRP 172 is shown as an example of a drone only, it 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, the NT-TRP 172 may be known by other names in some implementations, such as non-terrestrial node, non-terrestrial network device, or non-terrestrial base station.

[0137] 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 congestion. One, some, or all of the antennas 256 may also be panels. 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 in the figure, but the T-TRP may include one or more other components.

[0138] 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 congestion. 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 congestion. One, some, or all of the antennas may also 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 in the figure, but the NT-TRP may include one or more other components.

[0139] NT-TRP 172 includes a processor 276 for performing operations 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 NT-TRP 172, and processing a transmission received via backhaul from T-TRP 170 and / or another NT-TRP 172. Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in the uplink or 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, such as for configuring one or more parameters of ED 110. In some embodiments, NT-TRP 172 implements physical layer processing but not higher-level functions such as those at the medium access control (MAC) or radio link control (RLC) layers. Since this is only an example, more generally, NT-TRP 172 may implement higher-level functions in addition to physical layer processing.

[0140] Memory 278 is used to store information, and optionally data. Memory 258 stores instructions and data used, generated, or acquired by NT-TRP 172. For example, memory 278 may store software instructions or modules executed by processor 276 for implementing some or all of the functions and / or embodiments described herein.

[0141] Although not shown, processor 276 may form part of transmitter 272 and / or receiver 274. Although not shown, memory 278 may form part of processor 276.

[0142] The processing components of processor 276, transmitter 272, and receiver 274 may 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 may 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 may actually be multiple NT-TRPs operating together to coordinate services such as multicast transmission ED 110.

[0143] When NT-TRP 172 is a device within a unit (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, and 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. The information may include control signaling and / or data.

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

[0145] 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), which is 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 the sidelink, signaling between different terminals or sensing devices (e.g., between ED 110i and ED 110j) can be called sidelink control information (SCI) and is transmitted in the physical sidelink control channel (PSCCH). Signaling can be carried in higher-layer (e.g., above the physical layer) signaling, which is transmitted in the physical layer data channel. For example, downlink signaling is transmitted in the physical downlink shared channel (PDSCH), uplink signaling in the physical uplink shared channel (PUSCH), and sidelink signaling in the physical sidelink shared channel (PSSCH). Higher-layer signaling can also be called static signaling 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 include a combination of physical layer signaling and higher layer signaling.

[0146] It should be noted that in this invention, when "information" and "message" are different, they can be carried in a single message or in more than one single message.

[0147] One or more steps of the method provided in this invention can be based on Figure 4 The corresponding unit or module is executed. Figure 4 Units or modules in devices or apparatuses, such as in ED 110, T-TRP 170, or NT-TRP 172, are illustrated. For example, signals may be transmitted by a transmitting unit or transmitting module. Signals may be received by a receiving unit or receiving module. Signals may be processed by a processing unit or processing module. Other steps may be performed by artificial intelligence (AI) or machine learning (ML) modules. 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 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 units or modules may be logic, such as a part of a circuit, an integrated circuit, or a logical function executed 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, then these modules may be retrieved by the processor, wholly or partially, individually or collectively, for processing, in one or more instances, as needed, and these modules themselves may include instructions for further deployment and instantiation. Similar units or modules are applicable to other nodes / entities in this invention.

[0148] Additional 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.

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

[0150] The 6G system adopts a service-based architecture and the XaaS concept. XaaS services in the 6G system are categorized into three layers. The conceptual structure of the 6G system is as follows: Figure 5 As shown.

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

[0152] Each infrastructure can have control and management functions for infrastructure management, represented as C / M functions. Each of these infrastructures is an Infrastructure as a Service.

[0153] The control and management (C / M) layer includes control and management services for the 6G system. These are developed and deployed using slicing technology and leveraging resources provided by the infrastructure layer. The 6G services in the control and management (C / M) layer are:

[0154] - Control Function Relocation (RM) as a service provides the ability to manage the lifecycle of various slices and allocate air resources to wireless devices.

[0155] - A 6G mission is defined as the service provided to customers by a 6G system. A mission can be a type of service provided by a single 6G XaaS service, or it can be a type of service that requires contributions from multiple XaaS services.

[0156] - Mission management (MM) is the ability to program the configuration of XaaS services at the service layer to provide mission services.

[0157] - The Confederation Network (CONET) as a Service provides the ability for multiple partners to jointly deliver 6G services. This capability is provided through protocol negotiation involving alliance formation, mutual authentication, mutual authorization, and the recording and retrospective of selected actions performed by partners, ensuring a trusted environment for the operation of 6G systems.

[0158] Service provisioning management (SPM) refers to the ability of service providers to control and manage customer access to 6G services and configure requested services. This capability is provided through unified mutual authentication, authorization and policies, key management, QoS guarantees, and accounting between any pair of XaaS service providers and customers. Customers include not only end customers in the physical world but also digital representatives in the digital world.

[0159] - Connectivity management (CM) as a service leverages 5G connectivity management capabilities but extends to include the digital world.

[0160] Protocol as a Service (PCA) provides the ability to customize protocol stacks for the design services of the identified interfaces.

[0161] - Protocol stacks can be predefined for selection on demand, or designed on demand.

[0162] Cybersecurity as a Service (CSIS) provides infrastructure owners with the ability to detect potential security risks to their infrastructure.

[0163] XaaS services in the C / M layer support the control and management of the 6G system itself and provide support to vertical industries upon request. For example, the RM service can provide over-the-air control function relocation services for the RAN, or over-the-air resource allocation services to end customers in vertical industries. XaaS in the C / M layer can be deployed using slicing technology.

[0164] The service layer includes 6G services provided to customers. In the 6G system conceptual architecture:

[0165] - AI services are represented as NET4AI as a Service. Artificial intelligence services provide AI capabilities to support a wide range of AI applications.

[0166] Data acquisition, data cleansing, data analysis, and data delivery services are represented as data analytics and management (DAM) as a service. This service provides the ability to manage the lifecycle of statistical data, including acquiring, de-privatizing, analyzing, and delivering data, which is statistical data from any type of sensor, device, network function, etc.

[0167] - Data storage and sharing services are represented as NET4Data as a Service, which provides the ability to reliably store and share data under the control of the data owner and in accordance with the regulations of recognized authorities on the control of identified data.

[0168] - Services that provide access to the digital world are represented as NET4DW as a Service. 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.

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

[0170] - Enhanced connectivity services, such as connection-oriented networking (NET4CON) as a service.

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

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

[0173] 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 other vertical industries is that vertical industries are purely customers who require other XaaS services to support their operation, while each XaaS service provides its capabilities to the 6G customer.

[0174] Any pair of XaaS services in a 6G system can also be customer and provider to each other. Some examples include: the infrastructure owner providing its resources to XaaS services in the service layer and the C / M layer; the RM service potentially requiring capabilities provided by NET4AI, DAM, and NET4DW to enable its control function relocation for vertical slices; and the CONET and NET4Data services potentially requiring capabilities provided by NET4BC for them to function.

[0175] Key concepts of 6G systems include:

[0176] - Basic XaaS services are defined by decoupling comprehensive service types into basic XaaS services. Basic XaaS services provide unique capabilities to enable specific types of services, such as NET4AI services, NET4DW services, DAM services, NET4Data services, blockchain services, mission management services, etc.

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

[0178] - Define the data plane of the 6G system, including the data plane processing capabilities of XaaS services. By programming the interconnection of these capabilities through mission management services, a variety of customized customer services can be supported.

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

[0180] - Define the C / M plane of the 6G system, including the C / M functions in XaaS services, which may include the 5G control plane (CP) (e.g., AMF) depending on the implementation options.

[0181] - Define the basic architecture structure (BAS), which is a unified basic structure with a minimal number of interfaces and is independent of the infrastructure type.

[0182] - The BAS concept simplifies the standardization, development, and deployment of 6G systems, while supporting a variety of infrastructure deployment scenarios.

[0183] - By applying BAS or subsets of it to the infrastructure based on the capabilities, capacity, and requirements of the infrastructure network, it can be adapted to a variety of deployment scenarios.

[0184] -Utilize the SBI interface concept and apply SBI interaction in both the 6G C / M plane and the 6G data plane.

[0185] -Simplify the service-based interface (SBI) by introducing a trusted gateway (GW) in the data plane and C / M plane of the 6G system.

[0186] - Improve trustworthiness from the perspective of 6G system operation by introducing CONET capabilities, NET4BC capabilities and anonymity service configurations provided by a trusted GW into the C / M plane and data plane of the 6G system.

[0187] - Trustworthiness is enhanced from the perspective of end-customer privacy protection by providing unified mutual authentication, ID management (IDM), and data purification through SPM service, DAM service and 6G blockchain service.

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

[0189] - By defining multiple architecture options, it supports multiple development paths from 5G systems to 6G systems, without requiring excessive investment due to the introduction of the BAS concept.

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

[0191] - Supports future expansion by adding new XaaS services, and the impact on standardization and deployment can be minimized because the concept of anonymous service configuration is implemented in the trusted GW in the 6G C / M plane and 6G data plane.

[0192] As mentioned earlier, the ME process in a communication system needs to be controlled by at least one TCF. However, due to external environmental factors, such as increased management load required by the ME, the o-TCF may no longer meet the management requirements, potentially necessitating TCF relocation of the o-TCF. However, there is currently no efficient TCF relocation implementation method.

[0193] The described embodiments introduce a TCF relocation system, which includes at least one device for TCF relocation, enabling efficient relocation of the TCF. The first device may be an MM (Medium-Modified Component) as described below, the second device may be an o-TCF (Optical-to-Frequency Component) as described below, and the third device may be an n-TCF as described below.

[0194] According to some embodiments, when TCF relocation is required, the MM can identify the n-TCF and control the o-TCF to migrate all its functions to the n-TCF, for example, by sending TE information to the n-TCF so that the n-TCF can know the progress of the TE or the current execution result of the TE.

[0195] According to some embodiments, before synchronization, the MM can also send n-TCF information to the o-TCF so that the o-TCF can clearly identify the object to which it will perform data synchronization. Furthermore, the MM can send corresponding synchronization rules to both the o-TCF and n-TCF to facilitate successful data synchronization between the two.

[0196] According to some embodiments, the MM can also control the MM to pause the execution of the currently running mission to prevent information interruption during the synchronization process. It should be noted that the following mission-related sections will describe the details of the mission.

[0197] The following will combine Figure 6 The TCF relocation system described herein is introduced. Essentially, the described method and TCF relocation system are based on the same inventive concept.

[0198] The system uses Figure 6 The architecture shown performs ME management and control function relocation provided by this invention. This architecture includes many network functions: Mission Client, MM, TCF, and PSF. It should be noted that... Figure 3 and Figure 4 The devices, units, and modules shown can also be applied to equipment / DN, MM, TCF, and PSF.

[0199] Mission customer (MC): An authorized network entity (such as an application function (AF), device, or network function) can send a request to the MM to request the ME. The authorized network entity is called the mission customer (MC).

[0200] Mission Management (MM): MM includes Control / Management Plane (CP) functions for managing / coordinating one or more Mission Execution Entities (MEs). MM controls and coordinates MEs through mission instances, including starting, pausing, resuming, stopping, and terminating MEs. MM starts, pauses, resumes, stops, or terminates MEs based on requests (e.g., from the Control Plane) or specific events (e.g., time events). MM is responsible for establishing data plane paths for mission execution between one or more Control Plane Entities (CBs) within a mission instance and between mission participants (e.g., UEs) and one or more CBs. When coordinating mission execution, MM 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). MM can control mission execution according to relevant MM policies, which can be pre-configured at MM or obtained by MM from another control plane entity. The mission context associated with the ME is maintained in the CP and DP until the ME is terminated.

[0201] Task Control Function (TCF): The TCF controls and coordinates the Task Execution Framework (TE), including starting, stopping, and terminating the TE. The TCF starts, stops, or terminates the TE as part of the Task Execution Framework (ME) based on one or more requests from the Task Manager (MM). The MM notifies the TCF that network entities (e.g., devices) are accessing / participating in the TE. Accordingly, the TCF can invite network entities to access / participate in the TE at appropriate times (e.g., when task resources are ready), whereby the network entities can provide data to support task execution or receive data related to the TE. The task context associated with the TE is maintained in the Service Module's CP and the Service Module's DP before task execution terminates.

[0202] Processing Service Function (PSF): The PSF receives and processes DP traffic. The PSF can generate data plane traffic. The PSF can transmit its received (possibly processed) or generated data plane traffic to other PSFs, DNs, or UEs through one or more data plane gateways (also called data gateways (data GWs)). These data plane gateways are similar to the user plane function (UPF) in 5G systems.

[0203] According to some embodiments, the MM can play a coordinating role to determine whether relocation is needed and to send information to the o-TCF and n-TCF during the relocation process, or to control the interaction between the o-TCF, n-TCF, and PSF. Information is passed between them to control each role in the system, thereby assisting in the step-by-step completion of the TCF relocation process.

[0204] The following section will introduce mission and mission-related terminology.

[0205] A mission is a specified objective to achieve what is called a mission objective, which includes (1) providing protocol data unit (PDU) connectivity and optionally (2) providing data processing. When a mission objective includes providing data processing, the mission 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, a mission includes one or more computing blocks (CBs) and is associated with a networking process between CBs for solving one or more specific computational problems. A CB within a mission corresponds to a defined computational step for the mission objective (i.e., solving one or more specific computational problems) and can be supported by a service (in the form of a task), a data network (DN), or another mission; therefore, a CB is called a task CB, an external CB, or a sub-mission CB. Mission management includes programming missions, instantiating missions, and implementing mission objectives.

[0206] A mission slice is a logical network that provides specific capabilities and characteristics in terms of networking and computing (including storage) for a mission. A CB within a mission corresponds to a subnet of the mission slice, called a CB subnet. The CB subnet provides the computing functionality to implement the corresponding computing steps for the mission objectives. A mission slice instance includes a collection of network function instances and the required resources (e.g., computing, storage, and networking resources) and computing logic (e.g., in terms of parameter configuration), which constitute the deployed mission slice. Mission services are services that provide the implementation (also known as mission execution) of mission objectives between a network entity (NE) (e.g., UE or AS) and a DN. A mission session refers to the association between an NE and a DN, providing mission services through the support of mission slice instances.

[0207] Unless explicitly stated otherwise, for ease of expression and to avoid ambiguity, "mission" and "mission slice" are used interchangeably; similarly, "CB" and "CB subnet" are used interchangeably. When a mission is instantiated, a mission slice instance is created for that mission. Therefore, a mission slice instance is considered an instance of the mission. For each CB within a mission, the mission instance includes an instance of the CB. If the CB is a task CB, the CB instance resides in the XaaS service module (or simply service module) supporting the task CB; if the CB is an external CB, the CB instance resides in the corresponding DN; if the CB is a sub-mission CB, the CB instance is an instance of the mission corresponding to the CB. A mission can have multiple instances. When a CB instance is stateless, it can be shared by multiple mission instances. Similarly, when a mission instance is stateless, it can be shared by multiple applications (i.e., support multiple applications). A mission instance is stateless if and only if it does not include stateful CB instances.

[0208] An application residing in a DN can be a client of a mission and provide application services to its users by leveraging the execution of the mission. A mission can support more than one application. A mission supports an application through a mission instance. A mission can act as an application, natively providing application services to application users; in this case, the application is considered to reside within a mission. An NE is authorized to access an application using a mission session, which is specific to the DN where the application resides and is supported by an instance of the mission. When an application resides within a mission, the DN is an abstract DN corresponding to the mission. A mission instance can be used to support more than one application. Different applications can be supported by different instances of missions.

[0209] To support applications via mission instances as described above, mission sessions can be established on mission instances. During mission session establishment, data planes (e.g., one or more data plane paths across one or more CB instances) and control planes (e.g., one or more MCFs and one or more TCFs) are configured for the mission session.

[0210] After a mission session is established, application-related data traffic can flow through mission instances and be processed under the coordination of the MM framework according to the network logic (if any) associated with the mission. The process of coordinating data flow and processing is called mission execution (ME) (or simply ME). ME includes one or more task executions (TEs) based on the network logic (if any) associated with the mission. TEs are called CB executions and include one or more executions of one or more data plane (DP) computation / processing functions based on predefined execution dependencies and / or logic (if any) associated with the CB. The ME management service is responsible for initiating, coordinating, and terminating ME processes.

[0211] During mission execution, TCFs may need to be relocated for the following reasons: (1) PSF relocation, which may result in suboptimal TCF deployment for all or one PSFs involved in the TE; (2) scarce computing / communication resources on network entities with embedded TCFs.

[0212] The methods or procedures required for mission execution include how to dynamically relocate one or more TCFs during the ME process and how the MM subscribes to information on one or more available TCFs / PSFs provided by one or more XaaS services (which can be used to relocate one or more TCFs during the ME process).

[0213] Accordingly, the present invention provides a method for control function relocation. This method includes relocation of one or more TCFs and subscription to available TCF / PSF information during mission execution. Therefore, this method enables dynamic TCF relocation during mission execution to address resource scarcity and suboptimal deployment issues, and allows MMs to subscribe to information on one or more available TCFs / PSFs provided by one or more XaaS services.

[0214] It should be noted that the described content is not limited to the factors that cause TCF relocation mentioned above. According to the described embodiments, the cause of TCF relocation of the program may be other reasons.

[0215] Control function relocation refers to the process during ME (Engineering Management) that changes one or more TE (Technical Equipment) control functions involved in the ME from old control functions to new control functions. The old and new control functions may have different locations (i.e., network addresses).

[0216] The reason for control function relocation during ME is:

[0217] One or more data plane (DP) functions may be relocated, which may result in suboptimal deployment of legacy control functions. For example, the network address of a legacy control function may not be reachable at one or more relocated DP functions in one or more new locations.

[0218] - Computing / communication resources are scarce on network entities with embedded control functions.

[0219] -PSF relocation.

[0220] To enable control function relocation, the ME's controller may need to know in advance all or one of the available control functions, which can be selected as one or more new control functions. Therefore, an available network function information subscription process is defined to provide the ME's controller with information on one or more available network functions (including both control functions and DP functions).

[0221] In response to the problem of TCF relocation, this paper provides a method for TCF relocation mainly through the interaction between MM, o-TCF, n-TCF, and PSF. This method not only achieves high relocation efficiency without affecting mission execution but also ensures system security. The following will combine... Figure 7 and Figure 8 An exemplary process for describing this method is provided.

[0222] For illustrative purposes, specific exemplary embodiments will now be explained in more detail with reference to the accompanying drawings and the systems, EDs, TRPs, and network nodes mentioned above.

[0223] The embodiments described herein illustrate information sufficient to practice the claimed subject matter and demonstrate methods for practicing such subject matter. Upon reading the following description in conjunction with the accompanying drawings, those skilled in the art will understand the concepts of the claimed subject matter and will recognize that the application of these concepts is not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of this invention and the appended claims.

[0224] like Figure 7 As shown, the present invention provides a method for control function relocation (e.g., TCF relocation).

[0225] The TCF relocation process can be triggered by the MM during the ME process. In order to perform the TCF relocation process, the MM may need to have information on all or one available TCFs acquired during the TCF / PSF information subscription process (described later).

[0226] During TCF relocation, the o-TCF is called the old TCF, which manages one or more ongoing TEs and will be discarded after the TCF relocation is completed; the n-TCF is called the new TCF, which will replace the o-TCF and manage one or more TEs after the TCF relocation is completed.

[0227] Figure 7 The TCF relocation process is illustrated:

[0228] S101: MM performs TCF load monitoring.

[0229] MM performs TCF load monitoring to continuously monitor compute load information on all or one TCFs.

[0230] Computational load information includes the percentage of computational units (e.g., CPU) occupied / consumed due to managing one or more ongoing TEs associated with the TCF.

[0231] According to some embodiments, MM’s TCF load monitoring can be performed based on a preset frequency.

[0232] S102: MM performs TCF relocation determination.

[0233] The MM determines to discard / relocate the old TCF (o-TCF) based on the monitored information, because of insufficient resources on the o-TCF, or because the o-TCF position is not optimal due to DP function relocation (e.g., PSF relocation).

[0234] According to some embodiments, MM can perform TCF relocation determination based on the data monitored in step S101.

[0235] For example, if the percentage of computing unit (e.g., CPU) occupancy / consumption is detected to be too high in step S101, such as exceeding a preset value, then MM can determine that TCF relocation needs to be performed.

[0236] For example, MM can also monitor PSFs managed by TCFs. If PSF relocation is detected, and the n-PSF of the relocated PSF is associated with other TCFs besides the o-TCF, then MM can determine that TCF relocation is required.

[0237] For example, MM can also monitor the DP used for TCF management. If the DP changes, for example, becoming closer to other TCFs, MM can determine that TCF relocation is needed.

[0238] S103: MM selects n-TCF.

[0239] MM selects a new TCF (n-TCF) from one or more available TCFs to replace the o-TCF.

[0240] Selection criteria may include at least one of the following:

[0241] -n-TCF must be within the same CBI as o-TCF (ensuring that n-TCF can manage all or one or more TEs managed by o-TCF).

[0242] The position of -n-TCF, for example, close to all or one PSF.

[0243] The available resources on the n-TCF, for example, whether the n-TCF has sufficient computing / communication resources.

[0244] For example, MM can identify all or one available TCFs in the CBI to which the o-TCF belongs, and then determine the n-TCF from these one or more TCFs. For example, the TCF that is closest to one or more PSFs managed by the o-TCF can be selected as the n-TCF. Specifically, for each TCF, its distance to each PSF can be calculated, the sum of the distances to each PSF can be calculated, and the TCF with the smallest sum of distances can be selected as the n-TCF.

[0245] For example, MM can also identify one or more TCFs from all or more TCFs of the CBI to which the o-TCF belongs that have available resources that match the demand, and then select one or more TCFs from these one or more TCFs that are closest to one or more PSFs managed by the o-TCF as n-TCF.

[0246] S104: MM performs n-TCF configuration.

[0247] MM configures TCF relocation configuration parameters for n-TCF, and the TCF relocation configuration parameters may include at least one of the following:

[0248] - TCF configuration parameters defined in the mission session configuration phase (e.g., one or more IDs and / or one or more locations of one or more PSFs it manages).

[0249] -o-TCF position

[0250] -TCF data synchronization rules (e.g., the interface and QoS for receiving data from o-TCF), used to synchronize data with o-TCF, will be used in step S105.

[0251] According to some embodiments, the MM can record historical resource usage data of the o-TCF and determine the resource standard of the n-TCF based on the recorded resource usage data. Then, based on the determined resource standard, it can determine whether the n-TCF has sufficient computing / communication resources. For example, the resource standard can be 110%, 120%, etc., higher than the maximum historical data.

[0252] According to some embodiments, the MM can assess the management resources required by one or more TEs managed by the o-TCF, and then determine whether the n-TCF has sufficient computing / communication resources based on the assessment results.

[0253] For example, n-TCF configuration step S104 includes the following sub-steps:

[0254] S1041: MM sends an n-TCF configuration request to n-TCF.

[0255] The n-TCF configuration request configures the n-TCF based on the TCF relocation configuration parameters included in the request.

[0256] S1042: n-TCF sends an n-TCF configuration request response to MM.

[0257] In step S1041, the n-TCF configures / modifies its local settings according to the received TCF relocation configuration parameters. Then, the n-TCF sends the response to the MM to indicate that the n-TCF configuration is complete.

[0258] It should be noted that step S1042 is optional.

[0259] S105: MM triggers TCF synchronization.

[0260] After n-TCF configuration, MM can trigger the TCF synchronization process.

[0261] Specifically, the MM copies the local settings / parameters of the o-TCF to the n-TCF. The local settings / parameters of the o-TCF may include at least one of the following: information on one or more completed TEs (e.g., one or more TE IDs); information on one or more ongoing TEs (e.g., one or more TE IDs and the percentage of TE completion); information on one or more loaded management schemes / algorithms; intermediate parameters of one or more running schemes / algorithms used to manage one or more TEs, etc.

[0262] For example, several types of loaded management schemes or algorithms are stored in the TCF or the cloud. The information of one or more loaded management schemes / algorithms can be at least one ID or at least one name of a scheme / algorithm(s). Based on this, the n-TCF can obtain one or more loaded management schemes / algorithms and use them to manage one or more TEs.

[0263] According to some embodiments, the MM can send a message to the o-TCF to trigger the o-TCF to initiate a synchronization process. The sub-steps involved in step S105 include at least one of the following:

[0264] S1051: TCF synchronization request from MM to o-TCF.

[0265] The TCF synchronization request from MM to o-TCF is used to request o-TCF to synchronize its local settings / parameters to n-TCF. The TCF synchronization request includes: (1) the ID / name and location of n-TCF; (2) TCF data synchronization rules (e.g., for sending o-TCF's local settings / parameters to n-TCF's interface and QoS) to synchronize data with n-TCF.

[0266] According to some embodiments, each ID of an n-TCF corresponds to each n-TCF.

[0267] S1052: o-TCF sends TE pause request / receives TE pause response.

[0268] o-TCF can send a TE pause request to one or more associated PSFs of one or more ongoing TEs to pause one or more TEs.

[0269] This behavior prevents one or more ongoing TEs from being affected by TCF relocation. One or more related PSFs can send a TE pause request response to o-TCF after one or more PSFs have been paused. It should be noted that this step of sending a TE pause request response is optional.

[0270] According to some embodiments, a TE pause request may include TE information, such as the TE ID (the ID of the CBI running the TE + mission session).

[0271] S1053: Perform TCF data synchronization between o-TCF and n-TCF.

[0272] According to the TCF data synchronization rules received in step S1051, the o-TCF synchronizes its local settings / parameters with the n-TCF.

[0273] S1054: Response to TCF synchronization request from o-TCF to MM.

[0274] The TCF synchronization request response notifies the MM that the o-TCF local settings / parameters have been synchronized with the n-TCF.

[0275] It should be noted that step S1054 is optional.

[0276] S1055: n-TCF synchronization completion message from n-TCF to MM.

[0277] The n-TCF synchronization completion message from n-TCF to MM notifies MM that n-TCF has successfully received all settings / parameters from o-TCF. The TCF synchronization process is complete after MM receives messages S1054 and S1055.

[0278] It should be noted that step S1055 is optional.

[0279] According to some embodiments, after TCF synchronization, n-TCF learns all the algorithms, settings and parameters used for TE management, and thus gains the ability to control TE.

[0280] According to some embodiments, after TCF synchronization, n-TCF knows the progress of one or more completed TEs and one or more ongoing TEs, and based on this, n-TCF can precisely continue all or more TEs that need to be continued.

[0281] For example, the first task is managed by the o-TCF and has reached 40% completion. At this point, the MM decides to perform a TCF relocation on the o-TCF. Then, during TCF synchronization, the o-TCF can send information about the first task, its progress (i.e., 40% complete), and the result of the currently 40% completed task to the n-TCF. After receiving this information, the n-TCF can continue executing the first task based on its 40% completion progress.

[0282] According to some embodiments, the MM can send a message to the n-TCF to trigger the n-TCF to initiate a synchronization process. In these embodiments, the MM can send a TCF synchronization request to the n-TCF, and the n-TCF can send a TE pause request to the o-TCF to pause all or one ongoing TEs under the control of the o-TCF. The TE pause request can also instruct the o-TCF to initiate a synchronization process between the o-TCF and the n-TCF.

[0283] S106: MM initiates the PSF association update process.

[0284] After TCF synchronization is complete, MM can further request o-TCF to update the associated TCF information of all or one PSFs managed by it.

[0285] According to some embodiments, the associated TCF information that needs to be updated can be stored in each PSF. Based on this, a PSF can grant administrative permissions to associate with a TCF. For example, if an o-TCF modifies the association information of a PSF from o-TCF to n-TCF, it enables the n-TCF to manage the PSF.

[0286] For example, the sub-steps in step S106 include:

[0287] S1061: PSF association update request from MM to o-TCF.

[0288] The PSF association update request from MM to o-TCF is used to request o-TCF to modify the associated TCF information (i.e., TCF ID / name and location) stored / recorded by all or one PSF managed by o-TCF from o-TCF information to n-TCF information.

[0289] PSF association update requests may include at least one of the following:

[0290] -n-TCF information, namely, the ID / name of the n-TCF and the location of the n-TCF.

[0291] -n-TCF Effective Time / Slot: The scheduled time / slot, used to indicate the PSF when the associated TCF information (i.e., n-TCF information) should take effect. This time / slot must be a future time / slot scheduled by MM.

[0292] S1062: The o-TCF sends a PSF customization request to at least one PSF managed by it to change / revise the associated TCF information of each PSF.

[0293] The PSF associated update request includes: (1) n-TCF information; (2) n-TCF validity period.

[0294] S1063: PSF changes / revises the associated TCF information stored / recorded from the o-TCF information to the received n-TCF information during the n-TCF validity period.

[0295] Then, PSF sends a PSF Customization Request response to o-TCF to indicate that the associated TCF information changes are complete.

[0296] S1064: The o-TCF can send a PSF association update request response to the MM to indicate that the PSF association update process is complete. This can occur after receiving a PSF customization request response from all or more PSFs managed by the o-TCF.

[0297] According to some embodiments, without a PSF association update process, one or more PSFs cannot be accessed or managed by the n-TCF or one or more other TCFs other than the o-TCF, thereby ensuring data security on the PSF side. After the PSF association update process, one or more PSFs are associated with the n-TCF and cannot be accessed or managed by one or more other TCFs, including the o-TCF.

[0298] S107: n-TCF performs a handshake with one or more PSFs.

[0299] In some implementations, the n-TCF can trigger a handshake process (e.g., a three-way handshake) with each PSF it manages to test the connection between the n-TCF and the PSF.

[0300] It should be noted that step S107 is optional.

[0301] According to some embodiments, the handshake process of the n-TCF can be based on a preset frequency, such as triggering a handshake process once every preset time interval, to determine whether the PSF can be successfully managed by the n-TCF. Therefore, the n-TCF can double-check whether it is successfully associated with one or more PSFs and detect successful relocation as early as possible, so that the n-TCF can provide timely feedback to the MM, thereby enabling the MM to continue subsequent operations, such as releasing the o-TCF.

[0302] S108: Notification of TCF relocation completion from n-TCF to MM.

[0303] The TCF relocation completion notification from n-TCF to MM can notify MM that the TCF relocation process is complete.

[0304] According to some embodiments, after n-TCF performs S107 and the handshake is successful, a TCF relocation completion notification can be sent to MM.

[0305] According to some embodiments, after the n-TCF successfully manages one or more PSFs for TE, a TCF relocation completion notification can be sent to the MM.

[0306] S109: MM sends an o-TCF release request / receives an o-TCF release response.

[0307] In some implementations, the MM can send an o-TCF release request to the o-TCF to delete the o-TCF's local settings / parameters and release the associated storage / computing resources.

[0308] o-TCF can send an o-TCF release request response after deleting o-TCF local settings / parameters and releasing associated storage / computing resources.

[0309] It should be noted that step S109 is optional.

[0310] According to some embodiments, by synchronizing the parameter information in the o-TCF to the n-TCF and changing all information in the PSF managed by the o-TCF that is associated with the o-TCF to be associated with the n-TCF, this method achieves efficient relocation from the o-TCF to the n-TCF and enables the n-TCF to successfully control the PSF managed by the o-TCF to perform TE.

[0311] The TCF relocation process can achieve dynamic TCF relocation during the ME process, which can solve the problems of TCF resource scarcity and suboptimal deployment.

[0312] As mentioned above, the MM needs to determine whether to relocate the o-TCF and needs to determine the n-TCF from one or more available TCFs, which requires the MM to know information about each of the one or more TCFs and one or more PSFs.

[0313] In some embodiments, MM can subscribe to TCF / PSF information.

[0314] like Figure 8 As shown, the present invention provides a method for TCF / PSF information subscription.

[0315] The TCF / PSF information subscription process can be used in the TCF relocation process mentioned above. The TCF / PSF information subscription process enables the MM to have up-to-date information on any available TCF and PSF resources provided by the XaaS service. A network repository function (NRF) that stores information on one or more available TCFs and one or more PSFs participates in the TCF / PSF information subscription process.

[0316] According to some embodiments, after learning information about available TCFs, the MM can determine the n-TCFs that meet the requirements from all available TCFs. According to some embodiments, after learning information about available PSFs, when the PSF managed by the TCF is overloaded, the MM can select at least one PSF from the available PSFs to join one or more PSFs managed by the TCF. This allows one or more updated PSFs to meet the execution load requirements.

[0317] Figure 8 The TCF / PSF information subscription process is shown and may include at least one of the following:

[0318] S201: n-PSF / TCF information subscription request from MM to NRF.

[0319] The MM requests to subscribe to available TCF and / or PSF information from the NRF. The n-PSF / TCF information subscription request may include at least one of the following requirements:

[0320] - Subscription feature type (TCF, PSF, or both);

[0321] - Subscribed XaaS service information (e.g., XaaS service ID / name). This section describes the XaaS services associated with the subscribed TCF and PSF information.

[0322] - Information update methods: event-triggered updates or periodic updates. In event-triggered updates, the MM immediately receives information about the new TCF / PSF (n-TCF / PSF) after it has been registered with the NRF. In periodic updates, the MM periodically receives information about all or more n-TCF / PSFs registered with the NRF in the previous period. If the periodic update method is selected, the update period (e.g., every 12 hours, daily) can be specified in the n-PSF / TCF information subscription request.

[0323] S202: Response to n-PSF / TCF information subscription request from NRF to MM.

[0324] The n-PSF / TCF information subscription request response notifies the MM that the NRF has accepted the n-PSF / TCF information subscription request.

[0325] S203: XaaS service triggers n-TCF / PSF information registration.

[0326] Once the XaaS service discovers / initiates an n-TCF / PSF, the XaaS service's service control function (SCF) (e.g., the XaaS service's controller) can trigger the n-TCF / PSF information registration process to register the n-TCF / PSF information in the NRF.

[0327] The n-TCF / PSF information registration process (step S203) may include at least one of the following:

[0328] S2031: n-PSF / TCF information registration request from SCF to NRF.

[0329] The SCF registers its information with the NRF by sending the n-TCF / PSF information to the NRF via an n-PSF / TCF information registration request. This request includes the n-TCF / PSF information.

[0330] Information about an n-TCF may include at least one of the following: (1) the ID / name of the n-TCF; (2) the location of the n-TCF; (3) the available storage / computing resources on the n-TCF; (4) one or more available interfaces connecting to the n-TCF; and (5) one or more IDs and / or locations of the PSFs it manages. Information about an n-PSF may include at least one of the following: (1) the ID / name of the n-PSF; (2) the location of the n-PSF; (3) the available storage / computing resources on the n-PSF; and (4) one or more available interfaces connecting to the n-PSF; etc.

[0331] S2032: NRF performs PSF / TCF dataset updates.

[0332] NRF updates the local PSF / TCF dataset by adding the n-TCF / PSF information received in step S2031.

[0333] S2033: Response to n-PSF / TCF information registration request from NRF to SCF.

[0334] The n-PSF / TCF information registration request response notifies the SCF that n-TCF / PSF information registration is complete. This is optional.

[0335] It should be noted that step S2033 may occur before step S2031 or step S2032.

[0336] S204: n-PSF / TCF information update from NRF to MM.

[0337] The NRF sends n-TCF / PSF information to the MM according to the requirements defined in the n-PSF / TCF information subscription request received in step S201.

[0338] S205: n-PSF / TCF information update response from MM to NRF.

[0339] The n-PSF / TCF information update response notifies the NRF that updated n-TCF / PSF information has been received.

[0340] If step S203 occurs before step S201 or step S202, then steps 204 and 205 may not be necessary.

[0341] It should be noted that step S203 can occur more than once. For each occurrence of step S203, corresponding steps S204 and S205 can occur, or one step S204 and step S205 can correspond to more than one step S203. The TCF / PSF information subscription process enables MM to subscribe to information from one or more available TCF / PSFs provided by one or more XaaS services. The information from one or more available TCF / PSFs can be used during TCF and PSF relocation processes.

[0342] according to Figure 8 In the illustrated embodiment, the MM can monitor the PSF / TCF in real time through SCF / NRF, enabling the MM to detect TCF overload or PSF relocation in a timely manner, so as to quickly initiate TCF relocation and thus avoid TCF overload.

[0343] Illustratively, see reference Figure 9 , Figure 9A schematic block diagram of an apparatus provided in some embodiments of the present invention is shown. Apparatus 1000 includes a processor 1010. The processor 1010 is coupled to a memory 1020. The memory 1020 is used to store computer programs or instructions and / or data. The processor 1010 is used to execute the computer programs or instructions and / or data stored in the memory 1020 to perform the methods described in the method embodiments above.

[0344] In some embodiments, the device 1000 includes one or more processors 1010.

[0345] In some embodiments, such as Figure 9 As shown, the device 1000 may also include a memory 1020.

[0346] In some embodiments, device 1000 may include one or more memories 1020.

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

[0348] In some embodiments, such as Figure 9 As shown, device 1000 may further include a communication interface 1030 for communicating with other devices / chips / devices / chipsets. For example, processor 1010 may receive signals via a receiver or transmit signals via a transmitter through communication interface 1030. As another example, processor 1010 may store data in or retrieve data from memory through communication interface 1030.

[0349] In some embodiments, a detailed description of the processor 1010 may be found in the processors 90 / 260 / 276 described above.

[0350] In some embodiments, a detailed description of memory 1020 may be found in memory 208 / 258 / 278 described above.

[0351] In some embodiments, the device 1000 may include more modules.

[0352] In some embodiments, device 1000 can be used as a BS or UE. Furthermore, device 1000 can execute instructions to implement... Figure 7 and Figure 8 The steps performed by the UE.

[0353] In some embodiments, device 1000 may be a chip or chipset.

[0354] While this invention has been described with reference to illustrative embodiments, it is not intended to be construed as limiting. Those skilled in the art will recognize, upon referring to this description, various modifications and combinations of the illustrative embodiments, as well as other embodiments of the invention.

[0355] Additionally or alternatively, features disclosed herein in the context of any particular embodiment may be implemented in other embodiments. For example, method embodiments may be implemented in apparatus, system, and / or computer program product embodiments. Furthermore, although embodiments are described primarily in the context of methods and apparatus, other implementations are contemplated, for example, as instructions stored in one or more non-transitory computer-readable media. These media may store programming or instructions to perform any of the various methods consistent with the present invention.

[0356] Although various aspects of the invention have been described with reference to specific features and embodiments thereof, various modifications and combinations thereof can be made without departing from the invention. The specification and drawings are therefore to be regarded only as illustrative of some embodiments of the invention as defined in the appended claims, and any and all modifications, variations, combinations, or equivalents covering the scope of the invention are contemplated. Therefore, while the invention and its potential advantages have been described in detail, various changes, substitutions, and alterations may be made herein without departing from the invention as defined in the appended claims. Furthermore, the scope of this application is not limited to the specific embodiments of the processes, machines, articles of manufacture, material compositions, modules, methods, and steps described in the specification. Those skilled in the art will readily understand from the disclosure of this invention that processes, machines, articles of manufacture, material compositions, modules, methods, or steps (including those currently existing or later developed) can be used according to the invention to perform or achieve substantially the same function or result as the corresponding embodiments described herein. Therefore, the appended claims are intended to include such processes, machines, articles of manufacture, material compositions, modules, methods, or steps within their scope.

[0357] Furthermore, any module, component, or device executing instructions illustrated herein may include or otherwise access one or more non-transitory computer-readable or processor-readable storage media to store information, such as computer-readable or processor-readable instructions, data structures, program modules, and / or other data. A non-exhaustive list of examples of non-transitory computer-readable or 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 (DVD), Blu-ray™ and other optical discs, volatile and non-volatile, removable and non-removable media implemented in any method or technology, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, or other storage technologies. Any such non-transitory computer-readable or processor-readable storage medium may be part of a device or may access or be connected to a device. Any application or module described herein may be implemented using computer-readable and executable instructions, or may be stored or otherwise held by a processor by such non-transitory computer-readable or processor-readable storage medium.

[0358] In some aspects of the present invention, a device / chipset system is provided, including components (e.g., at least one processor) for implementing a method implemented by a UE of the present invention (or implemented at a UE of the present invention). The device / chipset system may be a UE (i.e., a terminal device) or a module / component within a UE. Specifically, at least one processor may execute instructions stored in a computer-readable medium to implement the method.

[0359] In some aspects of the invention, a device / chipset system is provided, the device / chipset system including components (e.g., at least one processor) for implementing the methods implemented by a network device (e.g., a base station) of the invention (or at a network device of the invention). The device / chipset system may be a network device or a module / component within a network device. Specifically, at least one processor may execute instructions stored in a computer-readable medium to implement the methods.

[0360] In some aspects of the present invention, a system is provided comprising at least one of means in a UE of the present invention or in a network device of the present invention.

[0361] In some aspects of the invention, a method is provided performed by a system comprising at least one of means in (or at) a UE of the invention and means in (or at) a network device of the invention.

[0362] In some aspects of the present invention, a device / chipset system is provided, including components (e.g., at least one processor) for implementing a method implemented by a UE of the present invention (or implemented 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, TCF, device (i.e., terminal device), or a module / component in a network entity. Specifically, at least one processor may execute instructions stored in a computer-readable medium to implement the method.

[0363] In some aspects of the invention, a system is provided that includes at least two of the network entities mentioned in the invention, such as AF, TCF, devices, etc.

[0364] In some aspects of the invention, a method is provided performed by a system comprising at least two of the network entities mentioned in the invention.

[0365] It should be noted that two or more of the network entities shown in this invention may reside within a physical network entity or be implemented as a single functional entity. In this case, interaction between the two or more of the mentioned network entities may not be necessary; that is, one or more corresponding steps may be omitted (optionally).

[0366] It should be noted that although two or more network entities are shown in this invention, for the exemplary schemes of this invention, only one may be sufficient. For example, in Figure 8 In the example shown, from the MM's perspective, only n-PSF / TCF information subscription requests / responses and n-PSF / TCF information updates / responses are needed. For operations performed by other network entities (e.g., step S203), the MM will not see these operations (or they may be transparent to the MM).

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

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

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

[0370] It should be understood that any module, component, or device disclosing the 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 (DVD), Blu-ray™ and other optical discs, volatile and non-volatile, removable and non-removable media implemented in any method or technology, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other storage technologies. Any such non-transitory computer / processor-readable storage medium may be part of a device or apparatus, or may access or be 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.

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

[0372] Unless otherwise specified, the terms “device” and “equipment” are used interchangeably, as are the terms “identity” and “identifier”.

[0373] In this invention, when used in conjunction with the term "comprising / including" in the claims and / or specification, the word "a / an" 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.

[0374] In this invention, the use of terms such as "first," "second," etc., before the same term (e.g., ED or operational step) does not indicate the order or sequence of those terms. For example, unless specifically stated otherwise, "first ED" and "second ED" refer to two different EDs, and similarly, while this invention describes methods and processes with steps in a specific order, one or more steps of the methods and processes may be omitted or modified as appropriate. Where appropriate, one or more steps may be performed in an order other than that described. For example, unless specifically stated otherwise, "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 logical relationship between the two steps.

[0375] The terms “coupled / coupling” or “connection” as used herein can have several different meanings depending on the context in which they are used. For example, the terms “coupled / coupling” or “connection” as used herein can indicate 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.

[0376] It should be noted that the expression "at least one of A or B" used in this article is interchangeable with the expression "A and / or B". It refers to a list in which either A or B, or both A and B, can be selected. Similarly, the expression "at least one of A, B, or C" used in this article is interchangeable with "A and / or B and / or C" or "A, B, and / or C". It refers to a list in which the following can be selected: A or B or C, or both A and B, or both A and C, or both B and C, or all of A, B, and C. The same principle applies to longer lists with the same format.

[0377] This invention encompasses a variety of embodiments, including not only method embodiments but also other embodiments, such as apparatus embodiments and embodiments related to non-transitory computer-readable storage media. Embodiments may be combined individually or in combination with the features disclosed herein.

[0378] The terms “receive,” “detect,” and “decode” used in this document can have several different meanings depending on the context in which they are used. For example, without specific indication, the term “receive” can refer to the successful reception of information (e.g., DCI, MAC-CE, RRC signaling, or TB) by the receiving node, meaning that the receiving side correctly detected and decoded the information. In this scenario, “receive” can encompass both “detect” and “decode,” or it can refer to the same thing; for example, “receive paging” means correctly decoding the paging and successfully acquiring it, and correspondingly, “received paging” means that the receiving side did not detect and / or decode the paging. “Not received paging” means that the receiving side attempted to detect and / or decode the paging but failed to acquire it. The term “receive” can sometimes indicate that a signal has arrived at the receiving side, but this does not mean that the information in the signal has been correctly detected and decoded. The receiving side then needs to detect and decode the signal to obtain the information carried in it. In this scenario, “receive,” “detect,” and “decode” can indicate different processes by which the receiving side acquires information.

[0379] While this invention has been described with reference to illustrative embodiments, it is not intended to be construed as limiting. Those skilled in the art will recognize, upon referring to this description, various modifications and combinations of the illustrative embodiments, as well as other embodiments of the invention. When two or more embodiments are combined, not all features of the embodiments to be combined are necessary for the combination.

[0380] Additionally or alternatively, features disclosed herein in the context of any particular embodiment may be implemented in other embodiments. For example, method embodiments may be implemented in apparatus, system, and / or computer program product embodiments. Furthermore, although embodiments are described primarily in the context of methods and apparatus, other implementations are contemplated, for example, as instructions stored in one or more non-transitory computer-readable media. These media may store programming or instructions to perform any of the various methods consistent with the present invention.

[0381]

Claims

1. A first device, characterized in that, include: At least one processor coupled to at least one memory storing computer program code; Wherein, when the computer program code is executed by the at least one processor, the first device performs the following operations: For a first task executed by a first task control function (TCF), it is determined that the first TCF will be replaced by a second TCF, wherein the first TCF and the second TCF are managed by mission management (MM). A first synchronization request, including information about the second TCF, is sent to the first TCF to request the first TCF to send task execution (TE) information to the second TCF, wherein the TE information includes execution information of the first task executed by the first TCF.

2. The first device according to claim 1, characterized in that, When the computer program code is executed by the at least one processor, the first device is also caused to perform the following operations: Send a first update request to the first TCF, including the information of the second TCF, to request that the TCF for managing the processing service function (PSF) be updated from the first TCF to the second TCF.

3. The first device according to claim 1 or 2, characterized in that, The information in the second TCF includes at least one of an identifier (ID), name, location, and validity period.

4. The first device according to any one of claims 1 to 3, characterized in that, When the computer program code is executed by the at least one processor, the first device is also caused to perform the following operations: A configuration request is sent to the second TCF, the configuration request including information about the first TCF and a first synchronization rule.

5. The first device according to claim 4, characterized in that, The information of the first TCF includes at least one of the first TCF's ID, name, and location.

6. The first device according to claim 4 or 5, characterized in that, The first synchronization rule includes a first interface and first establishment information for synchronizing the second TCF.

7. The first device according to claim 1, characterized in that, The first synchronization request is further configured to request the first TCF to send a pause request to the PSF managed by the first TCF, wherein the pause request instructs the PSF to pause the process of the first task.

8. The first device according to any one of claims 1 to 7, characterized in that, When the computer program code is executed by the at least one processor, the first device is also caused to perform the following operations: Receive relocation completion notification from the second TCF.

9. The first device according to claim 8, characterized in that, When the computer program code is executed by the at least one processor, the first device is also caused to perform the following operations: In response to the relocation completion notification, a release request is sent to the first TCF. The release request is used to request the first TCF to delete local settings and release storage and computing resources.

10. The first device according to claim 1, characterized in that, When the computer program code is executed by the at least one processor, the first device is also caused to perform the following operations: Send a subscription request to the network repository function (NRF) to request the NRF to send information about available TCFs to the MM, wherein the NRF receives the information about available TCFs from an X as a service (XaaS) service; Receive the information about available TCFs from the NRF; The second TCF is determined from the available TCF.

11. The first device according to claim 10, characterized in that, The NRF is used to receive registration requests for new TCFs from the service control function (SCF), and update the information about available TCFs based on the registration requests for new TCFs. The receipt of the information about available TCFs from the NRF includes: Receive the information about the new TCF from the NRF.

12. The first device according to claim 10 or 11, characterized in that, The subscription request includes at least one of the following: TCF subscription functionality, information about SCF services, and update time.

13. The first device according to claim 11, characterized in that, The registration request includes at least one of the following: TCF name, TCF location, TCF resources, TCF interface, and information about the PSF managed by the TCF.

14. A second device, characterized in that, include: At least one processor coupled to at least one memory storing computer program code; Wherein, when the computer program code is executed by the at least one processor, the second device: Receive a first synchronization request from MM, including information from the second TCF; In response to the first synchronization request, TE information is sent to the second TCF, wherein the TE information includes execution information of the first task executed by the first TCF.

15. The second device according to claim 14, characterized in that, When the computer program code is executed by the at least one processor, the second device is also enabled: Receive a first update request from the MM, including the information from the second TCF; Update the TCF that manages the PSF from the first TCF to the second TCF.

16. The second device according to claim 15, characterized in that, The at least one memory and the computer program code are used, together with the at least one processor, to also cause the second device to update the relevant TCF in the following manner: In response to the first update request, a second update request is sent to the PSF managed by the first TCF. The second update request includes information about the second TCF, and is used to request the PSF managed by the first TCF to update the TCF managing the PSF from the first TCF to the second TCF.

17. The second device according to any one of claims 14 to 16, characterized in that, The first synchronization request also includes a second synchronization rule, which includes a second interface and second establishment information for synchronizing the second TCF. The at least one memory and the computer program code are used, together with the at least one processor, to further enable the second device to transmit the TE information in the following manner: Based on the second establishment information used for synchronization, the TE information is sent to the second TCF through the second interface.

18. The second device according to claim 15 or 16, characterized in that, When the computer program code is executed by the at least one processor, the second device is also enabled: A pause request is sent to the PSF managed by the first TCF, wherein the pause request instructs the PSF managed by the first TCF to pause the first task.

19. The second device according to any one of claims 14 to 18, characterized in that, When the computer program code is executed by the at least one processor, the second device is also enabled: Receive a release request from the MM; Delete local settings and free up storage and computing resources; Send a response to the release request to the MM to confirm the completion of deleting the local settings and releasing the storage and computing resources.

20. A third device, characterized in that, include: At least one processor coupled to at least one memory storing computer program code; Wherein, when the computer program code is executed by the at least one processor, the third device: Receive TE information from the first TCF, wherein the TE information includes execution information of a first task executed by the first TCF; Based on the TE information, the first task is executed through the PSF managed by the second TCF.

21. The third device according to claim 20, characterized in that, The at least one memory and the computer program code are used, together with the at least one processor, to further enable the third device to perform the first task in the following manner: The first task is performed through the PSF, and the relevant TCF of the PSF is updated from the first TCF to the second TCF based on the TE information.

22. The third device according to claim 20 or 21, characterized in that, When the computer program code is executed by the at least one processor, the third device is also enabled: A configuration request is received from the MM, the configuration request including information about the first TCF and a first synchronization rule.

23. The third device according to claim 22, characterized in that, The information of the first TCF includes at least one of the first TCF's ID, name, and location.

24. The third device according to claim 22, characterized in that, The first synchronization rule includes a first interface and first establishment information for synchronizing the second TCF.

25. The third device according to claim 24, characterized in that, The at least one memory and the computer program code are configured, together with the at least one processor, to enable the third device to receive the configuration request in the following manner: Based on the first establishment information for synchronization, the configuration request is received from the MM through the first interface.

26. The third device according to any one of claims 22 to 25, characterized in that, When the computer program code is executed by the at least one processor, the third device is also enabled: Send a relocation completion notification to the MM.

27. A method applied to MM, characterized in that, include: Determine the first TCF to be relocated and the second TCF to replace the first TCF; A first synchronization request, including information about the second TCF, is sent to the first TCF managed by the MM to request the first TCF to send TE information to the second TCF, wherein the TE information includes execution information of a first task performed by the first TCF.

28. The method according to claim 27, characterized in that, Also includes: Send a first update request to the first TCF, including the information of the second TCF, to request that the TCF for managing the processing service function (PSF) be updated from the first TCF to the second TCF.

29. The method according to claim 27 or 28, characterized in that, The information in the second TCF includes at least one of an identifier ID, name, location, and validity period.

30. The method according to any one of claims 27 to 29, characterized in that, Also includes: A configuration request is sent to the second TCF, the configuration request including information about the first TCF and a first synchronization rule.

31. The method according to claim 30, characterized in that, The information of the first TCF includes at least one of the first TCF's ID, name, and location.

32. The method according to claim 30 or 31, characterized in that, The first synchronization rule includes a first interface and first establishment information for synchronizing the second TCF.

33. The method according to claim 28, characterized in that, The first synchronization request is further configured to request the first TCF to send a pause request to the PSF managed by the first TCF, wherein the pause request instructs the PSF managed by the first TCF to pause the first task.

34. The method according to any one of claims 27 to 33, characterized in that, Also includes: Receive relocation completion notification from the second TCF.

35. The method according to any one of claims 27 to 34, characterized in that, Also includes: In response to the relocation completion notification, a release request is sent to the first TCF. The release request is used to request the first TCF to delete local settings and release storage and computing resources.

36. The method according to claim 27, characterized in that, Also includes: Send a subscription request to the NRF to request the NRF to send information about available TCFs to the MM, wherein the NRF receives the information about available TCFs from XaaS; Receive the information about available TCFs from the NRF; The second TCF is determined from the available TCF.

37. The method according to claim 36, characterized in that, The NRF is used to receive registration requests for new TCFs from the Service Control Function (SCF), and update the information about available TCFs based on the registration requests for new TCFs. The receipt of the information about available TCFs from the NRF includes: Receive the information about the new TCF from the NRF.

38. The method according to claim 36 or 37, characterized in that, The subscription request includes at least one of the following: TCF subscription functionality, information about SCF services, and update time.

39. The method according to claim 37, characterized in that, The registration request includes at least one of the following: TCF name, TCF location, TCF resources, TCF interface, and information about the PSF managed by the TCF.

40. A method applied to a first TCF, characterized in that, include: Receive a first synchronization request from MM, including information from the second TCF; In response to the first synchronization request, TE information is sent to the second TCF, wherein the TE information includes execution information of the first task executed by the first TCF.

41. The method according to claim 40, characterized in that, Also includes: Receive a first update request from the MM, including the information from the second TCF; Update the relevant TCF of the PSF managed by the first TCF to the second TCF.

42. The method according to claim 41, characterized in that, Updating the relevant TCF of the PSF managed by the first TCF to the second TCF includes: In response to the first update request, a second update request is sent to the PSF managed by the first TCF. The second update request includes information about the second TCF, and is used to request the PSF managed by the first TCF to update the relevant TCF from the first TCF to the second TCF.

43. The method according to any one of claims 40 to 42, characterized in that, The first synchronization request also includes a second synchronization rule, which includes a second interface and second establishment information for synchronizing the second TCF. Sending TE information to the second TCF includes: Based on the second establishment information used for synchronization, the TE information is sent to the second TCF through the second interface.

44. The method according to claim 41 or 42, characterized in that, Also includes: A pause request is sent to the PSF managed by the first TCF, wherein the pause request instructs the PSF managed by the first TCF to pause the first task.

45. The method according to any one of claims 40 to 44, characterized in that, Also includes: Receive a release request from the MM; Delete local settings and free up storage and computing resources.

46. ​​A method applied to a second TCF, characterized in that, include: Receive TE information from the first TCF, wherein the TE information includes execution information of a first task executed by the first TCF; Based on the TE information, the first task is executed through the PSF managed by the second TCF.

47. The method according to claim 46, characterized in that, Performing the first task includes: The first task is performed through the PSF, and the relevant TCF of the PSF is updated from the first TCF to the second TCF based on the TE information.

48. The method according to claim 46 or 47, characterized in that, Also includes: A configuration request is received from the MM, the configuration request including information about the first TCF and a first synchronization rule.

49. The method according to claim 48, characterized in that, The information of the first TCF includes at least one of the first TCF's ID, name, and location.

50. The method according to claim 48, characterized in that, The first synchronization rule includes a first interface and first establishment information for synchronizing the second TCF.

51. The method according to claim 50, characterized in that, The TE information received from the first TCF includes: Based on the first establishment information for synchronization, the configuration request is received from the MM through the first interface.

52. The method according to any one of claims 48 to 51, characterized in that, Also includes: Send a relocation completion notification to the MM.

53. A first device applied to MM, characterized in that, Includes modules for the following operations: Determine the first TCF to be relocated and the second TCF to replace the first TCF; A first synchronization request, including information about the second TCF, is sent to the first TCF managed by the MM to request the first TCF to send TE information to the second TCF, wherein the TE information includes execution information of a first task performed by the first TCF.

54. A second device applied to a first TCF, characterized in that, Includes modules for the following operations: Receive a first synchronization request from MM, including information from the second TCF; In response to the first synchronization request, TE information is sent to the second TCF, wherein the TE information includes execution information of the first task executed by the first TCF.

55. A third device applied to a second TCF, characterized in that, Includes modules for the following operations: Receive TE information from the first TCF, wherein the TE information includes execution information of a first task executed by the first TCF; Based on the TE information, the first task is executed through the PSF managed by the second TCF.

56. A computer-readable medium, characterized in that, Includes program instructions for causing the apparatus to perform at least the method according to any one of claims 27 to 39, 40 to 45, or 46 to 52.

Images