Modeling method and apparatus for multi-element fusion and encapsulation

Abstract

This disclosure provides a multi-element fusion and encapsulation modeling method and apparatus, relating to the field of Internet technology. The specific steps are: standardizing the capabilities of resource objects to generate corresponding atomic capabilities; combining and encapsulating the atomic capabilities to determine molecular capabilities; combining and encapsulating the molecular capabilities based on their relationships to generate corresponding functional domains; and selecting the corresponding functional domains based on the functions required by the business scenario for combination and encapsulation to generate a scenario domain model. This disclosure, by modeling the capabilities of resource objects, achieves rapid integration of resources required by the business scenario, improving the efficiency of business processing.

Description

Technical Field

[0001] This disclosure relates to the field of Internet technology, and in particular to a modeling method and apparatus for multi-element fusion and encapsulation. Background Technology

[0002] In related technologies, existing resource object capability modeling involves uniformly modeling objects that provide business capabilities, such as network devices and network management systems, to achieve a unified description of information on various objects such as resources, network services, and services. Its target objects are mainly network resources in telecommunications operators.

[0003] However, it cannot meet the modeling requirements of multiple elements such as cloud, network, edge, terminal, data, intelligence, chain, and security under the current computing power network. It is limited to business design based on product dimensions and cannot meet the unified design requirements of overall solutions for external user parks, industries, etc., resulting in low efficiency in business processing. Summary of the Invention

[0004] This disclosure provides a multi-element fusion and encapsulation modeling method, apparatus, and system to at least address the problem of low efficiency in business processing in related technologies. The technical solution of this disclosure is as follows:

[0005] According to a first aspect of the present disclosure, a multi-element fusion and encapsulation modeling method is provided, comprising:

[0006] The capabilities of resource objects are standardized to generate corresponding atomic capabilities;

[0007] The molecular capabilities are determined by combining the atomic capabilities into the encapsulation.

[0008] The molecular capabilities are combined and encapsulated to generate corresponding functional domains;

[0009] Based on the functions required by the business scenario, select the corresponding functional domains and combine and encapsulate them to generate scenario domain models.

[0010] Optionally, the resource object is a device that provides network services, including at least one of the following: physical resources, logical resources, network element nodes, and service platforms.

[0011] Optionally, the atomic capability includes capability attributes and adaptation information, and the step of standardizing the capabilities of the resource object to generate the corresponding atomic capability specifically includes:

[0012] Configure the capability attributes of the atomic capabilities;

[0013] Configure the atomic capabilities to adapt information to resource objects.

[0014] Optionally, the ability attribute specifically includes at least one of the following:

[0015] Attribute values;

[0016] Attribute value type;

[0017] Is this field required?

[0018] Range of values;

[0019] Calculation rules.

[0020] Optionally, configuring the atomic capabilities to the adaptation information of each underlying infrastructure resource node specifically includes:

[0021] Determine the mapping relationship between the attributes of the resource object and the atomic capabilities;

[0022] Determine the applicable platform range for the attributes of the resource object on the atomic capability.

[0023] Optionally, the step of determining molecular capabilities based on the atomic capability combination encapsulation specifically includes:

[0024] Configure the capability tags, capability attributes, operational capabilities, and applicable scenarios of the molecular capabilities.

[0025] Optionally, the step of combining and encapsulating the molecules based on the correlation between their capabilities to generate corresponding functional domains specifically includes:

[0026] Configure the function label type and function label attributes of the function domain;

[0027] Configure the relationships between the molecular capabilities, and encapsulate them into functional domains based on the relationships, wherein the relationships include at least one of the following: dependency, inclusion, and association.

[0028] Optionally, the step of selecting and combining corresponding functional domains based on the functions required by the business scenario to generate a scenario domain model specifically includes:

[0029] Configure the scene topology, scene attributes, business metrics, and scene access parameters corresponding to the scene domain.

[0030] Optionally, the business metrics include: business parameters, technical parameters, and the mapping relationship between the business parameters and the technical parameters.

[0031] Optionally, the scenario opening parameters include at least one of the following: effective, published, online, updated, canceled, invalidated, and offline.

[0032] According to a second aspect of the present disclosure, a multi-element fusion encapsulation modeling apparatus is provided, comprising:

[0033] The first processing module is used to standardize the capabilities of resource objects to generate corresponding atomic capabilities;

[0034] The second processing module is used to determine molecular capabilities based on the atomic capability combination encapsulation;

[0035] The third processing module is used to combine and encapsulate the molecular capabilities according to the correlation between them to generate corresponding functional domains.

[0036] The modeling module is used to select the corresponding functional domains based on the functions required by the business scenario, combine and encapsulate them to generate scenario domain models.

[0037] According to a third aspect of the present disclosure, an electronic device is provided, comprising:

[0038] processor;

[0039] Memory used to store the processor's executable instructions;

[0040] The processor is configured to execute the instructions to implement the method as described in any one of the first aspects.

[0041] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein when instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the method as described in any one of the first aspects.

[0042] The technical solutions provided by the embodiments of this disclosure have at least the following beneficial effects:

[0043] The accumulation of core business resources. Through the four-layer resource object model proposed in this disclosure, the multi-element capabilities of computing network infrastructure can be quickly integrated and opened up, accelerating the accumulation of core operator resources and the monetization of capabilities.

[0044] The new business launch cycle is short, allowing for a first-mover advantage. Industry hotspots such as computing power networks are attracting attention from various operators and cloud service providers. This public offering can encapsulate network capabilities into product capabilities for front-end sales, enabling rapid product launches and allowing companies to seize hot markets and launch best-selling products ahead of other industries.

[0045] Resource efficiency is improved and costs are saved. This disclosure, through the design, deployment, and opening of capabilities, enables effective management of operators' resources, especially computing resources. By designing scenarios from the perspective of global resource balance, resource utilization efficiency can be improved to a certain extent, thereby optimizing computing power utilization and saving costs.

[0046] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0047] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0048] Figure 1 This is a flowchart illustrating a multi-element fusion encapsulation modeling method according to an exemplary embodiment.

[0049] Figure 2 This is a structural diagram illustrating a multi-element fusion encapsulation modeling according to an exemplary embodiment.

[0050] Figure 3 This is an atomic domain modeling design diagram illustrated according to an exemplary embodiment.

[0051] Figure 4 This is a molecular domain modeling design diagram illustrated according to an exemplary embodiment.

[0052] Figure 5 This is a functional domain modeling design diagram illustrated according to an exemplary embodiment.

[0053] Figure 6 This is a scene domain modeling design diagram illustrated according to an exemplary embodiment.

[0054] Figure 7 This is a block diagram illustrating a multi-element fusion encapsulation modeling apparatus according to an exemplary embodiment.

[0055] Figure 8 This is a block diagram illustrating an apparatus according to an exemplary embodiment.

[0056] Figure 9 This is a block diagram illustrating an apparatus according to an exemplary embodiment. Detailed Implementation

[0057] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0058] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0059] It should be noted that the user information involved in this disclosure (including but not limited to user device information, user personal information, etc.) is all information authorized by the user or fully authorized by all parties.

[0060] In one possible embodiment, resource object capability modeling involves uniformly modeling objects that provide service capabilities, such as network devices and network management systems, to achieve a unified description of information on various objects such as resources, network services, and services. Its target objects are mainly network resources in telecommunications operators.

[0061] Specifically, the resource object capability modeling of existing technical solutions is mainly designed and managed according to a three-layer object model:

[0062] The first layer consists of resource objects, primarily referring to resource objects that provide network services. This involves the classification of physical resources (network devices, lines), logical resources (IP addresses, ports, links), network elements (UDMs, PCFs), and service platforms within the network. The design primarily focuses on attributes, directories, topologies, and APIs.

[0063] The second layer consists of network service objects, which are assembled from resource objects and mainly include network nodes and network connections, such as backbone networks, core networks, and other related networks.

[0064] The third layer consists of business objects, which are assembled from network service objects. This mainly refers to the business layer combining various network resources according to the customer's business scenarios, including one or more complete network models, such as 5G slicing services and cloud private network services.

[0065] However, the three-layer object modeling technology in the above embodiments can assemble resource objects into network service objects and network service objects into business objects. But since it mainly targets network device resources, it cannot meet the modeling requirements of multiple elements such as cloud, network, edge, terminal, data, intelligence, chain, and security under the current computing power network. It is limited to business design based on product dimensions and cannot meet the current demand for unified design of overall solutions for external user parks, industries, etc. It is mainly promoted and used in a single domain and cannot be realized in the integration of cross-domain products or solutions and government and enterprise empowerment.

[0066] Figure 1 This is a flowchart illustrating a multi-element fusion and encapsulation modeling method according to an exemplary embodiment, such as... Figure 1 As shown, the method includes the following steps.

[0067] Step 101: Standardize the capabilities of the resource object to generate corresponding atomic capabilities;

[0068] Step 102: Determine molecular capabilities by combining the atomic capabilities into the encapsulation.

[0069] Step 103: Combine and encapsulate according to the correlation between the molecular capabilities to generate corresponding functional domains;

[0070] Step 104: Select the corresponding functional domains according to the functions required by the business scenario, combine and encapsulate them to generate scenario domain modeling.

[0071] In this embodiment, atomic capability is the smallest management unit of the multi-element fusion modeling method. It can align the capabilities of the underlying computing power, network, and capability nodes in the access infrastructure layer according to the needs of computing network services, forming a standardized resource capability encapsulation. Through atomic capabilities, they can be combined and encapsulated into various molecular capabilities.

[0072] Molecular capabilities are formed by combining and encapsulating atomic capability elements under the same directory. They are combined and encapsulated on demand using a unified resource object structure element. Therefore, there are multiple combination methods for different resource specification requirements. At the same time, the modeling adopts an applicable scenario management method, which can manage and match the various specifications of molecular capabilities that have been designed according to the applicable scenario.

[0073] A functional domain refers to a set of capabilities that share common terminal network connectivity requirements and metrics. Functional domain design requires encapsulation based on the principle of aggregating capabilities for similar scenarios, such as AI training domains, AI recognition domains, storage domains, and rendering domains. After encapsulating individual capabilities, these capabilities can be combined and arranged according to actual business scenarios, and the interdependencies and relationships between them can be set, thus forming a functional domain.

[0074] A scenario domain is a capability that models applications based on their usage requirements. It is a holistic application scenario solution that combines elements such as cloud, network, edge, terminal, data, and intelligence. The design of a scenario domain is formed by multiple types of functional domains. Each type of functional domain corresponds to common network connectivity requirements. Each associated functional domain can be used repeatedly in different scenario domains. Therefore, based on the sub-capabilities and functional domains, the application scenarios of the scenario domain can be analyzed, and scenario-based solutions that meet the needs of government and enterprise front-ends can be quickly encapsulated by combining and orchestrating them according to business requirements.

[0075] Figure 2 This is a structural diagram illustrating a multi-element fusion encapsulation modeling according to an exemplary embodiment. For example... Figure 2 As shown, this embodiment not only designs business models based on operator network resources, but also expands the scope to include multiple resource elements such as cloud, network, edge, terminal, data, intelligence, chain, and security. The resource capability modeling method follows a design approach combining component factors and capability types, significantly reducing the professional threshold for designers during business scenario encapsulation design and making it easier to understand the meaning of design elements. Furthermore, after completing the scenario encapsulation design, the ease of understanding and simplified processing requirements of government and enterprise front-ends are fully considered. Key business parameters are mapped and transformed. Once the business scenario template is released to the government and enterprise front-end, it supports the rapid design of product packages that can be sold to external customers, truly achieving end-to-end business integration.

[0076] Figure 3 This is an atomic domain modeling design diagram illustrated according to an exemplary embodiment. For example... Figure 3 As shown, optionally, the resource object is a device that provides network services, including at least one of the following: physical resources, logical resources, network element nodes, and service platforms.

[0077] Optionally, the atomic capability includes capability attributes and adaptation information, and the step of standardizing the capabilities of the resource object to generate the corresponding atomic capability specifically includes:

[0078] Configure the capability attributes of the atomic capabilities;

[0079] Configure the atomic capabilities to adapt information to resource objects.

[0080] Optionally, the capability attribute specifically includes at least one of the following: attribute value; attribute value type; whether it is required; value range; calculation rule.

[0081] In one possible embodiment, the attribute value type includes: fixed, enumerated, and range. For example, the fixed value is 2, the enumerated value is a predefined value such as A, B, or C, and the range value is 100 to 200.

[0082] In one possible embodiment, the value range is 100 to 200.

[0083] In one possible embodiment, the calculation rule is a function transformation: sum = A1 + A2.

[0084] Optionally, configuring the atomic capabilities to the adaptation information of each underlying infrastructure resource node specifically includes:

[0085] Determine the mapping relationship between the attributes of the resource object and the atomic capabilities;

[0086] Determine the applicable platform range for the attributes of the resource object on the atomic capability.

[0087] In this embodiment, the mapping between the attributes of resource objects and the atomic capability attributes is shown. The attributes of resource objects correspond to the attribute columns in the table below. The mapping can establish a relationship between atomic capabilities and the attributes of resource objects, such as manufacturer (atomic capability attribute) and vendor (original attribute).

[0088] The applicable platform scope of a resource object's attributes for atomic capabilities. For example, a 1C CPU atomic capability is applicable to Huawei Cloud Platform and VMware, but not to ZTE Cloud.

[0089] Table 1 shows an example of atomic capability modeling in one possible implementation, using a cloud host as an example.

[0090]

[0091]

[0092] Table 1

[0093] Optionally, the step of determining molecular capabilities based on the atomic capability combination encapsulation specifically includes:

[0094] Configure the capability tags, capability attributes, operational capabilities, and applicable scenarios of the molecular capabilities.

[0095] Figure 4 This is a molecular domain modeling design diagram illustrated according to an exemplary embodiment. For example... Figure 4 As shown, the modeling design of molecular capabilities should include:

[0096] (1) Configuration of molecular capabilities:

[0097] Tag type

[0098] Tag attributes

[0099] (2) The ability attributes possessed by the ability to configure molecules:

[0100] Attribute values

[0101] Attribute value type (fixed, enumeration, range)

[0102] Is this field required?

[0103] Range of values

[0104] Calculation rules

[0105] (3) The ability to manipulate molecules:

[0106] Add operation

[0107] Change operation

[0108] Deletion operation

[0109] (3) Applicable scenarios for configuring molecular capabilities:

[0110] Scenario types, such as memory-optimized, general-purpose computing, GPU-accelerated, and ultra-high I / O computing scenarios.

[0111] Scene attributes are the resource attributes corresponding to each scene, such as memory-optimized CPU, memory, architecture, clock speed, operating system, video memory, etc. Each of these is a scene attribute.

[0112] The scope of the scenario refers to the reference range in which the scenario is applicable. For example, general computing is suitable for scenarios with low to medium performance and ordinary computing that do not have high requirements for CPU.

[0113] Taking cloud servers as an example, cloud server molecular capabilities can be encapsulated according to different resource specification requirements to suit different business application scenarios. Table 2 is an example of molecular capability modeling in one possible implementation.

[0114]

[0115]

[0116] Table 2

[0117] Optionally, the step of combining and encapsulating the molecules based on the correlation between their capabilities to generate corresponding functional domains specifically includes:

[0118] Configure the function label type and function label attributes of the function domain;

[0119] Configure the relationships between the molecular capabilities, and encapsulate them into functional domains based on the relationships, wherein the relationships include at least one of the following: dependency, inclusion, and association.

[0120] Figure 5 This is a functional domain modeling design diagram illustrated according to an exemplary embodiment.

[0121] In this embodiment, the relationship type refers to the relationship between the capabilities of components within a functional domain. For example, the facial recognition functional domain includes scientific computing cloud servers, image computing cloud servers, object storage, VPC, and facial recognition AI. Relationships are established such that facial recognition AI + scientific computing cloud server + image computing cloud server + VPC must be bound together; otherwise, it cannot be activated. This includes inclusion and association relationships. A cloud server includes a VPC, and facial recognition AI is associated with both scientific computing cloud servers and image computing cloud servers. Dependency relationships typically involve the network depending on the cloud VPC.

[0122] Business metrics are functions that transform user computing tasks into computing power capabilities. Therefore, business metric rules need to be managed during the computing power domain modeling process. They consist of three main components: metric indicators, basic computing power, and metric rules.

[0123] Metrics: Classified by business capabilities, such as CPU computing power, GPU computing power, object storage capacity, etc., are all metrics.

[0124] Basic computing power: refers to the basic computing power of computing resources and equipment, such as the basic computing power of a cloud server with 4C8G Intel processors being 1.2 FLOPS;

[0125] Measurement rules: These refer to the rules for converting user business requirements into specific metric values. For example, the GPU computing power value for image recognition AI needs to be calculated using the recognition scale, response time, and basic computing power to determine the GPU computing power value required by the user.

[0126] Table 3 shows an example of functional domain modeling in one possible embodiment, taking the image recognition functional domain as an example.

[0127]

[0128] Table 3

[0129] Optionally, the step of selecting and combining corresponding functional domains based on the functions required by the business scenario to generate a scenario domain model specifically includes:

[0130] Configure the scene topology, scene attributes, business metrics, and scene access parameters corresponding to the scene domain.

[0131] Figure 6 This is a scene domain modeling design diagram illustrated according to an exemplary embodiment. For example... Figure 6 As shown, the modeling design of the scenario domain should include the following: Parameters used by the BSS (Business Support System) are defined as business parameters, i.e., those that are understandable to users, such as the scale of face recognition access and the number of cameras. Parameters used by the network side are defined as technical parameters, i.e., those that are understandable to the network, such as the concurrency scale (scale of face recognition access) and the number of video access channels (corresponding to the number of cameras). The business parameters and technical parameters need to be associated, i.e., mapped.

[0132] Optionally, the business metrics include: business parameters, technical parameters, and the mapping relationship between the business parameters and the technical parameters.

[0133] Optionally, the scenario opening parameters include at least one of the following: effective, published, online, updated, canceled, invalidated, and offline.

[0134] Table 4 shows an example of scene domain modeling in one possible implementation, taking an industrial visual inspection scenario as an example.

[0135]

[0136] Table 4

[0137] This embodiment has the following beneficial effects:

[0138] (1) More comprehensive and universal: The modeling objects disclosed herein involve multiple elements such as cloud, network, edge, terminal, data, intelligence, security, and chain, which are more in line with the current business needs and status quo of multiple elements participating in the current computing power network. They can better solve the overall solution problem and are more comprehensive than the modeling objects in the third article.

[0139] (2) Easier to understand: The modeling approach disclosed here adopts the approach of resource object components + capability type, which manages and designs from the perspective of resource composition. This approach is easier for designers to understand and can effectively reduce the professional threshold for users.

[0140] (3) Less workload: The modeling method disclosed herein encapsulates and models objects layer by layer from the bottom layer into four layers: atomic capability, molecular capability, functional domain and scene domain. The reusability of the capability is maximized, and the scene domain can be opened to government and enterprise front-ends, which can accelerate the loading and online efficiency of products and the efficiency of business acceptance, and complete more design and sales work with less workload.

[0141] (4) Accumulation of core operator resources. The four-layer resource object model proposed in this proposal can quickly integrate and open up the multi-element capabilities of computing network infrastructure, thereby accelerating the accumulation of core operator resources and the monetization of capabilities.

[0142] (5) Short new business launch cycle to seize the initiative. In hot industries such as computing networks, various operators and cloud service providers want to get a share of the pie. This proposal can encapsulate network capabilities into product capabilities that are sold to the front end, allowing the front end to quickly launch products, thereby seizing the hot market and launching best-selling products one step ahead of other industries.

[0143] (6) Improved resource efficiency and cost savings. This proposal effectively manages the operator's resources, especially computing resources, through the design, deployment, and opening of capabilities. By designing scenarios from the perspective of global resource balance, resource utilization efficiency can be improved to a certain extent, thereby optimizing the utilization rate of computing power and saving costs.

[0144] Figure 7 This is a block diagram illustrating a multi-element fusion encapsulation modeling apparatus according to an exemplary embodiment. (Refer to...) Figure 7 The device 700 includes:

[0145] The first processing module 710 is used to standardize the capabilities of resource objects to generate corresponding atomic capabilities;

[0146] The second processing module 720 is used to determine molecular capabilities based on the atomic capability combination packaging;

[0147] The third processing module 730 is used to combine and encapsulate the molecular capabilities according to the correlation between them to generate corresponding functional domains.

[0148] Modeling module 740 is used to select the corresponding functional domains according to the functions required by the business scenario, combine and encapsulate them to generate scenario domain models.

[0149] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0150] Figure 8 This is a block diagram illustrating an apparatus 800 according to an exemplary embodiment. For example, apparatus 800 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0151] Reference Figure 8 The device 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input / output (I / O) interface 812, a sensor component 814, and a communication component 816.

[0152] Processing component 802 typically controls the overall operation of device 800, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 802 may include one or more modules to facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

[0153] Memory 804 is configured to store various types of data to support the operation of device 800. Examples of this data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, etc. Memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0154] Power supply component 806 provides power to various components of device 800. Power supply component 806 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to device 800.

[0155] Multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 808 includes a front-facing camera and / or a rear-facing camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0156] Audio component 810 is configured to output and / or input audio signals. For example, audio component 810 includes a microphone (MIC) configured to receive external audio signals when device 800 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 804 or transmitted via communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

[0157] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0158] Sensor assembly 814 includes one or more sensors for providing status assessments of various aspects of device 800. For example, sensor assembly 814 may detect the on / off state of device 800, the relative positioning of components such as the display and keypad of device 800, changes in the position of device 800 or a component of device 800, the presence or absence of user contact with device 800, the orientation or acceleration / deceleration of device 800, and temperature changes of device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 814 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0159] Communication component 816 is configured to facilitate wired or wireless communication between device 800 and other devices. Device 800 can access wireless networks based on communication standards, such as WiFi, carrier networks (such as 2G, 3G, 4G, or 5G), or combinations thereof. In one exemplary embodiment, communication component 816 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 816 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0160] In an exemplary embodiment, the apparatus 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0161] In an exemplary embodiment, a storage medium including instructions is also provided, such as a memory 804 including instructions, which can be executed by a processor 820 of the device 800 to perform the above method. Optionally, the storage medium may be a non-transitory computer-readable storage medium, such as a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device.

[0162] Figure 9This is a block diagram illustrating an apparatus 900 according to an exemplary embodiment. For example, apparatus 900 may be provided as a server. (Refer to...) Figure 9 The apparatus 900 includes a processing component 922, which further includes one or more processors, and memory resources represented by memory 932 for storing instructions, such as application programs, that can be executed by the processing component 922. The application programs stored in memory 932 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 922 is configured to execute instructions to perform the methods described above.

[0163] The device 900 may also include a power supply component 926 configured to perform power management of the device 900, a wired or wireless network interface 950 configured to connect the device 900 to a network, and an input / output (I / O) interface 958. The device 900 can operate on an operating system stored in memory 932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or similar.

[0164] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0165] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A multi-element fusion and encapsulation modeling method, characterized in that, include: The capabilities of resource objects are standardized to generate corresponding atomic capabilities; The molecular capabilities are determined by combining the atomic capabilities into the encapsulation. The molecular capabilities are combined and encapsulated to generate corresponding functional domains; Based on the functions required by the business scenario, select the corresponding functional domains and combine and encapsulate them to generate scenario domain models; The process of determining molecular capabilities based on the combination of atomic capabilities specifically includes: Configure the capability tags, capability attributes, operational capabilities, and applicable scenarios of the molecules; The step of combining and encapsulating molecules based on the correlations between their capabilities to generate corresponding functional domains specifically includes: Configure the function label type and function label attributes of the function domain; Configure the relationships between the molecular capabilities, and encapsulate them into functional domains based on the relationships, wherein the relationships include at least one of the following: dependency, inclusion, and association.

2. The method according to claim 1, characterized in that, The resource object is a device that provides network services, including at least one of the following: physical resources, logical resources, network element nodes, and service platforms.

3. The method according to claim 1, characterized in that, The atomic capability includes capability attributes and adaptation information. The step of standardizing the capabilities of the resource object to generate the corresponding atomic capability specifically includes: Configure the capability attributes of the atomic capabilities; Configure the atomic capabilities to adapt information to resource objects.

4. The method according to claim 3, characterized in that, The ability attribute specifically includes at least one of the following: Attribute values; Attribute value type; Is this field required? Range of values; Calculation rules.

5. The method according to claim 4, characterized in that, The specific information for configuring the atomic capabilities to adapt to resource objects includes: Determine the mapping relationship between the attributes of the resource object and the atomic capabilities; Determine the applicable platform range for the attributes of the resource object on the atomic capability.

6. The method according to claim 1, characterized in that, The step of selecting and combining corresponding functional domains based on the functions required by the business scenario to generate scenario domain modeling specifically includes: Configure the scene topology, scene attributes, business metrics, and scene access parameters corresponding to the scene domain.

7. The method according to claim 6, characterized in that, The business metrics include: business parameters, technical parameters, and the mapping relationship between the business parameters and the technical parameters.

8. The method according to claim 6, characterized in that, The scenario open parameters include at least one of the following: effective, published, online, updated, canceled, invalidated, and offline.

9. A multi-element fusion and encapsulation modeling device, characterized in that, include: The first processing module is used to standardize the capabilities of resource objects to generate corresponding atomic capabilities; The second processing module is used to determine molecular capabilities based on the atomic capability combination encapsulation; The third processing module is used to combine and encapsulate the molecular capabilities according to the correlation between them to generate corresponding functional domains. The modeling module is used to select the corresponding functional domains based on the functions required by the business scenario, combine and encapsulate them to generate scenario domain models. The second processing module is specifically used for: Configure the capability tags, capability attributes, operational capabilities, and applicable scenarios of the molecules; The third processing module is specifically used for: Configure the function label type and function label attributes of the function domain; Configure the relationships between the molecular capabilities, and encapsulate them into functional domains based on the relationships, wherein the relationships include at least one of the following: dependency, inclusion, and association.

10. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, wherein instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method as described in any one of claims 1 to 8.

Images