WO2019158964A1 - Policy based function callbacks for a server - Google Patents
Policy based function callbacks for a server Download PDFInfo
- Publication number
- WO2019158964A1 WO2019158964A1 PCT/IB2018/050874 IB2018050874W WO2019158964A1 WO 2019158964 A1 WO2019158964 A1 WO 2019158964A1 IB 2018050874 W IB2018050874 W IB 2018050874W WO 2019158964 A1 WO2019158964 A1 WO 2019158964A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- function
- server program
- server
- callbacks
- nodes
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
Definitions
- the clients will be provided with the policy table along with a brief summary of the function callback itself and hence client side socket connections will bind to a port in accordance with the function or functions they want to execute at the server side.
- a hash table consisting of compute node Internet Protocol (IP) address where the server program is running, process identifier of the server program and client side port number from the policy table as the key and the value as list of storage nodes that will serve the storage access requests for the socket connections in the server program with client side port number as specified in the key of the hash table.
- IP Internet Protocol
Abstract
Let us consider a cloud with switching nodes, compute nodes and storage nodes. There will be a server program running on the compute node which will listen to a port depending upon the protocol used for communication with the client and accept new connection requests. There will be a policy table with each entry having client side port number as the key and the function callback or chain of function callbacks as the value per server program.
Description
Policy based function callbacks for a server
Let us consider a cloud with switching nodes, compute nodes and storage nodes. There will be a server program running on the compute node which will listen to a port depending upon the protocol used for communication with the client and accept new connection requests. There will be a policy table with each entry having client side port number as the key and the function callback or chain of function callbacks as the value per server program. The server program will look up at the policy table to register a function callback or a chain of function callbacks for a socket connection when packets arrive at the server side socket and also a function callback or a chain of function callbacks can be registered when packets are sent from the server side socket. The clients will be provided with the policy table along with a brief summary of the function callback itself and hence client side socket connections will bind to a port in accordance with the function or functions they want to execute at the server side. Also in addition we may maintain a hash table consisting of compute node Internet Protocol (IP) address where the server program is running, process identifier of the server program and client side port number from the policy table as the key and the value as list of storage nodes that will serve the storage access requests for the socket connections in the server program with client side port number as specified in the key of the hash table.
Claims
1. Let us consider a cloud with switching nodes, compute nodes and storage nodes. There will be a server program running on the compute node which will listen to a port depending upon the protocol used for communication with the client and accept new connection requests. There will be a policy table with each entry having client side port number as the key and the function callback or chain of function callbacks as the value per server program. The server program will look up at the policy table to register a function callback or a chain of function callbacks for a socket connection when packets arrive at the server side socket and also a function callback or a chain of function callbacks can be registered when packets are sent from the server side socket. The clients will be provided with the policy table along with a brief summary of the function callback itself and hence client side socket connections will bind to a port in accordance with the function or functions they want to execute at the server side. Also in addition we may maintain a hash table consisting of compute node Internet Protocol (IP) address where the server program is running, process identifier of the server program and client side port number from the policy table as the key and the value as list of storage nodes that will serve the storage access requests for the socket connections in the server program with client side port number as specified in the key of the hash table. The above novel technique by which we can just plug in different functions in a server program in the cloud to serve different clients is the claim for this invention.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/IB2018/050874 WO2019158964A1 (en) | 2018-02-13 | 2018-02-13 | Policy based function callbacks for a server |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/IB2018/050874 WO2019158964A1 (en) | 2018-02-13 | 2018-02-13 | Policy based function callbacks for a server |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019158964A1 true WO2019158964A1 (en) | 2019-08-22 |
Family
ID=67618944
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/IB2018/050874 WO2019158964A1 (en) | 2018-02-13 | 2018-02-13 | Policy based function callbacks for a server |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2019158964A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114048239A (en) * | 2022-01-12 | 2022-02-15 | 树根互联股份有限公司 | Storage method, query method and device of time series data |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003281109A (en) * | 2002-03-26 | 2003-10-03 | Hitachi Ltd | Load distribution method |
WO2011079149A2 (en) * | 2009-12-23 | 2011-06-30 | Citrix Systems, Inc. | Systems and methods for listening policies for virtual servers of an appliance |
CN102801819A (en) * | 2012-07-17 | 2012-11-28 | 杭州华三通信技术有限公司 | Method for passing through IPv6 addresses in network access control system |
-
2018
- 2018-02-13 WO PCT/IB2018/050874 patent/WO2019158964A1/en active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003281109A (en) * | 2002-03-26 | 2003-10-03 | Hitachi Ltd | Load distribution method |
WO2011079149A2 (en) * | 2009-12-23 | 2011-06-30 | Citrix Systems, Inc. | Systems and methods for listening policies for virtual servers of an appliance |
CN102801819A (en) * | 2012-07-17 | 2012-11-28 | 杭州华三通信技术有限公司 | Method for passing through IPv6 addresses in network access control system |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114048239A (en) * | 2022-01-12 | 2022-02-15 | 树根互联股份有限公司 | Storage method, query method and device of time series data |
CN114048239B (en) * | 2022-01-12 | 2022-04-12 | 树根互联股份有限公司 | Storage method, query method and device of time series data |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9485183B2 (en) | System and method for efectuating packet distribution among servers in a network | |
US9813344B2 (en) | Method and system for load balancing in a software-defined networking (SDN) system upon server reconfiguration | |
US11683401B2 (en) | Correlating packets in communications networks | |
JP6721166B2 (en) | System and method for distributed flow state P2P configuration in virtual networks | |
EP3281369B1 (en) | Server load balancing | |
CN107948076B (en) | Method and device for forwarding message | |
KR101664922B1 (en) | System and Method for Distribution of Policy Enforcement Point | |
US20180241664A1 (en) | Flow routing system | |
JP2018525935A5 (en) | ||
US9807016B1 (en) | Reducing service disruption using multiple virtual IP addresses for a service load balancer | |
US20160150043A1 (en) | Source ip address transparency systems and methods | |
US10326712B2 (en) | Multicast data packet forwarding | |
WO2017050117A1 (en) | Network load balance processing system, method, and apparatus | |
US20160380986A1 (en) | Communicating private data and data objects | |
WO2015096149A1 (en) | Tcp link configuration method, apparatus and device | |
Nakasan et al. | A simple multipath OpenFlow controller using topology‐based algorithm for multipath TCP | |
US20180307523A1 (en) | Network function virtualization (nfv) parameter trust in data communication systems | |
US9667543B2 (en) | Routing requests with varied protocols to the same endpoint within a cluster | |
US20180091446A1 (en) | Packet forwarding | |
US20160323371A1 (en) | Methods and apparatus for load balancing in a network | |
WO2019158964A1 (en) | Policy based function callbacks for a server | |
US20160352637A1 (en) | Client-based port filter table | |
JP2014093642A (en) | High-speed distribution method to session border controller, and connection system | |
WO2012159493A1 (en) | Instant messaging system and method for sharing user information | |
US20070147376A1 (en) | Router-assisted DDoS protection by tunneling replicas |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18906125 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18906125 Country of ref document: EP Kind code of ref document: A1 |