Secure sharing of LOB bound information in client applications
First Claim
1. A method to be executed at least in part in a computing device for providing secure sharing of bound items between clients associated with a Line Of Business (LOB) service, the method comprising:
- in response to detecting an exchange attempt for a bound item, placing, by the computing device, the bound item in a pending state, the bound item comprising bound information, the bound information comprising identifiable information, with at least one of a unique name and an identifier, that is directly under the control of at least one of the clients and is simultaneously tracked and maintained by the LOB service;
forwarding, by the computing device, the exchange attempt to the LOB service;
if data transfer is successfully completed and affirmation is received from the LOB service, moving, by the computing device, the bound item to a bound state enabling a receiver to access the bound item and associated bound data;
if data transfer is successfully completed but affirmation is not received from the LOB service, moving, by the computing device, the bound item to an unbound state preventing the receiver from accessing the bound data associated with the bound item; and
if data transfer is not successfully completed, moving, by the computing device, the bound item to a failed state and notifying a sender attempting the exchange.
2 Assignments
0 Petitions
Accused Products
Abstract
Secure sharing of bound information is enabled in client applications associated with a backend LOB service. Bound item IDs are assigned to newly created bound items by a client, the items synchronized with the LOB system, a correlation ID received in response to the synchronization, and the two IDs mapped. A reverse sequence of actions is performed when the LOB service creates the bound item. In response to an attempt by a client to exchange bound information, the item is placed in a pending state and allowed to be received by a receiver upon successful completion of data transfer and LOB system permission of the exchange passing the bound item ID and the correlation ID. If the LOB system rejects the exchange, the item is placed in an unbound state and the receiver not allowed to receive the bound information.
-
Citations
20 Claims
-
1. A method to be executed at least in part in a computing device for providing secure sharing of bound items between clients associated with a Line Of Business (LOB) service, the method comprising:
-
in response to detecting an exchange attempt for a bound item, placing, by the computing device, the bound item in a pending state, the bound item comprising bound information, the bound information comprising identifiable information, with at least one of a unique name and an identifier, that is directly under the control of at least one of the clients and is simultaneously tracked and maintained by the LOB service; forwarding, by the computing device, the exchange attempt to the LOB service; if data transfer is successfully completed and affirmation is received from the LOB service, moving, by the computing device, the bound item to a bound state enabling a receiver to access the bound item and associated bound data; if data transfer is successfully completed but affirmation is not received from the LOB service, moving, by the computing device, the bound item to an unbound state preventing the receiver from accessing the bound data associated with the bound item; and if data transfer is not successfully completed, moving, by the computing device, the bound item to a failed state and notifying a sender attempting the exchange. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. A system for providing secure sharing of bound items by a client application associated with an LOB service, the system comprising:
-
a memory; a processor coupled to the memory, wherein the processor is configured to execute program modules including; a collaborative application to provide a user interface and maintain records associated with calendar items of a user, wherein a portion of the calendar items are bound items with extended LOB properties, the bound items comprising bound information, the bound information comprising identifiable information, with at least one of a unique name and an identifier that is directly under the control of the client application and is simultaneously tracked and maintained by the LOB service; a bound item manager module configured to; receive a client generated bound item ID assigned to a newly created bound item; receive a correlation ID from the LOB service in response to synchronizing the bound item, wherein the client generated bound item ID is not understood by the LOB service and wherein the correlation ID is used as a parameter to identify the bound information; map the correlation ID with the client generated bound item ID; place the bound item in a pending state in response to detecting an exchange attempt for the bound item; move the bound item to a bound state enabling a receiver to access bound data associated with the bound item in response to successful data completion and affirmation from the LOB service; move the bound item to an unbound state preventing the receiver from accessing the bound data in response to a successful data completion but lack of affirmation from the LOB service; move the bound item to a failed state and notifying a sender attempting the exchange in response to an unsuccessful data completion; request affirmation from the LOB system using the correlation ID and the bound item ID, wherein the LOB service determines whether to allow the exchange based on a set of authorization and compliance rules; and a synchronization module to synchronize bound items between the collaborative application and the LOB service. - View Dependent Claims (13, 14, 15, 16)
-
-
17. A computer-readable storage medium with instructions stored thereon for securely sharing bound items between clients associated with an LOB service, the instructions comprising:
-
receiving a client generated bound item ID assigned to a newly created bound item, the bound item comprising bound information, the bound information comprising identifiable information, with at least one of a unique name and an identifier, that is directly under the control of at least one of the clients and is simultaneously tracked and maintained by the LOB service; receiving a correlation ID from the LOB service in response to synchronizing the bound item, wherein the client generated bound item ID is not understood by the LOB service and wherein the correlation ID is used as a parameter to identify the bound information; mapping the correlation ID with the client generated bound item ID; placing the bound item in a pending state in response to detecting an exchange attempt for the bound item; and moving the bound item to a bound state enabling a receiver to access bound data associated with the bound item in response to successful data completion and affirmation from the LOB service; moving the bound item to an unbound state preventing the receiver from accessing the bound data in response to a successful data completion but lack of affirmation from the LOB service; and moving the bound item to a failed state and notifying a sender attempting the exchange in response to an unsuccessful data completion. - View Dependent Claims (18, 19, 20)
-
Specification