Interaction interface and interaction method

Abstract

Provided are an interaction interface and an interaction method. The interaction interface comprises a first interface and a second interface, wherein the first interface is used for sensing a service provided by a network or a cloud computing resource pool, mapping the service to a service identifier, and associating, with the service identifier, a scheduling policy corresponding to the service; and the second interface is used for subscribing, on the basis of a service subscription request of a terminal, to the service from the network or the cloud computing resource pool in the form of the service identifier.

Description

An interactive interface and an interactive method

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure is based on Chinese patent application CN202410020650.6 filed on January 4, 2024, entitled “An Interactive Interface and an Interactive Method”, and claims the priority of the patent application, and all the contents disclosed therein are incorporated into this disclosure by reference. Technical Field

[0003] The present disclosure relates to the field of communications, and in particular, to an interaction interface and an interaction method. Background Art

[0004] With the development of digital infrastructure, various intelligent applications are rapidly evolving, cloud computing services are developing in a diversified manner, and network demands are becoming increasingly refined and diverse. The interactive collaboration between terminals, networks, and cloud computing is a fundamental requirement for new business scenarios that integrate computing and networks, and it is also a fundamental requirement for future industrial development and technological innovation.

[0005] Currently, terminal applications, bearer networks, and cloud computing resource pools are independent systems, each developing independently and belonging to different operational and technical fields. This disconnects services from the network, making it impossible to meet the requirements for efficient interaction and collaboration between terminals, networks, and cloud computing. From the perspective of business applications, the network is viewed as a pipeline, and business terminals and cloud computing resource pools are unable to schedule network resources based on the real-time network status. For example, in Internet telephony or video conferencing services, the network dispatches services from user terminals to the server on a best-effort basis. However, when traffic bursts, network congestion, or excessive latency occur, user terminals and servers are unable to immediately detect the network anomaly, resulting in service delays or interruptions, resulting in service freezes and "poor network signal" prompts. From a network (Layer 3 routing) perspective, current applications associate service names with Internet Protocol (IP) addresses through Domain Name System (DNS) queries. The network uses fixed IP addresses for service transmission. The IP+port number (5-tuple) does not carry sufficient service feature information. The network cannot fully distinguish the atomic service types of services, making it impossible to match services in a fine-grained manner for precise and rapid responses.

[0006] In summary, the network cannot perceive the business in a fine-grained manner and cannot guarantee business needs in real time; the business cannot perceive the network service capabilities in real time; and the technical barriers between terminals, networks, and cloud computing cannot be broken down to achieve efficient interconnection and interoperability, which urgently needs to be solved.

[0007] Summary of the Invention

[0008] The embodiments of the present disclosure provide an interactive interface and an interactive method to at least solve the problem in related technologies that terminals, networks, and cloud computing resource pools cannot achieve efficient interactive collaboration.

[0009] According to one embodiment of the present disclosure, an interactive interface is provided, which includes a first interface and a second interface, wherein the first interface is used to perceive the business services provided by the network or cloud computing resource pool, map the business services to service identifiers, and associate the scheduling policies corresponding to the business services with the service identifiers; the second interface is used to subscribe to business services from the network or cloud computing resource pool in the form of a service identifier based on the terminal's service subscription request.

[0010] According to another embodiment of the present disclosure, an interaction method is provided for performing information interaction using the interaction interface in any of the above embodiments.

[0011] According to another embodiment of the present disclosure, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above method embodiments are executed.

[0012] According to another embodiment of the present disclosure, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] FIG1 is a schematic diagram of an application scenario of an interactive interface according to an embodiment of the present disclosure;

[0014] FIG2 is a structural block diagram of an interactive interface in an embodiment of the present disclosure;

[0015] FIG3 is a schematic diagram (I) of an interactive interface for implementing end-network-cloud interaction based on a service identifier in an embodiment of the present disclosure;

[0016] FIG4 is a schematic diagram (II) of an interactive interface for implementing end-network-cloud interaction based on a service identifier in an embodiment of the present disclosure;

[0017] FIG5 is a schematic diagram (III) of an interactive interface for implementing end-network-cloud interaction based on a service identifier in an embodiment of the present disclosure;

[0018] FIG6 is a schematic diagram of the service interface governance and the end-network-cloud interaction process in one embodiment of the present disclosure. DETAILED DESCRIPTION

[0019] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings and in conjunction with embodiments.

[0020] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0021] The disclosed embodiment is oriented towards the three systems of terminals, networks, and cloud computing resource pools in a service-aware network, and designs an interactive interface that uses service identifiers as interface indexes.

[0022] Figure 1 is a schematic diagram of the application scenario of the interactive interface according to the embodiment of the present disclosure. As shown in Figure 1, the interactive interface is implemented based on service identification. The service identification governance is oriented to the end, network, and cloud. It is used to connect the three systems of terminal, network, and cloud computing resource pool. The service identification is used as the global semantics and global index. In the three systems of end, network, and cloud, it can serve as an index interface for service call access, service refined connection, and service perception delivery, respectively, to achieve efficient interconnection and interoperability of end, network, and cloud.

[0023] In some embodiments, the network is an L3 routing and forwarding layer network.

[0024] FIG2 is a block diagram of the interactive interface in an embodiment of the present disclosure. As shown in FIG2 , the interactive interface includes:

[0025] The first interface 10 and the second interface 20 .

[0026] The first interface 10 is used to sense the business services provided by the network or cloud computing resource pool, map the business services to service identifiers, and associate the scheduling policy corresponding to the business services with the service identifiers;

[0027] The second interface 20 is used to subscribe to the business service from the network or the cloud computing resource pool in the form of the service identifier based on the service subscription request of the terminal.

[0028] The disclosed embodiments can provide service call access for terminals based on service identifiers, realize business service awareness of networks and computing resource pools based on service identifiers, and provide refined network connections for business services through scheduling strategies, thereby solving the problem in related technologies that terminals, networks, and cloud computing resource pools cannot achieve efficient interactive collaboration.

[0029] In this embodiment, the cloud computing resource pool is used to provide cloud computing services for terminal business traffic. Cloud computing services include services in different dimensions, such as computing resources, functions, and applications. The network can be an L3 routing and forwarding layer network, which is used to forward business traffic and dispatch business traffic to service instances for corresponding business processing according to the scheduling policy.

[0030] In some embodiments, the first interface is used to obtain service attributes of the business service from the network or the cloud computing resource pool, and register a service interface according to the service attributes, wherein the interface index of the service interface is the service identifier.

[0031] In some embodiments, the first interface is also used to generate a scheduling policy corresponding to the business service based on the service attributes, and associate the scheduling policy corresponding to the business service with the service identifier, wherein the scheduling policy is used to guide the scheduling of the business traffic of the terminal in the network.

[0032] In some embodiments, a second interface is used to obtain the service subscription request from the terminal, allocate the service interface to the terminal according to the service subscription request, and send the service identifier corresponding to the service interface to the terminal, wherein the service interface is one of multiple service interfaces registered with the network or the cloud computing resource pool, and the service interface is used to provide the business service for the business traffic, and the business service is delivered based on the service identifier.

[0033] In some embodiments, the interactive interface further includes: a third interface 30 .

[0034] The third interface 30 is used to transmit the business traffic carrying the service identifier from the terminal to the network, determine the scheduling strategy based on the service identifier, and schedule the business traffic to the cloud computing resource pool or the network according to the scheduling strategy to realize the delivery of the business service.

[0035] In an exemplary embodiment, the first interface 10 includes a cloud computing resource perception interface 11 and a computing network strategy mapping interface 12 .

[0036] The cloud computing resource perception interface 11 is used to perceive the cloud computing service provided by the cloud computing resource pool, obtain the cloud computing service attributes of the cloud computing service from the cloud computing resource pool, and register the service interface according to the cloud computing service attributes, wherein the interface attributes of the service interface are the cloud computing service attributes.

[0037] The computing network strategy mapping interface 12 is used to obtain the cloud computing service attributes from the cloud computing resource pool, determine the network scheduling strategy corresponding to the cloud computing service according to the cloud computing service attributes, and associate the network scheduling strategy with the service identifier.

[0038] In this embodiment, the business service includes the cloud computing service, the scheduling strategy includes the network scheduling strategy, and the network scheduling strategy is used to guide the scheduling of the business traffic in the network.

[0039] Furthermore, the scheduling strategy is calculated and generated based on the service capabilities and network requirements, providing different scheduling strategies for different services; when the service is connected to the network, refined network connections can be provided for the service based on the scheduling strategy.

[0040] In some embodiments, the cloud computing resource perception interface is configured to receive a service registration request for the cloud computing service from the cloud computing resource pool, wherein the service registration request carries the cloud computing service attributes, and the cloud computing service attributes include at least a service type. Exemplarily, the cloud computing service attributes may include service capability attributes (e.g., service type / name) and service requirement attributes.

[0041] In some embodiments, the cloud computing resource perception interface is also used to determine a unique service identifier based on the service type; determine whether the cloud computing service has been registered based on the service identifier; if the cloud computing service has not been registered, add a corresponding service interface for the cloud computing service, and use the service identifier as the interface index of the service interface, and use the cloud computing service attributes as the interface attributes of the service interface; if the cloud computing service has been registered, update the service interface with the service identifier as the interface index based on the cloud computing service attributes.

[0042] Furthermore, each service interface may include one or more service instances, and the service identifier is only used to identify the service type / name, not the location of the service instance.

[0043] In some embodiments, the service identifier is generated when the resource pool registers the cloud computing service. The attributes and status associated with the service identifier can be updated and maintained during the use of service access, service scheduling, and service delivery. In addition, a service cancellation function can also be provided to reclaim and revoke the service identifier when all services are cancelled.

[0044] In some embodiments, the network scheduling strategy includes at least one of the following: a computing power measurement value, a target strategy, and a network scheduling result.

[0045] Furthermore, based on different network scheduling strategies, the computing network strategy mapping interface can also be used to implement any one of the following methods or a combination of methods:

[0046] (1) for obtaining the cloud computing service attributes from the cloud computing resource pool based on the service identifier, generating a computing power measurement value of the cloud computing service based on the cloud computing service attributes, and associating the computing power measurement value with the service identifier;

[0047] (2) for obtaining the cloud computing service attributes from the cloud computing resource pool based on the service identifier, selecting a target policy from a plurality of preset policies based on the cloud computing service attributes, and associating the target policy with the service identifier;

[0048] (3) It is used to obtain the cloud computing service attributes from the cloud computing resource pool based on the service identifier, determine the computing power measurement value and the target strategy based on the cloud computing service attributes, perform network scheduling on the cloud computing service according to the computing power measurement value and the target strategy, obtain the network scheduling result, and associate the network scheduling result with the service identifier.

[0049] In an exemplary embodiment, the preset policies include but are not limited to: experience priority policy, resource priority policy, network priority policy, cloud computing priority policy, balancing policy, etc.

[0050] In another exemplary embodiment, the first interface 10 includes a network service open interface 13 and an orchestration policy mapping interface 14 .

[0051] The network service open interface 13 is used to perceive the network service provided by the network, obtain the network service attributes of the network service from the network, and register a service interface according to the network service attributes, wherein the interface attributes of the service interface are the network service attributes.

[0052] The orchestration strategy mapping interface 14 is used to obtain the network service attributes from the network, orchestrate the corresponding cloud computing scheduling strategy for the cloud computing service in the cloud computing resource pool according to the network service attributes, and associate the cloud computing scheduling strategy with the service identifier.

[0053] In this embodiment, the business service includes the network service, the scheduling policy includes the cloud computing scheduling policy, and the cloud computing scheduling policy is used to indicate the network service provided by the network for the business traffic.

[0054] In an exemplary embodiment, the orchestration strategy mapping interface orchestrates the network services that the network can provide based on the service requirements of the cloud computing service (such as bandwidth requirements, latency requirements, etc.), and obtains a cloud computing scheduling strategy that meets the service requirements (i.e., the orchestration result of the network service).

[0055] In some embodiments, the network service open interface is used to receive a service registration request for the network service from the network, wherein the registration request carries the network service attributes, and the network service attributes include at least a service type.

[0056] In some embodiments, the network service open interface is also used to determine a unique service identifier based on the service type; determine whether the network service has been registered based on the service identifier; if the network service has not been registered, add a corresponding service interface for the network service, and use the service identifier as the interface index of the service interface, and use the network service attributes as the interface attributes of the service interface; if the network service has been registered, update the service interface with the service identifier as the interface index based on the network service attributes.

[0057] In an exemplary embodiment, the second interface 20 includes a computing network service calling interface 21 .

[0058] The computing network service calling interface 21 is used to obtain the service subscription request sent by the terminal, parse the service subscription request to obtain the service type of the business service, wherein the service subscription request carries the service type.

[0059] The computing network service calling interface 21 is further used to allocate one of the service interfaces to the terminal according to the service type and the interface attributes of the multiple service interfaces, and send the service identifier corresponding to the service interface to the terminal to complete the subscription to the business service.

[0060] In some embodiments, the interface attributes of the service interface further include a service status attribute, wherein the service status attribute includes an available status, an unavailable status, or a used status.

[0061] Furthermore, the network service calling interface 21 is also used to allocate a service interface with the same service type and in an available state to the terminal according to the service type and the interface attributes of the multiple service interfaces, and update the corresponding service status attribute to the used state after the subscription is completed.

[0062] In an exemplary embodiment, the third interface 30 includes a service access interface 31 and a service delivery interface 32 .

[0063] The service access interface 31 is configured to receive the service traffic carrying the service identifier sent by the terminal and forward the service traffic to the network;

[0064] The service delivery interface 32 is used to determine the cloud computing scheduling strategy or the network scheduling strategy based on the service identifier, and schedule the business traffic to the cloud computing resource pool according to the cloud computing scheduling strategy, or schedule the business traffic to the network according to the network scheduling strategy, wherein the scheduling strategy includes the cloud computing scheduling strategy or the network scheduling strategy.

[0065] In some embodiments, the service attributes include at least one of the following: service capability attributes, service requirement attributes, and service status attributes. Exemplarily, the service capability attributes include, but are not limited to, service name, service type, service level, service gateway, service instance, service resource information, and service processing information; the service requirement attributes include, but are not limited to, bandwidth requirements, latency requirements, jitter requirements, reliability requirements, and stability requirements; and the service status attributes include, but are not limited to, available status, unavailable status, or used status.

[0066] The disclosed embodiments can connect user services, cloud computing services, and networks based on service identifiers, use service identifiers as global indexes, and serve as index interfaces for service call access, service refined connection, and service perception delivery in the end, network, and cloud systems, respectively. This solves the problem in related technologies where terminals, networks, and cloud computing resource pools cannot achieve efficient interactive collaboration, and helps build a unified service model integrating the end, network, and cloud, enabling more intelligent, agile, efficient, and refined digital services.

[0067] FIG3 is a schematic diagram (I) of an interactive interface for implementing end-network-cloud interaction based on a service identifier in an embodiment of the present disclosure. As shown in FIG3 , the interactive interface includes the following structure:

[0068] Cloud computing resource perception interface 11, computing network strategy mapping interface 12 and computing network service calling interface 21.

[0069] In this embodiment, the interface features of the cloud computing resource perception interface include the following:

[0070] Interface index: service ID.

[0071] Interface attributes: Cloud computing service attributes. The most basic is the service type / name. For example, cloud computing service attributes can include the service capability attributes provided by the cloud computing resource, service requirement attributes, and service status attributes (optional).

[0072] Function: The interactive interface between the cloud computing resource pool and the network. Based on the cloud computing resource perception interface, the cloud computing resource pool provides the network with the service capabilities and service status of cloud computing resources in the form of service identifiers, and proposes service-level agreements (SLAs) that meet the business requirements.

[0073] Interface operation: The cloud computing resource pool registers the interface attributes of the cloud computing service through this interface, or the network announces the interface attributes through the routing protocol, generates the interface index according to the relevant algorithm, and calculates the service status attributes (optional).

[0074] Interface index allocation: Generate a service interface index, i.e., a service identification ID, for the service provided by the cloud computing resource pool, and position it as the unique service semantic identifier (global identifier) ​​within the service domain. It only corresponds to the service type information and service level information (optional), and other attribute information is used as its associated attributes.

[0075] In some embodiments, the cloud computing resource perception interface is not limited to direct interaction between the cloud computing resource pool and the network, but may also include indirect interaction between the network and the cloud computing resource pool's proxy gateway, cloud management platform, etc.

[0076] In some embodiments, the service identifier can be generated based on the service name (or service type) and service level (optional) in the interface attributes. If the interface index already exists when the service is registered, the service interface attributes are added, and the service capability attributes and service status attributes in the service interface attributes are updated.

[0077] In an exemplary embodiment, the service capability attribute refers to the capability that can be provided when the service is provided externally. The service capability attribute includes at least one of the following: service name, service type information, service level information (hierarchical classification), service gateway information (gateway address, gateway port, etc.), service instance information, service resource information (Graphics Processing Unit (GPU) core number, memory amount, number of accessible users, etc.), service processing information (service computing rate, cloud computing side processing delay, packet loss rate, etc.).

[0078] In an exemplary embodiment, the service requirement attribute refers to the service's requirement for the computing network quality, and the service requirement attribute includes at least one of the following: SLA information such as bandwidth requirement, delay requirement, jitter requirement, and reliability requirement.

[0079] In an exemplary embodiment, the service status attributes include an available status (valid), an unavailable status (unavailable), and a used status (used).

[0080] In an exemplary embodiment, a service ID can be associated with multiple service instances that provide the same service in different locations. During the service interface index allocation process, service IDs can be allocated according to different preset allocation strategies. Exemplary allocation strategies may include: 1. The system plans a unified identification resource pool, and sequentially obtains identifications from the identification resource pool and allocates them to services; 2. Allocates hierarchical service IDs according to the service type and service level in the service registration data; 3. Combines encryption algorithm strategies to allocate secure and intelligent service IDs.

[0081] In this embodiment, the interface characteristics of the computing network policy mapping interface include the following:

[0082] Interface index: Service ID. Used to identify the service type. It can include multiple service instances or multiple service locations corresponding to the same service type.

[0083] Interface attributes: computing power measurement value, scheduling policy and / or scheduling result.

[0084] Function: The interactive interface between the network and the cloud computing resource pool. Based on the interface index, the network perceives the cloud computing service capabilities and service requirements provided by the cloud resource pool, performs measurement calculations for the corresponding cloud computing service capabilities and requirements, generates the corresponding computing network routing or computing network scheduling policy (i.e., the network scheduling policy mentioned above), and maps it to the computing network devices (including computing power routing gateways, computing network controllers, etc.) through the computing network policy mapping interface.

[0085] Interface operation: Based on the service capability attributes and service demand attributes, combined with network attributes, and according to different scheduling strategies, the computing network is scheduled for the cloud computing service, routing decisions are made, and the decision results are sent to the computing network equipment / computing power routing gateway.

[0086] In an exemplary embodiment, the computing power measurement value includes a computing power metric or a computing network metric, the scheduling strategy includes an experience priority strategy, a resource priority strategy, a network priority strategy, a cloud computing priority strategy, a balancing strategy, etc., and the scheduling result includes configuration information, traffic diversion information, path information, computing power routing table items, etc.

[0087] In this embodiment, the interface features of the computing network service call interface include the following:

[0088] Function: The interactive interface between the terminal and the cloud computing resource pool. The terminal subscribes to the required cloud computing services through the computing network service call interface and calls the computing network service.

[0089] Interface index: service ID.

[0090] Interface attributes: service name / type.

[0091] Interface operation: The terminal sends a service interface subscription request, which carries service type information. Based on the service status attributes of the service interface, the terminal determines the available service interface. The terminal only needs to obtain the service identifier of the available service, without having to obtain the IP location information of the service instance through the Domain Name System (DNS).

[0092] Through the embodiments of the present disclosure, the business services provided by the cloud computing resource pool can be mapped to service identifiers, and the scheduling policies corresponding to the business services can be associated with the service identifiers. The business services can be subscribed to the cloud computing resource pool in the form of service identifiers based on the service subscription requests of the terminals, thereby solving the problem in related technologies that the terminals, networks and cloud computing resource pools cannot achieve efficient interactive collaboration, and helping to build a unified service model integrating terminals, networks and clouds.

[0093] FIG4 is a schematic diagram (II) of an interactive interface for implementing end-network-cloud interaction based on a service identifier in an embodiment of the present disclosure. As shown in FIG4 , the interactive interface includes the following structure:

[0094] Service access interface 31 and service delivery interface 32.

[0095] In this embodiment, the interface features of the service access interface include the following:

[0096] Function: The interactive interface between the terminal and the network. The terminal application accesses the cloud computing service through the service access interface, and the network performs service scheduling. The network can perceive the cloud computing service scheduling request raised by the terminal based on this interface and provide refined service-based scheduling capabilities.

[0097] Interface index: service identifier. This service identifier is obtained through the second interface (such as the computing network service call interface) and is encapsulated and carried in the service traffic data packet.

[0098] Interface operation: The terminal encapsulates the service identifier index into the business traffic data packet and transmits it to the computing network device in the network. The computing network device parses the data packet to obtain the service identifier and uses the service identifier as an index to obtain service requirement attributes, service capability attributes, and service interface status attributes, thereby providing service scheduling with service-level granularity.

[0099] In this embodiment, the relationship between the service identifier and the service interface's service requirement attributes, service capability attributes, and service status attributes is a mapping relationship that is pre-perceived and established through a first interface (such as a cloud computing resource perception interface and a computing network policy mapping interface).

[0100] In this embodiment, the interface features of the service delivery interface include the following:

[0101] Function: The interactive interface between the network and the cloud computing resource pool. Through the service delivery interface, the network schedules services based on the computing network strategy (or scheduling results), and the cloud resource pool provides service delivery for the services.

[0102] Interface index: service identifier, encapsulated and carried in service traffic data packets.

[0103] Interface operation: The network identifies the service identifier in the business traffic and, based on the scheduling policy in the computing-network policy mapping interface, associates the business traffic with the mapping policy and scheduling results of the service identifier index. For example, network scheduling can be performed based on the network scheduling policy, cloud computing scheduling can be performed based on the cloud computing scheduling policy, and network and cloud computing can be jointly scheduled based on the computing-network comprehensive policy (including network scheduling policy and cloud computing scheduling policy). Ultimately, the business traffic is dispatched to the cloud computing resource pool for service processing.

[0104] In some embodiments, the service access interface 31 and the service delivery interface 32 can be combined with the cloud computing resource perception interface 11, the computing network strategy mapping interface 12 and the computing network business call interface 21 to complete interactive functions such as cloud computing resource perception, computing network strategy mapping, and computing network business call, and complete end-to-end interaction of business traffic.

[0105] Through the embodiments disclosed herein, the three systems of end, network and cloud can be connected based on the service identifier, and the service identifier can be used as a global index to serve as an index interface for service call access, service refined connection and service perception delivery in the three systems, respectively. This solves the problem in related technologies that terminals, networks and cloud computing resource pools cannot achieve efficient interactive collaboration, and helps to build a unified service model integrating end, network and cloud, and realize more intelligent, agile, efficient and refined digital services.

[0106] FIG5 is a schematic diagram (III) of an interactive interface for implementing end-network-cloud interaction based on a service identifier in an embodiment of the present disclosure. As shown in FIG5 , the interactive interface includes the following structure:

[0107] Network service open interface 13, orchestration strategy mapping interface 14 and computing network service calling interface 21.

[0108] In this embodiment, the interface features of the network service open interface include the following:

[0109] Function: The interface between the network and the cloud computing resource pool. Through this interface, the network exposes its service capabilities and status to the cloud computing resource pool. This interface is not limited to direct interaction between network devices and the cloud computing resource pool; it also includes network controllers and network management platforms.

[0110] Interface index: service identifier, generated based on the service name / type and service level (optional) of the network service.

[0111] Interface attributes: Network service attributes, including network service capability attributes and network service status attributes provided by the network.

[0112] Interface operation: The network registers the interface properties of the network service through the interface, or notifies the network interface properties through the routing protocol, generates an interface index based on the relevant algorithm, and provides the network service associated with this interface index to the cloud computing resource pool for perception and orchestration.

[0113] In an exemplary embodiment, network service capability refers to the capability that can be provided when network services are provided externally. Network service capability attributes include network processing capabilities (bandwidth, latency, jitter, packet loss rate, etc.), service level information (hierarchical classification), and access gateway information (gateway address, gateway port, etc.).

[0114] In this embodiment, the interface characteristics of the orchestration policy mapping interface include the following:

[0115] Function: The interface between the cloud computing resource pool and the network. The cloud computing resource pool or cloud management platform uses the interface index (service identifier) ​​to perceive the network service capabilities provided by the network and orchestrate efficient cloud computing service scheduling strategies for business services.

[0116] Interface index: service identifier. The service identifier can be used to identify the type of network service, but not the specific path for providing the network service.

[0117] Interface operation: The cloud computing resource pool obtains the network service capabilities associated with the interface index (service identifier), selects the corresponding network service for business orchestration based on business needs, and notifies the terminal application of the orchestration results.

[0118] In this embodiment, the interface features of the computing network service call interface include the following:

[0119] Function: The interactive interface between the terminal and the cloud computing resource pool. The terminal subscribes to the required network services through the computing network service call interface.

[0120] Interface index: service ID.

[0121] Interface attributes: service name / type.

[0122] Interface operation: The terminal sends a service interface subscription request, which carries service type information. The corresponding network service is determined based on the service type. The terminal only needs to obtain the service identifier of the available network service without obtaining the specific network path.

[0123] In some embodiments, the network service open interface 13, the orchestration strategy mapping interface 14, and the computing network service call interface 21 can also be combined with the service access interface 31 and the service delivery interface 32 to implement the call and delivery of network services based on the service identifier, thereby completing end-to-end interaction of business traffic.

[0124] Through the embodiments of the present disclosure, the network services provided by the network can be mapped to service identifiers, and the scheduling policies corresponding to the network services can be associated with the service identifiers. The network services can be subscribed to the network in the form of service identifiers based on the service subscription requests of the terminals, thereby solving the problem in related technologies that the terminals, networks and cloud computing resource pools cannot achieve efficient interactive collaboration, and helping to build a unified service model integrating terminals, networks and clouds.

[0125] In the disclosed embodiment, an interactive interface between the terminal, network, and cloud computing resource pool based on service identification is designed. Through the cloud computing resource perception interface, the network can perceive the cloud computing service in a fine-grained manner; through the computing network strategy mapping interface, the network can provide real-time guarantee at the service flow level; through the computing network service call interface, the terminal service can directly subscribe to service information; through the service access interface, the service flow can directly initiate a service connection; through the service delivery interface, the service is directly dispatched to the service instance in the cloud computing resource pool; through the network service perception interface, the service can perceive the network capability in a fine-grained manner; through the orchestration strategy mapping interface, the service can efficiently orchestrate the network path. The disclosed embodiment can break the technical barriers between the terminal, network, and cloud, solve the problem of the separation of the terminal, network, and cloud, open up the channel between the network layer and the application layer, improve the interaction efficiency between the service and the network, and realize efficient interconnection between the three systems of terminal, network, and cloud.

[0126] In another embodiment of the present disclosure, an interaction method is provided for performing information interaction using the interaction interface in any of the above embodiments.

[0127] Figure 6 is a schematic diagram of the service interface management and the end-network-cloud interaction process in an embodiment of the present disclosure. As shown in Figure 6, the present disclosure uses the service identifier as a global index to perform service interface management for the end, network, and cloud.

[0128] In this embodiment, the end-network-cloud interaction process includes the following steps:

[0129] Step S601: registering a service interface through the cloud computing resource perception interface;

[0130] Step S602: conveying the computing network strategy through the computing network strategy mapping interface;

[0131] Step S603: calling (subscribing) the service through the computing network service calling interface;

[0132] Step S604: Business flow interaction is performed through the service access interface;

[0133] Step S605: Business flow interaction is performed through the service delivery interface.

[0134] In this embodiment, a service instance is deployed within the cloud computing resource pool. For example, the service instance provides service A (e.g., rendering service), with a service level of 2 (differentiated in various ways, such as 1 for HD, 2 for 8K, and 3 for 4K), a service gateway address of 10.1.1.1, port number 8080, 20-core CPUs, 400GB of memory, a maximum number of supported users of 200, and service requirements of 20ms latency and 20GB of bandwidth. The status is available.

[0135] In an exemplary embodiment, through step S601, the cloud computing resource pool carries information such as service attributes to register the service, registers the service interface through the cloud computing resource perception interface, filters the registration information, and assigns an interface index (for example: 1001) according to the service name A and service level 2. The interface index (i.e., service identifier) ​​1001 is associated with the corresponding service interface attributes (for example: 10.1.1.1, 40CPU, 400G, 20ms, etc.), and generates the service status attribute valid (available status).

[0136] For example, the service interface code obtained by registration is as follows:

[0137] In an exemplary embodiment, when assigning an interface index, if the interface index already exists, the original interface index is used, the corresponding service capability attributes in the service interface attributes are updated, and the service status attributes are recalculated. For example, if a new service gateway provides service A for 20.1.1.1, and the interface index calculated by the interface index is 1001, the service instance and corresponding interface attribute information are added to the service interface with interface index 1001.

[0138] For example, the updated service interface code is as follows:

[0139] In this embodiment, step S602 may specifically include: generating a computing network scheduling table or routing table associated with a service ID, interface attributes, and service requirements based on the computing network scheduling policy, and sending it to the network device. For example, service A provides services based on a resource priority policy, and based on a computing power metric, generates a computing network scheduling (routing) table with the service IP address 10.1.1.1 as the preferred service, as shown in Table 1 below:

[0140] Table 1

[0141] In this embodiment, step S603 may specifically include: the terminal application requests a cloud computing service from the cloud computing resource pool, obtains a service identifier based on the service type, and encapsulates the service identifier into a data packet of the service traffic. For example, if the terminal application requires service A, it requests an interface index (i.e., service identifier) ​​from the interface management party through the computing network service call interface, obtains interface index 1001 for service A, and records the allocated service resources in the interface attributes associated with the interface index.

[0142] In this embodiment, step S604 may specifically include: the terminal carries a service identifier in the service flow, the network identifies the service identifier, and queries the computing network scheduling table (such as Table 1). For example, the service identifier 1001 is carried in the service flow of the terminal application A service. After the network receives the service flow, it parses the service identifier 1001 carried in the flow message, queries and obtains the service gateway IP address 10.1.1.1 according to the scheduling policy and the computing network scheduling table, and the network device corresponding to the IP address forwards the service flow.

[0143] In this embodiment, step S605 may specifically include the network sending the service flow to the corresponding cloud computing resource pool. The service flow message carries the service identifier interface index. The network performs network policy scheduling based on the service identifier, and the flow reaches the cloud computing resource pool via the service gateway. Alternatively, the cloud computing resource pool may further identify the service instance providing the service based on the service identifier in the service flow. For example, the cloud resource pool receives a service flow from 10.1.1.1, identifies the service identifier as 1001, and delivers the traffic to the service instance providing service A.

[0144] In some embodiments, the interface attributes of the cloud computing resource perception interface can be updated according to the cloud computing services provided by the cloud computing resource pool. The interface index of the cloud computing resource perception interface is a service identifier, which can be associated with the service status provided by the service instance and the resource usage of the service. The service interface adds an available service instance when registering, and the interface status attribute (i.e., the service status attribute) is set to the available state; when the service instance is subscribed or revoked, it checks whether there is an available service instance. If there is no idle service instance, the interface status attribute is updated to unavailable; when the service is revoked, it is necessary to check and migrate the service in the used state. After the service is released, the service interface will be recycled, and the interface status attribute will be set to available, and the service can be used again. During the use of the service, not only can the changes in the interface status attributes be managed according to the use of the service, but the amount of service used can also be recorded, and the interface status attributes can be updated according to the difference between the remaining usage and the available threshold, so as to analyze whether the service can continue to be subscribed and used.

[0145] For example, the service gateway updates the service capabilities of the service instance of service A provided by 20.1.1.1, updates the service instance and corresponding interface attribute information in the service interface with interface index 1001, and recalculates the service status attributes. If there are available service resources, its interface status attribute is valid (available status).

[0146] In some embodiments, when the interface attributes of the cloud computing resource perception interface are updated, the interface attributes of the computing network policy mapping interface need to be updated simultaneously. For example, if service A updates its service capabilities, the metric value calculated from the computing power measurement changes, and the metric attributes of the computing network scheduling table mapped to the network are updated. When service A adds or removes service resources, entries are added or deleted from the computing network scheduling table mapped to the network.

[0147] In some embodiments, when receiving service update, revocation, and reclaim request information from a service instance, it is necessary to update the computing network mapping strategy, migrate the service instance, and update the interface attributes. If there is no valid and available service instance, the allocated service identification index is reclaimed. For example, if all resource pools providing service A request to revoke the provided service A, the service status attributes are calculated based on the revocation request. If there is no service resource in an available state under the interface index 1001, and the service status attributes are all unavailable (unavailable state), then a request is made to reclaim the service interface and its allocated interface index (service identification).

[0148] Through the embodiments disclosed herein, a service interface with a service identifier as a global index is designed, which implements service call access, service refined connection, and service-aware delivery based on the service identifier in the terminal, network, and cloud systems, thereby solving the problem in related technologies that terminals, networks, and cloud computing resource pools cannot achieve efficient interactive collaboration, and helps to build a unified service model that integrates terminals, networks, and clouds.

[0149] An embodiment of the present disclosure further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above method embodiments are executed.

[0150] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0151] An embodiment of the present disclosure further provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0152] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0153] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail here.

[0154] Obviously, those skilled in the art should understand that the modules or steps of the present disclosure described above can be implemented using a general-purpose computing device, they can be concentrated on a single computing device, or distributed across a network composed of multiple computing devices, they can be implemented using program code executable by the computing device, and thus, they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be performed in a different order than herein, or they can be fabricated into separate integrated circuit modules, or multiple modules or steps can be fabricated into a single integrated circuit module for implementation. Thus, the present disclosure is not limited to any particular combination of hardware and software.

[0155] The foregoing description is merely a preferred embodiment of the present disclosure and is not intended to limit the present disclosure. Those skilled in the art will readily appreciate that various modifications and variations of the present disclosure are possible. Any modifications, equivalent substitutions, or improvements made within the principles of the present disclosure shall be included within the scope of protection of the present disclosure.

Claims

1. An interaction interface, the interaction interface includes a first interface and a second interface, wherein, the first interface is used to perceive the business services provided by the network or the cloud computing resource pool, map the business services to service identifiers, and associate the scheduling policies corresponding to the business services to the service identifiers; the second interface is used to subscribe to the business services from the network or the cloud computing resource pool in the form of the service identifiers based on the service subscription requests of the terminals.

2. The interaction interface according to claim 1, wherein, the first interface is used to obtain the service attributes of the business services from the network or the cloud computing resource pool, and register service interfaces according to the service attributes, wherein the interface index of the service interfaces is the service identifier; the first interface is further used to generate scheduling policies corresponding to the business services according to the service attributes, and associate the scheduling policies corresponding to the business services to the service identifiers, wherein the scheduling policies are used to guide the scheduling of the business traffic of the terminals in the network.

3. The interaction interface according to claim 2, wherein, the second interface is used to obtain the service subscription requests from the terminals, allocate the service interfaces to the terminals according to the service subscription requests, and send the service identifiers corresponding to the service interfaces to the terminals, wherein the service interfaces are one of the multiple service interfaces registered by the network or the cloud computing resource pool, the service interfaces are used to provide the business services for the business traffic, and the business services are delivered based on the service identifiers.

4. The interactive interface according to claim 3, wherein The interaction interface further includes: a third interface; the third interface is used to transmit the business traffic carrying the service identifiers from the terminals to the network, determine the scheduling policies based on the service identifiers, and schedule the business traffic to the cloud computing resource pool or the network according to the scheduling policies to realize the delivery of the business services.

5. The interaction interface according to claim 2, wherein, the first interface includes a cloud computing resource perception interface and a computing network policy mapping interface; the cloud computing resource perception interface is used to perceive the cloud computing services provided by the cloud computing resource pool, obtain the cloud computing service attributes of the cloud computing services from the cloud computing resource pool, and register service interfaces according to the cloud computing service attributes, wherein the interface attributes of the service interfaces are the cloud computing service attributes; the computing network policy mapping interface is used to obtain the cloud computing service attributes from the cloud computing resource pool, determine the network scheduling policies corresponding to the cloud computing services according to the cloud computing service attributes, and associate the network scheduling policies to the service identifiers; wherein, the business services include the cloud computing services, the scheduling policies include the network scheduling policies, and the network scheduling policies are used to guide the scheduling of the business traffic in the network.

6. The interaction interface according to claim 5, wherein, The cloud computing resource perception interface is used to receive a service registration request of the cloud computing service from the cloud computing resource pool, where the service registration request carries the cloud computing service attributes, and the cloud computing service attributes at least include the service type; The cloud computing resource perception interface is further used to determine a unique service identifier according to the service type; judge whether the cloud computing service has been registered according to the service identifier; in the case that the cloud computing service has not been registered, add a corresponding service interface for the cloud computing service, use the service identifier as the interface index of the service interface, and use the cloud computing service attributes as the interface attributes of the service interface; in the case that the cloud computing service has been registered, update the service interface with the service identifier as the interface index according to the cloud computing service at tributes.

7. The interaction interface according to claim 5, wherein, The network scheduling policy includes at least one of the following: computing power metric value, target policy, network scheduling result; The computing-network policy mapping interface is used to obtain the cloud computing service attributes from the cloud computing resource pool based on the service identifier, generate a computing power metric value of the cloud computing service based on the cloud computing service attributes, and associate the computing power metric value with the service identifier; Or, The computing-network policy mapping interface is used to obtain the cloud computing service attributes from the cloud computing resource pool based on the service identifier, select a target policy from multiple preset policies based on the cloud computing service attributes, and associate the target policy with the service identifier; Or, The computing-network policy mapping interface is used to obtain the cloud computing service attributes from the cloud computing resource pool based on the service identifier, determine the computing power metric value and the target policy based on the cloud computing service attributes, perform network scheduling on the cloud computing service according to the computing power metric value and the target policy to obtain the network scheduling result, and associate the network scheduling result with the service identifier.

8. The interactive interface according to claim 7, wherein, The preset policies include at least one of the following: Experience priority policy, resource priority policy, network priority policy, cloud computing priority policy, balance policy.

9. The interaction interface according to claim 2, wherein, The first interface includes a network service opening interface and an orchestration policy mapping interface; The network service opening interface is used to perceive the network services provided by the network, obtain the network service attributes of the network services from the network, and register a service interface according to the network service attributes, where the interface attributes of the service interface are the network service attributes; The orchestration policy mapping interface is used to obtain the network service attributes from the network, orchestrate corresponding cloud computing scheduling policies for the cloud computing services in the cloud computing resource pool according to the network service attributes, and associate the cloud computing scheduling policies with the service identifier; Wherein, the business service includes the network service, the scheduling policy includes the cloud computing scheduling policy, and the cloud computing scheduling policy is used to indicate the network service provided by the network for the service traffic.

10. The interaction interface according to claim 9, wherein, The network service open interface is used to receive a service registration request of the network service from the network, where the service type is carried in the registration request, and the network service attribute at least includes the service type. The network service open interface is further configured to determine a unique service identifier according to the service type; determine whether the network service has been registered according to the service identifier; in the case where the network service has not been registered, add a corresponding service interface for the network service, use the service identifier as the interface index of the service interface, and use the network service attribute as the interface attribute of the service interface; in the case where the network service has been registered, update the service interface with the service identifier as the interface index according to the network service attribute.

11. The interaction interface according to claim 3, wherein The second interface includes a computing and networking service call interface. The computing and networking service call interface is configured to obtain the service subscription request sent by the terminal, and parse the service subscription request to obtain the service type of the service, where the service type is carried in the service subscription request. The computing and networking service call interface is further configured to allocate one of the service interfaces to the terminal according to the service type and the interface attributes of the multiple service interfaces, and send the service identifier corresponding to the service interface to the terminal to complete the subscription to the service.

12. The interaction interface according to claim 11, wherein The interface attribute of the service interface further includes a service status attribute, where the service status attribute includes an available state, an unavailable state, or a used state. The computing and networking service call interface is further configured to allocate a service interface with the same service type and in an available state to the terminal according to the service type and the interface attributes of the multiple service interfaces, and update the corresponding service status attribute to the used state after the subscription is completed.

13. The interaction interface according to claim 4, wherein The third interface includes a service access interface and a service delivery interface. The service access interface is configured to receive the service traffic carrying the service identifier sent by the terminal, and forward the service traffic to the network. The service delivery interface is configured to determine a cloud computing scheduling policy or a network scheduling policy based on the service identifier, schedule the service traffic to the cloud computing resource pool according to the cloud computing scheduling policy, or schedule the service traffic to the network according to the network scheduling policy, where the scheduling policy includes the cloud computing scheduling policy or the network scheduling policy.

14. The interaction interface according to any one of claims 2 to 13, wherein, The service attribute includes at least one of the following: service capability attribute, service demand attribute, service status attribute. The service capability attribute includes at least one of the following: service name, service type, service level, service gateway, service instance, service resource information, service processing information. The service demand attribute includes at least one of the following: bandwidth demand, latency demand, jitter demand, reliability demand, stability demand. The service status attribute includes: available state, unavailable state, or used state.

15. An interaction method for performing information interaction using the interaction interface described in any one of claims 1 to 14.

16. A computer-readable storage medium storing a computer program therein, wherein, When the computer program is run by a processor, the method described in claim 15 is executed.

17. An electronic device, comprising a memory and a processor, wherein, A computer program is stored in the memory, and the processor is configured to run the computer program to execute the method described in claim 15.

Images