[go: up one dir, main page]

WO2018000617A1 - 一种数据库的更新方法及调度服务器 - Google Patents

一种数据库的更新方法及调度服务器 Download PDF

Info

Publication number
WO2018000617A1
WO2018000617A1 PCT/CN2016/099969 CN2016099969W WO2018000617A1 WO 2018000617 A1 WO2018000617 A1 WO 2018000617A1 CN 2016099969 W CN2016099969 W CN 2016099969W WO 2018000617 A1 WO2018000617 A1 WO 2018000617A1
Authority
WO
WIPO (PCT)
Prior art keywords
content server
interface
database
server
interface information
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.)
Ceased
Application number
PCT/CN2016/099969
Other languages
English (en)
French (fr)
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.)
Le Holdings Beijing Co Ltd
LeCloud Computing Co Ltd
Original Assignee
Le Holdings Beijing Co Ltd
LeCloud Computing 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 Le Holdings Beijing Co Ltd, LeCloud Computing Co Ltd filed Critical Le Holdings Beijing Co Ltd
Publication of WO2018000617A1 publication Critical patent/WO2018000617A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23Updating
    • G06F16/235Update request formulation

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method for updating a database and a scheduling server.
  • the content distribution network CDN sends a connection between the CDN and the user equipment UE to the scheduling server (Global Server Load Balance, GSLB) every ten seconds, that is, the connection situation includes the number of connection interfaces used by the content distribution network CDN. The value and the number of remaining connection interfaces.
  • the scheduling server may determine, according to the connection situation sent by the content distribution network CDN, which user distribution network CDN establishes a connection with the content distribution network CDN.
  • the scheduling server reports the connection status, that is, the number of used connection interfaces is 900, and the number of remaining connection interfaces is 100.
  • the scheduling server allocates 100 connection interfaces available to the content distribution network CDN to the user equipment according to the connection request sent by the user equipment, and the user equipment implements the connection with the content distribution network CDN through the allocated connection interface. If the period of the connection situation is not reported to the content distribution network CDN at this time, the scheduling server still considers that the number of connection interfaces remaining in the content distribution network CDN is 100.
  • connection request sent by the user equipment to download the multimedia is a random event, it is possible that the number of connection requests for downloading multimedia received by the scheduling server suddenly increases. If the user equipment sends a connection request to the dispatch server again at this time, the dispatch server may still allocate the connection interface of the content distribution network CDN to the user equipment. However, the content distribution network CDN actually has no assignable connection interface for the newly connected user equipment to connect, and obviously such a scheduling method is obviously unreasonable.
  • the content distribution network CDN periodically reports the connection status of the content distribution network CDN to the scheduling server GSLB.
  • the update mode will result in the connection status of the content distribution network CDN and the content distribution network learned by the scheduling server GSLB.
  • the actual connection of the CDN does not match, causing the scheduling to fail. If the reporting period of the content distribution network CDN is shortened, the load of the content distribution network CDN is too large, which affects the playback quality of the connected user equipment on the content distribution network CDN.
  • the application provides a database update method and a scheduling server, which are used to ensure that the interface information of the content server stored in the database in the scheduling server and the interface of the content server are actual without changing the reporting period of the content server.
  • the connection situation is consistent, which improves the scheduling efficiency of the scheduling server.
  • an embodiment of the present application provides a method for updating a database, including:
  • an embodiment of the present application provides a scheduling server, including: at least one processor; and a memory; wherein the memory stores an instruction executable by the at least one processor, where the instruction is A processor is operative to enable the at least one processor to perform an update method of any of the above-described databases of the present application.
  • the method for updating the database and the scheduling server determine the interface identifier of the content server allocated to the user equipment according to the received request sent by the user equipment and the interface information of the content server in the database, and then according to the determined
  • the interface identifier of the content server updates the interface information of the content server corresponding to the interface identifier in the database, so as to ensure interface information of the content server stored in the database in the scheduling server without changing the reporting period of the content server.
  • the actual connection status of the interface of the content server is consistent, the scheduling efficiency of the scheduling server is improved, and the resource scheduling is more reasonable, especially in the case of large concurrent, the efficiency and rationality of the scheduling server scheduling are improved.
  • FIG. 1 is a flowchart of a method for updating a database provided by an embodiment of the present application
  • FIG. 2 is a flowchart of a method for updating a database according to an embodiment of the present application
  • FIG. 3 is a flowchart of a method for updating a database according to an embodiment of the present application
  • FIG. 4 is a flowchart of a method for updating a database according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of an apparatus for updating a database according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a scheduling server according to an embodiment of the present application.
  • the application provides a database update method and a scheduling server, which are used to ensure that the interface information of the content server stored in the database in the scheduling server and the interface of the content server are actual without changing the reporting period of the content server.
  • the connection situation is consistent, which improves the scheduling efficiency of the scheduling server.
  • an embodiment of the present application provides a method for updating a database, including:
  • S101 Receive a request for acquiring an interface identifier of a content server.
  • the interface identifier of the content server allocated to the user equipment is determined according to the received request sent by the user equipment and the interface information of the content server in the database, and then the database is updated according to the determined interface identifier of the content server.
  • the interface identifies the interface information of the content server, so as to ensure that the interface information of the content server stored in the database in the scheduling server and the actual connection of the interface of the content server are maintained without changing the reporting period of the content server. Consistently, improve the scheduling efficiency of the scheduling server.
  • the response of the interface identifier including the determined content server is generated, and the generated response is sent to the user equipment.
  • the method for updating the database includes:
  • the interface information in the request received by the content server is the same as the interface information of the content server in the database, it is ensured that the interface information of the content server stored in the database is consistent with the interface usage of the content server. If not, the interface information of the content server in the database is updated, thereby ensuring that the interface information of the content server stored in the database is consistent with the interface usage of the content server.
  • the content server may periodically send a request for updating the interface information of the content server according to a preset period.
  • the request for updating the interface information of the content server may be sent to the scheduling server by triggering the content server.
  • the request for updating the interface information of the content server is sent according to multiple manners, so as to ensure that the interface information of the content server stored in the database is consistent with the interface usage of the content server in different environments.
  • the interface information of the content server includes the number of connected interfaces and/or the number of unconnected interfaces.
  • the interface information of the content server further includes: a mapping relationship between the number of connected interfaces of the content server and an interface identifier of the content server, and/or an interface number of the unconnected interface and the interface of the content server.
  • the mapping relationship of the identity is not limited to: a mapping relationship between the number of connected interfaces of the content server and an interface identifier of the content server, and/or an interface number of the unconnected interface and the interface of the content server.
  • the interface identifier of the content server allocated to the user equipment includes a connection address of an interface of the content server allocated to the user equipment.
  • the interface identifier of the content server allocated to the user equipment is not limited to the connection address of the interface of the content server allocated to the user equipment, and any identifier of the interface capable of determining the content server may be .
  • the interface information of the content server corresponding to the interface identifier in the database is updated according to the determined interface identifier of the content server, including:
  • the number of connected interfaces of the content servers in the database is increased and/or the number of unconnected interfaces of the content servers in the database is reduced.
  • the response increases or decreases the number of connected interfaces of the content server in the database or the number of unconnected interfaces, thereby implementing update of the interface information of the content server corresponding to the interface identifier in the database, that is, implementing the content server without changing.
  • the interface information of the content server stored in the database in the scheduling server is consistent with the actual connection status of the interface of the content server, and the scheduling efficiency of the scheduling server is improved.
  • the scheduling server may be a global load balancing GSLB, and the content server may be a content distribution network CDN.
  • the content distribution network CDN includes a multimedia file, such as a video file.
  • the user equipment sends a request for acquiring an interface identifier of the content server to the scheduling server.
  • the scheduling server determines, according to the received request for acquiring the interface identifier of the content server and the interface information of the content server in the preset database, the interface of the content server corresponding to the interface identifier allocated to the user equipment. Connection address.
  • the scheduling server generates a response including an interface identifier of the determined content server according to the determined connection address of the interface of the content server.
  • the scheduling server increases the number of connected interfaces of the content server in the database and/or reduces the content server in the database according to the number of connection addresses of interfaces of the content server determined in the generated response message.
  • the number of unconnected interfaces that is, the interface information of the content server in the database in the scheduling server is updated.
  • the scheduling server sends the generated response message to the user equipment.
  • the content server When the content server reaches the reporting period, the content server sends a request for updating the interface information of the content server to the scheduling server.
  • step S304 and step S305 are not limited to the order provided by the embodiment of the present application.
  • the user equipment sends a request for connecting the content distribution network CDN to download a video file to the scheduling server.
  • the scheduling server searches for a content distribution network that stores the video file corresponding to the video file identifier in the preset database according to the received video file identifier in the request for acquiring the interface identifier of the content distribution network CDN. CDN.
  • the scheduling server determines an interface identifier of the content distribution network CDN according to the search result of step S402.
  • the scheduling server determines, according to the interface identifier of the content distribution network CDN and the mapping relationship between the connection address of the interface of the content distribution network CDN and the interface identifier of the CDN in the preset database, to determine that the user equipment downloads the video file.
  • the connection address of the interface of the content distribution network CDN that is, the IP (Internet Protocol) address of the interface of the content distribution network CDN; wherein the mapping relationship may be a one-to-one correspondence.
  • the scheduling server generates a response for connecting to the content server according to the connection address of the interface of the determined content distribution network CDN, wherein the response includes a connection address of the interface of the determined content distribution network CDN.
  • the scheduling server sends the response to the user equipment.
  • the scheduling server updates the number of connected interfaces of the content server in the database and/or the number of unconnected interfaces according to the connection address of the interface of the content server in the response generated in step S405.
  • the user equipment determines, according to the received response message, a connection address of an interface of the content server.
  • the user equipment sends a connection request to the content distribution network CDN corresponding to the determined connection address.
  • the content distribution network CDN parses the received connection request and performs a connection operation.
  • the content distribution network CDN returns a response including the processing result to the user equipment.
  • step S406 and step S407 are not limited to the order provided by the embodiment of the present application.
  • an embodiment of the present application provides a database update apparatus, including:
  • the receiving module 501 is configured to receive a request for acquiring an interface identifier of the content server
  • the response module 502 is configured to determine, according to the received request and the interface information of the content server in the preset database, an interface identifier of the content server allocated to the user equipment;
  • the update module 503 is configured to update interface information of the content server corresponding to the interface identifier in the database according to the determined interface identifier of the content server.
  • the interface information of the content server includes the number of connected interfaces and/or the number of unconnected interfaces.
  • the interface identifier of the content server allocated to the user equipment includes a connection address of an interface of the content server allocated to the user equipment.
  • the update module 503 is specifically configured to:
  • the number of connected interfaces of the content server in the database is increased and/or the number of unconnected interfaces of the content server in the database is increased according to the determined number of connection addresses of the interface identifier of the content server.
  • the update module 503 is further configured to:
  • the interface information of the content server in the received request is different from the interface information of the content server in the database, the interface information of the content server in the database is updated.
  • an embodiment of the present application provides a scheduling server, including: a processor 601; and a memory 602.
  • the processor 601 includes: a receiving module 501, a response module 502, and an updating module 503, where
  • the receiving module 501 is configured to receive a request for acquiring an interface identifier of the content server
  • the response module 502 is configured to: according to the received request and the preset content server in the database Interface information, determining an interface identifier of a content server allocated to the user equipment;
  • the update module 503 is configured to update interface information of the content server corresponding to the interface identifier in the database according to the determined interface identifier of the content server.
  • the interface information of the content server includes the number of connected interfaces and/or the number of unconnected interfaces.
  • the interface identifier of the content server allocated to the user equipment includes a connection address of an interface of the content server allocated to the user equipment.
  • the update module 503 is specifically configured to:
  • the number of connected interfaces of the content servers in the database is increased and/or the number of unconnected interfaces of the content servers in the database is reduced.
  • the update module 503 is further configured to:
  • the interface information of the content server in the received request is different from the interface information of the content server in the database, the interface information of the content server in the database is updated.
  • An embodiment of the present application provides an update system for a database, where the update system includes: a content server, a user equipment, and the foregoing scheduling server.
  • the scheduling server may be a global load balancing GSLB, and the content server may be a content distribution network CDN.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • the various embodiments can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on such understanding, the above technical solutions can contribute in essence or to the relevant technologies.
  • the computer software product can be stored in a computer readable storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes a plurality of instructions for causing a computer device (which can be a personal computer or a server) , or a network device, etc.) performs the methods described in various embodiments or portions of the embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请提供一种数据库的更新方法及调度服务器,用以实现在不改变内容服务器的上报周期的前提下,确保调度服务器中的数据库存储的内容服务器的接口信息与该内容服务器的接口的实际的连接情况相一致,提升调度服务器的调度效率。所述方法包括,接收用于获取内容服务器的接口标识的请求;根据接收到的请求以及预设的数据库中内容服务器的接口信息,确定分配给所述用户设备的内容服务器的接口标识;根据确定的内容服务器的接口标识,更新所述数据库中所述接口标识对应的内容服务器的接口信息。

Description

一种数据库的更新方法及调度服务器
本申请要求在2016年06月29日提交中国专利局、申请号为201610500354.1、发明名称为“一种数据库的更新方法、装置及系统”的中国专利申请的优先权,该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域,尤其涉及一种数据库的更新方法及调度服务器。
背景技术
在信息资源爆炸的时代,多媒体信息的增长量呈现指数型的增长。多媒体信息的存储成为日益关注的热点问题。此时,内容分发网络(Content Delivery Network,CDN)应运而生。通过在现有的因特网(Internet)中增加一层新的网络架构,将网站的内容发布到最接近用户的网络”边缘”,并将用户请求导向最近的服务节点,解决因特网(Internet)网络拥塞状况,提高用户访问网站的响应速度。从技术上全面解决由于网络带宽小、用户访问量大、网点分布不均等原因,解决用户访问网站的响应速度慢的根本原因。虽然内容分发网络CND在一定程度上改善了网络带宽小,用户访问量大的问题,然而,每一内容分发网络CDN的连接接口仍然是有限的。
现有技术中,内容分发网络CDN每十秒向调度服务器(Global Server Load Balance,GSLB)发送CDN与用户设备UE的连接情况,即该连接情况包括,内容分发网络CDN已用的连接接口的数量值以及剩余的连接接口的数量值。当用户设备向调度服务器发送下载多媒体信息的连接请求时,调度服务器可根据内容分发网络CDN发送的连接情况,确定该用户设备与哪一内容分发网络CDN建立连接。
假设内容分发网络CDN的最大连接接口为1000,该内容分发网络CDN向 调度服务器上报连接情况,即已用的连接接口的数量值为900,剩余的连接接口的数量值为100。该调度服务器根据用户设备发送的连接请求,给用户设备分配了该内容分发网络CDN可用的100个连接接口,用户设备通过分配的连接接口实现了与内容分发网络CDN的连接。若此时尚未到该内容分发网络CDN上报连接情况的周期,则调度服务器仍然认为该内容分发网络CDN剩余的连接接口的数量值为100。发明人发现,由于用户设备发送下载多媒体的连接请求是随机事件,即有可能出现调度服务器接收到的下载多媒体的连接请求数量突增。若此时再次有用户设备向该调度服务器发送连接请求,调度服务器可能仍然会给该用户设备分配该内容分发网络CDN的连接接口。然而,该内容分发网络CDN实际上已经没有可分配的连接接口,供新连接的用户设备连接,显然此种调度方式明显不合理。
综上所述,现有技术中内容分发网络CDN周期性向调度服务器GSLB上报该内容分发网络CDN的连接情况,然而该更新方式将导致调度服务器GSLB获知的内容分发网络CDN的连接情况与内容分发网络CDN的实际连接情况不符,使得调度失败。若缩短内容分发网络CDN的上报周期,则会造成内容分发网络CDN的负载过大,影响该内容分发网络CDN上连接的用户设备的播放质量。
发明内容
本申请提供一种数据库的更新方法及调度服务器,用以实现在不改变内容服务器的上报周期的前提下,确保调度服务器中的数据库存储的内容服务器的接口信息与该内容服务器的接口的实际的连接情况相一致,提升调度服务器的调度效率。
第一方面,本申请实施例提供一种数据库的更新方法,包括:
接收用于获取内容服务器的接口标识的请求;
根据接收到的请求以及预设的数据库中内容服务器的接口信息,确定分配给所述用户设备的内容服务器的接口标识;
根据确定的内容服务器的接口标识,更新所述数据库中所述接口标识对 应的内容服务器的接口信息。
第二方面,本申请实施例提供一种调度服务器,包括:至少一个处理器;以及存储器;其中,所述存储器存储有可被所述至少一个处理器执行的指令,所述指令被所述至少一个处理器执行,以使所述至少一个处理器能够执行本申请上述任一项数据库的更新方法。
本申请实施例提供的一种数据库的更新方法及调度服务器,根据接收到的用户设备发送的请求以及数据库中内容服务器的接口信息,确定分配给用户设备的内容服务器的接口标识,再根据确定的内容服务器的接口标识,更新数据库中该接口标识所对应的内容服务器的接口信息,从而实现在不改变内容服务器的上报周期的前提下,确保调度服务器中的数据库存储的内容服务器的接口信息与该内容服务器的接口的实际的连接情况相一致,提升调度服务器的调度效率,使得资源调度更合理,尤其在大并发的情况下,提高调度服务器调度的效率以及合理性。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明,这些示例性说明并不构成对实施例的限定,附图中具有相同参考数字标号的元件表示为类似的元件,除非有特别申明,附图中的图不构成比例限制。
图1本申请实施例提供的数据库的更新方法的流程图;
图2为本申请实施例提供的数据库的更新方法的流程图;
图3为本申请实施例提供的数据库的更新方法的流程图;
图4为本申请实施例提供的数据库的更新方法的流程图;
图5为本申请实施例提供的数据库的更新装置的结构示意图;
图6为本申请实施例提供的调度服务器的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚,以下将参照本申请实施 例中的附图,通过实施方式清楚、完整地描述本申请的技术方案,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。
本申请提供一种数据库的更新方法及调度服务器,用以实现在不改变内容服务器的上报周期的前提下,确保调度服务器中的数据库存储的内容服务器的接口信息与该内容服务器的接口的实际的连接情况相一致,提升调度服务器的调度效率。
参见图1,本申请实施例提供一种数据库的更新方法,包括:
S101、接收用于获取内容服务器的接口标识的请求;
S102、根据接收到的请求以及预设的数据库中内容服务器的接口信息,确定分配给所述用户设备的内容服务器的接口标识;
S103、根据确定的内容服务器的接口标识,更新所述数据库中所述接口标识对应的内容服务器的接口信息。
本申请实施例中,通过根据接收到的用户设备发送的请求以及数据库中内容服务器的接口信息,确定分配给用户设备的内容服务器的接口标识,再根据确定的内容服务器的接口标识,更新数据库中该接口标识所对应的内容服务器的接口信息,从而实现在不改变内容服务器的上报周期的前提下,确保调度服务器中的数据库存储的内容服务器的接口信息与该内容服务器的接口的实际的连接情况相一致,提升调度服务器的调度效率。
具体地,在步骤S103更新所述数据库中所述接口标识对应的内容服务器的接口信息的同时,生成包括所述确定的内容服务器的接口标识的响应,并将生成的响应发送给用户设备。
其中,参见图2,为确保数据库中存储的内容服务器的接口信息与该内容服务器的接口使用情况相一致,本申请实施例除上述步骤外,数据库的更新方法还包括:
S201、接收到内容服务器发送的用于更新内容服务器的接口信息的请求;
S202、若接收到的请求中内容服务器的接口信息与所述数据库中内容服务器的接口信息不同,则更新所述数据库中内容服务器的接口信息。
本申请实施例中,若内容服务器接收到的请求中的接口信息与所述数据库中内容服务器的接口信息相同,则确保数据库中存储的内容服务器的接口信息与该内容服务器的接口使用情况相一致;若不相同,则更新所述数据库中的内容服务器的接口信息,从而确保数据库中存储的内容服务器的接口信息与该内容服务器的接口使用情况相一致。
其中,内容服务器可根据预设的周期,周期性发送用于更新内容服务器的接口信息的请求;亦可通过对内容服务器的触发,实现向调度服务器发送用于更新内容服务器的接口信息的请求。
本申请实施例中,根据多种方式发送用于更新内容服务器的接口信息的请求,从而确保在不同环境下,数据库中存储的内容服务器的接口信息与该内容服务器的接口使用情况均一致。
具体地,所述内容服务器的接口信息包括,已连接的接口的数量和/或未连接的接口的数量。
本申请实施例中,所述内容服务器的接口信息还包括,内容服务器的已连接的接口的数量与该内容服务器的接口标识的映射关系和/或未连接的接口的数量与该内容服务器的接口标识的映射关系。
具体地,所述分配给所述用户设备的内容服务器的接口标识包括,分配给所述用户设备的内容服务器的接口的连接地址。
本申请实施例中,所述分配给所述用户设备的内容服务器的接口标识并不局限于分配给所述用户设备的内容服务器的接口的连接地址,任何能够确定内容服务器的接口的标识均可。
其中,根据确定的内容服务器的接口标识,更新所述数据库中所述接口标识对应的内容服务器的接口信息,包括:
根据确定的内容服务器的接口的连接地址的数量,增加所述数据库中内容服务器的已连接的接口的数量和/或减少所述数据库中内容服务器的未连接的接口的数量。
本申请实施例中,通过根据确定的内容服务器的接口的连接地址的数量, 响应的增加或减少数据库中内容服务器的已连接的接口的数量或未连接的接口的数量,从而实现对数据库中该接口标识所对应的内容服务器的接口信息的更新,即实现在不改变内容服务器的上报周期的前提下,确保调度服务器中的数据库存储的内容服务器的接口信息与该内容服务器的接口的实际的连接情况相一致,提升调度服务器的调度效率。
其中,所述调度服务器可为全局负载均衡GSLB,所述内容服务器可为内容分发网络CDN。其中,所述内容分发网络CDN包括多媒体文件,例如视频文件。
为便于理解,下面将结合图3,对数据库的更新方法的整体流程进一步进行解释说明。
S301、用户设备向调度服务器发送用于获取内容服务器的接口标识的请求。
S302、所述调度服务器根据接收到的用于获取内容服务器的接口标识的请求以及预设数据库中内容服务器的接口信息,确定分配给所述用户设备的该接口标识所对应的内容服务器的接口的连接地址。
S303、所述调度服务器根据确定的内容服务器的接口的连接地址,生成包括所述确定的内容服务器的接口标识的响应。
S304、所述调度服务器根据生成的响应消息中确定的内容服务器的接口的连接地址的数量,响应的增加所述数据库中内容服务器的已连接的接口的数量和/或减少所述数据库中内容服务器的未连接的接口的数量,即更新所述调度服务器中数据库中的内容服务器的接口信息。
S305、所述调度服务器将生成的响应消息发给所述用户设备。
S306、当内容服务器到其上报周期时,所述内容服务器向所述调度服务器发送用于更新内容服务器的接口信息的请求;
S307、若所述调度服务器接收到的消息中内容服务器的接口信息与所述数据库中内容服务器的接口信息不同,则更新所述调度服务器中数据库中的内容服务器的接口信息。
其中,步骤S304与步骤S305的执行顺序不局限于本申请实施例所提供的顺序。
假设本申请实施例的应用场景为用户设备希望下载某视频文件,结合图4,多媒体资源调度以及多媒体文件下载的整体流程进一步进行解释说明。
S401、用户设备向调度服务器发送用于连接内容分发网络CDN下载某视频文件的请求。
S402、所述调度服务器根据接收到的用于获取内容分发网络CDN的接口标识的请求中的该视频文件标识,在预设数据库中查找存储有该视频文件标示所对应的视频文件的内容分发网络CDN。
S403、所述调度服务器根据步骤S402的查找结果,确定内容分发网络CDN的接口标识。
S404、所述调度服务器根据所述内容分发网络CDN的接口标识以及预设数据库中内容分发网络CDN的接口的连接地址与CDN的接口标识的映射关系,确定所述用户设备下载该视频文件所对应的内容分发网络CDN的接口的连接地址,即该内容分发网络CDN的接口的IP(Internet Protocol)地址;其中,所述映射关系可以为一一对应。
S405、所述调度服务器根据确定的内容分发网络CDN的接口的连接地址,生成用于连接内容服务器的响应,其中,所述响应包括确定的内容分发网络CDN的接口的连接地址。
S406、所述调度服务器向所述用户设备发送所述响应。
S407、所述调度服务器根据步骤S405生成的响应中的内容服务器的接口的连接地址,更新所述数据库中内容服务器的已连接的接口的数量和/或未连接的接口的数量。
S408、所述用户设备根据接收到的响应消息,确定内容服务器的接口的连接地址。
S409、所述用户设备向确定的连接地址所对应的内容分发网络CDN发送连接请求。
S410、所述内容分发网络CDN解析接收到的连接请求,并进行连接操作。
S411、所述内容分发网络CDN向所述用户设备返回包括处理结果的响应。
其中,步骤S406与步骤S407的执行顺序不局限于本申请实施例所提供的顺序。
参见图5,本申请实施例提供一种数据库的更新装置,包括:
接收模块501,配置为接收用于获取内容服务器的接口标识的请求;
响应模块502,配置为根据接收到的请求以及预设的数据库中内容服务器的接口信息,确定分配给所述用户设备的内容服务器的接口标识;
更新模块503,配置为根据确定的内容服务器的接口标识,更新所述数据库中所述接口标识对应的内容服务器的接口信息。
具体地,所述内容服务器的接口信息包括,已连接的接口的数量和/或未连接的接口的数量。
具体地,所述分配给所述用户设备的内容服务器的接口标识包括,分配给所述用户设备的内容服务器的接口的连接地址。
具体地,所述更新模块503,具体配置为:
根据确定的内容服务器的接口标识的连接地址的数量,增加所述数据库中内容服务器的已连接的接口的数量和/或减少所述数据库中内容服务器的未连接的接口的数量。
具体地,所述更新模块503,还配置为:
接收到内容服务器发送的用于更新内容服务器的接口信息的请求;
若接收到的请求中内容服务器的接口信息与所述数据库中内容服务器的接口信息不同,则更新所述数据库中内容服务器的接口信息。
参见图6,本申请实施例提供一种调度服务器,包括:一个处理器601;以及存储器602;其中,所述处理器601包括:接收模块501、响应模块502以及更新模块503,其中,
接收模块501,配置为接收用于获取内容服务器的接口标识的请求;
响应模块502,配置为根据接收到的请求以及预设的数据库中内容服务器 的接口信息,确定分配给所述用户设备的内容服务器的接口标识;
更新模块503,配置为根据确定的内容服务器的接口标识,更新所述数据库中所述接口标识对应的内容服务器的接口信息。
具体地,所述内容服务器的接口信息包括,已连接的接口的数量和/或未连接的接口的数量。
具体地,所述分配给所述用户设备的内容服务器的接口标识包括,分配给所述用户设备的内容服务器的接口的连接地址。
具体地,所述更新模块503,具体配置为:
根据确定的内容服务器的接口的连接地址的数量,增加所述数据库中内容服务器的已连接的接口的数量和/或减少所述数据库中内容服务器的未连接的接口的数量。
具体地,所述更新模块503还配置为:
接收到内容服务器发送的用于更新内容服务器的接口信息的请求;
若接收到的请求中内容服务器的接口信息与所述数据库中内容服务器的接口信息不同,则更新所述数据库中内容服务器的接口信息。
本申请实施例提供一种数据库的更新系统,该更新系统包括:内容服务器、用户设备以及上述的调度服务器。
其中,所述调度服务器可为全局负载均衡GSLB,所述内容服务器可为内容分发网络CDN。
以上所描述的装置实施例仅仅是示意性的,其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到各实施方式可借助软件加通用硬件平台的方式来实现,当然也可以通过硬件。基于这样的理解,上述技术方案本质上或者说对相关技术做出贡献的部分可以 以软件产品的形式体现出来,该计算机软件产品可以存储在计算机可读存储介质中,如ROM/RAM、磁碟、光盘等,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行各个实施例或者实施例的某些部分所述的方法。
最后应说明的是:以上实施例仅用以说明本申请的技术方案,而非对其限制;尽管参照前述实施例对本申请进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (14)

  1. 一种数据库的更新方法,应用于调度服务器,其特征在于,该方法包括:
    接收用于获取内容服务器的接口标识的请求;
    根据接收到的请求以及预设的数据库中内容服务器的接口信息,确定分配给所述用户设备的内容服务器的接口标识;
    根据确定的内容服务器的接口标识,更新所述数据库中所述接口标识对应的内容服务器的接口信息。
  2. 根据权利要求1所述的方法,其特征在于,所述内容服务器的接口信息包括,已连接的接口的数量和/或未连接的接口的数量。
  3. 根据权利要求2所述的方法,其特征在于,所述分配给所述用户设备的内容服务器的接口标识包括,分配给所述用户设备的内容服务器的接口的连接地址。
  4. 根据权利要求3所述的方法,其特征在于,根据确定的内容服务器的接口标识,更新所述数据库中所述接口标识对应的内容服务器的接口信息,包括:
    根据确定的内容服务器的接口的连接地址的数量,增加所述数据库中内容服务器的已连接的接口的数量和/或减少所述数据库中内容服务器的未连接的接口的数量。
  5. 根据权利要求1所述的方法,其特征在于,该方法还包括:
    接收到内容服务器发送的用于更新内容服务器的接口信息的请求;
    若接收到的请求中内容服务器的接口信息与所述数据库中内容服务器的接口信息不同,则更新所述数据库中内容服务器的接口信息。
  6. 根据权利要求5所述的方法,其特征在于,所述内容服务器发送的用于更新内容服务器的接口信息的请求,包括:
    所述内容服务器周期性发送用于更新内容服务器的接口信息的请求,或 根据所述内容服务器接收到的触发消息,发送用于更新内容服务器的接口信息的请求。
  7. 根据权利要求1所述的方法,其特征在于,该方法还包括:
    生成包括所述分配给所述用户设备的内容服务器的接口标识的响应,并将生成的响应发送给所述用户设备。
  8. 一种调度服务器,其特征在于,包括:至少一个处理器;以及存储器;其中,所述存储器存储有可被所述至少一个处理器执行的指令,所述指令被所述至少一个处理器执行,以使所述至少一个处理器能够:
    接收用于获取内容服务器的接口标识的请求;
    根据接收到的请求以及预设的数据库中内容服务器的接口信息,确定分配给所述用户设备的内容服务器的接口标识;
    根据确定的内容服务器的接口标识,更新所述数据库中所述接口标识对应的内容服务器的接口信息。
  9. 根据权利要求8所述的调度服务器,其特征在于,所述内容服务器的接口信息包括,已连接的接口的数量和/或未连接的接口的数量。
  10. 根据权利要求9所述的调度服务器,其特征在于,所述分配给所述用户设备的内容服务器的接口标识包括,分配给所述用户设备的内容服务器的接口的连接地址。
  11. 根据权利要求10所述的调度服务器,其特征在于,根据确定的内容服务器的接口标识,更新所述数据库中所述接口标识对应的内容服务器的接口信息,包括:
    根据确定的内容服务器的接口的连接地址的数量,增加所述数据库中内容服务器的已连接的接口的数量和/或减少所述数据库中内容服务器的未连接的接口的数量。
  12. 根据权利要求8所述的调度服务器,其特征在于,所述计算机可执行指令,还用于:
    接收到内容服务器发送的用于更新内容服务器的接口信息的请求;
    若接收到的请求中内容服务器的接口信息与所述数据库中内容服务器的接口信息不同,则更新所述数据库中内容服务器的接口信息。
  13. 根据权利要求12所述的调度服务器,其特征在于,所述内容服务器发送的用于更新内容服务器的接口信息的请求,包括:
    所述内容服务器周期性发送用于更新内容服务器的接口信息的请求,或根据所述内容服务器接收到的触发消息,发送用于更新内容服务器的接口信息的请求。
  14. 根据权利要求8所述的调度服务器,其特征在于,所述计算机可执行指令,还用于:
    生成包括所述分配给所述用户设备的内容服务器的接口标识的响应,并将生成的响应发送给所述用户设备。
PCT/CN2016/099969 2016-06-29 2016-09-23 一种数据库的更新方法及调度服务器 Ceased WO2018000617A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610500354.1 2016-06-29
CN201610500354.1A CN106202263A (zh) 2016-06-29 2016-06-29 一种数据库的更新方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2018000617A1 true WO2018000617A1 (zh) 2018-01-04

Family

ID=57463699

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/099969 Ceased WO2018000617A1 (zh) 2016-06-29 2016-09-23 一种数据库的更新方法及调度服务器

Country Status (2)

Country Link
CN (1) CN106202263A (zh)
WO (1) WO2018000617A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116860719A (zh) * 2023-07-06 2023-10-10 中国工商银行股份有限公司 数据库的升级方法及其装置、电子设备及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113806069B (zh) * 2021-08-05 2024-04-05 广东核电合营有限公司 一种核电站系统交互方法、装置、外围系统及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080001791A1 (en) * 2006-06-30 2008-01-03 Omneon Video Networks Transcoding for a distributed file system
CN101977148A (zh) * 2010-10-26 2011-02-16 中兴通讯股份有限公司 内容分发网络节点媒体服务器之间数据交互的方法及系统
CN103747273A (zh) * 2013-12-23 2014-04-23 乐视网信息技术(北京)股份有限公司 一种视频请求方法、设备及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080001791A1 (en) * 2006-06-30 2008-01-03 Omneon Video Networks Transcoding for a distributed file system
CN101977148A (zh) * 2010-10-26 2011-02-16 中兴通讯股份有限公司 内容分发网络节点媒体服务器之间数据交互的方法及系统
CN103747273A (zh) * 2013-12-23 2014-04-23 乐视网信息技术(北京)股份有限公司 一种视频请求方法、设备及系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116860719A (zh) * 2023-07-06 2023-10-10 中国工商银行股份有限公司 数据库的升级方法及其装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN106202263A (zh) 2016-12-07

Similar Documents

Publication Publication Date Title
JP7252356B2 (ja) モバイルエッジコンピューティングノードの選択方法、装置及びシステム並びにコンピュータプログラム
US11316786B2 (en) Systems and methods for directly responding to distributed network traffic
CN110602254B (zh) 一种实现负载均衡的方法、装置及系统
US10447775B2 (en) System and method to balance servers based on server load status
CN108737270B (zh) 一种服务器集群的资源管理方法和装置
US10404790B2 (en) HTTP scheduling system and method of content delivery network
US12289656B2 (en) Method and system for performing charging processing on network slice customer, and related device
WO2020228505A1 (zh) 一种移动边缘计算节点的选择方法、装置及系统
CN102281190B (zh) 负载均衡装置组网方法以及服务器、客户端接入方法
JP7611318B2 (ja) 強化されたオンラインプライバシ
US7953887B2 (en) Asynchronous automated routing of user to optimal host
US20170171245A1 (en) Dynamic detection and reconfiguration of a multi-tenant service
CN111327647B (zh) 一种容器对外提供服务的方法、装置及电子设备
US20210410057A1 (en) Service Discovery Extension in a 5G Mobile Communication Network
US20140188801A1 (en) Method and system for intelligent load balancing
WO2015019224A1 (en) Dynamic edge server allocation
CN105871975A (zh) 选择回源服务器的方法及装置
US20170163749A1 (en) Information exchange method and server
CN112491066B (zh) 负载均衡方法、装置、系统、目标负载均衡设备及介质
WO2018000202A1 (zh) 一种负载迁移方法、装置及系统
JP2016527623A (ja) リースエージェントシステム間での制作者システムの分配
US20160226963A1 (en) Load balancing using predictable state partitioning
US20220012110A1 (en) Networking-related system call interception and modification
CN110995890B (zh) 域名请求的调度方法及装置
WO2018000617A1 (zh) 一种数据库的更新方法及调度服务器

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16907013

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16907013

Country of ref document: EP

Kind code of ref document: A1