Apparatus, method, device and readable storage medium for resource management

Abstract

A device, method, apparatus, and readable storage medium for resource management are provided. According to one embodiment, the apparatus includes a processor coupled to a memory storing computer program code, configured to cause a first device such as an RDF (Resource Resource Provider) to: receive a resource management request including device information of at least one target device; determine a resource management scheme in response to the resource management request; and send information about the resource management scheme to the RDF, wherein the RDF is configured to allocate resources to the at least one target device by executing the resource management scheme. Therefore, communication or computing resources of the target device can be allocated efficiently and rationally.

Description

[0001] Cross-reference to related applications

[0002] This application relates to and claims priority to the following applications:

[0003] The entire contents of U.S. Provisional Patent Application No. 63 / 594,112, filed on October 30, 2023, entitled “Method, Apparatus, and System for AI-enabled device-level resource management,” are incorporated herein by reference. Technical Field

[0004] This invention relates to the field of communication technology, and more particularly to a device, method, apparatus, and readable storage medium for resource management in artificial intelligence (AI) based networks. Background Technology

[0005] With the transformation and evolution of wireless networks, communication networks are trending towards entirely new architectures. 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.

[0006] In the proposed 6G network, both network slicing and network access devices require computing or communication resources. For example, modules providing AI services in the service layer need computing resources. If these resources are not allocated reasonably, some resources may become oversaturated while others remain idle. For instance, different modules may use the same resources, causing some modules to fail to utilize the resources successfully, thus affecting business processing efficiency. Summary of the Invention

[0007] To address the aforementioned problems, a device, method, apparatus, and readable storage medium for resource management are described, wherein resources of a target device can be allocated efficiently.

[0008] According to a first aspect, a first device for resource management 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: receiving a resource management request including device information of at least one target device; determining a resource management scheme in response to the resource management request; and sending information of the resource management scheme to a resource management operation function (ROF), the ROF being used to allocate resources to at least one target device by executing the resource management scheme.

[0009] Based on some of the described implementation methods, RDF can assist RM clients with resource management needs in coordinating resource management tasks, including determining one or more RM schemes. ROF can then execute one or more RM schemes to allocate resources. Therefore, for target devices in a communication system, an appropriate RM scheme determines the resources to be allocated to each target device, enabling optimal resource management as required by the client.

[0010] In one possible implementation of the first aspect, the resource management request further includes at least one of resource type information, scenario information, resource management method requirements, training data requirements, and execution parameter requirements for resource management.

[0011] In one possible implementation of the first aspect, determining the resource management scheme includes: determining a resource management method that matches the resource management request; and determining the resource management scheme based on the resource management method.

[0012] In one possible implementation of the first aspect, the resource management method includes at least one of algorithms, models, formulas, and functions.

[0013] In one possible implementation of the first aspect, the first device includes at least one first resource management method, and determining the resource management method that matches the resource management request includes: determining the first resource management method that matches the resource management request from at least one first resource management method.

[0014] In one possible implementation of the first aspect, determining the resource management method matching the resource management request includes: sending a method request to an external library configured with at least one second resource management method, the method request including information from the resource management request, and instructing the external library to determine a second resource management method from the at least one second resource management method that matches the resource management request; and receiving a method response from the external library instructing the second resource management method.

[0015] In one possible implementation of the first aspect, determining the resource management scheme according to the resource management method includes: determining the resource management task according to the resource management method; sending an execution request including the resource management task to an external network; receiving an execution response from the external network, the execution response including the execution result of the external network executing the resource management task; and determining the resource management scheme based on the execution result.

[0016] In one possible implementation of the first aspect, determining the resource management scheme according to the resource management method includes: determining a sub-task for each of one or more external networks according to the resource management method; sending an execution request including the sub-task of each external network to each external network; receiving an execution response from each external network, the execution response including the execution result of the sub-task of each external network; and determining the resource management scheme based on at least one execution result corresponding to at least one of the one or more external networks.

[0017] In one possible implementation of the first aspect, determining the sub-task of each of one or more external networks according to the resource management method includes: sending a capability query to each external network; receiving a capability query response from each external network that includes the capabilities of each external network; and determining the sub-task of each external network based on the capabilities of each external network and a resource management method that matches the resource management request.

[0018] In one possible implementation of the first aspect, determining the resource management scheme according to the resource management method includes: determining the resource management task according to the resource management method; sending an execution request including the resource management task to the mission management (MM); receiving an execution response from the MM, the execution response including the execution result of the MM executing the resource management task; and determining the resource management scheme based on the execution result.

[0019] According to a second aspect, a second device for resource management is described, comprising: at least one processor coupled to at least one memory including computer program code; wherein, when the computer program code is executed by the at least one processor, the second device causes to: receive information on a resource management scheme from a resource management decision function (RDF), the resource management scheme being determined by the RDF in response to a resource management request; and execute the resource management scheme to control the resources allocated to the target device.

[0020] According to a third aspect, a resource management method applied to an RDF is described, comprising: receiving a resource management request including device information of at least one target device; determining a resource management scheme in response to the resource management request; and sending information of the resource management scheme to a ROF in a communication system, wherein the ROF is used to allocate resources to at least one target device by executing the resource management scheme.

[0021] In one possible implementation of the third aspect, the resource management request also includes at least one of the following: resource type information, scenario information, resource management method requirements, training data requirements, and execution parameter requirements for resource management.

[0022] In one possible implementation of the third aspect, determining the resource management scheme includes: determining a resource management method that matches the resource management request; and determining the resource management scheme based on the resource management method.

[0023] In one possible implementation of the third aspect, the resource management method includes at least one of algorithms, models, formulas, and functions.

[0024] In one possible implementation of the third aspect, RDF includes at least one first resource management method, and determining the resource management method that matches the resource management request includes: determining the first resource management method that matches the resource management request from at least one first resource management method.

[0025] In one possible implementation of the third aspect, determining the resource management method that matches the resource management request includes: sending a method request to an external library configured with at least one second resource management method, the method request including information from the resource management request, and instructing the external library to determine the second resource management method that matches the resource management request from the at least one second resource management method; and receiving a method response from the external library that instructs the second resource management method.

[0026] In one possible implementation of the third aspect, determining the resource management scheme according to the resource management method includes: determining the resource management task according to the resource management method; sending an execution request including the resource management task to an external network; receiving an execution response from the external network, the execution response including the execution result of the resource management task executed by the external network; and determining the resource management scheme based on the execution result.

[0027] In one possible implementation of the third aspect, determining the resource management scheme according to the resource management method includes: determining a sub-task for each of one or more external networks according to the resource management method; sending an execution request including the sub-task of each external network to each external network; receiving an execution response from each external network, the execution response including the execution result of the sub-task of each external network; and determining the resource management scheme based on at least one execution result corresponding to at least one of the one or more external networks.

[0028] In one possible implementation of the third aspect, determining the sub-task of each of one or more external networks according to the resource management method includes: sending a capability query to each external network; receiving a capability query response from each external network that includes the capabilities of each external network; and determining the sub-task of each external network based on the capabilities of each external network and the resource management method that matches the resource management request.

[0029] In one possible implementation of the third aspect, determining the resource management scheme according to the resource management method includes: determining the resource management task according to the resource management method; sending an execution request including the resource management task to the mission management (MM); receiving an execution response from the MM, the execution response including the execution result of the MM executing the resource management task; and determining the resource management scheme based on the execution result.

[0030] According to the fourth aspect, a resource management method applied to ROF is described, comprising: receiving a resource management scheme from an RDF in a communication system, wherein the resource management scheme is determined by the RDF in response to a resource management request; and executing the resource management scheme to control the resources allocated to the target device.

[0031] According to a fifth aspect, a first apparatus for use with an RDF is described, comprising means for: receiving a resource management request including device information of at least one target device; determining a resource management scheme in response to the resource management request; and sending information of the resource management scheme to a ROF in a communication system, wherein the ROF is used to allocate resources to at least one target device by executing the resource management scheme.

[0032] According to the sixth aspect, a second apparatus for use with a Resource Provider (ROF) is described, comprising means for: receiving a resource management scheme from an RDF in a communication system, wherein the resource management scheme is determined by the RDF in response to a resource management request; and executing the resource management scheme to control the resources allocated to a target device.

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

[0034] In an eighth aspect, a chip is provided. The chip includes at least one processing circuit for performing a method of any of the foregoing aspects or any possible implementation thereof.

[0035] According to the ninth aspect, a communication system including an RDF and a ROF is described, wherein the RDF is used to: receive a resource management request including device information of at least one target device; determine a resource management scheme in response to the resource management request; send information of the resource management scheme to the ROF in the communication system, the ROF being used to allocate resources to at least one target device by executing the resource management scheme; and the ROF being used to: receive a resource management scheme from the RDF in the communication system, wherein the resource management scheme is determined by the RDF in response to the resource management request; and execute the resource management scheme to control the resources allocated to the target device. Attached Figure Description

[0036] The above-described invention and the following detailed description of exemplary embodiments will be better understood when read in conjunction with the accompanying drawings. For illustrative purposes, details, which are currently preferred, are shown in the drawings according to some embodiments. However, the description is not limited to the specific arrangements and tools shown.

[0037] Figure 1 Schematic diagrams of some example communication systems are shown;

[0038] Figure 2 Schematic diagrams of some example communication systems are shown;

[0039] Figure 3 A schematic diagram of a device 310 that wirelessly communicates with at least one of two devices is shown, illustrating some examples.

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

[0041] Figure 5 The diagram shows some examples of 6G systems;

[0042] Figure 6 The diagram shows some examples of device-level RM systems for AI-enabled applications;

[0043] Figure 7 Schematic flowcharts illustrating some examples of resource management methods are shown;

[0044] Figure 8 Schematic flowcharts illustrating some examples of resource management methods are shown;

[0045] Figure 9 Schematic flowcharts illustrating some examples of resource management methods are shown;

[0046] Figure 10 Schematic flowcharts illustrating some examples of resource management methods are shown;

[0047] Figure 11 Schematic flowcharts illustrating some examples of resource management methods are shown;

[0048] Figure 12 Schematic diagrams of the structure of some example first or second devices are shown. Detailed Implementation

[0049] The illustrative embodiments described include, but are not limited to, devices, methods, apparatuses, and readable storage media for resource management.

[0050] Many new trends will trigger thinking and design for 6G / future wireless networks:

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

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

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

[0054] - A more globalized / open / collaborative operating trend, namely, a more open and collaborative operating model is becoming a common practice in many fields.

[0055] New expectations and stricter requirements for future networks have also driven a rethinking and development of next-generation wireless networks. These requirements include...

[0056] - Privacy and trustworthiness, etc.

[0057] -Simplify standardization

[0058] - Rapid deployment

[0059] -etc.

[0060] All of the above have promoted research on 6G network architecture.

[0061] Our proposed 6G network architecture (centered on X) has the following characteristics:

[0062] -Based on SBA (XaaS service)

[0063] -Cloud Native

[0064] 6G system network architecture design requirements:

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

[0066] - The proposed 6G network architecture needs to build a more open ecosystem, opening the door to technically capable third parties.

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

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

[0069] In the proposed 6G network, resource management (RM) is a crucial network service responsible for network slicing and the allocation and scheduling of network resources for devices accessing the network. AI / ML-based resource management schemes / algorithms can be applied to RM to generate network resource allocation and scheduling decisions.

[0070] When a device accesses an application through a communication system (e.g., a 5G system or a future 6G system), the communication system connects the device to the application location—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 the application, it communicates with the application server via the data plane path. There may be more than one application location. When multiple devices access the application, the communication system can connect multiple devices to different application locations.

[0071] The purpose of providing this background information is to disclose information that the applicant believes may be relevant to the present invention. It is not necessarily an admission, nor should any of the foregoing information be construed as constituting prior art in relation to the present invention.

[0072] In the following description, reference is made to the accompanying drawings, which form part of this invention, illustrating by way of description specific aspects of the invention or its applicability. It should be understood that one aspect of the invention can be used in other aspects and includes 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.

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

[0074] refer to Figure 1The simplified schematic diagram of the communication system is provided as an illustrative example and not a limitation. 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 2nd-generation, 2G) RAN. One or more electronic devices (EDs) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (collectively referred to as 110) may interconnect with each other or be connected to one or more network nodes (170a, 170b, collectively 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.

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

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

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

[0078] 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 create a heterogeneous network that can be considered as comprising multiple layers. Heterogeneous networks can achieve better overall performance through efficient multi-link joint operation between terrestrial and non-terrestrial networks, more flexible function sharing, and faster physical layer link switching.

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

[0080] 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 (collectively 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, 170b, which are typically referred to as terrestrial transmit and receive points (T-TRP) 170a, 170b. In one implementation, the non-terrestrial communication network 120c includes RAN nodes, such as access nodes (or base stations) 172, which can generally be referred to as a non-terrestrial transmit and receive point (NT-TRP) 172. Based on the similarity of the reference figures, it can be inferred that the non-terrestrial communication network 120c can be considered as 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 a corresponding at least one terrestrial network device, wherein the at least one NTN device acts as a transport layer device, and the corresponding at least one terrestrial network device acts as a RAN node, with the terrestrial network device communicating with the ED through the NTN device. Furthermore, there may be an NTN gateway (i.e., referred to as a terrestrial network device) on the ground that acts as a transport layer device communicating with the NTN device, and the RAN node communicating with the ED through the NTN device and the NTN gateway. In some implementations, the NTN gateway and the RAN node may reside in the same device.

[0081] Alternatively or additionally, any ED 110 can be used to connect, access, or communicate with any T-TRP 170a, T-TRP 170b, and NT-TRP 172, the Internet 150, the core network 130, the PSTN 140, other networks 160, or any combination thereof. In some examples, ED 110a can 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.

[0082] 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 between two or more communication devices via a wireless communication link. 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 that define the transmission of information (e.g., data) via the wireless communication link. The 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 link between a device (e.g., ED 110a) and a device (e.g., ED 110b) (e.g., between two user equipment devices) (e.g., a “LS” link), and / or a link between a non-terrestrial (NT) communication network (e.g., RAN 120c) and a user equipment (e.g., ED 110d). Below are some examples of the components described above.

[0083] 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 (NMA) 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-domain 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 (WF).

[0084] The frame structure component can specify the configuration of a frame or a set of frames. The frame structure component can indicate one or more of the following parameters for a frame or a set of frames: time, frequency, pilot signature, code, subcarrier spacing, cyclic prefix length, or other parameters. The frame structure will be discussed in detail below.

[0085] Multiple access scheme components can specify multiple access technology options, including technologies that define how communication devices share a common physical channel, such as: Code Division Multiple Access (CDMA), Space Division Multiple Access (SDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single-Carrier FDMA (SC-FDMA), also known as Discrete Fourier Transform Spread OFDMA (DFT-s-OFDMA), Low Density Signature Multicarrier CDMA (LDS-MC-CDMA); Non-Orthogonal Multiple Access (NOMA); Pattern Division Multiple Access (PDMA); Lattice Partition Multiple Access (LPMA); Resource Spread Multiple Access (RSMA); and Sparse Code Multiple Access (SDMA). Multiple access (SCMA). Furthermore, multiple access technology options can include: scheduled access versus unscheduled access, also known as unlicensed access; non-orthogonal multiple access versus orthogonal multiple access, for example, via dedicated channel resources (e.g., not shared between multiple communication devices); contention-based shared channel resources versus non-contention-based shared channel resources; and cognitive radio-based access. Air interfaces 190a and 190b can utilize other higher-dimensional signal spaces, which may involve combinations of orthogonal and / orthogonal dimensions.

[0086] Encoding and modulation components specify how information being transmitted can be encoded / decoded and modulated / demodulated to achieve the transmission / reception purpose. Encoding can refer to methods of error detection and forward error correction. Non-limiting examples of encoding options include turbo lattice codes, turbo product codes, fountain codes, low-density parity-check codes, and polar codes. Modulation can simply refer to a star chart (e.g., including modulation techniques and orders), or more specifically to various types of advanced modulation methods, such as layered modulation and low PAPR modulation.

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

[0088] 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 via a link. For some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of ED 110s and one or more NT-TRP 172s for multicast transmission.

[0089] 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 serve as a gateway access between (i) RANs 120a and 120b or EDs 110a, 110b, and 110c or both RANs and EDs and (ii) other networks (e.g., PSTN 140, Internet 150, and other networks 160). Additionally, some or all of EDs 110a, 110b, and 110c may include the ability to communicate with different wireless networks via different radio links using different radio technologies and / or protocols. ED 110a, 110b, and 110c can communicate with a service provider or exchange (not shown) via a wired communication channel and with the Internet 150, but not wirelessly (or also wirelessly). PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include a network of computers and subnets (intranets) or both, and also includes 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 under various wireless access technologies, and also include multiple transceivers required to support these technologies.

[0090] Furthermore, 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 within T-TRP 170 and / or NT-TRP 172. In another implementation, the sensing agent is a separate node with an interface for communicating with core network 130 and / or RAN 120 (e.g., T-TRP 170 and / or NT-TRP 172).

[0091] Figure 3 An example of a device 310 is shown that performs wireless communication 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 middle). Device 320a can be a terrestrial network device (e.g., ED 110). Figure 3 The T-TRP170 shown), device 320b can be a non-terrestrial network device (e.g., Figure 3 (NT-TRP 172 shown). However, this is not a necessary condition. For example, according to the invention, device 320a can be NT-TRP, while 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 described as an example of device 310, T-TRP 170 is described as an example of device 320a, and NT-TRP 172 is described as an example of device 320a. Although there is only one device 310, one device 320a, and one device 320b, 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), more than one T-TRP 170, more than one NT-TRP 172, or one or more T-TRP 170s and one or more NT-TRP 172s.

[0092] The ED 110 is used to connect people, objects, and machines. It can be widely used in various scenarios, including, for example, 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 twin, 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.

[0093] Each ED 110 represents any end-user equipment suitable for wireless operation and may include (or be referred to as, but not limited to) devices such as: user equipment / device (UE), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), MTC device, 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 that include or incorporate the above-mentioned devices (e.g., communication module, modem, or chip). 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 hereinafter as T-TRP 170. Similarly... 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.

[0094] 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. The transmitter 201 and receiver 203 may, for example, be integrated as a transceiver. The transceiver is used to modulate data or other content for transmission by at least one antenna 204 or a network interface controller (NIC). The transceiver is also used to demodulate data or other content received by at least one antenna 204. Each transceiver includes any suitable structure to generate signals for wireless or wired transmission and / or process signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure to transmit and / or receive 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.

[0095] Memory 208 stores instructions. Memory 208 may also store data used, generated, or collected by ED 110. For example, memory 208 may store software instructions or modules that are executed by one or more processing units (e.g., processor 210) to implement some or all of the functions and / or embodiments described herein. 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, processor cache, etc.

[0096] 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 can interact 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 network interface communication. Suitable structures include, for example, speakers, microphones, numeric keypads, keyboards, displays, touch screens, etc.

[0097] 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 receiving transport blocks (TBs), using resources for decoding one of the received TBs, releasing resources for decoding another of the received TBs, and / or receiving configuration information for configuration resources. Specifically, operations may include transmission-related operations for preparing uplink transmissions to NT-TRP 172 and / or T-TRP 170; operations related to processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170; and operations related to processing sidelink transmissions to and from another ED 110. Processing operations related to preparing uplink transmissions may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. Processing operations related to the processing side downlink transmissions may include transmit / receive beamforming, modulation / demodulation, and encoding / decoding symbols. According to embodiments, receiver 203 may receive downlink transmissions (possibly using receive beamforming), and processor 210 may extract signaling from the downlink transmissions (e.g., by detecting and / or decoding signaling). Examples of signaling may be reference signals transmitted by NT-TRP 172 and / or T-TRP 170. In some embodiments, processor 210 implements transmit beamforming and / or receive beamforming based on beam direction indications received from T-TRP 170, such as beam angle information (BAI). In some embodiments, processor 210 may perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as operations related to detecting synchronization sequences, decoding, and obtaining system information. In some embodiments, processor 210 may perform channel estimation (e.g., using reference signals received from NT-TRP 172 and / or T-TRP 170).

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

[0099] The processing components of processor 210, transmitter 201, and receiver 203 can each be implemented by one or more processors, which may be the same or different, to 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 can each be implemented using dedicated circuitry, such as a programmable field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), graphics processing unit (GPU), or hardware accelerators such as artificial intelligence (AI) accelerators.

[0100] In some implementations, ED 110 may be a device (also referred to as a component) such as a communication module, modem, chip, or chipset, including at least one processor 210 and an interface or at least one pin. In this scenario, 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, while receiving information from NT-TRP 172 and / or T-TRP 170 and / or another ED 110 can be referred to as receiving information from an interface or at least one pin, or as receiving information from NT-TRP 172 and / or T-TRP 170 and / or another ED 110 via an interface or at least one pin. Information may include control signaling and / or data. Similar rules apply to other nodes / entities in this invention.

[0101] 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, but the T-TRP may include one or more other components.

[0102] In some implementations, the T-TRP 170 may have other names, such as base station, basetransceiver station (BTS), wireless base station, network node, network equipment, network-side equipment, 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 equipment, 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, or donor node, or a combination thereof. T-TRP 170 may refer to the aforementioned device or a component within the aforementioned device (e.g., a communication module, modem, or chip).

[0103] In some embodiments, the various parts 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 for T-TRP 170 and may be coupled to the device housing the antenna 256 via a communication link (not shown) sometimes referred to as a fronthaul (e.g., a common public radio interface (CPRI)). Therefore, in some embodiments, the term T-TRP 170 may also refer to modules on the network side that perform processing operations such as determining the location of ED 110, resource allocation (scheduling), message generation, and encoding / decoding, and 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 (e.g., by using coordinated multicast) to service ED 110.

[0104] The operations performed by processor 260 include those related to: preparing transmissions for downlink transmissions to ED 110, processing uplink transmissions received from ED 110, preparing transmissions for backhaul transmissions 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 transmissions 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 a beam direction indication, such as a BAI, which scheduler 253 can schedule for transmission. 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 can 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.

[0105] 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 it. Scheduler 253 may schedule uplink, downlink, lateral link, and / or backhaul transports, including issuing scheduling authorizations and / or configuring unscheduled (e.g., “configuration authorization”) resources.

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

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

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

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

[0110] 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 telecommunications base stations and unmanned aerial vehicles. Furthermore, in some implementations, the NT-TRP 172 may be referred to by other names, such as non-terrestrial node, non-terrestrial network equipment, or non-terrestrial base station.

[0111] 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, but the T-TRP may include one or more other components.

[0112] 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, but the NT-TRP may include one or more other components.

[0113] NT-TRP 172 includes a processor 276 for performing operations, including operations 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 another NT-TRP 172, and processing transmissions received via backhaul from T-TRP 170 and / or another NT-TRP 172. Processing operations related to preparing transmissions 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, the processor 276 implements transmit beamforming and / or receive beamforming based on beam direction information (e.g., BAI) received from T-TRP 170. In some embodiments, processor 276 may generate signaling, for example, to configure one or more parameters of ED 110. In some embodiments, NT-TRP 172 implements physical layer processing but does not implement higher-level functions such as medium access control (MAC) or radio link control (RLC) layer functions. Since this is only an example, more generally, NT-TRP 172 may implement higher-level functions in addition to physical layer processing.

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

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

[0116] The processing components of processor 276, transmitter 272, and receiver 274 can each be implemented by one or more processors, which may be the same or different, to execute instructions stored in memory (e.g., memory 278). Alternatively, some or all of the processing components of processor 276, transmitter 272, and receiver 274 can be implemented using dedicated circuitry, such as a programmable FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC. In some embodiments, NT-TRP 172 may actually be multiple NT-TRPs that operate together (e.g., through coordinating multipoint transmissions) to service ED 110.

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

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

[0119] It should be noted that, for simplicity, the term "signaling" used herein may 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 downlink, physical layer signaling can be referred to as downlink control information (DCI) transmitted in the physical downlink control channel (PDCCH). For uplink, physical layer signaling can be referred to as uplink control information (UCI) transmitted in the physical uplink control channel (PUCCH). For sidelinks, signaling between different terminals or sensing devices (e.g., between ED 110i and ED 110j) can be referred to as sidelink control information (SCI) 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 physical layer data channels, such as the physical downlink shared channel (PDSCH) for downlink signaling, the physical uplink shared channel (PUSCH) for uplink signaling, and the physical sidelink shared channel (PSSCH) for sidelink signaling. Higher-layer signaling can also be referred to as static 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 be included in a combination of physical layer signaling and higher layer signaling.

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

[0121] One or more steps of the method provided in this invention can be performed by Figure 4 The corresponding unit or module is executed. Figure 4 Units or modules in a device or apparatus are shown, such as in ED 110, T-TRP 170, or NT-TRP 172. 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 an artificial intelligence (AI) module or a machine learning (ML) module. The corresponding units or modules may be implemented using hardware, one or more components or devices executing software, or a combination thereof. For example, one or more of these units or modules may be circuits such as integrated circuits. Examples of integrated circuits include programmable FPGAs, GPUs, or ASICs. For example, one or more of these units or modules may be logical functions, such as logical functions executed by circuits, by a portion of an integrated circuit, or by software instructions executed by a processor. It should be understood that if these modules are implemented, for example, using software executed by a processor, the processor may retrieve these modules, in whole or in part, as needed, individually or collectively for processing, in one or more instances, and these modules themselves may include instructions for further deployment and instantiation. Similar units or modules apply to other nodes / entities in this invention.

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

[0123] The proposed 6G system architecture is defined as supporting 6G X as a Service (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.

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

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

[0126] Each infrastructure can have its own control and management functions for infrastructure management, represented as C / M functions. Each of these infrastructures belongs to an Infrastructure as a Service type.

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

[0128] Resource Management (RM) as a service provides the ability to manage the lifecycle of various slices and assign over-the-air resources to wireless devices.

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

[0130] Mission Management (MM) as a Service provides the ability to programmatically provide XaaS services at the service layer to deliver task services.

[0131] Confederation Network (CONET) as a Service provides the capability for multiple partners to jointly deliver 6G services. This capability is provided through the formation of consortia, mutual authentication and authorization among partners, and negotiation protocols for recording and tracing selected actions performed by partners, ensuring a trusted environment for the operation of 6G systems.

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

[0133] Connectivity Management (CM) as a service leverages 5G connectivity management capabilities and extends to include the digital world.

[0134] Protocol as a Service (PCA) provides the ability to design customized protocol stacks for services based on identified interfaces.

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

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

[0137] XaaS services in the C / M layer support control and management of the 6G system itself, and also provide support for vertical industries if needed. For example, the RM service can provide air resource management services to the RAN, and can also provide services for vertical industries to allocate air resources to their end customers. XaaS in the C / M layer can be deployed using slicing technology.

[0138] The service layer includes 6G services that provide services to customers. In the 6G system conceptual architecture:

[0139] The AI ​​service is referred to as NET4AI as a Service. This artificial intelligence service provides AI capabilities and supports a variety of AI applications.

[0140] Data collection, data cleaning, 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 (information statistics from any type of sensor, device, network function, etc.).

[0141] Data storage and sharing services are represented as NET4Data as a Service. The service 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 regarding the control of identified data.

[0142] The provision of services for the digital world is 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.

[0143] The 6G blockchain service is represented as NET4BC as a service. The 6G connectivity service is represented as NET4Con as a service. These services provide the capability to support 6G blockchain services.

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

[0145] The service provides the ability to support the exchange of messages and data between new 6G services.

[0146] 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 can be provided by its control and management functions, as well as service-specific data processing capabilities.

[0147] In addition to supporting 6G XaaS services at the service layer, the 6G system also leverages the 5G system to provide vertical services. The difference between 6G XaaS services and those in other vertical industries is that vertical industries are purely customers who require other XaaS services to support their operations, and each XaaS service provides its capabilities to 6G customers.

[0148] In a 6G system, any pair of XaaS services can also act as both customer and provider to each other. Some examples include infrastructure owners providing their resources to XaaS services in the service layer and the client / main layer; RM services potentially requiring the capabilities provided by NET4AI, DAM, and NET4DW for vertical slice resource management; and CONET and NET4Data services potentially requiring the capabilities provided by NET4BC for operation.

[0149] Key concepts of 6G systems include:

[0150] - Define basic XaaS services 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, task management services, etc.

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

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

[0153] -Simplify the 6G system architecture by categorizing basic control and management services and merging them into basic XaaS services in the Control and Management (C / M) layer.

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

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

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

[0157] - Apply BAS or a subset thereof to the infrastructure based on the infrastructure network's capabilities, capacity, and requirements, thereby adapting to various deployment scenarios.

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

[0159] - By introducing a trusted gateway in the data plane and C / M plane of the 6G system, the service-based interface (SBI) is simplified.

[0160] - By introducing CONET capabilities, NET4BC capabilities, and anonymous services provided by trusted GW into the C / M plane and data plane of the 6G system, trustworthiness is improved from the perspective of 6G system operation.

[0161] - By providing unified mutual authentication, ID management (IDM), and data cleansing through SPM, DAM, and 6G blockchain services, trustworthiness is enhanced from the perspective of end-customer privacy protection.

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

[0163] - Introducing the concept of BAS, by defining multiple architectural options, it is possible to support multiple development paths from 5G systems to 6G systems without investing too much effort.

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

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

[0166] According to Figure 6 An RM system according to some embodiments is introduced.

[0167] Figure 6An example of a system for AI-enabled device-level RM is shown.

[0168] System usage Figure 6 The architecture shown executes the AI-enabled device-level RM provided by this invention. Please note that... Figure 3 and Figure 4 The devices, units, and modules shown can also be applied to devices that run RDF and devices that run ROF.

[0169] The architecture includes two functions:

[0170] RM Decision Function (RDF): The RDF determines the RM decision for each device. RM decisions include:

[0171] Information about the RM scheme: the ID / name / description of one or more schemes / algorithms determined by the device to generate RM results locally (e.g., the ID / description of a real-time resource scheduling / access algorithm). The RM results are referred to as the resources allocated / scheduled by the device to perform one or more specific actions (e.g., one or more resource blocks scheduled for data transfer, computing units allocated for data processing).

[0172] Information about the allocated resource set: the ID / description of the resource set (e.g., a shareable RAN resource set accessible to multiple devices), assigned to one or more target devices to generate RM results on the device side. The RM scheme included in the RM decision should generate RM results based on the allocated resource set.

[0173] RDF can be configured on the network side.

[0174] RM operation function (ROF): ROF can be pre-configured on the device side (e.g., on each device) or on the network side (e.g., in the RAN or CN). ROF implements and executes the RM scheme determined by RDF to generate RM results.

[0175] In some implementations, RDF can interact with one or more external network functions that have AI capabilities to determine one or more RM (Real-Time Decision Generation) decisions. For example, RDF can request training data from one or more external training datasets to train the RM decision generation AI; if RDF does not have AI model training capabilities, it can send AI training requests to external AI training functions to train the RM decision generation AI and receive the AI ​​training results (e.g., a well-trained RM decision generation AI model) from the external AI training functions.

[0176] In some implementations, a device using one or more generated RM results can continuously update its local resources and / or environmental changes (e.g., resource consumption ratios on the device) to the RDF to update one or more RM decisions (e.g., if the RM decisions are generated by a reinforcement learning (RL) based scheme / algorithm). If one or more external training datasets are involved, the updated local resources and / or environmental changes can be sent to one or more external training datasets to update the training dataset used to train the RM decision generation AI.

[0177] In some implementations, the RDF can receive RM requests, generate RM decisions based on the RM requests, and then send the RM decisions to the ROF. For example, the RM decision may include information about the RM scheme that determines the allocated resources. After receiving the RM decision, the ROF can execute the RM scheme on the device side or the network side to obtain the RM result, including detailed resources allocated to the device. The ROF can then apply the RM result, for example, to allocate bandwidth resources to a target base station or computing resources to a target server.

[0178] In some implementations, RM requests can include several types of information, such as the type of resource to be managed, device information, and scenario information. Based on this information, RDF can determine which method is suitable for RM requests.

[0179] In some implementations, RDF may have pre-configured RM methods. In others, RDF may also send RM method requests to external network functions to obtain information about external RM methods, which is then integrated with the local RM method information. RDF can then determine the appropriate RM method for the RM request from the integrated set of methods.

[0180] In some implementations, the RM system may also include a Task Management Function (MMF). The RDF can convert a defined RM method adapted to the RM request into an RM task, and then send a task execution request, including the RM task, to the MMF. Upon receiving the task execution request, the MMF can execute the RM task to generate an RM decision, and then send the RM decision to the RDF.

[0181] In some implementations, RDF can interact with one or more external networks with AI capabilities, such as AI-enabled XaaS services. RDF can transform an RM method adapted to an RM request into at least one subtask and assign a specific XaaS service to each subtask. RDF can then send the task request corresponding to each subtask to the corresponding external network. Upon receiving the subtask, the external network can execute it and return the result. RDF can then obtain the RM decision based on all the result data returned by the external network, enabling the external network to leverage its AI capabilities to provide computational services to the RM system, thereby improving the processing efficiency of the RM system.

[0182] Basically, the RM method provided in this embodiment is based on the same inventive concept as the RM system described above.

[0183] According to some embodiments, the Resource Management (RM) system can respond to RM requests in real time and manage the resources of the requested device or network, thereby achieving reasonable resource allocation and rapid deployment. Furthermore, the RM system pre-configures multiple RM methods, which can be selected based on different scenarios and management objectives corresponding to the RM request, thus obtaining a more suitable RM method and generating RM decisions that meet the requester's needs. When necessary, it can also utilize external networks with AI capabilities for AI training and function execution, thereby enhancing its capabilities.

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

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

[0186] In the proposed 6G network, resource management (RM) is a crucial network service responsible for network slicing and the allocation and scheduling of network resources for devices accessing the network. AI / ML-based resource management schemes / algorithms can be applied to RM to generate network resource allocation and scheduling decisions.

[0187] In some implementations, the network directly determines the resource allocation (RM) results for the device (e.g., resource allocation / scheduling). This approach lacks flexibility and cannot adapt to dynamic resource requirements at the device end. For example:

[0188] The network can monitor changes in resource requirements on the device side (e.g., through sensing or device updates) to adjust RM results, but this may involve response latency.

[0189] Furthermore, some AI-based RM algorithms can not only determine the RM result, but also determine the RM scheduling scheme that can be applied by the device for local RM behavior. The solutions mentioned above lack support for outputting RM scheduling scheme information to the device.

[0190] Therefore, this invention provides an AI-based device-level resource management (RM) method. The AI-based device-level RM process may include: RM decision generation and RM decision distribution with or without external NFs (e.g., MM, one or more XaaS services) providing computing / processing capabilities. Furthermore, an AI-based device-level RM system is also provided, including an RM decision function (RDF) and an RM operation function (ROF).

[0191] Specifically, the following is a description of device-level resource management (device-level RM).

[0192] Device-level Resource Management (DRM): The RM service determines and controls the allocation and scheduling of resources from one or more access devices (i.e., one or more target devices) to the network (e.g., RAN). Devices in DRM include any wireless devices connected to the network, such as user equipment (UE), sensors, connected vehicles, etc. Resources that DRM can allocate / schedule include: uplink / downlink spectrum / radio resources, network-side and / or device-side computing resources, device / RAN infrastructure transmission power, beam resources, etc. DRM can be triggered by an RM client, which can be an AF, a device, or RAN infrastructure. In some embodiments, the RM client triggering DRM can also be one or more target devices.

[0193] In 6G networks, device-level RM can leverage internal (e.g., implemented on one or more network functions running the device-level RM) or external (e.g., provided by one or more other network functions or third-party applications) AI / ML capabilities to generate device-level RM decisions; this is known as AI-enabled device-level RM. AI / ML capabilities include computing resources (e.g., central processing unit (CPU), GPU), algorithm resources (e.g., AI / ML models / algorithms), and data resources (e.g., training datasets).

[0194] RDF and ROF are defined in the system architecture section.

[0195] like Figures 7 to 11 As shown, an AI-enabled device-level RM method is provided.

[0196] RM customers (e.g., AF / device / RAN infrastructure (Inf)) can trigger AI-enabled device-level RM processes to request the device-level RM system to generate RM results.

[0197] In some embodiments, an RM customer can be a service provider for an application (APP). They can allocate computing resources, algorithm resources, and data resources to the servers used by the APP. In some embodiments, an RM customer can be a telecommunications operator that allocates communication resources, such as channel resources, to equipment such as base stations.

[0198] In AI-enabled device-level Resource Management (RM) processes, the RDF (Resource Flow Deployment) is pre-loaded with knowledge / information on one or more RM methods (e.g., one or more detailed algorithms or information / templates for tasks that can generate RM decisions) for generating RM decisions. RM methods may include one or more algorithms / computation processes for generating RM decisions, such as clustering algorithms / DNN models for generating radio resource allocation decisions among base stations in the RAN. Information on one or more RM methods may be provided by a third party (e.g., AF) or the network operator. The RDF may store information on one or more RM methods in a local library or in an external library provided by other network functions (e.g., data analysis management (DAM) functions) or third parties. Information on RM methods may include at least one of the following:

[0199] - Target device requirements, such as registration with a specific carrier.

[0200] - One or more types of resources to be managed, such as wireless resources or computing resources.

[0201] - Training data requirements, such as data sample size and data sample format.

[0202] - Application scenario requirements, for example, applicable only to a specific operator's RAN.

[0203] - It can guarantee QoS, for example, the frequency of decision generation.

[0204] - (Optional) RM method content, such as detailed algorithm / code.

[0205] RDF can expose its RM capabilities to one or more RM clients before executing device-level RM procedures; that is, information about one or more RM methods pre-installed in the RDF. Therefore, RM clients can be aware of the RDF's capabilities and determine whether to request RDF for resource management based on the compatibility between the RM client's resource allocation needs and the RDF's capabilities.

[0206] For example, if an RM client wants to allocate communication resources to base stations in a specific area, and RDF's capabilities include communication resource allocation, and RDF comes pre-installed with methods for allocating communication resources, then as long as the RM client knows RDF's capabilities, it can send a resource management request to RDF.

[0207] For example, if an RM client wants to allocate communication resources to base stations in a certain area, but RDF's capabilities do not include communication resource allocation, and therefore RDF does not have a pre-installed method for allocating communication resources, then the RM client only needs to know that RDF lacks this capability. Once the capability is acquired, the RM client can determine whether to perform resource management itself or request resource management from a third party, rather than sending a request to RDF.

[0208] Before executing an AI-enabled device-level RM process, it may be necessary to pre-establish all connections and control / management (C / M) plane data transmission routes between the network functions involved, namely RDF, one or more ROFs, RM clients, and (optionally) external NFs providing AI capabilities. Furthermore, training data collected from one or more devices and / or one or more RAN infrastructures for generating one or more RM decisions should be pre-stored in the network (e.g., in RDF local storage or in a DAM function). The training data may include at least one of the following:

[0209] - RAN deployment information, such as the geographical location of the infrastructure that makes up the RAN.

[0210] - Spatial and temporal distribution of UE location

[0211] - Spatial and temporal distribution of UL / DL services

[0212] - Channel fading / path loss distribution within the RAN area: This can be represented by a detailed channel fading / path loss map, which shows the statistical path loss value between each geographical location and the corresponding infrastructure. The map can be generated based on field experiments or AI / ML-based learning methods.

[0213] like Figure 7 As shown, the AI-enabled device-level RM process includes:

[0214] S701: Device-level RM request message from RM client to RDF (RDF_RM_RM request).

[0215] The RDF_RM_RM request is used to trigger the execution of a device-level RM procedure. The message may include at least one of the following:

[0216] - Requirements for one or more types of resources to be managed, such as uplink / downlink wireless resources and computing resources.

[0217] Depending on the implementation, the requirements for managing one or more resource types can include more specific resource type information, such as information about which computing resources need to be managed. For example, it could be cloud computing resources, AI model resources, etc.

[0218] - Target device / information requirements: For example, one or more IDs / one or more locations of one or more target devices.

[0219] Depending on the implementation, one or more locations of a target device can be identified based on the RAN ID.

[0220] -Scenario Requirements: Identify information about one or more scenarios of the application device-level RM process, such as one or more IDs of one or more RANs, geographic location information of a specific area, or one or more IDs / one or more geographic locations of one or more RAN infrastructures that constitute the scenario.

[0221] - QoS requirements of the device-level RM, such as maximum / minimum throughput / latency requirements.

[0222] - Requirements for potential RM methods: One or more IDs of one or more target RM methods (based on the RM capabilities exposed by RDF), or (if any) complete information about the target RM methods.

[0223] - (Optional) Network function requirements: One or more names / one or more IDs of one or more specific network functions may be involved in the execution of the device-level RM process (e.g., the IDs of one or more XaaS services that provide AI capabilities).

[0224] The information contained in the RDF_RM_RM request sent by the RM client can help RDF make RM decisions. For example, it can determine the appropriate RM method based on the information in the RDF_RM_RM request and execute the RM method to generate an RM decision.

[0225] S702: RDF execution RM decision generation.

[0226] Specifically, after the RM is pre-configured, RDF further triggers the RM decision generation process to generate one or more RM decisions.

[0227] As an example, RDF can generate RM decisions based on pre-installed RM methods. According to some embodiments, one or more RM methods used to generate one or more RM decisions are the most suitable among all RM methods for the RDF_RM_RM request message. More details about the steps are below. Figure 8 The information is given in the section.

[0228] In addition, external AI capability providers may be involved during the RM decision generation process.

[0229] S703: RDF executes the RM decision distribution process.

[0230] Regarding RM decision distribution, given one or more RM decisions generated in the RM decision generation process, RDF executes the RM decision distribution process to distribute the RM decisions to one or more target ROFs. Figure 9 The details of the RM decision distribution process are shown below; more details about the steps are below. Figure 9 The information is given in the section.

[0231] S704: Device-level RM request response from RDF to RM client (RDF_RM_RM request response).

[0232] The RDF_RM_RM request response is used to indicate that the device-level RM process is complete. In step S703, each ROF can also schedule allocated resources to each device based on one or more received RM decisions.

[0233] Note that step S704 is an optional step. In some embodiments, the method may include steps S701 to S703, while in other embodiments, the method may include steps S701 to S704.

[0234] According to the implementation of this invention, RDF can assist RM clients with resource management needs in coordinating resource management tasks. This includes determining one or more RM methods that meet the RM client's requirements, generating one or more RM decisions, and distributing these one or more RM decisions to the corresponding ROFs of one or more target devices, thereby achieving resource management for one or more target devices. The RM methods are determined based on the RM client's requirements, for example, based on information in the RM request message (RDF-RM-RM request). One or more RM methods determined in this way can be more suitable for the resource management methods required by the RM client, making the generated one or more RM decisions more suitable for the RM request message, thereby improving RM efficiency.

[0235] Figure 8 The details of the RM decision generation process are shown.

[0236] like Figure 8 As shown, the RM decision generation process, i.e. step S702, may include at least one of the following:

[0237] S801: RDF execution RM method selection.

[0238] Depending on some implementations, RDF selects one or more appropriate RM methods based on the RDF_RM_RM request message received in step S801 of the AI-enabled device-level RM process.

[0239] To select one or more RM methods, RDF can run an RM method selection algorithm that compares the information in the RDF_RM_RM request message with information about all or more RM methods. The algorithm-selected RM method should ensure that all requirements defined in the RDF_RM_RM request message are met. In some embodiments, information supporting one or more RM schemes may be stored in an external library (e.g., in a network repository function (NRF) or a third-party DN). RDF can then perform the following steps S8011 to S8012 to select the RM scheme:

[0240] Depending on the implementation, RDF can determine a variety of RM methods, and the selected RM methods can be connected in series or in parallel to perform resource management tasks.

[0241] Depending on the implementation, RDF can define a variety of RM methods, each of which can be used for resource management on different target devices.

[0242] Depending on the implementation, the RM method can be stored in an external library. S801 can include S8011 and S8012, as follows:

[0243] S8011: MDR_RM_method information request message from RDF to external library.

[0244] The MDR_RM_method information request message is used to request information from an external library about one or more potential RM methods. The message may include the requirements for potential RM methods included in the RDF_RM_RM request message.

[0245] S8012: Response to the MDR_RM_method information request from an external library to RDF:

[0246] Given an MDR_RM_method information request message from RDF, the external library compares the information in the MDR_RM_method information request message with information from all pre-stored potential RM methods (one or more). It then selects one or more potential RM methods that are guaranteed to meet all the requirements of the potential RM methods included in the MDR_RM_method information request message. The external library then sends the information of the selected potential RM methods to RDF in the MDR_RM_method information request response.

[0247] According to some embodiments, potential Resource Management (RM) methods that meet all the information contained in a resource management request can be determined by RDF. That is, the information may include at least one of the following: requirements for one or more resource types to be managed, target device / information requirements, one or more locations of the target device, scenario requirements, QoS requirements for device-level RM, requirements for potential RM methods: one or more IDs of one or more target RM methods, and network function requirements. In this embodiment, an external library can compare the above information with all pre-stored one or more RM methods and select one or more RM methods that can ensure all the requirements of the above information are met. Therefore, RDF can select one or more RM methods based on all potential one or more RM methods to find the one or more RM methods most suitable for RM decision calculation.

[0248] S802: RDF performs RM decision calculations.

[0249] RDF generates RM decisions by executing one or more selected RM methods. In some implementations, RDF can request external AI capabilities from other NFs and / or third-party AF / DNs (e.g., AI training support from network-for-AI (NET4AI) XaaS services, or training data from DAMs). Figure 10 and / or Figure 11 The method described herein supports the RM decision calculation process with external capability providers.

[0250] According to some embodiments, RM decision calculation can be based on at least one of the following:

[0251] - RAN deployment information, such as the geographical location of the infrastructure that makes up the RAN.

[0252] - Spatial and temporal distribution of UE location

[0253] - Spatial and temporal distribution of UL / DL services

[0254] - Channel fading / path loss distribution within the RAN area: This can be represented by a detailed channel fading / path loss map, which shows the statistical path loss value between each geographical location and the corresponding infrastructure. The map can be generated based on field experiments or AI / ML-based learning methods.

[0255] - Other data collected from the target device.

[0256] According to the embodiments, the number of RM decisions can be multiple, specifically including several RM decisions corresponding to different target devices or different ROFs.

[0257] According to the implementation of the present invention, RDF can query RM methods from external libraries, which can expand the query scope of RM methods and increase the number of available RM methods, making it easier for RDF to determine the appropriate RM method.

[0258] like Figure 9 As shown, the RM decision distribution process described above, step S703 includes:

[0259] S901: RDF determines ROF configuration information.

[0260] Based on one or more RM decisions generated in the RM decision generation process, RDF further determines at least one of the following ROF configuration information:

[0261] - QoS requirements for executing the RM scheme to be distributed, such as execution latency requirements and minimum computing resource requirements.

[0262] -RM scheme execution parameters (start time, completion time, etc.).

[0263] S902: ROF_RM_ROF configuration request from RDF to ROF.

[0264] The ROF_RM_ROF configuration request is used to distribute the necessary information to the ROF for configuration. The necessary information included in the message may include at least one of the following: 1) information on the determined RM decision, and 2) determined ROF configuration information to be applied to the target ROF.

[0265] S903: ROF execution configuration ROF.

[0266] After receiving the message in step S902, ROF configures its local settings / parameters according to the determined ROF configuration information and implements the RM scheme.

[0267] S904: ROF_RM_ROF configuration request response from ROF to RDF.

[0268] The ROF_RM_ROF configuration request response is used to indicate to ROF that the RM decision distribution is complete.

[0269] according to Figure 9 The embodiments described herein configure ROF so that ROF can execute the RM scheme according to the execution parameters required by RDF.

[0270] By leveraging AI technology, AI-enabled device-level RM methods enable future RMs to flexibly adapt one or more RM decisions to the dynamic resource requirements of the device side.

[0271] In some implementations, RDF can trigger RM decision computation using mission management (MM) processes to request the network entity executing the MM (i.e., MM for short) to establish and execute one or more corresponding mission sessions to compute one or more RM decisions.

[0272] Figure 10 This illustrates the RM decision calculation using the MM process:

[0273] S1001: RDF execution task information determined.

[0274] Given information and details about one or more selected RM methods, RDF can transform those methods into one or more tasks (i.e., one or more RM tasks). Each RM task transformed from a selected RM method should have the same inputs and outputs (i.e., RM decisions) as the corresponding selected RM method.

[0275] According to some embodiments, RM tasks and RM methods can have a one-to-one correspondence. Basically, if there are multiple RM methods, then correspondingly, there are also multiple RM tasks. For example, RM methods can be provided by one or more XaaS services, or RM methods can be executed using the computing power provided by one or more XaaS services. As an example, for each RM task transformed from a selected RM method, RDF determines its task information, which includes:

[0276] 1) Task ID;

[0277] 2) Identify the composition information of one or more XaaS services (e.g., NET4AI, DAM) required for the RM task;

[0278] As an example, one or more XaaS services may provide computing power or RM methods. According to some embodiments, the one or more XaaS services providing computing power may differ from the one or more XaaS services providing RM methods.

[0279] 3) Information describing one or more interconnections between one or more XaaS services defined in the composition information.

[0280] According to some embodiments, one or more XaaS services can be connected in parallel or in series.

[0281] As an example, a defined RM method can be executed using the computing power of two XaaS services (a first XaaS service and a second XaaS service). The first XaaS service is used to execute the first phase of the RM method, and the second XaaS service is used to execute the second phase of the RM method. In this case, the first XaaS service and the second XaaS service can be cascaded.

[0282] As another example, the determined RM method can be executed using the computing power of two XaaS services (a first XaaS service and a second XaaS service). The first XaaS service executes the RM method to generate RM decisions for a portion of the target devices, and the second XaaS service executes the RM method to generate RM decisions for the remaining target devices. In this case, the first and second XaaS services can be connected in parallel.

[0283] S1002: MM_RM_RM task request from RDF to MM.

[0284] RDF executes as a task client to trigger the creation and execution of RM tasks. The message includes the defined RM task information described in S1001.

[0285] According to some embodiments, the MM_RM_RM task request includes the RM task generated in step S1001 and the task information described in step S1001. Upon receiving the MM_RM_RM task request, the MM can perform task creation, establishment, and execution.

[0286] S1003: MM execution tasks include creation, setup, and execution.

[0287] Based on the determined RM task information received in step S1002, the MM creates an RM task instance, establishes an RM task session, and executes the RM task session to generate one or more RM decisions. The task creation, establishment, and execution process may involve one or more other XaaS services (e.g., NET4AI, DAM) to provide AI and computing capabilities.

[0288] For example, in the above implementation of creating, establishing, and executing tasks through the first XaaS service and the second XaaS service, the MM can call the first XaaS service and the second XaaS service respectively to execute part or stage of their RM methods.

[0289] S1004: MM_RM_RM task request response from MM to RDF.

[0290] After the RM task is completed, the MM sends one or more generated RM decisions to the RDF via a message.

[0291] In some implementations where MM services are unavailable, RDF can trigger RM decision computation using XaaS service processes by interacting directly with one or more XaaS services to compute one or more RM decisions. Figure 11 This illustrates the RM decision calculation using the XaaS service process:

[0292] S1101: XaaS capability query from RDF to XaaS service (controller).

[0293] RDF queries can identify the AI / computing capabilities that an XaaS service can provide. Messages can include requirements for the XaaS service (e.g., using a specific format / description language) to disclose information about the capabilities the XaaS service can offer.

[0294] S1102: XaaS capability query response from XaaS service to RDF.

[0295] Upon receiving the query in step 1101, the XaaS service notifies RDF about the AI / computing capabilities that the XaaS service can support. The message may include information about the provided capabilities as specified in the XaaS capability query. Information for each provided capability may include at least one of the following: 1) the capability's ID / name; 2) a description of the capability; 3) the capability's requirements (e.g., one or more input / output data formats, training data requirements), etc.

[0296] According to some embodiments, XaaS capabilities include, but are not limited to, federated learning, reinforcement learning, deep neural networks, convolutional neural networks, etc.

[0297] S1103: RDF execution of XaaS task confirmed.

[0298] Upon receiving an XaaS capability query response, RDF can determine the XaaS task based on the information about the capabilities provided included in the XaaS capability query response.

[0299] Given information about the capabilities provided by all or more XaaS services, and details of the selected RM method or method, RDF can decouple / reorganize the selected RM method or method into one or more tasks. Each task should be executable by a specific XaaS service. RDF maintains the workflow / dependencies between one or more tasks to generate one or more RM decisions. For each task, RDF should further determine its XaaS execution parameters, which may include at least one of the following: 1) the ID / name of the XaaS service executing the task; 2) the QoS requirements for task execution; 3) (optionally) the storage address for the input data used for task execution, etc.

[0300] S1104: XaaS execution request from RDF to XaaS service (to execute a task).

[0301] For each task, MM sends a request to the XaaS service to execute the task. The message includes the XaaS execution parameters for the task, as well as the input data for task execution (e.g., output data received from previous task executions based on defined workflows / dependencies).

[0302] S1105: XaaS service execution.

[0303] Based on the XaaS execution parameters and input data received in step S1004, the XaaS service executes the task.

[0304] S1106: XaaS execution request and response from XaaS service to RDF.

[0305] The message notifies the RDF task of completion and sends the task execution result information to RDF. The task execution result information may include at least one of the following: 1) the execution result data format; 2) the storage address of the execution result data or the execution result data itself.

[0306] For different tasks, RDF can trigger execution steps S1103 to S1106 multiple times based on the defined workflow / dependencies of the tasks, until the tasks generate all the results of the task execution required to generate one or more RM decisions.

[0307] S1107: RDF generates RM decision.

[0308] RDF can generate RM decisions based on the task execution result data received in step S1106.

[0309] According to one implementation, the task execution result data includes information on at least one RM scheme for each target device, such as algorithm A for device 1 and algorithm B for device 2. Then, RDF can determine the RM decision, which includes information on algorithm A for device 1 and algorithm B for device 2, as well as the corresponding resource set, based on which algorithm A or algorithm B can be executed.

[0310] The RM decision computation process enables RDF to compute RM decisions by leveraging the AI / computing capabilities provided by MM or one or more XaaS services.

[0311] In some alternative implementations, by utilizing XaaS services to perform tasks, external resources can be leveraged to accelerate the generation of RM decisions, enabling RDF to obtain RM decisions more quickly and complete the distribution of RM solutions as soon as possible.

[0312] Figure 12 This is a block diagram illustrating the apparatus of an embodiment. At 1200, Figure 12 Components of an exemplary device are shown, wherein transmitting features may be implemented or may be combined therewith, and components of an exemplary device are shown at 1250, wherein receiving features may be implemented or may be combined therewith. A controller 1230 may be provided in any of these types of devices. In some embodiments, the device may include transmitting and receiving features. Figure 12 In the example shown, the device with all the shown components supports both transmit and receive features.

[0313] For sending features, Figure 12 An exemplary device includes an input interface 1202, a transmitter 1204 coupled to the input interface, an output interface 1206 coupled to the transmitter, and a controller 1230 coupled to the transmitter. The input interface 1202 is shown to typically represent a connection to other device components to obtain information to be transmitted. Although in Figure 12 While shown as a separate component, the output interface 1206 through which the transmitter 1204 transmits can be provided by the transmitter or incorporated into the transmitter. Similarly, although in Figure 12 The interface shown is a separate input interface 1202, but the interface through which the transmitter 1204 obtains information for transmission can be provided by the transmitter or incorporated into the transmitter.

[0314] For receiving characteristics, Figure 12 An exemplary device includes an input interface 1256 for receiving signals, a receiver 1254 coupled to the input interface, an output interface 1252 coupled to the receiver, and a controller 1230 coupled to the receiver. The input interface 1256 is shown to generally represent a connection to other device components for receiving signals from one or more network devices. Although in Figure 12 While shown as a separate component, receiver 1254 can be provided by or incorporated into a receiver via its signal input interface 1256. Similarly, although in Figure 12 The output interface 1252 is shown as a separate output interface, but the receiver 1254 may provide or be integrated into the receiver through its interface for providing information from the received signal to other components.

[0315] The sending and receiving features or functions, as well as other features or functions described herein, can be implemented in any of a variety of ways, such as in one or more components of hardware, firmware, or execution software. This invention is not limited to any particular type of implementation, and implementation details may differ between different devices.

[0316] Information for transmission can be obtained through any of various types of interfaces, signals can be sent, signals can be received, and information from received signals can be provided to other device components. Interfaces include communication interfaces in cases where signals are sent by transmitter 1204 and / or received by receiver 1254. Embodiments are not limited in any way to any particular type of interface, and their implementation may be at least in part determined by the type of device (e.g., UE or network device) from which the apparatus will be implemented.

[0317] In one embodiment, the apparatus for a first device disclosed herein includes a receiver, such as receiver 1254, for receiving from an RM client of a second device, and a controller, such as controller 1230, coupled to receiver 1254 to determine a resource management scheme.

[0318] In one embodiment, the apparatus for a second device disclosed herein includes a receiver, such as receiver 1254, for receiving from a first device, and a controller, such as controller 1230, coupled to receiver 1254 to execute a resource management scheme to control the resources allocated to the target device.

[0319] Although the present invention has referenced illustrative embodiments, it is not intended to be interpreted in a limiting sense. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of the invention, will be apparent to those skilled in the art upon reference to this specification.

[0320] Features disclosed herein in the context of any particular embodiment may or alternatively be implemented in other embodiments. For example, method embodiments may, additionally or alternatively, 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 as instructions stored in one or more non-transitory computer-readable media, etc. These media may store programs or instructions for performing any of the various methods consistent with the present invention.

[0321] Although various aspects of the invention have been described with reference to specific features and embodiments thereof, various modifications and combinations may be made to the invention without departing from its scope. Therefore, the description and drawings are to be regarded only as illustrations of some embodiments of the invention as defined in the appended claims, and are intended to cover any and all modifications, variations, combinations, or equivalents falling within the scope of the invention. Thus, although embodiments and 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 components, apparatuses, methods, and steps described in the specification. It will be readily understood by those skilled in the art from the disclosure of this invention that processes, machines, articles of manufacture, material components, apparatuses, methods, or steps that exist or will be developed later and perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein can be utilized according to the invention. Therefore, the appended claims are intended to include such processes, machines, articles of manufacture, material components, apparatuses, methods, or steps within their scope.

[0322] 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 Disc™ and other optical storage devices, 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 media may be part of a device or may be accessible to or connected to a device. Any application or module described herein can be implemented using instructions that can be read and executed by a computer or processor, and can be stored or otherwise preserved by such non-transitory computer-readable or processor-readable storage medium.

[0323] In some aspects of the present invention, a device / chipset system is provided, comprising means (e.g., at least one processor) for implementing a method implemented by a UE (or 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, the at least one processor may execute instructions stored in a computer-readable medium to implement the method.

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

[0325] In some aspects of the present invention, a system is provided that includes at least one of means in a UE (or at the UE) of the present invention or means in a network device of the present invention.

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

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

[0328] In some aspects of the invention, a system is provided that includes at least two of the network entities mentioned, such as the AF and device shown in the invention.

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

[0330] Please note 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 mentioned network entities may not be required; that is, one or more corresponding steps may be omitted (optionally).

[0331] Please note that although two or more network entities are shown in this invention, for the exemplary solutions of this invention, only one may be sufficient. For example, in Figure 10 In the example shown, RDF cannot see the operation performed by other network entities (e.g., step S1003) (or they may be transparent to RDF).

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

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

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

[0335] It should be understood that any module, component, or device disclosing executable instructions herein may include or otherwise access one or more non-transitory computer / processor-readable storage media for storing information, such as computer / processor-readable instructions, data structures, program modules, and / or other data. A non-exhaustive list of examples of non-transitory computer / processor-readable storage media includes magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, compact disc read-only memory (CD-ROM), digital video disc or digital versatile disc (DVD), Blu-ray Disc™ 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 storage medium may be part of a device or apparatus, or may be accessed or connected to a device or apparatus. Computer / processor-readable / executable instructions used to implement the methods, applications, or modules described herein may be stored by such non-transitory computer / processor-readable storage media or otherwise preserved.

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

[0337] Unless otherwise specified, the terms “apparatus” and “equipment” are used interchangeably, as are the terms “identifier” and “identifier”.

[0338] In this invention, when used in conjunction with the terms "comprising" or "including" in the claims and / or description, the word "a" or "an" may mean "one," but it also has the same meaning as "one or more," "at least one," and "one or more," unless explicitly stated otherwise. Similarly, the word "another" may refer to at least a second or more, unless explicitly stated otherwise.

[0339] In this invention, when used before the same term (e.g., ED or operational step), the words "first," "second," etc., do not imply an order or sequence of terms. For example, "first ED" and "second ED" refer to two different EDs without specific indication. Similarly, although this invention describes methods and processes having steps in a specific order, one or more steps in the methods and processes may be appropriately omitted or modified. Where appropriate, one or more steps may be performed in an order other than that described. For example, "first step" and "second step" refer to two different operational steps without specific indication, but this does not mean that the first step must occur before the second step. The actual order depends on the logic of the two steps.

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

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

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

[0343] 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 context, the term “receive” can mean that information (e.g., DCI or MAC-CE, RRC signaling, or TB) has been successfully received by the receiving node, meaning that the receiving side correctly detected and decoded the information. In this scenario, “receive” can include both “detect” and “decode,” or it can mean the same thing; for example, “receive paging” means correctly decoding a paging message and successfully obtaining it. Correspondingly, “received paging” means that the receiving side did not detect and / or decode a paging message. “Not received paging” means that the receiving side attempted to detect and / or decode a paging message but failed to obtain it. The term “receive” can sometimes mean that a signal has arrived at the receiving side, but this does not necessarily mean that the information in the signal has been correctly detected and decoded. In this case, the receiving side needs to detect and decode the signal to obtain the information carried in it. In this scenario, “receive,” “detect,” and “decode” can represent different processes by which the receiving side obtains information.

[0344] Although the present invention has referenced illustrative embodiments, it is not intended to be interpreted in a limiting sense. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of the invention, will be apparent to those skilled in the art upon reference to this specification. When two or more embodiments are combined, not all features of the combined embodiments are necessary for the combination.

[0345] Features disclosed herein in the context of any particular embodiment may or alternatively be implemented in other embodiments. For example, method embodiments may, additionally or alternatively, 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 as instructions stored in one or more non-transitory computer-readable media, etc. These media may store programs or instructions for performing any of the various methods consistent with the present invention.

[0346]

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: Receive a resource management request that includes device information for at least one target device; In response to the resource management request, a resource management plan is determined; The resource management scheme information is sent to the resource management operation function (ROF), wherein the ROF is used to allocate resources to the at least one target device by executing the resource management scheme.

2. The first device according to claim 1, characterized in that, The resource management request also includes at least one of the following: resource type information, scenario information, resource management method requirements, training data requirements, and execution parameter requirements.

3. The first device according to claim 1 or 2, characterized in that, The determination of the resource management scheme includes: Determine the resource management method that matches the resource management request; The resource management scheme is determined based on the resource management method.

4. The first device according to claim 3, characterized in that, The resource management method includes at least one of an algorithm, a model, or a computational process.

5. The first device according to claim 3 or 4, characterized in that, The first device includes at least one first resource management method. The resource management method for determining the resource management request includes: A first resource management method that matches the resource management request is determined from the at least one first resource management method.

6. The first device according to claim 3 or 4, characterized in that, The method for determining the resource management request that matches the resource management request includes: Send a method request to an external library configured with at least one second resource management method, the method request including the information in the resource management request, and instruct the external library to determine a second resource management method from the at least one second resource management method that matches the resource management request; Receive a method response from the external library that instructs the second resource management method.

7. The first device according to any one of claims 3 to 6, characterized in that, Determining the resource management scheme according to the resource management method includes: Resource management tasks are determined based on the described resource management method; Send an execution request, including the resource management task, to an external network; Receive an execution response from the external network, the execution response including the execution result of the resource management task performed by the external network; Determine the resource management plan based on the execution results.

8. The first device according to any one of claims 3 to 6, characterized in that, Determining the resource management scheme according to the resource management method includes: The resource management method is used to determine the sub-tasks of each of one or more external networks. Send an execution request to each of the external networks, the execution request including the sub-task of each of the external networks; Receive an execution response from each of the external networks, the execution response including the execution result of the subtask performed by each of the external networks; The resource management scheme is determined based on at least one execution result corresponding to at least one of the one or more external networks.

9. The first device according to claim 8, characterized in that, Determining the sub-tasks of each of one or more external networks according to the resource management method includes: Send capability queries to each external network; Receive a capability query response from each external network, the capability query response including the capabilities of each external network; Based on the capabilities of each external network and the resource management method that matches the resource management request, determine the sub-tasks for each external network.

10. The first device according to any one of claims 3 to 6, characterized in that, Determining the resource management scheme according to the resource management method includes: Resource management tasks are determined based on the described resource management method; Send an execution request, including the resource management task, to mission management (MM); Receive an execution response from the MM, the execution response including the execution result of the resource management task performed by the MM; Determine the resource management plan based on the execution results.

11. A second device, characterized in that, include: At least one processor coupled to at least one memory containing computer program code; Wherein, when the computer program code is executed by the at least one processor, the second device: Receive information on resource management plans from the Resource Management Decision Function (RDF), wherein the resource management plans are determined by the RDF in response to resource management requests; The resource management scheme is executed to control the resources allocated to the target device.

12. A method applied to resource management decision function (RDF), characterized in that, include: Receive a resource management request that includes device information for at least one target device; In response to the resource management request, a resource management plan is determined; The information of the resource management scheme is sent to the ROF in the communication system, wherein the ROF is used to allocate resources to the at least one target device by executing the resource management scheme.

13. The method according to claim 12, characterized in that, The resource management request also includes at least one of the following: resource type information, scenario information, resource management method requirements, training data requirements, and execution parameter requirements.

14. The method according to claim 12 or 13, characterized in that, Determining the resource management scheme includes: Determine the resource management method that matches the resource management request; The resource management scheme is determined based on the resource management method.

15. The method according to claim 14, characterized in that, The first resource management method includes at least one of the following: algorithm, model, formula, and function.

16. The method according to claim 14 or 15, characterized in that, The RDF includes at least one first resource management method. The resource management method for determining the resource management request includes: A first resource management method that matches the resource management request is determined from the at least one first resource management method.

17. The method according to claim 14 or 15, characterized in that, The method for determining the resource management request that matches the resource management request includes: Send a method request to an external library configured with at least one second resource management method, the method request including the information in the resource management request, and instruct the external library to determine a second resource management method from the at least one second resource management method that matches the resource management request; Receive a method response from the external library that instructs the second resource management method.

18. The method according to any one of claims 14 to 17, characterized in that, Determining the resource management scheme according to the resource management method includes: Resource management tasks are determined based on the described resource management method; Send an execution request, including the resource management task, to an external network; Receive an execution response from the external network, the execution response including the execution result of the resource management task performed by the external network; Determine the resource management plan based on the execution results.

19. The method according to any one of claims 14 to 17, characterized in that, Determining the resource management scheme according to the resource management method includes: The resource management method is used to determine the sub-tasks of each of one or more external networks. Send an execution request to each of the external networks, the execution request including the sub-task of each of the external networks; Receive an execution response from each of the external networks, the execution response including the execution result of the subtask performed by each of the external networks; The resource management scheme is determined based on at least one execution result corresponding to at least one of the one or more external networks.

20. The method according to claim 19, characterized in that, Determining the sub-tasks of each of one or more external networks according to the resource management method includes: Send capability queries to each external network; Receive a capability query response from each external network, the capability query response including the capabilities of each external network; Based on the capabilities of each external network and the resource management method that matches the resource management request, determine the sub-tasks for each external network.

21. The method according to any one of claims 14 to 17, characterized in that, Determining the resource management scheme according to the resource management method includes: Resource management tasks are determined based on the described resource management method; Send an execution request, including the resource management task, to mission management (MM); Receive an execution response from the MM, the execution response including the execution result of the resource management task performed by the MM; Determine the resource management plan based on the execution results.

22. A method applied to a resource management operation function (ROF), characterized in that, include: Receive a resource management scheme from RDF, wherein the resource management scheme is determined by RDF in response to a resource management request; The resource management scheme is executed to control the resources allocated to the target device.

23. A first apparatus for use in resource management decision function (RDF), characterized in that, Includes means for the following operations: Receive a resource management request that includes device information for at least one target device; In response to the resource management request, a resource management plan is determined; The information of the resource management scheme is sent to the ROF in the communication system, wherein the ROF is used to allocate resources to the at least one target device by executing the resource management scheme.

24. A second device for use in a resource management operation function (ROF), characterized in that, Includes means for the following operations: Receive a resource management scheme from RDF, wherein the resource management scheme is determined by RDF in response to a resource management request; The resource management scheme is executed to control the resources allocated to the target device.

25. A computer-readable medium, characterized in that, Includes program instructions for causing the device to perform at least the method according to any one of claims 12 to 21 or claim 22.

Images