Microsoft Technology Licensing, LLC

Alcatel Lucent

Alcatel Canada Inc.

Rashid Qureshi

Jorge I Raastroem

Shai Herzog

Scott Michael Bragg

Xuemei Bao

Qian Zhang

Rajeev Bansal

Abolade Gbadegesin

Anand Muthurajan

Jithendra K Veeramachaneni

Robert Craig

Carolyn Elaine Duke

Victor J Major

Robert De Vlugt

Wlodek Olesinski

Mark Woodward

Embodiments enable recovery of push notification channels via session information associated with user identifiers. A proxy service creates session information describing push notification channels (e.g., subscriptions) for a user and associates the session information with a user identifier. The session information is stored in a cloud service or other storage area separate from the proxy service. After failure of a user computing device or the proxy service, the session information is obtained via the user identifiers and the push notification channels are re-created with the session information. In some embodiments, the proxy service enables delivery of the same notification to multiple computing devices associated with the user identifier.

Re-establishing push notification channels via user identifiers

Systems and methods for use in communication between a client and a server, via a networking device, are provided. The method may include sending a request to establish a data connection from the client to the server via the networking device, setting a data connection keep-alive interval for the data connection to a predetermined safe value, and sending a request to establish a test connection between the client and the server. The method may further include determining an efficient keep-alive interval for communication between the client and server via the networking device, using the test connection, setting the data connection keep-alive interval to the efficient keep-alive interval determined using the test connection, and uploading the efficient keep-alive interval from the client to the server in an efficient keep-alive interval notification message, for communication to other clients connected to the server.

Determining an efficient keep-alive interval for a network connection

Techniques and tools for flexible authentication and authorization of services on a push framework. For example, a push notification framework allows services (social networking web services, etc.) to use either an authenticated access mode or an unauthenticated access mode, in order to push information to client devices (e.g., mobile devices). In the authenticated mode, the push framework requires registration of the service with the push framework before allowing the service to push notifications to client devices. Different authenticated modes are provided for third-party and first-party services. In the unauthenticated mode, registration is not required, but notifications are throttled, thereby limiting risk of abuse by unauthenticated services. This allows flexibility for services that use the push framework.

Flexible authentication and authorization mechanism

A method is provided for verifying an Element Management System-Network Management System (EMS-NMS) interface. A pattern file is used in a test tool that can emulate an NMS for testing the respective EMS side of the EMS-NMS interface. The pattern file includes specifications on valid data which may be sent to or received from the EMS, such as valid data ranges, allowed actions on specific devices, and valid data values for objects for various software releases. The pattern file can be created based on the design interface specifications for new EMS and NMS software releases, which provides a significant benefit because it allows interface verification to be decoupled from EMS and NMS verification, which can greatly shorten the verification cycle of new EMS/NMS software releases.

Automated QS interface testing framework

A system and method are provided for throttling event messages to be sent to a network management system (NMS), so as to avoid overflow of element management system (EMS) buffers. Three states are defined for buffers within a proxy: low, high, and full. Changes between states occur as the fill-level of the buffers crosses thresholds. When the proxy buffers are in the low state, the event logger of an EMS forwards all event messages to the proxy, which are then forwarded to the NMS. When the proxy buffers are in the high state, the EMS only forwards high priority messages to the proxy. Low priority messages are stored within the EMS. When the proxy buffers are in a full state, the EMS does not forward any messages to the proxy. In this way, event messages are throttled, thereby reducing the frequency of network reconciliation, in a way which does not further burden the Qs channel process.

Throttling network management and element management system messaging

A method and apparatus of initiating a plurality of requests for statistics to be sent to an associated plurality of nodes in a segment of a communication network is provided. One or more requests are associated with an individual node. Each node has one or more node attributes. The method includes defining a sequence for initiating the requests to be sent to the nodes. The sequence is based on a value of a selected node attribute of each node. The method also includes initiating the requests according to the sequence.

Method and apparatus for processing requests for statistics in a communication network

Growing community of inventors

Redmond, WA, United States of America

Rashid Qureshi