TWI627541B - Forwarding activity-related information from source electronic devices to companion electronic devices - Google Patents

Abstract

The described embodiment transfers an activity from a source electronic device to a companion electronic device. The source electronic device receives activity information describing an activity executed in a first application at the source electronic device and broadcasts an activity announcement that includes an activity identifier for the activity. After receiving the event announcement, the companion electronic device determines whether a second application associated with the first application is available at the companion electronic device. If the second application is available, the companion electronic device obtains extended activity data from the source electronic device and uses the extended activity data to configure the second application and start the second application at the companion electronic device The program performs the activity. The source electronic device may also forward information related to the activity (for example, information copied and pasted from one of the source electronic devices to the accompanying electronic device).

Description

Forward information related to activities from source electronic device to accompanying electronic device

The disclosed embodiments relate to electronic devices. More specifically, the disclosed embodiments relate to the transfer of information related to activities from a source electronic device to a companion electronic device.

The latest developments in computer technology have enabled manufacturers to produce high-power computing devices of various appearance sizes, thereby enabling users to use small and portable devices such as smartphones or tablets to perform desktop or laptop-type devices that previously required The task of the supercomputer. As a result of these developments, users often own and use multiple computing devices, such as smart phones while on the road, tablet computers during meetings, and laptop or desktop computers at the table. Although the user may have different devices each with powerful computing power, in some cases, the user may find that he or she uses a device that is not suitable for the task being performed or the user's situation. For example, a user may start to expect a shorter email on a device such as a smart phone with a small display screen, and then attributable to the size of the display screen when the email result is longer than expected, It may be difficult to enter and edit text in emails. Alternatively, the user may read a web page or watch a movie on the desktop computer but may have to leave the room where the desktop computer is located. Although the user can capture another device and start the task, this is cumbersome.

Related application This application is a partial continuation application of the pending US Patent Application No. 14 / 586,566, and the priority of this case is hereby claimed. The US Patent Application No. 14 / 586,566 is entitled "Activity Continuation between Electronic Devices", The case was applied on December 30, 2014. This application also claims the priority of the now-expired U.S. Provisional Patent Application No. 62 / 005,781, which is titled "Activity Continuation between Electronic Devices" and it was applied on May 30, 2014, and the original application 14 / 586,566 also claimed its priority. These two applications are incorporated by reference. This application is related to the United States Patent Application, which was filed by the inventors Marc J. Krochmal, Christopher S. Linn, John J. Iarocci, Geoffrey Stahl, and Jacques P. Gasselin de Richebourg on the same date as this application. No. 14 / 586,511, the title of the case is "Companion Application for Activity Cooperation", and the case has the agent case number APL-P23129US1. This application is also related to US Patent Application No. 14 / 475,329 in the application filed by inventors Craig P. Dooley, Akshay Mangalam Srivatsa, Anjali S. Sandesara and Michael J. Giles on September 2, 2014. The title of the case is "Operating Mode Transitions based on Advertising Information", and the case has the agent case number APL-P22643US1. This application is also related to US Patent Application No. 14 / 474,466 in the application filed by inventors Jason C. Conn, Akshay Mangalam Srivatsa, Craig P. Dooley and Michael J. Giles on September 2, 2014. The case title is "Predefined Wireless Pairing", and the case has the agent case number APL-P22642US1. This application is further about the inventors Christopher S. Linn, Keith Stattenfield, Christopher C. Jensen, Alexander R. Ledwith, David A. Carter, Marc J. Krochmal, John J. Iarocci and Jonathan M. Grynspan in December 2014 U.S. Patent Application No. 14 / 586,566 in the application filed on May 30, the title of the case is "Activity Continuation between Electronic Devices", and the case has attorney case number APL-P22791US1. Each of the applications described above is incorporated herein by reference. The following description is presented to enable any person skilled in the art to make and use the described embodiments, and to provide the following description in the context of specific applications and their requirements. Those skilled in the art will readily understand various modifications to the described embodiments, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the described embodiments. Therefore, the described embodiments are not limited to the shown embodiments, but are intended to conform to the broadest scope consistent with the principles and features disclosed herein. In some embodiments, an electronic device (such as electronic device 100 and / or a portion thereof in FIG. 1) uses program code and / or data stored on a computer-readable storage medium to perform some of the operations described herein Or all. More specifically, the electronic device reads the code and / or data from the computer-readable storage medium and executes the code and / or usage data when performing the described operation. In such embodiments, the computer-readable storage medium may be any device or medium that stores the program code and / or data used by the electronic device, or a combination thereof. For example, computer-readable storage media may include (but is not limited to) volatile memory or non-volatile memory, such as semiconductor memory (eg, flash memory, random access memory (eDRAM, RAM, SRAM , DRAM, DDR, DDR2 / DDR3 / DDR4 SDRAM, etc.) and / or magnetic or optical storage media (such as disk drives, tapes, CDs, DVDs). In the described embodiments, computer-readable storage media does not include illegal computer-readable storage media such as temporary signals. In some embodiments, one or more hardware modules are configured to perform the operations described herein. For example, hardware modules may include (but are not limited to) one or more processors / cores / central processing units (CPUs), application specific integrated circuit (ASIC) chips, field programmable gate arrays (FPGAs) , Cache memory / cache memory controller, memory management unit, computing unit, embedded processor, graphics processor (GPU) / graphics core, pipeline and / or other programmable logic devices. When these hardware modules are activated, the hardware modules perform some or all of the operations. In some embodiments, the hardware module includes one or more general circuits configured to execute operations by executing instructions (program code, firmware, etc.). In this description, reference may be made to functional blocks when describing some embodiments. Generally speaking, a functional block includes one or more associated circuits, devices, and / or mechanisms that perform one or more of the described operations. In some embodiments, at least some of the functional blocks include general-purpose processing circuits that execute program code (eg, microcode, firmware, application programs, etc.) that causes the general-purpose processing circuits to perform the described operations.Overview The described embodiment transfers the activities performed at the source electronic device from the source electronic device to the companion electronic device-a process that is referred to as "continuing" the activity in the companion electronic device. In the described embodiment, to perform the transfer, the source electronic device sends information describing the activities performed in the first application at the source electronic device to the accompanying electronic device. The companion electronic device then uses some or all of the information to configure the second application at the companion electronic device to perform the corresponding activity. In general, an activity includes one or more operations that are performed at least in part at the source electronic device, and the one or more operations are transferred to / continue on the companion electronic device. Examples of activities include reading and / or editing documents (such as word processing documents, spreadsheets, presentations or other types of documents), writing email messages, emails, voice messages or videos, drafting notes, accessing (browsing) websites, Watch movies, play audio files, or use applications or apps in other ways to perform corresponding operations. In some embodiments, when transferring activities from a source device to a companion device, the source electronic device first uses a wireless network interface (such as Bluetooth Low Energy (BLE), Zigbee, etc.) to broadcast an event announcement message (also known as " Upcoming Events"). In some embodiments, the source electronic device generates an activity identifier for the activity executed in the first application at the source electronic device and includes the activity identifier in the activity announcement message. The source electronic device generates an activity identifier by performing a set of operations (such as a hash operation, etc.) using activity information describing activities received from the first application. The following describes an example of event information in more detail with reference to FIG. 11. As the electronic device monitors the network for the activity announcement message on the network interface (eg, Bluetooth low energy network), the network interface corresponds to the network interface in the source electronic device from which the activity announcement is broadcast. After detecting the event announcement broadcast from the source electronic device, the companion electronic device compares the event identifier used for the event available at the companion electronic device with the event identifier in the event announcement message. The companion electronic device uses this comparison to determine whether a second application program that can execute an activity corresponding to the activity executed in the first application program is available at the companion electronic device. In some embodiments, after determining that the second application is available, the accompanying electronic device is established via a communication channel (eg, using the same wireless network interface or different network interface (wireless and / or wired) used to receive the event announcement message) Communication with the source electronic device. The accompanying electronic device then uses the communication channel to request the source electronic device for extended activity data for the activity performed in the first application. In some embodiments, after receiving the request for the extension activity data, the source electronic device uses the same (or different) communication channel to provide the extension activity data to the companion electronic device. Generally speaking, extended activity data includes information that can be used to configure the second application accompanying the electronic device to continue the activity, such as document identifiers, scrolling locations, and uniform resources related to activities performed in the first application Locator (URL), etc. In some embodiments, the companion electronic device uses the activity identifier and / or extended activity data to configure the second application to perform activities corresponding to the activities performed in the first application at the source electronic device. Then, the companion electronic device starts to perform activities in the second application at the companion electronic device. For example, after configuring the second application with the electronic device, the user can use the accompanying electronic device to continue working on the document that the user is working at the source electronic device, and continue to watch Movies, continue to browse web pages that users browse at source electronic devices, and so on. In some embodiments, the accompanying electronic device sends a notification to the source electronic device to indicate that the activity is transferred to the second application. The notification may enable the source electronic device and / or the first application to perform housekeeping tasks, such as deleting the draft document of the activity, closing the open document of the activity, and so on. In some embodiments, in addition to the activity identifier and / or extended activity data described above, the source electronic device forwards information related to the activity to the accompanying electronic device. For example, in some embodiments, the source electronic device forwards some or all of the contents of the copy and paste scrapbook (or "scrapbook") in the source electronic device to the accompanying electronic device. After receiving the information related to the activity, the accompanying electronic device provides the information related to the activity for performing the activity (eg, the transferred activity or other activities) in the accompanying electronic device. For example, in some or all of the embodiments in which the contents of the scrapbook are transferred from the source electronic device, the companion electronic device may use the contents of the scrapbook received from the source electronic device to overwrite the scrapbook in the companion electronic device Some or all of the existing content. In this way, the companion electronic device can make the contents of the scrapbook from the source electronic device (that is, information related to the activity) available to accompany the activity in the electronic device. For example, text, images, videos, sounds, files, fields, and / or text copied to (or otherwise placed in) the scrapbook (top) in the source electronic device can be made via the scrapbook accompanying the electronic device Or other information can be used to accompany activities in electronic devices. By performing the operations described above at the companion electronic device to continue the activities performed at the source electronic device, the described embodiments enable the user to continue tasks smoothly and without complex user intervention. This allows users to more easily perform tasks on the desired electronic device, which can improve the overall experience for users with two or more electronic devices.Electronic device FIG. 1 presents a block diagram illustrating an electronic device 100 according to some embodiments. The electronic device 100 includes a processing subsystem 102, a memory subsystem 104, a network connection subsystem 106, and a display subsystem 108. The processing subsystem 102 is a functional block that performs calculation operations in the electronic device 100. The processing subsystem 102 includes one or more central processing units (CPUs) / CPU cores, graphics processing units (GPUs) / GPU cores, embedded processors, application-specific integrated circuits (ASICs), and / or other computing mechanisms. The memory subsystem 104 is a functional block that stores data and / or commands for use by other functional blocks in the electronic device 100 (such as the processing subsystem 102, etc.). The memory subsystem 104 includes volatile memory circuits such as dynamic random access memory (DRAM), static random access memory (SRAM), and / or other types of memory for storing instructions and data, and The mechanism used to control the memory circuit. In some embodiments, the memory subsystem 104 includes a memory hierarchy with one or more cache memories coupled to the memory circuit. In some of these embodiments, the processing subsystem 102 also includes one or more cache memories that are part of the memory hierarchy. In some embodiments, the memory subsystem 104 is coupled to one or more non-volatile high-capacity mass storage devices (not shown). For example, the memory subsystem 104 may be coupled to a magnetic or optical disk drive, a solid-state drive, or another type of mass storage device. In these embodiments, the memory subsystem 104 can be used by the electronic device 100 as a fast-access storage for frequently used data, and a mass storage device is used to store less frequently used data. The network connection subsystem 106 is a function that includes one or more devices configured to couple to a wired and / or wireless network and communicate on the wired and / or wireless network (ie, to perform network operations) Block. For example, the network connection subsystem 106 may include Bluetooth^TM Network connection system, cellular network connection system (for example, 3G / 4G network such as UMTS, LTE, etc.), Universal Serial Bus (USB) network connection system, based on the description in IEEE 802.11, 802.15, etc. Standard network connection system (such as Zigbee or Wi-Fi network connection system, etc.), Ethernet network connection system and / or another network connection system. The network connection subsystem 106 includes a processor, controller, radio / antenna, socket / plug, and / or for coupling to each supported network connection system, communicating on each supported network connection system, and Handle other devices and data for each supported network connection system. In the following description, each network system's mechanism for coupling to the network, communicating on the network, and handling data and events on the network is collectively referred to as the "interface" or "network interface" of the network system . The display subsystem 108 is a functional block that includes one or more devices configured to display information on the visual interface of the electronic device 100. For example, in some embodiments, the display subsystem 108 includes a graphics processor (GPU), a graphics card, and / or a display screen for displaying information. In some embodiments, the communication path (including one or more bus bars, wires, and / or connections) is coupled between the functional blocks (processing subsystem 102, memory subsystem 104, etc.) in the electronic device 100, As shown by the arrows between the elements. Communication paths are used to transmit commands, data, event notifications, and / or other information between components. Although specific components are used to describe the electronic device 100, in some embodiments, different components and / or subsystems may exist in the electronic device 100. For example, the electronic device 100 may include one or more additional processing subsystems 102, memory subsystems 104, and so on. In addition, one or more of the subsystems may not exist in the electronic device 100 or some or all of the functions of the subsystems may be incorporated in other subsystems. Furthermore, in some embodiments, the electronic device 100 may include one or more additional subsystems not shown in FIG. 1. For example, the electronic device 100 may include, but is not limited to, a data collection subsystem, an audio and / or video subsystem, an alarm subsystem, a media processing subsystem, and / or an input / output (I / O) subsystem. The electronic device 100 may be any device that performs computing operations or may be included therein. For example, the electronic device 100 may be or be included in the following: desktop computer, laptop computer, wearable computing device, tablet computer, smart phone, server, network electrical equipment, toy, Audio visual equipment (such as receivers, set-top boxes, Apple TV, etc.), automobiles (such as car interface systems, navigation systems, head-up displays, etc.), household electrical equipment, controllers, etc. and / or combinations thereof. (Apple TV is a registered trademark of Apple Inc. of Cupertino, California).Network environment FIG. 2 presents a block diagram illustrating a network environment according to some embodiments. As can be seen in FIG. 2, the network environment 200 includes a source electronic device 202, a companion electronic device 204, and a second source electronic device 206 (collectively referred to as “electronic devices”). In some embodiments, each of the electronic devices is an electronic device similar to the electronic device 100, that is, has a subsystem similar to the electronic device 100. However, this is not required; the described embodiments may use any electronic device that can perform the operations described herein. The source electronic device 202 and the second source electronic device 206 are electronic devices that participate in the exchange with the accompanying electronic device 204 regarding the activity transfer operation. In some embodiments, the source electronic device 202 (and / or the second source electronic device 206) is an electronic device that is recognized by the companion electronic device 204 and thus is allowed to participate in the activity transfer operation. For example, both the source electronic device 202 and the accompanying electronic device 204 may have registered with the service provider using the same account and thus can recognize each other through the information stored in each electronic device. For example, in some embodiments, the source electronic device 202 and the accompanying electronic device 204 participate in a pre-pairing operation (eg, pre-defined pairing) (and recognize each other through information acquired through the pre-pairing operation), as by inventor Jason C . Conn, Akshay Mangalam Srivatsa, Craig P. Dooley and Michael Giles are described in the US Patent Application No. xx / xxx, xxx in the application on the same date as this application, the title of the case is "Predefined Wireless Pairing ", This case has the agent case number APL-P22642USP1, and its contents are incorporated by reference as described above. In some embodiments, the source electronic device 202 and the companion electronic device 204 may participate in the device-to-device exchange of identification factors (encryption keys, credentials, etc.) so that the source electronic device 202 and the companion electronic device 204 then recognize each other. In the network environment 200, the accompanying electronic device 204 can communicate with the source electronic device 202 and the second source electronic device 206 using a wireless communication signal 208 (illustrated using a zigzag line labeled "communication signal 208" in FIG. 2). In some embodiments, the communication signal 208 is formatted and exchanged according to the corresponding wireless protocol (eg, via wireless network protocols such as Bluetooth, Zigbee, 802.11-based protocols, and / or other wireless network protocols) (broadcast , Transmission / reception, etc.). In some embodiments, some or all of the communication signals 208 are transmitted as wired communication signals (eg, signals in wired Ethernet, wired LAN, wired WAN, etc.). In some embodiments, the activity transfer operation described herein relies on the source electronic device 202 and the accompanying electronic device 204 being sufficiently close to each other to enable the communication signal 208 (and therefore the incorporated message) sent by each electronic device Received by another electronic device. In other words, the source electronic device 202 and the accompanying electronic device 204 are "close" to each other, thereby enabling information exchange between the electronic devices. "Proximity" as used herein therefore means the distance that a message broadcast / transmitted from a given electronic device can be received by one or more other electronic devices. This distance is specified by the radio equipment (antenna, receiver / transmitter, etc.) in the electronic device and the specific radio protocol / signal used to broadcast / send messages, such as environmental conditions (electromagnetic interference, etc.), intermediate objects (furniture , Walls, clothes / bags, etc.). For example, in some embodiments, the communication signal 208 is exchanged between the source electronic device 202 and the accompanying electronic device 204 using an agreement with an expected range of 30 meters, and thus these devices are connected when the devices are within 30 meters of each other "Close" (however, note that the expected range can be significantly changed by the factors described above). 16 presents a block diagram illustrating electronic devices that are close to each other according to some embodiments. As can be seen in FIG. 16, the companion electronic device 204 is within the range 1602 of the radio signal (eg, the communication signal 208) of the source electronic device 202, meaning that the companion electronic device 204 can receive the radio signal sent from the source electronic device 202. In addition, the source electronic device 202 is within the range 1604 of the radio signal accompanying the electronic device 204 (for example, the communication signal 208), which means that the source electronic device 202 can receive the radio signal transmitted from the accompanying electronic device 204. Therefore, as described above, the source electronic device 202 and the accompanying electronic device 204 are "close" to each other, thereby enabling communication (and corresponding operation) of the messages described herein. However, neither the source electronic device 202 nor the companion electronic device 204 is within the radio signal range 1606 of the electronic device 1600, meaning that neither the source electronic device 202 nor the companion electronic device 204 is close to the electronic device 1600. It should be noted that the ranges 1602 to 1606 in FIG. 16 are displayed using irregular shapes, thereby illustrating that the radio signal from the electronic device has an irregular range, depending on the electronic device (antenna configuration, etc.), factors described above, etc. . In some embodiments, messages, data, etc. communicated between electronic devices are encrypted. In these embodiments, some or all of the electronic devices perform corresponding encryption and decryption operations, for example, by using a common key, a key obtained from the common key, and / or a one-time key. For example, as previously mentioned, in some embodiments, the source electronic device 202 and accompanying electronic device 204 are involved in the application by the inventors Jason C. Conn, Akshay Mangalam Srivatsa, Craig P. Dooley and Michael Giles. The pre-defined pairing described in US Patent Application No. xx / xxx, xxx in the application filed on the same date, the title of the case is "Predefined Wireless Pairing", the case has the agent case number APL-P22642USP1, and the The contents of the case are incorporated by reference as described above. In some embodiments, the source electronic device 202 and the companion electronic device 204 encrypt and decrypt the active transfer by using one or more encryption keys obtained by the source electronic device 202 and the companion electronic device 204 while participating in the predefined pairing Operate the exchanged messages. Although various electronic devices are shown in FIG. 2, in some embodiments, different configurations of electronic devices are used to perform some or all of the operations described herein. For example, in some embodiments, the second source electronic device 206 does not exist. In general, the described embodiments include sufficient devices to transfer activity between electronic devices as described herein.Broadcast event announcement message FIG. 3 presents a flowchart illustrating a processing procedure for broadcasting event announcement messages according to some embodiments. More specifically, during the processing procedure shown in FIG. 3, an electronic device such as the source electronic device 202 broadcasts an event announcement message. It should be noted that the operations shown in FIG. 3 are presented as general examples of operations performed by some embodiments. The operations performed by some embodiments include different operations and / or operations performed in different orders. In addition, although some mechanisms are used to describe operations (eg, source electronic device 202, etc.), in some embodiments, other mechanisms perform operations. For example, one or both of the electronic device 204 and the second source electronic device 206 can perform similar operations to broadcast their own activity announcement messages. The processing procedure shown in FIG. 3 starts when the source electronic device 202 receives the first application described at the source electronic device 202 (that is, the first application installed on the source electronic device 202 / available at the source electronic device 202 ) Activity information of the activity executed in) (step 300). (The following describes an example of event information in more detail with reference to FIG. 11). In some embodiments, the first application provides or reports activity information to the source electronic device 202, for example, provides or reports activity information to the operating system, wizard assistance program, or other processing procedures and / or services at the source electronic device 202. In some embodiments, the source electronic device 202 queries the first application for activity information. In general, activity information includes information describing activities performed at least in part using electronic devices. Examples of activities include reading and / or editing documents (such as word processing documents, spreadsheets, presentations or other types of documents), writing e-mail messages, drafting notes, accessing (browsing) websites, watching movies, playing audio files, Or use the application or app in other ways to perform the corresponding operation. Next, the source electronic device 202 determines whether to filter the received activity information (step 302), which includes using one or more criteria to discard activity information that should not undergo additional processing and / or should not be broadcast in the activity announcement message. For example, the source electronic device 202 can measure the frequency with which the first application provides updates to the activity information, and can discard the activity information from the first application (which can be (Referred to as "throttling" activity information from the first application). As another example, the source electronic device 202 may discard duplicates or duplicates that do not contain significant changes in previously reported activity information (eg, "unchanged" automatic reports, simple / basic operation / change reports, etc.) The fact that the source electronic device 202 knows, etc. activity information. As yet another example, in some embodiments, the source electronic device 202 filters activity information based on an indication that the activity described by the activity information does not want to be announced. For example, in some embodiments, the source electronic device 202 and / or the user of the source electronic device 202 may configure certain activities and / or certain types of activities as activities that do not want to be announced. As yet another example, in some embodiments, the source electronic device 202 sorts some or all activities (the activity information of such activities exists) (that is, some or all of the activities that can be announced) and discards these based on the ranking One or more of the activities. For example, the source electronic device 202 may assign a higher ranking to activities that the user previously continued and a lower ranking to activities that the user did not continue previously. In some of these embodiments, the source electronic device 202 uses the message from the companion electronic device 204 to determine which announcement activities were previously continued and which announcement activities were not previously, for example, such as described below with reference to step 510 of FIG. 5 Messages of other messages. If the source electronic device 202 filters (eg, discards) activity information (step 302, YES), the processing procedure ends. Otherwise, if the source electronic device 202 does not filter the activity information (step 302, No), the source electronic device 202 stores some or all of the activity information in the structure (step 304). For the purpose of illustration, I describe the embodiment where the activity information is stored in the input items in the table, and I refer to this table as the "announced activity" table. However, it should be noted that the embodiments are not limited to the use of tables for storing activity information. Some embodiments use different storage mechanisms / structures for storing activity information, such as associative arrays, content addressable memory, and so on. In some embodiments, while storing the activity information, the source electronic device 202 overwrites and / or removes the activity information previously stored in the announced activity table. For example, the source electronic device 202 may use the least recently used (LRU) algorithm to overwrite and / or remove input items from the announced activity list. An example of the announced activity table is described in more detail below with reference to FIG. Next, the source electronic device 202 determines the activity identifier used for the activity information (step 306). In general, the activity identifier includes information from activity information that identifies the first application and the activities performed in the first application. In some embodiments, the source electronic device 202 generates the activity identifier by reducing the activity information to a smaller encoded representation that can be broadcast more efficiently than the complete activity information. In some of these embodiments, the encoded representation is a hash of activity information, that is, the output of its input contains a hash function of the activity information (eg, MD4, MD5, SHA, MurmurHash, etc.). In some embodiments, the source electronic device 202 stores the activity identifier together with the activity information in the announced activity table (or any structure used by the source electronic device 202 to store the activity information). An example of the activity identifier is described in more detail below with reference to FIG. In some embodiments, the activity identifier includes a representation of the domain name. For example, in some embodiments, when the activity performed in the first application includes the use of resources at the domain, the activity information includes the domain name of the domain, such as at least a uniform resource locator (URL) portion. In some embodiments, the source electronic device 202 determines the activity identifier by including some or all of the domain names in the activity identifier. For example, the activity identifier may be a hash of some or all of the URL used for the resource. In some embodiments, the activity identifier identifies the input items in the structure where the source electronic device 202 stores activity information (eg, as described above with reference to step 304). For example, the activity identifier may identify the input item in the activity table of the announcement where the source electronic device 202 stores the activity information. The activity identifier may also include the identifier of the announced activity table itself. In some embodiments, to identify the input items in the structure in which the source electronic device 202 stores the activity information, the activity identifier includes: (1) a hash of the data in the announced activity table, which is used to identify the announced activity table, and (2) The index of the input items in the activity table of the announcement storing the activity information. The source electronic device 202 next includes the activity identifier in the activity announcement message (step 308). In some embodiments, in addition to the event identifier, the event announcement message also includes other data. For example, in some embodiments, the event announcement message includes a flag to indicate when the event identifier includes the domain name of the online resource related to the event. In these embodiments, the source electronic device 202 validates the flag (eg, sets the flag to a predetermined value such as 1) to indicate that the activity identifier includes a representation of the domain name. In some embodiments, the source electronic device 202 confirms the flag in the activity announcement message to indicate that the announcement activity can be provided by the source electronic device 202 separately to the accompanying electronic device 204 (eg, by the source electronic device 202 including the corresponding instruction Continue in the extension activity profile (described in more detail below). In some embodiments, the event announcement message includes a time stamp for the event / event information. The time stamp (which may represent an absolute time or a relative time) may indicate the last time the activity was performed in the first application, such as the last time to edit a document, access a website, watch a movie, etc. In some embodiments, the time stamp is independent of the activity / activity information, and the real-time stamp also indicates when the user last interacted with the source electronic device 202, regardless of whether the user's last interaction included the user performing the activity. The source electronic device 202 then broadcasts the event announcement message (step 310). For example, the source electronic device 202 may use the communication signal 208 to broadcast an event announcement message. In some embodiments, the source electronic device 202 broadcasts / announces the event announcement message in the network environment 200 so that nearby devices in the network environment 200 can receive the event announcement message. For example, in these embodiments, the source electronic device 202 uses Bluetooth such as Bluetooth Low Energy (BLE)^TM Communication channel to broadcast event announcement messages. Some embodiments may broadcast event announcement messages on different communication channels (such as peer networks, LAN, Internet, etc.). It should be noted that event broadcasting may occur more than once, for example, the source electronic device 202 may broadcast the same event announcement message multiple times and / or periodically.Build available activity table In some embodiments, the companion electronic device 204 stores available activity information, for example, activity information describing activities available at the companion electronic device 204 (see FIG. 11 for an example of activity information described in more detail below). For example, in some embodiments, the accompanying electronic device 204 stores an activity identifier for available activity information. For illustrative purposes, I describe the accompanying electronic device 204 that stores available activity information in a table, which I refer to as the "available activity" table (an example of the available activity table is described in more detail later in the invention) . It should be noted that although we describe an embodiment that stores available activity information in an available activity table, the embodiment is not limited to using a table to store available activity information. Some embodiments may use other structures for storing available activity information, such as associative arrays, content addressable memory, and so on. 4 presents a flowchart illustrating a processing procedure for storing activity information describing activities available at the companion electronic device 204 into an available activity table according to some embodiments. It should be noted that the operations shown in FIG. 4 are presented as general examples of operations performed by some embodiments. The operations performed by some embodiments include different operations and / or operations performed in different orders. In addition, although some mechanisms are used to describe operations (eg, accompanying electronic device 204, etc.), in some embodiments, other mechanisms perform operations. For example, one or both of the source electronic device 202 and the second source electronic device 206 may perform similar operations to store available activity information describing activities available for itself. The processing procedure shown in FIG. 4 begins when the accompanying electronic device 204 receives activity information describing activities available at the second application at the accompanying electronic device 204 (eg, activity information describing activities that can be performed at the accompanying electronic device 204 ) (Step 400). In general, this activity information describes activities that can be performed in the second application at the companion electronic device 204, that is, operations or functions that the second application at the companion electronic device 204 can perform. In some embodiments, when the second application is installed and / or used, the second application reports / provides activity information. In some embodiments, the electronic device 204 queries or otherwise monitors the second application to collect activity information describing activities available at the second application. In some embodiments, the activity information includes activity information for activities that have not yet been executed on the companion electronic device 204 but are available for execution (eg, when the second application is installed / updated, activated, and used at the companion electronic device 204 Activity information reported by the second application at the same time). Next, the electronic device 204 determines the second activity identifier (that is, the activity identifier used to describe the activity information of the activity available at the second application) (step 402). Generally speaking, the second activity identifier identifies the second application and the activities available at the second application. The second activity identifier may be a coded representation of activity information describing activities available at the second application. In some embodiments, some of the same operations that accompany the electronic device 204 by executing the source electronic device 202 to generate an activity identifier (see FIG. 3, step 306) for the activity performed in the first application or All determine the second activity identifier. For example, in some embodiments, the companion electronic device 204 uses the same hash function to generate the second activity identifier used by the source electronic device 202 to generate the activity identifier for the activity performed in the first application. In some embodiments, when the second application can execute an activity that includes accessing resources at the domain, the activity information for this activity includes the domain name of the domain. In some of these embodiments, the second activity identifier is an encoded representation of the domain name, which enables the second application to "claim" the domain name, that is, to declare that the second application can use the domain name The resources are available so that the accompanying electronic device 204 can transfer the corresponding activities to the second application. For example, as will be described later, in the case where the second application streams movies from a specific site on the Internet, the second activity identifier may be at least some of the domain name of the site The encoded representation of the part. It should be noted that the second application may be different from the first application (ie, the application whose activity is announced in the event announcement message), so that the application different from the first application can continue to be active at the accompanying electronic device 204. Next, the electronic device 204 stores the second activity identifier in the available activity table (step 404).Request for extension activities and transfer activities In some embodiments, after receiving the event announcement message, the electronic device may request extended event data for the announced event so that the announced event can then be transferred to the electronic device. FIG. 5 presents a flowchart illustrating a processing procedure for requesting extension activity data and transferring activities according to some embodiments. More specifically, during the processing procedure shown in FIG. 5, accompanying electronic device 204 requests source electronic device 202 for extended activity data for activities performed in the first application in source electronic device 202. It should be noted that the operations shown in FIG. 5 are presented as general examples of operations performed by some embodiments. The operations performed by some embodiments include different operations and / or operations performed in different orders. Additionally, although certain mechanisms are used to describe operations (eg, source electronic device 202, accompanying electronic device 204), in some embodiments, other electronic devices and / or mechanisms perform the operations. The processing procedure shown in FIG. 5 starts when the electronic device 204 receives an event announcement message (step 500), such as an event announcement message broadcast from the source electronic device 202 (see FIG. 3, step 310). Next, the companion electronic device 204 determines whether the companion electronic device 204 is in the receiving state (step 502). Generally speaking, the companion electronic device 204 is in the receiving state when it is available for performing activity transfer. For example, in some embodiments, the accompanying electronic device 204 transitions to the receiving state when the device "wake up" (eg, when the user presses the button to wake up the device to display the lock screen). In some embodiments, the companion electronic device 204 is when the companion electronic device 204 is in use (eg, when the user is using the application at the companion electronic device 204 and / or when the user has used the application within a given period of time Program) is not in the receiving state. If the accompanying electronic device 204 is not in the receiving state (step 502, No), the processing procedure ends (that is, the activity announcement message is ignored). Otherwise, if the companion electronic device 204 is in the receiving state (step 502, YES), the companion electronic device 204 determines whether the second application associated with the first application is available at the companion electronic device 204 (step 504). Generally speaking, this operation includes determining whether the application is available on the companion electronic device 204 to continue the activity described in the activity announcement message from the source electronic device 202. The determination of whether the second application is available is described in more detail later with reference to FIGS. 7 to 8. If the second application is not available (step 504, No), the processing procedure ends. Otherwise, if the second application is available (step 504, YES), the electronic device 204 accompanies the activity information for the second application (step 506). For example, as will also be described in more detail with reference to FIGS. 7-8 and 11-12, after determining the second application, the accompanying electronic device 204 may use the activity identifier for the second application to The activity information describing the activities available in the second application is retrieved from the available activity table (or another structure used by the accompanying electronic device 204 to store the available activity information). In some embodiments, accompanying electronic device 204 uses the retrieved activity information (eg, using the application identifier in the retrieved activity information) to customize the indication that the activity is recoverable, such as referring to step 508 and / or as follows Or described in Figure 14. Refer to FIG. 11 to describe the application identifier in more detail. Next, the electronic device 204 presents an indication that the activity system is recoverable (step 508). For example, the companion electronic device 204 may present graphical icons and / or notifications in the display of the companion electronic device 204. The instructions are described in more detail below with reference to FIG. 14. Next, the electronic device 204 determines whether the activity transfer is accepted (step 510). In some embodiments, the user accompanying electronic device 204 accepts and performs actions by performing instructions on the instruction (such as clicking on the instruction, dragging the instruction in one or more directions, and / or to one or more specific locations, etc.) / Or refuse to transfer the event. For example, to accept activity transfer, users can use their fingers (on the touchscreen display) to tap the icon / notification and in the first direction (eg left to right, upward, clockwise in a circle, etc.) ), Drag icons / notifications. As another example, to reject the activity, the user may use a finger to touch the icon / notification and drag the icon / notification in a second direction (eg, right-to-left, down, in a counterclockwise direction, etc.). In some embodiments, the companion electronic device 204 determines that the activity transfer is not accepted based on a timeout period (ie, by determining that a period of time has elapsed since the indication was presented without a user performing an action to accept the indication / activity transfer). If the activity transfer is not accepted (step 510, No), the processing procedure ends. It should be noted that in some embodiments, if the activity transfer is not accepted, the accompanying electronic device 204 sends a message to the source electronic device 202 to indicate that the activity transfer is not accepted. If the activity transfer is accepted (Yes in step 510), the accompanying electronic device 204 sends a message to the source electronic device 202 to request extended activity data for the activity executed in the first application (step 512). In general, the request for extension activity data includes information used to facilitate the source electronic device 202 to determine the activity for which the extension data is being requested. For example, in some embodiments, the companion electronic device 204 includes an event identifier from an event announcement message with a request to extend event data. Next, after receiving the extension activity data from the source electronic device 202 in response to the request for the extension activity data, the accompanying electronic device 204 configures the second application using the extension activity data (step 514). Configuring the second application may include starting / starting the second application, setting the state of the second application based on the extended activity data (or causing the state to change), and otherwise configuring the second application to perform the corresponding operation. For example, the accompanying electronic device 204 may pass a document / resource identifier, information representing the document / resource, and / or a reference to the document / resource in the extended activity data to the second application to enable the second application to access Documents / resources (for example, an identifier of a cloud storage document accessed by a second application from a cloud-based storage located on the Internet / information representing the cloud storage document / reference to the cloud storage document, for The identifier of the document retrieved from the database by the second application / information representing the document / reference to the document, etc.). In some embodiments, when the activity includes writing a document stored at the source electronic device 202, the extended activity data includes the document or information representing the document, thereby enabling the accompanying electronic device 204 and / or the second application to accompany The electronic device 204 uses / regenerates the document for the second application. In some embodiments, the extended activity data includes edits in the document, such as the location and / or content of the edits in the document. In some embodiments, the extended activity data includes location information, such as the last playback / viewing / recording location in the media file (that is, the location in the media file where playback or recording stopped or was last performed), the location of the logo in the file, The position / state of the game in the video game (e.g. the last level played, the coordinates of the player ’s last position, the scores and / or achievements won, and / or can be used to reproduce the source electronic device at the accompanying electronic device 204 Information on the state of the game played on 202), etc. Next, the companion electronic device 204 starts to execute activities in the second application (step 516), which usually includes starting / launching the second application at the companion electronic device 204 (if the second application has not been executed) and based on the extended activity data The second application program is executed at the companion electronic device 204. For example, the accompanying electronic device 204 can cause the second application to start executing in the viewing and / or editing mode for the document related to the announcement activity, and can cause the second application to scroll into the document at the source electronic device 202 Last position to view / edit files. Next, accompanying the electronic device 204 sends a notification indicating that the activity is transferred to the source electronic device 202 (step 518). It should be noted that some embodiments may use the information in the event announcement message (such as an event identifier) to start configuring the second application while the extended event data is being transmitted or even before the extended event data is requested. Some of these embodiments use the information in the event announcement message to set the initial background for the second application and set the mode for the second application (eg, edit mode, read-only mode, email writing mode, notes Write mode, etc.). Therefore, some embodiments may start and / or configure the second application before receiving extended activity data (perhaps once the activity transfer is accepted), thereby improving the slow network by hiding the data transmission time with the application startup time Effectiveness in the road. In some embodiments, the accompanying electronic device 204 uses a signal different from the communication signal 208 and / or sends the extension by using a communication channel / network interface different from the communication channel / network interface on which the activity announcement message is received Activity information request. For example, the companion electronic device 204 can receive an event announcement message via a Bluetooth link (using the BLE protocol) and can request extension of event data via a Wi-Fi link or the Internet. In these embodiments, the source electronic device 202 and the accompanying electronic device 204 use a communication signal 208 (eg, Bluetooth link) to exchange information that enables the electronic device to communicate via different communication channels / networks. For example, in some of these embodiments, the electronic device 204 establishes a peer-to-peer network (such as a dedicated Wi-Fi network) and provides information to access the peer-to-peer network to the source electronic device 202 . In some embodiments, the source electronic device 202 provides extended activity data to the server and accompanies the electronic device 204 to receive the extended activity data from the server, for example, via the Internet.Transfer to receiving status based on announcement information Although FIG. 5 describes an embodiment of receiving an activity announcement message (FIG. 5, step 500) and determining whether the accompanying electronic device 204 is in a receiving state (FIG. 5, step 502), some embodiments are based on the received activity announcement message The information is transferred to the receiving state. In some of these embodiments, after receiving the activity announcement message (eg, as shown in FIG. 5, step 500), the accompanying electronic device 204 does not determine whether the accompanying electronic device 204 is in the receiving state, that is, FIG. 5 The processing procedure shown in step 5 continues from step 500 to step 504 without performing the operation of step 502. For example, in some embodiments, the source electronic device 202 uses a low power protocol (such as Bluetooth Low Energy (BLE), Zigbee, etc.) to broadcast an event announcement message via the corresponding communication signal 208. Devices such as companion electronic devices 204 can use corresponding low-power mechanisms (such as corresponding baseband processors in the network interface, such as the baseband processors in the network connection subsystem 106) to monitor activities broadcast from the source electronic device 202 Announcement message. In some of these embodiments, the reception of the activity announcement message is handled by the companion electronic device 204 using only the baseband processor of the companion electronic device 204, which means that the companion electronic device 204 can additionally be in an idle state ( For example, a subsystem such as a processing subsystem is in a low power state). For example, in some embodiments, the companion electronic device 204 may be a smart phone in an idle state in the user's pocket, in which the baseband processor monitors activity announcement messages while processing the subsystem (and It usually accompanies the electronic device 204) in a low power state. In some embodiments, after such recognition of the activity announcement message, the baseband processor wakes up the processing subsystem (and can usually move the accompanying electronic device 204 out of the idle operating state to a higher power / more active operating state) to execute Follow-up operation. For example, in some embodiments, the accompanying electronic device 204 can monitor the activity announcement message and react to the activity announcement message as described in the pending US Patent Application No. xx / xxx, xxx, which is achieved by The inventors Craig P. Dooley, Akshay Mangalam Srivatsa, Anjali S. Sandesara and Michael Giles applied on the same date as this application. The title of the case is "Operating Mode Transitions based on Advertising Information", which has an agent case number APL- P22643USP1, and it is incorporated by reference as described above. In some embodiments, the companion electronic device 204 / smartphone may not need to be removed from the user's pocket and activated to place the companion electronic device 204 in the receiving state.Respond to requests for information on extension activities FIG. 6 presents a flowchart illustrating a processing procedure for responding to requests for extended activity data according to some embodiments. More specifically, during the processing procedure shown in FIG. 6, the electronic device such as the source electronic device 202 responds to the request for the extended activity data from the electronic device such as the companion electronic device 204. It should be noted that the operations shown in FIG. 6 are presented as general examples of operations performed by some embodiments. The operations performed by some embodiments include different operations and / or operations performed in different orders. Additionally, although certain mechanisms are used to describe operations (eg, source electronic device 202, accompanying electronic device 204), in some embodiments, other electronic devices and / or mechanisms perform the operations. The processing procedure shown in FIG. 6 starts when the source electronic device 202 receives a request for extension activity data (step 600), for example, as described with reference to step 512 in FIG. 5, accompanying the request for extension activity data transmitted by the electronic device 204 . Next, the source electronic device 202 uses the information in the request for extension activity data to determine that the request is extension activity data for the first application (step 602). For example, as previously mentioned, the request for extending event data may include an event identifier from the event announcement message (see step 308 in FIG. 3). In some embodiments, the source electronic device 202 performs a search for the activity identifier in the announcement activity table (or other structure in which the announced activity information is stored; the example of the announcement activity table is described in more detail below with reference to FIG. 12). When the source electronic device 202 finds an input item that includes an activity identifier in the announced activity table from the activity announcement message, the source electronic device 202 can retrieve the activity information of the input item, for example, by determining the application identifier of the input item It is determined that the activity identifier corresponds to the first application for the application identifier of the first application (refer to FIGS. 11 to 12 for more detailed examples of activity information and application identifiers). Next, the source electronic device 202 sends notifications / requests to the first application as needed to perform activity-related updates (step 604). In some embodiments, the notification causes the first application to update the extended activity data before providing the extended activity data to the companion electronic device 204. For example, the first application may use the notification to update the last scrolling / viewing position of the document related to the event and / or perform the activity-related completion operation before transferring the event, such as storing the document related to the event, to The latest drafts of the documents related to the event update the extended event information, etc. Next, the source electronic device 202 retrieves extended activity data for the first application (step 606). In some embodiments, the source electronic device 202 requests the first application to provide extended activity data. In some embodiments, the first application provides extended activities along with some or all of the initial activity information (see FIG. 3, step 300) and / or periodically reports extended activity information (eg, everyN Second report, whereN For numbers such as 1, 3, etc., whenever an event occurs in the first application (such as when the document is stored in the first application, the movie being watched is paused in the first application, etc.), the extension activity information ). Next, the source electronic device 202 sends the extended activity profile to the accompanying electronic device 204 (step 608). Generally speaking, the extended activity data includes information that can be used to configure the second application to continue the activity, such as a document identifier (and / or information representing the document) that identifies the document used for the activity performed in the first application, Such as references to documents), uniform resource location (URL) of web pages accessed / browsed in the first application (and / or information representing web pages / URLs, such as references to web pages / URLs), location information (e.g. Indication of the last viewed / scrolled position in the document or web page, the last played position in the video game, etc.), at the source electronic device 202 and / or available on the Internet (e.g. "cloud storage") Or a copy of the draft document (and / or information representing the draft document, such as a reference to the draft document) stored in a storage device accessed on the company network. Next, the source electronic device 202 receives a notification that the activity is transferred (step 610), for example, a notification sent by the accompanying electronic device 204 as described with reference to step 518 of FIG. In some embodiments, in response to receiving the notification, the source electronic device 202 notifies that the first application activity is transferred (step 612). In some embodiments, the source electronic device 202 and / or the first application program performs one or more operations related to the activity based on receiving the notification, such as deleting the document / document draft stored locally, closing the opened document, and closing the application Housekeeping tasks such as programs. In some embodiments, the source electronic device 202 uses a signal different from the communication signal 208, and / or by using a communication channel / network interface other than the one on which the event announcement message and / or the request to extend the event data are communicated The communication channel / internet interface provides extended event data. For example, the source electronic device 202 may receive a request for extended activity data via a Bluetooth link and may provide extended activity data via a Wi-Fi link or the Internet.Secure communication using cloud pairing As discussed earlier, in some embodiments, electronic devices that perform activity transfer operations participate in pre-pairing operations, such as "cloud pairing" operations, such as by inventors Jason C. Conn, Akshay Mangalam Srivatsa, Craig P. Dooley, and Michael Giles' pre-defined pairing described in US Patent Application No. xx / xxx, xxx in the application filed on the same date as this application, the title of the case is "Predefined Wireless Pairing", and the case has the agent case number APL -P22642USP1, and the contents of the case are incorporated by reference as described above. In some embodiments, the electronic device uses security information acquired during the cloud pairing operation (eg, using an encryption key acquired during the cloud pairing operation) to encrypt and decrypt messages exchanged with each other for performing the activity transfer operation. For example, in some embodiments, the source electronic device 202 uses the encryption key obtained during the cloud pairing operation performed by the source electronic device 202 and the accompanying electronic device 204 to encrypt the activity announcement message (see FIG. 3, step 310) and / Or extend the activity data (see Figure 6, step 608). In some embodiments, the companion electronic device 204 uses the same security information, different security information acquired during the cloud pairing operation performed by the companion electronic device 204 and the source electronic device 202, and / or the security obtained during the cloud pairing operation The information encrypted by the sex information is for the request to extend the activity data (see FIG. 5, step 512) and / or the notification that the activity is transferred (see FIG. 5, step 518).Use the activity identifier to determine the second application As previously mentioned, in some embodiments, the electronic device determines whether the second application associated with the first application is available in the electronic device (to facilitate the possible transfer of activities to the electronic device). 7 presents a flowchart illustrating a processing procedure for determining whether a second application is available at the companion electronic device 204 according to some embodiments. The operations shown in FIG. 7 may be performed during the processing procedure shown in FIG. 5 (eg, at step 504). It should be noted that the operations shown in FIG. 7 are presented as general examples of operations performed by some embodiments. The operations performed by some embodiments include different operations and / or operations performed in different orders. In addition, although some mechanisms are used to describe operations (eg, accompanying electronic device 204, etc.), in some embodiments, other mechanisms perform operations. For example, one or both of the source electronic device 202 and the second source electronic device 206 may perform similar operations to determine whether the second application is available. The processing procedure shown in FIG. 7 starts with the electronic device 204 determining whether the flag in the activity announcement message is confirmed (step 700). As previously mentioned, in some embodiments, the source electronic device 202 confirms that the flag in the event announcement message indicates that the event identifier is / contains a representation of the domain name used for the announced event. In some of these embodiments, the accompanying electronic device 204 determines that the activity announcement message includes a representation of the domain name by determining that the flag is confirmed. The flag will be described in more detail later in this specification with reference to FIGS. 11 and 13, for example. If the flag in the event announcement message is confirmed (step 700, YES), then the electronic device 204 processes the flag (step 702). The processing of the flag that occurs at step 702 will be described later with reference to FIG. 8. Some embodiments repeat step 702 for each confirmation flag in the activity announcement message (ie, the processing described with reference to FIG. 8), for example, when the activity announcement message includes two or more confirmation flags The handling of each confirmation flag. If the event announcement message does not contain a confirmed flag (step 700, No), the accompanying electronic device 204 compares the event identifier from the event announcement message with the event identifier for the event available at the accompanying electronic device 204 (step 704). For example, the companion electronic device 204 can look up the activity identifier from The event identifier of the event announcement message. If the search for the activity identifier finds a match in the input items in the available activity table (step 706, YES), the electronic device 204 determines that the second application is an application whose activity identifier is stored in the other input item (step 708) ). If the search activity identifier does not find a match in the available activity information (step 706, No), the accompanying electronic device 204 determines that the application associated with the first application is not available at the accompanying electronic device 204 (step 710).Use the flag to determine the second app As previously mentioned, some embodiments confirm the flag in the event announcement message. 8 presents a flowchart illustrating a processing procedure for determining a second application using flags according to some embodiments. More specifically, FIG. 8 presents a flowchart illustrating the processing procedure accompanying the electronic device 204 at step 702 of FIG. 7. It should be noted that the operations shown in FIG. 8 are presented as general examples of operations performed by some embodiments. The operations performed by some embodiments include different operations and / or operations performed in different orders. In addition, although some mechanisms are used to describe operations (eg, accompanying electronic device 204, etc.), in some embodiments, other mechanisms perform operations. For example, one or both of source electronic device 202 and second source electronic device 206 may perform similar operations on their own. The processing procedure shown in FIG. 8 starts when the electronic device 204 determines that the application corresponds to the flag (step 800). In some embodiments, the accompanying electronic device 204 uses the location of the confirmation flag and / or the value of the flag to determine the application corresponding to the flag. For example, when the activity announcement message includes more than one flag that can be verified, each of the flags can be used to identify different applications that can be used to continue the activity. In some embodiments, the flag is a multi-bit field and different values of the multi-bit field identify different applications. In some embodiments, the accompanying electronic device 204 stores the mapping of the application corresponding to the location / value of the identification flag. Next, the companion electronic device 204 determines whether the application corresponding to the flag is available at the companion electronic device 204 (step 802). For example, the companion electronic device 204 may check whether the application corresponding to the flag is installed at the companion electronic device 204. In some embodiments, step 802 is not executed / skipped, so that the processing procedure shown in FIG. 8 continues from step 800 to step 804. For example, step 802 is not performed in an embodiment that uses flags to only identify pre-installed applications that are known to be available at the companion electronic device 204 and that cannot be uninstalled by the user. If an application corresponding to the flag is available (step 802, YES), the electronic device 204 determines that the second application is an application corresponding to the flag (step 804). The processing procedure then ends, which may include continuing to step 506 in FIG. 5. If the application corresponding to the flag is not available at the accompanying electronic device 204 (step 802, No), the processing procedure ends. At this time, the accompanying electronic device 204 may determine that the second application is unavailable (for example, as shown in step 504 in FIG. 5, No), or may continue to step 704 in FIG. 7 to determine the first by using the event identifier from the event announcement message Second, whether the application is available. In some embodiments, the process shown in FIG. 8 allows applications other than the first application to continue to be active at the companion electronic device 204. For example, consider a situation where the first application is a web browser and the activities performed in the first application include browsing a social media website. In this example, the second application may be a social media app that accesses resources (eg, social media user pages, etc.) accessed in the first application / web browser (that is, the second application is app and not a web browser). By using flags, these embodiments can configure the social media app to continue activities performed at the social media website at the same point where the web browser stopped. As another example, in some embodiments, the first application is an independent media streaming app (such as a media player app) that streams movies from a website and the second application is a web browser that can stream movies Device. By using flags, these embodiments configure the web browser to continue playing the movie, which may include using extended event data for the event so that the web browser continues to play the movie where the media streaming app stops. In some embodiments, the source electronic device 202 sets a second flag (or a different value for the flag) in the activity announcement message to indicate that the source electronic device 202 will then provide information on how to continue the activity at the companion electronic device 204 Instructions / information. In some embodiments, the application corresponding to the flag contains instructions / information on how to continue activities at the companion electronic device 204. In some embodiments, the extended activity data provides instructions / information for continuing activities at the companion electronic device 204.Use the structure of the stored announcement activity to determine the second application As described above with reference to FIG. 3, in some embodiments, the activity identifier in the activity announcement message identifies an input item in a structure (eg, a table), and the electronic device that announces the activity stores the activity information used for the announcement activity in the structure in. 9 presents a flowchart illustrating a process for determining whether a second application is available when an activity identifier recognizes an input item in this structure according to some embodiments. More specifically, during the processing procedure shown in FIG. 9, the electronic device 204 uses the activity identifier of the input item in the recognized announcement activity table (in which the source electronic device 202 stores the activity information for the announcement activity) to determine Whether a second application program associated with the first application program is available at the companion electronic device 204 (an example of an announcement activity table is described in more detail below with reference to FIG. 12). It should be noted that the operations shown in FIG. 9 are presented as general examples of operations performed by some embodiments. The operations performed by some embodiments include different operations and / or operations performed in different orders. Additionally, although certain mechanisms are used to describe operations (eg, source electronic device 202, accompanying electronic device 204), in some embodiments, other electronic devices and / or mechanisms perform the operations. The processing procedure shown in FIG. 9 starts when the electronic device 204 receives an activity identifier that identifies an input item in a bulletin activity table in which the source electronic device 202 stores activity information for a bulletin activity (step 900). In some embodiments, the activity identifier includes a table identifier and an input item index, the table identifier identifies the announcement activity table in which the source electronic device 202 stores the activity information for the announcement activity, and the input item index is identified by the table identifier The entry items in the identified announcement activity table that store activity information for announcement activities. In some embodiments, the table identifier is a hash of the announcement activity table data. Next, the companion electronic device 204 determines whether the announcement activity table for the activity identifier is available at the companion electronic device 204 (step 902). In some embodiments, the companion electronic device 204 uses the table identifier from the activity identifier to determine whether the companion electronic device 204 stores a local copy of the announcement activity table. If the announcement activity table for the activity identifier is not available at the accompanying electronic device 204 (step 902, No), the accompanying electronic device 204 retrieves the announcement activity table from the source electronic device 202 (step 904). In some embodiments, the accompanying electronic device 204 requests the source electronic device 202 to send the announcement activity table identified by the activity identifier from the activity announcement message, such as the announcement activity table identified by the table identifier. Using the communication signal 208 and / or different communication signals / different channels, the accompanying electronic device 204 can transmit this request, and the source electronic device 202 can respond to the request. In some embodiments, the electronic device 204 periodically synchronizes the local copy / multiple copies of its announcement activity table with the source electronic device 202. For example, the accompanying electronic device 204 may use a "push" mechanism (ie, without sending a request for a copy of the announcement activity table) to receive a copy of the announcement activity table from the source electronic device 202. If the announcement activity table for the activity identifier is available at the accompanying electronic device 204 (step 902, Yes), or after receiving the announcement activity table from the source electronic device 202, the accompanying electronic device 204 uses the activity identifier to The activity information is retrieved from the announcement activity table (step 906). For example, the companion electronic device 204 can retrieve activity information from the input items identified by the input item index in the announcement activity table. In some embodiments, the operations shown in FIG. 9 enable information describing more than one event to be announced in a single event announcement message. For example, consider a case where the size of the event announcement message is limited due to, for example, the limitation of the network protocol used to broadcast the event announcement message. In this case, the input item identifier (that is, the activity identifier that identifies the input item in which activity information is stored) may be smaller than the encoded representation (that is, the activity identifier generated from the same activity information) (for example, use less than The activity identifier is represented in bits) so that these embodiments can carry multiple input item identifiers in the activity announcement message. As previously described with reference to FIG. 3, the described embodiments are not limited to the use of tables for storing available activity information. Some embodiments use different structures for storing available activity information, such as associative arrays, content addressable memory, and so on. In these embodiments, the activity identifier may identify input items in the structure in which the source electronic device 202 stores activity information used to announce the activity. For example, in these embodiments, the table identifier can identify the structure and the input item index can identify the index in the structure where the source electronic device 202 stores the activity information used to announce the event. In addition, although we describe an embodiment that uses one announcement activity table, some embodiments use more than one announcement activity table, for example, storing event information for announcement activities in different announcement activity tables.Determine recent activity As described above, the network environment 200 may include the second source electronic device, which may broadcast an activity announcement message for activities performed at the second source electronic device. As also described earlier, some embodiments include a timestamp in the event announcement message to indicate when the event announced in the event announcement message was last executed. FIG. 10 presents a flowchart illustrating a processing procedure for determining the most recent activity from two or more activity announcement messages according to some embodiments. More specifically, during the processing procedure shown in FIG. 10, the electronic device 204 uses the timestamp included with the announcement from the source electronic device 202 ("event announcement") and the announcement from the second source electronic device 206 ("Second Event Announcement") A time stamp included together to determine the nearest of the events announced in the event announcement and the second event announcement. It should be noted that the operations shown in FIG. 10 are presented as general examples of operations performed by some embodiments. The operations performed by some embodiments include different operations and / or operations performed in different orders. Additionally, although certain mechanisms are used to describe operations (eg, source electronic device 202, companion electronic device 204, second source electronic device 206), in some embodiments, other electronic devices and / or mechanisms perform operations. For the processing procedure shown in FIG. 10, it is assumed that the accompanying electronic device 204 has received the activity announcement from the source electronic device 202, for example, as shown in FIG. Therefore, the accompanying electronic device 204 has an event announcement, including the first time stamp included with the event announcement. The processing procedure shown in FIG. 10 starts when the electronic device 204 receives the second event announcement (step 1000). Next, the electronic device 204 compares the first time stamp included with the event announcement with the second time stamp included with the second event announcement (step 1002). For example, the companion electronic device 204 may compare timestamps to understand which one is newer (ie, indicates the most recent time). If the comparison indicates that the first timestamp is newer (step 1004, YES), then the electronic device determines that the activity performed in the first application (that is, the activity announced in the activity announcement) is the most recent activity (step 1006). Otherwise, if the comparison indicates that the second timestamp is newer (step 1004, No), the electronic device 204 determines the activity to be executed in the second application (that is, the activity announced in the second activity announcement) Is the most recent activity (step 1008). In some embodiments, the companion electronic device 204 reduces presentation to the user on the display of the companion electronic device 204 (eg, as shown in FIG. 14) by only presenting an indication that the activity is recoverable for the most recent of the announcement activity The number of instructions. In some embodiments, the timestamp is used with the electronic device 204 to present an indication of recoverable activities in order, such as presenting the most recent activity first, followed by presenting other announcement activities in descending order based on relative recentness. In such embodiments, two or more indications may be presented side by side according to the relative recentness of the corresponding activity, one above the other, and so on. In some embodiments, the electronic device 204 uses a history of previously resumed activities to present an indication of recoverable activities in order. In some embodiments, the accompanying electronic device 204 prioritizes previously resumed activities, that is, an indication of a resumeable previously resumed activity is presented before an instruction of a resumeable previously not resumed activity. In some embodiments, two or more indications are presented in order based on the number of times each of the corresponding activities has previously continued.Activity Information As previously mentioned, some embodiments use activity information describing activities performed at the electronic device. 11 presents a block diagram illustrating activity information 1100, activity information 1110, and activity information 1120 according to some embodiments. It should be noted that the event information 1100, event information 1110, and event information 1120 shown in FIG. 11 are presented as a general example of the format of event information used by some embodiments. Some embodiments use different formats and / or different information included in the event information. The activity information 1100 includes an application identifier 1102 that identifies an application used to execute the activity described in the activity information 1100. For example, the application identifier 1102 (which includes the stringcom . apple . Keynote ) Identify the application Keynote, which is an application that can be used to edit and view presentations. Activity descriptor 1104 includes a stringEditPresentation , Which recognizes activities performed using the application Keynote as editing presentations. The time stamp 1106 (which includes the string / number 103) identifies the last time the activity was performed, for example, the last time the user edited the presentation in the keynote application. The timestamp may indicate the actual time at which the activity was last executed (eg, wall clock time (or its representation, such as system time)), or it may be a representation of the time elapsed since the activity was last executed after the hour or since the synchronization event. In some embodiments, the timestamp indicates the actual time (eg, absolute / wall clock time (or its representation, such as system time)) of the source electronic device 202 was last used (eg, actively used by the user), or it may be A representation of the time elapsed since the source electronic device 202 was last used after the hour or since the synchronization event. In the event information 1100, the flag 1108 was not confirmed. The event information 1110 includes an application identifier 1112 that identifies the application used to execute the activity described in the event information 1110. For example, the application identifier 1112 (which includes the stringcom . apple . Mail ) Identify the application Mail (an application that can be used to write and send e-mail messages). Activity descriptor 1114 includes a stringComposeDraft To identify the activities performed using the application Mail including writing message drafts. The timestamp 1116 (which includes the string / number 315) identifies the last time the activity was performed, for example, the last time the user used Mail to write a draft. The flag 1118 used for event information 1110 has not been confirmed. The event information 1120 includes an application identifier 1122 that identifies the application used to execute the activity described in the event information 1120. For example, the application identifier 1122 (which includes the stringcom . apple . Safari ) Identify the application Safari (web browser). Activity descriptor 1124 includes a stringwww . evideostreamer . com , Which identifies the domain name accessed using a web browser. In this example, the activity descriptor 1124 retains the domain name, so the flag 1128 in the activity information 1120 is the verified flag 1128 to indicate that the activity description 1124 includes the domain name. The timestamp 1126 (which includes the string / number 820) identifies the last time the web browser used to access the mobile streaming website. The activity information 1130 includes an application identifier 1132 that identifies the application used to execute the activity described in the activity information 1130. For example, the application identifier 1132 (which includes the stringcom . CompanyA . MediaPlayer ) Identify the application MediaPlayer (which in this example is the developerCompanyA Development) (which is an application that can be used to play and record multimedia content). Activity descriptor 1134 includes a stringPlayVideo To identify the activities performed using the application MediaPlayer include playing video (ie, video playing). The timestamp 1136 (which includes the string / number 902) identifies the last time the activity was executed, for example, the last time the user used MediaPlayer to play the video. The flag 1138 used for event information 1130 has not been confirmed. For illustrative purposes, the timestamp shown in FIG. 11 is calculated as the increment (difference) since the synchronization event (eg, hour). Therefore, in the example shown in FIG. 11, the activity described using the activity information 1100 is the most recent activity. This is because the timestamp 1106 indicates that the minimum amount of time has elapsed since the hour since the activity described using the activity information 1100 was performed. . It should be noted that although the example shown in FIG. 11 uses strings for application identifiers and activity descriptors, some embodiments may use different information to identify applications and / or activities. For example, some embodiments use digital identifiers for application identifiers and / or activity descriptors. In some embodiments, the application identifier is the identifier of the corresponding application in the online "app store". In some embodiments, the application identifier includes some or all of the bundle identifier (eg, bundle ID). Additionally, although the application identifier shown is separate from the activity descriptor, some embodiments combine the application identifier and activity descriptor in a single identifier. In some embodiments, application / app developers provide information for activity descriptors such as activity descriptor 1104, activity descriptor 1114, activity descriptor 1124, and activity descriptor 1134. In these embodiments, the developer of the application / app can determine certain activities for the application / app and can provide relevant values of the activity descriptor.Announcement activity table FIG. 12 presents a block diagram illustrating an announcement activity table 1200 according to some embodiments. As described above, the announcement activity table 1200 includes information about activities that have been announced (that is, activities whose activity announcement messages have been sent by electronic devices such as the source electronic device 202). It should be noted that the announcement activity table shown in FIG. 12 is presented as a general example of the announcement activity table used by some embodiments. Some embodiments represent the event information in different ways and / or include more or less information in the announcement event table. The input item 1202 (which is identified by the input item index 1206) stores the activity information 1100 and the activity identifier 1204. In this example, the activity identifier 1204 uses the application identifier 1102 and the activity descriptor 1104 (such as the string "com . apple . Keynote :: EditPresentation "Hash"). The input item 1212 (which is identified by the input item index 1216) stores the event information 1110 and the event identifier 1214. In this example, the activity identifier 1214 uses the application identifier 1112 and the activity descriptor 1114 (such as the string "com . apple . Mail :: ComposeDraft "Hash"). The input item 1222 (which is identified by the input item index 1226) stores the event information 1120 and the event identifier 1224. In this example, an activity identifier 1124 (such as a hash of the string www.evideostreamer.com) is used to generate an activity identifier 1224. The input item 1232 (identified by the input item index 1236) stores the event information 1130 and the event identifier 1234. In this example, the activity identifier 1234 uses the application identifier 1132 and the activity descriptor 1134 (such as the string "com . CompanyA . MediaPlayer :: PlayVideo "Hash"). For illustrative purposes, input items 1202 to 1232 store all activity information 1100 to 1130, respectively. However, it should be noted that in some embodiments, the input items 1202 to 1232 store only some of the activity information 1100 to 1130, respectively. For example, some embodiments do not store timestamps 1106 to 1136 in input items 1202 to 1232.Available Activity List In some embodiments, the available activity table described above is formatted similar to the announcement activity table 1200 shown in FIG. 12. However, the input items in the available activity table include application information for applications available in the corresponding electronic device (eg, accompanying electronic device 204).Event announcement message FIG. 13 presents a block diagram illustrating an activity announcement 1300 (eg, activity announcement message) according to some embodiments. It should be noted that the event announcement message shown in FIG. 13 is presented as a general example of the event announcement message used by some embodiments. Some embodiments sequence the fields in the event announcement message in different ways and / or include different information in the event announcement message. The event announcement message 1300 includes a device ID field 1302 and a version ID field 1304 as needed. The device ID field 1302 includes an identifier that identifies the device (eg, the identification source electronic device 202) from which the activity announcement message 1300 was sent. The version ID field 1304 includes a version identifier, such as a version identifier that accompanies the electronic device 204 to determine how the field in the activity information 1300 is formatted and / or how the information is stored in the field. The activity identifier field 1306 includes an activity identifier, such as one or more of activity identifiers 1204 to 1224. The flag field 1308 includes one or more flags corresponding to the announcement activity, such as flags 1108 to 1128. The timestamp field 1310 includes a timestamp for the activity announced in the activity identifier field 1306, such as one or more of the timestamps 1106 to 1126.Resumable activity instructions As previously mentioned, some embodiments present an indication that the activity is recoverable before requesting to extend the activity data. 14 presents a block diagram illustrating an indication of recoverable activity (ie, an indication that the activity is recoverable) according to some embodiments. More specifically, FIG. 14 shows a resumeable activity indication displayed on the display 1400 accompanying the electronic device 204. It should be noted that the recoverable activity indicator shown in FIG. 14 is presented as a general example of the recoverable activity indicator used by some embodiments. Some embodiments use different recoverable activity indications and / or present recoverable activity indications in different ways. In the illustrated embodiment, the accompanying electronic device 204 is a smart phone that includes a touch screen display 1400. The embodiment shown in FIG. 14 is in the receiving state, because the display 1400 shows a lock screen with an unlock indicator 1402 (which shows the phrase "slide to unlock"). Generally speaking, the user of the accompanying electronic device 204 uses the unlocking indicator 1402 to perform an operation to unlock the accompanying electronic device 204, such as sliding a figure of the unlocking indicator 1402 across the display 1400 using a finger. The resumeable activity indication 1404 includes a graphic (such as an illustration) that the user can manipulate to accept (or reject) the transfer of activity. In FIG. 14, the recoverable activity indication 1404 includes an icon similar to an envelope, indicating that the recoverable activity includes the use of a mail application. In some embodiments, the user may accept the activity transfer by tapping / touching the recoverable activity indicator 1404 on the recoverable activity indicator 1404, and / or by moving the recoverable activity indicator 1404 along a path on the display 1400 . For example, in some embodiments, the user may accept the activity transfer by touching and dragging the recoverable activity indicator 1404 along or near the path 1406 (shown as a dotted line). For illustrative purposes, the resumeable activity indicator 1404 is displayed at the lock screen that accompanies the electronic device 204. In some embodiments, the resumeable activity indicator 1404 may be displayed at different screens / locations (eg, at the unlock screen, at the menu bar, by using notification windows / push-ups, etc.). In addition, the position, size, graphics, color, and / or other visual characteristics of the recoverable activity indicator 1404 may vary for different embodiments, and may depend on the type of recoverable activity. For example, in some embodiments, the companion electronic device 204 determines the graphic displayed in the recoverable activity indication 1404 based on the application identifier used to announce the activity. As another example, in some embodiments, the resumeable activity indication 1404 is displayed at the lower left corner of the display 1400. Some embodiments present multiple recoverable activity indicators simultaneously. It should be noted that the acceptance (or rejection) of the activity transfer may include moving the recoverable activity indication 1404 along a path different from the path 1406 (eg, to the top of the screen, along a curved path, etc.). In some embodiments, the user can select the recoverable activity indicator 1404, tap on the recoverable activity indicator 1404, slide the recoverable activity indicator 1404, and use the recoverable activity indicator 1404 Performs gestures and the like to accept activity transfer.Automatic and manual event announcements In some embodiments, the source electronic device 202 automatically broadcasts an event announcement at a predetermined time interval, once activity information is received, based on the detected location of the source electronic device 202, and so on. In these embodiments, the source electronic device 202 may provide settings that the user can use to turn on or off the broadcast of the event announcement, such as system preferences. In some embodiments, the source electronic device 202 manually starts broadcasting the activity announcement, that is, waits for input from the user to start broadcasting the activity announcement. In some of these embodiments, the source electronic device 202 starts broadcasting the activity announcement after detecting the user's input and continues to broadcast the activity announcement for a predetermined period of time and / or until the user provides the source electronic device 202 to stop Until the event announcement is entered. In some embodiments, the user input for starting and / or stopping the activity announcement includes the movement of the source electronic device 202 (eg, shaking the source electronic device 202, moving the source electronic device 202 in an arc, swinging the source electronic device 202, etc.) 1. Perform one or more gestures, press keys and / or button combinations on the touch screen of the source electronic device 202, etc. In some embodiments, the event announcement message and / or the source electronic device 202 together with the event announcement message (ie, in addition to the event announcement message) are sent to the message accompanying the electronic device 204 such that the accompanying electronic device 204 starts the timer . In some embodiments, the companion electronic device 204 remains in the receiving state as described above until this timer expires. The source electronic device 202 may provide the expiration time of the timer to the accompanying electronic device 204, or the accompanying electronic device 204 may determine the expiration time. In some embodiments, the accompanying electronic device 204 presents an indication that the activity is recoverable until the timer expires, and if the user accepts the instruction, the activity continues at the accompanying electronic device 204 without the user performing one or more Operations (such as fingerprint scanning, password input, etc.) to unlock the companion electronic device 204. More specifically, the companion electronic device 204 can detect that the user accepts the instruction and can bypass the lock screen / unlock operation, thereby allowing the user to start using the companion electronic device 204 without unlocking the companion electronic device 204. In some embodiments, the user is allowed to bypass the lock screen / unlock operation only before the timer expires.Activities continue to frame In some embodiments, the third-party application receives some of the activity transfer operations (such as the operations described earlier with reference to FIGS. 3 to 10) via the "activity continuation" framework available at the electronic device that can participate in the activity transfer operation Or full access. The activity continuation framework can provide third-party applications with access to operating system functions, wizard helpers, processing procedures, services, etc. (which perform at least some of the activity transfer operations). For example, in some embodiments, the provider of the electronic device and / or the operating system of the electronic device provides an application programming interface (API) through which third-party applications can face functions that facilitate the transfer of activities Make the call. In some embodiments, the activity continuation framework enables third-party applications (and third-party application developers) to transfer activities from one electronic device to another electronic device without implementing (or even understanding) the low-level level of activity continuation detail. For example, in some embodiments, to enable third-party applications to participate in activity transfer operations, third-party application developers provide activity descriptors for third-party application-executable activities and configure third-party applications To perform activities. In some of these embodiments, at an electronic device such as source electronic device 202, the third-party application invokes the functions provided by the activity continuation framework to provide activities for the activities performed in the third-party application Descriptors (and possibly extended activity data). At an electronic device such as the accompanying electronic device 204, to configure a third-party application to perform an activity, the activity continuation framework can transfer extended activity data to the third-party application (eg, via a command line switcher or parameters, by using objects, Wait). Therefore, the activity continuation framework can promote the continuation of the activities of third-party applications with minimum effort and expense for third-party application developers.Exchange messages between electronic devices 15 presents a swimlane diagram illustrating messages exchanged between electronic devices according to some embodiments. As can be seen in FIG. 15, messages are exchanged between the source electronic device 202 and the accompanying electronic device 204 within a period of time, where the activity announcement 1500 appears first and the lower message appears subsequently. Although FIG. 15 shows messages exchanged in a specific order, in some embodiments, other messages are exchanged and / or messages are exchanged in a different order. Generally speaking, the electronic devices in the described embodiments exchange sufficient information to achieve the operations described herein. The message in FIG. 15 is associated with two operations performed by the source electronic device 202 and / or accompanying electronic device 204. The first operation (which includes the announcement 1500) is an activity announcement operation such as shown in FIG. During the event announcement operation, the source electronic device 202 broadcasts at least one event announcement 1500. The second operation (which includes a request 1502 for extension of activity information, extension of activity information 1504 and notification of activity transfer 1506) is an activity transfer operation such as shown in FIGS. 5-6. During the event transfer operation, the electronic device 204 responds to the event announcement 1500 with a request 1502 for extending event materials. After receiving the request 1502 for the extension activity data, the source electronic device 202 responds by sending the extension activity data 1504. In some embodiments, after the accompanying electronic device 204 uses the extended activity data to start executing the activity at the second application, the accompanying electronic device 204 sends a notification 1506 of the activity transfer to let the source electronic device 202 know that the activity is transferred.Forward information related to the event As described above, in some embodiments, the source electronic device (eg, source electronic device 202) relays information related to the activity to the companion electronic device (eg, companion electronic device 204). In general, the information related to the activity includes any information that can be used when performing the activity (eg, transfer to an activity accompanying the electronic device or another activity performed on the accompanying electronic device as described herein). For example, the information related to the activity includes (but is not limited to) the information from the source electronic device 202 that is copied and pasted in the clipboard (eg, text, images, video, sound, settings, files, etc.), file comparison The content of the earlier version, the undo buffer (which retains a record of changes made by the user to the system that can be used to reverse the changes, etc.), and / or other types of information. After receiving the information related to the event, the accompanying electronic device can use the information related to the event for one or more events. For example, when the information related to the activity includes the contents of the undo buffer, the accompanying electronic device may update the local undo buffer using the contents of the undo buffer received from the source electronic device (that is, the undo in the electronic device buffer). For example, the undo buffer may include a list of the last N operations performed when editing a file, the list is configured to enable reverse or "undo" operations using menus, hotkey combinations, etc. while editing the file subsequently . In this way, the companion electronic device can configure itself to reverse or undo the operations previously performed on the source electronic device. FIG. 17 presents a flowchart illustrating a processing procedure for forwarding activity-related information from a source electronic device to a companion electronic device according to some embodiments. More specifically, FIG. 17 illustrates an embodiment in which the source electronic device 202 uses an announcement message to relay information related to the event to the accompanying electronic device 204. It should be noted that the operations shown in FIG. 17 are presented as general examples of operations performed by some embodiments. The operations performed by some embodiments include different operations and / or operations performed in different orders. In addition, although some mechanisms are used to describe operations (eg, accompanying electronic device 204, etc.), in some embodiments, other mechanisms perform operations. For the processing procedure shown in FIG. 17, the contents of the scrapbook in the source electronic device 202 are used as information related to the activity. However, in some embodiments, and as described above, other types of activity-related information may be transferred from the source electronic device 202. In addition, "scrapbook" as used herein indicates copying and pasting of the scrapbook in the corresponding device. In some embodiments, the scrapbook is a software service that provides temporary storage of information in an electronic device (eg, operating system software services, standalone applications, etc.). The scrapbook enables users to perform operations such as copying, pasting, cutting, etc. to interact with information. Such scrapbooks are generally known in the art and therefore are not described in more detail herein. The processing procedure shown in FIG. 17 starts when the source electronic device 202 determines that the information related to the activity is available for forwarding to the companion electronic device 204 (step 1700). For example, based on receiving the activity information described above (see, for example, step 300 in FIG. 3), the source electronic device 202 may perform one or more checks and determine that information related to the activity is available. As another example, after receiving an instruction that the user has performed a copy operation to copy information (eg, copy text, files, images, etc.) to the clipboard, the source electronic device 202 may determine that the information related to the activity is available. As another example, the source electronic device 202 may monitor various operations performed in the source electronic device 202 as part of performing an activity and may directly or indirectly determine that information related to the activity has become available. As described above, for the example in FIG. 17, the content of the scrapbook is information related to the event. The source electronic device 202 therefore determines in step 1700 that there are one or more copied items placed on the scrapbook when performing the current activity. The source electronic device 202 then generates an information bulletin related to the activity (step 1702). In general, the information announcement related to the event includes sufficient information to enable the accompanying electronic device 204 (and other devices that may receive the information announcement related to the event) to determine that the information related to the event is of interest and handle the event-related Information. Continuing with the scrapbook example, the source electronic device 202 may generate an event-related information bulletin, which enables the accompanying electronic device 204 to determine the event-related information described in the event-related information bulletin (ie, from the source electronic device 202 The content of the scrapbook) is of interest to the accompanying electronic device 204, and the scrapbook in the accompanying electronic device 204 is updated using the content of the scrapbook from the source electronic device 202 or based on the content of the scrapbook from the source electronic device 202. FIG. 18 presents a block diagram illustrating an activity-related information bulletin 1800 generated by the source electronic device 202 according to some embodiments. The information announcement 1800 related to the event includes a device ID field 1802, a version ID field 1804, an event identifier field 1806 and a time stamp field 1808 as needed. The device ID field 1802 includes an identifier that identifies the device (for example, the identification source electronic device 202) from which the information bulletin 1800 related to the activity is sent. The version ID field 1804 includes a version identifier, such as a version identifier that can be used by the electronic device 204 to determine how the field in the information bulletin 1800 related to the activity is formatted and / or how the information is stored in the field. The activity identifier field 1806 includes an activity identifier that identifies the information corresponding to the activity and its associated activity, such as one or more of the activity identifiers 1204 to 1224. The timestamp field 1808 includes a timestamp for the event announced in the event identifier field 1806. As described above, the timestamp can be used to resolve the order in which two or more event-related information announcements 1800 are handled, which event-related information announcements 1800 are ignored, and so on. The event-related information field 1810 includes event-related information and / or information based on the event-related information, information obtained from the event-related information, or information that otherwise identifies the event-related information. Continuing the above example, in some embodiments, the source electronic device 202 includes some or all of the actual content from the scrapbook in the source electronic device 202 in the information field 1810 related to the activity. For example, if a section of text was recently copied to the clipboard, the section of text (that is, the text itself) (which may have meta data including formatting, time stamps, version information, etc.) may be included in the activity-related Information field 1810. As another example, if sections, images, and files of text are individually copied to the clipboard during one or more copy operations, some of the sections, images, and files of text (which may have corresponding metadata) Or all of them can be included in the information field 1810 related to the activity. As another example, in an embodiment where the source electronic device 202 includes information based on activity-related information in the activity-related information field 1810, information obtained from it, etc., the source electronic device 202 may convert the compressed information , Representative information, information that can be used to derive information related to the event, and / or other information based on or related to the event-related information is included in the event-related information field 1810. For example, the source electronic device 202 may include an indication that the information is available (eg, indicators, tags, identifiers, references, and / or other indicators) (may include basic identification of the type of information), but is not related to the activity The information announcement 1800 includes the actual information related to the event itself. In these embodiments, the accompanying electronic device 204 may perform one or more operations for retrieving information related to the activity indicated in the information bulletin 1800 related to the activity. For example, assuming that the source electronic device 202 includes an indicator to the event-related information in the event-related information field 1810, the accompanying electronic device 204 can be retrieved from the source electronic device 202 via one or more corresponding independent communications Information related to the activity indicated by the indicator. In some embodiments, in addition to some or all of the actual information related to the activity, information based on the information related to the activity, information obtained from it, etc. may be included in the information field 1810 related to the activity. Continuing the scrapbook example, it is assumed that a small section of text (100 bytes) and a larger image (4 MB) are copied to the scrapbook in the source electronic device 202. The source electronic device 202 can be in the field 1810 related to the activity Includes small sections of text (and possibly corresponding meta data), but may only include references to images. The companion electronic device 204 can then use the reference to request images as described above. In some embodiments, the size of the information related to the event is used to determine whether the information related to the event or the information based on it will be included in the information announcement 1800 related to the event. For example, based on one or more thresholds (such as the maximum size of the information announcement 1800 used for the activity, etc.), information related to the activity may be included directly or indirectly (e.g., by indicators, indicators Etc.) in the information field 1810 related to the activity. The source electronic device 202 then transmits (eg, broadcast, unicast, multicast, etc.) information announcements 1800 related to the activity (step 1704). For example, using the corresponding protocol, the source electronic device 202 may unicast the information announcement 1800 related to the event to the accompanying electronic device 204. Generally speaking, during this operation, the source electronic device 202 provides an activity-related information bulletin 1800 to the accompanying electronic device 204 via a wired or wireless communication link. As described in more detail below, after receiving the information bulletin 1800 related to the event, the companion electronic device 204 selectively provides information related to the event for use in performing one or more activities in the companion electronic device 204. For example, in FIG. 17, an embodiment is described in which the source electronic device 202 separately announces information related to an event from the above-described event announcement (eg, event announcement 1300). In other words, in some embodiments, the activity announcement 1300 is transmitted in addition to the information announcement 1800 related to the activity. However, in some embodiments, some or all of the activity-related information (ie, actual information, indicators, etc.) described above is included in the activity announcement 1300. In these embodiments, a separate event-related information bulletin 1800 may not be used. In these embodiments, the activity announcement 1300 includes various fields, values, etc. for retaining information related to the activity or based on the information. In these embodiments, the companion electronic device 204 can perform operations similar to those shown in FIG. 19 to process event-related information in the event announcement 1300. Although the information bulletin 1800 related to the event is shown as an example of the information bulletin related to the event, in some embodiments, the information bulletin 1800 related to the event is formatted in different ways (for example, including different configurations of fields, etc. ). For example, in some embodiments, one or more of the fields described as optional are not optional. In general, the event-related information announcement 1800 includes sufficient information to enable the source electronic device 202 to communicate the event-related information to the companion electronic device 204 so that the companion electronic device 204 can provide the event-related information to Used in 204 to perform one or more activities. FIG. 19 presents a flowchart illustrating a processing procedure for receiving activity-related information from a source electronic device in a companion electronic device according to some embodiments. More specifically, FIG. 19 illustrates an embodiment where accompanying electronic device 204 receives activity-related information from source electronic device 202. It should be noted that the operations shown in FIG. 19 are presented as general examples of operations performed by some embodiments. The operations performed by some embodiments include different operations and / or operations performed in different orders. In addition, although some mechanisms are used to describe operations (eg, accompanying electronic device 204, etc.), in some embodiments, other mechanisms perform operations. For the processing procedure shown in FIG. 19, the contents of the scrapbook in the source electronic device 202 are used as information related to the activity. However, in some embodiments, and as described above, other types of activity-related information may be received from the source electronic device 202. The processing procedure shown in FIG. 19 starts when the electronic device 204 receives the information bulletin 1800 related to the activity from the source electronic device 202 (step 1900). As described above, this operation may include receiving information including information that enables the companion electronic device 204 to process activity-related information and selectively provide information related to the activity to be used when performing one or more activities in the companion electronic device 204 Information announcements related to activities such as unicast, broadcast, and multicast 1800. The accompanying electronic device 204 then determines whether the event-related information described in the event-related information bulletin 1800 is of interest (1902). Generally speaking, during this operation, the companion electronic device 204 determines whether the information related to the activity is to be used for the companion electronic device 204. It should be noted that in this specification, the operation of deciding that the information related to the event is of concern and correspondingly providing (or not providing) the information related to the event is described as "selectively" providing the information related to the event. In other words, the companion electronic device 204 selects whether to provide information related to the event to the event in the companion electronic device 204 as described herein. In some embodiments, when determining whether the information related to the activity is of interest, the accompanying electronic device 204 presents an information availability indicator related to the activity on a display (eg, display 1400) accompanying the electronic device 204. FIG. 20 presents a block diagram illustrating an information availability indicator 2000 related to an activity according to some embodiments. As can be seen in FIG. 20, the information availability indicator 2000 related to the activity is an icon presented on the display 1400 accompanying the electronic device 204. In some embodiments, the activity availability information indicator 2000 is a simple icon that generally indicates that the activity related information is available. However, in some embodiments, the activity-related information availability indicator 2000 includes an indication of the type of activity-related information in the icon (eg, text indicator, video indicator, undo buffer indicator as shown Device, scrapbook indicator, combination indicator, etc.). Similar to the recoverable activity indication 1404 described above, in some embodiments, the user can select the information availability indicator 2000 related to the activity to signal the acceptance (or non-acceptance) of the information related to the activity to the accompanying Electronic device 204. For example, the user may touch the activity availability information indicator 2000 with a finger on the touch-sensitive screen, and hover and click the mouse pointer on the activity availability information indicator 2000. Drag the information availability indicator 2000 related to the event along the designated path, etc. In some embodiments, the acceptance of the information related to the activity causes the accompanying electronic device 204 to determine that the information related to the activity is of interest. In some embodiments, when determining whether the information related to the activity is of interest (in addition to or in lieu of using the information availability indicator 2000 related to the activity described above), the accompanying electronic device 204 determines whether the corresponding activity Whether to transfer the information related to the activity from the source electronic device 202 to the companion electronic device 204 in a format supported by the companion electronic device 204, etc. Generally speaking, when the information related to the activity should and can make the activity in the accompanying electronic device 204 available, the accompanying electronic device 204 determines that the information related to the activity is of interest. If the event-related information described in the event-related information announcement 1800 is not of interest (step 1904), the accompanying electronic device 204 may stop the process related to the event-related information announcement 1800 and the processing procedure ends. For this operation, in some embodiments, the accompanying electronic device 204 can remove the information availability indicator 2000 related to the activity from the display screen, can configure itself to ignore future repeated announcements, can convey a negative answer or refuse to the source Electronic device 202, etc. If the event-related information described in the event-related information bulletin 1800 is of interest (step 1904), the electronic device 204 accompanies the event-related information (1906). Generally speaking, during this operation, the accompanying electronic device 204 retrieves at least some of the information related to the activity from one or both of the information bulletin 1800 related to the activity and the source electronic device 202. For this operation, if the information bulletin 1800 related to the event contains some or all of the actual information related to the event, the accompanying electronic device 204 can obtain some or some of the information related to the event from the information bulletin 1800 related to the event All. For example, assuming that the source electronic device 202 includes at least some of the contents of the scrapbook in the information bulletin 1800 related to the event, the accompanying electronic device 204 can obtain the contents of the scrapbook from the information bulletin 1800 related to the event. In addition to or in lieu of obtaining information related to the event from the information bulletin 1800 related to the event, the accompanying electronic device 204 may obtain some or all of the information related to the event from the source electronic device 202. For example, if the source electronic device 202 includes an indicator (or other indicator) to the event-related information on the source electronic device 202 in the activity-related information bulletin 1800 (for example, a clip to the source electronic device 202 The information such as image files on the book, etc.), the accompanying electronic device 204 may request the source electronic device 202 for information related to the activity. In some embodiments, the information related to the event can be obtained by the source electronic device 202 together with the extended event data, that is, it can be included in the extended event data. In some of these embodiments, accompanying electronic device 204 requests to send event-related information along with extended event data. For example, the event-related information bulletin 1800 may include an indication that the event-related information is available (eg, indicators or other indicators), and as described herein, the electronic device may receive a request to obtain data related to the event And transfer the corresponding activities (that is, request to extend the activity data). The companion electronic device 204 then provides information related to the activity for use when performing one or more activities in the companion electronic device 204 (step 1908). During this operation, the electronic device 204 uses one or more corresponding structures (memory, clipboard, cache, buffer, etc.) to store information related to the event so that the information related to the event can be used for the event (e.g. Move from the source electronic device 202 to the activity accompanying the electronic device 204, the activity started on the accompanying electronic device 204, etc.). In some embodiments, "providing activity-related information for use in performing one or more activities" includes providing activity-related information in a manner that can be used in a corresponding and expected manner during the operation of the activity . Continuing the scrapbook example, this may include making the contents of the scrapbook from the source electronic device 202 available for pasting and other operations, because the information on the scrapbook (that is, from the scrapbook accompanying the electronic device 204) is generally available In the accompanying electronic device 204. For example, hotkeys and menu selections can be used to access the contents of the scrapbook copied from the source electronic device 202 on the companion electronic device 204. As another example, assuming that the information related to the activity includes the contents of the undo buffer, the undo buffer in the electronic device 204 can use the information related to the activity (that is, the history of operations performed in the source electronic device 202) To update so that the corresponding operation that was not originally performed in the companion electronic device 204 can be undone in the companion electronic device 204. Continuing the scrapbook example, in some embodiments, providing information related to the activity to use when copying the content of the scrapbook described in the information bulletin 1800 related to the activity when performing one or more activities in the companion electronic device 204 To accompany the scrapbook in the electronic device 204. In these embodiments, the contents of the scrapbook may be partially or completely overwritten by the contents of the scrapbook described in the information bulletin 1800 related to the event. In some embodiments, in order to avoid overwriting and thus loss of applicable information on the scrapbook accompanying the electronic device 204, an independent transfer information buffer is provided along with the electronic device 204 (eg, the operating system thereon). In these embodiments, corresponding menu selections, hot keys, etc. may be used to access the transfer information buffer. In some embodiments, the user may be presented with the option to overwrite the scrapbook or write information to the transfer activity buffer (eg, with a prompt). In some embodiments, the transfer information buffer is a software service that provides temporary storage of information in the electronic device (such as operating system software services, stand-alone applications, etc.), but the hardware-based transfer information buffer can be separate or with software The transfer information buffer is used in combination. The transfer information buffer enables users to perform operations such as copying, pasting, cutting, etc. to interact with the information stored in the transfer information buffer. In some embodiments, the user may be presented with an interface (eg, on the display 1400) that enables the user to determine what content from the scrapbook of the source electronic device 202 is to be copied to the scrapbook in the accompanying electronic device and from the source The contents of the scrapbook of the electronic device 202 are to be copied to the accompanying scrapbook in the electronic device. For example, after selecting the information availability indicator 2000 related to the activity, a pop-up window that displays or otherwise lists the contents of the scrapbook from the source electronic device 202 may be presented on the display 1400. The pop-up window includes An organization that selects which content to copy to the scrapbook accompanying the electronic device 204, where to copy the content to the scrapbook, and so on. It should be noted that although the information availability indicator 2000 related to the activity is presented in a specific location on the lock screen, in some embodiments, the information availability indicator 2000 related to the activity may be presented during the operation accompanying the electronic device 204 On any screen, in different locations, etc. In addition, information availability indicator 2000 related to the activity may be presented along with and / or associated with the recoverable activity indication 1404. In these embodiments, the user may select one or both of the information availability indicator 2000 and the resumeable activity indication 1404 related to the activity to perform the transfer activity (as described herein) or receive information related to the activity One or both. In some embodiments, the companion electronic device 204 only presents the resumeable activity indication 1404 and the user selects the resumeable activity indication 1404 so that the companion electronic device 204 transfers the activity (as described herein) and accepts information related to the activity. The foregoing description of the embodiments is presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the embodiments to the disclosed form. Therefore, many modifications and changes will be apparent to those skilled in the art. In addition, the above disclosure is not intended to limit the embodiments. The scope of the embodiments is defined by the scope of the attached patent application.

100‧‧‧Electronic device

102‧‧‧ processing subsystem

104‧‧‧Memory subsystem

106‧‧‧Network connection subsystem

108‧‧‧ Display subsystem

200‧‧‧Network environment

202‧‧‧Source electronic device

204‧‧‧With electronic device

206‧‧‧Second source electronic device

208‧‧‧Communication signal

1100‧‧‧Event Information

1102‧‧‧Application identifier

1104‧‧‧Activity descriptor

1106‧‧‧Time stamp

1108‧‧‧ flag

1110‧‧‧Event Information

1112‧‧‧Application identifier

1114‧‧‧Activity descriptor

1116‧‧‧Timestamp

1118‧‧‧ flag

1120‧‧‧Event Information

1122‧‧‧Application identifier

1124‧‧‧Activity descriptor

1126‧‧‧Time stamp

1128‧‧‧ flag

1130‧‧‧Event Information

1132‧‧‧Application identifier

1134‧‧‧Activity descriptor

1136‧‧‧Time stamp

1138‧‧‧ flag

1200‧‧‧Announcement Activity Table

1202‧‧‧entry items

1204‧‧‧Activity identifier

1206‧‧‧Enter the item index

1212‧‧‧entry items

1214‧‧‧ Activity identifier

1216‧‧‧Enter the item index

1222‧‧‧entry items

1224‧‧‧Activity identifier

1226‧‧‧Enter the item index

1232‧‧‧entry items

1234‧‧‧ Activity identifier

1236‧‧‧Enter the item index

1300‧‧‧Event announcement / Event announcement message

1302‧‧‧Device ID field

1304‧‧‧Version ID field

1306‧‧‧Activity identifier field

1308‧‧‧ flag field

1310‧‧‧Timestamp field

1400‧‧‧Monitor

1402‧‧‧Unlock indicator

1404‧‧‧Resumable activity instructions

1406‧‧‧ Path

1500‧‧‧Event Announcement

1502‧‧‧ Request for extension activities

1504‧‧‧Extended event information

1506‧‧‧Notice of activity transfer

1600‧‧‧Electronic device

1602‧‧‧Scope

1604‧‧‧Scope

1606‧‧‧Scope

1800‧‧‧ Information announcement related to the event

1802‧‧‧Device ID field

1804‧‧‧Version ID field

1806‧‧‧Activity identifier field

1808‧‧‧Timestamp field

1810‧‧‧ Information field related to the event

2000‧‧‧ Activity availability indicator

FIG. 1 presents a block diagram illustrating an electronic device according to some embodiments. FIG. 2 presents a block diagram illustrating a network environment according to some embodiments. FIG. 3 presents a flowchart illustrating a processing procedure for broadcasting event announcement messages according to some embodiments. FIG. 4 presents a flowchart illustrating a processing procedure for storing activity information describing activities available at an accompanying electronic device according to some embodiments. FIG. 5 presents a flowchart illustrating a processing procedure for requesting extension activity data and transferring activities according to some embodiments. FIG. 6 presents a flowchart illustrating a processing procedure for responding to requests for extended activity data according to some embodiments. 7 presents a flowchart illustrating a processing procedure for determining whether a second application is available at a companion electronic device according to some embodiments. 8 presents a flowchart illustrating a processing procedure for determining a second application using flags according to some embodiments. 9 presents a flowchart illustrating a processing procedure for determining whether a second application is available when an activity identifier identifies an input item in a structure storing an announced activity, according to some embodiments. FIG. 10 presents a flowchart illustrating a processing procedure for determining the most recent activity from two or more activity announcement messages according to some embodiments. 11 presents a block diagram illustrating activity information according to some embodiments. FIG. 12 presents a block diagram illustrating an announcement activity table according to some embodiments. 13 presents a block diagram illustrating an activity announcement message according to some embodiments. Figure 14 presents a block diagram illustrating an indication of resumable activity according to some embodiments. 15 presents a swimlane diagram illustrating messages exchanged between electronic devices according to some embodiments. 16 presents a block diagram illustrating electronic devices that are close to each other according to some embodiments. FIG. 17 presents a flowchart illustrating a processing procedure for forwarding activity-related information from a source electronic device to a companion electronic device according to some embodiments. FIG. 18 presents a block diagram illustrating an event-related information announcement generated by a source electronic device according to some embodiments. FIG. 19 presents a flowchart illustrating a processing procedure for receiving activity-related information from a source electronic device in a companion electronic device according to some embodiments. FIG. 20 presents a block diagram illustrating information availability indicators related to activities in accordance with some embodiments. In the drawings, similar reference numerals refer to the same drawing elements.

Claims (18)

A method comprising: performing an operation for the following by means of a companion electronic device: receiving an announcement containing information related to an event from a source electronic device or the information related to an event can be obtained from the source electronic device Using an instruction, the information related to the activity includes source scrapbook information, the source scrapbook information includes a copy of some or all of a content of a scrapbook in the source electronic device; in response to receiving the announcement The information related to the event, extract the information related to the event from the announcement; in response to receiving the instruction in the announcement, request the information related to the event and receive the event in a separate transmission Related information; and selectively provide the information related to the activity for use in performing one or more activities in the accompanying electronic device. The method of claim 1, wherein the activity-related information is selectively provided to be used when performing the one or more activities includes: using the source scrapbook information to replace a content of a scrapbook in the accompanying electronic device Some or all of them. The method of claim 1, wherein selectively providing the activity-related information for use when performing one or more activities includes: storing the source scrapbook information in a transfer information buffer in the accompanying electronic device The transfer information buffer is different from a scrapbook in the companion electronic device; and the source scrapbook information from the transfer information buffer is provided for use in activities in the companion electronic device. The method of claim 1, wherein requesting the information related to the activity includes: using the instruction to request some or all of the information related to the activity from the source electronic device. The method of claim 1, wherein receiving the event-related information from the source electronic device includes: requesting the source electronic device for extended activity data, the extended activity data including an application program that can be used to configure the accompanying electronic device To continue information from an activity of the source electronic device; and receive the information related to the activity together with extended activity data for the activity performed in the first application from the source electronic device. The method of claim 1, wherein selectively providing the activity-related information includes: presenting an activity-related information availability indicator on a display of the accompanying electronic device; upon receiving the activity-related information availability After accepting the indicator, provide the activity-related information for use when performing one or more activities in the accompanying electronic device; and after receiving a rejection of the activity-related information availability indicator , Does not provide information related to the activity to be used when performing one or more activities in the accompanying electronic device. An accompanying electronic device, comprising: a processing subsystem; and a network connection subsystem; the accompanying electronic device: receiving an announcement containing information related to an activity from a source electronic device or the information related to an activity can be An indication used by the source electronic device that the activity-related information includes source scrapbook information that includes a copy of some or all of a content of a scrapbook in the source electronic device; Receive the event-related information in the announcement, extract the event-related information from the announcement; in response to receiving the instruction in the announcement, request the event-related information in a separate transmission and receive the Activity-related information; and selectively provide the activity-related information for use in performing one or more activities in the accompanying electronic device. The accompanying electronic device of claim 7, further comprising: a scrapbook; wherein when the information related to the activity is selectively provided for use when performing the one or more activities, the accompanying electronic device: uses the source The scrapbook information replaces some or all of a content accompanying the scrapbook in the electronic device. As the accompanying electronic device of claim 7, it further includes: a transfer information buffer, which is different from a scrapbook in the accompanying electronic device; wherein the information related to the activity is selectively provided When used when performing one or more activities, the companion electronic device: stores the source scrapbook information in the transfer information buffer; and provides the source scrapbook information from the transfer information buffer to the companion electronic device Used in activities. As in the accompanying electronic device of item 7, wherein when requesting the activity-related information, the accompanying electronic device: uses the instruction to request some or all of the activity-related information from the source electronic device. The accompanying electronic device of claim 7, wherein when receiving the event-related information from the source electronic device, the accompanying electronic device: requests the source electronic device for extended activity data, the extended activity data includes information that can be used to configure the Accompanying an application in the electronic device to continue information from an activity of the source electronic device; and receiving the information related to the activity together with the activity for execution in the first application from the source electronic device Extended activity information. The accompanying electronic device of claim 7 further includes: a display subsystem including a display; wherein when selectively providing the activity-related information, the accompanying electronic device: presents on the display An information availability indicator related to the activity; after receiving an acceptance of the information availability indicator related to the activity, providing the activity-related information for use when performing one or more activities in the accompanying electronic device Information; and after receiving a rejection of the availability indicator of the activity-related information, the activity-related information for use when performing one or more activities in the accompanying electronic device is not provided. A computer-readable storage medium storing instructions that when executed by a processing subsystem in a companion electronic device causes the companion electronic device to execute a method, the method comprising: receiving from a source electronic device An announcement of the information or an indication that the activity-related information can be used from the source electronic device, the activity-related information includes source scrapbook information, and the source scrapbook information includes a scrapbook in the source electronic device A copy of some or all of a content of; a response to receiving the information related to the event in the announcement, extracting the information related to the event from the announcement; a response to receiving the instruction in the announcement, in a separate Requests transmission of the information related to the activity and receives the information related to the activity; and selectively provides the information related to the activity for use in performing one or more activities in the accompanying electronic device. The computer-readable storage medium of claim 13, wherein the information related to the activity is selectively provided to be used when the one or more activities are performed, including: using the source scrapbook information to replace one of the accompanying electronic device clips Some or all of the contents of the book. The computer-readable storage medium of claim 13, wherein the activity-related information is selectively provided for use when performing one or more activities including: storing the source scrapbook information in one of the accompanying electronic devices for transfer In the information buffer, the transfer information buffer is different from a scrapbook in the companion electronic device; and the source scrapbook information from the transfer information buffer is provided for use in activities in the companion electronic device. For example, the computer-readable storage medium of claim 13, wherein requesting the information related to the activity includes: using the instruction to request some or all of the information related to the activity from the source electronic device. The computer-readable storage medium of claim 13, wherein receiving the event-related information from the source electronic device includes: requesting the source electronic device for extended activity data, the extended activity data includes information that can be used to configure the accompanying electronic device An application to continue information from an activity of the source electronic device; and receive the information related to the activity together with extended activity data for the activity executed in the first application from the source electronic device. The computer-readable storage medium of claim 13, wherein selectively providing the activity-related information includes: presenting an activity-related information availability indicator on a display of the accompanying electronic device; upon receiving the activity-related information Upon acceptance of the relevant information availability indicator, provide the activity-related information for use when performing one or more activities in the accompanying electronic device; and upon receiving the activity-related information availability indicator After a rejection, the event-related information used for performing one or more activities in the accompanying electronic device is not provided.