JP4828619B2 - Routing hint - Google Patents

Abstract

A first exemplary media implementation includes processor-executable instructions that direct a device to perform actions including: creating a session identifier (210) using a host identifier (214); and formulating a host session initiation message with the created session identifier. An exemplary device implementation includes: at least one processor; and one or more media including processor-executable instructions that direct the device to perform actions including: formulating a host session message with a session identifier that is created responsive to a host identifier; and sending the formulated host session message that includes the session identifier from the device. A second exemplary media implementation includes processor-executable instructions that direct an apparatus to perform actions including: ascertaining a host identifier from a session identifier field of a session message; and routing the session message responsive to the ascertained host identifier.

Description

  This disclosure relates generally to routing hints, and specifically provides routing hints from hosts to use such routing hints at network gateways to facilitate intranet routing as an example rather than a limitation. About doing.

  Communication has been greatly influenced by the capabilities of the Internet. The Internet makes it possible to communicate information quickly and relatively easily between two people or other entities using packets. The Internet includes a number of network nodes linked together so that packets containing information can be transferred between them. Network nodes include routers that propagate packets from one link to another, individual client computers, a completely personal network (eg, for a particular entity), and the like.

  Communication between the first entity and the second entity on the Internet is realized by configuring a connection between them. These connections sometimes include sessions. A session is established to provide a context for communication exchanges that take place over the corresponding connection or connections. Session establishment typically includes one-way or two-way information exchange between the first entity and the second entity. The complexity and duration of the session establishment phase usually varies based on the type of session.

  Each session establishment uses processing resources and consumes a certain time period, which is converted into a delay experienced by the user. After the session establishment phase, the first entity and the second entity communicate according to the established session context. This communication and connection may end without ending the session. In some cases, such an existing session then uses that information if the information previously exchanged between the two entities during the previous session establishment phase is held by these entities May continue.

  In other words, previously exchanged information is used to continue the existing session. Thus, continuation of an existing session generally relates to a situation where the same first and second entities that previously established the session attempt to continue that session. As a result, problems may arise when the first entity attempts to continue an existing session if the second entity is unknown and / or difficult to identify or contact.

  Accordingly, there is a need for schemes and / or techniques that improve, simplify, and / or facilitate session continuity between two entities.

  In a first exemplary media implementation, when one or more processor-accessible media are executed, the host identifier is used to create a session identifier, and the created session identifier is used to host Processor executable instructions that instruct the device to perform operations that formulate a session initiation message.

  In a first exemplary device implementation, a device includes at least one processor and one or more media including processor executable instructions that can be executed by the at least one processor, the processor executable instructions comprising: Performing an operation of formulating a host session message using a session identifier created in response to the host identifier and an operation of sending the formulated host session message including the session identifier from the device. Adapted to instruct the device.

  In a second exemplary media implementation, one or more processor-accessible media includes a data structure, the data structure being a message including a session identifier field, wherein at least a portion of the session identifier field is Contains the host identifier.

  In a second exemplary device implementation, a device includes a host identifier and a session identifier creator adapted to create a session identifier using the host identifier.

  In an exemplary network gateway implementation, a network gateway can accept a session related message having a session identifier field, and the network gateway is adapted to extract a host identifier from a value entered in the session identifier field. And the network gateway is further adapted to perform a routing operation of the session related message using the host identifier.

  In a third exemplary media implementation, one or more processor-accessible media, when executed, responds to the confirmed host identifier with an operation of confirming a host identifier from a session identifier field of a session message. Processor-executable instructions for instructing the device to perform operations to route the session message.

  In an exemplary apparatus implementation, an apparatus includes at least one processor and one or more media including processor-executable instructions that can be executed by the at least one processor, wherein the processor-executable instructions include a host identifier. The apparatus is adapted to instruct the apparatus to perform an operation of receiving a session message having a session identifier including and an operation of routing the session message in response to the host identifier.

  Implementations of other methods, systems, techniques, devices, application programming interfaces (APIs), devices, media, procedures, arrangements, etc. are described herein.

  The same numbers are used throughout the drawings to reference like and / or corresponding aspects, features, and components.

FIG. 2 illustrates an exemplary communication environment showing a first connection that establishes a session and a second connection that continues the session. FIG. 6 illustrates an exemplary technique for providing and using routing hints with session messages. FIG. 4 illustrates an example session message that can include a routing hint. 2 is a flow diagram illustrating an exemplary method for providing routing hints. FIG. 6 illustrates another exemplary approach for providing and using routing hints with session messages. FIG. 6 illustrates an exemplary table showing host identifier and network address linking used with routing hints. FIG. 6 illustrates an exemplary table showing host identifier and network address linking used with routing hints. 5 is a flow diagram illustrating an exemplary method for using routing hints. FIG. 6 illustrates an example computing (or general device) operating environment in which at least one aspect of the routing hints described herein can be implemented (in whole or in part).

  FIG. 1 is an exemplary communication environment 100 showing a first connection 114 (1) establishing a session and a second connection 114 (2) continuing the session. As can be seen, the exemplary communication environment 100 includes a plurality of clients 102 (1), 102 (2),..., 102 (m) and a plurality of hosts 108 (1), 108 (2),. (N), and network 104 and network gateway (NG) 106 are included. Network gateway 106 serves as a gateway between network 104 and intranet 110. Host 108 is coupled to intranet 110.

  In the described implementation, clients 102 (1), 102 (2),..., 102 (m) correspond to addresses “C1”, “C2”,. Each of the clients 102 can be any device capable of network communication, such as a computer, mobile station, entertainment device, another network, and the like. Client 102 may also correspond to a person or other entity operating a client device. In other words, the client 102 can include logical clients that are users and / or machines.

  The network 104 may be formed from one or more networks, such as the Internet, another intranet, a wired or wireless telephone network, a wireless broadband network. Additional examples of devices of network type / topology for client 102 and network 104 are described below with reference to FIG. Individual clients 102 can communicate with one or more hosts 108 via network 104 and network gateway 106, and vice versa.

  The hosts 108 (1), 108 (2),..., 108 (n) correspond to the addresses “H1”, “H2”,. The host addresses H1, H2,..., Hn exist on the intranet 110. Host 108 typically hosts one or more applications (not shown). These applications (i) provide services related to interaction and / or communication with the client 102 and (ii) are for use by the client 102 and the like. By way of example only, such applications may include file delivery programs, website management / server programs, remote access programs, email programs, database access programs, and the like.

  Each host 108 may correspond to one server and / or one device, multiple servers and / or multiple devices, part of a server and / or part of a device, some combination thereof, and the like. Certain exemplary implementations of the host 108 are further described below with reference to FIGS. 2, 4, and 5. In addition, an additional exemplary device implementation of the host 108 is described below with reference to FIG.

  The network gateway 106 is reachable or locable via the network 104 at one or more addresses “NGN”, and the network gateway 106 also has a presence on the intranet 110 having at least one address “NGI”. Communication from the client 102 (or other node) destined for the address NGN of the network gateway 106 is received at the network gateway 106 and then the hosts 108 (1), 108 (2), ..., 108 (n The network gateway 106 consists of one or more network gateway elements (not separately shown in FIG. 1). The gateway element 106 can include routers, proxies, load balancers, all or part of firewall devices, some combination thereof, etc. An exemplary non-specific device implementation of the network gateway element 106 is also illustrated below. Explanation will be made with reference to FIG.

  In general, the connection 114 is configured on the network 104 via the network gateway 106 between the client 102 and the host 108. Typically, the client 102 initiates the connection 114, but instead the host 108 can be the initiator. Specifically, in this example, the client 102 (1) starts the connection 114 (1) with the host 108 (2). However, the client 102 (1) is not involved in the address H2 of the host 108 (2). Rather, client 102 (1) directs this connection (eg, a packet requesting a connection) to address NGN of network gateway 106.

  The network gateway 106 then performs a routing operation 116 (1) for the connection 114 (1) according to some default policy (eg, rule). As a result, the network gateway 106 routes the connection 114 (1) to the host 108 (2) via the intranet 110 for this example. In general, the network gateway 106 cannot simply transmit the packet of the connection 114 from the client 102 (1) as it is to the host 108 (2) of the network address H2. This is because the destination address of this packet is specified for the address NGN of the network gateway 106. Instead, the network gateway 106 typically passes over the intranet 110 using one or more of the exemplary options such as network address translation (NAT), half-NAT, tunneling, some combination thereof, and the like. Route the packet.

  In a Transmission Control Protocol / Internet Protocol (TCP / IP) environment, the NAT has (i) the source (ie, client 102 (1)) IP address C1 and port number generated by the IP address NGI and NAT of the network gateway 106. This is executed by overwriting with the number, and (ii) overwriting the destination IP address NGN with the IP address H2 of the host 108 (2). half-NAT is performed by overwriting the destination IP address NGN with the IP address H2 of the host 108 (2) so that the source IP address C1 and port number are saved. Tunneling is performed by encapsulating each packet in a new IP packet addressed to the address H2 of the host 108 (2) and sending the encapsulated packet from the network gateway 106 to the host 108 (2). At 108 (2), the encapsulated packet can be decapsulated.

  During connection 114 (1), a session is established between client 102 (1) and host 108 (2). For the established session of connection 114 (1), a session context 112 is created at host 108 (2). Similar, similar, and / or mutual session contexts (not shown) are typically created at the client 102 (1). Session context 112 facilitates communication between client 102 (1) and host 108 (2).

  Accordingly, connection 114 (1) may or may not have established one or more of a number of different types of sessions thereon. Exemplary types of sessions include: (i) Secure Sockets Layer (SSL) session, (ii) Transport Layer Security (TLS) session, (iii) Secure Internet Protocol (IPsec) session, (iv) Hypertext Transfer Protocol (HTTP) ) Cookie-based session, (v) point-to-point tunneling protocol (PPTP) session, (vi) IPSec / layer-2 tunneling protocol (L2TP) session, (vii) proprietary session, (viii) terminal server session, (ix) ) Administrator-defined sessions, and (x) others. These examples of different session types also show how multiple layers of sessions are established and used.

  The content of the session context 112 can vary, at least in part, depending on the type of session it was created for. For example, a particular session context 112 may include a TCP 4 tuple (eg, for a session established using a TCP connection), a session identifier, the location of one or more database entries that maintain the persistent state of the corresponding session, host One or more of the public key of the client 102 (1) supplied to 108 (2), the negotiated secret encryption key, other security-related parameters, etc. may be included. The TCP 4 tuple includes a source IP address, a source TCP port, a destination IP address, and a destination TCP port. For example, for an SSL session under the current standard, the session identifier can be up to 32 bytes long.

  As explained above, in the current example, after configuring connection 114 (1), a session is established between client 102 (1) and host 108 (2). Client 102 (1) more specifically establishes a session with at least one application that resides on and / or runs on host 108 (2). However, for clarity of explanation, such applications can generally be included when referring to the host 108 (2).

  The session establishment phase creates or provides a session context 112. Session context 112 provides a context for communication exchange between client 102 (1) and host 108 (2). Session context 112 may include information that is actually critical to these communications exchanges, simply useful, or in any other way relevant.

  If the client 102 (1) can be a logical client, the session context 112 can (1) communicate with a particular device and / or a particular user of the device and (ii) a host 108 (2). Can be related. As a result, the session context 112 associated with the user client 102 (1) will continue to be associated with the user client 102 (1) even when the user client 102 (1) accesses the host 108 from a different device. Can do. The devices may be different at the local level of the client 102 (1), at the network 104 level, and so on. Examples of such different device scenarios include proxy scenarios (e.g., certain Internet service provider (ISP) proxy scenarios), terminal server session scenarios, and the like.

  Session context 112 is stored on host 108 (2) and / or accessible from host 108 (2). When the connection 114 (1) is completed or otherwise stopped, the session context 112 may not be used again. Conversely, session context 112 becomes useful once again when client 102 (1) attempts to initiate another connection with host 108 for the same session, a similar session, or an associated session, etc. there is a possibility. If this other connection is not routed to the same host 108 (2) that stores the session context 112, the client 102 (1) must establish a new session, which It can be data, processing intensive and / or annoying to users (especially the user corresponding to client 102 (1)). If there is no session affinity storage mechanism in the network gateway 106, there is usually no higher possibility than a random opportunity where the second connection is routed to the host 108 (2).

  The session affinity storage mechanism or session affinity storage functionality is adapted to route connections (including packet level requests and logical level requests) to the host 108 associated with the session context 112 of the existing session that is continued with the connection. . For example, the session affinity storage functionality attempts to allow the connection 114 (2) of the client 102 (1) to be routed to the host 108 (2) with which the session context 112 is associated. Such a session affinity storage mechanism can be implemented according to one or more exemplary strategies. Although generally applicable to the network gateway 106, these exemplary strategies are described from the perspective of a load balancing implementation.

  The first strategy relates to load balancing using a “sticky” mode, in which most, if not all requests coming from a given, eg, IP address, go to a single host 108. Routed. However, although this strategy relies on the assumption that a given IP address represents a single client 102, this assumption is clearly not true for proxies. A proxy appears to a load balancer as a single IP address, but actually represents a large number of potentially thousands of client 102 requests. As a result, routing all of these requests to a single host 108 can lead to very uneven load distribution among the devices. Typically, a device that receives an incoming request from a proxy is assigned a much larger number of clients 102 as a result. Furthermore, requests from clients 102 with changing IP addresses are also routed incorrectly using this first strategy. An IP address may change in a mobile environment, such as when an address is temporarily assigned from an IP address pool.

  The second strategy involves using a load balancing heuristic that uses session identifiers. A request to continue an existing session is routed to the host 108 that previously established (eg, negotiated) that session using the particular individual session identifier. In operation, after a particular session is established between a particular client 102 and a particular host 108, a mapping that links that particular host 108 to that particular session is stored and the session is stored in a particular session. Identified by an identifier. When a request is received that includes a particular session identifier from that particular client 102, the request can be routed to that particular host 108 using this mapping. This second strategy thus allows for the preservation of session affinity.

  However, the second strategy has several relative drawbacks from an efficiency perspective. First, the load balancer maintains a table of these mappings between session identifiers and hosts 108. The size of this table can be huge because there is a separate entry for each existing session. For example, if each host 108 caches 10000 sessions and there are 500 hosts 108, this table will store 5 million entries to route requests for these sessions with optimal efficiency. use. Second, for each newly established session, the load balancer monitors the session establishment phase until a session identifier is detected and an entry can be added to the table. Third, each time a request to resume a session is received, the load balancer queries this (very likely) table to perform routing.

  Fourth, because the session has a lifetime and is actively aged out of the host 108 cache due to congestion, the load balancer table also implements some aging mechanism so that individual hosts 108 Mirror what you are doing or expected to do with your own cache. If the aging mechanism of the host 108 and the load balancer is not synchronized, the load balancer may delete state information about sessions that are still valid on the host 108 too early, or vice versa. May hold session state information that no longer exists.

  A third strategy for session affinity storage functionality is through the selective creation / determination of session identifiers for newly established sessions, without a table requiring an entry for each individual session, at the network gateway 106. Session affinity preservation can be achieved. When determining the session identifier, the host 108 embeds the host identifier therein.

  The network gateway 106 extracts the host identifier from the session identifier, and routes the traffic of the session to which the session identifier is assigned in response to the host identifier. Thus, a third strategy uses a table with a bounded number of entries (eg, a number of entries equal to the number of hosts 108) to route session continuation requests and / or for each such session. A relatively stateless approach can be used to route session continuation requests without using a table with entries. Aspects of this third strategy are further described herein.

  In the example communication environment 100, a session context 112 is created at the host 108 (2) after the session establishment phase is completed as part of the connection 114 (1). Thereafter, connection 114 (1) is terminated. When a request for connection 114 (2) arrives at network gateway 106, a routing operation 116 (2) is performed thereon. This connection 114 (2) is indicated by the session identifier assigned to it to relate to the continuation of the previously established session corresponding to the session context 112. This session identifier includes the identifier of host 108 (2) according to the third strategy. By using the host identifier of host 108 (2) extracted from the session identifier of the session continuation request, connection 114 (2) is routed to host 108 (2) in routing operation 116 (2), and this host 108 (2) relates to the session context 112.

  Items 114 (1) and 114 (2) can also represent session related messages (eg, requests) that occur within a single connection as well as session related messages that occur during multiple connections. Further, certain communications between the client 102 and the host 108 are described herein as messages. Messages are typically propagated from the client 102 to the host 108 and vice versa as one or more packets. Client messages are sent from the client 102, and host messages are sent from the host 108. A session message is a message related to a session (for example, a message related to session establishment, continuation / resumption, destruction, etc.). An exemplary session message is further described below with reference to FIG.

  A session start message is a message sent by the client 102 and / or the host 108 regarding the start of a session. A session continuation message is a message sent by the client 102 and / or the host 108 regarding the continuation of an existing session. Session initiation messages and session continuation messages can have clearly different formats, similar formats, identical formats, and so on. However, in the described implementation, the session initiation message and the session continuation message have at least a similar format, in which the presence of a session identifier indicates that a client session message is a client session continuation message; The absence of a session identifier indicates that a client session message is a client session start message.

  Although the description herein is not limited thereto, the implementation described below sometimes coordinates or focuses on the load balancing implementation of the network gateway 106. Also, other protocols and combinations of protocols are applicable and can be used instead, but in the description below, mainly TCP / IP connections and SSL / TLS sessions are used for clarity of explanation. use.

  By way of example and not limitation, a client session start message or a client session continuation message may be a “Client Hello” message that conforms to a certain specification (eg, “the TLS Protocol Version 1.0 Spec (January 1999)”). . If the Client Hello message includes a session identifier, this message can be a client session continuation message; otherwise, this message can be a client session start message. Similarly, the host session start message or the host session continuation message may be a “Server Hello” message according to a certain specification (for example, see Non-Patent Document 1). If the Server Hello message includes the session identifier supplied by the client in the Client Hello message to which the Server Hello message is responding, this message can be a host session continuation message. If the Server Hello message is in response to a Client Hello message that does not include a session identifier, this message can be a host session start message. The creation and formulation of a session identifier for such a host session initiation message is further described below.

  FIG. 2 illustrates an exemplary approach for providing and using routing hints with session messages. Session messages 202, 204, and 206 are sent through the network 104, through the network gateway element 106, from the client 102 to the host 108, and vice versa. Network gateway element 106 represents an element of network gateway 106 (of FIG. 1). Although each of the session messages 202, 204, and 206 is illustrated as being routed by the network gateway element 106, each individual session message is instead routed by a different individual element of the network gateway 106. be able to.

  As can be seen, the host 108 includes a message handler 208 that processes messages sent to and received from the client 102. Message handler 208 includes an incoming message handler portion 208IC and an outgoing message handler portion 208OG. The host 108 is associated with the host identifier 214, which is stored on the host 108 or otherwise accessible from the host 108. An example of the host identifier 214 is further described below with reference to FIG. The host 108 also includes a session identifier creator 212 that uses the host identifier 214 to create a session identifier (eg, session identifier 210).

  In the described implementation, client 102 has address “C”, network gateway element 106 has addresses NGN and NGI, and addresses C and NGN are located on network 104. Host 108 has an address “H”, which is located on intranet 110 along with address NGI. Session messages from the client 102 are received at the network gateway element 106 via the network 104. The network gateway element 106 then routes these session messages to the host 108 using the routing operation 216 via the intranet 110. In the reverse path, a session message from the host 108 is sent / sent via the intranet 110 to the network gateway element 106, which routes the message to the client 102 using a routing operation 216.

  Specifically, the client 102 sends a client session initiation message (SIM) 202 to the network gateway element 106 over the network 104. The client session start message 202 does not include a session identifier as long as a request for a new session is included. Since the client session initiation message 202 is not related to an existing session, the network gateway element 106 routes the client session initiation message 202 to the host 108 using a general policy in the routing operation 216 (A). For example, the network gateway element 106 can route the client session initiation message 202 according to current and / or associated load balancing policies (eg, round robin distribution of incoming new session requests).

  The host 108 receives the client session start message 202 at the incoming message handler portion 208IC via the intranet 110. In the absence of a session identifier, the incoming message handler portion 208IC recognizes the client session start message 202 as relating to a new session. Session identifier creator 212 is activated to create a new session identifier for the requested new session. Session identifier creator 212 confirms / retrieves host identifier 214.

  Session identifier creator 212 uses session identifier 214 to create session identifier 210. For example, session identifier creator 212 inserts host identifier 214 into session identifier 210. The session identifier 210 can include a value other than the host identifier 214. Additional values for session identifier 210 may be created using either one or more techniques. Such techniques include, but are not limited to, randomly selected values, values from incrementing counters, security related values, hashed values, some combination of these, and the like.

  In the described implementation, the first portion of session identifier 210 (ie, host identifier 214) is dedicated to identifying the host 108 that currently owns the corresponding session. This first part is unique across the hosts 108 of a given cluster (ie, none of the hosts 108 share a host identifier 214 with other hosts 108 in the same cluster). This first part can be an IP address owned by the host 108, an integer assigned by the administrator, or the like. The second part of the session identifier 210 can increase the uniqueness (and unpredictability) of the session identifier 210. For this second part, use various techniques such as a combination of using global counters (with rollover to 0) incremented once for each new session and using random numbers and / or hashing techniques can do.

  Session identifier creator 212 provides session identifier 210 to message handler 208. The outgoing message handler portion 208 OG prepares / formulates a host session start message 204 that includes a session identifier 210. The host session start message 204 is sent to the network gateway element 106 via the intranet 110. Next, the network gateway element 106 sends a host session start message 204 to the client 102 via the network 104 using the route back routing operation 216 (B). Although not shown as such, the host session initiation message 204 is instead sent to the network gateway element 106 as long as the network gateway element 106 can route subsequent client messages without accumulating state information for each session. You can route along paths that do not include.

  The client 102 extracts the session identifier 210 from the host session initiation message 204 and saves the session identifier 210 for possible future use (and current use for the established session) to continue the established session. To do. At some point, the actual use of the established session is terminated (eg, the connection is terminated). In order to continue an established existing session with the host 108, the client 102 formulates a client session continuation message (SCM) 206. The client 102 includes the stored session identifier 210 in the client session continuation message 206. A client session continuation message 206 is then sent from the client 102 to the network gateway element 106 over the network 104.

  When the network gateway element 106 receives the client session continuation message 206, it detects that the client 102 is attempting to continue the existing session indicated by the included session identifier 210. At routing operation 216 (C), network gateway element 106 routes client session continuation message 206 using session identifier 210. Specifically, the network gateway element 106 is part of the session identifier 210 and uses the host identifier 214 extracted therefrom to route the client session continuation message 206.

  Host identifier 214 identifies the host 108 associated with it. Accordingly, the network gateway element 106 routes the client session continuation message 206 in a routing operation 216 (C) using the identity of the host 108 indicated by the host identifier 214. Accordingly, the client session continuation message 206 is sent from the network gateway element 106 to the host 108 via the intranet 110. At host 108, incoming message handler portion 208IC receives client session continuation message 206 and uses the stored session context (eg, session context 112 shown in FIG. 1) to continue the previously established session. Can start.

  The host identifier 214 can identify the host 108 associated therewith in a number of ways. For example, the host identifier 214 can include the (intranet) network address H of the host 108. In this case, the network gateway element 106 can route the client session continuation message 206 to the host 108 without using the session association table or the host identifier table. In other words, the client session continuation message 206 is forwarded to the host 108 by using the host identifier 214 or at least a portion thereof as the destination address of one or more packets placed on the intranet 110 with respect to the client session continuation message 206. can do.

  Instead, the host identifier 214 can be mapped to the address H of the host 108. This form of mapping involves a table (or calculation), but the number of entries “n” in this table can be the same as the number of hosts 108 in the server cluster, on the intranet 110, in a web farm, etc. . Therefore, this table has a bounded number of entries and does not include state information for each session. Referring to the example used above, if each host 108 caches 10000 sessions and there are 500 hosts 108, this table is used to efficiently route requests for these sessions. Entries (rather than 5 million) can be used.

  Table 1 below is an exemplary linking data structure that links host identifier 214 to host 108 by host 108 address.

  In operation, the network gateway element 106 extracts the host identifier 214 (#) from the session identifier 210 of the client session continuation message 206 when received from the client 102. The network gateway element 106 then accesses a linking data structure, such as the linking data structure of Table 1, by using the host identifier 214 (#) and identifies the host address H # linked thereto. This host address H # corresponds to the address of the host 108 (#) on the intranet 110 and is used as a destination address for routing the client session continuation message 206 to the host 108 (#). An exemplary host identifier to network address linking table is further described below with reference to FIGS. 6A and 6B.

  FIG. 3 illustrates an exemplary session message 302 that can include a routing hint. Session message 302 is a message associated with one or more sessions. As can be seen, the session message 302 includes a plurality of fields. The plurality of fields includes a session identifier 210 and one or more other fields represented by other fields 304.

  The session identifier 210 includes at least one host identifier 214. The host identifier 214 includes a device identifier 306 and optionally an application identifier 308. The device identifier 306 can include the network address 310 or the key 312 (A). Alternatively, the host identifier 214 can include the key 312 (B).

  In the described implementation, one or more formats of the session message 302 are defined by a network or communication standard or protocol, such as SSL / TLS. Session identifier 210 can be placed anywhere within session message 302 as defined by an applicable standard or protocol. Other fields 304 may include source and / or destination addresses, general header information, security type information, other session related information, data, some combination thereof, and the like. For example, the session message 302 can be a Client Hello message or a Server Hello message defined by the TLS Protocol Version 1.0 standard, and the session identifier 210 corresponds to the “SessionID” field of any TLS Hello message. can do. An example of a field 304 that includes security type information is a cryptographic field that indicates which cryptographic options are supported by the session participant (eg, client or host) formulating the session message 302.

  Session identifier 210 includes host identifier 214 and optionally other values that together form a session identifier. This session identifier is entered in the session identifier 210 field of the session message 302. The host identifier 214 can be placed anywhere in the field for the session identifier 210, including being split, scattered and / or scattered in the session identifier 210 field.

  In the described implementation, the subfield of session identifier 210 corresponding to host identifier 214 is implemented as a continuous sequence of bytes to simplify extraction. This consecutive sequence of bytes appears at a fixed offset from the most significant byte of session identifier 210. However, the fixed offset can instead be from the least significant byte.

  For additional flexibility, the host identifier 214 can be made configurable externally rather than being selected by, for example, an SSL / TLS component. For example, the host identifier 214 can be configured externally by reading it as a value from a registry key. As noted above, the administrator can determine the host identifier 214, such as by setting a registry key value or via some other mechanism.

  The host identifier 214 can instead be embedded in a field that is different from the field of the session identifier 210. For example, certain fields that are sent to the client 102 and returned unchanged when the client 102 requests to resume an existing session can be used. This alternative is particularly applicable when the message format and the underlying protocol require or allow the host 108 with the desired session context 112 to create / select the value of this particular field. It is. For this alternative, the network gateway element 106 performs a routing operation 216 using at least a portion of the contents of this particular field.

  The host identifier 214 includes a device identifier 306 and can also include an application identifier 308. Device identifier 306 corresponds to the device for / for host 108 hosted by host identifier 214. As can be seen, the device identifier 306 includes a network address 310 or key 312 (A) that identifies the device of the host 108.

  The network address 310 is a network address on the intranet 110 of the device of the host 108. Thus, when the device identifier 306 includes the network address 310, the network gateway element 106 can insert the device identifier 306 in the destination field of one or more packets that are forwarded to the host 108.

  The key 312 (A) is a value mapped to the network address on the intranet 110 of the device of the host 108. This mapping can be achieved by looking up a network address in a table, performing a calculation (eg, following an equation, implementing an algorithm, etc.), and the like. For example, the key 312 (A) can be linked to the host address H with a data structure such as that described above with reference to Table 1. An exemplary table in which the key 312 (A) is linked to the network address 310 is further described below with reference to FIG. 6A.

  When the host identifier 214 includes the device identifier 306 and the application identifier 308, the host identifier 214 includes the application endpoint. Application identifier 308 identifies a particular application on the host device identified by device identifier 306. Accordingly, the host identifier 214 including the device identifier 306 and the application identifier 308 identifies a particular application among multiple applications that are on a single host 108 and / or replicated across multiple hosts 108. be able to.

  An application endpoint can also be included in the host identifier 214 that includes the device identifier 306 but not the application identifier 308. For example, this is particularly likely when the device has only one application, when the device is multihomed, when the device's NIC has two IP addresses, and so on. In any case, the host identifier 214 serves to identify a particular application as well as a particular host 108. As a result, routing of the client session continuation message 206 can be quickly performed toward a desired application having session affinity with the requesting client 102.

  The host identifier 214 can include a key 312 (B) instead. The key 312 (B) is a value that is mapped to (i) the network address on the intranet 110 of the device of the host 108, and (ii) to a specific application thereon. Such a mapping allows the key 312 (B) to be mapped to an application endpoint without using a separate application identifier 308. This mapping can be achieved by looking up a network address / application identifier pair in the table, performing a calculation (eg, following an equation, implementing an algorithm, etc.), etc. For example, key 312 (B) can be linked to network address 310 and application identifier 308 in a data structure. An exemplary table in which key 312 (B) is linked to network address 310 and application identifier 308 is further described below with reference to FIG. 6B.

  In another alternative implementation, the code can be embedded in the session identifier 210 field of the session message 302. This code can occupy part of the entire session identifier 210 field. This code can be used to communicate information (eg, data, commands, etc.) from the host 108 to the network gateway element 106 and / or the client 102. The session identifier field of the session message 302 can be populated with the code itself and / or a session identifier 210 created using the code. Client 102 and / or network gateway element 106 can extract this code and utilize the communicated information as is, such as after code mapping (eg, lookup, calculation, etc.).

  FIG. 4 is a flow diagram 400 illustrating an exemplary method for providing routing hints. The flowchart 400 includes seven blocks 402-414. Although the operations of flowchart 400 can be performed in other environments and with various hardware architectures and software schemes, FIGS. 1-3 (and 5) are particularly used to illustrate certain aspects and examples of this method. Is done. For example, the host 108 can perform the operations described.

  At block 402, a client session message is received. For example, the host 108 can receive a client session message 202 or 206 from the client 102 (eg, at the incoming message handler portion 208IC of the message handler 208). At block 404, it is determined whether the received client session message includes a session identifier. For example, a received client session message 202 or 206 (eg, in a format such as session message 302) can be examined to determine if it has a session identifier 210 in the session identifier field.

  If the received client session message includes a session identifier 210, the received client session message is a client session continuation message (SCM) 206 and the method continues at block 412. On the other hand, if the session identifier 210 is not included in the received client session message, the received client session message is a client session start message (SIM) 202 and the method continues at block 406. The

  At block 406, a session identifier is created using the host identifier. For example, the host identifier 214 of the host 108 is used by the session identifier creator 212 to create the session identifier 210. Session identifier creator 212 can insert host identifier 214 into session identifier 210 along with other values.

  At block 408, a host session start message is formulated using the created session identifier. For example, the outgoing message handler portion 208OG can formulate a host session start message 204 populated with a session identifier 210 that includes a host identifier 214 (eg, using a format such as the format of the session message 302). At block 410, a host session start message is sent. For example, the host 108 can send a host session start message 204 to the client 102 via the network 104 and via the network gateway element 106.

  On the other hand, if it is determined (at block 404) that the received client session message includes a session identifier, at block 412 a host session continuation message is formulated using the received session identifier. For example, a host session continuation message (not specifically shown in FIG. 2) in which the outgoing message handler portion 208OG is populated with a received session identifier 210 (which may include a previously embedded host identifier 214). ) Can be formulated (eg, using a format such as the format of session message 302). At block 414, a host session continuation message is sent. For example, the host 108 can send a host session continuation message to the client 102 via the network 104 and via the network gateway element 106.

  FIG. 5 illustrates another exemplary technique for providing and using routing hints with session messages. This exemplary approach focuses on the use of routing hints at the network gateway element 106. As can be seen, clients 102 (1), 102 (2),..., 102 (m) submit messages addressed to NGN network gateway element 106 via network 104.

  The network gateway element 106 routes these requests to the hosts 108 (1), 108 (2),... 108 (n). Each host 108 (1), 108 (2),..., 108 (n) is associated with a respective host identifier 214 (1), 214 (2),. The host identifier 214 can uniquely identify one application endpoint from a set of endpoints to which a particular type of session can potentially be directed, for example.

  In the described implementation, the network gateway element 106 relates to network load balancing. One or more routing policies 508 can be used with network load balancing (or other network gateways with routing functionality). The routing policy 508 can include, for example, a routing policy that allows an administrator to create or set a script to cause the network load balancer to route incoming packets and / or requests in a specified manner. Routing policy 508 may also include more flexible and / or extended routing policies that rely on real-time parameters such as host 108 health and load information.

  A network load balancing implementation of the network gateway element 106 can be realized using integrated network load balancing functionality. This implementation is described with respect to client session continuation message 206 (A) and routing operation 216 (C). A network load balancing implementation of the network gateway element 106 can also be realized using a separate network load balancing functionality. This implementation is described with respect to client session continuation message 206 (B) and routing operation 512.

  In this exemplary network load balancing implementation with isolated functionality, network gateway element 106 includes forwarder 502, classifier 504, and host identifier (HI) to network address (NA) linking table 506. Forwarder 502 forwards packets between client 102 and host 108 using network 104 and intranet 110, respectively. The classifier 504 performs routing operations by classifying packets, requests, connections, etc. in order to achieve network load balancing functionality and / or session affinity preservation functionality.

  Forwarder 502 and classifier 504 may reside and be running on different devices of network gateway 106 or on that single device. Furthermore, each of forwarder 502 and classifier 504 can be distributed across multiple devices. In addition, multiple forwarder 502 components and / or classifier 504 components may be placed on a single network gateway 106. As can be seen, each classifier 504 includes a host identifier-to-network address linking table 506. Alternatively, the network gateway 106 may have only one host identifier to network address linking table 506. The host identifier-to-network address linking table 506 can be located at and / or associated with different functional components.

  In operation of an integrated network load balancing implementation, client 102 (1) sends a client session continuation message 206 (A) over network 104 to network gateway element 106 at address NGN. Client 102 (1) has previously established a session with host 108 (1) and stores session identifier 210 (1) assigned to the previously established session. The session identifier 210 (1) includes the host identifier 214 (1) associated with the host 108 (1). The session identifier 210 (1) is included in the client session continuation message 206 (A).

  In implementations with integrated network load balancing functionality, the network gateway element 106 performs a routing operation 216 (C) for the client session continuation message 206 (A). Since the client session continuation message 206 (A) has a session identifier 210 (1) that includes a host identifier 214 (1), the network gateway element 106 uses the host identifier 214 (1) portion of the session identifier 210 (1). Then, the client session continuation message 206 (A) is routed. In general, network gateway element 106 routes client session continuation message 206 (A) to host 108 (1) using host identifier 214 (1) extracted from session identifier 210 (1).

  Specifically, the network gateway element 106 can insert the host identifier 214 (1) in the destination address field of the packet of the client session continuation message 206 (A) routed to the host 108 (1). This technique is effective when the host identifier 214 (1) includes the network address H1 of the host 108 (1).

  Alternatively, network gateway element 106 can also perform mapping of host identifier 214 (1) to network address H1. For example, a calculation operation or a lookup operation can be performed for such a mapping. For computing operations, the host identifier 214 (1) is mapped to the network address H1 via some formula, algorithm, etc. For lookup operations, the host identifier 214 (1) accesses the host identifier vs. network address table that includes an entry that links the host identifier 214 (1) to the network address H1, such as the host identifier vs. network address linking table 506. , Mapped to the network address H1. An example of such a table is further described below with reference to FIG. 6A.

  In operation of the isolated network load balancing implementation, the client 102 (2) sends a client session continuation message 206 (B) via the network 104 to the network gateway element 106 at address NGN. Client 102 (2) has previously established a session with host 108 (2) and stores a session identifier 210 (2) assigned to the previously established session. The session identifier 210 (2) includes a host identifier 214 (2) associated with the host 108 (2). The session identifier 210 (2) is included in the client session continuation message 206 (B).

  In implementations with isolated network load balancing implementation functionality, forwarder 502 receives client session continuation message 206 (B). Since client session continuation message 206 (B) relates to an unknown session to forwarder 502 (and possibly also to a new connection), forwarder 502 forwards client session continuation message 206 (B) to classifier 504 in communication exchange 510. To do. The client session continuation message 206 (B) has a session identifier 210 (2) that includes a host identifier 214 (2), so that the classifier 504 is the host identifier 214 of the session identifier 210 (2) in the routing operation 512. (2) The portion is used to classify the client session continuation message 206 (B). Also, in communication exchange 510, classifier 504 forwards client session continuation message 206 (B) to forwarder 502 and / or adds a routing entry at forwarder 502, and the message / packet for this session is sent to host 108 ( 2) indicates that it must be transferred.

  Accordingly, classifier 504 and forwarder 502 jointly route client session continuation message 206 (B) to host 108 (2) using host identifier 214 (2) extracted from session identifier 210 (2). . As described above with respect to routing operation 216 (C), forwarder 502 and classifier 504 may (i) insert host identifier 214 (2) in the destination address field and (ii) address network address H2. A mapping (eg, calculation, lookup, etc.) of the host identifier 214 (2) may be performed.

  Host identifier-to-network address linking table 506 has been described as part of classifier 504 or otherwise associated with it. Although the host identifier-to-network address linking table 506 is illustrated as being located at the network gateway element 106, it can instead reside on a different device (eg, a proxy device). A network gateway element 106 having isolated or integrated (eg, network load balancing related) functionality when placed on such a proxy device has access to a host identifier-to-network address linking table 506 therefrom. Can do.

  6A and 6B are exemplary tables 506 (A) and 506 (B) showing the linking of the host identifier 214 and network address 310 used with routing hints. The host identifier to network address linking table 506 (A) generally corresponds to an implementation in which the host identifier 214 is mapped to a device. Host identifier to network address linking table 506 (B) generally corresponds to an implementation in which host identifier 214 is mapped to an application endpoint. However, the host identifier-to-network address linking table 506 (A) can also be mapped to application endpoints as described above with reference to FIG.

  As can be seen, the host identifier to network address linking table 506 (A) links each host identifier 214 to each network address 310. The table 506 (A) includes a plurality of entries 602 (1A), 602 (2A),..., 602 (nA). Each entry 602 (1A), 602 (2A),..., 602 (nA) has a respective host identifier 214 (1), 214 (2),. Addresses 310 (1), 310 (2),..., 310 (n) are included.

  In the described implementation, table 506 (A) includes “n” entries, where n is equal to the number of hosts 108 and each host identifier 214 (1), 214 (2),. (N) corresponds to the key 315 (A) (in FIG. 3). In such an implementation, network addresses 310 (1), 310 (2),..., 310 (n) correspond to host addresses H1, H2,. In operation, the network gateway element 106 accesses the table 506 (A) using the host identifier 214 (#) to locate the associated entry 602 (#A). From the entry 602 (#A), the network address 310 (#) linked to the host identifier 214 (#) routes the client session continuation message 206 (A) or 206 (B) to the host 108 (#). Extracted for use.

  As can be seen, the host identifier-to-network address linking table 506 (B) links each host identifier 214 to each network address 310 and application identifier 308. The table 506 (B) includes a plurality of entries 602 (1B), 602 (2B), 602 (3B),..., 602 (wB). In each respective entry 602 (1B), 602 (2B), 602 (3B),..., 602 (wB), (i) the respective host identifier 214 (1 *), 214 (2 *), 214 (3 *) ),..., 214 (w), and (ii) the respective network addresses 310 (1), 310 (2), 310 (2),. 308 (1), 308 (2), 308 (3),..., 308 (z) are included.

  In the described implementation, table 506 (B) contains “w” entries, where w is equal to the number of application endpoints on host 108 and each host identifier 214 (1 *), 214 (2 * ), 214 (3 *),..., 214 (w) correspond to the key 315 (B) (FIG. 3). For illustration purposes, referring to FIG. 5, the illustrated host identifier to network address linking table 506 (B) may be utilized in the following exemplary situation. Host 108 (1) is associated with host identifier 214 (1 *), has one application corresponding to application identifier 308 (1), and address H1 corresponds to network address 310 (1). Host 108 (2) corresponds to host identifiers 214 (2 *) and 214 (3 *), has two applications corresponding to application identifiers 308 (2) and 308 (3), and address H2 is a network Corresponds to address 310 (2).

  Further, the host 108 (n) corresponds to the host identifier 214 (w), has one application corresponding to the application identifier 308 (z), and the address Hn corresponds to the network address 310 (n). The variable “z” may be equal to the number w of application endpoints where each application identifier 308 is unique to each application installation. On the other hand, if the application identifier 308 is shared between application installations of the same application, z may be less than w.

  FIG. 7 is a flow diagram 700 illustrating an exemplary method for using routing hints. The flow diagram 700 includes eight blocks 702-716. Although the operations of flowchart 700 can be performed in other environments and using various hardware architectures and software schemes, FIGS. 1-3 and 5-6 illustrate certain aspects and examples of this method. Especially used. For example, one or more network gateway elements 106 may perform the operations described.

  At block 702, a client message is received. For example, the network gateway element 106 can receive a client message from the client 102 over the network 104. At block 704, the contents of the received client message are examined. For example, the network gateway element 106 can inspect one or more fields of the session message 302, such as the session identifier 210 field.

  At block 706, it is determined whether the received client message is session related. For example, if the received client message includes a session message 302 having a field for session identifier 210, the received client message is session related. On the other hand, if the received client message does not have a field for session identifier 210, the received client message is not session related and the method continues at block 708.

  At block 708, the received client message is routed using the default policy. For example, the network gateway element 106 may route received client messages using a general routing policy of a routing policy 508, such as a default network load balancing policy. As indicated by dashed arrow 718A, network gateway element 106 can then wait for receipt of the next client message.

  On the other hand, if the received client message is determined to be session related (at block 706), at block 710, the session identifier field is examined. For example, the network gateway element 106 can examine the session identifier field of the received client session message 302. At block 712, it is determined whether the client has specified a session identifier using the session identifier field. For example, the network gateway element 106 can determine whether the session identifier 210 has been entered in the session identifier field of the session message 302.

  If it is determined that the session identifier was not specified (at block 712), then at block 708, the received client session initiation message 202 can be routed using the default policy. On the other hand, if it is determined that the session identifier was specified by the client (at block 712), at block 714, the host identifier is extracted from the specified session identifier. For example, the network gateway element 106 can extract the host identifier 214 from the session identifier 210 specified in the received client session continuation message 206.

  At block 716, the received client message is routed using the extracted host identifier. For example, the received client session continuation message 206 can be routed by the network gateway element 106 to the host 108 associated with the host identifier 214. This routing can include unaltered insertion of the host identifier 214 into the destination field of one or more packets forwarded to the host 108 or mapping of the host identifier 214 to at least one network address 310. This mapping uses the host identifier 214 to look up the network address 310 in the table 506 and perform calculations on the host identifier 214 that yields the network address 310 (eg, according to an equation, implementing an algorithm, etc.) Etc. can be realized.

  Particularly for implementations in which the network gateway element 106 is a network load balancer, the network gateway element 106 may have access to health information and / or load information for multiple hosts 108. This health information and / or load information is used by the destination (eg, host 108 and / or its application endpoint) associated with the extracted host identifier 214 for health and / or load reasons to handle session continuation. You can show that it's not suitable or can't. In that case, the network gateway element 106 may perform the operation of block 708 for default routing policy even when the client 102 specifies a session identifier 210 that includes a host identifier 214.

  After the operation of block 716, the network gateway element 106 may wait for receipt of the next client message, as indicated by the dashed arrow 718B. The network gateway element 106 can route the received client session continuation message 206 using the extracted host identifier 214 in a number of ways depending on the type of the extracted host identifier 214.

  For example, the network gateway element 106 may receive a client session continuation if the host identifier 214 includes a device identifier 306 and an application identifier 308, or if the key 312 (B) is mapped to a device and application on the host 108. The message 206 can be routed directly to the intended application. In addition, the network gateway element 106 can route the received client session continuation message 206 to the affineized host 108 using the network address 310 implementation of the device identifier 306 of the host identifier 214. Where the network address 310 is used as the destination address of one or more routed packets.

  Alternatively, the network gateway element 106 may use the key 312 (A) implementation of the device identifier 306 of the host identifier 214 to look up the network address 310 of the device of the host 108 that has been definitized. For example, key 312 (#) can be used to access table 506 (A) (eg, a data structure) that maps key 312 (A) to host 108 network address 310. An entry 602 (#A) having a key 312 (#) is located in this data structure. The network address 310 (#) linked to the key 312 (#) in the located entry 602 (#A) is extracted and used to route the client session continuation message 206 to the affiliated host 108. .

  Further, the network gateway element 106 uses the device identifier 306 of the host identifier 214 and the application endpoint specific key 312 (B) implementation of the application identifier 308 to identify the network address 310 of the device of the host 108 that has been affiliated and its application. Application identifier 308 can be looked up. For example, the key 312 (#) can be used to access a table 506 (B) (eg, a data structure) that maps the key 312 (B) to an application endpoint of the host 108. An entry 602 (#B) with a key 312 (#) is located in this data structure. The application endpoint (eg, network address 310 (#) and application identifier 308 (#)) linked to the key 312 (#) in the located entry 602 (#B) is extracted and affiliated host 108. Used to route client session continuation message 206 to a specific application on / for a specific device.

  The operations, aspects, features, components, etc. of FIGS. 1-7 are shown in a diagram divided into a plurality of blocks. However, the order, number, arrangement, interconnections, layout, etc., illustrated and / or illustrated in these blocks of FIGS. 1-7 are not intended to be construed as limitations and are arbitrary. One or more systems, methods, devices, procedures, media, application programming interfaces (APIs) of routing hints, in any number of combinations, rearrangements, augmentations, omissions, etc. Device, arrangement, etc. can be implemented. Further, although the description herein includes references to a particular implementation (and the exemplary operating environment of FIG. 8), the illustrated and / or described implementation may be replaced with any suitable hardware, It can be implemented in software, firmware, or a combination thereof using any suitable network organization, transport / communication protocol, client-server architecture, etc.

  FIG. 8 implements (in whole or in part) at least one system, device, apparatus, component, arrangement, protocol, technique, method, procedure, medium, API, combinations thereof, etc. of the routing hints described herein. 2 illustrates an exemplary computing (or general device) operating environment 800 that can be automatically). The operating environment 800 can be utilized in the computer and network architecture described below, or in an independent context.

  The exemplary operating environment 800 is only one example of an environment and limits the scope of use or functionality of the applicable device (computer, network node, entertainment device, mobile device, general electronic device, etc.) architecture. It is not intended to be proposed. Neither should the operating environment 800 (or its device) be interpreted as having any dependency or requirement on any of the components illustrated in FIG.

  Furthermore, routing hints can be implemented using the environment or configuration of many other general purpose or special purpose devices (including computing systems). Examples of well-known devices, systems, environments and / or configurations that may be suitable for use include personal computers, server computers, thin clients, thick clients, personal digital assistants (PDAs) or mobile phones, watches, Handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, video game consoles, game consoles, portable or handheld gaming units, network PCs, minicomputers, mainframe computers, networks Node, distributed computing environment or multi-processing machine containing any of the above systems or devices Computing environment, etc. some combination thereof, these limitations are not.

  Routing hint implementations can be described in the general context of processor-executable instructions. Generally, processor-executable instructions include routines, programs, protocols, objects, interfaces, components, data structures, etc. that perform and / or enable specific tasks and / or implement specific abstract data types. included. The routing hints described herein in an implementation may also be practiced in distributed processing environments where tasks are performed by remote linked processing devices that are connected through a communication link and / or a communication network. In particular, in a distributed computing environment, processor-executable instructions can be located on separate storage media, executed by different processors, and / or propagated through a transmission medium.

  The exemplary operating environment 800 includes a general purpose computing device in the form of a computer 802, and the computer 802 may include all (eg, electronic) devices that have computing / processing capabilities. The components of computer 802 can include, but are not limited to, one or more processors or processing units 804, system memory 806, and system bus 808 that couples various system components including processor 804 to system memory 806. Not done.

  The processor 804 is not limited by the material that forms it or the processing mechanisms used therein. For example, the processor 804 can comprise a semiconductor and / or a transistor (eg, an electronic integrated circuit (IC)). In that context, the processor-executable instructions can be electronically executable instructions. In the alternative, the mechanisms of processor 804 and thus of computer 802 may include, but are not limited to, quantum computing, optical computing, mechanical computing (eg, using nanotechnology), and the like.

  The system bus 808 can include many types of wired or wired, including a memory bus or memory controller, a point-to-point connection, a switching fabric, a peripheral bus, an accelerated graphics port, and a processor bus or local bus that uses any of a variety of bus architectures. Represents one or more of any wireless bus structures. For example, such architectures include the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MCA) bus, the Enhanced ISA (EISA) bus, the Video Electronics Standards Association (VESA) local PC, and the Mezzanine bus. ) Buses, certain combinations of these, and the like.

  Computer 802 typically includes a variety of processor accessible media. Such media can be any available media that can be accessed by computer 802 or another (eg, electronic) device, such as volatile and nonvolatile media, removable and non-removable media, and storage media And transmission media.

  System memory 806 includes processor-accessible storage media in the form of volatile memory, such as random access memory (RAM) 810, and / or non-volatile memory, such as read only memory (ROM) 812. A basic input / output system (BIOS) 814 that contains basic routines that help to transfer information between elements within computer 802, such as during startup, is typically stored in ROM 812. RAM 810 typically contains data and / or program modules / instructions that are immediately accessible and / or currently being manipulated by processing unit 804.

  The computer 802 may also include other removable / non-removable and / or volatile / nonvolatile storage media. For example, FIG. 8 shows a (usually) hard disk drive or disk drive array 816 that reads from and writes to a fixed non-volatile magnetic medium (not shown separately), and (usually) a removable non-volatile magnetic disk 820. Read from and / or write to (usually) a removable non-volatile optical disk 824 such as a magnetic disk drive 818 and a CD, DVD or other optical media (e.g., a "floppy disk") A writing optical disk drive 822 is shown. The hard disk drive 816, magnetic disk drive 818, and optical disk drive 822 are each connected to the system bus 808 by one or more storage media interfaces 826. Alternatively, the hard disk drive 816, magnetic disk drive 818, and optical disk drive 822 can be connected to the system bus 808 by one or more other separate or combined interfaces (not shown).

  The disk drive and associated processor-accessible medium provide computer 802 with non-volatile storage of processor-executable instructions, such as data structures, program modules, and other data. An exemplary computer 802 shows a hard disk 816, a removable magnetic disk 820, and a removable optical disk 824, but a magnetic cassette or other magnetic storage device, flash memory, compact disk (CD), digital versatile disk. (DVD) or other optical storage, RAM, ROM, other types of processor accessible media such as electrically erasable programmable read only memory (EEPROM) can be understood to store instructions accessible by the device. I want. Such media can also include so-called special purpose IC chips or hardwired IC chips. In other words, any processor-accessible medium can be utilized to implement the storage medium of the exemplary operating environment 800.

  Any number of program modules (or other units or sets of instructions / code) may be stored on the hard disk 816, magnetic disk 820, optical disk 824, ROM 812, and / or RAM 810. These program modules may include an operating system 828, one or more application programs 830, other program modules 832, and program data 834 as general examples.

  A user can enter commands and / or information into computer 802 via input devices such as a keyboard 836 and a pointing device 838 (eg, a “mouse”). Other input devices 840 (not specifically shown) may include a microphone, joystick, game pad, satellite dish, serial port, scanner, and / or the like. These and other input devices are connected to the processing unit 804 via an input / output interface 842 coupled to the system bus 808. However, input devices and / or output devices may instead be connected to a parallel port, game port, universal serial bus (USB) port, infrared port, IEEE 1394 (“Firewire”) interface, IEEE 802.11 wireless interface, Bluetooth ( It can be connected by other interfaces such as a registered trademark interface and bus structure.

  A monitor / view screen 844 or other type of display device can also be connected to the system bus 808 via an interface, such as a video adapter 846. Video adapter 846 (or another component) may or may not include a graphics card that handles graphics intensive calculations and handles demanding display requirements. Typically, a graphics card includes a graphics processing unit (GPU), video RAM (VRAM), etc. to facilitate rapid display of graphics and execution of graphics operations. In addition to the monitor 844, other output peripheral devices can include components such as speakers (not shown) and a printer 848 that can be connected to the computer 802 via the input / output interface 842.

  Computer 802 can operate in a networked environment using logical connections to one or more remote computers, such as remote computing device 850. For example, the remote computing device 850 can be a personal computer, portable computer (eg, laptop computer, tablet computer, PDA, mobile station, etc.), palm-sized or pocket-sized computer, watch, game console, server, router, network computer. , A peer device, another network node, or another device type listed above. However, remote computing device 850 is illustrated as a portable computer that can include many or all of the elements and features described herein relative to computer 802.

  The logical connections between the computer 802 and the remote computer 850 are illustrated as a local area network (LAN) 852 and a general wide area network (WAN) 854. Such networking environments include offices, company-wide computer networks, intranets, the Internet, landline and mobile phone networks, ad hoc and infrastructure wireless networks, other wireless networks, gaming networks, certain combinations of these, etc. It is commonplace. Such networks and communication connections are examples of transmission media.

  When implemented in a LAN networking environment, the computer 802 is typically connected to the LAN 852 via a network interface or network adapter 856. When implemented in a WAN networking environment, computer 802 typically includes a modem 858 or other means for establishing communications via WAN 854. The modem 858 can be internal to the computer 802 or external, but can be connected to the system bus 808 via the input / output interface 842 or other suitable mechanism. It should be appreciated that the network connections shown are exemplary and other means of establishing a communications link between computers 802 and 850 can be used.

  In addition, other hardware specifically designed for the server can be used. For example, an SSL acceleration card can be used to offload SSL calculations. In addition, TPC offload hardware and / or packet classifiers on a network interface or network adapter 856 (eg, on a network interface card) can be installed and used on a server device, particularly in a network load balancing operating environment.

  In a networked environment, such as that illustrated with operating environment 800, the program modules or other instructions illustrated for computer 802, or portions thereof, may be stored in whole or in part on a remote media storage device. Can do. For example, the remote application program 860 may reside in a memory component of the remote computer 850, but be usable or otherwise accessible via the computer 802. Also, for illustration purposes, application program 830 and other processor-executable instructions, such as operating system 828, are shown as separate blocks herein, but such programs, components, and other It is understood that the instructions reside at different storage components of computing device 802 (and / or remote computing device 850) at various times and are executed by processor 804 of computer 802 (and / or remote computing device 850). I want to be.

  System, media, device, method, procedure, apparatus, technique, scheme, approach, procedure, arrangement, and other implementation, structural, logical, algorithmic, and functional features and / or diagrams specific terms However, it is to be understood that the invention as defined in the claims is not necessarily limited to the specific features or drawings described. Rather, the specific features and drawings are disclosed as exemplary forms of implementing the claimed invention.

Claims (8)

When executed
An operation of confirming a host identifier from a session identifier field of a session message, the host identifier including an operation including a network address of the host ;
A processor-accessible instruction for instructing a device to perform the operation of routing the packet containing the session message by inserting the network address in a destination field of the packet. recoding media. The operation to check is
The processor-accessible recording medium according to claim 1, further comprising: an operation of extracting the host identifier as a continuous block from the session identifier field of the session message. A device,
At least one processor;
A medium containing processor-executable instructions that can be executed by the at least one processor, the processor-executable instructions comprising:
Receiving a session message having a session identifier including a host identifier , wherein the host identifier includes a network address of the host ;
An apparatus adapted to instruct the apparatus to perform an operation of routing a packet containing the session message by inserting the network address in a destination field of the packet . The action to receive is
Receiving the session message having the session identifier from a client, wherein the session message is associated with a session context associated with a host, and the host is associated with the host identifier. The apparatus according to claim 3 . The processor executable instructions are:
4. The apparatus of claim 3 , wherein the apparatus is adapted to instruct the apparatus to perform a further action of sending the session message from the apparatus based on the routing to a host associated with the host identifier. Equipment. The processor executable instructions are:
An operation of determining whether the received session message includes a received session identifier; and
Routing the received session message according to at least one default routing policy if it is determined that the received session message does not include a received session identifier;
4. The apparatus of claim 3 , wherein the apparatus is adapted to instruct the apparatus to further perform. A network gateway capable of accepting a session message having a session identifier field, wherein the network gateway is adapted to extract a host identifier from a value entered in the session identifier field, wherein the host identifier is Including a network address of a host, wherein the network gateway is further adapted to perform a routing operation of the packet including the session message by inserting the network address in a destination field of the packet. Network gateway. When executed
An operation of confirming a host identifier from a session identifier field of a session message, the host identifier including an operation including a network address of the host ;
A processor-executable instruction for instructing a device to perform the operation of routing the packet containing the session message by inserting the network address in a destination field of the packet ;
The session identifier entered in the session identifier field includes a first portion including the host identifier and a second portion that increases the uniqueness of the session identifier;
The processor-accessible recording medium, wherein the first part is unique across hosts of a given cluster .

Images