System, method, and article of manufacture for a network media channel

• US 20070168419A1
• Filed: 12/19/2005
• Published: 07/19/2007
• Est. Priority Date: 12/19/2005
• Status: Abandoned Application

• Current Assignee: Eduardo Sciammarella
• Original Assignee: Eduardo Sciammarella
• Inventors: Sciammarella, Eduardo
• Application Number:
  US11/312,291
• Publication Number:
  US 20070168419A1
• Time in Patent Office: Days
• US Class Current: 709/204
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests

Abstract

This invention discloses a network media channel that can be used by the subscribers of the channel to share media files based on ad-hoc specifications. Temporal, spatial, channel identity and mask components, or any combination thereof, are among the specifications that subscribers can use to create ad-hoc specifications. A transmitting subscriber creates a media file and a kernel containing the ad-hoc specifications, wherein the media file is stored according to the first kernel. Access to the media file is according to the first kernel. A receiving subscriber can in turn create a second kernel to introduce additional refinements to the ad-hoc specification and be notified according to the first and second kernel. The receiving subscriber may retrieve the media file upon reception of the notice.

Claims

1. A method for providing a network media channel, comprising:

(a) creating a media file utilizing a device, said device coupled with a server via a network;

(b) creating a first kernel;

(c) transmitting said media file and first kernel to said network, via the device;

(d) receiving said media file and first kernel from said network, via the server;

(e) storing said media file and first kernel in a repository in said server; and

(f) allowing access to said repository across said network according to the first kernel.

2. The method of claim 1, wherein creating a media file comprises:

(i) inputting at least one of a text component, an image component, an audio component, and a video component; and

(ii) storing at least one of the text component, the image component, the audio component, and the video component, in the media file.

3. The method of claim 1, wherein said media file comprises at least one of a text component, an image component, an audio component, and a video component.

4. The method of claim 1, wherein said device is a client.

5. The method of claim 4, wherein said client comprises at least one of a mobile phone, a personal digital assistant, a personal computer, and a laptop computer.

6. The method of claim 1, wherein said network comprises a presence-based network.

7. The method of claim 1, wherein creating a first kernel comprises:

(i) inputting at least one of a temporal data, a spatial data, a channel identity data, and a mask data; and

(ii) storing at least one of the temporal data, the spatial data, the channel identity data, and the mask data in the first kernel.

8. The method of claim 1, wherein said first kernel comprises at least one of a temporal component, a spatial component, a channel identity component, and a mask component.

9. The method of claim 8, wherein said temporal component comprises at least one of a local time and a temporal period.

10. The method of claim 8, wherein said spatial component comprises at least one of a geographic location and a spatial boundary.

11. The method of claim 8, wherein said channel identity component comprises at least one of a LifeChannel identity, a MediaLife identity, a NaviLife identity, and a LocalLife identity.

12. The method of claim 11, wherein said LifeChannel identity identifies a user-generated content.

13. The method of claim 11, wherein said MediaLife identity identifies an entertainment and information content.

14. The method of claim 11, wherein said NaviLife identity identifies a scheduling and event content.

15. The method of claim 11, wherein said LocalLife identity identifies a location content.

16. The method of claim 8, wherein said mask component comprises at least one of a keyword and an identification list.

17. The method of claim 16, wherein said identification list comprises at least one of a name, a gender, an age, and a physical attribute.

18. The method of claim 1, wherein the steps (c) and (d) occur via at least one of a wired and a wireless connection.

19. The method of claim 1, wherein said repository comprises at least one of a LifeChannel component, a MediaLife component, a NaviLife component, and a LocalLife component.

20. The method of claim 1, wherein said notice comprises at least one of a temporal component, a spatial component, a channel identity component, and a mask component.

21. The method of claim 1, wherein said access is allowed according to at least one of a temporal component, a spatial component, a channel identity component, and a mask component.

22. The method of claim 1, further comprising:

(a) modifying the first kernel;

(b) transmitting said modified kernel to said server; and

(c) replacing said first kernel with said modified kernel.

23. The method of claim 22, further comprising modifying a received media file according to said modified first kernel.

24. The method of claim 1, further comprising:

(a) creating a second kernel;

(b) transmitting said second kernel to said server;

(c) storing said second kernel in the repository in said server;

(d) transmitting a notice to said network according to the first and second kernel, via the server;

(e) receiving the notice; and

(f) receiving said media file from said repository in said server according to the second kernel.

25. The method of claim 24, wherein said second kernel comprises at least one of a temporal component, a spatial component, a channel identity component, and a mask component.

26. The method of claim 24, further comprising:

(a) modifying the second kernel;

(b) transmitting said modified kernel to said server; and

(c) replacing said second kernel with said modified kernel.

27. A computer program embodied on a computer readable medium for providing a network media channel, comprising:

(a) a code segment that creates a media file utilizing a device, said device coupled with a server via a network;

(b) a code segment that creates a first kernel;

(c) a code segment that transmits said media file and first kernel to said network, via the device;

(d) a code segment that receives said media file and first kernel from said network, via the server;

(e) a code segment that stores said media file and first kernel in a repository in said server; and

(f) a code segment that allows access to said repository across said network according to the first kernel.

28. The computer program of claim 27, wherein the code segment that creates a media file comprises:

(i) a code segment that inputs at least one of a text component, an image component, an audio component, and a video component; and

(ii) a code segment that stores at least one of the text component, the image component, the audio component, and the video component, in the media file.

29. The computer program of claim 27, wherein said media file comprises at least one of a text component, an image component, an audio component, and a video component.

30. The computer program of claim 27, wherein said device is a client.

31. The computer program of claim 30, wherein said client comprises at least one of a mobile phone, a personal digital assistant, a personal computer, and a laptop computer.

32. The computer program of claim 27, wherein said network comprises a presence-based network.

33. The computer program of claim 27, wherein the code segment that creates a first kernel comprises:

(i) a code segment that inputs at least one of a temporal data, a spatial data, a channel identity data, and a mask data; and

(ii) a code segment that stores at least one of the temporal data, the spatial data, the channel identity data, and the mask data in the first kernel.

34. The computer program of claim 27, wherein said first kernel comprises at least one of a temporal component, a spatial component, a channel identity component, and a mask component.

35. The computer program of claim 34, wherein said temporal component comprises at least one of a local time and a temporal period.

36. The computer program of claim 34, wherein said spatial component comprises at least one of a geographic location and a spatial boundary.

37. The computer program of claim 34, wherein said channel identity component comprises at least one of a LifeChannel identity, a MediaLife identity, a NaviLife identity, and a LocalLife identity.

38. The computer program of claim 37, wherein said LifeChannel identity identifies a user-generated content.

39. The computer program of claim 37, wherein said MediaLife identity identifies an entertainment and information content.

40. The computer program of claim 37, wherein said NaviLife identity identifies a scheduling and event content.

41. The computer program of claim 37, wherein said LocalLife identity identifies a location content.

42. The computer program of claim 34, wherein said mask component comprises at least one of a keyword and an identification list.

43. The computer program of claim 42, wherein said identification list comprises at least one of a name, a gender, an age, and a physical attribute.

44. The computer program of claim 27, wherein the steps (c) and (d) occur via at least one of a wired and a wireless connection.

45. The computer program of claim 27, wherein said repository comprises at least one of a LifeChannel component, a MediaLife component, a NaviLife component, and a LocalLife component.

46. The computer program of claim 27, wherein said notice comprises at least one of a temporal component, a spatial component, a channel identity component, and a mask component.

47. The computer program of claim 27, wherein said access is allowed according to at least one of a temporal component, a spatial component, a channel identity component, and a mask component.

48. The computer program of claim 27, further comprising:

(a) a code segment that modifies the first kernel;

(b) a code segment that transmits said modified kernel to said server; and

(c) a code segment that replaces said first kernel with said modified kernel.

49. The computer program of claim 48, further comprising a code segment that modifies said received media file according to said modified first kernel.

50. The computer program of claim 27, further comprising:

(a) a code segment that creates a second kernel;

(b) a code segment that transmits said second kernel to said server;

(c) a code segment that stores said second kernel in the repository in said server;

(d) a code segment that transmits a notice to said network according to the first and second kernel, via the server; and

(e) a code segment that receives the notice; and

(f) a code segment that receives said media file from said repository in said server according to the second kernel.

51. The computer program of claim 50, wherein said second kernel comprises at least one of a temporal component, a spatial component, a channel identity component, and a mask component.

52. The computer program of claim 50, further comprising:

(a) a code segment that modifies the second kernel;

(b) a code segment that transmits said modified kernel to said server; and

(c) a code segment that replaces said second kernel with said modified kernel.

53. A system for providing a network media channel, comprising:

(a) logic that creates a media file utilizing a device, said device coupled with a server via a network;

(b) logic that creates a first kernel;

(c) logic that transmits said media file and first kernel to said network, via the device;

(d) logic that receives said media file and first kernel from said network, via the server;

(e) logic that stores said media file and first kernel in a repository in said server; and

(f) logic that allows access to said repository across said network according to the first kernel.

54. The system of claim 53, wherein the logic that creates a media file comprises:

(i) logic that inputs at least one of a text component, an image component, an audio component, and a video component; and

(ii) logic that stores at least one of the text component, the image component, the audio component, and the video component, in the media file.

55. The system of claim 53, wherein said media file comprises at least one of a text component, an image component, an audio component, and a video component.

56. The system of claim 53, wherein said device is a client.

57. The system of claim 56, wherein said client comprises at least one of a mobile phone, a personal digital assistant, a personal computer, and a laptop computer.

58. The system of claim 53, wherein said network comprises a presence-based network.

59. The system of claim 53, wherein the logic that creates a first kernel comprises:

(i) logic that inputs at least one of a temporal data, a spatial data, a channel identity data, and a mask data; and

(ii) logic that stores at least one of the temporal data, the spatial data, the channel identity data, and the mask data in the first kernel.

60. The system of claim 53, wherein said first kernel comprises at least one of a temporal component, a spatial component, a channel identity component, and a mask component.

61. The system of claim 60, wherein said temporal component comprises at least one of a local time and a temporal period.

62. The system of claim 60, wherein said spatial component comprises at least one of a geographic location and a spatial boundary.

63. The system of claim 60, wherein said channel identity component comprises at least one of a LifeChannel identity, a MediaLife identity, a NaviLife identity, and a LocalLife identity.

64. The system of claim 63, wherein said LifeChannel identity identifies a user-generated content.

65. The system of claim 63, wherein said MediaLife identity identifies an entertainment and information content.

66. The system of claim 63, wherein said NaviLife identity identifies a scheduling and event content.

67. The system of claim 63, wherein said LocalLife identity identifies a location content.

68. The system of claim 60, wherein said mask component comprises at least one of a keyword and an identification list.

69. The system of claim 68, wherein said identification list comprises at least one of a name, a gender, an age, and a physical attribute.

70. The system of claim 53, wherein the steps (c) and (d) occur via at least one of a wired and a wireless connection.

71. The system of claim 53, wherein said repository comprises at least one of a LifeChannel component, a MediaLife component, a NaviLife component, and a LocalLife component.

72. The system of claim 53, wherein said notice comprises at least one of a temporal component, a spatial component, a channel identity component, and a mask component.

73. The system of claim 53, wherein said access is allowed according to at least one of a temporal component, a spatial component, a channel identity component, and a mask component.

74. The system of claim 53, further comprising:

(a) logic that modifies the first kernel;

(b) logic that transmits said modified kernel to said server; and

(c) logic that replaces said first kernel with said modified kernel.

75. The system of claim 74, further comprising modifying said received media file according to said modified first kernel.

76. The system of claim 53, further comprising:

(a) logic that creates a second kernel;

(b) logic that transmits said second kernel to said server;

(c) logic that stores said second kernel in the repository in said server;

(d) logic that transmits a notice to said network according to the first and second kernel;

(e) logic that receives the notice; and

(f) logic that receives said media file from said repository in said server according to the second kernel.

77. The system of claim 76, wherein said second kernel comprises at least one of a temporal component, a spatial component, a channel identity component, and a mask component.

78. The computer program of claim 76, further comprising:

(a) a code segment that modifies the second kernel;

(b) a code segment that transmits said modified kernel to said server; and

(c) a code segment that replaces said second kernel with said modified kernel.

79. A system for providing a network media channel, comprising:

(a) a first device capable of creating a media file and a first kernel and transmitting said media file and first kernel to a network;

(b) a server coupled with the device via the network and capable of receiving the media file and first kernel from the network, storing the media file in a repository according to the first kernel, and allowing access to the repository according to the first kernel

(c) a second device coupled with the server via the network and capable of creating a second kernel, transmitting said second kernel to said server, wherein the server stores said second kernel in the repository in said server and transmits a notice to the network according to the first and second kernel, receiving the notice, and receiving the media file from the repository in the server according to the second kernel.