PATENT DOCUMENT

Publication Number: US-8655322-B2
Application Number: US-201113111908-A
Country: US
Kind Code: B2

Title: Disabling access point notifications

Abstract:
Disabling wireless access point notifications is described. In some implementations, wireless access point notifications on a mobile device can be disabled when movement of the mobile device is detected. In some implementations, wireless access point notifications on a mobile device can be re-enabled when the mobile device detects that the mobile device has been stationary for a specified period of time following movement of the mobile device. In some implementations, wireless access point notifications can be disabled on a per access point basis.

Claims:
What is claimed is: 
     
       1. A method comprising:
 detecting a wireless access point at a device; 
 causing a wireless access point notification to be presented for the wireless access point as a graphical object on a display of the device; 
 receiving input to the graphical object to disable future wireless access point notifications for the wireless access point; and 
 storing wireless access point information indicating that wireless access point notifications are disabled for the wireless access point, 
 where the method is performed by one or more processors. 
 
     
     
       2. A method comprising:
 detecting a first wireless access point at a device; 
 determining whether access point notifications for the first wireless access point have been disabled; 
 preventing presenting an access point notification for the first wireless access point when access point notifications have been disabled for the first wireless access point; 
 detecting a second wireless access point at the device; 
 determining whether access point notifications for the second wireless access point have been disabled; and 
 causing an access point notification for the second wireless access point to be presented when access point notifications have not been disabled for the second wireless access point, where the method is performed by one or more processors. 
 
     
     
       3. The method of  claim 2 , further comprising:
 storing access point information that identifies one or more wireless access points for which wireless access point notifications have been disabled; and 
 determining whether access point notifications for the first wireless access point have been disabled based on the access point information. 
 
     
     
       4. The method of  claim 2 , further comprising displaying a listing of detected wireless access points, wherein the listing includes the second wireless access point, but does not include the first wireless access point. 
     
     
       5. A non-transitory computer-readable medium including one or more sequences of instructions which, when executed by one or more processors, causes:
 detecting a wireless access point at a device; 
 presenting a wireless access point notification for the wireless access point as a graphical object on a display of the device; 
 receiving input to the graphical object to disable future wireless access point notifications for the wireless access point; and 
 storing wireless access point information indicating that wireless access point notifications are disabled for the wireless access point. 
 
     
     
       6. A system comprising:
 at least one processor; and 
 a computer-readable medium including one or more sequences of instructions which, when executed by the at least one processor, causes:
 detecting a wireless access point at a device; 
 presenting a wireless access point notification for the wireless access point as a graphical object on a display of the device; 
 receiving input to the graphical object to disable future wireless access point notifications for the wireless access point; and 
 storing wireless access point information indicating that wireless access point notifications are disabled for the wireless access point. 
 
 
     
     
       7. A non-transitory computer-readable medium including one or more sequences of instructions, executable by one or more processors to:
 detect a first wireless access point at a device; 
 determine whether access point notifications for the first wireless access point have been disabled; 
 prevent presenting an access point notification for the first wireless access point when access point notifications have been disabled for the first wireless access point; 
 detect a second wireless access point at the device; 
 determine whether access point notifications for the second wireless access point have been disabled; and 
 cause an access point notification for the second wireless access point to be presented when access point notifications have not been disabled for the second wireless access point, where the method is performed by one or more processors. 
 
     
     
       8. The non-transitory computer-readable medium of  claim 7 , wherein the instructions are further executable to:
 store access point information that identifies one or more wireless access points for which wireless access point notifications have been disabled; and 
 determine whether access point notifications for the first wireless access point have been disabled based on the access point information. 
 
     
     
       9. The non-transitory computer-readable medium of  claim 7 , wherein the instructions are further executable to:
 display a listing of detected wireless access points, wherein the listing includes the second wireless access point, but does not include the first wireless access point. 
 
     
     
       10. A system comprising:
 at least one processor; and 
 a computer-readable medium including one or more sequences of instructions, executable by the at least one processor to:
 detect a first wireless access point at a device; 
 determine whether access point notifications for the first wireless access point have been disabled; 
 prevent presenting an access point notification for the first wireless access point when access point notifications have been disabled for the first wireless access point; 
 detect a second wireless access point at the device; 
 determine whether access point notifications for the second wireless access point have been disabled; and 
 cause an access point notification for the second wireless access point to be presented when access point notifications have not been disabled for the second wireless access point, where the method is performed by one or more processors. 
 
 
     
     
       11. The system of  claim 10 , wherein the instructions are further executable to:
 store access point information that identifies one or more wireless access points for which wireless access point notifications have been disabled; and 
 determine whether access point notifications for the first wireless access point have been disabled based on the access point information. 
 
     
     
       12. The system of  claim 10 , wherein the instructions are further executable to:
 display a listing of detected wireless access points, wherein the listing includes the second wireless access point, but does not include the first wireless access point.

Description:
TECHNICAL FIELD 
     The disclosure generally relates to wireless network detection. 
     BACKGROUND 
     Modern mobile computing devices are capable of detecting and connecting to wireless access points for accessing networks, including the internet. These computing devices often provide notifications (e.g., dialog boxes, pop-up windows, etc.) to users when access points are detected. Wireless access point notifications are often displayed to provide the user of the mobile device with a convenient way to identify and connect to wireless access points. However, in some circumstances, wireless access point notifications can be inconvenient and can interfere with the use of mobile computing devices. 
     SUMMARY 
     Disabling wireless access point notifications is described. In some implementations, wireless access point notifications on a mobile device can be disabled when movement of the mobile device is detected. In some implementations, wireless access point notifications on a mobile device can be re-enabled when the mobile device detects that the mobile device has been stationary for a specified period of time following movement of the mobile device. In some implementations, movement of the mobile device can be detected based on the strength of wireless access point signals received at the mobile device. In some implementations, movement of the mobile device can be detected based on global positioning system data, motion sensor data, cell tower triangulation, or any other type of location and/or movement determining mechanism. 
     In some implementations, wireless access point notifications can be disabled on a per access point basis. For example, a user can interact with a wireless access point notification to indicate a wireless access point for which future wireless access point notifications should be disabled. 
     Particular implementations provide at least the following advantages: wireless access point notifications are dynamically and automatically disabled; wireless access point notifications are prevented from displaying at inconvenient or inappropriate times. 
     Details of one or more implementations are set forth in the accompanying drawings and the description below. Other features, aspects, and potential advantages will be apparent from the description and drawings, and from the claims. 
    
    
     
       DESCRIPTION OF DRAWINGS 
         FIG. 1  illustrates an example of a mobile device moving between wireless access points. 
         FIG. 2  a flow diagram of an example process for disabling wireless access point notifications. 
         FIGS. 3A and 3B  illustrate example interfaces for disabling individual wireless access point notifications. 
         FIG. 4  is flow diagram of an example process for disabling individual wireless access point notifications. 
         FIG. 5  is a flow diagram of an example process for preventing wireless access point notifications. 
         FIG. 6  is a block diagram of an exemplary system architecture implementing the features and processes of  FIGS. 1-5 . 
     
    
    
     Like reference symbols in the various drawings indicate like elements. 
     DETAILED DESCRIPTION 
     Automatically Disabling Notifications 
       FIG. 1  illustrates an example of a mobile device  108  moving between wireless access points  102 ,  104  and  106  on a city grid  100 . For example, mobile device  108  (e.g., a cell phone, smartphone, laptop, etc.) can be moved along path  130 . Mobile device  108  can be carried on a person or transported in a vehicle, for example. As mobile device  108  moves along path  130  (e.g., along a street or sidewalk), mobile device  108  can detect wireless access points  102 ,  104 ,  106 . For example, wireless access points  102 ,  104  and  106  can correspond to wireless access points provided my various businesses, such as coffee houses, restaurants, bookstores, etc., that mobile device  108  may pass as it travels along path  130 . 
     In some implementations, when mobile device  108  detects a wireless access point, mobile device  108  can present a wireless access point notification. For example, mobile device can display a window or dialog box on a display that indicates that a wireless access point has been detected and identifies (e.g., by name) the wireless access point to the user. In some implementations, the user can provide input to mobile device  108  (e.g., through the displayed wireless access point notification) to cause mobile device  108  to connect, join or associate with the detected wireless access point. 
     Sometimes, however, a user may not want to connect to wireless access points while the user, and mobile device  108 , is moving. For example, a user may be riding in a moving car. The speed at which the car is traveling may not allow for mobile device  108  to stay in range of a stationary wireless access point (e.g., wireless access points  102 ,  104 ,  106 ) for long enough to access data through the wireless access point. For example, by the time the moving mobile device  108  connects to the wireless access point, mobile device  108  may be moving out of range of the wireless access point and be forced to disconnect from the wireless access point. 
     Moreover, a user of mobile device  108  may be using mobile device  108  while mobile device  108  is moving. For example, a passenger in a moving car may be using a feature or application of mobile device  108 . If the passenger/user is repeatedly interrupted by wireless access point notifications while using mobile device  108 , the user may get annoyed or frustrated by the interruptions. For example, as mobile device  108  moves from location  110 , to location  116 , to location  118 , to location  120 , the mobile device can detect three wireless access points  102 ,  104 ,  106  and present three wireless access point notifications. If a user is using mobile device  108  as the mobile device moves from location  110  to location  120 , the user will be interrupted with wireless access point notifications three times even though mobile device  108  may not stay within range of any wireless access point for long enough to use the wireless access point. 
     In some implementations, wireless access point notifications on mobile device  108  can be automatically disabled while mobile device  108  is moving. For example, wireless access point notifications can be disabled when mobile device  108  is moving so that wireless access point notifications will not be presented when a user is unlikely to join detected wireless access points. 
     In some implementations, movement of mobile device  108  can be detected based on the strength of the signal received from a wireless access point. For example, mobile device  108  can receive signals from wireless access point  102  at locations  110 ,  112 , and  114 . At each of the locations  110 ,  112  and  114  the signal strength of the signal received from wireless access point  102  can change or can have different strengths. For example, the signal strength of the signal received from wireless access point  102  at location  110  can be weaker than the signal strength at location  112 . The signal strength of the signal received from wireless access point  102  at location  114  can be weaker than the strength of the signal received at location  112  and weaker than the signal received at location  110 . In some implementations, movement of mobile device  108  can be determined based on the strength of the signal received from a wireless access point over a period of time. For example, if the signal strength of a signal from wireless access point  102  received at mobile device  108  is weak at first, then becomes stronger, then becomes weaker, mobile device  108  is likely moving relative to wireless access point  102 . The gradual increase in signal strength from location  110  to location  112  can indicate that mobile device  108  is moving closer to wireless access point  102 . The gradual decrease in signal strength from location  112  to location  114  can indicate that mobile device  108  is moving away from wireless access point  102 . 
     In some implementations, wireless access point notifications for mobile device  108  can be enabled once mobile device  108  has stopped moving or has become stationary. For example, if a user carrying mobile device  108  stops at a coffee shop that provides wireless access point  104 , the user may be more likely to want to connect to the coffee shop&#39;s wireless access point  104 . Thus, mobile device  108  can be configured to present wireless access point notifications once mobile device  108  has stopped moving. 
     In some implementations, wireless access point notifications for mobile device  108  can be enabled once mobile device  108  has stopped moving for a configured or specified period of time. For example, if mobile device  108  is moving in a car and the car temporarily stops at a stop light, the user of mobile device  108  is not likely to want to connect to any wireless access points because the car is going to start moving again once the stop light turns green. To prevent presenting notifications during short pauses in movement, mobile device  108  can be configured to enable wireless access point notifications only after mobile device  108  has stopped moving for a configured period of time (e.g., three minutes, five minutes, the duration of a stop light, etc.). 
       FIG. 2  a flow diagram of an example process  200  for disabling wireless access point notifications. In some implementations, wireless access point notifications on a mobile device configured to present wireless access point notifications can be automatically disabled based on detected movement of the mobile device. In some implementations, wireless access point notifications on a mobile device can be automatically enabled based on determining that the mobile device has stopped moving. 
     At step  202 , a wireless access point is detected at a mobile device. For example, the wireless access point can be detected by wireless communication subsystem  624  of  FIG. 6 . 
     At step  204 , a determination is made whether the mobile device is moving. In some implementations, the determination is made based in wireless access point signal strengths, as described above. In some implementations, the determination is made based on global positioning system data, movement sensor data (e.g., accelerometer data), and/or based on location triangulation techniques using signals transmitted from cell towers, wireless access points, or other transmission sources. 
     At step  206 , wireless access point notifications on the mobile device can be disabled when the mobile device is moving. In some implementations, when mobile device  108  determines that mobile device  108  is moving, wireless access point notifications can be disabled on mobile device  108 . For example, wireless access point notification popups, windows, dialog boxes, etc. can be prevented from displaying on mobile device  108  while mobile device  108  is moving. 
     At step  208 , wireless access point notifications can be enabled (re-enabled) on the mobile device when the mobile device has stopped moving. In some implementations, mobile device  108  can determine when mobile device  108  has stopped moving. For example, the same techniques for detecting movement described at step  204  can be used to determine when mobile device  108  has stopped moving. In some implementations, mobile device  108  can determine when mobile device  108  has stopped moving for a configured period of time. For example, mobile device  108  can store data indicating a period of time that the mobile device needs to be stationary before wireless access points are enabled on mobile device  108 . Once mobile device  108  determines that mobile device  108  has stopped moving, mobile device  108  can wait the configured period of time before enabling wireless access point notifications on mobile device  108 . 
     Manually Disabling Individual Notifications 
       FIG. 3A  illustrates example interface  300  for disabling individual wireless access point notifications. For example, a mobile device can be configured to present wireless access point notifications when the mobile device detects a wireless access point. In some implementations, detected wireless access points can be displayed on interface  300 . For example, interface  300  can present graphical elements  302 ,  304 ,  306  and  308  on interface  300  for displaying information related to detected wireless access points. For example, graphical elements  302 - 308  can each be associated with a corresponding wireless access point and present information for the wireless access point, such as display names associated with wireless access points, security information (e.g., encryption algorithms, password requirements, etc.), and signal strength. 
     In some implementations, a user can interact with graphical elements  302 - 308  to disable wireless access point notifications for particular wireless access points. For example, if interface  300  is presented on a touch-sensitive display (e.g., touch screen  646  of  FIG. 6 ), a user may slide a finger along graphical element  308  as indicated by dashed line  310  to cause graphical element  312  to display. In some implementations, graphical element  312  can be selected by a user to disable wireless access point notifications for the wireless access point associated with graphical element  308 . For example, when a user selects graphical element  312 , information can be stored on the mobile device that indicates that wireless access point notification should not be presented when the wireless access point corresponding to graphical element  308  is detected in the future. 
     In some implementations, a user can select graphical element  312  to present options for the wireless access point corresponding to graphical element  304 . For example, if a user selects graphical element  312 , interface  350  can be displayed on the mobile device. 
       FIG. 3B  illustrates example interface  350  for disabling individual wireless access point notifications. In some implementations, a user can provide input to interface  350  to disable wireless access point notifications for the wireless access point associated with user interface  350 . In some implementations, a user can select graphical element  352  to disable future wireless access point notifications for the wireless access point associated with interface  350 . 
     In some implementations, a user can input authentication information into graphical element  354 . For example, some wireless access points can require a user or device to be authorized to access the wireless access point. A user can provide authentication information (e.g., a password, key, etc.) through graphical element  354 . Once the user has provided the authentication information, the user can select graphical element  356  to join or connect to the wireless access point. If a user does not want to connect to the wireless access point, the user can select graphical element  358  to close interface  350  without connecting to the wireless access point. 
       FIG. 4  is flow diagram of an example process for disabling individual wireless access point notifications. At step  402 , a wireless access point is detected at a mobile device. For example, wireless communication subsystem  624  of  FIG. 6  can detect wireless access points that are reachable by the mobile device. 
     At step  404 , a wireless access point notification is presented. For example, in response to detecting wireless access points, the mobile device can present a wireless access point notification identifying some or all of the wireless access points that are reachable by the mobile device. The wireless access point notification can also provide information identifying the wireless access point, indicating the strength of the signal received from the wireless access point and/or authentication requirements. 
     At step  406 , input is received to disable future notifications for a wireless access point. For example, a user can disable future wireless access point notifications for selected wireless access points, as described above with reference to  FIG. 3A and 3B . 
     At step  408 , wireless access point information can be stored for disabled wireless access points. For example, the mobile device can maintain a database (e.g., access point notification database  674  of  FIG. 6 ) of wireless access points for which a user has disabled future wireless access point notifications. In some implementations, when input is received from a user indicating that the user does not wish to receive future wireless access point notifications for a particular wireless access point, identification information for the particular wireless access point (e.g., a name, service set identifier (SSID), media access control (MAC) address, etc.) can be stored in the database. For example, the database can be referenced when wireless access points are detected to determine which wireless access points should generate wireless access point notifications. 
       FIG. 5  is a flow diagram of an example process  500  for preventing wireless access point notifications. At step  502 , wireless access points are detected at a mobile device. For example, wireless communication subsystem  624  of  FIG. 6  can detect wireless access points that are reachable by the mobile device. 
     At step  504 , the mobile device can determine if notifications for the detected wireless access points are disabled. In some implementations, mobile device can compare information associated with the detected wireless access points (e.g., names, SSIDs, MAC addresses, etc.) to information stored in a wireless access point database to determine if wireless access point notifications are disabled for the detected wireless access points. For example, if a detected wireless access point is identified in the database or if the database indicates that notifications for the detected wireless access point have been disabled, then wireless access point notifications should not be generated for the detected wireless access point. 
     At step  506 , the mobile device can prevent wireless access point notifications from being presented for identified wireless access points. For example, if step  504  determines that notifications for a detected wireless access point were disabled, then a wireless access point notification will not be generated for the detected wireless access point. In some implementations, wireless access point notifications can be generated for some detected wireless access points and not for other detected wireless access points. For example, a detected wireless access point for which notifications were disabled will not appear in the listing of wireless access points on interface  3 A while a detected wireless access point for which notifications were not disabled may generate a wireless access point notification and appear in the wireless access point listing of interface  300 . 
     Example Mobile Device Architecture 
       FIG. 6  is a block diagram  600  of an example implementation of the mobile device  100  of  FIGS. 1-5 . The mobile device  100  can include a memory interface  602 , one or more data processors, image processors and/or central processing units  604 , and a peripherals interface  606 . The memory interface  602 , the one or more processors  604  and/or the peripherals interface  606  can be separate components or can be integrated in one or more integrated circuits. The various components in the mobile device  100  can be coupled by one or more communication buses or signal lines. 
     Sensors, devices, and subsystems can be coupled to the peripherals interface  606  to facilitate multiple functionalities. For example, a motion sensor  610 , a light sensor  612 , and a proximity sensor  614  can be coupled to the peripherals interface  606  to facilitate orientation, lighting, and proximity functions. Other sensors  616  can also be connected to the peripherals interface  606 , such as a positioning system (e.g., GPS receiver), a temperature sensor, a biometric sensor, or other sensing device, to facilitate related functionalities. 
     A camera subsystem  620  and an optical sensor  622 , e.g., a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, can be utilized to facilitate camera functions, such as recording photographs and video clips. The camera subsystem  620  and the optical sensor  622  can be used to collect images of a user to be used during authentication of a user, e.g., by performing facial recognition analysis. 
     Communication functions can be facilitated through one or more wireless communication subsystems  624 , which can include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of the communication subsystem  624  can depend on the communication network(s) over which the mobile device  100  is intended to operate. For example, a mobile device  100  can include communication subsystems  624  designed to operate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi or WiMax network, and a Bluetooth™ network. In particular, the wireless communication subsystems  624  can include hosting protocols such that the device  100  can be configured as a base station for other wireless devices. In some implementations, wireless communication subsystem can detect wireless access points, detect signal strengths of wireless access points and support other features described with reference to  FIGS. 1-5 . 
     An audio subsystem  626  can be coupled to a speaker  628  and a microphone  630  to facilitate voice-enabled functions, such as speaker recognition, voice replication, digital recording, and telephony functions. The I/O subsystem  640  can include a touch screen controller  642  and/or other input controller(s)  644 . The touch-screen controller  642  can be coupled to a touch screen  646 . The touch screen  646  and touch screen controller  642  can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen  646 . 
     The other input controller(s)  644  can be coupled to other input/control devices  648 , such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, and/or a pointer device such as a stylus. The one or more buttons (not shown) can include an up/down button for volume control of the speaker  628  and/or the microphone  630 . 
     In one implementation, a pressing of the button for a first duration can disengage a lock of the touch screen  646 ; and a pressing of the button for a second duration that is longer than the first duration can turn power to the mobile device  100  on or off. Pressing the button for a third duration can activate a voice control, or voice command, module that enables the user to speak commands into the microphone  630  to cause the device to execute the spoken command. The user can customize a functionality of one or more of the buttons. The touch screen  646  can, for example, also be used to implement virtual or soft buttons and/or a keyboard. 
     In some implementations, the mobile device  100  can present recorded audio and/or video files, such as MP3, AAC, and MPEG files. In some implementations, the mobile device  100  can include the functionality of an MP3 player, such as an iPod™. The mobile device  100  can, therefore, include a 36-pin connector that is compatible with the iPod. Other input/output and control devices can also be used. 
     The memory interface  602  can be coupled to memory  650 . The memory  650  can include high-speed random access memory and/or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and/or flash memory (e.g., NAND, NOR). The memory  650  can store an operating system  652 , such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks. 
     The operating system  652  can include instructions for handling basic system services and for performing hardware dependent tasks. In some implementations, the operating system  652  can be a kernel (e.g., UNIX kernel). In some implementations, the operating system  652  can include instructions for performing voice authentication. For example, operating system  652  can implement the features as described with reference to  FIGS. 1-5 . 
     The memory  650  can also store communication instructions  654  to facilitate communicating with one or more additional devices, one or more computers and/or one or more servers. The memory  650  can include graphical user interface instructions  656  to facilitate graphic user interface processing; sensor processing instructions  658  to facilitate sensor-related processing and functions; phone instructions  660  to facilitate phone-related processes and functions; electronic messaging instructions  662  to facilitate electronic-messaging related processes and functions; web browsing instructions  664  to facilitate web browsing-related processes and functions; media processing instructions  666  to facilitate media processing-related processes and functions; GPS/Navigation instructions  668  to facilitate GPS and navigation-related processes and instructions; and/or camera instructions  670  to facilitate camera-related processes and functions. 
     The memory  650  can store access point (AP) notification instructions  672  to facilitate the processes and functions described with reference to  FIGS. 1-5 . For example, the software instructions can include instructions for performing voice authentication on a per application or per feature basis and for allowing a user to configure authentication requirements of each application or feature available on device  100 . Memory  650  can store an access point notification database for storing information related to access points, such as the access point notification information stored and used with respect to the processes described with reference to  FIGS. 1-5 . 
     The memory  650  can also store other software instructions (not shown), such as web video instructions to facilitate web video-related processes and functions; and/or web shopping instructions to facilitate web shopping-related processes and functions. In some implementations, the media processing instructions  666  are divided into audio processing instructions and video processing instructions to facilitate audio processing-related processes and functions and video processing-related processes and functions, respectively. 
     Each of the above identified instructions and applications can correspond to a set of instructions for performing one or more functions described above. These instructions need not be implemented as separate software programs, procedures, or modules. The memory  650  can include additional instructions or fewer instructions. Furthermore, various functions of the mobile device  100  can be implemented in hardware and/or in software, including in one or more signal processing and/or application specific integrated circuits.

Metadata:
Filing Date: 20110519
Publication Date: 20140218
Grant Date: 20140218
Priority Date: 20110519
Inventors: NAAMAN ALEXANDRE
Assignee: APPLE INC
CPC Classifications: [{"code": "H04W4/027", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W48/14", "inventive": true, "first": true, "tree": "[]"}, {"code": "H04W48/08", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W4/027", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W48/14", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W68/02", "inventive": true, "first": true, "tree": "[]"}]
Family ID: 46028247