Abstract: A geo-fencing system includes a plurality of beacons defining zones within a venue. The system receives a first beacon identifier from a mobile device and registers the mobile device in a first zone corresponding to the first beacon. The system causes a first menu to be displayed on the mobile device, indicating options for the first zone. In response to selection of one of the options, the system registers the mobile device as being active in the first zone. The system then receives a second beacon identifier and registers the mobile device as being in the second zone. The system also suspends the activity of the mobile device in the first zone and causes options to be displayed to continue or terminate the activity in the first zone.

Abstract: A geo-fencing system includes a plurality of beacons defining zones within a venue. The system receives a first beacon identifier from a mobile device and registers the mobile device in a first zone corresponding to the first beacon. The system causes a first menu to be displayed on the mobile device, indicating options for the first zone. In response to selection of one of the options, the system registers the mobile device as being active in the first zone. The system then receives a second beacon identifier and registers the mobile device as being in the second zone. The system also suspends the activity of the mobile device in the first zone and causes options to be displayed to continue or terminate the activity in the first zone.

Abstract: Single sign on (SSO) functionality is provided across native and hybrid applications executing on a mobile communication device, such that both native and hybrid applications can access authenticated services offered through respective application servers without repeatedly providing authentication credentials. In operation, the mobile device obtains an SSO token from an SSO server providing the SSO functionality, and native applications executing on the mobile device retrieve the SSO token from memory for use in accessing authenticated services. In the case of hybrid applications, an alias is assigned to the mobile device in response to receiving a page request received from the hybrid application. The alias is associated with SSO token of the mobile device in the SSO server, and is used to provide the SSO token directly to the hybrid application from the SSO server such that the hybrid application can use the SSO token for authentication.

Abstract: Single sign on (SSO) functionality is provided across native and hybrid applications executing on a mobile communication device, such that both native and hybrid applications can access authenticated services offered through respective application servers without repeatedly providing authentication credentials. In operation, the mobile device obtains an SSO token from an SSO server providing the SSO functionality, and native applications executing on the mobile device retrieve the SSO token from memory for use in accessing authenticated services. In the case of hybrid applications, an alias is assigned to the mobile device in response to receiving a page request received from the hybrid application. The alias is associated with SSO token of the mobile device in the SSO server, and is used to provide the SSO token directly to the hybrid application from the SSO server such that the hybrid application can use the SSO token for authentication.