System for managing internet connections

[0001] The invention relates to a system for managing internet connections routed across an internet communications network comprising two or more domains, and to a domain manager and a domain boundary controller for supporting the management of internet connections routed across an internet communications network comprising two or more domains.

[0002] The invention is based on the present-day standard management of internet connections on the internet in which the service quality of internet connections is assured by the introduction of new protocols which influence the routing and switching of internet connections in part up to layer 3 of the OSI protocol stack (OSI=Open System Interconnection).

[0003] Service platforms are also known, such as the TINA service platform (TINA=Telecommunications Information Network Architecture) described for example in the article “TINA Service Architecture” by A. Conchon et al., published in the magazine “Alcatel Telecommunication Review”, 1st Quarter 1998.

[0004] In addition to providing an IT platform for telecommunications services, a service architecture and TINA services, TINA also provides a business model. This business model allows different roles supported by the TINA architecture to be allocated to the various participants in the provision of a service. As a result, charge metering of the services provided by the various participants is also supported by the TINA architecture. The TINA platform thus offers a type of marketplace for services and networks.

[0005] The object of the invention is to facilitate the provision of a specific service quality for specific internet connections within an internet communications network.

[0006] This object is achieved by a system according to the invention for managing internet connections, a domain manager according to the invention for supporting the management of internet connections, and a domain boundary controller according to the invention for supporting the management of internet connections.

[0007] Each domain is provided with a domain manager assigned thereto for managing the service quality for internet connections within the particular domain and with one or more domain boundary controllers for monitoring the boundary of the particular domain. The domain manager is designed such that, to assure the service quality of internet connections, it communicates with the domain boundary controllers of the particular domain to which it is assigned and, by transferring service parameters, authorises these domain boundary controllers to permit the establishment and maintenance of special internet connections under special conditions across the boundary of the domain into the domain. The domain boundary controllers are in each case designed such that they monitor the establishment of internet connections across the boundary of their particular domain into their particular domain and permit the establishment and maintenance of internet connections across the boundary of their domain into their domain only for those special internet connections, and under those special conditions, for which they have been authorised by the domain manager assigned to their domain.

[0008] This concept is not limited to internet as network technology but can be applied for any connetionless network technology (i.e. X.25).

[0009] The advantage of the invention consists in that it facilitates an effective and comprehensive assurance of service quality for internet connections. The invention enables service quality for internet connections to be introduced on a broad basis on the internet without having to accept the disadvantage of allocating all the available resources for this purpose.

[0010] Moreover, the distributed architecture of the system according to the invention facilitates an improvement in the average service quality available for internet connections by optimising the utilization of resources while nevertheless minimising the computation- and coordination outlay required for this purpose.

[0011] Advantageous developments of the invention are described in the sub-claims.

[0012] It is particularly advantageous to implement the domain manager as a TINA component which interacts with other TINA components on a TINA platform. If both ends of an internet connection are assigned the roles of parties in a TINA service session initiating the provision of the resources for this connection on the internet, it is possible for all the users of an internet connection to be debited with the charges incurred in the overall system for the service quality which they have requested.

[0013] It is also advantageous to initiate the provision of a specific service quality for a specific internet connection by means of a TINA service session assigned to this internet connection. It is also advantageous to manage the infrastructure and charge metering of the allocation of resources by means of the TINA business model.

[0014] It is also advantageous that the domain manager manages all the resources required by internet connections within the domain to which it is assigned. This permits the dynamic assignment of network resources to users, as well as the implementation of security checks and charge metering for these resources.

[0015] It is also advantageous that other TMN tasks (TMN=Telecommunication Network Management) than configuration and accounting management can be performed by this concept. Such tasks are for example fault management, performance management and security management.

P-0016[0016] In the following the invention will be explained by way of example in the form of a plurality of exemplary embodiments making reference to the attached drawings in which:

P-0017[0017]FIG. 1 is a block circuit diagram of an internet communications network with a system according to the invention for managing internet connections;

P-0018[0018]FIG. 2 is a more detailed block circuit diagram of the system according to the invention for managing internet connections as shown in FIG. 1;

P-0019[0019]FIG. 3 is a more detailed block circuit diagram of a portion of the system according to the invention for managing internet connections as shown in FIG. 1;

P-0020[0020]FIG. 4 is a functional diagram of a portion of the system according to the invention for managing internet connections as shown in FIG. 1;

P-0021[0021]FIG. 5 is a functional diagram of a portion of the system according to the invention for managing internet connections as shown in FIG. 1.

P-0022[0022]FIG. 1 illustrates an internet communications network <b>10</b> and a system <b>1</b> for managing internet connections of the components of the system <b>1</b>, FIG. 1 shows four domain managers <b>11</b> to <b>14</b> (IP LNC=IP Layer Network Coordinator).

P-0023[0023] The internet communications network <b>10</b> is formed by a plurality of interconnected physical communications networks using an IP protocol (IP=Internet Protocol) as common layer 3 protocol.

P-0024[0024] The internet communications network <b>10</b> illustrated in FIG. 1 comprises, for example, four domains <b>21</b> to <b>24</b> each constituting a logic portion of the internet communications network <b>10</b>. Advantageously, the domains <b>21</b> to <b>24</b> are each formed by a logic sub-network of the communications network <b>10</b> which is managed by a network manager or assigned to a network operator.

P-0025[0025] Each of the domains <b>21</b> to <b>24</b> is assigned a respective domain manager which manages the provision of service quality for internet connections within the particular domain. The domain managers <b>11</b>, <b>12</b>, <b>13</b> and <b>14</b> are thus in each case assigned to the domains <b>21</b> to <b>24</b>.

P-0026[0026] The domain managers <b>11</b>, <b>12</b>, <b>13</b>, and <b>14</b> are each formed by one or more computer(s) which are interconnected via a computer network and whose software platform runs applications programs which provide and control the functions, to be described in the following, of a domain manager. It is of course also possible for the domain managers <b>11</b>, <b>12</b>, <b>13</b> and <b>14</b> to in each case consist of a virtual software component formed by one or more applications program(s). These virtual software components can then run, together with other software components which for example perform network management functions, on a common hardware platform or distributed between a plurality of computers. A plurality of software components, each of which represents a domain manager assigned to a different domain, can also run on a common hardware platform.

P-0027[0027] The domain managers <b>11</b>, <b>12</b>, <b>13</b> and <b>14</b> in each case communicate with one another via identical, standardized reference points <b>31</b> to <b>33</b> (IP LNGrf Reference Point=IP Layer Network Federation Reference Point). The reference points <b>31</b> to <b>33</b> here describe all the interfaces and the information exchange necessary between adjacent domain managers for the management of common internet connections and the initiation of internet connections across the domain boundaries. The domain managers <b>11</b>, <b>12</b>, <b>13</b> and <b>14</b> thus communicate with one another in accordance with the reference points <b>31</b> to <b>33</b> using one or more first protocol(s).

P-0028[0028] The detailed construction and functioning of the system <b>1</b> for managing internet connections will now be explained by way of an example on the basis of the domain <b>22</b> making reference to FIG. 2.

P-0029[0029]FIG. 2 shows the domains <b>21</b> to <b>23</b>, the domain manager <b>12</b> and two domain boundary controllers (DBCs) <b>41</b> and <b>42</b> which likewise form part of the system <b>1</b> for managing internet connections.

P-0030[0030] The domain boundary controllers <b>41</b> and <b>42</b> are assigned to the domain <b>22</b> and monitor the domain boundary of this domain. The number of domain boundary controllers has been selected by way of an example in FIG. 2. The domain boundary controllers <b>41</b> and <b>42</b> are each formed by one or more, distributed, physical as well as logic units(s). The software platform of these units runs applications programs which provide the functions, to be described in the following, of the domain boundary controllers <b>41</b> and <b>42</b> by controlling the peripheral assemblies of the units.

P-0031[0031] The domain manager <b>12</b> in each case communicates with the domain boundary controllers <b>41</b> and <b>42</b> via identical standardized reference points <b>51</b> and <b>52</b> (IP LNW Resource Adapter=IP Layer Network Resource Adapter). The reference points <b>31</b> to <b>33</b> here describe all the interfaces and the information exchange possible between a domain manager and resources of the domain. The communication between the domain manager <b>12</b> and other resources of the domain <b>22</b> can thus also take place via such a reference point. The domain manager <b>12</b> therefore communicates with resources of the domain <b>22</b>, for example the domain boundary controllers <b>41</b> and <b>42</b>, in accordance with the reference points <b>51</b> and <b>52</b> using one or more second protocol(s)

P-0032[0032] The domain manager <b>12</b> serves to support the management of internet connections routed across the internet communications network <b>10</b>. Here the domain manager <b>12</b> manages the service quality of internet connections within the domain <b>22</b>, which it is assigned, of the internet communications network <b>10</b>.

P-0033[0033] It is also advantageous that the domain manager <b>12</b> communicates with the domain managers <b>11</b> and <b>13</b> of the adjacent domains <b>21</b> and <b>23</b> and exchanges information therewith for the management of common internet connections which are routed both through the domain <b>22</b> of the domain manager <b>12</b> and through the domains <b>21</b> and <b>23</b> of the in each case adjacent domain managers <b>11</b> and <b>13</b>. In that the domain manager <b>12</b> communicates with the domain manager of an adjacent domain, for example with the domain manager <b>13</b> of the domain <b>23</b>, it can initiate the establishment of an internet connection across the domain boundary into the domain of this domain manager.

P-0034[0034] If we only consider IP packets up till layer 3—hence not taking into account any session or application related information—a connection is defined as a set of header parameters of IP packets. For establishment of a connection we have to configure the domain boundary controllers of one or several domains to allow IP packets belonging to the same connection to pass through. Due to the connectionless nature of IP it is however not certain whether all these packages will follow the exact configured route. I.e. establishing an internet connection in this context means that all the domain boundary controllers are configured in such a way that whatever route the individual IP packages (within the quality of service and security constrains of the connection of course) follow they are recognized as belonging to the connection and are treated according to the quality of service specification of the connection.

P-0035[0035] To assure the service quality of internet connections, the domain manager <b>12</b> communicates with the domain boundary controllers <b>41</b> and <b>42</b> of the domain <b>22</b> which it is assigned. By transferring service parameters, the domain manager <b>12</b> authorises the domain boundary controllers <b>41</b> and <b>42</b> to permit the establishment and maintenance of special internet connections under special conditions across the boundary of the domain <b>22</b> into the domain <b>22</b>. The service parameters transferred from the domain manager <b>12</b> to the domain controllers <b>41</b> and <b>42</b> here specify the conditions under which a special internet connection can be established and maintained across the boundary of the domain <b>22</b> into the domain <b>22</b>.

P-0036[0036] Here an internet connection is specified by the domain manager <b>21</b> by means of its regular IP properties (e.g. source IP, sink IP, protocol, source port, sink port). However it is also possible for internet connections to be additionally specified by higher-level information, for example by their specific URL or MIME type. By means of such additional parameters, which serve for example to configure higher-level resources, such as routers, firewalls or proxies, such resources can be configured by the domain manager <b>12</b> for the internet connection specified by these parameters.

P-0037[0037] It is also advantageous that, in addition to controlling the domain boundary controllers <b>41</b> and <b>42</b>, the domain manager <b>12</b> also manages if possible all of the resources required by internet connections within the domain <b>22</b> which it is assigned. The domain manager <b>12</b> controls the allocation of these resources, which it manages, to internet connections in accordance with the service quality agreed upon for the particular internet connection. This provides the domain manager <b>12</b> with an additional means of assuring service quality for these internet connections in the domain <b>22</b> which it is assigned.

P-0038[0038] It is also advantageous that the domain manager <b>12</b> communicates by means of a first protocol with the other domain managers <b>11</b>, <b>13</b> and <b>14</b> assigned to the other domains and by means of a second, different type of protocol with the domain boundary controllers <b>41</b> and <b>42</b> of the domain <b>22</b> which it is assigned.

P-0039[0039] The domain boundary controllers <b>41</b> and <b>42</b> serve to support the management of internet connections routed across the internet communications network <b>10</b>. The domain boundary controllers <b>41</b> and <b>42</b> in each case monitor the domain boundary of the domain <b>22</b>, which they are assigned, of the internet communications network <b>10</b>. Here the domain boundary controller <b>41</b> monitors the domain boundary between the domain <b>22</b> and the domain <b>21</b>. The domain boundary controller <b>42</b> monitors the domain boundary between the domain <b>22</b> and the domain <b>23</b>. On the other hand the domain boundary controllers <b>41</b> and <b>42</b> communicate with the domain manager <b>12</b> of the assigned domain <b>22</b> which manages the service quality of internet connections within the domain <b>22</b> which they are assigned. The domain boundary controllers <b>41</b> and <b>42</b> monitor the establishment of internet connections across the boundary of their assigned domain <b>22</b> into the domain <b>22</b>. The domain boundary controller <b>41</b> here monitors the establishment of internet connections from the domain <b>21</b> into the domain <b>22</b> and the domain boundary controller <b>41</b> monitors the establishment of internet connections from the domain <b>23</b> into the domain <b>22</b>. The domain boundary controllers <b>41</b> and <b>42</b> also permit the establishment and maintenance of internet connections across the boundary of their assigned domain <b>22</b> into the domain <b>22</b> only for those special internet connections, and under those special conditions, for which they have been authorised by the domain manager <b>12</b> of the assigned domain <b>22</b>.

P-0040[0040] The domain boundary controllers <b>41</b> and <b>42</b> have two main functions within the domain <b>22</b>: firstly as policing agent and secondly as traffic shaper. The service parameters transferred from the domain manager <b>12</b> to the domain boundary controllers <b>41</b> and <b>41</b> specify the conditions under which a special internet connection can be established and maintained across the boundary of the domain <b>22</b> into the domain <b>22</b>. In such conditions, these service parameters describe how the domain boundary controllers <b>41</b> and <b>42</b> are to handle a special internet connection.

P-0041[0041] The service parameters can specify for example the following policing functions for an internet connection, which are then executed by the domain boundary controllers <b>41</b> and <b>42</b> for these internet connections:

P-0042[0042] rejection of packets assigned to a specific internet connection when specific limit values are exceeded;

P-0043[0043] labelling of all or specific packets of a connection to facilitate later differentiation of these packets;

P-0044[0044] rejection of all packets not assigned to an internet connection forming part of a group of internet connections which can cross the boundary of the domain <b>22</b>.

P-0045[0045] In addition, the domain boundary controllers <b>41</b> and <b>42</b> can comprise components which ensure a special service quality for special internet connections in accordance with the service parameters transferred from the domain boundary manager <b>12</b>.

P-0046[0046] Service quality in this sense can constitute a special traffic quality defined by the service parameters; for example the service parameters define a specified constant bit rate, maximum delay and jitter.

P-0047[0047] To ensure this service quality, the domain boundary controllers <b>41</b> and <b>42</b> can influence the memory management of the buffer memories which, within the domain <b>22</b>, serve for the buffer storage of data packets assigned to internet connections. It is also possible for the domain boundary controllers <b>41</b> and <b>42</b> themselves to be provided with such buffer memories serving for this purpose. The domain boundary controllers <b>41</b> and <b>42</b> can control the service quality of special internet connections by accessing the memory management of these buffer memories, in particular the control algorithms of the queues and the control priority of the packets of the queues.

P-0048[0048] Service quality in this sense can also constitute a special quality of security specified by the service parameters. For this purpose the domain boundary controllers <b>41</b> and <b>42</b> make available security functions which assure different security levels in the domain <b>22</b> for different internet connections in accordance with the service parameters.

P-0049[0049] An alternative construction of the domain boundary manager <b>12</b> will now be described with reference to FIG. 3.

P-0050[0050]FIG. 3 shows the domain manager <b>12</b>, the sub-domain managers <b>121</b> to <b>124</b>, the domain <b>22</b> and three sub-domains <b>61</b> to <b>63</b>.

P-0051[0051] The domain manager <b>12</b> can also be constructed from a plurality of hierarchically structured sub-domain managers. FIG. 3 shows such an architecture by way of example.

P-0052[0052] The architecture illustrated in FIG. 3 consists of two stages. The domain <b>22</b> is split into the sub-domains <b>61</b> to <b>63</b>, each of which is assigned a sub-domain manager, namely the sub-domain managers <b>122</b>, <b>123</b> and <b>124</b>. The sub-domain managers <b>122</b> to <b>124</b> themselves delegate responsibility to the sub-domain manager <b>121</b> which oversees the entire domain <b>22</b>.

P-0053[0053] It is of course also possible for the domain manager to be constructed from a hierarchy of sub-domain managers consisting of more than two stages.

P-0054[0054] Sub-domain managers thus communicate on the one hand with the subordinate sub-domain managers which manage the sub-domains collectively forming their particular sub-domain. They also communicate with adjacent sub-domain managers to negotiate about resources at common sub-domain boundaries. They also communicate with network elements of their assigned sub-domain to ensure the service quality of specific internet connections or a group of internet connections within the particular sub-network by means of the configuration of these network elements.

P-0055[0055]FIG. 4 illustrates how one of the smallest elements of an IP communications network, an IP LAN (LAN=Local Area Network) is managed by a sub-domain manager to ensure the service quality of internet connections within the sub-network.

P-0056[0056]FIG. 4 illustrates a sub-network <b>101</b> of the internet communications network <b>10</b>, three network elements <b>131</b> to <b>133</b> with the assigned IP stacks <b>141</b> to <b>143</b>, and the sub-domain manager <b>122</b>.

P-0057[0057] The sub-network <b>101</b> is an IP LAN. The IP stacks <b>141</b> to <b>143</b> of the network elements <b>131</b> to <b>133</b> are modified in such manner that they can be controlled by the sub-domain manager <b>122</b>. The sub-domain manager <b>122</b> can thus change the queues and priorities of the queues from or to specified IP addresses, protocols and ports. This control can take place for example via a CORBA interface (CORBA=Common Object Request Broker Architecture).

P-0058[0058] The provision of the service quality for an end-to-end internet connection in a system according to the invention as shown in FIG. 1 will now be explained making reference to FIG. 5.

P-0059[0059]FIG. 5 illustrates the internet communications network <b>10</b>, three terminals <b>211</b> to <b>213</b> connected via the internet communications network <b>10</b>, and the system <b>1</b> for managing internet connections. The internet communications network <b>10</b> is modelled as a TINA layer network using IP as network technology.

P-0060[0060] The system <b>1</b> is based on a TINA platform. However it is also possible for the system to be based on a a different platform or a different type of SW bus, for example a DCOM platform.

P-0061[0061] Of the components of the system <b>1</b>, FIG. 5 shows the domain manager <b>12</b>, three terminal layer adapters (TLAs) <b>221</b> to <b>223</b>, three terminal communication session managers (TCSMs) <b>231</b> to <b>233</b>, a communication session manager (CSM) <b>250</b> and a connection coordinator (CC) <b>240</b>, which communicate with one another.

P-0062[0062] The domain manager <b>12</b> thus fulfils the function of a component within a TINA architecture, which communicates with other components, the terminal layer adapters <b>221</b>, <b>222</b>, <b>223</b> and the connection coordinator <b>240</b>, in accordance with the TINA architecture to provide the service quality for internet connections.

P-0063[0063] The terminal communication session managers <b>231</b> to <b>233</b> manage the resources within the respective terminals <b>211</b>, <b>212</b> and <b>213</b>. They communicate with and control the local hardware managers. They analyze the available resources and communicate about these resources with the service application and the communication session manager <b>250</b>. The service application can inform the communication session manager <b>250</b> of the end-points of an internet connection on a very abstract level, for example can provide the communication session manager <b>250</b> with a high quality video source as end-point. This abstract end-point is associated with other end-points at the service level to form an internet connection.

P-0064[0064] The communication session manager <b>250</b> manages a communication session. It thus forms the central contact point of a service which provides for the establishment of an end-to-end internet connection. An end-to-end internet connection also includes the Layers 4 to 7 of the OSI stack. The main function of the communication session manager <b>250</b> is making sure these match for all application level end points. After that it will retrieve to which network end point these protocols stacks can be hooked up within the terminal. The setup of the connection between the terminals' network end points is delegated to the connection coordinator <b>240</b>. The communication session manager <b>250</b> makes a request to the connection coordinator <b>240</b> for the establishment of the internet connection at the level of a communications network connection.

P-0065[0065] The terminal layer adapters <b>221</b> to <b>223</b> manage the endpoints of the internet connection within the terminals <b>211</b>, <b>212</b> and <b>213</b>.

P-0066[0066] The domain manager <b>12</b> is responsible for the establishment of an internet connection through its particular domain. For this purpose it communicates with the end-points of an internet connection, thus with the terminal layer adapters <b>221</b> to <b>223</b> when the terminals assigned to these end-points are assigned to its domain <b>22</b>. It also communicates with the adjacent domain managers when it initiates the establishment of an internet connection through their particular domain. The domain manager <b>12</b> shown in FIG. 2 also communicates with the resources of its domain <b>22</b> in order to ensure the service quality of the internet connection within its domain.