WO2005034463A1 - Verfahren zur bereitstellung von leistungsmerkmalen bei bedarf - Google Patents
Verfahren zur bereitstellung von leistungsmerkmalen bei bedarf Download PDFInfo
- Publication number
- WO2005034463A1 WO2005034463A1 PCT/EP2004/051729 EP2004051729W WO2005034463A1 WO 2005034463 A1 WO2005034463 A1 WO 2005034463A1 EP 2004051729 W EP2004051729 W EP 2004051729W WO 2005034463 A1 WO2005034463 A1 WO 2005034463A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bandwidth
- server
- feature
- request
- terminal
- Prior art date
Links
Classifications
-
- 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/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/28—Flow control; Congestion control in relation to timing considerations
-
- 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- 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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- 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/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Definitions
- the invention relates to a method for transmitting software and / or data on request from a server to a terminal in a packet network.
- the principle is often used to only reload certain software components from the network when necessary. This principle is referred to as software on demand.
- the end device can use less storage capacity because the proportion of software and data in the end device that is not used anyway is reduced, on the other hand, it enables central management of the data and software and, in some cases, software savings -License fees.
- This principle is also known in particular for IP-based (internet protocol-based) telecommunications networks, in which end devices only reload the software for certain performance features when the user needs the performance feature, i.e. if he uses it or activates it (feature-on-demand).
- the features are stored on a central server, which is also called the "Feature Mall", and a feature is transferred to the terminal when it is activated and installed there.
- the Feature Mall can also be a central or decentralized service ,
- LAN local area networks
- the bandwidths are normally sufficient to enable the feature to be transmitted almost in real time. In this case, the user cannot distinguish whether the feature is transmitted on-demand or whether it is already installed in his end device.
- Bandwidths are managed in a packet network by a network resource manager.
- network resource management is only used to carry out a call acceptance check. This does not prevent waiting times when reloading features on demand.
- the object of the invention is to provide a method and a device with which a transfer of software and data on-demand under practical conditions is possible in a satisfactory manner.
- the object is achieved with a method according to claim 1 and a server according to claim 14, with a terminal according to claim 21 and in a network arrangement according to claim 23.
- the invention includes the essential idea of checking before transmission whether the available resources are sufficient to quickly make software or data available. The key question is whether a transfer can be carried out quickly enough upon a load request, which mainly depends on the bandwidth. If the currently available bandwidth is not sufficient, the load request is rejected.
- the method according to the invention and the server use the bandwidth test to ensure that, at the time of transmission, there is sufficient bandwidth available for transmission within a time limit (which can be predetermined in view of user habits).
- a satisfactory loading time can be guaranteed for the user via the bandwidth, and it reliably prevents software or data from being transmitted with unreasonable waiting times.
- the terminal device makes transparent to the user which features are actually available to him in an acceptable time and not just nominally. Even if the available bandwidth is low, the user is not tempted to select a feature several times that is in his selection list, but at least cannot be transmitted at the moment.
- the method is preferably used in IP-based telecommunication networks.
- Terminal devices with fewer resources of their own, which are often used in telecommunications, benefit from on-demand transmission, and at the same time the acceptable waiting times are short.
- the software to be transferred is a performance feature that is requested by the end device when required.
- the method according to the invention ensures that the use of such performance is not made difficult by long charging times.
- the bandwidth required is advantageously calculated on the basis of an upper limit for the loading time.
- the parameter that is of greatest interest to the user is used as the criterion with the loading time. It does not use more bandwidth and ultimately expensive network resources than necessary.
- the information about the required bandwidth is preferably part of the request and is thus made available by the terminal. This allows an individual and also configurable requirement for the available bandwidth, depending on the device. Alternatively or additionally, the information about the required bandwidth is associated with the requested data or the requested software and is therefore made available by the server.
- the server has access to the respectively requested software or the requested data, with which a bandwidth requirement can be stored at the same time or from which the bandwidth requirement can be easily determined.
- the information about the available bandwidth is made available by a network resource manager, this information being updated in particular regularly or at the request of the server. Current bandwidth data is therefore always available and network resource management that already exists for other tasks can be used.
- the network resource management preferably manages priorities for all network resource requests and carries out the following steps in the event of a negative test result of the bandwidth test: - Determination of the difference in demand between required and existing network resources for the transmission,
- This procedure enables network resources to be assigned to different users, end devices or requested data or software depending on their importance, and a loading request that initially failed could still be served with the required bandwidth if the importance was high.
- a message is sent to the end device, which message can include one of the following two rejections:
- the terminal receives the information as to whether another similar charging request could be successful immediately or at a later point in time. After a temporary rejection, a new loading request is advantageously generated automatically. Was the required bandwidth only temporarily not available, it can be used at a later time.
- a permanent rejection can preferably be generated by one of the following steps:
- the user of the terminal is preferably shown the message, in particular by marking the option for the request that led to the message with a warning or making it completely inaccessible.
- a bandwidth requirement memory for storing the required bandwidth for a performance feature is advantageously additionally connected to the performance feature providing device so that the performance feature providing device can carry out the bandwidth test to determine which bandwidth a transmission of data and / or software according to a La - Required for a feature.
- This bandwidth requirement memory enables the required bandwidth to be looked up quickly.
- Preference has the performance feature - Most ready! 1 device access to a maximum bandwidth memory for storing the maximum available bandwidths for connections to terminal devices in order to provide an additional or alternative bandwidth perform the tentest based on the maximum available bandwidths.
- the maximum bandwidths can therefore be easily looked up.
- a network resource allocation device which is connected to the performance feature provision device and has access to the available bandwidth memory, the network resource allocation device being able to allocate or refuse network resources to the loading request and accordingly to the available bandwidths - Memory updated.
- a network resource allocation device is usually part of a server and can be used in a simple manner for communication relating to the bandwidth with the performance feature provision device.
- the network resource allocation device is connected to a network resource test device which has access to the available bandwidth memory and at least one connection to a terminal in order to keep up to date
- the network resource test device can determine and store the currently available bandwidths so that current data is stored in the available bandwidth memory.
- the network resource allocation device has access to a network resource distribution memory which stores data about bandwidths assigned to processes and priorities of these processes, the network resource allocation device being able to redistribute network resources depending on the priorities of the processes and the loading request in order to provide sufficient bandwidth for the loading request close.
- a network resource distribution memory is a prerequisite for intelligent management of the existing network resources.
- the network resource allocation device further preferably has access to a network resource request memory which stores data about requested bandwidths in order to manage processes to which no bandwidth is currently allocated. A storage for unprocessed or frozen
- Table 1 shows an example of a network resource management table that is stored in a server according to the invention
- Table 2 shows an example of an availability table of performance features that is stored in a server according to the invention.
- 1 is a highly simplified schematic representation of a minimal network with a terminal according to the invention and a server according to the invention
- 2 shows an example for the data exchange between a terminal and a server according to the inventive method
- FIG. 3 shows a more detailed schematic representation of the functional units in a server according to the invention.
- FIG. 4 shows a block diagram of a network arrangement according to the invention.
- the network is a packet network and can be an IP-based telecommunication network, in which case the terminal 10 can also be a telecommunication terminal.
- the terminal 10 offers the user via a user interface 11 access to various software or data which the user can select and which are then loaded on-demand by the server 20 if they are not available locally.
- the software is often a feature that is requested by a feature loading device 12 connected to the user interface on-demand from the server 20 or a service running on this server. Therefore, in the following only the term performance feature is used, but also general software or data are included, which are processed in principle in the same way by the inventive method and the devices.
- bandwidth is always used as a criterion for sufficient performance.
- bandwidth translates directly into waiting time, ie it is the appropriate parameters, although sufficient bandwidth is of no immediate importance to the user. This means that the need for a real-time application can also be included if necessary, because real-time ultimately means nothing other than that the waiting times are very short and, depending on the requirements of the requesting application, can be neglected or lie in the area that is also required for activation local functions is required.
- a loading request corresponding to the selected performance feature is sent from the performance feature loading device 12 to a performance feature management device 30 connected to it in the server 20 and processed there.
- the performance feature management device 30 is connected to a network resource management device 40 which, among other things, provides information about network resources.
- FIG. 2 shows an example of the data and message exchange between the terminal 10 and the server 20 using the method according to the invention.
- a user selects a feature in the user interface 11, and the user interface 12 forwards a corresponding request to the feature loading device 12 (step S1).
- the feature loading device normally forwards this loading request to the feature management device 30 in the server 20 (step S2).
- it can also be tested beforehand whether a similar charging request has already been made or whether the request should not be forwarded due to network problems, for example.
- the performance management device 20 generates a bandwidth status request to the network resource management device 40 after receiving the load request (Step S3).
- This bandwidth status request is processed by the network resource management device 40 in a manner detailed in connection with FIG. 4 (step S4), and the bandwidth status is returned to the feature management device 30 (step S5).
- the performance feature management device 30 evaluates the charging request (step S6). First, it is tested whether the available bandwidth is sufficient for a transmission of the requested performance. (This bandwidth test is also explained in more detail below in connection with FIG. 4.) It is pointed out that the bandwidth test can also be carried out without a network resource management device 40 and the associated method steps S3 to 35. Then the test is limited to information that is independent of the dynamic properties of the network connections. Examples of this could be, in principle, not to transfer any performance features via a bottleneck, such as an internet connection, or outside of your own local network (LAN), or to set a (possibly time-dependent) limit on the server side, i.e. in principle not to transmit any performance characteristics that exceed a maximum bandwidth requirement.
- a bottleneck such as an internet connection, or outside of your own local network (LAN)
- LAN local network
- the bandwidth test delivers a positive test result, the requested feature, otherwise a message about the rejection to the feature loading device 12, is transmitted (step S7).
- the feature loading device 12 can simply pass on the feature or the message to the user interface
- Step S8 and thus end the process cycle.
- it can also carry out its own processing steps. This includes caching, temporary storage of the performance feature in order to make it available to another connected user interface, or local storage of the performance feature for later inquiries on a permanent storage medium.
- the performance feature loading device 12 automatically evaluates the rejection and, if necessary, generates a new loading request and sends it to the server.
- the rejection is divided into at least two classes, namely temporary and permanent rejections.
- a temporary rejection could mean that although not enough bandwidth is currently available, a transfer with the desired bandwidth would in principle be possible with a lower utilization by other processes.
- a permanent rejection indicates that further charging requests will not result in the desired performance being transferred.
- a temporary or repeated repeated rejection can lead to a permanent rejection. This decision can be made on the server side as well as on the end device. Another possible reason for a permanent rejection is if the maximum bandwidth is already smaller than the required one.
- the user interface 11 installs the transmitted performance feature, which can be used by the user from this point in time. If the user's load request has not resulted in the transfer of the selected feature, the user interface indicates this to the user. This can be a simple message; However, it is clearer if the result of the current and previous charging requirements can be seen directly in the selection of possible performance features.
- Each feature can e.g. be provided on a control panel of the corresponding end device with a (color) coding or an addition which indicates its status: local performance feature, already reloaded, (simple or x-fold) failed attempt to charge. In particular, a performance feature can no longer be displayed even after an associated attempt to charge has failed.
- the user can also be shown why his request led to a rejection.
- he has requested a feature that requires a bandwidth of 200 kbit / s, and the rejection includes the information that only 100 kbit / s are currently available.
- the user interface can also offer him an option to send the load request again, which then includes information about the reduced bandwidth required.
- FIG. 3 shows a more detailed schematic representation of the functional units in a server according to the invention.
- Several functional units in the server 20 are connected to a network 50 with terminals 10.
- the server has the main features of the feature management device 30 and the network resource management device 40.
- the feature management device 30 has a feature providing device which is externally connected to the feature loading device 12 of a terminal 10 in the network 50. It also includes a feature memory 32, which stores the software or data for features, and a bandwidth requirement memory 33, which, in association with the features, stores the bandwidths required for transmission.
- the feature providing device has access to these two memories 32 and 33 of the feature management device.
- the central element of the network resource management device is a network resource allocation device 41, which is connected to terminals 10 of the network 50 and to the feature provision device 31, from which it can receive network resource requests and bandwidth status requests.
- the network resource allocation device 41 points Processes and load requests bandwidth or denied them.
- the network resource allocator 41 has access to an available bandwidth store 42, which holds a list of available bandwidths for the connection to the terminals 10, and a maximum bandwidth store 43, which a corresponding list of maximum available bandwidths for the Connection to terminals 10 holds.
- the performance feature provision device also has direct access to the two bandwidth memories 42 and 43.
- the network resource allocation device 41 has access to a network resource distribution memory 44, in which data about the allocation of the network resources to associated processes are stored, and a network resource request memory 45, in which data about requests for network resources or such processes are saved, to which no network resources are assigned in spite of need.
- a network resource test device 46 is connected to terminals 10 of the network 50 in order to test which bandwidths are currently available for the connection to a terminal 10.
- Network resource tester 46 has access to available bandwidth memory 42 to update the data stored therein and a connection to network resource allocator 41 to receive requests for such an update.
- FIG. 4 is a block diagram of a network 150 according to the invention.
- First to fourth terminals according to the invention are a block diagram of a network 150 according to the invention.
- the feature server 120 is part of a main LAN 160, in which the typical tasks such as a proxy server, a name server, an Internet server, a firewall, etc. are combined in a main LAN server 161.
- the feature server 160, the main LAN server 161 and a RAS server (Remote Access Service Server) 162 are connected to one another by the main LAN 160 via connections D. All of the described services of the main LAN 160 can of course be physically distributed to any number of computers or, in extreme cases, all run on the same computer.
- a branch LAN server 171 is connected to the main LAN server 161 via a connection C1 that does not belong to one of the two LANs; otherwise the main and branch LAN 160 and 170 would only be one LAN.
- the branch LAN server 171 in the branch LAN 171 has the same tasks as the main LAN server 161 in the main LAN 160.
- a provider server 181 is indirectly connected to the main LAN server 161 via a stage server 151 via the connection paths B1 and B2.
- connections shown are of course to be understood as examples. In a realistic network, each connection will have far more indications and will include any number of other stage servers and routers.
- the terminals HOa-llOd illustrate different scenarios on which ways features can be requested and transmitted.
- the first terminal 110a is connected to the RAS server 162 via a connection A, which can be an ISDN line, for example.
- a teleworker could work on this terminal via a normal telephone connection.
- the second terminal 110b is connected to the provider server 181 via a connection B3. This could be a teleworker on a VPN client (Virtual Private Network Client) via a DSL line or a user of a mobile telephone terminal.
- the third terminal 110c is connected fertilized C2 connected to the branch LAN server 171.
- the branch LAN 170 can be the LAN of a branch office, another branch office, a foreign agency or the like.
- the fourth terminal 11Od is integrated directly into the main LAN 160 via a connection D.
- Other, also wireless, connection types e.g. LAN or Blue Tooth are possible with the usual network connections.
- step S4 The evaluation of the bandwidth status request (step S4) and the evaluation of the loading request (S6) are described in more detail below.
- the method steps which have not been taken up again here can also be applied to the more complex network example 150 without further explanation.
- step S4 the network resource allocator 41 receives a bandwidth status request.
- This contains the information about which bandwidth is requested and for which end device.
- the associated route can be identified, for example, via IP addresses, a terminal identification number, domain names or LINs (Location Identification Numbers).
- the performance feature provision device 31 looks up the bandwidth information on the basis of the requested performance feature in the bandwidth requirement memory.
- Table 1 the two thickly framed left columns show a corresponding list with an identification number for the feature and the associated required bandwidth.
- the required bandwidth can also be part of the load request.
- the network resource allocation device 41 uses the data of the available bandwidth memory 42 to check whether the bandwidth is available.
- Table 1 an example of a table of such data is shown in the thickly outlined two headers, in which the available bandwidth is indicated for each terminal. If sufficient bandwidth is available, that is to say the required bandwidth is less than or equal to the available, the required bandwidth is assigned to the loading request and is subtracted from the available bandwidth of the corresponding connection in order to update the available bandwidth memory 42. The corresponding allocation of network resources is then the response to the feature provision device (step S5).
- a rejection of the network resource allocation which may include a message about the available bandwidth, is sent only in response to the bandwidth status request.
- the network resource allocation device 41 uses an optimization method in order to still be able to provide the requested bandwidth. It is conceivable here that assigned and requested network resources are assigned priorities and, if there are processes of lower priority than the load request, their network resources are reduced or completely withdrawn. Of course, this only makes sense if the sum of the bandwidth made accessible in this way and the already free bandwidth of the charging request are also sufficient, and it requires a consistent priority system that is based on the importance of tasks, but also on users or end devices can.
- the performance feature provision device 31 can compile a table from the data about the available bandwidth, as is shown as an example in the 4x6 right and lower columns b7w. Rows of Table 1 is shown. This is simpler if the feature provision device 31 can also directly access the available bandwidth memory 42. In it is for each feature and for every possible connection to a terminal, whether the feature is available or temporary or permanently unavailable. Steps S3-S6 then coincide into a single look up in this table. It should also be mentioned that the performance
- Provisioning device 31 can also refuse to transmit the feature at this point if the bandwidth has been sufficient, for example for security reasons.
- the memory 42 In order to keep the available bandwidths in the memory 42 up-to-date, the memory 42 must be updated periodically or at the request of the performance feature provision device 31 or the resource allocation device 41.
- the network resource test device 46 sends a bandwidth request to each terminal HOa-11Od. On the way to the terminal, the bandwidth of the associated partial connection is registered after each hop, and the collected data are sent back to the network resource test device 46 via partial connections.
- Table 2 shows the result of this test procedure.
- the terminal device 110b is connected to the feature server 120 via the provider server 181, the stage server 151 and the main LAN 160.
- the bandwidths available in accordance with the test are entered for the corresponding sub-connections D, B1, B2 and B3.
- the bandwidths within a LAN are assumed to be sufficient in any case and are accordingly set to infinity.
- the column on the maximum bandwidth is taken from the maximum bandwidth memory 43, but can be initialized in a completely analogous manner to the available bandwidths. The same applies to the connection type.
- the available bandwidth for the connection to a terminal can be seen in Table 2 according to the principle of bottle easily determine the neck.
- this bottleneck is the DSL connection B3 between the terminal 110b and the provider server 181, and the available bandwidth to the terminal 110b is therefore 256 kbit / s according to Table 2.
- Tables 1 and 2 show a clear and quick example of how the bandwidth test can be carried out.
- the respective data can also be determined in individual cases and such tables can be dispensed with.
- a service for locating the server 20 can also be used.
- the latter can either determine a server 20 or a feature mall service that provides the performance feature, or one that is connected with the highest possible bandwidth.
- the Feature Mall Service can optionally run decentrally on a terminal endpoint.
- the feature management device 30 can be physically and logically separated from the network resource management device 40 or form a unit with it.
- the performance feature management device 30 can be decentralized or central. It is also conceivable that these services are distributed, that is to say that depending on the performance feature, another server is responsible. In this case, the Feature Mall Service is distributed and / or decentralized. It is clear to the person skilled in the art that the server 20 only represents the localization of the required services.
- the invention does not depend on the type of packet network and in particular for H.323, SIP (Session Initiation Protocol) or proprietary standards.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/574,170 US8656005B2 (en) | 2003-09-29 | 2004-08-05 | Method for providing performance characteristics on demand |
CN200480028242.6A CN1860762B (zh) | 2003-09-29 | 2004-08-05 | 在需要时提供功能特征的方法 |
EP04766434A EP1668860A1 (de) | 2003-09-29 | 2004-08-05 | Verfahren zur bereitstellung von leistungsmerkmalen bei bedarf |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE10345184 | 2003-09-29 | ||
DE10345184.6 | 2003-09-29 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005034463A1 true WO2005034463A1 (de) | 2005-04-14 |
Family
ID=34399030
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2004/051729 WO2005034463A1 (de) | 2003-09-29 | 2004-08-05 | Verfahren zur bereitstellung von leistungsmerkmalen bei bedarf |
Country Status (4)
Country | Link |
---|---|
US (1) | US8656005B2 (de) |
EP (1) | EP1668860A1 (de) |
CN (1) | CN1860762B (de) |
WO (1) | WO2005034463A1 (de) |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100242048A1 (en) * | 2006-04-19 | 2010-09-23 | Farney James C | Resource allocation system |
US20080259810A1 (en) * | 2007-04-23 | 2008-10-23 | At&T Knowledge Ventures, Lp | Broadband Service Applications Test Tool |
US8184538B2 (en) * | 2007-06-22 | 2012-05-22 | At&T Intellectual Property I, L.P. | Regulating network service levels provided to communication terminals through a LAN access point |
US8174974B2 (en) * | 2009-11-12 | 2012-05-08 | Yahoo! Inc. | Voluntary admission control for traffic yield management |
US20130013666A1 (en) * | 2011-07-07 | 2013-01-10 | International Business Machines Corporation | Monitoring data access requests to optimize data transfer |
US10896432B1 (en) * | 2014-09-22 | 2021-01-19 | Amazon Technologies, Inc. | Bandwidth cost assignment for multi-tenant networks |
US9923965B2 (en) | 2015-06-05 | 2018-03-20 | International Business Machines Corporation | Storage mirroring over wide area network circuits with dynamic on-demand capacity |
US10581680B2 (en) | 2015-11-25 | 2020-03-03 | International Business Machines Corporation | Dynamic configuration of network features |
US10216441B2 (en) | 2015-11-25 | 2019-02-26 | International Business Machines Corporation | Dynamic quality of service for storage I/O port allocation |
US10177993B2 (en) | 2015-11-25 | 2019-01-08 | International Business Machines Corporation | Event-based data transfer scheduling using elastic network optimization criteria |
US10057327B2 (en) | 2015-11-25 | 2018-08-21 | International Business Machines Corporation | Controlled transfer of data over an elastic network |
US9923784B2 (en) | 2015-11-25 | 2018-03-20 | International Business Machines Corporation | Data transfer using flexible dynamic elastic network service provider relationships |
US9923839B2 (en) | 2015-11-25 | 2018-03-20 | International Business Machines Corporation | Configuring resources to exploit elastic network capability |
CN108400888B (zh) * | 2018-01-29 | 2021-07-23 | 深圳壹账通智能科技有限公司 | 一种日志处理方法、存储介质及终端设备 |
US10868853B2 (en) * | 2018-06-08 | 2020-12-15 | Verizon Patent And Licensing Inc. | System and method for image file generation and management |
US11018960B2 (en) * | 2019-03-06 | 2021-05-25 | Cisco Technology, Inc. | Accelerated time series analysis in a network |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0996264A1 (de) * | 1998-09-24 | 2000-04-26 | Bowne Global Solutions Germany GmbH | Verfahren und Vorrichtung zur Dateienübertragung |
EP1022883A2 (de) * | 1999-01-25 | 2000-07-26 | Siemens Aktiengesellschaft | Verfahren zum Realisieren einer Leistungsmerkmalsteuerung in einem Kommunikationsdatennetz |
WO2001061944A1 (en) * | 2000-02-16 | 2001-08-23 | Microsoft Corporation | System and method for transferring data over a network |
Family Cites Families (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4891805A (en) * | 1988-06-13 | 1990-01-02 | Racal Data Communications Inc. | Multiplexer with dynamic bandwidth allocation |
CA2130395C (en) * | 1993-12-09 | 1999-01-19 | David G. Greenwood | Multimedia distribution over wide area networks |
US6222856B1 (en) * | 1996-07-02 | 2001-04-24 | Murali R. Krishnan | Adaptive bandwidth throttling for individual virtual services supported on a network server |
US6968379B2 (en) * | 1997-05-30 | 2005-11-22 | Sun Microsystems, Inc. | Latency-reducing bandwidth-prioritization for network servers and clients |
US6075772A (en) * | 1997-08-29 | 2000-06-13 | International Business Machines Corporation | Methods, systems and computer program products for controlling data flow for guaranteed bandwidth connections on a per connection basis |
US6529499B1 (en) * | 1998-09-22 | 2003-03-04 | Lucent Technologies Inc. | Method for providing quality of service for delay sensitive traffic over IP networks |
US6459681B1 (en) * | 1998-11-13 | 2002-10-01 | Sprint Communications Company L.P. | Method and system for connection admission control |
US7225264B2 (en) * | 1998-11-16 | 2007-05-29 | Softricity, Inc. | Systems and methods for delivering content over a computer network |
US6850965B2 (en) * | 1998-11-17 | 2005-02-01 | Arthur Douglas Allen | Method for connection acceptance and rapid determination of optimal multi-media content delivery over network |
US6411601B1 (en) * | 1998-12-15 | 2002-06-25 | Siemens Information And Communication Networks, Inc. | System and method for securing available communications network resources |
US6826612B1 (en) * | 1999-12-21 | 2004-11-30 | Alcatel Canada Inc. | Method and apparatus for an improved internet group management protocol |
US6920110B2 (en) * | 2001-02-14 | 2005-07-19 | Microsoft Corporation | System and method for transferring data over a network |
US6795445B1 (en) * | 2000-10-27 | 2004-09-21 | Nortel Networks Limited | Hierarchical bandwidth management in multiservice networks |
US6941380B2 (en) * | 2000-12-28 | 2005-09-06 | Nortel Networks Limited | Bandwidth allocation in ethernet networks |
US6636482B2 (en) * | 2001-03-08 | 2003-10-21 | Arris International, Inc. | Method and apparatus for controlling traffic loading of different service levels in a cable data system |
US6584017B2 (en) * | 2001-04-05 | 2003-06-24 | Saifun Semiconductors Ltd. | Method for programming a reference cell |
US6754230B2 (en) * | 2001-08-31 | 2004-06-22 | The Boeing Company | User bandwidth monitor and control management system and method |
US6956857B2 (en) * | 2001-09-24 | 2005-10-18 | Lucent Technologies Inc. | Guaranteed admission and incremental bandwidth allocation in a packet network |
US20030097443A1 (en) * | 2001-11-21 | 2003-05-22 | Richard Gillett | Systems and methods for delivering content over a network |
US7039712B2 (en) * | 2002-10-16 | 2006-05-02 | Microsoft Corporation | Network connection setup procedure for traffic admission control and implicit network bandwidth reservation |
US20040158644A1 (en) * | 2003-02-11 | 2004-08-12 | Magis Networks, Inc. | Method and apparatus for distributed admission control |
-
2004
- 2004-08-05 WO PCT/EP2004/051729 patent/WO2005034463A1/de active Application Filing
- 2004-08-05 EP EP04766434A patent/EP1668860A1/de not_active Ceased
- 2004-08-05 CN CN200480028242.6A patent/CN1860762B/zh not_active Expired - Fee Related
- 2004-08-05 US US10/574,170 patent/US8656005B2/en not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0996264A1 (de) * | 1998-09-24 | 2000-04-26 | Bowne Global Solutions Germany GmbH | Verfahren und Vorrichtung zur Dateienübertragung |
EP1022883A2 (de) * | 1999-01-25 | 2000-07-26 | Siemens Aktiengesellschaft | Verfahren zum Realisieren einer Leistungsmerkmalsteuerung in einem Kommunikationsdatennetz |
WO2001061944A1 (en) * | 2000-02-16 | 2001-08-23 | Microsoft Corporation | System and method for transferring data over a network |
Also Published As
Publication number | Publication date |
---|---|
US20070198627A1 (en) | 2007-08-23 |
EP1668860A1 (de) | 2006-06-14 |
CN1860762B (zh) | 2013-03-27 |
US8656005B2 (en) | 2014-02-18 |
CN1860762A (zh) | 2006-11-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2005034463A1 (de) | Verfahren zur bereitstellung von leistungsmerkmalen bei bedarf | |
DE69933852T2 (de) | Hausnetz- autokonfigurierung | |
DE69731965T2 (de) | Zugriff auf rechnerbetriebsmittel von aussen durch eine firewall | |
DE69934451T2 (de) | Internetteilnehmerprofil | |
EP1488611B1 (de) | Aaa serversystem zur effizienten zugangskontrolle und adresszuordnung | |
DE19842673B4 (de) | Verfahren und Vorrichtung zur Vermittlung bei der Datenkommunikation | |
DE602004004321T2 (de) | Vorrichtung und Verfahren zur Echtzeitbeurteilung einer Netzverwaltungsregel | |
DE69735426T2 (de) | Nachrichtenübertragung in netzwerken bestehend aus unternetzwerken mit verschiedenen namensraümen | |
DE69933312T2 (de) | Auswahlsteuerung eines gateway-unterstützungsknotens | |
DE69827351T2 (de) | Mehrfach-virtuelle Wegsucher | |
DE102005053688A1 (de) | Verfahren und Mechanismus zum Identifizieren eines nicht-verwalteten Schalters in einem Netz | |
EP2324620A1 (de) | Verfahren zur übertragung und aushandlung von netzwerk kontrollierten funktionsdaten zwischen einem client und einem server | |
EP1123622A1 (de) | Verfahren zur steuerung von netzelementen | |
DE60205501T2 (de) | Verwaltung von informationen über subskriptionen der dienstleistungen von dritten | |
EP1872595A1 (de) | Änderungsverfahren der arbeitsweise einer technischen-kommunikationsgruppen-plattform (tkgp) eines telekommunikations-netzes (tk-netzes) | |
DE60038171T2 (de) | Verfahren zur Auswahl von Übertragungsentitäten | |
DE10314597A1 (de) | Verfahren und Anordnungen in einem Telekommunikationsnetz | |
DE102011080676A1 (de) | Konfiguration eines Kommunikationsnetzwerks | |
EP1942633A2 (de) | Verfahren und System für ein Erreichbarkeitsmanagement | |
EP1195945B1 (de) | Client, System und Verfahren zum Netzmanagement in einem Multiserver-Kommunikationsnetz | |
DE60107433T2 (de) | Verfahren und Vorrichtung zur Koordinierung von Telekommunikationsdiensten | |
DE60100685T2 (de) | Verwaltungsverfahren vor einem telekommunikationsnetzwerk und vorrichtung zur durchführung des Verfahrens | |
WO2007118891A1 (de) | Verfahren zum beschränken des zugriffs auf daten von gruppenmitgliedern und gruppenverwaltungsrechner | |
EP2041923A2 (de) | Verfahren und anordnung zur realisierung von zugangsnetzwerken zu einem öffentlichen netzwerk | |
DE602004004786T2 (de) | Zentralisierte Infrastruktur zur Verwaltung drahtloser Kommunikationen |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200480028242.6 Country of ref document: CN |
|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2004766434 Country of ref document: EP |
|
DPEN | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed from 20040101) | ||
WWP | Wipo information: published in national office |
Ref document number: 2004766434 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10574170 Country of ref document: US Ref document number: 2007198627 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 10574170 Country of ref document: US |