JP5922779B2 - Generate processed web address information - Google Patents

Description

[Cross-reference of other applications]
This application names the invention of the application filed October 25, 2011, incorporated herein by reference for all purposes, "WEB ADDRESS INFORMATION, SHARINGING METHODS, FRIEND ADDING METHOD AND EQUIMENT THER Claims priority based on Chinese Patent Application No. 201113034836.X, “Providing and supplying method, friend adding method, and apparatus therefor”.

  The present application relates to the field of communication technology, and more particularly, to a technology that enables sharing of web address information between users and establishment of friendships between users.

  When a user is browsing a website, sometimes they can find web content that interests them and wants to share with others. For example, a user may send a link associated with the web content to a contact via an instant messaging service. Alternatively, the user may share the link on a microblog or blog. When other users view a link shared by the user, the link may be selected to confirm the associated web content. Specifically, for example, a user can find a web page of a product of interest when browsing an electronic commerce website. Users can share a link to this web page on a personal blog. The reader of the blog can see the published link and select the link to view the product information contained on the web page.

  Through such online sharing, the sharing source user and the user who has selected the shared link may notice that both are interested in the web content of the shared link. In this way, those users can have a common interest. It is desirable to connect two users through a friendship that is allowed on a website so that users can easily find other users to share information in the future.

  Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.

The figure which shows one Embodiment of the system for producing | generating a to-be-processed web address information.

The flowchart which shows one Embodiment of the process for producing | generating a to-be-processed web address information.

The flowchart which shows an example of the process for producing | generating process target web address information.

The figure which shows one Embodiment of the system for producing | generating a to-be-processed web address information.

The flowchart which shows another embodiment of the process for producing | generating a to-be-processed web address information.

The figure which shows another embodiment of the system for producing | generating a to-be-processed web address information.

The flowchart which shows one Embodiment of the process for establishing friendship between a 1st user and a 2nd user.

6 is a flowchart illustrating an example of performing activation for a user who has selected shared web address information.

1 is a diagram illustrating one embodiment of a system for enabling sharing of web address information between users. FIG.

FIG. 5 illustrates another embodiment of a system for enabling sharing of web address information between users.

  The present invention is a process, apparatus, system, composition of matter, computer program product embodied on a computer readable storage medium, and / or processor (stored in and / or stored in a memory connected to a processor). A processor configured to execute the provided instructions) and can be implemented in various forms. In this specification, these implementations or any other form that the invention may take may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or memory that is described as being configured to perform a task is a general component that is temporarily configured to perform a task at a certain time, or It may be implemented as a particular component that is manufactured to perform a task. As used herein, the term “processor” is intended to refer to a processing core configured to process one or more devices, circuits, and / or data such as computer program instructions.

  The following provides a detailed description of one or more embodiments of the invention with reference to the drawings illustrating the principles of the invention. Although the invention has been described in connection with such embodiments, it is not limited to any embodiment. The scope of the invention is limited only by the claims and includes many alternatives, modifications, and equivalents. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. These details are for the purpose of illustration, and the present invention may be practiced according to the claims without some or all of these specific details. For the purpose of simplicity, technical elements that are known in the technical fields related to the invention have not been described in detail so that the invention is not unnecessarily obscured.

  The generation of processed web address information is described herein. In various embodiments, first web address information that the first user wants to share is processed into second web address information. In some embodiments, the first web address information is processed into second web address information based at least in part on the user ID of the first user. In some embodiments, the second web address information is shared (eg, on a website (eg, microblog, blog, social networking platform) or via a client application such as an instant messaging application, for example. Public, display). In some embodiments, in response to selection by the second user of the second web address information, the second web address information establishes a friendship between the first user and the second user. It is configured to let you.

  FIG. 1 is a diagram illustrating an embodiment of a system for generating processed web address information. In this example, the system 100 includes clients 102, 103, and 105, a network 104, a web server 106, and a web address information system 108. Network 104 may include a high speed data network and / or a telecommunications network.

  Clients 102, 103, and 105 are configured to communicate with web server 106 and web address information sharing system 108 via network 104. Each of clients 102, 103, and 105 is illustrated as a laptop, but other examples of clients 102, 103, and 105 include desktop computers, smartphones, portable devices, tablets, or any Other computer devices. A client application, such as a web browser application, may be installed on each of the clients 102, 103, and 105 so that a user using the client can view the web page. For example, a first user may utilize client 102 to access various web pages associated with a website hosted by web server 106. The second user may utilize the client 103 to access various web pages associated with the website hosted by the web server 106. Further, the third user may utilize the client 105 to access various web pages associated with the website hosted by the web server 106. For example, the website may include an electronic commerce website where users can buy and sell goods. In some embodiments, user ID information associated with registered users of the website is stored on the web server 106. In some embodiments, the website supported by the web server 106 includes social networking features that allow two users registered on the website to be friends with each other. Users who are friends on the website may enjoy certain features of the website that may not be available to users of the website that are not friends of each other. For example, users who are friends on a website can share information with each other through social network features such as posting to each other's profiles, private messages, and instant messages. For example, a first user using the client 102 may be friends with a third user using the client 105 on a website, so that the first user and the third user can interact with each other on the website. Can communicate and share through.

  Web address information sharing system 108 is configured to allow users of clients 102, 103, and 105 to share web address information associated with a web page. In some embodiments, the first user of client 102 may visit a web page associated with web server 106 that they want to share with other users. In some embodiments, web page content may be identified and accessed by web address information (eg, links, URLs). In some embodiments, a request to share web address information is sent by client 102 (in response to a first user's selection to share web address information) to web address information sharing system 108. Is done. For example, the request includes web address information of a web page that the first user wishes to share and ID information associated with the first user. In response to receiving the request, the web address information sharing system 108 is configured to generate new web address information based at least in part on the web address information included in the request and the first user's ID information. Yes. In some embodiments, the web address information sharing system 108 allows the first user to copy and publish / publish web address information with other users (eg, via email, blog publishing, microblog publishing). The generated web address information is configured to be presented to the first user of the client 102 so that it can be shared. In some embodiments, the web address information sharing system 108 may post the type of sharing selected by the first user (e.g., the type of sharing posts generated web address information directly to the first user's blog). The generated web address information is automatically shared on behalf of the first user by publishing / sharing the generated web address information.

  The web address information sharing system 108 is further configured to allow users (eg, registered users) associated with a website hosted by the web server 106 to be friends with each other. For example, a second user using the client 103 can see and click on the generated web address information shared on the first user's blog. In response to the second user clicking on the generated generated web address information, an indication that the second user has accessed the generated web address information is displayed by the client 103 by the web address information sharing system 108. Sent to. In response to the suggestion, the client 103 accesses the web page content of the web address information that is the basis of the generated web address information (for example, the web page that the first user wanted to share) from the web server 106. The web address information sharing system 108 is configured to extract the user ID of the first user from the generated web address information. In some embodiments, the web address information sharing system 108 sends an add friend prompt message to the second user to encourage the second user of the client 103 to add the first user as a friend. Configured, where the prompt message includes controls related to the approval to add the first user as a friend. When the second user activates control of the prompt message, the web address information sharing system 108 communicates to the web server 106 that the first user is added as a new contact to the second user's friend list. It is configured as follows.

  In some embodiments, web server 106 and web address information sharing system 108 are included in the same system and / or controlled by the same party. In some embodiments, the logical code / computer code is stored locally on the client 102 so that the client 102 can perform at least some of the functions of the web address information sharing system 108 (such as those described above). .

  FIG. 2 is a flowchart illustrating an embodiment of a process for generating processed web address information. In some embodiments, process 200 may be implemented on a system such as system 100.

  Using process 200, processed web address information can be generated based at least in part on a user ID associated with the user, and the user can then pass the processed web address information to another user. Can be shared with.

  At step 202, a request to share a web page is received. This request includes at least first web address information regarding the web page and user ID information associated with the first user.

  When a first user is browsing various web pages of a website using a web browser application, he or she may find a web page that he or she wants to share with other users. In some embodiments, a button associated with sharing web address information may be presented on a particular web page of the website, and the user may select the button when they want to share the web page. . In some embodiments, the button is presented by the website of the web page that the first user is viewing. In response to an instruction by the user to share the web page (eg, selection of a button), a request may be sent for the user. In some alternative embodiments, each time a user visits a web page of such a specially configured website, a request may be issued automatically on behalf of the user. The request may include at least web address information (eg, URL) regarding the web page and user ID information associated with the first user. For example, the user ID information of the first user may be logon name information of the first user at a website related to the web page, but is not limited thereto. For example, a registered user of a website may have a logon name and / or password ID information stored with the website. For example, the user ID information includes user account information (which may include the user ID number of the user), user purchaser credit score (e.g., the number of times the user has purchased a product on the website and the user Value based on the number of times feedback sent about purchased items), whether the user opened an online shop on the website, and which other users are friends of the user on the website (for example, which other And / or may be related to the user's friends list).

  In some embodiments, time information regarding the request is also included in the request. For example, the time information may be information regarding when the request was made.

  In step 204, second web address information is generated based at least in part on the first web address information and user ID information associated with the first user.

  In some embodiments, the first web address information is processed to generate second web address information. In some embodiments, the generated second web address information is based at least in part on a combination of user ID information associated with the first user and the first web address information. In some embodiments, in addition to the user ID information of the first user and the first web address information, the generated second web address information may further include time information and / or first information about the request. Based at least in part on digital signature information associated with the user. For example, the digital signature information can be determined based on the user ID information of the first user by executing a hash function on the user ID information.

  In step 206, the second web address information is presented to the first user. The second web address information is configured so that it can be shared by the first user.

  Instead of presenting the first web address information (ie, the original web address information about the web page) to the user, the second web address information is presented to the user. For example, the second web address information may be presented in a pop-up frame when requested by the first user selecting a share button. Alternatively, for example, when a request is automatically issued on behalf of the first user due to a visit to the web page by the first user, the second web address information is stored in the web browser application used by the first user. It may be presented in a navigation bar / address field (where the web browser also displays the content of the web page associated with the first web address information). After the generated first web address information is presented to the first user, the first user may be on another web page (eg, a blog or microblog or social networking platform) or a messaging system (eg, The second web address information may be copied and shared via an email or instant messaging system). The second user can then view the shared second web address information and select it to be directed to a web page that the first user wishes to share with other users.

  Despite the second web address information being based on a combination of the first web address information and other information (eg, user ID information associated with the first user), the second web address information When the address information is selected by the second user, the web browser is directed to the web page referenced by the first web address information as if the second user selected the first web address information directly. to access. In some embodiments, the additional information included in the second web address information allows the user selection of the second address information to establish a friendship between the first user and the second user. Trigger processing.

  In some embodiments, the website of process 200 includes an e-commerce website. For example, in such an electronic commerce website, the first user may be a person involved in product transactions. For example, the status of the first user can be the status of the purchaser or seller of the e-commerce website. Prevent users with merchant status from publishing advertisements and establishing friendships with buyer status users (because merchant status user activity is a potential buyer status on the website) In some embodiments, first, before generating the second web address information for the first user, first the first user is used. The user ID information stored on the e-commerce website is checked to see if has a merchant status. If the first user has a merchant status, the first web address information is not disclosed and the first user cannot share the processed web address information. Conversely, if the first user has no merchant status, has a buyer status, or is a new user who has not yet participated in the transaction, the first web address information is processed and the second Web address information is generated.

  The following is an example of a technique for checking the seller or purchaser status of a first user. The first user's user ID information may be retrieved from a storage / database associated with the e-commerce website. For example, such user ID information may include purchaser credit score information and information regarding any shop opened on an electronic commerce website. Based on the user ID, it is determined that the first user has a buyer credit score higher than a predetermined credit score threshold, and no shop information is found for the first user (ie, the first user). Is not open on the e-commerce website), the first user's status is determined to be the buyer status. However, if the first user has a buyer credit score lower than a predetermined threshold and / or the first user has at least one shop open on the e-commerce website, the status of the first user Is determined to be the seller status.

  FIG. 3 is a flowchart illustrating an example of a process for generating processed web address information. In some embodiments, process 200 may be implemented using a process such as process 300.

  Process 300 illustrates an example of sharing web address information associated with an electronic commerce website. In an electronic commerce website, a particular web page may include product information regarding products being sold (eg, by a user).

  At step 302, a request associated with first web address information regarding a web page accessed by a first user is received. For example, a first user may visit a web page of an e-commerce website while browsing the website and indicate a desire to share a web page address. For example, the request may be issued by the first user selecting a button associated with sharing presented by the website, or the first user based on access to the web page by the first user. May be sent automatically instead of. In some embodiments, the request to generate processed web address information may be generated and transmitted by the web browser application of the client device. The following are four examples of original web address information, each including an original link to a specific web page containing product information.

  http: // item. taobao. com / item. htm? id = 87789467987

  http: // item. taobao. com / action / item_detail. htm? item_num_id = 87789467987

  http: // item. tmall. com / item. htm? id = 87789467987

  http: // item. lp. taobao. com / item. htm? item_id = 88789467987

  In step 304, it is determined whether user ID information associated with the first user can be retrieved. For example, a database of user ID information associated with registered users of an e-commerce website may be maintained for the e-commerce website. If the series of user IDs for the first user cannot be retrieved, the process ends. Otherwise, control proceeds to step 306.

  For example, the first user's user ID information may be retrieved from a database associated with the e-commerce website if the first user is logged on to the e-commerce website and browsing the e-commerce website. . However, even if the first user is browsing the e-commerce website without logging on to the e-commerce website, the user ID information of the first user is the previous user's previous e-commerce website Can be obtained using logon history and / or password information (eg, cookie information) stored by the web browser for access (eg, a first user may have previously logged on to an e-commerce website using a web browser) As such, any such historical information stored by the web browser can be used to find the first user's ID information at the e-commerce website).

  At step 306, based at least in part on the retrieved user ID information, it is determined whether the status of the first user is associated with the seller or the purchaser. For example, when it is determined that the first user is a seller, the process ends. However, if it is determined that the first user is a purchaser, control proceeds to step 308.

  For example, the first user's buyer credit score and shop information may be determined from the first user's retrieved ID information. If the first user's buyer credit score is greater than a predetermined threshold and no shop information is found for the first user, the first user's status on the e-commerce website is determined to be the buyer status. The Otherwise, the status of the first user on the e-commerce website is determined to be the seller status and the process ends.

  In step 308, second web address information is generated based at least in part on the first web address information and user ID information associated with the first user.

  In some embodiments, a digital signature may be generated for the first user based on the retrieved user ID information. In some embodiments, the time information is determined based on time information that may be included in the request or based on the current time. In some embodiments, the second web address information is generated based on a combination of the first web address information, the first user's user ID information, a digital signature, and time information.

  For example, assume that the first web address information of a web page containing product information on an electronic commerce website is as follows.

  http: // item. taobao. com / item. htm? id = 87789467987

  From the first web address information, the product ID of the product information included in the web page can be determined to be id = 87878967987. The current time is t = 20110411. After obtaining the first user's ID information (userId = 1402799043) on the e-commerce website, t is added to userId (eg, t is added to userId), base32 conversion is performed on userId + t, h = 19 ppogv is obtained. An MD5 hash (md5) may be generated with the following argument = MD5 (character i + id + userId + t + encryption key) = b83367751312b10f2788d522d287df33f. Here, the letter i is a product type value (which can be acquired from the product ID) corresponding to the product information described above, and the encryption key is set in advance. (In this example, MD5 hashing is used, but other types of hashing techniques may be used instead). For example, the length of userId may be used to obtain the mod of userId. m can be obtained by extracting four digits following the mod-th digit in md5. In this example, m = 3675. Then, u = h + m = 19 ppogv3675. The calculated u may then be combined with the first web address information to obtain the second web address information. For example, a value (for example, u in this example) calculated based on the user ID information, digital signature, and time information of the first user may be added to the end of the first web address information. Therefore, the second web address information generated in this example is as follows.

  http: // item. taobao. com / item. htm? id = 87789467987 & u = 19ppogv3675

  Here, the second web address information (http://item.taobao.com/item.html?id=87878967987 & u = 19ppogv3675) is the first web address information (http://item.taobao.com/item). .Htm? Id = 87789467987) is included at the end of the calculated u (& u = 19ppogv3675).

  When the second user selects second web address information (http://item.taobao.com/item.htm?id=87878967987 & u = 19ppogv3675) that can be published on the website, the web browser Access the web page content associated with the web address information (http://item.taobao.com/item.html?id=87789467987) and use the remaining value (& u = 19ppogv3675) to the first user And establish a friendship on the website with the second user.

  FIG. 4 is a diagram illustrating one embodiment of a system for generating processed web address information. In some embodiments, processes 200 and 300 may be performed on a system such as system 400. The system 400 includes a web address information acquisition unit 31, a web address information generation unit 32, and a web address information provision unit 33.

  These units may be software components that run on one or more processors, hardware such as programmable logic devices and / or application specific integrated circuits designed to perform specific functions, or Can be implemented as a combination of In some embodiments, the unit is a non-volatile storage medium (optical disk), such as a plurality of instructions for causing a computing device (personal computer, server, network device, etc.) to perform the methods described in the embodiments of the present invention. , A flash storage device, a portable hard disk, etc.) may be embodied in the form of a software product. Units may be implemented on a single device or distributed across multiple devices.

  The web address information acquisition unit 31 is configured to receive a request to share a web page, and the request includes first web address information, user ID information associated with the first user, and including.

  The web address information generation unit 32 is configured to generate second web address information based at least in part on the first web address information and the user ID information associated with the first user. Yes.

  The web address information providing unit 33 is configured to present the second web address information to the first user so that the first user can optionally share the second web address information with other users. ing.

  FIG. 5 is a flowchart illustrating another embodiment of a process for generating processed web address information. In some embodiments, process 500 may be implemented in system 100.

  Using process 500, processed web address information can be generated based at least in part on a user ID associated with the user, and the processed web address information is then shared by the user. Can be shared automatically on behalf of the user in a manner.

  At step 502, a request to share a web page is received. The request includes at least first web address information regarding the web page, user ID information associated with the first user, and selection regarding the type of sharing. A first user may find a web page that he wants to share with other users. In some embodiments, the first user can indicate that he wants to share the web page by selecting a button associated with the sharing request. In some embodiments, the first web address information associated with the web page is presented by the web browser in its navigation / address field. In some embodiments, the first user selects a particular share type from a plurality of share types available in connection with the share request. For example, multiple choices of sharing types may be presented to the first user, such as sharing on a blog, sharing on an instant message, sharing on a social network platform, and sharing on a microblog. Prior to sending the request, the first user may be prompted to confirm the completion of the request.

  In some embodiments, the request may further include text entered by the user regarding the web page corresponding to the first web address information. The first user may be prompted to write or provide comments regarding the content of the shared web page. Such user input text regarding the web page may also be included in the request.

  For example, assume that the web page that the first user wants to share is the web page of the e-commerce website. Assume that the product corresponding to the product information included in the web page is a router of model number 123. The first user submits the following explanation content in a request for sharing the web page. “Router 123, price 170 yuan, really good, so share it with everyone.” Thus, after the first user confirms the input text, the request for sharing includes not only the first web address information but also the user input text regarding the web page.

  In step 504, second web address information is generated based at least in part on the first web address information for the web page and the user ID information associated with the first user. For example, step 504 may be performed in the same manner as step 204 of process 200 of FIG.

  In step 506, the second web address information is shared based at least in part on the selection regarding the sharing type.

  The second web address information is shared according to the sharing type indicated in the request. For example, if the selected sharing style is a style related to sharing on the first user's blog, the second web address information is posted to the first user's blog. In some embodiments, first user authentication information for websites, blogs, microblogs, and social media platforms where second web address information is shared is stored to allow access to such services. Is done. If the request also includes text entered by the first user, the second web address information can be shared with the user entered text. For example, the text entered by the first user is “Router 123, price 170 yuan, really good, so share with everyone” and the generated second web address information is “http: // t .Cn / h1m8jk ”and the sharing type selected by the first user is“ shared by the blog of the first user ”. For example, the second web address information can be processed into “http://t.cn/h1m8jk” by the link shortening service. Therefore, the information published on the first user's blog can be as follows.

  “Router 123, price 170 yuan, really good, so share it with everyone. The web address is http://t.cn/h1m8jk”

  In some embodiments, as will be described below with reference to FIGS. 7 and 8, a second user accesses a web page and is further published to the first user's blog. By selecting address information, it can be recommended to be friends with the first user.

  FIG. 6 is a diagram illustrating another embodiment of a system for generating processed web address information. In some embodiments, process 500 may be implemented in system 600. The system 600 includes a web address information acquisition unit 51, a web address information provision unit 52, a sharing type unit 53, a web address information generation unit 54, and a sharing unit 55.

  The web address information acquisition unit 51 is configured to receive a request to share a web page, the request including first web address information about a web page accessed by a first user, User ID information associated with other users and selections regarding share types

  The share type unit 53 is configured to receive a request to share a web page and specify a selection regarding the share type.

  The web address information generation unit 54 is configured to generate second web address information based at least in part on the first web address information and the user ID information associated with the first user. Yes.

  The sharing unit 55 is configured to share the second web address information based at least on a selection regarding the sharing type identified by the sharing type unit 53.

  FIG. 7 is a flowchart illustrating one embodiment of a process for establishing a friendship between a first user and a second user. In some embodiments, process 700 may be implemented on a system such as system 100.

  Process 700 may be performed after process 200 of FIG. 2 or process 300 of FIG. The process 700 includes a friendship relationship between a first user related to sharing web address information and a second user related to accessing one or more web pages related to shared web address information. For example, it can be used to establish friendships recognized by websites.

  At step 702, suggestions regarding access to web address information by a second user are received. Web address information may be shared by a first user, for example, on a website, social media platform, blog, or microblog, and a second user who has viewed the published web address information will be made public. Can be accessed by selecting (for example, clicking) web address information.

  At step 704, web page content associated with the web address information is retrieved in response to the suggestion. The web address information may or may not be processed based on other web address information, such as the generated second web address information described in process 200 of FIG. 2 or process 300 of FIG. , Including user ID information of the first user. As described above, the second web address information generated based on the first web address information may be disclosed by the first user of the website. Then, when the second web address information (which has been processed to include the first web address information) is selected by the second user, the web browser is responsible for the web page content associated with the first web address information. To access.

  If the web address information is not processed based on another web address information, it may not include user ID information of another user.

  In step 706, it is determined whether the web address information is associated with user ID information associated with the first user.

  After the web page browser used by the second user accesses the web page content, it is determined whether the web address information includes user ID information associated with the first user (eg, The first user may include users other than the second user who may have been involved in sharing the web address information selected by the second user). When it is determined that the web address information does not include the user ID information of the first user, the web address information is determined not to be shared by the first user. No attempt is made to establish friendships with other users. Also, the process ends. However, when it is determined that the web address information includes the user ID information of the first user, it is determined that the web address information is shared by the first user, so the second user and An attempt is made to establish a friendship with the first user. Control also proceeds to step 708. In some embodiments, at least a portion of the web address information is extracted to determine whether the web address information includes user ID information associated with the first user, The presence or absence of data generated based on this may be examined. For example, if the web address information is http: // item. taobao. com / item. htm? When id = 8778946787 & u = 19ppogv3675, the part after “& u” may be extracted and the presence / absence of user ID information may be checked. For example, the extracted part may be converted back to the original user information.

  In step 708, a prompt message including controls for adding the first user as a friend is sent to the second user.

  If it is determined that the web address information includes user ID information associated with the first user, those users further have a common interest that can be more easily shared with each other when they become friends with each other. Because there is a possibility that the friendship between the first user and the second user may be promoted. For example, both a first user and a second user may be registered on a website (such as an e-commerce website) that includes elements of a social network where various users can be friends with each other on the website. For example, users who are friends on a website may be able to access each other's contact information that can only be obtained by friends. Also, for example, users who are friends can share content with each other, such as private messages on websites that users can only do if they are friends, public postings on user profile pages, tagging with user ID information, etc. You can enjoy various means for sharing.

  Therefore, a friend addition prompt message is sent to the second user asking whether the second user wants to be friends with the first user who shared the web address information. For example, the add friend prompt message may appear as a pop-up message that overlaps the web page that the second user is currently browsing on the web browser. Prompt messages include controls. In some embodiments, the second user activates a control (eg, the control can include an approval button) in the add friend prompt message (eg, by clicking on the control) and the first user If approving the friendship with the user, the first user is added to the friend list of the second user.

  In some embodiments, the friendship between the second user and the first user established by the second user activating control of the add friend prompt message is a one-way friendship. is there. That is, even if only the second user agrees to add the first user as a friend, and the first user does not explicitly agree to add the second user as a friend, The user can add the first user as a friend to the friend list of the second user. This is equivalent to the second user sending a friend addition approval message. When the second user activates control of the add friend prompt message, ID information of the second user at the website corresponding to the web address information is obtained. Specifically, for example, it is first determined whether or not the second user is logged on to the website. If the second user is currently logged on, the second user's ID information can be obtained directly from the website. However, if the second user is not currently logged on, the second user is prompted to log on to the website. After the second user logs on, the second user's ID information can be obtained from the website. After the ID information of the second user is acquired, a friend addition request message is generated. The friend addition request message includes ID information of the second user and the first user on the website. When processing the add friend request message, the second user's friend list on the website is looked up using the second user's ID information, and then the first user's ID information is the new contact. To be added to the second user's friend list. In this way, the second user can add the first user as a friend on the website.

  In some embodiments, the friendship between the second user and the first user established by the second user activating control of the add friend prompt message is a two-way friendship. is there. That is, the first user and the second user can clearly add each other as friends. In this case, if the second user approves adding the first user as a friend (this is equivalent to sending a friend addition approval message), the ID of the second user at that website Information is obtained and then a friend addition request is generated. The friend addition request message includes ID information of the second user and the first user on the website. When processing the add friend request message, the second user's friend list on the website is looked up using the second user's ID information, and then the first user's ID information is the new contact. To be added to the second user's friend list. Also, the first user's friend list on the website is looked up using the first user's ID information, and then the second user's ID information becomes the first user's friend as a new contact. Added to the list. In this way, the second user and the first user can add each other as friends.

  In some embodiments, the first user is not added as a friend of the second user until a clear approval is received from the first user. When the second user activates control of the add friend prompt message, an add friend prompt message is sent to the first user asking if the first user wants to be friends with the second user. Prompt messages include controls. For example, the friend addition prompt message may include ID information of the second user. In some embodiments, the first user authorizes a friend relationship with the second user by activating the control in the add friend prompt message (by a user click by the first user). Then, a friend addition approval message is generated. The second user's friend list is looked up using the second user's ID information, and then the first user's ID information is added to the looked up second user's friend list. Further, the first user's friend list is looked up using the first user's ID information, and the second user's ID information is added to the first user's friend list. In this way, the second user and the first user can add each other as friends.

  In some embodiments, before sending a prompt message to a second user to add the first user as a friend, the web page that the second user had previously viewed is the second user. A check may be performed as to whether the domain name information associated with the domain name information associated with the web address information that the user is trying to access. If two domain name information matches, i.e. the previous web page and the web page linked by web address information are related to the same website, it is shared by the second user by the first user It is suggested that you did not visit the web page with the given web address information. In this case, the friend addition prompt message regarding adding the first user as a friend is not transmitted to the second user. If the two domain name information do not match, i.e. the previous web page and the web page linked by the web address information are not related to the same website, it is shared by the second user by the first user The web address information provided indicates that the web page was visited. In this case, a friend addition prompt message related to adding the first user as a friend is transmitted to the second user.

  In some embodiments, the web address information shared by the first user may be associated with a deadline condition, i.e., the processed web address information shared by the first user has a predetermined effective sharing period. After elapse, do not trigger an attempt to establish a friendship between the first user and the second user. For example, after the web address information is determined to include the first user's ID information and before the add friend prompt message is sent to the second user, the time for the first web address information Verification may be performed. When performing time verification, time information related to the request may be extracted from the web address information, and then it is determined whether a predetermined effective sharing period has passed from the time indicated by the extracted time information. Is done. If a period longer than the predetermined effective sharing period has passed from the time indicated by the extracted time information, the processed web address information shared by the first user expires and access to the processed web address information is no longer available. Do not trigger an attempt to establish a friendship between the first user and the second user. However, the web browser still accesses the associated web page content if a user selection of web address information is made. However, if the predetermined effective sharing period has not passed from the time indicated by the extracted time information, the processed web address information shared by the first user has not expired, and access to the processed web address information Triggers an attempt to establish a friendship between the first user and the second user, and an add friend prompt message is sent to the second user regarding adding the first user as a friend. This feature can protect the user from the trouble caused by expired web address information.

  In some embodiments, an activation evaluation may be performed to determine whether it is desirable to establish a friendship between the first user and the second user. In some embodiments, the activation evaluation includes determining whether the digital signature included in the web address information associated with the first user can be verified. In some embodiments, the activation evaluation may be performed before the add friend prompt message is sent to the second user. In some embodiments, the digital signature included in the web address information may be extracted during activation evaluation. As described above, the digital signature can be generated based on a user ID associated with the first user. In some embodiments, the digital signature may be converted back to the original user ID. In some embodiments, if the digital signature is generated using an irreversible hash, the information from which the digital signature is derived can be obtained using a hash dictionary. This user ID information is then compared with the first user ID information determined from the processed web address information. If there is a match, activation is successful and an add friend prompt message is sent to the second user regarding adding the first user as a friend. However, if they do not match, the activation fails, the digital signature information is determined to be fake or revoked, and the add friend prompt message regarding adding the first user as a friend is not sent to the second user. .

  In some embodiments, it may be determined whether the first user and the second user are already friends with each other on the website. In order to execute this determination, the ID information of the first user and the ID information of the second user are used. The first user's ID information is derived from the web address information. The second user's ID information may be the second user's ID information stored by the website, or the second user's ID information based on previous visits to the website by the second user. ID information stored by the user's web browser. When the second user is not currently logged on to the website, the second user ID information of the second user used to execute the determination is an ID information history stored by the web page browser. When the second user has already logged on to the website, the second user ID information of the second user used to execute the determination is the ID information of the second user stored by the website. However, when the ID information history stored by the web page browser is used, the activation evaluation is performed by verifying the digital signature of the first user included in the web address information. If the second user's ID information stored by the website is used, an activation evaluation is performed to determine whether the first user is already included in the second user's friend list. If it is determined that the first user is already included in the second user's friend list, the add friend prompt message is not sent to the second user (the first user is added to the second user's friend list). Activation evaluation will automatically fail because it does not need to be added to However, if it is determined that the first user is not yet included in the second user's friend list, a friend addition prompt message regarding adding the first user as a friend is sent to the second user, An activation evaluation is performed, such as by verifying the first user's digital signature included in the web address information.

  In some embodiments, it may be determined whether the first user and the second user are the same user at the website. This determination may be performed by comparing the first user's ID information with the second user's ID information, and if they match, the first user and the second user are the same user on the website. Since it is determined that there is, a friend addition prompt message regarding adding the first user as a friend is not transmitted to the second user. However, if they do not match, it may be determined whether the first user is already included in the second user's friend list.

  In some embodiments, the website associated with the web address information of process 700 is associated with an electronic commerce website. If the website is an e-commerce website, it may be desirable to prevent users with merchant status from establishing friendships with other users with buyer status. To avoid annoying buyer users with ads and other actions based on social interests). To that end, in some embodiments, after determining that the second user's ID information and the first user's ID information at the e-commerce website are not the same, and the first user is already in the second The status of the second user on the e-commerce website can also be determined based on the second user's ID information before determining whether it is included in the user's friend list. If it is determined that the status of the second user is a seller, a friend addition prompt message regarding adding the first user as a friend is not transmitted to the second user. If the status of the second user is a purchaser, it may be determined whether the first user is already included in the second user's friend list.

  As described above, in some embodiments, after the first user's digital signature information included in the web address information is successfully verified, the activation evaluation may be confirmed as successful. However, in some embodiments, after successfully verifying the digital signature information included in the web address information, the following is performed so as not to provide the second user with an extra friend addition prompt message regarding the same web address information: May be. A first name list may be maintained for the web address information, wherein the first name list includes ID information at a user's website for which the web address information has already been successfully activated (e.g., a second name list). If the user is on the first name list, the friendship between the second user and the first user has already been established by the second user selecting the shared web address information. ing). If the second user's ID information is found in the first name list, the activation evaluation is considered to have failed. However, if the second user's ID information is not found in the first name list, the activation evaluation is confirmed to be successful and the first name list is updated to include the second user's ID information. The In some embodiments, to limit the number of times the same web address information is activated, determine whether the second user ID information of the second user is already on the first name list. Previously, the number of add friend prompt messages sent in association with web address information within a predetermined time period (ie, the number of times the same web address information has been activated) is obtained. If the determined number is greater than the first predetermined threshold, the activation evaluation is considered failed because the frequency of activation of the web address information exceeds the maximum number of activations for the web address information. However, if the determined number is less than or equal to the first predetermined threshold, the frequency of activation of the web address information does not exceed the maximum number of activations, so the second user's ID information is already the first name. It is determined whether it is on the list. If the second user's ID information is already in the first name list, the add friend prompt message is not sent to the second user (the second user has already successfully activated the second web address information) Because)

  In some embodiments, the first user's digital signature information included in the web address information has been successfully verified so as not to provide the second user with an extra friend addition prompt message related to the first user. Later, the following may be performed: A second user's friend list may be obtained, and it is determined whether the first user is already included in the list. Active if the first user is already on the second user's friend list (ie, the first user and the second user are already friends), even if the digital signature verification is successful Evaluation will automatically fail. However, if the first user is not included in the second user's friend list (ie, the first user and the second user are not yet friends), the activation evaluation is confirmed as successful and the first user Are added to the second user's friend list.

  In some embodiments, a web address already selected / activated by the second user to limit the number of times the same second user activates any web address information published by another user A second name list is maintained for other users who have published the information. The number of friend addition prompt messages sent in relation to the second user within a predetermined period of time before determining whether the user ID information of the first user is already on the second name list ( That is, the number of times the second user has activated the web address information published by any user is acquired. If the number is greater than a second predetermined threshold, the activation is considered failed because the frequency of activation of the second user exceeds the maximum number of activations for the second user. However, if the number is less than or equal to the second predetermined threshold, the activation frequency of the second user has not exceeded the maximum number of activations for the second user, so activation is confirmed as successful, It is determined whether the ID information of one user is already on the second user list. If the first user's ID information is already in the second name list, the add friend prompt message is not sent to the second user (the second user has already successfully activated the second web address information) Because)

  FIG. 8 is a flowchart illustrating an example of performing activation for a user who has selected shared web address information. In some embodiments, at least a portion of the activation evaluation of process 500 may be performed using process 800. In the example of process 800, the website associated with the web address information is an e-commerce related website.

  In step 71, web address information and ID information associated with a second user are received. The information is received when the second user accesses (eg, clicks) web address information published on the website. Web address information is information about the electronic commerce website and is shared by the first user. The ID information associated with the second user may be stored by a web browser used by the second user.

  In step 72, it is determined whether the received second user ID information of the second user matches the second user ID information retrieved from the electronic commerce website. If the ID information matches, control proceeds to step 73. If the ID information does not match, control proceeds to step 76.

  In step 73, it is determined whether the ID information associated with the second user matches the ID information associated with the first user. The first user includes a user who has shared the web address information selected (eg, clicked) by the second user. If the ID information associated with the second user matches the ID information associated with the first user, the first user and the second user are considered to be the same user, so control is Proceeding to step 712, which indicates an activation failure, the process ends. However, if the ID information associated with the second user does not match the ID information associated with the first user, the first user and the second user do not include the same user, so control is Proceed to step 74.

  In step 74, it is determined whether the second user has a purchaser status based at least in part on the second user's ID information. If the second user is evaluated to have buyer status, control proceeds to step 75. However, if the second user is evaluated to have merchant status, control proceeds to step 712.

  In step 75, whether the first user is already included in the second user's friend list is determined based at least in part on the second user's ID information and the first user's ID information. The If it is determined that the first user is already included in the second user's friend list, control proceeds to step 712. Otherwise, control proceeds to step 76.

  In step 76, it is determined whether the digital signature information extracted from the web address information can be successfully verified with the first user ID information extracted from the web address information. If verification is successful, control proceeds to steps 77 and 79. Conversely, if verification fails, control proceeds to step 712.

  In step 77, it is determined whether the number of friend addition prompt messages transmitted in association with the web address information within a predetermined time domain is greater than a first predetermined threshold. If the first predetermined threshold is exceeded, control proceeds to step 712. Otherwise, control proceeds to step 78.

  In step 78, it is determined whether the ID information associated with the second user is already on the first name list. The first name list includes ID information associated with the user who activated the web address information. If it is determined that the ID information associated with the second user is already on the first name list, control proceeds to step 712. If it is determined that the ID information associated with the second user is not yet on the first name list, control proceeds to step 711.

  In step 79, it is determined whether the number of add friend prompt messages transmitted in association with the second user within a predetermined time domain is greater than a second predetermined threshold. If the first predetermined threshold is exceeded, control proceeds to step 712. Otherwise, control proceeds to step 710.

  In step 710, it is determined whether the ID information associated with the first user is already on the second name list. The second name list is a list relating to other users who have published web address information that has already been selected / activated by the second user. If it is determined that the ID information associated with the first user is already on the second name list, control proceeds to step 712. If it is determined that the ID information associated with the first user is not yet on the second name list, control proceeds to step 711 where activation is successful and the process ends.

  In step 711, the activation is determined to be successful and the process ends.

  In step 712, the activation is determined to have failed and the process ends.

  As described above, in various embodiments, a first user shares processed web address information about a web page that the first user wants to share with other users. The shared web address information includes user ID information associated with the first user. The second user can then click to visit the shared web address information. The web browser used by the second user can then access and display web page content associated with the web address information. In some embodiments, after accessing the web page content associated with the web address information, it is determined whether the web address information includes user ID information associated with the first user. If it is determined that the user ID information associated with the user ID information associated with the first user is included, the first user is added to the second user's friend list as a new contact An add friend prompt message is sent to the second user for recommendation to the second user. If the second user approves establishing a friendship with the first user (eg, by adding the first user to the second user's friend list), the first user and the second user Users can be friends recognized on relevant websites. In this way, the two users can easily communicate with each other on the website using sharing / communication tools available on the website (eg, instant messaging, sharing by user profile, private messaging, etc.). become.

  FIG. 9 is a diagram illustrating one embodiment of a system for enabling sharing of web address information between users. In this example, the system 900 includes a web address information acquisition unit 81, a first user ID information confirmation unit 82, and a prompt message providing unit 83.

  The web address information acquisition unit 81 is configured to determine web address information corresponding to a web page selected (eg, clicked) by the second user.

  The first user ID information confirmation unit 82 is configured to determine whether the web address information acquired by the web address information acquisition unit 81 includes the user ID information of the first user.

  The prompt message providing unit 83 is configured to receive an indication from the first user ID information confirmation unit 82 that the user ID information of the first user ID is included in the web address information. The prompt message providing unit 83 is further configured to send an add friend prompt message to the second user, the prompt message being associated with the first ID associated with the ID information determined from the web address information when activated. Control that causes the user to be added to the friend list of the second user.

  In some embodiments, the system 900 further includes:

  Before the prompt message providing unit 83 sends the add friend prompt message to the second user, the previously viewed web page of the second user is related to the web address information that the second user was trying to access. A domain name information evaluation unit configured to determine whether the domain name information corresponding to the domain name information to be determined is related. If the domain name information does not match, the prompt message providing unit 83 is configured to send a friend addition prompt message to the second user.

  In some embodiments, the web address information further includes time information. Accordingly, in some embodiments, the system 900 may further include:

  A point-of-time information extraction unit configured to extract time information from the web address information acquired by the web address information acquisition unit 81 before the prompt message providing unit 83 transmits a friend addition prompt message to the second user.

  A time length evaluation unit configured to determine whether or not the length of time elapsed from the time indicated in the time information extracted from the web address information exceeds a predetermined effective sharing period. When the time length evaluation unit determines that the length of time elapsed from the time indicated in the time information does not exceed the predetermined effective sharing period, the prompt message providing unit 83 receives the second message for adding a friend prompt message. Configured to send to users.

  In some embodiments, the system 900 further includes:

  Before the prompt message providing unit 83 transmits the friend addition prompt message to the second user, the user ID information of the first user and the digital signature information generated based on the user ID information of the first user A web address information transmission unit configured to transmit web address information including the web address information to a web page server corresponding to the web address information. In some embodiments, the web address information sending unit is further configured to send the user ID information of the second user to the web page server. For example, the user ID information of the second user may be retrieved from a website associated with the web address information, or may be retrieved from information stored by a web browser used by the second user.

  An instruction message receiving unit configured to receive an add friend instruction message from a web server. The prompt message providing unit 83 is configured to transmit a friend addition prompt message to the second user when the command message receiving unit receives the friend addition command message.

  In some embodiments, the system 900 further includes:

  An approval message receiving unit configured to receive a friend addition approval message transmitted by the second user.

  An ID information acquisition unit configured to acquire the ID information of the second user at the website corresponding to the web address information after the friend addition approval message is received by the approval message receiving unit.

  The request message transmission unit is configured to transmit a friend addition request message including the ID information of the second user and the ID information of the first user on the website to the web page server.

  FIG. 10 is a diagram illustrating another embodiment of a system for enabling sharing of web address information between users. In this example, the system 1000 includes a web address information receiving unit 91, a verification unit 92, and a command message transmission unit 93.

  The web address information receiving unit 91 is configured to determine web address information corresponding to the web page selected by the second user. In some embodiments, the web address information includes user ID information of the first user and digital signature information generated based on the user ID information of the first user.

  The verification unit 92 is configured to verify the digital signature information extracted from the web address information using the user ID information of the first user extracted from the web address information.

  The command message transmission unit 93 is configured to transmit a friend addition command message after the verification by the verification unit 92 is successful.

  In some embodiments, the web address information receiving unit 91 receives the web address information, the user ID information of the second user, and the user ID information of the first user extracted from the web address information. It is configured. For example, the user ID information of the second user may be retrieved from a website associated with the web address information, or may be retrieved from information stored by a web browser used by the second user.

  In some embodiments, the system 1000 further includes:

  Before the verification unit 92 verifies the digital signature information included in the web address information, the received user ID information of the second user is stored in the website corresponding to the web address information. An ID evaluation unit configured to determine whether it matches information.

  The friend list evaluation unit is configured to determine whether or not the first user is already included in the second user's friend list using the second user's ID information and the first user's ID information. Has been. The verification unit 92 receives the second user ID information that matches the second user ID information stored on the website, and the first user is still included in the second user's friend list. If not, the digital signature information extracted from the web address information is verified.

  In some embodiments, the system 1000 further includes:

  Before the name list evaluation unit evaluates whether the first user is already included in the second user's friend list, the ID information of the second user and the first user is the same on the website An ID information evaluation unit configured to determine whether or not. Whether the first user is already included in the friend list of the second user when the ID information evaluation unit determines that the first user and the second user are not the same user. It is comprised so that it may determine.

  In some embodiments, the system 1000 further includes:

  The first name list obtaining unit is configured to obtain a first name list corresponding to the web page associated with the web address information before the command message sending unit sends the add friend command message.

  The first name list evaluation unit is configured to determine whether the user ID information of the second user is already on the first user list.

  The command message sending unit 93 is configured to send a friend addition command message in response to a determination by the first name list evaluation unit that the second user's ID information is not found in the first name list. .

  In some embodiments, the system 1000 further includes:

  The first message number acquisition unit is within a predetermined time domain before the first name list evaluation unit evaluates whether the user ID information of the second user is already on the second name list. It is configured to obtain the number of add friend command messages transmitted in association with the web address information.

  The first message number evaluation unit is configured to determine whether the number acquired by the first message number acquisition unit exceeds a predetermined threshold. The first name list evaluation unit is transmitted in association with the web address information within a predetermined time domain when it is determined that the number acquired by the first message number acquisition unit does not exceed a predetermined threshold. Is configured to retrieve the number of friend add command messages.

  In some embodiments, the system 1000 further includes:

  The second name list acquisition unit is configured to acquire a second name list corresponding to the second user before the instruction message transmission unit transmits the friend addition instruction message.

  The second name list evaluation unit is configured to determine whether the user ID information of the first user is already on the second name list.

  The command message sending unit 93 is configured to send a friend addition command message when the second name list evaluation unit determines that the first user's ID information is not yet on the second name list. ing.

  In some embodiments, the system 1000 further includes:

  The second message number acquisition unit is within a predetermined time domain before the second name list evaluation unit evaluates whether or not the user ID information of the first user is already on the second name list. It is configured to obtain the number of friend addition command messages transmitted in association with the second user.

  The second message number evaluation unit is configured to determine whether the number acquired by the second message number acquisition unit exceeds a predetermined threshold. The second name list evaluation unit determines the user ID information of the first user when the second message number acquisition unit determines that the number acquired by the second message number acquisition unit does not exceed a predetermined threshold. Is already determined to be on the second name list.

  In some embodiments, the system 1000 further includes:

  The friend addition request message receiving unit is configured to acquire a transmitted friend addition request message including the ID information of the second user and the ID information of the first user.

  The friend list lookup unit is configured to look up the second user's friend list using the second user's ID information.

  The friend addition unit is configured to add the ID information of the first user to the friend list of the second user.

  One of ordinary skill in the art should understand that the embodiments of the present application may be provided as a method, a device (apparatus), or a computer software product. Accordingly, the present application can take an embodiment consisting entirely of hardware, an embodiment consisting entirely of software, and an embodiment combining software and hardware. Further, the present application provides a computer program implemented on one or more computer-operable storage media (including but not limited to magnetic disk storage devices, CD-ROMs, and optical storage devices) that include computer program code. It can take the form of

  The present application is described with reference to flowchart illustrations and / or block diagrams based on methods, devices (apparatus), and computer program products of embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, and combinations of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data device to generate a machine, so that the computer or other programmable data The instructions are executed by the processor of the apparatus to generate a device that is used to implement one or more processes in the flowchart and / or functions described in one or more blocks in the block diagram.

  These computer program instructions may be stored on a dedicated computer readable storage device capable of directing a computer or other programmable data device such that the instructions on these computer readable devices are Is stored, a product including an instruction device is generated. These instruction devices implement one or more processes in the flowchart and / or functions described in one or more blocks in the block diagram.

  These computer program instructions may be loaded onto a computer or other programmable data device so that a series of operational steps are performed on the computer or other programmable device to perform computer processing. Is called. In this manner, instructions executed on a computer or other programmable device may cause steps to implement one or more processes in the flowchart and / or functions described in one or more blocks in the block diagram. provide.

  Although preferred embodiments of the present application have been described, those skilled in the art can make other variations or modifications to these embodiments once they understand the basic creative concepts. Accordingly, the appended claims should be construed to include the preferred embodiment and all variations and modifications that are within the scope of this application. Obviously, those skilled in the art can make modifications and variations without departing from the spirit and scope of the present invention. Therefore, when these modifications and variations of the present application are within the scope of the claims and the equivalent technique, the present application also covers these modifications and variations.

Although the embodiments described above have been described in some detail for ease of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not intended to be limiting.
Application Example 1: A system for generating processed web address information, wherein one or a plurality of processors receives a request for sharing a web page, and the request relates to at least the web page. Including first web address information and user ID information associated with the first user, wherein at least the first web address information and the user ID information associated with the first user Based in part on one or more processors configured to generate second web address information and present the second web address information; and connected to the one or more processors, And one or more memories configured to provide instructions to the one or more processors.
Application Example 2: The system according to Application Example 1, wherein the request further includes one or both of time information and a digital signature.
Application Example 3: The system according to Application Example 1, wherein the second web address information is configured to be sharable by the first user.
Application Example 4: The system according to Application Example 1, wherein the request further includes a selection regarding a sharing type.
Application Example 5: The system according to Application Example 4, wherein the one or more processors are further configured to share the second web address information based at least in part on the selection regarding the sharing type. Configured in the system.
Application Example 6: The system according to Application Example 1, wherein the one or more processors are further configured based on at least in part the user ID information associated with the first user. A system that is configured to determine whether the user is associated with a buyer status.
Application Example 7: The system according to Application Example 1, wherein the one or more processors further receive an indication regarding access to the second web address information by a second user and respond to the indication Retrieving the web page content associated with the second web address information, extracting the user ID information associated with the first user from the second web address information, and A system configured to send a prompt message to the second user including a control for adding the user as a friend.
Application Example 8: The system according to Application Example 7, wherein a message is sent to include the first user in the friend list of the second user when the control is activated. .
Application Example 9: The system according to Application Example 7, wherein the second web address information includes a digital signature, and the one or more processors further obtain the digital signature from the second web address information. A system configured to extract and verify the digital signature based at least in part on the user ID information associated with the first user.
Application Example 10: The system according to Application Example 7, wherein the second web address information includes time information, and the one or more processors further obtain the time information from the second web address information. A system configured to extract and perform time verification on the time information based at least in part on a predetermined effective sharing period.
Application Example 11: The system according to Application Example 7, wherein the one or more processors further retrieve the friend list of the second user before sending the prompt message to the second user. And the system is configured to determine whether the first user is included in the friend list of the second user.
Application example 12: The system according to application example 7, wherein the one or more processors are further associated with the second user before sending the prompt message to the second user. A system configured to retrieve user ID information and compare the user ID information associated with the second user with the user ID information associated with the first user.
Application Example 13: The system according to Application Example 7, wherein the one or more processors further include a first name list including ID information of a user who has already successfully activated the second web address information. To determine the number of add friend prompt messages sent in relation to the second web address information, and to determine the number of add friend prompt messages sent in relation to the second web address information. A system configured to compare to a first predetermined threshold.
Application Example 14: The system according to Application Example 7, wherein the one or more processors further include ID information of a user who has published web address information already activated by the second user. Retrieve the name list, determine the number of add friend prompt messages sent in relation to the second user, and set the number of add friend prompt messages sent in relation to the second user to the second A system configured to compare with a predetermined threshold of.
Application Example 15: A method of generating processed web address information, wherein a request for sharing a web page is received, and the request includes at least first web address information related to the web page, User ID information associated with the user, and based on at least in part the first web address information and the user ID information associated with the first user, a second web address Generating information and presenting the second web address information.
Application Example 16: The method according to Application Example 15, wherein the second web address information is configured to be sharable by the first user.
Application Example 17: The method according to Application Example 15, wherein the request further includes a selection regarding a sharing type.
Application example 18: The method of application example 17, further comprising sharing the second web address information based at least in part on the selection regarding the sharing type.
Application example 19: The method according to application example 15, wherein the first user is associated with a purchaser status based at least in part on the user ID information associated with the first user. Determining whether it has been or not.
Application example 20: The method according to application example 15, further comprising receiving a suggestion regarding access to the second web address information by a second user, and in response to the suggestion, the second web Retrieving web page content associated with address information, extracting the user ID information associated with the first user from the second web address information, and adding the first user as a friend Sending a prompt message including a control to the second user.
Application example 21: The method according to application example 20, wherein when the control is activated, a message is sent to include the first user in the friend list of the second user. .
Application example 22: The method according to application example 20, wherein the second web address information includes a digital signature, and the method further extracts the digital signature from the second web address information, and Performing verification on the digital signature based at least in part on the user ID information associated with a first user.
Application example 23: The method according to application example 20, wherein the second web address information includes time information, and the method further extracts the time information from the second web address information, Performing time verification on the time information based at least in part on the effective sharing period of the method.
Application Example 24: The method according to Application Example 20, wherein the first user is further retrieved before the prompt message is transmitted to the second user and the friend list of the second user is retrieved. Determining whether is included in the friend list of the second user.
Application Example 25: The method according to Application Example 20, wherein the user ID information associated with the second user is further retrieved before the prompt message is transmitted to the second user, Comparing the user ID information associated with a second user with the user ID information associated with the first user.
Application Example 26: Computer program product for generating processed web address information, wherein the computer program product is embodied in a computer readable storage medium and receives a request to share a web page And the request includes at least first web address information relating to the web page, user ID information associated with a first user, the first web address information, Computer instructions for generating second web address information based at least in part on the user ID information associated with the first user, and a computer for presenting the second web address information A computer program product comprising instructions.

Claims (24)

A system for generating a web address information processed,
One or more processors,
Receiving a request to share a web page, wherein the request includes at least first web address information about the web page and user ID information associated with the first user;
Wherein a first web address information, based on the said user ID information associated with the first user to generate a second web address information,
Presenting the second web address information to the first user ;
Receiving an indication regarding access to the second web address information by a second user;
In response to the suggestion, the user ID information associated with the first user is extracted from the second web address information;
Determining whether the first user has a merchant status based on the user ID information associated with the first user;
If the first user does not have a merchant status, send a prompt message to the second user including an approval button for adding the first user as a friend to a friend list;
One or more processors configured to not send the prompt message to the second user if the first user has merchant status ;
One or more memories connected to the one or more processors and configured to store instructions to be provided to the one or more processors;
A system comprising: The system of claim 1, wherein the request further includes one or both of time information and a digital signature regarding the time at which the request was made . A system according to claim 1, wherein the second web address information, Ru shareable der by the first user, the system. The system of claim 1, wherein the request further includes a sharing type from a sharing type including sharing on a blog, sharing on an instant message, sharing on a social network platform, and sharing on a microblog . System, including selection. A system according to claim 4, wherein the one or more processors is further based on the said selection for the shared type, are configured to share the second web address information, the system . A system according to claim 1, wherein the one or more processors, further the first based on the the user ID information associated with the user, the first user position purchaser A system that is configured to determine whether or not to have . A system according to claim 1, wherein when the approval button is clicked, the message to include the first user to the buddy list of the second user is transmitted, the system. The system of claim 1 , wherein the second web address information includes a digital signature, the one or more processors further extract the digital signature from the second web address information, and first based on the user ID information user associated with is configured to perform verification for the digital signature, the system. A system according to claim 1, wherein said second web address information time information, the one or more processors is further configured to extract the time information from said second web address information, web based on the predetermined effective sharing period showing a time limit condition of the address information is configured to perform verification of time for the time information, the system. The system of claim 1 , wherein the one or more processors are further configured to send the prompt message to the second user.
Search for the friend list of the second user,
A system configured to determine whether the first user is included in the friend list of the second user. The system of claim 1 , wherein the one or more processors are further configured to send the prompt message to the second user.
Search for user ID information associated with the second user,
Compare the user ID information associated with the second user with the user ID information associated with the first user to see if the first user should be added as a friend Configured as a system. The system of claim 1 , wherein the one or more processors further comprises:
Searching a first name list containing ID information of users who have already successfully activated the second web address information;
Determining the number of add friend prompt messages sent in connection with the second web address information;
A system configured to compare the number of add friend prompt messages transmitted in association with the second web address information to a first predetermined threshold. The system of claim 1 , wherein the one or more processors further comprises:
Searching for a second name list containing ID information of users who have published web address information already activated by the second user;
Determining the number of add friend prompt messages sent in relation to the second user;
A system configured to compare the number of add friend prompt messages transmitted in association with the second user to a second predetermined threshold. A method of generating a web address information to be processed,
Receiving a request to share a web page, wherein the request includes at least first web address information about the web page and user ID information associated with the first user;
Wherein a first web address information, based on the said user ID information associated with the first user to generate a second web address information,
Presenting the second web address information to the first user ;
Receiving an indication regarding access to the second web address information by a second user;
In response to the suggestion, the user ID information associated with the first user is extracted from the second web address information;
Determining whether the first user has a merchant status based on the user ID information associated with the first user;
If the first user does not have a merchant status, send a prompt message to the second user including an approval button for adding the first user as a friend to a friend list;
Not sending the prompt message to the second user if the first user has merchant status ;
A method comprising: The method of claim 14, wherein the second web address information, Ru shareable der by the first user, the method. 15. The method of claim 14 , wherein the request further includes a sharing type from a sharing type including sharing on a blog, sharing on an instant message, sharing on a social network platform, and sharing on a microblog . A method comprising selection. The method of claim 16, further comprising that based on the said selection for the shared type, sharing the second web address information, methods. The method of claim 14, further based on the the user ID information associated with the first user, whether the first user is associated to the buyer's position A method comprising determining. The method of claim 14, wherein when the approval button is clicked, the message to include the first user to the buddy list of the second user is transmitted, the method. 15. The method of claim 14 , wherein the second web address information includes a digital signature, the method further extracting the digital signature from the second web address information, and the first user. group Zui and the user ID information associated with provided that, to perform validation for the digital signature method. 15. The method according to claim 14 , wherein the second web address information includes time information, and the method further extracts the time information from the second web address information to obtain a predetermined effective sharing period. based in the comprises, performing verification of time for the time information, the method. 15. The method of claim 14 , prior to sending the prompt message to the second user,
Search the friend list of the second user,
Determining whether the first user is included in the friend list of the second user;
A method comprising: 15. The method of claim 14 , further prior to sending the prompt message to the second user,
Search for user ID information associated with the second user,
Compare the user ID information associated with the second user with the user ID information associated with the first user to see if the first user should be added as a friend about,
A method comprising: A computer program for generating a web address information to be processed,
A function for receiving a request to share a web page; and the request includes at least first web address information regarding the web page and user ID information associated with the first user;
Said first web address information, based on the said user ID information associated with the first user, a function for generating a second web address information,
A function for presenting the second web address information to the first user ;
A function for receiving an indication regarding access to the second web address information by a second user;
In response to the suggestion, a function for extracting the user ID information associated with the first user from the second web address information;
A function for determining whether the first user has a merchant status based on the user ID information associated with the first user;
If the first user does not have a merchant status, a prompt message including an approval button for adding the first user as a friend to a friend list is sent to the second user. Function and
A function not to send the prompt message to the second user if the first user has merchant status ;
A computer program that makes a computer realize.

Images