WO2016157240A1 - Management server for managing online shopping portal sites, control method therefor, and computer program - Google Patents

Management server for managing online shopping portal sites, control method therefor, and computer program Download PDF

Info

Publication number
WO2016157240A1
WO2016157240A1 PCT/JP2015/001786 JP2015001786W WO2016157240A1 WO 2016157240 A1 WO2016157240 A1 WO 2016157240A1 JP 2015001786 W JP2015001786 W JP 2015001786W WO 2016157240 A1 WO2016157240 A1 WO 2016157240A1
Authority
WO
WIPO (PCT)
Prior art keywords
store
access
management server
information
virtual store
Prior art date
Application number
PCT/JP2015/001786
Other languages
French (fr)
Japanese (ja)
Inventor
あい 河津
紗佑里 星川
真吾 伊勢路
瑛逸 ▲高▼橋
Original Assignee
楽天株式会社
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 楽天株式会社 filed Critical 楽天株式会社
Priority to JP2015532231A priority Critical patent/JP5848496B1/en
Priority to PCT/JP2015/001786 priority patent/WO2016157240A1/en
Priority to TW105109734A priority patent/TWI596557B/en
Publication of WO2016157240A1 publication Critical patent/WO2016157240A1/en

Links

Images

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 management server that manages an online shopping portal site, a control method thereof, and a computer program.
  • Patent Document 1 discloses a method for presenting a campaign based on a user's behavior history.
  • the present invention has the following configuration. That is, a first portal site for online shopping that provides access to a plurality of virtual stores, and access to some virtual stores having a specific attribute among the plurality of virtual stores, and the identification
  • a management server that manages a second portal site having the following attributes: Management means for managing store information including attribute information of the virtual store and site information including information of the specific attribute of the second portal site;
  • a first accepting unit that accepts an access provision application for requesting access to the virtual store in the second portal site from any one of the plurality of virtual stores;
  • the virtual store that has made the access provision application has the specific attribute based on the store information and the site information managed by the managing unit.
  • Determination means for determining whether or not, When the determination unit determines that the virtual store that has applied for the access provision has the specific attribute, the management unit stores the store information of the virtual store that has applied for the access provision, and the second portal site Updating to indicate that access to the virtual store is provided.
  • a management server that provides and manages a product that is required by a user and a portal site that is easy to find a store that handles the product. it can.
  • the accompanying drawings are included in the specification, constitute a part thereof, show an embodiment of the present invention, and are used to explain the principle of the present invention together with the description.
  • the flowchart of the customer user registration process which concerns on this invention. Flow chart of unique portal participation processing according to this embodiment
  • each store is displayed in principle to be accessible to all customer users on the portal site, and the customer user can freely access the store site.
  • a portal site opened to all customer users is referred to as a “general portal” in this specification.
  • products, etc.” the nature of the products and services they handle
  • target narrow down a predetermined customer segment
  • sales campaigns and advertisements sometimes you want to be notified.
  • consumables for infants (baby goods) such as diapers and powdered milk are products that require little appeal to customer users who are not raising children. I want to be notified selectively (by targeting).
  • the customer user side also has the freedom to freely access a large number of stores in the general portal, but must select a store that handles products he / she is interested in from a huge number of stores. There is a burden of store selection that must be done. Under such circumstances, customer users often have a desire to obtain notifications from stores that have not been used.
  • the campaign provided by the store includes issuance of coupons that can be used at the time of product purchase and free shipping.
  • an attribute is given to each of a customer user, a store, and a product handled in the store.
  • the attribute is information related to the customer user or the store, and may be any information as long as it can classify the customer user and the store. For example, if you are a customer user, age (age), gender, birthplace, location (home address, work address), occupation, interest, as well as rate plans and restrictions on infrastructure services provided by the management server, membership type, etc. Can be included.
  • information such as the location of the store, the classification of the products handled by the store (books, clothing, food), the classification of the store (bookstore, clothing store, grocery store, etc.) can be included.
  • an example of the attribute given to a store or a customer user is as shown in FIG.
  • the attributes may be newly defined by the store user or the customer user in addition to those prepared in advance on the infrastructure service providing side. For example, when a new product or service is born, the name or the like may be defined as a new attribute.
  • a set in which one or more attributes as described above are associated is referred to as a “segment”. And the customer user and store which have the attribute linked
  • the above-described general portal does not limit the attributes of stores and customer users, and does not limit access from customer users.
  • access control is performed so that only a customer user having an attribute associated with a corresponding segment can access.
  • stores that can participate in the unique portal are also limited to stores that have an attribute associated with a segment or that handle products or the like that have an attribute associated with a segment.
  • “participation” means that a store becomes accessible from a customer user through a specific portal where the store is located, or that an arbitrary advertisement or campaign is displayed. At this time, a store participating in a specific portal can display the details of the event on the specific portal associated with the segment by setting and registering the event for the segment.
  • FIG. 1 is a diagram illustrating an example of the overall configuration of a system according to the present embodiment.
  • a management server 101 a store PC 102, and a customer PC 103 are connected via the Internet 104.
  • the management server 101 is an information processing apparatus that provides an infrastructure as a basis for an online shopping service to a store user and a customer user via the store PC 102 and the customer PC 103, respectively.
  • an online shopping service can be provided by a store user who provides products and the like registered as an online store.
  • each store is first registered in a general portal and is accessible to all customer users.
  • the store PC 102 is an information processing device used by store users.
  • the customer PC 103 is an information processing apparatus handled by a customer user who uses an online shopping service.
  • the store PC 102 and the customer PC 103 may be desktop PCs or mobile terminals such as smartphones and tablets.
  • Each user accesses a general portal provided by the management server 101 via a Web browser (not shown) provided in the store PC 102 or the customer PC 103.
  • the connection from each PC to the Internet 104 may be wired or wireless. In FIG. 1, one device is shown, but a plurality of devices may be connected.
  • FIG. 2 shows a hardware configuration example of each information processing apparatus included in the system according to the present embodiment.
  • a general information processing apparatus will be described as an example, but other configurations may be provided.
  • the information processing apparatus 200 includes a CPU 201, a RAM 202, a ROM 203, an HDD 204, a display IF 205, a display unit 206, an input IF 207, an input unit 208, and an NW IF 209. Each component is communicably connected via the bus 210.
  • the CPU 201 controls the entire processing of the information processing apparatus 200, and implements various processes by reading various programs stored in the ROM 203 and the like into the RAM 202 and executing them.
  • the RAM 202 is a volatile storage area and is used for applications such as work memory when various programs are executed.
  • the ROM 203 is a non-volatile storage area and stores various programs used for processing.
  • the HDD 204 is a non-volatile storage area that stores and holds processing results and the like.
  • the HDD 204 only needs to be a nonvolatile large-capacity storage area, and may be configured by a semiconductor memory such as a flash memory in addition to the hard disk.
  • the display IF 205 is connected to the display unit 206 and performs display control of the display unit 206.
  • the display unit 206 is a display such as a liquid crystal display, and displays a processing result and various user interface screens (UI screens) described later.
  • the display unit 206 may be configured to be externally attached to the information processing apparatus 200, and in that case, the display unit 206 is connected to the information processing apparatus 200 via the display IF 205.
  • the input IF 207 is connected to the input unit 208 and receives an instruction from the input unit 208 based on a user operation.
  • the input unit 208 is, for example, a keyboard or a mouse (not shown), and is used when a user performs an input operation. Note that a touch panel in which the display unit 206 and the input unit 208 are integrated may be used.
  • the NW IF 209 connects to an external network such as the Internet 104.
  • the connection form here may be either wired or wireless.
  • FIG. 3 is a diagram illustrating a software configuration example of the management server 101 according to the present embodiment.
  • the software shown here is stored as a program in a storage unit (ROM 203, HDD 204, or the like) included in the management server 101, and is read out and executed by the CPU 201 of the management server 101, thereby realizing various controls and processes.
  • the customer user management unit 301 manages user information of customer users who use the online shopping service.
  • the customer user information has, for example, the configuration shown in FIG. 4A and will be described in detail later.
  • the store management unit 302 manages store information related to each online store setting registered by a store user.
  • the store information has, for example, the configuration shown in FIG. 4B and will be described in detail later.
  • the segment management unit 303 generates and registers various segments in response to requests from store users.
  • the segment generation unit 303 performs processing such as editing, merging, and management of the registered segment.
  • the segment information has, for example, the configuration shown in FIG. 4C and will be described in detail. A detailed description and processing flow regarding the segment will be described later.
  • the UI control unit 304 provides a UI screen corresponding to a request from each PC according to various settings.
  • An example of the UI screen is as shown in FIGS. 11A to 11G.
  • the customer user authentication unit 305 performs login control of a customer user who has accessed the online shopping site. Specifically, authentication information (user name and password) input by the customer user is received, and authentication processing is performed based on the user name and password information managed by the customer user management unit 301. The customer user authentication unit 305 also performs control when each customer user accesses the unique portal.
  • the store authentication unit 306 performs authentication processing for access from store users. The authentication here may be performed in the same manner as the customer user authentication, or a separate authentication method may be used. The store authentication unit 306 also performs participation processing when a request for participation in the unique portal is made from the store side. Details of this processing will be described later.
  • the search unit 307 searches for information on customer users belonging to the segment.
  • the information searched here corresponds to the number of customer users belonging to a segment, for example.
  • the product management unit 308 manages product information handled by each store in association with the store. As for product information, registration of products handled by the store is accepted. At this time, if it is a commodity or the like that is generally sold, the management server 101 may register in advance so that the store user can select it.
  • the merchandise information has, for example, the configuration shown in FIG. 4D, and details will be described later.
  • the event management unit 309 accepts and manages registration of various events (campaigns, advertisements, etc.) in response to a registration request from a store.
  • the event information has, for example, the configuration shown in FIG. 4E and will be described in detail later. Examples of events registered here include those notified by a general portal and events notified only within a specific portal. Details of the event registration process will be described later.
  • the transaction management unit 310 manages information on sales transactions such as products between the customer user and the store.
  • the information on the sales transaction has, for example, the configuration shown in FIG. 4F and will be described in detail later.
  • [Data structure] 4A to 4F are diagrams illustrating examples of the configuration of various data managed by the management server 101 according to the present embodiment. Each data shown here is assumed to be held in an internal or external storage area managed by the management server 101. Each piece of information shown below may be managed in one table, or may be divided into a plurality of tables and managed.
  • FIG. 4A shows a data configuration example of customer information related to a customer user.
  • the customer information includes, for example, a customer ID, a user name, a password, a customer attribute, and a participation segment.
  • the customer ID is an ID (identification information) for uniquely identifying a customer user.
  • the user name is its own name used by the customer user on the site, and is also used as a login name when the customer user logs in to various UI screens for the customer user.
  • the password is used for authentication when the customer user logs in to various UI screens for the customer user provided by the management server 101.
  • Customer attributes include information on the above customer users (age (age), gender, hometown, location (home address, work address), occupation, interest, rate plan and restrictions, membership type (silver member, gold member, diamond) Member etc.)).
  • the participation segment indicates information on a segment corresponding to a unique portal accessible by the customer user.
  • FIG. 4B shows a data configuration example of store information related to a store.
  • the store information includes, for example, store ID, store name, password, store attribute, product ID, participation segment, and participation mode information.
  • the store ID is an ID (identification information) for uniquely identifying the store.
  • the store name is the name of the store used in the general portal and the unique portal. It is also used as a login name when a store user logs in to various UI screens for store users.
  • the password is used for authentication when the store user logs in to various UI screens provided by the management server 101 for the store user.
  • the store attributes include information such as the classification of products handled by the above-described stores and the classification of stores.
  • the product ID indicates identification information (ID) for uniquely identifying product information handled by the store.
  • the participation segment indicates information on a segment to which the store belongs.
  • the participation form includes information on a form in which the store participates in the segment. As will be described later, there are a “store type” that participates as a whole store and a “product type” that participates for each product.
  • store type all product information handled by the store is registered in the product ID, or link information to another table that manages all the product information is registered.
  • product type information on the product targeted for participation is registered in the product ID.
  • FIG. 4C shows a data configuration example of segment information.
  • the segment information includes, for example, a segment ID, a created store, merge availability, a segment name, a segment attribute, and a participating store.
  • the segment ID is an ID (identification information) for uniquely identifying a segment.
  • the created store the store ID of the store that created the segment is set. If it is a segment generated by the management server 101, this is indicated.
  • “Mergeability” indicates a setting of whether similar segments can be merged. Details of merge permission / inhibition information and its usage will be described in the second embodiment.
  • the segment name indicates the name of the segment.
  • the segment attribute indicates an attribute for specifying a customer user (target) belonging to the segment.
  • the segment attribute can be used to determine whether the customer user is a user belonging to the segment, i.e., a customer user who can access the unique portal corresponding to the segment. It can also be used to extract potential customer users who can access the specific portal.
  • the attribute registered in the segment attribute is compared with the attribute registered in the customer information table shown in FIG. 4A. For example, USER A in FIG. 4A has a customer attribute of male, 30s, and a gold member, and matches the segment attribute of segment A and has the eligibility to participate. USER A actually registers segment A as a participating segment.
  • the segment attribute can be used when specifying a segment (unique portal) in which the store can participate. For example, when a store applies for participation in a unique portal, whether or not to permit participation is determined by comparing the content of the store attribute given to the store with the segment attribute of the unique portal.
  • a store wants to conduct a new event, such as a campaign, for a unique portal associated with a segment it determines whether registration is possible based on attribute relationships when applying for event registration. be able to.
  • a participating store indicates a store participating in a unique portal corresponding to the segment.
  • the store ID of the store is shown.
  • the stores indicated in the participating stores can register events in a unique portal corresponding to the segment.
  • FIG. 4D shows a data configuration example of product information of products handled by each store.
  • the goods here may be books, stationery, foods, or services such as accommodation reservations, golf course reservations, and multimedia downloads.
  • the term “product” will be collectively referred to regardless of the distinction between goods and services.
  • the merchandise information includes, for example, a merchandise ID, a merchandise name, a store ID, and a merchandise attribute.
  • the product ID is an ID (identification information) for uniquely identifying the product, and corresponds to the product ID registered in the store information table of FIG. 4B.
  • the product name is a general distribution name of the corresponding product.
  • the store ID is the store ID of the store that handles the product, but the relationship between the product and the store can be specified in FIG.
  • the product attribute is information indicating a product category, a target (target), and the like. For example, if the product is a garment, information such as the type and name of the garment (T-shirt, sweater, etc.), the gender, size, price, availability of coupon, product description, product photo, etc.
  • FIG. 4E shows a data configuration example of event information for managing a campaign for a customer user set by a store, notification of a unique product, etc. (hereinafter collectively referred to as “event”).
  • the event information includes, for example, an event ID, an event name, a store ID, a segment ID, a notification period, and event contents.
  • the event ID is an ID (identification information) for uniquely identifying the event.
  • Store ID shows store ID of the store which participates in an event.
  • the event may be performed for each store or may be performed in common for stores participating in the unique portal. In the latter case, the same event ID is assigned to a plurality of store IDs. For example, if the event is performed only at a certain store, the store registers the event.
  • a plurality of stores may be specified when the event is registered, or may be specified in units of segments (unique portals). Furthermore, you may make it accept participation hope from the store side.
  • the event name is a name given to the event.
  • the segment ID indicates the segment ID of the segment that is the event notification destination (target). Customer users belonging to the segment specified here are treated as event notification destinations (targets).
  • the notification period indicates a period during which an event is notified to a customer user, that is, a period during which the event is being performed. During the period specified here, for example, notification of an event is performed on a predetermined UI screen of a specific portal.
  • the event content indicates the detailed content of the registered event.
  • Types of events include, for example, issuing coupons that can be used as cash vouchers when purchasing shopping at the store, and issuing free shipping coupons that free shipping when shopping at the store.
  • the contents here may be finely set by the store user, or options that can be set in advance on the management server 101 side may be prepared. Further, it may be an advertisement or notification for an individual product (product unit), or may be an advertisement or notification for the entire store (store unit).
  • FIG. 4F shows a data configuration example of transaction information for managing information on sales transactions (use history) performed between a store and a customer user.
  • the transaction information includes, for example, a transaction ID, a seller, a buyer, a date and time, and a transaction content.
  • the transaction ID is an ID (identification information) for uniquely identifying a transaction.
  • the seller indicates seller information such as products in the transaction.
  • the store ID of the store that is the seller is shown.
  • the buyer indicates buyer information such as products in the transaction.
  • the customer ID of the customer user who is the purchaser is shown.
  • the date / time indicates date / time information on the transaction.
  • Information such as purchased products, purchased stores, and access history is included.
  • the transaction content indicates the type and number of products used for the transaction, other optional information, and the like.
  • FIG. 5 shows a processing flow when the store user accesses the management server 101 from the store PC 102 and makes a store registration application to the management server 101.
  • a store is opened and disclosed on a general portal. Thereby, the customer user can access the store registered on the general portal.
  • This processing flow is realized by the CPU of each of the management server 101 and the store PC 102 reading and executing a program stored in a storage unit such as an HDD.
  • a storage unit such as an HDD.
  • the store PC 102 has a Web browser (not shown).
  • the store PC 102 accesses the management server 101 using HTTP (Hyper Text Transfer Protocol) or the like via a Web browser, and displays various UI screens provided by the management server 101.
  • HTTP Hyper Text Transfer Protocol
  • the store PC 102 accesses the management server 101 based on an instruction from the store user and requests store registration.
  • the store user can access the initial screen (FIG. 11A) provided by the management server 101 and make a store registration request from there.
  • FIG. 11A shows a configuration example of an initial screen (general portal) when accessed from each PC.
  • a login screen and a link for registering a store are displayed.
  • the link can be selected to obtain a store registration screen.
  • a store search, a list of products handled at each store, and the like are displayed.
  • the store user selects the link, thereby transitioning to a registration screen.
  • the configuration of the portal screen is not limited to this, and the portal screen may be provided on a plurality of screens according to functions.
  • the management server 101 provides a store registration screen (FIG. 11B) as a response to the store registration request from the store PC 102.
  • FIG. 11B shows a configuration example of a store registration screen when registering a store in response to a request received from the store PC 102.
  • store registration for example, store name, product, owner information, and attribute information can be input.
  • the input store name, attribute, and product information are managed as store name and store attribute information registered in the table shown in FIG. 4B and product attribute information shown in FIG. 4D.
  • each product may be registered on a dedicated UI screen (not shown) after store registration.
  • the store PC 102 displays the store registration screen provided from the management server 101 on the Web browser, and accepts input of various store information from the store user. Thereafter, when the input is completed, the store PC 102 transmits the input store information to the management server 101. At this time, product information such as products handled in the store may be registered together.
  • the input product is registered in the table shown in FIG. 4D.
  • the management server 101 registers the product via the product management unit 308. Moreover, you may enable it to register the information of the 1 or several shop attribute linked
  • the management server 101 when the management server 101 receives the store information from the store PC 102, the management server 101 issues information such as a store ID and a password, and registers it in the table shown in FIG. 4B together with the store information.
  • the management server 101 notifies the store PC 102 of the issued information together with the registration completion notification.
  • store PC 102 receives the information transmitted from management server 101 and displays the information. Thereafter, this processing flow ends.
  • FIG. 6 shows a processing flow when a customer user accesses the management server 101 from the customer PC 103 and performs user registration.
  • This processing flow is realized by the CPU of each of the management server 101 and the customer PC 103 reading and executing a program stored in the HDD or the like.
  • the customer PC 103 has a Web browser (not shown), accesses the management server 101 via the Web browser, and displays various UI screens provided by the management server 101.
  • the customer PC 103 accesses the management server 101 based on an instruction from the customer user and requests user registration.
  • the management server 101 provides a customer user registration screen (FIG. 11C) as a response to the user registration request from the customer PC 103.
  • FIG. 11C shows a configuration example of a customer user registration screen when registering a customer user in response to a request received from the customer PC 103.
  • information such as a user name, date of birth, contact information, attribute, password, and segment designation can be input.
  • personal information such as gender, birthplace, location (home address, work address), occupation, and interest can be entered.
  • the input user name, password, and personal information are managed as, for example, the user name, password, and customer attribute registered in the table shown in FIG. 4A.
  • the customer PC 103 displays the customer user registration screen provided from the management server 101 on the Web browser, and accepts input of various user information from the customer user. Thereafter, when the input is completed, the customer PC 103 transmits the input user information to the management server 101. At this time, one or more attribute information associated with the customer user can be registered. Furthermore, the customer user can select an arbitrary segment from the segments related to his / her attributes and specify whether or not to apply for participation. Alternatively, for example, segments may be automatically allocated on the management server 101 side according to the price plan and the attributes of the customer user. As described above, a customer user who is assigned a segment can access the unique portal corresponding to the segment.
  • the management server 101 when receiving the user information from the customer PC 103, issues information such as a customer ID and registers the user information in the table shown in FIG. 4A.
  • approval determination and authentication are performed as to whether participation in the segment selected by the customer user is possible.
  • the segment information is registered in the participation segment of FIG. 4A.
  • the details of the participation approval determination and authentication processing here may be performed in accordance with, for example, the correspondence relationship between the attribute of the customer user, the attribute of the product purchased in the past, and the attribute of the segment. For example, only a customer user who has purchased a product having an attribute corresponding to the attribute of the segment may be able to participate in the segment. By this processing, participation in a segment unrelated to the customer user can be prevented.
  • the management server 101 notifies the customer PC 103 of the issued information together with the registration completion notification.
  • the customer PC 103 receives the information transmitted from the management server 101 and displays the information. Thereafter, this processing flow ends.
  • FIG. 7 shows a processing flow when the store user accesses the management server 101 from the store PC 102 and applies for participation in the unique portal corresponding to the already set segment.
  • This processing flow is realized by the CPU of each of the management server 101 and the store PC 102 reading and executing a program stored in the HDD or the like.
  • the store management unit 302 On the management server 101 side, the store management unit 302, the segment management unit 303, the UI control unit 304, and the store authentication unit 306 shown in FIG. Further, the store PC 102 has a Web browser (not shown), accesses the management server 101 via the Web browser, and displays various UI screens provided by the management server 101.
  • the store PC 102 accesses the management server 101 based on an instruction from the store user and requests participation in the unique portal. At this time, it is assumed that the store is already registered in the management server 101 and the authentication by the store authentication unit 306 using a password or the like has been completed.
  • the management server 101 provides a unique portal participation screen (FIG. 11D) as a response to the participation request to the unique portal from the store PC 102.
  • FIG. 11D shows a configuration example of a unique portal participation screen when participating in a unique portal (segment) in response to a request received from the store PC.
  • a request for participation can be made by designating a segment associated with a specific portal that the store wants to participate in or a specific portal itself.
  • a list of segments that can participate may be displayed in a selectable manner.
  • the store user may input an attribute, display a unique portal associated with a segment having the input attribute, and accept a selection input from the store user.
  • the store user can select a participation form on the screen of FIG. 11D.
  • a form of participation in the unique portal there are a store-type form that participates as a whole store and a product-type form that participates for each product handled by the store.
  • store type is selected as the participation form
  • product type is selected as the participation form
  • the selection of the product may be a method of specifying individual products, or a method of specifying the type or genre of the products.
  • the store is a drug store
  • paper diapers and powdered milk can be individually specified as products, but a type including baby products and these individual products can also be specified.
  • the information set here is registered in the store information as the product ID, participation segment, and participation form information of FIG. 4B.
  • the store PC 102 displays the unique portal participation screen provided from the management server 101 on the Web browser, and accepts input of information on the specific portal (segment) to be participated from the store user. Thereafter, the store PC 102 transmits information on the selected unique portal to the management server 101.
  • UI screen display control may be performed so that unique portals (segments) that cannot participate are not displayed from the beginning.
  • the unique portal that cannot participate is a unique portal that does not have the attribute of the segment associated with the unique portal, or the product that the store handles. In this case, since the store does not have the qualification to participate in the unique portal, it is desirable to exclude it from the options in advance. Alternatively, in order to provide motivation for future participation, it may be included in the list display, but may be excluded from the selection target by being grayed out.
  • S ⁇ b> 704 when the management server 101 receives selection of a unique portal from the store PC 102, the management server 101 performs approval determination and authentication as to whether or not the store can participate in the selected unique portal.
  • participation is permitted in S704
  • the information of the segment of the specific portal permitted to participate is registered in the participation segment of FIG. 4B, and the information of the store is registered in the participating store shown in FIG. 4C.
  • the management server 101 confirms the input content and participates.
  • the approval judgment for example, the authority of the store (infrastructure service use plan by the store) and the rules, the correspondence between the segment and the attribute associated with the unique portal, or the attribute of the product handled by the store, etc. You may make it carry out according to.
  • a condition for participating in the unique portal it may be requested that there is a transaction record with the customer user registered in the unique portal, and the evaluation of the store has obtained a certain level of evaluation. You may request that.
  • the presence / absence of transaction results can be determined by referring to the transaction information in FIG. 4F.
  • Whether or not there is a track record is not limited to simply having a track record, but a threshold is set according to the number of customer users registered in the unique portal. You may make it request
  • the thresholds are set lower by relaxing the transaction performance conditions, while for newly established unique portals, sales performance of products and services corresponding to segment attributes, Or it is good also as conditions that there are many transaction results with the customer user who has the said attribute.
  • the management server 101 transmits a notification of completion of the participation process to the unique portal to the store PC 102.
  • the store PC 102 receives a notification of completion of the process of participating in the unique portal from the management server 101, and displays that effect. Thereafter, this processing flow ends.
  • FIG. 8 shows a processing flow when the store user accesses the management server 101 from the store PC 102 and registers a segment.
  • This processing flow is realized by the CPU of each of the management server 101 and the store PC 102 reading and executing a program stored in the HDD or the like. Further, the store PC 102 has a Web browser (not shown), accesses the management server 101 via the Web browser, and displays various UI screens provided by the management server 101.
  • the store PC 102 accesses the management server 101 based on an instruction from the store user and requests segment registration. At this time, it is assumed that the store is already registered in the management server 101 and authentication using a password or the like has been completed.
  • the management server 101 provides a segment registration screen (FIG. 11E) as a response to the segment registration request from the store PC 102.
  • FIG. 11E shows a configuration example of a segment registration screen when registering a segment in response to a request received from the store PC 102.
  • the customer user can input the segment name, the attribute, and whether merge is possible.
  • the input segment name, attribute, and merge possibility are managed as the segment name, merge possibility, and segment attribute registered in the table shown in FIG. 4C after the segment is set.
  • the attributes are set collectively, but the attributes may be set for each category such as store, customer user, and product.
  • the store PC 102 displays the segment registration screen provided from the management server 101 on the Web browser.
  • the store PC 102 receives input of various segment information from the store user. At this time, the store PC 102 receives an input of an attribute associated with the segment. Thereafter, the store PC 102 transmits the received information of one or more attributes to the management server 101.
  • the management server 101 searches the table for customer user information corresponding to the attribute combination.
  • the customer user information extracted here corresponds to the total number of customer users, for example, but may be other information.
  • the extracted customer users may be classified into age, sex, occupation, birthplace, location, interest, etc., and the number of customer users for each classification may be provided. Alternatively, it may be the number of customer users who have a record of purchasing a product related to the attribute. These conditions may be input by the customer user together with attributes in S804.
  • customer information corresponds to personal information, and generally strict management restrictions are assumed. Therefore, detailed information such as the personal name and address of the customer user may not be output.
  • the search may be performed using the AND condition of the attributes, or may be performed using the OR condition. Moreover, you may set an upper limit number / lower limit number according to a search result about the number of the attributes which a shop user can input. After the search is completed, the management server 101 notifies the store PC 102 of the search result.
  • the attributes that can be input by the store user in S805 may be limited to attributes that match or are related to the attributes of the store user's store (included in the attribute range).
  • the attribute can be set hierarchically such as a higher concept, a middle concept, and a lower concept.
  • the subordinate concept is included in the range of the superordinate concept and the intermediate concept, and the intermediate concept is included in the range of the superordinate concept.
  • the scope of the upper concept of clothes includes a medium concept such as clothes and Japanese clothes
  • the lower concept of clothes includes a suit, a jacket, pants, and the like. Therefore, if the attribute “clothes” is selected, the suit or jacket is related to the attribute and included in the range.
  • store PC102 receives the information transmitted from management server 101, and displays the information. Based on the search result, the store PC 102 receives an instruction from the store user as to whether or not to register with the contents of the segment information.
  • the store PC 102 determines whether or not a registration instruction has been received from the store user. If a registration instruction is accepted (YES in S807), the process proceeds to S808. If an instruction to change the input attribute is accepted (NO in S807), the process proceeds to S804, and the process is repeated.
  • the store user can determine whether the set attribute appropriately surrounds the customer user that the store should be a potential customer. When the store user cannot obtain the expected search result, the store user can redo the attribute setting and repeat the above process. Thereby, the store user can establish a unique portal that can efficiently enclose potential customer users.
  • store PC 102 transmits the registration instruction received from the store user and the input segment information to management server 101.
  • the management server 101 upon receiving the segment information from the store PC 102, issues information such as a segment ID and registers the segment information in the table shown in FIG. 4C. At this time, the structure which makes the store which created the segment participate from the beginning may be sufficient, and the structure which can select the created store may be sufficient.
  • the management server 101 may be configured to reject the creation of the number of stores and the number of customer users that do not exceed a predetermined threshold based on the number of stores and the number of customer users corresponding to the segment information.
  • whether or not a segment can be created may consider the presence or absence of a transaction record (sales record) with a customer user corresponding to the attribute included in the segment information. For example, an application can be rejected as not allowing the right to create a segment to a store that has no sales record with the customer user or a store that does not have a certain number of sales records.
  • the management server 101 transmits a registration completion notification to the store PC 102.
  • the store PC 102 receives a registration completion notification from the management server 101, and displays that fact. Thereafter, this processing flow ends.
  • FIG. 8 shows the flow of processing when a new segment is created and registered
  • the main editing contents include addition / modification / deletion of attributes associated with segments.
  • a change request is transmitted in steps S801 to S803, and a segment to be edited is selected on the editing screen obtained as a response.
  • FIG. 9 shows a flowchart of event registration processing according to the present embodiment.
  • the store management unit 302 the segment management unit 303, the UI control unit 304, the store authentication unit 306, and the event management unit 309 shown in FIG.
  • This processing flow is realized by the CPU of each of the management server 101 and the store PC 102 reading and executing a program stored in the HDD or the like. Further, the store PC 102 has a Web browser (not shown), accesses the management server 101 via the Web browser, and displays various UI screens provided by the management server 101. The processing related to the display and notification of events registered here will be described later with reference to FIG.
  • the store PC 102 accesses the management server 101 based on an instruction from the store user and requests event registration. At this time, it is assumed that the store has already been registered in the management server 101 and the store authentication unit 306 has completed authentication using a password or the like. In addition, in event registration, an upper limit of the number of registrations may be set for each store, and registration availability may be determined according to the contents of the event. In this case, once there is a registration request from the store PC 102, the management server 101 is controlled to perform an event registration approval process (not shown).
  • the management server 101 provides an event registration screen (FIG. 11F) as a response to the event registration request from the store PC 102.
  • FIG. 11F shows a configuration example of an event registration screen when an event is registered in response to a request received from the store PC 102.
  • the store user can input event name, segment ID, notification period, and event content information.
  • the input information is managed as event name, segment ID, notification period, and event content information registered in the table shown in FIG. 4E.
  • a list of selectable segments may be displayed.
  • the store PC 102 displays the event registration screen provided from the management server 101 on the Web browser.
  • the store PC 102 receives input of various event information from the store user. At this time, selection of a segment associated with the event is accepted.
  • the segment that can be selected by the store user corresponds to a segment corresponding to a specific portal in which the store participates.
  • UI screen display control may be performed so that a segment that cannot be registered is not displayed in advance or cannot be selected.
  • the event is not an event limited to a specific portal but an event performed on a general portal, the segment is not selected and the target is set as a general portal. Note that a new segment may be generated in this step.
  • the store PC 102 transmits the received event information to the management server 101.
  • segment and unique portal associated therewith By selecting a segment (customer user) targeted by the store as a setting of various event information, it is possible to clearly specify the other party (segment and unique portal associated therewith) that is desired to be registered as an event target. Even if the store does not participate in the unique portal, when trying to register an event related to a unique product from the store side, it is associated with the attribute of the product and the segment to be registered. Registration may be permitted when the attribute matches. In addition, when a segment is selected, the number of customer users who are notified of an event may be displayed.
  • the management server 101 upon receiving event information from the store PC 102, issues information such as an event ID by the event management unit 309, and registers the event information in the table shown in FIG. 4E.
  • the registration process is performed after confirming the input content (automatic determination or determination by the administrator) on the management server 101 side. May be.
  • the confirmation in this case may be performed in accordance with, for example, authority on the store side (infrastructure service use plan by the store) or rules.
  • the management server 101 transmits a registration completion notification to the store PC 102.
  • the store PC 102 receives a registration completion notification from the management server 101, and displays that fact. Thereafter, this processing flow ends.
  • Event notification processing The event notification method according to this embodiment will be described below.
  • the user can make a transition to an accessible unique portal by logging in to a service site provided by the management server 101.
  • contents (events) displayed in accordance with corresponding segments are different.
  • a unique portal is associated with each segment, and an event registered for the unique portal is displayed.
  • an event registered for the general portal is notified.
  • the portal site (unique portal) that can be accessed by the customer user changes.
  • FIG. 10 shows a process flow of event notification according to the present embodiment. This processing flow is realized by the CPU of the management server 101 reading and executing a program stored in a storage unit such as an HDD. On the management server 101 side, the customer user management unit 301, UI control unit 304, customer user authentication unit 305, and event management unit 309 shown in FIG.
  • the management server 101 receives a login request from a customer user via the customer PC 103. At this time, the management server 101 receives the user ID and password together and performs authentication processing. Here, the process proceeds assuming that the authentication is successful.
  • the management server 101 refers to the customer information of the customer user who has been successfully authenticated, and determines whether there is a segment registered to be able to participate. If there is a segment that can participate (YES in S1002), the process proceeds to S1003. If there is no segment that can participate (NO in S1002), the process flow ends.
  • the management server 101 permits the logged-in customer user to access a unique portal associated with a segment that can be participated.
  • the management server 101 displays an event corresponding to the segment (FIG. 11G) based on the table in FIG. 4E when the customer user accesses the unique portal permitted to access in S1003.
  • FIG. 11G shows a configuration example of an event notification screen displayed when a customer user accesses a page of a specific portal.
  • events related to the unique portal are displayed.
  • the events are displayed in a list format, but the present invention is not limited to this.
  • the events may be displayed so as to switch to the event display area in the page. Thereafter, this processing flow ends.
  • notification is displayed on an accessible unique portal, but the present invention is not limited to this, and other notification methods may be used.
  • a unique portal is provided only for customer users related to specific attributes among customer users registered in the portal site (general portal) provided by the management server. be able to. Only the specific store which satisfy
  • the unique portal is a portal site that is provided as a place for transactions between a store related to a specific attribute and a customer user. From the standpoint of the customer user, the unique portal needs it by participating in the unique portal. Since it is possible to efficiently search for and purchase products and services, it is possible to effectively reduce the effort and burden of searching for the products and stores that are required from among a large number of stores and products.
  • the unique portal of this embodiment is constructed by setting conditions for stores and customer users to which the management server can participate, and stores and customer users who are not related to products and services handled by the unique portal, sales results, Stores with low evaluations can be excluded.
  • the customer user's standpoint it is possible to save time and effort to narrow down the stores that handle the products that they need by simply participating in the unique portal. You can find out. Also, if you visit a unique portal, you can reliably obtain information on the events that are held by the stores of the unique portal, so you can prevent oversight of event information.
  • segments set by a store user are merged (integrated) according to the degree of similarity.
  • a store user When a store user generates a plurality of segments, it is possible that a similar segment is generated. In such a case, the segments can be easily managed by merging the segments.
  • similar segments it is assumed that the targets are also similar, and there is often no problem even if they are merged.
  • segments that you do not want to merge In consideration of these, in the present embodiment, segment merge processing is performed.
  • FIG. 13 shows a processing flow for integrating segments in the management server 101 according to this embodiment.
  • This processing flow is realized by the CPU of the management server 101 reading and executing a program stored in the HDD or the like.
  • the execution timing of this processing flow may be executed at a date and time designated in advance, or when the number of segments having the same or similar attributes exceeds a predetermined number, or a segment created by a certain store It may be executed when the number exceeds a predetermined number.
  • the management server 101 refers to the table in FIG. 4C and acquires the generated segment information. At this time, the segment is searched using the store ID as a key.
  • the management server 101 removes information on segments for which merging is prohibited from the acquired segment information.
  • the segment for which merging is prohibited is set by the store user, and specifically, is determined according to the setting of “Mergeability” in FIG. 4C.
  • the management server 101 derives the similarity between the segments based on the attributes of the segment information.
  • the method of deriving the similarity is not particularly limited. For example, between two segments, the ratio of the number of matching attributes to the number of types of attributes of the two segments, the number of matching attributes, It may be calculated as a value obtained by weighted addition of the number of attributes that do not match.
  • the management server 101 sorts the combinations in descending order of similarity.
  • the management server 101 determines whether or not the similarity of the combination with the highest similarity among the sorted segment combinations is equal to or greater than a predetermined threshold.
  • a predetermined threshold is set in advance and held in a storage area such as an HDD. If the similarity of the combination of segments having the highest similarity is equal to or greater than a predetermined threshold (YES in S1304), the process proceeds to S1305, and if it is smaller than the threshold (NO in S1304), the process flow ends.
  • the management server 101 merges the segments having the highest similarity.
  • the merging is performed by newly generating one segment and associating the attribute associated with the similar segment with the new segment.
  • the unique portals associated with the merged segments are also integrated into one.
  • segments that are considered to be similar are deleted.
  • a flag that indicates that the segment generated by merging may be provided.
  • the information may be managed as a segment before merging without deleting the segment before merging.
  • the similar segments when the number of similar segments increases, the similar segments can be automatically merged on the management server side. Moreover, the state can be maintained even for a specific segment that is not desired to be merged.
  • segments generated at the same store are merged.
  • similar segments may be merged between different stores.
  • ⁇ Third embodiment> This embodiment shows an example different from the first embodiment regarding a method for notifying an event to a customer user.
  • the unique portal described in the first and second embodiments can be accessed only by customer users having specific attributes, and the customer users have a potential demand for products and the like handled by stores. Have. However, if it sees for every store, not all stores have the transaction results with all the customer users, and it is assumed that there is a customer user with no transaction results depending on the stores.
  • the invention that makes it possible to newly create a transaction record with such a customer user has been described.
  • depending on the store there may be a case where it is desired to notify an event only for a customer user who has a transaction record. Therefore, in this embodiment, a method for giving an event notification with priority given to a customer user who has a transaction record will be described.
  • FIG. 14 shows a processing flow of event notification according to the present embodiment.
  • This processing flow is realized by the CPU of the management server 101 reading and executing a program stored in a storage unit such as an HDD.
  • a storage unit such as an HDD.
  • the management server 101 refers to the various tables and determines whether there is an event registered by the store where the logged-in customer user has made a purchase procedure in the past. Specifically, the tables shown in FIGS. 4E and 4F managed by the transaction management unit 310 are used. If there is no event registered by a store with a purchase history (NO in S1404), the process proceeds to S1406, and if there is (YES in S1404), the process proceeds to S1405.
  • the management server 101 displays an event corresponding to the corresponding segment and store based on the tables in FIGS. 4E and 4F when the customer user accesses the unique portal permitted to be accessed in S1403. Control to do. Thereafter, this processing flow ends.
  • the limited event notified by a certain store A is displayed when the store A and the customer user A who has a transaction record access the unique portal, but the store user A and the customer user B who has no transaction record have the unique portal. It will not be displayed even if accessed.
  • the general event notified by the store A is displayed whenever any of the customer user A and the customer user B visits the unique portal. When the customer user A visits the unique portal, both the limited event and the general event are displayed. In this case, the limited event is displayed so as to be distinguishable from the general event. Good.
  • a limited event notification may be given as a group to indicate that the event is a limited event (e.g., enclosed in a frame, or provided with a headline indicating the limited event).
  • the notification of the limited event may be prioritized in the display order over the notification of the general event.
  • the limited event may be only a part of the notification period set in FIG. 11F, and the remaining period may be switched to a general event. For example, if the notification period is 1 week, event notification is given only to customer users who have a track record of trading as a limited event for the first 2 days, and the remaining 5 days can be switched to a general event to access a unique portal. All customer users can be notified.
  • the above-described unique portal may have a segment-specific function.
  • a function may be provided that can search only for events and stores registered for a segment corresponding to the unique portal.
  • an event that can be used only on the unique portal may be registered.
  • related with the segment may be sufficient.
  • the customer user side requests the store side having a predetermined attribute to register an event via a unique portal.
  • the structure which can register the segment which has a predetermined attribute from the customer user side may be sufficient.
  • the information processing apparatus can also be realized by a program that causes one or more computers to function as the information processing apparatus.
  • the program can be provided / distributed by being recorded on a computer-readable recording medium or through a telecommunication line.

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)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

A management server for managing a first portal site for online shopping, and for managing a second portal site, said first portal site providing access to a plurality of virtual stores, and said second portal site having a particular attribute and providing access to some virtual stores which are among the plurality of virtual stores, and which have the particular attribute. If the management server receives an access service request which was sent from one of the plurality of virtual stores, and which requests that the second portal site provide access to that virtual site, then the management server determines whether the virtual store that sent the access service request has the particular attribute, and if it is determined that the virtual store that sent the access service request has the particular attribute, the management server updates store information about the virtual store so that the store information indicates that the second portal site provides access to the virtual store.

Description

オンラインショッピングのポータルサイトを管理する管理サーバおよびその制御方法、並びにコンピュータプログラムManagement server for managing online shopping portal site, control method therefor, and computer program
　本願発明は、オンラインショッピングのポータルサイトを管理する管理サーバおよびその制御方法、並びにコンピュータプログラムに関する。 The present invention relates to a management server that manages an online shopping portal site, a control method thereof, and a computer program.
　近年、インターネット等を利用したオンラインショッピングが普及しており、利用者はオンライン上に出店している店舗が販売している商品の購入等のサービスを利用することができる。オンラインショッピングの提供形態は様々であり、出店している複数の店舗へのポータルサイトを提供する、所謂モール型のインフラシステムも存在する。モール型のインフラシステムでは店舗側に対して出店に係るインフラが提供されるため、店舗側は独自のシステムを構築せずとも容易にオンライン上に出店することができる。 In recent years, online shopping using the Internet and the like has become widespread, and users can use services such as purchasing products sold at stores that are online. There are various forms of providing online shopping, and there is also a so-called mall-type infrastructure system that provides portal sites to a plurality of stores that have opened stores. In the mall-type infrastructure system, the store side is provided with the infrastructure related to the store opening. Therefore, the store side can easily open a store online without building an original system.
　このようなインフラシステムでは、モール全体における販売促進や潜在顧客の確保のために、様々な付加価値を利用者に対して提供している。例えば、オンライン上の所定の店舗にて利用可能なクーポンやポイントの発行などが行われている。特許文献１では、利用者の行動履歴に基づいて、キャンペーンを提示する方法が開示されている。 Such an infrastructure system provides users with various added values for sales promotion and securing potential customers throughout the mall. For example, coupons and points that can be used at predetermined stores online are issued. Patent Document 1 discloses a method for presenting a campaign based on a user's behavior history.
特開２０１０－２７７３６０号公報JP 2010-277360 A
　このようなインフラシステムにおけるオンラインショッピングにおいて、利用者は、モール内に多数の店舗や商品が存在するため、自身が必要とする商品や、そのような商品を扱う店舗を見つけにくいという問題がある。 In online shopping in such an infrastructure system, since there are many stores and products in the mall, there is a problem that it is difficult for users to find products that they need and stores that handle such products.
　当該問題を解決するため、ユーザが必要とする商品や当該商品を扱う店舗が見つけやすいポータルサイトを提供し、管理する必要があるが、当該ポータルサイトを構築するための具体的な手段及び方法は未だ提案されていない。 In order to solve the problem, it is necessary to provide and manage a product required by the user and a portal site that is easy to find a store that handles the product. Specific means and methods for constructing the portal site are as follows. Not yet proposed.
　上記課題を解決するために本願発明は以下の構成を有する。すなわち、複数の仮想店舗へのアクセスを提供するオンラインショッピングの第１のポータルサイトと、前記複数の仮想店舗のうち特定の属性を有する一部の仮想店舗へのアクセスを提供し、かつ、該特定の属性を有する第２のポータルサイトとを管理する管理サーバであって、
　前記仮想店舗が有する属性の情報を含む店舗情報と、前記第２のポータルサイトが有する前記特定の属性の情報を含むサイト情報とを管理する管理手段と、
　前記複数の仮想店舗のうちのいずれかの仮想店舗から、前記第２のポータルサイトにおける該仮想店舗へのアクセス提供を求めるアクセス提供申請を受け付ける第１の受付手段と、
　前記第１の受付手段が前記アクセス提供申請を受け付けた場合に、前記管理手段が管理する前記店舗情報と前記サイト情報とに基づき、前記アクセス提供申請を行った仮想店舗が前記特定の属性を有するか否かを判定する判定手段とを備え、
　前記判定手段が前記アクセス提供申請を行った仮想店舗が前記特定の属性を有すると判定した場合、前記管理手段は前記アクセス提供申請を行った仮想店舗の店舗情報を、前記第２のポータルサイトが該仮想店舗へのアクセスを提供することを示すように更新することを特徴とする。 In order to solve the above problems, the present invention has the following configuration. That is, a first portal site for online shopping that provides access to a plurality of virtual stores, and access to some virtual stores having a specific attribute among the plurality of virtual stores, and the identification A management server that manages a second portal site having the following attributes:
Management means for managing store information including attribute information of the virtual store and site information including information of the specific attribute of the second portal site;
A first accepting unit that accepts an access provision application for requesting access to the virtual store in the second portal site from any one of the plurality of virtual stores;
When the first accepting unit accepts the access provision application, the virtual store that has made the access provision application has the specific attribute based on the store information and the site information managed by the managing unit. Determination means for determining whether or not,
When the determination unit determines that the virtual store that has applied for the access provision has the specific attribute, the management unit stores the store information of the virtual store that has applied for the access provision, and the second portal site Updating to indicate that access to the virtual store is provided.
　本発明によれば、ユーザが必要とする商品や当該商品を扱う店舗が見つけやすいポータルサイトを提供し管理する管理サーバにより、ポータルサイトを構築するための具体的な手段及び方法を提供することができる。 According to the present invention, it is possible to provide specific means and a method for building a portal site by a management server that provides and manages a product that is required by a user and a portal site that is easy to find a store that handles the product. it can.
　本発明のその他の特徴及び利点は、添付図面を参照とした以下の説明により明らかになるであろう。なお、添付図面においては、同じ若しくは同様の構成には、同じ参照番号を付す。 Other features and advantages of the present invention will become apparent from the following description with reference to the accompanying drawings. In the accompanying drawings, the same or similar components are denoted by the same reference numerals.
　添付図面は明細書に含まれ、その一部を構成し、本発明の実施の形態を示し、その記述と共に本発明の原理を説明するために用いられる。
本願発明に係るシステム全体の構成例を示す図。 本願発明に係る情報処理装置のハードウェア構成の例を示す図。 本願発明に係る管理サーバのソフトウェア構成の例を示す図。 本願発明に係る顧客ユーザ情報の管理テーブルの構成例を示す図。 本願発明に係る店舗情報の管理テーブルの構成例を示す図。 本願発明に係るセグメント情報の管理テーブルの構成例を示す図。 本願発明に係る商品情報の管理テーブルの構成例を示す図。 本願発明に係るイベント情報の管理テーブルの構成例を示す図。 本願発明に係る売買取引情報の管理テーブルの構成例を示す図。 本願発明に係る店舗登録処理のフローチャート。 本願発明に係る顧客ユーザ登録処理のフローチャート。 本実施形態に係る固有ポータル参加処理のフローチャート 本願発明に係るセグメント登録処理のフローチャート。 本願発明に係るイベント登録処理のフローチャート。 第一の実施形態に係るイベント通知処理のフローチャート。 本願発明に係る初期のＵＩ画面の構成例を示す図。 本願発明に係る店舗登録用のＵＩ画面の構成例を示す図。 本願発明に係る顧客ユーザ登録用のＵＩ画面の構成例を示す図。 本願発明に係る固有ポータルへの参加申請用のＵＩ画面の構成例を示す図。 本願発明に係るセグメント登録用のＵＩ画面の構成例を示す図。 本願発明に係るイベント登録用のＵＩ画面の構成例を示す図。 本願発明に係るイベント表示用のＵＩ画面の構成例を示す図。 本願発明に係るセグメントを説明するための図。 第二の実施形態に係るセグメントのマージ処理のフローチャート。 第三の実施形態に係るイベント通知処理のフローチャート。 The accompanying drawings are included in the specification, constitute a part thereof, show an embodiment of the present invention, and are used to explain the principle of the present invention together with the description.
The figure which shows the structural example of the whole system which concerns on this invention. The figure which shows the example of the hardware constitutions of the information processing apparatus which concerns on this invention. The figure which shows the example of the software structure of the management server which concerns on this invention. The figure which shows the structural example of the management table of customer user information which concerns on this invention. The figure which shows the structural example of the management table of the shop information which concerns on this invention. The figure which shows the structural example of the management table of the segment information which concerns on this invention. The figure which shows the structural example of the management table of the merchandise information which concerns on this invention. The figure which shows the structural example of the management table of the event information which concerns on this invention. The figure which shows the structural example of the management table of the sales transaction information which concerns on this invention. The flowchart of the store registration process which concerns on this invention. The flowchart of the customer user registration process which concerns on this invention. Flow chart of unique portal participation processing according to this embodiment The flowchart of the segment registration process which concerns on this invention. The flowchart of the event registration process which concerns on this invention. The flowchart of the event notification process which concerns on 1st embodiment. The figure which shows the structural example of the initial stage UI screen which concerns on this invention. The figure which shows the structural example of UI screen for shop registration concerning this invention. The figure which shows the structural example of UI screen for customer user registration which concerns on this invention. The figure which shows the structural example of UI screen for participation application to the specific portal which concerns on this invention. The figure which shows the structural example of UI screen for the segment registration which concerns on this invention. The figure which shows the structural example of UI screen for event registration which concerns on this invention. The figure which shows the structural example of UI screen for the event display which concerns on this invention. The figure for demonstrating the segment which concerns on this invention. The flowchart of the merge process of the segment which concerns on 2nd embodiment. The flowchart of the event notification process which concerns on 3rd embodiment.
　以下、図面を用いて、本願発明に係る実施形態について説明する。なお、以下に示す実施形態は一例であり、これに限定するものではない。そのため、本願発明の特徴的構成を適用できれば他の構成であってもよい。 Hereinafter, embodiments of the present invention will be described with reference to the drawings. In addition, embodiment shown below is an example and is not limited to this. Therefore, other configurations may be used as long as the characteristic configuration of the present invention can be applied.
　＜第一の実施形態＞
　［セグメントの説明］
　まず、本願発明にて扱う「セグメント」について説明する。本明細書では、オンラインショッピングのサービスを利用するユーザを「顧客ユーザ」と記載する。また、本願発明に係る管理サーバが提供するインフラサービスにオンライン上の仮想店舗を登録し、顧客ユーザ向けにオンラインショッピングのサービスを提供するユーザ（オーナー）を「店舗ユーザ」と記載する。また、管理サーバにて提供されるモール型のインフラサービス上に設けられるオンライン上に出店された仮想店舗を単に「店舗」と記載する。 <First embodiment>
[Description of segment]
First, the “segment” handled in the present invention will be described. In this specification, a user who uses an online shopping service is referred to as a “customer user”. A user (owner) who registers an online virtual store in the infrastructure service provided by the management server according to the present invention and provides an online shopping service for a customer user is referred to as a “store user”. In addition, a virtual store opened online on a mall-type infrastructure service provided by the management server is simply referred to as “store”.
　モール型のインフラサービスでは、各店舗は、原則としてポータルサイトにおいて全ての顧客ユーザに対してアクセス可能に表示され、顧客ユーザは自由に店舗のサイトにアクセスすることが可能である。このような全顧客ユーザに対して開放されているポータルサイトを本明細書では「一般ポータル」と呼ぶ。しかし、オンラインショッピングのサービスを提供する店舗は、自身が扱う商品やサービス（以下、「商品等」という）の性質を考慮し、所定の客層（ターゲット）を絞って販売促進のキャンペーンや広告等の通知を行いたい場合がある。例えば、おむつや粉ミルクなどの幼児用消耗品（ベビー用品）は育児を行っていない顧客ユーザに対してはほとんどアピールを必要としない商品であり、店舗ユーザとしては現在育児中の顧客ユーザに対して選択的に（ターゲットを絞って）通知を行いたい。その一方で、顧客ユーザ側でも、一般ポータル内の多数の店舗に自由にアクセス可能な自由度がある反面、膨大な数の店舗の中から自身が興味のある商品等を扱う店舗を選択しなければならないという店舗選択の負担が存在する。このような状況において、顧客ユーザは、これまでに利用のない店舗からの通知も取得したいという欲求を有している場合も多い。 In the mall-type infrastructure service, each store is displayed in principle to be accessible to all customer users on the portal site, and the customer user can freely access the store site. Such a portal site opened to all customer users is referred to as a “general portal” in this specification. However, stores that offer online shopping services consider the nature of the products and services they handle (hereinafter referred to as “products, etc.”), narrow down a predetermined customer segment (target), and promote sales campaigns and advertisements. Sometimes you want to be notified. For example, consumables for infants (baby goods) such as diapers and powdered milk are products that require little appeal to customer users who are not raising children. I want to be notified selectively (by targeting). On the other hand, the customer user side also has the freedom to freely access a large number of stores in the general portal, but must select a store that handles products he / she is interested in from a huge number of stores. There is a burden of store selection that must be done. Under such circumstances, customer users often have a desire to obtain notifications from stores that have not been used.
　さらに、店舗ユーザ側には、これまで取引実績のない顧客ユーザ等、潜在的なニーズがある客層を新たに発掘したいという要望もある。また、顧客ユーザは、これまでは特に興味のない商品等であっても、店舗からのキャンペーン等に起因して新たに興味を持つことがある。ここでの店舗が提供するキャンペーンとは、商品購入時に利用可能なクーポンの発行や、送料無料などが挙げられる。 Furthermore, there is a demand on the store user side to find a new customer segment with potential needs, such as a customer user who has no past transaction record. In addition, even if a customer user is not particularly interested in a product or the like, the customer user may have a new interest due to a campaign from a store or the like. The campaign provided by the store here includes issuance of coupons that can be used at the time of product purchase and free shipping.
　発明の実施形態では、顧客ユーザ、店舗、および店舗にて扱う商品等にそれぞれ属性が与えられる。属性とは、顧客ユーザや店舗に関する情報であって、顧客ユーザや店舗を分類可能な情報であればどのようなものであってもよい。例えば、顧客ユーザであれば年齢（年代）、性別、出身地、所在地（自宅住所、勤務住所）、職業、興味対象の他、管理サーバが提供するインフラサービス上における料金プランや制約、会員種別などを含むことができる。また、店舗であれば、店舗の所在地、店舗が扱う商品の分類（書籍、衣類、食品）や、店舗の分類（書店、衣料品店、食料品店等）等の情報を含むことができる。本実施形態において、店舗や顧客ユーザに付与される属性の一例は図１２に示す通りである。属性については、インフラサービスを提供する側で予め用意しておくものに加え、店舗ユーザや顧客ユーザが新たに定義するものであってもよい。例えば、新たな商品やサービスが生まれた場合などに伴って、その名称などを新たな属性として定義することも考えられる。 In the embodiment of the invention, an attribute is given to each of a customer user, a store, and a product handled in the store. The attribute is information related to the customer user or the store, and may be any information as long as it can classify the customer user and the store. For example, if you are a customer user, age (age), gender, birthplace, location (home address, work address), occupation, interest, as well as rate plans and restrictions on infrastructure services provided by the management server, membership type, etc. Can be included. In the case of a store, information such as the location of the store, the classification of the products handled by the store (books, clothing, food), the classification of the store (bookstore, clothing store, grocery store, etc.) can be included. In this embodiment, an example of the attribute given to a store or a customer user is as shown in FIG. The attributes may be newly defined by the store user or the customer user in addition to those prepared in advance on the infrastructure service providing side. For example, when a new product or service is born, the name or the like may be defined as a new attribute.
　本明細書では、上記のような１または複数の属性が関連付けられた集合を「セグメント」と呼ぶ。そして、セグメントに関連付けられた属性を有する顧客ユーザや店舗はそのセグメントに属するものとして扱う。また、本明細書において、各セグメントにはそれぞれ、本実施形態で「固有ポータル」と呼ぶポータルサイトが関連付けられているものとする。固有ポータルの例としては、例えば年齢が１９から２４歳までの学生を対象とした学生向けのポータルサイトや、子育て中の家族を対象としたポータルサイト等がある。 In this specification, a set in which one or more attributes as described above are associated is referred to as a “segment”. And the customer user and store which have the attribute linked | related with the segment are handled as what belongs to the segment. Further, in this specification, it is assumed that a portal site called “unique portal” in the present embodiment is associated with each segment. Examples of the unique portal include a portal site for students targeting students aged 19 to 24, a portal site targeting families who are raising children, and the like.
　詳細については後述するが、上記の一般ポータルは、店舗や顧客ユーザの属性を限定しておらず、顧客ユーザからのアクセスの制限を設けていない。これに対し、固有ポータルでは、対応するセグメントに関連付けられた属性を有する顧客ユーザ以外はアクセスできないようにアクセス制御されるものとする。また、固有ポータルに参加できる店舗も、セグメントに関連付けられた属性を有している、もしくはセグメントに関連付けられた属性を有する商品等を扱っている店舗に限定される。ここでの「参加」とは、店舗がある固有ポータルを介して顧客ユーザからアクセス可能となったり、任意の広告やキャンペーンなどを表示したりすることを意味する。このとき、ある固有ポータルに参加している店舗は、セグメントに対してイベントを設定登録することで、そのセグメントが関連付けられた固有ポータル上にイベントの詳細を表示等することができるものとする。 Although details will be described later, the above-described general portal does not limit the attributes of stores and customer users, and does not limit access from customer users. On the other hand, in the unique portal, access control is performed so that only a customer user having an attribute associated with a corresponding segment can access. In addition, stores that can participate in the unique portal are also limited to stores that have an attribute associated with a segment or that handle products or the like that have an attribute associated with a segment. Here, “participation” means that a store becomes accessible from a customer user through a specific portal where the store is located, or that an arbitrary advertisement or campaign is displayed. At this time, a store participating in a specific portal can display the details of the event on the specific portal associated with the segment by setting and registering the event for the segment.
　以下、本実施形態に対応する固有ポータルを提供するシステム、及び、当該システムが提供するサービスの詳細を説明する。 Hereinafter, a system for providing a unique portal corresponding to the present embodiment and details of services provided by the system will be described.
　［システム構成］
　図１は、本実施形態に係るシステムの全体構成の例を示す図である。システムにおいて、管理サーバ１０１、店舗ＰＣ１０２、および顧客ＰＣ１０３が、インターネット１０４を介して接続されている。管理サーバ１０１は、オンラインショッピングサービスの基盤となるインフラを、店舗ＰＣ１０２および顧客ＰＣ１０３を介して店舗ユーザおよび顧客ユーザにそれぞれ提供する情報処理装置である。このインフラに対し、商品等を提供する店舗ユーザがオンライン上の店舗として登録することでオンラインショッピングサービスの提供が可能となる。なお、原則として、各店舗はまずは一般ポータルに登録されることとなり、全ての顧客ユーザがアクセス可能となっている。 [System configuration]
FIG. 1 is a diagram illustrating an example of the overall configuration of a system according to the present embodiment. In the system, a management server 101, a store PC 102, and a customer PC 103 are connected via the Internet 104. The management server 101 is an information processing apparatus that provides an infrastructure as a basis for an online shopping service to a store user and a customer user via the store PC 102 and the customer PC 103, respectively. With respect to this infrastructure, an online shopping service can be provided by a store user who provides products and the like registered as an online store. In principle, each store is first registered in a general portal and is accessible to all customer users.
　店舗ＰＣ１０２は、店舗ユーザが利用する情報処理装置である。また、顧客ＰＣ１０３は、オンラインショッピングサービスを利用する顧客ユーザが扱う情報処理装置である。なお、店舗ＰＣ１０２、および顧客ＰＣ１０３は、デスクトップＰＣでも良いし、スマートフォンやタブレットなどのモバイル端末でもよい。各ユーザは、店舗ＰＣ１０２や顧客ＰＣ１０３が備えるＷｅｂブラウザ（不図示）を介して、管理サーバ１０１が提供する一般ポータルへとアクセスする。なお、各ＰＣからインターネット１０４への接続は、有線でも無線でも構わない。また、図１では、各機器が１台ずつ示されているが、それぞれ複数接続されていても構わない。 The store PC 102 is an information processing device used by store users. The customer PC 103 is an information processing apparatus handled by a customer user who uses an online shopping service. The store PC 102 and the customer PC 103 may be desktop PCs or mobile terminals such as smartphones and tablets. Each user accesses a general portal provided by the management server 101 via a Web browser (not shown) provided in the store PC 102 or the customer PC 103. The connection from each PC to the Internet 104 may be wired or wireless. In FIG. 1, one device is shown, but a plurality of devices may be connected.
　［ハードウェア構成］
　図２は、本実施形態に係るシステムに含まれる各情報処理装置のハードウェア構成例を示す。なお、以下では一般的な情報処理装置を例に挙げて説明するが、これ以外の構成を備えていても構わない。 [Hardware configuration]
FIG. 2 shows a hardware configuration example of each information processing apparatus included in the system according to the present embodiment. In the following description, a general information processing apparatus will be described as an example, but other configurations may be provided.
　情報処理装置２００は、ＣＰＵ２０１、ＲＡＭ２０２、ＲＯＭ２０３、ＨＤＤ２０４、表示ＩＦ２０５、表示部２０６、入力ＩＦ２０７、入力部２０８、およびＮＷ　ＩＦ２０９を備える。各構成要素は、バス２１０を介して通信可能に接続されている。ＣＰＵ２０１は、情報処理装置２００の全体の処理制御を行い、また、ＲＯＭ２０３等に保持された各種プログラムをＲＡＭ２０２に読み出して実行することで各種処理を実現する。ＲＡＭ２０２は、揮発性の記憶領域であり、各種プログラムの実行時におけるワークメモリなどの用途で用いられる。ＲＯＭ２０３は、不揮発性の記憶領域であり、処理に用いられる各種プログラム等が格納される。ＨＤＤ２０４は、不揮発性の記憶領域であり、処理結果などを記憶して保持する。ＨＤＤ２０４は、不揮発性の大容量の記憶領域であればよく、ハードディスク以外にも、例えばフラッシュメモリのような半導体メモリにより構成されても良い。 The information processing apparatus 200 includes a CPU 201, a RAM 202, a ROM 203, an HDD 204, a display IF 205, a display unit 206, an input IF 207, an input unit 208, and an NW IF 209. Each component is communicably connected via the bus 210. The CPU 201 controls the entire processing of the information processing apparatus 200, and implements various processes by reading various programs stored in the ROM 203 and the like into the RAM 202 and executing them. The RAM 202 is a volatile storage area and is used for applications such as work memory when various programs are executed. The ROM 203 is a non-volatile storage area and stores various programs used for processing. The HDD 204 is a non-volatile storage area that stores and holds processing results and the like. The HDD 204 only needs to be a nonvolatile large-capacity storage area, and may be configured by a semiconductor memory such as a flash memory in addition to the hard disk.
　表示ＩＦ２０５は、表示部２０６に接続され、表示部２０６の表示制御を行う。表示部２０６は、液晶などのディスプレイであり、処理結果を表示したり、後述する各種ユーザインタフェース画面（ＵＩ画面）などを表示したりする。なお、表示部２０６は情報処理装置２００に対し外付けされるように構成されてもよく、その場合は表示ＩＦ２０５を介して情報処理装置２００に接続される。入力ＩＦ２０７は、入力部２０８に接続され、ユーザ操作に基づく入力部２０８からの指示を受け付ける。入力部２０８は、例えば、キーボードやマウス（不図示）であり、ユーザが入力操作を行う際に用いられる。なお、表示部２０６と入力部２０８とが一体型となったタッチパネルが用いられても構わない。ＮＷ　ＩＦ２０９は、インターネット１０４などの外部ネットワークとの接続を行う。ここでの接続形態は有線／無線のいずれであっても構わない。 The display IF 205 is connected to the display unit 206 and performs display control of the display unit 206. The display unit 206 is a display such as a liquid crystal display, and displays a processing result and various user interface screens (UI screens) described later. The display unit 206 may be configured to be externally attached to the information processing apparatus 200, and in that case, the display unit 206 is connected to the information processing apparatus 200 via the display IF 205. The input IF 207 is connected to the input unit 208 and receives an instruction from the input unit 208 based on a user operation. The input unit 208 is, for example, a keyboard or a mouse (not shown), and is used when a user performs an input operation. Note that a touch panel in which the display unit 206 and the input unit 208 are integrated may be used. The NW IF 209 connects to an external network such as the Internet 104. The connection form here may be either wired or wireless.
　［ソフトウェア構成］
　図３は、本実施形態に係る管理サーバ１０１のソフトウェア構成例を示す図である。ここで示すソフトウェアは、管理サーバ１０１が備える記憶部（ＲＯＭ２０３やＨＤＤ２０４等）にプログラムとして保持され、管理サーバ１０１のＣＰＵ２０１に読み出して実行されることにより各種の制御及び処理が実現される。 Software configuration
FIG. 3 is a diagram illustrating a software configuration example of the management server 101 according to the present embodiment. The software shown here is stored as a program in a storage unit (ROM 203, HDD 204, or the like) included in the management server 101, and is read out and executed by the CPU 201 of the management server 101, thereby realizing various controls and processes.
　顧客ユーザ管理部３０１は、オンラインショッピングのサービスを利用する顧客ユーザのユーザ情報を管理する。顧客ユーザの情報は、例えば、図４Ａに示す構成を備え、詳細については後述する。 The customer user management unit 301 manages user information of customer users who use the online shopping service. The customer user information has, for example, the configuration shown in FIG. 4A and will be described in detail later.
　店舗管理部３０２は、店舗ユーザから登録されたオンライン上の店舗の各設定に関する店舗情報を管理する。店舗情報は、例えば、図４Ｂに示す構成を備え、詳細については後述する。 The store management unit 302 manages store information related to each online store setting registered by a store user. The store information has, for example, the configuration shown in FIG. 4B and will be described in detail later.
　セグメント管理部３０３は、店舗ユーザからの要求に応じて、各種セグメントを生成し、登録する。また、セグメント生成部３０３は、登録したセグメントの編集およびマージ、管理等の処理を行う。セグメント情報は、例えば、図４Ｃに示す構成を備え、詳細については説明する。また、セグメントに関する詳細な説明や処理フローについては後述する。 The segment management unit 303 generates and registers various segments in response to requests from store users. The segment generation unit 303 performs processing such as editing, merging, and management of the registered segment. The segment information has, for example, the configuration shown in FIG. 4C and will be described in detail. A detailed description and processing flow regarding the segment will be described later.
　ＵＩ制御部３０４は、各種設定内容に応じて、各ＰＣからの要求に対応したＵＩ画面を提供する。ＵＩ画面の一例は図１１Ａから図１１Ｇに示す通りである。 The UI control unit 304 provides a UI screen corresponding to a request from each PC according to various settings. An example of the UI screen is as shown in FIGS. 11A to 11G.
　顧客ユーザ認証部３０５は、オンラインショッピングサイトへアクセスを行った顧客ユーザのログイン制御を行う。具体的には、顧客ユーザが入力した認証情報（ユーザ名、パスワード）を受け付け、顧客ユーザ管理部３０１にて管理されているユーザ名とパスワードの情報に基づいて、認証処理を行う。また、顧客ユーザ認証部３０５は、各顧客ユーザによる固有ポータルへのアクセス時の制御も行う。 The customer user authentication unit 305 performs login control of a customer user who has accessed the online shopping site. Specifically, authentication information (user name and password) input by the customer user is received, and authentication processing is performed based on the user name and password information managed by the customer user management unit 301. The customer user authentication unit 305 also performs control when each customer user accesses the unique portal.
　店舗認証部３０６は、店舗ユーザからのアクセスに対し、認証処理を行う。ここでの認証は、顧客ユーザの認証と同様に行っても良いし、別途認証方式を用いてもよい。また、店舗認証部３０６は、店舗側から固有ポータルへの参加を要求された場合の参加処理も行う。本処理の詳細については後述する。 The store authentication unit 306 performs authentication processing for access from store users. The authentication here may be performed in the same manner as the customer user authentication, or a separate authentication method may be used. The store authentication unit 306 also performs participation processing when a request for participation in the unique portal is made from the store side. Details of this processing will be described later.
　検索部３０７は、店舗ユーザがセグメントを生成する際や編集する際に、そのセグメントに属する顧客ユーザの情報を検索する。ここで検索される情報としては、例えば、セグメントに属する顧客ユーザ数などが該当する。 When the store user creates or edits a segment, the search unit 307 searches for information on customer users belonging to the segment. The information searched here corresponds to the number of customer users belonging to a segment, for example.
　商品管理部３０８は、各店舗が扱う商品の情報を店舗と関連づけて管理する。商品の情報については、店舗が扱う商品等の登録を受け付ける。このとき、一般的に販売されている商品等であれば、予め管理サーバ１０１が登録しておき、その中から店舗ユーザが選択できるようにしてもよい。商品情報は、例えば、図４Ｄに示す構成を備え、詳細については後述する。 The product management unit 308 manages product information handled by each store in association with the store. As for product information, registration of products handled by the store is accepted. At this time, if it is a commodity or the like that is generally sold, the management server 101 may register in advance so that the store user can select it. The merchandise information has, for example, the configuration shown in FIG. 4D, and details will be described later.
　イベント管理部３０９は、店舗からの登録要求に応じて、各種イベント（キャンペーンや広告等）の登録を受け付け、管理する。イベント情報は、例えば、図４Ｅに示す構成を備え、詳細については後述する。また、ここで登録されるイベントは、一般ポータルにて通知されるものや、固有ポータル内に限定して通知されるものなどが挙げられる。イベント登録処理の詳細については後述する。 The event management unit 309 accepts and manages registration of various events (campaigns, advertisements, etc.) in response to a registration request from a store. The event information has, for example, the configuration shown in FIG. 4E and will be described in detail later. Examples of events registered here include those notified by a general portal and events notified only within a specific portal. Details of the event registration process will be described later.
　取引管理部３１０は、顧客ユーザと店舗との間で商品等の売買取引の情報を管理する。売買取引の情報は、例えば、図４Ｆに示す構成を備え、詳細については後述する。 The transaction management unit 310 manages information on sales transactions such as products between the customer user and the store. The information on the sales transaction has, for example, the configuration shown in FIG. 4F and will be described in detail later.
　［データ構成］
　図４Ａから図４Ｆは、本実施形態に係る管理サーバ１０１が管理する各種データの構成例を示す図である。ここで示される各データは、管理サーバ１０１が管理する内部もしくは外部の記憶領域に保持されているものとする。また、以下に示す各情報は、１のテーブルで管理されても良いし、複数のテーブルに分割されて管理されてもよい。 [Data structure]
4A to 4F are diagrams illustrating examples of the configuration of various data managed by the management server 101 according to the present embodiment. Each data shown here is assumed to be held in an internal or external storage area managed by the management server 101. Each piece of information shown below may be managed in one table, or may be divided into a plurality of tables and managed.
　図４Ａは、顧客ユーザに関する顧客情報のデータ構成例を示す。顧客情報は、例えば、顧客ＩＤ、ユーザ名、パスワード、顧客属性、参加セグメントを含んで構成される。顧客ＩＤは、顧客ユーザを一意に識別するためのＩＤ（識別情報）である。ユーザ名は顧客ユーザがサイト上で使用する自身の名称であって、顧客ユーザ向けの各種ＵＩ画面に顧客ユーザがログインする際のログイン名としても使用される。パスワードは、管理サーバ１０１が提供する、顧客ユーザ向けの各種ＵＩ画面に顧客ユーザがログインする際の認証に用いられる。顧客属性は、上述の顧客ユーザに関する情報（年齢（年代）、性別、出身地、所在地（自宅住所、勤務住所）、職業、興味対象、料金プランや制約、会員種別（シルバー会員、ゴールド会員、ダイヤモンド会員等）等）である。参加セグメントは、当該顧客ユーザがアクセス可能な固有ポータルに対応するセグメントの情報を示す。 FIG. 4A shows a data configuration example of customer information related to a customer user. The customer information includes, for example, a customer ID, a user name, a password, a customer attribute, and a participation segment. The customer ID is an ID (identification information) for uniquely identifying a customer user. The user name is its own name used by the customer user on the site, and is also used as a login name when the customer user logs in to various UI screens for the customer user. The password is used for authentication when the customer user logs in to various UI screens for the customer user provided by the management server 101. Customer attributes include information on the above customer users (age (age), gender, hometown, location (home address, work address), occupation, interest, rate plan and restrictions, membership type (silver member, gold member, diamond) Member etc.)). The participation segment indicates information on a segment corresponding to a unique portal accessible by the customer user.
　図４Ｂは、店舗に関する店舗情報のデータ構成例を示す。店舗情報は、例えば、店舗ＩＤ、店舗名、パスワード、店舗属性、商品ＩＤ、参加セグメント及び参加形態の情報を含んで構成される。店舗ＩＤは、店舗を一意に識別するためのＩＤ（識別情報）である。店舗名は、一般ポータル及び固有ポータルで使用する店舗の名称である。店舗ユーザが店舗ユーザ向けの各種ＵＩ画面にログインする際のログイン名としても利用される。パスワードは、管理サーバ１０１が提供する、店舗ユーザ向けの各種ＵＩ画面に店舗ユーザがログインする際の認証に用いられる。店舗属性は、上述の店舗が扱う商品の分類や、店舗の分類等の情報を含む。商品ＩＤは、店舗が扱う商品情報を一意に識別するための識別情報（ＩＤ）を示す。参加セグメントは、当該店舗が属するセグメントの情報を示す。参加形態は、店舗がセグメントに参加する形態の情報を含む。参加形態は後述するように店舗全体として参加する「店舗型」と、商品毎の参加する「商品型」とがある。参加形態が「店舗型」の場合、商品ＩＤには店舗が扱う商品情報の全てが登録されるか、当該商品情報の全てを管理する別テーブルへのリンク情報が登録される。一方、参加形態が「商品型」の場合、商品ＩＤには参加の対象となった商品の情報が登録される。 FIG. 4B shows a data configuration example of store information related to a store. The store information includes, for example, store ID, store name, password, store attribute, product ID, participation segment, and participation mode information. The store ID is an ID (identification information) for uniquely identifying the store. The store name is the name of the store used in the general portal and the unique portal. It is also used as a login name when a store user logs in to various UI screens for store users. The password is used for authentication when the store user logs in to various UI screens provided by the management server 101 for the store user. The store attributes include information such as the classification of products handled by the above-described stores and the classification of stores. The product ID indicates identification information (ID) for uniquely identifying product information handled by the store. The participation segment indicates information on a segment to which the store belongs. The participation form includes information on a form in which the store participates in the segment. As will be described later, there are a “store type” that participates as a whole store and a “product type” that participates for each product. When the participation form is “store type”, all product information handled by the store is registered in the product ID, or link information to another table that manages all the product information is registered. On the other hand, when the participation form is “product type”, information on the product targeted for participation is registered in the product ID.
　図４Ｃは、セグメント情報のデータ構成例を示す。セグメント情報は、例えば、セグメントＩＤ、作成店舗、マージ可否、セグメント名、セグメント属性、および参加店舗を含んで構成される。セグメントＩＤは、セグメントを一意に識別するためのＩＤ（識別情報）である。作成店舗は、セグメントを作成した店舗の店舗ＩＤが設定される。管理サーバ１０１が生成したセグメントであれば、その旨が示される。マージ可否は、類似するセグメントのマージの可否の設定を示す。マージ可否の情報の詳細及びその利用方法については、第二の実施形態にて説明する。セグメント名は、セグメントの名称を示す。 FIG. 4C shows a data configuration example of segment information. The segment information includes, for example, a segment ID, a created store, merge availability, a segment name, a segment attribute, and a participating store. The segment ID is an ID (identification information) for uniquely identifying a segment. In the created store, the store ID of the store that created the segment is set. If it is a segment generated by the management server 101, this is indicated. “Mergeability” indicates a setting of whether similar segments can be merged. Details of merge permission / inhibition information and its usage will be described in the second embodiment. The segment name indicates the name of the segment.
　セグメント属性は、セグメントに属する顧客ユーザ（ターゲット）を特定するための属性を示す。セグメント属性は、顧客ユーザがセグメントに属するユーザであるか、即ち、セグメントに対応する固有ポータルにアクセス可能な顧客ユーザであるかを判定するために利用可能である。また、当該固有ポータルにアクセス可能な潜在的な顧客ユーザを抽出するために用いることもできる。その際、セグメント属性に登録された属性は、図４Ａに示す顧客情報のテーブルに登録された属性と比較される。例えば、図４ＡのＵＳＥＲ Ａは、顧客属性が男、３０代、ゴールド会員であり、セグメントＡのセグメント属性と一致し参加資格を有している。そして、ＵＳＥＲ ＡはセグメントＡを参加セグメントとして実際に登録されている。 The segment attribute indicates an attribute for specifying a customer user (target) belonging to the segment. The segment attribute can be used to determine whether the customer user is a user belonging to the segment, i.e., a customer user who can access the unique portal corresponding to the segment. It can also be used to extract potential customer users who can access the specific portal. At that time, the attribute registered in the segment attribute is compared with the attribute registered in the customer information table shown in FIG. 4A. For example, USER A in FIG. 4A has a customer attribute of male, 30s, and a gold member, and matches the segment attribute of segment A and has the eligibility to participate. USER A actually registers segment A as a participating segment.
　また、セグメント属性は、店舗が参加可能なセグメント（固有ポータル）を特定する際にも用いることができる。例えば、店舗が固有ポータルへの参加を申請した場合、参加を許可するか否かは店舗に与えられた店舗属性の内容と、固有ポータルのセグメント属性とを比較することにより判定される。また、あるセグメントに関連付けられた固有ポータルに対して、ある店舗が新たにキャンペーン等のイベントを行いたい場合に、そのイベント登録の申請時において、属性の関係性により登録可能か否かを判断することができる。参加店舗は、そのセグメントに対応する固有ポータルに参加している店舗を示す。ここでは、店舗の店舗ＩＤが示される。参加店舗に示される店舗は、例えば、セグメントに対応する固有ポータルにイベントを登録可能である。 Also, the segment attribute can be used when specifying a segment (unique portal) in which the store can participate. For example, when a store applies for participation in a unique portal, whether or not to permit participation is determined by comparing the content of the store attribute given to the store with the segment attribute of the unique portal. In addition, when a store wants to conduct a new event, such as a campaign, for a unique portal associated with a segment, it determines whether registration is possible based on attribute relationships when applying for event registration. be able to. A participating store indicates a store participating in a unique portal corresponding to the segment. Here, the store ID of the store is shown. For example, the stores indicated in the participating stores can register events in a unique portal corresponding to the segment.
　図４Ｄは、各店舗が扱う商品の商品情報のデータ構成例を示す。ここでの商品とは、書籍、文具、食品等の物であっても良いし、宿泊予約、ゴルフ場予約、マルチメディアのダウンロードなどのサービスであってもよい。以下の説明では、簡単のために物やサービスの区別を問わず「商品」と総称して説明する。商品情報は、例えば、商品ＩＤ、商品名、店舗ＩＤ、および商品属性を含んで構成される。商品ＩＤは、商品を一意に識別するためのＩＤ（識別情報）であり、図４Ｂの店舗情報のテーブルに登録されている商品ＩＤに対応する。商品名は対応する商品の一般的な流通名称である。店舗ＩＤは、その商品を扱っている店舗の店舗ＩＤであるが、商品と店舗との関係は図４Ｂで特定可能であるので、ここでの店舗ＩＤは省略しても良い。商品属性は、商品の分類や対象（ターゲット）などを示す情報である。例えば、商品が衣服であれば、衣服の種類や名称（Ｔシャツ、セーター等）、購入対象者の性別、サイズ、価格、クーポン利用の可否、商品説明、商品写真等の情報が含まれる。 FIG. 4D shows a data configuration example of product information of products handled by each store. The goods here may be books, stationery, foods, or services such as accommodation reservations, golf course reservations, and multimedia downloads. In the following description, for the sake of simplicity, the term “product” will be collectively referred to regardless of the distinction between goods and services. The merchandise information includes, for example, a merchandise ID, a merchandise name, a store ID, and a merchandise attribute. The product ID is an ID (identification information) for uniquely identifying the product, and corresponds to the product ID registered in the store information table of FIG. 4B. The product name is a general distribution name of the corresponding product. The store ID is the store ID of the store that handles the product, but the relationship between the product and the store can be specified in FIG. 4B, so the store ID here may be omitted. The product attribute is information indicating a product category, a target (target), and the like. For example, if the product is a garment, information such as the type and name of the garment (T-shirt, sweater, etc.), the gender, size, price, availability of coupon, product description, product photo, etc.
　図４Ｅは、店舗が設定する顧客ユーザに対するキャンペーンや固有の商品の告知など（以下、「イベント」と総称する）を管理するためのイベント情報のデータ構成例を示す。イベント情報は、例えば、イベントＩＤ、イベント名、店舗ＩＤ、セグメントＩＤ、通知期間、イベント内容を含んで構成される。イベントＩＤは、イベントを一意に識別するためのＩＤ（識別情報）である。店舗ＩＤは、イベントに参加する店舗の店舗ＩＤを示す。本実施形態においてイベントは、店舗単位に実施されても良いし、固有ポータルに参加する店舗に共通に実施されても良い。後者の場合、複数の店舗ＩＤに対して同一のイベントＩＤが割り当てられる。例えば、ある店舗のみで行うイベントであれば、その店舗がイベントを登録するような構成となる。一方、複数店舗に共通して行われるイベントであれば、そのイベントを登録する際に複数の店舗を指定しても良いし、セグメント（固有ポータル）単位で指定してもよい。更には、店舗側から参加希望を受け付けるようにしてもよい。イベント名は、イベントに与えられた名称である。セグメントＩＤは、イベントの通知先（ターゲット）となるセグメントのセグメントＩＤを示す。ここで指定されたセグメントに属する顧客ユーザがイベントの通知先（ターゲット）として扱われることとなる。通知期間は、イベントの実施を顧客ユーザに対して通知する期間、即ちイベントが実施されている期間を示す。ここで指定された期間において、例えば固有ポータルの所定のＵＩ画面にてイベントの通知が行われる。イベント内容は、登録したイベントの詳細な内容を示す。イベントの種類には、例えば当該店舗にて買い物を購入する際に金券として使用可能なクーポン券の発行、当該店舗にて買い物をした場合に送料を無料とする送料無料クーポンの発行等がある。ここでの内容は店舗ユーザが細かく設定できるようにしても良いし、管理サーバ１０１側で予め設定可能な選択肢を用意しておいてもよい。また、個別の商品に対する広告や通知でも良いし（商品単位）、店舗全体に関する広告や通知であってもよい（店舗単位）。 FIG. 4E shows a data configuration example of event information for managing a campaign for a customer user set by a store, notification of a unique product, etc. (hereinafter collectively referred to as “event”). The event information includes, for example, an event ID, an event name, a store ID, a segment ID, a notification period, and event contents. The event ID is an ID (identification information) for uniquely identifying the event. Store ID shows store ID of the store which participates in an event. In the present embodiment, the event may be performed for each store or may be performed in common for stores participating in the unique portal. In the latter case, the same event ID is assigned to a plurality of store IDs. For example, if the event is performed only at a certain store, the store registers the event. On the other hand, if an event is performed in common with a plurality of stores, a plurality of stores may be specified when the event is registered, or may be specified in units of segments (unique portals). Furthermore, you may make it accept participation hope from the store side. The event name is a name given to the event. The segment ID indicates the segment ID of the segment that is the event notification destination (target). Customer users belonging to the segment specified here are treated as event notification destinations (targets). The notification period indicates a period during which an event is notified to a customer user, that is, a period during which the event is being performed. During the period specified here, for example, notification of an event is performed on a predetermined UI screen of a specific portal. The event content indicates the detailed content of the registered event. Types of events include, for example, issuing coupons that can be used as cash vouchers when purchasing shopping at the store, and issuing free shipping coupons that free shipping when shopping at the store. The contents here may be finely set by the store user, or options that can be set in advance on the management server 101 side may be prepared. Further, it may be an advertisement or notification for an individual product (product unit), or may be an advertisement or notification for the entire store (store unit).
　図４Ｆは、店舗と顧客ユーザとの間で行われた売買取引（利用履歴）の情報を管理するための取引情報のデータ構成例を示す。取引情報は、例えば、取引ＩＤ、売主、買主、日時、および取引内容を含んで構成される。取引ＩＤは、取引を一意に識別するためのＩＤ（識別情報）である。売主は、取引において商品等の売主情報を示す。ここでは、販売者である店舗の店舗ＩＤが示される。買主は、取引において商品等の買主情報を示す。ここでは、購入者である顧客ユーザの顧客ＩＤが示される。日時は、取引を行った日時情報を示す。購入した商品や購入店舗、アクセス履歴などの情報が含まれる。取引内容は、取引に用いられる商品の種類や個数、その他オプション情報などが示される。 FIG. 4F shows a data configuration example of transaction information for managing information on sales transactions (use history) performed between a store and a customer user. The transaction information includes, for example, a transaction ID, a seller, a buyer, a date and time, and a transaction content. The transaction ID is an ID (identification information) for uniquely identifying a transaction. The seller indicates seller information such as products in the transaction. Here, the store ID of the store that is the seller is shown. The buyer indicates buyer information such as products in the transaction. Here, the customer ID of the customer user who is the purchaser is shown. The date / time indicates date / time information on the transaction. Information such as purchased products, purchased stores, and access history is included. The transaction content indicates the type and number of products used for the transaction, other optional information, and the like.
　上記の各種データの構成例は、本願発明にて用いられる情報の一例であり、他の情報が含まれてもよい。 The above-described configuration examples of various data are examples of information used in the present invention, and may include other information.
　［処理フロー］
　図５～図１０は、本実施形態に係る処理のフローチャートを示す。 [Processing flow]
5 to 10 show flowcharts of processing according to the present embodiment.
　（店舗登録処理）
　図５は、店舗ユーザが店舗ＰＣ１０２から管理サーバ１０１にアクセスし、管理サーバ１０１への店舗の登録申請を行う際の処理フローを示す。本処理により店舗が登録されることにより、一般ポータルへの出店、開示が行われるようになる。これにより顧客ユーザは、一般ポータル上で登録された店舗へアクセスが可能となる。 (Store registration process)
FIG. 5 shows a processing flow when the store user accesses the management server 101 from the store PC 102 and makes a store registration application to the management server 101. By registering a store by this processing, a store is opened and disclosed on a general portal. Thereby, the customer user can access the store registered on the general portal.
　本処理フローは、管理サーバ１０１と店舗ＰＣ１０２それぞれのＣＰＵがＨＤＤ等の記憶部に格納されたプログラムを読み出して実行することにより実現される。管理サーバ１０１側では、図３に示す店舗管理部３０２、ＵＩ制御部３０４、店舗認証部３０６が機能することにより、本処理が行われる。また、店舗ＰＣ１０２は、Ｗｅｂブラウザ（不図示）を有する。店舗ＰＣ１０２は、Ｗｅｂブラウザを介して、ＨＴＴＰ（Hyper Text Transfer Protocol）などを用いて管理サーバ１０１にアクセスし、管理サーバ１０１が提供する各種ＵＩ画面を表示する。 This processing flow is realized by the CPU of each of the management server 101 and the store PC 102 reading and executing a program stored in a storage unit such as an HDD. On the management server 101 side, the store management unit 302, UI control unit 304, and store authentication unit 306 shown in FIG. The store PC 102 has a Web browser (not shown). The store PC 102 accesses the management server 101 using HTTP (Hyper Text Transfer Protocol) or the like via a Web browser, and displays various UI screens provided by the management server 101.
　Ｓ５０１にて、店舗ＰＣ１０２は、店舗ユーザからの指示に基づき、管理サーバ１０１にアクセスし、店舗登録の要求を行う。例えば、店舗ユーザは、管理サーバ１０１が提供する初期画面（図１１Ａ）にアクセスし、そこから店舗登録要求を行うことができる。図１１Ａは、各ＰＣからアクセスされた際の初期画面（一般ポータル）の構成例を示す。ログイン用画面や店舗登録を行う際のリンクなどが表示される。店舗登録を行う場合は、当該リンクを選択し店舗登録用の画面を取得することができる。また、店舗の検索や各店舗にて扱われている商品の一覧などを表示している。例えば、店舗登録を行う際には、そのリンクを店舗ユーザが選択することで、登録画面へと遷移することとなる。なお、ポータル画面の構成はこれに限定するものではなく、機能に応じて複数の画面にて提供するようにしてもよい。 In S501, the store PC 102 accesses the management server 101 based on an instruction from the store user and requests store registration. For example, the store user can access the initial screen (FIG. 11A) provided by the management server 101 and make a store registration request from there. FIG. 11A shows a configuration example of an initial screen (general portal) when accessed from each PC. A login screen and a link for registering a store are displayed. When store registration is performed, the link can be selected to obtain a store registration screen. Also, a store search, a list of products handled at each store, and the like are displayed. For example, when registering a store, the store user selects the link, thereby transitioning to a registration screen. The configuration of the portal screen is not limited to this, and the portal screen may be provided on a plurality of screens according to functions.
　Ｓ５０２にて、管理サーバ１０１は、店舗ＰＣ１０２からの店舗登録要求の応答として、店舗登録画面（図１１Ｂ）を提供する。図１１Ｂは、店舗ＰＣ１０２から受信した要求に応じて、店舗を登録する際の店舗登録画面の構成例を示す。店舗登録を行う際には、例えば店舗名、商品、オーナー情報、属性の情報を入力することができる。入力された店舗名、属性、商品の情報は、図４Ｂに示すテーブルに登録される店舗名、店舗属性の情報や、図４Ｄに示す商品属性の情報として管理される。なお、扱う商品が膨大な場合には、店舗登録の後に専用のＵＩ画面（不図示）にて各商品を登録するようにしてもよい。 In S502, the management server 101 provides a store registration screen (FIG. 11B) as a response to the store registration request from the store PC 102. FIG. 11B shows a configuration example of a store registration screen when registering a store in response to a request received from the store PC 102. When performing store registration, for example, store name, product, owner information, and attribute information can be input. The input store name, attribute, and product information are managed as store name and store attribute information registered in the table shown in FIG. 4B and product attribute information shown in FIG. 4D. In addition, when a large number of products are handled, each product may be registered on a dedicated UI screen (not shown) after store registration.
　Ｓ５０３にて、店舗ＰＣ１０２は、管理サーバ１０１から提供された店舗登録画面をＷｅｂブラウザに表示し、店舗ユーザから各種店舗情報の入力を受け付ける。その後、入力が完了したら、店舗ＰＣ１０２は、入力された店舗情報を管理サーバ１０１へ送信する。このとき、店舗にて扱う商品等の商品情報を併せて登録できるようにしてもよい。商品を登録する場合には、入力された商品は、図４Ｄに示すテーブルに登録される。この場合には、管理サーバ１０１は、商品管理部３０８を介して、商品の登録を行うこととなる。また、店舗自身に関連付ける１または複数の店舗属性の情報を登録できるようにしてもよい。ここでの登録において、管理サーバ１０１が提供するインフラサービスの料金プランや規約などに応じて、一定条件の下、登録可能な情報が変動してもよい。 In S503, the store PC 102 displays the store registration screen provided from the management server 101 on the Web browser, and accepts input of various store information from the store user. Thereafter, when the input is completed, the store PC 102 transmits the input store information to the management server 101. At this time, product information such as products handled in the store may be registered together. When registering a product, the input product is registered in the table shown in FIG. 4D. In this case, the management server 101 registers the product via the product management unit 308. Moreover, you may enable it to register the information of the 1 or several shop attribute linked | related with the shop itself. In the registration here, the information that can be registered may vary under certain conditions in accordance with the rate plan or the rules of the infrastructure service provided by the management server 101.
　Ｓ５０４にて、管理サーバ１０１は、店舗ＰＣ１０２から店舗情報を受け付けると、店舗ＩＤやパスワード等の情報を発行し、店舗情報と共に図４Ｂに示すテーブルに登録する。 In S504, when the management server 101 receives the store information from the store PC 102, the management server 101 issues information such as a store ID and a password, and registers it in the table shown in FIG. 4B together with the store information.
　Ｓ５０５にて、管理サーバ１０１は、登録完了の通知と共に、発行した情報を店舗ＰＣ１０２へ通知する。 In S <b> 505, the management server 101 notifies the store PC 102 of the issued information together with the registration completion notification.
　Ｓ５０６にて、店舗ＰＣ１０２は、管理サーバ１０１から送信された情報を受信し、その情報を表示する。その後、本処理フローを終了する。 At S506, store PC 102 receives the information transmitted from management server 101 and displays the information. Thereafter, this processing flow ends.
　（顧客ユーザ登録処理）
　図６は、顧客ユーザが顧客ＰＣ１０３から管理サーバ１０１にアクセスし、ユーザ登録を行う際の処理フローを示す。管理サーバ１０１側では、図３に示す顧客ユーザ管理部３０１、ＵＩ制御部３０４、顧客ユーザ認証部３０５が機能することにより、本処理が行われる。本処理フローは、管理サーバ１０１と顧客ＰＣ１０３それぞれのＣＰＵがＨＤＤ等に格納されたプログラムを読み出して実行することにより実現される。また、顧客ＰＣ１０３は、Ｗｅｂブラウザ（不図示）を有しており、Ｗｅｂブラウザを介して、管理サーバ１０１にアクセスし、管理サーバ１０１が提供する各種ＵＩ画面を表示する。 (Customer user registration process)
FIG. 6 shows a processing flow when a customer user accesses the management server 101 from the customer PC 103 and performs user registration. On the management server 101 side, the customer user management unit 301, UI control unit 304, and customer user authentication unit 305 shown in FIG. This processing flow is realized by the CPU of each of the management server 101 and the customer PC 103 reading and executing a program stored in the HDD or the like. The customer PC 103 has a Web browser (not shown), accesses the management server 101 via the Web browser, and displays various UI screens provided by the management server 101.
　Ｓ６０１にて、顧客ＰＣ１０３は、顧客ユーザからの指示に基づき、管理サーバ１０１にアクセスし、ユーザ登録の要求を行う。 In S601, the customer PC 103 accesses the management server 101 based on an instruction from the customer user and requests user registration.
　Ｓ６０２にて、管理サーバ１０１は、顧客ＰＣ１０３からのユーザ登録要求の応答として、顧客ユーザ登録画面（図１１Ｃ）を提供する。図１１Ｃは、顧客ＰＣ１０３から受信した要求に応じて、顧客ユーザを登録する際の顧客ユーザ登録画面の構成例を示す。顧客ユーザを登録する際には、ユーザ名、生年月日、連絡先、属性、パスワード、セグメント指定等の情報を入力することができる。その他、性別、出身地、所在地（自宅住所、勤務住所）、職業、興味対象等の個人情報を入力することができる。入力されたユーザ名、パスワード、個人情報は、例えば、図４Ａに示すテーブルに登録されるユーザ名、パスワード、顧客属性として管理される。 In S602, the management server 101 provides a customer user registration screen (FIG. 11C) as a response to the user registration request from the customer PC 103. FIG. 11C shows a configuration example of a customer user registration screen when registering a customer user in response to a request received from the customer PC 103. When registering a customer user, information such as a user name, date of birth, contact information, attribute, password, and segment designation can be input. In addition, personal information such as gender, birthplace, location (home address, work address), occupation, and interest can be entered. The input user name, password, and personal information are managed as, for example, the user name, password, and customer attribute registered in the table shown in FIG. 4A.
　Ｓ６０３にて、顧客ＰＣ１０３は、管理サーバ１０１から提供された顧客ユーザ登録画面をＷｅｂブラウザに表示し、顧客ユーザから各種ユーザ情報の入力を受け付ける。その後、入力が完了したら、顧客ＰＣ１０３は、入力されたユーザ情報を管理サーバ１０１へ送信する。このとき、顧客ユーザ自身に関連付ける１または複数の属性情報を登録できる。さらには、顧客ユーザは、自身の属性と関連するセグメントの中から任意のセグメントを選択し、参加申請するか否かを指定できる。もしくは、例えば、料金プランや顧客ユーザ自身が有する属性に応じて、管理サーバ１０１側で自動的にセグメントを割り当てるようにしてもよい。上述したように、セグメントを割り当てられた顧客ユーザは、そのセグメントに対応する固有ポータルへのアクセスが可能となる。 In S603, the customer PC 103 displays the customer user registration screen provided from the management server 101 on the Web browser, and accepts input of various user information from the customer user. Thereafter, when the input is completed, the customer PC 103 transmits the input user information to the management server 101. At this time, one or more attribute information associated with the customer user can be registered. Furthermore, the customer user can select an arbitrary segment from the segments related to his / her attributes and specify whether or not to apply for participation. Alternatively, for example, segments may be automatically allocated on the management server 101 side according to the price plan and the attributes of the customer user. As described above, a customer user who is assigned a segment can access the unique portal corresponding to the segment.
　Ｓ６０４にて、管理サーバ１０１は、顧客ＰＣ１０３からユーザ情報を受け付けると、顧客ＩＤ等の情報を発行し、図４Ａに示すテーブルにユーザ情報を登録する。ここで、受け付けたユーザ情報の中にセグメントへの参加申請が含まれる場合、顧客ユーザが選択したセグメントへの参加が可能か否かについて、承認判定、認証を行う。参加を許可する場合はそのセグメントの情報が図４Ａの参加セグメントに登録される。ここでの参加承認判定及び認証の処理の詳細に関しては、例えば顧客ユーザが有する属性や過去に購入した商品の属性と、セグメントが有する属性との対応関係などに準じて行うようにしてよい。例えば、セグメントの属性に対応する属性を有する商品を購入した実績のある顧客ユーザのみが当該セグメントに参加可能としても良い。この処理により、顧客ユーザと無関係なセグメントへの参加を防止することができる。 In S604, when receiving the user information from the customer PC 103, the management server 101 issues information such as a customer ID and registers the user information in the table shown in FIG. 4A. Here, when the application for participation in the segment is included in the received user information, approval determination and authentication are performed as to whether participation in the segment selected by the customer user is possible. When the participation is permitted, the segment information is registered in the participation segment of FIG. 4A. The details of the participation approval determination and authentication processing here may be performed in accordance with, for example, the correspondence relationship between the attribute of the customer user, the attribute of the product purchased in the past, and the attribute of the segment. For example, only a customer user who has purchased a product having an attribute corresponding to the attribute of the segment may be able to participate in the segment. By this processing, participation in a segment unrelated to the customer user can be prevented.
　Ｓ６０５にて、管理サーバ１０１は、登録完了の通知と共に、発行した情報を顧客ＰＣ１０３へ通知する。 In S605, the management server 101 notifies the customer PC 103 of the issued information together with the registration completion notification.
　Ｓ６０６にて、顧客ＰＣ１０３は、管理サーバ１０１から送信された情報を受信し、その情報を表示する。その後、本処理フローを終了する。 In S606, the customer PC 103 receives the information transmitted from the management server 101 and displays the information. Thereafter, this processing flow ends.
　（固有ポータル参加処理）
　図７は、店舗ユーザが店舗ＰＣ１０２から管理サーバ１０１にアクセスし、既に設定済みのセグメントに対応する固有ポータルへの参加を申請する際の処理フローを示す。本処理により、店舗が任意の固有ポータルに参加した場合、例えば、その固有ポータル上での店舗や商品の表示や、その固有ポータル内に限ったイベントの広告などが可能となる。 (Unique portal participation process)
FIG. 7 shows a processing flow when the store user accesses the management server 101 from the store PC 102 and applies for participation in the unique portal corresponding to the already set segment. By this process, when a store participates in an arbitrary unique portal, for example, it is possible to display a store or a product on the unique portal, or to advertise an event limited to the unique portal.
　本処理フローは、管理サーバ１０１と店舗ＰＣ１０２それぞれのＣＰＵがＨＤＤ等に格納されたプログラムを読み出して実行することにより実現される。管理サーバ１０１側では、図３に示す店舗管理部３０２、セグメント管理部３０３、ＵＩ制御部３０４、店舗認証部３０６が機能することにより本処理が行われる。また、店舗ＰＣ１０２は、Ｗｅｂブラウザ（不図示）を有しており、Ｗｅｂブラウザを介して、管理サーバ１０１にアクセスし、管理サーバ１０１が提供する各種ＵＩ画面を表示する。 This processing flow is realized by the CPU of each of the management server 101 and the store PC 102 reading and executing a program stored in the HDD or the like. On the management server 101 side, the store management unit 302, the segment management unit 303, the UI control unit 304, and the store authentication unit 306 shown in FIG. Further, the store PC 102 has a Web browser (not shown), accesses the management server 101 via the Web browser, and displays various UI screens provided by the management server 101.
　Ｓ７０１にて、店舗ＰＣ１０２は、店舗ユーザからの指示に基づき、管理サーバ１０１にアクセスし、固有ポータル参加の要求を行う。このとき、店舗はすでに管理サーバ１０１に登録され、パスワード等を用いた店舗認証部３０６による認証が完了しているものとする。 In S701, the store PC 102 accesses the management server 101 based on an instruction from the store user and requests participation in the unique portal. At this time, it is assumed that the store is already registered in the management server 101 and the authentication by the store authentication unit 306 using a password or the like has been completed.
　Ｓ７０２にて、管理サーバ１０１は、店舗ＰＣ１０２からの固有ポータルへの参加要求の応答として、固有ポータル参加画面（図１１Ｄ）を提供する。図１１Ｄは、店舗ＰＣから受信した要求に応じて、固有ポータル（セグメント）への参加を行う際の固有ポータル参加画面の構成例を示す。ここでは、店舗が参加したい固有ポータルに対応付けられたセグメント或いは固有ポータル自体を指定することで参加の要求（申請）を行うことができる。また、参加可能なセグメントのリスト（一覧）を選択可能に表示してもよい。また、セグメントに関連付けられた属性の情報を併せて表示するようにしてもよい。また、店舗ユーザが属性を入力し、入力された属性を有するセグメントに関連づけられた固有ポータルを表示し、店舗ユーザからの選択入力を受け付けるようにしても良い。 In S702, the management server 101 provides a unique portal participation screen (FIG. 11D) as a response to the participation request to the unique portal from the store PC 102. FIG. 11D shows a configuration example of a unique portal participation screen when participating in a unique portal (segment) in response to a request received from the store PC. Here, a request for participation (application) can be made by designating a segment associated with a specific portal that the store wants to participate in or a specific portal itself. In addition, a list of segments that can participate may be displayed in a selectable manner. Moreover, you may make it display the information of the attribute linked | related with the segment together. Further, the store user may input an attribute, display a unique portal associated with a segment having the input attribute, and accept a selection input from the store user.
　さらに店舗ユーザは図１１Ｄの画面で参加形態を選択することができる。ここで固有ポータル参加の形態としては、店舗全体として参加する店舗型の形態と、店舗が扱っている商品毎に参加する商品型の形態とがある。参加形態として「店舗型」を選択した場合は商品を設定する必要はない。一方、参加形態として「商品型」を選択した場合、固有ポータルに掲載する商品を選択する。商品の選択は個々の商品を指定する方法であっても良いし、商品の種別やジャンルを指定する方法であっても良い。例えば、店舗がドラッグストアである場合に、商品として紙おむつや粉ミルクを個別に指定することもできるが、ベビー用品してこれらの個別商品を包含する種別を指定することもできる。ここで設定された情報は図４Ｂの商品ＩＤ、参加セグメント及び参加形態の情報として店舗情報に登録される。 Furthermore, the store user can select a participation form on the screen of FIG. 11D. Here, as a form of participation in the unique portal, there are a store-type form that participates as a whole store and a product-type form that participates for each product handled by the store. When “store type” is selected as the participation form, it is not necessary to set a product. On the other hand, when “product type” is selected as the participation form, the product to be posted on the unique portal is selected. The selection of the product may be a method of specifying individual products, or a method of specifying the type or genre of the products. For example, when the store is a drug store, paper diapers and powdered milk can be individually specified as products, but a type including baby products and these individual products can also be specified. The information set here is registered in the store information as the product ID, participation segment, and participation form information of FIG. 4B.
　このような参加形態の選択を可能とする場合、店舗全体として参加する形態では、固有ポータルから店舗のサイトへアクセスすることが可能であり、かつ、店舗が扱っている商品が全て固有ポータルに帰属することになる。よって、固有ポータル全体に適用されるイベント（クーポンや送料無料）は店舗全体が適用対象となる。一方、商品毎の参加形態では、店舗で扱っている商品のうちの一部が選択され、固有ポータルからアクセス可能となる。この場合、固有ポータル全体に適用されるイベントがあっても、固有ポータルに登録している一部の商品等のみが対象となる。このような商品毎の参加形態により、複数種類の商品を扱っている大型店舗のように店舗全体としては固有ポータルに参加できない店舗も商品単位の参加が可能となる。 When selecting such a participation form is possible, in the form of participating as a whole store, it is possible to access the store site from the unique portal, and all the products handled by the store belong to the unique portal. Will do. Therefore, the event (coupon and free shipping) applied to the entire unique portal is applied to the entire store. On the other hand, in the participation form for each product, a part of the products handled at the store is selected and can be accessed from the unique portal. In this case, even if there is an event that applies to the entire unique portal, only some products registered in the unique portal are targeted. With such a participation form for each product, a store that cannot participate in the unique portal as a whole store, such as a large store that handles a plurality of types of products, can participate in product units.
　Ｓ７０３にて、店舗ＰＣ１０２は、管理サーバ１０１から提供された固有ポータル参加画面をＷｅｂブラウザに表示し、店舗ユーザから参加対象となる固有ポータル（セグメント）の情報の入力を受け付ける。その後、店舗ＰＣ１０２は、選択された固有ポータルの情報を、管理サーバ１０１へ送信する。なお、セグメントの選択時において、参加できない固有ポータル（セグメント）については、初めから表示されないようにＵＩ画面の表示制御を行うようにしてもよい。参加できない固有ポータルとは、該固有ポータルに関連づけられたセグメントが有する属性を店舗或いは該店舗が扱う商品が有していない固有ポータルのことである。この場合、当該店舗はその固有ポータルに参加する資格を有していないので予め選択肢から除外しておくことが望ましい。あるいは、将来的な参加の動機づけを与えるべく、一覧表示には含めてもよいが、グレーアウトするなどして選択対象から除外してもよい。 In S703, the store PC 102 displays the unique portal participation screen provided from the management server 101 on the Web browser, and accepts input of information on the specific portal (segment) to be participated from the store user. Thereafter, the store PC 102 transmits information on the selected unique portal to the management server 101. When selecting a segment, UI screen display control may be performed so that unique portals (segments) that cannot participate are not displayed from the beginning. The unique portal that cannot participate is a unique portal that does not have the attribute of the segment associated with the unique portal, or the product that the store handles. In this case, since the store does not have the qualification to participate in the unique portal, it is desirable to exclude it from the options in advance. Alternatively, in order to provide motivation for future participation, it may be included in the list display, but may be excluded from the selection target by being grayed out.
　次にＳ７０４にて、管理サーバ１０１は、店舗ＰＣ１０２から固有ポータルの選択を受け付けると、当該店舗が選択された固有ポータルに参加可能か否かについて、承認判定、認証を行う。Ｓ７０４で参加が許可されると、参加が許可された固有ポータルのセグメントの情報が図４Ｂの参加セグメントに登録されると共に、図４Ｃに示す参加店舗に当該店舗の情報が登録される。る。 Next, in S <b> 704, when the management server 101 receives selection of a unique portal from the store PC 102, the management server 101 performs approval determination and authentication as to whether or not the store can participate in the selected unique portal. When participation is permitted in S704, the information of the segment of the specific portal permitted to participate is registered in the participation segment of FIG. 4B, and the information of the store is registered in the participating store shown in FIG. 4C. The
　Ｓ７０４における判定及び認証の処理の詳細に関しては、店舗ＰＣ１０２側から固有ポータルへの参加要求があった後、管理サーバ１０１側で入力内容の確認を行った上で参加させる。この場合の承認判定では、例えば、店舗側の権限（店舗によるインフラサービスの利用プラン）や規約、固有ポータルに関連付けられたセグメントと店舗が有する属性、もしくは店舗が扱う商品が有する属性の対応関係などに準じて行うようにしてよい。 Regarding the details of the determination and authentication processing in S704, after the store PC 102 requests to participate in the unique portal, the management server 101 confirms the input content and participates. In the approval judgment in this case, for example, the authority of the store (infrastructure service use plan by the store) and the rules, the correspondence between the segment and the attribute associated with the unique portal, or the attribute of the product handled by the store, etc. You may make it carry out according to.
　さらに、承認判定では、固有ポータルに参加する条件として、固有ポータルに登録している顧客ユーザと取引実績があることを要求しても良いし、店舗の評価として一定以上の評価を獲得していることを要求しても良い。取引実績の有無は図４Ｆの取引情報を参照することにより判定が可能である。実績の有無についても、単なる有る無しに限らず、固有ポータルに登録している顧客ユーザ数に応じた閾値を設けて、参加ユーザ数が多い固有ポータルについては、店舗の参加条件としてより多くの取引実績を要求するようにしても良い。その逆に、顧客ユーザ数が多い固有ポータルについては取引実績の条件を緩和して閾値を低く設定する一方、新規に設立された固有ポータルについて、セグメントの属性に対応する商品やサービスの販売実績、或いは当該属性を有する顧客ユーザとの取引実績の多いことを条件としても良い。 Furthermore, in the approval judgment, as a condition for participating in the unique portal, it may be requested that there is a transaction record with the customer user registered in the unique portal, and the evaluation of the store has obtained a certain level of evaluation. You may request that. The presence / absence of transaction results can be determined by referring to the transaction information in FIG. 4F. Whether or not there is a track record is not limited to simply having a track record, but a threshold is set according to the number of customer users registered in the unique portal. You may make it request | require results. Conversely, for unique portals with a large number of customer users, the thresholds are set lower by relaxing the transaction performance conditions, while for newly established unique portals, sales performance of products and services corresponding to segment attributes, Or it is good also as conditions that there are many transaction results with the customer user who has the said attribute.
　Ｓ７０５にて、管理サーバ１０１は、固有ポータルへの参加処理の完了の通知を店舗ＰＣ１０２へ送信する。 In S <b> 705, the management server 101 transmits a notification of completion of the participation process to the unique portal to the store PC 102.
　Ｓ７０６にて、店舗ＰＣ１０２は、固有ポータルへの参加処理の完了の通知を管理サーバ１０１から受信し、その旨を表示する。その後、本処理フローを終了する。 In S706, the store PC 102 receives a notification of completion of the process of participating in the unique portal from the management server 101, and displays that effect. Thereafter, this processing flow ends.
　（セグメント登録処理）
　図７では、設定済みの固有ポータルへ店舗が参加を申請する場合の処理について説明したが、以下では店舗が新たにセグメントを設定し固有ポータルを開設する場合の処理について説明する。図８は、店舗ユーザが店舗ＰＣ１０２から管理サーバ１０１にアクセスし、セグメントを登録する際の処理フローを示す。管理サーバ１０１側では、図３に示す店舗管理部３０２、セグメント管理部３０３、ＵＩ制御部３０４、店舗認証部３０６、検索部３０７が機能することにより、本処理が行われる。 (Segment registration process)
In FIG. 7, the process in the case where the store applies for participation to the set unique portal has been described. Hereinafter, the process in the case where the store newly sets a segment and opens a unique portal will be described. FIG. 8 shows a processing flow when the store user accesses the management server 101 from the store PC 102 and registers a segment. On the management server 101 side, the store management unit 302, segment management unit 303, UI control unit 304, store authentication unit 306, and search unit 307 shown in FIG.
　本処理フローは、管理サーバ１０１と店舗ＰＣ１０２それぞれのＣＰＵがＨＤＤ等に格納されたプログラムを読み出して実行することにより実現される。また、店舗ＰＣ１０２は、Ｗｅｂブラウザ（不図示）を有しており、Ｗｅｂブラウザを介して、管理サーバ１０１にアクセスし、管理サーバ１０１が提供する各種ＵＩ画面を表示する。 This processing flow is realized by the CPU of each of the management server 101 and the store PC 102 reading and executing a program stored in the HDD or the like. Further, the store PC 102 has a Web browser (not shown), accesses the management server 101 via the Web browser, and displays various UI screens provided by the management server 101.
　Ｓ８０１にて、店舗ＰＣ１０２は、店舗ユーザからの指示に基づき、管理サーバ１０１にアクセスし、セグメント登録の要求を行う。このとき、店舗はすでに管理サーバ１０１に登録され、パスワード等を用いた認証が完了しているものとする。 In S801, the store PC 102 accesses the management server 101 based on an instruction from the store user and requests segment registration. At this time, it is assumed that the store is already registered in the management server 101 and authentication using a password or the like has been completed.
　Ｓ８０２にて、管理サーバ１０１は、店舗ＰＣ１０２からのセグメント登録要求の応答として、セグメント登録画面（図１１Ｅ）を提供する。図１１Ｅは、店舗ＰＣ１０２から受信した要求に応じて、セグメントを登録する際のセグメント登録画面の構成例を示す。顧客ユーザは、セグメント名、属性、マージの可否について入力することができる。入力されたセグメント名、属性、マージの可否は、セグメントが設定された後に、図４Ｃに示すテーブルに登録されるセグメント名、マージ可否、セグメント属性として管理される。なお、図１１Ｅでは、属性をまとめて設定するような構成にしているが、店舗、顧客ユーザ、商品といった分類ごとに属性を設定できるようにしてもよい。 In S802, the management server 101 provides a segment registration screen (FIG. 11E) as a response to the segment registration request from the store PC 102. FIG. 11E shows a configuration example of a segment registration screen when registering a segment in response to a request received from the store PC 102. The customer user can input the segment name, the attribute, and whether merge is possible. The input segment name, attribute, and merge possibility are managed as the segment name, merge possibility, and segment attribute registered in the table shown in FIG. 4C after the segment is set. In FIG. 11E, the attributes are set collectively, but the attributes may be set for each category such as store, customer user, and product.
　Ｓ８０３にて、店舗ＰＣ１０２は、管理サーバ１０１から提供されたセグメント登録画面をＷｅｂブラウザに表示する。 In S803, the store PC 102 displays the segment registration screen provided from the management server 101 on the Web browser.
　Ｓ８０４にて、店舗ＰＣ１０２は、店舗ユーザから各種セグメント情報の入力を受け付ける。この時、店舗ＰＣ１０２は、セグメントに対応付ける属性の入力を受け付ける。その後、店舗ＰＣ１０２は、受け付けた１または複数の属性の情報を、管理サーバ１０１へ送信する。 In S804, the store PC 102 receives input of various segment information from the store user. At this time, the store PC 102 receives an input of an attribute associated with the segment. Thereafter, the store PC 102 transmits the received information of one or more attributes to the management server 101.
　Ｓ８０５にて、管理サーバ１０１は、受信した属性の組み合わせに基づいて、その属性の組み合わせに該当する顧客ユーザの情報をテーブルから検索し、抽出する。ここで抽出される顧客ユーザの情報とは、例えば顧客ユーザの総数などが該当するが、他の情報であってもよい。例えば、抽出された顧客ユーザを年代、性別、職業、出身地、所在地、興味対象等に分類し、分類毎の顧客ユーザ数を提供しても良い。或いは、属性に関連する商品を購入した実績のある顧客ユーザ数であってもよい。これらの条件はＳ８０４にて顧客ユーザが属性と共に入力しても良い。なお、顧客情報は個人情報に該当し、一般的に管理上の厳密な制限が想定されるため、顧客ユーザの個人名や住所等の詳細な情報は出力されないようにしてよい。また、店舗ユーザによって複数の属性が入力された場合、属性のＡＮＤ条件で検索しても良いし、ＯＲ条件で検索してもよい。また、店舗ユーザが入力可能な属性の数について、検索結果に応じて上限数／下限数を設定してもよい。検索が完了した後、管理サーバ１０１は、検索結果を店舗ＰＣ１０２に通知する。 In S805, based on the received attribute combination, the management server 101 searches the table for customer user information corresponding to the attribute combination. The customer user information extracted here corresponds to the total number of customer users, for example, but may be other information. For example, the extracted customer users may be classified into age, sex, occupation, birthplace, location, interest, etc., and the number of customer users for each classification may be provided. Alternatively, it may be the number of customer users who have a record of purchasing a product related to the attribute. These conditions may be input by the customer user together with attributes in S804. Note that customer information corresponds to personal information, and generally strict management restrictions are assumed. Therefore, detailed information such as the personal name and address of the customer user may not be output. Further, when a plurality of attributes are input by the store user, the search may be performed using the AND condition of the attributes, or may be performed using the OR condition. Moreover, you may set an upper limit number / lower limit number according to a search result about the number of the attributes which a shop user can input. After the search is completed, the management server 101 notifies the store PC 102 of the search result.
　また、Ｓ８０５にて店舗ユーザが入力可能な属性は、店舗ユーザの店舗が有する属性と一致または、当該属性と関連するもの（属性の範囲に含まれるもの）に限定してもよい。この属性の関連性或いは範囲について、本実施形態では属性を上位概念、中位概念、下位概念のように階層的に設定することができる。下位概念は上位概念、中位概念の範囲に含まれ、中位概念は上位概念の範囲に含まれる。例えば、衣服という上位概念の範囲には洋服、和服などの中位概念が含まれ、洋服の下位概念にはスーツ、ジャケット、パンツ等が含まれる。よって、「衣服」という属性が選択されれば、スーツやジャケットは当該属性に関連すると共にその範囲に含まれることとなる。このように入力可能な属性を制限することにより、店舗に無関係なセグメントの設定を防止することができる。 In addition, the attributes that can be input by the store user in S805 may be limited to attributes that match or are related to the attributes of the store user's store (included in the attribute range). With regard to the relevance or range of this attribute, in the present embodiment, the attribute can be set hierarchically such as a higher concept, a middle concept, and a lower concept. The subordinate concept is included in the range of the superordinate concept and the intermediate concept, and the intermediate concept is included in the range of the superordinate concept. For example, the scope of the upper concept of clothes includes a medium concept such as clothes and Japanese clothes, and the lower concept of clothes includes a suit, a jacket, pants, and the like. Therefore, if the attribute “clothes” is selected, the suit or jacket is related to the attribute and included in the range. By limiting the attributes that can be input in this way, it is possible to prevent the setting of segments unrelated to the store.
　Ｓ８０６にて、店舗ＰＣ１０２は、管理サーバ１０１から送信された情報を受信し、その情報を表示する。その検索結果に基づき、店舗ＰＣ１０２は、店舗ユーザからそのセグメント情報の内容で登録するか否かの指示を受け付ける。 In S806, store PC102 receives the information transmitted from management server 101, and displays the information. Based on the search result, the store PC 102 receives an instruction from the store user as to whether or not to register with the contents of the segment information.
　Ｓ８０７にて、店舗ＰＣ１０２は、店舗ユーザから登録の指示を受け付けたか否かを判定する。登録の指示を受け付けた場合（Ｓ８０７にてＹＥＳ）Ｓ８０８へ進み、入力した属性を変更する指示を受け付けた場合（Ｓ８０７にてＮＯ）Ｓ８０４へ進み、処理を繰り返す。店舗ユーザは、検索結果を参照することで、設定した属性が、店舗が潜在的な顧客とすべき顧客ユーザを適切に囲い込んでいるかどうかを判定することができる。店舗ユーザは期待した検索結果が得られなかった場合には属性の設定をやり直して再度上記の処理を繰り返すことができる。これにより、店舗ユーザは潜在的な顧客ユーザを効率的に囲い込むことが可能な固有ポータルを設立することができる。 In S807, the store PC 102 determines whether or not a registration instruction has been received from the store user. If a registration instruction is accepted (YES in S807), the process proceeds to S808. If an instruction to change the input attribute is accepted (NO in S807), the process proceeds to S804, and the process is repeated. By referring to the search result, the store user can determine whether the set attribute appropriately surrounds the customer user that the store should be a potential customer. When the store user cannot obtain the expected search result, the store user can redo the attribute setting and repeat the above process. Thereby, the store user can establish a unique portal that can efficiently enclose potential customer users.
　Ｓ８０８にて、店舗ＰＣ１０２は、店舗ユーザから受け付けた登録の指示および入力されたセグメント情報を管理サーバ１０１へ送信する。 In S808, store PC 102 transmits the registration instruction received from the store user and the input segment information to management server 101.
　Ｓ８０９にて、管理サーバ１０１は、店舗ＰＣ１０２からセグメント情報を受け付けると、セグメントＩＤ等の情報を発行し、図４Ｃに示すテーブルにセグメント情報を登録する。このとき、セグメントを作成した店舗をはじめから参加させるような構成でも良いし、作成した店舗が選択できるような構成であってもよい。ここで、管理サーバ１０１はセグメント情報に該当する店舗数や顧客ユーザ数に基づき、所定の閾値を超えない店舗数や顧客ユーザ数のセグメントの作成を拒否する構成にしても良い。また、セグメントの作成の可否は、セグメント情報に含まれる属性に該当する顧客ユーザとの取引実績（販売実績）の有無を考慮しても良い。例えば、当該顧客ユーザとの販売実績のない店舗や、一定数以上の販売実績がない店舗にはセグメントの作成権利を認めないこととして、申請を拒否することができる。 In S809, upon receiving the segment information from the store PC 102, the management server 101 issues information such as a segment ID and registers the segment information in the table shown in FIG. 4C. At this time, the structure which makes the store which created the segment participate from the beginning may be sufficient, and the structure which can select the created store may be sufficient. Here, the management server 101 may be configured to reject the creation of the number of stores and the number of customer users that do not exceed a predetermined threshold based on the number of stores and the number of customer users corresponding to the segment information. In addition, whether or not a segment can be created may consider the presence or absence of a transaction record (sales record) with a customer user corresponding to the attribute included in the segment information. For example, an application can be rejected as not allowing the right to create a segment to a store that has no sales record with the customer user or a store that does not have a certain number of sales records.
　Ｓ８１０にて、管理サーバ１０１は、登録完了の通知を店舗ＰＣ１０２へ送信する。 In S810, the management server 101 transmits a registration completion notification to the store PC 102.
　Ｓ８１１にて、店舗ＰＣ１０２は、登録完了の通知を管理サーバ１０１から受信し、その旨を表示する。その後、本処理フローを終了する。 In S811, the store PC 102 receives a registration completion notification from the management server 101, and displays that fact. Thereafter, this processing flow ends.
　なお、図８では、新たにセグメントを生成し、登録する際の処理の流れを示したが、すでに登録されているセグメントの内容を編集する際も同様の流れで行われる。主な編集内容としては、セグメントに対応づける属性の追加・修正・削除等がある。編集の場合は、Ｓ８０１～Ｓ８０３の工程で変更要求を送信し、その応答として得られる編集画面にて、編集対象となるセグメントを選択することとなる。 Although FIG. 8 shows the flow of processing when a new segment is created and registered, the same flow is performed when editing the contents of a segment that has already been registered. The main editing contents include addition / modification / deletion of attributes associated with segments. In the case of editing, a change request is transmitted in steps S801 to S803, and a segment to be edited is selected on the editing screen obtained as a response.
　（イベント登録処理）
　図９は、本実施形態に係るイベント登録処理のフローチャートを示す。管理サーバ１０１側では、図３に示す店舗管理部３０２、セグメント管理部３０３、ＵＩ制御部３０４、店舗認証部３０６、イベント管理部３０９が機能することにより、本処理が行われる。 (Event registration process)
FIG. 9 shows a flowchart of event registration processing according to the present embodiment. On the management server 101 side, the store management unit 302, the segment management unit 303, the UI control unit 304, the store authentication unit 306, and the event management unit 309 shown in FIG.
　本処理フローは、管理サーバ１０１と店舗ＰＣ１０２それぞれのＣＰＵがＨＤＤ等に格納されたプログラムを読み出して実行することにより実現される。また、店舗ＰＣ１０２は、Ｗｅｂブラウザ（不図示）を有しており、Ｗｅｂブラウザを介して、管理サーバ１０１にアクセスし、管理サーバ１０１が提供する各種ＵＩ画面を表示する。なお、ここで登録されるイベントの表示や通知に関する処理は図１０を用いて後述する。 This processing flow is realized by the CPU of each of the management server 101 and the store PC 102 reading and executing a program stored in the HDD or the like. Further, the store PC 102 has a Web browser (not shown), accesses the management server 101 via the Web browser, and displays various UI screens provided by the management server 101. The processing related to the display and notification of events registered here will be described later with reference to FIG.
　Ｓ９０１にて、店舗ＰＣ１０２は、店舗ユーザからの指示に基づき、管理サーバ１０１にアクセスし、イベント登録の要求を行う。このとき、店舗はすでに管理サーバ１０１に登録され、店舗認証部３０６によりパスワード等を用いた認証が完了しているものとする。また、イベントの登録において、店舗ごとに登録数の上限を設定しても良いし、イベントの内容に応じて登録可否を判定してもよい。この場合、一旦、店舗ＰＣ１０２から登録の要求があった後、管理サーバ１０１側でイベント登録の承認処理（不図示）を行うように制御するものとする。 In S901, the store PC 102 accesses the management server 101 based on an instruction from the store user and requests event registration. At this time, it is assumed that the store has already been registered in the management server 101 and the store authentication unit 306 has completed authentication using a password or the like. In addition, in event registration, an upper limit of the number of registrations may be set for each store, and registration availability may be determined according to the contents of the event. In this case, once there is a registration request from the store PC 102, the management server 101 is controlled to perform an event registration approval process (not shown).
　Ｓ９０２にて、管理サーバ１０１は、店舗ＰＣ１０２からのイベント登録要求の応答として、イベント登録画面（図１１Ｆ）を提供する。図１１Ｆは、店舗ＰＣ１０２から受信した要求に応じて、イベントを登録する際のイベント登録画面の構成例を示す。店舗ユーザは、イベント名、セグメントＩＤ、通知期間、イベント内容の情報を入力することができる。入力された情報は、図４Ｅに示すテーブルに登録されるイベント名、セグメントＩＤ、通知期間、イベント内容の情報として管理される。なお、すでに登録されているセグメントから選択する際には、選択可能なセグメントのリストを表示させるようにしてもよい。 In S902, the management server 101 provides an event registration screen (FIG. 11F) as a response to the event registration request from the store PC 102. FIG. 11F shows a configuration example of an event registration screen when an event is registered in response to a request received from the store PC 102. The store user can input event name, segment ID, notification period, and event content information. The input information is managed as event name, segment ID, notification period, and event content information registered in the table shown in FIG. 4E. When selecting from already registered segments, a list of selectable segments may be displayed.
　Ｓ９０３にて、店舗ＰＣ１０２は、管理サーバ１０１から提供されたイベント登録画面をＷｅｂブラウザに表示する。 In S903, the store PC 102 displays the event registration screen provided from the management server 101 on the Web browser.
　Ｓ９０４にて、店舗ＰＣ１０２は、店舗ユーザから各種イベント情報の入力を受け付ける。この時、イベントに対応付けるセグメントの選択を受け付ける。ここで店舗ユーザが選択可能なセグメントは、店舗が参加している固有ポータルに対応するセグメントが相当する。セグメントの選択時において、登録ができないセグメントは予め表示されないように、或いは選択ができないようにＵＩ画面の表示制御を行うようにしてもよい。また、固有ポータルに限定したイベントではなく、一般ポータルにて行うイベントであれば、セグメントの選択は行わず、対象を一般ポータルとして設定することとなる。なお、この工程で新たにセグメントを生成できるようにしても良い。その後、店舗ＰＣ１０２は、受け付けたイベント情報を、管理サーバ１０１へ送信する。各種イベント情報の設定として店舗側がターゲットとするセグメント（顧客ユーザ）を選択することで、登録するイベントの対象としたい相手（セグメントおよびそれに関連付けられた固有ポータル）を明確に指定することができる。また、店舗が固有ポータルに参加していない場合であっても、店舗側から固有の商品に関するイベントを登録しようとする際には、その商品が有する属性と、登録しようとするセグメントに関連付けられた属性とが一致することで、登録を許可するようにしてもよい。また、セグメントを選択した際に、イベントの通知対象となる顧客ユーザ数が表示されるような構成にしてもよい。 In S904, the store PC 102 receives input of various event information from the store user. At this time, selection of a segment associated with the event is accepted. Here, the segment that can be selected by the store user corresponds to a segment corresponding to a specific portal in which the store participates. When selecting a segment, UI screen display control may be performed so that a segment that cannot be registered is not displayed in advance or cannot be selected. In addition, if the event is not an event limited to a specific portal but an event performed on a general portal, the segment is not selected and the target is set as a general portal. Note that a new segment may be generated in this step. Thereafter, the store PC 102 transmits the received event information to the management server 101. By selecting a segment (customer user) targeted by the store as a setting of various event information, it is possible to clearly specify the other party (segment and unique portal associated therewith) that is desired to be registered as an event target. Even if the store does not participate in the unique portal, when trying to register an event related to a unique product from the store side, it is associated with the attribute of the product and the segment to be registered. Registration may be permitted when the attribute matches. In addition, when a segment is selected, the number of customer users who are notified of an event may be displayed.
　Ｓ９０５にて、管理サーバ１０１は、店舗ＰＣ１０２からイベント情報を受け付けると、イベント管理部３０９によりイベントＩＤ等の情報を発行し、図４Ｅに示すテーブルにイベント情報を登録する。なお、登録においては別途申請／承認や、認証などの構成を設けてもよい。例えば、Ｓ９０４の工程において、店舗ＰＣ１０２側からイベントの情報入力があった後、管理サーバ１０１側で入力内容の確認（自動判定、もしくは管理者による判定）を行った上で登録処理を行うようにしてもよい。この場合の確認では、例えば、店舗側の権限（店舗によるインフラサービスの利用プラン）や規約などに準じて行うようにしてよい。 In S905, upon receiving event information from the store PC 102, the management server 101 issues information such as an event ID by the event management unit 309, and registers the event information in the table shown in FIG. 4E. In addition, you may provide structures, such as application / approval and authentication, separately in registration. For example, in the process of S904, after the event information is input from the store PC 102 side, the registration process is performed after confirming the input content (automatic determination or determination by the administrator) on the management server 101 side. May be. The confirmation in this case may be performed in accordance with, for example, authority on the store side (infrastructure service use plan by the store) or rules.
　Ｓ９０６にて、管理サーバ１０１は、登録完了の通知を店舗ＰＣ１０２へ送信する。 In S906, the management server 101 transmits a registration completion notification to the store PC 102.
　Ｓ９０７にて、店舗ＰＣ１０２は、登録完了の通知を管理サーバ１０１から受信し、その旨を表示する。その後、本処理フローを終了する。 In S907, the store PC 102 receives a registration completion notification from the management server 101, and displays that fact. Thereafter, this processing flow ends.
　上記図５から図９の説明では、顧客ユーザ、店舗、商品、イベント、セグメントなどに対する登録の処理について説明したが、例えば、すでに登録している情報を編集する際においても同様の流れで行うことが可能である。この場合には、各ＰＣからの要求に応じて、編集用のＵＩ画面（不図示）が管理サーバ１０１から各ＰＣに提供され、そのＵＩ画面を介して編集が行われるものとする。 In the description of FIGS. 5 to 9 described above, the registration process for the customer user, the store, the product, the event, the segment, and the like has been described. For example, the same process is performed when editing the already registered information. Is possible. In this case, in response to a request from each PC, an editing UI screen (not shown) is provided from the management server 101 to each PC, and editing is performed via the UI screen.
　（イベント通知処理）
　以下、本実施形態に係るイベントの通知方法について説明する。本実施形態では、顧客ユーザがユーザ登録を行った後に、管理サーバ１０１が提供するサービスサイトへログインすることでアクセス可能な固有ポータルへ遷移できるものとする。固有ポータルサイトでは、対応するセグメントに応じて表示される内容（イベント）が異なるものとする。具体的には、上述したように、セグメントそれぞれには固有ポータルが対応付けられ、その固有ポータルに対して登録されたイベントが表示される。同様に、一般ポータルにアクセスした際には、その一般ポータル向けに登録されたイベントが通知されることとなる。顧客ユーザが有する属性情報に応じて、その顧客ユーザがアクセス可能なポータルサイト（固有ポータル）が変化することとなる。 (Event notification processing)
The event notification method according to this embodiment will be described below. In the present embodiment, it is assumed that after a customer user performs user registration, the user can make a transition to an accessible unique portal by logging in to a service site provided by the management server 101. In the unique portal site, contents (events) displayed in accordance with corresponding segments are different. Specifically, as described above, a unique portal is associated with each segment, and an event registered for the unique portal is displayed. Similarly, when accessing a general portal, an event registered for the general portal is notified. Depending on the attribute information of the customer user, the portal site (unique portal) that can be accessed by the customer user changes.
　図１０は、本実施形態に係るイベントの通知の処理フローを示す。本処理フローは、管理サーバ１０１のＣＰＵがＨＤＤ等の記憶部に格納されたプログラムを読み出して実行することにより実現される。管理サーバ１０１側では、図３に示す顧客ユーザ管理部３０１、ＵＩ制御部３０４、顧客ユーザ認証部３０５、イベント管理部３０９が機能することにより、本処理が行われる。 FIG. 10 shows a process flow of event notification according to the present embodiment. This processing flow is realized by the CPU of the management server 101 reading and executing a program stored in a storage unit such as an HDD. On the management server 101 side, the customer user management unit 301, UI control unit 304, customer user authentication unit 305, and event management unit 309 shown in FIG.
　Ｓ１００１にて、管理サーバ１０１は、顧客ＰＣ１０３を介して、顧客ユーザからのログイン要求を受け付ける。この時、管理サーバ１０１は、ユーザＩＤおよびパスワードを併せて受け付け、認証処理を行う。ここでは、認証が成功しているものとして処理を進める。 In S1001, the management server 101 receives a login request from a customer user via the customer PC 103. At this time, the management server 101 receives the user ID and password together and performs authentication processing. Here, the process proceeds assuming that the authentication is successful.
　Ｓ１００２にて、管理サーバ１０１は、認証が成功した顧客ユーザの顧客情報を参照し、参加可能に登録されているセグメントがあるか否かを判定する。参加可能なセグメントがある場合（Ｓ１００２にてＹＥＳ）にてＳ１００３へ進み、参加可能なセグメントが無い場合（Ｓ１００２にてＮＯ）本処理フローを終了する。 In S1002, the management server 101 refers to the customer information of the customer user who has been successfully authenticated, and determines whether there is a segment registered to be able to participate. If there is a segment that can participate (YES in S1002), the process proceeds to S1003. If there is no segment that can participate (NO in S1002), the process flow ends.
　Ｓ１００３にて、管理サーバ１０１は、ログインした顧客ユーザに対し、参加可能なセグメントに対応付けられた固有ポータルへのアクセスを許可する。 In S1003, the management server 101 permits the logged-in customer user to access a unique portal associated with a segment that can be participated.
　Ｓ１００４にて、管理サーバ１０１は、Ｓ１００３にてアクセスを許可された固有ポータルに顧客ユーザからアクセスされた際に、図４Ｅのテーブルに基づいて、セグメントに対応するイベントを表示（図１１Ｇ）するように制御する。図１１Ｇは、顧客ユーザが固有ポータルのページにアクセスした際に表示される、イベントの通知画面の構成例を示す。ここでは、顧客ユーザがアクセス可能な固有ポータルにアクセスした際に、その固有ポータルに係るイベントが表示される。図１１Ｇの例では、イベントが一覧形式で表示されているがこれに限定するものではなく、例えば、ページ内のイベント表示用の領域に時間ごとに切り替わるように表示されても良い。その後、本処理フローを終了する。 In S1004, the management server 101 displays an event corresponding to the segment (FIG. 11G) based on the table in FIG. 4E when the customer user accesses the unique portal permitted to access in S1003. To control. FIG. 11G shows a configuration example of an event notification screen displayed when a customer user accesses a page of a specific portal. Here, when a customer portal accesses a unique portal accessible, events related to the unique portal are displayed. In the example of FIG. 11G, the events are displayed in a list format, but the present invention is not limited to this. For example, the events may be displayed so as to switch to the event display area in the page. Thereafter, this processing flow ends.
　なお、本実施形態では、アクセス可能な固有ポータル上にて表示して通知を行う例を示したが、これに限定するものではなく、他の通知方法で行うようにしてもよい。 In this embodiment, an example is shown in which notification is displayed on an accessible unique portal, but the present invention is not limited to this, and other notification methods may be used.
　［本実施形態の効果］
　以上で説明した本実施形態によれば、管理サーバが提供するポータルサイト（一般ポータル）に登録している顧客ユーザのうち、特定の属性と関連する顧客ユーザのみを対象とした固有ポータルを提供することができる。当該固有ポータルは一般ポータルに登録している店舗のうち、上記特定の属性に関する条件を満たす特定の店舗のみが参加可能である。即ち、固有ポータルは特定の属性に関連する店舗と顧客ユーザとが取引を行う場として提供されるポータルサイトであって、顧客ユーザの立場からは、固有ポータルに参加することにより自身が必要とする商品やサービスを効率的に探し出して購入することができるので、多数の店舗や商品の中から自分が必要とする商品や店舗を探し出す手間や負担を効果的に削減することが可能となる。また、店舗の立場からは、店舗が扱う商品、サービスに対する需要（ニーズ）を有する顧客ユーザを囲い込んで、その顧客ユーザに対して効率的に商品、サービスを提供できるので、効率的な店舗運営が可能となる。特に、一般ポータルにおいて不特定多数の顧客ユーザに対してプロモーションを行うよりも、より確実に販売に結びつけることが可能となり、販売実績を効率的に向上させることが可能となる。 [Effect of this embodiment]
According to the present embodiment described above, a unique portal is provided only for customer users related to specific attributes among customer users registered in the portal site (general portal) provided by the management server. be able to. Only the specific store which satisfy | fills the conditions regarding the said specific attribute among the stores registered into the general portal can participate in the said specific portal. In other words, the unique portal is a portal site that is provided as a place for transactions between a store related to a specific attribute and a customer user. From the standpoint of the customer user, the unique portal needs it by participating in the unique portal. Since it is possible to efficiently search for and purchase products and services, it is possible to effectively reduce the effort and burden of searching for the products and stores that are required from among a large number of stores and products. In addition, from the standpoint of the store, it is possible to enclose customer users who have demands (needs) for the products and services handled by the stores, and to efficiently provide products and services to the customer users. Is possible. In particular, it is possible to connect to sales more reliably than to conduct promotions for an unspecified number of customer users in a general portal, and sales performance can be improved efficiently.
　また、本実施形態の固有ポータルは、管理サーバが参加可能な店舗や顧客ユーザに条件を設定することで構築されており、固有ポータルで扱う商品、サービスに無関係な店舗や顧客ユーザ、販売実績や評価の低い店舗などを排除することができる。これにより、顧客ユーザの立場からは、固有ポータルに参加するだけで、自分が必要とする商品を扱っている店舗を絞り込む手間を確実に省くことが可能となり、これまで取引が無い店舗でも簡単に探し出すことができる。また固有ポータルに訪問すれば、固有ポータルの店舗が行っているイベントの情報を確実に入手できるのでイベント情報の見落としも防止することができる。一方の店舗の立場からは、自身商品やサービスを必要としている顧客ユーザに対してイベント通知などの働きかけが可能となるので、すでに取引を行っている顧客ユーザのみならず、これまでは購入履歴等が無い潜在的な顧客ユーザに対しても、店舗へ効果的に誘導することが可能となる。 In addition, the unique portal of this embodiment is constructed by setting conditions for stores and customer users to which the management server can participate, and stores and customer users who are not related to products and services handled by the unique portal, sales results, Stores with low evaluations can be excluded. As a result, from the customer user's standpoint, it is possible to save time and effort to narrow down the stores that handle the products that they need by simply participating in the unique portal. You can find out. Also, if you visit a unique portal, you can reliably obtain information on the events that are held by the stores of the unique portal, so you can prevent oversight of event information. From the standpoint of one store, it is possible to encourage customer users who need their products and services, such as event notifications, so not only customer users who have already made transactions, but also purchase histories so far Even a potential customer user who does not have a customer can be effectively guided to the store.
　＜第二の実施形態＞
　本実施形態は、店舗ユーザにて設定されたセグメントを、その類似度に応じてマージ（統合）する実施形態である。店舗ユーザが複数のセグメントを生成した場合に、類似するセグメントが生成されることが考えられる。このような場合には、セグメントをマージすることで、セグメントの管理を容易にする。また類似のセグメントの場合、ターゲットも類似することが想定され、マージしても問題が生じないことが多い。その一方で、マージを行いたくないセグメントも存在する。これらを考慮し、本実施形態では、セグメントのマージ処理を行う。 <Second Embodiment>
In the present embodiment, segments set by a store user are merged (integrated) according to the degree of similarity. When a store user generates a plurality of segments, it is possible that a similar segment is generated. In such a case, the segments can be easily managed by merging the segments. In the case of similar segments, it is assumed that the targets are also similar, and there is often no problem even if they are merged. On the other hand, there are segments that you do not want to merge. In consideration of these, in the present embodiment, segment merge processing is performed.
　まず、本実施形態において、店舗ユーザは、セグメントの登録／編集画面において、マージを許可するか否かの設定を受け付けているものとする。 First, in the present embodiment, it is assumed that the store user accepts the setting of whether to permit merging on the segment registration / edit screen.
　（セグメントのマージ処理）
　図１３は、本実施形態に係る管理サーバ１０１における、セグメントを統合する処理フローを示す。本処理フローは、管理サーバ１０１のＣＰＵがＨＤＤ等に格納されたプログラムを読み出して実行することにより実現される。本処理フローの実行のタイミングは、予め指定された日時に実行されるようにしても良いし、同一または類似の属性を有するセグメントの数が所定数を超えた場合や、ある店舗が作成したセグメント数が所定の数を超えた場合に実行するようにしても良い。 (Segment merge processing)
FIG. 13 shows a processing flow for integrating segments in the management server 101 according to this embodiment. This processing flow is realized by the CPU of the management server 101 reading and executing a program stored in the HDD or the like. The execution timing of this processing flow may be executed at a date and time designated in advance, or when the number of segments having the same or similar attributes exceeds a predetermined number, or a segment created by a certain store It may be executed when the number exceeds a predetermined number.
　Ｓ１３０１にて、管理サーバ１０１は、図４Ｃのテーブルを参照して、生成されたセグメント情報を取得する。この時、店舗ＩＤをキーにしてセグメントを検索する。 In S1301, the management server 101 refers to the table in FIG. 4C and acquires the generated segment information. At this time, the segment is searched using the store ID as a key.
　Ｓ１３０２にて、管理サーバ１０１は、取得したセグメント情報の中から、マージが禁止されているセグメントの情報を除去する。ここでのマージが禁止されているセグメントは、店舗ユーザによって設定されているものとし、具体的には、図４Ｃの「マージ可否」の設定に応じて判断される。 In S1302, the management server 101 removes information on segments for which merging is prohibited from the acquired segment information. Here, it is assumed that the segment for which merging is prohibited is set by the store user, and specifically, is determined according to the setting of “Mergeability” in FIG. 4C.
　Ｓ１３０３にて、管理サーバ１０１は、セグメント情報それぞれの属性に基づいて、セグメントと間の類似度を導出する。ここでの類似度の導出方法は特に限定するものではないが、例えば、２つのセグメント間において、一致する属性の数の２つのセグメントが有する属性の種類数に対する割合や、一致する属性の数と一致しない属性の数とを重み付け加算した値として、算出してもよい。全てのセグメントの組み合わせに対する類似度を算出した後、管理サーバ１０１は、類似度が高い組み合わせの順にソートを行う。 In S1303, the management server 101 derives the similarity between the segments based on the attributes of the segment information. The method of deriving the similarity here is not particularly limited. For example, between two segments, the ratio of the number of matching attributes to the number of types of attributes of the two segments, the number of matching attributes, It may be calculated as a value obtained by weighted addition of the number of attributes that do not match. After calculating the similarities for all segment combinations, the management server 101 sorts the combinations in descending order of similarity.
　Ｓ１３０４にて、管理サーバ１０１は、ソートしたセグメントの組み合わせのうち、最も類似度が高い組み合わせの類似度が所定の閾値以上であるか否かを判定する。ここでの所定の閾値は、予め設定され、ＨＤＤ等の記憶領域に保持されているものとする。最も類似度の高いセグメントの組み合わせの類似度が所定の閾値以上である場合（Ｓ１３０４にてＹＥＳ）はＳ１３０５へ進み、閾値より小さい場合（Ｓ１３０４にてＮＯ）は本処理フローを終了する。 In S1304, the management server 101 determines whether or not the similarity of the combination with the highest similarity among the sorted segment combinations is equal to or greater than a predetermined threshold. Here, it is assumed that the predetermined threshold is set in advance and held in a storage area such as an HDD. If the similarity of the combination of segments having the highest similarity is equal to or greater than a predetermined threshold (YES in S1304), the process proceeds to S1305, and if it is smaller than the threshold (NO in S1304), the process flow ends.
　Ｓ１３０５にて、管理サーバ１０１は、最も類似度が高いセグメント同士をマージする。ここでのマージとは、１のセグメントを新たに生成し、類似しているとされたセグメントに関連付けられた属性をその新たなセグメントに関連付けることにより行う。これにより、マージされたセグメントそれぞれに対応付けられた固有ポータルも１つに統合されることとなる。そして、類似しているとされたセグメントは削除する。なお、図４Ｃのテーブルにおいて、マージによって生成されたセグメントについては、その旨が分かるようなフラグを設けてもよい。また、マージ前のセグメント自体は削除せずに、マージ前のセグメントとしてその情報を管理してもよい。Ｓ１３０５のマージ処理が完了した後、Ｓ１３０３へ戻り、再度新たなセグメントを加えた組み合わせに対して類似度を算出する。 In S1305, the management server 101 merges the segments having the highest similarity. Here, the merging is performed by newly generating one segment and associating the attribute associated with the similar segment with the new segment. As a result, the unique portals associated with the merged segments are also integrated into one. Then, segments that are considered to be similar are deleted. In the table of FIG. 4C, a flag that indicates that the segment generated by merging may be provided. The information may be managed as a segment before merging without deleting the segment before merging. After the merge processing in S1305 is completed, the process returns to S1303, and the similarity is calculated for the combination in which a new segment is added again.
　以上、本実施形態により、類似するセグメントが増加した際に、管理サーバ側で類似のセグメントを自動的にマージすることができる。また、マージを行いたくない特定のセグメントについてもその状態を維持することができる。 As described above, according to the present embodiment, when the number of similar segments increases, the similar segments can be automatically merged on the management server side. Moreover, the state can be maintained even for a specific segment that is not desired to be merged.
　上記では、同じ店舗にて生成されたセグメントをマージする例を示したが、異なる店舗間で類似のセグメントをマージするようにしても構わない。 In the above example, segments generated at the same store are merged. However, similar segments may be merged between different stores.
　＜第三の実施形態＞
　本実施形態は、顧客ユーザへのイベントの通知方法について、第一の実施形態とは異なる例を示す。上記第一及び第二の実施形態で説明した固有ポータルには、特定の属性を有する顧客ユーザのみがアクセス可能であり、当該顧客ユーザは店舗が取り扱っている商品等に対して潜在的な需要を有している。しかし、店舗毎に見れば、全ての店舗が全ての顧客ユーザと取引実績があるわけではなく、店舗によっては未だ取引実績のない顧客ユーザが存在することも多分に想定される。そして、上記第一及び第二の実施形態ではそのような顧客ユーザと新たに取引実績を作ることを可能にする発明を説明した。その一方で、店舗によっては既に取引実績のある顧客ユーザ限定でイベント通知を行いたい場合も考えられる。そこで、本実施形態では、取引実績のある顧客ユーザを優先してイベント通知を行う方法を説明する。 <Third embodiment>
This embodiment shows an example different from the first embodiment regarding a method for notifying an event to a customer user. The unique portal described in the first and second embodiments can be accessed only by customer users having specific attributes, and the customer users have a potential demand for products and the like handled by stores. Have. However, if it sees for every store, not all stores have the transaction results with all the customer users, and it is assumed that there is a customer user with no transaction results depending on the stores. In the first and second embodiments, the invention that makes it possible to newly create a transaction record with such a customer user has been described. On the other hand, depending on the store, there may be a case where it is desired to notify an event only for a customer user who has a transaction record. Therefore, in this embodiment, a method for giving an event notification with priority given to a customer user who has a transaction record will be described.
　図１４は、本実施形態に係るイベントの通知の処理フローを示す。本処理フローは、管理サーバ１０１のＣＰＵがＨＤＤ等の記憶部に格納されたプログラムを読み出して実行することにより実現される。管理サーバ１０１側では、図３に示す顧客ユーザ管理部３０１、ＵＩ制御部３０４、顧客ユーザ認証部３０５、イベント管理部３０９、取引管理部３１０が機能することにより、本処理が行われる。図１４のＳ１４０１～Ｓ１４０３は、第一の実施形態にて述べた図１０のＳ１００１～Ｓ１００３と同様であるため、説明を省略する。 FIG. 14 shows a processing flow of event notification according to the present embodiment. This processing flow is realized by the CPU of the management server 101 reading and executing a program stored in a storage unit such as an HDD. On the management server 101 side, the customer user management unit 301, UI control unit 304, customer user authentication unit 305, event management unit 309, and transaction management unit 310 shown in FIG. Since S1401 to S1403 in FIG. 14 are the same as S1001 to S1003 in FIG. 10 described in the first embodiment, description thereof will be omitted.
　Ｓ１４０３の後、Ｓ１４０４にて、管理サーバ１０１は、各種テーブルを参照し、ログインしている顧客ユーザが過去に購入手続きを行った店舗により登録されたイベントがあるか否かを判定する。具体的には、取引管理部３１０によって管理されている図４Ｅ、図４Ｆに示すテーブルが用いられる。購入履歴のある店舗により登録されたイベントがない場合（Ｓ１４０４にてＮＯ）Ｓ１４０６に進み、ある場合は（Ｓ１４０４にてＹＥＳ）Ｓ１４０５へ進む。 After S1403, in S1404, the management server 101 refers to the various tables and determines whether there is an event registered by the store where the logged-in customer user has made a purchase procedure in the past. Specifically, the tables shown in FIGS. 4E and 4F managed by the transaction management unit 310 are used. If there is no event registered by a store with a purchase history (NO in S1404), the process proceeds to S1406, and if there is (YES in S1404), the process proceeds to S1405.
　Ｓ１４０５にて、管理サーバ１０１は、Ｓ１４０３にてアクセス許可された固有ポータルに顧客ユーザからアクセスされた際に、図４Ｅ、図４Ｆのテーブルに基づいて、該当するセグメントおよび店舗に対応するイベントを表示するように制御する。その後、本処理フローを終了する。 In S1405, the management server 101 displays an event corresponding to the corresponding segment and store based on the tables in FIGS. 4E and 4F when the customer user accesses the unique portal permitted to be accessed in S1403. Control to do. Thereafter, this processing flow ends.
　以上、本実施形態により、顧客ユーザの過去の購入履歴に応じてイベントを通知するか否かを制御することができる。 As described above, according to the present embodiment, it is possible to control whether or not to notify an event according to the past purchase history of the customer user.
　上記では、顧客ユーザごとに購入実績のある店舗のイベント通知のみが表示される場合を説明したが、発明の実施形態はこの通知方法に限定されない。例えば、図１１Ｆの店舗側がイベント登録をする際に、イベント通知をする対象を固有ポータルに参加する顧客ユーザ全員とするか、或いは、取引実績のある顧客ユーザのみに限定するかを設定可能とすることができる。これにより、固有ポータルにおいて通知されるイベントには、固有ポータルの参加者全員を通知対象者とするイベント（通常イベント）と、通知対象者を店舗と取引実績のある顧客ユーザに限定するイベント（限定イベント）との２種類が含まれることとなる。この場合、ある店舗Ａの通知する限定イベントについて、店舗Ａと取引実績のある顧客ユーザＡが固有ポータルにアクセスした際には表示されるが、店舗Ａと取引実績のない顧客ユーザＢが固有ポータルにアクセスしても表示されないこととなる。その一方、店舗Ａが通知する一般イベントは、顧客ユーザＡと顧客ユーザＢとのいずれが固有ポータルを訪問しても、そのたびに表示される。そして、顧客ユーザＡが固有ポータルを訪問した場合には、限定イベントと一般イベントとの両方が表示されることになり、その場合には限定イベントを一般イベントと識別可能に表示するようにしてもよい。例えば、限定イベントの通知を一群として限定イベントであることを示す表示（枠で囲む、或いは、限定イベントの旨を示す見出しを付与する等）を付与しても良い。あるいは、限定イベントの通知を一般イベントの通知よりも表示順序で優先するようにしてもよい。 In the above description, a case has been described in which only event notifications of stores with purchase results are displayed for each customer user, but embodiments of the invention are not limited to this notification method. For example, when the store side in FIG. 11F registers an event, it is possible to set whether the target of event notification is all the customer users who participate in the specific portal or only the customer users who have a transaction record. be able to. As a result, the events that are notified in the unique portal include the event that all participants of the unique portal are subject to notification (ordinary event) and the event that restricts the subject of notification to customer users who have transactions with stores (limited) Event) is included. In this case, the limited event notified by a certain store A is displayed when the store A and the customer user A who has a transaction record access the unique portal, but the store user A and the customer user B who has no transaction record have the unique portal. It will not be displayed even if accessed. On the other hand, the general event notified by the store A is displayed whenever any of the customer user A and the customer user B visits the unique portal. When the customer user A visits the unique portal, both the limited event and the general event are displayed. In this case, the limited event is displayed so as to be distinguishable from the general event. Good. For example, a limited event notification may be given as a group to indicate that the event is a limited event (e.g., enclosed in a frame, or provided with a headline indicating the limited event). Alternatively, the notification of the limited event may be prioritized in the display order over the notification of the general event.
　また、限定イベントは、図１１Ｆで設定される通知期間のうち、一部の期間のみとし、残りの期間は一般イベントに切り替えてもよい。例えば、通知期間を１週間とした場合、最初の２日間は限定イベントとして取引実績のある顧客ユーザのみを対象にイベント通知を行い、残りの５日間は一般イベントに切り替えて固有ポータルにアクセス可能な全顧客ユーザを通知対象とすることができる。 Also, the limited event may be only a part of the notification period set in FIG. 11F, and the remaining period may be switched to a general event. For example, if the notification period is 1 week, event notification is given only to customer users who have a track record of trading as a limited event for the first 2 days, and the remaining 5 days can be switched to a general event to access a unique portal. All customer users can be notified.
　以上のように、本実施形態によれば、店舗の固有ポータル内でのイベント通知を、当該店舗との取引実績の有無に応じて制御することが可能となり、顧客ユーザに対してイベント通知をより効果的に実施することができる。 As described above, according to the present embodiment, it is possible to control the event notification in the store's unique portal according to the presence or absence of transactions with the store, and more event notification to the customer user. Can be implemented effectively.
　＜その他の実施形態＞
　なお、上述した固有ポータルにおいて、セグメントに特化した機能を備えてもよい。例えば、固有ポータル上において、その固有ポータルに対応するセグメントに対して登録されたイベントや店舗のみを検索できる機能を備えてもよい。また、固有ポータル上でのみ利用可能なイベントが登録されてもよい。また、顧客ユーザが、セグメントに関連付けられた属性を有する商品から店舗を検索できるような構成であってもよい。 <Other embodiments>
Note that the above-described unique portal may have a segment-specific function. For example, on a unique portal, a function may be provided that can search only for events and stores registered for a segment corresponding to the unique portal. In addition, an event that can be used only on the unique portal may be registered. Moreover, the structure which a customer user can search a store from the goods which have the attribute linked | related with the segment may be sufficient.
　また、顧客ユーザ側から所定の属性を有する店舗側に対し、固有ポータルを介してイベントの登録を要求するような構成であってもよい。更には、顧客ユーザ側から所定の属性を有するセグメントの登録が可能な構成であってもよい。 Further, it may be configured such that the customer user side requests the store side having a predetermined attribute to register an event via a unique portal. Furthermore, the structure which can register the segment which has a predetermined attribute from the customer user side may be sufficient.
　本発明は上記実施の形態に制限されるものではなく、本発明の精神及び範囲から離脱することなく、様々な変更及び変形が可能である。従って、本発明の範囲を公にするために、以下の請求項を添付する。また本発明に係る情報処理装置は、１以上のコンピュータを該情報処理装置として機能させるプログラムによっても実現可能である。該プログラムは、コンピュータが読み取り可能な記録媒体に記録されることにより、あるいは電気通信回線を通じて、提供／配布することができる。 The present invention is not limited to the above embodiment, and various changes and modifications can be made without departing from the spirit and scope of the present invention. Therefore, in order to make the scope of the present invention public, the following claims are attached. The information processing apparatus according to the present invention can also be realized by a program that causes one or more computers to function as the information processing apparatus. The program can be provided / distributed by being recorded on a computer-readable recording medium or through a telecommunication line.

Claims (17)

  1. 　複数の仮想店舗へのアクセスを提供するオンラインショッピングの第１のポータルサイトと、前記複数の仮想店舗のうち特定の属性を有する一部の仮想店舗へのアクセスを提供し、かつ、該特定の属性を有する第２のポータルサイトとを管理する管理サーバであって、
    　前記複数の仮想店舗が有する属性の情報を含む店舗情報と、前記第２のポータルサイトが有する前記特定の属性の情報を含むサイト情報とを管理する管理手段と、
    　前記複数の仮想店舗のうちのいずれかの仮想店舗から、前記第２のポータルサイトにおける該仮想店舗へのアクセス提供を求めるアクセス提供申請を受け付ける第１の受付手段と、
    　前記第１の受付手段が前記アクセス提供申請を受け付けた場合に、前記管理手段が管理する前記店舗情報と前記サイト情報とに基づき、前記アクセス提供申請を行った仮想店舗が前記特定の属性を有するか否かを判定する判定手段と
    を備え、
    　前記判定手段が前記アクセス提供申請を行った仮想店舗が前記特定の属性を有すると判定した場合、前記管理手段は前記アクセス提供申請を行った仮想店舗の店舗情報を、前記第２のポータルサイトが該仮想店舗へのアクセスを提供することを示すように更新することを特徴とする管理サーバ。     A first portal site for online shopping providing access to a plurality of virtual stores, and providing access to some virtual stores having specific attributes among the plurality of virtual stores, and the specific attributes A management server for managing a second portal site having
    Management means for managing store information including attribute information of the plurality of virtual stores and site information including information of the specific attribute of the second portal site;
    A first accepting unit that accepts an access provision application for requesting access to the virtual store in the second portal site from any one of the plurality of virtual stores;
    When the first accepting unit accepts the access provision application, the virtual store that has made the access provision application has the specific attribute based on the store information and the site information managed by the managing unit. Determination means for determining whether or not,
    When the determination unit determines that the virtual store that has applied for the access provision has the specific attribute, the management unit stores the store information of the virtual store that has applied for the access provision, and the second portal site A management server that is updated to indicate that it provides access to the virtual store.
  2. 　前記店舗情報には、前記仮想店舗が扱う商品の属性の情報が含まれ、
    　前記判定手段は、前記アクセス提供申請を行った仮想店舗が扱う前記商品の属性が前記特定の属性を有するか否かに基づき、前記アクセス提供申請を行った仮想店舗が前記特定の属性を有するか否かを判定することを特徴とする請求項１に記載の管理サーバ。     The store information includes product attribute information handled by the virtual store,
    The determination means determines whether the virtual store that has applied for the access provision has the specific attribute based on whether the attribute of the product handled by the virtual store that has applied for the access provision has the specific attribute. The management server according to claim 1, wherein it is determined whether or not.
  3. 　前記店舗情報には、前記仮想店舗が扱う商品の属性の情報が含まれ、
    　前記第１の受付手段は、前記アクセス提供申請を、該申請を行う仮想店舗が扱う商品ごとに受け付け、
    　前記判定手段は、前記アクセス提供申請を受け付けた前記商品の属性が前記特定の属性を有するか否かに基づき、前記アクセス提供申請を行った仮想店舗が前記特定の属性を有するか否かを判定し、
    　前記判定手段が前記アクセス提供申請を行った仮想店舗が前記特定の属性を有すると判定した場合、前記管理手段は前記アクセス提供申請を行った仮想店舗の店舗情報を、前記第２のポータルサイトが該仮想店舗における前記申請された商品へのアクセスを提供することを示すように更新することを特徴とする請求項１に記載の管理サーバ。     The store information includes product attribute information handled by the virtual store,
    The first accepting means accepts the access provision application for each product handled by the virtual store performing the application,
    The determination means determines whether the virtual store that has made the access provision application has the specific attribute based on whether the attribute of the product that has received the access provision application has the specific attribute. And
    When the determination unit determines that the virtual store that has applied for the access provision has the specific attribute, the management unit stores the store information of the virtual store that has applied for the access provision, and the second portal site The management server of claim 1, wherein the management server is updated to indicate that it provides access to the requested product in the virtual store.
  4. 　前記管理手段は、前記第１のポータルサイト及び前記第２のポータルサイトを介して仮想店舗にアクセス可能な顧客ユーザの、該顧客ユーザが有する属性の情報を含むユーザ情報を更に管理し、
    　前記第１のポータルサイトを介して仮想店舗にアクセス可能な顧客ユーザのうち、前記特定の属性を有する顧客ユーザのみが前記第２のポータルサイトを介して仮想店舗にアクセス可能である事を特徴とする請求項１乃至３のいずれか１項に記載の管理サーバ。     The management means further manages user information including information on attributes of the customer user who can access the virtual store via the first portal site and the second portal site,
    Of the customer users who can access the virtual store via the first portal site, only the customer user having the specific attribute can access the virtual store via the second portal site. The management server according to any one of claims 1 to 3.
  5. 　前記第１のポータルサイトを介して仮想店舗にアクセス可能な前記顧客ユーザから、前記第２のポータルサイトを介した仮想店舗へのアクセスの許可を求めるアクセス許可申請を受け付ける第２の受付手段を更に備え、
    　前記第２の受付手段が前記アクセス許可申請を受け付けた場合に、前記判定手段は前記管理手段が管理する前記ユーザ情報に基づき前記アクセス許可申請を行った顧客ユーザが前記特定の属性を有するか否かを判定し、
    　前記判定手段が前記アクセス許可申請を行った顧客ユーザが前記特定の属性を有すると判定した場合、前記管理手段は前記アクセス許可申請を行った顧客ユーザのユーザ情報を、該顧客ユーザが前記第２のポータルサイトを介して仮想店舗へのアクセス可能であることを示すように更新することを特徴とする請求項４に記載の管理サーバ。     Second receiving means for receiving an access permission application for requesting permission to access the virtual store via the second portal site from the customer user who can access the virtual store via the first portal site; Prepared,
    When the second accepting unit accepts the access permission application, the determination unit determines whether the customer user who made the access permission application based on the user information managed by the managing unit has the specific attribute. Determine whether
    When the determination means determines that the customer user who has made the access permission application has the specific attribute, the management means has user information of the customer user who has made the access permission application, The management server according to claim 4, wherein the management server is updated so as to indicate that the virtual store can be accessed via the portal site.
  6. 　前記管理手段は、前記仮想店舗の取引履歴の情報を更に管理し、
    　前記判定手段は、前記アクセス提供申請を行った仮想店舗が、前記第２のポータルサイトを介して仮想店舗にアクセスが可能な顧客ユーザとの取引実績を有するか否かを前記取引履歴の情報に基づき更に判定し、
    　前記判定手段は前記アクセス提供申請を行った仮想店舗が前記特定の属性を有し、かつ、前記取引実績を有すると判定した場合、前記管理手段は前記アクセス提供申請を行った仮想店舗の店舗情報を、前記第２のポータルサイトが該仮想店舗へのアクセスを提供することを示すように更新することを特徴とする請求項４または５に記載の管理サーバ。     The management means further manages transaction history information of the virtual store,
    In the transaction history information, the determination means determines whether the virtual store that has applied for the access provision has a transaction record with a customer user who can access the virtual store via the second portal site. Further judgment based on
    When the determination unit determines that the virtual store that has made the access provision application has the specific attribute and has the transaction record, the management unit stores store information of the virtual store that has made the access provision application The management server according to claim 4 or 5, wherein the management server is updated to indicate that the second portal site provides access to the virtual store.
  7. 　前記判定手段は前記取引実績を有するか否かの判定において、前記第２のポータルサイトを介して仮想店舗にアクセスが可能な顧客ユーザの数に応じた所定数以上の取引実績を有するか否かを判定することを特徴とする請求項６に記載の管理サーバ。 Whether the determination means has a transaction record of a predetermined number or more according to the number of customer users who can access the virtual store via the second portal site in determining whether or not the transaction record has been obtained. The management server according to claim 6, wherein the management server is determined.
  8. 　第２のポータルサイトがアクセスを提供する前記仮想店舗から、前記第２のポータルサイト内で該第２のポータルサイトを介して仮想店舗にアクセス可能な顧客ユーザ向けのイベントの申請を更に受け付ける第３の受付手段を更に備えることを特徴とする請求項４乃至７のいずれか１項に記載の管理サーバ。 A third accepting application for an event for a customer user who can access the virtual store via the second portal site in the second portal site from the virtual store to which the second portal site provides access; The management server according to claim 4, further comprising: a receiving unit.
  9. 　前記イベントは、該イベントの申請を行った仮想店舗と取引実績のある顧客ユーザであって、前記第２のポータルサイトを介して仮想店舗にアクセス可能な顧客ユーザのみを対象とすることを特徴とする請求項８に記載の管理サーバ。 The event is intended only for a customer user who has a transaction record with a virtual store that has applied for the event and can access the virtual store via the second portal site. The management server according to claim 8.
  10. 　前記イベントには、該イベントを前記第２のポータルサイト内で実施する期間が設定され、
    　前記イベントは、前記期間のうちの一部の期間は、該イベントの申請を行った仮想店舗と取引実績のある顧客ユーザであって、前記第２のポータルサイトを介して仮想店舗にアクセス可能な顧客ユーザのみを対象とし、前記期間のうちの残りの期間は前記第２のポータルサイトを介して仮想店舗にアクセス可能な顧客ユーザ全てを対象とすることを特徴とする請求項８に記載の管理サーバ。     In the event, a period during which the event is carried out in the second portal site is set,
    The event is a customer user who has a transaction record with the virtual store that applied for the event during a part of the period, and can access the virtual store via the second portal site. 9. The management according to claim 8, wherein only the customer users are targeted, and the remaining period of the period is targeted to all customer users who can access the virtual store via the second portal site. server.
  11. 　複数の仮想店舗のうちのいずれかの仮想店舗から新たな第２のポータルサイトの設定要求を更に受け付ける第４の受付手段と、
    　前記設定要求を受け付けた場合に、前記新たな第２のポータルサイトが有すべき属性と関連する属性を有し、かつ、前記第１のポータルサイトを介して仮想店舗にアクセス可能な顧客ユーザの情報を前記仮想店舗に提供する提供手段とを
    更に備えることを特徴とする請求項４乃至１０のいずれか１項に記載の管理サーバ。     A fourth receiving means for further receiving a setting request for a new second portal site from any one of the plurality of virtual stores;
    When the setting request is received, the customer user who has an attribute related to the attribute that the new second portal site should have and has access to the virtual store via the first portal site The management server according to any one of claims 4 to 10, further comprising providing means for providing information to the virtual store.
  12. 　前記提供手段は、前記顧客ユーザの情報を、顧客ユーザの属性毎のユーザ数の情報として提供する請求項１１に記載の管理サーバ。 The management server according to claim 11, wherein the providing means provides the customer user information as information on the number of users for each attribute of the customer user.
  13. 　前記顧客ユーザの属性には、年齢、年代、性別、出身地、所在地、自宅住所、勤務住所、職業及び興味対象のうちの少なくともいずれかが含まれることを特徴とする請求項１２に記載の管理サーバ。 13. The management according to claim 12, wherein the attribute of the customer user includes at least one of age, age, gender, birthplace, location, home address, work address, occupation, and object of interest. server.
  14. 　前記受付手段は、前記設定要求を行う仮想店舗が有する属性と関連する属性を有する第２のポータルサイトの設定要求のみを受け付けることを更に特徴とする請求項１１乃至１３のいずれか１項に記載の管理サーバ。 The said reception means receives only the setting request | requirement of the 2nd portal site which has an attribute relevant to the attribute which the virtual store which performs the said setting request | requirement has further, The one of Claim 11 thru | or 13 characterized by the above-mentioned. Management server.
  15. 　前記特定の属性が共通する複数の前記第２のポータルサイトが存在する場合に、該複数の第２のポータルサイトを統合するか否かを判定する統合判定手段を更に備えることを特徴とする請求項１乃至１４のいずれか１項に記載の管理サーバ。 The system further comprises an integration determination unit that determines whether or not to integrate the plurality of second portal sites when there are a plurality of the second portal sites having the same specific attribute. Item 15. The management server according to any one of Items 1 to 14.
  16. 　複数の仮想店舗へのアクセスを提供するオンラインショッピングの第１のポータルサイトと、前記複数の仮想店舗のうち特定の属性を有する一部の仮想店舗へのアクセスを提供し、かつ、該特定の属性を有する第２のポータルサイトとを管理する管理サーバの制御方法であって、
    　前記複数の仮想店舗のうちのいずれかの仮想店舗から、前記第２のポータルサイトにおける該仮想店舗へのアクセス提供を求めるアクセス提供申請を受け付ける受付工程と、
    　前記第１の受付手段が前記アクセス提供申請を受け付けた場合に、前記仮想店舗が有する属性の情報を含む店舗情報と、前記第２のポータルサイトが有する前記特定の属性の情報を含むサイト情報とに基づき、前記アクセス提供申請を行った仮想店舗が前記特定の属性を有するか否かを判定する判定工程と
    　前記判定工程において前記アクセス提供申請を行った仮想店舗が前記特定の属性を有すると判定された場合、前記アクセス提供申請を行った仮想店舗の店舗情報を、前記第２のポータルサイトが該仮想店舗へのアクセスを提供することを示すように更新する更新工程と
    を有することを特徴とする管理サーバの制御方法。     A first portal site for online shopping providing access to a plurality of virtual stores, and providing access to some virtual stores having specific attributes among the plurality of virtual stores, and the specific attributes A management server for managing a second portal site having
    An accepting step of accepting an access provision application for requesting access to the virtual store in the second portal site from any one of the plurality of virtual stores;
    When the first accepting unit accepts the access provision application, store information including attribute information of the virtual store, site information including information of the specific attribute of the second portal site, and And determining whether or not the virtual store that has made the access provision application has the specific attribute, and determining that the virtual store that has made the access provision application in the determination step has the specific attribute An update step of updating the store information of the virtual store that has applied for the access provision so as to indicate that the second portal site provides access to the virtual store. Management server control method.
  17. 　コンピュータを、請求項１乃至１５のいずれか１項に記載の管理サーバの各手段として機能させるコンピュータプログラム。 A computer program that causes a computer to function as each unit of the management server according to any one of claims 1 to 15.
PCT/JP2015/001786 2015-03-27 2015-03-27 Management server for managing online shopping portal sites, control method therefor, and computer program WO2016157240A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2015532231A JP5848496B1 (en) 2015-03-27 2015-03-27 Management server for managing online shopping portal site, control method therefor, and computer program
PCT/JP2015/001786 WO2016157240A1 (en) 2015-03-27 2015-03-27 Management server for managing online shopping portal sites, control method therefor, and computer program
TW105109734A TWI596557B (en) 2015-03-27 2016-03-28 Management server for managing online shopping portal and control method thereof, and computer program

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/001786 WO2016157240A1 (en) 2015-03-27 2015-03-27 Management server for managing online shopping portal sites, control method therefor, and computer program

Publications (1)

Publication Number Publication Date
WO2016157240A1 true WO2016157240A1 (en) 2016-10-06

Family

ID=55176146

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/001786 WO2016157240A1 (en) 2015-03-27 2015-03-27 Management server for managing online shopping portal sites, control method therefor, and computer program

Country Status (3)

Country Link
JP (1) JP5848496B1 (en)
TW (1) TWI596557B (en)
WO (1) WO2016157240A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001184405A (en) * 1999-12-24 2001-07-06 Sumitomo Corp Virtual shopping mall system, data processing device for sale promotion, virtual shopping mall operating method, data processing method for sale promotion, and recording medium
JP2002007749A (en) * 2000-06-27 2002-01-11 Hitachi Ltd Server-allocating device, and system and method for providing service
JP2002342663A (en) * 2001-05-14 2002-11-29 Initia Consulting Inc Information sharing system
JP2007102522A (en) * 2005-10-05 2007-04-19 Cns:Kk E-commerce system, method, and program

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5430442B2 (en) * 2010-02-25 2014-02-26 楽天株式会社 Electronic commerce system, electronic commerce method, and electronic commerce program

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001184405A (en) * 1999-12-24 2001-07-06 Sumitomo Corp Virtual shopping mall system, data processing device for sale promotion, virtual shopping mall operating method, data processing method for sale promotion, and recording medium
JP2002007749A (en) * 2000-06-27 2002-01-11 Hitachi Ltd Server-allocating device, and system and method for providing service
JP2002342663A (en) * 2001-05-14 2002-11-29 Initia Consulting Inc Information sharing system
JP2007102522A (en) * 2005-10-05 2007-04-19 Cns:Kk E-commerce system, method, and program

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MY TOWN SAITAMA: "Saitama Shoko Kaigisho", 7 July 2011 (2011-07-07), Retrieved from the Internet <URL:https://web.archive.org/web/20110707122200/http://www.amatias.com> [retrieved on 20150527] *

Also Published As

Publication number Publication date
JPWO2016157240A1 (en) 2017-04-27
JP5848496B1 (en) 2016-01-27
TW201643792A (en) 2016-12-16
TWI596557B (en) 2017-08-21

Similar Documents

Publication Publication Date Title
US12014390B2 (en) Systems and methods for shopping in an electronic commerce environment
KR101761226B1 (en) Selective sharing of user information based on contextual relationship information, such as to crowd-source gifts of interest to a recipient
US20190035008A1 (en) Internet vending machine/mobile vending machine system and method
US20120197753A1 (en) Systems and methods for shopping in an electronic commerce environment
CN107430618A (en) Realize the system and method interacted with host computer device progress user speech
WO2012103462A2 (en) Systems and methods for shopping in an electronic commerce environment
JP6580189B1 (en) Display control apparatus, display control method, and display control program
JP5848496B1 (en) Management server for managing online shopping portal site, control method therefor, and computer program
KR102218238B1 (en) method and apparatus for recommending advertisements using information obtained through Social Network Service
KR20080008677A (en) Open type internet shoppingmall system and method for operating the same
JP2021022403A (en) Information selection device, information selection method, and information selection program
JP6325710B1 (en) Information processing apparatus, information processing program, and information processing method
KR100714423B1 (en) Multi-stage membership Promotion method using a mobile phone
JP7428857B2 (en) Information processing device, information processing method, and information processing program
JP7400046B1 (en) Information processing device, information processing method and program
KR20200097184A (en) Fashion web-collection social network service system based on internet shopping mall service
JP7504275B2 (en) Information processing device, information processing method, and information processing program
JP2019046115A (en) Method and program for providing information on product
JP2019079123A (en) Information processing device, information processing method and information processing program
JP2019079130A (en) Server apparatus, generation method and generation program
KR100843943B1 (en) System and Method for distributing music contents
JP6483734B2 (en) Generating device, generating method, and generating program
KR101934907B1 (en) Server, device and method for post providing for micro blog
JP2016173804A (en) Information processing device, control method and program
JP6599126B2 (en) Segment management system and program

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2015532231

Country of ref document: JP

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15887398

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15887398

Country of ref document: EP

Kind code of ref document: A1