Service directory implementation apparatus and method

Abstract

The application provides a service directory implementation device and method, which can improve the efficiency of managing services and resources. The service directory implementation device comprises: an RES design module, which is used for defining an RES object, the RES object representing the classification of physical resources and logical resources in an operator network, and the RES object being a resource object; an RFS design module, which is in communication connection with the RES design module, and is used for defining an RFS object, the RFS object representing a resource-oriented service, and the RFS object being composed of at least one RES object; the RFS representing network capability; and a CFS design module, which is in communication connection with the RFS design module, and is used for defining a CFS object, the CFS object representing a customer-oriented service, and the CFS object being composed of at least one RFS object.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a service catalog implementation apparatus and method. Background Technology

[0002] With the continuous emergence of new technologies in the communications field, network operators are also upgrading their network equipment, initiating business transformation, and providing dynamic services to users. Network operators need to upgrade their service provisioning and maintenance support capabilities, with service orchestration systems being a core module. Service orchestration systems enable rapid service orchestration and deployment. Service catalogs are an important functional module within the orchestration system; however, service orchestration systems cannot fully adapt to the needs of business scenarios in network operations, or their performance may be poor in certain specific scenarios, resulting in inefficient management of services and resources. Summary of the Invention

[0003] To address the aforementioned technical problems, this invention is proposed. Embodiments of this invention provide a service catalog implementation apparatus and method, which can improve the efficiency of managing services and resources.

[0004] According to one aspect of the present invention, a service catalog implementation apparatus is provided, comprising: a RES design module, wherein the RES design module is used to define RES objects, wherein the RES objects represent the abstract classification of physical and logical resources in an operator's network, and the RES objects are resource objects; an RFS design module, wherein the RFS design module is communicatively connected to the RES design module, wherein the RFS design module is used to define RFS objects, wherein the RFS objects represent resource-oriented services, and the RFS objects are composed of at least one RES object; RFS represents network capabilities; and a CFS design module, wherein the CFS design module is communicatively connected to the RFS design module, wherein the CFS design module is used to define CFS objects, wherein the CFS objects represent customer-oriented services, and the CFS objects are composed of at least one RFS object; wherein the functions and services of the RES design module, the RFS design module, and the CFS design module are decoupled, and the specifications of the service catalog are defined based on the RES design module, the RFS design module, and the CFS design module.

[0005] In one embodiment, the RES design module includes: a resource object management unit, which manages RES objects, including adding, deleting, modifying, and querying RES objects; and a resource object design unit, which describes the RES objects to define their attribute values.

[0006] In one embodiment, the RFS design module includes: an RFS object management unit, which manages RFS objects, including adding, deleting, modifying, and querying RFS objects; and an RFS object design unit, which describes RFS objects to define their attribute values, resource object members, rules, actions, and associated APIs.

[0007] In one embodiment, the RFS object design unit includes: an RFS object attribute value subunit, which is used to maintain the specification information of the RFS object, including adding, deleting, modifying, querying, enabling, and disabling attribute values; an RFS resource object member function unit, which is used to maintain the RES resource objects contained in the RFS, to add and delete defined RES resource objects; and an RFS rule function unit, which is used to maintain the dependencies between RFS objects.

[0008] In one embodiment, the RFS object design unit includes: an RFS action function unit, which is used to maintain all actions supported by the RFS object; and an API function unit, which is used to maintain API information corresponding to the implementation of RFS actions, and to add and delete API binding relationships.

[0009] In one embodiment, the CFS design module includes: a CFS object management unit, which manages CFS objects, including adding, deleting, modifying, and querying CFS objects; and a CFS object design unit, which describes CFS objects to define their attribute values, RFS members, rules, actions, associated processes, and business models.

[0010] In one embodiment, the CFS object design unit includes: a CFS object attribute value subunit, which is used to maintain the specification information of the CFS object, including adding, deleting, modifying, querying, enabling, and disabling attribute values; a CFS member function subunit, which is used to maintain the RFS objects contained in the CFS, to add and delete defined RFS objects; and a CFS rule function unit, which is used to add and delete dependencies between CFS objects.

[0011] In one embodiment, the CFS object design unit includes: a CFS action function unit, which is used to add and delete actions supported by the CFS object; a CFS process function unit, which is used to add and delete process information corresponding to CFS actions; and a CFS business model function unit, which is used to maintain the business model corresponding to the CFS.

[0012] In one embodiment, the service catalog implementation apparatus further includes a synchronization module, which is used to synchronize the defined CFS to the customer relationship management system, so that the customer relationship management system defines products based on the defined CFS, combined with market demand factors and pricing strategy factors.

[0013] According to another aspect of the present invention, a service catalog implementation method is provided, applicable to the service catalog implementation apparatus described in any of the above embodiments. The service catalog implementation method includes: abstracting and classifying physical resources and logical resources in an operator network to obtain RES objects, and defining RES objects through a RES design module; integrating RES objects into network capabilities and defining RFS objects through an RFS design module; integrating network capabilities into customer-oriented services and defining CFS objects through a CFS design module.

[0014] The service catalog implementation apparatus and method provided by this invention designs and implements a service catalog based on the CFS / RFS specification for defining and configuring services. It includes basic service information, attribute parameters, dependencies, and other information. It can support operators to quickly define RFS and CFS based on the network and can better distinguish between customer-oriented services (CFS) and resource-oriented services (RFS). By distinguishing between customer-oriented services and resource-oriented services, it is possible to better understand and manage the characteristics, delivery processes, and performance indicators of various services, thereby improving efficiency and reducing costs. Attached Figure Description

[0015] The above and other objects, features, and advantages of the present invention will become more apparent from the more detailed description of the embodiments of the invention in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of the invention and form part of the specification. They are used together with the embodiments of the invention to explain the invention and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same parts or steps.

[0016] Figure 1 This is a schematic diagram of the structure of a service catalog implementation device provided in an exemplary embodiment of the present invention.

[0017] Figure 2 This is a schematic diagram of the structure of a service catalog implementation device provided in another exemplary embodiment of the present invention.

[0018] Figure 3 This is a flowchart illustrating a service catalog implementation method provided in an exemplary embodiment of the present invention.

[0019] Explanation of reference numerals in the attached drawings: 1. Service catalog implementation device; 11. RES design module; 111. Resource object management unit; 112. Resource object design unit; 12. RFS design module; 121. RFS object management unit; 122. RFS object design unit; 1221. RFS object attribute value subunit; 1222. RFS resource object member function unit; 1223. RFS rule function unit; 1224. RFS action function unit; 1225. API function unit; 13. CFS design module; 131. CFS object management unit; 132. CFS object design unit; 1321. CFS object attribute value subunit; 1322. CFS member function subunit; 1323. CFS rule function unit; 1324. CFS action function unit; 1325. CFS process function unit; 1326. CFS business model function unit; 14. Synchronization module. Detailed Implementation

[0020] Hereinafter, exemplary embodiments according to the present invention will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments of the present invention. It should be understood that the present invention is not limited to the exemplary embodiments described herein.

[0021] This invention relates to service orchestrators, which cater to various types of services in the communications field, including broadband, voice, television, leased lines, and cloud services. Service orchestrators primarily define, organize, and coordinate the interactions and execution order between services to achieve specific business processes or workflows. Service orchestrators typically have the following functions: 1. Service definition and configuration: Allowing users to define and configure services, their parameters, dependencies, and execution conditions; 2. Process design and modeling: Providing tools and interfaces that enable users to design and model the processes, sequences, and logic of service execution; 3. Automated execution: Automatically executing predefined service processes and handling exceptions as needed; 4. Monitoring and tracing: Monitoring the status and performance of service execution and providing tracing and logging functions for subsequent analysis and optimization; 5. Flexibility and scalability: Possessing flexibility and scalability to adapt to different business needs and changing environments.

[0022] This invention implements a service catalog based on CFS / RFS, a business specification in the telecommunications field proposed by the Telecommunications Management Forum (TMF). The SID system proposed by TMF includes three concepts: Product, Service, and Resource. Product refers to the features, functions, and operational capabilities of the smallest saleable unit (SMU) provided to customers. The network attributes and network services involved in the product are obtained through the service layer. Service is divided into two layers, including CFS and RFS. CFS: Customer-facing services, various services that customers can perceive and use, assembled from network-facing services, including point-to-point, point-to-network, telephone calls, internet connectivity, SMS sending, etc. These services directly affect the end-user experience and satisfaction. RFS: Services for service providers' internal or other network resources, network communication capabilities provided by various communication networks, assembled from atomic capabilities provided by resources, and can also be directly leased to customers; RFS is typically used to manage and optimize network resources, such as configuration, capacity, and routing. These services support the infrastructure and resources required to provide CFS. RES: Resources are a classification of entities involved in the network, including physical resources (network devices, lines), logical resources (IP addresses, ports, links), network elements (UDM, PCF), and service platforms. Among these, "product" refers to CRM (Customer Relationship Management) functionality, which is not included in the service orchestrator, which primarily focuses on service layer orchestration. This invention designs and implements a service catalog based on the CFS / RFS specification for defining and configuring services. It includes basic service information, attribute parameters, dependencies, etc., enabling operators to quickly define RFS and CFS based on the network, better manage services and resources, improve efficiency, reduce costs, and enhance customer experience and market competitiveness.

[0023] Figure 1 This is a schematic diagram of the structure of a service catalog implementation device provided in an exemplary embodiment of the present invention, as shown below. Figure 1As shown, the service catalog implementation device 1 includes: a RES design module 11, which defines RES objects, representing the abstract classification of physical and logical resources in the operator's network; an RFS design module 12, which is communicatively connected to the RES design module 11, defines RFS objects, which represent resource-oriented services, and consists of at least one RES object; RFS represents network capabilities; and a CFS design module 13, which is communicatively connected to the RFS design module 12 and the RES design module 11, defines CFS objects, which represent customer-oriented services, and consists of at least one RFS object. The functions and services of the RES design module 11, RFS design module 12, and CFS design module 13 are decoupled. Based on the RES design module 11, RFS design module 12, and CFS design module 13, the specifications of the service catalog are defined.

[0024] This invention implements a service catalog based on the CFS / RFS specification for a service orchestrator. The service catalog mainly comprises three modules: RES design, RFS design, and CFS design, achieving functional and business decoupling of RES, RFS, and CFS. Specifically, the RES design module 11 defines RES objects (resource objects), which abstractly categorize physical and logical resources in the operator's network. RES design module 11 includes two main functions: resource object management and resource object design. Resource object management primarily manages RES objects, including functions such as adding, deleting, modifying, and querying. Resource object design mainly describes resource objects and can define their attribute values. This invention supports adding, deleting, modifying, and querying resource object attribute values. The RFS design module 12 is mainly used to define RFS objects. RFS is a resource-oriented service, composed of one or more RES objects. RFS design module 12 includes two main functions: RFS object management and RFS object design. RFS object management is primarily used for managing RFS objects, including functions such as adding, deleting, modifying, and querying. RFS object design mainly describes RFS objects, defining resource object attribute values, resource object members, rules, actions, associated APIs, and other information. CFS design module 13 is mainly used to define CFS objects. CFS is a client-facing service composed of one or more RFS objects. CFS design module 13 includes two main functions: CFS object management and CFS object design. CFS object management is primarily used for managing CFS objects, including functions such as adding, deleting, modifying, and querying. CFS object design mainly describes CFS objects, defining resource object attribute values, RFS members, rules, actions, associated processes, and business model information.

[0025] By designing the service catalog functionality, the attributes, members, rules, and actions of RES / RFS / CFS are clearly defined, allowing for a better distinction between customer-facing services (CFS) and resource-facing services (RFS). This distinction enables a better understanding and management of the characteristics, delivery processes, and performance metrics of various services, thereby improving service management efficiency. Clearly defined and managed CFS ensures that services provided to end users meet their needs and expectations, thus enhancing user satisfaction. RFS management helps optimize the configuration and utilization of network and infrastructure resources, ensuring effective resource utilization when providing services to users, thereby reducing costs and improving efficiency. Differentiating between CFS and RFS allows for more accurate fault identification and handling, and optimization of service performance. This helps reduce service interruptions and improve service quality. Clearly defined CFS and RFS provide a foundation for the development and launch of new services and support flexible service composition and customization, thereby promoting innovation and market competitiveness. In this invention, the three-layer structure of RES, RFS, and CFS can be defined and reused separately, reducing the configuration workload of operators. Furthermore, CFS can be reused in different products, shortening the launch time of new products and improving the competitiveness of operators.

[0026] Figure 2 This is a schematic diagram of the structure of a service catalog implementation apparatus provided in another exemplary embodiment of the present invention, such as... Figure 2 As shown, the RES design module 11 may include: a resource object management unit 111, which is used to manage RES objects, including adding RES objects, deleting RES objects, modifying RES objects, and querying RES objects; and a resource object design unit 112, which is used to describe RES objects to define the attribute values ​​of RES objects.

[0027] The RES design module 11 comprises two main functions: resource object management and resource object design. Resource object management primarily manages RES (resource objects), including functions for adding, deleting, modifying, and querying. Resource object design mainly describes resource objects, allowing the definition of their attribute values ​​and supporting functions for adding, deleting, modifying, and querying these attribute values.

[0028] The attribute values ​​of a resource object refer to numerical values ​​or data used to describe specific characteristics or parameters of the resource object. These attribute values ​​can be classified and summarized according to different resource types and uses. For example, attribute values ​​can include static attributes and dynamic attributes. Static attributes include resource number: a unique identifier for the resource; resource category: the classification or type to which the resource belongs, such as natural resources, cultural resources, human resources, etc.; resource name: the formal or descriptive name of the resource; resource address information: the geographical location or storage location of the resource; resource provider: the individual or organization that provides or owns the resource; processor technical parameters, memory technical parameters, hard disk technical parameters, graphics card technical parameters, and network bandwidth technical parameters. Dynamic attributes include resource load attribute information: describing the load of the resource during operation, such as CPU utilization, memory usage, etc.; task running status information: describing the status of tasks running on the resource, such as task progress, task status (running, paused, completed, etc.). The above attribute values ​​are only examples, and not all resource objects have these attribute values. Different resource objects may have different attribute values, depending on the type of resource, its use, and the system or platform on which it is located. In practical applications, the attribute values ​​of resource objects can be defined and described according to specific needs.

[0029] In one embodiment, such as Figure 2 As shown, the RFS design module 12 may include: an RFS object management unit 121, which is used to manage RFS objects, including adding, deleting, modifying, and querying RFS objects; and an RFS object design unit 122, which is used to describe RFS objects to define their attribute values, resource object members, rules, actions, and associated APIs.

[0030] RFS design module 12 comprises two main functions: RFS object management and RFS object design. RFS object management primarily manages RFS resources, including functions such as adding, deleting, modifying, and querying. RFS object design mainly describes RFS objects, defining resource object attribute values, resource object members, rules, actions, associated APIs, and other information. Operators can abstract resource objects (RES) based on the network and integrate them into network capabilities (RFS). The attribute values ​​of an RFS object define the object's state or characteristics. For example, if an RFS object represents a video stream resource, it might have the following attribute values: id: a unique identifier for the resource; name: the name of the resource; format: the video format (e.g., MP4, HLS); bitrate: the video bitrate; resolution: the video resolution; status: the resource's status (e.g., available, processing, unavailable). Resource object members are the basic components or data parts that constitute an RFS object. These members typically include the previously defined attribute values, but can also include other complex objects or data structures. For example: `metadata` contains metadata information about the resource, such as title, description, and creation time; `content` contains the actual content of the resource or links to the content (such as the URL of a video stream); `permissions` defines access permissions to the resource. Rules define behavioral constraints or conditions for the RFS object. These rules can be based on attribute values, resource object members, or other external factors. For example, if the status is `unavailable`, access to the resource is not allowed; whether high-definition video can be downloaded depends on user permissions; and the bitrate of the video stream is automatically adjusted based on current network conditions. Actions are operations or methods that the RFS object can perform. These actions are usually associated with API endpoints, allowing clients to manage and interact with the resource. For example: `startStream()`: starts playing the video stream; `pauseStream()`: pauses the video stream; `setBitrate(bitrate)`: sets the bitrate of the video stream; `getResourceInfo()`: retrieves detailed information about the resource. The associated APIs define how to interact with the RFS object. Each action typically corresponds to one or more API endpoints.API design should follow RESTful principles or other applicable design principles. Here are some example API endpoints: GET / api / resources / {id}: Retrieves details of the specified resource; POST / api / resources / {id} / start: Starts playback of the specified resource; POST / api / resources / {id} / pause: Pauses playback of the specified resource; PUT / api / resources / {id} / bitrate: Sets the bitrate of the specified resource.

[0031] In one embodiment, such as Figure 2 As shown, the RFS object design unit 122 may include: an RFS object attribute value subunit 1221, which is used to maintain the specification information of the RFS object, including adding, deleting, modifying, querying, enabling, and disabling attribute values; an RFS resource object member function unit 1222, which is used to maintain the RES resource objects contained in the RFS, to add and delete defined RES resource objects; and an RFS rule function unit 1223, which is used to maintain the dependency relationships between RFS objects.

[0032] RFS object attribute values ​​are used to maintain RFS specification information, and attribute values ​​can be added, deleted, modified, queried, enabled, and disabled. RFS resource object membership functions maintain the resource objects contained in the RFS, and resource objects defined in the RES design can be added and deleted. RFS rule functions maintain dependencies between RFS objects; for example, RFS_B can be defined as dependent on RFS_A, and the system supports adding and deleting dependencies. Some RFS objects may depend on the existence and availability of other resource objects. For example, a virtual machine (VM) may depend on a specific volume or network interface (NIC) to run. Service-level dependencies may involve coordination between multiple components or services. For example, a web application may depend on a backend database service, a caching service, and a load balancer.

[0033] In one embodiment, such as Figure 2 As shown, the RFS object design unit 122 may include: an RFS action function unit 1224, which is used to maintain all actions supported by the RFS object; and an API function unit 1225, which is used to maintain the API information corresponding to the implementation of the RFS action, and to add and delete API binding relationships.

[0034] The RFS action function maintains all actions supported by RFS, such as add, delete, and modify. The system supports adding and deleting RFS-supported actions. The RFS associated API function maintains the API information corresponding to the implementation of RFS actions. For example, which API is used to add a new RFS is defined in this function. Adding a new RFS is usually implemented through an API (Application Programming Interface). The specific API used depends on the implementation method of the RFS service provider or platform. The system supports adding and deleting API bindings.

[0035] In one embodiment, such as Figure 2 As shown, the CFS design module 13 may include: a CFS object management unit 131, which is used to manage CFS objects, including adding, deleting, modifying, and querying CFS objects; and a CFS object design unit 132, which is used to describe CFS objects to define their attribute values, RFS members, rules, actions, associated processes, and business models.

[0036] CFS design module 13 comprises two main functions: CFS object management and CFS object design. CFS object management primarily manages CFS objects, including functions for adding, deleting, modifying, and querying them. CFS object design mainly describes CFS objects, defining their attribute values, RFS members, rules, actions, associated processes, and business model information. Operators abstract resource objects (RES) from the network, integrate these resource objects into network capabilities (RFS), and then integrate these network capabilities into customer-facing services (CFS). The CFS is then synchronized with the CRM (Customer Resource Management) system for product design, allowing operators greater flexibility in product configuration.

[0037] In one embodiment, such as Figure 2 As shown, the CFS object design unit 132 may include: a CFS object attribute value subunit 1321, which is used to maintain the specification information of the CFS object, including adding, deleting, modifying, querying, enabling, and disabling attribute values; a CFS member function subunit 1322, which is used to maintain the RFS objects contained in the CFS, to add and delete defined RFS objects; and a CFS rule function unit 1323, which is used to add and delete dependencies between CFS objects.

[0038] CFS object attribute values ​​are used to maintain CFS specification information, and attribute values ​​can be added, deleted, modified, queried, enabled, and disabled. CFS member functions maintain the RFS contained within the CFS, allowing the addition and deletion of RFS defined in the design. Rule functions maintain the dependencies between CFSs; for example, CFS_B can be defined as dependent on CFS_A. The system supports adding and deleting dependencies.

[0039] In one embodiment, such as Figure 2 As shown, the CFS object design unit 132 may include: a CFS action function unit 1324, which is used to add and delete actions supported by the CFS object; a CFS process function unit 1325, which is used to add and delete process information corresponding to CFS actions; and a CFS business model function unit 1326, which is used to maintain the business model corresponding to the CFS.

[0040] The CFS action function maintains all actions supported by CFS, such as install, uninstall, relocate, and modify. The system supports adding and deleting CFS-supported actions. The CFS associated process function maintains the process information corresponding to the implementation of CFS actions; for example, which process is used to implement a new CFS is defined in this function. The system supports adding and deleting process binding relationships. The CFS business model function maintains the corresponding business model for CFS. The business model defines the resource objects and parameters in CFS in a graphical way, and the service topology can be displayed in the service inventory management function.

[0041] In one embodiment, such as Figure 2 As shown, the service catalog implementation device 1 may further include: a synchronization module 14, which is used to synchronize the defined CFS to the customer relationship management system, so that the customer relationship management system can define products based on the defined CFS, combined with market demand factors and pricing strategy factors.

[0042] Synchronization module 14 provides CFS synchronization functionality, enabling the synchronization of CFS defined in the service orchestrator to systems such as CRM. CRM can define Products based on the CFS defined in the service orchestrator, combined with factors such as market demand and pricing strategies. The three-tiered structure of RES, RFS, and CFS can be defined and reused separately, reducing the configuration workload for operators and allowing CFS to be reused across different products, shortening the time to market for new products and enhancing the operator's competitiveness.

[0043] Figure 2This is a flowchart illustrating a service catalog implementation method provided by an exemplary embodiment of the present invention, as shown below. Figure 2 As shown, the service catalog implementation method is applicable to the service catalog implementation device provided in this application. The service catalog implementation method includes: Step 100: Abstracting and classifying physical resources and logical resources in the operator network to obtain RES objects, and defining RES objects through the RES design module; Step 200: Integrating RES objects into network capabilities, and defining RFS objects through the RFS design module; Step 300: Integrating network capabilities into customer-oriented services, and defining CFS objects through the CFS design module.

[0044] Physical resources refer to tangible resources that affect communication / information service capabilities, including but not limited to: spatial resources (such as administrative divisions, streets, business areas, service areas, stations, base stations, user access points, corridors, computer rooms, and other basic hardware and software facilities), network equipment (such as routers, switches, base station equipment, etc.), connection equipment (such as optical fibers, cables, copper wires, and other transmission media), and wireless equipment (such as antennas, towers, and other wireless communication infrastructure). These physical resources can be abstracted and categorized by attributes such as geographical location, equipment type, and connection type to form physical resources (RES). In addition, logical resources are intangible resources relative to physical resources, mainly including the topology and resource composition of network service capabilities. For example, the topology of service capabilities includes resource composition such as time slots, circuits, and logical paths. Logical resources can be abstracted and categorized by attributes such as service type, bandwidth, and transmission rate to form logical resources (RES). By abstracting and categorizing physical and logical resources in the operator's network into RES, unified management and optimized configuration of network resources can be achieved. For example, when a RES object is a video stream, its abstraction process needs to consider the basic characteristics of the video stream, its transmission method, and its representation in the network. A video stream consists of a series of consecutive image frames and may use various encoding formats. By assigning a unique resource identifier to the video stream, providing detailed metadata, specifying transmission information, defining quality levels, and setting access control policies, efficient transmission and correct playback of the video stream in the network can be ensured. At the same time, this abstracted information also helps the network management system to uniformly manage and optimize the video stream. Therefore, the abstraction of a RES object includes assigning a unique resource identifier (RES ID) to the video stream to uniquely identify it in the network; abstracting metadata containing detailed information about the video stream, such as title, description, author, encoding format, resolution, frame rate, and duration. This metadata helps clients correctly decode and play the video stream; and abstracting transmission information, specifying the transmission method of the video stream, including the protocol used, URL, and streaming media server address. In addition, other parameters related to video streaming transmission can be included, such as bandwidth requirements and buffering strategies, and quality levels can be abstracted. If the video stream supports Adaptive Bit Rate (ABR) technology, multiple quality levels (such as high definition, standard definition, smooth, etc.) can be abstracted so that the client can automatically select the appropriate video quality according to network conditions. Access control policies such as authentication, authorization, and encryption can also be set for the video stream to ensure the secure transmission and access of the video stream.

[0045] Integrating RES objects (response objects, typically used in network programming to represent server responses to client requests) into network capabilities essentially involves effectively utilizing the functionality and characteristics of RES objects to enhance the performance and user experience of network applications. For example: (I) First, clarify the functions and attributes of the RES object. RES objects usually contain response codes, response headers, and response bodies. Response codes indicate the server's status, such as 200 for success and 404 for not found. Response headers contain metadata about the response, such as content type, content length, and cache control. The response body is the actual data returned by the server to the client, which can be text, images, video, etc. (II) Customize the RES object according to the network application's needs. Based on the network application's requirements, customize the response content, format, and encoding of the RES object. For example, in video streaming applications, the RES object may contain information such as the URL, format, and bitrate of the video stream data. (III) Use the RES object to implement network functions. Data transmission: RES objects can be used to transmit data to the client. In web development, the server uses the RES object to send response data back to the client, achieving bidirectional data transmission. State management: The response codes of the RES object can be used to manage the state of the network application. For example, the response code can be used to determine whether a request was successful, thus deciding on the next step. Cache control: Cache control directives in the response header of the RES object can be used to manage client-side caching. This helps reduce network traffic and improve application response speed. (IV) Optimizing the performance of the RES object: Compressing data: Compressing the response body of the RES object, such as using algorithms like Gzip or Brotli, can reduce the amount of data transmitted and improve transmission efficiency.

[0046] Configure appropriate response headers: Based on application requirements, configure appropriate response headers, such as Content-Type and Content-Length, to ensure that the client can correctly parse and process the response data. Optimize transmission strategies: Based on network conditions and client capabilities, select appropriate transmission strategies, such as Adaptive Bit Rate (ABR) technology, to ensure smooth playback of the video stream.

[0047] Integrating predefined RFS objects into a customer-facing service typically requires clearly defining service goals and functions, such as providing video streaming services, resource management services, or other RFS object-related services. Based on the RFS object's attribute values ​​and actions, the functions the service should provide are defined, such as playing video, adjusting video quality, and retrieving resource information. Next, API interfaces are designed, defining corresponding API endpoints for each function. Then, the backend logic is implemented, based on the API interface definitions, including handling requests, invoking RFS object actions, and retrieving and processing data. Finally, the RFS objects are integrated; they are created and initialized when the service starts, mapping the RFS object actions to the backend logic for API calls. Finally, the service is deployed to an appropriate server, ensuring the server meets the service requirements, and rigorously tested.

[0048] By abstracting and classifying the physical and logical resources in the operator's network, RES objects are obtained. Then, RES objects are defined through the RES design module, and the defined RES objects are integrated into network capabilities. RFS objects are defined through the RFS design module, and the defined RFS objects are integrated into customer-facing services. Finally, CFS objects are defined through the CFS design module, thereby completing the service catalog function design.

[0049] By designing the service catalog functionality, the attributes, members, rules, and actions of RES / RFS / CFS are clearly defined, allowing for a better distinction between customer-facing services (CFS) and resource-facing services (RFS). This distinction enables a better understanding and management of the characteristics, delivery processes, and performance metrics of various services, thereby improving service management efficiency. Clearly defined and managed CFS ensures that services provided to end users meet their needs and expectations, thus enhancing user satisfaction. RFS management helps optimize the configuration and utilization of network and infrastructure resources, ensuring effective resource utilization when providing services to users, thereby reducing costs and improving efficiency. Differentiating between CFS and RFS allows for more accurate fault identification and handling, and optimization of service performance. This helps reduce service interruptions and improve service quality. Clearly defined CFS and RFS provide a foundation for the development and launch of new services and support flexible service composition and customization, thereby promoting innovation and market competitiveness. In this invention, the three-layer structure of RES, RFS, and CFS can be defined and reused separately, reducing the configuration workload of operators. Furthermore, CFS can be reused in different products, shortening the launch time of new products and improving the competitiveness of operators.

[0050] This invention provides a service catalog implementation apparatus. The apparatus can be implemented through software, hardware, or a combination of both. From a hardware perspective, in addition to a CPU, memory, network interface, and non-volatile memory, the device in the embodiment typically includes other hardware, such as a forwarding chip responsible for processing packets. Taking software implementation as an example, as a logically defined apparatus, it is formed by the CPU of the device loading the corresponding computer program instructions from the non-volatile memory into memory for execution.

[0051] According to another aspect of the present invention, a computer-readable storage medium is provided, the storage medium storing a computer program for performing the service catalog implementation method of any of the above embodiments.

[0052] In addition to the methods and devices described above, embodiments of the present invention may also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the steps in the service catalog implementation methods according to various embodiments of the present invention described in the "Exemplary Methods" section above.

[0053] According to another aspect of the present invention, an electronic device is provided, comprising: a processor; a memory for storing processor-executable instructions; and a processor for executing the service catalog implementation method of any of the above embodiments.

[0054] Furthermore, embodiments of the present invention may also be computer-readable storage media storing computer program instructions thereon, which, when executed by a processor, cause the processor to perform the steps in the service catalog implementation methods according to various embodiments of the present invention described in the "Exemplary Methods" section above.

[0055] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A service directory implementation apparatus, characterized by comprising: Comprise: The RES design module is used for defining RES object, RES object is used for abstracting and classifying physical resource and logical resource in operator network, and RES object is resource object; The RFS design module is connected with the RES design module in communication, and is used for defining RFS object, RFS object is used for resource-oriented service, and RFS object is composed of at least one RES object; RFS represents network capability; The CFS design module is connected with the RFS design module in communication, and is used for defining CFS object, CFS object is used for customer-oriented service, and CFS object is composed of at least one RFS object; Wherein, the RES design module, the RFS design module and the CFS design module define the specification of service directory; The RFS design module comprises: The RFS object management unit is used for managing RFS object, and the management of RFS object includes adding RFS object, deleting RFS object, modifying RFS object and inquiring RFS object; The RFS object design unit is used for describing RFS object, so as to define attribute value, resource object member, rule, action and associated API of RFS object; The CFS design module comprises: The CFS object management unit is used for managing CFS object, and the management of CFS object includes adding CFS object, deleting CFS object, modifying CFS object and inquiring CFS object; The CFS object design unit is used for describing CFS object, so as to define attribute value, RFS member, rule, action, associated flow and business model of CFS object.

2. The service directory implementation apparatus of claim 1, wherein The RES design module comprises: The resource object management unit is used for managing RES object, and the management of RES object includes adding RES object, deleting RES object, modifying RES object and inquiring RES object; The resource object design unit is used for describing RES object, so as to define attribute value of RES object.

3. The service directory implementation device of claim 2, wherein, The RFS object design unit comprises: The RFS object attribute value subunit is used for maintaining specification information of RFS object, and the maintenance of specification information of RFS object includes adding, deleting, modifying, inquiring, enabling and disabling attribute value; The RFS resource object member function unit is used for maintaining RES resource object contained by RFS, so as to add and delete defined RES resource object; The RFS rule function unit is used for maintaining the dependent relationship between RFS objects.

4. The service directory implementation device of claim 3, wherein, The RFS object design unit comprises: The RFS action function unit is used for maintaining all actions supported by RFS object; An API function unit is configured to maintain API information corresponding to the RFS action and to add and delete API binding relations.

5. The service directory implementation device of claim 4, wherein, The CFS object design unit includes: A CFS object attribute value subunit is configured to maintain specification information of the CFS object, including adding, deleting, modifying, querying, enabling and disabling attribute values; A CFS member function subunit is configured to maintain RFS objects contained in the CFS, to add and delete defined RFS objects; A CFS rule function unit is configured to add and delete dependency relations between CFS objects.

6. The service directory implementation device of claim 5, wherein, The CFS object design unit includes: A CFS action function unit is configured to add and delete actions supported by the CFS object; A CFS flow function unit is configured to add and delete flow information corresponding to the CFS action; A CFS service model function unit is configured to maintain a service model corresponding to the CFS.

7. The service directory implementation apparatus of claim 1, wherein The service directory implementation device further includes: A synchronization module is configured to synchronize the defined CFS to a customer relationship management system, so that the customer relationship management system defines a product based on the defined CFS, in combination with market demand factors and pricing strategy factors.

8. A service directory implementation method, characterized by, The service directory implementation method includes: Abstracting and classifying physical resources and logical resources in an operator network to obtain RES objects, and defining the RES objects through an RES design module; Integrating the defined RES objects into network capabilities, and defining RFS objects through an RFS design module; Integrating the network capabilities into customer-oriented services, and defining CFS objects through a CFS design module. The service directory implementation method includes: Abstracting and classifying physical resources and logical resources in an operator network to obtain RES objects, and defining the RES objects through an RES design module; Integrating the defined RES objects into network capabilities, and defining RFS objects through an RFS design module; Integrating the network capabilities into customer-oriented services, and defining CFS objects through a CFS design module.

Images