CN108737121B - Cost accounting method, node device, client server, network system, and medium - Google Patents
Cost accounting method, node device, client server, network system, and medium Download PDFInfo
- Publication number
- CN108737121B CN108737121B CN201810451424.8A CN201810451424A CN108737121B CN 108737121 B CN108737121 B CN 108737121B CN 201810451424 A CN201810451424 A CN 201810451424A CN 108737121 B CN108737121 B CN 108737121B
- Authority
- CN
- China
- Prior art keywords
- node
- client
- node device
- server
- data
- 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
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1432—Metric aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1432—Metric aspects
- H04L12/1435—Metric aspects volume-based
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1432—Metric aspects
- H04L12/1439—Metric aspects time-based
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1485—Tariff-related aspects
Abstract
The invention discloses a cost accounting method, node equipment, a client server, a network system and a medium, wherein the method comprises the steps that the node equipment provides service for a client terminal; the node equipment counts the contribution information of the nodes through the client plug-in; the node equipment sends the node contribution information to the client server, and the client server acquires the node contribution information from at least one node equipment; and the client server analyzes the service cost of the client terminal and/or the client server according to the node contribution information. The service cost of the client terminal and/or the client server is analyzed by counting the node contribution information providing service for the client terminal through the client plug-in the node equipment, and the service actually provided by the node equipment for the client terminal is taken as a standard for charging.
Description
Technical Field
The present invention relates to a network technology, and more particularly, to a cost accounting method, a node device, a client server, 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.
In the existing network system, a management party and a maintenance party of the node and a data provider are usually separate main bodies, and the management party of the existing data has no incentive, such as payment, for the management party and the maintenance party of the node, so that the management party and the maintenance party of the node have no power to stimulate a node owner, and thus the number of the nodes in the network system is gradually reduced, the stability is poor, and better service quality cannot be provided for users. Therefore, how to account for services provided by node devices to users and data providers is an urgent problem to be solved.
Disclosure of Invention
In order to overcome the defects of the prior art, one of the purposes of the invention is a cost accounting method for a node device, which can solve the problem of how to account the service provided by the node device to a user and a data provider.
The second purpose of the present invention is to provide a fee accounting method for a client server, which can solve the problem of how to account the services provided by a node device to users and data providers.
The invention also aims to provide the node equipment, which can solve the problem of how to account the service provided by the node equipment to the user and the data provider.
The fourth purpose of the present invention is to provide a client server which can solve the problem of how to account the services provided by the node device to the user and the data provider.
The fifth purpose of the present invention is to provide a network system that can solve the problem of how to account for services provided by node devices to users and data providers.
It is still another object of the present invention to provide a medium storing a computer program that can solve the problem of how to account for services provided by a node device to a user or a data provider.
One of the purposes of the invention is realized by adopting the following technical scheme:
the cost accounting method is used for node equipment, a client plug-in is arranged in the node equipment, and the node equipment interacts with a client server and a client terminal through the client plug-in;
the cost accounting method comprises the following steps:
providing a service to the client terminal;
counting node contribution information through the client plug-in;
and sending the node contribution information to the client server and/or the service server.
Further, the providing of the service to the client terminal specifically includes:
and if the data downloading request is acquired from the client terminal, sending data to the client terminal through the client plug-in.
Further, the fee accounting method further comprises the following steps:
after data is acquired from a client server or another node device, first feedback information is sent to the client server through the client plug-in, so that the client server confirms that the node device is a source node device according to the first feedback information and a data request of a client terminal, and a source node list is generated, wherein the source node list comprises a network address of at least one source node device.
Further, the counting of the node contribution information by the client plug-in specifically includes the following steps:
and counting the node contribution information of the source node equipment to the client terminal through the client plug-in.
Further, 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.
Further, the sending the node contribution information to the client server specifically includes:
and sending the node contribution information of the source node equipment to the client terminal to the client server so as to enable the client server to analyze the service cost of the client terminal and/or the client server.
Further, the sending the node contribution information to a service server specifically includes:
and sending the node contribution information of the source node equipment to the client terminal to the service server so that the service server analyzes the service cost of the client terminal and/or the client server.
Further, after the statistics of the node contribution information of the source node device to the client terminal is performed by the client plug-in, the method further includes the following steps:
and if the node contribution information meets the node expansion condition, forwarding the data to at least another node device.
Further, after the statistics of the node contribution information of the source node device to the client terminal is performed by the client plug-in, the method further includes the following steps:
and if the node 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 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.
Further, the node contribution information includes a contribution frequency of the source node device, and the node extension condition includes: the contribution frequency of the source node device is greater than a frequency threshold.
The second purpose of the invention is realized by adopting the following technical scheme:
the cost accounting method is used for a client server, the client server is connected with a plurality of node devices, client plug-ins are arranged in the node devices, and the node devices interact with the client server and a client terminal through the client plug-ins;
the cost accounting method comprises the following steps:
obtaining node contribution information from at least one of the node devices;
and analyzing the service cost of the client terminal and/or the client server according to the node contribution information.
Further, before obtaining the node contribution information from at least one of the node devices, the method further includes the following steps:
obtaining a data request from a client terminal;
determining at least one source node device according to the data request;
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, before obtaining the data request from the client terminal, the method further comprises the following steps:
obtaining first feedback information from at least one node device, the node device obtaining data from a client server or another node device;
the determining at least one source node device according to the data request specifically includes: and determining at least one node device as a source node device according to the data request and the first feedback information.
Further, the obtaining node contribution information from at least one of the node devices specifically includes:
obtaining node contribution information from the source node device;
the node contribution information is counted by the source node device through the client plug-in.
Further, 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.
Further, after obtaining the node contribution information from at least one of the node devices, the method further includes the following steps:
and if the node contribution information meets the node expansion condition, sending a new service request to the service server.
Further, 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.
Further, the node contribution information includes a contribution frequency of the source node device, and the node extension condition includes: the contribution frequency of the source node device is greater than a frequency threshold.
The third purpose of the invention is realized by adopting the following technical scheme:
node apparatus 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 cost accounting method as described above.
The fourth purpose of the invention is realized by adopting the following technical scheme:
a client 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 when executing the program implementing the steps of the cost accounting method as described above.
The fifth purpose of the invention is realized by adopting the following technical scheme:
the network system comprises the node equipment, the client server, a service server and a client terminal; 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, in which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned cost accounting method.
Compared with the prior art, the embodiment of the invention has the beneficial effects that: the service cost of the client terminal and/or the client server is analyzed by counting the node contribution information providing service for the client terminal through the client plug-in the node equipment, and the service actually provided by the node equipment for the client terminal is taken as a standard for charging.
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 client plug-in is built in the node device, and the node device interacts with the client server and the client terminal through the client plug-in. In a preferred embodiment, the client plug-in is specifically a plug-in provided by a client server manager, and may run in a sandbox of the node device.
As shown in fig. 4, the fee accounting method includes the steps of:
step S210, the node equipment provides service for the client terminal.
As a preferred implementation manner, in this embodiment, in step S210, the node device provides a service to the client terminal, specifically, the source node device provides data to the client terminal. Step S210, the node device provides service to the client terminal, specifically:
and if the data downloading request is acquired from the client terminal, sending data to the client terminal through the client plug-in.
The node device transmits the first feedback information to the client server through the client plug-in after acquiring the data from the client server or another node device, and the client server acquires the first feedback information from at least one node device which acquired the data from the client server or another node device.
As a preferred embodiment, step S210, the node device provides a service to the client terminal, and specifically includes the following steps:
step S211, the client server acquires a data request from the client terminal.
The client terminal is provided with a program corresponding to the client server, such as an entertainment player, a data downloader, and the like. When a client terminal needs certain data, a data request can be sent to a client server; the data request may include a hash value of the data.
Since the client server counts which data are stored in which node devices through the first feedback information, the client terminal can be instructed to acquire the data from the corresponding node device.
Step S212, the client server determines at least one source node device according to the data request.
As a preferred embodiment, step S212 is specifically that the client server determines at least one node device as a source node device according to the first feedback information and the data request of the client terminal, and generates a source node list, where the source node list includes a network address of the at least one source node device.
The client server counts which data are stored in which node devices 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. Preferably, the data request includes location information of the terminal device, the client server preferentially designates a node device that is close to the terminal device as a source node device, and the source node list may be generated according to the source node device.
Step S213, the client server sends the information of the source node device, i.e. the source node list, to the client terminal, so that the client terminal obtains data from the source node device through the client plug-in.
The source node list includes the network address of the source node device, so that the client terminal can acquire the required data from the source node device according to the network address of the source node device for subsequent operations, such as playing video.
And step S220, the node equipment counts the contribution information of the nodes through the client plug-in.
As a preferred embodiment, the step S220 of the node device counting the node contribution information through the client plug-in is specifically: and the source node equipment counts the node contribution information of the source node equipment to the client terminal through the client plug-in.
The client plug-in runs the node device, and when the node device provides data to the client terminal, the client plug-in can monitor the state and quality of 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 node device sends the node contribution information to the client server, and the client server obtains the node contribution information from at least one node device.
As a preferred implementation manner, in step S230, the node device sends the node contribution information to the client server, specifically: and the source node equipment sends the node contribution information of the source node equipment to the client terminal to the client server so as to enable the client server to analyze the service cost of the client terminal and/or the client server.
As a preferred embodiment, the step of the client server obtaining the node contribution information from at least one of the node devices specifically includes: the client server acquires node contribution information from the source node equipment; the node contribution information is counted by the source node device through the client plug-in.
And step S240, the client server analyzes the service cost of the client terminal and/or the client server according to the node contribution information.
The client server counts the node contribution information sent by a plurality of node devices in the network system, namely the node devices in the network system actually provide the data, network bandwidth and other support for the client server and/or the terminal device; 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, and then the service fees of the client terminals and/or the client servers may be accounted and then the fees may be paid to the service server manager.
As a preferred embodiment, the source node device may further send node contribution information to the service server, that is, the source node device sends the node contribution information of the source node device to the client terminal to the service server, so that the service server analyzes the service cost of the client terminal and/or the client server. That is, the service server may also account for the service fee of the client terminal and/or the client server and then charge the fee to the client server manager.
The cost accounting method provided in this embodiment performs statistics on node contribution information providing services to the client terminal through the client plug-in the node device, so as to analyze the service cost of the client terminal and/or the client server, and perform charging based on the service actually provided by the node device as the client terminal.
Example four
The charge accounting method as shown in fig. 5 includes the steps of:
step S310, the node device provides service for the client terminal.
And step S320, the node equipment counts the contribution information of the nodes through the client plug-in.
Step S330, the node device sends the node contribution information to the client server and/or the service server, and the client server obtains the node contribution information from at least one node device.
And step S340, the client server analyzes the service cost of the client terminal and/or the client server according to the node 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 node contribution information by the node device through the client plug-in, the method further includes the following steps:
step S301, if the node contribution information satisfies the node expansion condition, the node device forwards the data to at least another node device.
The node contribution information may reflect the state and quality of the service provided by the node device to the client terminal, and when a certain node device has insufficient capability to meet the data download speed requirement of the client terminal, some node devices need to be expanded to store the data, that is, the source node device forwards the data to at least another node device.
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 embodiment, after the node device counts node contribution information through the client plug-in step S320, the method further includes the following steps:
step S302, if the node contribution information satisfies a node expansion condition, the node device sends a first expansion notification to the client server, so that the client server sends a new service request to the service server.
When the node contribution information of a certain source node device meets the node extension condition, the data can be directly forwarded to other node devices, or the source node device can notify the client server, and then the client server requests more node devices to store the data from the service server. At this time, the data is issued by the client server, so that the tampered data in the node device can be prevented from being distributed to other node devices.
As a preferred implementation manner, after the client server acquires the node contribution information from at least one of the node devices in step S330, the method further includes the following steps
S303, if the node contribution information meets the node expansion condition, the client server sends a new service request to the service server.
After the client server acquires the node contribution information from a certain node device, the state and quality of service provided by the node device to the client terminal can also be judged; when the node device has insufficient capacity to meet the data downloading speed requirement of the client terminal, more node devices can be requested to store data from the service server.
The cost accounting method provided by this embodiment may store data to more node devices through the node contribution information and the node extension 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 node 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 node device has a built-in client plug-in for interacting with the client server. The resource scheduling method provided by the embodiment further includes the following steps:
step S461, the node device provides the data to the client terminal, and the node device is a source node device.
As a preferred embodiment, the step S461 node device provides the data to the client terminal, and specifically includes the following steps:
step S4611, the client server obtains a data request from the client terminal;
step S4612, the client server determines at least one source node device according to the data request, and the source node device stores the data requested by the client terminal;
step S4613, the client 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.
And step S462, the node device counts node contribution information of the node device to the client terminal through the client plug-in.
The client plug-in runs the node device, and when the node device provides data to the client terminal, the client plug-in can monitor the state and quality of 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 node device counts the node contribution information of the node device to the client terminal through the client plug-in step S462, the method further includes the following steps:
step S463, if the node contribution information satisfies a node extension condition, forwarding the data to at least another node device.
The node contribution information may reflect the state and quality of the service provided by the node device to the client terminal, and when a certain node device has insufficient capability to meet the data download speed requirement of the client terminal, some node devices need to be expanded to store the data, that is, the source node device forwards the data to at least another node device.
As a preferred embodiment, after the node device counts the node contribution information of the node device to the client terminal through the client plug-in step S462, the method further includes the following steps:
step S464, if the node contribution information satisfies the node expansion condition, the node device sends a first expansion notification to the client server, so that the client server sends a new service request to the service server.
When the node contribution information of a certain source node device meets the node extension condition, the source node device can inform the client server, and then the client server requests more node devices to store data from the service server.
As a preferred embodiment, after the node device counts the node contribution information of the node device to the client terminal through the client plug-in step S462, the method further includes the following steps:
step S471, the node device sends the node contribution information of the node device to the client terminal to the client server; and the client server acquires node contribution information of the source node equipment to the client terminal from at least one source node equipment.
Step S472, the client server determines whether the node contribution information satisfies the node expansion condition, and if so, sends a new service request to the server. The client server judges whether more nodes are required to be requested to the service server to store the data or not according to the node contribution information, so that the macroscopic scheduling of data resources by the client server is facilitated.
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.
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 node contribution information counted when the node equipment provides the data to the client terminal, and when the capacity of a certain node equipment for meeting the data downloading speed requirement 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 aforementioned steps of the fee accounting method, or the resource scheduling 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 (23)
1. The cost accounting method is characterized in that: the node equipment is internally provided with a client plug-in, and interacts with a client server and a client terminal through the client plug-in;
the cost accounting method comprises the following steps:
providing a service to the client terminal;
counting node contribution information through the client plug-in;
sending the node contribution information to the client server and/or the business server;
the providing of the service to the client terminal specifically includes:
the client server acquires a data request from a client terminal;
the client server determines at least one source node device according to the data request; the method specifically comprises the following steps: the client server sends a service request to the service server; the service server determines at least one node device as a target node device according to the service request, and generates node distribution information; the service server sends the node distribution information to the client server; after obtaining node distribution information from a service server, a client server distributes data to the target node equipment according to the node distribution information;
and the client server sends the information of the source node equipment to the client so that the client terminal acquires data from the source node equipment through the client plug-in.
2. The charge accounting method of claim 1, wherein said providing a service to said client terminal comprises:
and if the data downloading request is acquired from the client terminal, sending data to the client terminal through the client plug-in.
3. The charge accounting method of claim 2, further comprising the steps of:
after data is acquired from a client server or another node device, first feedback information is sent to the client server through the client plug-in, so that the client server confirms that the node device is a source node device according to the first feedback information and a data request of a client terminal, and a source node list is generated, wherein the source node list comprises a network address of at least one source node device.
4. A cost accounting method as claimed in claim 3 wherein: the counting of the node contribution information through the client plug-in specifically comprises the following steps:
and counting the node contribution information of the source node equipment to the client terminal through the client plug-in.
5. A cost accounting method as claimed in claim 4 wherein: 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.
6. A cost accounting method as claimed in claim 4 wherein: the sending the node contribution information to the client server specifically includes:
and sending the node contribution information of the source node equipment to the client terminal to the client server so as to enable the client server to analyze the service cost of the client terminal and/or the client server.
7. A cost accounting method as claimed in claim 4 wherein: the sending of the node contribution information to a service server specifically includes:
and sending the node contribution information of the source node equipment to the client terminal to the service server so that the service server analyzes the service cost of the client terminal and/or the client server.
8. A cost accounting method as claimed in claim 4 wherein: after the statistics of the node contribution information of the source node device to the client terminal is carried out through the client plug-in, the method further comprises the following steps:
and if the node contribution information meets the node expansion condition, forwarding the data to at least another node device.
9. A cost accounting method as claimed in claim 4 wherein: after the statistics of the node contribution information of the source node device to the client terminal is carried out through the client plug-in, the method further comprises the following steps:
and if the node 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.
10. A charge accounting method as claimed in claim 8 or 9 wherein: 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.
11. A charge accounting method as claimed in claim 8 or 9 wherein: 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.
12. The cost accounting method is characterized in that: the client server is connected with a plurality of node devices, client plug-ins are arranged in the node devices, and the node devices interact with the client server and client terminals through the client plug-ins;
the cost accounting method comprises the following steps:
the client server acquires a data request from a client terminal;
the client server determines at least one source node device according to the data request; the method specifically comprises the following steps: the client server sends a service request to the service server; the service server determines at least one node device as a target node device according to the service request, and generates node distribution information; the service server sends the node distribution information to the client server; after obtaining node distribution information from a service server, a client server distributes data to the target node equipment according to the node distribution information;
the client server sends the information of the source node equipment to the client so that the client terminal can acquire data from the source node equipment through a client plug-in;
obtaining node contribution information from at least one of the node devices;
and analyzing the service cost of the client terminal and/or the client server according to the node contribution information.
13. A cost accounting method as claimed in claim 12 wherein: before obtaining the node contribution information from at least one of the node devices, the method further includes the following steps:
obtaining a data request from a client terminal;
determining at least one source node device according to the data request;
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.
14. A cost accounting method as claimed in claim 13 wherein: before the data request is obtained from the client terminal, the method further comprises the following steps:
obtaining first feedback information from at least one node device, the node device obtaining data from a client server or another node device;
the determining at least one source node device according to the data request specifically includes: and determining at least one node device as a source node device according to the data request and the first feedback information.
15. A cost accounting method as claimed in claim 13 wherein: the acquiring node contribution information from at least one of the node devices specifically includes:
obtaining node contribution information from the source node device;
the node contribution information is counted by the source node device through the client plug-in.
16. A method of cost accounting according to any one of claims 13 to 15 wherein: 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.
17. A cost accounting method as claimed in claim 16 wherein: after the node contribution information is acquired from at least one node device, the method further comprises the following steps:
and if the node contribution information meets the node expansion condition, sending a new service request to the service server.
18. A cost accounting method as claimed in claim 17 wherein: 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.
19. A cost accounting method as claimed in claim 17 wherein: 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.
20. A node device, characterized by: 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 fare accounting method according to any one of claims 1-11.
21. A client server, characterized by: comprising a memory, a processor and a program stored in the memory, the program being configured for execution by the processor, the processor when executing the program implementing the steps of the fare accounting method according to any one of claims 12-19.
22. A network system, characterized by: comprising a node device according to claim 20, a client server according to claim 21, and a service server and a client terminal; 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.
23. A medium storing a computer program, characterized in that: the computer program when executed by a processor implements:
a step of the charge accounting method according to any one of claims 1 to 11; or
A method of cost accounting according to any one of claims 12 to 19.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810451424.8A CN108737121B (en) | 2018-05-11 | 2018-05-11 | Cost accounting method, node device, client server, network system, and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810451424.8A CN108737121B (en) | 2018-05-11 | 2018-05-11 | Cost accounting method, node device, client server, network system, and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108737121A CN108737121A (en) | 2018-11-02 |
| CN108737121B true CN108737121B (en) | 2022-02-01 |
Family
ID=63937362
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810451424.8A Active CN108737121B (en) | 2018-05-11 | 2018-05-11 | Cost accounting method, node device, client server, network system, and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108737121B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101873345A (en) * | 2010-05-27 | 2010-10-27 | 中国科学院计算技术研究所 | Integrated block switching P2P shared-file system and method for motivating seed-providing for other nodes thereof |
| CN102624681A (en) * | 2011-01-30 | 2012-08-01 | 索尼公司 | Method and system for distributing copyrighted digital content in peer-to-peer network |
| CN102932460A (en) * | 2012-11-06 | 2013-02-13 | 北京交通大学 | Campus network peer-to-peer (P2P) incentive method based on contribution values |
| CN103299580A (en) * | 2011-12-30 | 2013-09-11 | 华为技术有限公司 | Service distribution method, device and system |
| CN103581245A (en) * | 2012-07-30 | 2014-02-12 | 腾讯科技（深圳）有限公司 | Content delivery method and system of content delivery network |
| CN105791427A (en) * | 2016-04-22 | 2016-07-20 | 百度在线网络技术（北京）有限公司 | Method, device and system for supplementing resource heat |
| CN105791247A (en) * | 2014-12-25 | 2016-07-20 | 中国移动通信集团公司 | Unified traffic payment business implementation method and associated equipment and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040203751A1 (en) * | 2002-10-21 | 2004-10-14 | Excino Technologies Inc. | Peer-to-peer (P2P) collaborative system for service aggregation, rapid service provisioning and service roaming |
-
2018
- 2018-05-11 CN CN201810451424.8A patent/CN108737121B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101873345A (en) * | 2010-05-27 | 2010-10-27 | 中国科学院计算技术研究所 | Integrated block switching P2P shared-file system and method for motivating seed-providing for other nodes thereof |
| CN102624681A (en) * | 2011-01-30 | 2012-08-01 | 索尼公司 | Method and system for distributing copyrighted digital content in peer-to-peer network |
| CN103299580A (en) * | 2011-12-30 | 2013-09-11 | 华为技术有限公司 | Service distribution method, device and system |
| CN103581245A (en) * | 2012-07-30 | 2014-02-12 | 腾讯科技（深圳）有限公司 | Content delivery method and system of content delivery network |
| CN102932460A (en) * | 2012-11-06 | 2013-02-13 | 北京交通大学 | Campus network peer-to-peer (P2P) incentive method based on contribution values |
| CN105791247A (en) * | 2014-12-25 | 2016-07-20 | 中国移动通信集团公司 | Unified traffic payment business implementation method and associated equipment and system |
| CN105791427A (en) * | 2016-04-22 | 2016-07-20 | 百度在线网络技术（北京）有限公司 | Method, device and system for supplementing resource heat |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108737121A (en) | 2018-11-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108683730B (en) | Resource scheduling method, service server, client terminal, network system and medium | |
| EP3143539B1 (en) | Content discovery in managed wireless distribution networks | |
| CN105491557B (en) | System and method for realizing capability opening and capability opening platform | |
| EP3143540B1 (en) | Distributing content in managed wireless distribution networks | |
| CN109525602B (en) | Method, mobile terminal and system for accessing network based on flow-free platform | |
| US20140149562A1 (en) | Method and system for providing user-based bandwidth management | |
| US20090178058A1 (en) | Application Aware Networking | |
| CN108616600B (en) | Resource scheduling method, client server, node device, network system, and medium | |
| CN107251525A (en) | For supporting the predictive content of mobile device user to prefetch the distributed server architecture of service | |
| EP3143541B1 (en) | Content delivery prioritization in managed wireless distribution networks | |
| EP3143748B1 (en) | Managed wireless distribution network | |
| US10985988B2 (en) | Profile generation for bandwidth management | |
| CN101132373A (en) | Method of providing qos for a flow | |
| CN106330997A (en) | Content distribution method and system for mobile terminal application | |
| KR20100048858A (en) | System and method for enabling p2p application in wireless mobile network | |
| US8565263B2 (en) | Dynamic adjustment of bandwidth for providing increased bandwidth during business hours | |
| CN108683728B (en) | Data transmission method, server, terminal, network system and storage medium | |
| CN108667935A (en) | Network service method, server, network system and storage medium | |
| CN113612640A (en) | Data communication method and device, electronic equipment and storage medium | |
| CN113596166A (en) | Data acquisition method and device, computer equipment and storage medium | |
| CN108737121B (en) | Cost accounting method, node device, client server, network system, and medium | |
| CN108683515B (en) | Fee accounting method, client terminal, service server, network system and medium | |
| Zhou et al. | Design, implementation, and measurement of a crowdsourcing-based content distribution platform | |
| CN108683726B (en) | Data transmission method, server, terminal, network system and storage medium | |
| US8301775B2 (en) | Affiliate bandwidth management |
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 |