WO2017055927A1 - Procédés et appareils pour fournir une fonctionnalité de synchronisation - Google Patents

Procédés et appareils pour fournir une fonctionnalité de synchronisation Download PDF

Info

Publication number
WO2017055927A1
WO2017055927A1 PCT/IB2016/001536 IB2016001536W WO2017055927A1 WO 2017055927 A1 WO2017055927 A1 WO 2017055927A1 IB 2016001536 W IB2016001536 W IB 2016001536W WO 2017055927 A1 WO2017055927 A1 WO 2017055927A1
Authority
WO
WIPO (PCT)
Prior art keywords
timer
worker
cloud
node
identifier
Prior art date
Application number
PCT/IB2016/001536
Other languages
English (en)
Inventor
Fei NIE
Chunlei Wang
Original Assignee
Alcatel Lucent
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 Alcatel Lucent filed Critical Alcatel Lucent
Publication of WO2017055927A1 publication Critical patent/WO2017055927A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/28—Timers or timing mechanisms used in protocols
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/466—Transaction processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/5011—Pool

Definitions

  • the present invention relates to the field of communication technologies, and more specifically to a technology of providing timing functionality.
  • a timer is a local resource.
  • Fig. 1(a) illustrates a schematic diagram of a traditional application model. As illustrated in Fig. 1(a), in traditional applications, a timer, a service logic, and state information are together embedded in each application instance.
  • the traditional application has a relatively poor elasticity, i.e., it is hard to change the size and location of the application.
  • elasticity is a feature a cloud application must have. Without elasticity, the application cannot enjoy various advantages of the cloud computing environment.
  • Fig. 1(b) illustrates a schematic diagram of a Worker-State model. It is seen that in the Worker-State model, processing and data are separated. State information in the traditional application is stored in an elastic cloud database that may support big data. The state information here does not only refer to narrow state -related information; instead, it broadly refers to all user data. Further, a service logic in the traditional application is implemented by a worker, and all service logics are placed in a worker pool. The worker here actually refers to processing. Then, how the timer in a traditional application is implemented in such a Worker-State model?
  • Type 1 not send a Data Delete notification message to the worker
  • the cloud database will not send a notification message to the worker.
  • the Cassandra cloud database just adopts this approach.
  • Type 2 send a Data Delete notification message to the worker
  • the worker may subscribe a Data Delete event.
  • the cloud database will send a notification message to the worker.
  • the Redis cloud database just employs this manner.
  • the notification message can only be sent to a worker that previously subscribed the notification message, while in the Worker-State model, it always occurs that when the timer is expiration, the worker that previously subscribed the notification message already does not exist, such that the notification message cannot be successfully sent.
  • the timer is started by a worker, and the correspondence relationship between the timer and the worker is saved in the cloud database.
  • the timer may also be relocated along therewith. For example, if a worker X of a session SI is deleted after completing worker of a request message Reql, when the session SI generates a request message Req2, the worker Y will process the request message 2. However, the timer TimerX started by the worker X is not expiration yet; the worker Y knows, by querying a cloud database, that the timer for starting the worker X is TimerX; the worker Y will restart the timer TimerX and update the cloud database: updating the corresponding relationship between the worker X and the timer TimerX to the correspondence relationship between the worker Y and the timer TimerX.
  • timer relocation The above scenario is referred to as timer relocation.
  • An objective of the present invention is to provide methods and apparatuses of providing timing functionality for a system where processing is separated from data.
  • a method of providing, in a cloud timer, timing functionality for a system where processing is separated from data the system including a worker pool, a cloud database, and the cloud timer, the worker pool consisting of at least one worker, the cloud timer consisting of at least one node, the method comprising steps of: A. receiving, by the cloud timer, a timer start request from one worker, the timer start request including an identifier of a timer, an expiration time, and an identifier of a notified object; B. sending, by the cloud timer, an acknowledgement message of successfully starting the timer to the worker; C. in response to reaching the expiration time of the timer, sending, by the cloud timer, a timer expiration notification to a network entity corresponding to the identifier of the notified object.
  • the timer start request further includes information related to the timer
  • the timer expiration notification further includes the information related to the timer
  • the identifier of the notified object includes an identifier of at least one network entity, each network entity corresponding to a different priority; the step C further comprises: sending, by the cloud timer, the timer expiration notification to a network entity with a lower priority after failing to send the timer expiration notification to a network entity with a higher priority.
  • the identifier of the notified object at least includes an identifier of the worker and an identifier of the worker pool including the worker, the priority of the worker being higher than the priority of the worker pool.
  • the step A further comprises: receiving, by a first node in the cloud timer, the timer start request from the worker; and the method further comprises the following steps between the step A and the step B: determining, by the first node, N nodes in the cloud timer for starting the timer according to a preset algorithm and a preset redundant number N, where N>1; and sending, by the first node, a timer start request to the N nodes to indicate the N nodes to start the timer; the step B further comprises: sending, by the first node, an acknowledgement message of successfully starting the timer to the worker; the step C further comprises: in response to reaching the expiration time of the timer in a second node of the N nodes, sending, by the second node, a timer cancelling request to the remaining (N-l) nodes to indicate the remaining (N-l) nodes to cancel the timer; and sending, by the second node, the timer expiration notification to the network entity corresponding to the identifier
  • a method of facilitating provision of timing functionality for a system where processing is separated from data in the worker including a worker pool, a cloud database, and a cloud timer, the worker pool consisting of at least one worker, the cloud timer consisting of at least one node, the method comprising steps of: sending, by the worker, a timer start request to the cloud timer, the timer start request including an identifier of a timer, an expiration time, and an identifier of a notified object; and in response to an acknowledgement message of successfully starting the timer from the cloud timer, sending a request for adding data to the cloud database, the request for adding data including information of data to be added.
  • a method of facilitating provision of timing functionality for a system where processing is separated from data in the worker including a worker pool, a cloud database, and a cloud timer, the worker pool consisting of at least one worker, the cloud timer consisting of at least one node, the method comprising steps of: receiving, by the worker, a timer expiration notification from the cloud timer, the timer expiration notification including information related to the timer; and sending, by the worker, a data operation request to the cloud database based on information related to the timer.
  • a cloud timer for providing timing functionality for a system where processing is separated from data, the system including a worker pool, a cloud database, and the cloud timer, the worker pool consisting of at least one worker, the cloud timer consisting of at least one node, the cloud timer at least including one first node and one second node; the first node being configured to receive a timer start request from one worker, the timer start request including an identifier of a timer, an expiration time, and an identifier of a notified object; and to send an acknowledgement message of successfully starting the timer to the worker; the second node being configured, in response to reaching the expiration time of the timer, to send a timer expiration notification to a network entity corresponding to the identifier of the notified object.
  • the timer start request further includes information related to the timer
  • the timer expiration notification further includes information related to the timer
  • the identifier of the notified object includes an identifier of at least one network entity, each network entity corresponding to a different priority; and the second node sends the timer expiration notification to a network entity with a lower priority after failing to send the timer expiration notification to a network entity with a higher priority.
  • the identifier of the notified object at least includes an identifier of the worker and an identifier of the worker pool including the worker, the priority of the worker being higher than the priority of the worker pool.
  • the first node is further configured to: determine N nodes in the cloud timer for starting the timer according to a preset algorithm and a preset redundant number N, where N>1, and send a timer start request to the N nodes to indicate the N nodes to start the timer.
  • the second node is one of the N nodes and is configured to, in response to reaching the expiration time of the timer in the second node, send a timer cancelling request to the remaining (N-l) nodes to indicate the remaining (N-l) nodes to cancel the timer.
  • an apparatus of facilitating providing timing functionality for a system where processing is separated from data in the worker including a worker pool, a cloud database, and a cloud timer, the worker pool consisting of at least one worker, the cloud timer comprising at least one node, the apparatus comprising: first sending means for the worker to send a timer start request to the cloud timer, the timer start request including an identifier of a timer, an expiration time, and an identifier of a notified object; and second sending means for, in response to an acknowledgement message of successfully starting the timer from the cloud timer, sending a request for adding data to the cloud database, the request for adding data including information of data to be added.
  • an apparatus of facilitating providing timing functionality for a system where processing is separated from data in the worker including a worker pool, a cloud database, and a cloud timer, the worker pool consisting of at least one worker, the cloud timer comprising at least one node, the apparatus comprising: receiving means for receiving a timer expiration notification from the cloud timer, the timer expiration notification including information related to the timer; and third sending means for sending a data operation request to the cloud database according to information related to the timer.
  • the present invention newly introduces a cloud timer into a system where processing is separated from data so as to implement timing functionality.
  • the present invention has the following advantages: 1) not compromising the design principle of the Worker-State model; it is not needed to save data and timers at the processing side, such that the worker may focus more on processing logic without extra addition of auxiliary processing regarding the timer; besides, no complexity is added at the data side. 2)
  • a starter of the timer may designate an object to notify when the timer is expiration, which is very flexible in implementation and also avoids a scenario of failing to send the timer expiration notification n, thereby avoiding potential system bugs.
  • the starter of the timer may designate information carried in the timer expiration notification, which facilitates subsequent processing of relevant network elements.
  • the design of cloud timer adopts a principle of multi-node redundant backup, which conforms to the design concept of a cloud computing environment. 5) Compared with a timer implemented with assistance of processing, the present invention avoids timer relocation and thus enhances the accuracy.
  • FIG. 1 (a) illustrates a schematic diagram of a traditional application model
  • FIG. 1(b) illustrates a schematic diagram of a Worker-State model
  • FIG. 2 illustrates an application scenario diagram according to one embodiment of the present invention
  • FIG. 3 illustrates a process schematic diagram of providing timing functionality to a system where processing is separated from data according to one embodiment of the present invention
  • Fig. 4 illustrates an apparatus schematic diagram of facilitating providing of timing functionality in worker X according to one embodiment of the present invention
  • Fig. 5 illustrates an apparatus schematic diagram of facilitating providing of timing functionality in worker Y according to one embodiment of the present invention.
  • Fig. 2 illustrates an application scenario diagram according to one embodiment of the present invention.
  • the embodiment illustrates a system where processing is separated from data in a cloud computing environment.
  • the system includes a worker pool 201, a cloud timer 202, and a cloud database 203.
  • the worker pool 201 consists of at least one worker, as illustrated in the figure, comprising worker 1, worker 2, and worker P.
  • the cloud timer consists of at least one node.
  • the cloud timer 202 is a network entity newly introduced in the present invention.
  • the cloud timer is a logic functional body comprising a plurality of distributed nodes that have the same capabilities, i.e., the functions they may perform are identical.
  • these nodes may be virtual machines (VM).
  • VM virtual machines
  • a same timer may be started simultaneously at multiple nodes, thereby avoiding a single-point failure.
  • the cloud timer 202 is designed based on a No-SQL database (i.e., cloud database); therefore, the number of nodes in the cloud timer 202 may be dynamically adjusted.
  • the cloud timer 202 is a separate entity which is independent from the worker pool 201 and the cloud database 203. However, because its design is similar to the cloud database, it may also be embedded into the cloud database 203 in actual implementation. [0043] Fig. 3 illustrates a process schematic diagram of providing timing functionality for a system where processing is separated from data according to one embodiment of the present invention.
  • the session S 1 has a plurality of transactions during its existence, where transaction Tl corresponds to request 1, while transaction Tn corresponds to request n.
  • the worker X is for processing request 1
  • worker Y is for processing request n. Both of the worker X and worker Y are in the worker pool 201.
  • the cloud timer 202 comprises node Nl, node N2, node N3, node N4, and node N5.
  • the 5 nodes have the same capabilities.
  • step S301 the worker X sends a timer start request to the cloud timer 202, wherein the timer start request comprises an identifier Timer 1 of a timer, an expiration time corresponding to the timer, and an identifier of a notified object.
  • a notified object here refers to an object to which the cloud timer 202 should be notified when the timer Timerl exceeds. It may be seen that different from the prior art, the worker X may designate an object who should be notified when the timer is expiration. This object may be worker X or other entity. In this way, the object to which the cloud timer 202 should be notified when the timer Timerl is expiration might not be the entity that initially started the timer Timerl, such that the implementation will be very flexible.
  • the identifier of the notified object includes an identifier of at least one network entity, each network entity corresponding to a different priority.
  • the cloud timer 202 fails in sending a timer expiration notification to a network entity with a higher priority, it will then send the timer expiration notification to a network entity with a lower priority, thereby reducing a failure rate.
  • the identifier of the notified object at least comprises an identifier of the worker X and an identifier of the worker pool 201 where the worker X is located; besides, the priority of the worker X is higher than the priority of the worker pool 201.
  • the timer Timerl is expiration, the worker X already does not exist, such that the cloud timer 202 fails in sending the timer expiration notification to the worker X, and then the cloud timer 202 will send the timer expiration notification to the worker pool 201.
  • node Nl in the cloud timer 202 receives the timer start request. Then, the node Nl determines N nodes that start the timer Timerl according to a preset algorithm and a preset redundant number N (N>1).
  • the algorithm here may be a consistent Hash algorithm.
  • the redundant number N here refers to a preset number of nodes in the cloud timer 202 which simultaneously start a timer. Meanwhile, it is mainly intended to avoid single-point failures to start a same timer simultaneously in multiple nodes. This is also a common method in the cloud computing environment.
  • the algorithm preset in the cloud timer 202 is a Hash algorithm
  • the redundant number is preset to 3.
  • the node Nl determines that the three nodes for starting the timer Timerl to be node N2, node N3, and node N4 according to the Hash algorithm and the redundant number 3.
  • step S302 the node Nl sends a timer start request to the determined N nodes (i.e., node N2, node N3, and node N4), to indicate the node N2, node N3, and node N4 to start the timer Timerl .
  • the node N2, node N3, and node N4, after receiving the timer start request, will start the timer Timerl, respectively. In other words, the node N2, node N3, and node N4 will simultaneously run the timer Timerl .
  • N nodes know the remaining N-l nodes that simultaneously run the timer Timerl .
  • step S303 the cloud timer 202 sends a acknowledgement message of successfully starting the timer to the worker X.
  • the node Nl in the cloud timer 202 sends the acknowledgement message of successfully starting the timer to the worker X.
  • step S304 the worker X sends a request for adding data to the cloud database 203, the request for adding data including information of the data to be added by the worker X to the cloud database 203.
  • the expiration time of the timer Timerl is reached.
  • the node N2, node N3, and node N4 are simultaneously running the timer Timerl, the time when they receive the message is different, or due to reasons like network delay or processing speed, the same timer Timerl running on the 3 nodes is always asynchronous, and there is always a timer Timerl in one node is expiration first.
  • step S305 the node N4 with the timer Timerl being expiration first in the N nodes sends a timer cancelling request to the remaining N-l nodes, for indicating the remaining N-l nodes to cancel the timer Timerl running thereon.
  • the node N4 will send a timer cancelling request to node N2 and node N3; after receiving the message, the node N2 and node N3 will cancel the timer Timerl running thereon.
  • step S306 the cloud timer 202 sends a timer expiration notification to a network entity corresponding to the identifier of the notified object.
  • node N4 in the cloud timer 202 sends a timer expiration notification to a network entity corresponding to the identifier of the notified object.
  • the identifier of the notified object includes an identifier of the worker X and an identifier of the worker pool 201 where the worker X is located; besides, the priority of the worker X is higher than the priority of the worker pool 201.
  • the worker X has already been deleted because it has completed its task; and the node N4 fails in sending the timer expiration notification to worker X; therefore, the node N4 will send the timer expiration notification to the worker pool 201 again.
  • the worker pool will send the notification to the worker Y; the notification comprises a timer identifier, i.e., the identifier of the timer Timerl .
  • the timer start request in step S301 further comprises information related to the timer Timerl .
  • information related to the timer Timerl may be: an address of the notified object, keywords of data corresponding to the timer Timerl, a function to the executed by the notified object when the timer Timerl is expiration, etc.
  • the timer expiration notification in step S306 also includes the information related to the timer Timerl . In this way, the starter of the timer may decide the information that needs to be brought back when the timer is expiration.
  • the worker Y After receiving the timer expiration notification, the worker Y knows that the timer Timerl is expiration.
  • step S307 the worker Y will send a data operation request to the cloud database 203.
  • the worker Y may determine data related to the timer Timerl, the request being for operating the data related to the timer Timerl .
  • These data may be data added by the worker X into the cloud database 203 in step S304.
  • These operations include, but not limited to, search, delete, etc.
  • request 1 is a Register message initiated by the SIP terminal for registration
  • the worker Y when the worker Y receives the notification that the timer Timerl is expiration, it will notify the terminal, i.e., the request n is a Notify message; then, the worker Y will directly delete the data added by the worker X into the cloud database 203.
  • request 1 is an Invite message initiated for the SIP terminal to establish a session
  • the worker Y receives the notification that the timer Timer 1 is expiration
  • the worker Y will retrieve the data added by the worker X into the cloud database 203, and then checks whether the session is still valid, i.e., the request n is an Update message; the worker Y sends the Update message to the terminal to perform a heartbeat detection to the session.
  • Node Nl node N2, node N3, node N4 and node N5 in the embodiment above are somewhat different, each node has the same capabilities. This may greatly avoid occurrence of a single-point failure. For the same node, the functions actually performed in different transaction processing might be somewhat different.
  • FIG. 4 illustrates an apparatus schematic diagram of facilitating providing timing functionality in the worker X according to one embodiment of the present invention.
  • the apparatus 400 comprises: first sending means 401 and second sending means 402.
  • the sending means 401 sends a timer start request to the cloud timer 202, wherein the timer start request comprises an identifier Timer 1 of a timer, an expiration time corresponding to the timer, and an identifier of a notified object.
  • a notified object here refers to an object to which the cloud timer 202 should be notified when the timer Timerl exceeds. It may be seen that different from the prior art, the worker X may designate an object which should be notified when the timer is expiration. This object may be worker X or other entity. In this way, the object to which the cloud timer 202 should be notified when the timer Timerl is expiration might not be the entity that initially started the timer Timerl, such that the implementation will be very flexible.
  • the identifier of the notified object includes an identifier of at least one network entity, each network entity corresponding to a different priority.
  • the cloud timer 202 fails in sending a timer expiration notification to a network entity with a higher priority, it will then send the timer expiration notification to a network entity with a lower priority, thereby reducing a failure rate.
  • the identifier of the notified object at least comprises an identifier of the worker X and an identifier of the worker pool 201 where the worker X is located; besides, the priority of the worker X is higher than the priority of the worker pool 201.
  • the timer Timerl is expiration, the worker X already does not exist, such that the cloud timer 202 fails in sending the timer expiration notification to the worker X, and then the cloud timer 202 will send the timer expiration notification to the worker pool 201.
  • the second means 402 in response to an acknowledgement message of successfully starting the timer from the cloud timer 202, sends a request for adding data to the cloud database, the request for adding data including information of the data to be added by the worker X into the cloud database 203.
  • FIG. 5 illustrates an apparatus schematic diagram of facilitating providing timing functionality in the worker Y according to one embodiment of the present invention.
  • the apparatus 500 comprises: receiving means 501 and third sending means 502.
  • the receiving means 501 receives a timer expiration notification from the cloud time 202, the timer expiration notification including a timer identifier, i.e., identifier of the timer Timerl, and information related to the timer Timerl .
  • timer identifier i.e., identifier of the timer Timerl
  • information related to the timer Timerl may be: address of the notified object, keywords of data corresponding to the timer Timerl, function to the executed by the notified object when the timer Timerl is expiration, etc.
  • the third sending means 502 will send a data operation request to the cloud database 203.
  • the worker Y may determine data related to the timer Timerl, the request being for operating the data related to the timer Timerl .
  • These data may be data added by the worker X into the cloud database 203 in step S304.
  • These operations include, but not limited to, search, delete, etc.
  • request 1 is a Register message initiated by the SIP terminal for registration
  • the worker Y when the worker Y receives the notification that the timer Timerl is expiration, it will notify the terminal, i.e., the request n is a Notify message; then, the worker Y will directly delete the data added by the worker X into the cloud database 203.
  • request 1 is an Invite message initiated for the SIP terminal to establish a session
  • the worker Y receives the notification that the timer Timer 1 is expiration
  • the worker Y will retrieve the data added by the worker X into the cloud database 203, and then checks whether the session is still valid, i.e., the request n is an Update message; the worker Y sends the Update message to the terminal to perform a heartbeat detection to the session.
  • the present disclosure may be implemented in software or a combination of software and hardware; for example, it may be implemented by a dedicated integrated circuit (ASIC), a general-purpose computer, or any other similar hardware device.
  • the software program of the present disclosure may be executed by a processor so as to implement the above steps or functions.
  • the software program of the present disclosure (including relevant data structure) may be stored in a computer readable recording medium, for example, a RAM memory, a magnetic or optical driver, or a floppy disk, and similar devices.
  • some steps of functions of the present disclosure may be implemented by hardware, for example, a circuit cooperating with the processor to execute various functions or steps.
  • part of the present invention may be applied as a computer program product, e.g., computer program instructions which, when being executed by the computer, may invoke or provide the methods and/or technical solutions of the present invention through operations of the computer.
  • program instructions invoking the methods of the present invention may be stored in a fixed or mobile recording medium, and/or transmitted by broadcasting or data flows in other signal carrying media, and/or stored in a working memory of a computer device run according to the program instructions.
  • one embodiment according to the present invention comprises an apparatus that comprises a memory for storing computer program instructions and a processor for executing the program instructions, wherein, the computer program instructions, when being executed by the processor, trigger the apparatus to execute the methods and/or technical solutions according to a plurality of embodiments of the present invention.

Abstract

Un objectif de l'invention est de proposer des procédés et des appareils permettant de fournir une fonctionnalité de synchronisation pour un système où un traitement est séparé des données. L'invention concerne un temporisateur Cloud comprenant au moins un premier nœud et un second nœud. Le premier nœud est configuré pour recevoir une demande de démarrage de temporisateur depuis un ouvrier, la demande de démarrage de temporisateur comprenant un identifiant de temporisateur, un temps d'expiration, et un identifiant d'un objet notifié; et le deuxième nœud est configuré pour, lorsque l'on atteint le temps d'expiration du temporisateur, envoyer un avertissement d'expiration de temporisateur à une entité de réseau correspondant à l'identifiant de la notification. Par comparaison à l'état de la technique, l'invention ne compromet pas le principe de conception du modèle ouvrier-statut; un démarreur de la minuterie peut désigner un objet devant être averti lorsque le temporisateur a expiré et des informations contenues dans l'avertissement d'expiration de minuterie, ce qui compense les inconvénients dans l'état de la technique. En outre, la conception de temporisateur Cloud adopte un principe de secours redondant à nœuds multiples, qui est conforme à l'idée de conception d'un environnement d'informatique Cloud.
PCT/IB2016/001536 2015-09-30 2016-09-28 Procédés et appareils pour fournir une fonctionnalité de synchronisation WO2017055927A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510639282.4A CN106557522B (zh) 2015-09-30 2015-09-30 一种用于提供定时功能的方法与设备
CN201510639282.4 2015-09-30

Publications (1)

Publication Number Publication Date
WO2017055927A1 true WO2017055927A1 (fr) 2017-04-06

Family

ID=57233779

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2016/001536 WO2017055927A1 (fr) 2015-09-30 2016-09-28 Procédés et appareils pour fournir une fonctionnalité de synchronisation

Country Status (2)

Country Link
CN (1) CN106557522B (fr)
WO (1) WO2017055927A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111510469A (zh) * 2019-01-31 2020-08-07 上海哔哩哔哩科技有限公司 一种消息处理方法和装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107730126B (zh) * 2017-10-23 2021-06-01 浪潮通用软件有限公司 一种实现定时的方法及装置
CN110351223B (zh) * 2018-04-02 2021-09-17 腾讯科技（深圳）有限公司 定时提醒方法、装置和计算机程序介质
CN114647696A (zh) * 2020-12-17 2022-06-21 中兴通讯股份有限公司 一种定时器系统及方法

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150078237A1 (en) * 2010-12-27 2015-03-19 Microsoft Corporation Power management via coordination and selective operation of timer-related tasks

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014200076A (ja) * 2013-03-15 2014-10-23 株式会社リコー 配信制御システム、配信制御方法、及びプログラム
CN104601533A (zh) * 2013-10-31 2015-05-06 阿尔卡特朗讯 一种用于关闭Diameter连接的方法与设备

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150078237A1 (en) * 2010-12-27 2015-03-19 Microsoft Corporation Power management via coordination and selective operation of timer-related tasks

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111510469A (zh) * 2019-01-31 2020-08-07 上海哔哩哔哩科技有限公司 一种消息处理方法和装置

Also Published As

Publication number Publication date
CN106557522B (zh) 2020-06-12
CN106557522A (zh) 2017-04-05

Similar Documents

Publication Publication Date Title
US11539579B2 (en) Method and apparatus for detection of network function failure and restart in a network environment
WO2017185961A1 (fr) Procédé et appareil de traitement de la découverte de services
CN107872528B (zh) 消息推送方法及装置
WO2017055927A1 (fr) Procédés et appareils pour fournir une fonctionnalité de synchronisation
CN107277029B (zh) 一种远程过程调用的方法、装置及计算机设备
US20170346676A1 (en) Alarm correlation in network function virtualization environment
JP2017528809A5 (fr)
US7536603B2 (en) Maintaining functionality during component failures
EP3248361B1 (fr) Temporisateurs dans une architecture sans état
WO2016070837A1 (fr) Procédé et système de rapport de panne et dispositif s'y rapportant
JP7326443B2 (ja) Ｎｆ間のダイレクトシグナリングを使用したｎｆサービスコンシューマー再起動検出
CN110635905B (zh) 一种密钥管理方法、相关设备及计算机可读存储介质
JP2017517064A (ja) トランザクションミドルウェアマシン環境におけるドメイン間メッセージ通信のためにバイパスドメインモデルおよびプロキシモデルをサポートし、かつサービス情報を更新するためのシステムおよび方法
JP6826207B2 (ja) ルーティング方法および装置
CN104809816A (zh) 取件处理方法、取件执行方法、取件方法和装置及系统
EP3452904A1 (fr) Création d'instantanés dans un environnement de réseau virtuel
WO2015038137A1 (fr) Reprise d'un état de tâche après panne dans un traitement de flux basé sur des lots
CN104869163A (zh) 一种集群环境下基于代理的动态服务调用方法
WO2014182310A1 (fr) Récupération de n-uplets
CN105373563B (zh) 数据库切换方法及装置
WO2016101759A1 (fr) Procédé d'acheminement de données, dispositif de gestion de données et système de stockage distribué
CN107479985B (zh) 一种远程过程调用的方法、装置及计算机设备
WO2019119269A1 (fr) Procédé de détection de défaillance de réseau et dispositif centre de commande
TWI690849B (zh) 應用升級與關閉應用之方法及裝置
US8429136B2 (en) Information processing method and information processing apparatus

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: 16791077

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: 16791077

Country of ref document: EP

Kind code of ref document: A1