Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L45/00—Routing or path finding of packets in data switching networks
  • H04L45/74—Address processing for routing
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04J—MULTIPLEX COMMUNICATION
  • H04J3/00—Time-division multiplex systems
  • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
  • H04J3/1605—Fixed allocated frame structures
  • H04J3/1623—Plesiochronous digital hierarchy [PDH]
  • H04J3/1629—Format building algorithm
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04J—MULTIPLEX COMMUNICATION
  • H04J3/00—Time-division multiplex systems
  • H04J3/24—Time-division multiplex systems in which the allocation is indicated by an address the different channels being transmitted sequentially
  • H04J3/247—ATM or packet multiplexing
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L43/00—Arrangements for monitoring or testing data switching networks
  • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
  • H04L43/0852—Delays
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L43/00—Arrangements for monitoring or testing data switching networks
  • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
  • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
  • H04L43/0894—Packet rate
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L43/00—Arrangements for monitoring or testing data switching networks
  • H04L43/16—Threshold monitoring
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L45/00—Routing or path finding of packets in data switching networks
  • H04L45/24—Multipath
  • H04L45/245—Link aggregation, e.g. trunking
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L45/00—Routing or path finding of packets in data switching networks
  • H04L45/66—Layer 2 routing, e.g. in Ethernet based MAN's
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L45/00—Routing or path finding of packets in data switching networks
  • H04L45/74—Address processing for routing
  • H04L45/742—Route cache; Operation thereof
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L2101/00—Indexing scheme associated with group H04L61/00
  • H04L2101/60—Types of network addresses
  • H04L2101/604—Address structures or formats
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L2101/00—Indexing scheme associated with group H04L61/00
  • H04L2101/60—Types of network addresses
  • H04L2101/618—Details of network addresses
  • H04L2101/622—Layer-2 addresses, e.g. medium access control [MAC] addresses
• • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
  • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
  • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
  • Y02D30/00—Reducing energy consumption in communication networks
  • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Definitions

• time division multiplexing was limited in several ways.
• Figure 1 shows a bright line separation of user data from data transport and network control according to an embodiment.
• Figure 2 shows a diagram of hierarchical core network tiers using SAIN technology according to an embodiment.
• Figure 6.2 shows forwarding switches in a SAIN architecture according to an embodiment.
• Figure 13-1 shows a fixed length control vector with m-Bit cellet messages (data only) according to an embodiment.
• a circuit-based network is called a Network and a packet-based network is called a P-Network; 2) a circuit- based switch is called a C-Switch; a packet-based switch is called a P-Switch, such as an Ethernet 'switch' ; and 3) a circuit-based frame is called a C-Frame; a packet-based frame (such as an Ethernet frame) is called a P-Frame.
• a network based on SAIN principles can carry data packets and other forms of communication from one node to another in a universally applicable circuit-based format. Switching in a SAIN network uses small data elements call cellets that are placed in space/time division frames. The position of each cellet within a frame defines the connection to which the cellet belongs. [This method of forwarding data connections is called implicit addressing.]
• Control Vectors described below, as unique system objects that can support specific functionality disclosed in this application.
• Synchronized State Objects A semantic connection of two objects with states synchronized to one another can control one or a plurality of system processes. The objects including their space/time synchronized states can define a new disjoint object.
• a Control Vector (disclosed in detail below) can accomplish the synchrony of states by sending one or a plurality of messages over a communication facility between source and destination objects.
• No Network object can cause a state within another object to change without using a CV or equivalent method to connect an object pair.
• CVs or equivalents affecting object connectivity can be under the sole control of a SAIN source object within the operational boundary of a SAIN Network.
• a cellet is a quantum of forwarded traffic within a trunk or link that can be as large as many bytes and as small as one bit. The choice of the quantum size need not be network- wide; it is local in a semantic sense of connected object pairs.]
• Each CID does not need to exist in perpetuity.
• Each CID prepended packet represents a connection that has been sent relatively recently over a forwarding connection.
• a mechanism is needed to control the size of a local CID cache. This can assure that a CID that appeared in the distant past can be flushed from the local system so that a new different packet can use the same CID numeral.
• the mechanism disclosed herein is called a Connection Time to Live (CTTL) method.
• CTTL value disclosed herein, can be assigned to each current CID within any CID cache in a Network. The purpose of a CTTL is quite different from a Time to Live (TTL) value common in router-based P-Network s.
• TTL Time to Live
• a novel way determine the likelihood of a new packet being one that has been recently transmitted before insofar as addressing and other static parts of packets.
• a SAIN network can use Control Vectors (CVs) to send control messages within and between network nodes.
• CVs can establish and adjust parameters associated with a logical connection that controls a physical connection or a physical action.
• the structure of a CV depends on its particular application as described below. In general, the definition of a CV includes but is not limited to the following:
• the parameters for each Control Vector 800 in such a CV Sub-Channel Frame 813 can have the same format except for the length of the Control Vector 800.
• a CV CoS can include a plurality of (disjoint) routes between CV node pairs.
• a CV can send two (or more) CV copies over the plurality of CV routes.
• a CV CoS route can use methods disclosed below.
• the algorithm that causes the interleaving has an algorithm that returns the corrected segment to its initial state.
• the SAIN multiplexing algorithm making use of cellets that contain a single bit can result in automatically interleaved data so that an independent interleaving /
• deinterleaving operations are not required.
• the result is simplification and, more importantly, does not add delay to the data transport process.
• Fig. 13-3 and Fig. 13-4 illustrates the following:
• a Type 2 SCV2 can represent a plurality of changes less than or equal to the C-Frame length.
• An alternative is a CCV with a bit vector that shows the plurality of positions requiring change.
• a Point-to-Point connection begins with a User Source Data Port 291 connected to an Ingress NIC 211 in a Source E-Node 201. Attached to the Ingress NIC 211 is an Ingress E-Node Controller 221.
• a two-point Path Aggregation Link 710 connection between a Path Aggregation Switch 511 and a Path Disaggregation Switch 512 The number of connections in the path can be large, but is divisible into disjoint partitions. A partition number and a short connection object number within the partition can identify each connection.
• T-Node 301 can forward this information to each of its Source E-Nodes 201 thereby assuring that no bandwidth commitment occurs when the required bandwidth does not exist. [A number of scenarios can minimize the occurrence of this event within the core network. The largest vulnerability resulting in lack of available bandwidth can occur in an E-Node-to-T-Node Trunk 231 or a T-Node-to-E-Node Trunk 322. A service provider must feel responsible for keeping bandwidth available in these trunks "ahead of the curve”.]
• a network or data center can partition a network into virtual VLAN/VPNs using addresses that can be as large as desired.
• a CID can add a VLAN/VPN address to the identification of a connection. The address can limit its use to port numbers, MAC addresses, and additional information such as person
• connection space For a large VLAN or VPN, a partition or sub-partitions of connection space could be appropriate. Used properly with proper administrative procedures can enhance network security.
• a SAIN network does not require adopting industry standards for data forwarding.
• Currently installed networks such as RSI and Carrier Ethernet could be a Physical Layer surrogate in supporting the SAIN transport protocol. Doing so would not result in some of the delay and bandwidth utilization benefits of a SAIN network using basic Physical Layers. Nevertheless, it would allow existing networks to make use of many SAIN benefits other than assuring SAIN's lowest possible delay.
• Running the algorithm in A Preferred Method of Discovering Loop-Free Routes in a Mesh Network beginning at paragraph [0050] can enable the system to choose a route through a network that meets user requirements.
• the chosen route can be a list of successive hops through which a connection passes.
• a Source T-Node 301, T3 there is a CrossConnect Switch 570 for each Destination T-Node 302 in the network.
• the CrossConnect Switches 570 handle all L2 Aggregation Superpaths 720 generated by each Source E-Node 201 child of the Source T-Node 301 parent.
• Each CrossConnect Switch 570 handles those L2 Aggregation Superpaths 720 that pass through one of the Destination T-Nodes 302 on their way to its Destination E-Node 202 children.
• the outputs from a CrossConnect Switch 570 are L2
• Each of the terminating L2 Aggregation Superpaths 720 contains a plurality of Destination Paths 712 each of which originated as a Source Path 711 in each of the children of the Source T-Node 301.
• Destination T-Node 302 exist within L2 Aggregation Superpaths 720 routed among the T-Nodes 300. [Routes can exist for multi-point connections where routes consist of subsets of Point-to-Point connections can originate and terminate through multiple T-Nodes 300. These embodiments are included in other applications.]
• a Source T-Node Controller 371 can control traffic either originating or passing through the Source T-Node 301. In this case, the controller chooses Gate 550 labeled "G3".
• Source-to-Destination TT-Trunks 351 connect the Source T-Node 301 to other neighboring nodes. These five Source-to-Destination TT-Trunks 351 handle all outgoing traffic leaving the Source T-Node 301. This includes traffic from all CrossConnect Switches 570 in addition to transit traffic from other T-Nodes 300 and possible traffic generated within the Source T-Node 301 such as Control Vectors.
• CrossConnect Switch 570 is a single data stream insofar as functionality exists with a Source T-Node 301.
• L2 Aggregation Superpaths 720 disaggregate from an L3 Aggregation
• Each Disaggregation Forwarding Switch 542 in a Forwarding T-Node 303 has a similar structure to an L3 Aggregation Switch 531 that is the source of a route in a Source T-Node 301.
• Each Disaggregation Forwarding Switch 542 has a number of Gates 550 equal to the number of Aggregation Forwarding Switches 541 in a Forwarding T-Node 303.
• Each Aggregation Forwarding Switch 541 can have a number of Gates 550 equal to the number of Disaggregation Forwarding Switches 542 in Forwarding T-Node 303.
• the Gates 550 in a Forwarding T-Node 303 are set for each link that passes through the node.
• L3 Aggregation Switches 531 are trunk-like since they are not part of an aggregation. They become link-like in an Aggregation Forwarding Switch 541 since such a C-Switch aggregates a plurality of the Source L3 Aggregation Superpath 731 from the L3 Aggregation Switches 531. [Not shown explicitly in Fig. 5d of RSI, but implied, are greyed- out stubs entering the Aggregation Forwarding Switches 541.] A substantially larger number of Point-to-Point Level 2 aggregations are possible in an Aggregation Forwarding Switch 541 / Disaggregation Forwarding Switch 542. In the model network, there are Point-to-Point connections among T-Nodes 300.
• Forwarding connections can make use of FIFO buffers at the ingress connection to a Source L3 Aggregation Superpath 731, Source L4 Aggregation Superpath 741, or a Destination L4 Disaggregation Superpath 742 connection.
• the reason for the buffers is the possible timing difference between network components.
• a SAIN network can operate with four levels of data aggregation. These are:
• Level 1 This path level aggregates user connections and logically involves a single hop route between a Source E-Node 201 and Destination E-Node 202 pair.
• Level 2 This level aggregates Level 1 connections and logically involves two hop routes between Source E-Nodes 201 and Destination E-Nodes 202.
• the first hops are between L2 Source Aggregation Switches 521 in a Source E-Node 201 and L2 Disaggregation Switches 522 within each CrossConnect Switch 570 C-Switch in the parent Source T-Node 301 of the Source E-Node 201.
• the second hops are between L2 Source Aggregation Switches 521 in the CrossConnect Switches 570 and L2 Disaggregation Switches 522 in each Destination E-Node 202.
• Level 3 This level aggregates Level 2 connections and logically involves three hop routes between Source E-Node 201 and Destination E-Node 202 pair. The first hop is between an L3 Aggregation Switch 531 in a Source E-Node 201 and its parent Source
• T-Node 301 It aggregates all Source L2 Aggregation Superpath 721 generated in the Source E-Node 201.
• the L3 Disaggregation Switch 532 all Destination L2 Disaggregation
• the second hops are between L3 Aggregation Switches 531 that aggregate Source L2 Aggregation Superpaths 721 from the CrossConnect Switches 570 and matching L3 Disaggregation Switch 532 in Destination T-Nodes 302.
• the third hops are between the L3 Aggregation Switches 531 in the Destination T-Nodes 302 that connect to each of the network's Destination E- Nodes 202.
• Level 4 This level aggregates all Level 3 routes created by
• the two hops for each L2 Aggregation Superpath 720 involve a CrossConnect Switch 570.
• the bandwidths of Path Aggregation Links 710 require synchronization through a CrossConnect Switch 570. This can involve implementation of Control Vectors from an L2 Source Aggregation Switch 521 to two L2 Disaggregation
• the Control Vector for the L2 Disaggregation Switch 522 in the CrossConnect Switch 570 can support the L2 Source Aggregation Switch 521 in the CrossConnect Switch 570 concomitantly. As shown in the figures, the sum of the bandwidth of Source L2 Aggregation Superpaths 721 leaving a CrossConnect Switch 570 is equal to sum of the bandwidth of all Destination
• E-Nodes 202 may not apply to networks involving multipoint connections.
• the third hop for point-to-point connections from a Destination T-Node 302 to a Destination E-Node 202 is similar to the first with one major exception.
• the plurality of Destination L2 Disaggregation Superpaths 722 originates in a different Source E-Node 201.
• the method of adding a connection can take place at each of the aggregation levels.
• a new connection can take place by assigning a new connection to an unused position in a Switch Stack Selector 120 within a Source E-Node 201 and a Destination E-Node 202.
• This connection can have no effect on an L2 Aggregation Superpath 720 in which the connection exists except for its possible effect on the bandwidth of the L2 Aggregation Superpath 720.
• a new connection can take place when a new T-Node 300 becomes a part of a network.
• a new position on each L2 Source Aggregation Switch 521and L2 Disaggregation Switch 522 in the network that will support traffic involving the new T-Node. It is possible for security reasons to add such positions only to those nodes with connections requiring access. Even with the addition of a new T-Node 300 with physical access from every E-Node 200 in a network, careful addition and surveillance of VLAN and VPN capability can provide similar benefits to disallowing access from certain E-Nodes 200 and/or T-Nodes 300.
• a suitable method to change a connections bandwidth is as follows:
• Fig. 20 (b) shows the same "E" cellets whose first position is at position 28 in the Connection Domain.
• the "E" cellets are no longer equally spaced, but they remain in the same positions in the 4 C-Frame partitions.
• the cellets represent two baseband four-cellet QDR's combined into a single subframe.
• the lesson learned from the two figures is that two disjoint subframe connections are viewable as one larger connection. From an apparatus point of view this enables the following:
• the method can use an "OR" gate to combine two "AND” gate outputs from a "C"-like and an "E"-like positions in a Switch Stack Selector 120.
• the method can apply to any plurality of Switch Stack Selector 120 outputs. In operation, there can be a Destination Switch Stack Selector 122 synchronized to a Source Switch Stack Selector 121 using Control Vectors 800. There can also be multiple hops for multipoint connections using the same technique.
• Fig. 20 (e) and (f) illustrate an extremely important point of the process method disclosed herein thus far.
• the "C", "F”, and “E” connections are not rooted on a Power- of-Two boundary.
• combining disjoint connections can include any combination of Power-of-Two connections into a larger integer multiple of a Base Bandwidth QDR'.
• a large C-Frame can split into a plurality of subframe partitions, each of which can use a Base Bandwidth independent of another.
• Each T-Node 300 contains a T-Node Master Clock 380 to which all aggregation and disaggregation C-Switches can be synchronized.
• the C-Switches include, but are not limited to Path A/D Switches 510, L2 A/D Switches 520, L3 A/D Switches 530, and L4 A/D Switches 540.
• the E-Node Master Source Clock 281 can synchronize all clocked objects in the Source E-Node 201 partition in the E-Node 200.
• the E-Node Master Destination Clock 282 can synchronize all clocked objects in the Destination E-Node 202.
• the goal of the method is to cause data and Control Vector signals from all Source E-Nodes 201 connected to the parent T-Node 300 to be in phase with the T-Node Master Clock 380 with a small amount of time ahead of T-Node processing required to forward data and Control Vector signals to other T-Nodes 300.
• a time stamp length (in bits) needs to be large enough to meet delay variations between routes that interconnect T-Nodes 300, but not larger.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Environmental & Geological Engineering (AREA)
• Computer Hardware Design (AREA)
• Data Exchanges In Wide-Area Networks (AREA)

Priority Applications (2)

Applications Claiming Priority (4)

Publications (1)

Family

ID=49117415

Family Applications (1)

Country Status (4)

Cited By (2)

Families Citing this family (15)

Citations (5)

Family Cites Families (38)

• 2013
  • 2013-03-08 KR KR20147026876A patent/KR20150002622A/ko not_active Application Discontinuation
  • 2013-03-08 WO PCT/US2013/030040 patent/WO2013134732A1/en active Application Filing
  • 2013-03-08 US US13/791,709 patent/US9137201B2/en not_active Expired - Fee Related
  • 2013-03-08 EP EP13758304.3A patent/EP2823621A4/de not_active Withdrawn
• 2015
  • 2015-09-11 US US14/851,660 patent/US20160173375A1/en not_active Abandoned
• 2017
  • 2017-03-17 US US15/462,377 patent/US20170195224A1/en not_active Abandoned
  • 2017-10-09 US US15/728,273 patent/US20180176131A1/en not_active Abandoned

Patent Citations (5)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events