CN113810438B - Service computing resource scheduling and requesting method, node equipment and terminal - Google Patents

Service computing resource scheduling and requesting method, node equipment and terminal Download PDF

Info

Publication number
CN113810438B
CN113810438B CN202010536025.9A CN202010536025A CN113810438B CN 113810438 B CN113810438 B CN 113810438B CN 202010536025 A CN202010536025 A CN 202010536025A CN 113810438 B CN113810438 B CN 113810438B
Authority
CN
China
Prior art keywords
service
information
computing power
terminal
resource demand
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010536025.9A
Other languages
Chinese (zh)
Other versions
CN113810438A (en
Inventor
付月霞
耿亮
姚惠娟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Mobile Communications Group Co Ltd, China Mobile Communications Ltd Research Institute filed Critical China Mobile Communications Group Co Ltd
Priority to CN202010536025.9A priority Critical patent/CN113810438B/en
Publication of CN113810438A publication Critical patent/CN113810438A/en
Application granted granted Critical
Publication of CN113810438B publication Critical patent/CN113810438B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5083Techniques for rebalancing the load in a distributed system

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The embodiment of the invention provides a scheduling and requesting method for service computing resources, node equipment and a terminal, wherein the method at the node equipment side comprises the following steps: acquiring resource demand information of a terminal, wherein the resource demand information comprises: service type information and/or computing power resource demand information of the terminal; and according to the resource demand information, dispatching service computing power resources for the terminal. The scheme of the invention can realize that the node equipment schedules the computing power resource required by the terminal for the terminal, thereby meeting the service requirement of the business.

Description

Service computing resource scheduling and requesting method, node equipment and terminal
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method for scheduling and requesting service computing resources, a node device, and a terminal.
Background
The application aware network, as shown in fig. 1, carries service requirement information including bandwidth, delay, jitter, packet loss rate, etc. when a service initiates a request, so that the network is aware of the service requirement.
On the other hand, to meet the computational demands of emerging services, another power aware network: the network is provided with computing power resources which need to be perceived and deployed ubiquitously, so that the manageability and the controllability of computing power are realized, and the cooperative scheduling of the network and the computing resources is realized.
Therefore, by combining the characteristics of application perception and calculation power perception, the service requirement information comprises the requirements for the network and the calculation power, and the service quality can be ensured when the requirements are met.
In addition, more and more applications are deployed in the form of micro services, in a micro service architecture, the applications are deconstructed into a plurality of micro services, on-demand, dynamic calling and instantiation are realized, an API Gateway (application program interface Gateway) is used as a Gateway of the micro service architecture, and the dispatching task of the micro services is completed after a service request is received. The implementation flow and mechanism of the existing micro-service registration are as follows: all micro-service addresses within the system are registered and managed by establishing a service registry. When a new micro-service is started, the registration information of the service registration center includes: service name and port number; the API Gateway can then query all micro-services in the system through the service registry. In addition, after registration is completed, the service can keep connection with the service registration center, heartbeat messages are sent regularly, and if the received messages are overtime, the instance is deleted to maintain the normal state of each service instance.
As shown in fig. 2, in the existing application-aware network, a service request packet only carries requirement information about the network, including bandwidth, delay and the like, and when the network selects an optimal network path for the service request, the service quality of a destination node cannot be known, or the service request of the service cannot be satisfied.
On the other hand, as shown in fig. 3, for the computing node, it does not sense the power demand information of the service, only knows the service information, such as the service identifier, etc., and therefore, after receiving the service request, it cannot perform internal computing resource scheduling and allocation, such as computing time, computing accuracy, power demand resource type, etc., according to the power demand of the service.
More specifically, for a cloud service node deployed with an API gateway+micro service architecture, there is no real-time, accurate perception of internal service computing power information, except for the imperceptibility of the service computing power demand information. The existing load balancing mechanism implementation flow is: after the API Gateway inquires service registration information from the service registration center, the API Gateway interacts with the micro-services in each list, sequentially inquires information such as the load of the micro-services, and performs load balancing according to a given mechanism.
The solutions in the prior art have at least the following problems:
problem 1: the API Gateway and each micro-service are subjected to interactive query in turn, so that the communication cost of the API Gateway is increased, and meanwhile, the process of query-response also increases the processing time delay of the service;
problem 2: the whole load balancing process does not consider the service requirement of the user, so that even if the load balancing is performed, the service requirement of the user is not always met.
Disclosure of Invention
The invention provides a scheduling and requesting method for service computing resources, node equipment and a terminal. The node equipment can schedule the computing power resource required by the terminal for the terminal, and the service requirement of the business is met.
In order to solve the technical problems, the embodiment of the invention provides the following scheme:
a method of scheduling service computing resources for a first node device, the method comprising:
acquiring resource demand information of a terminal, wherein the resource demand information comprises: service type information and/or computing power resource demand information of the terminal;
and according to the resource demand information, dispatching service computing power resources for the terminal.
Optionally, acquiring resource requirement information of the terminal includes:
receiving resource requirement information sent by a terminal through at least one second node device in a network, wherein the resource requirement information comprises: the service type information of the terminal and/or the computing power resource demand information obtained after the second node equipment is mapped according to the service type information sent by the terminal; or alternatively, the process may be performed,
and receiving the service type information and/or the computing power resource demand information of the terminal directly transmitted by the terminal.
Optionally, according to the resource requirement information, scheduling service computing power resources for the terminal includes:
acquiring service computing power resources of at least one micro service from a service registry;
and determining the service computing power resource matched with the resource demand information from the service computing power resources of the at least one micro service according to the resource demand information.
Optionally, the service computing power resource scheduling method further includes: the service registry obtains registration information of at least one micro service, the registration information including at least one of: at least one of service identification, port number, service load information, calculation metric information, processing delay, and message type;
and acquiring service computing power resources of the micro service according to the registration information of the micro service, wherein the service computing power resources comprise computing power quantity information.
Optionally, the message types include: registration packets or update packets.
Optionally, the resource requirement information is carried by a destination option header field in an extension header of the IPV 6.
The embodiment of the invention also provides a request method for serving the computing power resource, which is applied to the terminal and comprises the following steps:
transmitting resource requirement information to a first node device, wherein the resource requirement information comprises: service type information and/or computing power resource demand information of the terminal;
and receiving service computing power resources which are scheduled for the terminal by the first node equipment according to the resource demand information.
Optionally, sending the resource requirement information to the first node device includes:
transmitting service type information to second node equipment in a network, mapping the service type information into computing power resource demand information by the second node equipment, and transmitting the computing power resource demand information to the first node equipment through other node equipment in a path; the resource requirement information includes: service type information of the terminal and/or the computing power resource demand information; or alternatively, the process may be performed,
and directly sending the service type information and/or the computing power resource demand information of the terminal to the first node equipment.
Optionally, the resource requirement information is carried by a destination option header field in an extension header of the IPV 6.
The embodiment of the invention also provides a scheduling device for serving the computing power resource, which is applied to the first node equipment and comprises the following components:
the acquisition module is used for acquiring resource demand information of the terminal, wherein the resource demand information comprises: service type information and/or computing power resource demand information of the terminal;
and the processing module is used for scheduling service computing resources for the terminal according to the resource demand information.
The embodiment of the invention also provides node equipment, which comprises:
the transceiver is configured to obtain resource requirement information of a terminal, where the resource requirement information includes: service type information and/or computing power resource demand information of the terminal;
and the processor is used for scheduling service computing power resources for the terminal according to the resource demand information.
The embodiment of the invention also provides a request device for serving the computing power resource, which is applied to the terminal and comprises the following steps:
the transceiver module is configured to send resource requirement information to the first node device, where the resource requirement information includes: service type information and/or computing power resource demand information of the terminal; and receiving service computing power resources which are scheduled for the terminal by the first node equipment according to the resource demand information.
The embodiment of the invention also provides a terminal, which comprises:
a transceiver configured to send resource requirement information to a first node device, the resource requirement information comprising: service type information and/or computing power resource demand information of the terminal; and receiving service computing power resources which are scheduled for the terminal by the first node equipment according to the resource demand information.
The embodiment of the invention also provides a communication device, which comprises: a processor, a memory storing a computer program which, when executed by the processor, performs the method as described above.
Embodiments of the present invention also provide a computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform a method as described above.
The scheme of the invention at least comprises the following beneficial effects:
according to the scheme, the resource demand information of the terminal is acquired, and the resource demand information comprises: service type information and/or computing power resource demand information of the terminal; and according to the resource demand information, dispatching service computing power resources for the terminal. The node equipment can schedule the computing power resource required by the terminal for the terminal, and the service requirement of the business is met.
Drawings
FIG. 1 is a schematic diagram of an application aware network;
FIG. 2 is a schematic diagram of a power aware network;
FIG. 3 is a schematic diagram of business computing power requirements for network, computing power joint routing and delivery to computing nodes;
FIG. 4 is a flowchart of a method for scheduling service computing resources according to an embodiment of the present invention;
FIG. 5 is a diagram of a micro-service scheduling method for dynamically matching computing power requirements according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of an API gateway dynamically matching service requirements to implement micro-service scheduling in an embodiment of the invention;
FIG. 7 is a diagram illustrating the use of IPV6 Destination Options Header fields to carry computing power requirements to computing nodes in accordance with an embodiment of the present invention;
FIG. 8 is a schematic diagram illustrating different interfaces between a micro service and an API gateway according to an embodiment of the present invention;
FIG. 9 is a schematic diagram of registering service computing information of a service to be registered with a service registry through an HTTP POST in an embodiment of the present invention;
FIG. 10 is a schematic diagram of a registered service updating service computing information to a service registry in an embodiment of the present invention;
FIG. 11 is a functional schematic of a dynamic matching module according to an embodiment of the present invention;
fig. 12 is a flowchart of a method for requesting service of a computing power resource according to an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present invention may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
As shown in fig. 4, an embodiment of the present invention provides a scheduling method for service computing power resources, which is applied to a first node device, where the first node device may be a computing node in a network, that is, a node with computing power, and the method includes:
step 41, obtaining resource requirement information of a terminal, wherein the resource requirement information comprises: service type information and/or computing power resource demand information of the terminal;
and step 42, according to the resource demand information, service computing resources are scheduled for the terminal.
In this embodiment of the present invention, the computing power resource is information reflecting a ubiquitous deployment computing capability state and a deployment location in a network; the computing power resource includes at least one of: a number of service connections; CPU/GPU computing power; deploying a form; a deployment location; a storage capacity; storing the form; hash rate, etc. In this embodiment, the computing node may dynamically match the computing power resources of the corresponding micro service for the terminal according to the terminal resource requirement information, and satisfy the computing power requirement of the service through on-demand scheduling of the micro service.
In an alternative embodiment of the present invention, step 41 may include:
step 411, receiving resource requirement information sent by a terminal through at least one second node device in a network, where the resource requirement information includes: the service type information of the terminal and/or the computing power resource demand information obtained after the second node equipment is mapped according to the service type information sent by the terminal; or alternatively, the process may be performed,
and step 412, receiving the service type information and/or the computing power resource requirement information of the terminal directly sent by the terminal. Here, the terminal may also directly send the resource requirement information to the first node device. For example, the terminal with computing capability may send its own service type information and/or computing resource requirement information directly to the first node device.
In addition, as shown in fig. 5, the specific implementation process of step 411 is that the terminal carries service type information and computing power resource requirement information, where the service type information may be a specific service type identifier, for example, delay, quality of service, and computing power resource information required by the service; when the demand is mapped into the resource demand in the computing power perception+application perception network, and the network and the calculation joint route are completed, the service is routed to an optimal calculation node, and the service information and the computing power demand information are sent to an API gateway together; specifically, the service demand of the user or the terminal is mapped into computing power resource demand information in the terminal side or the network, and after the joint route is calculated through the network, the service request is scheduled to a certain computing node; the routing path here includes: the ingress router, namely the second node device, transmits the computing power resource requirement information to the egress router, namely the second node device through the other second node device R2 (namely the other router); and the exit router informs the computing node of the computing power resource demand information of the terminal, and the computing node needs to dynamically match the received computing power resource demand information with the self service computing power information to form a service providing strategy.
For example, in the network with power awareness capability shown in fig. 2, for the computing node deploying the API gateway+micro service framework, unlike the conventional API gateway which only receives service request information, the API gateway needs to dynamically match resource requirements with power information of internal micro services according to the received power resource requirement information, calculate a list of functional components capable of providing services for the service, and meet the power requirement of the service through on-demand scheduling of the micro services. The router shown in fig. 5 may be a node device in a computational effort routing layer in the network shown in fig. 2, and the computing nodes that serve the computational effort resources for dynamic matching of the terminals may be computing nodes in a computational effort service layer.
Here, as shown in fig. 7, the resource requirement information is carried through a destination option header field in the extension header of the IPV 6. The resource requirement information of the user needs to be carried together when sending the service request to the API gateway, and the power requirement information can be additionally carried to the destination node through the APN, for example, the power requirement information can be carried through Destination Options Header (destination option header) in the extension header (Extension Headers) of the IPV6, and the information carried in the Destination Options Header field is information that needs to be read by the computing node, and the field will be checked after reaching the computing node.
In an alternative embodiment of the present invention, the computing node may include: an API gateway, a service registry, and a plurality of micro services; step 42 may include:
step 421, obtaining service computing power resources of at least one micro service from a service registry;
step 422, determining, from the service computing resources of the at least one micro service, a service computing resource matching the resource requirement information according to the resource requirement information.
As shown in fig. 5, for the API gateway, it needs to know the calculation power information of each micro service component, so that the micro service reports the service calculation power information to the service registry, and the service registry maintains the deployment location information and calculation power information of each micro service at the same time, and updates the service calculation power information periodically.
When the API gateway initiates service inquiry, the service registration center sends the required service calculation information to the API gateway, the calculation power resource requirement of the service and the calculation power information of the required service are dynamically matched by the API gateway, and calculation is carried out through the dynamic matching module to form a service scheduling strategy and access the service.
As shown in fig. 6, the dynamic matching module includes a computing power information receiving module, an algorithm module and an information output module, wherein the algorithm module can dynamically select an algorithm according to parameters, and finally form a service access policy.
In an alternative embodiment of the present invention, the method for scheduling service computing resources further includes:
step 423, the service registry obtains registration information of at least one micro service, where the registration information includes at least one of: at least one of service identification, port number, service load information, calculation metric information, processing delay, and message type; here, the registration information of the micro service may be carried through an HTTP POST BODY field. Of course, the registration information of the micro service can also be carried by fields of other protocols, not limited to the fields of the HTTP protocol; optionally, the message types include: registration packets or update packets.
Step 424, obtaining service computing power resources of the micro service according to the registration information of the micro service, wherein the service computing power resources comprise computing power quantity information.
As shown in fig. 8, there are various methods for reporting service computing resources of the micro service to the service registry, and depending on an interface protocol between API gateways, if an HTTP protocol is used, service computing information may be carried in an HTTP POST BODY, including, but not limited to, a service identifier, a port number, service load information, computing strength information, a processing delay, a message type, etc., as shown in fig. 9, where a "message type" field is used to indicate whether a packet type is a service registration packet or an information update packet.
In addition, the micro service needs to update service computing power information, as shown in fig. 10, and similarly, the updated service computing power information is carried according to an interface protocol between the micro service and the API gateway, for example, the update information can be carried in a body through an HTTP POST packet, and the packet is indicated as an information update packet through an "information type" field.
As shown in fig. 11, after the API Gateway receives the service request and the resource request, the service registry is queried to obtain the deployment location and calculation information of the corresponding micro service, and the dynamic matching module generates the micro service scheduling policy and accesses the micro service scheduling policy to ensure the service requirement.
In an alternative embodiment of the present invention, the method for scheduling service computing resources further includes:
and step 43, returning the result of the service computing resources scheduled for the terminal to the terminal. Specifically, for example, the functional components of the micro-service may be returned to the terminal to satisfy the business needs of the user.
In the embodiment of the invention, the calculation force requirement of the service is transmitted to the calculation node, so that the service calculation requirement of the user can be ensured; the computing power information of the micro-service is registered to the service registration center in advance, so that the state query cost and time delay of the micro-service and the API gateway are reduced, and the service deployment position, the corresponding load, computing power and time delay information can be obtained by one query of the API gateway; the service registration center realizes the registration and update of the micro service computing power information by transmitting the demand information to the computing node deployed with the micro service architecture, and the API gateway performs dynamic scheduling of the micro service by combining the service resource demand and the micro service computing power information.
As shown in fig. 12, an embodiment of the present invention further provides a method for requesting service computing power resources, which is applied to a terminal, and the method includes:
step 121, sending resource requirement information to the first node device, where the resource requirement information includes: service type information and/or computing power resource demand information of the terminal; the first node device here may be a computing node;
and step 122, receiving service computing power resources scheduled for the terminal by the first node equipment according to the resource demand information.
In this embodiment of the present invention, the computing power resource is information reflecting a ubiquitous deployment computing capability state and a deployment location in a network; the computing power resource includes at least one of: a number of service connections; CPU/GPU computing power; deploying a form; a deployment location; a storage capacity; storing the form; hash rate, etc. In this embodiment, the computing node may dynamically match the computing power resources of the corresponding micro service for the terminal according to the terminal resource requirement information, and satisfy the computing power requirement of the service through on-demand scheduling of the micro service. The resource requirement information is carried by a destination option header field in the extension header of the IPV 6. The resource requirement information of the user needs to be carried together when sending the service request to the API gateway, and the power requirement information can be additionally carried to the destination node through the APN, for example, the power requirement information can be carried through Destination Options Header (destination option header) in the extension header (Extension Headers) of the IPV6, and the information carried in the Destination Options Header field is information that needs to be read by the computing node, and the field will be checked after reaching the computing node.
In an alternative embodiment of the present invention, step 121 may include:
step 1211, sending service type information to a second node device in the network, mapping the service type information into computing power resource demand information by the second node device, and sending the computing power resource demand information to the first node device through other node devices in the path; the resource requirement information includes: service type information of the terminal and/or the computing power resource demand information; or alternatively, the process may be performed,
step 1212, directly sending service type information and/or computing power resource requirement information of the terminal to the first node device. The terminal can also directly send the resource demand information to the computing node, so that the computing node can dynamically match corresponding service computing power resources for the terminal according to the resource demand information of the terminal.
In an alternative embodiment of the present invention, the resource requirement information is carried by a destination option header field in the extension header of IPV 6.
The method described in this embodiment is a method on the terminal side corresponding to the method shown in fig. 4, and all the implementation manners in the above embodiment are applicable to this embodiment, so that the same technical effects can be achieved.
The embodiment of the invention also provides a scheduling device for serving the computing power resource, which is applied to the first node equipment and comprises the following components:
the acquisition module is used for acquiring resource demand information of the terminal, wherein the resource demand information comprises: service type information and/or computing power resource demand information of the terminal;
and the processing module is used for scheduling service computing resources for the terminal according to the resource demand information.
Optionally, the acquiring module is specifically configured to: receiving resource requirement information sent by a terminal through at least one second node device in a network, wherein the resource requirement information comprises: the service type information of the terminal and/or the computing power resource demand information obtained after the second node equipment is mapped according to the service type information sent by the terminal; or receiving service type information and/or computing power resource demand information of the terminal directly sent by the terminal.
Optionally, according to the resource requirement information, scheduling service computing power resources for the terminal includes:
acquiring service computing power resources of at least one micro service from a service registry;
and determining the service computing power resource matched with the resource demand information from the service computing power resources of the at least one micro service according to the resource demand information.
Optionally, the service computing power resource scheduling method further includes: the service registry obtains registration information of at least one micro service, the registration information including at least one of: at least one of service identification, port number, service load information, calculation metric information, processing delay, and message type;
and acquiring service computing power resources of the micro service according to the registration information of the micro service, wherein the service computing power resources comprise computing power quantity information.
Optionally, the registration information of the micro service is carried by an HTTP POST BODY field.
Optionally, the message types include: registration packets or update packets.
Optionally, the resource requirement information is carried by a destination option header field in an extension header of the IPV 6.
Optionally, the service computing power resource scheduling method further includes: and returning the service computing power resources scheduled for the terminal to the terminal.
The method described in this embodiment is a device corresponding to the method shown in fig. 4, and all the implementation manners in the method embodiment described above are applicable to this embodiment, so that the same technical effects can be achieved.
The embodiment of the invention also provides node equipment, which comprises:
the transceiver is configured to obtain resource requirement information of a terminal, where the resource requirement information includes: service type information and/or computing power resource demand information of the terminal;
and the processor is used for scheduling service computing power resources for the terminal according to the resource demand information.
Optionally, acquiring resource requirement information of the terminal includes:
receiving resource requirement information sent by a terminal through at least one second node device in a network, wherein the resource requirement information comprises: the service type information of the terminal and/or the computing power resource demand information obtained after the second node equipment is mapped according to the service type information sent by the terminal; or alternatively, the process may be performed,
and receiving the service type information and/or the computing power resource demand information of the terminal directly transmitted by the terminal.
Optionally, according to the resource requirement information, scheduling service computing power resources for the terminal includes:
acquiring service computing power resources of at least one micro service from a service registry;
and determining the service computing power resource matched with the resource demand information from the service computing power resources of the at least one micro service according to the resource demand information.
Optionally, the service computing power resource scheduling method further includes: the service registry obtains registration information of at least one micro service, the registration information including at least one of: at least one of service identification, port number, service load information, calculation metric information, processing delay, and message type;
and acquiring service computing power resources of the micro service according to the registration information of the micro service, wherein the service computing power resources comprise computing power quantity information.
Optionally, the registration information of the micro service is carried by an HTTP POST BODY field.
Optionally, the message types include: registration packets or update packets.
Optionally, the resource requirement information is carried by a destination option header field in an extension header of the IPV 6.
Optionally, the service computing power resource scheduling method further includes: and returning the service computing power resources scheduled for the terminal to the terminal.
The method described in this embodiment is a device corresponding to the method shown in fig. 4, and all the implementation manners in the method embodiment described above are applicable to this embodiment, so that the same technical effects can be achieved.
The embodiment of the invention also provides a request device for serving the computing power resource, which is applied to the terminal and comprises the following steps:
the transceiver module is configured to send resource requirement information to the first node device, where the resource requirement information includes: service type information and/or computing power resource demand information of the terminal; and receiving service computing power resources which are scheduled for the terminal by the first node equipment according to the resource demand information.
Optionally, sending the resource requirement information to the first node device includes:
transmitting service type information to second node equipment in a network, mapping the service type information into computing power resource demand information by the second node equipment, and transmitting the computing power resource demand information to the first node equipment through other node equipment in a path; the resource requirement information includes: service type information of the terminal and/or the computing power resource demand information; or alternatively, the process may be performed,
and directly sending the service type information and/or the computing power resource demand information of the terminal to the first node equipment.
Optionally, the resource requirement information is carried by a destination option header field in an extension header of the IPV 6.
The method described in this embodiment is a device corresponding to the method shown in fig. 12, and all the implementation manners in the method embodiment described above are applicable to this embodiment, so that the same technical effects can be achieved.
The embodiment of the invention also provides a terminal, which comprises:
a transceiver configured to send resource requirement information to a first node device, the resource requirement information comprising: service type information and/or computing power resource demand information of the terminal; and receiving service computing power resources which are scheduled for the terminal by the first node equipment according to the resource demand information.
Optionally, sending the resource requirement information to the first node device includes:
transmitting service type information to second node equipment in a network, mapping the service type information into computing power resource demand information by the second node equipment, and transmitting the computing power resource demand information to the first node equipment through other node equipment in a path; the resource requirement information includes: service type information of the terminal and/or the computing power resource demand information; or alternatively, the process may be performed,
and directly sending the service type information and/or the computing power resource demand information of the terminal to the first node equipment.
Optionally, the resource requirement information is carried by a destination option header field in an extension header of the IPV 6.
The method described in this embodiment is a device corresponding to the method shown in fig. 12, and all the implementation manners in the method embodiment described above are applicable to this embodiment, so that the same technical effects can be achieved.
The embodiment of the invention also provides a communication device, which comprises: a processor, a memory storing a computer program which, when executed by the processor, performs the method as described above. All the implementation manners in the method embodiment are applicable to the embodiment, and the same technical effect can be achieved.
Embodiments of the present invention also provide a computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform a method as described above. All the implementation manners in the method embodiment are applicable to the embodiment, and the same technical effect can be achieved.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.
Furthermore, it should be noted that in the apparatus and method of the present invention, it is apparent that the components or steps may be disassembled and/or assembled. Such decomposition and/or recombination should be considered as equivalent aspects of the present invention. Also, the steps of performing the series of processes described above may naturally be performed in chronological order in the order of description, but are not necessarily performed in chronological order, and some steps may be performed in parallel or independently of each other. It will be appreciated by those of ordinary skill in the art that all or any of the steps or components of the methods and apparatus of the present invention may be implemented in hardware, firmware, software, or a combination thereof in any computing device (including processors, storage media, etc.) or network of computing devices, as would be apparent to one of ordinary skill in the art after reading this description of the invention.
The object of the invention can thus also be achieved by running a program or a set of programs on any computing device. The computing device may be a well-known general purpose device. The object of the invention can thus also be achieved by merely providing a program product containing program code for implementing said method or apparatus. That is, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. It is apparent that the storage medium may be any known storage medium or any storage medium developed in the future. It should also be noted that in the apparatus and method of the present invention, it is apparent that the components or steps may be disassembled and/or assembled. Such decomposition and/or recombination should be considered as equivalent aspects of the present invention. The steps of executing the series of processes may naturally be executed in chronological order in the order described, but are not necessarily executed in chronological order. Some steps may be performed in parallel or independently of each other.
While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that various modifications and adaptations can be made without departing from the principles of the present invention, and such modifications and adaptations are intended to be comprehended within the scope of the present invention.

Claims (13)

1. A method for scheduling service computing resources, applied to a first node device, the method comprising:
acquiring resource demand information of a terminal, wherein the resource demand information comprises: service type information and/or computing power resource demand information of the terminal;
according to the resource demand information, dispatching service computing power resources for the terminal;
according to the resource demand information, scheduling service computing power resources for the terminal, including:
acquiring service computing power resources of at least one micro service from a service registry;
determining service computing power resources matched with the resource demand information from the service computing power resources of the at least one micro service according to the resource demand information;
the method further comprises the steps of: the service registry obtains registration information of at least one micro service, the registration information including at least one of: at least one of service identification, port number, service load information, calculation metric information, processing delay, and message type;
and acquiring service computing power resources of the micro service according to the registration information of the micro service, wherein the service computing power resources comprise computing power quantity information.
2. The method for scheduling service computing power resources according to claim 1, wherein obtaining resource demand information of a terminal comprises:
receiving resource requirement information sent by a terminal through at least one second node device in a network, wherein the resource requirement information comprises: the service type information of the terminal and/or the computing power resource demand information obtained after the second node equipment is mapped according to the service type information sent by the terminal; or alternatively, the process may be performed,
and receiving the service type information and/or the computing power resource demand information of the terminal directly transmitted by the terminal.
3. The method of scheduling service computing resources of claim 1, wherein the message type comprises: registration packets or update packets.
4. The method for scheduling service computing resources according to claim 1, wherein the resource requirement information is carried by a destination option header field in an extension header of IPV 6.
5. A method for requesting a service computing resource, the method being applied to a terminal, the method comprising:
transmitting resource requirement information to a first node device, wherein the resource requirement information comprises: service type information and/or computing power resource demand information of the terminal;
receiving service computing power resources which are scheduled for the terminal by the first node equipment according to the resource demand information;
the first node device scheduling service computing power resources for the terminal according to the resource demand information includes:
acquiring service computing power resources of at least one micro service from a service registry;
determining service computing power resources matched with the resource demand information from the service computing power resources of the at least one micro service according to the resource demand information;
the service registry obtains registration information of at least one micro service, the registration information including at least one of: at least one of service identification, port number, service load information, calculation metric information, processing delay, and message type;
and acquiring service computing power resources of the micro service according to the registration information of the micro service, wherein the service computing power resources comprise computing power quantity information.
6. The method of claim 5, wherein sending the resource requirement information to the first node device comprises:
transmitting service type information to second node equipment in a network, mapping the service type information into computing power resource demand information by the second node equipment, and transmitting the computing power resource demand information to the first node equipment through other node equipment in a path; the resource requirement information includes: service type information of the terminal and/or the computing power resource demand information; or alternatively, the process may be performed,
and directly sending the service type information and/or the computing power resource demand information of the terminal to the first node equipment.
7. The method of claim 5, wherein the resource requirement information is carried by a destination option header field in an extension header of IPV 6.
8. A scheduling apparatus for serving computing resources, the apparatus being adapted for use with a first node device, the apparatus comprising:
the acquisition module is used for acquiring resource demand information of the terminal, wherein the resource demand information comprises: service type information and/or computing power resource demand information of the terminal;
the processing module is used for scheduling service computing resources for the terminal according to the resource demand information;
the step of scheduling service computing power resources for the terminal according to the resource demand information comprises the following steps:
acquiring service computing power resources of at least one micro service from a service registry;
determining service computing power resources matched with the resource demand information from the service computing power resources of the at least one micro service according to the resource demand information;
the service registry obtains registration information of at least one micro service, the registration information including at least one of: at least one of service identification, port number, service load information, calculation metric information, processing delay, and message type;
and acquiring service computing power resources of the micro service according to the registration information of the micro service, wherein the service computing power resources comprise computing power quantity information.
9. A node device, comprising:
the transceiver is configured to obtain resource requirement information of a terminal, where the resource requirement information includes: service type information and/or computing power resource demand information of the terminal;
the processor is used for scheduling service computing power resources for the terminal according to the resource demand information;
the step of scheduling service computing power resources for the terminal according to the resource demand information comprises the following steps:
acquiring service computing power resources of at least one micro service from a service registry;
determining service computing power resources matched with the resource demand information from the service computing power resources of the at least one micro service according to the resource demand information;
wherein the service registry obtains registration information of at least one micro service, the registration information including at least one of: at least one of service identification, port number, service load information, calculation metric information, processing delay, and message type;
and acquiring service computing power resources of the micro service according to the registration information of the micro service, wherein the service computing power resources comprise computing power quantity information.
10. A request device for serving an computing resource, the device being applied to a terminal, the device comprising:
the transceiver module is configured to send resource requirement information to the first node device, where the resource requirement information includes: service type information and/or computing power resource demand information of the terminal; receiving service computing power resources which are scheduled for the terminal by the first node equipment according to the resource demand information;
the first node device scheduling service computing power resources for the terminal according to the resource demand information includes:
acquiring service computing power resources of at least one micro service from a service registry;
determining service computing power resources matched with the resource demand information from the service computing power resources of the at least one micro service according to the resource demand information;
the service registry obtains registration information of at least one micro service, the registration information including at least one of: at least one of service identification, port number, service load information, calculation metric information, processing delay, and message type;
and acquiring service computing power resources of the micro service according to the registration information of the micro service, wherein the service computing power resources comprise computing power quantity information.
11. A terminal, comprising:
a transceiver configured to send resource requirement information to a first node device, the resource requirement information comprising: service type information and/or computing power resource demand information of the terminal; receiving service computing power resources which are scheduled for the terminal by the first node equipment according to the resource demand information;
the first node device scheduling service computing power resources for the terminal according to the resource demand information includes:
acquiring service computing power resources of at least one micro service from a service registry;
determining service computing power resources matched with the resource demand information from the service computing power resources of the at least one micro service according to the resource demand information;
the service registry obtains registration information of at least one micro service, the registration information including at least one of: at least one of service identification, port number, service load information, calculation metric information, processing delay, and message type;
and acquiring service computing power resources of the micro service according to the registration information of the micro service, wherein the service computing power resources comprise computing power quantity information.
12. A communication device, comprising: a processor, a memory storing a computer program which, when executed by the processor, performs the method of any one of claims 1 to 4 or any one of claims 5 to 7.
13. A computer readable storage medium comprising instructions which, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 4 or 5 to 7.
CN202010536025.9A 2020-06-12 2020-06-12 Service computing resource scheduling and requesting method, node equipment and terminal Active CN113810438B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010536025.9A CN113810438B (en) 2020-06-12 2020-06-12 Service computing resource scheduling and requesting method, node equipment and terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010536025.9A CN113810438B (en) 2020-06-12 2020-06-12 Service computing resource scheduling and requesting method, node equipment and terminal

Publications (2)

Publication Number Publication Date
CN113810438A CN113810438A (en) 2021-12-17
CN113810438B true CN113810438B (en) 2023-05-23

Family

ID=78892138

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010536025.9A Active CN113810438B (en) 2020-06-12 2020-06-12 Service computing resource scheduling and requesting method, node equipment and terminal

Country Status (1)

Country Link
CN (1) CN113810438B (en)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114828039A (en) * 2021-01-21 2022-07-29 维沃移动通信有限公司 Data transmission method, terminal and network side equipment
CN115714785A (en) * 2021-08-18 2023-02-24 维沃移动通信有限公司 Method and equipment for determining computing power resource
CN116938837A (en) * 2022-04-01 2023-10-24 中国移动通信有限公司研究院 Resource scheduling method, device and equipment
CN114785851B (en) * 2022-04-20 2024-01-09 中国电信股份有限公司 Resource call processing method and device, storage medium and electronic equipment
CN117098098A (en) * 2022-05-12 2023-11-21 上海诺基亚贝尔股份有限公司 Apparatus, method, device, and medium for a computing network
CN114884862A (en) * 2022-06-06 2022-08-09 中国联合网络通信集团有限公司 Terminal service processing method and device
CN115277598B (en) * 2022-06-20 2024-04-02 中国联合网络通信集团有限公司 Method and device for scheduling computing power resources and computer readable storage medium
CN115118784A (en) * 2022-06-30 2022-09-27 中国电信股份有限公司 Computing resource scheduling method, device and system
CN115550452B (en) * 2022-09-30 2024-04-16 中国联合网络通信集团有限公司 Data processing method, power computing equipment and communication system
CN115580539A (en) * 2022-10-13 2023-01-06 联通(广东)产业互联网有限公司 Network computing storage scheduling method, system and equipment based on artificial intelligence scene

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110532092A (en) * 2019-08-21 2019-12-03 云湾科技(嘉兴)有限公司 Reso urce matching method, device and equipment

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103501347B (en) * 2013-10-14 2016-08-10 中国联合网络通信集团有限公司 Resource allocation methods and device
CN109358965B (en) * 2018-09-25 2022-01-11 杭州朗和科技有限公司 Cloud computing cluster resource scheduling method, medium, device and computing equipment
CN111240836A (en) * 2020-01-06 2020-06-05 北京百度网讯科技有限公司 Computing resource management method and device, electronic equipment and storage medium

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110532092A (en) * 2019-08-21 2019-12-03 云湾科技(嘉兴)有限公司 Reso urce matching method, device and equipment

Also Published As

Publication number Publication date
CN113810438A (en) 2021-12-17

Similar Documents

Publication Publication Date Title
CN113810438B (en) Service computing resource scheduling and requesting method, node equipment and terminal
EP3748908B1 (en) Method, system, network device, storage medium for creating a network slice
CN108989372A (en) Method, registration center and the equipment of service discovery
CN113841432A (en) Method and apparatus for providing connection with terminal for using edge computing service
US10231163B2 (en) Efficient centralized resource and schedule management in time slotted channel hopping networks
US20080008091A1 (en) Qos CONTROL SYSTEM
US11963124B2 (en) Entities for providing an external service to a network
RU2687128C1 (en) Method and system for disclosing information of possibility and function object of disclosing information of possibility
US11700301B2 (en) Service registration based on service capabilities requirements and preferences
EP3057287A1 (en) Node allocation method, device and system
CN106464670B (en) Network entity and service strategy management method
CN106102022B (en) Transfer control method and system based on bottom-layer network characteristic
CN113810442B (en) Resource reservation method, device, terminal and node equipment
CN115226073A (en) Message forwarding method, device and system and computer readable storage medium
CN102316086A (en) Relay method for service data and relay node system
CN103560937A (en) Data accessing method and entry server
CN110602264A (en) Method, apparatus, device and medium for transferring domain name resolution address weight information
JP5894981B2 (en) Accessing a network of nodes distributed across a communication architecture using a topology server with multiple criteria selection
CN112584373B (en) Event subscription method and device
KR100812680B1 (en) Interprocessor communication protocol providing guaranteed quality of service and selective broadcasting
CN116074365A (en) Method and device for establishing connection, storage medium and electronic device
CN114079974A (en) Network capability opening method and device, UPF entity and CPE network element
JP2004343462A (en) Network measurement control system
KR100522715B1 (en) System for managing digital home service, and management method thereof
CN114553965B (en) Scheduling method of intranet equipment, network equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant