Abstract: A method is provided by a network element to execute a forwarding information base (FIB) manager to program a packet forwarding function of the network element. The FIB manager supports a hybrid control plane with software defined networking (SDN) and local control plane processes. The method includes receiving a request to configure a node reachability configuration element, where the node reachability element describes packet processing instruction for the packet forwarding function to forward packets toward a referred node, selecting a flow control agent to be updated for reachability to the referred node, and updating a logical forwarding information representation to encode a next hop identifier for the referred node.

Abstract: A method (100), performed by a first network node in a communication network, is disclosed. The first network node is connected to a second network node of the communication network via an interface implementing a GPRS Tunnelling Protocol (GTP). The method comprises selecting a user data packet for transmission to the second network node (110) and identifying information about the user data packet which impacts how the user data packet should be routed over the interface (120). The method further comprises encoding the identified information into a User Datagram Protocol (UDP) header of the user data packet (130) and forwarding the user data packet to the interface for transmission to the second network node (140). Another method (300) is disclosed, performed by a node in a Mobile Transport Network, the Mobile Transport Network providing a GTP based interface between a first network node of a communication network and a second network node of the communication network.

Abstract: The present disclosure generally relates to packet processing by a network element system that transfers first and second packet flows of the same traffic handling class (e.g., the Ethernet express traffic class). A method aspect performed by the network element system comprises the step of receiving, from a network controller, information defining opening times for packet gates associated with network element ports. The opening times define a relative transmission order among first packet flow packets and second packet flow packets. Upon receipt of first and second packet flow packets at the respective ports, the packet gates are controlled based on the received information to trigger transmission of the first and second packet flow packets in the predefined transmission order.

Abstract: A method performed by a network element that transfers first and second packet flows of the same traffic handling class comprises the step of receiving, from a network controller, information defining a relative forwarding order between first and second packet flow packets. Upon receipt, at least one ingress port of the network element, of a first and a second packet, determining that the first packet belongs to the first packet flow and the second packet to the second packet flow. The first and second packets will then be forwarded towards at least one egress port of the network element in an order defined by the information received from the network controller.

Abstract: A method is provided by a network element to execute a forwarding information base (FIB) manager to program a packet forwarding function of the network element. The FIB manager supports a hybrid control plane with software defined networking (SDN) and local control plane processes. The method includes receiving a request to configure a node reachability configuration element, where the node reachability element describes packet processing instruction for the packet forwarding function to forward packets toward a referred node, selecting a flow control agent to be updated for reachability to the referred node, and updating a logical forwarding information representation to encode a next hop identifier for the referred node.

Abstract: A router receives, from a BGP peer, a BGP update message including NLRI (VPN-NLRI) specific to a virtual private network, as well as path information including an address of a next hop for the VPN-NLRI. The router determines that there is no route to the next hop, modifies the filtering information to permit propagation of NLRI including the address of the next hop, and sends the modified filtering information to BGP neighbors. Alternatively, a router determines that such a BGP update message is due to be sent to a BGP peer. The router determines that the filtering information does not allow propagation, to the peer, of NLRI including the address of the next-hop, modifies the filtering information so as to permit propagation, to the BGP peer, of NLRI including the address of the next hop, and sends the BGP update message to the peer.

Abstract: A pseudowire redundancy network comprises a plurality of pseudowires (PW13, PW 14) attached to a provider edge node (201). For selecting an active pseudowire (PW13) to be used for forwarding user traffic, the provider edge node (201) determines a local preferential forwarding status for each of the pseudowires (PW13, PW14). The determined preferential forwarding status is active for no more than one of the pseudowires (PW13, PW14). The provider edge node (201) indicates the determined local preferential forwarding status of the pseudowires (PW13, PW14) to remote provider edge nodes (203, 204). Further, the provider edge node (201) receives indications of a remote preferential forwarding status for each of the pseudowires (PW13, PW14) from the remote provider edge nodes (203, 204). The provider edge node (201) then selects that one of the pseudowires (PW13, PW14) as active for which both the local preferential forwarding status and the remote preferential forwarding status is active.

Abstract: Exemplary methods for allocating multiple local sub-blocks (LsBs) of segment identifiers (IDs) include allocating a first set of LsBs, each LsB associated with a start index and a range, wherein the start index indicates a starting SID of a corresponding LsB and the range indicates a total number of SIDs included in the corresponding LsB, each LsB identified by a sub-block number. In one embodiment, the methods include mapping a plurality of segment routing global block (SRGB) indexes to a plurality of corresponding SIDs of the first set of LsBs, the mapping performed based on the SRGB indexes, start indexes of each LsB, and ranges of SIDs of each LsB. In one embodiment, the methods include advertising the first set of LsBs by transmitting a first advertisement message that includes the start indexes, ranges of SIDs, and sub-block numbers of all LsBs of the first set of LsBs.

Abstract: The present invention relates to a method and embodiments thereof in a Radio Node, a node, computer program and computer program products for adapting of Radio Coordination schemes to transport network characteristics. The method comprises detecting new neighbours, retrieving transport characteristics values between radio neighbours, validity checking of the active Radio Coordination scheme(s), and updating of Radio Coordination scheme, if necessary, based on the measured transport characteristics values.

Abstract: Methods and apparatus are disclosed for applying multiple Link Aggregation Group (LAG) entities on the same set of physical links, thus making bundling of individual services or conversations possible by the different LAG entities within Link Aggregation. Each LAG entity is configured such that a single physical link is Active and all the other links are Standby. Each LAG entity may be regarded as a “bundle.” Thus the services/conversations are bundled into a LAG entity and are handed-off on the Active link during normal operation. If service hand-off is not possible on the Active link (e.g., due to a failure), then the LAG entity switches over to a Standby link thus the service/conversation is handed-off on that formerly Standby link. Bundling may simplify operations of control and signaling.

Abstract: Exemplary methods for allocating multiple local sub-blocks (LsBs) of segment identifiers (IDs) include allocating a first set of LsBs, each LsB associated with a start index and a range, wherein the start index indicates a starting SID of a corresponding LsB and the range indicates a total number of SIDs included in the corresponding LsB, each LsB identified by a sub-block number. In one embodiment, the methods include mapping a plurality of segment routing global block (SRGB) indexes to a plurality of corresponding SIDs of the first set of LsBs, the mapping performed based on the SRGB indexes, start indexes of each LsB, and ranges of SIDs of each LsB. In one embodiment, the methods include advertising the first set of LsBs by transmitting a first advertisement message that includes the start indexes, ranges of SIDs, and sub-block numbers of all LsBs of the first set of LsBs.

Abstract: A router receives, from a BGP peer, a BGP update message including NLRI (VPN-NLRI) specific to a virtual private network, as well as path information including an address of a next hop for the VPN-NLRI. The router determines that there is no route to the next hop, modifies the filtering information to permit propagation of NLRI including the address of the next hop, and sends the modified filtering information to BGP neighbours. Alternatively, a router determines that such a BGP update message is due to be sent to a BGP peer. The router determines that the filtering information does not allow propagation, to the peer, of NLRI including the address of the next-hop, modifies the filtering information so as to permit propagation, to the BGP peer, of NLRI including the address of the next hop, and sends the BGP update message to the peer.

Abstract: A pseudowire redundancy network comprises a plurality of pseudowires (PW13, PW 14) attached to a provider edge node (201). For selecting an active pseudowire (PW13) to be used for forwarding user traffic, the provider edge node (201) determines a local preferential forwarding status for each of the pseudowires (PW13, PW14). The determined preferential forwarding status is active for no more than one of the pseudowires (PW13, PW14). The provider edge node (201) indicates the determined local preferential forwarding status of the pseudowires (PW13, PW14) to remote provider edge nodes (203, 204). Further, the provider edge node (201) receives indications of a remote preferential forwarding status for each of the pseudowires (PW13, PW14) from the remote provider edge nodes (203, 204). The provider edge node (201) then selects that one of the pseudowires (PW13, PW14) as active for which both the local preferential forwarding status and the remote preferential forwarding status is active.

Abstract: A technique for status change handling in an interconnect node is described, wherein the node comprises a data plane that can assume, per service, a passive or active status. A method aspect in the node comprises transmitting, to another node, a first indication that a change has been or is about to be performed, awaiting, from the other node, reception of a second indication that the data plane in the other node has been set to the passive status, and activating, responsive to the received indication, the data plane of the node from the passive status to the active status. The method aspect in the other node further comprises receiving, from the node, the first indication, passivating, responsive to the receiving step, the data plane being in the active status to the passive status, and transmitting, upon completion of the passivating step, the second indication.

Abstract: The present invention relates to the combination of memantine and baclofen active ingredients, and also to the method for achieving body weight loss and thereby treating obesity and related co-morbidities by co-administration of baclofen and memantine.

Abstract: Methods and apparatus are disclosed for applying multiple Link Aggregation Group (LAG) entities on the same set of physical links, thus making bundling of individual services or conversations possible by the different LAG entities within Link Aggregation. Each LAG entity is configured such that a single physical link is Active and all the other links are Standby. Each LAG entity may be regarded as a “bundle.” Thus the services/conversations are bundled into a LAG entity and are handed-off on the Active link during normal operation. If service hand-off is not possible on the Active link (e.g., due to a failure), then the LAG entity switches over to a Standby link thus the service/conversation is handed-off on that formerly Standby link. Bundling may simplify operations of control and signaling.