US20050190775A1 - System and method for establishing service access relations - Google Patents
System and method for establishing service access relations Download PDFInfo
- Publication number
- US20050190775A1 US20050190775A1 US10/503,183 US50318305A US2005190775A1 US 20050190775 A1 US20050190775 A1 US 20050190775A1 US 50318305 A US50318305 A US 50318305A US 2005190775 A1 US2005190775 A1 US 2005190775A1
- Authority
- US
- United States
- Prior art keywords
- service
- user
- access
- handler
- ethernet
- 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.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
- H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
- H04L12/2858—Access network architectures
- H04L12/2861—Point-to-multipoint connection from the data network to the subscribers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
- H04L12/2869—Operational details of access network equipments
- H04L12/287—Remote access server, e.g. BRAS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
- H04L12/4645—Details on frame tagging
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
- H04L12/467—Arrangements for supporting untagged frames, e.g. port-based VLANs
-
- 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
Definitions
- the present invention relates to a multiservice Ethernet access system and methods of establishing service access relations in the system.
- Ethernet has been developed mainly as a LAN (Local Area Network) technology, aiming to provide an efficient infrastructure for data networks within a company. Originally it was developed for moderate speed shared media, but current technology applies mainly to point-to-point links up to 10 Gbit/s, interconnected by high capacity Ethernet switches, supporting virtual LAN, VLAN, as described in the standard IEEE 802.1q.
- a virtual LAN is a group of system, such as computers in a workgroup, that need to communicate with each other, and protocols that restrict the delivery of VLAN frames to members of the VLAN.
- a LAN can be partitioned into multiple VLAN:s, where each VLAN is assigned a number called a VLAN identifier that identifies it uniquely within the LAN.
- a LAN contains at least one VLAN, the default VLAN.
- Switches contain advanced self learning features and broadcast behaviour, which are well suited for the building of for example a corporate network, supporting a number of user groups.
- each user would ideally have his own completely isolated set of work groups available.
- a particular problem is then that the number of available VLAN tags, each tag defining a user, is limited to a number 4096, which is far from enough to serve hundreds of thosands of users.
- WO 00/77983 In the international patent application No. WO 00/77983 is described a telecommunications system in which users can select services.
- Service networks and users are connected to a switched domain.
- the service networks are arranged into groups and each group is allocated a VLAN by konfiguring the ports in the switches.
- the users can select services by configuring their apparatuses to a selected one of the VLAN:s.
- a switched domain has switches to which service providers and network terminals are connected.
- the switches have a user port connected to an uplink port in the network terminal.
- the user port is configured for the different service providers and the network terminals have corresponding service ports.
- the service ports corresponding to predetermined ones of the services are configured.
- EP 1045553 A2 VLAN bridging of a network.
- the network has nodes for changing of addresses.
- a user sending a message via the network addresses it to a receiver.
- the receiver address is changed into a temporary address for the network. This address is changed back when the message leaves the network via another of the network nodes.
- the present invention is concerned with a problem how to create a multiservice access system with ethernet technology for a practically unrestricted number of users.
- Another problem is how to offer the users sevices via the system, a number of the services practically covering all offered services.
- a further problem is how to offer secure service bindings between the users and the service providers.
- Still a problem is how to establish the service bindings as unicast bindings.
- Still another problem is how to establish the service bindings as multicast bindings.
- a problem is also to offer services from both communication service providers and application service providers.
- an access system including a node, called an edge access server, for connecting the service providers and a node, called a penult, for connecting the users, the nodes being interconnected by an arrangement supporting exchanging of Ethernet frames.
- the edge access server has service agents for the connecting of the service providers and the penults have user ports for connection to user networks.
- secure individual service access relations are provided in the access system, each relation being provided between one of the service agents and one of the user ports.
- the service access relations are provided between one of the service agents and a plurality of the user ports. The relation is extended for connecting of the user networks.
- Each service access relation has a dynamically assigned MAC address assigned to the relevant one of the service agents.
- the service access relation is in one alternative defined by the dynamically assigned MAC address and in an alternative defined by the MAC address in combination with a further identifier.
- the service access relation is bound to one of the user ports and, in the multicast case, bound to a plurality of the user ports.
- a service access relation can be established for a user to an application service provider. In this case either the user already has a service access relation to one of the communication service providers or the application service provider itself is equipped such that a service access relation can be established directly to it.
- the access system has a broadcast handler system and broadcast messages involved in service access or service use are picked up by this system in the penult hosting the user port. Shaping of the traffic is performed with the aid of the dynamically assigned MAC address and, where appropriate, in combination with the further identifier.
- a purpose with the invention is to give a practically unrestricted number of users access to services via an access system with Ethernet technology.
- Another purpose is that the number of services that can be offered simultaneously to a user practically covers all offered services.
- a further purpose is that sevice access relations between service providers and user devices shall be secure relations.
- Ethernet technology shall be utilized for establishing service access relations in the network.
- Still another purpose is to establish the service access relations as either unicast or multicast relations.
- Yet a purpose is to control the traffic in the system.
- a purpose is also to offer services from both communication service providers and application service providers.
- An advantage with the invention is that a multiservice access network for a practically unrestricted number of users can be created, using already standardized Ethernet technology.
- Another advantage is that the number of services that simultaneously can be offered to a user practically covers all offered services.
- a further advantage is that service access relations between service providers and users are secure relations.
- Ethernet technology is utilized for establishing service bindings in the network.
- Still another advantage is that the service access relations can be established as unicast relations or as multicast relations.
- An advantage is also that the service access relations can be established to both communication service providers and application service providers.
- FIG. 1 shows a block schematic with an overview of an access system
- FIG. 2 shows a block schematic with more details for the access system of FIG. 1 ;
- FIG. 3 a shows a diagram over an ethernet frame
- FIG. 3 b shows a diagram over a VLAN tag in the frame
- FIG. 3 c shows a diagram over an address field in the frame
- FIG. 4 shows a block schematic over a user in FIG. 1 with the user's VLAN:s;
- FIG. 5 shows a block diagram over a register in a broadcast handler
- FIG. 6 shows a block schematic over an uplink Ethernet frame
- FIG. 7 shows a block with addresses
- FIG. 8 shows a block diagram over a register in a handler
- FIG. 9 shows a flow chart over a method for defining an access relation
- FIG. 10 shows a flow chart over a DHCP request method
- FIG. 11 shows a flow chart over an ARP request method
- FIG. 12 shows a block shematic over the access system in a multicast situation
- FIG. 13 shows a flow chart over a multicast method.
- FIG. 1 shows a multiservice access system ACC 1 to which users U 11 , U 12 , U 13 , U 21 , . . . , Um 1 and communication service providers SP 1 , SP 2 , . . . , SPn are connected.
- the communication service providers SP 1 . . . SPn provide connection to networks.
- an application service provider AS is connected, which provides connection to an application.
- An objective is to build the system such that the number of the users U 11 . . . Um 1 can be very great, e.g. in the range of several hundred thousands users.
- Another objective is that the number of the service providers SP 1 . . . SPn, that each user can utilize, also is a great number, e.g. in the range of thousands of services.
- the access system ACC 1 includes nodes P 1 , P 2 . . . Pk, to which the users are connected with the aid of Ethernet technology.
- the access system also includes a node EAS, to which the service providers are connected.
- the node EAS is connected to the user's nodes P 1 -Pk via a network, which is an Ethernet based network ETH 1 according to the standard IEEE 802.1q.
- This network is a large network and has among others a number of VLAN capable Ethernet switches, not shown in the figure.
- the users and the service providers are connected to each other by individual service access relations through the network ETH 1 , e.g. a relation R 11 for the user U 11 and the service provider SP 1 . These relations have a guaranteed quality of service and are secure in the meaning that only the user and the service provider having the relation can listen to or else utilize this relation.
- the relations will be described more in detail below.
- the embodiment in FIG. 1 is more closely shown in FIG. 2 .
- the nodes P 1 , P 2 , . . . Pk of the access system ACC 1 hereinafter called penults, have user ports UP 11 , UP 12 , UP 13 , UP 21 , . . . , UPk 1 .
- Each of the user ports are connected to each a single one of the users U 11 -Um 1 by wires W 11 -Wk 1 .
- the penults P 1 -Pk have each a handler H 1 , H 2 , . . . , Hk, which administers the user ports on the respective penult.
- the handlers have each a register REG 11 , REG 21 , . . . REGk 1 .
- the node EAS of the access system ACC 1 is an edge access server, which in turn includes communication service agents SA 1 , SA 2 , . . . , SAn with each a respective service port PT 1 , PT 2 , . . . , PTn. It also includes an application service agent ASA
- the edge access server also has interfaces IF 1 , IF 2 , IF 3 , . . . IFj, an administating unit AD 1 and a broadcast handler BH 1 with a register REG 1 .
- the units of the edge access server are all bound to an Ethernet frame distribution system SW 1 .
- Each of the communication service agents are attributed to each a single one of the communication service providers SP 1 -SPn and the application service agent ASA is attributed to the application service provider AS.
- the penults are connected to the edge access server EAS via the interfaces.
- the handlers H 1 -Hk in the penults are bound to the broadcast handler BH 1 in the edge access server EAS, together forming a distributed handling system.
- the users U 11 -Um 1 have each a number of user devices and e.g. the user U 11 has devices UD 11 , UD 12 , UD 13 and UD 14 , and the user U 12 has devices UD 21 , UD 22 and UD 23 .
- the network ETH 1 and the users U 11 -Um 1 utilize Ethernet technology.
- the Eternet technology therefore will be shortly commented below.
- FIG. 3 a is shown an Ethernet frame FR 1 according to the standard IEEE802.1q.
- the frame has a field D 1 for a destination address and a following field S 1 for a source address. It also has a field T 1 for defining a type of Ethernet frame.
- a field VL 1 points out which VLAN that is concerned and a field EPL 1 contains the payload, the message that is to be transmitted.
- An address F is reserved as a broadcast address.
- FIG. 3 c shows the source address field S 1 , which consists of 48 bits.
- One bit L 1 points out whether the address is locally or globally administrated.
- One bit M 1 points out whether the frame FR 1 is a multicast frame used for e.g. IP multicast messages.
- the remaining 46 bits in a field ADR 1 are address bits for MAC addresses.
- Any of the user devices has one globally administrated MAC address, which is given by the manufacturer of the device.
- the user device UD 11 in FIG. 2 for example has an address UMAC 1 .
- FIG. 4 details how the user devices are related to the penult.
- the figure is a logic view over the relations.
- the user U 11 has an Ethernet LAN ETH 2 containing user VLAN:s with tags TAG 1 , TAG 2 , TAG 3 and TAG 4 , which LAN is connected to the user port PT 11 via the wire W 11 .
- the user device UD 11 is in turn attributed to the VLAN with tag TAG 1
- the device UD 12 has the tag TAG 2
- the device UD 13 has both the tags TAG 2 and TAG 3
- the device UD 14 has the tag TAG 4 .
- a common Ethernet In a common Ethernet, on one hand, the different participants within each VLAN can communicate with each other freely and efficiently, which is a basic principle of the Ethernet.
- a first user that wants to contact a second user sends broadcast an address resolution protocol ARP with a request “Who has this IP address?”. Everybody in the network can listen and the second user, that has the IP address in question, sends back his MAC address to the first user.
- a relation between the users is established.
- a fundamental service is to both enable establishment of service bindings between users and service providers and, in such bindings, provide a transport service through the access system such that the service can be delivered to the user with high security and without any quality degradation.
- the users decide which services they select and which VLAN they decide for a certain of the services.
- Each user can make his own decisions for the correspondence between VLAN and service, independently of the other users.
- the user U 11 selects the service from the service provider SP 1 and decides the VLAN with the tag TAG 1 for this service.
- the user U 11 also selects service from provider SP 2 and decides the VLAN with the tag TAG 2 for this service.
- the user U 11 selects service provider SP 3 on the VLAN with the tag TAG 3 and service provider SP 4 on the VLAN with the tag TAG 4 .
- Other users can select other services and decide other VLAN:s.
- the user U 12 selects the service from service provider SP 1 and decides the VLAN with the tag TAG 3 for this service.
- the user U 12 also selects service from the service provider SP 3 and decides the VLAN with the tag TAG 1 for this service.
- the users then send their decisions to the administrative unit AD 1 in the edge access server EAS, the users defining themselves by their respective user port. This sending can be performed by any suitable means, e.g. by assigning a web page, by a common letter or by a telephone call.
- the administrative unit AD 1 also has the information about the correspondence between the service providers SP 1 -SPn and the service agents SA 1 -SAn. The administrative unit thus has triplets of information containing service agent, VLAN tag and user port.
- the administrative unit AD 1 will build up the register REG 1 in the broadcast handler BH 1 , as shown in FIG. 5 .
- the administrative unit AD 1 For the different user ports UP 11 -UPk 1 corresponding lists L 11 ,L 12 , L 13 , L 21 . . . Lk 1 are created with fields corresponding to the VLAN tags. In this fields are written unique MAC addresses, which are dynamically allocated to the different service agent's respective service port by the administrative unit AD 1 .
- the administrative unit dynamically allocates a unique MAC address SAMAC 1 to the service port PT 1 of the service agent SA 1 , connected to the service provider SP 1 .
- the address is allocated from a set of locally administrated addresses, LAA. This address is written on the list L 11 for the user port UP 11 and in a field pointed out by the VLAN tag TAG 1 . This means that the allocated MAC address SAMAC 1 is bound to solely one information pair which has the user port UP 11 and the identification tag TAG 1 of the VLAN.
- the relation R 11 is defined by the address SAMAC 1 for the service port PT 1 , the address being bound to the user port UP 11 and the VLAN tag TAG 1 . It should be noted that no other participant but the service provider SP 1 and the user U 11 can utilize the relation R 11 .
- a unique MAC address SAMAC 2 is dynamically allocated to the service port PT 2 of the service agent SA 2 and is written in a field defined by the VLAN tag TAG 2 on the same list L 11 .
- a new relation R 21 is created, which is defined by the address SAMAC 2 and is bound to the user port UP 11 and the VLAN with the tag TAG 2 .
- MAC address SAMAC 5 is allocated to the service agent SA 3 , service port PT 3 , in a field with the tag TAG 3 and a MAC address SAMAC 6 is allocated to the service agent SA 4 , service port PT 4 , in a field with the tag TAG 4 .
- a unique MAC address SAMAC 3 is dynamically allocated to the service port PT 1 of the service agent SA 1 and this address is written in a field pointed out by the VLAN tag TAG 3 on the list L 12 .
- a MAC address SAMAC 4 is dynamically allocated to the service agent SA 3 , service port PT 3 , and this address is written in a field pointed out by the VLAN tag TAG 1 on the list L 12 .
- each of the service ports PT 1 -PTn can get associated with a set of the unique MAC addresses for the service agents and that each of these MAC addresses is associated with only one particular of the user ports UP 11 -UPk 1 .
- the relations between user port and service agent are built up as described above and are stored in the register REG 1 , but still the user devices can't utilize their respective service. It is in fact not even necessary until now that the user devices are connected.
- the users intend to utilize the services they connect their user devices to the wires W 11 -Wk 1 via the VLAN:s as is shown by an example in FIG. 4 for the user U 11 .
- the conventional DHCP Dynamic Host Configuration Protocol
- the DHCP is an example on a more general service attachment request. By this protocol the different user devices will get their default gateway, which is the relevant service agent. Then they will also get their respective IP address and the IP address to the relevant service agent. This is performed in the following manner.
- the user device UD 11 sends a frame FR 2 with the addresses and payload as is shown in FIG. 6 .
- the broadcast address F is written.
- the MAC address UMAC 1 for the user device UD 11 is written and in the VLAN field VL 1 the VLAN tag TAG 1 is written, the tag appearing from FIG. 4 .
- the message in the frame FR 2 is “this is a DHCP request”.
- the users U 11 -Um 1 are connected via the Ethernet VLANs and have no information about the organization of the system ACC 1 . From the horizon of the users they act as if they were connected to a conventional Ethernet and it is therefore the user device UD 11 sends the frame FR 2 in FIG. 6 as a broadcast request.
- the aim from the view of the user device UD 11 is that the broadcast request gives the user the identity of the relevant DHCP server.
- this sever is the service agent SA 1 , which has a set of IP addresses that it can allocate.
- the broadcast request in the frame FR 2 first is intercepted by the handler H 1 via the user port UP 11 .
- the handler H 1 that gets the frame FR 2 via the port UP 11 , adds the identification for this port. It then packs the port identification together with the frame FR 2 as a unicast message U 1 , see FIG. 2 , and sends this message to the broadcast handler BH 1 in the edge access server EAS.
- the broadcast handler BH 1 looks in its register, the register REG 1 of FIG. 5 . With the aid of the user port UP 11 and the VLAN tag TAG 1 it finds the MAC address SAMAC 1 for the service agent SA 1 . Now the default gateway, the service agent SA 1 , for the user device U 11 is found. The user device UD 11 also must be given an IP address itself and an IP address to its default gateway, which is performed in the following manner.
- the broadcast handler sends the request to the found service agent SA 1 , which now has the information as appears from a table TAB 1 in FIG. 7 .
- This information is the own port address SAMAC 1 , the VLAN tag TAG 1 , a subnet mask SM 1 , the user MAC address UMAC 1 and the service agent's own IP address IPSA 1 .
- the service agent SA 1 From its set of IP addresses the service agent SA 1 now allocates an IP address IPUD 11 to the user device UD 11 , which is associated with the content in the table TAB 1 .
- the DHCP response includes the IP address IPSA 1 of the service agent as default gateway address, the allocated IP address IPUD 11 and the subnet mask SM 1 .
- the user device UD 11 stores the IP address IPSA 1 to the service agent SA 1 , its own IP address IPUD 11 and the subnet mask, as host configuration data in a conventional manner.
- the other devices of the user U 11 send their DHCP requests with their MAC addresses and corresponding VLAN tag, the tags appearing from FIG. 4 .
- the user device UD 13 has to send two DHCP requests with the tags TAG 2 respective TAG 3 .
- the relation R 11 is now established on an IP level.
- the service agent SA 1 gets an IP packet with the address IPUD 11 it finds the information in the table TAB 1 and sends the packet to the correct receiver with the MAC address UMAC 1 .
- the user device UD 11 also has the IP address IPSA 1 to the service agent, its “default gateway”.
- the user device UD 11 utilizes in conventional manner an ARP request (Address Resolution Protocol) to get a MAC address to the IP address IPSA 1 .
- the user device UD 11 therefore transmits broadcast the ARP message which is received by the handler H 1 in the penult P 1 via the user port UP 11 .
- the handler adds the identification for the user port and sends the message unicast to the broadcast handler BH 1 in the edge access server EAS.
- the broadcast handler looks in its register REG 1 on the list L 11 for the user port UP 11 .
- the broadcast handler finds the service agent MAC address SAMAC 1 . It transmits the address SAMAC 1 to the handler H 1 , which in turn responds with the address SAMAC 1 to the user device UD 11 .
- the user device UD 11 With the aid of the address SAMAC 1 the user device UD 11 now can utilize the relation R 11 and get the service from the service provider SP 1 .
- the handler H 1 in the penult P 1 successively creates the register REG 11 , shown in FIG. 8 .
- the register REG 11 is similar to the register REG 1 in the broadcast handler BH 1 .
- the register REG 11 only comprises the penult's own user ports UP 11 , UP 112 and UP 13 on respective lists PL 11 , PL 12 and PL 13 and the VLAN tags.
- the handler H 1 gets back the MAC address SAMAC 1 from the broadcast handler BH 1 .
- the handler Hi then fills in the address SAMAC 1 in the register REG 11 .
- the handler H 1 first looks in its own register REG 11 instead of sending the request to the broadcast handler BH 1 .
- the handler H 1 finds the requested address SAMAC 1 on the VLAN tag TAG 1 and sends the address immediately back to the user device UD 11 .
- the register REG 11 in the handler H 1 is built up when the register REG 1 in the broadcast handler BH 1 is built up.
- a user first made the DHCP request via the access system ACC 1 to get the IP addresses. This request then was followed by the ARP request.
- the configuration is performed in an alternative way by alternative means.
- the request for the IP addresses can e.g. be performed by so called static configuration.
- the user device makes the ARP request as described above to get the MAC address to its default gateway, the relevant service agent.
- all ARP requests from the users also when not preceeded by a DHCP request, will be intercepted by the penult and result in the address to the respective default gateway. In this way all communication between different users is forced to flow to the service agent.
- the dynamically allocated MAC addresses were locally administrated addresses, LAA.
- An alternative is that a set of MAC addresses is bought from the IEEE.
- the service agent successively builds up a list for translating between IP addresses and user device MAC addresses. When it receives a packet it reads the IP address and if this address is whitin the service agent's own administrated subnet it looks for the IP address and finds the user MAC address. The service agent forwards the packet to this user MAC address and packets with any other IP address will be forwarded to the service provider.
- the distributed handler system comprised the handler H 1 in the penult and the broadcast handler BH 1 in the edge access server EAS.
- the penult and the edge access server were interconnected by the network ETH 1 .
- the penult is a unit close to the edge access server.
- the transmission of messages between the penult and the edge access server is performed by Ethernet frames without the interconnecting network ETH 1 . It is even so that the penult can be regarded as a part of the edge access server itself.
- edge access server EAS the penults P 1 -Pk
- the handler registers REG 1 , REG 11 -REGk 1 and other parts of the access system not necessarily are physical units. Rather they are functional units which can be centralized or distributed depending on what is most appropriate in a situation.
- each of the service access relations was defined by solely one unique service agent MAC address, e.g. the relation R 11 defined by the address SAMAC 1 .
- Each of the service agents therefore could have a set of different MAC addresses allocated to its service agent port, each address for one of the relations to the respective user port.
- each service agent has only one single service agent MAC address for all its different service access relations to different of the user ports.
- the respective service access relation is in this embodiment defined by a complete access relation identifier including the service agent MAC address and a further service access relation identifier. This further identifier appears from the Ethernet header in the transmitted frames. An example on such an identifier is the combination of the VLAN tag and the user device MAC address.
- the user U 11 had the Ethernet ETH 2 with tagged VLAN:s to relate the user devices to the penult P 1 .
- the user has a port based VLAN with a switch, that reads the tag and switches to a port for the relevant user device.
- the user has a MAC based VLAN and the penult checks that the user MAC address corresponds to the VLAN identifier.
- the VLAN tag is transmitted from the service agent to the penult to transmit a requested service to the correct user device.
- no VLAN tag is transmitted to the penult but only the service agent MAC address, e.g. SAMAC 1 .
- the penult itself derives the VLAN identity, e.g. the VLAN tag, from the unique service agent MAC address, defining the service access relation.
- the service providers SP 1 -SPn were connected to each one of the service agents SA 1 -San.
- a service provider can be connected to two or more service agents.
- DHCP request For other types of services than IP or other types of establishment of a relation between a user device and a service agent, other types of broadcast service attachment requests can be used. By the broadcast handler also those alternative requests are replied to by a service agent MAC address, which is identified in the same way as for the DHCP.
- a service agent MAC address As an example can be mentioned the use of PPP over Ethernet, PPPoE, where a broadcast PPPOE request will be responded with a service agent MAC address to the service agent acting as PPPoE server.
- ARP request is mentioned above.
- IP protocol Similar procedures are utilized to bring about address resolution.
- one of the users decides one of his VLAN:s for one of the services, e.g. the user U 11 selects the service from the service provider SP 1 and decides the VLAN with the tag TAG 1 for the service.
- the user sends the the decided tag and the selected service together with his user port UP 11 to the administrative unit AD 1 in a step 91 .
- a step 92 the administrative unit checks which one of the service agents SA 1 -SAn that corresponds to the selected service and finds the service agent SA 1 .
- the administrative unit dynamically allocates the unique service agent MAC address SAMAC 1 to the service agent SA 1 in a step 93 .
- the register REG 1 is created in the broadcast handler BH 1 in a step 94 , in which register the service agent MAC address SAMAC 1 is related to the user port UP 11 and VLAN tag TAG 1 . Thereby the service access relation R 11 is defined, step 95 .
- the handler H 1 receives the broadcast DHCP request with the frame FR 2 from the user device UD 11 .
- the frame includes both the user MAC address UMAC 1 and the VLAN tag TAG 1 .
- the handler H 1 adds the user port identification UP 11 in a step 101 and in a step 102 the handler sends the complete message unicast to the broadcast handler BH 1 in the edge access server EAS.
- the broadcast handler notes the user port UP 11 and the VLAN tag TAG 1 in a step 103 and, looking in its register REG 1 , it points out the corresponding unique service agent MAC address SAMAC 1 in a step 104 .
- the broadcast handler finds the relevant service agent SA 1 . Now the first part of the procedure is ready, finding the default gateway. Next part is to send IP addresses to the user device.
- the broadcast handler BH 1 sends the user port and the VLAN tag to the service agent SA 1 .
- the service agent SA 1 allocates the IP address IPUD 11 to the user device UD 11 .
- the service agent sends the DHCP response, including the own IP address IPSA 1 and the allocated IP address IPUD 11 , step 108 .
- the user device stores the received IP addresses.
- the relation R 11 is now estabished on IP level.
- a first step 110 the handler H 1 in the penult P 1 receives an ARP message from the user device UD 11 on the user port UP 11 .
- the handler adds the port identification in a step 111 and in a step 112 the handler H 1 sends a message, including the ARP message and the port, unicast to the broadcast handler BH 1 .
- the broadcast handler looks in the register REG 1 for the user port UP 11 and the VLAN tag TAG 1 and finds the service agent MAC address SAMAC 1 , step 113 .
- the broadcast handler sends the address SAMAC 1 to the handler H 1 and in a step 115 the handler transmits the address SAMAC 1 to the user and the address is received by the user device UD 11 .
- the broadcast handler sends the MAC address SAMAC 1 to the relevant service agent SA 1 with an order to transmit the address to the handler H 1 .
- FIG. 12 shows a somewhat simplified view of FIG. 2 with the access system ACC 1 interconnecting the service providers SP 1 -SPn and the users U 11 -Um 1 .
- the access system has, as above, the edge access server EAS and the penults P 1 -Pk interconnected by the Ethernet network ETH 1 .
- Ethernet switches SW 191 , SW 192 and SW 193 supporting multicast.
- the penults P 18 , P 19 and P 20 support multicast access.
- the penult P 19 has the user port UP 191 with a connection to the user U 191 and the user port UP 192 connected to the user U 192 .
- the penult P 20 has the user port P 201 connected to the user U 193 .
- the user 191 has user devices UD 191 and UD 192 attributed to the user port UP 191 via a VLAN with a VLAN tag TAG 19 and the user U 192 has a user device UD 193 attributed to the user port UP 192 , also via the VLAN with the tag TAG 19 .
- the user U 193 has a user device UD 194 which is attributed to the user port UP 201 , also via the VLAN with the tag TAG 19 .
- the aim with the multicast access relation MR 11 is, naturally, to distribute a service from the service provider SP 19 via the service agent SA 19 to the users. Note that this distribution takes place only downstream, from the service provider to the users.
- the distribution is performed by branching up the service access relation MR 11 in the edge access server, in the switches and in the penults.
- the relation MR 11 to the users, which utilize the service from the provider SP 19 is defined by one and the same MAC address, in the example a MAC address SAMAC 19 allocated to the service agent SA 19 by the administrative unit AD 1 .
- Each multicast flow from this service agent has a specific multicast address to which all participating users are listening.
- the multicast bit M 1 in FIG. 3 c is set.
- the service from the service provider SP 19 is distributed on one and the same Ethernet LAN, in the example the VLAN with the tag TAG 19 , which is bound to the multicast access relation MR 11 .
- the users can't decide their own VLAN:s for the service, but a common decision concerning the VLAN identification must be made.
- the establishing of the relation MR 11 is performed in a corresponding way as described above.
- the service agent for a certain service can have more than one assigned MAC address, in the same way as described above in the unicast case.
- a step 130 the VLAN with the tag TAG 19 for a selected service from the service provider SP 19 is decided. The decision is distributed to the edge access server EAS and to the users in a step 131 .
- the administrative unit AD 1 checks which one of the service agents SA 1 -SAn that corresponds to the selected service and finds the service agent SA 19 .
- the administrative unit AD 1 dynamically allocates the service agent MAC address SAMAC 19 to the service agent SA 19 in a step 133 , this MAC address defining the multicast access relation MR 11 .
- the MAC address SAMAC 19 is bound to the decided VLAN with tag TAG 19 .
- the multicast access relation MR 11 is established in a corresponding way as is described for the unicast relations.
- the multicast bit M 1 is set for frames transmitted over the multicast service access relation MR 11 .
- the services from the service providers SP 1 -SPn must be delivered with a certain quality level.
- the resources within the access system ACC 1 are however limited, which delimits the quality level.
- An example on a limited resource is the available bandwidth.
- Many relations, as the relation R 11 are to be transmitted via the connections between the service agent and a switch, between the switch and the penult and between the penult and the user VLAN, which relations have to share the available bandwidth.
- the quality of service for the relations are deicided in agreements and are denoted for each relation in the register REG 1 in FIG. 5 .
- the quality values are utilzed when the traffic is shaped by shapers in the access system.
- shapers are shown, in FIG. 2 , a shaper SHn in the edge access server EAS and a shaper SHk in the penult Pk.
- shapers in the edge access server look on the service agent MAC addresses, which always appears in a transmitted frame either as source or destination address. With the aid of the address the shaper finds the corresponding value for the quality level. e.g.
- the shaper has to look also on the further identifier.
- the shaper SHk in the penult Pk can utilize the VLAN tag and the user port in a corresponding manner.
- the shaping includes in conventional manner buffering the frames, prioritizing with the aid of the priority tag PTG 1 and sheduling.
- the penults can have a traffic filter, e.g. a filter F 21 at the user port UP 21 in the penult P 2 .
- the filter reads the addresses in the transmitted frames. Frames from the user devices may only have the service agent MAC addresses or the broadcast address as destination address. Frames to the user devices may only have the service agent MAC addresses as source address. Other addresses are not allowed and frames with such addresses are deleted in the filter. Also, broadcast messages from a user, which are not to be handled by any of the service agents, are deleted.
- the MAC addresses can have an internal address structure that is adapted to the structure of the access network ETH 1 . This can simplify the implementation of the network and its components in the access system ACC 1 .
- the application service provider AS and the application service agent ASA are more closely described in the enclosed “Public Ethernet access to Application services”, enclosure 1.
- the invention addresses how to provide service bindings with determined properties to Application services providers directly attached to a Public Ethernet access network.
- any accessed network in particular an IP network there are conventional manners of how to reach Application services connected to that network.
- PCT/SE02/00226 does not address access to application services.
- An objective with the invention is to allow for application service providers to attach directly to a Public Ethernet access system, and enable service bindings with guaranteed properties between users and such application service providers.
- Another objective of the invention is to provide the service bindings to an application service such that it can be reached by users having service bindings to the networks of different service providers.
- Examples of application services that can be accessed using the invention of application service bindings are Video-On-Demand servers, Telephony gateways to a circuit switched telephony network, game servers, proxy access to other networks, backup file service providers etc.
- SA service agents
- ASA Application service agents
- IP Internet Protocol
- An access network can contain a plurality of service agents, providing service bindings to different networks. These can be public or private IP networks.
- a service provider offering application services connects to the access network. When the application service is to be offered to several IP networks, this connection may need to contain several logical interfaces, e.g. using different VLAN tags. (This is the case when service is to be offered to several separate networks with overlapping address ranges).
- the service provider system requests via the ASA, at least one IP address in each network to which the application service is to be addressable.
- the ASA relays the request for IP addresses from the service agents SA 1 , SA 2 , , , SAn.
- Each SA will allocate the IP address within the subnet reflected by the subnet mask given to the users when establishing service bindings as described in [1].
- the SA will also inform the broadcast handler (BH 1 ) that any ARP message from a user device about the IP address of the ASA shall consider bindings to the ASA to find the MAC address by which the ARP shall be responded.
- the ASA assigns a logical interface to the service providing system to be associated to each allocated address.
- a user wanting a service binding to an application service requests this normally by addressing a service administration web page.
- the application service is identified and the user selects the wanted properties (e.g. bandwidth and QoS attributes) of the desired service binding.
- the administrative system (AD 1 ) now checks for available communication resources in the access network, and if successful allocates a new SAMAC, A-SAMAC associated with the selected ASA, and registers the new service binding.
- the ASA is notified about the A-SAMAC, which user port (UP) and VLAN Tag (TAG) and which network the user will use for access. If necessary the ASA triggers an authentication process between the user and the application service provider.
- the penult, to which the user is attached is informed to open communication between the user VLAN and the A-SAMAC of the ASA.
- the user device Since the IP address associated with the application service was allocated within the same subnet as the user, the first time (and later occasionally) the user addresses the application service, the user device will make an ARP request for the IP address of the application service. The penult will, as described earlier in [1], trap this request and hand it over to the broadcast handler. The broadcast handler will recognize the IP address as being associated with the ASA, and will instruct the ASA to respond to the ARP with the A-SAMAC of the service binding that has previously been established.
- the basis for identification of which A-SAMAC to use is the UP, VLAN tag and IP address of the user device. Different embodiments may have different means for cooperation between the broadcast handler and the ASA to determine the A-SAMAC.
- the ASA For each ASA IP address the ASA will store in a table association between each user IP address accessing the application service and the A-SAMAC of the users service binding to the ASA and the MAC address of the user device having the IP address.
- this table contains complete Ethernet headers that can be located using the IP address within the subnet as a table index.
- the user device will now know the A-SAMAC of the application service binding and any subsequent IP packet will be addressing the ASA directly by using the SAMAC as the Ethernet address.
- the application service sends response to the IP address of the user
- the ASA sends it to the user, as an Ethernet frame with source address equal to the A-SAMAC in its table, and the destination address set to the MAC address of the user device.
- the application server For each communication network the application service provider wishes to be visible to, the application server request an IP address, using a conventional address allocation protocol such as DHCP.
- a conventional address allocation protocol such as DHCP.
- application service providers can make their services accessible to the users of several communication networks, via service bindings of the access network.
- Each service binding can be individually be secured to have well defined properties and can individually be subject to charging according to any selected business model.
Abstract
An access system (ACC1) for relating communication service providers (SP1-SPn) and application service providers (AS) to users (U11-Um1) includes an edge access server (EAS) connecting the service providers and penults (P1-Pk) connecting the users. User devices (UD11-UD14) are connected via VLAN:s to user port (UP11) on the penult. Service agents (SA1-San, ASA), an administrator (AD1), a broadcast handler (BH1) and handlers (H1-Hk) in the penults form a handling system. A user (U11) decision including VLAN, service (SP1) and user port (UP11) is sent to the administrator (AD1), which dynamically allocates to the relevant service agent (SA1) a MAC address, defining a relation (r11). A user device (UD11) broadcasts an ARP request to get the MAC address to teh service agent (SA1). A service access relation to the application service provider (AS) is provided such that it can be reached by users having relations (R11, R21) to the communication service providers (SP1-SPn).
Description
- The present invention relates to a multiservice Ethernet access system and methods of establishing service access relations in the system.
- Ethernet has been developed mainly as a LAN (Local Area Network) technology, aiming to provide an efficient infrastructure for data networks within a company. Originally it was developed for moderate speed shared media, but current technology applies mainly to point-to-point links up to 10 Gbit/s, interconnected by high capacity Ethernet switches, supporting virtual LAN, VLAN, as described in the standard IEEE 802.1q. A virtual LAN is a group of system, such as computers in a workgroup, that need to communicate with each other, and protocols that restrict the delivery of VLAN frames to members of the VLAN.
- A LAN can be partitioned into multiple VLAN:s, where each VLAN is assigned a number called a VLAN identifier that identifies it uniquely within the LAN. A LAN contains at least one VLAN, the default VLAN.
- Switches contain advanced self learning features and broadcast behaviour, which are well suited for the building of for example a corporate network, supporting a number of user groups.
- However, in public service structures different requirements are put with respect to security, scaling and chargeability of services. In the public network, each user would ideally have his own completely isolated set of work groups available. A particular problem is then that the number of available VLAN tags, each tag defining a user, is limited to a number 4096, which is far from enough to serve hundreds of thosands of users.
- In the international patent application No. WO 00/77983 is described a telecommunications system in which users can select services. Service networks and users are connected to a switched domain. The service networks are arranged into groups and each group is allocated a VLAN by konfiguring the ports in the switches. The users can select services by configuring their apparatuses to a selected one of the VLAN:s.
- In the international patent application No. WO 00/79830 is described a telecommunication system in which users can select services. A switched domain has switches to which service providers and network terminals are connected. The switches have a user port connected to an uplink port in the network terminal. The user port is configured for the different service providers and the network terminals have corresponding service ports. The service ports corresponding to predetermined ones of the services are configured.
- In these two applications the number of users is restricted.
- In the European patent application EP 1045553 A2 is disclosed VLAN bridging of a network. The network has nodes for changing of addresses. A user sending a message via the network addresses it to a receiver. When the message reaches one of the network nodes the receiver address is changed into a temporary address for the network. This address is changed back when the message leaves the network via another of the network nodes.
- The present invention is concerned with a problem how to create a multiservice access system with ethernet technology for a practically unrestricted number of users.
- Another problem is how to offer the users sevices via the system, a number of the services practically covering all offered services.
- A further problem is how to offer secure service bindings between the users and the service providers.
- Still a problem is how to establish the service bindings as unicast bindings.
- Still another problem is how to establish the service bindings as multicast bindings.
- Yet another problem is how to control the traffic in the system.
- A problem is also to offer services from both communication service providers and application service providers.
- The problem is solved by an access system including a node, called an edge access server, for connecting the service providers and a node, called a penult, for connecting the users, the nodes being interconnected by an arrangement supporting exchanging of Ethernet frames. The edge access server has service agents for the connecting of the service providers and the penults have user ports for connection to user networks. In a unicast case secure individual service access relations are provided in the access system, each relation being provided between one of the service agents and one of the user ports. In a multicast case the service access relations are provided between one of the service agents and a plurality of the user ports. The relation is extended for connecting of the user networks.
- Somewhat more in detail the user ports are designed for connecting of the user networks, which have each one Ethernet LAN with at least one VLAN. Each service access relation has a dynamically assigned MAC address assigned to the relevant one of the service agents. The service access relation is in one alternative defined by the dynamically assigned MAC address and in an alternative defined by the MAC address in combination with a further identifier. The service access relation is bound to one of the user ports and, in the multicast case, bound to a plurality of the user ports. A service access relation can be established for a user to an application service provider. In this case either the user already has a service access relation to one of the communication service providers or the application service provider itself is equipped such that a service access relation can be established directly to it. The access system has a broadcast handler system and broadcast messages involved in service access or service use are picked up by this system in the penult hosting the user port. Shaping of the traffic is performed with the aid of the dynamically assigned MAC address and, where appropriate, in combination with the further identifier.
- A purpose with the invention is to give a practically unrestricted number of users access to services via an access system with Ethernet technology.
- Another purpose is that the number of services that can be offered simultaneously to a user practically covers all offered services.
- A further purpose is that sevice access relations between service providers and user devices shall be secure relations.
- Still a purpose is that Ethernet technology shall be utilized for establishing service access relations in the network.
- Still another purpose is to establish the service access relations as either unicast or multicast relations.
- Yet a purpose is to control the traffic in the system.
- A purpose is also to offer services from both communication service providers and application service providers.
- An advantage with the invention is that a multiservice access network for a practically unrestricted number of users can be created, using already standardized Ethernet technology.
- Another advantage is that that the number of services that simultaneously can be offered to a user practically covers all offered services.
- A further advantage is that service access relations between service providers and users are secure relations.
- Still an advantage is that Ethernet technology is utilized for establishing service bindings in the network.
- Still another advantage is that the service access relations can be established as unicast relations or as multicast relations.
- An advantage is also that the service access relations can be established to both communication service providers and application service providers.
- Yet other advantages are that no coordination of VLAN use between users is required in the unicast case, standard Ethernet components can be utilized both in the access system and in the user networks and the invention makes possible a simple administration and configuration of the access network.
- The invention will now be described more in detail with the aid of embodiments and with reference to the enclosed figures.
-
FIG. 1 shows a block schematic with an overview of an access system; -
FIG. 2 shows a block schematic with more details for the access system ofFIG. 1 ; -
FIG. 3 a shows a diagram over an ethernet frame; -
FIG. 3 b shows a diagram over a VLAN tag in the frame; -
FIG. 3 c shows a diagram over an address field in the frame; -
FIG. 4 shows a block schematic over a user inFIG. 1 with the user's VLAN:s; -
FIG. 5 shows a block diagram over a register in a broadcast handler; -
FIG. 6 shows a block schematic over an uplink Ethernet frame; -
FIG. 7 shows a block with addresses; -
FIG. 8 shows a block diagram over a register in a handler; -
FIG. 9 shows a flow chart over a method for defining an access relation; -
FIG. 10 shows a flow chart over a DHCP request method; -
FIG. 11 shows a flow chart over an ARP request method; -
FIG. 12 shows a block shematic over the access system in a multicast situation; and -
FIG. 13 shows a flow chart over a multicast method. -
FIG. 1 shows a multiservice access system ACC1 to which users U11, U12, U13, U21, . . . , Um1 and communication service providers SP1, SP2, . . . , SPn are connected. The communication service providers SP1 . . . SPn provide connection to networks. Also an application service provider AS is connected, which provides connection to an application. An objective is to build the system such that the number of the users U11 . . . Um1 can be very great, e.g. in the range of several hundred thousands users. Another objective is that the number of the service providers SP1 . . . SPn, that each user can utilize, also is a great number, e.g. in the range of thousands of services. The access system ACC1 includes nodes P1, P2 . . . Pk, to which the users are connected with the aid of Ethernet technology. The access system also includes a node EAS, to which the service providers are connected. The node EAS is connected to the user's nodes P1-Pk via a network, which is an Ethernet based network ETH1 according to the standard IEEE 802.1q. This network is a large network and has among others a number of VLAN capable Ethernet switches, not shown in the figure. The users and the service providers are connected to each other by individual service access relations through the network ETH1, e.g. a relation R11 for the user U11 and the service provider SP1. These relations have a guaranteed quality of service and are secure in the meaning that only the user and the service provider having the relation can listen to or else utilize this relation. The relations will be described more in detail below. - The embodiment in
FIG. 1 is more closely shown inFIG. 2 . The nodes P1, P2, . . . Pk of the access system ACC1, hereinafter called penults, have user ports UP11, UP12, UP13, UP21, . . . , UPk1. Each of the user ports are connected to each a single one of the users U11-Um1 by wires W11-Wk1. The penults P1-Pk have each a handler H1, H2, . . . , Hk, which administers the user ports on the respective penult. The handlers have each a register REG11, REG21, . . . REGk1. The node EAS of the access system ACC1 is an edge access server, which in turn includes communication service agents SA1, SA2, . . . , SAn with each a respective service port PT1, PT2, . . . , PTn. It also includes an application service agent ASA The edge access server also has interfaces IF1, IF2, IF3, . . . IFj, an administating unit AD1 and a broadcast handler BH1 with a register REG1. The units of the edge access server are all bound to an Ethernet frame distribution system SW1. Each of the communication service agents are attributed to each a single one of the communication service providers SP1-SPn and the application service agent ASA is attributed to the application service provider AS. The penults are connected to the edge access server EAS via the interfaces. The handlers H1-Hk in the penults are bound to the broadcast handler BH1 in the edge access server EAS, together forming a distributed handling system. The users U11-Um1 have each a number of user devices and e.g. the user U11 has devices UD11, UD12, UD13 and UD14, and the user U12 has devices UD21, UD22 and UD23. - As mentioned, the network ETH1 and the users U11-Um1 utilize Ethernet technology. The Eternet technology therefore will be shortly commented below.
- In
FIG. 3 a is shown an Ethernet frame FR1 according to the standard IEEE802.1q. The frame has a field D1 for a destination address and a following field S1 for a source address. It also has a field T1 for defining a type of Ethernet frame. A field VL1 points out which VLAN that is concerned and a field EPL1 contains the payload, the message that is to be transmitted. An address F is reserved as a broadcast address. - In
FIG. 3 b the field VL1 is shown in some more detail. It has 16 bits which includes 3 bits for a priority tag PTG1, one indicator bit and 12 bits in a field VTG1 for a VLAN tag. It is this VLAN tag that points out the specific VLAN and as this tag has 12 bits it can distinguish 212=4096 different VLANs. -
FIG. 3 c shows the source address field S1, which consists of 48 bits. One bit L1 points out whether the address is locally or globally administrated. One bit M1 points out whether the frame FR1 is a multicast frame used for e.g. IP multicast messages. The remaining 46 bits in a field ADR1 are address bits for MAC addresses. Any of the user devices has one globally administrated MAC address, which is given by the manufacturer of the device. The user device UD11 inFIG. 2 for example has an address UMAC1. The MAC address is unique for the device. From the description below it will also appear that the number of different service providers, e.g. among the service providers SP1-SPn, that can be connected to one and the same of the users, is restricted by the number of the VLAN tags, i.e. thenumber 212=4096. - In
FIG. 4 is shown details how the user devices are related to the penult. The figure is a logic view over the relations. In the example the user U11 has an Ethernet LAN ETH2 containing user VLAN:s with tags TAG1, TAG2, TAG3 and TAG4, which LAN is connected to the user port PT11 via the wire W11. The user device UD11 is in turn attributed to the VLAN with tag TAG1, the device UD12 has the tag TAG2, the device UD13 has both the tags TAG2 and TAG3 and the device UD14 has the tag TAG4. - In a common Ethernet, on one hand, the different participants within each VLAN can communicate with each other freely and efficiently, which is a basic principle of the Ethernet. A first user that wants to contact a second user sends broadcast an address resolution protocol ARP with a request “Who has this IP address?”. Everybody in the network can listen and the second user, that has the IP address in question, sends back his MAC address to the first user. A relation between the users is established. In an access system, on the other hand, a fundamental service is to both enable establishment of service bindings between users and service providers and, in such bindings, provide a transport service through the access system such that the service can be delivered to the user with high security and without any quality degradation. In a multi-service, multi service provider scenario several such bindings must be possible for each user at any given point in time, without interference between the bindings or between bindings for different users. In the present description will be disclosed how a multiservice access system, e.g. the access system ACC1, will fullfill these requirements on the services using Ethernet technology.
- To get the access network ACC1 to work, first the users decide which services they select and which VLAN they decide for a certain of the services. Each user can make his own decisions for the correspondence between VLAN and service, independently of the other users. In the present example the user U11 selects the service from the service provider SP1 and decides the VLAN with the tag TAG1 for this service. The user U11 also selects service from provider SP2 and decides the VLAN with the tag TAG2 for this service. Correspondingly the user U11 selects service provider SP3 on the VLAN with the tag TAG3 and service provider SP4 on the VLAN with the tag TAG4. Other users can select other services and decide other VLAN:s. The user U12, for example, selects the service from service provider SP1 and decides the VLAN with the tag TAG3 for this service. The user U12 also selects service from the service provider SP3 and decides the VLAN with the tag TAG1 for this service. The users then send their decisions to the administrative unit AD1 in the edge access server EAS, the users defining themselves by their respective user port. This sending can be performed by any suitable means, e.g. by assigning a web page, by a common letter or by a telephone call. The administrative unit AD1 also has the information about the correspondence between the service providers SP1-SPn and the service agents SA1-SAn. The administrative unit thus has triplets of information containing service agent, VLAN tag and user port. Gradually, when the users U11-Um1 send their information, the administrative unit AD1 will build up the register REG1 in the broadcast handler BH1, as shown in
FIG. 5 . For the different user ports UP11-UPk1 corresponding lists L11,L12, L13, L21 . . . Lk1 are created with fields corresponding to the VLAN tags. In this fields are written unique MAC addresses, which are dynamically allocated to the different service agent's respective service port by the administrative unit AD1. - In the example above the user U11 selected the service from service provider SP1 and decided the VLAN with the tag TAG1. The administrative unit dynamically allocates a unique MAC address SAMAC1 to the service port PT1 of the service agent SA1, connected to the service provider SP1. The address is allocated from a set of locally administrated addresses, LAA. This address is written on the list L11 for the user port UP11 and in a field pointed out by the VLAN tag TAG1. This means that the allocated MAC address SAMAC1 is bound to solely one information pair which has the user port UP11 and the identification tag TAG1 of the VLAN. Now the relation R11 is defined by the address SAMAC1 for the service port PT1, the address being bound to the user port UP11 and the VLAN tag TAG1. It should be noted that no other participant but the service provider SP1 and the user U11 can utilize the relation R11. Following the above examples, a unique MAC address SAMAC2 is dynamically allocated to the service port PT2 of the service agent SA2 and is written in a field defined by the VLAN tag TAG2 on the same list L11. A new relation R21 is created, which is defined by the address SAMAC2 and is bound to the user port UP11 and the VLAN with the tag TAG2. Also a MAC address SAMAC5 is allocated to the service agent SA3, service port PT3, in a field with the tag TAG3 and a MAC address SAMAC6 is allocated to the service agent SA4, service port PT4, in a field with the tag TAG4.
- For the user U12 with the user port UP12 a unique MAC address SAMAC3 is dynamically allocated to the service port PT1 of the service agent SA1 and this address is written in a field pointed out by the VLAN tag TAG3 on the list L12. For the user U12 also a MAC address SAMAC4 is dynamically allocated to the service agent SA3, service port PT3, and this address is written in a field pointed out by the VLAN tag TAG1 on the list L12.
- It appears from the above that, in the embodiment, each of the service ports PT1-PTn can get associated with a set of the unique MAC addresses for the service agents and that each of these MAC addresses is associated with only one particular of the user ports UP11-UPk1.
- The relations between user port and service agent are built up as described above and are stored in the register REG1, but still the user devices can't utilize their respective service. It is in fact not even necessary until now that the user devices are connected. When the users intend to utilize the services they connect their user devices to the wires W11-Wk1 via the VLAN:s as is shown by an example in
FIG. 4 for the user U11. Then there also must be built up a correspondance between IP addresses and MAC addresses. To get such a correspondance the conventional DHCP (Dynamic Host Configuration Protocol) is used in the present embodiment. The DHCP is an example on a more general service attachment request. By this protocol the different user devices will get their default gateway, which is the relevant service agent. Then they will also get their respective IP address and the IP address to the relevant service agent. This is performed in the following manner. - The user device UD11 sends a frame FR2 with the addresses and payload as is shown in
FIG. 6 . In the destination address field D1 the broadcast address F is written. In the source address field S1 the MAC address UMAC1 for the user device UD11 is written and in the VLAN field VL1 the VLAN tag TAG1 is written, the tag appearing fromFIG. 4 . The message in the frame FR2 is “this is a DHCP request”. The users U11-Um1 are connected via the Ethernet VLANs and have no information about the organization of the system ACC1. From the horizon of the users they act as if they were connected to a conventional Ethernet and it is therefore the user device UD11 sends the frame FR2 inFIG. 6 as a broadcast request. The aim from the view of the user device UD11 is that the broadcast request gives the user the identity of the relevant DHCP server. In the embodiment this sever is the service agent SA1, which has a set of IP addresses that it can allocate. The broadcast request in the frame FR2 first is intercepted by the handler H1 via the user port UP11. The handler H1, that gets the frame FR2 via the port UP11, adds the identification for this port. It then packs the port identification together with the frame FR2 as a unicast message U1, seeFIG. 2 , and sends this message to the broadcast handler BH1 in the edge access server EAS. When getting the message U1, the broadcast handler BH1 looks in its register, the register REG1 ofFIG. 5 . With the aid of the user port UP11 and the VLAN tag TAG1 it finds the MAC address SAMAC1 for the service agent SA1. Now the default gateway, the service agent SA1, for the user device U11 is found. The user device UD11 also must be given an IP address itself and an IP address to its default gateway, which is performed in the following manner. The broadcast handler sends the request to the found service agent SA1, which now has the information as appears from a table TAB1 inFIG. 7 . This information is the own port address SAMAC1, the VLAN tag TAG1, a subnet mask SM1, the user MAC address UMAC1 and the service agent's own IP address IPSA1. From its set of IP addresses the service agent SA1 now allocates an IP address IPUD11 to the user device UD11, which is associated with the content in the table TAB1. In a conventional manner, according to the DHCP protocol, information is transfered back to the user U11. The DHCP response includes the IP address IPSA1 of the service agent as default gateway address, the allocated IP address IPUD11 and the subnet mask SM1. The user device UD11 stores the IP address IPSA1 to the service agent SA1, its own IP address IPUD11 and the subnet mask, as host configuration data in a conventional manner. - In a corresponding manner the other devices of the user U11 send their DHCP requests with their MAC addresses and corresponding VLAN tag, the tags appearing from
FIG. 4 . Note that the user device UD13 has to send two DHCP requests with the tags TAG2 respective TAG3. - The relation R11 is now established on an IP level. When the service agent SA1 gets an IP packet with the address IPUD11 it finds the information in the table TAB1 and sends the packet to the correct receiver with the MAC address UMAC1. The user device UD11 also has the IP address IPSA1 to the service agent, its “default gateway”. The user device UD11 utilizes in conventional manner an ARP request (Address Resolution Protocol) to get a MAC address to the IP address IPSA1. The user device UD11 therefore transmits broadcast the ARP message which is received by the handler H1 in the penult P1 via the user port UP11. The handler adds the identification for the user port and sends the message unicast to the broadcast handler BH1 in the edge access server EAS. The broadcast handler looks in its register REG1 on the list L11 for the user port UP11. On the VLAN tag TAG1 the broadcast handler finds the service agent MAC address SAMAC1. It transmits the address SAMAC1 to the handler H1, which in turn responds with the address SAMAC1 to the user device UD11. With the aid of the address SAMAC1 the user device UD11 now can utilize the relation R11 and get the service from the service provider SP1.
- In an alternative embodiment the handler H1 in the penult P1 successively creates the register REG11, shown in
FIG. 8 . The register REG11 is similar to the register REG1 in the broadcast handler BH1. The register REG11 only comprises the penult's own user ports UP11, UP112 and UP13 on respective lists PL11, PL12 and PL13 and the VLAN tags. When the user device UD11 has made the ARP request for the first time, as described above, the handler H1 gets back the MAC address SAMAC1 from the broadcast handler BH1. The handler Hi then fills in the address SAMAC1 in the register REG11. The next time the user device UD11 makes the ARP request, the handler H1 first looks in its own register REG11 instead of sending the request to the broadcast handler BH1. The handler H1 finds the requested address SAMAC1 on the VLAN tag TAG1 and sends the address immediately back to the user device UD11. - In still an embodiment the register REG11 in the handler H1 is built up when the register REG1 in the broadcast handler BH1 is built up.
- Below will be described a number of alternative embodiments.
- In the above embodiment is described that a user first made the DHCP request via the access system ACC1 to get the IP addresses. This request then was followed by the ARP request. In an alternative embodiment the configuration is performed in an alternative way by alternative means. The request for the IP addresses can e.g. be performed by so called static configuration. After this configuration the user device makes the ARP request as described above to get the MAC address to its default gateway, the relevant service agent. In the same way as described above all ARP requests from the users, also when not preceeded by a DHCP request, will be intercepted by the penult and result in the address to the respective default gateway. In this way all communication between different users is forced to flow to the service agent. It was also described that the dynamically allocated MAC addresses were locally administrated addresses, LAA. An alternative is that a set of MAC addresses is bought from the IEEE.
- The service agent successively builds up a list for translating between IP addresses and user device MAC addresses. When it receives a packet it reads the IP address and if this address is whitin the service agent's own administrated subnet it looks for the IP address and finds the user MAC address. The service agent forwards the packet to this user MAC address and packets with any other IP address will be forwarded to the service provider.
- In connection with
FIGS. 1 and 2 was described that the distributed handler system comprised the handler H1 in the penult and the broadcast handler BH1 in the edge access server EAS. The penult and the edge access server were interconnected by the network ETH1. In an alternative embodiment the penult is a unit close to the edge access server. The transmission of messages between the penult and the edge access server is performed by Ethernet frames without the interconnecting network ETH1. It is even so that the penult can be regarded as a part of the edge access server itself. It should be noted that the edge access server EAS, the penults P1-Pk, the handler registers REG1, REG11-REGk1 and other parts of the access system not necessarily are physical units. Rather they are functional units which can be centralized or distributed depending on what is most appropriate in a situation. - In the embodiment in connection with
FIG. 2 each of the service access relations was defined by solely one unique service agent MAC address, e.g. the relation R11 defined by the address SAMAC1. Each of the service agents therefore could have a set of different MAC addresses allocated to its service agent port, each address for one of the relations to the respective user port. In an alternative embodiment each service agent has only one single service agent MAC address for all its different service access relations to different of the user ports. The respective service access relation is in this embodiment defined by a complete access relation identifier including the service agent MAC address and a further service access relation identifier. This further identifier appears from the Ethernet header in the transmitted frames. An example on such an identifier is the combination of the VLAN tag and the user device MAC address. - With the abovementioned further service access relation identifier it is also possible, in an embodiment, that a plurality of MAC addresses are allocated to the port of one of the service agents. Each of these MAC addresses is then bound to a set of relations, each of the relations having its own further identifier.
- In connection with
FIG. 4 it was described that the user U11 had the Ethernet ETH2 with tagged VLAN:s to relate the user devices to the penult P1. As an alternative the user has a port based VLAN with a switch, that reads the tag and switches to a port for the relevant user device. Still an alternative is that the user has a MAC based VLAN and the penult checks that the user MAC address corresponds to the VLAN identifier. - In an embodiment the VLAN tag is transmitted from the service agent to the penult to transmit a requested service to the correct user device. In an alternative embodiment no VLAN tag is transmitted to the penult but only the service agent MAC address, e.g. SAMAC1. The penult itself derives the VLAN identity, e.g. the VLAN tag, from the unique service agent MAC address, defining the service access relation.
- In connection with
FIG. 2 it was described that the service providers SP1-SPn were connected to each one of the service agents SA1-San. In an alternative a service provider can be connected to two or more service agents. - Above is described the use of DHCP request. For other types of services than IP or other types of establishment of a relation between a user device and a service agent, other types of broadcast service attachment requests can be used. By the broadcast handler also those alternative requests are replied to by a service agent MAC address, which is identified in the same way as for the DHCP. As an example can be mentioned the use of PPP over Ethernet, PPPoE, where a broadcast PPPOE request will be responded with a service agent MAC address to the service agent acting as PPPoE server. Also, the ARP request is mentioned above. For other protocols than the IP protocol similar procedures are utilized to bring about address resolution.
- In connection with a flow chart in
FIG. 9 will be described an overview over the above method of defining the service access relations in the multiservice access system ACC1. In astep 90 one of the users decides one of his VLAN:s for one of the services, e.g. the user U11 selects the service from the service provider SP1 and decides the VLAN with the tag TAG1 for the service. The user sends the the decided tag and the selected service together with his user port UP11 to the administrative unit AD1 in astep 91. - In a
step 92 the administrative unit checks which one of the service agents SA1-SAn that corresponds to the selected service and finds the service agent SA1. The administrative unit dynamically allocates the unique service agent MAC address SAMAC1 to the service agent SA1 in astep 93. The register REG1 is created in the broadcast handler BH1 in astep 94, in which register the service agent MAC address SAMAC1 is related to the user port UP11 and VLAN tag TAG1. Thereby the service access relation R11 is defined,step 95. - The method of building up the correspondence between IP addresses and MAC addresses will be described in short in connection with flow charts in
FIG. 10 andFIG. 11 . In afirst step 100 inFIG. 10 the handler H1 receives the broadcast DHCP request with the frame FR2 from the user device UD11. The frame includes both the user MAC address UMAC1 and the VLAN tag TAG1. The handler H1 adds the user port identification UP11 in astep 101 and in astep 102 the handler sends the complete message unicast to the broadcast handler BH1 in the edge access server EAS. The broadcast handler notes the user port UP11 and the VLAN tag TAG1 in astep 103 and, looking in its register REG1, it points out the corresponding unique service agent MAC address SAMAC1 in astep 104. In astep 105 the broadcast handler finds the relevant service agent SA1. Now the first part of the procedure is ready, finding the default gateway. Next part is to send IP addresses to the user device. In astep 106 the broadcast handler BH1 sends the user port and the VLAN tag to the service agent SA1. In astep 107 the service agent SA1 allocates the IP address IPUD11 to the user device UD11. In a conventional manner the service agent sends the DHCP response, including the own IP address IPSA1 and the allocated IP address IPUD11,step 108. In astep 109 the user device stores the received IP addresses. The relation R11 is now estabished on IP level. It should be noted that the procedure described in connection withFIG. 10 , finding the default gateway in thesteps 100 to 105 and the user device receiving the IP addresses in thesteps 106 to 109, can be performed in alternative ways. One such way is by the static configuration procedure as mentioned above. - The procedure when the service access relation R11 is established in the reverse direction, from the user side to the service agent side, will be described shortly in connection with the flow chart in
FIG. 11 . In afirst step 110 the handler H1 in the penult P1 receives an ARP message from the user device UD11 on the user port UP11. The handler adds the port identification in astep 111 and in astep 112 the handler H1 sends a message, including the ARP message and the port, unicast to the broadcast handler BH1. The broadcast handler looks in the register REG1 for the user port UP11 and the VLAN tag TAG1 and finds the service agent MAC address SAMAC1,step 113. In astep 114 the broadcast handler sends the address SAMAC1 to the handler H1 and in astep 115 the handler transmits the address SAMAC1 to the user and the address is received by the user device UD11. Alternatively the broadcast handler sends the MAC address SAMAC1 to the relevant service agent SA1 with an order to transmit the address to the handler H1. - The above described arrangements and procedures are related to unicast access between the service agents and the user ports on the penults. In connection with
FIG. 12 will shortly be described an embodiment with multicast access.FIG. 12 shows a somewhat simplified view ofFIG. 2 with the access system ACC1 interconnecting the service providers SP1-SPn and the users U11-Um1. The access system has, as above, the edge access server EAS and the penults P1-Pk interconnected by the Ethernet network ETH1. In this network are shown Ethernet switches SW191, SW192 and SW193 supporting multicast. Also the penults P18, P19 and P20 support multicast access. In the figure is shown a multicast access relation MR11 from the service agent SA19 to the penults P18, P19 and P20. The penult P19 has the user port UP191 with a connection to the user U191 and the user port UP192 connected to the user U192. The penult P20 has the user port P201 connected to the user U193. The user 191 has user devices UD191 and UD192 attributed to the user port UP191 via a VLAN with a VLAN tag TAG19 and the user U192 has a user device UD193 attributed to the user port UP192, also via the VLAN with the tag TAG19. The user U193 has a user device UD194 which is attributed to the user port UP201, also via the VLAN with the tag TAG19. - The aim with the multicast access relation MR11 is, naturally, to distribute a service from the service provider SP19 via the service agent SA19 to the users. Note that this distribution takes place only downstream, from the service provider to the users. The distribution is performed by branching up the service access relation MR11 in the edge access server, in the switches and in the penults. The relation MR11 to the users, which utilize the service from the provider SP19, is defined by one and the same MAC address, in the example a MAC address SAMAC19 allocated to the service agent SA19 by the administrative unit AD1. Each multicast flow from this service agent has a specific multicast address to which all participating users are listening. In the multicast frames transmitted via the relation MR11 the multicast bit M1 in
FIG. 3 c is set. Furthermore, the service from the service provider SP19 is distributed on one and the same Ethernet LAN, in the example the VLAN with the tag TAG19, which is bound to the multicast access relation MR11. In the multicast case the users can't decide their own VLAN:s for the service, but a common decision concerning the VLAN identification must be made. The establishing of the relation MR11 is performed in a corresponding way as described above. Also in the multicast access case the service agent for a certain service can have more than one assigned MAC address, in the same way as described above in the unicast case. - In connection with
FIG. 13 will be described an overview over a procedure for establishing the multicast access relations. In astep 130 the VLAN with the tag TAG19 for a selected service from the service provider SP19 is decided. The decision is distributed to the edge access server EAS and to the users in astep 131. In astep 132 the administrative unit AD1 checks which one of the service agents SA1-SAn that corresponds to the selected service and finds the service agent SA19. The administrative unit AD1 dynamically allocates the service agent MAC address SAMAC19 to the service agent SA19 in astep 133, this MAC address defining the multicast access relation MR11. In astep 134 the MAC address SAMAC19 is bound to the decided VLAN with tag TAG19. In astep 135 the multicast access relation MR11 is established in a corresponding way as is described for the unicast relations. In astep 136 the multicast bit M1 is set for frames transmitted over the multicast service access relation MR11. - The services from the service providers SP1-SPn must be delivered with a certain quality level. The resources within the access system ACC1 are however limited, which delimits the quality level. An example on a limited resource is the available bandwidth. Many relations, as the relation R11, are to be transmitted via the connections between the service agent and a switch, between the switch and the penult and between the penult and the user VLAN, which relations have to share the available bandwidth. The quality of service for the relations are deicided in agreements and are denoted for each relation in the register REG1 in
FIG. 5 . This is exemplified by a quality of service Q having a level QoS1 denoted on the list L11 for the relation R11, which relation is defined by the service agent MAC address SAMAC1. The quality values, e.g. a bandwidth parameter, are utilzed when the traffic is shaped by shapers in the access system. As examples on shapers are shown, inFIG. 2 , a shaper SHn in the edge access server EAS and a shaper SHk in the penult Pk. When shaping the traffic flow the shapers in the edge access server look on the service agent MAC addresses, which always appears in a transmitted frame either as source or destination address. With the aid of the address the shaper finds the corresponding value for the quality level. e.g. the value QoS1. In the embodiment when some of the relations were defined by its respective service agent MAC address and the further service access relation identifier, the shaper has to look also on the further identifier. The shaper SHk in the penult Pk can utilize the VLAN tag and the user port in a corresponding manner. The shaping includes in conventional manner buffering the frames, prioritizing with the aid of the priority tag PTG1 and sheduling. - It can happen that a participant tries to make more use of the access system ACC1 than the agreement allows, e.g. sends more traffic than it is agreed. This means that the participant's traffic even after shaping takes more bandwidth than the bandwidth parameter allows. The system can look upon the unique service agent MAC address in the frames and compare with the agreement. In the relation that uses too much bandwidth the system can apply policing and delet some of the transmitted frames. Also for this function the system has to look on the further service access relation identifier in the alternative embodiment for identifying the relations.
- It can also happen that the users exchange their MAC addresses by some means and tries to utilize the access system ACC1 for communication between themselves and not with the service providers. To prevent such a behaviour the penults can have a traffic filter, e.g. a filter F21 at the user port UP21 in the penult P2. The filter reads the addresses in the transmitted frames. Frames from the user devices may only have the service agent MAC addresses or the broadcast address as destination address. Frames to the user devices may only have the service agent MAC addresses as source address. Other addresses are not allowed and frames with such addresses are deleted in the filter. Also, broadcast messages from a user, which are not to be handled by any of the service agents, are deleted.
- The MAC addresses can have an internal address structure that is adapted to the structure of the access network ETH1. This can simplify the implementation of the network and its components in the access system ACC1.
- The application service provider AS and the application service agent ASA are more closely described in the enclosed “Public Ethernet access to Application services”,
enclosure 1. - Public Ethernet access to Application services
- Public Ethernet access to Application services
- Ingmar Tönnby, Ulf Larsson
- Priority claimed from pending patent application PCT/SE02/00226
- The invention addresses how to provide service bindings with determined properties to Application services providers directly attached to a Public Ethernet access network.
- The pending patent application “ARRANGEMENTS AND METHODS IN AN ACCESS SYSTEM”, International patent application No. PCT/SE02/00226 (Ref [1]) describes the principles of a large scale Ethernet based access system providing service bindings with determined properties between users and freely selectable providers of communication services, such as ISPs or corporate networks.
- For any accessed network, in particular an IP network there are conventional manners of how to reach Application services connected to that network.
- PCT/SE02/00226 does not address access to application services.
- Conventional access to application services are not easily adapted to business scenarios with commercial, multi service provider situations, accessed via independent access provider networks. Nor is it easy to provide these to be reached in independent and separated communication networks.
- The present invention is seen as an addition to the invention described in the specification part of PCT/SE02/00226, which is considered as a part of the current specification.
- An objective with the invention is to allow for application service providers to attach directly to a Public Ethernet access system, and enable service bindings with guaranteed properties between users and such application service providers.
- Another objective of the invention is to provide the service bindings to an application service such that it can be reached by users having service bindings to the networks of different service providers.
- Examples of application services that can be accessed using the invention of application service bindings, are Video-On-Demand servers, Telephony gateways to a circuit switched telephony network, game servers, proxy access to other networks, backup file service providers etc.
- [1] introduces the concept of service agents (SA), handling service bindings between users and an associated network service provider. In the same manner we introduce now Application service agents (ASA) associated with an application service from a service provider.
- In the description of the invention we will assume that the Internet Protocol IP will be used for an application in the user environment to reach the accessed application service. This is currently the most viable case. A person skilled in the art can from this understand how the invention can be modified for use with different versions of IP (IPv4 or IPv6) or another network protocol if applicable.
- An access network can contain a plurality of service agents, providing service bindings to different networks. These can be public or private IP networks. A service provider offering application services connects to the access network. When the application service is to be offered to several IP networks, this connection may need to contain several logical interfaces, e.g. using different VLAN tags. (This is the case when service is to be offered to several separate networks with overlapping address ranges).
- Before service bindings can provided to an ASA the service provider system requests via the ASA, at least one IP address in each network to which the application service is to be addressable. The ASA relays the request for IP addresses from the service agents SA1, SA2 , , , SAn. Each SA will allocate the IP address within the subnet reflected by the subnet mask given to the users when establishing service bindings as described in [1]. The SA will also inform the broadcast handler (BH1) that any ARP message from a user device about the IP address of the ASA shall consider bindings to the ASA to find the MAC address by which the ARP shall be responded. The ASA assigns a logical interface to the service providing system to be associated to each allocated address.
- A user wanting a service binding to an application service, requests this normally by addressing a service administration web page. In this request the application service is identified and the user selects the wanted properties (e.g. bandwidth and QoS attributes) of the desired service binding. The administrative system (AD1) now checks for available communication resources in the access network, and if successful allocates a new SAMAC, A-SAMAC associated with the selected ASA, and registers the new service binding. The ASA is notified about the A-SAMAC, which user port (UP) and VLAN Tag (TAG) and which network the user will use for access. If necessary the ASA triggers an authentication process between the user and the application service provider. The penult, to which the user is attached, is informed to open communication between the user VLAN and the A-SAMAC of the ASA.
- Since the IP address associated with the application service was allocated within the same subnet as the user, the first time (and later occasionally) the user addresses the application service, the user device will make an ARP request for the IP address of the application service. The penult will, as described earlier in [1], trap this request and hand it over to the broadcast handler. The broadcast handler will recognize the IP address as being associated with the ASA, and will instruct the ASA to respond to the ARP with the A-SAMAC of the service binding that has previously been established. The basis for identification of which A-SAMAC to use is the UP, VLAN tag and IP address of the user device. Different embodiments may have different means for cooperation between the broadcast handler and the ASA to determine the A-SAMAC.
- For each ASA IP address the ASA will store in a table association between each user IP address accessing the application service and the A-SAMAC of the users service binding to the ASA and the MAC address of the user device having the IP address. In a preferred embodiment this table contains complete Ethernet headers that can be located using the IP address within the subnet as a table index.
- After this procedure the user device will now know the A-SAMAC of the application service binding and any subsequent IP packet will be addressing the ASA directly by using the SAMAC as the Ethernet address. When the application service sends response to the IP address of the user, the ASA sends it to the user, as an Ethernet frame with source address equal to the A-SAMAC in its table, and the destination address set to the MAC address of the user device.
- As a summary of the invention possible action sequences for a number of uses cases is stated below:
- Use Case: Application Server Attachment
- For each communication network the application service provider wishes to be visible to, the application server request an IP address, using a conventional address allocation protocol such as DHCP.
-
- 1. The application server requests an IP address from the associated application service agent (ASA).
- 2. The ASA relays the request to the service agent SA, associated to the communication network.
- 3. The SA allocates an IP address within the same subnet as the users having service bindings to the communication network, and associates the allocated IP address with the MAC address of the application server and the VLAN through which it is connected.
- 4. The allocated address is sent to the application server via the ASA.
- Use Case: Creation of Application Service Binding
-
- 1. The user addresses the web page for service selection, and selects the application service and the qualities of the application service binding.
- 2. The administrative system (AD1) identifies the ASA associated to the service, checks for communication resources in the access network, and allocates a unique MAC address, A-SAMAC at the ASA, for the service binding.
- 3. The ASA is informed about the new binding, and ASA stores the IP address of the user, the MAC address of the user device and the allocated A-SAMAC in its tables.
- 4. AD1 instructs the penult to open the user port (UP) at which the user device is connected, to accept traffic between the user device and the allocated A-SAMAC.
- Use Case: Address Resolution
-
- 1. The user addresses the application service identified by its IP address.
- 2. The user device finds that the address of the AS is within the same subnet as the user device, and emits a broadcast ARP request.
- 3. The penult traps the ARP request and sends it to the broadcast handler in the EAS.
- 4. BH finds, based on the UP and VLAN from which the ARP was sent, the ASA associated with the IP address, and instructs the ASA to respond to the ARP with the A-SAMAC.
- Use Case: IP Packet Exchange Between User and ASP
-
- 1. After address resolution ha been performed, the user device, when sending an IP packet to the application server, will send it in an Ethernet frame addressed to ASAMAC.
- 2. The frame arrives to the ASA, which forwards it to the application server.
- 3. The server sends back a packet addressed to the IP address of the user.
- 4. The ASA receives the packet, examines the IP address, and finds that the user has a service binding to the ASA, associated with A-SAMAC and the user device MAC address and VLAN tag.
- 5. The ASA sends the IP packet through the access network in an Ethernet frame with A-SAMAC as source address and the user MAC address as destination address on the selected VLAN.
- 6. The frame arrives to the penult, which forwards it to the user port UP, after checking that the port is open for traffic from the A-SAMAC.
- 7. The frame arrives to the user device.
- With the invention application service providers can make their services accessible to the users of several communication networks, via service bindings of the access network. Each service binding can be individually be secured to have well defined properties and can individually be subject to charging according to any selected business model.
- [1] International patent application No. PCT/SE02/00226.
- A method of providing service bindings to an application service over a public Ethernet
- Arrangement . . .
Claims (30)
1. An access system for communication between service providers and users via service access relations, the system including:
an edge access server having at least one service agent with a connection intended for one of the service providers;
at least one penult having at least one user port intended for one of the users; and
an interconnecting arrangement, supporting exchanging of Ethernet frames, interconnecting the edge access server and the penults, the edge access server being arranged to dynamically allocate unique Ethernet MAC addresses to at least a part of the service agents, the unique Ethernet MAC addresses defining each one service access relation with one of the user ports.
2. An access system for communication between service providers and users via service access relations, the system including:
an edge access server having at least one service agent with a connection intended for one of the service providers;
at least one penult having at least one user port intended for one of the users; and
an interconnecting arrangement, supporting exchanging of Ethernet frames, interconnecting the edge access server and the penults,
the edge access server being arranged to dynamically allocate at least one Ethernet MAC address to each one of at least a part of the service agents, the edge access server also being arranged both to bind said Ethernet MAC addresses to the service access relations to the user ports and to bind relation identifiers to said service access relations, said identifier appearing in a header of a transmitted Ethernet frame.
3. An access system for communication between service providers and users via service access relations, the system including:
an edge access server having at least one service agent with a connection intended for one of the service providers;
at least one penult supporting multicast access having at least one user port intended for at least one user Ethernet VLAN; and
an interconnecting arrangement, supporting exchanging of Ethernet frames, interconnecting the edge access server and the penults, said arrangement including switches supporting multicast,
the edge access server being arranged to dynamically allocate Ethernet MAC addresses to at least one of the service agents, the Ethernet MAC address defining a multicast service access relation with at least one of the user ports, the edge access server being arranged to bind one and the same identification of one of the user Ethernet VLAN:s to the multicast service access relation, said user Ethernet VLAN identification being intended for the users participating in the multicast service.
4. The access system according to claim 2 , said user port being intended for at least one user Ethernet VLAN, the edge access server being arranged to bind also an identification of one of the user Ethernet VLAN:s on said user port to the service access relation.
5. The access system according to claim 4 including a register in the edge access server for the service access relations, the register including the service agent MAC address, the user port and the identification of the user Ethernet VLAN.
6. The access system according to claim 5 including:
a handling system with a handler attributed to the penult and a broadcast handler attributed to the service agents;
the handler being arranged to receive a broadcast service attachment request from a user device having a user MAC address, the request including the user Ethernet VLAN identification; and
the handler in the penult being arranged both to add to said service attachment request an identification of the user port and to send unicast the request with the user port identification to the broadcast handler.
7. The access system according to claim 6 including:
the broadcast handler being arranged both to note the user port and the Ethernet VLAN identification and to point out the corresponding one of the service agent MAC addresses;
the broadcast handler being arranged to find the relevant service agent via the service agent MAC address; and
said service agent being arranged to allocate an IP address for said user device having said user MAC address.
8. The access system according to claim 7 including said service agent being arranged to transmit to said user device via the service access relation, both said allocated user device IP address and its own IP address.
9. The access system according to claim 8 including:
the handler being arranged to receive from the user device a broadcast address resolution protocol broadcast message including the Ethernet VLAN identification;
the handler being arranged to add to said address resolution broadcast message an identification of the user port; and
the handler being arranged to transmit unicast said address resolution broadcast message with the user port identification to the broadcast handler.
10. The access system according to claim 9 including:
the broadcast handler being arranged to note the user port and the Ethernet VLAN identification and to find the relevant service agent MAC address;
the broadcast handler being arranged to transmit the service agent MAC address to the handler in the penult; and
the handler being arranged to transmit the service agent MAC address to the user device.
11. The access system according to claim 10 including, in the handler, a handler register including the user port and the Ethernet VLAN identification pointing out the service agent MAC address.
12. The access system according to claim 11 including:
the handler being arranged to receive from the user device, an address resolution protocol broadcast message including the Ethernet VLAN identification;
the handler being arranged to find in the handler register the relevant service agent MAC address; and
the handler being arranged to transmit the service agent MAC address to the user device.
13. A method for communication between service providers and users in an access system, the system having:
an edge access server having at least one service agent with a connection intended for one of the service providers;
at least one penult having at least one user port intended for one of the users; and
an interconnecting arrangement, supporting exchanging of Ethernet frames, interconnecting the edge access server and the penults, the method including the steps of:
dynamically allocating in the edge access server unique Ethernet MAC addresses to at least a part of the service agents; and
binding the unique service agent MAC addresses to solely each one service access relation with one of the user ports.
14. A method for communication between service providers and users in an access system, the system having:
an edge access server having at least one service agent with a connection intended for one of the service providers;
at least one penult having at least one user port intended for one of the users; and
an interconnecting arrangement, supporting exchanging of Ethernet frames, interconnecting the edge access server and the penults,
the method including the steps of:
dynamically allocating in the edge access server at least one Ethernet MAC address to each one of at least a part of the service agents;
binding said Ethernet MAC addresses to the service access relations to the user ports; and
binding relation identifiers to said service access relations, said identifier appearing in a header of a transmitted Ethernet frame.
15. A method for communication between service providers and users via service access relations in an access system, the system having:
an edge access server having at least one service agent with a connection intended for one of the service providers;
at least one penult supporting multicast access having at least one user port intended for at least one user Ethernet VLAN; and
an interconnecting arrangement, supporting exchanging of Ethernet frames, interconnecting the edge access server and the penults, said arrangement including switches supporting multicast,
the method including the steps of:
dynamically allocating in the edge access server Ethernet MAC addresses to at least one of the service agents, the Ethernet MAC address defining a multicast service access relation with at least one of the user ports; and
binding one and the same identification of one of the user Ethernet VLAN:s to the multicast service access relation,
said user Ethernet VLAN identification being intended for the users participating in the multicast service.
16. The method in an access system according to claim 14 , said user port being intended for at least one user Ethernet VLAN, the method including binding an identification of one of the user Ethernet VLAN:s on said user port to the service access relation.
17. The method in an access system according to claim 16 , the method including creating a register in the edge access server for the service access relations, the register including the service agent MAC address, the user port and the identification of the user Ethernet VLAN.
18. The method in an access system according to claim 17 , the access system including a handling system with a handler attributed to the penult and a broadcast handler attributed to the service agents, the method including:
receiving in the handler a broadcast service attachment request from a user device having a user MAC address, the request including the user Ethernet VLAN identification;
adding to said service attachment request an identification of the user port, the adding performed in the handler in the penult; and
sending unicast the request with the user port identification to the broadcast handler.
19. The method in an access system according to claim 18 , the method including:
noting in the broadcast handler the user port and the Ethernet VLAN identification;
pointing out the one of the service agent MAC addresses that corresponds to the user port and the Ethernet VLAN identification;
finding the relevant service agent via the service agent MAC address; and
allocating in said relevant service agent an IP address to said user device having said user MAC address.
20. The method according to claim 19 the method including transmitting, via the service access relation, both said allocated user device IP address and an IP address for the allocating service agent to said user device.
21. The method according to claim 20 , the method including:
receiving in the handler, from the user device, a broadcast address resolution protocol broadcast message including the Ethernet VLAN identification;
adding to the message an identification of the user port; and
transmitting unicast from the handler said address resolution broadcast message with the user port identification to the broadcast handler.
22. The method according to claim 21 , the method including:
noting in the broadcast handler the user port and the Ethernet VLAN identification;
finding the relevant service agent MAC address;
transmitting the service agent MAC address to the handler in the penult; and
transmitting from the handler the service agent MAC address to the user device.
23. The method according to claim 22 , the method including creating in the handler a handler register including the user port and the Ethernet VLAN identification pointing out the service agent MAC address.
24. The method according to claim 23 , the method including:
receiving in the handler, from the user device, an address resolution protocol broadcast message including the Ethernet VLAN identification;
finding in the handler register the relevant service agent MAC address; and
transmitting from the handler the service agent MAC address to the user device.
25. (canceled)
26. The method according to claim 19 including:
attributing an application service provider (AS) to the access network (ACC1) via an application service agent (ASA) of the edge access server (EAS);
requesting, by the application service agent (ASA), at least one IP address in at least one of the networks of the communication service providers; and
allocating the IP address of the corresponding communication service agent to the requesting application service agent (ASA).
27. The access system according to claim 1 , said user port being intended for at least one user Ethernet VLAN, the edge access server being arranged to bind also an identification of one of the user Ethernet VLAN:s on said user port to the service access relation.
28. The method in an access system according to claim 13 , said user port being intended for at least one user Ethernet VLAN, the method including binding an identification of one of the user Ethernet VLAN:s on said user port to the service access relation.
29. The method in an access system according to claim 15 , the method including creating a register in the edge access server for the service access relations, the register including the service agent MAC address, the user port and the identification of the user Ethernet VLAN.
30. The access system according to claim 7 including:
an application service agent (ASA) in the edge access server (EAS);
an application service provider (AS) that is attributed to the access network (ACC1) via the application service agent (ASA),
the application service agent (ASA) being arranged to request for at least one IP address in at least one of the networks of the communication service providers and the corresponding communication service agent being arranged to allocate its IP address to the requesting application service agent (ASA).
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/SE2002/000226 WO2003067821A1 (en) | 2002-02-08 | 2002-02-08 | Method and system relating service providers to clients, in an access network, using dynamically allocated mac addresses |
SEPCTSE0200226 | 2002-02-08 | ||
PCT/SE2003/000209 WO2003067822A1 (en) | 2002-02-08 | 2003-02-07 | System and method for establishing service access relations |
Publications (1)
Publication Number | Publication Date |
---|---|
US20050190775A1 true US20050190775A1 (en) | 2005-09-01 |
Family
ID=27731060
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/504,414 Abandoned US20050160174A1 (en) | 2002-02-08 | 2002-02-08 | Method and system relating service providers to clients in a access network using dynamically allocated mac addresses |
US10/503,184 Expired - Fee Related US7711824B2 (en) | 2002-02-08 | 2003-01-07 | Arrangements and methods in an access system |
US10/503,183 Abandoned US20050190775A1 (en) | 2002-02-08 | 2003-02-07 | System and method for establishing service access relations |
US10/502,880 Abandoned US20050152271A1 (en) | 2002-02-08 | 2003-02-07 | Methods and arrangements in an access system |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/504,414 Abandoned US20050160174A1 (en) | 2002-02-08 | 2002-02-08 | Method and system relating service providers to clients in a access network using dynamically allocated mac addresses |
US10/503,184 Expired - Fee Related US7711824B2 (en) | 2002-02-08 | 2003-01-07 | Arrangements and methods in an access system |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/502,880 Abandoned US20050152271A1 (en) | 2002-02-08 | 2003-02-07 | Methods and arrangements in an access system |
Country Status (9)
Country | Link |
---|---|
US (4) | US20050160174A1 (en) |
EP (4) | EP1472821B1 (en) |
CN (4) | CN100431305C (en) |
AT (2) | ATE413747T1 (en) |
AU (4) | AU2002230343A1 (en) |
DE (2) | DE60229786D1 (en) |
DK (1) | DK1472823T3 (en) |
ES (2) | ES2315353T3 (en) |
WO (4) | WO2003067821A1 (en) |
Cited By (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040037308A1 (en) * | 2002-08-06 | 2004-02-26 | Realtek Semiconductor Corp. | System and method for network connection detection |
US20050111455A1 (en) * | 2003-11-20 | 2005-05-26 | Daiki Nozue | VLAN server |
US20050160174A1 (en) * | 2002-02-08 | 2005-07-21 | Telefonaktiebolaget Lm Ericsson | Method and system relating service providers to clients in a access network using dynamically allocated mac addresses |
US20050201381A1 (en) * | 2004-03-12 | 2005-09-15 | Abbasi Salman Y. | Method and apparatus to manage network addresses for private voice communications |
US20060120364A1 (en) * | 2004-12-03 | 2006-06-08 | Alcatel | Method for transmitting information from a source via a first network unit and a network and a second network unit to a destination |
US20060182146A1 (en) * | 2005-02-14 | 2006-08-17 | Sylvain Monette | Method and nodes for aggregating data traffic through unicast messages over an access domain using service bindings |
US20060184695A1 (en) * | 2005-02-14 | 2006-08-17 | Sylvain Monette | Method and nodes for handling multicast messages |
US20060184645A1 (en) * | 2005-02-14 | 2006-08-17 | Sylvain Monette | Method and nodes for performing bridging of data traffic over an access domain |
WO2007142567A1 (en) | 2006-06-09 | 2007-12-13 | Telefonaktiebolaget Lm Ericsson (Publ.) | Operator managed virtual home network |
US20080034407A1 (en) * | 2006-08-01 | 2008-02-07 | Cisco Technology, Inc. | Apparatus and methods for supporting 802.1X in daisy chained devices |
US20100284284A1 (en) * | 2009-05-08 | 2010-11-11 | Qualcomm Incorporated | VOICE OVER INTERNET PROTOCOL (VoIP) ACCESS TERMINAL |
US7881198B2 (en) * | 2005-04-25 | 2011-02-01 | Telefonaktiebolaget L M Ericsson (Publ) | Method for managing service bindings over an access domain and nodes therefor |
WO2011014668A2 (en) * | 2009-07-30 | 2011-02-03 | Zinan Chen | Independent carrier ethernet interconnection platform |
US20110282996A1 (en) * | 2009-11-19 | 2011-11-17 | Yoram Zahavi | Method and system for dynamically allocating services for subscribers data traffic |
US8155125B1 (en) * | 2004-09-17 | 2012-04-10 | Cisco Technology, Inc. | Apparatus and method for utilizing aggregate network links for multicast switching |
US20140223018A1 (en) * | 2012-12-13 | 2014-08-07 | Level 3 Communications, Llc | Content Delivery Framework With Autonomous CDN Partitioned into Multiple Virtual CDNs |
US20140372588A1 (en) | 2011-12-14 | 2014-12-18 | Level 3 Communications, Llc | Request-Response Processing in a Content Delivery Network |
US20150131674A1 (en) * | 2013-11-13 | 2015-05-14 | Institute For Information Industry | Management server and management method thereof for managing cloud appliances in virtual local area networks |
US9634918B2 (en) | 2012-12-13 | 2017-04-25 | Level 3 Communications, Llc | Invalidation sequencing in a content delivery framework |
US10652087B2 (en) | 2012-12-13 | 2020-05-12 | Level 3 Communications, Llc | Content delivery framework having fill services |
US10701149B2 (en) | 2012-12-13 | 2020-06-30 | Level 3 Communications, Llc | Content delivery framework having origin services |
US10701148B2 (en) | 2012-12-13 | 2020-06-30 | Level 3 Communications, Llc | Content delivery framework having storage services |
US10791050B2 (en) | 2012-12-13 | 2020-09-29 | Level 3 Communications, Llc | Geographic location determination in a content delivery framework |
US11368548B2 (en) | 2012-12-13 | 2022-06-21 | Level 3 Communications, Llc | Beacon services in a content delivery framework |
Families Citing this family (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040120329A1 (en) * | 2002-12-18 | 2004-06-24 | Wen-Tzu Chung | SNMP management with a layer 2 bridge device |
US7594268B1 (en) | 2003-09-19 | 2009-09-22 | Symantec Corporation | Preventing network discovery of a system services configuration |
US7380123B1 (en) * | 2003-10-02 | 2008-05-27 | Symantec Corporation | Remote activation of covert service channels |
US7707312B2 (en) * | 2003-12-31 | 2010-04-27 | Alcatel Lucent | Printer discovery protocol system and method |
FR2866768A1 (en) | 2004-02-19 | 2005-08-26 | France Telecom | Audio/video Internet protocol service accessing process for e.g. personal computer, involves determining and associating channel identifier to information provided to mediation module, and receiving identifier by terminal, from module |
CN100361468C (en) * | 2004-06-30 | 2008-01-09 | 华为技术有限公司 | Method for realizing connection of private network connection device in connection network |
EP1628458A1 (en) * | 2004-08-19 | 2006-02-22 | Siemens Aktiengesellschaft | Method for transporting IP-packets between customer networks and IP-provider-networks through an access network |
CN100435520C (en) * | 2004-09-02 | 2008-11-19 | 上海贝尔阿尔卡特股份有限公司 | Method for selecting services provided by different providers of network service |
US7535926B1 (en) | 2005-01-07 | 2009-05-19 | Juniper Networks, Inc. | Dynamic interface configuration for supporting multiple versions of a communication protocol |
CN101120553B (en) * | 2005-02-14 | 2010-10-13 | 艾利森电话股份有限公司 | Method for aggregating data traffic over an access domain and nodes therefor |
US8077619B2 (en) * | 2005-02-14 | 2011-12-13 | Telefonaktiebolaget L M Ericsson (Publ) | Method for aggregating data traffic over an access domain and nodes therefor |
ATE360938T1 (en) * | 2005-03-17 | 2007-05-15 | Alcatel Lucent | METHOD FOR EXCHANGING DATA PACKETS |
EP1739929B1 (en) * | 2005-06-29 | 2012-05-30 | Alcatel Lucent | Method to forward downstream message and network unit realizing said method |
US8576846B2 (en) | 2005-10-05 | 2013-11-05 | Qualcomm Incorporated | Peer-to-peer communication in ad hoc wireless network |
US7606232B1 (en) | 2005-11-09 | 2009-10-20 | Juniper Networks, Inc. | Dynamic virtual local area network (VLAN) interface configuration |
US7492766B2 (en) | 2006-02-22 | 2009-02-17 | Juniper Networks, Inc. | Dynamic building of VLAN interfaces based on subscriber information strings |
US7808994B1 (en) | 2006-02-22 | 2010-10-05 | Juniper Networks, Inc. | Forwarding traffic to VLAN interfaces built based on subscriber information strings |
US7680926B2 (en) * | 2006-02-27 | 2010-03-16 | International Business Machines Corporation | Apparatus, system, and method for dynamically determining a set of storage area network components for performance monitoring |
WO2007133786A2 (en) | 2006-05-12 | 2007-11-22 | Telsima Corporation | Dynamic vlan ip network entry |
US7716356B2 (en) * | 2006-06-30 | 2010-05-11 | International Business Machines Corporation | Server-based acquisition, distributed acquisition and usage of dynamic MAC addresses in a virtualized Ethernet environment |
CN100544288C (en) * | 2006-07-26 | 2009-09-23 | 鸿富锦精密工业(深圳)有限公司 | Client and connection method for detecting thereof |
EP1885100B1 (en) * | 2006-08-02 | 2009-04-08 | Siemens Aktiengesellschaft | Method for automatic address allocation between communication devices |
CN100589428C (en) * | 2006-08-09 | 2010-02-10 | 华为技术有限公司 | Multi-service and multi-edge device and system |
US20080089323A1 (en) * | 2006-10-13 | 2008-04-17 | At&T Knowledge Ventures, L.P. | System and method for assigning virtual local area networks |
US7706265B2 (en) * | 2006-10-30 | 2010-04-27 | Telefonaktiebolaget L M Ericsson (Publ) | Decentralized node, access edge node, and access node for aggregating data traffic over an access domain, and method thereof |
WO2008065294A1 (en) * | 2006-11-28 | 2008-06-05 | France Telecom | Method of transmitting functional information, corresponding termination equipment, signals and computer programme product |
CN101009669B (en) * | 2007-01-05 | 2011-04-13 | 杭州华三通信技术有限公司 | A method and system and route device for transmitting the multicast message |
ATE536033T1 (en) * | 2007-02-05 | 2011-12-15 | Koninkl Kpn Nv | VLAN NUMBERING IN ACCESS NETWORKS |
US8040820B2 (en) * | 2007-03-06 | 2011-10-18 | Cisco Technology, Inc. | Modelling service flows in dynamic access domains |
EP2007072A1 (en) * | 2007-06-19 | 2008-12-24 | Nokia Siemens Networks Oy | Method for determining user port information for central functions |
US20090097492A1 (en) * | 2007-10-12 | 2009-04-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Support of triple play services in user devices |
CN101414940B (en) * | 2007-10-16 | 2011-12-28 | 华为技术有限公司 | Method for establishing Ethernet business, net element equipment and network system |
EP2220849B1 (en) * | 2007-12-12 | 2019-03-13 | Nokia Technologies Oy | Address assignment protocol |
US9385877B2 (en) * | 2008-09-16 | 2016-07-05 | Adobe Systems Incorporated | Multicast systems, methods, and computer program products |
CN101741702B (en) * | 2008-11-25 | 2012-02-29 | 中兴通讯股份有限公司 | Method and device for limiting broadcast of ARP request |
CA2740881C (en) | 2009-06-26 | 2017-09-19 | Telekom Malaysia Berhad | Method and system for tagging packets routed to customer premises devices via clusters of dedicated customer interfaces |
JP5776337B2 (en) * | 2011-06-02 | 2015-09-09 | 富士通株式会社 | Packet conversion program, packet conversion apparatus, and packet conversion method |
WO2013022481A1 (en) * | 2011-08-10 | 2013-02-14 | Thomson Licensing | Method to selectively add priority tagging to network traffic |
CN102946330B (en) * | 2012-09-29 | 2017-03-15 | 华为技术有限公司 | network packet loss measuring method, device and system |
CN102932792B (en) * | 2012-11-14 | 2016-06-15 | 邦讯技术股份有限公司 | A kind of method realizing wireless network cloud and controller |
US8832321B1 (en) * | 2014-02-12 | 2014-09-09 | tw telecom holdings, inc. | External injection of cloud based network functions into network services |
CN105792265B (en) * | 2014-12-23 | 2019-04-26 | 中国电信股份有限公司 | Malicious traffic stream detection method and system, monitor supervision platform |
CN107113884B (en) * | 2015-01-28 | 2021-07-23 | 苹果公司 | LAA (licensed assisted access) burst control information |
CN105871632A (en) * | 2016-05-31 | 2016-08-17 | 深圳市双赢伟业科技股份有限公司 | Virtual local area network configuration method and device |
CN107888713B (en) * | 2016-09-30 | 2021-10-01 | 中兴通讯股份有限公司 | Method and device for dynamically allocating MAC address and access equipment |
KR102486151B1 (en) * | 2018-10-16 | 2023-01-10 | 현대자동차주식회사 | Communication Device, Vehicle having the same and method for controlling the same |
CN110460683B (en) * | 2019-07-05 | 2022-05-20 | 锐捷网络股份有限公司 | Method and switching equipment for processing data message through gateway |
CN110995717B (en) * | 2019-12-06 | 2022-11-01 | 杭州海康威视数字技术股份有限公司 | Message processing method and device, electronic equipment and vulnerability scanning system |
US11277282B2 (en) | 2020-01-19 | 2022-03-15 | Cisco Technology, Inc. | Micro and macro segmentation in enterprise networks without a per segment layer-3 domain |
CN114599053B (en) * | 2020-12-07 | 2024-04-09 | 中国移动通信集团山西有限公司 | Networking and networking protection method |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5825772A (en) * | 1995-11-15 | 1998-10-20 | Cabletron Systems, Inc. | Distributed connection-oriented services for switched communications networks |
US5835725A (en) * | 1996-10-21 | 1998-11-10 | Cisco Technology, Inc. | Dynamic address assignment and resolution technique |
US20020013844A1 (en) * | 2000-03-20 | 2002-01-31 | Garrett John W. | Service selection in a shared access network supporting quality of service |
US20020036658A1 (en) * | 2000-03-20 | 2002-03-28 | Carolan Sean E. | Method and apparatus for dynamically displaying brand information in a user interface |
US20030130833A1 (en) * | 2001-04-20 | 2003-07-10 | Vern Brownell | Reconfigurable, virtual processing system, cluster, network and method |
US6829250B2 (en) * | 2000-08-10 | 2004-12-07 | Verizon Communications Inc. | Automatic programming of customer premises equipment for vertical services integration |
US20040249927A1 (en) * | 2000-07-17 | 2004-12-09 | David Pezutti | Intelligent network providing network access services (INP-NAS) |
Family Cites Families (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
SE511236C2 (en) | 1996-11-29 | 1999-08-30 | Ericsson Telefon Ab L M | A modem with IP support |
US5898839A (en) * | 1997-03-17 | 1999-04-27 | Geonet Limited, L.P. | System using signaling channel to transmit internet connection request to internet service provider server for initiating and internet session |
US6430621B1 (en) * | 1998-12-29 | 2002-08-06 | Nortel Networks Limited | System using different tag protocol identifiers to distinguish between multiple virtual local area networks |
US6937574B1 (en) | 1999-03-16 | 2005-08-30 | Nortel Networks Limited | Virtual private networks and methods for their operation |
SE9902266L (en) | 1999-06-16 | 2000-10-23 | Ericsson Telefon Ab L M | Device and method of a switched telecommunication system |
SE9902245L (en) | 1999-06-23 | 2000-10-23 | Ericsson Telefon Ab L M | Device and method of a switched telecommunication system |
JP4351349B2 (en) * | 2000-01-31 | 2009-10-28 | パスロジ株式会社 | COMMUNICATION SYSTEM, RELAY DEVICE, SERVICE PROVIDING DEVICE, RELAY METHOD, SERVICE PROVIDING METHOD, AND INFORMATION RECORDING MEDIUM |
WO2001061920A1 (en) * | 2000-02-15 | 2001-08-23 | Jihun Kang | The method and the system for accessing multiple services using a single identifier |
ATE393513T1 (en) * | 2000-03-20 | 2008-05-15 | At & T Corp | METHOD AND APPARATUS FOR COORDINATING SERVICE PROVIDER SWITCHING BETWEEN A CLIENT AND A SERVER USING IDENTITY-BASED SERVICE ACCESS MANAGEMENT |
US7320036B1 (en) * | 2001-04-13 | 2008-01-15 | Redback Networks Inc. | Method and apparatus for multiple communications sessions |
US7450595B1 (en) * | 2001-05-01 | 2008-11-11 | At&T Corp. | Method and system for managing multiple networks over a set of ports |
US7352853B1 (en) * | 2001-05-22 | 2008-04-01 | Cisco Technology, Inc. | Automation of customer premises equipment provisioning in a telecommunications network |
KR100382360B1 (en) * | 2001-07-06 | 2003-05-09 | 주식회사 케이티프리텔 | Method and apparatus for transmitting explict multicast data packet over ethernet |
JP4236398B2 (en) * | 2001-08-15 | 2009-03-11 | 富士通株式会社 | Communication method, communication system, and communication connection program |
US7593318B2 (en) * | 2002-01-07 | 2009-09-22 | Reams Byron L | Method and apparatus for header updating |
US7818409B2 (en) * | 2002-01-22 | 2010-10-19 | Alcatel-Lucent Usa Inc. | Dynamic virtual private network system and methods |
US7260097B2 (en) * | 2002-01-30 | 2007-08-21 | Nortel Networks Limited | Label control method and apparatus for virtual private LAN segment networks |
CN100431305C (en) * | 2002-02-08 | 2008-11-05 | 艾利森电话股份有限公司 | Method and system ralating service providers to clients in an access network, using dynamically allocated MAC addresses |
US20030177125A1 (en) * | 2002-03-18 | 2003-09-18 | Dmitrii Loukianov | Enhanced residential gateway and associated methods |
US7436782B2 (en) * | 2004-03-25 | 2008-10-14 | Alcatel Lucent | Full mesh LSP and full mesh T-LDP provisioning between provider edge routers in support of Layer-2 and Layer-3 virtual private network services |
US7408936B2 (en) * | 2004-08-20 | 2008-08-05 | Alcatel Lucent | Scalable VLAN grouping in a provider Metro Ethernet |
-
2002
- 2002-02-08 CN CNB028279425A patent/CN100431305C/en not_active Expired - Fee Related
- 2002-02-08 WO PCT/SE2002/000226 patent/WO2003067821A1/en not_active Application Discontinuation
- 2002-02-08 DE DE60229786T patent/DE60229786D1/en not_active Expired - Lifetime
- 2002-02-08 AU AU2002230343A patent/AU2002230343A1/en not_active Abandoned
- 2002-02-08 ES ES02711596T patent/ES2315353T3/en not_active Expired - Lifetime
- 2002-02-08 US US10/504,414 patent/US20050160174A1/en not_active Abandoned
- 2002-02-08 AT AT02711596T patent/ATE413747T1/en not_active IP Right Cessation
- 2002-02-08 EP EP02711596A patent/EP1472821B1/en not_active Expired - Lifetime
-
2003
- 2003-01-07 US US10/503,184 patent/US7711824B2/en not_active Expired - Fee Related
- 2003-01-07 CN CNB038035316A patent/CN1331330C/en not_active Expired - Fee Related
- 2003-02-07 CN CNB038035553A patent/CN100353719C/en not_active Expired - Fee Related
- 2003-02-07 WO PCT/SE2003/000210 patent/WO2003067823A1/en not_active Application Discontinuation
- 2003-02-07 DE DE60329275T patent/DE60329275D1/en not_active Expired - Lifetime
- 2003-02-07 WO PCT/SE2003/000211 patent/WO2003067824A1/en not_active Application Discontinuation
- 2003-02-07 US US10/503,183 patent/US20050190775A1/en not_active Abandoned
- 2003-02-07 AU AU2003206543A patent/AU2003206543A1/en not_active Abandoned
- 2003-02-07 AU AU2003206333A patent/AU2003206333A1/en not_active Abandoned
- 2003-02-07 DK DK03703624T patent/DK1472823T3/en active
- 2003-02-07 ES ES03703624T patent/ES2333709T3/en not_active Expired - Lifetime
- 2003-02-07 EP EP03705586A patent/EP1472825A1/en not_active Withdrawn
- 2003-02-07 AT AT03703624T patent/ATE443390T1/en not_active IP Right Cessation
- 2003-02-07 EP EP03703625A patent/EP1472824A1/en not_active Withdrawn
- 2003-02-07 EP EP03703624A patent/EP1472823B1/en not_active Expired - Lifetime
- 2003-02-07 AU AU2003206332A patent/AU2003206332A1/en not_active Abandoned
- 2003-02-07 CN CNB038035529A patent/CN1332540C/en not_active Expired - Fee Related
- 2003-02-07 US US10/502,880 patent/US20050152271A1/en not_active Abandoned
- 2003-02-07 WO PCT/SE2003/000209 patent/WO2003067822A1/en not_active Application Discontinuation
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5825772A (en) * | 1995-11-15 | 1998-10-20 | Cabletron Systems, Inc. | Distributed connection-oriented services for switched communications networks |
US5835725A (en) * | 1996-10-21 | 1998-11-10 | Cisco Technology, Inc. | Dynamic address assignment and resolution technique |
US20020013844A1 (en) * | 2000-03-20 | 2002-01-31 | Garrett John W. | Service selection in a shared access network supporting quality of service |
US20020019875A1 (en) * | 2000-03-20 | 2002-02-14 | Garrett John W. | Service selection in a shared access network |
US20020036658A1 (en) * | 2000-03-20 | 2002-03-28 | Carolan Sean E. | Method and apparatus for dynamically displaying brand information in a user interface |
US20040249927A1 (en) * | 2000-07-17 | 2004-12-09 | David Pezutti | Intelligent network providing network access services (INP-NAS) |
US6829250B2 (en) * | 2000-08-10 | 2004-12-07 | Verizon Communications Inc. | Automatic programming of customer premises equipment for vertical services integration |
US20030130833A1 (en) * | 2001-04-20 | 2003-07-10 | Vern Brownell | Reconfigurable, virtual processing system, cluster, network and method |
Cited By (95)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050160174A1 (en) * | 2002-02-08 | 2005-07-21 | Telefonaktiebolaget Lm Ericsson | Method and system relating service providers to clients in a access network using dynamically allocated mac addresses |
US7626937B2 (en) * | 2002-08-06 | 2009-12-01 | Realtek Semiconductor Corp. | System and method for network connection detection |
US20040037308A1 (en) * | 2002-08-06 | 2004-02-26 | Realtek Semiconductor Corp. | System and method for network connection detection |
US20050111455A1 (en) * | 2003-11-20 | 2005-05-26 | Daiki Nozue | VLAN server |
US8094660B2 (en) * | 2003-11-20 | 2012-01-10 | Hitachi, Ltd. | VLAN server |
US7420979B2 (en) * | 2003-11-20 | 2008-09-02 | Hitachi Communcation Technologies, Ltd. | VLAN server |
US20080310416A1 (en) * | 2003-11-20 | 2008-12-18 | Daiki Nozue | Vlan server |
US20050201381A1 (en) * | 2004-03-12 | 2005-09-15 | Abbasi Salman Y. | Method and apparatus to manage network addresses for private voice communications |
US7907615B2 (en) * | 2004-03-12 | 2011-03-15 | At&T Intellectual Property Ii, L.P. | Method and apparatus to manage network addresses for private voice communications |
US8155125B1 (en) * | 2004-09-17 | 2012-04-10 | Cisco Technology, Inc. | Apparatus and method for utilizing aggregate network links for multicast switching |
US20060120364A1 (en) * | 2004-12-03 | 2006-06-08 | Alcatel | Method for transmitting information from a source via a first network unit and a network and a second network unit to a destination |
US8094657B2 (en) * | 2004-12-03 | 2012-01-10 | Alcatel Lucent | Method for transmitting information from a source via a first network unit and a network and a second network unit to a destination |
US20060184695A1 (en) * | 2005-02-14 | 2006-08-17 | Sylvain Monette | Method and nodes for handling multicast messages |
US7660253B2 (en) * | 2005-02-14 | 2010-02-09 | Telefonaktiebolaget L M Ericsson (Publ) | Method and nodes for aggregating data traffic through unicast messages over an access domain using service bindings |
US7792996B2 (en) * | 2005-02-14 | 2010-09-07 | Telefonaktiebolaget L M Ericsson | Method and nodes for handling multicast messages |
US7801039B2 (en) * | 2005-02-14 | 2010-09-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and nodes for performing bridging of data traffic over an access domain |
US20060184645A1 (en) * | 2005-02-14 | 2006-08-17 | Sylvain Monette | Method and nodes for performing bridging of data traffic over an access domain |
US20060182146A1 (en) * | 2005-02-14 | 2006-08-17 | Sylvain Monette | Method and nodes for aggregating data traffic through unicast messages over an access domain using service bindings |
US7881198B2 (en) * | 2005-04-25 | 2011-02-01 | Telefonaktiebolaget L M Ericsson (Publ) | Method for managing service bindings over an access domain and nodes therefor |
EP2027675A1 (en) * | 2006-06-09 | 2009-02-25 | Telefonaktiebolaget LM Ericsson (PUBL) | Operator managed virtual home network |
EP2027675A4 (en) * | 2006-06-09 | 2017-03-29 | Telefonaktiebolaget LM Ericsson (publ) | Operator managed virtual home network |
WO2007142567A1 (en) | 2006-06-09 | 2007-12-13 | Telefonaktiebolaget Lm Ericsson (Publ.) | Operator managed virtual home network |
US7539189B2 (en) * | 2006-08-01 | 2009-05-26 | Cisco Technology, Inc. | Apparatus and methods for supporting 802.1X in daisy chained devices |
US20080034407A1 (en) * | 2006-08-01 | 2008-02-07 | Cisco Technology, Inc. | Apparatus and methods for supporting 802.1X in daisy chained devices |
US20100284284A1 (en) * | 2009-05-08 | 2010-11-11 | Qualcomm Incorporated | VOICE OVER INTERNET PROTOCOL (VoIP) ACCESS TERMINAL |
WO2011014668A3 (en) * | 2009-07-30 | 2011-06-09 | Zinan Chen | Independent carrier ethernet interconnection platform |
WO2011014668A2 (en) * | 2009-07-30 | 2011-02-03 | Zinan Chen | Independent carrier ethernet interconnection platform |
US20110282996A1 (en) * | 2009-11-19 | 2011-11-17 | Yoram Zahavi | Method and system for dynamically allocating services for subscribers data traffic |
US8886805B2 (en) * | 2009-11-19 | 2014-11-11 | Flash Networks, Ltd | Method and system for dynamically allocating services for subscribers data traffic |
US11838385B2 (en) | 2011-12-14 | 2023-12-05 | Level 3 Communications, Llc | Control in a content delivery network |
US20140372588A1 (en) | 2011-12-14 | 2014-12-18 | Level 3 Communications, Llc | Request-Response Processing in a Content Delivery Network |
US11218566B2 (en) | 2011-12-14 | 2022-01-04 | Level 3 Communications, Llc | Control in a content delivery network |
US9451045B2 (en) | 2011-12-14 | 2016-09-20 | Level 3 Communications, Llc | Content delivery network |
US9456053B2 (en) | 2011-12-14 | 2016-09-27 | Level 3 Communications, Llc | Content delivery network |
US9516136B2 (en) | 2011-12-14 | 2016-12-06 | Level 3 Communications, Llc | Customer-specific request-response processing in a content delivery network |
US10841398B2 (en) | 2011-12-14 | 2020-11-17 | Level 3 Communications, Llc | Control in a content delivery network |
US10187491B2 (en) | 2011-12-14 | 2019-01-22 | Level 3 Communications, Llc | Request-response processing an a content delivery network |
US9641401B2 (en) | 2012-12-13 | 2017-05-02 | Level 3 Communications, Llc | Framework supporting content delivery with content delivery services |
US9749191B2 (en) | 2012-12-13 | 2017-08-29 | Level 3 Communications, Llc | Layered request processing with redirection and delegation in a content delivery network (CDN) |
US9628342B2 (en) | 2012-12-13 | 2017-04-18 | Level 3 Communications, Llc | Content delivery framework |
US9628347B2 (en) | 2012-12-13 | 2017-04-18 | Level 3 Communications, Llc | Layered request processing in a content delivery network (CDN) |
US9634906B2 (en) | 2012-12-13 | 2017-04-25 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services with feedback |
US9634905B2 (en) | 2012-12-13 | 2017-04-25 | Level 3 Communications, Llc | Invalidation systems, methods, and devices |
US9634904B2 (en) | 2012-12-13 | 2017-04-25 | Level 3 Communications, Llc | Framework supporting content delivery with hybrid content delivery services |
US9634918B2 (en) | 2012-12-13 | 2017-04-25 | Level 3 Communications, Llc | Invalidation sequencing in a content delivery framework |
US9634907B2 (en) | 2012-12-13 | 2017-04-25 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services with feedback |
US9628343B2 (en) | 2012-12-13 | 2017-04-18 | Level 3 Communications, Llc | Content delivery framework with dynamic service network topologies |
US9641402B2 (en) | 2012-12-13 | 2017-05-02 | Level 3 Communications, Llc | Configuring a content delivery network (CDN) |
US9647900B2 (en) | 2012-12-13 | 2017-05-09 | Level 3 Communications, Llc | Devices and methods supporting content delivery with delivery services |
US9647899B2 (en) | 2012-12-13 | 2017-05-09 | Level 3 Communications, Llc | Framework supporting content delivery with content delivery services |
US9647901B2 (en) | 2012-12-13 | 2017-05-09 | Level 3 Communications, Llc | Configuring a content delivery network (CDN) |
US9654356B2 (en) | 2012-12-13 | 2017-05-16 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services |
US9654355B2 (en) | 2012-12-13 | 2017-05-16 | Level 3 Communications, Llc | Framework supporting content delivery with adaptation services |
US9654354B2 (en) | 2012-12-13 | 2017-05-16 | Level 3 Communications, Llc | Framework supporting content delivery with delivery services network |
US9654353B2 (en) | 2012-12-13 | 2017-05-16 | Level 3 Communications, Llc | Framework supporting content delivery with rendezvous services network |
US9660875B2 (en) | 2012-12-13 | 2017-05-23 | Level 3 Communications, Llc | Devices and methods supporting content delivery with rendezvous services having dynamically configurable log information |
US9660874B2 (en) | 2012-12-13 | 2017-05-23 | Level 3 Communications, Llc | Devices and methods supporting content delivery with delivery services having dynamically configurable log information |
US9660876B2 (en) | 2012-12-13 | 2017-05-23 | Level 3 Communications, Llc | Collector mechanisms in a content delivery network |
US9661046B2 (en) | 2012-12-13 | 2017-05-23 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services |
US9667506B2 (en) | 2012-12-13 | 2017-05-30 | Level 3 Communications, Llc | Multi-level peering in a content delivery framework |
US9686148B2 (en) | 2012-12-13 | 2017-06-20 | Level 3 Communications, Llc | Responsibility-based cache peering |
US9705754B2 (en) | 2012-12-13 | 2017-07-11 | Level 3 Communications, Llc | Devices and methods supporting content delivery with rendezvous services |
US20140223018A1 (en) * | 2012-12-13 | 2014-08-07 | Level 3 Communications, Llc | Content Delivery Framework With Autonomous CDN Partitioned into Multiple Virtual CDNs |
US9722882B2 (en) | 2012-12-13 | 2017-08-01 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services with provisioning |
US9722884B2 (en) | 2012-12-13 | 2017-08-01 | Level 3 Communications, Llc | Event stream collector systems, methods, and devices |
US9722883B2 (en) | 2012-12-13 | 2017-08-01 | Level 3 Communications, Llc | Responsibility-based peering |
US9628346B2 (en) | 2012-12-13 | 2017-04-18 | Level 3 Communications, Llc | Devices and methods supporting content delivery with reducer services |
US9749190B2 (en) | 2012-12-13 | 2017-08-29 | Level 3 Communications, Llc | Maintaining invalidation information |
US9749192B2 (en) | 2012-12-13 | 2017-08-29 | Level 3 Communications, Llc | Dynamic topology transitions in a content delivery framework |
US9755914B2 (en) | 2012-12-13 | 2017-09-05 | Level 3 Communications, Llc | Request processing in a content delivery network |
US9787551B2 (en) | 2012-12-13 | 2017-10-10 | Level 3 Communications, Llc | Responsibility-based request processing |
US9819554B2 (en) | 2012-12-13 | 2017-11-14 | Level 3 Communications, Llc | Invalidation in a content delivery framework |
US9847917B2 (en) | 2012-12-13 | 2017-12-19 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services with feedback |
US9887885B2 (en) | 2012-12-13 | 2018-02-06 | Level 3 Communications, Llc | Dynamic fill target selection in a content delivery framework |
US10135697B2 (en) | 2012-12-13 | 2018-11-20 | Level 3 Communications, Llc | Multi-level peering in a content delivery framework |
US10142191B2 (en) * | 2012-12-13 | 2018-11-27 | Level 3 Communications, Llc | Content delivery framework with autonomous CDN partitioned into multiple virtual CDNs |
US9628345B2 (en) | 2012-12-13 | 2017-04-18 | Level 3 Communications, Llc | Framework supporting content delivery with collector services network |
US10608894B2 (en) | 2012-12-13 | 2020-03-31 | Level 3 Communications, Llc | Systems, methods, and devices for gradual invalidation of resources |
US10652087B2 (en) | 2012-12-13 | 2020-05-12 | Level 3 Communications, Llc | Content delivery framework having fill services |
US10701149B2 (en) | 2012-12-13 | 2020-06-30 | Level 3 Communications, Llc | Content delivery framework having origin services |
US10701148B2 (en) | 2012-12-13 | 2020-06-30 | Level 3 Communications, Llc | Content delivery framework having storage services |
US10700945B2 (en) | 2012-12-13 | 2020-06-30 | Level 3 Communications, Llc | Role-specific sub-networks in a content delivery framework |
US10708145B2 (en) | 2012-12-13 | 2020-07-07 | Level 3 Communications, Llc | Devices and methods supporting content delivery with adaptation services with feedback from health service |
US10742521B2 (en) | 2012-12-13 | 2020-08-11 | Level 3 Communications, Llc | Configuration and control in content delivery framework |
US10791050B2 (en) | 2012-12-13 | 2020-09-29 | Level 3 Communications, Llc | Geographic location determination in a content delivery framework |
US10826793B2 (en) | 2012-12-13 | 2020-11-03 | Level 3 Communications, Llc | Verification and auditing in a content delivery framework |
US9628344B2 (en) | 2012-12-13 | 2017-04-18 | Level 3 Communications, Llc | Framework supporting content delivery with reducer services network |
US10841177B2 (en) | 2012-12-13 | 2020-11-17 | Level 3 Communications, Llc | Content delivery framework having autonomous CDN partitioned into multiple virtual CDNs to implement CDN interconnection, delegation, and federation |
US10862769B2 (en) | 2012-12-13 | 2020-12-08 | Level 3 Communications, Llc | Collector mechanisms in a content delivery network |
US10931541B2 (en) | 2012-12-13 | 2021-02-23 | Level 3 Communications, Llc | Devices and methods supporting content delivery with dynamically configurable log information |
US10992547B2 (en) | 2012-12-13 | 2021-04-27 | Level 3 Communications, Llc | Rendezvous systems, methods, and devices |
US11121936B2 (en) | 2012-12-13 | 2021-09-14 | Level 3 Communications, Llc | Rendezvous optimization in a content delivery framework |
US11368548B2 (en) | 2012-12-13 | 2022-06-21 | Level 3 Communications, Llc | Beacon services in a content delivery framework |
US20150131674A1 (en) * | 2013-11-13 | 2015-05-14 | Institute For Information Industry | Management server and management method thereof for managing cloud appliances in virtual local area networks |
US9705847B2 (en) * | 2013-11-13 | 2017-07-11 | Institute For Information Industry | Management server and management method thereof for managing cloud appliances in virtual local area networks |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20050190775A1 (en) | System and method for establishing service access relations | |
CN100566334C (en) | Dynamic Service is selected and the end user disposes Ethernet Digital Subscriber Line Access Multiplexer and method are provided | |
CN101006707B (en) | Method for switching Ip packets between client networks and Ip provider networks by means of an access network | |
US6189042B1 (en) | LAN internet connection having effective mechanism to classify LAN traffic and resolve address resolution protocol requests | |
US8260887B2 (en) | Method for automatic configuration of an access router compatible with the DHCP protocol, for specific automatic processing of IP flows from a client terminal | |
US5581552A (en) | Multimedia server | |
EP2241091B1 (en) | Combining locally addressed devices and wide area network (wan) addressed devices on a single network | |
US7639689B2 (en) | Method for exchanging packets of user data | |
US20060182113A1 (en) | Automatic discovery of pseudo-wire peer addresses in ethernet-based networks | |
CN103329506B (en) | Identify privately owned device in the public network | |
EP1075749A1 (en) | Establishing connectivity in networks | |
WO2006125594A2 (en) | Traffic diversion in an ethernet-based access network | |
WO1997048210A1 (en) | Logical ip address assignment in atm lan | |
US20070263538A1 (en) | Directed Pppoe Session Initiation Over a Switched Ethernet | |
US20100254396A1 (en) | Method of connecting vlan systems to other networks via a router | |
US7570647B2 (en) | LAN type internet access network and subscriber line accommodation method for use in the same network | |
Cisco | Configuring the DHCP Option 82 for Subscriber Identification | |
KR20040011936A (en) | Switching apparatus for ethernet having a plurality of vlans and communication method by using same | |
JP2003078548A (en) | Subscriber wireless access system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL), SWEDEN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TONNBY, INGMAR;LARSSON, ULF;REEL/FRAME:015825/0528;SIGNING DATES FROM 20040815 TO 20040818 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |