Abstract: A method of enabling extension of a network service of a first domain to a remote customer site hosted by an Access Gateway (AG) in a Provider Ethernet domain. In the first domain, the remote customer site is represented as being hosted by a border gateway (BG) connected to the Provider Ethernet domain, such that subscriber packets associated with the network service are forwarded to or from the remote customer site via the BG. In the Provider Ethernet domain, a trunk connection is instantiated through the Provider Ethernet domain between the host AG and the BG. A trunk cross-connection function is installed in the host AG, for transferring subscriber packets associated with the network service between a respective attachment virtual circuit (AVC) through which the remote customer site is connected to the host AG and an extended AVC tunnelled through the trunk connection.

Abstract: Data between a client and a server is pinned through a receiving interworking unit and a transmitting interworking unit connected via a non-IP based communications path. The receiving interworking unit and transmitting interworking unit convert received data between IP and a non-IP based communications protocols. The transmitting interworking unit receives IP data for the client from the server. The data is converted and transmitted via the non-IP based communications link to the receiving interworking unit, which converts the data back into an IP format and forwards the converted data on to the client. One segment of the path between server and client transports the data in a non-IP format. Neither IP client nor the server are aware of the non IP segment and no change in their IP network mode of operation is required.

Abstract: Data between a client and a server is pinned through a receiving interworking unit and a transmitting interworking unit connected via a non-IP based communications path. The receiving interworking unit and transmitting interworking unit convert received data between IP and a non-IP based communications protocols. The transmitting interworking unit receives IP data for the client from the server. The data is converted and transmitted via the non-IP based communications link to the receiving interworking unit, which converts the data back into an IP format and forwards the converted data on to the client. One segment of the path between server and client transports the data in a non-IP format. Neither IP client nor the server are aware of the non IP segment and no change in their IP network mode of operation is required.

Abstract: Methods and systems for extending the IMS/SIP architecture of the NGN to provide QoS service to generic bearer flows. QoS treatment of a bearer flow destined to a non-SIP client attached to the network via an attachment segment connected to an attachment gateway is supported. A SIP-INVITE message is received in respect of the bearer flow. The SIP-INVITE message contains a Universal Resource Identifier (URI) identifying the non-SIP client as a destination of the bearer flow. An attempt is made to install a QoS policy on the attachment segment in accordance with a Traffic Specification (T-Spec) identified in the SIP-INVITE message, and the result of the installation attempt detected. A appropriate SIP messaging is generated on behalf of the non-SIP client, to either accept or refuse the bearer flow, based on the detected result.

Abstract: A system for interfacing a client system in a first network domain with a Provider Link State Bridging (PLSB) domain includes at least two Backbone Edge Bridges (BEBs) of the PLSB domain. Each BEB is an end-point of a connection in the first network domain to the client system and an end-point of at least a unicast path in the PLSB domain. An inter-node trunk is provided in the PLSB domain for interconnecting the BEBs. A phantom node is defined in the PLSB domain and is notionally located on the inter-node trunk. Each of the BEBs is configured such that: an ingress packet received from the client system via the connection in the first network domain is forwarded through a path notionally rooted at the phantom node; and an egress packet destined for the client system is forwarded to the client system through the connection in the first network domain.

Abstract: Data between a client and a server is pinned through a receiving interworking unit and a transmitting interworking unit connected via a non-IP based communications path. The receiving interworking unit and transmitting interworking unit convert received data between IP and a non-IP based communications protocols. The transmitting interworking unit receives IP data for the client from the server. The data is converted and transmitted via the non-IP based communications link to the receiving interworking unit, which converts the data back into an IP format and forwards the converted data on to the client. One segment of the path between server and client transports the data in a non-IP format. Neither IP client nor the server are aware of the non IP segment and no change in their IP network mode of operation is required.

Abstract: A method of enabling extension of a network service of a first domain to a remote customer site hosted by an Access Gateway (AG) in a Provider Ethernet domain. In the first domain, the remote customer site is represented as being hosted by a border gateway (BG) connected to the Provider Ethernet domain, such that subscriber packets associated with the network service are forwarded to or from the remote customer site via the BG. In the Provider Ethernet domain, a trunk connection is instantiated through the Provider Ethernet domain between the host AG and the BG. A trunk cross-connection function is installed in the host AG, for transferring subscriber packets associated with the network service between a respective attachment virtual circuit (AVC) through which the remote customer site is connected to the host AG and an extended AVC tunnelled through the trunk connection.

Abstract: A method of enabling extension of a network service of a first domain to a remote customer site hosted by an Access Gateway (AG) in a Provider Ethernet domain. In the first domain, the remote customer site is represented as being hosted by a border gateway (BG) connected to the Provider Ethernet domain, such that subscriber packets associated with the network service are forwarded to or from the remote customer site via the BG. In the Provider Ethernet domain, a trunk connection is instantiated through the Provider Ethernet domain between the host AG and the BG. A trunk cross-connection function is installed in the host AG, for transferring subscriber packets associated with the network service between a respective attachment virtual circuit (AVC) through which the remote customer site is connected to the host AG and an extended AVC tunnelled through the trunk connection.

Abstract: A system for interfacing a client system in a first network domain with a Provider Link State Bridging (PLSB) domain includes at least two Backbone Edge Bridges (BEBs) of the PLSB domain. Each BEB is an end-point of a connection in the first network domain to the client system and an end-point of at least a unicast path in the PLSB domain. An inter-node trunk is provided in the PLSB domain for interconnecting the BEBs. A phantom node is defined in the PLSB domain and is notionally located on the inter-node trunk. Each of the BEBs is configured such that: an ingress packet received from the client system via the connection in the first network domain is forwarded through a path notionally rooted at the phantom node; and an egress packet destined for the client system is forwarded to the client system through the connection in the first network domain.

Abstract: A system for interfacing a client system in a first network domain with a Provider Link State Bridging (PLSB) domain includes at least two Backbone Edge Bridges (BEBs) of the PLSB domain. Each BEB is an end-point of a connection in the first network domain to the client system and an end-point of at least a unicast path in the PLSB domain. An inter-node trunk is provided in the PLSB domain for interconnecting the BEBs. A phantom node is defined in the PLSB domain and is notionally located on the inter-node trunk. Each of the BEBs is configured such that: an ingress packet received from the client system via the connection in the first network domain is forwarded through a path notionally rooted at the phantom node; and an egress packet destined for the client system is forwarded to the client system through the connection in the first network domain.

Abstract: A pseudo-wire merge is disclosed. Communicating with a first communication server enables registration of a first endpoint with the first communication server thereby enabling the first endpoint to establish a communication session under control of the first communication server with a second endpoint coupled to the communication network. Communicating with a second communication server enables registration of the first endpoint with the second communication server while the first endpoint is registered with the first communication server thereby enabling the first endpoint to establish a communication session over the communication network selectively either under the control of the second communication server or under the control of the first communication server.

Abstract: An Internet Priority Service (IPS) provides to authorized users priority access to communication over the Internet during emergencies. Transmission of data packets from an authorized user that accesses the IPS are given priority for transmission over the Internet. The level of priority given to a data packet depends on the type of application associated with the data packet. Each user or group of users may also be given a respective IPS level of priority. Furthermore, for a particular authorized user, access to the IPS may be limited to a specific number of application types, which for example do not have high bandwidth requirements. Assigning different priority levels as a function of application type and user or group of users, and limiting IPS access to specific application types allows efficient methods of emergency communication to be implemented over the Internet during emergencies.

Abstract: An Internet Priority Service (IPS) provides to authorized users priority access to communication over the Internet during emergencies. Transmission of data packets from an authorized user that accesses the IPS are given priority for transmission over the Internet. The level of priority given to a data packet depends on the type of application associated with the data packet. Each user or group of users may also be given a respective IPS level of priority. Furthermore, for a particular authorized user, access to the IPS may be limited to a specific number of application types, which for example do not have high bandwidth requirements. Assigning different priority levels as a function of application type and user or group of users, and limiting IPS access to specific application types allows efficient methods of emergency communication to be implemented over the Internet during emergencies.

Abstract: A method of enabling extension of a network service of a first domain to a remote customer site hosted by an Access Gateway (AG) in a Provider Ethernet domain. In the first domain, the remote customer site is represented as being hosted by a border gateway (BG) connected to the Provider Ethernet domain, such that subscriber packets associated with the network service are forwarded to or from the remote customer site via the BG. In the Provider Ethernet domain, a trunk connection is instantiated through the Provider Ethernet domain between the host AG and the BG. A trunk cross-connection function is installed in the host AG, for transferring subscriber packets associated with the network service between a respective attachment virtual circuit (AVC) through which the remote customer site is connected to the host AG and an extended AVC tunnelled through the trunk connection.

Abstract: A method of enabling extension of a network service of a first domain to a remote customer site hosted by an Access Gateway (AG) in a Provider Ethernet domain. In the first domain, the remote customer site is represented as being hosted by a border gateway (BG) connected to the Provider Ethernet domain, such that subscriber packets associated with the network service are forwarded to or from the remote customer site via the BG. In the Provider Ethernet domain, a trunk connection is instantiated through the Provider Ethernet domain between the host AG and the BG. A trunk cross-connection function is installed in the host AG, for transferring subscriber packets associated with the network service between a respective attachment virtual circuit (AVC) through which the remote customer site is connected to the host AG and an extended AVC tunnelled through the trunk connection.

Abstract: A system for interfacing a client system in a first network domain with a Provider Link State Bridging (PLSB) domain includes at least two Backbone Edge Bridges (BEBs) of the PLSB domain. Each BEB is an end-point of a connection in the first network domain to the client system and an end-point of at least a unicast path in the PLSB domain. An inter-node trunk is provided in the PLSB domain for interconnecting the BEBs. A phantom node is defined in the PLSB domain and is notionally located on the inter-node trunk. Each of the BEBs is configured such that: an ingress packet received from the client system via the connection in the first network domain is forwarded through a path notionally rooted at the phantom node; and an egress packet destined for the client system is forwarded to the client system through the connection in the first network domain.

Abstract: A method of enabling extension of a network service of a first domain to a remote customer site hosted by an Access Gateway (AG) in a Provider Ethernet domain. In the first domain, the remote customer site is represented as being hosted by a border gateway (BG) connected to the Provider Ethernet domain, such that subscriber packets associated with the network service are forwarded to or from the remote customer site via the BG. In the Provider Ethernet domain, a trunk connection is instantiated through the Provider Ethernet domain between the host AG and the BG. A trunk cross-connection function is installed in the host AG, for transferring subscriber packets associated with the network service between a respective attachment virtual circuit (AVC) through which the remote customer site is connected to the host AG and an extended AVC tunnelled through the trunk connection.

Abstract: The downstream IP packets of uni-cast services, such as Internet Access or Voice over IP network, are transported over the pseudo wire from service provider nodes at the metro hub to the access edge, whereupon they are converted to be transported on the first mile technology, such as a DSL loop, that serves the subscriber's residence. A television service provider delivers the collection of television channels through the regional network to an intermediate node, herein called the metro edge device. The function of the metro edge for downstream uni-cast traffic is to de-multiplex the downstream pseudo-wires coming on packet trunks from metro hubs, into a greater number of packet trunks leading to access edges. In this invention the metro edge device is operable to unicast individual selected channels to the subscriber's residence by adding copies of the IP packets of the selected channels into the downstream flow of packets in the subscriber's pseudo wire.

Abstract: An Internet Priority Service (IPS) provides to authorized users priority access to communication over the Internet during emergencies. Transmission of data packets from an authorized user that accesses the IPS are given priority for transmission over the Internet. The level of priority given to a data packet depends on the type of application associated with the data packet. Each user or group of users may also be given a respective IPS level of priority. Furthermore, for a particular authorized user, access to the IPS may be limited to a specific number of application types, which for example do not have high bandwidth requirements. Assigning different priority levels as a function of application type and user or group of users, and limiting IPS access to specific application types allows efficient methods of emergency communication to be implemented over the Internet during emergencies.

Abstract: A method system for interfacing a client system in a first network domain with a Provider Link State Bridging (PLSB) network domain. At least two Backbone Edge Bridges (BEBs) of the PLSB domain 20 are provided. Each BEB is an end-point of a connection in the first network domain to the client system and an end-point of at least a unicast path defined within the PLSB domain 20. An inter-node trunk is provided in the PLSB domain 20 for interconnecting the at least two BEBs. A phantom node is defined in the PLSB domain 20. The phantom node has a unique address in the PLSB domain 20 and is notionally located on the inter-node trunk one hop from each of the BEBs. Each of the BEBs is configured such that: an ingress packet received from the client system via the connection in the first network domain is forwarded through a path notionally rooted at the phantom node; and an egress subscriber packet destined for the client system is forwarded to the client system through the connection in the first network domain.