System and method for blog functionality

• US 20060101035A1
• Filed: 11/11/2004
• Published: 05/11/2006
• Est. Priority Date: 11/11/2004
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Turcanu, Calin, Lindholm, Christian B., Mustakallio, Minna M.
• Application Number:
  US10/988,274
• Publication Number:
  US 20060101035A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

Systems and methods applicable, for instance, in blog functionality. For example, a blog entry may be created that exists both in a media diary and as part of a blog. As another example, notifications regarding blogs may be received. As yet another example, a contacts card may convey details of one or more blogs.

Claims

1. A method, comprising:

dispatching a blog entry to a blog server; and

including the blog entry as a blog entry media item in a media diary,

wherein the blog server employs the dispatched blog entry as a part of a blog, and

wherein the media diary presents, in an automatically organized timeline, the blog entry media item.

2. The method of claim 1, wherein there is coordination between the blog entry media item and the part of the blog.

3. The method of claim 1, wherein the media diary presents, in the automatically organized timeline, further media items.

4. The method of claim 1, wherein the media diary presents a plurality of types of media items.

5. The method of claim 1, further comprising receiving selection of one or more media items from the media diary to include in the blog entry.

6. The method of claim 1, further comprising receiving text to include in the blog entry.

7. The method of claim 1, wherein the media diary presents media items created at the node.

8. The method of claim 1, wherein the media diary presents media items captured at the node.

9. The method of claim 1, wherein the media diary presents media items received at the node.

10. The method of claim 4, wherein the plurality of types includes images.

11. The method of claim 4, wherein the plurality of types includes movies.

12. The method of claim 4, wherein the plurality of types includes sounds.

13. The method of claim 4, wherein the plurality of types includes messages.

14. The method of claim 4, wherein the plurality of types includes blog entries.

15. The method of claim 1, wherein the blog entry media item is updated to include replies to the part of the blog.

16. The method of claim 1, wherein the blog entry media item is updated to include number of accesses of the part of the blog.

17. The method of claim 1, wherein the blog entry media item is updated to include times of accesses of the part of the blog.

18. The method of claim 1, wherein the blog entry media item is updated to include names of users accessing the part of the blog.

19. The method of claim 1, wherein the part of the blog is updated to include changes made to the blog entry media item.

20. The method of claim 1, wherein a blog entry editor is provided.

21. The method of claim 1, further comprising associating metadata with the blog entry.

22. The method of claim 5, further comprising associating, with the selected media items, metadata associated with the blog entry.

23. The method of claim 5, further comprising associating, with the blog entry, metadata associated with the selected media items.

24. The method of claim 5, wherein the selected media items are identified by a user via a blog entry editor.

25. The method of claim 5, wherein the selected media items are placed into a blog folder by a user.

26. The method of claim 1, wherein blog entries of a blog of a user not owning the media diary are stored in the media diary.

27. The method of claim 1, wherein blog entries of a blog of a user not owning the media diary are stored in a blog folder.

28. The method of claim 26, further comprising offering one or more links to the blog.

29. The method of claim 27, further comprising offering one or more links to the blog.

30. The method of claim 1, wherein the blog entry is converted into a format appropriate for a blog.

31. The method of claim 1, wherein one or more templates are provided by a blog service.

32. The method of claim 1, wherein atom is employed.

33. The method of claim 1, wherein really simple syndication is employed.

34. The method of claim 1, further comprising suggesting one or more media items from the media diary for inclusion in the blog entry.

35. The method of claim 34, further comprising comparing blog metadata with metadata associated with one or more media items from the media diary.

36. The method of claim 34, further comprising comparing blog metadata with metadata associated with one or more new media items from the media diary.

37. A method, comprising:

monitoring for changes to a blog; and

providing, to a node, presence data,

wherein the presence data indicates communication availability, and

wherein the presence data indicates change to the blog.

38. The method of claim 37, wherein monitoring for changes to a blog of a user is performed.

39. The method of claim 37, wherein monitoring for changes to a blog of a third party is performed.

40. The method of claim 37, wherein the blog corresponds to a user, and wherein access to the blog is provided via a contacts card corresponding to the user.

41. The method of claim 37, wherein the blog corresponds to a user, and wherein access to the blog is provided via a buddy list entry corresponding to the user.

42. The method of claim 37, wherein the presence data is provided upon a change being made to the blog.

43. The method of claim 37, wherein the presence data is provided periodically.

44. The method of claim 37, wherein the node provides indication in a contacts user interface in the case where a change is made to the blog.

45. The method of claim 37, wherein, while an interface of the node is in an inactive state, the node provides on-screen display in the case where a change is made to the blog.

46. The method of claim 37, wherein atom is employed in monitoring for changes to the blog.

47. The method of claim 37, wherein really simple syndication is employed in monitoring for changes to the blog.

48. The method of claim 37, wherein the blog is accessed in monitoring for changes to the blog

49. The method of claim 37, wherein access to a new entry in the blog is provided.

50. The method of claim 37, wherein the information regarding a new entry in the blog is provided.

51. The method of claim 37, wherein access to a new blog entry reply is provided.

52. The method of claim 37, wherein the information regarding a new blog entry reply is provided.

53. The method of claim 37, wherein the presence data further indicates one or more usage information values for the blog.

54. The method of claim 53, wherein the usage information values comprise one or more numbers of accesses to the blog.

55. The method of claim 53, wherein the usage information values comprise one or more names of users accessing the blog.

56. The method of claim 53, wherein the usage information values comprise one or more times of accesses to the blog.

57. The method of claim 53, wherein the provided presence data is stored in a media diary of the node.

58. The method of claim 53, wherein, while an interface of the node is in an inactive state, the node provides on-screen display regarding one or more usage information values for the blog.

59. A system, comprising:

a memory having program code stored therein; and

a processor disposed in communication with the memory for carrying out instructions in accordance with the stored program code;

wherein the program code, when executed by the processor, causes the processor to perform;

dispatching a blog entry to a blog server; and

including the blog entry as a blog entry media item in a media diary,

wherein the blog server employs the dispatched blog entry as a part of a blog, and

wherein the media diary presents, in an automatically organized timeline, the blog entry media item.

60. The system of claim 59, wherein there is coordination between the blog entry media item and the part of the blog.

61. The system of claim 59, wherein the media diary presents, in the automatically organized timeline, further media items.

62. The system of claim 59, wherein the media diary presents a plurality of types of media items.

63. The system of claim 59, wherein the processor further performs receiving selection of one or more media items from the media diary to include in the blog entry.

64. The system of claim 59, wherein the processor further performs receiving text to include in the blog entry.

65. The system of claim 59, wherein the media diary presents media items created at the node.

66. The system of claim 59, wherein the media diary presents media items captured at the node.

67. The system of claim 59, wherein the media diary presents media items received at the node.

68. The system of claim 62, wherein the plurality of types includes images.

69. The system of claim 62, wherein the plurality of types includes movies.

70. The system of claim 62, wherein the plurality of types includes sounds.

71. The system of claim 62, wherein the plurality of types includes messages.

72. The system of claim 62, wherein the plurality of types includes blog entries.

73. The system of claim 59, wherein the blog entry media item is updated to include replies to the part of the blog.

74. The system of claim 59, wherein the blog entry media item is updated to include number of accesses of the part of the blog.

75. The system of claim 59, wherein the blog entry media item is updated to include times of accesses of the part of the blog.

76. The system of claim 59, wherein the blog entry media item is updated to include names of users accessing the part of the blog.

77. The system of claim 59, wherein the part of the blog is updated to include changes made to the blog entry media item.

78. The system of claim 59, wherein a blog entry editor is provided.

79. The system of claim 59, wherein the processor further performs associating metadata with the blog entry.

80. The system of claim 63, wherein the processor further performs associating, with the selected media items, metadata associated with the blog entry.

81. The system of claim 63, wherein the processor further performs associating, with the blog entry, metadata associated with the selected media items.

82. The system of claim 63, wherein the selected media items are identified by a user via a blog entry editor.

83. The system of claim 63, wherein the selected media items are placed into a blog folder by a user.

84. The system of claim 59, wherein blog entries of a blog of a user not owning the media diary are stored in the media diary.

85. The system of claim 59, wherein blog entries of a blog of a user not owning the media diary are stored in a blog folder.

86. The system of claim 84, wherein the processor further performs offering one or more links to the blog.

87. The system of claim 85, wherein the processor further performs offering one or more links to the blog.

88. The system of claim 59, wherein the blog entry is converted into a format appropriate for a blog.

89. The system of claim 59, wherein one or more templates are provided by a blog service.

90. The system of claim 59, wherein atom is employed.

91. The system of claim 59, wherein really simple syndication is employed.

92. The system of claim 59, wherein the processor further performs suggesting one or more media items from the media diary for inclusion in the blog entry.

93. The system of claim 92, wherein the processor further performs comparing blog metadata with metadata associated with one or more media items from the media diary.

94. The system of claim 92, wherein the processor further performs comparing blog metadata with metadata associated with one or more new media items from the media diary.

95. A system, comprising:

a memory having program code stored therein; and

a processor disposed in communication with the memory for carrying out instructions in accordance with the stored program code;

wherein the program code, when executed by the processor, causes the processor to perform;

monitoring for changes to a blog; and

providing, to a node, presence data,

wherein the presence data indicates communication availability, and

wherein the presence data indicates change to the blog.

96. The system of claim 95, wherein monitoring for changes to a blog of a user is performed.

97. The system of claim 95, wherein monitoring for changes to a blog of a third party is performed.

98. The system of claim 95, wherein the blog corresponds to a user, and wherein access to the blog is provided via a contacts card corresponding to the user.

99. The system of claim 95, wherein the blog corresponds to a user, and wherein access to the blog is provided via a buddy list entry corresponding to the user.

100. The system of claim 95, wherein the presence data is provided upon a change being made to the blog.

101. The system of claim 95, wherein the presence data is provided periodically.

102. The system of claim 95, wherein the node provides indication in a contacts user interface in the case where a change is made to the blog.

103. The system of claim 95, wherein, while an interface of the node is in an inactive state, the node provides on-screen display in the case where a change is made to the blog.

104. The system of claim 95, wherein atom is employed in monitoring for changes to the blog.

105. The system of claim 95, wherein really simple syndication is employed in monitoring for changes to the blog.

106. The system of claim 95, wherein the blog is accessed in monitoring for changes to the blog

107. The system of claim 95, wherein access to a new entry in the blog is provided.

108. The system of claim 95, wherein the information regarding a new entry in the blog is provided.

109. The system of claim 95, wherein access to a new blog entry reply is provided.

110. The system of claim 95, wherein the information regarding a new blog entry reply is provided.

111. The system of claim 95, wherein the presence data further indicates one or more usage information values for the blog.

112. The system of claim 111, wherein the usage information values comprise one or more numbers of accesses to the blog.

113. The system of claim 111, wherein the usage information values comprise one or more names of users accessing the blog.

114. The system of claim 111, wherein the usage information values comprise one or more times of accesses to the blog.

115. The system of claim 111, wherein the provided presence data is stored in a media diary of the node.

116. The system of claim 111, wherein, while an interface of the node is in an inactive state, the node provides on-screen display regarding one or more usage information values for the blog.

117. An article of manufacture comprising a computer readable medium containing program code that when executed causes a node to perform:

dispatching a blog entry to a blog server; and

including the blog entry as a blog entry media item in a media diary,

wherein the blog server employs the dispatched blog entry as a part of a blog, and

wherein the media diary presents, in an automatically organized timeline, the blog entry media item.

118. An article of manufacture comprising a computer readable medium containing program code that when executed causes a server to perform:

monitoring for changes to a blog; and

providing, to a node, presence data,

wherein the presence data indicates communication availability, and

wherein the presence data indicates change to the blog.

119. A node, comprising:

a memory having program code stored therein;

a processor disposed in communication with the memory for carrying out instructions in accordance with the stored program code; and

a network interface disposed in communication with the processor;

wherein the program code, when executed by the processor, causes the processor to perform;

dispatching a blog entry to a blog server; and

including the blog entry as a blog entry media item in a media diary,

wherein the blog server employs the dispatched blog entry as a part of a blog, and

wherein the media diary presents, in an automatically organized timeline, the blog entry media item.

120. A server, comprising:

a memory having program code stored therein;

a processor disposed in communication with the memory for carrying out instructions in accordance with the stored program code; and

a network interface disposed in communication with the processor;

wherein the program code, when executed by the processor, causes the processor to perform;

monitoring for changes to a blog; and

providing, to a node, presence data,

wherein the presence data indicates communication availability, and

wherein the presence data indicates change to the blog.