NODE-ENABLED MONITORING OF ACTIVITY OF A PERSON USING A HIERARCHICAL NODE NETWORK

• US 20150154844A1
• Filed: 11/12/2014
• Published: 06/04/2015
• Est. Priority Date: 11/29/2013
• Status: Active Grant

• Current Assignee: Fedex Corporate Services Incorporated (FedEx Corporation)
• Original Assignee: Fedex Corporate Services Incorporated (FedEx Corporation)
• Inventors: Skaaksrud, Ole-Petter
• Granted Patent: US 9,775,126 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: B60W 60/00256 Delivery operations
• CPC Class Codes: B65B 25/02 Packaging agricultural or horticultural products
• CPC Class Codes: B65D 25/02 Internal fittings of containers made by folding or erecting blanks made of paper B65D5/44
• CPC Class Codes: B65D 25/102 Straps, bands, strings or other elongate elements
• CPC Class Codes: G01C 21/3407 specially adapted for specific applications
• CPC Class Codes: G01C 21/3453 Special cost functions, i.e. other than distance or default speed limit of road segments
• CPC Class Codes: G01C 21/362 received from an external device or application, e.g. PDA, mobile phone or calendar application
• CPC Class Codes: G01S 2205/01 specially adapted for specific applications
• CPC Class Codes: G01S 5/0289 of multiple transceivers, e.g. in ad hoc networks
• CPC Class Codes: G01S 5/14 Determining absolute distances from a plurality of spaced points of known location
• CPC Class Codes: G05D 1/0022 characterised by the communication link data switching networks in general H04L12/00
• CPC Class Codes: G05D 1/0088 characterized by the autonomous decision making process, e.g. artificial intelligence, predefined behaviours using knowledge based models G06N5/00
• CPC Class Codes: G05D 1/021 specially adapted to land vehicles
• CPC Class Codes: G06K 19/0712 the arrangement being capable of triggering distinct operating modes or functions dependent on the strength of an energy or interrogation field in the proximity of the record carrier active means for hindering electromagnetic reading or writing G06K19/07336
• CPC Class Codes: G06K 7/10366 the interrogation device being adapted for miscellaneous applications
• CPC Class Codes: G06Q 10/083 Shipping
• CPC Class Codes: G06Q 10/0832 Special goods or special handling procedures, e.g. handling of hazardous or fragile goods
• CPC Class Codes: G06Q 10/0833 Tracking
• CPC Class Codes: G06Q 10/0835 Relationships between shipper or supplier and carriers
• CPC Class Codes: G06Q 10/08355 Routing methods
• CPC Class Codes: G06Q 10/0836 : Recipient pick-ups
• CPC Class Codes: G06Q 10/0838 : Historical data
• CPC Class Codes: G06Q 10/087 : Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: G06Q 20/14 : specially adapted for billing systems
• CPC Class Codes: G06Q 20/22 : Payment schemes or models
• CPC Class Codes: G06Q 20/308 : using the Internet of Things
• CPC Class Codes: G06Q 20/321 : using wearable devices
• CPC Class Codes: G06Q 20/325 : using wireless networks
• CPC Class Codes: G06Q 20/40 : Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/0267 : Wireless devices
• CPC Class Codes: G06Q 30/0269 : based on user profile or attribute
• CPC Class Codes: G08B 21/0261 : System arrangements wherein the object is to detect trespassing over a fixed physical boundary, e.g. the end of a garden
• CPC Class Codes: G08B 21/0269 : System arrangements wherein the object is to detect the exact location of child or item using a navigation satellite system, e.g. GPS
• CPC Class Codes: G16H 10/60 : for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 10/65 : stored on portable record carriers, e.g. on smartcards, RFID tags or CD
• CPC Class Codes: G16H 40/63 : for local operation
• CPC Class Codes: G16H 40/67 : for remote operation
• CPC Class Codes: G16H 80/00 : ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
• CPC Class Codes: H04B 1/3822 : specially adapted for use in vehicles H04B1/3827 takes precedence
• CPC Class Codes: H04H 20/61 : for local area broadcast, e.g. instore broadcast
• CPC Class Codes: H04H 20/71 : Wireless systems
• CPC Class Codes: H04L 41/026 : using e-messaging for transporting management information, e.g. email, instant messaging or chat
• CPC Class Codes: H04L 41/0813 : characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/0823 : characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for optimising operational conditions of wireless networks H04W24/02
• CPC Class Codes: H04L 43/10 : Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 45/22 : Alternate routing
• CPC Class Codes: H04L 65/403 : Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 67/01 : Protocols
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/12 : specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/303 : Terminal profiles
• CPC Class Codes: H04L 67/52 : specially adapted for the location of the user terminal
• CPC Class Codes: H04W 12/06 : Authentication
• CPC Class Codes: H04W 12/08 : Access security
• CPC Class Codes: H04W 24/10 : Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/023 : using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/025 : using location based information parameters
• CPC Class Codes: H04W 4/029 : Location-based management or tracking services
• CPC Class Codes: H04W 4/38 : for collecting sensor information
• CPC Class Codes: H04W 4/60 : Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
• CPC Class Codes: H04W 4/80 : Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 52/0212 : managed by the network, e.g. network or access point is master and terminal is slave
• CPC Class Codes: H04W 52/04 : TPC
• CPC Class Codes: H04W 64/00 : Locating users or terminals or network equipment for network management purposes, e.g. mobility management
• CPC Class Codes: H04W 64/003 : locating network equipment
• CPC Class Codes: H04W 64/006 : with additional information processing, e.g. for direction or speed determination
• CPC Class Codes: H04W 76/10 : Connection setup
• CPC Class Codes: H04W 8/18 : Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 8/24 : Transfer of terminal data
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Methods and systems are described for monitoring an activity of a person using a hierarchical node network having at least an ID node, a master node, and a server. The ID node is associated with a person, can monitor the person'"'"'s activity, can communicate directly with the master node but is unable to directly communicate with the server. The master node can directly communicate with the server and separately communicate with the ID node. The master node associates with the ID node upon detecting a signal broadcast from the ID node. The server determines a location of the ID node. The ID node detects an actionable event related to the person'"'"'s activity based upon the ID node location, and transmits a message to the master node reporting the actionable event. The master node notifies the server about the event. The server initiates a responsive action based upon the notification.

Claims

1. A method for monitoring an activity of a person using a hierarchical node network having at least an ID node, a master node, and a server, the method comprising:

associating, by the master node, the master node and the ID node when the master node detects a signal broadcast from the ID node, wherein the ID node is associated with a person and operative to monitor the activity of the person and to communicate directly with the master node but is unable to directly communicate with the server, and wherein the master node is operative to directly communicate with the server and separately communicate with the ID node;

determining, by the server, a location of the ID node;

detecting, by the ID node, an actionable event related to the activity of the person based upon the location of the ID node;

transmitting, by the ID node to the master node, a message reporting the actionable event;

notifying the server by the master node about the actionable event; and

initiating, by the server, a responsive action based upon the notification.

2. The method of claim 1, wherein the associating step further comprises establishing a passive association between the master node and the ID node without requiring without requiring a prior authority granted by the server.

3. The method of claim 1, wherein the associating step further comprises establishing an active association between the master node and the ID node, the active association reflecting an authorized connection between the master node and the ID node based upon an authority granted by the server.

4. The method of claim 3, wherein the authorized connection between the master node and the ID node is preauthorized by the server to avoid the need for the master node to request the authority from the server after detecting the signal broadcast from the ID node.

5. The method of claim 1, wherein the step of detecting further comprises detecting, by the ID node, a movement status related to the activity of the person based upon the location of the ID node, the movement status being the actionable event.

6. The method of claim 5, wherein the person is a medical patient.

7. The method of claim 6, wherein the medical patient is located in a healthcare facility and wherein the ID node is integrated into a healthcare facility identification.

8. The method of claim 7, wherein the movement status indicates the medical patient has left the healthcare facility based upon the location of the ID node.

9. The method of claim 7, wherein the movement status indicates the medical patient has entered a part of the healthcare facility based upon the location of the ID node, the part of the healthcare facility being a location where the medical patient is not anticipated to be within the healthcare facility.

10. The method of claim 6, wherein the step of initiating the responsive action further comprises notifying, by the server, a user access device associated with a relative of the medical patient.

11. The method of claim 7, wherein the step of initiating the responsive action further comprises notifying, by the server, a user access device associated with a healthcare provider affiliated with the healthcare facility.

12. The method of claim 7, wherein the step of initiating the responsive action further comprises:

tracking, by the server, the movements of the medical patient to determine a pattern of movement;

correlating the determined pattern of movement to a recorded change in patient behavior; and

notifying, by the server, a user access device associated with a healthcare provider affiliated with the healthcare facility, the notification indicating the relationship between the determined pattern of movement and the recorded change in patient behavior.

13. The method of claim 1, wherein the person is a medical patient;

wherein the ID node comprises a mobile sensor node associated with the person, the mobile sensor node being operative to sense a quantifiable health characteristic related to the health of the medical patient; and

wherein the step of detecting the actionable event further comprises;

sensing the quantifiable health characteristic using the mobile sensor node, and

detecting the actionable event when the sensed quantifiable health characteristic meets a predetermined condition.

14. The method of claim 1, wherein the person is a medical patient located at a residence.

15. The method of claim 14, wherein the movement status indicates the medical patient has left the residence based upon the location of the ID node.

16. The method of claim 14, wherein the movement status indicates the medical patient is not moving.

17. The method of claim 14, wherein the movement status indicates the medical patient is moving with a pattern of movement indicative of a medical condition.

18. The method of claim 14, wherein the step of initiating the responsive action further comprises notifying, by the server, a user access device associated with a relative of the medical patient.

19. The method of claim 14, wherein the step of initiating the responsive action further comprises notifying, by the server, a user access device associated with a healthcare provider.

20. The method of claim 1, wherein the step of determining the location of the ID node further comprises tracking the location of the ID node over time and refining the location of the ID node based upon context data related to an operating environment of the person and the ID node.

21. A system within a hierarchical node network for monitoring an activity of a person, the system comprising:

a server;

a master node operative to directly communicate with the server over a longer range communication path; and

an ID node associated with the person and operative to monitor the activity of the person, the ID node being further operative to wirelessly communicate directly with the master node over a shorter range communication path but is unable to directly communicate with the server;

wherein ID node is operative to

detect an actionable event related to the activity of the person, and

transmit a message to the master node reporting the actionable event;

wherein the master node is operative to

associate with the ID node upon detection of a signal broadcast from the ID node, and

notify the server about the actionable event reported in the message received from the ID node; and

wherein the server is operative to;

determine a location of the ID node,

receive the notification from the master node regarding the actionable event, and

initiate a responsive action based upon the notification.

22. The system of claim 21, wherein the master node is further operative to associate by being operative to establish a passive association between the master node and the ID node without requiring without requiring a prior authority granted by the server.

23. The system of claim 21, wherein the master node is further operative to associate by being operative to establish an active association between the master node and the ID node, the active association reflecting an authorized connection between the master node and the ID node based upon an authority granted by the server.

24. The system of claim 23, wherein the authorized connection between the master node and the ID node is preauthorized by the server to avoid the need for the master node to request the authority from the server after detecting the signal broadcast from the ID node.

25. The system of claim 21, wherein the ID node is further operative to detect the actionable event by being operative to detect a movement status related to the activity of the person based upon the location of the ID node, the movement status being the actionable event.

26. The system of claim 25, wherein the person is a medical patient.

27. The system of claim 26, wherein the medical patient is located in a healthcare facility and wherein the ID node is integrated into a healthcare facility identification.

28. The system of claim 27, wherein the movement status indicates the medical patient has left the healthcare facility based upon the location of the ID node.

29. The system of claim 27, wherein the movement status indicates the medical patient has entered a part of the healthcare facility based upon the location of the ID node, the part of the healthcare facility being a location where the medical patient is not anticipated to be within the healthcare facility.

30. The system of claim 26, wherein the server is further operative to initiate the responsive action by being operative to notify a user access device associated with a relative of the medical patient.

31. The system of claim 27, wherein the server is further operative to initiate the responsive action by being operative to notify a user access device associated with a healthcare provider affiliated with the healthcare facility.

32. The system of claim 27, wherein the server is further operative to initiate the responsive action by being operative to:

track the movements of the medical patient to determine a pattern of movement;

correlate the determined pattern of movement to a recorded change in patient behavior; and

notify a user access device associated with a healthcare provider affiliated with the healthcare facility, the notification indicating the relationship between the determined pattern of movement and the recorded change in patient behavior.

33. The system of claim 21, wherein the person is a medical patient;

wherein the ID node further comprises a sensor operative to sense a quantifiable health characteristic related to the health of the medical patient; and

wherein the ID node is further operative to detect the actionable event by being operative to;

sense the quantifiable health characteristic using the mobile sensor node, and

detect the actionable event when the sensed quantifiable health characteristic meets a predetermined condition.

34. The system of claim 21, wherein the person is a medical patient located at a residence.

35. The system of claim 25, wherein the movement status indicates the medical patient has left the residence based upon the location of the ID node.

36. The system of claim 25, wherein the movement status indicates the medical patient is not moving.

37. The system of claim 25, wherein the movement status indicates the medical patient is moving with a pattern of movement indicative of a medical condition.

38. The system of claim 25, wherein the server is further operative to initiate the responsive action by being operative to notify a user access device associated with a relative of the medical patient.

39. The system of claim 25, wherein the server is further operative to initiate the responsive action by being operative to notify a user access device associated with a healthcare provider.

40. The system of claim 21, wherein the server is further operative to determine the location of the ID node by being operative to:

track the location of the ID node over time; and

refine the location of the ID node based upon context data related to an operating environment of the person and the ID node.