Distributed file system consistency mechanism extension for enabling internet video broadcasting

• US 9,449,017 B2
• Filed: 08/05/2013
• Issued: 09/20/2016
• Est. Priority Date: 09/09/2005
• Status: Active Grant

• Current Assignee: William M. Pitts
• Original Assignee: William M. Pitts
• Inventors: Pitts, William M
• Primary Examiner(s): Hasan, Syed
• Application Number:
  US13/959,508
• Publication Number:
  US 20130326572A1
• Time in Patent Office: 1,142 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/148 File search processing
• CPC Class Codes: G06F 16/156 Query results presentation
• CPC Class Codes: G06F 16/1734 Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/183 Provision of network file services by network file servers, e.g. by using NFS, CIFS network file access protocols H04L67/1097
• CPC Class Codes: G06F 16/24578 using ranking
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: H04H 20/82 using signals not modulated onto a carrier
• CPC Class Codes: H04N 21/222 Secondary servers, e.g. proxy server, cable television Head-end provisioning of proxy services in data packet switching networks H04L67/56
• CPC Class Codes: H04N 21/6125 involving transmission via Internet transmission by internet of broadcast information H04H60/82
• CPC Class Codes: H04N 21/654 Transmission by server directed to the client
• CPC Class Codes: H04N 21/84 Generation or processing of descriptive data, e.g. content descriptors systems specially adapted for using meta-information in broadcast systems H04H60/73

Abstract

The consistency callback mechanisms employed by local file systems such as NTFS and distributed file systems such as DDS, NFS and CIFS are extended to provide a shared memory foundation for efficiently broadcasting real-time high definition video from a source object to large numbers of viewers via the Internet. Distributed applications such as video viewing client applications establish connections to a common distributed file system object, and then each application registers with the underlying distributed file system to receive notifications whenever the video source modifies the source object. The data required to update images maintained by viewing clients is included in notification messages. The distributed file system employs a network of proxy cache nodes. Proxy cache nodes receive notification messages (complete with image update data) and update their cached images of the source object and then retransmit the notification messages towards the viewing clients using IP multicast techniques. In this manner, the distributed file system'"'"'s consistency mechanism efficiently employs network resources to enable the real-time distribution of video content streams.

Claims

1. A method of communicating various file access read and write requests performed on a file located at an origin file server site within a distributed file system that includes multiple caching node sites to a plurality of applications running at different sites in the distributed file system, comprising:

an origin file server site within a distributed file system;

receiving from each of a plurality of applications running at different sites in the distributed file system;

a request for notification whenever a file access request received at any site in the distributed file system triggers a notification, the request for notification containing;

a file descriptor identifying the file for which the application requests notification of file access requests; and

,

a specification of the type of file access activity required to trigger a notification;

for the file identified by the file descriptor;

creating a notification attribute as an extended attribute for the file;

storing the request for notification within the notification attribute; and

employing a consistency mechanism of the distributed file system to ensure all images of the notification attribute at all sites currently accessing the file are the same; and

when any distributed file system site receives a request to access the file;

referencing each of the notification attributes to determine which of the different sites in the distributed file system at which the file is currently being accessed have requested a notification message; and

delivering a notification message to each of the different sites in the distributed file system that have requested a notification message.

2. The method of claim 1 wherein registering a request for notification further comprises an IOCTL system call function having arguments which include the file descriptor.

3. The method of claim 2, wherein the IOCTL system call function returns when a notification has been triggered.

4. The method of claim 2, wherein the file descriptor includes a notification routine address.

5. The method of claim 4, wherein the IOCTL system call function returns immediately and the notification routine identified by the notification routine address is called when a notification is received.

6. The method of claim 2, wherein the IOCTL system call function includes a description of the type of file access required to trigger a notification.

7. The method of claim 1 further comprising:

discarding the notification attribute of the file when all of the applications that have registered for that specific notification have terminated their connections to the identified file.

8. The method of claim 1 wherein delivering a notification message to each of the different sites in the distributed file system that have requested a notification message further comprises employing IP multicast to send the notification message to all of the sites.

9. The method of claim 1 wherein the request for notification includes at least one of:

an identification of the event which will trigger the request for notification;

the event range of the access which will trigger the request for notification;

the update range of the access which will trigger the request for notification;

or

the notification routine address to be called when asynchronous notifications are being employed.

10. The method of claim 1 wherein the identification of the event includes at least one of:

an identification of the event which triggered the notification;

the event range of the access which triggered the notification;

the update range of the access which triggered the notification;

or

the notification routine address to be called when asynchronous notifications are being employed.

11. The method of claim 1 wherein the notification message includes at least one of:

an identification of the event which triggered the notification message;

the event range of the access which triggered the notification message;

the update range of the access which triggered the notification message;

or

a site identifier which Identifies the site that performed the file access which triggered the notification message.

12. The method of claim 1 further comprising:

the file access request that triggered a notification is not processed by the distributed file system until all sites receiving the notification have acknowledged receipt of the notification.

13. The method of claim 1, wherein creating a notification attribute as an extended attribute for the file includes:

the notification attributes are cached and valid wherever the regular attributes are cached and valid.

14. The method of claim 1, wherein creating a notification attribute as an extended attribute for the file includes:

the notification attributes are under the same consistency controls as the file'"'"'s data and metadata.

15. The method of claim 1, wherein creating a notification attribute as an extended attribute for the file includes:

the notification attributes are present and valid and may be referenced at some point in the processing of every file access request targeting the associated file or directory.

16. The method of claim 1, wherein creating a notification attribute as an extended attribute for the file includes:

the notification attributes will persist across a restart of a failed origin file server or intermediate caching node.

17. The method of claim 1, wherein creating a notification attribute as an extended attribute for the file includes:

the notification attribute will not persist beyond the last connected application or process terminating its connection to the file.