Communication method and apparatus

Abstract

A communication method and apparatus, which are used for supporting the deployment of an RAN network element and an edge application server. The method comprises: a first network device receiving first request information, wherein the first request information is used for requesting the deployment of a first object; on the basis of the first request information, the first network device further determining type information of the first object, wherein the type information is used for indicating whether the first object is an RAN network element or an RAN edge application server; and on the basis of the type information, the first network device further deploying the first object.

Description

A communication method and apparatus

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411600283.3, filed on November 8, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of mobile communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] Cloudification of radio access networks (RANs) has become a key technological focus for major telecommunications industry alliances in guiding the evolution of future communication networks. In RAN cloudification, RAN network elements utilize cloud resources to provide services. Furthermore, application servers are deployed at more peripheral locations, such as within the RAN itself. Edge application servers deployed within the RAN also require the use of cloud resources.

[0005] Currently, how to achieve collaborative deployment of RAN network elements and edge application servers is a technical problem that urgently needs to be solved. Summary of the Invention

[0006] This application provides a communication method and apparatus to support the deployment of RAN network elements and edge application servers.

[0007] Firstly, embodiments of this application provide a communication method, which can be executed by a first communication device, or in other words, the method can be applied to a first communication device. Unless otherwise specified, the "first communication device" in this application can refer to the first network device itself, a component within the first network device, or a logical module or software capable of implementing all or part of the first network device. The first network device can be a cloud-network collaborative orchestration function or a cloud resource orchestration function. The components in this application may include, for example, at least one of a chip, chip system, processor, transceiver, processing unit, transceiver unit, or other functional modules. Taking the first network device as the executing entity as an example, the method includes:

[0008] The first network device receives a first request message, which is used to request the deployment of a first object; the first network device may also determine the type information of the first object based on the first request message, which is used to indicate that the first object is a RAN network element or a RAN edge application server; the first network device may also deploy the first object based on the type information.

[0009] Based on the first aspect, the first network device can determine the type information of the first object according to the deployment request of the first object, and deploy the first object according to the type information to support the deployment of RAN network elements and edge application servers.

[0010] In one possible implementation, the first request information includes the identifier of the RAN network element and / or network element type information, wherein the network element type information is used to indicate whether the network element is a virtual network element or a physical network element, and the type information of the first object is used to indicate that the first object is a RAN network element.

[0011] Based on this implementation method, the first network device can flexibly determine that the first object is a RAN network element based on the identifier of the RAN network element and / or the network element type information of the RAN network element.

[0012] In one possible implementation, the first request information includes first indication information and / or a software image of the RAN edge application server, wherein the first indication information is used to indicate the RAN edge application server, and the type information of the first object is used to indicate that the first object is a RAN edge application server.

[0013] Based on this implementation, the first network device can flexibly determine that the first object is a RAN network element based on the first indication information and / or the software image of the RAN edge application server.

[0014] In one possible implementation, the first network device may also send a resource allocation request to the second network device according to the type information. The resource allocation request is used to request resources of the first object, and the resource allocation request includes the type information. In another possible implementation, the first network device may also receive indication information of a first resource from the second network device. The indication information of the first resource is used to indicate the first resource of the first cloud, the first resource serves the first object, and the indication information of the first resource is obtained according to the resource allocation request.

[0015] Based on this implementation, the first network device can request the second network device to allocate type information for the first object according to the type information.

[0016] In one possible implementation, the first network device may also receive a cloud identifier of the first cloud and second indication information from the second network device, the second indication information being used to indicate that the remaining resources of the first cloud are less than the resource requirements of the first object; the first network device may also send third indication information to the second network device, the third indication information being used to indicate a reduction in the second object's occupancy of the first cloud, the first cloud also serving the second object.

[0017] Based on this implementation, when the available resources of the first cloud are insufficient, the first network device can instruct the second network device to reduce the resource consumption of the second object on the first cloud, thereby prioritizing the resource needs of the first object. For example, the resource needs of the RAN edge application server can be prioritized.

[0018] In one possible implementation, the second indication information includes the difference between the remaining resources of the first cloud and the resource requirements of the first object.

[0019] In one possible implementation, the third indication information is specifically used to indicate the transfer of the task of the second object of the first cloud to the second resource. The third indication information includes indication information of the second resource and the identifier of the task of the second object. The indication information of the second resource is used to indicate the second resource of the second cloud. The third indication information may also include information about the first object. For example, if the first object is a RAN edge application server, the third indication information may include information about the RAN edge application server, or it may be indication information for co-deploying the RAN edge application server with the RAN network element in the same cloud.

[0020] Based on this implementation, the first network device can instruct the cloud resource orchestration function to transfer the resources occupied by the second object in the first cloud to the second cloud, so that the resources of the second cloud meet the resource requirements of the second object.

[0021] In one possible implementation, the first network device may send a second request message to the third network device, the second request message being used to request information about the service object of the first cloud, the service object of the first cloud including the second object, the second request message including the cloud identifier of the first cloud; the first network device may also receive information about the second object from the third network device; the first network device may also send a fourth indication message to the third network device, the fourth indication message being used to indicate updating the resource information and / or configuration information of the second object.

[0022] Based on this implementation, the first network device can obtain information about the service objects of the first cloud, such as information about the second object, from the third network device in order to determine whether to reduce the resource consumption of the second object on the first cloud.

[0023] In one possible implementation, the type information of the first object is used to indicate that the first object is a RAN edge application server. The first network device can also determine the first RAN network element based on the configuration information of the first object and the configuration information of at least one RAN network element. The first cloud serves the first RAN network element, and the resource allocation request includes the cloud identifier of the first cloud.

[0024] Based on this implementation method, the first network device can flexibly determine whether the RAN edge application server is deployed in the same cloud as the RAN network element, so as to realize the collaborative orchestration of the RAN edge application server and the RAN network element.

[0025] In one possible implementation, the configuration information includes one or more of the following: PLMN information, location information, network slice information, and hardware device information.

[0026] In one possible implementation, the first network device may also send a configuration request for the first object to the third network device, the configuration request including indication information of the first resource.

[0027] Based on this implementation, the first network device can provide the configuration function with the resource information of the first object so that the configuration function can configure the resources of the first object.

[0028] In one possible implementation, the resource allocation request further includes a task description of the first object, and the first network device may also receive an identifier of the task of the first object from the second network device. The identifier of the task of the first object is determined according to the task description, and the configuration request of the first object further includes the identifier of the task of the first object.

[0029] Based on this implementation, the cloud resource orchestration function can determine the task identifier corresponding to the first object based on the task description of the first object, thereby enabling flexible allocation of task identifiers. Furthermore, the first object can correspond to one or more tasks, and each task can correspond to a cloud resource.

[0030] In one possible implementation, the first request information includes fifth indication information, which indicates that the first object and the third object are deployed in the same cloud, and that the resources serving the first object and the resources serving the third object belong to the same cloud.

[0031] Based on this implementation method, the deployment service consumer can instruct the RAN network element and the RAN edge application server to be deployed together in the cloud.

[0032] In one possible implementation, the type information of the first object is used to indicate that the first object is a RAN network element, and the type information of the third object is used to indicate that the third object is an edge application server.

[0033] In one possible implementation, the first network device may further send a first resource allocation request to the second network device, the first resource allocation request being used to request resources of the third object, the resource allocation request including type information of the first object; the first network device may also receive indication information of a first resource from the second network device, the first resource indication information being used to indicate the first resource of the first cloud, the first resource serving the first object; the first network device may further send a second resource allocation request to the second network device, the resource allocation request being used to request resources of the third object, the resource allocation request including a cloud identifier of the first cloud, the second resource allocation request including type information of the third object; the first network device may also receive indication information of a third resource from the second network device, the third resource indication information being used to indicate a third resource of the first cloud, the third resource serving the third object.

[0034] Based on this implementation, when the RAN network element and the RAN edge application server are deployed in the same cloud, the first network device can request the cloud resource orchestration function to allocate the cloud resources of the RAN network element to the RAN edge application server, so as to improve the resource allocation efficiency in the co-cloud deployment scenario.

[0035] Secondly, embodiments of this application provide a communication method, which can be executed by a second communication device, or in other words, the method can be applied to a second communication device. Unless otherwise specified, the "second communication device" in this application can refer to the second network device itself, a component within the second network device, or a logic module or software capable of implementing all or part of the functions of the second network device. The components in this application may include, for example, at least one of a chip, chip system, processor, transceiver, processing unit, transceiver unit, or other functional modules. The second network device may be, for example, a cloud resource orchestration function.

[0036] Taking the second network device as the execution subject as an example, the method includes: receiving a resource allocation request from the first network device, the resource allocation request being used to request resources of the first object, the resource allocation request including the type information; sending indication information of the first resource to the first network device, the indication information of the first resource being used to indicate the first resource of the first cloud, the first resource serving the first object.

[0037] In one possible implementation, the second network device may also send the cloud identifier of the first cloud and second indication information to the first network device, the second indication information being used to indicate that the remaining resources of the first cloud are less than the resource requirements of the first object; the second network device may also receive third indication information from the first network device, the third indication information being used to indicate reducing the second object's occupation of the first cloud, the first cloud also serving the second object.

[0038] In one possible implementation, the second indication information includes the difference between the remaining resources of the first cloud and the resource requirements of the first object.

[0039] In one possible implementation, the third indication information is specifically used to indicate the transfer of the task of the second object of the first cloud to the second resource. The third indication information includes indication information of the second resource and the identifier of the task of the second object. The indication information of the second resource is used to indicate the second resource of the second cloud.

[0040] In one possible implementation, the resource allocation request further includes a task description of the first object, and the second network device may also send an identifier of the task of the first object to the first network device, the identifier of the task of the first object being determined according to the task description.

[0041] The beneficial effects of the second aspect and its possible implementation methods can be found in the description of the beneficial effects of the first aspect and its corresponding implementation methods, and will not be repeated here.

[0042] Thirdly, a communication device is provided. The device can implement the method described in any possible implementation of any of the first or second aspects described above. The device possesses the functions of the first or second communication device described above. The device is, for example, a terminal device, a functional module within a terminal device, a network device, or a functional module within a network device, etc.

[0043] In one optional implementation, the device may include modules corresponding one-to-one with the methods / operations / steps / actions performed in any possible implementation of any of the first to second aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software. In another optional implementation, the device includes a processing unit (sometimes also called a processing module) and a communication unit (sometimes also called a transceiver module, communication module, etc.). The transceiver unit is capable of both sending and receiving functions. When the transceiver unit performs the sending function, it may be called a sending unit (sometimes also called a sending module); when the transceiver unit performs the receiving function, it may be called a receiving unit (sometimes also called a receiving module). The sending unit and the receiving unit may be the same functional module, which is called the transceiver unit and can perform both sending and receiving functions; or, the sending unit and the receiving unit may be different functional modules, with the transceiver unit being a collective term for these functional modules.

[0044] For example, when the apparatus is used to perform the method described in any one of the first to second aspects, the apparatus may include a communication unit and a processing unit.

[0045] Fourthly, embodiments of this application also provide a communication device, including a processor for executing a computer program (or computer-executable instructions) stored in a memory, such that when the computer program (or computer-executable instructions) is executed, the device performs the method as described in any possible implementation of any of the first to second aspects.

[0046] In one possible implementation, the processor and memory are integrated together;

[0047] In another possible implementation, the memory is located outside the communication device.

[0048] The communication device also includes a communication interface for communicating with other devices, such as sending or receiving data and / or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0049] Fifthly, a computer-readable storage medium is provided for storing a computer program or instructions that, when executed, enable the implementation of the method described in any possible implementation of any of the first to second aspects, and the method shown in any possible implementation of the first aspect.

[0050] A sixth aspect provides a computer program product containing instructions that, when run on a computer, enables the method described in any possible implementation of any of the first to second aspects to be implemented.

[0051] In a seventh aspect, embodiments of this application also provide a communication device for performing the method described in any possible implementation of any of the first to second aspects described above.

[0052] Eighthly, a chip system is provided, comprising logic circuitry (or, as understood, a processor, which may include logic circuitry, etc.), and further comprising input / output interfaces. The input / output interfaces can be used to input messages or to output messages. The input / output interfaces can be the same interface, i.e., the same interface can implement both sending and receiving functions; or, the input / output interface includes an input interface and an output interface, the input interface being used to implement the receiving function, i.e., to receive messages; and the output interface being used to implement the sending function, i.e., to send messages. The logic circuitry can be used to perform operations other than the sending and receiving functions in any possible implementation of any of the first to second aspects described above; the logic circuitry can also be used to transmit messages to the input / output interfaces or to receive messages from other communication devices from the input / output interfaces. The chip system can be used to implement the methods described in any possible implementation of any of the first to second aspects described above. The chip system can be composed of chips or can include chips and other discrete devices.

[0053] Optionally, the chip system may also include a memory, which can be used to store instructions, and the logic circuits can call the instructions stored in the memory to implement the corresponding functions.

[0054] Ninth aspect, a communication method is provided, which may include the method implemented by a first communication device as shown in the first aspect and any possible implementation thereof, and the method implemented by a second communication device as shown in the second aspect and any possible implementation thereof.

[0055] A tenth aspect provides a communication system that may include a first communication device and a second communication device. The first communication device may be used to implement the method shown in the first aspect and any possible implementation thereof, and the second communication device may be used to implement the method shown in the second aspect and any possible implementation thereof.

[0056] The technical effects brought about by the third to tenth aspects above can be found in the descriptions of the beneficial effects of the corresponding solutions in the first and second aspects above, and will not be repeated here. Attached Figure Description

[0057] Figure 1 is a schematic diagram of a network management system architecture provided in an embodiment of this application;

[0058] Figure 2 is a schematic diagram of an O-RAN system architecture provided in an embodiment of this application;

[0059] Figure 3 is a schematic diagram of an edge computing application layer architecture provided in an embodiment of this application;

[0060] Figure 4 is a schematic diagram of an object deployment architecture provided in an embodiment of this application;

[0061] Figure 5 is a schematic diagram of another object deployment architecture provided in an embodiment of this application;

[0062] Figure 6 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0063] Figure 7 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0064] Figure 8 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0065] Figure 9 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0066] Figure 10 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0067] Figure 11 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0068] Figure 12 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0069] The technical solutions involved in the embodiments of this application will be described below with reference to the accompanying drawings. The embodiments of this application can be applied to various communication networks, such as: 5G communication networks (e.g., 5G new radio (NR) networks), 5G-A networks, long term evolution (LTE) networks, advanced long term evolution (LTE-A) networks, future communication networks, etc., and are not limited thereto.

[0070] For ease of understanding, some terms used in the embodiments of this application will be explained below.

[0071] (1) Network Management System

[0072] Network management systems can be used to support network management services.

[0073] Referring to Figure 1, a schematic diagram of a network management system architecture is shown. This system architecture includes: a business operation unit, a cross-domain management function unit, a domain management function unit, and one or more of multiple network elements.

[0074] A business operations unit can invoke or manage one or more cross-domain management function units. A cross-domain management function unit can manage one or more domain management function units. A domain management function unit can manage one or more network elements. The following is a brief introduction to each unit.

[0075] A, Business Operations Unit.

[0076] A business operations unit, also known as a communication service management function (CSMF), provides functions and management services such as billing, settlement, accounting, customer service, sales, network monitoring, communication service lifecycle management, and service intent translation. A business operations unit can include an operator's operating system or a vertical industry's operating system (vertical operational technology system).

[0077] In this application, the business operation unit can act as an edge computing service consumer to obtain edge computing deployment services. The edge computing service consumer can be simply referred to as a consumer. For example, the business operation unit can specifically be government / enterprise equipment, third-party application developers, data users, or application functions (APs), etc., without specific limitations.

[0078] The business operations unit can also be called a network management service consumer.

[0079] B, Cross-Domain Management Function Unit, or Cross-Domain Management Module.

[0080] A cross-domain management function unit, also known as a network management function (NMF) or network management system (NMS), belongs to the cross-domain management system and is responsible for the unified management of multiple network element management systems. A cross-domain management function unit can provide one or more of the following functions or management services: network lifecycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, and network optimization. The network here can include one or more network elements, subnetworks, or network slices. For example, a cross-domain management function unit could be a network slice management function (NSMF), a management data analytics function (MDAF), a cross-domain self-organizing network function (SON-function), or a cross-domain intent management function unit.

[0081] In certain deployment scenarios, the cross-domain management function unit can also provide one or more of the following management functions or services: subnetwork lifecycle management, subnetwork deployment, subnetwork fault management, subnetwork performance management, subnetwork configuration management, subnetwork assurance, and subnetwork optimization. A subnetwork can consist of multiple smaller subnetworks or multiple network slice subnetworks. For example, an operator's access network subnetwork may include access network subnetworks from equipment vendor 1 and access network subnetworks from equipment vendor 2.

[0082] Understandably, in implementation, a cross-domain management function unit can be implemented as a management platform plus multiple management applications, where the management applications implement the management functions of one or more networks or sub-networks; or it can be that a network element in the network has the function of a cross-domain management function unit.

[0083] C, Domain Management Functional Unit

[0084] A domain management function unit can also be called a single-domain management function unit or a single-domain management system (EMS). Domain management function units can further include subnetwork management functions, network element / function management functions, radio access network (RAN) domain management function units, or core network (CN) domain management function units. A domain management function unit can provide one or more of the following functions or services: lifecycle management of subnetworks or network elements, deployment of subnetworks or network elements, fault management of subnetworks or network elements, performance management of subnetworks or network elements, assurance of subnetworks or network elements, and optimization management of subnetworks or network elements. A subnetwork can include one or more network elements. Alternatively, a subnetwork can include one or more subnetworks, i.e., one or more subnetworks forming a subnetwork with a larger coverage area. Or, a subnetwork can include one or more network slice subnetworks. A sub-network can be described in at least one of the following ways: a network of a certain technology domain, such as a wireless access network, core network, or transmission network; a network of a certain standard, such as a Global System for Mobile Communications (GSM) network, an LTE network, or a 5G network; a network provided by a certain equipment vendor, such as a network provided by equipment vendor X; or a network of a certain geographical area, such as the network of factory A or the network of prefecture-level city B.

[0085] Furthermore, a sub-network can also refer to one or more public land mobile networks (PLMNs), meaning the domain management functional unit includes the PLMN management system. Taking 5G networks as an example, the PLMN management system can be used to manage the 5G RAN or the 5G core network. It can be understood that the EMS responsible for managing the 5G RAN can be called EMS-RAN.

[0086] A sub-network can also refer to an edge data network (EDN). The domain management functional unit responsible for managing the 5G RAN can be called an edge computing service provider (ECSP). ECSPs can provide edge computing services; for example, they can provide edge application servers (EAS), edge enabler servers (EES), or edge configuration servers (ECS) to support edge computing services. Alternatively, ECSs can be considered not to belong to ECSPs.

[0087] The domain management function unit may also include multi-access edge computing (MEC) domain management functions, used to manage functional entities within the MEC, which may include edge application servers, etc. For example, entities within MECs deployed in the EDN or the RAN can be managed through the MEC domain management function.

[0088] Understandably, in implementation, a domain management function unit can be implemented as a management platform plus multiple management applications, where the management applications implement the management functions of one or more sub-networks or network elements; or it can be that a network element in the network has the function of a domain management function unit.

[0089] (2) Managed object

[0090] A managed object is used to describe information about a managed object or management task in a management system (such as an intent management system). The information model of a managed object can be used as an interaction parameter in the management interface. Creating a managed object means creating management information in the management system, enabling the management system to manage the managed object or perform management tasks based on the management information.

[0091] In this application, the managed object may include network devices in the network, such as network functions (NFs) or network equipment (NEs). For example, the managed object may be a base station in the RAN, or a core network element in the core network. It can be considered that this application does not distinguish between the meanings of NF and network element; NF and network element can be collectively referred to as network device, network element, or other names.

[0092] The following text will use network elements as an example for introduction.

[0093] In this application, a network element refers to an entity that provides network services, including core network elements, radio access network elements, and transport network elements. For example, a core network element may include, but is not limited to, access and mobility management function (AMF) entities, session management function (SMF) entities, policy control function (PCF) entities, user plane function (UPF) entities, network data analysis function (NWDAF) entities, network repository function (NRF) entities, and network exposure function (NEF) gateways.

[0094] Radio access network equipment can be a base station, an evolved NodeB (eNodeB / eNB), a transmission reception point (TRP), a transmission point (TP), a next-generation NodeB (gNB) or next-generation (NG)-eNB in ​​a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. Radio access network equipment can also be open RAN (O-RAN or ORAN) equipment or cloud radio access network (CRAN) equipment. Radio access network equipment can also be a communication system that integrates two or more of the above systems.

[0095] Furthermore, the wireless access network equipment can also be a module or unit that performs some of the functions of a base station. For example, it can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. A CU can include a CU-CP and a CU-UP. In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called an open CU (O-CU), DU can also be called an open DU (O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-UP), and RU can also be called an open RU (O-RU). For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the CU (or CU-CP, CU-UP), DU and RU units in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0096] As shown in Figure 2, in an O-RAN network, the radio access network equipment may include a service management and orchestration (SMO), a near-real-time RAN intelligent controller (near-real-time RIC), an O-CU, an O-DU, and an open cloud (O-cloud). The SMO may also include a non-real-time RAN intelligent controller (non-real-time RIC).

[0097] The SMO (Service Management Organization) can be used for RAN domain management. That is, the SMO can serve as a domain management functional unit for the RAN domain. In the architecture shown in Figure 2, the non-real-time RAN intelligent controller can be used as an internal module of the SMO to support access network management, such as configuring or sending access network-related control configurations, and managing machine learning-related models. Because the non-real-time RAN intelligent controller is deployed at the management layer, its RAN control optimization is non-real-time. The near real-time RAN intelligent controller can be used to provide near real-time RAN control optimization. O-cloud can include certain cloud resources and cloud management capabilities.

[0098] (3) Management service producer (MnS producer) and management service consumer (MnS consumer)

[0099] For any given management service, there exists a provider and a consumer. The management service is provided by the provider to the consumer. As a possible example, when the management service is provided by the aforementioned business operation unit, the business operation unit is the management service provider, and other business operation units can be management service consumers. When the management service is provided by the aforementioned cross-domain management function unit, the cross-domain management function unit is the management service provider, and the business operation unit can be a management service consumer. When the management service is provided by the aforementioned domain management function unit, the domain management function unit is the management service provider, and either the cross-domain management function unit or the business operation unit can be a management service consumer. When the management service is provided by the aforementioned network element, the network element is the management service provider, and either the domain management function unit, the cross-domain management function unit, or the business operation unit can be a management service consumer.

[0100] This application embodiment can manage networks (or autonomous networks) of different ranges shown in Figure 1. The network range can include the following three situations:

[0101] Case 1, Single-domain network, or single-domain autonomous network: includes network elements and domain management functional units;

[0102] Case 2, cross-domain network, or cross-domain autonomous network: includes network elements, domain management functional units, and cross-domain management functional units;

[0103] Case 3, Business Network, or Business Autonomous Network: includes network elements, domain management functional units, cross-domain management functional units, and business operation units.

[0104] (4) RAN cloudification

[0105] RAN cloudification, also known as cloud-RAN (C-RAN), is a radio access network (RAN) architecture based on centralized cloud computing that supports cooperative radio technology and real-time virtualization.

[0106] The primary goal of RAN cloudification is to decouple RAN hardware and software, centralizing the baseband units (BBUs) of multiple radio access network devices into a single baseband unit pool. This pool can be centrally located, maximizing statistical multiplexing gain, while simultaneously delegating the responsibility for fast wired transmission of orthogonal and phase data to the access network devices. RAN cloudification facilitates energy-efficient network operation and potential savings in baseband resource costs.

[0107] In RAN cloudification technology, cloud resources are allocated to RAN network elements to support the virtualization deployment of RAN network elements through cloud resources.

[0108] (5) Edge computing

[0109] Edge computing is a distributed computing architecture that pushes computing power and data storage to the network edge, close to the source of data generation (such as IoT devices and smart terminals). Edge computing differs from traditional cloud computing, which relies on centralized, remote data centers. The main purpose of edge computing is to enhance application performance and user experience by reducing data transmission latency, lowering bandwidth requirements, and improving real-time performance. Edge computing achieves this by pushing data processing capabilities closer to the data source, such as devices, sensors, and network edge nodes. Compared to uploading all data to a central cloud data center for processing, edge computing processes data locally, reducing latency and network transmission burden.

[0110] (6) RAN edge computing

[0111] In an O-RAN-based application layer architecture, the application server for edge computing can be deployed in the access network or O-RAN network elements, or it can be a new entity located close to the access network or O-RAN network elements to support RAN edge computing. This application server can be called an edge application server (EAS) or other names, such as far edge, without specific limitations. As shown in Figure 3, compared to edge computing schemes where EAS is deployed in the EDN, RAN edge computing deploys the EAS in the access network closer to the user, thus further reducing latency. In this application, the traditional edge application server deployment method can be called EDN-MEC. The edge computing architecture under RAN edge computing can be called RAN-MEC.

[0112] As an example of RAN edge computing, edge application servers can be deployed in an O-CU, O-DU, or O-RU, or in a new entity located close to an O-CU, O-DU, or O-RU.

[0113] In the RAN edge computing architecture, data transmission between terminal devices and application servers occurs via links between the terminal devices and O-RAN network elements. Because the application servers are deployed within O-RAN network elements, data transmission between them does not need to pass through the core network. This means the application servers are deployed closer to the terminal devices, further reducing data transmission latency compared to application-layer architectures based on EDN.

[0114] In RAN edge computing, cloud resources need to be allocated to edge application servers to support the virtualization deployment of edge application servers.

[0115] It should be noted that the above name is merely an exemplary designation, and this application is not limited to the specific names of the above concepts.

[0116] Additionally, it should be understood that the terms "system" and "network" in the embodiments of this application are interchangeable. Unless otherwise stated, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, sequence, priority, or importance of multiple objects. For example, "first request information" and "second request information" do not indicate that the content corresponding to these two request information is different.

[0117] Furthermore, the terms "comprising" and "having" in the embodiments, claims, and drawings of this application are not exclusive. For example, a process, method, system, product, or device that includes a series of steps or modules is not limited to the listed steps or modules, but may also include steps or modules not listed.

[0118] In summary, RAN can currently deploy RAN network elements and edge application servers. How to achieve the coordinated deployment of RAN network elements and edge application servers is a technical problem that urgently needs to be solved.

[0119] To address the aforementioned technical problems, this application provides a communication method. This method can be implemented by at least a first network device. As an example, the first network device can be a cloud-network collaborative orchestration function, a cloud resource orchestration function, or other network devices, functions, or network elements. Alternatively, the communication method can also be implemented by a first communication device. The first communication device can be a component of the first network device, such as a chip or functional module. Of course, the first communication device can also be other devices (or functional units, or management platforms, etc.) possessing the functions of the first network device described in this application.

[0120] In this application, the first network device can receive requests from deployment service consumers and deploy RAN network elements or RAN edge application servers according to the requests. For example, the first network device can configure RAN network elements or RAN edge application servers through configuration functions. Deployment service consumers can use this to request deployment services for RAN network elements or RAN edge application servers.

[0121] In this application, edge application servers can be orchestrated or deployed through cloud-network collaborative orchestration and cloud resource orchestration functions. For example, as shown in Figure 4, the deployment service consumer can be deployed in (or as) a cross-domain management function unit, while the cloud-network collaborative orchestration and configuration functions can be deployed in a domain management function unit. As shown in Figure 5, the deployment service consumer can be deployed in (or as) a business operation unit, the cloud-network collaborative orchestration function can be deployed in a cross-domain management function unit, and the configuration function can be deployed in a domain management function unit. RAN network elements and RAN edge application servers can be configured using the same or different configuration functions. For example, as shown in Figure 4, RAN network elements and RAN edge application servers can be configured using the configuration function deployed in the domain management function. For example, as shown in Figure 5, RAN network elements can be configured using the configuration function deployed in the RAN domain management function, and RAN edge application servers can be configured using the configuration function deployed in the MEC domain management function.

[0122] As shown in Figures 4 and 5, the cloud-network collaborative orchestration function can serve as an entity for managing RAN network elements and / or RAN edge application servers.

[0123] In addition, cloud resource orchestration capabilities can be deployed, for example, in the European Telecommunications Standards Institute (ETSI) Network Functions Virtualization (NFV) Management and Orchestration (MANO) (ETSI NFV MANO).

[0124] The communication method will be described below with reference to Figure 6.

[0125] S101: The first network device receives the first request information, which is used to request the deployment of the first object.

[0126] The first object can be deployed in the RAN or located near the RAN. For example, the first object is a RAN network element or a RAN edge application server.

[0127] As an example, the first network device can function as a cloud-network collaborative orchestration function, and the first request information can originate from a deployment service consumer. In this example, the first request information can specifically be used to request the deployment of a RAN network element or a RAN edge application server; for example, the first request information can specifically be a deployment request for a RAN network element or a RAN edge application server. The deployment service consumer can specifically be a business operation unit, such as government and enterprise equipment, third-party application developers, data users, or application functions. The deployment service consumer can send the first request information based on the needs of the RAN network element or RAN edge application server to be deployed or business requirements. For example, when it is necessary to deploy a RAN network element or a RAN edge application server, the deployment service consumer can send this first request information to request the deployment of the RAN network element or RAN edge application server.

[0128] As another example, the first network device can function as a cloud resource orchestration function, and the first request information can originate from the cloud-network collaborative orchestration function. In this example, the first request information can specifically be a resource allocation request from a RAN network element or a RAN edge application server. This first request information can be sent from the first network device to the cloud resource orchestration function after the edge computing service consumer receives a deployment request from the edge computing service consumer for a RAN network element or a RAN edge application server.

[0129] Optionally, if the first object is a RAN network element, the first request information may include the network element identifier, network element type information, or software image of the RAN network element.

[0130] The network element identifier of a RAN network element can be a device identifier or a network function identifier, etc., without specific limitations. This network element identifier can be an identifier assigned to the RAN network element by the deployment service consumer. It can be understood that if the first request information contains the network element identifier of the RAN network element to be deployed, then the first network device can identify the first object to be deployed as a RAN network element based on the network element identifier. The network element identifier can be the device identifier or NF identifier of the RAN network element, etc. Taking a base station as an example, the network element identifier can be the base station identifier.

[0131] The network element type information can be used to indicate whether a RAN network element is a virtual network element, a cloud network element, or a physical network element. If the network element type information indicates that the RAN network element is a virtual network element or a cloud network element, it means that the RAN network element is a cloud-based network element, which means that cloud resources need to be allocated to the RAN network element. If the network element type information indicates that the RAN network element is a physical network element, it means that the RAN network element is a traditional physical RAN network element, which does not need to be allocated cloud resources.

[0132] Specifically, network element type information can occupy one or more bits. When these one or more bits take a first value, it can represent that the RAN network element is a virtual network element; when they take a second value, it can represent that the RAN network element is a cloud network element; when they take a third value, it can represent that the RAN network element is a physical network element. Any two of the first, second, and third values ​​must be distinct. For example, if network element type information occupies 2 bits, the first value can be 00, the second value can be 01, and the third value can be 10. Alternatively, the first value can also represent that the RAN network element is a virtual network element or a cloud network element, and the second value can represent that the RAN network element is a physical network element. In this case, the network element type information can occupy 1 bit; for example, the first value can be 0, the second value can be 1, or the first value can be 1 and the second value can be 0.

[0133] A RAN (Radio Access Element) software image is an application file that runs on the corresponding cloud resources of the RAN network element to implement its functions. For example, a software image can be loaded into the cloud resources allocated to a RAN network element to run the corresponding application software of the RAN network element through those cloud resources. It is understood that the first request information may carry the RAN network element's software image, or it may carry information such as the software image's address or identifier to obtain the software image.

[0134] It is understood that if the first request information contains one or more of the following: the network element identifier, network element type information, or software image of the RAN network element to be deployed, the first network device can determine that the first object to be deployed is a RAN network element based on the network element type information.

[0135] Additionally, if the first object is a RAN edge application server, the first request information may include information about the edge application server. This information may include, for example, first instruction information and / or a software image of the RAN edge application server.

[0136] The first indication information can be used to indicate that the first object requested for deployment is a RAN edge application server. The first indication information can also be called a far edge indication, used to indicate a request to deploy a RAN edge application server. For example, the first indication information occupies 1 bit, and when the value of this bit is 0 (or 1), it means that the first request information contains the first indication information; when the value of this bit is 1 (or 0), it means that the first request information does not contain the first indication information.

[0137] The software image of the RAN edge application server is the application file that runs on the cloud resources corresponding to the edge application, used to implement the functionality of the edge application server. For example, the software image can be loaded into the cloud resources allocated for the RAN edge application server to run the corresponding application software of the first edge application server through those cloud resources. It is understood that the first request information may carry the software image of the RAN edge application server, or it may carry information such as the address or identifier of the software image for obtaining the software image.

[0138] It is understandable that if the first request information contains information about the edge application server, the first network device can determine that the first object to be deployed is the RAN edge application server based on the information about the edge application server.

[0139] In one possible embodiment, the first request information may further include a task description of the first object. This task description, also known as a feature description, can be used to describe the task corresponding to the first object. For example, if the first object is a RAN network element, the task description may indicate the functional type of the RAN network element to be deployed, such as CU, DU, RU, or UPF. Alternatively, the task description may indicate the capabilities supported by the RAN network element, such as terminal device registration, session management, or routing. Furthermore, if the first object is a RAN edge application server, the task description may indicate the services supported by the RAN edge application server, such as voice, video, gaming, or live streaming services. Here, each capability of the RAN network element and / or each service supported by the RAN edge application server can be understood as a task of the RAN network element.

[0140] It is also understood that the first request information in this application may include information required for deploying the first object, such as resource requirements information of the first object, PLMN information of the first object, location information of the first object, network slicing information, or hardware device information. For ease of explanation, one or more of the following information, such as the identifier of the first object, resource requirements information, PLMN information, location information, network slicing information, or hardware device information, may be referred to as the configuration information of the first object.

[0141] The following section introduces the resource requirements, PLMN information, location information, network slicing information, and hardware device information of the first object.

[0142] (1) Resource demand information

[0143] First, let's introduce cloud resources.

[0144] In this application, cloud resources can refer to a cloud site, cloud node, cloud cluster, or cloud resource pool. In this application, cloud resources can also be referred to as resources; that is, this application does not distinguish between "resources" and "cloud resources."

[0145] A cloud site can consist of one or more cloud nodes. A cloud site can have a cloud identifier, meaning it can be identified by that identifier. Multiple cloud nodes can form a cloud cluster, meaning any cloud cluster can contain multiple cloud nodes. A cloud resource pool can contain one or more cloud nodes. Cloud nodes, cloud clusters, or cloud resource pools can each have their own identifier; for example, a cloud node can be identified by a cloud node identifier, a cloud cluster by a cloud cluster identifier, and a cloud resource pool by a cloud resource pool identifier. These cloud node identifiers, cloud cluster identifiers, and cloud resource pool identifiers can be collectively referred to as cloud resource identifiers.

[0146] Furthermore, a cloud can be understood as a collection of cloud resources. That is, a cloud can contain one or more cloud sites, one or more cloud nodes, one or more cloud clusters, or one or more cloud resource pools. One or more clouds can be deployed in a network, and the resources of different clouds do not overlap. Clouds can be distinguished by cloud identifiers. Additionally, cloud resources can be distinguished by cloud resource identifiers. For example, a cloud resource identifier can be used to distinguish multiple cloud resources within the same cloud; that is, cloud resources in each cloud can be independently identified. To distinguish cloud resources in different clouds, a combination of a cloud identifier and a cloud resource identifier can uniquely represent a cloud resource. Alternatively, cloud resources in multiple clouds can be distinguished by different cloud identifiers; that is, cloud resources in multiple clouds can be independently identified, and in this case, the cloud resource identifier can uniquely represent a cloud resource.

[0147] In this application, resource requirement information can be used to indicate the cloud resource requirements of the first object. These cloud resource requirements include the computing resource requirements of the first object. Resource requirements may include, for example, requirements for computing resource types, storage types, computational load, and storage load. Computing types may include, for example, central processing units (CPUs), graphics processing units (GPUs), data processing units (DPUs), neural network processing units (NPUs), or tensor processing units (TPUs). Storage types may include hard disks or memory.

[0148] In one possible embodiment, the resource requirement information may include one or more of the following: the computing power type required by the first object, the computing power required, the storage type required, the storage quantity required, and the computing latency required.

[0149] The following sections will introduce the types of computing power required, the computing power required, the storage capacity required, and the computation latency required.

[0150] A. The type of computing power required, or computing power type requirement. Computing power type refers to the type of computing equipment used in the computing node. For example, computing power type can include one or more of CPU, GPU, NPU, or TPU. CPUs primarily rely on low-latency, high-complexity operations, capable of performing various arithmetic and logical operations and completing them quickly, making them suitable for a variety of computing tasks, especially scenarios requiring complex logical judgments and data processing. GPUs, due to their powerful parallel processing capabilities, are widely used in many fields, such as for computing processing in deep learning or graphics rendering. NPUs are processors similar to the human nervous system, designed specifically to accelerate AI applications. Due to their energy-saving characteristics, they can meet the needs of long-term use and are suitable for continuously processing AU (Analog Object) computing tasks, such as image generation or facial recognition.

[0151] The computing power type can be related to the business type of the first object. For example, for general technical tasks such as running operating systems and various software applications, designing for neural network inference, AI tasks, logical judgments, and data processing, the computing power type required by the first object can include CPU. Similarly, for graphics rendering businesses such as image rendering and 3D graphics processing, as well as other processing tasks, the computing power type required by the first object can include GPU. For neural network-related tasks, the computing power type required by the first object can include NPU. Furthermore, for large-scale AI training and inference tasks specifically designed for tensor operations in deep learning, especially applications using the tensor flow framework, the computing power type required by the first object can include TPU.

[0152] It is understandable that resource requirement information can use indexes or identifiers to represent the computing power type required by the first object. For example, index 0 represents a required computing power type of CPU, and index 1 represents a required computing power type of GPU. Accordingly, resource requirement information can contain index 0 and / or index 1, representing that the computing power type required by the first object is CPU and / or GPU. This correspondence between indexes and computing power types is merely an example and should not be construed as limiting.

[0153] B. Computing power required, or computing power requirement. Computing power refers to the amount of computation required to execute the computation task on the data to be computed in the first object. The unit of computing power can be millions of instructions per second (MIPS), dhrystone million instructions executed per second (DMIPS), operations per second (OPS), floating-point operations per second (FLOPS), or hash operations per second (Hash / s), etc. The computing power required for the first object can be related to the size of the data to be computed; for example, the required computing power should not be less than the computing power corresponding to the data to be computed.

[0154] The resource requirement information can include a numerical value or range of the required computing power. For example, if the computing power corresponding to the data to be calculated is 100, the resource requirement information can include the value 100, indicating that the computing power required by the first object is not less than 100. Additionally, the resource requirement information can also include an index of the computing power range to indicate the computing power required by the first object. For instance, index 0 represents a computing power range of 50 to 100, index 1 represents a computing power range of 101 to 200, and so on. If the computing power of the data to be calculated is less than or equal to 100, the resource requirement information can include index 1, indicating that the computing power required by the first object is not less than 100.

[0155] It is understood that the correspondence between computing power range and index can be preset, predefined or preconfigured, and this application does not specifically require it.

[0156] C, the required storage type, or storage type requirement, refers to the requirement for the type of storage space. The storage type required for the first object can be hard disk or memory, etc.

[0157] It is understandable that resource requirement information can use indexes or identifiers to represent the storage type required by the first object. For example, index 0 represents a storage type of disk, and index 1 represents a storage type of memory. Accordingly, resource requirement information can contain index 0 and / or index 1, representing that the storage type required by the first object is disk and / or memory. This correspondence between indexes and storage types is merely an example and should not be construed as limiting.

[0158] D, the required storage capacity, also known as storage requirement. Storage capacity refers to the amount of storage space needed to perform the computation task on the data to be computed in the first object. This storage space can include one or more of the following: cache space, memory space, or hard disk storage space. The unit of storage capacity can be bits or bytes, etc., without specific limitations. The size of the data to be computed in the first object can be related to the required storage capacity. For example, the stored content can include the data to be computed, temporary data generated during the computation, the final computation result, or one or more of other parameters required for computation execution (such as computation context or materials).

[0159] The resource requirement information can include the required storage quantity. For example, if the required storage quantity is 100, the resource requirement information can contain the value 100, indicating that the storage quantity required by the first object is not less than 100.

[0160] Additionally, the resource requirement information can also include an index indicating the storage range required by the first object. For example, index 0 represents a storage range of 50 to 100, index 1 represents a storage range of 101 to 200, and so on. If the required storage is less than or equal to 100, the resource requirement information can include index 1, indicating that the storage required by the first object is not less than 100.

[0161] It is understood that the correspondence between storage range and index can be preset, predefined or preconfigured, and this application does not specifically require it.

[0162] (2) Information about PLMN

[0163] The information from the PLMN can be used to indicate the PLMN to which the first object belongs, so that the first object can be deployed in the corresponding PLMN.

[0164] (3) Location information

[0165] Location information can be used to indicate the deployment location or deployment range of the first object. Location information can be related to the service range of the first object. For example, the location information in the first request information can be geographic location information, or location information that the core network can recognize, such as tracking area identity (TAI) or cell ID.

[0166] Optionally, different location information can be considered to correspond to different clouds, so the location information of the first object can be used to determine the cloud, and some or all of the cloud resources in the cloud can be used as the first resource.

[0167] (4) Network slice information

[0168] Network slice information can indicate the network slice corresponding to the first object. For example, the network slice information of the first object includes single network slice selection assistance information (S-NSSAI) or other information used to indicate the network slice.

[0169] (5) Hardware device information

[0170] Hardware device information can indicate the hardware device of the first object. Hardware devices include, for example, computing devices and / or storage devices. For instance, hardware device information may include the identifier of the computing device and / or the identifier of the storage device corresponding to the first object. Furthermore, hardware device information may also include location information or region information of the hardware device; therefore, the location or region of the hardware device can also represent the hardware device of the first object.

[0171] It is understood that the above description outlines the information that may be carried in the first request information. This application does not limit the first request information to also carrying other configuration parameters required during the deployment of RAN network elements and / or RAN edge application servers. These configuration parameters may also be included in the configuration information provided by the first network device to the configuration function. For example, the configuration information may also include network performance indicators, sleep mode parameters, or operating mode parameters of the RAN network elements and / or RAN edge application servers, without specific limitations. Network performance indicators may include network performance parameters such as key performance indicators (KPIs).

[0172] S102: The first network device determines the type information of the first object based on the first request information. The type information is used to indicate that the first object is a network element or an edge application server.

[0173] S102 can be understood as the first network device determining, based on the first request information, whether the first object to be deployed is a RAN network element or a RAN edge application server. That is, the type information of the first object can be used to indicate whether the first object is a RAN network element or a RAN edge application server.

[0174] As an exemplary implementation of S102, if the first request information includes one or more of the following: the network element identifier of the RAN network element, network type information or software image, address or identifier of the software image, then the type information of the first object can be used to indicate that the first object is a RAN network element.

[0175] Additionally, if the first request information includes information about the edge application server, such as the first indication information and / or the software image or address or identifier of the RAN edge application server, then the type information of the first object can be used to indicate that the first object is a RAN edge application server.

[0176] The type information of the first object can occupy one or more bits. Taking the type information of the first object occupying 1 bit as an example, if the value of the first object is 0 (or 1), the type information of the first object can be used to indicate that the first object is a RAN network element. If the value of the first object is 1 (or 0), the type information of the first object can be used to indicate that the first object is a RAN edge application server.

[0177] Alternatively, the type information of the first object can be considered to include one or more of the following: the network element identifier of the RAN network element, network type information or software image, and the address or identifier of the software image, to indicate that the first object is a RAN network element. Similarly, the type information of the first object can be considered to include one or more of the following: the first indication information and / or the software image of the RAN edge application server, and the address or identifier of the software image, to indicate that the first object is a RAN edge application server.

[0178] S103: The first network device deploys the first object according to the type information of the first object.

[0179] S103 can also be described as follows: The first network device configures the first object according to the type information of the first object.

[0180] It is understood that the deployment of the first object in S103 may include: the first network device determining the first object as a RAN network element or a RAN edge application server based on the type information of the first object, and / or deploying the RAN network element or the RAN edge application server.

[0181] The first object to be deployed in S103 may also include: resource allocation or determination information for the first network device.

[0182] Specifically, if the first network device is a cloud-network collaborative orchestration function, it can request resource information of the first object from the cloud resource orchestration function, and the cloud resource orchestration function can provide resource information to the cloud-network collaborative orchestration function. If the first network device is a cloud resource orchestration function, it can allocate resources for the first object after receiving the first request information.

[0183] For ease of explanation, the resources of the first object will be referred to as the first resource, which is located on the first cloud. That is, the first cloud can be used to deploy the first object, and the first resource of the first cloud can be used to run the application of the first object.

[0184] The following section, using method A1, describes how the cloud-network collaborative orchestration function obtains the resource information of the first object from the cloud resource orchestration function.

[0185] In method A1, after receiving the first request information, the cloud-network collaborative orchestration function sends a resource allocation request to the cloud resource orchestration function. This resource allocation request can be used to request the cloud resource orchestration function to allocate resources for the first object. The resource allocation request may include the resource requirement information and / or the type information of the first object. Correspondingly, the cloud resource orchestration function can determine the first resource based on the resource requirement information and / or the type information of the first object, and send the indication information of the first resource to the cloud-network collaborative orchestration function.

[0186] In this application, the indication information of the first resource can be used to indicate the first resource of the first cloud. The first cloud is the cloud to which the first resource belongs; it can also be said that the first cloud is used to deploy the first object, or that the first cloud serves the first object. For example, the indication information of the first resource includes the identifier of the first cloud and the identifier of the first resource, meaning the first resource can be uniquely identified by the identifier of the first cloud and the identifier of the first resource. Furthermore, if resources in multiple clouds use different resource identifiers, the first resource can be uniquely indicated from the resources of those multiple clouds by its identifier; in this case, the indication information of the first resource can be the resource identifier of the first resource. In this application, the identifier of the cloud can be called the cloud identifier. That is, resource information can include the indication information of the first resource.

[0187] In this application, the cloud resource orchestration function can determine the cloud that meets the resource requirements of the first object based on the resource requirement information of the first object and the resource status information of at least one cloud, and the cloud can serve as the first cloud serving the first object.

[0188] Cloud resource status information can represent the usage status of resources in the cloud. For example, taking the resource status information of the first cloud as an example, the resource status information of the first cloud includes the identifiers of occupied resources and the identifiers of unoccupied resources in the first cloud. Optionally, the cloud resource orchestration function can determine the unoccupied resources in the first cloud based on the identifiers of occupied resources and unoccupied resources, so as to identify the first resource from the unoccupied resources.

[0189] In addition, resource status information may also include the identifier of the task (or first object) corresponding to the occupied resources in the cloud.

[0190] The identifier of the task corresponding to the occupied resource can be used to indicate the service application (APP), microservice (MS), or other computing task occupying the resource. For example, the task identifier can be a workload identifier. The task corresponding to the occupied resource can also be referred to as the task occupying the resource.

[0191] In addition, the cloud's resource status information may also include at least one of the following: cloud's available and / or occupied computing power type, computing power, storage type, storage amount, or computing latency, to determine whether the cloud meets the resource requirements of the first object.

[0192] It is understandable that a cloud satisfies the resource requirements of the first object if its resource status information meets at least one of the following conditions:

[0193] Condition 1: The available computing power types of the cloud include the computing power type required by the first object. Here, the available computing power type of the cloud can refer to the computing power type supported by the available resources of the cloud. Available cloud resources are cloud resources with currently existing available computing power.

[0194] Condition 2: The available computing power of the cloud is not less than the computing power required by the first object. Here, the available computing power of the cloud can refer to the remaining computing power of the cloud's available resources.

[0195] Condition 3: The available storage types in the cloud include the storage type required by the first object. Here, "available storage type in the cloud" refers to the storage type of the available storage space in the cloud. Available storage space in the cloud refers to the cloud storage space with currently available storage capacity.

[0196] Condition 4: The available storage capacity of the cloud is not less than the storage capacity required by the first object. Here, the available storage capacity of the cloud can refer to the remaining storage capacity of the cloud's available storage space.

[0197] Condition 5: The cloud's computing latency is not higher than the computing latency required by the first object. Here, cloud computing latency refers to the time required for the available cloud resources to execute computing tasks, specifically the time required for those resources to execute a certain amount of computing tasks.

[0198] In this application, if the unoccupied resources of a certain cloud can meet the resource requirements of the first object, then that cloud can be used as the first cloud. The first network device can allocate first resources from the unoccupied resources of the first cloud.

[0199] Furthermore, if the unused resources of the cloud cannot meet the resource requirements of the first object, the cloud resource orchestration function can indicate to the cloud-network collaborative orchestration function that cloud resources are insufficient. For example, if no cloud exists that meets the resource requirements, the cloud resource orchestration function can send a second indication to the cloud-network collaborative orchestration function to indicate insufficient cloud resources. Specifically, the second indication information can indicate that the remaining resources of the first cloud are less than the resource requirements of the first object. For example, the second indication information can include the difference between the resource requirements of the first object and the remaining resources of the first cloud. In addition, the second indication information can also include the cloud identifier and resource status information of the first cloud, which are used by the cloud-network collaborative orchestration function to determine whether to deploy the first object in the first cloud. The remaining resources can also be replaced with available resources.

[0200] The resource status information of the first cloud may include the identifier of the occupied resources in the first cloud and the type information of the object corresponding to the task of the occupied resource. Optionally, the resource status information of the first cloud may also include one or more of the following: computing power type, computing power, storage type, storage amount, computing latency, identifier of the task corresponding to the occupied resource, or storage method information of the task corresponding to the occupied resource.

[0201] Optionally, the first cloud may be determined based on the type information of the first object. For example, the first cloud supports object services for the type indicated by the type information of the first object.

[0202] For example, clouds can be categorized based on the type of objects they support, allowing different clouds to provide services to different types of objects. For instance, a first cloud set might include at least one cloud that can provide services to RAN network elements, while a second cloud set might include at least one cloud that can provide services to RAN edge application servers. In other words, when the type information of a first object indicates that the first object is a RAN network element, the cloud resource orchestration function can determine the first cloud from the clouds in the first cloud set; conversely, when the type information of a first object indicates that the first object is a RAN edge application server, the cloud resource orchestration function can determine the first cloud from the clouds in the second cloud set.

[0203] If a second instruction is received, cloud-network collaborative orchestration can determine whether to deploy the first object in the first cloud based on the type information of the first object and the type information of the second object. The second object can be one or more objects already occupying resources in the first cloud. For example, if the deployment type information of the first object indicates that the first object is a RAN edge application server, the task corresponding to the resources occupied in the first cloud is the task of the second object, and the type information of the second object indicates that the second object is a RAN network element, then cloud-network collaborative orchestration can determine to deploy the first object in the first cloud. For instance, the cloud-network collaborative orchestration function can instruct to reduce the second object's resource occupation in the first cloud, so that the available resources in the first cloud meet the resource requirements of the first object. Optionally, cloud-network collaborative orchestration can also send a third instruction to the cloud resource orchestration function to instruct to reduce the second object's occupation of resources in the first cloud.

[0204] It is understandable that the cloud-network collaborative orchestration function can obtain the type information of the second object from the configuration function. For example, if the second object is a configured object, the configuration function can maintain its configuration information, including its type information. Upon receiving a second instruction from the cloud resource orchestration function, the cloud-network collaborative orchestration function can send a second request to the configuration function, based on the cloud identifier of the first cloud contained in the second instruction, to request an object from the first cloud service. This second request may contain the cloud identifier of the first cloud. Correspondingly, the configuration function can query the object from the first cloud service based on the cloud identifier of the first cloud, obtain the information of the second object, and provide this information to the cloud collaborative orchestration function. The information of the second object may include its type information and information such as the resources it occupies.

[0205] As an example, the third instruction information can be used to instruct the transfer of a second object's task to a second cloud. In this case, the third instruction information may include the task identifier of the second object. The task identifier of the second object is also the identifier of the task corresponding to the occupied resources of the first cloud, which is contained in the resource status information of the first cloud. The second cloud can be determined by network-operational orchestration, meaning the third instruction information can include the cloud identifier of the second cloud. Alternatively, the second cloud can be determined by cloud resource orchestration functions. In this case, the third instruction information does not need to carry the cloud identifier of the second cloud; that is, the third instruction information can be used to instruct the transfer of the second object's task to a cloud other than the first cloud.

[0206] Upon receiving the third instruction information, the cloud resource orchestration function can transfer the task of the second object to a second resource in the second cloud. Optionally, the third instruction information may also include instruction information for the second resource, meaning the second resource can be allocated by the cloud-network collaborative orchestration function. Referring to the description of the instruction information for the first resource, the instruction information for the second resource can be used to instruct the second resource in the second cloud. Furthermore, the cloud resource orchestration function can also allocate the second resource; for example, it can determine, based on the resource requirements of the second object and the resource status information of other clouds, that the second resource in the second cloud will provide services for the task of the second object.

[0207] For example, if the deployment type information of the first object indicates that the first object is a RAN network element, and the type information of the second object corresponding to the resources occupied in the first cloud is a RAN network element or a RAN edge application server, then cloud-network collaborative orchestration can determine not to deploy the first object in the first cloud. In this case, a resource allocation failure message can be displayed, or another cloud can be selected for the first object.

[0208] In other words, cloud resources can be allocated to provide services to RAN edge application servers to meet the service needs of the applications corresponding to those servers. For example, compared to the service needs of RAN network elements, the applications corresponding to RAN edge application servers may require lower computational latency, so resources can be allocated to RAN edge application servers first.

[0209] As another example, the third instruction information can be used to instruct the cessation of the second object's task. Accordingly, cloud resource orchestration can stop the second task's occupation of resources in the first cloud. Optionally, cloud resource orchestration can also allocate resources for the second object from other clouds besides the first cloud; the description of determining the second resources in the second cloud using cloud resource orchestration in the previous example will not be repeated here.

[0210] It is understandable that the cloud resource orchestration function can send the first resource instruction information to the cloud network collaborative orchestration function after allocating the first resource, in order to indicate the first resource.

[0211] In addition, the resource allocation method for the first object when cloud resource orchestration is used as the first network device will be introduced below in conjunction with method A2.

[0212] In one possible embodiment, the cloud resource orchestration function can further assign task identifiers to the first object based on the task description of the first object. Specifically, if the task description of the first object indicates that the first object has multiple tasks, the cloud resource orchestration function can assign a task identifier to each task. This can be understood as different tasks using different resource services, or in other words, the cloud resource orchestration function can allocate resources for each task. For example, each task identifier corresponds to one resource identifier. Optionally, after allocating resources, the cloud resource orchestration function can send the correspondence between the multiple task identifiers and multiple resource identifiers of the first object to the cloud-network collaborative orchestration function. This can also be understood as the first resource including multiple resources corresponding to multiple tasks (or task identifiers).

[0213] The task description of the first object can be sent by the cloud resource orchestration function of the cloud-network collaborative orchestration function item.

[0214] In addition, the cloud-network collaborative orchestration function can send a fourth instruction to the configuration function. This fourth instruction can be used to instruct the updating of the configuration information and / or resource information of the second object. For example, the fourth instruction includes the updated configuration information and / or resource information of the second object.

[0215] In one possible implementation, the cloud-network collaborative orchestration function can update the configuration information of the second object to reduce its resource consumption. For example, the cloud-network collaborative orchestration function can update the configuration of the second object to reduce parameters such as power consumption, thereby reducing the resource consumption of the second object. Correspondingly, the cloud-network collaborative orchestration function can send the updated configuration parameters to the configuration function, enabling the configuration function to maintain the updated configuration parameters of the second object and / or configure the second object according to the updated configuration parameters. For example, the updated configuration information could be a hibernation configuration, meaning the updated configuration information can be used to adjust the second object into hibernation mode to reduce its resource requirements.

[0216] In addition, when the second object stops occupying resources in the first cloud, the cloud-network collaborative orchestration function can send updated resource information of the second object to the configuration function to indicate that the second object no longer occupies the first resource.

[0217] Optionally, if the resources occupied by the second object are transferred to the second resource in the second cloud, the updated resource information of the second object may include indication information of the second resource.

[0218] Optionally, if the first object is the RAN edge application server cloud-network collaborative orchestration function, it can also determine the RAN network elements to be deployed in the same cloud as the RAN edge application server based on at least one of the following: information about the PLMN to which the RAN edge application server belongs, the location information of the RAN edge application server, information about the PLMN to which the RAN network element belongs, and the location information of the RAN network element. For example, if the information about the PLMN to which the RAN network element belongs is the same as the information about the PLMN to which the RAN edge application server belongs, and / or, the location information of the RAN network element is the same as the location information of the RAN edge application server, then the RAN network element and the RAN edge application server can be deployed in the same cloud. As another example, if the RAN network element and the RAN edge application server use the same network slice and / or hardware equipment, then the RAN network element and the RAN edge application server can be deployed in the same cloud. Specifically, it can be determined whether the RAN network element and the RAN edge application server use the same network slice based on the network slice information of the RAN network element and the slice information of the RAN edge application server. Additionally, it can be determined whether the RAN network element and the RAN edge application server use the same hardware equipment based on the hardware equipment information of the RAN network element and the hardware equipment information of the RAN edge application server. It is understandable that network slicing information and / or hardware device information of RAN network elements and / or RAN edge application servers can be carried in the deployment request sent by the deployment service consumer to the cloud-network collaborative orchestration function.

[0219] The subsequent cloud-network collaborative orchestration function can request the cloud resource orchestration function to allocate resources from the same cloud for the RAN edge application server and the RAN network element. For example, the resource allocation request sent by the cloud-network collaborative orchestration function to the cloud resource orchestration function can include a cloud identifier. This cloud identifier indicates the cloud corresponding to the RAN network element deployed in the same cloud as the RAN edge application server, meaning it can request resources from that cloud to serve the RAN edge application server. After allocating resources to the RAN network element, the cloud-network collaborative orchestration function can store the correspondence between the RAN network element and the cloud identifier (or resource indication information). During the subsequent deployment of the RAN edge application server, it can use this correspondence to determine the cloud identifier corresponding to the RAN network element deployed in the same cloud as the RAN edge application server. Accordingly, the cloud resource orchestration function can determine the resources serving the RAN edge application server within that cloud.

[0220] Furthermore, if the RAN edge application server does not have any RAN network elements deployed in the same cloud, the resource allocation request sent by the cloud-network collaborative orchestration function to the cloud resource orchestration function may not include a cloud identifier, meaning it is not required that the cloud to which the resources served by the RAN edge application server belong. In other words, it is not required that the RAN edge application server and the RAN network elements be deployed in the same cloud, i.e., it is not required that the RAN edge application server and the RAN network elements be allocated resources in the same cloud.

[0221] In method A2, if the cloud resource orchestration function is the first network device, the cloud resource orchestration function can determine the first resource based on the resource requirement information and / or type information of the first object from the cloud-network collaborative orchestration function, and send the instruction information of the first resource to the cloud-network collaborative orchestration function.

[0222] Referring to the description in method A1, the cloud resource orchestration function can determine the cloud that meets the resource requirements of the first object as the first cloud. Furthermore, referring to the description in method A1, the cloud resource orchestration function can determine the first resource based on the resource requirement information of the first object and the resource status information of the first cloud.

[0223] Furthermore, if the unused resources in the first cloud cannot meet the resource requirements of the first object, the cloud resource orchestration function can determine whether to deploy the first object in the first cloud based on the first object's type information. For example, if the deployment type information of the first object indicates that the first object is a RAN edge application server, the task corresponding to the occupied resources in the first cloud is the task of the second object, and the resource status information of the first cloud includes the type information of the second object, which indicates that the second object is a RAN network element, then cloud-network collaborative orchestration can reduce the second object's resource occupation in the first cloud, ensuring that the available resources in the first cloud meet the resource requirements of the first object.

[0224] Optionally, the cloud resource orchestration function can transfer the tasks of the second object to the second resources of the second cloud, that is, the cloud resource orchestration function can allocate the second resources. For example, the cloud resource orchestration function can determine, based on the resource requirements information of the second object and the resource status information of other clouds, that the second resources in the second cloud will provide services for the tasks of the second object.

[0225] For example, if the deployment type information of the first object indicates that the first object is a RAN network element, and the type information of the second object corresponding to the resources occupied in the first cloud is a RAN network element or a RAN edge application server, then the cloud resource orchestration function can determine not to deploy the first object in the first cloud. In this case, the cloud resource orchestration function can prompt the cloud-network collaborative orchestration function with a resource allocation failure, or select a cloud other than the first cloud for the first object.

[0226] Referring to the description in Method A1, in Method A2, the cloud resource orchestration function can determine whether there are RAN network elements deployed in the same cloud as the RAN edge application server. If there are RAN network elements and RAN edge application servers deployed in the same cloud, the cloud resource orchestration function can allocate resources for the RAN network element and RAN edge application server from the resources of the same cloud.

[0227] For example, in the deployment process of RAN network elements, the cloud-network collaborative orchestration function can provide the cloud resource orchestration function with the fifth instruction information to instruct the RAN network element and the RAN edge application server to be deployed in the same cloud. In addition, in the deployment process of RAN edge application servers, the cloud-network collaborative orchestration function can also provide the cloud resource orchestration function with the fifth instruction information to instruct the RAN edge application server and the RAN network element to be deployed in the same cloud. Therefore, the cloud resource orchestration function can determine the RAN network element and the RAN edge application server to be deployed in the same cloud based on the fifth instruction information, thereby allocating resources in the same cloud for the RAN network element and the RAN edge application server.

[0228] For example, the cloud-network collaborative orchestration function can provide the cloud resource orchestration function with at least one of the following: PLMN, location information, network slice information, or hardware device information of the RAN network element; and provide at least one of the following: PLMN, location information, network slice information, or hardware device information of the RAN edge application server. This enables the cloud resource orchestration function to determine the co-cloud deployment of the RAN network element and the RAN edge application server based on at least one of the following: PLMN, location information, network slice information, or hardware device information.

[0229] Deploying the first object in S103 may also include: the first network device sending configuration information and / or resource information of the first object to the configuration function.

[0230] The configuration information of the first object may include the first object's identifier, resource requirements, PLMN information, location information, network slicing information, or hardware device information. This configuration information can be carried within the first request information; that is, the first network device can obtain the first object's configuration information from the first request information.

[0231] For example, the cloud-network collaborative orchestration function can send a management object creation request to the configuration function to deploy the first object as a management object. This management object creation request may include the first object's configuration information and / or resource information. Subsequently, the configuration function can create the first object and maintain its configuration and / or resource information. Furthermore, the configuration function can configure the first object based on the configuration information, or configure the first object's resources based on the resource information.

[0232] The deployment process of RAN network elements and RAN edge application servers will be described below with reference to Figure 7. In Figure 7, RAN network elements and / or RAN edge application servers can be considered as the first objects in the process shown in Figure 6.

[0233] As shown in Figure 7, a communication method provided in this application embodiment may include the following steps:

[0234] S201: The deployment service consumer sends a first deployment request to the cloud-network collaborative orchestration function. The first deployment request can be used to request the deployment of RAN network elements.

[0235] The first deployment request may include the identifier of the RAN network element, the information of the PLMN to which the RAN network element belongs, the location information of the RAN network element, the network element type information of the RAN network element, the task description of the RAN network element, the software image of the RAN network element, and the resource requirements information of the RAN network element.

[0236] This first deployment request can be used as an example of the first request information in S101. The identifier of the RAN network element, the information of the PLMN to which the RAN network element belongs, the location information of the RAN network element, the network element type information of the RAN network element, the task description of the RAN network element, the software image of the RAN network element, and the resource requirement information of the RAN network element can be referred to in S101 and will not be repeated here.

[0237] Among them, the network element type information of the RAN network element in the first deployment request can be used to indicate whether the RAN network element is a virtual network element or a cloud network element.

[0238] S202: The cloud-network collaborative orchestration function determines the cloud resource orchestration to be performed based on the first deployment request.

[0239] In S202, the cloud-network collaborative orchestration function can determine whether cloud resources need to be allocated to RAN network elements based on the identifier and / or network element type information of the RAN network elements, that is, whether cloud resource orchestration needs to be performed or cloud resource support is required.

[0240] S203: The cloud-network collaborative orchestration function sends a resource allocation request to the cloud resource orchestration function to request the allocation of cloud resources for RAN network elements.

[0241] In S203, the resource allocation request can carry the software image of the RAN network element, resource requirement information, task description and type information.

[0242] The type information can be used to indicate that the object to be deployed is a RAN network element. For example, the value of the type information is NF.

[0243] S204: The cloud resource orchestration function has been identified as resource #1 for RAN network element services.

[0244] Resource #1 can be used as an example of the first resource. The method for determining resource #1 can be referred to the description in method A1. For example, the cloud resource orchestration function can determine cloud #1 based on the resource requirement information of the RAN network element and the resource status information of at least one cloud, and determine resource #1 from the available resources of cloud #1.

[0245] Among them, Cloud #1 can be used as an example of the first cloud. That is, Cloud #1 can meet the resource requirements of RAN network elements.

[0246] Optionally, the cloud resource orchestration function can also determine the task identifiers of one or more tasks for an RNA network element based on the task description of the RAN network element. Each task can correspond to a cloud resource.

[0247] In addition, the cloud resource orchestration function can also run the software image of the RAN network element in resource #1.

[0248] S205: The cloud resource orchestration function item cloud network collaborative orchestration function sends a resource allocation response, which includes the indication information for resource #1.

[0249] For example, the indication information for resource #1 includes the identifier of cloud #1 and the identifier of resource #1.

[0250] Optionally, the resource allocation response may also include task identifiers for one or more tasks of the RNA network element.

[0251] S206: Cloud and network share the same orchestration function to store the configuration and resource information of RAN network elements.

[0252] The configuration information of a RAN network element includes at least one of the following: the RAN network element's identifier, the PLMN to which the RAN network element belongs, the RAN network element's location information, and the RAN network element's resource requirement information. The resource information of the RAN network element includes indication information for the first resource.

[0253] S207: The cloud-network collaborative orchestration function sends configuration and resource information of RAN network elements to the configuration function.

[0254] Correspondingly, the configuration function can configure RAN network elements based on configuration information and resource information.

[0255] In addition, the cloud-network collaborative orchestration function can also send deployment response information corresponding to the first deployment request to the deployment service consumer to indicate that the RAN network element deployment is complete.

[0256] S208: The deployment service consumer sends a second deployment request to the cloud-network collaborative orchestration function. The second deployment request can be used to request the deployment of the RAN edge application server.

[0257] The second deployment request may include first instruction information, information about the PLMN to which the RAN edge application server belongs, location information of the RAN edge application server, task description of the RAN edge application server, software image of the RAN edge application server, and resource requirements information of the RAN edge application server.

[0258] This second deployment request can be considered as an example of the first request information in S101. The first instruction information, the information of the PLMN to which the RAN edge application server belongs, the location information of the RAN edge application server, the task description of the RAN edge application server, the software image of the RAN edge application server, and the resource requirements information of the RAN edge application server can be referred to in S101 and will not be repeated here. The first instruction information can be used to indicate that the object of the deployment request is the RAN edge application server. The software image of the RAN edge application server can be an application software image.

[0259] S209: The cloud-network collaborative orchestration function determines the execution of cloud resource orchestration based on the second deployment request.

[0260] In S209, the cloud-network collaborative orchestration function can determine, based on the first instruction information and / or the software image of the RAN edge application server, whether cloud resources need to be allocated to the RAN edge application server, that is, whether cloud resource orchestration needs to be performed or cloud resource support is required.

[0261] Optionally, the cloud-network collaborative orchestration function can also determine the RAN network elements deployed in the same cloud as the RAN edge application server based on at least one of the following: the PLMN to which the RAN edge application server belongs, the location information of the RAN edge application server, the PLMN to which the RAN network element belongs, and the location information of the RAN network element. Subsequently, it can request the allocation of the same cloud resources for the RAN edge application server and the RAN network element.

[0262] Among them, the RAN network elements deployed in the same cloud as the RAN edge application server can be the network elements deployed in S201 to S208, other RAN network elements, or RAN network elements that have not yet been deployed. If the RAN network elements deployed in the same cloud as the RAN edge application server cannot be determined in S209, then the cloud where the RAN edge application server is deployed is not restricted.

[0263] S210: The cloud-network collaborative orchestration function sends a resource allocation request to the cloud resource orchestration function to request the allocation of cloud resources for the RAN edge application server.

[0264] In S210, the resource allocation request may carry at least one of the following: the software image of the RAN edge application server, resource requirement information, task description, and type information.

[0265] The type information can be used to indicate that the object to be deployed is a RAN edge application server. For example, the value of the type information is APP.

[0266] Optionally, if there is a RAN network element deployed in the same cloud as the RAN edge application server, the resource allocation request may include the cloud identifier of the RAN network element so as to request the cloud resource orchestration function to allocate resources for the RAN edge application server in that cloud.

[0267] S211: The cloud resource orchestration function has been identified as resource #2 for the RAN edge application server service.

[0268] Resource #2 can be used as an example of the first resource. The method for determining resource #2 can be referred to the description in method A1. For example, the cloud resource orchestration function can determine cloud #2 based on the resource requirement information of the RAN edge application server and the resource status information of at least one cloud, and determine resource #2 from the available resources of cloud #2.

[0269] Cloud #2 can serve as an example of a first-class cloud. That is, Cloud #2 can meet the resource requirements of the RAN edge application server.

[0270] Optionally, the cloud resource orchestration function can also determine the task identifiers of one or more tasks of the RNA edge application server based on the task description of the RAN edge application server. Each task can correspond to a cloud resource.

[0271] In addition, the cloud resource orchestration function can also run the software image of the RAN edge application server in resource #2.

[0272] S212: The cloud resource orchestration function item cloud network collaborative orchestration function sends a resource allocation response, which includes the indication information for resource #2.

[0273] For example, the indication information for resource #2 includes the identifier of cloud #2 and the identifier of resource #2.

[0274] Optionally, the resource allocation response may also include task identifiers for one or more tasks of the RNA edge application server.

[0275] S213: Cloud and network share the same orchestration function to store the configuration and resource information of the RAN edge application server.

[0276] The configuration information of the RAN edge application server includes at least one of the following: the identifier of the RAN edge application server, the information of the PLMN to which the RAN edge application server belongs, the location information of the RAN edge application server, and the resource requirements information of the RAN edge application server. The resource information of the RAN edge application server includes indication information of the first resource.

[0277] S214: The cloud-network collaborative orchestration function sends configuration and resource information of the RAN edge application server to the configuration function.

[0278] Correspondingly, the configuration function can configure the RAN edge application server based on configuration information and resource information.

[0279] In addition, the cloud-network collaborative orchestration function can also send deployment response information corresponding to the second deployment request to the deployment service consumer to indicate that the RAN edge application server deployment is complete.

[0280] It is understandable that S201 to S207 in Figure 7 can be considered as the deployment process when the first object is the RAN network element, and S208 to S214 can be considered as the deployment process when the first object is the RAN edge application server. S201 to S207 and S208 to S214 can be considered as two independent processes, meaning the RAN network element and the RAN edge application server can be deployed independently. Alternatively, S201 to S207 and S208 to S214 can be combined into a single process.

[0281] In one possible embodiment of this application, a deployment service consumer may request a shared cloud deployment requirement between the RAN network element and the RAN edge application server. The resources serving the RAN network element and the resources serving the RAN edge application server may belong to the same cloud. For example, the RAN network element may provide the edge application server functionality, and the deployment service consumer may indicate a subsequent shared cloud deployment requirement for the RAN edge application server when requesting the deployment of the RAN network element. For instance, in campus network or private network scenarios, both the RAN network element and the RAN edge application server may be dedicated to third-party customers, making shared cloud deployment of the RAN network element and the RAN edge application server highly probable.

[0282] For example, if the first object is a RAN network element and the third object is a RAN edge application server, and the first and third objects have a shared cloud deployment requirement, the first request information can include a fifth indication. This fifth indication can be used to indicate that the first and third objects are deployed in the same cloud. For example, the fifth indication can include information about the RAN edge application server to indicate that the RAN network element and the RAN edge application server are deployed in the same cloud. For example, the information about the RAN edge application server may include information such as software image information, PLMN information, or location information. Alternatively, the fifth indication may not specify a particular RAN edge application server. For example, it can be assumed that if both the deployment request for the RAN network element and the deployment request for the RAN edge application server include the fifth indication, it means that the RAN network element and the RAN edge application server are deployed in the same cloud.

[0283] If the first request information includes the fifth indication information, or if the first request is used to request the deployment of RAN network elements and RAN edge application servers, the cloud-network collaborative orchestration function and / or cloud resource orchestration function can allocate resources for the first object and the third object in the same cloud. For example, the cloud-network collaborative orchestration function can obtain the resource information of the first object from the cloud resource orchestration function, that is, obtain the indication information of the first resource. The cloud-network collaborative orchestration function can also request the cloud resource orchestration function to allocate a third resource for the third object from the first cloud, and obtain the indication information of the third resource from the cloud resource orchestration function. This indication information of the third resource can be used to indicate the third resource in the first cloud.

[0284] Furthermore, the cloud-network collaborative orchestration function can also request the cloud resource orchestration function to allocate resources for a first object and a third object through the same request information or message. This resource allocation request can include type information for both the first and third objects. Accordingly, the cloud resource orchestration function can determine whether to deploy the first and third objects in the same cloud based on this type information; for example, it can determine the first resource serving the first object and the third resource serving the third object from the resources of the first cloud. The cloud resource orchestration function can also send indication information for both the first and third resources to the cloud-network collaborative orchestration function.

[0285] The following section, with reference to Figure 8, will introduce the deployment of RAN network elements and RAN edge application servers in the first cloud as an example.

[0286] If the cloud-network collaborative orchestration function receives a first request message for deploying RAN network elements, and this first request message contains a fifth indication message, then the cloud-network collaborative orchestration function can determine the RAN network elements and the RAN edge application server. The cloud-network collaborative orchestration function can obtain the first resource indication message for the RAN network elements from the cloud resource orchestration function.

[0287] As shown in Figure 8, a communication method provided in this application embodiment may include the following steps:

[0288] S301: The deployment service consumer sends a first deployment request to the cloud-network collaborative orchestration function. The first deployment request can be used to request the deployment of RAN network elements. The first deployment request includes a far-edge indication, which can be used to indicate that the RAN network element and the RAN edge application server are deployed in the same cloud.

[0289] Specifically, the far-edge indication may include information about the RAN edge application server to indicate that the RAN network element and the RAN edge application server are deployed in the same cloud. For example, the RAN edge application server information may include software image information, PLMN information, or location information. Alternatively, the far-edge indication may not indicate a specific RAN edge application server.

[0290] Furthermore, referring to the description in S201, the first deployment request may include the identifier of the RAN network element, information about the PLMN to which the RAN network element belongs, the location information of the RAN network element, the network element type information of the RAN network element, the task description of the RAN network element, the software image of the RAN network element, and the resource requirement information of the RAN network element.

[0291] This first deployment request can serve as an example of the first request information in S101.

[0292] It is understandable that this far edge indication can serve as an example of how the fifth indication information can be implemented.

[0293] S302: The cloud-network collaborative orchestration function determines the cloud resource orchestration to be performed based on the first deployment request.

[0294] S303: The cloud-network collaborative orchestration function sends a resource allocation request to the cloud resource orchestration function to request the allocation of cloud resources for RAN network elements.

[0295] S304: The cloud resource orchestration function is determined to be resource #1 in cloud #1 of RAN network element service.

[0296] S305: The cloud resource orchestration function item, cloud-network collaborative orchestration function, sends a resource allocation response, which includes indication information for resource #1.

[0297] For example, the indication information for resource #1 includes the identifier of cloud #1 and the identifier of resource #1.

[0298] S306: Cloud and network share the same orchestration function to store the configuration and resource information of RAN network elements.

[0299] S307: The cloud-network collaborative orchestration function sends configuration and resource information of RAN network elements to the configuration function.

[0300] In addition, the cloud-network collaborative orchestration function can also send deployment response information corresponding to the first deployment request to the deployment service consumer to indicate that the RAN network element deployment is complete.

[0301] S302 to S307 can be referred to S202 to S207 respectively, and will not be repeated here.

[0302] S308: The deployment service consumer sends a second deployment request to the cloud-network collaborative orchestration function. This second deployment request can be used to request the deployment of a RAN edge application server. The second deployment request includes a far-edge indication, which can be used to indicate that the RAN network element and the RAN edge application server are deployed in the same cloud.

[0303] The cloud-network collaborative orchestration function determines that the RAN edge application server and the RAN network elements deployed in S301 to S307 are deployed in the same cloud based on the far edge indication in the first deployment request and the far edge indication in the second deployment request.

[0304] Additionally, referring to the description in S208, the second deployment request may include first instruction information, information about the PLMN to which the RAN edge application server belongs, location information of the RAN edge application server, task description of the RAN edge application server, software image of the RAN edge application server, and resource requirement information of the RAN edge application server.

[0305] This second deployment request can serve as an example of the first request information in S101.

[0306] S309: The cloud-network collaborative orchestration function determines the execution of cloud resource orchestration based on the second deployment request.

[0307] S309 can be referenced from S209, and will not be elaborated further.

[0308] Understandably, since the second deployment request includes a far edge indication, the cloud-network collaborative orchestration function can determine the RAN edge application server and the aforementioned RAN network elements to be deployed in the same cloud based on the far edge indication. It is no longer necessary to determine other RAN network elements to be deployed in the same cloud as the RAN edge application server based on at least one of the following: the information of the PLMN to which the RAN edge application server belongs, the location information of the RAN edge application server, the information of the PLMN to which the RAN network element belongs, and the location information of the RAN network element.

[0309] S310: The cloud-network collaborative orchestration function sends a resource allocation request to the cloud resource orchestration function to request the allocation of cloud resources for the RAN edge application server.

[0310] In S310, the resource allocation request includes the cloud identifier of cloud #1, which is used to request the cloud resource orchestration function to allocate resources in cloud #1 to the RAN edge application server.

[0311] Additionally, referring to the description in S210, the resource allocation request in S310 can carry the software image of the RAN edge application server, resource requirement information, task description, and type information.

[0312] S311: The cloud resource orchestration function has been identified as resource #2 for the RAN edge application server service.

[0313] Resource #2 can be used as an example of the first resource. The method for determining resource #2 can be referred to the description in method A1. For example, the cloud resource orchestration function can determine resource #2 from the available resources of cloud #1 based on the resource requirement information of the RAN edge application server and / or the resource status information of at least one cloud.

[0314] Optionally, the cloud resource orchestration function can also determine the task identifiers of one or more tasks of the RNA edge application server based on the task description of the RAN edge application server. Each task can correspond to a cloud resource.

[0315] In addition, the cloud resource orchestration function can also run the software image of the RAN edge application server in resource #2.

[0316] S312: The cloud resource orchestration function item cloud network collaborative orchestration function sends a resource allocation response, which includes the indication information for resource #2.

[0317] S313: Cloud and network share the same orchestration function to store the configuration and resource information of the RAN edge application server.

[0318] S314: The cloud-network collaborative orchestration function sends configuration and resource information of the RAN edge application server to the configuration function.

[0319] In addition, the cloud-network collaborative orchestration function can also send deployment response information corresponding to the second deployment request to the deployment service consumer to indicate that the RAN edge application server deployment is complete.

[0320] The above S312 to S314 can be referred to the explanations of S212 to S214 respectively, and will not be repeated here.

[0321] It is understandable that S301 to S307 in Figure 8 can serve as the deployment process for RAN network elements, while S308 to S314 can serve as the deployment process for RAN edge application servers deployed in the same cloud as the RAN network element. S301 to S307 and S308 to S314 can be considered two independent processes, meaning the RAN network element and the RAN edge application server can be deployed independently. Alternatively, S301 to S307 and S308 to S314 can be combined into a single process.

[0322] It can also be understood that the process in Figure 8, which uses the deployment process of RAN network elements deployed in the same cloud before the deployment process of RAN edge application servers deployed in the same cloud, can be changed to the deployment process of RAN edge application servers deployed in the same cloud before the deployment process of RAN network elements deployed in the same cloud. For example, S308 to S314 can be executed first, followed by S301 to S307. Correspondingly, cloud #1 is the cloud allocated by the cloud resource orchestration function to the RAN edge application server. When the same orchestration function of the cloud network requests the allocation of RAN network element resources from the cloud resource orchestration function through S303, it can carry the cloud identifier of cloud #1 in the resource allocation request.

[0323] As shown in Figure 9, when the available resources of the cloud do not meet the deployment requirements of the RAN edge application server, a communication method provided in this application embodiment may include the following steps:

[0324] S401: The deployment service consumer sends a deployment request to the cloud-network collaborative orchestration function. The second deployment request can be used to request the deployment of the RAN edge application server.

[0325] S401 can be referred to in the description of S208, and will not be repeated here.

[0326] S402: The cloud-network collaborative orchestration function determines the cloud resource orchestration to be executed based on the deployment request.

[0327] S402 can be referred to in the description of S209, and will not be repeated here.

[0328] S403: The cloud-network collaborative orchestration function sends a resource allocation request to the cloud resource orchestration function to request the allocation of cloud resources for the RAN edge application server.

[0329] The resource allocation request may include the cloud identifier of cloud #1. For example, cloud #1 is a cloud that serves RAN network elements deployed in the same cloud as the RAN edge application server. The method for determining cloud #1 can refer to the method for determining cloud #1 in the process of Figure 7, or it can refer to the method for determining cloud #1 in the process of Figure 8, and is not specifically limited.

[0330] In addition, the resource allocation request may carry resource requirement information for the RAN edge application server. Furthermore, as described in S210, the resource allocation request may also include at least one of the following: the software image of the RAN edge application server, task description, and type information.

[0331] S404: The cloud resource orchestration function determines, based on the resource requirements of the RAN edge application server and the resource status information of cloud #1, that the available resources of cloud #1 do not meet the resource requirements of the RAN edge application server.

[0332] For example, in S404, the cloud resource orchestration function can determine that the available resources of cloud #1 are less than the resource size required by the RAN edge application server, and therefore determine that the available resources of cloud #1 do not meet the resource requirements of the RAN edge application server.

[0333] S405: The cloud resource orchestration function item, Cloud-Network Collaborative Orchestration Function, sends a cloud resource allocation response, which may include the cloud identifier of Cloud #1 and a resource quantity difference, indicating that the available resources for Cloud #1 are insufficient. This resource quantity difference is the difference between the available resources of Cloud #1 and the resource quantity required by the RAN edge application server.

[0334] Optionally, the cloud resource allocation response may also include one or more of the following: the identifier of the occupied resource in cloud #1, the computing power type, computing power, storage type, storage amount, computing latency, the identifier of the task corresponding to the occupied resource, or the storage method information of the task corresponding to the occupied resource.

[0335] This cloud resource allocation response can serve as an example of a second indication message.

[0336] S406: The cloud-network collaborative orchestration function sends a request message to the configuration function to request information about the object of the cloud #1 service.

[0337] The request information may include the cloud identifier for cloud #1.

[0338] Specifically, this request information can be used to request information about the RAN network elements of the Cloud #1 service.

[0339] This request information can serve as an example of a second request information.

[0340] In S406, the cloud-network collaborative orchestration function can send this request information based on the cloud identifier and resource quantity difference of the received cloud #1.

[0341] S407: Configure the cloud-network collaborative orchestration function to send information about the RAN network elements of the cloud #1 service.

[0342] The information of the RAN network elements in Cloud #1 includes the configuration information of the RAN network elements in Cloud #1 and / or the resource information occupied by the RAN network elements in Cloud #1.

[0343] S408: The cloud-network collaborative orchestration function determines to reduce the RAN network element's occupation of cloud #1 resources based on the resource quantity difference and RAN network element information.

[0344] For example, the configuration information of RAN network elements can indicate RAN network elements in a dormant state, and correspondingly, the cloud-network collaborative orchestration function can reduce the cloud resources occupied by that RAN network element. As another example, the cloud-network collaborative orchestration function can decide to adjust low-load RAN network elements to dormant mode to reduce the RAN network elements' consumption of cloud #1 resources.

[0345] S409: The cloud-network collaborative orchestration function sends updated configuration information and / or resource information of RAN network elements to the configuration function.

[0346] The updated configuration information can be used to reduce the RAN network element's demand for cloud resources by changing the RAN network element's configuration. For example, the updated configuration information can be used to adjust the RAN network element to hibernation mode. The updated resource information can be used to indicate the resources occupied by the RAN network element after reducing resource consumption.

[0347] Updated configuration and / or resource information can serve as an example of fourth instruction information.

[0348] S410: The cloud-network collaborative orchestration function sends a resource allocation transfer instruction to the cloud resource orchestration function to instruct RAN network elements to reduce their occupation of cloud #1 resources. The resource allocation transfer instruction can also be called a resource allocation transfer request or other names, without specific limitations.

[0349] The resource allocation transfer instruction may include the identifier of cloud #1, the identifier of the RAN network element whose resource occupation needs to be stopped, or the identifier of the RAN network element whose resource occupation needs to be stopped.

[0350] The resource allocation transfer instruction may also include a far edge instruction or other information representing the RAN edge application server, indicating that the resources in cloud #1 originally occupied by RAN network elements can be allocated to the RAN edge application server after the transfer.

[0351] Optionally, the resource allocation transfer instruction may also include the cloud identifier and / or resource identifier of the cloud where the resources are located after the RAN network element is transferred. That is, the cloud resources after the RAN network element is transferred can be determined by the same orchestration function of the cloud network. It can be understood that if it is only necessary to stop the resource occupation of the RAN network element, the cloud identifier and resource identifier of the transferred resources do not need to be indicated.

[0352] S411: After receiving the resource allocation transfer instruction, the cloud resource orchestration function reduces the resource consumption of RAN network elements and allocates resource #2 in cloud #1 to the RAN edge application server.

[0353] Specifically, the cloud resource orchestration function can stop or transfer the resources of RAN network elements according to the resource allocation transfer instruction, so that the available resources of cloud #1 can meet the resource requirements of the RAN edge application server, and allocate resources #2 from the available resources of cloud #1 to the RAN edge application server.

[0354] Resource allocation and transfer instructions can serve as an example of third-party instruction information.

[0355] S412: The cloud resource orchestration function item, cloud-network collaborative orchestration function, sends a resource allocation response, which includes indication information for resource #2.

[0356] S413: Cloud and network share the same orchestration function to store the configuration and resource information of the RAN edge application server.

[0357] S414: The cloud-network collaborative orchestration function sends configuration and resource information of the RAN edge application server to the configuration function.

[0358] In addition, the cloud-network collaborative orchestration function can also send deployment response information corresponding to the deployment request to the deployment service consumer to indicate that the RAN edge application server deployment is complete.

[0359] The above S412 to S414 can be referred to the explanations of S212 to S214 respectively, and will not be repeated here.

[0360] It is understandable that S401 to S414 in Figure 9 can serve as the deployment process for the RAN edge application server. Before S401, the deployment process for RAN network elements can also be executed. For example, the deployment process for RAN network elements can refer to S201 to S207 or S301 to S307.

[0361] It can also be understood that the process in Figure 9, which uses the deployment process of RAN network elements deployed in the same cloud before the deployment process of RAN edge application servers deployed in the same cloud, can be changed to the deployment process of RAN edge application servers deployed in the same cloud before the deployment process of RAN network elements deployed in the same cloud. For example, S401 to S414 can be executed first, followed by the deployment process of RAN network elements. Correspondingly, cloud #1 is the cloud allocated by the cloud resource orchestration function to the RAN edge application server. When the same orchestration function of the cloud network requests the allocation of RAN network element resources from the cloud resource orchestration function through the deployment process of RAN network elements, it can carry the cloud identifier of cloud #1 in the resource allocation request.

[0362] As shown in Figure 10, when the cloud resource orchestration function determines that the RAN network element and the RAN edge application server are deployed in the same cloud according to the far edge indication, the communication method provided in this application embodiment may include the following steps:

[0363] S501: The deployment service consumer sends a first deployment request to the cloud-network collaborative orchestration function. The first deployment request can be used to request the deployment of RAN network elements. The first deployment request includes a far-edge indication, which can be used to indicate that the RAN network element and the RAN edge application server are deployed in the same cloud.

[0364] In addition, referring to the description in S201, the first deployment request may also include the identifier of the RAN network element, the information of the PLMN to which the RAN network element belongs, the location information of the RAN network element, the network element type information of the RAN network element, the task description of the RAN network element, the software image of the RAN network element, and the resource requirement information of the RAN network element.

[0365] S501 can be referred to the description of S301, and will not be repeated here.

[0366] S502: The cloud-network collaborative orchestration function sends a resource allocation request to the cloud resource orchestration function to request the allocation of cloud resources for RAN network elements.

[0367] The resource allocation request may include a far edge indication, RAN element type information, RAN element task description, RAN element software image, and RAN element resource requirement information.

[0368] This can also be understood as the cloud-network collaborative orchestration function in S502 transmitting the first deployment request to the cloud resource orchestration function.

[0369] S503: The cloud resource orchestration function determines the execution of cloud resource orchestration based on resource allocation requests.

[0370] In S503, the cloud resource orchestration function can determine whether cloud resources need to be allocated to RAN network elements based on the identifier and / or network element type information of the RAN network elements, that is, whether cloud resource orchestration needs to be performed or cloud resource support is required.

[0371] S504: The cloud resource orchestration function determines resource #1 for RAN network element services.

[0372] S504 can determine resource #1 by referring to the description in method A2. For example, the cloud resource orchestration function can determine cloud #1 based on the resource requirement information of the RAN network element and the resource status information of at least one cloud, and determine resource #1 from the available resources of cloud #1.

[0373] Among them, Cloud #1 can be used as an example of the first cloud. That is, Cloud #1 can meet the resource requirements of RAN network elements.

[0374] Optionally, the cloud resource orchestration function can also determine the task identifiers of one or more tasks for an RNA network element based on the task description of the RAN network element. Each task can correspond to a cloud resource.

[0375] In addition, the cloud resource orchestration function can also run the software image of the RAN network element in resource #1.

[0376] S505: The cloud resource orchestration function item, cloud-network collaborative orchestration function, sends a resource allocation response, which includes indication information for resource #1.

[0377] For example, the indication information for resource #1 includes the identifier of cloud #1 and the identifier of resource #1.

[0378] Optionally, the resource allocation response may also include task identifiers for one or more tasks of the RNA network element.

[0379] S506: Cloud and network share the same orchestration function to store the configuration and resource information of RAN network elements.

[0380] The configuration information of a RAN network element includes at least one of the following: the RAN network element's identifier, the PLMN to which the RAN network element belongs, the RAN network element's location information, and the RAN network element's resource requirement information. The resource information of the RAN network element includes indication information for the first resource.

[0381] S507: The cloud-network collaborative orchestration function sends configuration and resource information of RAN network elements to the configuration function.

[0382] Correspondingly, the configuration function can configure RAN network elements based on configuration information and resource information.

[0383] In addition, the cloud-network collaborative orchestration function can also send deployment response information corresponding to the first deployment request to the deployment service consumer to indicate that the RAN network element deployment is complete.

[0384] S508: The deployment service consumer sends a second deployment request to the cloud-network collaborative orchestration function. This second deployment request can be used to request the deployment of a RAN edge application server. The second deployment request includes a far-edge indication, which can be used to indicate that the RAN network element and the RAN edge application server are deployed in the same cloud.

[0385] Additionally, referring to the description in S208, the second deployment request may include first instruction information, information about the PLMN to which the RAN edge application server belongs, location information of the RAN edge application server, task description of the RAN edge application server, software image of the RAN edge application server, and resource requirement information of the RAN edge application server.

[0386] This second deployment request can serve as an example of the first request information in S101.

[0387] S509: The cloud-network collaborative orchestration function sends a resource allocation request to the cloud resource orchestration function to request the allocation of cloud resources for the RAN edge application server.

[0388] The resource allocation request may include a far edge indication, a first indication information, a task description of the RAN edge application server, a software image of the RAN edge application server, and resource requirement information of the RAN edge application server.

[0389] This can also be understood as the cloud-network collaborative orchestration function in S509 transmitting a second deployment request to the cloud resource orchestration function.

[0390] The cloud resource orchestration function can determine whether the RAN edge application server and the RAN network elements deployed in S501 to S507 are co-deployed in the cloud based on the far edge indication received in S502 and S509.

[0391] S510: The cloud resource orchestration function determines the execution of cloud resource orchestration based on resource allocation requests.

[0392] In S510, the cloud resource orchestration function can determine whether cloud resources need to be allocated to the RAN edge application server based on the first instruction information and / or the software image of the RAN edge application server, that is, whether cloud resource orchestration needs to be performed or cloud resource support is required.

[0393] S511: The cloud resource orchestration function identifies resource #2 from cloud #1 as a service for the RAN edge application server.

[0394] For example, the process of determining resource #2 can be referred to S311, or S404 to S411, which will not be repeated here.

[0395] S512: The cloud resource orchestration function item, cloud-network collaborative orchestration function, sends a resource allocation response, which includes indication information for resource #2.

[0396] S513: Cloud and network share the same orchestration function to store the configuration and resource information of the RAN edge application server.

[0397] S514: The cloud-network collaborative orchestration function sends configuration and resource information of the RAN edge application server to the configuration function.

[0398] In addition, the cloud-network collaborative orchestration function can also send deployment response information corresponding to the second deployment request to the deployment service consumer to indicate that the RAN edge application server deployment is complete.

[0399] The above S512 to S514 can be referred to the explanations of S212 to S214 respectively, and will not be repeated here.

[0400] It is understandable that S501 to S507 in Figure 10 can serve as the deployment process for RAN network elements, while S508 to S514 can serve as the deployment process for RAN edge application servers deployed in the same cloud as the RAN network element. S501 to S507 and S508 to S514 can be considered two independent processes, meaning the RAN network element and the RAN edge application server can be deployed independently. Alternatively, S501 to S507 and S508 to S514 can be combined into a single process.

[0401] It can also be understood that the process in Figure 10, which uses the deployment process of RAN network elements deployed in the same cloud before the deployment process of RAN edge application servers deployed in the same cloud, can be changed to the deployment process of RAN edge application servers deployed in the same cloud before the deployment process of RAN network elements deployed in the same cloud. For example, S508 to S514 can be executed first, followed by S501 to S507. Correspondingly, cloud #1 is the cloud allocated by the cloud resource orchestration function to the RAN edge application server. When the same orchestration function of the cloud network requests the allocation of RAN network element resources from the cloud resource orchestration function through S503, it can carry the cloud identifier of cloud #1 in the resource allocation request.

[0402] It is understood that, in order to achieve the functions in the above embodiments, the communication device includes hardware structures and / or software modules corresponding to each function. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0403] Figures 11 and 12 are schematic diagrams of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of the first network device (or the first communication device) or the second network device (or the second communication device) in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. For example, the first session management network element can be a cloud-network collaborative orchestration function or a cloud resource orchestration function, and the second network device can be a cloud resource orchestration function. In the embodiments of this application, the communication device can be the first network device or the second network device, or it can be a module or component (such as a chip) in the first network device or the second network device. For example, the communication device can be used to implement the functions of the first network device or the second network device in the processes shown in Figures 6 to 10.

[0404] The communication device 1100 shown in Figure 11 includes a processing unit 1110 and a transceiver unit (or communication unit) 1120. The communication device 1100 is used to implement the functions of the first session management network element, the first network device, the second network device, or the access and mobility management function network element in the above method embodiments. The transceiver unit may include a sending unit and a receiving unit, used for sending and receiving, respectively.

[0405] Taking the process shown in Figure 6 as an example, when the communication device 1100 is used to implement the cloud-network collaborative orchestration function in the method embodiment shown in Figure 6, specifically, the transceiver unit 1120 can be used to receive the first request information; the processing unit 1110 can be used to determine the type information of the first object according to the first request information, and deploy the first object according to the type information.

[0406] For a more detailed description of the above-mentioned processing unit 1110 and transceiver unit 1120, please refer directly to the description of the process steps and related features in the above method embodiments, which will not be repeated here.

[0407] The communication device 1200 shown in Figure 12 includes a processor 1210 and an interface circuit 1220. The processor 1210 and the interface circuit 1220 are coupled to each other. It is understood that the interface circuit 1220 can be a transceiver or an input / output interface. Optionally, the communication device 1200 may also include a memory 1230 for storing instructions executed by the processor 1210, or storing input data required by the processor 1210 to execute instructions, or storing data generated after the processor 1210 executes instructions.

[0408] When the communication device 1200 is used to implement the above method embodiment, the processor 1210 is used to implement the function of the processing unit 1110, and the interface circuit 1220 is used to implement the function of the transceiver unit 1120.

[0409] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), microprocessors without interlocked piped stages architecture (MIPS), advanced instruction set computers (RISC) machines (ARM), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0410] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, compact disc read-only memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in a first session management network element (or a first communication device), a second session management network element (or a second communication device), or a policy control network element (or a third communication device). Alternatively, the processor and storage medium can exist as discrete components in the first session management network element (or the first communication device), the second session management network element (or the second communication device), or the policy control network element (or the third communication device).

[0411] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. A computer program is a set of instructions that directs each step of an action of an electronic computer or other device with message processing capabilities. It is typically written in a programming language and runs on a target architecture. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed, in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be volatile or non-volatile, or it can include both types of storage media.

[0412] Based on the same technical concept, embodiments of this application also provide a computer-readable storage medium, including a program or instructions, which, when run on a computer, cause the methods in the above method embodiments to be executed.

[0413] Based on the same technical concept, embodiments of this application also provide a computer program product, including instructions that, when run on a computer, cause the methods in the above method embodiments to be executed.

[0414] Based on the same technical concept, embodiments of this application also provide a communication system to implement the communication methods shown in Figures 6 to 10.

[0415] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0416] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0417] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects.

[0418] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0419] This application can be presented in terms of aspects, embodiments, or features surrounding a system that may include multiple devices, components, modules, etc. It should be understood and appreciated that various systems may include additional devices, components, modules, etc., and / or may not include all devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these solutions may also be used. Additionally, in the embodiments of this application, words such as "exemplarily," "for example," etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the term "example" is intended to present concepts in a concrete manner. In the embodiments of this application, "of," "corresponding / relevant," and "corresponding" may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.

[0420] In this application, "transmit (Tx / tx)" and "receive (Rx / rx)" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX. "Send information" can include direct transmission or indirect transmission through other communication devices, communication apparatuses, units, or modules. "Receive information from YY" can be understood as the source of the information being YY. "Receive information" can include direct reception from YY or indirect reception from YY through other communication devices, communication apparatuses, units, or modules. Furthermore, "transmit" can also be understood as the "output" of a chip interface, and "receive" can be understood as the "input" of a chip interface. In other words, "transmit" or "receive" can occur between devices, for example, between access network devices and terminals via an air interface. "Transmit" or "receive" can also occur within a device, for example, between components, modules, chips, software modules, or hardware modules within a device via a bus, wiring, or interface.

[0421] In this application, "for indicating" can include both direct and indirect indication. When describing "information" for indicating A, it can include whether the information directly indicates A or indirectly indicates A, but does not necessarily mean that the information carries A.

[0422] The information indicated by a given piece of information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also be indirectly indicated by indicating other information, where there is a relationship between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing the indication overhead to some extent. At the same time, common parts of various pieces of information can be identified and indicated uniformly to reduce the indication overhead caused by individually indicating the same information.

[0423] Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be repeated here. As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method; therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated.

[0424] The information to be instructed can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device.

[0425] "Preset," "predefined," or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including terminals and network devices), or by pre-defining them in a protocol. This application does not limit the specific implementation method. "Stored" can refer to storing in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separate installations, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

Claims

1. A communication method, characterized in that, Applied to the first network device, including: Receive a first request message, which is used to request the deployment of a first object; The type information of the first object is determined based on the first request information, and the type information is used to indicate that the first object is a radio access network (RAN) element or a RAN edge application server. Deploy the first object according to the type information.

2. The method as described in claim 1, characterized in that, The first request information includes the identifier of the RAN network element and / or network element type information. The network element type information is used to indicate whether the network element is a virtual network element or a physical network element, and the type information of the first object is used to indicate that the first object is a RAN network element.

3. The method as described in claim 1, characterized in that, The first request information includes first indication information and / or a software image of a RAN edge application server. The first indication information is used to indicate a RAN edge application server, and the type information of the first object is used to indicate that the first object is a RAN edge application server.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: A resource allocation request is sent to the second network device according to the type information. The resource allocation request is used to request resources from the first object. The resource allocation request includes the type information. The system receives indication information for a first resource from the second network device. The indication information for the first resource is used to indicate the first resource of the first cloud. The first resource serves the first object. The indication information for the first resource is obtained based on the resource allocation request.

5. The method as described in claim 4, characterized in that, The method further includes: Receive a cloud identifier and a second indication information from the second network device for the first cloud, wherein the second indication information is used to indicate that the remaining resources of the first cloud are less than the resource requirements of the first object. A third instruction message is sent to the second network device, the third instruction message being used to instruct the second object to reduce its occupancy of the first cloud, the first cloud also serving the second object.

6. The method as described in claim 5, characterized in that, The second indication information includes the difference between the remaining resources of the first cloud and the resource requirements of the first object.

7. The method as described in claim 6, characterized in that, The third indication information is specifically used to indicate the transfer of the task of the second object of the first cloud to the second resource. The third indication information includes the indication information of the second resource and the identifier of the task of the second object. The indication information of the second resource is used to indicate the second resource of the second cloud.

8. The method as described in any one of claims 5-7, characterized in that, The method further includes: Send a second request message to the third network device. The second request message is used to request information about the service object of the first cloud. The service object of the first cloud includes the second object. The second request message includes the cloud identifier of the first cloud. Receive information from the second object from the third network device; Send a fourth indication message to the third network device, the fourth indication message being used to indicate updating the resource information and / or configuration information of the second object.

9. The method according to any one of claims 4-8, characterized in that, The type information of the first object is used to indicate that the first object is a RAN edge application server, and the method further includes: Based on the configuration information of the first object and the configuration information of at least one RAN network element, a first RAN network element is determined, the first cloud serves the first RAN network element, and the resource allocation request includes the cloud identifier of the first cloud.

10. The method as described in claim 9, characterized in that, The configuration information includes one or more of the following: Information about the PLMN, including its location, network slices, and hardware devices.

11. The method according to any one of claims 4-10, characterized in that, The method further includes: A configuration request for the first object is sent to a third network device, the configuration request including indication information of the first resource.

12. The method as described in claim 11, characterized in that, The resource allocation request also includes a task description for the first object, and the method further includes: The configuration request for the first object receives an identifier of the task of the first object from the second network device. The identifier of the task of the first object is determined according to the task description. The configuration request for the first object also includes the identifier of the task of the first object.

13. The method according to any one of claims 1-12, characterized in that, The first request information includes a fifth indication information, which indicates that the first object and the third object are deployed in the same cloud, and that the resources serving the first object and the resources serving the third object belong to the same cloud.

14. The method as described in claim 13, characterized in that, The type information of the first object is used to indicate that the first object is a RAN network element, and the type information of the third object is used to indicate that the third object is an edge application server.

15. The method as described in claim 13 or 14, characterized in that, The method further includes: Send a first resource allocation request to the second network device. The first resource allocation request is used to request resources from the third object. The resource allocation request includes the type information of the first object. Receive indication information of a first resource from the second network device, the indication information of the first resource being used to indicate the first resource of the first cloud, the first resource serving the first object; Send a second resource allocation request to a second network device. The resource allocation request is used to request resources from the third object. The resource allocation request includes the cloud identifier of the first cloud. The second resource allocation request includes the type information of the third object. The system receives indication information from the second network device for a third resource, the indication information for the third resource being used to indicate a third resource of the first cloud, the third resource serving the third object.

16. A communication method, characterized in that, Applied to second network devices, including: Receive a resource allocation request from a first network device, the resource allocation request being used to request resources from the first object, the resource allocation request including the type information; Send indication information of a first resource to the first network device. The indication information of the first resource is used to indicate the first resource of the first cloud, and the first resource serves the first object.

17. The method as described in claim 16, characterized in that, The method further includes: Send the cloud identifier of the first cloud and the second indication information to the first network device. The second indication information is used to indicate that the remaining resources of the first cloud are less than the resource requirements of the first object. The system receives a third instruction from the first network device, the third instruction being used to instruct a reduction in the second object's occupancy of the first cloud, the first cloud also serving the second object.

18. The method as described in claim 17, characterized in that, The second indication information includes the difference between the remaining resources of the first cloud and the resource requirements of the first object.

19. The method as described in claim 18, characterized in that, The third indication information is specifically used to indicate the transfer of the task of the second object of the first cloud to the second resource. The third indication information includes the indication information of the second resource and the identifier of the task of the second object. The indication information of the second resource is used to indicate the second resource of the second cloud.

20. The method according to any one of claims 16-19, characterized in that, The resource allocation request also includes a task description for the first object, and the method further includes: The identifier of the task of the first object is sent to the first network device, and the identifier of the task of the first object is determined according to the task description.

21. A communication device, characterized in that, It includes units or modules for performing the method as described in any one of claims 1-15, or units or modules for performing the method as described in any one of claims 16-20.

22. A communication device, characterized in that, Includes a processor for executing computer programs or instructions to implement the method as described in any one of claims 1-15, or to implement the method as described in any one of claims 16-20.

23. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1-15, or the method as described in any one of claims 16-20.

24. A computer program product, characterized in that, When the computer program product is executed by a computer, the computer executes the method as described in any one of claims 1-15, or executes the method as described in any one of claims 16-20.

Images