Method and system for managing remote clients in a network constituted by a central server which is linked to remote clients
30 claims: 6 independent, 24 dependent
- 1Verfahren, umfassend:Empfangen einer Nachricht auf einem Client ( 12 ) von einem Server ( 10 ), welche an den Client ( 12 ) adressiert ist;und Steuern des zeitlichen Ablaufs einer Datenladesitzung basierend auf der Nachricht.
- 2Verfahren nach Anspruch 1, welches ferner umfaßt:Zuordnen einer individuellen Kennung an die Clients aufweisend eine Gruppe von Clients, welche den Client ( 12 ) umfassen;Zuordnen einer Gruppenkennung an eine Untergruppe von Clients innerhalb der Gruppe von Clients;und Ermöglichen, daß der Client ( 12 ) in der Gruppe bestimmt, ob eine Nachricht an den Client ( 12 ) oder an die Untergruppe gesendet wird.
- 3Verfahren nach Anspruch 2, bei welchem eine Nachricht an einen Client ( 12 ) in einem unidirektionalen Übertragungssystem gesendet wird.
- 4Verfahren nach Anspruch 1, bei welchem eine Nachricht empfangen wird, welche eine Kennung enthält, die eine auf einer Speichereinrichtung ( 43 ) durchzuführende Aufgabe spezifiziert.
- 5Verfahren nach Anspruch 4, bei welchem eine Nachricht empfangen wird, welche eine Kennung enthält, die eine Änderung an einer Partition auf der Speichereinrichtung ( 43 ) angibt.
- 6Verfahren nach Anspruch 1, bei welchem eine Kennung in einer Nachricht angeordnet wird, welche einen Agenten ( 44 , 45 , 46 , 48 ) am Client ( 12 ) zum Bearbeiten der Nachricht angibt, und die Nachricht an den Agenten ( 44 , 45 , 46 , 48 ) übertragen wird.
- 7Verfahren nach Anspruch 6, bei welchem ermöglicht wird, daß der Agent ( 44 , 45 , 46 , 48 ) die Daten an den Server ( 10 ) über einen Rückkanal ( 47 ) ladet.
- 8Verfahren nach Anspruch 6, bei welchem ferner eine spezifizierte Zeit von der Nachricht gewonnen wird und die Daten zu der speziellen Zeit geladen werden.
- 9Verfahren nach Anspruch 1, bei welchem von der Nachricht eine Kennung gewonnen wird, welche die auf den Server ( 10 ) zu ladende Information spezifiziert, und die spezifizierte Nachricht auf den Server ( 10 ) geladen wird.
- 10Verfahren nach Anspruch 9, bei welchem die Nachricht eine Serverkennung enthält und die Daten an den gekennzeichneten Server geladen werden.
- 11Computerprogramm, welches Befehle aufweist, die veranlassen, daß ein prozessorbasiertes System:eine Nachricht von einem Server ( 10 ) empfängt, welche an das System adressiert ist;den Ablauf des Ladens von Informationen von dem System an den Server basierend auf der Nachricht zeitlich steuert.
- 12Computerprogramm nach Anspruch 11, welches ferner Befehle aufweist, die veranlassen, daß ein prozessorbasiertes System:eine individuelle Kennung an jeden der Clients, welche eine Gruppe von Clients einschließlich des Systems umfassen, zuordnet;eine Gruppenkennung an eine Untergruppe von Clients innerhalb der Gruppe von Clients zuordnet;und ermöglicht, daß das System bestimmt, ob eine Nachricht an das System oder die Untergruppe gesendet wird.
- 13Computerprogramm nach Anspruch 12, welches ferner Befehle aufweist, die veranlassen, daß das prozessorbasierte System eine Nachricht an einen Client ( 12 ) in einem unidirektionalen Übertragungssystem sendet.
- 14Computerprogramm nach Anspruch 11, welches ferner Befehle aufweist, die veranlassen, daß das prozessorbasierte System einen Befehl innerhalb einer Nachricht dekodiert, um die Speicherung der Information auf einer Speichereinrichtung ( 43 ) zu verändern.
- 15Computerprogramm nach Anspruch 11, welches ferner Befehle aufweist, die veranlassen, daß das prozessorbasierte System eine Kennung innerhalb der Nachricht anordnet, welche einen Agent ( 44 , 45 , 46 , 48 ) im System spezifiziert, um die Nachricht zu bearbeiten, und die Nachricht an den Agenten ( 44 , 45 , 46 , 48 ) überträgt.
- 16Computerprogramm nach Anspruch 15, welches ferner Befehle aufweist, die veranlassen, daß das prozessorbasierte System die Daten an den Server ( 10 ) über einen Rückkanal ( 47 ) ladet.
- 17Computerprogramm nach Anspruch 15, welches ferner Befehle aufweist, die veranlassen, daß das prozessorbasierte System eine spezifizierte Zeit aus der Nachricht ableitet und die Daten zu der speziellen Zeit ladet.
- 18Computerprogramm nach Anspruch 11, welches ferner Befehle aufweist, die veranlassen, daß das prozessorbasierte System von der Nachricht eine Kennung ableitet, welche die auf den Server ( 10 ) zu ladende Information spezifiziert, und die spezifizierte Information auf den Server ( 10 ) ladet.
- 19Computerprogramm nach Anspruch 18, welches ferner Befehle aufweist, die veranlassen, daß das prozessorbasierte System die Daten an einen in der Nachricht identifizierten Server ( 21 , 16 ) ladet.
- 20System, mit:einer prozessorbasierten Einrichtung;und einem Speicher ( 43 ), welcher Befehle speichert, die ermöglichen, daß die prozessorbasierte Einrichtung eine Nachricht von einem Server ( 10 ) empfängt, welche an die prozessorbasierte Einrichtung andressiert ist, und den Ablauf des Ladens von Informationen an den Server ( 10 ) basierend auf der Nachricht zeitlich steuert.
- 21System nach Anspruch 20, bei welchem der Speicher ( 43 ) Befehle speichert, die ermöglichen, daß die Einrichtung eine Gruppenkennung in einer Nachricht vergleicht, um zu bestimmen, ob die Einrichtung sich innerhalb der durch den Server ( 10 ) adressierten Gruppe befindet.
- 22System nach Anspruch 20, bei welchem der Speicher ( 43 ) Befehle speichert, die ermöglichen, daß die prozessorbasierte Einrichtung eine Kennung innerhalb der Nachricht anordnet, welche einen Agenten ( 44 , 45 , 46 , 48 ) in der Einrichtung spezifiziert, um die Nachricht zu behandeln, und die Nachricht an den Agenten ( 44 , 45 , 46 , 48 ) überträgt.
- 23Verfahren, welches umfaßt:Übertragen einer Nachricht an einen Client ( 12 );und Steuern des zeitlichen Ablaufs des Ladens von Informationen auf den Client ( 12 ) basierend auf der Nachricht.
- 24Verfahren nach Anspruch 23, bei welchem ferner Befehle gespeichert werden, die ermöglichen, daß das prozessorbasierte System eine Datenladung über einen Rückkanal von einem Client ( 12 ) empfängt.
- 25Verfahren nach Anspruch 24, bei welchem ferner eine Zeitangabe in der Nachricht übertragen wird, und eine Datenladung von einem Client ( 12 ) zu der spezifizierten Zeit empfangen wird.
- 26Computerprogramm, welches Befehle aufweist, die veranlassen, daß ein prozessorbasiertes System:eine Nachricht an einen Client ( 12 ) überträgt;und den Ablauf des Ladens von Information in das System basierend auf der Nachricht zeitlich steuert.
- 27Computerprogramm nach Anspruch 26, welches ferner Befehle aufweist, die veranlassen, daß das prozessorbasierte System eine Information in der Nachricht überträgt, die eine Zeit für das Laden von Information von dem Client ( 12 ) spezifiziert.
- 28Computerprogramm nach Anspruch 26, welches ferner Befehle aufweist, die veranlassen, daß das prozessorbasierte System eine Nachricht überträgt, die die vom Client ( 12 ) zu ladende Information spezifiziert.
- 29System, mit:einer prozessorbasierten Einrichtung;und einem Speicher ( 25 ), welcher Befehle speichert, die ermöglichen, daß die prozessorbasierte Einrichtung eine Nachricht an einen Client ( 12 ) überträgt und den Ablauf des Ladens von Information am Client ( 12 ) in das System basierend auf der Nachricht zeitlich steuert.
- 30System nach Anspruch 29, bei welchem der Speicher ( 25 ) Befehle speichert, die ermöglichen, daß die prozessorbasierte Einrichtung spezifiziert, wie die Information von dem Client ( 12 ) an das System bereitgestellt wird.
Independent claims30
66 paragraphs, as filed
background
0001These Invention relates generally to the exchange of information in a network.
0002On Multicast network enables that messages is sent to a target group of clients, which is a subset constitute the entirety of the clients on the network. In general, a multicasting or a multicast carried out by For example, in a header the addresses of all concerned contained clients that are addressed.
0003On Broadcast network operator may have a server or head-end unit using a multicast network to groups or individual broadcast receiver platforms to control trigger with the goal of network management sessions. These Sessions (session) can serve to network management information into the server or the head-end unit to load. This allows the Network Operator exchanging network management information in a very scalable Fashion administered.
0004<patcit><text>US 5978845 A</text></patcit> to the Example discloses a system to connect more than one SNMP agent a UDP / IP interface allowed. For this, an SNMP forwarding between the UDP / IP interface and the agents connected, the incoming messages to the Contents of a routing table is divided to the individual agents. when all agents who have received a portion of the message, a returned answer value have added forwarding the reply to a single message together and send them back to the server. The system exchanges messages and queries from that are used to manage the system. The procedure is the division a message to the various agents and the subsequent joining of the individual responses to a reply message through the SNMP forwarding. This splitting is not specified by the message. Rather, the routing table to which agent gets what part of the message for processing. In the Message itself is not defined how and when any particular Message to which agent is to be transferred.
0005Louis, S., among others: Management Issues for High-Performance Storage Systems, IEEE, 1995, S.336-348, treated management tasks that should satisfy a memory system, in general. How these tasks are carried out, is the example a "HPSS project" more specific explains but not performed accurately. It can be seen for example from the chapter "SSM operation and information flow" that Messages between data servers, management servers, and other Servers to be replaced. Since it is a storage system, can also take place an exchange of data. However, there is nothing about scheduling any kind to learn; and also received on a message based management or management of meetings (no matter what Art) is not mentioned.
0006Hein, Mathias, Griffiths, David: SNMP Simple Network Management Protocol Version 2, 1st edition, Bonn, International Thomson Publishing GmbH, 1994 S. 339-340, employed with a network management protocol.
0007<patcit><text>US 5892912 A</text></patcit> deals with the use of network protocol agents.
0008It there is a need for solutions to the exchange of information between clients and a server, a head-end unit or a broadcast to Netzwerkkooperator improve.
Summary of the Invention
0009After a first aspect the invention provides a method according to the Subject of the independent Claim 1 ready. A second aspect relates to a computer program after the subject of the independent Claim 11. A third aspect relates to a system according to the subject the independent Claim 20. In a further aspect, the invention provides a Method according to independent Claim 23 ready. Another aspect of the invention is directed to a computer program according to claim 26 and a system according to claim 29. Other aspects and embodiments the invention will be apparent from the dependent claims, the following description and the drawings.
Brief Description of Drawings
0010<figref idrefs="S26">1</figref> is a schematic view of an embodiment of the present Invention;
0011<figref idrefs="S27">2</figref> is a flow chart one on the in <figref idrefs="S26">1</figref> shown Client resident Software, in accordance with an embodiment of the present invention;
0012<figref idrefs="S28">3</figref> is a flow chart a resident on the server or head-end unit software, according to an embodiment the present invention;
0013<figref idrefs="S29">4</figref> is a flow chart one on the in <figref idrefs="S26">1</figref> gezeig th client resident Software, enttalking to another embodiment of the present Invention;
0014<figref idrefs="S30">5</figref> is a flow chart a resident on the server or head-end unit software, According to a further embodiment the present invention;
0015<figref idrefs="S31">6</figref> is a flow chart one on the in <figref idrefs="S26">1</figref> shown Client resident Software, in accordance with another embodiment of the present Invention; and
0016<figref idrefs="S32">7</figref> is a flow chart a resident on the server or head-end unit software, According to a further embodiment of the present invention.
0017According to <figref idrefs="S26">1</figref> can a network at least one server, a head-end unit or a network operator <figref>10</figref> and a plurality of clients, <figref>12</figref> (in which only one is shown having). The server<figref>10</figref> can with a plurality of clients (including the client <figref>12</figref>) A Verteilungssy system be coupled, which on a wired System, a wireless or a broadcast system (broadcast system) based. examples for Such networks include television broadcasting networks, such as digital Videobraodcastsysteme.
0018In one embodiment, of the present invention, the server <figref>10</figref> with clients <figref>12</figref> a transmission device <figref>14</figref> communicate. The transfer means <figref>14</figref> can constructed in accordance with an analog or digital broadcast system be. As an example, the transmission device<figref>14</figref> in accordance with the Digital Video Broadcast (DVB), network-independent protocol, ETS 300 802, November 1997 available by the European Telecommunications Standards Institute (ETS), Valbonne, France be constructed. The transfer means can be for example a satellite, cable or radio waves broadcast system.
0019In accordance with embodiments the present invention detects the client <figref>12</figref> News, which individually to that client <figref>12</figref> from the server <figref>10</figref> or in some embodiments, from other clients <figref>12</figref> be sent. bandwidth can be maintained by messages to a group of clients be addressed without the is necessary within a header, the individual identification mark of each of the large Number insert of addressed clients.
0020In addition, the client <figref>12</figref> one or more addressable agents <figref>44</figref>. <figref>45</figref>. <figref>46</figref> and <figref>48</figref> exhibit, which independently thereof through distant units, such as the server <figref>10</figref>addressed can be. By further addressable agents <figref>44</figref>. <figref>45</figref>. <figref>46</figref> and <figref>48</figref> in a particular client <figref>12</figref> Provided, Mail, which are specialized or which require special handling, are addressed to specific agents, which the client <figref>12</figref> to the perform are an appropriate handling resident.
0021Of the server <figref>10</figref> can a Netzwerkmanagementbefehls- and -steuerungsserver <figref>16</figref> exhibit. Of the server <figref>16</figref> is used to collect data from the client <figref>12</figref> to manage. The server<figref>16</figref> transmits messages which a unique service identifier contained (z. B. Dienst_ID = 0 × 02). The server <figref>10</figref> can also a Schnellnachrichten- or short message service (SMS) server <figref>18</figref> exhibit, which also transmits messages a unique service identifier contained (z. B. Dienst_ID = 0 × 04).
0022In addition, a client disk management server <figref>20</figref> be provided. The client disk management server <figref>20</figref> can transmit messages, the one or more unique identifiers services included (eg. B. Dienst_ID = 0 × 01). In some cases A variety of messages through the client disk management server <figref>20</figref> generated be to desired Functions on a storage device or disk drive trigger the client. For example, different service identifiers are used for commands For example, to create partitions, delete partitions or to modify partitions.
0023On Data management session control server <figref>21</figref> can for handling to be responsible of loading a data set, which on a client via an available Back channel connection <figref>47</figref> clearly is identifiable. This is a useful capability, which enables that the Network operator to obtain data and the scalability the associated server can manage. An identifier for a unidirectional message service type and a unidirectional message can for a data management session control (Data Management Session Control (DMSC)) are used to data management meetings for groups manage clients or individual clients. This group management is inherently through a unidirectional transmission service through a strategic Mapping of client identifiers for all broadcast receiving clients on the network support, which by the server <figref>10</figref> to get managed.
0024Of the Data management session control server <figref>21</figref> transmits messages which one or more unique identifiers services include (z. B. Dienst_ID = 0 × 03). The server <figref>21</figref> generates a DMSC message data structure and transmits a information and data to the Unidirektionalübertragungsserver <figref>22</figref>. such as private application data and data size, unique client identifier, a group flag, which is a Boolean variable indicating whether the Client identifier a group mask or an individual client identifier is a service identifier value the DMSC service and a message identifier for private use.
0025According to a embodiment of the present invention, the server <figref>10</figref> a unidirectional transmission system to implement. In a unidirectional transmission system, the server<figref>10</figref> news transmit to a plurality of clients, which can give an answer in any case. An example of such Network is a Direct-to-Home (DTH) broadcast network, which coincides with the DVB protocol. The network can be used as examples of a connection-oriented communication protocol use or a connectionless real-time communication protocol. There are many applications for unidirectional data transfer from a server to a client, such as by way of example a high-speed data transmission, Issuing of orders and control, as well as notification and display. In other cases, be the network a bidirectional network, eg. as an Internet Protocol (IP) multicast backbone.
0026In one embodiment, of the present invention, the server <figref>10</figref> a Unidirektionalübertragungsserver (UMS) <figref>22</figref> exhibit, which with the servers <figref>16</figref>. <figref>18</figref>. <figref>20</figref> and <figref>21</figref> connected is to generate messages in an appropriate format. The by the UMS server <figref>22</figref> transmitted messages Mail included, which originally by one of the servers <figref>16</figref>. <figref>20</figref>. <figref>18</figref> or <figref>21</figref> generated were. The UMS server<figref>22</figref> may then with an internet protocol multicast module <figref>24</figref> coupled are that the messages in an appropriate multicast protocol format arranges. After all A DVB Multiprotokollkapselung (multiprotocol encapsulation (MPE)) <figref>26</figref> with the Internet Protoll multicast module <figref>24</figref> coupled. The MPE's DVB specification for data broadcasting (EN 301 192) and as Spe fication for Service Information (SI) in DVB systems (EN 300 468 VI. 3. 1 1998-2) described, which are both available from the ETS. The output of DVB-MPE <figref>26</figref> and a DVB Service Information (SI) generator <figref>28</figref> are with the transfer device <figref>14</figref> coupled. A service information are digital data transmission system which, Content and sequence control (scheduling) / timing of broadcast data streams describing.
0027At the client <figref>12</figref> is the current from the generator DVB-SI <figref>28</figref> With a DVB-SI receiver <figref>40</figref> and a Service acquisition module <figref>38</figref> connected. The service acquisition module<figref>38</figref> determined a program identifier (program identifier (PID) and delivers them to a DVB demultiplexer <figref>32</figref>, A tuner<figref>30</figref> can the client <figref>12</figref> Vote on an appropriate channel, which the determined program identifier corresponds.
0028The Message from the DVB MPE <figref>26</figref> is a DVB MPE receiver <figref>42</figref> provided. Recipient <figref>42</figref> communicates with an IP multicast module <figref>40</figref> and a Unidirektionalübertragungsserver <figref>38</figref>, The server <figref>38</figref> down the message on to determine whether a service identifier in said data stream is included. If this is the case, the message is to a appropriate agent forwarded, is which intended to receive messages with specific service codes.
0029On Disk Management Agent <figref>44</figref> can with a disk drive controller <figref>47</figref> connected be, in turn, to a memory device <figref>43</figref> connected which may be a hard drive, for example. The Disk Management Agent<figref>44</figref> can as a message recipient by the client disk management server <figref>20</figref> addressed be. The Disk Management Agent<figref>44</figref> can cause operations which by the controller <figref>47</figref> be undertaken, which in turn the use of the memory device <figref>43</figref> control. This Control operation may include a determination of which information on the memory device <figref>43</figref> is stored and how this information on the storage means <figref>43</figref> saved is.
0030In one embodiment, of the present invention, the Netzwerkmanagementbefehls- and -steuerungsserver <figref>16</figref> a specific message identifier deploy, which causes a message through a Network Management Session Management Agent <figref>48</figref> Will be received, which is tuned to a particular service identifier. Similarly way can News of the quick messaging server <figref>18</figref> a bearer included, which causes these Messages to the agent <figref>48</figref> in the client <figref>12</figref> transfer will. Similarly way can News of the data management session control server <figref>21</figref> suitable have identifiers that cause them to the data management session control agent <figref>45</figref> at the client <figref>12</figref> are diverted.
0031Of the server <figref>10</figref> may include a memory <figref>25</figref> exhibit, which software <figref>134</figref>. <figref>70</figref> and <figref>102</figref> for controlling the operation of the server <figref>22</figref> stores. Similarly Enables the server <figref>38</figref> on client <figref>12</figref> with a memory <figref>43</figref> be coupled, which software <figref>50</figref>. <figref>82</figref> and <figref>114</figref> stores, the operation of the server <figref>38</figref> controls. The servers<figref>22</figref> and <figref>38</figref> can also be processor-based systems.
0032It Referring now to <figref idrefs="S27">2</figref> taken, after which the software <figref>50</figref> on the client <figref>12</figref> first address and port of Unidirektionalübertragungsservers from the server <figref>10</figref> receives. the client <figref>12</figref> can also be a client identifier to be assigned, as in block <figref>52</figref> is shown. In this manner, a Internet Protocol multicast system are formed, each client a UMS address and a including port and a unique client identifier, which by the server <figref>10</figref> is assigned. In some embodiments, , the server <figref>10</figref> the addresses and ports and the client IDs dynamically adjust to a transfer of special news, news groups or types of messages to special clients in a dynamic and reconfigurable enabling manner.
0033After this the client <figref>12</figref> obtained his address, port and client identifier has closed the recipient the client <figref>12</figref> a multicast group and listen to messages from, specifically for addressed him or a group to which the client <figref>12</figref> heard it in block <figref>54</figref> is shown.
0034On Disk Management Agent <figref>44</figref> registers its service identification at the UMS server <figref>38</figref>As shown in block <figref>56</figref> shown is. If the UMS server<figref>38</figref> a package with a UMS message receives, as in block <figref>58</figref> shown, intended to consider whether the specific client <figref>12</figref> is the intended recipient, such as it in the diamond <figref>60</figref> is shown. If this is not the case is, the message is discarded, as in Block <figref>62</figref> shown is.
0035If However, the particular client is the intended receiver, checked the server <figref>38</figref> the service identification of the message and forwards the Message to the correct agent <figref>44</figref>. <figref>46</figref> or <figref>48</figref> further, as it in block <figref>64</figref> is shown. The message is then to the appropriate agent <figref>44</figref> sent, as in Block <figref>66</figref> shown is. In agent<figref>44</figref> the information is analyzed and supplied to the appropriate handling process, as in Block <figref>68</figref> shown is.
0036in the Case of addressing, such as sending the disk management agent <figref>44</figref> suitable Commands to the controller <figref>47</figref> for forwarding to the memory device <figref>43</figref>, Depending on the service identifier, which accompanies the message, the agent can <figref>44</figref> appropriately Way translated commands to controller <figref>47</figref> transfer, such as the commands to create a partition, delete a Partition or modify a partition. Each of these commands can be prepared by separate service identifier values such as 0 × 03, and 0 × 04 0 × 05, be given. The Disk Management Agent<figref>44</figref> a message may with a service identifier value into a format suitable for the control <figref>47</figref> on the basis of the of the client disk management server <figref>20</figref> received transmitted message. For example, the Agent <figref>44</figref> in a message which a service identifier value 0 × 03 contains a command for the control <figref>47</figref> produce to the memory <figref>43</figref> to partition.
0037On the in <figref idrefs="S28">3</figref> shown server side starts the network software <figref>70</figref>. by multicast addresses and ports for a unidirectional transmission service to a plurality of clients, <figref>12</figref> be assigned as it in block <figref>72</figref> is shown. The server<figref>10</figref> can and client IDs in a dynamic and reconfigurable Assign way. The address, the port and the client IDs are then transmitted to the client, as in block <figref>47</figref> is shown.
0038thereupon can the disk management server <figref>20</figref> a data structure and generate this data structure to the server <figref>22</figref> transfer, in block <figref>76</figref> is shown. The server<figref>22</figref> generated a unidirectional message and assigns a client value, sets a group flag, and copies private data in the Private Bytes the message, as in Block <figref>78</figref> is shown. Especially , a unique (single) client identifier assigned to it. The client identifier can be either a special pre-assigned his client identifier or it may be as an example also zero, when a plurality of clients is addressed. A group flag may be a Boolean value, which indicates whether the client identifier is a group mask or custom special identifier. A group mask is an identifier, a subgroup of clients <figref>12</figref> identified on the network. This subset may include a plurality of clients, however, less than the total number of clients adressiebaren.
0039In an example of a unidirectional message header, the Message containing a number of variables which Gruppen_Maske a, a Dienst_ID, a version_id, a Nachrichten_ID and Privat_Daten_Byte include. In one embodiment, of the present invention, the Gruppen_Maske contain 64 bits, the Dienst_ID may include eight bits, the 16 bits can version_id contain Nachricht_ID can eight bits and the Privat_Daten_Byte may include eight bits. The version_id is the version of Unidirektionalübertragungsprotokolls and may initially are set to zero. The Dienst_ID can a bearer be, for example, 0 × 02 for one may be quick intelligence. Advantageously does not exceed the message size 1,024 bytes in order to avoid a potential Datenpaketfragmentation. The Gruppe_Filter can be used in conjunction with the field CLIENT_ID be to increase the size of Privat_Daten_Byte limit, which for a application needs becomes. Each header characters can an unsigned integer most significant Bit first (unsigned integer most significant Bit First (uimsbf)) contain identifier in accordance with the DVB specification, with the exception the Privat_Daten_Byte which a bit string, left bit first (Bit StringLeft Bit First (bslbf)) identifier may contain.
0040As it in block <figref>80</figref> As shown, the message is then provided to all clients <figref>20</figref> sent on the network. Each client determines then if the message for this client is determined. The client<figref>12</figref> determines whether it is the specific intended recipient, by stating, if the message to the client identifier of the client <figref>12</figref> addressed is. For example, by an AND logic operator between the identifier the message and the identifier of the client is used, the client <figref>12</figref> determine if the client <figref>12</figref> themselves is among a group of clients that by jointly the server <figref>10</figref> addressed.
0041After one embodiment, the present invention may different groups of users receive common client identifier elements. In this manner, a plurality of clients whose owners for have signed an extended service, a common code section included in their client identifier. When a message that this contains common code section in the client identifier is received, accept any of these clients the message. Similarly, clients may in special geographic areas, having particular interests or otherwise identified clients unique Prefices / suffixes or identifier code sections exhibit. The code section can be logically ANDed with be a Gruppen_Maske to determine whether a particular client a member of the target audience.
0042Of the Management message header may also include fields to the disk management agent <figref>44</figref> to address, such as a Volumen_Name_Län field which volume name, length and bytes for the associated Volume of the storage device <figref>45</figref> in the form of a hard disk drive indicates. In one embodiment, the present invention may be eight bits long and this field it may include a bslbf identifier. additionally an Volumen_Name_Byte box volume, name and bytes specify which form the name of the set up volume on which a partition is generated. According to an embodiment of the invention may be eight bits long and may include a bslbf identifier this field. After all an Partition_Größe field the size of the generating partition in bytes specify. This field may be 32 bits wide and can the uimsbf identifier use. Naturally can additional Fields and additional Service identifiers are used to still additional commands to the client storage device <figref>45</figref> perform.
0043On Thus, the client disk management server <figref>20</figref> under the monitoring by server or head-end unit <figref>10</figref> the way control, as the memory <figref>43</figref> on a target client <figref>12</figref> or a targeted group of clients <figref>12</figref> set up and use becomes. Each of the clients<figref>12</figref> can individually addressed be, the entire group of clients can be addressed, or each subgroup of clients can be addressed together, such that their storage devices <figref>45</figref> modified individually or collectively can be. In this way, the storage means <figref>43</figref> of one or more clients from the server <figref>10</figref> be controlled from selectively.
0044Referring on <figref idrefs="S29">4</figref> receives the software <figref>82</figref> to the client <figref>12</figref> for executing a network management session first address and port of Unidirektionalübertragungsservers from the server <figref>10</figref>, the client <figref>12</figref> can also be a client identifier to be assigned, as in block <figref>84</figref> is shown. In this manner, a Internet Protocol multicast system may be formed, wherein each client a / a UMS address and port as well as a unique has client identifier, which by the server <figref>10</figref> assigned becomes.
0045After this the client <figref>12</figref> received its address, port and client identifier has, the client receiver occurs <figref>12</figref> one Multicast group at and listening / waiting messages which addressed specifically to him or to a group are, to which the client <figref>12</figref> heard it in the block <figref>86</figref> shown is.
0046On Data management session control agent <figref>45</figref> recorded his Service identification at the UMS server <figref>38</figref>As shown in block <figref>88</figref> shown is. If the UMS server<figref>38</figref> a package with a UMS message receives, as in block <figref>90</figref> shown, intended to consider whether the specific client <figref>12</figref> is the intended recipient, as in the rhomboid <figref>92</figref> is shown. If not, discarded the message, as in Block <figref>94</figref> shown is.
0047If but the specific client <figref>12</figref> is the intended recipient, checked the server <figref>38</figref> the service ID of the message and forwards the Message to the correct agent <figref>45</figref>, As in block <figref>64</figref> is shown. The message is then to appropriate agent <figref>45</figref> transfer, as in block <figref>98</figref> is shown. In Agent<figref>45</figref> becomes the information analyzed and transferred to an appropriate process for handling the same, as in block <figref>100</figref> is shown. The data management session control agent<figref>45</figref> receives a Target message from the data management session control server <figref>21</figref> and provides in response thereto by the server <figref>21</figref> requested Data, for. Example, via a return channel <figref>47</figref>. ready. To thisExample, in one embodiment of the Agent <figref>45</figref> news received with a certain syntax which a management message () comprises the a Gruppen_Maske, a Dienst_ID, a version_id, a Nachrichten_ID, a Nachrichten_Byte_Zähler and a DMSitzungs control message () contains, which in turn is a Sitzung_ID, a Sitzung_Host_Name, a Sitzung_Start_Zeit, a Sitzung_Dauer and Daten_ID contains.
0048The Sitzung_ID is a unique (single) session identifier. Of the Server_Host_Name is a string hostname of the data management server, to set up a connection. The Sitzung_Start_Zeit concerns Data and the time for the client <figref>12</figref>To set up a meeting. The Sitzung_Dauer is the duration from the start time which the server <figref>21</figref> for a meeting accepted and that it provides a time window, if necessary. The Daten_ID is a unique identifier of information or of a data record, what / which during the meeting to be replaced. The procedure for managing and assigning of information and / or data of the identifier is a private application.
0049On Thus, the server <figref>21</figref> a message to the client <figref>12</figref> cause which causes the client <figref>12</figref> charging or loading of specific data initiated at a particular time. That is, the server<figref>21</figref> can specify a header that a Sitzung_ID, Server_Host_Name, Sitzung_Start_Zeit, Sitzung_Dauer and Daten_ID contains, and in response, collects the data management session control agent <figref>45</figref> the requested information and displays this image in the requested Shape ready for the requested time.
0050Of the server <figref>21</figref> can messages with different message identifiers, which a session creation message, a session deletion message and a session update message as examples include, provide. The session deletion message clears simply a previously generated session, and the session update message causes additional Information for planned meeting is provided.
0051In one embodiment, of the present invention, the bit with the 64 Gruppen_Maske uimsbf identifier included. The Sitzung_ID can eight bits with a uimsbf identifier included. The version_id may contain 16 bits with a uimsbf identifier. The Nachrichten_ID may contain eight bits and may contain an identification of 0 × 01 exhibit. The Nachrichten_Byte_Zähler may contain 16 bits with a uimsbf identifier. The data management session control message (), the syntax Sitzung_ID eight bit, 64-bit Sitzung_Start_Zeit, Sitzung_Dauer 32 contain bits and a Daten_ID with 32 bits in one embodiment, all in the uimsbf identifier format. The data management session control Mach directional () can also Server_Host_Namen with 128 bits with a bslbf identifier contain.
0052On the in <figref idrefs="S30">5</figref> Server side shown starts the network software <figref>102</figref>. by multicast addresses and ports for a unidirectional transmission service are assigned to a plurality of clients, as in Block <figref>104</figref> shown is. The server<figref>110</figref> can be a client identifiers in a assign dynamic and reconfigurable fashion. The address, Port and client identifiers are then transmitted to the client, as in block <figref>106</figref> is shown.
0053thereupon , the data management session control server <figref>21</figref> a generate the data structure and the data structure to the server <figref>22</figref> pass on, as in block <figref>108</figref> is shown. The server<figref>22</figref> generated a unidirectional message and assigns a client value, sets a group flag, and copies private data in the private bytes of Message, as in Block <figref>110</figref> is shown. Specifically, a unique client identifier to be assigned. The client identifier can be either a special preassigned client identifier be, or for example it may be zero if a plurality are approached by clients. A group flag may be a Boolean value, which indicates whether the client identifier is a group mask or special identifier. A group mask is an identifier a subset of clients <figref>12</figref> identified on the network. This subset may include a plurality of clients, at least less than the total number of addressable clients.
0054As it in block <figref>112</figref> As shown, the message is then to all clients <figref>12</figref> sent on the network. Each client determines then if the message for this client is intended. The client<figref>12</figref> determines whether it the specific intended recipient is, by determining whether the message to the client identifier for the client <figref>12</figref> addressed is. For example, by an AND logic operator between the identifier the message and the identifier of the client is used, the client <figref>12</figref> determine if the client <figref>12</figref> within the group of clients is represented by the server <figref>10</figref> addressed jointly are.
0055Of the Netzwerkmanagementbefehls- and -steuerungsserver <figref>16</figref> working along with the network session management agent <figref>48</figref>, If a message which the server <figref>16</figref> is generated to the agent <figref>48</figref> directed is calling the Agent <figref>48</figref> the session manager <figref>49</figref> at. The session manager, the desired Management information in a predetermined format via a backchannel <figref>43</figref> according to a embodiment the present invention provide.
0056The Network management meetings generally serve, a network management information in server <figref>16</figref> to load. For example, a Management Information Base (MIB) via a Simple Network Management Protocol (SNMP) on the return channel <figref>43</figref> loading will. The operation of the agent<figref>48</figref>, As in <figref idrefs="S31">6</figref> shown is equivalent to that of generally, which previously with respect agents <figref>44</figref> and <figref>45</figref> has been described. That is, the UMS addresses, port and client identifiers are received, as in block <figref>116</figref> is shown. The receiver joins the multicast group listen in and or waits for messages, as shown in block <figref>118</figref> ge shows is, and the network session management agent <figref>48</figref> recorded his Service identification at the UMS receiver, as in block <figref>120</figref> is shown. The UMS receiver then receives the packet with the message, as in Block <figref>122</figref> shown is.
0057A exam in the lozenge <figref>124</figref> determines whether the special agent <figref>48</figref> of the intended recipient is. If this is not the case, the message is discarded, as it in block <figref>126</figref> is shown. Otherwise, the receiver checks the Service identification and forwards the message to the agent <figref>48</figref> continue, as in block <figref>130</figref> is shown. The information is analyzed and to the session manager <figref>49</figref> transfer. The session manager<figref>49</figref> wound then the session with the server <figref>16</figref> using the channel <figref>43</figref> from.
0058The Message format is substantially the same as that by the DMSC used format. However, instead of a DMSitzungSteuerungsNachricht () includes a NMSitzungsSteuerungsNachricht () a Info_ID field. The Info_ID Field is a unique identifier or information or data group, which during the session is exchanged. The procedure for managing and assigning the information and / or data group identifier is a private application. For example, a specific SNMP MIB client are identified, to be uploaded to the server when the client often MIBs managed.
0059A MIB is information on an agent, which as a "Management Information Base "is known. This information forms the basis for an Event Report. The standards with MIBs are z. B. in RFC 1229 specified, distributed by Network Working Group (Mai 1991).
0060It Referring now to <figref idrefs="S32">7</figref> taken, after which the operation the network management server <figref>16</figref> using the software <figref>134</figref> in the substantially corresponds to that which was previously described. Again, the multicast address and the port for a UMS assigned, and the Clientken openings are assigned as in block <figref>136</figref> is shown. The UMS address and port and the client identifier are sent to the clients, as shown in block <figref>138</figref> is shown, and the Netzwerkmanagementbefehls- and -steuerungsserver <figref>16</figref> creates a data structure and transfers the data to the UMS server, as in Block <figref>140</figref> shown. The UMS server<figref>22</figref> generated then a UM message, assigns a client value, sets a Group flag and copies private data in private bytes of the message, as in block <figref>142</figref> is shown. Then, the message sent (block <figref>144</figref>).
0061thereupon receives the server <figref>16</figref> at a predetermined time, the sequence control information (scheduling information) of the session manager <figref>49</figref>, At an appropriate time may a session may be provided in which the MIBs or other information to the server <figref>16</figref> about Influence of agents <figref>48</figref> and the Session Manager <figref>49</figref> Loading.
0062In one embodiment, the present invention may different sets of users receive common client identifier elements. Therefore, a plurality of clients, whose owner is for one have registered improved service, a common code section included in their client identifier. When a message that this contains common code section in the client identifier is received, takes each of these clients to the message.
0063While the present invention with respect to a limited number of embodiments has been described, it is understood for the skilled person that numerous Modifications and variations can be made of it. It is intended that the appended claims the totality of such modifications and changes which under the The spirit and scope of this invention fall include.
7 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US5892912A | Cites | United States of America | Search report |
| US5978845A | Cites | United States of America | Search report |
| US6058399A | Cites | United States of America | Search report |
| LOUIS, S. u.a.: Management Issues for High-Performance Storage Systems (online), IEEE, 1995, S. 336-348 (recherchiert am 10.01.05). Im Internet: URL:http://ieeeplone.ieee.org/iel3/4020/1153800528243.pdf?isNumber=11538&prod=IEEE+CNF&arnumber=528243&arSt=336&ared=348&arAuthor=Louis%2C+S.%3 B+Burris%2C+R.D.%3B ; | Non-patent | – | Search report |
| HEIN, Mathias, GRIFFITHS, David: SNMP Simple Network Management Protocol Version 2, 1. Aufl., Bonn (u.a.), International Thomson Publishing GmbH, 1994, S. 339-340; | Non-patent | – | Search report |
| LOUIS, S. u.a.: Management Issues for High-Performance Storage Systems (online), IEEE, 1995, S. 336-348 (recherchiert am 10.01.05). Im Internet: <URL:http://ieeeplone.ieee.org/iel3/4020/11538/00528243.pdf?isNumber=11538&prod=IEEE+CNF&arnumber=528243&arSt=336&ared=348&arAuthor=Louis%2C+S.%3B+Burris%2C+R.D.%3B> | Non-patent | – | – |
| LOUIS, S. u.a.: Management Issues for High-Performance Storage Systems (online), IEEE, 1995, S. 336-348 (recherchiert am 10.01.05). Im Internet: URL:http://ieeeplone.ieee.org/iel3/4020/1153800528243.pdf?isNumber=11538&prod=IEEE+CNF&arnumber=528243&arSt=336&ared=348&arAuthor=Louis%2C+S.%3 B+Burris%2C+R.D.%3B ; | Non-patent | – | Search report |
| HEIN, Mathias, GRIFFITHS, David: SNMP Simple Network Management Protocol Version 2, 1. Aufl., Bonn (u.a.), International Thomson Publishing GmbH, 1994, S. 339-340; | Non-patent | – | Search report |
22 members in 13 offices
Priority claims10
| Document | Office | Kind | Date |
|---|---|---|---|
| 68675400 | United States of America | A | |
| 68675400 | United States of America | A | |
| 68675400 | United States of America | – | |
| 0131161 | United States of America | W | |
| 0131161 | United States of America | W | |
| 0131161 | United States of America | – | |
| 09686754 | – | – | – |
| PCTUS0131161 | – | – | – |
| US20000686754 | – | – | – |
| WO2001US31161 | – | – | – |
Members22
| Document | Office | Kind | |
|---|---|---|---|
| CA2423582A1 | Canada | A1 | |
| WO0232072A2 | World Intellectual Property Organization (WIPO) | A2 | |
| AU9662001A | Australia | A | |
| WO0232072A3 | World Intellectual Property Organization (WIPO) | A3 | |
| FI20030536A | Finland | A | |
| NO20031621D0 | Norway | D0 | |
| GB0306498D0 | United Kingdom | D0 | |
| TW530238B | Taiwan Province of China | B | |
| KR20030036910A | Republic of Korea | A | |
| NO20031621L | Norway | L | |
| GB2383731A | United Kingdom | A | |
| EP1325587A2 | European Patent Office (EPO) | A2 | |
| JP2004511960A | Japan | A | |
| GB2383731B | United Kingdom | B | |
| CN1528070A | China | A | |
| KR100545488B1 | Republic of Korea | B1 | |
| JP2007116682A | Japan | A | |
| CA2423582C | Canada | C | |
| DE10196775B3This record | Germany | B3 | |
| CN1528070B | China | B | |
| US7765316B1 | United States of America | B1 | |
| JP2010252360A | Japan | A |
2 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Application deemed withdrawn, or ip right lapsed, due to non-payment of renewal feeWithdrawnR119 | R119 | |
| No opposition during term of oppositionOpposition8364 | 8364 |
Numbers
- Publication
- 10196775
- Publication, DOCDB
- 10196775
- Publication, EPODOC
- DE10196775
- Application
- 10196775
- Application, DOCDB
- 10196775
- Application, EPODOC
- DE2001196775
Titles2
- German
- Verwalten von entfernten Clients
- English
- Managing remote clients
Classification
- CPC, 3
- H04L12/1881
- H04L12/18
- H04L41/046
- IPC, 8
- G06F13 00
- H04L29 00
- H04L12 18
- H04L12 24
- H04L12 56
- H04N7 14
- H04W4 06
- H04W8 26
