JP5705145B2 - Intelligent system for integrated content posting - Google Patents

Description

  Embodiments of the present invention relate to posting techniques. More specifically, embodiments of the present invention relate to a standardized and simplified processing method for posting content to a website.

  Posting information on the Internet is a daily routine. Image sharing sites, blogs, and other media sites require users to log on to popular websites and post media objects individually to different websites.

  RSS (Real Simple Syndication) technology makes it easy for users to access aggregate content via the Internet. RSS provides access to data and information by giving users the option to use an RSS feed aggregator to retrieve the latest articles from various websites such as forums, blogs, news sites, photo galleries, etc. Has been improved. Utilizing the RSS feature, the user can select a website to be added by the aggregator by clicking on the RSS icon on the website.

Embodiments of the present invention will now be described by way of example and not limitation, with like reference numerals referring to like parts in the accompanying drawings.
It is a conceptual diagram of the information of one Embodiment posted via a network. It is a conceptual diagram of one Embodiment of post service. 1 is a conceptual diagram of an embodiment of a posting technology via post service. FIG. 1 is a conceptual diagram of an embodiment of a posting technique via post service and client software. FIG. 1 is a conceptual diagram of an embodiment of a posting technique via post service and broker service. FIG. 1 is a conceptual diagram of one embodiment of a post format structure. FIG. It is a conceptual diagram of one Embodiment of post-feed. FIG. 3 is a conceptual diagram of one embodiment of a postfeed list. It is a conceptual diagram of one Embodiment of a post broker service. It is a conceptual diagram of one Embodiment of the delivered post broker service. It is a key map of one embodiment of user information verification technology. 1 is a conceptual diagram of an embodiment of a technique for posting material on a website based on one user's private key stored in advance in a post broker service. 1 is a conceptual diagram of one embodiment of a technique for posting material to a website based on a post broker service private key. FIG. FIG. 2 is a conceptual diagram of an embodiment of a device that determines posting.

  In the following description, numerous specific details are set forth. However, embodiments of the invention may be practiced without these specific details. In other instances, well known circuits, structures, and techniques have not been shown in detail in order to avoid obscuring the understanding of the present disclosure.

  Posting content to various websites on the Internet can be a cumbersome task. Usually, a user posts content by logging into a website and following various instructions. With the technology described here, a standardized, low-complexity, simplified process that improves content posting to websites can be realized. In one embodiment, a user can submit content in one go rather than logging into various websites and repeatedly providing posting content.

  FIG. 1 illustrates one embodiment of posting content to the Internet via a post service. In one embodiment, handheld device 110 communicates post information to post service broker 120 over a network. In alternative embodiments, the handheld device 110 may be a palm-held device, mobile phone, computer terminal, or other type of device capable of storing and communicating information. The post service broker 120 may post the received post information to the websites 130 and 140.

  For servers that do not provide post service (eg, websites 160 and 150), the post proxy layer of the post broker service may emulate the post service. The handheld device 110 may access the post service directly or post it via the post broker service. A website may provide a number of post services. In alternative embodiments, the posted content may be submitted via various devices with different transfer protocols.

  Reference to a handheld device as the source of data to be posted simplifies the description and mentions only one embodiment. The data to be posted may be provided by any type of electronic device that can generate, transmit, or process data to be posted to multiple websites.

  FIG. 2 illustrates one embodiment of post service. In one embodiment, original data content 210 is sent to post service 220 based on post feed list 215. The raw data content 210 may be in the form of a file, data structure, media file, or other type of data. The post feed list 215 may provide one or more post service identifiers (eg, addresses) that may be used to post the original data content 210. The post feed list 215 may be used by client software on the source device or post broker service. In general, one post service may be provided by one website. The content 210 may then be posted to a website that provides a post service or a website that has a corresponding post proxy in the broker service. Content 210 may be stored on device 110 of FIG. 1 or other storage media device.

  FIG. 3 illustrates one embodiment of a technique for posting information on a website via a post service. In one embodiment, the original content 320 is stored on the device 310. Device 310 may be a mobile phone, a notebook, a portable handheld device, or a hardwired computer terminal. Original content 320 may consist of image files, text files, video files, media files, and other computer media files. In one embodiment, the original content 320 may be converted to a post format 330. The post format 330 may be a type of the post format 610 of FIG.

  The post service 340 may receive the post format 330 via the network. Post 340 may be described as format 700 in FIG. The post service 340 may post the received original content 320 from the post format 330 to the website 350.

  FIG. 4 illustrates one embodiment of a technique for posting information on one website (or several websites) via post service and client software. In one embodiment, original content 420 is stored on mobile device 410. The original content 420 may consist of image files, text files, video files, media files, and other computer media files. The original content 420 may be converted to a post format 430. The post format 430 may be a type of the post format 610 of FIG.

  In one embodiment, client software 440 may be part of device 410. Client software 440 may include a post feed 450 and a post feed list 460. Post feed 450 may be a type of post feed 700 of FIG. The post feed list 460 may be the type of the post feed list 800 of FIG. Post feed lists may be obtained from a variety of sources. For example, the software on the client device may include a popular website post feed list, or a post feed list may be obtained as needed. The post feed list may be available from one or more websites that provide information about posting to the website.

  Post feed 450 may be utilized to format and / or send a post to post service 470 in response to post format 430. Then, the post service 470 posts the original content 420 to the website 490. In an alternative embodiment, the post feed list 460 may include a list of websites 490 and 495 that may be utilized for data to which the post format 420 is posted.

  FIG. 5 illustrates one embodiment of a technique for posting information on one website (or several websites) via post service and broker service. In one embodiment, original content 520 is stored on mobile device 510. Original content 520 may be composed of image files, text files, video files, media files, and other computer media files. The original content 520 may be converted to a post format 530. The post format 530 may be a type of the post format 600 of FIG.

  In one embodiment, post broker service 540 may receive data formatted according to post format 530. The post broker service 540 may be of a type similar to the post broker service 900 of FIG. Post broker service 540 may invoke post service 570 and / or post service 580 using post feed 550 or post feed list 560. Post services 570 and 580 may then post content to websites 590 and 595, respectively. Post feed 550 may be a type of post feed 700 of FIG. The post feed list 560 may be a type of the post feed list 800 of FIG.

  Client software or a post broker service may utilize information from post feed 550 to identify and call post service 570. The post service 570 may then post the original content 520 formatted according to the post format 530 on the website 590. In an alternative embodiment, the post feed list 560 may include a list of websites 590 and 595 where the original content 520 formatted according to the post format 530 is subsequently posted.

  FIG. 6 illustrates one embodiment of a post format structure. Post 610 may be a unified and extended format representing the content to be posted. General information about the post content may be embedded in the post format. The post 610 may include a title field 615 that describes the title of the post. Post 610 may include a timestamp field 620 that describes the time of the post. Post 610 may include an author field 625 that describes the author of the post. Author field 625 may further include information fields of name 630 and contact 635. The post 610 may further include a category field 640, a keyword field 645, an abstract field 650, and an extension field 655 that may describe, identify, or categorize the posted content 660. The content 660 may be described as being divided into separate items 665, 670, 675. In alternative embodiments, the content 660 may be further divided or not at all. The post 610 may further include a signature field 680 that identifies the post in the security process. In alternative embodiments, the post 610 may be embedded with a greater or lesser number of fields, or different fields.

  FIG. 7 shows one embodiment of a post-feed structure. The post feed 700 may provide information describing the post service. The post feed 700 may include a title 720 that may provide a post service name or other identifier. The post feed 700 may include a description field 730 that may describe the post service. The post feed 700 may further include a URL field 740 that may include the web address of the post service. The post feed 700 may further include a category field 750 that describes the type of post service. The post feed 700 may further include an extension field 760. In alternative embodiments, a greater or lesser number of fields or different fields may be part of the post feed 700.

  FIG. 8 illustrates one embodiment of a postfeed list structure. Post feed list 800 may collect multiple instance post feeds 700 into a single list. The feed list 800 may include a title 820 that may describe the title of the feed list. The feed list 800 may further include a description 830 that may describe the feed list. Feed list 800 may include an extension 840. The feed list 800 may further include a feed 805. The feed 805 may correspond to the post feed 700 of FIG. Feed list 800 may include one or more instances of feed 805. Title 850, description 860, URL (Uniform Resource Locator) 870, category 880, and extension 890 may correspond to title 720, description 730, URL 740, category 750, and extension 760 of FIG. 7, respectively. In alternative embodiments, a greater or lesser number of fields or different fields may be part of the feed list 800.

  FIG. 9 illustrates one embodiment of a post broker service structure. The post broker service 900 may include multiple layers to accept content submitted by users. Each layer may add functions related to content processing. The post broker service 900 may include a front end layer 910. The front end layer 910 may allow for posting content from various devices with different transfer protocols. In one embodiment, the front end layer 910 may transfer content from the original type of content to a post format. In one embodiment, the front end layer 910 receives an example of the original content 905 and content in SMS format and converts it to post format in the SMS front end 915. In an alternative embodiment, the postbroker service 900 uses different transport protocols (MMS, SMTP, HTTP, etc.) via different types of frontends embedded in the frontend layer 910 to deliver content from different devices. May be accepted. The post broker service 900 may include a filter layer 920. In one embodiment, the filter layer 920 may remove overlapping or unacceptable content from posting. In alternative embodiments, the filter layer 920 may remove content based on other criteria.

  The post broker service 900 may include a rendering layer 930. The rendering layer 930 may adapt or beautify the content to better represent the content. In alternative embodiments, the rendering layer 930 may render the content based on other criteria. The post broker service 900 may include a distribution layer 940. The distribution layer 940 may reliably post the content by calling a post service. Post broker service 900 may include a proxy layer 950. The proxy layer 950 may simulate a proxy service to create a website that does not provide a post service that conforms to the post service format (ie, some websites (eg, 980) provide the post service. If you don't, ensure that content posting is done). In one embodiment, proxy layer module 955 may function as an adapter that simulates the post service of website 980. In one embodiment, if a site supports the post service format, the data bypasses the proxy layer 950 and goes directly to the website 970. In alternative embodiments, the broker service 900 may have a fewer or greater number of layer structures than in FIG. 9, or a different layer structure.

  The post broker service 900 may include an additional feature layer 960. Layer 960 may store user profiles, aggregate post feeds by category into a post feed list, rank post services, and provide search functionality via a query service. In alternative embodiments, a greater or lesser number or different features may be available by post service.

  FIG. 10 illustrates one embodiment of a distributed post broker service. Mirror broker services 1010, 1020, 1030, and 1040 may be arranged in a delivery manner on servers 1050, 1060, 1070, and 1080, respectively. For example, server 1050 may be located in North America, server 1060 may be located in Asia, server 1070 may be located in Europe, and server 1080 may be located in Australia. In alternative embodiments, the mirror broker service may be located on a server elsewhere in the world. In one embodiment, servers 1050, 1060, 1070, and 1080 may be connected to central server 1090.

  FIG. 11 shows a user information verification technique. In one embodiment, the process 1120 converts the original content 1110 into a post format 1130. Post format 1130 may embed user signatures in the structure. The process 1120 may be performed on the user side. On the website side that receives the post, process 1140 extracts content information about the author and signature and validates it with the website information. The process 1150 may obtain a public key corresponding to the author information from a third party such as a registration database or a broker service using the information extracted in the process 1140. In process 1160, the integrity of the information may be verified by verifying that the signatures are equivalent using a public key obtained from a database or a third party broker. The process 1170 can pass information for posting to the website or pass the information back to the user.

  FIG. 12 illustrates one embodiment of a technique for posting material on a website based on a user's private key. In one embodiment, the user may store his private key in a post broker service. Device 1210 may include an original data format for posting. The original content may be sent from the device 1210 to the front end 1220 by, for example, multimedia messaging or other communication methods. The front end 1220 may identify the user by analyzing the received information. In one embodiment, the front end 1220 may obtain a user ID by telephone number. Thereafter, the process 1230 may change the original content to a post format and sign in to the website using a pre-stored private key associated with the user ID extracted by the front end 1220. Process 1230 may then deliver the post-formatted content for posting to website 1250. The website 1250 may then verify the received data ID and security information.

  FIG. 13 illustrates one embodiment of a technique for posting material to a website based on a post broker service private key. In one embodiment, a user may register a trusted post broker service with a website. Device 1310 may include an original data format for posting. The original content may be sent from the device 1310 to the front end 1320 via multimedia messaging or other communication methods. The front end 1320 may identify the user by analyzing the received information. In one embodiment, the front end 1320 may obtain a user ID by telephone number. Thereafter, the process 1330 may change the original content to post format and sign in to the website using the post broker service private key. The process 1330 may then deliver the post format content for posting to the website 1360. The website 1360 may then verify the received data ID and security information.

  FIG. 14 illustrates one embodiment of a device that can perform post-service processing. Device 1400 may be implemented with receive, transmit, wireless, broadband wired, access point, or any combination of these types of devices. Alternative devices may include a greater or lesser number of components, or different components. Device 1400 may include a bus 1405 or other communication device for communicating information, and a processor 1460 coupled to bus 1405 that may process information. Although device 1400 is shown as including a single processor, device 1400 may include multiple processors and / or coprocessors.

  Device 1400 may further include a memory 1470 coupled to bus 1405 that may store information and instructions that may be executed by processor 1460. Memory 1470 may be utilized to store temporary numeric variables or other intermediate information during instruction execution by processor 1460. Memory 1470 may include any type of memory known in the art, such as dynamic ram (DRAM), esram (SRAM), flash memory, and the like. In one embodiment, the memory 1470 may be any type of computer-readable that provides content (eg, computer-executable instructions) in a form readable by an electronic device (eg, a computer, information form terminal, cellular telephone). A storage medium may be included. For example, machine accessible media includes read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, and the like.

  The memory 1470 may further include the post broker service 1471 described above. Device 1400 may further include a read only memory (ROM) 1440 and / or other static storage device 1430 coupled to bus 1405 for storage of information and instructions. Data storage device 1430 may be a magnetic disk or an optical disk, and a corresponding drive may be coupled to device 1400.

  Device 1400 may further include a network interface (one or more) 1420 to access the network. The network interface (one or more) may include, for example, a wireless network interface having one or more omnidirectional antennas 1485. The network interface (s) 1420 further includes a wired network interface that communicates with a remote device via a network cable 1487 (which may be, for example, an Ethernet cable, coaxial cable, fiber optic cable, serial cable, or parallel cable). sell. Device 1400 may include additional components and / or other components.

  References herein to “one embodiment” or “an embodiment” are intended to imply that a particular feature, structure, or property described in that embodiment is at least one of the invention. It is meant to be included in one embodiment. Although phrases such as “in one embodiment” or “in one embodiment” appear throughout this specification, this does not necessarily refer to the same embodiment. Not necessarily.

  While the invention has been described in terms of several embodiments of the invention, those skilled in the art will recognize that the invention is not limited to the described embodiments and that variations and modifications within the spirit and scope of the attached drawings will be apparent. In addition, understand that it can be implemented. The description is thus to be regarded as illustrative instead of limiting.

Claims (14)

Device, instead of providing logged into multiple websites repeated content for posting, the content of posting to one or more of the web site via one or more remote servers, receiving once only Stages,
Formatting the received content according to a post format in which a signature is embedded for posting to one or more of the websites via one or more of the remote servers;
The device sends the formatted content with the embedded signature to a broker service server;
Broker Services The broker service server, having the step of receiving the content that is formatted from the device, the step of verifying the content formatted, and the step of transmitting the content that is validated in one or more said remote server Performing the steps,
One or more of the remote servers performing a post service for posting the formatted content to the one or more websites based on a post feed list;
The post feed list include the post feed, the post feed includes a description of the post service,
Method. The post feed list is formed by consolidating multiple post feed instances into a single list.
The method of claim 1. The post format includes one or more of a title, a timestamp, an author, a category, a keyword, an abstract, media content, and a signature.
The method according to claim 1 or 2. The step of executing the broker service is performed by the broker service server,
Receiving the formatted content and private key from the device;
Analyzing the received secret key to identify a user;
Validating the formatted content;
Signing in to one or more of the websites using the secret key;
Sending the verified content to one or more remote servers;
Having
4. A method according to any one of claims 1 to 3. The broker service server filters the formatted content;
The method of claim 4. The broker service is available on many servers in many locations,
The method according to claim 4 or 5. The received content conforms to one of a plurality of protocols including at least one of MMS, SMTTP and HTTP;
The method according to any one of claims 1 to 6. The broker service server, El Bei the step of rendering to conform to a predetermined reference the content before transmitting to the remote server,
8. A method according to any one of claims 1 to 7. The embedded signature is verified by a public key;
9. A method according to any one of claims 1 to 8. The content is in at least one form of a data structure and a media file.
10. A method according to any one of claims 1-9. The formatted content is posted to one or more websites based on a secret key;
11. A method according to any one of claims 1 to 10. When executed one or more computer-readable storage medium storing instructions for executing the method according to any one of the processors to claims 1 11.   An apparatus for performing the method according to any one of the preceding claims. Dynamic random access memory (DRAM);
12. A system coupled to said DRAM and comprising an agent for performing the method of any one of claims 1-11.

Images