CN108683730B - Resource scheduling method, service server, client terminal, network system and medium - Google Patents
Resource scheduling method, service server, client terminal, network system and medium Download PDFInfo
- Publication number
- CN108683730B CN108683730B CN201810453585.0A CN201810453585A CN108683730B CN 108683730 B CN108683730 B CN 108683730B CN 201810453585 A CN201810453585 A CN 201810453585A CN 108683730 B CN108683730 B CN 108683730B
- Authority
- CN
- China
- Prior art keywords
- service
- node
- server
- node device
- client
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
Abstract
本发明公开了资源调度方法、业务服务器、客户终端、网络系统和介质，方法包括客户服务器发送业务请求至业务服务器；业务服务器根据业务请求确定目标节点设备；业务服务器生成节点分发信息；客户服务器从业务服务器获取节点分发信息；客户服务器从业务服务器获取节点分发信息后，根据节点分发信息向目标节点设备分发数据。通过业务服务器对各节点设备的状态、能力等进行统计，并根据客户服务器的业务请求确定可用于客户服务器存储数据的节点设备；使客户服务器可以借助海量节点设备的存储能力和带宽为客户终端提供更快的数据下载等服务；进一步业务服务器还可以根据从客户终端获取的服务贡献信息宏观调度数据资源。
The invention discloses a resource scheduling method, a service server, a client terminal, a network system and a medium. The method comprises the following steps: the client server sends a service request to the service server; the service server determines a target node device according to the service request; the service server generates node distribution information; The service server acquires the node distribution information; after acquiring the node distribution information from the service server, the client server distributes data to the target node device according to the node distribution information. The status and capabilities of each node device are counted through the service server, and the node devices that can be used to store data on the client server are determined according to the service request of the client server; so that the client server can use the storage capacity and bandwidth of a large number of node devices to provide client terminals with Faster data download and other services; further, the business server can also macroscopically schedule data resources according to the service contribution information obtained from the client terminal.
Description
Technical Field
The present invention relates to network technologies, and in particular, to a resource scheduling method, a service server, a client terminal, a network system, and a medium.
Background
In recent years, a multi-source download technology represented by two modes of P2P and P2P and client/Server (P2SP, Peer to Server and Peer) networking has been widely adopted. The multi-source download is a data download method for simultaneously and concurrently downloading target files from a plurality of file sources in a network. However, in the existing network system, the nodes on which data is stored cannot be controlled, so that certain data may exist only on isolated node devices and cannot provide stable data for users; data may also be forwarded randomly in each node network, wasting a lot of storage resources and network resources.
Disclosure of Invention
In order to overcome the defects of the prior art, one of the objectives of the present invention is to provide a resource scheduling method for a service server, which can solve the problem that in the existing network system, data is stored in which nodes cannot be controlled, and therefore, some data may exist only in isolated node devices and cannot provide stable data for users; and data can be randomly forwarded in each node network, so that a large amount of storage resources and network resources are wasted.
The second objective of the present invention is to provide a resource scheduling method for a client terminal, which can solve the problem that in the existing network system, data is stored in which nodes cannot be controlled, so that there may be some data only existing in isolated node devices, and stable data cannot be provided for users; and data can be randomly forwarded in each node network, so that a large amount of storage resources and network resources are wasted.
The third purpose of the present invention is to provide a service server, which can solve the problem that in the existing network system, data is stored in which nodes cannot be controlled, so that some data may exist only in isolated node devices, and stable data cannot be provided for users; and data can be randomly forwarded in each node network, so that a large amount of storage resources and network resources are wasted.
The fourth purpose of the present invention is to provide a client terminal, which can solve the problem that in the existing network system, data is stored in which nodes cannot be controlled, so that some data may exist only in isolated node devices, and stable data cannot be provided for users; and data can be randomly forwarded in each node network, so that a large amount of storage resources and network resources are wasted.
The fifth objective of the present invention is to provide a network system, which can solve the problem that in the existing network system, data is stored in which nodes cannot be controlled, so that some data may exist only in isolated node devices, and stable data cannot be provided for users; and data can be randomly forwarded in each node network, so that a large amount of storage resources and network resources are wasted.
The sixth objective of the present invention is to provide a medium storing a computer program, which can solve the problem that in the existing network system, data is stored in which nodes cannot be controlled, so that some data may exist only in isolated node devices, and stable data cannot be provided for users; and data can be randomly forwarded in each node network, so that a large amount of storage resources and network resources are wasted.
One of the purposes of the invention is realized by adopting the following technical scheme:
the resource scheduling method is used for a service server, and comprises the following steps:
acquiring a service request sent by a client server;
determining at least one node device as a target node device according to the service request;
generating node distribution information, wherein the node distribution information comprises the network address of the target node equipment;
and sending the node distribution information to the client server to enable the client server to distribute the data to the target node device.
Further, the node distribution information further includes an extension instruction corresponding to the target node device;
the sending of the node distribution information to the client server to enable the client server to distribute data to the target node device specifically includes:
and sending the node distribution information to the client server to enable the client server to distribute the data and the extension instruction corresponding to the target node device.
Further, the service request includes the number of required nodes, and the number of target node devices in the node distribution information is smaller than the number of required nodes.
Further, the service request further includes a node condition requirement, and the node condition requirement includes at least one of a storage space, a node bandwidth, and a geographical distribution.
Further, the extension instruction comprises hop count requirement information and/or region requirement information, and forwarding count information.
Further, the resource scheduling method further includes the following steps:
acquiring service contribution information from a client terminal, wherein a service plug-in used for interacting with the service server is arranged in the client terminal;
and if the service contribution information meets the node expansion condition, sending a second expansion notice to the client server so that the client server sends a new service request to the service server.
Further, before obtaining the service contribution information from the client terminal, the method further includes the following steps:
obtaining a data request from the client terminal;
determining at least one source node device according to the data request, wherein the source node device stores the data requested by the client terminal;
and sending the information of the source node equipment to the client terminal so that the client terminal acquires data from the source node equipment through the client plug-in.
Further, the service contribution information includes node contribution information of at least one source node device to the client terminal.
Further, the node contribution information includes a transmission duration of the source node device, and the node extension condition includes: at least one source node device has a transmission duration greater than a time threshold.
Further, the node contribution information includes a contribution frequency of the source node device, and the node extension condition includes: at least one source node device contributes more frequently than a frequency threshold.
The second purpose of the invention is realized by adopting the following technical scheme:
the resource scheduling method is used for a client terminal, and a service plug-in used for interacting with a service server is arranged in the client terminal; the resource scheduling method comprises the following steps:
obtaining data from at least one source node device, the source node device storing the data;
counting service contribution information of the at least one source node device through the service plug-in;
sending the service contribution information to the service server so that the service server judges whether to inform a client server of sending a new service request; and/or
And sending the service contribution information to the client server so that the client server judges whether to send a new service request to the service server.
Further, after the service contribution information of the at least one source node device is counted by the service plug-in, the method further includes the following steps:
and if the service contribution information meets the node expansion condition, sending a first expansion notice to the client server so that the client server sends a new service request to the service server.
Further, the service contribution information includes node contribution information of the at least one source node device to the client terminal
Further, the node contribution information includes a transmission duration of the source node device, and the node extension condition includes: at least one source node device has a transmission duration greater than a time threshold.
Further, the node contribution information includes a contribution frequency of the source node device, and the node extension condition includes: at least one source node device contributes more frequently than a frequency threshold.
The third purpose of the invention is realized by adopting the following technical scheme:
a service server comprising a memory, a processor and a program stored in the memory, the program being configured to be executed by the processor, the processor implementing the steps of the resource scheduling method described above when executing the program.
The fourth purpose of the invention is realized by adopting the following technical scheme:
a client terminal comprising a memory, a processor and a program stored in the memory, the program being configured to be executed by the processor, the processor when executing the program implementing the steps of the resource scheduling method described above.
The fifth purpose of the invention is realized by adopting the following technical scheme:
the network system comprises the service server, the client terminal, the client server and a plurality of node devices; the service server and the client server are in communication connection with each node device, the service server is in communication connection with the client server, and the client terminal is used for acquiring data from the node devices.
The sixth purpose of the invention is realized by adopting the following technical scheme:
a medium storing a computer program which, when executed by a processor, implements the steps of the above-described resource scheduling method.
Compared with the prior art, the embodiment of the invention has the beneficial effects that: the online state, the hardware capability, the network capability and the like of each node device are counted through the service server, and the node devices which can be used for the client server to store data are determined according to the service request of the client server; therefore, the service server can provide support for the client server, so that the service server can provide services such as faster data downloading and the like for the client terminal by means of the storage capacity and bandwidth of the mass node equipment; further, the service server can also macroscopically schedule the data resources according to the service contribution information acquired from the client terminal.
Drawings
Fig. 1 is a schematic structural diagram of a network system according to a first embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a service server and a client server in FIG. 1;
fig. 3 is a flowchart illustrating a resource scheduling method according to a second embodiment of the present invention;
FIG. 4 is a schematic flow chart illustrating a cost accounting method according to a third embodiment of the present invention;
FIG. 5 is a schematic flow chart of a cost accounting method according to a fourth embodiment of the present invention;
fig. 6 is a flowchart illustrating a resource scheduling method according to a fifth embodiment of the present invention.
Detailed Description
The present invention will be further described with reference to the accompanying drawings and the detailed description, and it should be noted that any combination of the embodiments or technical features described below can be used to form a new embodiment without conflict.
Example one
Fig. 1 is a schematic structural diagram of a network system. The network system includes a service server, a client server, and a plurality of node devices and a plurality of client terminals. The service server and the client server are in communication connection with each node device, the service server is in communication connection with the client server, and the client terminal is used for acquiring data from the node devices; in a preferred embodiment, the service server, the client server, the node device and the client terminal are all connected to the internet.
In this embodiment, the node device may be a general-purpose computing device accessing to a network system, or may be a dedicated network device such as a guest cloud, and such devices all have a certain storage space, a certain computing capability, and a communication function accessing to the internet. The node devices form a peer-to-peer network, and the service server is responsible for counting the online state, hardware capability, network capability and the like of each node device.
The client terminal mainly refers to a device for acquiring data from a certain node device or certain node devices, such as a mobile phone, a tablet, a television, a computer and the like provided with a video player, live broadcast software and the like. The client server is a data provider, and can be a server for providing movie and television and live broadcast data, such as an entertainment server. In this embodiment, after the client server owner allows the service server owner, the client server owner may distribute the data to the node devices managed by the service server, so as to provide services such as faster data download for the client terminal by using the storage capacity and bandwidth of the massive node devices. It should be noted that the client server may distribute a complete file to each node device, or may distribute the file to different node devices after dividing the file into a plurality of data blocks.
As shown in fig. 2, the service server and the client server each include a memory 101, a processor 102, and programs stored in the memory 101, the programs being configured to be executed by the processor 102, and the processor 102 implementing the steps of the service server and the client server's fee accounting method and the resource scheduling method when executing the respective programs.
The business servers, client servers of embodiments of the present invention are operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics servers, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
Example two
The embodiment of the invention provides a resource scheduling method, so that a service server can provide support for a client server, and the service server can provide services such as faster data downloading and the like for a client terminal by means of the storage capacity, the computing capacity, the bandwidth and the like of mass node equipment.
Fig. 3 is a flowchart illustrating a resource scheduling method. The resource scheduling method comprises the following steps:
step S110, the client server sends a service request to the service server, and the service server acquires the service request sent by the client server.
When a client server needs to distribute certain data to node equipment, a service request is sent to a service server first, so that the service server provides the node equipment with information of the node equipment capable of storing the data and transmitting the data.
As a preferred embodiment, the service request includes the number of demand nodes. For example, a client server needs to distribute certain data to 5 ten thousand node devices.
As a preferred embodiment, the service request further includes a node condition requirement. For example, the client server needs to distribute certain data to 5 ten thousand node devices that meet the condition of a certain node.
In a preferred embodiment, the node condition requirement includes at least one of a storage space, a node bandwidth, and a geographical distribution.
For example, if a certain data size is 100Mb, then the storage space in the node condition requirement may be more than 100Mb, and the node bandwidth may require more, and if a certain data size is 10Mb, then the storage space in the node condition requirement may be more than 10Mb, and the node bandwidth may require less. In addition, since the number of client terminals using certain data is different in different regions, the service server may be required to allocate more node devices in places where the number of client terminals is large, and to allocate less node devices in places where the number of client terminals is small. For example, the geographical distribution may be 1 ten thousand node devices in the Guangdong, 500 node devices in Tibet, and so on.
Step S120, the service server determines at least one node device as a target node device according to the service request.
After a certain node device is started to access a network, a service server can acquire network access information of the node device and also can acquire information of a storage space, a bandwidth, a region where the node device is located and the like. Therefore, when the service server receives the service request of the client server, some node devices which are in accordance with the service request can be determined as target node devices for storing corresponding data according to the service request, and corresponding information is stored in a target node list, wherein the target node list comprises network addresses of the target node devices.
Step S130, the service server generates node distribution information, where the node distribution information includes a network address of at least one target node device.
As a preferred embodiment, the node distribution information further includes an extension instruction corresponding to the target node device. When the target node equipment acquires data from the client server, the data can be forwarded to other node equipment according to the expansion instruction; therefore, the number of target node devices in the node distribution information is smaller than the number of demand nodes in the service request, but the number of node devices that finally acquire the data may not be smaller than the number of demand nodes.
Step S140, the service server sends the node distribution information to the client server, and the client server obtains the node distribution information from the service server.
The client server receives the node distribution information from the service server, and can distribute data to the target node devices according to the network addresses of the target node devices.
Step S150, after the client server obtains the node distribution information from the service server, the client server distributes data to the target node device according to the node distribution information.
As a preferred embodiment, in step S150, the client server distributes data to the target node device according to the node distribution information, specifically: the client server distributes data and an expansion instruction corresponding to the target node equipment; so that the target node device may forward the data to at least one forwarding node device according to the extended instruction.
In a preferred embodiment, the extended instruction includes forwarding count information indicating that the node device receiving the extended instruction needs to directly or indirectly forward the acquired data to a corresponding number of node devices.
As a preferred embodiment, the extended instruction further includes hop count requirement information and/or region requirement information, so as to restrict that the node device that receives the extended instruction needs to forward the acquired data to the node device that meets the hop count requirement and/or the region requirement, so as to meet the requirement for decentralized storage of data or the requirement for centralized distribution of hot spots.
Step S160, the node device obtains data and an extension instruction corresponding to the node device from the client server.
In this embodiment, the node device that acquires data from the client server is the target node device. Step S160 is specifically that the target node device acquires data and an extension instruction corresponding to the target node device from the client server.
Step S170, the node device that obtains the data from the client server, that is, the target node device, forwards the data to at least one forwarding node device according to the extended instruction.
In this embodiment, the node device that acquires data from another node device is a forwarding node device.
Therefore, the node device may obtain data and an extension instruction corresponding to the node device from another node device, such as a target node device, in addition to the data and the extension instruction corresponding to the node device from the client server. When a certain forwarding node device acquires the data and the extension instruction, the data can be correspondingly forwarded to at least one other forwarding node device; therefore, the node device can also acquire the data and the extension instruction from another forwarding node device.
As a preferred embodiment, the extended instruction includes forwarding count information. After a certain node device forwards the acquired data to at least one forwarding node device according to the extended instruction, the method further comprises the following steps:
and step S181, adjusting the forwarding count information in the extended instruction.
For example, if ten pieces of forwarding count information in the expansion instruction acquired by a certain node device are obtained, the forwarding count information may be adjusted to 10-3 or 7 pieces of forwarding count information after the acquired data is successfully forwarded to certain three node devices, that is, forwarding node devices. It means that the three node devices are also required to forward the data to seven other node devices, that is, another forwarding node device, and therefore the extension instructions corresponding to the three node devices can be adjusted to two, and three, respectively, and the total is seven.
Step S182, sending the adjusted extension instruction to the at least one forwarding node device.
After the three forwarding node devices acquire the adjusted extension instructions, the three forwarding node devices respectively forward the acquired data to two, and three node devices.
The resource scheduling method provided by the embodiment of the invention, and the network system, the service server and the client server applying the resource scheduling method, the online state, the hardware capability, the network capability and the like of each node device are counted by the service server, and the node device which can be used for the client server to store data is determined according to the service request of the client server; therefore, the service server can provide support for the client server, so that the service server can provide services such as faster data downloading and the like for the client terminal by means of the storage capacity and bandwidth of the mass node equipment.
The embodiment of the invention further enables the node equipment which acquires the data to forward the data to other node equipment according to the extended instruction by placing the extended instruction in the node distribution information; therefore, the number of target node devices directly acquiring data from the client server can be smaller than the number of required nodes of the client server; the client server can distribute the data to a small number of node devices, and then the node devices receiving the data continue to forward the data according to the expansion instruction, so that the bandwidth required by the client server is small, and the data can be distributed to the node devices with the required node number more quickly.
As a preferred embodiment, the node device that acquires data from the client server or other node devices sends feedback information to the client server and/or the service server, so that the client server and/or the service server knows that the node device stores the data.
EXAMPLE III
Fig. 4 is a schematic diagram illustrating a flow of a cost accounting method for a client server or a service server to account service charges of a client terminal, such as data, acquired through a node device.
In this embodiment, a service plug-in is built in the client terminal, and the client terminal interacts with the service server and the node device through the service plug-in. In a preferred embodiment, the service plug-in is specifically a plug-in provided by a service server administrator. For example, the entertainment player, the data downloader and the like are internally provided with plug-ins for interacting with the node equipment and the service server. When a client terminal needs a certain data, a data request can be sent to a service server; the data request may include a hash value of the data.
As shown in fig. 4, the fee accounting method includes the steps of:
step S210, the client terminal obtains a service from at least one node device.
As a preferred implementation manner, in this embodiment, in step S210, the client terminal acquires a service from at least one node device, specifically, the client terminal acquires data from at least one node device.
As a preferred embodiment, before the client terminal acquires data from at least one node device, the method further includes the following steps:
step S211, the client terminal sends a data request to the service server, and the service server obtains the data request from the client terminal; the service server is used for receiving first feedback information from node equipment, and the node equipment acquires data from a client server or another node equipment.
In a preferred embodiment, the node device sends the first feedback information to the service server after acquiring the data from the client server or another node device, and the service server acquires the first feedback information from at least one node device that acquired the data from the client server or another node device. Therefore, the service server can control what data are stored in each node device, and convenience is provided for the client terminal to acquire the data from the node devices.
Step S212, the service server determines at least one source node device according to the data request.
The service server counts which node devices store which data through the first feedback information, and after a data request of a certain terminal device is obtained, one or more node devices are appointed to serve as source node devices according to the data request. As a preferred mode, the data request includes location information of the terminal device, and the service server preferentially designates a node device that is close to the terminal device as a source node device.
As a preferred implementation manner, in step S212, the service server determines at least one source node device according to the data request, specifically, the service server determines that at least one node device is a source node device according to the data request and the first feedback information.
Step S213, the service server sends the information of the source node device to the client terminal, and the client terminal obtains the information of the source node device from the service server.
As a preferred embodiment, the information of the source node device comprises its network address. Therefore, the client terminal can acquire the required data from the source node device according to the network address of the source node device, so as to facilitate subsequent operations, such as playing video and the like.
In a preferred embodiment, the client terminal obtains data from at least one node device, and in particular, the client terminal obtains data from at least one source node device. Further, the client terminal obtains data from the source node device through the service plug-in.
And step S220, the client terminal counts the service contribution information through the service plug-in.
As a preferred embodiment, the service contribution information includes node contribution information of the at least one source node device.
For example, when a client terminal pulls data segments from three different source node devices and then splices into complete data, its service information includes node contribution information of the three source node devices. The node contribution information of the source node device may reflect the status and quality of the service provided by the source node device to the client terminal.
In a preferred embodiment, the node contribution information includes at least one of a data provision amount, an egress network speed, a transmission duration, and a contribution frequency of the source node device.
The data supply quantity can represent the size of data quantity sent by the node equipment to the client terminal, and the exit network speed can represent the speed of data transmission between the node equipment and the client terminal; the transmission time may represent the time for the node device to continuously transmit data to the client terminal, and for data of a certain size, the longer the transmission time, the lower the data transmission quality between the node device and the client terminal; the contribution frequency represents the number of times that certain data in the node device is sent to the client terminal in the network system, and the higher the contribution frequency is, the more popular the data in the node device is.
Step S230, the client terminal sends the service contribution information to the service server, and the service server obtains the service contribution information from the client terminal.
As a preferred implementation manner, in step S230, the client terminal sends the service contribution information to the service server, specifically: and sending the service contribution information to the business server so that the business server analyzes the business cost of the client terminal and/or the client server. Namely:
step S240, the service server analyzes the service cost of the client terminal and/or the client server according to the service contribution information.
The service server can count service contribution information sent by a plurality of client terminals in the network system, namely a plurality of node contribution information of a plurality of node devices, so that the support of data, network bandwidth and the like actually provided by the node devices for the client server and/or the terminal devices in the network system can be obtained; and quantifying the service provided by the node equipment for the client terminal and/or the client server in the network system so as to account the service cost of the client terminal and/or the client server. For example, the data provision amounts of the respective node apparatuses may be accumulated, then the service fee of the client terminal and/or the client server may be accounted, and then the fee may be charged to the client server manager.
As a preferred embodiment, the client terminal may further send the service contribution information to a service server, specifically: the client terminal sends the service contribution information to the client server so that the client server analyzes the service cost of the client terminal and/or the client server. That is, the service charge of the client terminal and/or the client server may be accounted by the client server and then paid to the service server manager.
The cost accounting method provided in this embodiment implements analysis of the service cost of the client terminal and/or the client server by counting service contribution information, that is, node contribution information providing services to the client terminal, through the service plug-in the client terminal, and performs charging by using the service actually provided by the node device as the client terminal as a standard.
Example four
The charge accounting method as shown in fig. 5 includes the steps of:
step S310, the client terminal obtains a service from at least one node device.
And step S320, the client terminal counts the service contribution information through the service plug-in.
Step S330, the client terminal sends the service contribution information to the service server and/or the client server, and the service server obtains the service contribution information from the client terminal.
Step S340, the service server analyzes the service charge of the client terminal and/or the client server according to the service contribution information.
Steps S310, S320, S330, and S340 respectively correspond to steps S210, S220, S230, and S240 in the third embodiment, and are not described again.
In this embodiment, after the step S320 of counting the service contribution information by the client terminal through the service plug-in, the method further includes the following steps:
step S301, if the service contribution information satisfies the node expansion condition, the client terminal sends a first expansion notification to the client server, so that the client server sends a new service request to the service server.
The node contribution information in the service contribution information can reflect the state and quality of service provided by the node equipment to the client terminal, when the client terminal learns that the capacity of certain node equipment meeting the data downloading speed requirement and the like of the client terminal is insufficient through the service contribution information, a first extension notice is sent to the client server, and after receiving the first extension notice, the client server can request more node equipment to store data to the service server.
As a preferred embodiment, the node contribution information includes a transmission duration of the source node device, and the node extension condition includes: the transmission duration of the source node device is greater than a time threshold.
The transmission time may represent a time during which the node device continuously transmits data to the client terminal, and for a certain size of data, the longer the transmission time, the lower the quality of data transmission between the node device and the client terminal. It may be that the bandwidth of the node apparatus is small, or the load is large when the node apparatus transmits data to a plurality of client terminals at the same time. By forwarding the data to at least another node device, a larger number of node devices with better quality can be used as source node devices of the data, and the service can be better provided for the client terminal.
As a preferred embodiment, the node contribution information includes a contribution frequency of the source node device, and the node expansion condition includes: the contribution frequency of the source node device is greater than a frequency threshold.
The contribution frequency represents the number of times that certain data in the node device is sent to the client terminal in the network system, and the higher the contribution frequency is, the more popular the data in the node device is. Thus, in order to avoid too many client terminals to download data from the node device at the same time afterwards, the data may be forwarded to at least another node device, spreading the load of the source node device. More source node devices can provide larger total bandwidth to meet the requirement of the client terminal on hot data.
As a preferred implementation manner, after the step S330 of sending the service contribution information to the service server by the client terminal, and acquiring the service contribution information from the client terminal by the service server, the method further includes the following steps:
step S302, if the service contribution information satisfies the node expansion condition, the service server sends a second expansion notification to the client server, so that the client server sends a new service request to the service server. Namely, the business server judges whether the client server needs more node devices according to the service contribution information and provides suggestion, namely, a second extension notice to the client server. After receiving the second extension notification, the client server may request more node devices to store data from the service server.
The cost accounting method provided by this embodiment may store data to more node devices through the service contribution information and the node expansion condition when the state and quality of the service provided by the node device to the client terminal are not good or have a potential risk. The node equipment with more quantity and better quality becomes the source node equipment of the data, thereby better providing service for the client terminal.
Judging whether the data needs to be stored in more node devices or not through the service contribution information can also be applied to the resource scheduling method of the second embodiment, so as to realize the full-flow scheduling of the node device data, as in the fifth embodiment.
EXAMPLE five
Fig. 6 is a flowchart illustrating a resource scheduling method. The resource scheduling method comprises the following steps:
step S410, the client server sends a service request to the service server, and the service server obtains the service request sent by the client server.
Step S420, the service server determines at least one node device as a target node device according to the service request.
Step S430, the service server generates node distribution information, where the node distribution information includes a network address of at least one target node device.
Step S440, the service server sends the node distribution information to the client server, and the client server obtains the node distribution information from the service server.
Step S450, after the client server obtains the node distribution information from the service server, the client server distributes data to the target node equipment according to the node distribution information.
Steps S410, S420, S430, S440, and S450 respectively correspond to S110, S120, S130, S140, and S150 in the second embodiment, and are not described again.
In this embodiment, a service plug-in is built in the client terminal, and the client terminal interacts with the service server and the node device through the service plug-in.
The resource scheduling method provided by the embodiment further includes the following steps:
step S461, the client terminal obtains data from at least one source node device, and the source node device stores the data.
As a preferred embodiment, the step S461, where the client terminal acquires data from at least one source node device, specifically includes the following steps:
step S4611, the service server obtains a data request from the client terminal;
step S4612, the service server determines at least one source node device according to the data request, where the source node device stores the data requested by the client terminal.
Step S4613, the service server sends the information of the source node device to the client terminal, so that the client terminal obtains data from the source node device through the client plug-in.
Step S4611 to step S4613 refer to step S211 to step S213 in the third embodiment, and are not described herein again.
Step S462, the client terminal counts the service contribution information of the at least one source node device through the service plug-in.
The service plug-in runs at the client terminal, and when the client terminal acquires data from the node equipment, the service plug-in can monitor the state and quality of service provided by the source node equipment to the client terminal and generate service contribution information.
As a preferred embodiment, the service contribution information includes node contribution information of the at least one source node device.
For example, when a client terminal pulls data segments from three different source node devices and then splices into complete data, its service information includes node contribution information of the three source node devices. The node contribution information of the source node device may reflect the status and quality of the service provided by the source node device to the client terminal.
In a preferred embodiment, the node contribution information includes at least one of a data provision amount, an egress network speed, a transmission duration, and a contribution frequency of the source node device.
The data supply quantity can represent the size of data quantity sent by the node equipment to the client terminal, and the exit network speed can represent the speed of data transmission between the node equipment and the client terminal; the transmission time may represent the time for the node device to continuously transmit data to the client terminal, and for data of a certain size, the longer the transmission time, the lower the data transmission quality between the node device and the client terminal; the contribution frequency represents the number of times that certain data in the node device is sent to the client terminal in the network system, and the higher the contribution frequency is, the more popular the data in the node device is.
As a preferred embodiment, after the step S462 of counting the service contribution information of the at least one source node device by the client terminal through the service plug-in, the method further includes the following steps:
step S401, if the service contribution information satisfies the node expansion condition, sending a first expansion notification to the client server, so that the client server sends a new service request to the service server.
The node contribution information in the service contribution information can reflect the state and quality of service provided by the node equipment to the client terminal, when the client terminal learns that the capacity of certain node equipment meeting the data downloading speed requirement and the like of the client terminal is insufficient through the service contribution information, a first extension notice is sent to the client server, and after receiving the first extension notice, the client server can request more node equipment to store data to the service server.
Step S463, the client terminal sends the service contribution information to the service server, and the service server obtains the service contribution information from the client terminal.
Step S464, if the service contribution information satisfies the node expansion condition, the service server sends a second expansion notification to the client server, so that the client server sends a new service request to the service server. After receiving the second extension notification, the client server may request more node devices to store data from the service server. In this embodiment, the service server determines whether to notify the client server to send a new service request.
In another embodiment, the client terminal may further send the service contribution information to a client server, so that the client server determines whether to send a new service request to the service server. Namely, the client server can judge whether to send a new service request to the client server so as to acquire more node device storage data.
The resource scheduling method provided by the embodiment of the invention further judges whether the data needs to be stored in other node equipment or not through the service contribution information, namely the state, quality and the like of the data provided by the source node equipment to the client terminal, and when the capacity of a certain node equipment for meeting the data downloading speed requirement and the like of the client terminal is insufficient, the data is stored in more node equipment, so that the node equipment with more quantity and better quality becomes the source node equipment of the data, and the service is better provided for the client terminal.
From the above description of the embodiments, it is clear to those skilled in the art that the present invention can be implemented by software plus necessary general hardware platform. With such an understanding, the technical solutions of the present invention may be embodied in the form of a software product, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods according to the embodiments or some parts of the embodiments, such as:
a medium storing a computer program which, when executed by a processor, implements the steps of the aforementioned resource scheduling method, or cost accounting method.
The above embodiments are only preferred embodiments of the present invention, and the protection scope of the present invention is not limited thereby, and any insubstantial changes and substitutions made by those skilled in the art based on the present invention are within the protection scope of the present invention.
Claims (17)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810453585.0A CN108683730B (en) | 2018-05-11 | 2018-05-11 | Resource scheduling method, service server, client terminal, network system and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810453585.0A CN108683730B (en) | 2018-05-11 | 2018-05-11 | Resource scheduling method, service server, client terminal, network system and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108683730A CN108683730A (en) | 2018-10-19 |
| CN108683730B true CN108683730B (en) | 2021-08-06 |
Family
ID=63806318
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810453585.0A Active CN108683730B (en) | 2018-05-11 | 2018-05-11 | Resource scheduling method, service server, client terminal, network system and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108683730B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111105116A (en) * | 2018-10-27 | 2020-05-05 | 谷多多(成都)科技有限公司 | Business mode applied to organic agriculture |
| CN110018906B (en) * | 2019-02-26 | 2020-11-27 | 上海丽人丽妆网络科技有限公司 | Scheduling method, server and scheduling system |
| CN109981780A (en) * | 2019-03-27 | 2019-07-05 | 深圳市网心科技有限公司 | A kind of dispatching method, node device, scheduling system and storage medium |
| CN110691127B (en) * | 2019-09-25 | 2022-04-12 | 北京奇艺世纪科技有限公司 | Data acquisition control system, data acquisition control method and related device |
| CN111538575B (en) * | 2020-04-07 | 2023-11-14 | 北京达佳互联信息技术有限公司 | Resource scheduling system, method, device, equipment and medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102075790A (en) * | 2009-11-20 | 2011-05-25 | 上海电机学院 | Method for distributing and encrypting streaming media |
| CN102857470A (en) * | 2011-06-27 | 2013-01-02 | 腾讯科技（深圳）有限公司 | Network transmission system, servers and client |
| US8375456B2 (en) * | 2004-09-03 | 2013-02-12 | Microsoft Corp. | Digital rights management scheme for an on-demand distributed streaming system |
| CN103327046A (en) * | 2012-03-21 | 2013-09-25 | 腾讯科技（深圳）有限公司 | P2SP system scheduling method, equipment and system based on node service capacity |
| CN105791427A (en) * | 2016-04-22 | 2016-07-20 | 百度在线网络技术（北京）有限公司 | Method, device and system for supplementing resource heat |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104580305B (en) * | 2013-10-18 | 2018-11-06 | 腾讯科技（深圳）有限公司 | Network uploads scheduling and bandwidth detection method, system, client and server |
-
2018
- 2018-05-11 CN CN201810453585.0A patent/CN108683730B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8375456B2 (en) * | 2004-09-03 | 2013-02-12 | Microsoft Corp. | Digital rights management scheme for an on-demand distributed streaming system |
| CN102075790A (en) * | 2009-11-20 | 2011-05-25 | 上海电机学院 | Method for distributing and encrypting streaming media |
| CN102857470A (en) * | 2011-06-27 | 2013-01-02 | 腾讯科技（深圳）有限公司 | Network transmission system, servers and client |
| CN103327046A (en) * | 2012-03-21 | 2013-09-25 | 腾讯科技（深圳）有限公司 | P2SP system scheduling method, equipment and system based on node service capacity |
| CN105791427A (en) * | 2016-04-22 | 2016-07-20 | 百度在线网络技术（北京）有限公司 | Method, device and system for supplementing resource heat |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108683730A (en) | 2018-10-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108683730B (en) | Resource scheduling method, service server, client terminal, network system and medium | |
| CN106464720B (en) | Method and apparatus for distributing content in a managed wireless distribution network | |
| EP3143539B1 (en) | Content discovery in managed wireless distribution networks | |
| US11102290B2 (en) | Peer-to-peer network prioritizing propagation of objects through the network | |
| EP3143748B1 (en) | Managed wireless distribution network | |
| EP3143541B1 (en) | Content delivery prioritization in managed wireless distribution networks | |
| US11916743B2 (en) | Profile generation for bandwidth management | |
| KR20200083608A (en) | Video live broadcasting method and device | |
| KR20150096660A (en) | Content-acquisition source selection and management | |
| CN102137163A (en) | Multimedia file sharing system and method | |
| CN108616600B (en) | Resource scheduling method, client server, node device, network system, and medium | |
| Roverso et al. | Smoothcache 2.0: Cdn-quality adaptive http live streaming on peer-to-peer overlays | |
| CN108667935A (en) | Network business method, server, network system and storage medium | |
| CN108683728B (en) | Data transmission method, server, terminal, network system and storage medium | |
| CN108683515B (en) | Fee accounting method, client terminal, service server, network system and medium | |
| CN108737121B (en) | Cost accounting method, node device, client server, network system, and medium | |
| CN112925946B (en) | A business data storage method, device and electronic equipment | |
| CN112860432B (en) | Process management method, device and server | |
| KR20070059807A (en) | P2P based streaming service providing method and apparatus, streaming service system using same | |
| CN108683726B (en) | Data transmission method, server, terminal, network system and storage medium | |
| KR20130022512A (en) | Data exchange method in p2p network | |
| Granja et al. | Managing QoS constraints in a P2P-cloud video on demand system |
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 |