EP4144045A1 - Devices and methods for allocating transmission rights in communication networks - Google Patents
Devices and methods for allocating transmission rights in communication networksInfo
- Publication number
- EP4144045A1 EP4144045A1 EP21716705.5A EP21716705A EP4144045A1 EP 4144045 A1 EP4144045 A1 EP 4144045A1 EP 21716705 A EP21716705 A EP 21716705A EP 4144045 A1 EP4144045 A1 EP 4144045A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- client
- node
- transmission permission
- routing
- path
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 150
- 238000004891 communication Methods 0.000 title claims abstract description 110
- 238000000034 method Methods 0.000 title claims description 34
- 230000004044 response Effects 0.000 claims abstract description 36
- 238000004590 computer program Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 235000008694 Humulus lupulus Nutrition 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/78—Architectures of resource allocation
- H04L47/783—Distributed allocation of resources, e.g. bandwidth brokers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/78—Architectures of resource allocation
- H04L47/788—Autonomous allocation of resources
Definitions
- the present disclosure relates to communication networks in general. More specifically, the present disclosure relates to devices and methods for allocating transmission rights in a communication network for transmitting data from a plurality of clients to a server.
- Routing plays an important role in optimizing the overall pipeline of networking as well as computing resources for demanding applications such as real-time multimedia communication or industrial machine remote control.
- a network node for communicating with a plurality of clients over a communication network.
- the communication network comprises a plurality of routing nodes for routing data over the communication network.
- the network node may be, for instance, a server, and the plurality of routing nodes may comprise, for instance, a plurality of network routers and/or network switches in an IP-based communication network.
- the network node is configured to, in response to receiving a first transmission request from a first client of the plurality of clients, transmit a first transmission permission token to the first client, wherein the first transmission permission token is configured to permit the first client to transmit data to the network node along a first path through the communication network.
- the network node is configured to, in response to receiving a second transmission request from a second client of the plurality of clients, transmit a second transmission permission token to a selected routing node of the plurality of routing nodes, wherein the second transmission permission token is configured to permit the second client to transmit data to the network node along a second path through the communication network.
- the selected routing node of the plurality of routing nodes is a joint routing node of the first path and the second path through the communication network.
- the selected routing node of the plurality of routing nodes is one of the routing nodes defining the first path as well as one of the routing nodes defining the second path through the communication network.
- a network node is provided for scheduled routing of data in a communication network in an end-to-end, i.e. , from client to server, manner.
- the selected routing node of the plurality of routing nodes is the joint routing node of the first path and the second path through the communication network that is closest to the second client, e.g. the joint routing node of the first path and the second path with the smallest number of hops to the second client.
- the network node is further configured to, in response to a third transmission request from a third client of the plurality of clients, transmit a third transmission permission token to a further selected routing node of the plurality of routing nodes for permitting the third client to transmit, based on the third transmission permission token, data to the network node along a third path through the communication network.
- the further selected routing node of the plurality of routing nodes is a joint routing node of the second path and the third path through the communication network.
- the network node is further configured to schedule the first transmission permission token and the second transmission permission token to the first client and the second client on the basis of a token scheduling policy, for instance, a "first come first serve" scheduling policy.
- the network node is further configured to receive data from the first client along the first path through the communication network.
- the first transmission permission token comprises at least one of a first token identifier and an address or identifier of the first client.
- the second transmission permission token comprises at least one of a second token identifier and an address or identifier of the second client.
- a method for communicating with a plurality of clients over a communication network comprises a plurality of routing nodes for routing data over the communication network.
- the method comprises the following steps performed by a network node: in response to receiving a first transmission request from a first client of the plurality of clients, transmitting a first transmission permission token to the first client, wherein the first transmission permission token permits the first client to transmit data to the network node along a first path through the communication network; and, in response to receiving a second transmission request from a second client of the plurality of clients, transmitting a second transmission permission token to a selected routing node of the plurality of routing nodes, wherein the second transmission permission token permits the second client to transmit data to the network node along a second path through the communication network, wherein the selected routing node is a joint routing node of the first path and the second path through the communication network.
- a routing node for routing data from a plurality of clients over a communication network to a network node
- the communication network comprises a plurality of routing nodes.
- the routing node is configured to forward a first transmission permission token received from the network node to a first client of the plurality of clients, wherein the first transmission permission token permits the first client to transmit data to the network node along a first path through the communication network.
- the routing node is configured to cache a second transmission permission token received from the network node.
- the routing node is further configured to, in response to receiving information that the first transmission permission token is no longer used by the first client, forward the second transmission permission token to a second client of the plurality of clients, wherein the second transmission permission token permits the second client to transmit data to the network node along a second path through the communication network.
- the routing node is a joint routing node of the first path and the second path through the communication network.
- the routing node is configured to forward the second transmission permission token to the second client, in response to receiving the first transmission permission token from the first client or a request for releasing the first transmission permission token from the first client.
- the routing node is further configured to forward the information that the first transmission permission token is no longer used by the first client to the network node.
- the routing node is further configured to route data from the first client along the first path through the communication network to the network node.
- the first transmission permission token comprises at least one of a first token identifier and an address or identifier of the first client.
- the second transmission permission token comprises at least one of a second token identifier and an address or identifier of the second client.
- the network node is a server of the communication network.
- a method for routing data from a plurality of clients over a communication network to a network node comprises a plurality of routing nodes.
- the method comprises the following steps performed by a routing node of the plurality of routing nodes: forwarding a first transmission permission token received from the network node to a first client of the plurality of clients, wherein the first transmission permission token permits the first client to transmit data to the network node along a first path through the communication network; caching a second transmission permission token received from the network node; and, in response to receiving information that the first transmission permission token is no longer used by the first client, forwarding the second transmission permission token to a second client of the plurality of clients, wherein the second transmission permission token permits the second client to transmit data to the network node along a second path through the communication network, wherein the routing node is a joint routing node of the first path and the second path through the communication network.
- a computer program product comprising program code which causes a computer or a processor to perform the method according to the second aspect or the method according to the fourth aspect, when the program code is executed by the computer or the processor, is provided.
- Fig. 1 shows a schematic diagram illustrating a communication network including a network node according to an embodiment and a routing node according to an embodiment
- Figs. 2 to 7 show the communication network of figure 1 during different stages of exchanging transmission permission tokens between the network node according to an embodiment and the routing node according to an embodiment;
- Fig. 8 shows a flow diagram illustrating different aspects implemented by the network node according to an embodiment and the routing node according to an embodiment
- Fig. 9 shows a flow diagram illustrating a method for communicating with a plurality of clients over a communication network implemented by the network node according to an embodiment
- Fig. 10 shows a flow diagram illustrating a method for routing data from a plurality of clients over a communication network to a network node implemented by routing node according to an embodiment
- Fig. 11 shows a diagram illustrating a further communication network including a network node according to an embodiment and a routing node according to an embodiment.
- a disclosure in connection with a described method may also hold true for a corresponding device or system configured to perform the method and vice versa.
- a corresponding device may include one or a plurality of units, e.g. functional units, to perform the described one or plurality of method steps (e.g. one unit performing the one or plurality of steps, or a plurality of units each performing one or more of the plurality of steps), even if such one or more units are not explicitly described or illustrated in the figures.
- a specific apparatus is described based on one or a plurality of units, e.g.
- a corresponding method may include one step to perform the functionality of the one or plurality of units (e.g. one step performing the functionality of the one or plurality of units, or a plurality of steps each performing the functionality of one or more of the plurality of units), even if such one or plurality of steps are not explicitly described or illustrated in the figures. Further, it is understood that the features of the various exemplary embodiments and/or aspects described herein may be combined with each other, unless specifically noted otherwise.
- Figure 1 shows a schematic diagram illustrating a communication network 100 including a network node 110, in particular a server 110.
- the server 110 is configured to receive data from a plurality of clients 130a-c over the communication network 100.
- the communication network 100 comprises a plurality of routing nodes 120a-f for routing the data over the communication network 100 to the server 110.
- the plurality of routing nodes 120a-f may comprise, for instance, a plurality of network routers and/or network switches connected by communication links, such as L3 links, for supporting an IP-based communication network
- routing node 120a any of the other routing nodes 120b-f, may have the same functionality as the exemplary routing node 120a described in more detail in the following.
- the server 110 may comprise a communication interface, such as a network interface 113 configured to receive one or more data packets from the plurality of routing nodes 112a-f.
- the server 110 may further comprise one or more processors 111 for processing the data and a memory 115 for storing data.
- the exemplary routing node 120a may comprise a communication interface 123a, such as a network interface 123a configured to receive and route one or more data packets within the communication network 100.
- the exemplary routing node 120a may further comprise one or more processors 121a for processing the data and a memory 125a for storing data, such as a routing table.
- the processor 111 of the server 110 and/or the processor 121a of the exemplary routing node 120a may be implemented in hardware and/or software.
- the hardware may comprise digital circuitry, or both analog and digital circuitry.
- Digital circuitry may comprise components such as application-specific integrated circuits (ASICs), field-programmable arrays (FPGAs), digital signal processors (DSPs), or general-purpose processors.
- the memory 115 of the server 110 may be configured to store data and executable program code which, when executed by the processor 111 causes the server 110 to perform the functions, operations and methods described herein.
- the memory 125a of the exemplary network node 120a may be configured to store data and executable program code which, when executed by the processor 121 causes the exemplary routing node 120a to perform the functions, operations and methods described herein.
- the server 110 is configured to, in response to receiving a first transmission request from a first client 130a of the plurality of clients 130a-c, transmit a first transmission permission token 140 to the first client 130.
- the first transmission permission token 140 is configured to permit the first client 130a to transmit data to the server 110 along a first path through the communication network 100.
- the server 110 is configured to, in response to receiving a second transmission request from a second client 130b of the plurality of clients 130a-c, transmit a second transmission permission token 150 to a selected routing node of the plurality of routing nodes 120a-f (which in the embodiment shown in figures 1 to 7 may be the exemplary routing node 120a).
- the second transmission permission token 150 is configured to permit the second client 130b to transmit data to the server 110 along a second path through the communication network 100.
- the selected routing node 120a is a joint routing node of the first path and the second path through the communication network 100.
- the selected routing node 120a of the plurality of routing nodes is one of the routing nodes defining the first path as well as one of the routing nodes defining the second path through the communication network 100.
- the exemplary routing node 120a i.e. the selected routing node 120a being a joint routing node of the first path and the second path through the communication network 100, is configured to forward the first transmission permission token 140 received from the server 110 to the first client 130a.
- the exemplary routing node 120a is configured to cache the second transmission permission token 150 received from the server 110.
- the exemplary routing node 120a is further configured to, in response to receiving information that the first transmission permission token 140 is no longer used by the first client 130a, forward the second transmission permission token 150 to the second client 130b.
- Figures 1 to 7 show the communication network 100 during different stages of exchanging the first transmission permission token 140 and the second transmission permission token 150 between the server 110 according to an embodiment and the plurality of clients 130a-c via the plurality of routing nodes 120a-f, including the exemplary selected routing node 120a according to an embodiment.
- both the first transmission permission token 140 and the second transmission permission token 150 are located at the server 110.
- the first permission token 140 and the second permission token are configured such that a respective client 130a-c holding the respective transmission permission token 140, 150 is permitted, i.e. allowed to transmit data to the server 110.
- the server 110 may be configured to generate the first and the second transmission permission token 140, 150.
- the server 110 receives a first transmission request from the first client 130a for instance, because the first client 130a wants to transmit data to the server 110.
- the server receives this transmission request via a communication path defined by the first base station 135a and the routing nodes 120e, 120a and 120b.
- the server 110 in response to receiving the first transmission request from the first client 130a, the server 110 is configured to transmit the first transmission permission token 140 to the first client 130a for allowing the first client 130a to transmit data to the server. As illustrated in figure 2, the server 110 may have transmitted the first transmission permission token 140 to the first client 130a via the first communication path defined by the first base station 135a and the routing nodes 120e, 120a and 120b.
- the server 110 may receive the second transmission request from the second client 130b via the communication path defined by the second base station 135b and the routing nodes 120f, 120a and 120b, as illustrated in figure 3.
- the server 110 is configured to transmit the second transmission permission token 150 to the selected routing node 120a, because the selected routing node 120a is the is a joint routing node of the first path and the second path through the communication network 100 that is closest to the second client 130b, which is illustrated in figure 4.
- the routing node 120f would be even closer to the second client 130b than the selected routing node 120a, but the routing node 120f is not a joint routing node of the first path and the second path through the communication network 100.
- the server 110 may receive a third transmission request from a third client 130c via a third communication path defined by the third base station 135c and the routing nodes 120f, 120a and 120b, as illustrated in figure 5.
- the server 110 may transmit a third transmission permission token (not shown in the figures) to the further selected routing node 120f for permitting the third client 130c to transmit, based on the third transmission permission token, data to the server 110 along a third path through the communication network 100. Similar to the selected routing node 120a the further selected routing node 120f is that joint routing node of the second path and the third path through the communication network 110 that is closest to the third client.
- the first client 130a may release the first transmission permission token 140 by returning it to the server 110 via the first communication path defined by the defined by the first base station 135a and the routing nodes 120e, 120a and 120b.
- the selected routing node 120a caching the second transmission permission token 150 intended for the second client 130b may forward, as illustrated in figure 7, the second transmission permission token 150 via the routing node 120f and the second base station 135b to the second client 130b.
- the server 110 may forward the first transmission token 140 (for serving the third transmission request by the third client 130c) to the further selected routing node 120f as the joint routing node that is connected to both the second client 130b and the third client 130c and closest to the third client 130c.
- FIG 8 shows a flow diagram illustrating different aspects and processing steps implemented by the exemplary selected routing node 120a according to an embodiment (some of which already have been described in the context of figures 1 to 7).
- a transmission permission token such as the first transmission permission token 140 is received by the selected routing node 120a to be returned to the server 110.
- the exemplary selected routing node 120a is configured to check whether there are any outstanding transmission, i.e. token requests from one of the plurality of clients 130a-c. If this not the case, the token is returned to the server 110 (step 806). Otherwise, the exemplary selected routing node 120a may change the status of the received transmission permission token from "current" to "next" and forward this information to the server 110.
- the exemplary selected routing node 120a may retrieve any client from token response information for the received token identifier (this may be based on a token response table 808). In 809 the exemplary selected routing node 120a may change the status of the token from "next" to "current” and forward it to the client.
- the exemplary selected routing node 120a receives a token response intended for one of the clients 130a-c. In 813 of figure 8 the exemplary selected routing node 120a checks if the response in 811 belongs to the current token. If this is the case, the exemplary selected routing node 120a may store the client address and the token identifier in its memory 125a (step 815) and forward the response to the client (step 817). Otherwise, the exemplary selected routing node 120a may retrieve any interface information from token responses information for the received token identifier (step 819). In step 821 the exemplary selected routing node 120a is configured to check whether the incoming client is on the same interface as the stored token response.
- the exemplary selected routing node 120a may store, in step 810, the incoming client interface information and the token identifier to hold the token response in the token responses table 808.
- the first transmission permission token 140 and the second transmission permission token 150 may be different states, such as "current” and "next", of a transmission permission token.
- the selected routing node 120a receives a "next" state token from the server 110, it will not be sent it down a link, if a client 130a-c along another link is currently holding a "current” state token. Instead, it will be temporarily stored at the selected routing node 120a, until the "current" state token will be released.
- any pending "next" token request may be turned into a "current” token request and forwarded towards the requesting client 130a-c.
- the server 110 is configured to couple the assignment of the transmission right by means of the first transmission permission token 140 and the second transmission permission token 150 with other policies, such as a constraint-based client selection beyond simple bandwidth management or it may choose a random assignment of clients to incoming requests.
- the server 110 is the central coordinator for the handing out of the transmission permission tokens 140, 150.
- the server 110 avoids conflicts in sending and reduces possible congestion and buffer overflow in the selected routing node 120a. Tokens are ultimately sent to clients by router that is closest to server on joint path with current owner. Embodiments disclosed herein allow minimizing the delay in sending those permission tokens to the clients which requested them. In the worst case, the delay may be (max path length - 1) * hop latency, if the second transmission permission token 150 is held at the selected routing node 120a closest to the server 110. In this case delay is still better than a pure server realization. In the best case, the delay may correspond to a one hop latency, i.e. optimal latency, if the second transmission permission token 150 token is held at the selected routing node 120a closest to client 130a-c.
- Embodiments disclosed herein may be implemented using, for instance, the Internet Control Message Protocol (ICMP) or similar protocols.
- the transmission permission tokens could be implemented as bits or bit sequences.
- token information of the "current" and “next” interim token could be done as numbers (with 0 being current, and anything >0 being next in an ordered manner). This allows for easily maintaining more than one "next” token with procedures adjusted accordingly. Moreover, it also allows for granting more than one ‘current’ token (in case the server 110 can process more than one task assigned to the token).
- the strict synchronization through the server 110 may be relaxed.
- the second transmission permission token 150 may be released, when ‘last of flow’ packet is recognized at the selected routing node 120a, instead of AFTER the packet has been fully received (reduces latency by local node reception time). If flow length is known, the second transmission permission token150 may be released while packets of the currently transmitting client are still arriving, using delay estimates obtained, for instance, through telemetry means.
- Figure 9 shows a flow diagram illustrating a method 900 for communicating with the plurality of clients 130a-c over the communication network 100.
- the method 900 comprises the following steps performed by the network node, e.g. server 110: in response to receiving a first transmission request from the first client 130a of the plurality of clients 130a-c, a first step 901 of transmitting the first transmission permission token 140 to the first client 130a, wherein the first transmission permission token 140 permits the first client 130a to transmit data to the network node 110 along a first path through the communication network 100; and, in response to receiving a second transmission request from the second client 130b of the plurality of clients 130a-c, a further step 903 of transmitting the second transmission permission token 150 to the selected routing node 120a of the plurality of routing nodes 120a-f, wherein the second transmission permission token 150 permits the second client 130b to transmit data to the network node, e.g. server 110 along a second path through the communication network 100.
- the selected routing node 120a is
- Figure 10 shows a flow diagram illustrating a method 1000 for routing data from the plurality of clients 130a-c over the communication network 100 to the network node, i.e. server 110.
- the method 1000 comprises the following steps performed by the exemplary selected routing node 120a: a first step 1001 of forwarding the first transmission permission token 140 received from the server 110 to the first client 130a of the plurality of clients 130a-c, wherein the first transmission permission token 140 permits the first client 130a to transmit data to the server 110 along a first path through the communication network 100; a further step 1003 of caching the second transmission permission token 150 received from the server 110; and, in response to receiving information that the first transmission permission token 140 is no longer used by the first client 130a, a further step 1005 of forwarding the second transmission permission token to the second client 130b of the plurality of clients 130a-c, wherein the second transmission permission token 150 permits the second client 130b to transmit data to the server 110 along a second path through the communication network 100.
- the routing node 120a is
- Figure 11 shows a diagram illustrating a further embodiment of the communication network 100 including the network node, e.g. server 110 according to an embodiment and a plurality of routing nodes 120a-f, including the selected routing node 120a according to an embodiment.
- the plurality of clients 130a-n may transmit based on the allocation of the first and the second transmission permission tokens 140, 150 (and possibly further transmission permission tokens) image data via the plurality of routing nodes 120a-f to the network node, e.g. server 110.
- the network node, e.g. server 110 may comprise a buffer for storing this image data, before it is forwarded to a plurality of processing nodes 160a-m for further processing the image data.
- the plurality of processing nodes 160a-m may implement machine learning for further processing the image data received from the network node, e.g. server 110.
- the token assignment implemented by the network node, e.g. server 110 and the selected routing node 120a generates a kind of pipeline of image data being sent (and then pushed for further processing to the processing nodes 160a-m) that requires less network resources than a conventional system, where all clients may transmit simultaneously.
- the processing of the image data in the processing nodes 160a-m is less than the time to receive an image at the network node 110 from any of the clients 130a-n, the number m of required processing nodes is 1.
- the number m of processing nodes will be somewhere between >1 and n (e.g., if the processing takes roughly as long as receiving an image, n processing nodes will be required for processing the n received images). This is due to the unsynchronized nature of the sending of images from the clients to the network node in a conventional system.
- the disclosed system, apparatus, and method may be implemented in other manners.
- the described embodiment of an apparatus is merely exemplary.
- the unit division is merely logical function division and may be another division in an actual implementation.
- a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed.
- the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented by using some interfaces.
- the indirect couplings or communication connections between the apparatuses or units may be implemented in electronic, mechanical, or other forms.
- the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
- functional units in the embodiments of the invention may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units are integrated into one unit.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2021/058657 WO2022207113A1 (en) | 2021-04-01 | 2021-04-01 | Devices and methods for allocating transmission rights in communication networks |
Publications (1)
Publication Number | Publication Date |
---|---|
EP4144045A1 true EP4144045A1 (en) | 2023-03-08 |
Family
ID=75396782
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP21716705.5A Pending EP4144045A1 (en) | 2021-04-01 | 2021-04-01 | Devices and methods for allocating transmission rights in communication networks |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP4144045A1 (en) |
WO (1) | WO2022207113A1 (en) |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7710932B2 (en) * | 2005-12-14 | 2010-05-04 | Motorola, Inc. | Method and apparatus for encouraging routing in a network |
CN109068367B (en) * | 2018-09-29 | 2021-11-19 | 湖南基石通信技术有限公司 | Wireless token passing method, device, equipment and readable storage medium |
-
2021
- 2021-04-01 WO PCT/EP2021/058657 patent/WO2022207113A1/en unknown
- 2021-04-01 EP EP21716705.5A patent/EP4144045A1/en active Pending
Also Published As
Publication number | Publication date |
---|---|
WO2022207113A1 (en) | 2022-10-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP3279487B2 (en) | High-speed data communication modem | |
JP3150624B2 (en) | Communication system and communication path control method | |
JP3577393B2 (en) | High-speed data communication modem | |
US9172550B2 (en) | Management of a multicast system in a software-defined network | |
US20060149840A1 (en) | End-to-end publish/subscribe middleware architecture | |
EP1849092A2 (en) | End-to-end publish/subscribe middleware architecture | |
US6810452B1 (en) | Method and system for quarantine during bus topology configuration | |
US9258336B2 (en) | Dynamic modification of a subscriber connection | |
JP6265058B2 (en) | Network transmission system, its master node, slave node | |
JP6627964B2 (en) | SDN-based ARP implementation method and apparatus | |
JP2003298635A (en) | Source address selection system, router equipment, communication node and source address selection method | |
US6374316B1 (en) | Method and system for circumscribing a topology to form ring structures | |
US20010040896A1 (en) | Method and device for communicating between a first and a second network | |
US6647446B1 (en) | Method and system for using a new bus identifier resulting from a bus topology change | |
US6751697B1 (en) | Method and system for a multi-phase net refresh on a bus bridge interconnect | |
US6910090B1 (en) | Maintaining communications in a bus bridge interconnect | |
CN112838992B (en) | Message scheduling method and network equipment | |
US6584539B1 (en) | Method and system for message broadcast flow control on a bus bridge interconnect | |
CN109788075B (en) | Private network system, data acquisition method and edge server | |
US20200186463A1 (en) | Method and system for name-based in-networking processing | |
CN110661728A (en) | Buffer design method and device combining sharing and privately using in multi-virtual channel transmission | |
CN111106986A (en) | Router with enhanced robustness for controller area networks | |
EP4144045A1 (en) | Devices and methods for allocating transmission rights in communication networks | |
WO2014022424A1 (en) | Phase-based packet prioritization | |
JP4122328B2 (en) | Transmission equipment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20221129 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |