CN106375132B - Cloud server system and management method thereof - Google Patents

Cloud server system and management method thereof Download PDF

Info

Publication number
CN106375132B
CN106375132B CN201610932432.5A CN201610932432A CN106375132B CN 106375132 B CN106375132 B CN 106375132B CN 201610932432 A CN201610932432 A CN 201610932432A CN 106375132 B CN106375132 B CN 106375132B
Authority
CN
China
Prior art keywords
service
supply
list
record table
management server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201610932432.5A
Other languages
Chinese (zh)
Other versions
CN106375132A (en
Inventor
廖冬生
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
TCL Technology Group Co Ltd
Original Assignee
TCL Technology Group Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by TCL Technology Group Co Ltd filed Critical TCL Technology Group Co Ltd
Priority to CN201610932432.5A priority Critical patent/CN106375132B/en
Publication of CN106375132A publication Critical patent/CN106375132A/en
Application granted granted Critical
Publication of CN106375132B publication Critical patent/CN106375132B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0876Aspects of the degree of configuration automation
    • H04L41/0886Fully automatic configuration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements
    • H04L67/30Profiles

Abstract

The invention discloses a management method of a cloud server system and the cloud server system, wherein the method comprises the steps of sending registration information to a pre-configured management server when a service system in the cloud server system is started, receiving and analyzing the registration information by the management server, and respectively storing a demand service list and a supply service list obtained by analysis in a pre-established demand record table and a supply record table; feeding back a supply service list meeting the business system in the supply record table to the business system; and the business system accesses the corresponding business system according to the fed back supply service list. The method can manage the configuration of each service system through the management server, and when the service system is changed (such as service expansion, recombination, fault instance replacement, code upgrading and the like), the manual modification of the scheduling configuration is not needed, so that the workload is reduced, and the flexibility of the service system is improved.

Description

Cloud server system and management method thereof
Technical Field
The invention relates to the technical field of cloud server systems, in particular to a management method of a cloud server system and the cloud server system.
Background
With the continuous development of the internet, all traditional industries are continuously added into the internet, the internet user amount shows a geometric-level growth speed, and the complexity of online services is higher and higher. In order to support the change of user quantity and service complexity, a typical phenomenon is that more and more service systems are arranged at a service system end, when the number of the service systems is increased to a certain degree, each function of one service is split into a plurality of service systems to be realized, and the degree of interdependence between the service systems is deepened. For example, to complete an A business system, a dozen or so other business systems such as B, C, D, E may be required to cooperate. From a mathematical point of view, it can be found that the dependency between service systems increases in exponential order, for example, 3 service systems have 3 paths and 6 service systems have 15 paths.
The calling between the existing service systems is generally recorded in each service system directly through a configuration file, and the calling is mutually called through the configuration file. However, when the number of the service systems is large, when the service system changes the interface or exits, other service systems calling the service system need to modify the configuration file and restart, and the problems of large coordination workload and low efficiency exist. For example, a total of 10 service systems in a certain service system depend on the I interface of the a service system, and if the a service system implements a new interface O, the function of the original I interface can be better provided, and if the existing 10 service systems are to be switched to the O interface, the configuration of tens of hundreds of machines of the 10 service systems is modified and then restarted.
In addition, if the service system A has 20 machines in total, when 5 of the service systems have faults, if other service systems access the service system A through the domain name, the service system A can also access the 5 fault machines before the domain name cache fails, and an execution error is generated; if other service systems access the A service system through IP, then each time the A service system adds or deletes a machine, tens or hundreds of machines of all other 10 service systems need to be modified synchronously, which causes a problem of large coordination workload.
Thus, the prior art has yet to be improved and enhanced.
Disclosure of Invention
The invention aims to provide a management method of a cloud server system and the cloud server system.
The technical scheme adopted by the invention is as follows:
a method of managing a cloud server system, comprising:
when any business system in the cloud server system is started, sending registration information to a pre-configured management server, wherein the registration information carries a demand service list and a supply service list;
the management server receives and analyzes the registration information, and respectively stores a demand service list and a supply service list obtained by analysis in a demand record table and a supply record table which are established in advance; and
feeding back all supply service lists meeting the requirements of the business system in the supply record table to the business system;
and the service system stores all the received service supply lists to a service list preset and configured by the service system, and accesses the corresponding service system according to the service list.
The management method of the cloud server system, wherein when any business system in the cloud server system exits, the method further comprises the following steps:
the service system sends logout information to a pre-configured management server;
the management server receives the logout information and sends the logout information of the service system to all service systems calling the service system;
and all the service systems calling the service system delete the service list correspondingly supplied by the service system from the service list preset and configured by the service system according to the logout information.
The management method of the cloud server system, wherein the step of receiving the logout information by the management server and sending the logout information of the service system to all service systems calling the service system further comprises the following steps:
and the management server deletes the supply service list and the demand service list corresponding to the business system in the demand record table and the supply record table.
The management method of the cloud server system, wherein after feeding back all the supply service lists meeting the requirements of the business system in the supply record table to the business system, the method further comprises:
the management server searches whether a service system requiring the service system exists in the requirement record table according to the supply service list obtained by analysis;
and when a service system requiring the service system exists, sending the supply service list to all service systems requiring the service system.
The management method of the cloud server system, wherein the feeding back all the supply service lists meeting the business system in the supply record table to the business system comprises:
the management server searches a supply service list meeting the requirements of the business system in the supply record table; and
and feeding back all searched supply server lists to the service system.
A cloud server system, comprising: the system comprises a plurality of service systems and a management server, wherein each service system comprises a first sending module and an access module;
the first sending module is used for sending registration information to a pre-configured management server when a service system is started, wherein the registration information carries a demand service list and a supply service list;
the access module is used for storing all the received supply service lists to the service lists with preset configuration and accessing the corresponding service systems according to the service lists;
the management server comprises a receiving module and a feedback module;
the receiving module is used for receiving and analyzing the registration information, and respectively storing a demand service list and a supply service list obtained by analysis into a demand record table and a supply record table which are established in advance;
and the feedback module is used for feeding back all the supply service lists meeting the service system in the supply record table to the service system.
The cloud server system, wherein the business system further comprises a second sending module and a first deleting module;
the second sending module is used for sending logout information to a pre-configured management server;
the first deleting module is used for deleting the supply service list corresponding to the business system from the service list preset and configured by the business system according to the logout information;
the management server further includes:
and the second receiving module is used for receiving the logout information and sending the logout information of the service system to all service systems calling the service system.
The cloud server system, wherein the management server further includes:
and the second deleting module is used for deleting the supply service list and the demand service list corresponding to the business system in the demand record table and the supply record table.
The cloud server system, wherein the management server further includes:
the searching module is used for searching whether a service system requiring the service system exists in the requirement record table according to the supply service list obtained by analysis;
and the third sending module is used for sending the supply service list to all the service systems requiring the service systems when the service systems requiring the service systems exist.
The cloud server system, wherein the feedback module further comprises:
the searching unit is used for searching a supply service list meeting the requirements of the business system in the supply record table;
and the feedback unit is used for feeding back all the searched supply server lists to the service system.
Has the advantages that: when a service system in the cloud server system is started, sending registration information to a pre-configured management server, receiving and analyzing the registration information by the management server, and respectively storing a demand service list and a supply service list obtained by analysis in a pre-established demand record table and a pre-established supply record table; feeding back a supply service list meeting the business system in the supply record table to the business system; and the business system accesses the corresponding business system according to the fed back supply service list. The method can manage the configuration of each service system through the management server, and when the service system is changed (such as service expansion, recombination, fault instance replacement, code upgrading and the like), the manual modification of the scheduling configuration is not needed, so that the workload is reduced, and the flexibility of the service system is improved.
Drawings
Fig. 1 is a flowchart of a preferred implementation of a management method of a cloud server system according to the present invention.
Fig. 2 is a timing chart of a preferred implementation of the management method of the cloud server system provided by the present invention.
Fig. 3 is a flowchart of a first embodiment of a management method of a cloud server system provided in the present invention.
Fig. 4 is a timing diagram of a first embodiment of a management method of a cloud server system according to the present invention.
Fig. 5 is a schematic structural diagram of a cloud server system provided in the present invention.
Detailed Description
The present invention provides a management method of a cloud server system and a cloud server system, and in order to make the purpose, technical scheme, and effect of the present invention clearer and clearer, the present invention is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In the present invention, suffixes such as "module", "part", or "unit" used to indicate elements are used only for facilitating the description of the present invention, and have no specific meaning in themselves. Thus, "module", "component" or "unit" may be used mixedly.
The invention will be further explained by the description of the embodiments with reference to the drawings.
Example one
Referring to fig. 1 and fig. 2, fig. 1 is a flowchart illustrating a preferred embodiment of a management method of a cloud server system according to the present invention, and fig. 2 is a timing diagram illustrating a preferred embodiment of a management method of a cloud server system according to the present invention. The method comprises the following steps:
s100, when any business system in the cloud server system is started, sending registration information to a pre-configured management server, wherein the registration information carries a demand service list and a supply service list.
Specifically, each service system in the cloud server system presets and configures an address or a unique identifier of the management server, so that the service system can quickly determine the management server through the address or the unique identifier. And when the service system is started, the registration information is sent to the management server through the address or the unique identifier of the management server which is preset and configured. It should be noted that the service system is composed of one server, and may include a plurality of servers.
The registration information carries a required service list of services which the business system needs to provide by other business systems in the cloud server system, and a supply service list of services which the business system can provide to other business systems in the cloud server system. In practical application, the demand service list and the supply service list are pre-stored in the business system, and when the business system provided by the business system or the demanded service changes, the business system can automatically update the demand service list and/or the supply service list, so that the demand service list and the supply service list stored in the business system are consistent with the service and the demanded service which can be provided by the business system, and the coordination between the business systems is improved.
Illustratively, in order to ensure that the demand service list and the supply service list stored in the management server are consistent with the demand service list and the supply service list stored in the business system. When the demand service list and the supply service list existing in the service system are updated, a process of updating the demand service list and the supply service list in the management server is also required, which may specifically be: when the business system updates the demand service list and the supply service list, the business system sends update information carrying the updated demand service list and supply service list to the management server, so that the management server updates the demand service list and supply service list stored by the management server according to the update information. Of course, in practical applications, when the business system updates the demand service or the supply service, the business system needs to be restarted, so that the demand service list and the supply service list updated at the time of restarting can be used for updating the demand service list and the supply service list in the management server.
In this embodiment, the demand service list is denoted as L1, and the supply service list is denoted as L2; the demand service list and the supply service list may be in the following formats:
l1: { service name N1, service name N2, service name N3
L2: { service name O1: { Host1+ Port1: URL1}, service name; o2: { Host2+ Port2: URL2},
when L1 or L2 is empty, it can be expressed as { }; the business system will be uniquely identified by its hostname or IP + Port (Port), i.e., Host + Port.
S200, the management server receives and analyzes the registration information, and stores a demand service list and a supply service list obtained through analysis in a demand record table and a supply record table which are established in advance respectively.
Specifically, after the service system sends the registration information to the management service, the management server receives the registration information, and analyzes the registration information to obtain a demand service list and a supply service list carried in the registration information. And after the demand service list and the supply service list are obtained through analysis, respectively storing the demand service list and the supply service list of the business system in a demand record table and a supply record table which are preset in the business system. In practical application, the management server may directly add the service information of the demand service list and the supply service list provided by the business system into the demand record table and the supply record table, respectively.
The requirement record table and the supply record table of the management server record a requirement service list and a supply service list of a business system and a unique identifier of the business system, and the unique identifier of the business system is stored corresponding to the requirement service list and the supply service list of the business system, so that the services which can be provided by the business system or the business system which can provide the services can be rapidly determined.
Illustratively, the demand record is denoted as R1, and the supply record is denoted as R2; the requirement record table R1 and the supply record table R2 will be described by taking as an example the case where service information in the requirement service list and the supply service list is added to the requirement record table and the supply record table, respectively. The form of the demand record table R1 is shown in Table 1, and the form of the supply record table R2 is shown in Table 2;
table 1 requirement record table R1 storage form
Figure 629620DEST_PATH_IMAGE001
Table 2 supply record table R2 storage form
Figure 77919DEST_PATH_IMAGE002
Wherein, the style of the URL (uniform resource locator) may be:
Figure 654393DEST_PATH_IMAGE003
s300, feeding back all supply service lists meeting the requirements of the business system in the supply record table to the business system.
Specifically, after storing a demand service list and a supply service list in a demand record table and a supply record table respectively, the management server searches a supply service list meeting the demand in the supply service list according to the demand service list, and feeds back the supply service list to the business system.
In this embodiment, after the service system sends the registration information to the management server, the management server detects whether a service required in a requirement record table stored in the management server exists in a supply service list provided by the service system, and if the service required in the requirement record table stored in the management server exists, the management server sends the service information provided by the service system to the corresponding service system, so that other service systems in the cloud server system call the service provided by the service system.
S400, the service system stores all the received service supply lists to a service list of preset configuration, and accesses the corresponding service system according to the service list.
Specifically, after the management server feeds back the provisioning service list, the service system receives the provisioning service list sent by the management server, and stores the provisioning service list meeting the self-demand in a local area, and when a corresponding service is subsequently used, directly obtains a required service URL (uniform resource identifier) or an interface from the provisioning service list. In this embodiment, when one service corresponds to a plurality of URLs, one of the URLs is randomly selected to access the corresponding service system; when a service does not have any corresponding URL, alarm information is sent.
Example two
The present embodiment provides a management method for a cloud server system, which adds a management procedure for logging out a service system on the basis of the foregoing embodiments, and as shown in fig. 3 and 4, the logging out management procedure specifically includes:
s500, when any service system in the cloud server system exits, the service system sends logout information to a pre-configured management server;
s600, the management server receives the logout information and sends the logout information of the service system to all service systems calling the service system;
s700, all the service systems calling the service system delete the service list correspondingly provided by the service system from the preset service list according to the logout information.
Specifically, when each business system exits, a logout message is sent to the management server to inform the management server that it is about to exit from the no-longer-service system. When the management server receives the logout information, all the service systems using the services provided by the service systems are informed to quit the service not being provided, other service systems using the service provided by the service systems are prompted to delete the service providing lists of the service systems in the corresponding service providing lists maintained by the service systems respectively, and the service systems are not required to request the corresponding services subsequently. And simultaneously, the management server deletes the demand service list and the supply service list corresponding to the business system from the demand record table and the supply record table respectively.
The present invention also provides a cloud server system, as shown in fig. 5, which includes: the system comprises a plurality of service systems 100 and a management server 200, wherein each service system 100 comprises a first sending module and an access module;
the first sending module is used for sending registration information to a pre-configured management server when a service system is started, wherein the registration information carries a demand service list and a supply service list;
the access module is used for storing all the received supply service lists to the service lists with preset configuration and accessing the corresponding service systems according to the service lists;
the management server 200 includes a receiving module and a feedback module;
the receiving module is used for receiving and analyzing the registration information, and respectively storing a demand service list and a supply service list obtained by analysis into a demand record table and a supply record table which are established in advance;
and the feedback module is used for feeding back all the supply service lists meeting the service system in the supply record table to the service system.
The cloud server system, wherein the business system further comprises a second sending module and a first deleting module;
the second sending module is used for sending logout information to a pre-configured management server;
the first deleting module is used for deleting the supply service list corresponding to the business system from the service list preset and configured by the business system according to the logout information;
the management server further includes:
and the second receiving module is used for receiving the logout information and sending the logout information of the service system to all service systems calling the service system.
The cloud server system, wherein the management server further includes:
and the second deleting module is used for deleting the supply service list and the demand service list corresponding to the business system in the demand record table and the supply record table.
The cloud server system, wherein the management server further includes:
the searching module is used for searching whether a service system requiring the service system exists in the requirement record table according to the supply service list obtained by analysis;
and the third sending module is used for sending the supply service list to all the service systems requiring the service systems when the service systems requiring the service systems exist.
The cloud server system, wherein the feedback module further comprises:
the searching unit is used for searching a supply service list meeting the requirements of the business system in the supply record table;
and the feedback unit is used for feeding back all the searched supply server lists to the service system.
In the embodiments provided in the present invention, it should be understood that the disclosed business system and method can be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is only one logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another service system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a business system, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims (8)

1. A management method of a cloud server system is characterized by comprising the following steps:
when any business system in the cloud server system is started, sending registration information to a pre-configured management server, wherein the registration information carries a demand service list and a supply service list;
the management server receives and analyzes the registration information, and respectively stores a demand service list and a supply service list obtained by analysis in a demand record table and a supply record table which are established in advance; and
feeding back all supply service lists meeting the requirements of the business system in the supply record table to the business system;
the feeding back all the supply service lists meeting the business system in the supply record table to the business system comprises:
the management server searches a supply service list meeting the requirements of the business system in the supply record table; and
feeding back all searched supply service lists to the service system;
and the service system stores all the received service supply lists to a service list preset and configured by the service system, and accesses the corresponding service system according to the service list, wherein if the same service in the service list corresponds to a plurality of service systems, the service system randomly accesses any one of the plurality of service systems corresponding to the same service.
2. The method for managing the cloud server system according to claim 1, wherein when any business system in the cloud server system exits, the method further comprises:
the service system sends logout information to a pre-configured management server;
the management server receives the logout information and sends the logout information of the service system to all service systems calling the service system;
and all the service systems calling the service system delete the service list correspondingly supplied by the service system from the service list preset and configured by the service system according to the logout information.
3. The method for managing a cloud server system according to claim 2, wherein the step of the management server receiving the logout information and sending the service system logout information to all service systems invoking the service systems further comprises:
and the management server deletes the supply service list and the demand service list corresponding to the business system in the demand record table and the supply record table.
4. The method for managing the cloud server system according to claim 1, wherein the feeding back all the provision service lists satisfying the requirements of the business system in the provision record table to the business system further comprises:
the management server searches whether a service system requiring the service system exists in the requirement record table according to the supply service list obtained by analysis;
and when a service system requiring the service system exists, sending the supply service list to all service systems requiring the service system.
5. A cloud server system, comprising: the system comprises a plurality of service systems and a management server, wherein each service system comprises a first sending module and an access module;
the first sending module is used for sending registration information to a pre-configured management server when a service system is started, wherein the registration information carries a demand service list and a supply service list;
the access module is used for storing all the received service supply lists to a service list preset and configured by the service supply list, and accessing the corresponding service system according to the service list, wherein if the same service in the service list corresponds to a plurality of service systems, the service system randomly accesses any one of the plurality of service systems corresponding to the same service;
the management server comprises a receiving module and a feedback module;
the receiving module is used for receiving and analyzing the registration information, and respectively storing a demand service list and a supply service list obtained by analysis into a demand record table and a supply record table which are established in advance;
the feedback module is used for feeding back all the supply service lists meeting the service system in the supply record table to the service system;
the feedback module further comprises:
the searching unit is used for searching a supply service list meeting the requirements of the business system in the supply record table;
and the feedback unit is used for feeding back all the searched supply service lists to the service system.
6. The cloud server system of claim 5, wherein the business system further comprises a second sending module and a first deleting module;
the second sending module is used for sending logout information to a pre-configured management server;
the first deleting module is used for deleting the supply service list corresponding to the business system from the service list preset and configured by the business system according to the logout information;
the management server further includes:
and the second receiving module is used for receiving the logout information and sending the logout information of the service system to all service systems calling the service system.
7. The cloud server system of claim 6, wherein the management server further comprises:
and the second deleting module is used for deleting the supply service list and the demand service list corresponding to the business system in the demand record table and the supply record table.
8. The cloud server system of claim 5, wherein the management server further comprises:
the searching module is used for searching whether a service system requiring the service system exists in the requirement record table according to the supply service list obtained by analysis;
and the third sending module is used for sending the supply service list to all the service systems requiring the service systems when the service systems requiring the service systems exist.
CN201610932432.5A 2016-11-01 2016-11-01 Cloud server system and management method thereof Active CN106375132B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610932432.5A CN106375132B (en) 2016-11-01 2016-11-01 Cloud server system and management method thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610932432.5A CN106375132B (en) 2016-11-01 2016-11-01 Cloud server system and management method thereof

Publications (2)

Publication Number Publication Date
CN106375132A CN106375132A (en) 2017-02-01
CN106375132B true CN106375132B (en) 2021-04-13

Family

ID=57896126

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610932432.5A Active CN106375132B (en) 2016-11-01 2016-11-01 Cloud server system and management method thereof

Country Status (1)

Country Link
CN (1) CN106375132B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022040167A1 (en) * 2020-08-17 2022-02-24 Google Llc System service sharing between endpoint devices for increased endpoint device capability
CN112181501B (en) * 2020-09-02 2024-02-23 中国银联股份有限公司 Service framework of application, service control method, device and computer readable storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1604042A (en) * 2003-09-30 2005-04-06 国际商业机器公司 Method for dispatching task, dispatcher and net computer system
CN102137014A (en) * 2011-03-11 2011-07-27 华为技术有限公司 Resource management method, system and resource manager
CN103841129A (en) * 2012-11-21 2014-06-04 华为技术有限公司 Cloud computing resource information acquisition server, cloud computing resource information acquisition client and information processing method
CN104461736A (en) * 2014-12-08 2015-03-25 畅捷通信息技术股份有限公司 Resource allocation and search method and system and cloud server

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103533006B (en) * 2012-07-06 2019-09-24 中兴通讯股份有限公司 A kind of joint cloud disk client, server, system and joint cloud disk service method

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1604042A (en) * 2003-09-30 2005-04-06 国际商业机器公司 Method for dispatching task, dispatcher and net computer system
CN102137014A (en) * 2011-03-11 2011-07-27 华为技术有限公司 Resource management method, system and resource manager
CN103841129A (en) * 2012-11-21 2014-06-04 华为技术有限公司 Cloud computing resource information acquisition server, cloud computing resource information acquisition client and information processing method
CN104461736A (en) * 2014-12-08 2015-03-25 畅捷通信息技术股份有限公司 Resource allocation and search method and system and cloud server

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"制造云服务的按需供应模式及其关键技术";黄沈权等;《计算机集成制造系统》;20130915;第2323页左栏第28行-右栏第10行,图7 *

Also Published As

Publication number Publication date
CN106375132A (en) 2017-02-01

Similar Documents

Publication Publication Date Title
US10715485B2 (en) Managing dynamic IP address assignments
US10776104B2 (en) Systems and methods for tracking configuration file changes
CN100593165C (en) System and method for automatically updating a wireless device
US11720904B2 (en) Consent management system with device registration process
RU2357283C2 (en) Scheme for refreshing connection with network printing device for clients of printer device
CN109451088A (en) A kind of data access method and device
CN108200220A (en) A kind of method of data synchronization, server and storage medium
CN108881066B (en) Routing request method, access server and storage device
CN105049252A (en) Method and device for managing configuration information
US10972564B2 (en) System and method for automating actions in distributed computing
CN107404509A (en) Distributed Services configure system and approaches to IM
CN107992350B (en) Method and device for generating configuration overview page
CN106375132B (en) Cloud server system and management method thereof
WO2018082079A1 (en) Method and apparatus for dynamically managing data exchange
CN110798358B (en) Distributed service identification method and device, computer readable medium and electronic equipment
US10713278B2 (en) Flexible configuration of offline synchronization scope
KR20100035681A (en) Data storing system and data processing method of informational household appliance
CN108196962B (en) Method and device for realizing calling of interfaces of different versions
CN110650033B (en) Distributed application configuration management method and distributed computing system
US20200403862A1 (en) Systems and methods for cloud resource synchronization
CN114928604B (en) File distribution method and device
CN104298750B (en) Renewal processing method and processing device for real-time system communication
CN116614323B (en) Cloud storage enterprise network management method and system based on Rclone
CN112988168A (en) Method and device for building environment
CN111176716A (en) Upgrade package generation method and device, electronic equipment and storage medium

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
CB02 Change of applicant information

Address after: 516006 TCL science and technology building, No. 17, Huifeng Third Road, Zhongkai high tech Zone, Huizhou City, Guangdong Province

Applicant after: TCL Technology Group Co.,Ltd.

Address before: 516006 Guangdong province Huizhou Zhongkai hi tech Development Zone No. nineteen District

Applicant before: TCL RESEARCH AMERICA Inc.

CB02 Change of applicant information
GR01 Patent grant
GR01 Patent grant