EP0721167A2 - Verfahren und Scheduler zum Steuern, wenn ein Server eine Einheit bedient - Google Patents

Verfahren und Scheduler zum Steuern, wenn ein Server eine Einheit bedient Download PDF

Info

Publication number
EP0721167A2
EP0721167A2 EP95309404A EP95309404A EP0721167A2 EP 0721167 A2 EP0721167 A2 EP 0721167A2 EP 95309404 A EP95309404 A EP 95309404A EP 95309404 A EP95309404 A EP 95309404A EP 0721167 A2 EP0721167 A2 EP 0721167A2
Authority
EP
European Patent Office
Prior art keywords
time
server
entity
service
entities
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
EP95309404A
Other languages
English (en)
French (fr)
Other versions
EP0721167A3 (de
Inventor
Jon C. R. Bennett
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.)
Ericsson AB
Original Assignee
Fore Systems Inc
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 Fore Systems Inc filed Critical Fore Systems Inc
Publication of EP0721167A2 publication Critical patent/EP0721167A2/de
Publication of EP0721167A3 publication Critical patent/EP0721167A3/de
Ceased legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/46Multiprogramming arrangements
    • G06F9/48Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806Task transfer initiation or dispatching
    • G06F9/4843Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5038Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/50Indexing scheme relating to G06F9/50
    • G06F2209/506Constraint

Definitions

  • the present invention is related to a scheduler. More specifically, the present invention is related to a scheduler which allows an entity to receive service from a server before its finishing time.
  • the scheduler will provide the users access to the server in a fair manner so that no user will experience an undue delay based on its needs.
  • scheduler's have not necessarily been fair to users when the users have a significant divergence in their needs. Many times, either the user with the greatest needs is left waiting while the user with the lowest needs is being served by the server, and vice versa.
  • the present invention is directed to meeting the needs of users so users having lower needs can be served at times when users of greater needs do not require service at a given time.
  • the present invention pertains to a scheduler for controlling when N entities, where N is an integer ⁇ 1, are serviced by a server.
  • the scheduler comprises a starting time memory having starting times s i of the N entities, where 1 ⁇ i ⁇ N and is an integer, and s i corresponds to the time the i'th entity requests service from the server.
  • the scheduler is also comprised of a finishing time memory having finishing times f i of the N entities, where f i corresponds to the time the i'th entity should be serviced by the server.
  • the scheduler is also comprised of a virtual clock that keeps track of time so the starting times s i and finishing times f i can be identified.
  • the scheduler comprises a controller which chooses entities to receive service from the server in the order of the entities with an earliest finishing time f i and a starting time s i being serviced first, and then the entities with the earliest or latest starting time s i or having the highest or lowest id or rate if their finishing times are the same being serviced next at each given time.
  • a controller which chooses entities to receive service from the server in the order of the entities with an earliest finishing time f i and a starting time s i being serviced first, and then the entities with the earliest or latest starting time s i or having the highest or lowest id or rate if their finishing times are the same being serviced next at each given time.
  • the entities' finishing times are the same, then whatever protocol is desired to indicate which entity is to be provided to the server to be operated upon is the choice of the operator.
  • the present invention pertains to a method of scheduling when a server provides service to entities.
  • the method comprises the steps of requesting service from the server by N entities, where N ⁇ 1 and is an integer. Then there is the step of storing when each of the N entities starts requesting service and when each of the N entities should have received service. Next, there is the step of providing service to an entity of the N entities which has the earliest receive time and start time, unless there is more than one entity with the earliest receive time in which case the entity with the earliest start time receives service and possibly before its receive time.
  • the present invention pertains to a scheduler for scheduling when N entities each of which has a weight w, where N is an integer ⁇ 1 and w is a real number, are served by a server.
  • the scheduler is comprised of a starting time memory having starting times s i when the N entities request service, where 1 ⁇ i ⁇ N and is an integer, and s i is the time at which the i'th entity may next get service from the server.
  • the scheduler is also comprised of a finishing time memory having finishing times f i when the N entities should be serviced, where f i is the time by which the i'th entity should be serviced by the server.
  • T or X can be essentially any real number as long as both are not 0; and either Y or Z can be essentially any real number as long as both are not 0.
  • the scheduler is also comprised of a controller which chooses which entity is to be operated upon by the server in the order of the entity with an earliest finishing time f i and a start time s i receiving service first, and then the entities based on a predetermined criteria.
  • the predetermined criteria can essentially be any type of tie-breaking procedure that the user wishes to apply such as earliest start time or id number, etc.
  • the present invention pertains to a method for scheduling when a server provides service to entities.
  • the method comprises the steps of identifying when a first entity requests service from the server.
  • the present invention pertains to a scheduler for controlling when a server provides service to entities.
  • the scheduler comprises a memory having times which are a function of when entities request service from the server.
  • the scheduler is also comprised of a virtual clock that keeps track of time as a function of when entities request service from the server.
  • the scheduler is also comprised of a controller which causes an entity to receive service from the server as a function of when the entity requests service from the server.
  • Figure 1 is a schematic representation of the present invention.
  • Figures 2-11 are schematic representations of cells waiting for service from a server as a function of virtual time.
  • Figures 12-20 are schematic representations of cells waiting for service from a server as a function of virtual time.
  • Figure 21 is a schematic representation of an ATM switch element.
  • Figure 22 is a flow chart of a method of scheduling when a server provides service to entities of the present invention.
  • Figure 23 is a flow chart of an alternative method of scheduling when a server provides service to entities of the present invention.
  • a scheduler 10 for controlling when N entities 12, where N is an integer ⁇ 1, are operated upon by a server 14.
  • the scheduler 10 comprises a starting time memory, such as a priority queue 16, having starting times s i of the N entities, where 1 ⁇ i ⁇ N and is an integer, and s i corresponds to the time the i'th entity starts requesting service from the server 14.
  • the scheduler 10 is also comprised of a finishing time memory, such as a priority queue 18, having finishing times f i of the N entities 12, where f i corresponds to the time the i'th entity should be operated upon by the server 14.
  • the scheduler 10 is also comprised of a virtual clock 20 that keeps track of time so the starting times s i and finishing times f i can be identified. Additionally, the scheduler 10 comprises a controller 22 which provides entities service from the server 14 in the order of the entities with an earliest finishing time f i and a start time s i being operated upon first, and then the entities with the earliest or latest starting time s i or having the highest or lowest id or rate if their finishing times are the same being operated upon next at each given time. As is apparent from the latter, if the entities' finishing times are the same, then whatever protocol is desired to indicate which entity is to be provided to the server 14 to be operated upon is the choice of the operator.
  • scheduler 10 can include an element pool 24 which is connected with the N entities 12 and receives elements from the N entities 12 to be operated upon by the server 14.
  • the arrival times s i of elements then corresponds to the time elements from the i'th entity 12 arrives in the element pool 24 and the finishing times f i correspond to the time an element from the i'th entity 12 is to leave the element pool 24 and be operated upon by the server 14.
  • the controller 22 transfers or chooses elements to be operated upon by the server 14 from the element pool 24.
  • the controller 22 is connected to the virtual clock 20, the element pool 24, the starting time priority queue 16 and the finishing time priority queue 18 for controlling time of the virtual clock 20, storing the elements in the element pool 24, and the arrival times s i and their finishing times f i in the starting time priority queue 16 and the finishing time priority queue, respectively.
  • the controller 22 preferably operates upon entities or elements of the element pool 24 sequentially.
  • the controller 22 causes the virtual clock 20 to move present virtual time forward when an entity receives service or an element leaves the element pool 24.
  • the controller 22 can cause the virtual clock 20 to increment virtual time to the earliest starting time of an entity or an element if the earliest start time of an entity is later than virtual time, otherwise, the controller 22 causes the virtual clock 20 to increment virtual time by a unit of virtual time.
  • the controller 22 transfers the element out of the element pool 24 which has the earliest finishing time f i and a starting time s i unless there is more than one element with the earliest finishing time fi, in which case, preferably, the element with the earliest starting time s i is transferred out of the element pool 24 by the controller 22 and before its finishing time f i .
  • the present invention pertains to a scheduler 10 for scheduling when N entities each of which has a weight w, where N is an integer ⁇ 1 and w is a real number, are served by a server 14.
  • the scheduler 10 is comprised of a starting time memory 16 having starting times s i when the N entities 12 request service, where 1 ⁇ i ⁇ N and is an integer, and s i is the time at which the i'th entity may next get service from the server 14.
  • the scheduler 10 is also comprised of a finishing time memory 18 having finishing times f i when the N entities should be serviced, where f i is the time by which the i'th entity should be serviced by the server 14.
  • T or X can be essentially any real number as long as both are not 0; and either Y or Z can be essentially any real number as long as both are not 0.
  • the scheduler 10 is also comprised of a controller which chooses which entity is to be operated upon by the server 14 in the order of the entity with an earliest finishing time f i and a start time s i receiving service first, and then the entities based on a predetermined criteria.
  • the predetermined criteria can essentially be any type of tie-breaking procedure that the user wishes to apply such as earliest start time or id number, etc.
  • “1" is used to represent the maximum rate of work of the server 14, so it makes no sense to give a single entry a weight which would be equal to greater than 100% of the capacity of the server 14).
  • the sum of the weights of all entities will be less than or equal to 1 if the entities are not restricted as to how much work they can ask the server 14 to perform. This is equivalent to not allocating more than 100% of the server 14 capacity. If an entity is somehow restricted from asking for more than some fraction (say RS i ⁇ 1) of the server's capacity, then a more general statement is that the sum (over all entities) of MIN(w i , RS i ) should be less than 1.
  • s i is the time at which the i'th entity may next get service and f i is the time by which the i'th entity should be serviced.
  • U i can be different than one based on the application. For instance, u i may not be equal to one in a packet based network.
  • So f Fmin value of the finishing time of the entity with the smallest finishing time.
  • So s Smin value of the starting time of the entity with the smallest starting time.
  • V k indicates the k'th time that the server does work.
  • V k MAX ( V k -1 +(1 ⁇ X ), ( s Smin ⁇ Y ) +(( f Fmin - s Smin ) ⁇ Z ))
  • V k MAX ( V k -1 +((1/ AW ) ⁇ T ), ( s Smin ⁇ Y ) + (( f Fmin - s Smin ) ⁇ Z )) where ( ⁇ T ⁇ *( ⁇ Y ⁇ + ⁇ Z ⁇ )>0
  • Equation (1) is Equations (2) and (3) together.
  • Equation (1) with is "Virtual Clock” (VC). See Zhang, L. (1989) "A new architecture for packet switching network protocols". Report LCS TR 455, Laboratory for Computer Science, Massachusetts Institute of Technology. Cambridge, Massachusetts, incorporated by reference.
  • Equation (1) with is “Self-Clocked Fair Queueing” (SFQ). See “A Self-Clocked Fair Queueing Scheme for Broadband Applications” by S.J. Golestani, In Proc. IEEE Infocom, May 1994, incorporated by reference.
  • Equation (1) with is “approximately” “Weighted Fair Queueing” (WFQ). See “Analysis and Simulation of a Fair Queueing Algorithms” by A. Demers, S. Keshav, and S. Shenker; Internetworking: Research and Experience, Vol. 1, 3-26 (1990), incorporated by reference, and A.K.J. Parekh, A Generalized Processor Sharing Approach to Flow Control in Integrated Services Networks, Ph.D. Dissertation, Massachusetts Institute of Technology, Cambridge, Mass., February 1992, incorporated by reference.
  • Equation (1) with is "Virtual Service Queueing" (VSQ) of the present invention.
  • the present invention pertains to a method of scheduling when a server 10 operates on entities, as shown in figure 22.
  • the method comprises the steps of requesting service of the server from N elements, where N ⁇ 1 and is an integer. Then there is the step of storing when each of the N entities first requests service and when each of the N entities is to have received service from the server. Next, there is the step of providing service to an entity of the N entities which has the earliest receive time and a request time, unless there is more than one entity with the earliest receive time in which case the entity with the earliest request time receives service from the server. Preferably, after the providing step, there is the step of repeating the providing step in regard to other entities.
  • the controller 22 can cause the steps to be implemented.
  • the present invention also pertains to a method for scheduling when a server 14 provides service to entities, as shown in figure 23.
  • the method comprises the steps of identifying when an entity requests service from the server 14.
  • the process for identifying when a first entity requests service from the server can include any technique or method for calculating when the first entity requests service from the server 14. This can include identifying when the request occurs by actually determining the time when the entity requests service from the server 14. Or, it can be calculated from when a previous entity has requested service from the server 14 and determined by some function or relationship when the entity requests service from the server 14. Or, it can be determined as a function of another entity which is currently receiving service from the server 14. Alternatively, the time when the first entity requests service can be identified from a time when the entity is to receive service from the server 14. For instance, start time plus 1/W i equals finish time.
  • the identifying step can be part of a calculation where at some point in the overall process of identifying time for the server to provide service to the entity, the time when the entity requests service from the server is identified. Basically, the identifying step can be a conclusion to a process or as an interim step to a process.
  • the entity preferably is a first entity which requests service from the server 14.
  • the method for scheduling when a server 14 provides service to entities next comprises the step of providing service to an entity as a function of when the entity requests service from the server 14.
  • the entity can be the first entity and it receives service from the server 14 as a function of when the first entity requests the service from the server 14. It is preferably when the first entity first requests service from the server 14 that is a basis for providing service to the first entity.
  • the present invention pertains to a scheduler for controlling when a server provides service to entities.
  • the scheduler comprises a memory, having times which are a function of when entities request service from the server 14.
  • the scheduler 10 also comprises a virtual clock 20 that keeps track of time as a function of when entities request service from the server 14.
  • the scheduler 10 comprises a controller 22 which causes an entity to receive service from the server 14 as a function of when the entity requests service from the server 14.
  • the memory can be a starting time, such as a priority queue 16.
  • a scheduler 10 will schedule when the users with cells will be served by the server 14.
  • the scheduler 10 logs in the time a user first requests service from the server 14.
  • the scheduler 10 also logs in the latest time the user should finish waiting for service from the server 14.
  • the scheduler 10 records the start time and the finish time for each user that requests service from the server 14. This information is obtained from the user and from the virtual clock 20 identifying when the user has first started waiting for the service from the server 14. This can occur by the entity sending a signal to the server 14 or the scheduler 10 when it requests service; or by the scheduler 10 or the server 14 using a sensor, or trigger to identify when the entity is requesting service.
  • This aspect of the invention can be similar to how a telecommunications switch operates to switch signals which arrive at the switch from several connections, as is well known in the art.
  • the scheduler 10 determines which user of the users waiting for service from the server 14 has the earliest finishing time. The user with the earliest finishing time is then provided service by the server 14 and the user's cell is operated upon by the server 14. If the users have the same finishing time, then the server looks at which user has the earliest start time and provides service to the user with the earliest start time. The scheduler 10 causes the user to receive service from a server 14 even though its time to finish waiting for service may not as yet have occurred.
  • the scheduler 10 looks for the next user to receive service from the server 14.
  • a user that has a high rate will receive service from the server 14 more often than a user with a lower rate.
  • the scheduler 10 is not controlled by the user receiving service from the server 14 when its finish time occurs, users with lower rates can receive service from the server 14 intermittently when the server 14 is not providing service to a higher rate.
  • the server 14 is controlled by the fact that over a given unit cycle of operation, it has certain service capability, and that all the rates of the different users combine to equal that unit rate for the cycle, then over the course of a cycle, each user will have service provided by the server 14.
  • each user A-E has rates of .5, .2, .1, .1, .1, respectively.
  • each user A-E has a cell which arrives for service from a server 14.
  • a cell from user B arrives to receive service from server 14.
  • the server 14 provides service to the cell from user D since all the cells waiting for service have the same finish time but the cell from user D has a start time of 0, which is as early as a cell from user E but earlier than the cell from user B. See figure 7.
  • a cell from user A arrives for service from server 14.
  • the server 14 provides service to the cell from user A since the cell has the earliest finish time of the cells waiting for service from server 14. See figure 8.
  • a cell from user A arrives for service from the server 14.
  • the cycle then repeats itself as described above.
  • a cell from user A arrives for service from the server 14.
  • the virtual time is advanced by one increment to the earliest starting time of a cell that requires service from the server 14.
  • a cell from user A arrives for service from the server 14.
  • a cell from user B arrives for service from server 14.
  • the server from server 14 provides service to the cell from user B since the cell from user B has the earliest finish time of any cell waiting for service from server 14. See figure 17.
  • the virtual time is incremented to the next virtual time that corresponds to the earliest start time that a cell would require service from the server 14.
  • a cell from user A arrives for service from server 14.
  • the server 14 provides service to the cell from user A because it has the earliest finish time. See figure 18.
  • the virtual time is incremented by two units in this instance.
  • a cell from user A arrives for service from the server 14.
  • Server 14 provides service to the cell from user A since it has the earliest finish time. See figure 19.
  • each entity 12 there are three entities 12 connected to an element pool 24. These entities 12 have associated with them a weight and a rate. For instance, user 0 associated with the 0th entity 12 has a weight of .5 and a rate of .5. User 1 associated with the first entity 12 has a weight of .333 and a rate of .333. User 2 associated with the second entity 12 has a weight of .166 and a rate of .166.
  • the virtual time is 0.
  • Cells 000, 001 and 002 corresponding with the 0th, 1st, 2nd entities 12 of the 0th, 1st and 2nd users arrive at the element pool 24.
  • the start time column user 0 has the second or last position in regard to when the cell 000 associated with the 0th user arrived in the element pool 24.
  • there is a quantity Q identified in the column Q showing there is but 1 cell of user 0 in the element pool 24.
  • the quantity Q of user 0 is now 0 since its corresponding cell has been operated upon by the server 14 and is no longer in the element pool 24.
  • the finishing time priority queue 18 also reflects the finishing queue of user 0 having a -1 in the element pool 24 since the cell associated with user 0 is no longer present in the element pool 24.
  • the server can only operate on one cell at a time, only the cell of user 0, which has the earliest finishing time, is removed from the element pool 24.
  • all the cells of user 0, 1 and 2 have arrived at the same starting time in the element pool 24, even though their weights may be different, they are ordered in the starting time priority queue 16 on the basis of highest user number to lowest user number, although essentially any scheme of ordering could be chosen.
  • the quantity of cells associated with user 0 in the element pool 24 is then reduced by 1.
  • an ATM switch element has one to N input connections 102 and one to M output connections 104, as shown in figure 21.
  • ATM cells are received by the switch element 100 through the input connections 102.
  • the switch element 100 operates on the cells and sends them on their way through output connections 104.
  • a cell comes in over a specific input connection 102, it is placed in a pool 106, as is well known in the art, and informs the scheduler 108 of the switch element, as is well known in the art, of the presence of the cell in the corresponding pool 106.
  • each input connection 102 can have its own unique pool 106 in which cells entering the switch element 102 are stored or there can be a common pool 106 in which all cells from each individual input connection 102 are stored until the server 110 of the switch element is ready to operate upon them.
  • the scheduler 108 of the switch element 100 operates as described above except in the ATM context, the finish time is determined by the finish time identified in the scheduler for the cell as well as a bid value that has been provided by the cell in order to obtain service by the server 110 of the switch element 100.
  • This use of a bid is well known in the art. See, for instance, "Gigabit Networking” by Craig Partridge, Addison Wesley, 1994; "ATM User Network Interface Specification, Version 3.0" by the ATM Forum, Prentice Hall, 1994; “Asynchronous Transfer Mode Networks: Performance Issues", by Raif O. Onvural, Artech House, Inc., Norwood, Mass. 1994, all of which are incorporated by reference.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Computer Security & Cryptography (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Educational Administration (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Game Theory and Decision Science (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)
EP95309404A 1994-12-22 1995-12-22 Verfahren und Scheduler zum Steuern, wenn ein Server eine Einheit bedient Ceased EP0721167A3 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US362217 1994-12-22
US08/362,217 US5828879A (en) 1994-12-22 1994-12-22 Method and a scheduler for controlling when a server provides service to an entity

Publications (2)

Publication Number Publication Date
EP0721167A2 true EP0721167A2 (de) 1996-07-10
EP0721167A3 EP0721167A3 (de) 1998-01-28

Family

ID=23425176

Family Applications (1)

Application Number Title Priority Date Filing Date
EP95309404A Ceased EP0721167A3 (de) 1994-12-22 1995-12-22 Verfahren und Scheduler zum Steuern, wenn ein Server eine Einheit bedient

Country Status (4)

Country Link
US (2) US5828879A (de)
EP (1) EP0721167A3 (de)
JP (1) JP4263254B2 (de)
CA (1) CA2150966C (de)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998041957A1 (en) * 1997-03-19 1998-09-24 Trintech Limited A point-of-sale transaction processing system
CN103729927A (zh) * 2013-12-16 2014-04-16 王美金 一种免除银行客户等候的调度方法及系统
CN104091386A (zh) * 2014-06-02 2014-10-08 王美金 基于计算机和大数据的银行业务流程的方法和系统

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4151991B2 (ja) * 1997-05-26 2008-09-17 コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ ビデオサーバにおいてデータを取り出すシステム
US6243751B1 (en) * 1997-06-11 2001-06-05 Oracle Corporation Method and apparatus for coupling clients to servers
US6088728A (en) * 1997-06-11 2000-07-11 Oracle Corporation System using session data stored in session data storage for associating and disassociating user identifiers for switching client sessions in a server
US6393483B1 (en) * 1997-06-30 2002-05-21 Adaptec, Inc. Method and apparatus for network interface card load balancing and port aggregation
US9239763B2 (en) 2012-09-28 2016-01-19 Oracle International Corporation Container database
WO2001043347A2 (en) * 1999-12-08 2001-06-14 The University Of British Columbia Weighted fair queuing scheduler
JP4092388B2 (ja) * 2000-11-10 2008-05-28 富士通株式会社 ネットワークを用いたサービス提供方法及びそれを用いたサービス提供システム
US6925499B1 (en) * 2001-12-19 2005-08-02 Info Value Computing, Inc. Video distribution system using disk load balancing by file copying
US7039784B1 (en) * 2001-12-20 2006-05-02 Info Value Computing Inc. Video distribution system using dynamic disk load balancing with variable sub-segmenting
US20040127215A1 (en) * 2002-12-31 2004-07-01 Shaw Venson M. Delivery of network services
US7945914B2 (en) * 2003-12-10 2011-05-17 X1 Technologies, Inc. Methods and systems for performing operations in response to detecting a computer idle condition
US7502824B2 (en) 2004-08-12 2009-03-10 Oracle International Corporation Database shutdown with session migration
US7415470B2 (en) * 2004-08-12 2008-08-19 Oracle International Corporation Capturing and re-creating the state of a queue when migrating a session
US9176772B2 (en) * 2005-02-11 2015-11-03 Oracle International Corporation Suspending and resuming of sessions
US7995474B2 (en) * 2005-09-13 2011-08-09 International Business Machines Corporation Grid network throttle and load collector
US7853948B2 (en) * 2005-10-24 2010-12-14 International Business Machines Corporation Method and apparatus for scheduling grid jobs
US7831971B2 (en) * 2005-10-24 2010-11-09 International Business Machines Corporation Method and apparatus for presenting a visualization of processor capacity and network availability based on a grid computing system simulation
US20070118839A1 (en) * 2005-10-24 2007-05-24 Viktors Berstis Method and apparatus for grid project modeling language
US8549038B2 (en) 2009-06-15 2013-10-01 Oracle International Corporation Pluggable session context
US20110038325A1 (en) * 2009-08-13 2011-02-17 Clear Wireless Llc System and method for scheduling packets in a communication system
WO2015196410A1 (en) 2014-06-26 2015-12-30 Google Inc. Optimized browser render process
KR101768181B1 (ko) 2014-06-26 2017-08-16 구글 인코포레이티드 최적화된 브라우저 렌더링 프로세스
CN106462582B (zh) * 2014-06-26 2020-05-15 谷歌有限责任公司 批处理优化渲染和获取架构
US10289617B2 (en) 2015-12-17 2019-05-14 Oracle International Corporation Accessing on-premise and off-premise datastores that are organized using different application schemas
US10387387B2 (en) 2015-12-17 2019-08-20 Oracle International Corporation Enabling multi-tenant access to respective isolated data sets organized using different application schemas
US10303894B2 (en) 2016-08-31 2019-05-28 Oracle International Corporation Fine-grained access control for data manipulation language (DML) operations on relational data

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4736318A (en) * 1985-03-01 1988-04-05 Wang Laboratories, Inc. Data processing system having tunable operating system means
US4745836A (en) * 1985-10-18 1988-05-24 Dannenberg Roger B Method and apparatus for providing coordinated accompaniment for a performance
US5187790A (en) * 1989-06-29 1993-02-16 Digital Equipment Corporation Server impersonation of client processes in an object based computer operating system
US5261099A (en) * 1989-08-24 1993-11-09 International Business Machines Corp. Synchronous communications scheduler allowing transient computing overloads using a request buffer
WO1991004540A1 (en) * 1989-09-08 1991-04-04 Auspex Systems, Inc. Multiple facility operating system architecture
EP0422310A1 (de) * 1989-10-10 1991-04-17 International Business Machines Corporation Verteilter Mechanismus für die schnelle Planung von gemeinsamen Objekten
US5142533A (en) * 1991-03-28 1992-08-25 Motorola, Inc. Method for controlling the scheduling of multiple access to communication resources
US5327558A (en) * 1992-04-30 1994-07-05 Motorola, Inc. Method for asynchronous application communication
US5437039A (en) * 1992-05-21 1995-07-25 Intel Corporation Servicing transparent system interrupts and reducing interrupt latency
US5414845A (en) * 1992-06-26 1995-05-09 International Business Machines Corporation Network-based computer system with improved network scheduling system
US5404523A (en) * 1993-11-10 1995-04-04 Digital Equipment Corporation Method of managing requests in a transaction processing system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LIXIA ZHANG: "VIRTUALCLOCK: A NEW TRAFFIC CONTROL ALGORITHM FOR PACKET-SWITCHED NETWORKS", ACM TRANSACTIONS ON COMPUTER SYSTEMS, ACM, NEW YORK, NY, US LNKD- DOI:10.1145/103720.103721, vol. 9, no. 2, 1 May 1991 (1991-05-01), pages 101 - 124, XP000259558, ISSN: 0734-2071 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998041957A1 (en) * 1997-03-19 1998-09-24 Trintech Limited A point-of-sale transaction processing system
CN103729927A (zh) * 2013-12-16 2014-04-16 王美金 一种免除银行客户等候的调度方法及系统
CN104091386A (zh) * 2014-06-02 2014-10-08 王美金 基于计算机和大数据的银行业务流程的方法和系统

Also Published As

Publication number Publication date
CA2150966C (en) 2002-05-21
JPH08272709A (ja) 1996-10-18
JP4263254B2 (ja) 2009-05-13
US5845115A (en) 1998-12-01
US5828879A (en) 1998-10-27
CA2150966A1 (en) 1996-06-23
EP0721167A3 (de) 1998-01-28

Similar Documents

Publication Publication Date Title
US5828879A (en) Method and a scheduler for controlling when a server provides service to an entity
EP0721168A2 (de) Verfahren und Scheduler zum Steuern, wenn ein Server eine Einheit unter Berücksichtigung der Haüfigkeit bedient
US5859835A (en) Traffic scheduling system and method for packet-switched networks
EP1083709B1 (de) Verfahren und Vorrichtung zur Verkehrsablaufsteuerung um die Dienstqualität in einem Kommunikationsnetzwerk zu erfüllen
US7461159B2 (en) Weighted fair queuing scheduler
EP0859492B1 (de) Vorrichtung mit einem gewichteten gerechten Warteschlangenverfahren und mit adaptiver Umverteilung der Bandbreite
Shin et al. Design and evaluation of real-time communication for fieldbus-based manufacturing systems
Takagi et al. Analysis of a discrete-time queueing system with time-limited service
US7130270B2 (en) Method and apparatus for varying bandwidth provided to virtual channels in a virtual path
US7567572B1 (en) 2-rate scheduling based on search trees with configurable excess bandwidth sharing
Landry et al. Queueing study of a 3-priority policy with distinct service strategies
Altman et al. Discrete time queues with delayed information
Chen et al. A Queueing Analysis of the Performance of DQDB
Balakrishnan et al. Buffer losses vs. deadline violations for ABR traffic in an ATM switch: A computational approach
KR100333475B1 (ko) 고속 패킷 노드를 위한 속도 비례 자가 클럭 공정 패킷스케쥴링 장치 및 그 스케쥴링 방법
Tassiulas Cut-through switching, pipelining, and scheduling for network evacuation
Kwak et al. A new starting potential fair queuing algorithm with O (1) virtual time computation complexity
Puliafito et al. Buffer sizing for ABR traffic in an ATM switch
JP2004520731A (ja) 複数の情報パケットフロー間で共用資源をスケジュールするための手順及びシステム
Hariri et al. A hierarchical analysis approach for high performance computing and communication applications
Laevens et al. Discrete-time queueing models with feedback for input-buffered ATM switches
JPH10190665A (ja) コネクション帯域変更要求装置、atmエンドシステム及びatm交換機
La Corte et al. Jitter analysis in an ATM multimedia multiplexer
JPH118633A (ja) ユーザ指向入力型ネットワーク設計装置
Ko et al. Emulated weighted fair queueing algorithm for high-speed packet-switched networks

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): DE FR GB

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): DE FR GB

17P Request for examination filed

Effective date: 19980721

17Q First examination report despatched

Effective date: 20000317

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: MARCONI COMMUNICATIONS, INC.

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: MARCONI INTELLECTUAL PROPERTY (RINGFENCE) INC.

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ERICSSON AB

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ERICSSON AB

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ERICSSON AB

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20111119