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:
Methods and systems for extending the IMS/SIP architecture of the NGN to provide QoS service to generic bearer flows. More particularly, a method is provided for establishing an bearer end-to-end path of a communication session in a multi-domain communication network in which an out of band signalling protocol is used to establish communications sessions. The method comprises receiving an out-of-band signalling message including information representative of at least an opposite end point of a first bearer segment of the end-to-end path. The information is used to define a cross-connect mapping through a node of the network between respective local endpoints of the first bearer segment and a second bearer segment hosted by the node. Information representative of the cross-connect mapping is then inserted into the out-of-band signalling message, and the out-of-band signalling message forwarded.
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.
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.