WO2001088722A1 - Systeme de distribution de donnees - Google Patents

Systeme de distribution de donnees Download PDF

Info

Publication number
WO2001088722A1
WO2001088722A1 PCT/JP2001/004051 JP0104051W WO0188722A1 WO 2001088722 A1 WO2001088722 A1 WO 2001088722A1 JP 0104051 W JP0104051 W JP 0104051W WO 0188722 A1 WO0188722 A1 WO 0188722A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
distribution
data
partner
information
Prior art date
Application number
PCT/JP2001/004051
Other languages
English (en)
Japanese (ja)
Inventor
Makoto Yamamoto
Original Assignee
Mtom Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mtom Inc. filed Critical Mtom Inc.
Priority to AU2001256752A priority Critical patent/AU2001256752A1/en
Publication of WO2001088722A1 publication Critical patent/WO2001088722A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions

Definitions

  • the present invention relates to a data transmission system, and particularly to securing a user.
  • An object of the present invention is to solve the above-mentioned problem and to provide a data transmission system capable of easily collecting users who can determine information desired to be received.
  • a data transmission system capable of easily collecting users who can determine information desired to be received.
  • a user data storage means for storing a category of information desired to be received for each user
  • Data distribution means for distributing the distribution data to a user registered in the specified category, when a distribution data in which a category for information distribution is specified is given from the information distribution application computer;
  • the user data storage means stores a partner identifier indicating that each user is an introduction registration by a partner
  • the data distribution unit determines whether or not the distribution data provided from the information distribution application computer includes a distribution designation to a user to which the partner identifier has been assigned, and determines whether the distribution data includes the partner. In the case where a distribution designation to a user to which an identifier is given is included, the distribution date is not distributed to the user.
  • A) User data storage means for storing the category of information desired to be received for each user
  • the user data storage means stores a partner identifier indicating that each user is an introduction registration by a partner
  • the overnight delivery means determines whether the overnight delivery provided from the information delivery application computer includes a delivery designation to a user to which a partner identifier has been assigned,
  • the delivery data includes a delivery designation to a user to which a partner identifier is assigned, an approval request is transmitted to the computer of the partner specified by the partner identifier of the user, and the approval is received. If the delivery data Deliver the evening,
  • the distribution data does not include the distribution specification to the user to whom the partner identifier is assigned, the distribution data is distributed to the specified user.
  • A) User data storage means for storing, for each user, a category of information desired to be received
  • the user data storage means stores a partner identifier indicating that each user is registered for introduction by a partner
  • Category number of users reply means, based on the partner identifier, determines whether the distribution application request is a request from the information distribution computer of any of the partners specified by the partner identifier,
  • the distribution application request is a request from an information distribution computer other than one of the partners specified by the partner identifier, a user to whom a partner identifier is not assigned is determined. Replying to the information distribution application computer the respective numbers, with the user to whom the partner identifier has been assigned as the undetermined user,
  • the distribution application request is a request from the information distribution computer of one of the partners specified by the partner identifier
  • a partner identifier is assigned to the category of the relevant partner.
  • the user who has not been assigned is the confirmed user
  • the user to whom the partner identifier of the partner is assigned is the in-house user
  • another partner identifier is assigned.
  • the data distribution means determines whether or not the distribution data provided from the information distribution application computer includes a distribution designation to an undetermined user.
  • the distribution data is undetermined. In the case of including the delivery designation to the user, an approval request is transmitted to the computer of the partner specified by the partner identifier of the undecided user, and if the approval is received, the delivery data is delivered;
  • a partner is recruited for each category, a partner identifier is assigned to a user introduced by the partner, and the partner is stored.
  • information distribution data specifying one or more categories is given, it is determined whether one or more partners exist in the specified category based on the partner identifier, and 1 or 2 If the above partners exist, the approval is requested on the computer managed by the one or more partners, and the given information is also delivered to the user introduced by the approved partner. .
  • An information distribution server is an information distribution server that distributes information to a user computer, wherein the information distribution server recruits partners for each category, and introduces a message introduced by the partner.
  • the information distribution server assigns and stores a partner identifier when information distribution data specifying one or more categories is provided from another computer connected to the network. It is determined based on the partner identifier whether or not there is one or more partners in the distribution data, and the distribution data includes a distribution designation to a user to which the partner identifier is assigned. If the distribution data does not exist, the distribution data is distributed to the designated user. If the distribution data includes distribution designation to the user to which the partner identifier is assigned, the partner identifier of the user is assigned. The distribution data is distributed to the user only when approved by the partner specified in.
  • FIG. 1 is a functional block diagram of a data distribution system according to the present invention.
  • FIG. 2 is a diagram showing an example of a hardware configuration in which the data delivery system of FIG. 1 is realized using CPU.
  • Figure 3 shows the data structure of the user master.
  • Figure 4 shows the general structure of the general company master.
  • Figure 5 shows the data structure of the partner company.
  • Figure 6 shows the data structure of the distribution management master.
  • Figure 7 shows the data structure of the distribution content management cell.
  • FIG. 8 shows an example of a screen displayed on the terminal.
  • FIG. 9 is a flowchart of the personal user registration processing program.
  • FIG. 10 shows an example of a screen displayed on the terminal.
  • FIG. 11 is a flowchart of the advertising company new registration processing program.
  • FIG. 12 is a flowchart of the advertisement distribution receiving processing program.
  • FIG. 13 shows an example of a screen displayed on the terminal.
  • FIG. 14 shows an example of a screen displayed on the terminal.
  • Figure 15 shows an example of a title that was delivered HTML.
  • Figure 16 shows an example of a partner content distribution screen.
  • Figure 17 shows an example of displaying the distributed information on the schedule management screen of an individual user.
  • Figure 18 shows an example of the approval confirmation screen.
  • FIG. 1 shows a data distribution system 1 according to the present invention, which includes a user data storage unit 3, a category-specific user number response unit 5, and a data distribution unit 7, and a distribution application request from an information distribution application combinator 9 Is received, for each of the users stored in advance, based on the category of the information desired to be received, the user according to the category is replied to the distribution application computer 9, and the information distribution category from the information distribution application computer 9 is When a specified delivery date is given, the data delivery system delivers the delivery date to a user registered in the specified category.
  • the user data storage unit 3 stores a partner identifier indicating the introduction registration by the partner for each user.
  • the category number of users reply unit 5 determines whether the distribution application request is a request from the information distribution computer of any of the partners specified by the partner identifier, based on the partner identifier. Perform the following processing. el) If the distribution application request is a request from an information distribution computer other than one of the partners specified by the partner identifier, a user to whom a partner identifier is not assigned is regarded as a confirmed user, and the partner identifier is The assigned user is returned as an unconfirmed user to the information distribution application computer 9 with the respective numbers.
  • the distribution application request is a request from the evening of the information distribution computer of any of the partners identified by the partner identifier
  • the category of the partner is not considered.
  • Information that a user to which a partner identifier is not assigned is a confirmed user, a user to which the partner identifier of the partner is assigned is an in-house user, and a user to which another partner identifier is assigned is an undetermined user.
  • the respective numbers are returned to the distribution application computer 9, and for the category that is not the partner, the user without the partner identifier is regarded as the confirmed user, and the user with the partner identifier is not As the confirmed user, the number is returned to the information distribution application computer 9.
  • the data distribution unit 7 determines whether or not the distribution data provided from the information distribution application computer 9 includes a distribution designation to an undetermined user. In the case where the distribution designation is included, an approval request is transmitted to the partner computer 11 specified by the partner identifier of the unconfirmed user, and if approval is received, the approval request is transmitted to the user computer of the unconfirmed user. Distribute the distribution data. I) If the distribution data does not include a distribution instruction to an undetermined user, distribute the distribution data to the user computer of the designated user.
  • the overnight distribution unit 7 may provide the event information to a schedule program of a distribution target user.
  • the information receiving section of each user is stored in the user data storage section 3, and the category-based number of users reply section 5 replies by dividing the number of users by category into the information receiving section. It may be.
  • the user data storage unit 3 stores the regional information of each user, and the category-specific user number response unit 5 further replies the number of users for each category and the number of users classified for each region. You may do so.
  • the information distributor can know the number of users in each category in advance. Further, 1) when the distribution data includes a distribution designation to an undetermined user, the partner of the undetermined user An approval request is sent to the partner of the partner identified by the identifier, and when the approval is obtained, the delivery data is delivered.2) The delivery data includes a delivery designation to an undetermined user. If not, the distribution data is distributed to the designated user. Therefore, even if each partner cooperates with the user registration, it can decide whether or not to approve the information distribution from other competing partners to the user who desires the information distribution. As a result, the introduction of users by partners can be promoted, and more users can be registered. 2. Hardware configuration
  • Fig. 2 shows an example of a hardware configuration that implements the data distribution system shown in Fig. 1 using a CPU.
  • the data distribution system 1 includes a CPU 23, a memory 27, a hard disk 26, a CRT 30, a CDD (CDROM drive) 25, a keyboard 28, a mouse 31, a communication board 32, and a bus line 29.
  • the CPU 23 controls each unit via the bus line 29 according to a program stored in the hard disk 26.
  • These programs are read from the CDROM 25 a storing the programs via the CDD 25 and installed on the hard disk 26.
  • a program such as a flexible disk (FD) or an IC card may be installed on the hard disk from a computer-readable recording medium in which programs are substantially integrated. Furthermore, you may make it download using a communication line.
  • the computer indirectly executes the program stored in the CD ROM.
  • the program stored in the CD ROM may be directly executed from the CD D 25.
  • programs that can be executed directly include those that can be directly executed simply by installing the software as it is, as well as those that need to be converted into other forms (for example, Decompression, etc.), and those that can be executed in combination with other module parts are also included.
  • the hard disk 26 has a program storage unit 26p, a distribution management data storage unit 26h, a user data storage unit 26u, and a company data storage unit 26k.
  • UNIX was used as the operating system (OS) program.
  • the program storage unit 26p stores an individual user registration processing program, an advertisement company new registration processing program, and the like, which will be described later.
  • the data stored on the hard disk will be briefly described.
  • the user data storage section 26u stores a user master file having a data structure as shown in FIG. 3 for each user. For each user, user ID, password for login, login URL, place of residence (prefecture), desired receiving location (prefecture), reception category area (prefecture), partner identification code as partner identifier, total The number of open data is stored.
  • a general company master file shown in FIG. 4 and a partner company master file shown in FIG. 5 are stored for each company.
  • the general company master file shown in Fig. 4 stores the company ID, password for login, login URL, company name, mail address, distribution category type, etc. for each company.
  • the partner company master file shown in Figure 5 contains, for each partner company, company ID, password for login, login URL, company name, e-mail address, distribution category type, number of company users by category, and company file by residence area.
  • the number of copies is stored.
  • the number of in-house users by region of residence is stored as the number of in-house users for each prefecture. You may be able to do it.
  • the distribution management data storage unit 26h stores the distribution content management master file shown in FIG. 7 for each content together with the distribution management master file shown in FIG.
  • the distribution management master file shown in Fig. 6 shows the distribution form (HTML distribution, e-mail distribution, mail distribution, etc.) for each category (in this case, six categories of Internet Z computer, news, entertainment, business, living information, and travel) Separately, the number of confirmed users, the number of partner company users, the name of partner company, and the number of regional users (by location and selected area) are stored separately.
  • HTML distribution refers to a distribution method in which each user is provided with a URL that refers to the list, and when the user logs in to such a URL with a browser program, the list is displayed. This means that the URL list is delivered to a mail address by e-mail, and mobile phone mail delivery means that the URL list is delivered to a user's mobile phone mail address by mail.
  • the distribution content management master file shown in FIG. 7 stores, for each content, a content ID, a company ID, a distribution category, a distribution category region, a total number of clicks, a content URL, and the like.
  • the personal user registration processing program will be described with reference to FIG.
  • the user who wants to register starts the browser program and specifies the URL for new registration via Internet.
  • the following describes the case where the user specifies a public site, for example, http: ⁇ www.mtom.co.jp/user/signup.html, rather than from a partner company site.
  • a screen as shown in FIG. 8 is displayed on the user computer.
  • the CPU 23 of the data distribution system 1 determines whether or not there is a new registration request (step S1). If there is a new registration request, it is determined whether or not the request has been sent via the URL of the partner company. Judge (step S3). Whether or not it was sent via the URL of the partner company should be determined, for example, by clicking the area 51 shown in Fig. 8 and transmitting the partner company identifier together. Can be. In this way, it is sufficient to distinguish between a new registration request from the partner company's site and a new registration request from the public site.
  • CPU 23 transmits a user registration screen (step S7 in FIG. 9).
  • the user registration screen as shown in Fig. 10 is displayed on the user computer. Is displayed. The user inputs necessary data into each input box, and when the input is completed, clicks the transmission button 53 with the mouse.
  • the CPU 23 determines whether or not there is a registration request (step S9 in FIG. 9), and upon receiving the registration request, determines whether or not the user is a referral user of the partner company (step S11). In this case, since it is not the introduction user of the partner company, the CPU 23 stores the transmitted registration data (step S15). Thus, the transmitted registration data is stored in the user master shown in FIG. The CPU 23 transmits a message screen indicating the login UR LID and password of the user (step S17). As a result, the message is displayed on the screen of the terminal (not shown). If there is a registration request in step S9, it is determined whether or not the ID has been dubbed. If the ID has been dubbed, the ID may be input again. '
  • step S3 If the new registration request is sent via the URL of the partner company, it is determined in step S3 that the request has been sent via the URL of the partner company, and is stored as the partner introduction user ( Step S5). Then, if there is a registration request, it is determined in step S11 that the user is a partner introduction user, and the partner identification code is also stored (see FIG. 3 user master reference HB).
  • CPU 23 determines whether there is a new registration request (Fig. 11 In step S21), when there is a new registration request, a new registration screen is transmitted (step S23). As a result, an image similar to that of the user registration (see Fig. 10) is displayed on the computer of the company that wants to publish the advertisement.
  • the person in charge of the advertising company inputs the required data into each input box, and clicks a transmission button (not shown) with a mouse when the input is completed.
  • the CPU 23 determines whether or not there is a registration request (step S29 in FIG. 11). When there is a registration request, the CPU 23 stores the transmitted registration data (step S31). ). As a result, the transmitted registration data is stored in the general company master shown in FIG. The CPU 23 transmits a message screen indicating the login URL, ID, and password of the advertising company (step S33). As a result, the above message is displayed on the screen of the terminal of the advertising company (not shown).
  • step S29 it may be determined whether or not the ID has been dubbed. If the ID has been dubbed, the ID may be input again.
  • the person in charge of the advertising company who wants to distribute the advertisement first performs the following login processing.
  • CPU 23 is a It is determined whether or not there is (step S43 in FIG. 12). This can be determined from, for example, the URL of the user or the ID. If the company that wants to publish the advertisement that has logged in is not a partner company, the estimated number of users in each category is determined with reference to the distribution management partner company master shown in FIG. 6 (step S69 in FIG. 12). The estimated user is a user introduced by a partner company in each category when there is a partner company other than the company desiring to place the advertisement. If a general company is a company that wants to advertise, the number of partner company users is the estimated number of users.
  • the CPU 23 generates an advertisement application screen and transmits the screen to a company desiring to publish an advertisement (step S47 in FIG. 12). Specifically, for each category, a screen specifying the number of confirmed users and the estimated number of users is generated and transmitted for each type of information reception desired for each user.
  • an advertisement application screen as shown in Fig. 13 is displayed on the computer of the company that wants to publish the advertisement.
  • the person in charge of the company that wants to place the advertisement should enter the title, body, and, if there is an image file to be attached, the image file, related URL, and the advertisement period of the advertisement (content).
  • the CPU 23 determines whether or not to receive the distribution data (step S49 in FIG. 12).
  • the check box of the estimated number of users is selected. It is determined whether or not it has been performed (step S51). This is because, in this system, the partner company can determine whether or not to distribute the advertisement to the estimated user by checking the contents. Details will be described later.
  • the CPU 23 transmits the advertisement delivery content to the content check computer (step S59).
  • This is to adhere to the basic policy of this system, which is to deliver the information of the category desired by the user.
  • the inspector examines the data displayed on the content check computer, and performs an approval process if there is no problem in the content. On the other hand, if some of the distribution destinations are inappropriate or if there is a problem with the content, a response is given to the effect that they will not be approved.
  • the CPU 23 determines whether or not the content has been approved by the content check computer (step S61). If the approval has not been received, the message "Delivery is not possible" is sent to the company that wants to publish the advertisement. (Step S65). At this time, if the inspector gives a reason why delivery is not possible, if some of the delivery destinations are inappropriate or if there is a problem in the content, the reason will be sent together with the message.
  • step S61 if the approval is obtained in step S61, the advertisement is delivered to the designated delivery destination in the designated delivery form (step S63).
  • advertisement distribution is performed as follows.
  • the advertisement distribution contents requested to be published in the distribution content management area shown in Fig. 7 are stored. Then, a URL storing the title of each distribution information and detailed distribution contents is transmitted to the designated distribution destination. If each user wants to check the content by referring to the distributed title, he or she can click on the title.
  • the title input on the advertisement insertion request screen shown in FIG. 13 is transmitted in a distribution form specified by the user.
  • Figure 15 shows an example of the display screen when the content is distributed in HTML format.
  • Each user sees the titles listed for each category, and if there is a title for which he wants to see more detailed information, he or she can click the title with the mouse. As a result, data with detailed information is transferred from the linked URL.
  • step S51 the CPU 23 sends an approval message to the corresponding partner company (step S51).
  • step S53 For example, if the check box of the estimated number of users in the category “news” is selected, an approval mail is sent to the partner company X 2 with reference to FIG.
  • the CPU 23 determines whether or not approval has been given to the approval mail (step S55), and if approved, adds the estimated user to the distribution destination (step S57) ).
  • the CPU 23 sends an approval message to all applicable partners and performs the same processing.
  • step S59 After the approval process by the partner is completed, the CPU 23 performs the processes of step S59 and subsequent steps.
  • the person in charge of the company desiring to publish the advertisement when the advertisement distribution application screen as shown in FIG. 13 is sent, is notified of the number of confirmed users and the estimated number of users.
  • the minimum number of distributions and the maximum number of distributions can be predicted for the information that the user uses for advertisement distribution.
  • the number of partner company users is the estimated number of users.
  • the estimated number of users can be obtained by adding the number of partner company users in each category.
  • the distribution destination can be specified by distribution form and category, but it is also possible to specify the distribution destination by region. For example, in the case of local shopping information, it is almost meaningless to distribute information nationwide.
  • step S43 of FIG. 12 if the company that wants to log in the advertisement is a partner company, the CPU 23 determines whether the partner company is a partner company shown in FIG. 5 and a distribution management partner company shown in FIG. With reference to the master, the number of in-house users of the partner is determined (step S47). For example, if partner company XI is a company that wants to publish advertisements, the number of users in each category is determined as follows.
  • the CPU 23 extracts the category in which the partner company XI is the partner company.
  • the partner company XI is a partner company for the category "Internet / computer”. Therefore, for the category “Internet computers”, the number of partner company users is the number of in-house users.
  • partner company X1 is not a partner company, its own user count is zero, and all are the estimated number of users. As a result, as shown in FIG.
  • the number of in-house users is “2 3 4 3 8” for HTML distribution, the estimated number of users is “0”, and the number of in-house users is 18 2 7 ”, the estimated number of users is“ 0 ”, and for mobile phone mail distribution, the number of in-house users is“ 2 2 2 3 ”and the estimated number of users is“ 0 ”.
  • the categories for which the company is not a partner company are the same as for general companies, and a description thereof will be omitted. In this way, image data for notifying the number of users as shown in FIG. 16 is generated.
  • the number of partner company users is stored for each partner company, and the number of users for partner companies other than the company is added to estimate the number of users. It can be a number.
  • an individual user upon user registration, an individual user is provided with an e-mail address and a homepage space, and a schedule management area and its management program are provided free of charge. Therefore, the individual user can grasp his / her own schedule only by accessing the URL for managing the schedule.
  • the content publication period specified by the company that wants to publish the advertisement in Fig. 13 is automatically added to the scheduling table in the schedule program. As a result, the delivered advertisement information can be more reliably transmitted to the user.
  • only the title may be displayed on the scheduling display screen, and when this is clicked, the hyperlinked content may be displayed.
  • FIG. 17 shows an example of the scheduling screen.
  • the title of the distribution information with the title "xx department bargain sale" is displayed on the screen in 3Z07 to 3Z09.
  • detailed data can be obtained.
  • the cumulative number of title clicks is counted for each user (see FIG. 3), and the number of titles is increased as shown in FIG. It is displayed as the number of This means that the cumulative number of title clicks is high, which means that users who look at the advertisement information that has been delivered are good.
  • the company that has requested the advertisement distribution when the user sees the actual content
  • the predetermined privilege may be, for example, giving authority to create a new category.
  • the company that has requested the advertisement distribution pays the advertisement fee only when the user actually sees the content. Therefore, distribution by category and distribution by region seems unnecessary at first glance. However, from the user's point of view, they may want to cancel user registration when they receive information on categories they do not want. In the present embodiment, since the contents are checked (see step S59 in FIG. 12), the above problem can be avoided.
  • selecting a category and each distribution mode allows the area to be further narrowed down. However, the area is first narrowed down, and then the category and Z or each distribution mode is selected. Is also good. In particular, when distributing information that is closely related to the region, it is convenient to be able to specify the region first. Furthermore, it is also possible to temporarily narrow down by any element of category, distribution form or region.
  • the determination of approval / disapproval of the estimated user step S55 in FIG. 12
  • the operator determines whether an approval email has been received from the person in charge and determines whether or not an input has been made. Alternatively, the determination may be made based on whether or not an e-mail including a predetermined description has been received. Also, the judgment can be made as follows.
  • the server stores data such that an image including the advertisement to be approved is displayed. Send an email with this URL to the person in charge of partner company X2.
  • an image containing an approved ad is displayed as shown in Figure 18.
  • the person in charge may select approval button 93 when approving, or non-approval button 94 when not approving.
  • the approval button 93 it is determined that the approval has been given, and the process of step S57 in FIG. 12 is performed. If a non-approval button is selected, it is determined that there is no approval, and the process of step S59 in FIG. 12 is performed.
  • image data is generated each time by a Java sublet.
  • whether or not the person in charge of the partner company has approved may send an e-mail to the inspector of the content check computer.
  • the inspector of the content check computer may judge whether or not the presumed user has been approved by the partner company as an approval item in step S61 of FIG.
  • URI Uniform Resource Identifier
  • the resource identifier is an identifier capable of identifying a resource for receiving image data displayed on a browser.
  • step S61 of FIG. 12 An example is described in which advertisement delivery is not performed unless all the advertisers have been approved in step S61 of FIG. 12. If it is a one-toner company, distribution may be performed without approval in step S61.
  • the approval pattern is classified as follows. 1) For users of a certain partner company, there is no check if the partner distributes them.2) For users who do not have any partner companies, the administrator in step S61 checks.3 ) For users of another partner company, check the partner company is there.
  • the distribution schedule frequency may be stored for each user.
  • a mopile terminal having a browser function such as an i-mode terminal of the NTT DOCOMO group is known today.
  • the browser programs installed on such mobile terminals are not HTML languages but compact HTML languages, HDML languages (handheld markup language), MML languages (mobile markup language), WML languages (wireless markup language), etc. Has adopted. In such a case, it is necessary to distribute data from the server for each language.
  • the distribution server side determines the type of browser written in the request header transmitted first by the browser program, and dynamically generates the language in the language for the browser program (the one generated in advance). (Including the case of conversion). For example, by using Oracle9i Application Server (Oracle9i Application Server) manufactured by Oracle Corporation, it is possible to support such a plurality of browsers.
  • the type of the user agent program may be determined and converted into a corresponding language.
  • the present embodiment when a new individual member is newly registered, whether a related partner exists or not is not input to the member but based on a registration request from the partner company's URL. This is determined by whether or not there is.
  • the present invention is not limited to this, and a list may be obtained from a partner company and registered.
  • OS operating system
  • the CPU 23 in order to realize the function shown in FIG. 1, the CPU 23 is used and this is realized by software. However, some or all of them may be realized by hardware such as a logic circuit.
  • the user data storage means stores a partner identifier indicating that each user is an introduction registration by a partner
  • the data distribution means includes: It is determined whether or not the delivery data provided from the information delivery application computer includes a delivery designation to the user to which the partner identifier has been assigned, and the delivery data is provided with the partner identifier. In the case where the distribution data is specified to the user, the distribution data is not distributed to the user. Therefore, even if each partner cooperates with the user registration, information delivery from other competing partners is not performed to the user who desires information delivery. As a result, the introduction of users by partners can be promoted, and more users can be registered.
  • the data distribution server upon receiving a distribution application request from the information distribution application computer, the number of users by category responds to the distribution application view by the number of users by category. Means. Therefore, the information distributor can know the number of users to whom information is distributed in each category in advance.
  • the user data storage means stores a partner identifier indicating whether or not each user is registered for introduction by a partner.
  • the distribution means determines whether or not the distribution data provided from the information distribution application computer includes a distribution designation to an undetermined user. And dl) if the delivery data includes a delivery designation to a user to which a partner identifier is assigned, sends an approval request to the partner computer specified by the partner identifier of the user. And transmitting the distribution data if approved.d2) If the distribution data does not include a distribution specification to a user assigned a partner identifier, the distribution data is transmitted. Distribute to specified users. Therefore, even if each partner cooperates with the user registration, it can determine whether or not to approve the user who wants to distribute information about the distribution of information from other competing partners. This encourages partners to introduce users, It is possible to register more users.
  • the user data storage means stores a partner identifier indicating whether or not each user has been introduced and registered by a partner. Determines whether the distribution application request is a request from the information distribution computer of any of the partners specified by the partner identifier, based on the partner identifier. And ei) if the distribution application request is a request from an information distribution computer other than one of the partners specified by the partner identifier, a user to whom no partner identifier is assigned is determined as a confirmed user The user to whom the partner identifier is assigned is regarded as an undetermined user, and the respective numbers are returned to the information distribution application computer.e2) The distribution application request of any of the partners specified by the partner identifier is returned.
  • the user to whom the partner identifier has not been assigned is the user to whom the partner identifier has not been assigned, and the user to whom the partner identifier of the partner has been assigned.
  • the in-house user and users with other partner identifiers as undetermined users
  • each number is returned to the information distribution application computer.
  • the user to whom the partner identifier is not assigned is regarded as a confirmed user, and the user to whom the partner identifier is assigned is regarded as an undecided user, and the information distribution application computer is referred to the computer. Reply each number.
  • the data distribution means determines whether or not the distribution data provided from the information distribution application computer includes a distribution designation to an undetermined user. In the case where the distribution is specified to the confirmed user, an approval request is transmitted to the partner computer specified by the partner identifier of the unconfirmed user, and when the approval is approved, the distribution data is distributed; f 2) If the distribution data does not include a designation for distribution to an undetermined user, distribute the distribution data to the designated user. Therefore, each part Even if they cooperate with user registration, they can decide whether or not to approve the user who wants to distribute information about the distribution of information from other competing partners. As a result, the introduction of users by partners can be promoted, and more users can be registered.
  • the distribution data distributed to each user is not the all distribution data provided from the information distribution application computer, but the title of the all distribution data and the all distribution. This is a resource identifier for acquiring data overnight. Therefore, since all information is distributed only when the user desires, it is possible to prevent useless information from being transmitted on the network line.
  • the data distribution means when the distribution data is event information including an information posting period, the data distribution means supplies the event information to a schedule program of a distribution target user. Therefore, the user can receive the event information only by each user activating the schedule program.
  • the user data storage unit stores an information receiving section of each user
  • the category number-of-users reply unit stores the number of users by category in the information. Responds will be received for each receiving category. Therefore, the information distributor can distribute information to the information receiving section desired to be distributed.
  • the user data storage unit stores regional information of each user
  • the category-based number-of-users reply unit stores the number of users by category. In addition, the number of users classified by region is returned. Therefore, the information distributor can distribute information to the area where the distribution is desired.
  • a partner is recruited for each category, a partner identifier is assigned to a user introduced by the partner and stored, and a network connection is established.
  • a computer gives an information distribution data specifying one or more categories, Determine whether there is one or more partners in the specified category based on the partner identifier, and if there is one or more partners, the one or more partners The approval is requested from the computer managed by the partner, and the given information is also distributed to the user introduced by the authorized partner. Therefore, even if each partner cooperates with the user registration, it can determine whether or not to approve the user who desires the information distribution for the information distribution from other competing partners. As a result, the introduction of users by partners can be promoted, and more users can be registered.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

Dans une unité (3) de stockage de données d'usager se trouve un identificateur de partenaire attribué à un utilisateur et enregistré sous l'URL du partenaire. Si l'ordinateur du partenaire n'envoie pas de demande d'application de distribution, l'unité de consultation (5) du nombre d'utilisateurs par catégorie (5) indique le nombre d'utilisateurs sans attribution d'identificateur de partenaire représentant le nombre d'utilisateurs spécifiés, et le nombre d'utilisateurs avec attribution d'identificateur représentant le nombre d'utilisateurs non spécifiés à un ordinateur (9) d'application d'informations de distribution. Si les informations de distribution envoyées par ledit ordinateur (9) contiennent la désignation de distribution à un utilisateur non spécifié, une unité (7) de distribution envoie une demande d'approbation à un ordinateur de partenaire identifié par l'identificateur de partenaire de l'utilisateur non spécifié. On peut ainsi rassembler facilement les utilisateurs d'objet auxquels l'information est distribuée.
PCT/JP2001/004051 2000-05-17 2001-05-15 Systeme de distribution de donnees WO2001088722A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001256752A AU2001256752A1 (en) 2000-05-17 2001-05-15 Data distribution system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2000145279 2000-05-17
JP2000-145279 2000-05-17

Publications (1)

Publication Number Publication Date
WO2001088722A1 true WO2001088722A1 (fr) 2001-11-22

Family

ID=18651808

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2001/004051 WO2001088722A1 (fr) 2000-05-17 2001-05-15 Systeme de distribution de donnees

Country Status (2)

Country Link
AU (1) AU2001256752A1 (fr)
WO (1) WO2001088722A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS63146538A (ja) * 1986-12-10 1988-06-18 Hitachi Ltd 電子メ−ル発信制御方式
JPH0556097A (ja) * 1991-08-22 1993-03-05 Chubu Nippon Denki Software Kk 通信システムにおける送信承認方式
JPH06205043A (ja) * 1993-01-04 1994-07-22 Toshiba Corp メッセージ発信承認システム
JPH0991358A (ja) * 1995-09-28 1997-04-04 Fujitsu Ltd 情報提供装置および方法
JPH10301869A (ja) * 1997-04-28 1998-11-13 Matsushita Electric Ind Co Ltd 電子メール装置
JPH11345182A (ja) * 1998-03-31 1999-12-14 Nec Corp 電子メ―ル送受信システム、電子メ―ル送受信方法および電子メ―ル送受信プログラムを記録した記録媒体

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS63146538A (ja) * 1986-12-10 1988-06-18 Hitachi Ltd 電子メ−ル発信制御方式
JPH0556097A (ja) * 1991-08-22 1993-03-05 Chubu Nippon Denki Software Kk 通信システムにおける送信承認方式
JPH06205043A (ja) * 1993-01-04 1994-07-22 Toshiba Corp メッセージ発信承認システム
JPH0991358A (ja) * 1995-09-28 1997-04-04 Fujitsu Ltd 情報提供装置および方法
JPH10301869A (ja) * 1997-04-28 1998-11-13 Matsushita Electric Ind Co Ltd 電子メール装置
JPH11345182A (ja) * 1998-03-31 1999-12-14 Nec Corp 電子メ―ル送受信システム、電子メ―ル送受信方法および電子メ―ル送受信プログラムを記録した記録媒体

Also Published As

Publication number Publication date
AU2001256752A1 (en) 2001-11-26

Similar Documents

Publication Publication Date Title
JP3967589B2 (ja) 広告配信方法及び広告配信装置
Reagle et al. The platform for privacy preferences
US7797241B2 (en) Global information network product publication system
US8086746B2 (en) Delivering electronic content
JP2002132822A (ja) インターネット広告配信システム及びインターネット広告配信方法
WO2000052900A1 (fr) Systeme d'interface internet
KR100954142B1 (ko) 정보 배신 방법, 서버 및 프로그램 기록매체
JP4383440B2 (ja) 広告方法及び広告装置
JP2002109379A (ja) 電子情報の流通管理方法、システム、記録媒体、プログラム信号
US7526435B1 (en) Information offering system automating registration of advertisement information on home pages
WO2001088722A1 (fr) Systeme de distribution de donnees
JP3935362B2 (ja) 広告方法及び広告装置
JP4527748B2 (ja) 状態配信方法及び状態配信装置
KR20010111690A (ko) 전자메일 마케팅 서비스 대행 방법
CA2422878C (fr) Systeme et procede correspondant facilitant les echanges de demandes d'information
JP2005165394A (ja) アクセス経路追跡システムおよびこれを用いたアフィリエイトシステム並びにアクセス経路追跡方法
KR100431555B1 (ko) 메신저를 이용한 정보제공 방법
JP2003005640A (ja) 公開鍵証明書処理装置および方法
JP5064650B2 (ja) 電子メール送信システム
JP2002175325A (ja) 広告配信システム
JP2001195506A (ja) 参照状況出力システム、参照状況出力方法及び参照状況出力プログラムを記録した記録媒体
JP2002183047A (ja) 電子メール、電子メール送信システム、意志確認方法及びシステム並びに意志収集方法及びシステム
JP2005208970A (ja) 会員情報管理システム
JP2001306418A (ja) 逆クリック保証の可能な広告付きメール配信システム
JP2002149556A (ja) インターネット伝言板サービス

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP