Abstract: Systems and methods for generating and broadcasting a dynamic identifier are presented. Based on the current context and rules established for accessing personal information, a dynamic identifier corresponding to a computer user is dynamically generated and provided to a computing device corresponding to the computer user. The computing device may broadcast the dynamic identifier to others. Upon receipt of a dynamic identifier, a party wishing to determine information regarding the broadcasting party must query an information service with the dynamic identifier. According to a set of rules and/or permissions established for the target computer user (broadcasting the dynamic identifier), accessible information is identified and returned to the requesting party. Additionally, a user is provided with the ability to edit, add to, and/or delete information that is stored by the identification service regarding the user on behalf of a submitting party.

Abstract: Broadcasts from beacon devices each of which is disposed in a known different physical location within a venue are controlled. Scheduling information for events scheduled to take place at the venue may be collected from calendar management sources and analyzed. Notification of an emergent event associated with the venue or its geographic location may also be received from emergent event notification sources and analyzed. The result of these analyses and the knowledge of the physical location of each of the beacon devices are used to generate a set of broadcast rules for each of the beacon devices, where these rules specify one or more beacon signals to be periodically broadcast by the beacon device and the timing by which these signals are to be broadcast. For each of the beacon devices, the set of broadcast rules for the beacon device is downloaded to the beacon device.

Abstract: The described technology provides a system and method for dynamically managing a listen list for beacon aware devices. A mobile device may be configured to listen for one or more beacon UUIDs based on a listen list. A contextual change detected by the mobile device may trigger a collection of additional contextual information and update to the listen list based on the additional contextual information. Using the described technology, the mobile device may use a limited set of beacon UUIDs to improve micro-location granularity and enhance the mobile device's resources.

Abstract: Systems and methods for generating and broadcasting a dynamic identifier are presented. Based on the current context and rules established for accessing personal information, a dynamic identifier corresponding to a computer user is dynamically generated and provided to a computing device corresponding to the computer user. The computing device may broadcast the dynamic identifier to others. Upon receipt of a dynamic identifier, a party wishing to determine information regarding the broadcasting party must query an information service with the dynamic identifier. According to a set of rules and/or permissions established for the target computer user (broadcasting the dynamic identifier), accessible information is identified and returned to the requesting party. Additionally, a user is provided with the ability to edit, add to, and/or delete information that is stored by the identification service regarding the user on behalf of a submitting party.

Abstract: The described technology provides a system and method for dynamically managing a listen list for beacon aware devices. A mobile device may be configured to listen for one or more beacon UUIDs based on a listen list. A contextual change detected by the mobile device may trigger a collection of additional contextual information and update to the listen list based on the additional contextual information. Using the described technology, the mobile device may use a limited set of beacon UUIDs to improve micro-location granularity and enhance the mobile device's resources.

Abstract: Systems and methods for generating and broadcasting a dynamic identifier are presented. Based on the current context and rules established for accessing personal information, a dynamic identifier corresponding to a computer user is dynamically generated and provided to a computing device corresponding to the computer user. The computing device may broadcast the dynamic identifier to others. Upon receipt of a dynamic identifier, a party wishing to determine information regarding the broadcasting party must query an information service with the dynamic identifier. According to a set of rules and/or permissions established for the target computer user (broadcasting the dynamic identifier), accessible information is identified and returned to the requesting party.

Abstract: Broadcasts from beacon devices each of which is disposed in a known different physical location within a venue are controlled. Scheduling information for events scheduled to take place at the venue may be collected from calendar management sources and analyzed. Notification of an emergent event associated with the venue or its geographic location may also be received from emergent event notification sources and analyzed. The result of these analyses and the knowledge of the physical location of each of the beacon devices are used to generate a set of broadcast rules for each of the beacon devices, where these rules specify one or more beacon signals to be periodically broadcast by the beacon device and the timing by which these signals are to be broadcast. For each of the beacon devices, the set of broadcast rules for the beacon device is downloaded to the beacon device.

Abstract: Methods and systems for processing a signaling message are disclosed. An exemplary method comprises: determining a first transcoding policy associated with an originator endpoint contained in a received first call offer; determining a second transcoding policy associated with an answerer endpoint contained in the first call offer; applying the first transcoding policy to a first offer codec set in the first call offer to produce a second call offer containing a second offer codec set; applying the second transcoding policy to the second codec set to produce a third call offer containing a third offer codec set; comparing a first answerer codec set in a received first answer and a second answerer codec set contained in the second call offer; and determining whether or not to perform transcoding based on a result of the comparison.

Abstract: Graphical visual representations of electronic business cards may be generated from associated contact file information. Electronic business cards may be sent and received over digital media. Contacts information associated with received electronic business cards may be used for adding to or updating information contained in a recipient's electronic contact files.

Abstract: Systems and methods for redundancy in a network device are disclosed. An exemplary device comprises: a controller residing on a data forwarding element (DFE), the DFE performing data forwarding operations; and a first and a second control processor. Each of the control processors has either an active role or a standby role with respect to the DFE controller. The active-role control processor communicates with the DFE to configure the DFE forwarding operations and receives at least some communications from the DFE controller over a virtual channel. The DFE controller directs traffic on the virtual channel that is destined for the active-role control processor to either the first or the second control processor based on which of the control processors currently has the active role.

Abstract: Information is retrieved from the registry by creating a registry interface database containing information regarding registry data and uniquely identifying every registry entry for a registry interface. Source header files are generated using information about a program module, such as an application, contained in the registry interface database. The source header files are compiled with the application to generate the application's executable file. During run-time of the application, the registry interface is called by the application to retrieve registry data. If available, the registry interface retrieves the registry data and forwards this information to the application. In the event that the registry data is not available, the registry interface retrieves a default value in place of the registry data and forwards that default data to the application. A policy may be implemented by checking a policy area of the registry for the registry data and invoking the policy.

Abstract: Retrieving information form from the registry include by creating a registry interface database containing information regarding registry data and uniquely identifying every registry entry for a registry interface. Source header files are generated using information about a program module, such as an application, contained in the registry interface database. The source header files are compiled with the application to generate the application's executable file. During run-time of the application, the registry interface is called by the application to retrieve registry data. If available, the registry interface retrieves the registry data and forwards this information to the application. In the event that the registry data is not available, the registry interface retrieves a default value in place of the registry data and forwards that default data to the application. A policy may be implemented by checking a policy area of the registry for the registry data and invoking the policy.

Abstract: Retrieving information form from the registry include by creating a registry interface database containing information regarding registry data and uniquely identifying every registry entry for a registry interface. Source header files are generated using information about a program module, such as an application, contained in the registry interface database. The source header files are compiled with the application to generate the application's executable file. During run-time of the application, the registry interface is called by the application to retrieve registry data. If available, the registry interface retrieves the registry data and forwards this information to the application. In the event that the registry data is not available, the registry interface retrieves a default value in place of the registry data and forwards that default data to the application. A policy may be implemented by checking a policy area of the registry for the registry data and invoking the policy.

Abstract: Retrieving information form from the registry include by creating a registry interface database containing information regarding registry data and uniquely identifying every registry entry for a registry interface. Source header files are generated using information about a program module, such as an application, contained in the registry interface database. The source header files are compiled with the application to generate the application's executable file. During run-time of the application, the registry interface is called by the application to retrieve registry data. If available, the registry interface retrieves the registry data and forwards this information to the application. In the event that the registry data is not available, the registry interface retrieves a default value in place of the registry data and forwards that default data to the application. A policy may be implemented by checking a policy area of the registry for the registry data and invoking the policy.