Abstract: A uniform protocol can facilitate secure, authenticated communication between a controller device and an accessory device that is controlled by the controller. An accessory and a controller can establish a pairing, the existence of which can be verified at a later time and used to create a secure communication session. The accessory can provide an accessory definition record that defines the accessory as a collection of services, each service having one or more characteristics. Within a secure communication session, the controller can interrogate the characteristics to determine accessory state and/or modify the characteristics to instruct the accessory to change its state.

Abstract: A uniform protocol can facilitate secure, authenticated communication between a controller device and an accessory device that is controlled by the controller. An accessory and a controller can establish a pairing, the existence of which can be verified at a later time and used to create a secure communication session. The accessory can provide an accessory definition record that defines the accessory as a collection of services, each service having one or more characteristics. Within a secure communication session, the controller can interrogate the characteristics to determine accessory state and/or modify the characteristics to instruct the accessory to change its state.

Abstract: Described are call handling methods performed by a carrier network or client stations. A method performed by a carrier network includes designating rules for call handling for an account, receiving first and second voice calls for the account, wherein the voice calls may be either an incoming calls or originated calls and handling the first and second voice calls for the account based on the rules. A method performed by a client station includes receiving a first invitation to a first call, responding to the first invitation causing the first call to be active, receiving a second invitation to a second call while the first call remains active and responding to the second invitation causing the second call to be active and the first call to be on hold, the client station is prevented from originating a call when one call is active and one call is on hold.

Abstract: In some implementations, a user device (or resident device) can notify the user of anomalous accessory states. For example, the user device can determine which accessory states and contexts represent normal accessory states in the respective contexts. Similarly to scene suggestions, the user device can analyze historical accessory state data and context data to determine an accessory state pattern that indicates a normal state of an accessory for a given context. The user device can compare the current state and/or context of an accessory to historical accessory state data to determine when the current state of the accessory is abnormal for the current context. If the current accessory state is abnormal for the current context, the user device can present a notification to the user informing the user of the anomalous accessory state.

Abstract: In some implementations, a user device can automatically generate scene suggestions and/or trigger suggestions. For example, a scene can be a collection of accessories and corresponding accessory states. When the scene is invoked, the user device can cause the accessories associated with the scene to assume the corresponding accessory states. The user device can automatically determine the accessories and/or corresponding accessory states for a scene based on historical patterns of use represented in historical accessory state data. The user device can automatically determine triggers for automatically invoking scenes based on historical patterns of use. For example, the user device can analyze historical context (e.g., location, time, accessory state, etc.) data associated with accessory state transitions to determine triggers for automatically invoking a scene. The user device can present suggest scenes and/or triggers to the user of the user device.

Abstract: In some implementations, a user device can automatically generate scene suggestions and/or trigger suggestions. For example, a scene can be a collection of accessories and corresponding accessory states. When the scene is invoked, the user device can cause the accessories associated with the scene to assume the corresponding accessory states. The user device can automatically determine the accessories and/or corresponding accessory states for a scene based on historical patterns of use represented in historical accessory state data. The user device can automatically determine triggers for automatically invoking scenes based on historical patterns of use. For example, the user device can analyze historical context (e.g., location, time, accessory state, etc.) data associated with accessory state transitions to determine triggers for automatically invoking a scene. The user device can present suggest scenes and/or triggers to the user of the user device.

Abstract: Described are call handling methods performed by a carrier network or client stations. A method performed by a carrier network includes designating rules for call handling for an account, receiving first and second voice calls for the account, wherein the voice calls may be either an incoming calls or originated calls and handling the first and second voice calls for the account based on the rules. A method performed by a client station includes receiving a first invitation to a first call, responding to the first invitation causing the first call to be active, receiving a second invitation to a second call while the first call remains active and responding to the second invitation causing the second call to be active and the first call to be on hold, the client station is prevented from originating a call when one call is active and one call is on hold.

Abstract: A method performed by a provisioning server, the method including receiving registration data from a client station, transmitting activation data to a telephony service provider, the activation data generated as a function of the registration data, the activation data being used to generate telephony data for the user, the telephony data including access data to utilize a telephony network of the telephony service provider and transmitting the telephony data to the client station, wherein select portions of the telephony data and select portions of the activation data verify the client station as an authenticated device to utilize the telephony network.

Abstract: Described are call handling methods performed by a carrier network or client stations. A method performed by a carrier network includes designating rules for call handling for an account, receiving first and second voice calls for the account, wherein the voice calls may be either an incoming calls or originated calls and handling the first and second voice calls for the account based on the rules. A method performed by a client station includes receiving a first invitation to a first call, responding to the first invitation causing the first call to be active, receiving a second invitation to a second call while the first call remains active and responding to the second invitation causing the second call to be active and the first call to be on hold, the client station is prevented from originating a call when one call is active and one call is on hold.

Abstract: A uniform protocol can facilitate secure, authenticated communication between a controller device and an accessory device that is controlled by the controller. An accessory and a controller can establish a pairing, the existence of which can be verified at a later time and used to create a secure communication session. The accessory can provide an accessory definition record that defines the accessory as a collection of services, each service having one or more characteristics. Within a secure communication session, the controller can interrogate the characteristics to determine accessory state and/or modify the characteristics to instruct the accessory to change its state.

Abstract: A uniform protocol can facilitate secure, authenticated communication between a controller device and an accessory device that is controlled by the controller. An accessory and a controller can establish a pairing, the existence of which can be verified at a later time and used to create a secure communication session. The accessory can provide an accessory definition record that defines the accessory as a collection of services, each service having one or more characteristics. Within a secure communication session, the controller can interrogate the characteristics to determine accessory state and/or modify the characteristics to instruct the accessory to change its state.

Abstract: A uniform protocol can facilitate secure, authenticated communication between a controller device and an accessory device that is controlled by the controller. An accessory and a controller can establish a pairing, the existence of which can be verified at a later time and used to create a secure communication session. The accessory can provide an accessory definition record that defines the accessory as a collection of services, each service having one or more characteristics. Within a secure communication session, the controller can interrogate the characteristics to determine accessory state and/or modify the characteristics to instruct the accessory to change its state.

Abstract: In some implementations, a user device (or resident device) can notify the user of anomalous accessory states. For example, the user device can determine which accessory states and contexts represent normal accessory states in the respective contexts. Similarly to scene suggestions, the user device can analyze historical accessory state data and context data to determine an accessory state pattern that indicates a normal state of an accessory for a given context. The user device can compare the current state and/or context of an accessory to historical accessory state data to determine when the current state of the accessory is abnormal for the current context. If the current accessory state is abnormal for the current context, the user device can present a notification to the user informing the user of the anomalous accessory state.

Abstract: In some implementations, a user device can automatically generate scene suggestions and/or trigger suggestions. For example, a scene can be a collection of accessories and corresponding accessory states. When the scene is invoked, the user device can cause the accessories associated with the scene to assume the corresponding accessory states. The user device can automatically determine the accessories and/or corresponding accessory states for a scene based on historical patterns of use represented in historical accessory state data. The user device can automatically determine triggers for automatically invoking scenes based on historical patterns of use. For example, the user device can analyze historical context (e.g., location, time, accessory state, etc.) data associated with accessory state transitions to determine triggers for automatically invoking a scene. The user device can present suggest scenes and/or triggers to the user of the user device.

Abstract: Apparatus and method for maintaining hardware history profiles for a software-based emulator. In one embodiment, the disclosed software-based emulator monitors the history of the actual hardware device in a secondary device history, the history of the emulated hardware is presented within a primary device history. However, the primary device history is linked to the secondary device history, and receives the device wear history therefrom. In another aspect of the present invention, wear-leveling strategies are disclosed for handling various update sizes. Unlike existing solutions which are optimized for a single SIM that receives small data updates; various embodiments of the present invention are suitable for handling varying data sizes.

Abstract: Registering a client computing device for online communication sessions. A registration server receives a message that has a push token that is unique to the client computing device and a phone number of the client computing device from an SMS (Short Message Service) transit device, which received an SMS message having the push token from the client computing device and determined the phone number of the client computing device from that SMS message. The registration server associates the push token and the phone number and stores it in a registration data store, which is used for inviting users for online communication sessions.

Abstract: Apparatus and methods for distributing access control clients. In one exemplary embodiment, a network infrastructure is disclosed that enables delivery of electronic subscriber identity modules (eSIMs) to secure elements (e.g., electronic Universal Integrated Circuit Cards (eUICCs), etc.) The network architecture includes one or more of: (i) eSIM appliances, (ii) secure eSIM storages, (iii) eSIM managers, (iv) eUICC appliances, (v) eUICC managers, (vi) service provider consoles, (vii) account managers, (viii) Mobile Network Operator (MNO) systems, (ix) eUICCs that are local to one or more devices, and (x) depots. Moreover, each depot may include: (xi) eSIM inventory managers, (xii) system directory services, (xiii) communications managers, and/or (xiv) pending eSIM storages. Functions of the disclosed infrastructure can be flexibly partitioned and/or adapted such that individual parties can host portions of the infrastructure.

Abstract: Apparatus and method for maintaining hardware history profiles for a software-based emulator. In one embodiment, the disclosed software-based emulator monitors the history of the actual hardware device in a secondary device history, the history of the emulated hardware is presented within a primary device history. However, the primary device history is linked to the secondary device history, and receives the device wear history therefrom. In another aspect of the present invention, wear-leveling strategies are disclosed for handling various update sizes. Unlike existing solutions which are optimized for a single SIM that receives small data updates; various embodiments of the present invention are suitable for handling varying data sizes.

Abstract: Methods and apparatus for the automated updating of forwarding preferences for communications in a telecommunications network. In one embodiment, the network includes a wireless (e.g., cellular) network with user mobile user devices configured to detect a change to their configuration (such as a user changing out SIM cards or virtual access clients). In response, the device causes an update to its associated communication forwarding preferences to reflect the change. If the configuration alteration meets certain criteria (e.g., changes the phone number at which the device may be reached), the device sends a forwarding message instructing a network entity (e.g., routing server) to direct communications addressed to the old phone number to the new phone number. Thus, a user with two or more user profiles (such as two different carrier accounts) may be reached at any number associated with any of the profiles, even if only one profile is currently active.

Abstract: Apparatus and method for maintaining hardware history profiles for a software-based emulator. In one embodiment, the disclosed software-based emulator monitors the history of the actual hardware device in a secondary device history, the history of the emulated hardware is presented within a primary device history. However, the primary device history is linked to the secondary device history, and receives the device wear history therefrom. In another aspect of the present invention, wear-leveling strategies are disclosed for handling various update sizes. Unlike existing solutions which are optimized for a single SIM that receives small data updates; various embodiments of the present invention are suitable for handling varying data sizes.