Connection model-based control of concurrent connection count and properties

Patent metadata

Field	Value
Publication number	US-10965762-B2
Application number	US-201715486440-A
Country	US
Kind code	B2
Filing date	Apr 13, 2017
Priority date	Dec 6, 2012
Publication date	Mar 30, 2021
Grant date	Mar 30, 2021

Abstract

A connection request including a connection model key and a partner system attribute of a partner system requesting a connection is received at an application server from the partner system within a distributed system. Using a predefined connection model, a determination is made as to whether the received connection model key and the received partner system attribute respectively match a configured connection model key and a configured authorized partner system attribute within the predefined connection model. A logical connection is created that includes a first unique connection name derived from the received partner system attribute in response to determining that the received connection model key and the received partner system attribute match the respective configured connection model key and the configured authorized partner system attribute within the predefined connection model.

First claim

What is claimed is:

1. A method, comprising:
by an application server that self-regulates creation of new shared logical connections operative over a single physical connection within a distributed system:
receiving, from a partner system, a connection request comprising (i) a connection model key and (ii) a partner system attribute of the partner system requesting a connection;
determining, using a predefined connection model, whether the received connection model key and the received partner system attribute respectively match a configured connection model key and a configured authorized partner system attribute within the predefined connection model, wherein the predefined connection model comprises a connection namespace field limitation that limits a number of created unique connection names;
enforcing a limit on a number of multiplexed logical connections to the application server over the single physical connection from partner systems that share the partner system attribute using the connection namespace field limitation within the predefined connection model;
creating a logical connection over the single physical connection that comprises a first unique connection name derived from the received partner system attribute, where creating the logical connection is in response to determining that the received connection model key and the received partner system attribute match the respective configured connection model key and the configured authorized partner system attribute within the predefined connection model; and
denying at least one additional connection request in response to determining, based upon the connection namespace field limitation that limits the number of created unique connection names and previously-created connection names, that the limit on the number of multiplexed logical connections to the application server over the single physical connection from the partner systems that share the partner system attribute has been reached.

2. The method of claim 1 , where creating the logical connection over the single physical connection that comprises the first unique connection name derived from the received partner system attribute comprises the application server:
concatenating the received partner system attribute and a next available connection number to form the first unique connection name.

3. The method of claim 1 , further comprising the application server:
receiving a request to terminate a multiplexed logical connection from one of the partner systems;
terminating the multiplexed logical connection to the one of the partner systems requesting the termination of the multiplexed logical connection; and
reusing a connection name used by the terminated multiplexed logical connection for a new multiplexed logical connection in response to a new connection request comprising the connection model key and the partner system attribute.

4. The method of claim 1 , where:
the predefined connection model authorizes a plurality of specific partner system instances to connect concurrently over the single physical connection using the predefined connection model via the partner system attribute; and
further comprising the application server enforcing connection authorization of multiplexed logical connections to the application server over the single physical connection using the configured authorized partner system attribute within the predefined connection model.

5. The method of claim 1 , where the partner system attribute comprises a partner system cluster application instance identifier.

6. A system, comprising:
a memory; and
a processor programmed to execute an application server that self-regulates creation of new shared logical connections operative over a single physical connection within a distributed system, the processor being programmed to:
receive, from a partner system, a connection request comprising (i) a connection model key and (ii) a partner system attribute of the partner system requesting a connection;
determine, using a predefined connection model stored within the memory, whether the received connection model key and the received partner system attribute respectively match a configured connection model key and a configured authorized partner system attribute within the predefined connection model, wherein the predefined connection model comprises a connection namespace field limitation that limits a number of created unique connection names;
enforce a limit on a number of multiplexed logical connections to the application server over the single physical connection from partner systems that share the partner system attribute using the connection namespace field limitation within the predefined connection model;
create, in response to determining that the received connection model key and the received partner system attribute match the respective configured connection model key and the configured authorized partner system attribute within the predefined connection model, a connection that comprises a first unique connection name derived from the received partner system attribute; and
deny at least one additional connection request in response to determining, based upon the connection namespace field limitation that limits the number of created unique connection names and previously-created connection names, that the limit on the number of multiplexed logical connections to the application server over the single physical connection from the partner systems that share the partner system attribute has been reached.

7. The system of claim 6 , where in being programmed to create, in response to determining that the received connection model key and the received partner system attribute match the respective configured connection model key and the configured authorized partner system attribute within the predefined connection model, the connection that comprises the first unique connection name derived from the received partner system attribute, the processor is programmed to:
concatenate the received partner system attribute and a next available connection number to form the first unique connection name.

8. The system of claim 6 , where:
the predefined connection model authorizes a plurality of specific partner system instances to connect using the predefined connection model via the partner system attribute; and
the processor is further programmed to enforce connection authorization of multiplexed logical connections to the application server using the configured authorized partner system attribute within the predefined connection model.

9. The system of claim 6 , where the partner system attribute comprises a partner system cluster application instance identifier.

10. The system of claim 6 , where the processor is further programmed to:
receive a request to terminate a multiplexed logical connection from one of the partner systems;
terminate the multiplexed logical connection to the one of the partner systems requesting the termination of the multiplexed logical connection; and
reuse a connection name used by the terminated multiplexed logical connection for a new multiplexed logical connection in response to a new connection request comprising the connection model key and the partner system attribute.

11. A computer program product, comprising:
a computer readable storage device having computer readable program code embodied therewith, where the computer readable program code when executed on a computer implemented as an application server that self-regulates creation of new shared logical connections operative over a single physical connection within a distributed system causes the computer to:
receive, from a partner system, a connection

Assignees

• IBM

Inventors

• Allen Gerald M W
• Brooks Michael D
• Wakelin Philip I

Classifications

• H04L67/1023 Primary

  based on a hash applied to IP addresses or costs · CPC title

• H04L63/101

  Access control lists [ACL] · CPC title

• H04L67/141 Primary

  Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70) · CPC title

• H04L63/08

  for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title

• H04L63/10

  for controlling access to devices or network resources · CPC title