TWI596557B - Management server for managing online shopping portal and control method thereof, and computer program - Google Patents

Description

Management server for managing online shopping portal, control method thereof, and computer program

The invention of the present invention relates to a management server for managing an online shopping portal, a control method thereof, and a computer program.

In recent years, online shopping using the Internet has become widespread, and users are able to use services such as purchases of products sold in stores that are opened online. There are various forms of online shopping, and there is also a portal-type infrastructure system that provides access to a number of stores that open stores. In the mall-type infrastructure system, since the store side is provided with the infrastructure involved in opening the store, the store side does not need to set up an independent system, and can easily open the store online.

In such an infrastructure system, a variety of added value is provided to the user for the promotion of the entire mall or the securing of the potential customer. For example, it is possible to issue coupons or points that can be used in a predetermined store that is available online. Patent Document 1 discloses a method of presenting a promotion based on a user's action history.

[Previous Technical Literature] [Patent Literature]

[Patent Document 1] Japanese Patent Laid-Open Publication No. 2010-277360

In the online shopping in such an infrastructure system, since there are a large number of shops or products in the store, there is a problem that it is difficult to find a product that is required by the store or a store that displays such a product.

In order to solve the problem, it is necessary to provide and manage an entry site that is easy to find a product necessary for the user or a store that displays the product, but the specific means and method for setting up the portal site have not been proposed.

In order to solve the above problem, the invention of the present invention has the following constitution. That is, the management is: the first portal website for online shopping that provides access to the virtual store before the reciprocal; and the access to the virtual store that provides a part of the specific attribute among the pre-recorded virtual stores, and has the specific The management server of the second portal of the attribute is characterized by: management means: management information including the information of the attribute of the pre-recorded virtual store, and the pre-recording of the second entry website. The website information of the information of the attribute; and the first means of acceptance is the application for receiving access, which is used to request the virtual store from the previous record In any of the virtual stores, the access to the virtual store in the second portal is provided; and the judging means is based on the pre-recording management means when the first receiving means accepts the application for the pre-recording access. The pre-recorded shop information and the pre-posted website information are used to determine whether the virtual shop that has made the pre-record access request has the attribute specified in the pre-recording; the pre-determination means determines that the virtual shop that has made the pre-record access request has the pre-recording specific In the case of the attribute, the pre-recording management means updates the store information of the virtual shop in which the application is provided by the pre-recording, and updates to the pre-recorded second portal site to provide access to the virtual store.

According to the present invention, by providing and managing a management server that easily finds the products necessary for the user or the portal of the store displaying the goods, the specific means and method for setting up the portal can be provided.

Other features and advantages of the invention will be apparent from the description and appended claims. In addition, in the appended drawings, the same or the same components are denoted by the same reference numerals.

101‧‧‧Management Server

102‧‧‧Store PC

103‧‧‧Customer PC

104‧‧‧Internet

200‧‧‧Information processing device

201‧‧‧CPU

202‧‧‧RAM

203‧‧‧ROM

204‧‧‧HDD

205‧‧‧Show IF

206‧‧‧ display

207‧‧‧Enter IF

208‧‧‧ Input Department

209‧‧‧NW IF

210‧‧‧ Busbar

301‧‧‧Customer User Management Department

302‧‧‧Store Management Department

303‧‧‧ Departmental Management Department

304‧‧‧UI Control Department

305‧‧‧Customer User Certification Department

306‧‧‧Shop Certification Department

307‧‧‧Search Department

308‧‧‧Commodity Management Department

309‧‧‧Event Management Department

310‧‧‧Transaction Management Department

The accompanying drawings are included in the specification and are in a

Fig. 1 is a view showing an example of the configuration of the entire system of the present invention.

Fig. 2 is a view showing an example of a hardware configuration of an information processing apparatus according to the present invention.

FIG. 3 is a diagram showing an example of a software configuration of a management server according to the present invention.

4A is a diagram showing an example of a configuration of a management table of customer user information according to the present invention.

4B is a diagram showing an example of the configuration of a management table of shop information described in the present invention.

[Fig. 4C] A diagram showing an example of the configuration of the section information management table described in the present invention.

4D is a diagram showing an example of the configuration of a management table of product information described in the present invention.

4E is a diagram showing an example of a configuration of a management table of activity information described in the present invention.

[Fig. 4F] A diagram showing an example of the configuration of a management table for buying and selling transaction information described in the present invention.

Fig. 5 is a flow chart showing a shop registration process according to the present invention.

Fig. 6 is a flow chart showing the customer user registration process described in the present invention.

FIG. 7 is a flowchart of the unique entry participation process described in the embodiment.

FIG. 8 is a flowchart of the section registration process described in the present invention.

[Fig. 9] A flow chart of the activity registration processing described in the present invention.

FIG. 10 is a flowchart of the event notification processing described in the first embodiment.

FIG. 11A is a diagram showing an example of the configuration of an initial UI screen according to the present invention.

FIG. 11B is a diagram showing an example of the configuration of a UI screen for shop registration described in the present invention.

FIG. 11C is a diagram showing an example of a configuration of a UI screen for customer user registration according to the present invention.

[Fig. 11D] Fig. 11D is a diagram showing an example of a configuration of a UI screen for participation in an intrinsic entry as described in the present invention.

11E is a diagram showing an example of a configuration of a UI screen for section registration described in the present invention.

FIG. 11F is a diagram showing an example of a configuration of a UI screen for event registration described in the present invention.

11G is a diagram showing an example of a configuration of a UI screen for displaying an activity according to the present invention.

Fig. 12 is an explanatory diagram of a section described in the present invention.

Fig. 13 is a flow chart showing the merging process of the segments described in the second embodiment.

Fig. 14 is a flowchart of the event notification processing described in the third embodiment.

Hereinafter, embodiments of the present invention will be described using the drawings. In addition, the embodiment shown below is an example, and is not limited to this. Therefore, as long as the features of the invention of the present invention can be applied, For other components.

<First Embodiment> [Description of the section]

First, the "section" discussed in the invention of the present invention will be described. In this specification, a user who uses the online shopping service is described as a "customer user." In addition, the user (owner) who provides the online shopping service to the customer user in the virtual store on the infrastructure service registration line provided by the management server described in the present invention is described as the "store user". In addition, the virtual store opened online on the mall-type infrastructure service provided by the management server is simply referred to as "store".

In the mall-type infrastructure service, each store is in principle displayed as accessible to all customer users in the portal, and the customer user is free to access the website of the store. Such an entrance website that is open to all customer users is referred to as "general entrance" in this specification. However, shops that provide online shopping services sometimes consider the nature of the goods or services they display (hereinafter referred to as "goods, etc."), and want to promote sales promotion only for the specified customer (target). Notification of events or advertisements, etc. For example, a consumer product (baby article) such as a diaper or a milk powder is a product that is hardly emphasized for a customer who is not caring for a child, and a shop user wants to be selective for a customer who is currently in childcare (filtering) The notice is given. On the other hand, on the customer's side, although there is freedom to access most of the shops in the general entrance, on the contrary, it must be from a large number of shops. It is only necessary to select a store that displays products of interest to you, and there is a burden of such a store selection. Under such circumstances, the customer user often needs to obtain a notification sent by a store that has not been used so far.

Even on the store user side, it is hoped that new customers, such as customer users who have not had a transaction performance so far, have potential needs. Further, the customer user may generate interest because of a promotion from the store or the like even for a product that has not been particularly interesting so far. The promotion activities provided by the store here include the issuance of coupons that can be used when the products are purchased, or free shipping.

In the embodiment of the invention, attributes are assigned to customers, stores, and products displayed in the store. The attribute is information about a customer user or a store, and any information can be classified as long as it can classify a customer user or a store. For example, if it is a customer, it may include age (age), gender, birthplace, location (home address, company address), occupation, and interest, and may include the tariff on the infrastructure service provided by the management server. Program or restrictions, membership categories, etc. In addition, the store may include information such as the location of the store, the classification of the products displayed in the store (books, clothing, food), or the classification of the store (bookstore, clothing store, food store, etc.). In the present embodiment, an example of an attribute given to a shop or a customer user is shown in FIG. Regarding the attributes, in addition to being prepared in advance by the provisioning infrastructure service side, the shop user or the customer user can also be newly defined. For example, with the creation of new goods or services, you may consider Names, etc. are defined as new attributes.

In the present specification, a set in which 1 or a plurality of attributes are established as described above is referred to as a "segment". Then, a customer user or shop having an attribute associated with the section is deemed to be affiliated with the section. Further, in the present specification, it is assumed that each of the segment systems is associated with each other, and in the present embodiment, it is referred to as an "inheritance portal" portal. An example of the intrinsic entry is, for example, a student-specific portal for students aged 19 to 24, or an entry site for families that are being nursed.

Although the details will be described later, the general entry of the above is not limited to the attributes of the store or the customer, and there is no restriction on access from the customer. On the other hand, in the case of the unique entry, access control is performed so that the customer who has the attribute associated with the corresponding section cannot access it. Further, the store that can participate in the intrinsic entrance is also limited to have a property associated with the establishment of the section, or a store that displays the product having the attribute associated with the section. The term "participation" as used herein means that a store can be accessed from a customer by means of an inherent entrance, or an advertisement or promotion can be displayed. At this time, the shop that has participated in the unique entrance can set the registration activity for the zone, and can display the details of the activity on the unique entrance to which the zone is established.

Hereinafter, details of the system of the intrinsic entrance corresponding to the present embodiment and the service provided by the system will be provided.

〔System Components〕

Fig. 1 is a view showing an example of the overall configuration of the system according to the embodiment. In the system, the management server 101, the shop PC 102, and the customer PC 103 are connected via the Internet 104. The management server 101 is an information processing device that provides the infrastructure of the online shopping service to the shop user and the customer user through the shop PC 102 and the customer PC 103. For the infrastructure, shop users who provide goods and the like can provide online shopping services by logging into online stores. In addition, in principle, each store is first registered to the general entrance and can be accessed by all customer users.

The shop PC 102 is an information processing device used by shop users. Further, the customer PC 103 is an information processing device operated by a customer user who uses the online shopping service. Further, the shop PC 102 and the customer PC 103 may be desktop PCs or mobile terminals such as smart phones or tablets. Each user accesses the general portal provided by the management server 101 via a web browser (not shown) provided in the store PC 102 or the client PC 103. In addition, the connection from each PC to the Internet 104 is either wired or wireless. In addition, in FIG. 1, each machine system is shown in one figure, but you may connect a plurality of apparatuses.

[hard body composition]

Fig. 2 is a diagram showing an example of the hardware configuration of each information processing device included in the system according to the embodiment. In the following description, a general information processing device will be described as an example, but other configurations may be employed.

The information processing device 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 connected to be communicable through the bus bar 210. The CPU 201 performs processing control of the entire information processing device 200, and reads and executes various programs held in the ROM 203 and the like to the RAM 202 to perform various processes. The RAM 202 is a volatile memory field and is used as a working memory for execution of various programs. The ROM 203 is a non-volatile memory area, and stores various programs and the like used in processing. HDD204 is a non-volatile memory field that preserves the processing results and the like. The HDD 204 may be a non-volatile large-capacity memory field, and may be composed of a semiconductor memory such as a flash memory in addition to a 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, and displays a processing result or displays various user interface screens (UI screens) to be described later. Further, the display unit 206 may be configured to be externally connected to the information processing device 200, and in this case, connected to the information processing device 200 via the display IF 205. The input IF 207 is connected to the input unit 208, and accepts an instruction from the input unit 208 based on the user operation. The input unit 208 is, for example, a keyboard or a mouse (not shown), and is used when the user performs an input operation. Further, a touch panel in which the display unit 206 and the input unit 208 are integrated may be employed. The NW IF209 is connected to an external network such as the Internet 104. The connection form here is no matter Line/wireless and anything.

[soft body composition]

Fig. 3 is a view showing an example of the configuration of the software of the management server 101 according to the embodiment. The software shown here is held programmatically in the memory unit (ROM 203, HDD 204, etc.) included in the management server 101, and is read and executed by the CPU 201 of the management server 101, thereby realizing various controls and deal with.

The customer user management unit 301 manages user information of a customer user who uses the online shopping service. The information of the customer user has, for example, the configuration shown in FIG. 4A, and details will be described later.

The store management unit 302 manages the store information of each setting of the online store registered from the store user. The store information system has, for example, the configuration shown in FIG. 4B, and details will be described later.

The section management unit 303 generates various sections and registers them in response to requests from shop users. Further, the segment generation unit 303 performs processing such as editing, merging, and management of the registered segments. The segment information has, for example, the configuration shown in FIG. 4C, and the details are described. Further, a detailed description of the extents or a processing flow will be described later.

The UI control unit 304 provides a UI screen corresponding to the request from each PC in accordance with various setting contents. An example of a UI screen is shown in FIGS. 11A to 11G.

The customer user authentication unit 305 performs login control of the customer user who has accessed the online shopping website. Specifically, The authentication information (user name, password) input by the customer user is accepted, and the authentication process is performed based on the information of the user name and password managed by the customer user management unit 301. Further, the customer user authentication unit 305 also performs control when each customer user accesses the unique portal.

The shop authentication unit 306 performs authentication processing on access from the shop user. The certification here can be performed in the same manner as the authentication of the customer user, or another authentication method can be used. In addition, the store certification unit 306 also performs the participation process when the participation is requested from the store side to the intrinsic entrance. The details of this processing will be described later.

The search unit 307 searches for information of the customer who belongs to the section when the store user creates the section or edits it. The information searched here is equivalent to, for example, the number of customer users belonging to the section.

The product management unit 308 manages the information of the products displayed in each store in association with the store establishment. As for the information on the products, the products displayed in the store are registered and accepted. In this case, if it is a product that is generally sold, it may be registered in advance by the management server 101, and the shop user may be selected from among them. The product information has, for example, the configuration shown in FIG. 4D, and details will be described later.

The activity management unit 309 accepts and manages the registration of various activities (promotional activities, advertisements, etc.) in response to the registration request from the store. The activity information has, for example, the configuration shown in FIG. 4E, and details will be described later. Also, the activities registered here are exemplified at the general entrance. The person notified in the middle is limited to the person notified in the intrinsic entrance. The details of the event registration process will be described later.

The transaction management unit 310 manages information on purchase and sale transactions of products and the like between the customer user and the store. The information of the sale and purchase transaction has, for example, the configuration shown in FIG. 4F, and details will be described later.

[data composition]

4A to 4F are diagrams showing an example of the configuration of various materials managed by the management server 101 according to the present embodiment. The data shown here is assumed to be maintained in the internal or external memory area managed by the management server 101. Further, each of the information shown below may be managed by one table or may be managed by being divided into a plurality of tables.

FIG. 4A is a diagram showing an example of a data structure of customer information of a customer user. The customer information is composed of, for example, a customer ID, a user name, a password, a customer attribute, and a participation section. The customer ID is an ID (identification information) required to uniquely identify the customer user. The user name is a name used by the customer user on the website, and is used as a login name for the customer user to log in to various UI screens dedicated to the customer user. The password is used to authenticate the various UI screens dedicated to the customer user provided by the management server 101, and the customer user logs in. The customer attribute is the above-mentioned information about the customer (age (age), gender, birthplace, location (home address, company address), occupation, interest object, tariff plan or restriction, member type (silver member, Gold members, diamond members, etc.), etc.). Participation area The segment indicates the information of the segment corresponding to the intrinsic entry that can be accessed by the customer user.

FIG. 4B is a diagram showing an example of the data configuration of the store information about the store. The store information is composed of, for example, a shop ID, a shop name, a password, a shop attribute, a product ID, a participation section, and a participation form. The shop ID is an ID (identification information) required to uniquely identify the store. The store name is the name of the store used in the general entrance and the intrinsic entrance. The shop user also uses it as a login name when logging in on various UI screens dedicated to shop users. The password is used to authenticate the store user when logging in on various UI screens dedicated to the store user provided by the management server 101. The store attribute includes information such as the classification of the products displayed in the above-mentioned stores or the classification of the stores. The item ID is an identification information (ID) required to uniquely identify the item information displayed on the store. Participation section is information indicating the section to which the store belongs. Participation form includes information on the form in which the store participates in the section. As for the following, there is a "store type" that participates in the whole store, and a "commodity type" that participates in each product. In the case where the participation form is "store type", all the product information displayed in the product ID store is registered, or the link information of the other table that manages all the product information is registered. On the other hand, when the participation form is "commodity type", the product ID is registered with the information of the product registered as the participation target.

Fig. 4C is a diagram showing an example of the data structure of the section information. The section information includes, for example, section ID, creation shop, merge availability, section The name, the section attribute, and the participation in the store are formed. The section ID is an ID (identification information) required to uniquely identify the section. The store ID of the store in which the section is created. If it is the section generated by the management server 101, the intention is indicated. Whether or not the combination is possible is a setting indicating the possibility of merging of similar sections. The details of the information on the possibility of merging and the method of using the same are described in the second embodiment. The name of the section, which is the name of the section.

The section attribute indicates the attribute required to define the customer (target) to which the section belongs. The segment attribute is used to determine whether the customer user is the user to whom the segment belongs, that is, whether it is a customer user who can access the intrinsic entry corresponding to the segment. Moreover, it can also be used to potentially extract potential customers who can access the intrinsic portal. At this time, the attribute registered in the section attribute is compared with the attribute registered in the table of the customer information shown in FIG. 4A. For example, the USERA customer attribute of FIG. 4A is a male, a 30-year-old, a gold member, and has the participation qualification in accordance with the section attribute of the section A. Then, USER A actually registers the zone A as a participating zone.

Further, the section attribute may be used when defining a section (inherent entrance) in which the store can participate. For example, when the store applies for the participation of the intrinsic entrance, whether or not the permission is permitted to participate is determined by comparing the content of the shop attribute to which the shop is attached and the section attribute of the intrinsic entry. In addition, when a certain store wants to perform an activity such as a new promotion, it is possible to determine whether it is registrable by the relationship of the attribute when the activity is registered. Participate in the store Shop is a shop that has participated in the intrinsic entrance corresponding to the section. Here, the store ID of the store is indicated. In the store shown in the store, for example, the activity can be registered for the unique entrance corresponding to the section.

FIG. 4D is a diagram showing an example of the data structure of the product information of the products displayed in each store. The products referred to herein may be books, stationery, food, etc., and may also be services such as accommodation reservations, golf course reservations, multimedia downloads, and the like. In the following description, in order to simplify and not distinguish between objects or services, they are collectively referred to as "goods". The product information is composed of, for example, a product ID, a product name, a shop ID, and a product attribute. The item ID is an ID (identification information) required to uniquely identify the item, and corresponds to the item ID registered in the table of the shop information of FIG. 4B. The product name is the general circulation name of the corresponding product. The shop ID is the shop ID of the shop where the item is displayed. However, the relationship between the item and the shop is delimited in FIG. 4B. Therefore, the shop ID here may be omitted. The item attribute is a classification or object (target) indicating the item. For example, if the product is clothes, it may include information such as the type or name of the clothes (T-shirt, sweater, etc.), the gender of the purchaser, the size, the price, the availability of the coupon, the product description, and the product photo.

FIG. 4E is a diagram showing an example of a data structure for managing activity information required for a customer's promotion activity or a unique product notification (hereinafter collectively referred to as "activity") set by the store. The activity information includes, for example, an event ID, an event name, a shop ID, a section ID, a notification period, and an activity content. The activity ID is an ID (identification information) required to uniquely identify an activity. Store ID is the store that participates in the event. Store ID. In the present embodiment, the activity system may be implemented in a shop unit, or may be implemented in a shop that participates in an intrinsic entrance. In the latter case, the same store ID is assigned to the plurality of store IDs. For example, if there is only an activity performed by a certain store, the store will log in to the event. On the other hand, in the case of an activity that is common to a plurality of stores, a plurality of stores can be designated when the event is registered, and a section (inherent entry) unit can be used for designation. In addition, you can accept participation hope from the store side. The name of the event, the name given to the event. The section ID indicates the section ID of the section that will become the notification target (target) of the activity. The customer user who belongs to the section specified here is regarded as the notification object (target) of the activity. The notification period is a period during which the implementation of the activity is notified to the customer user, that is, the period during which the activity is implemented. In the period designated here, for example, in the predetermined UI screen of the unique portal, the notification of the activity is performed. The activity content indicates the details of the activity registered. The type of the activity is, for example, the issuance of a coupon that can be used as a banknote when the article is purchased in the store, and the issuance of a free shipping coupon that becomes free of charge when shopping in the store. The content here can also allow shop users to make more detailed settings, and the management server 101 side can also prepare pre-settable options. Further, it may be an advertisement or a notification (a commodity unit) for an individual product, or an advertisement or a notification (a shop unit) for the entire store.

4F is a diagram showing an example of a data structure of transaction information required for managing information on a transaction transaction (utilization history) performed between a store and a customer. The transaction information is composed of, for example, a transaction ID, a seller, a buyer, a date and time, and a transaction content. Transaction ID is used To uniquely identify the ID (identification information) required for the transaction. The seller is the seller information indicating the goods in the transaction. Here, it is the shop ID of the store that is a seller. The buyer is the buyer information indicating the goods in the transaction. Here, the customer ID of the customer user who is the purchaser is indicated. The date and time is the date and time information indicating the transaction. Contains information on purchased products, purchased stores, and access history. The transaction content indicates the type or number of products used in the transaction, other option information, and the like.

The example of the various materials described above is an example of the information used in the invention of the present invention, and may contain other information.

[Processing flow]

5 to 10 are flowcharts showing the processing described in the embodiment.

(store registration processing)

FIG. 5 is a flow chart showing the processing flow when the store user accesses the management server 101 from the store PC 102 and performs an application for registration of the store of the management server 101. By registering the store by this process, it is possible to open a store and expose the general entrance. Thereby, the customer user can access the registered shop on the general entrance.

This processing flow is realized by reading and executing a program stored in a memory unit such as an HDD by the CPU of each of the management server 101 and the shop PC 102. On the side of the management server 101, the shop management unit 302, the UI control unit 304, and the shop authentication unit 306 shown in FIG. The machine is capable of performing this process. Further, the store PC 102 has a web browser (not shown). The shop PC 102 accesses the management server 101 by using a web browser, using HTTP (Hyper Text Transfer Protocol) or the like, 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 the store to register. For example, the shop user can access the initial screen (Fig. 11A) provided by the management server 101 and request the store registration from it. FIG. 11A is a diagram showing an example of the configuration of an initial screen (general entry) when each PC is accessed. The login screen or the link when the store is registered is displayed. When the store is registered, you can select the link to obtain the store registration screen. In addition, a list of products or a list of products displayed in each store is displayed. For example, when a store is registered, the store user moves to the login screen by selecting the link. Further, the configuration of the entry screen is not limited thereto, and may be provided in a plurality of screens in response to the function.

In S502, the management server 101 provides a shop registration screen as a response to the store registration request from the store PC 102 (FIG. 11B). FIG. 11B is a diagram showing an example of a configuration of a shop registration screen when a store is registered in response to a request received from the store PC 102. When you log in to the store, you can enter information such as the name of the store, the product, the owner's information, and the attribute. The information of the shop name, attribute, and product that has been input is managed as the information of the shop name, the shop attribute registered in the table shown in FIG. 4B, or the product attribute shown in FIG. 4D. Reason. Further, if a large number of products are displayed, the products may be registered in a dedicated UI screen (not shown) after the shop is registered.

In S503, the shop PC 102 displays the shop registration screen provided from the management server 101 on the web browser, and accepts input of various shop information from the shop user. Thereafter, once the input is completed, the store PC 102 transmits the store information that has been input to the management server 101. At this time, it is also possible to register the product information such as the products displayed in the store together. When the product is registered, the product that has been input is registered in the table shown in FIG. 4D. In this case, the management server 101 registers the product through the product management unit 308. Further, it is also possible to register information on one or a plurality of shop attributes associated with the store itself. In the login here, the information that can be logged in may be changed under certain conditions in accordance with the tariff plan or protocol of the infrastructure service provided by the management server 101.

In S504, the management server 101 issues information such as a shop ID or a password once the shop information is received from the shop PC 102, and registers with the shop information to the table shown in FIG. 4B.

In S505, the management server 101 notifies the store PC 102 of the notification of completion of registration, together with the information that has been issued.

In S506, the shop PC 102 receives the information transmitted from the management server 101 and displays the information. Thereafter, the processing flow is ended.

(Customer user login processing)

FIG. 6 is a diagram showing a flow of processing when the customer user accesses the management server 101 from the client PC 103 and performs user login. The management server 101 side performs the present process by the function of the customer user management unit 301, the UI control unit 304, and the customer user authentication unit 305 shown in FIG. This processing flow is realized by reading and executing a program stored in the HDD or the like by the CPU of each of the management server 101 and the client PC 103. Further, the client PC 103 has a web browser (not shown), accesses the management server 101 via a 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 the user to log in.

In S602, the management server 101 provides a customer user login screen as a response to the user registration request from the client PC 103 (FIG. 11C). FIG. 11C is a diagram showing an example of a configuration of a customer user registration screen when a customer user is registered in response to a request received from the client PC 103. When the customer user logs in, the user name, date of birth, contact point, attribute, password, section designation, etc. can be entered. Others can also enter personal information such as gender, birthplace, location (home address, company address), occupation, and interests. The user name, password, and personal information that have been input 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 process provided from the management server 101 on the web browser. The customer user accepts input of various user information. Thereafter, once the input is completed, the customer PC 103 transmits the user information that has been input to the management server 101. At this time, 1 or a plurality of attribute information associated with the customer user itself can be registered. In addition, it is possible for the customer user to select an arbitrary section from among the sections associated with their own attributes, and to specify whether or not to apply for participation. Alternatively, for example, the section may be automatically assigned by the management server 101 side in accordance with the tariff plan or the attributes of the customer user. As described above, the customer user who has been assigned a section can access the intrinsic entry corresponding to the section.

In S604, the management server 101 issues information such as the customer ID when the user information is received from the client PC 103, and the user information is registered in the table shown in FIG. 4A. Here, when the accepted user information includes an application for participation in the section, whether or not the customer user can participate in the selected section will be recognized and authenticated. If the license is granted, the information of the section will be registered to the participating section of Figure 4A. The details of the processing of the participation approval determination and the authentication herein may be based on, for example, the attribute of the customer user or the attribute of the product purchased in the past, the correspondence relationship with the attribute of the section, and the like. For example, it is also possible that only a customer who has purchased the performance of the product having the attribute corresponding to the attribute of the section can participate in the section. By this processing, it is possible to prevent participation in a section that has no relationship with the customer user.

In S605, the management server 101 notifies the customer PC 103 of the completion of the registration, together with the information that has been issued.

In S606, the customer PC 103 is from the management server. The information transmitted by 101 is received and displayed. Thereafter, the processing flow is ended.

(inherent entrance participation processing)

FIG. 7 is a flowchart showing a process flow when the shop user accesses the management server 101 from the store PC 102 and applies for participation in the intrinsic entry corresponding to the already set section. According to this processing, when the store has participated in an arbitrary entrance, for example, the display of the store or the product can be performed on the unique entrance, or the advertisement for the activity in the inherent entrance can be limited.

This processing flow is realized by reading and executing a program stored in the HDD or the like by the CPU of each of the management server 101 and the shop PC 102. The management server 101 side performs the present process by the store management unit 302, the segment management unit 303, the UI control unit 304, and the shop authentication unit 306 shown in FIG. Further, the store PC 102 has a web browser (not shown), accesses the management server 101 via a 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 a unique entry. At this time, it is assumed that the shop has been registered to the management server 101, and the authentication by the shop authentication unit 306 using a password or the like has been completed.

In S702, the management server 101 provides an inherent entry as a response to the participation request from the intrinsic entrance of the store PC 102. Participate in the screen (Figure 11D). FIG. 11D is a diagram showing an example of a configuration of an intrinsic entry participation screen when a unique entry (segment) is participated in response to a request received from a store PC. Here, the store can make a request for participation (application) by designating the section corresponding to the intrinsic entrance to be participated or the intrinsic entrance itself. In addition, a list (list) of segments that can participate can be displayed as an option. Also, information on the attributes associated with the section creation may be displayed together. Further, the store user may enter an attribute, display an intrinsic entry associated with the section having the attribute that has been input, and accept the selection input from the shop user.

Even the shop user can select the participation form by the screen of Fig. 11D. In the form of a store type that participates as an intrinsic entrance, it is a form of a store type that participates in the whole store, and a form of a product type that participates in each product displayed in the store. If you select "Store Type" as the participation form, you do not need to set the item. On the other hand, if "commodity type" is selected as the participation form, the item to be published in the intrinsic entrance is selected. The choice of the product may also be a method of specifying the goods one by one, or a method of specifying the type or type of the goods. For example, if the shop is a drug store, the paper diaper or milk powder may be individually designated as a product, but it is also possible to specify the type of the individual product in the form of a baby product. The information that has been set here is registered as the information of the product ID, the participation section, and the participation form of FIG. 4B, and is registered to the store information.

When it is designed to be able to participate in the form of participation, it is a site that can be accessed from the intrinsic entrance, and the products displayed in the store are all intrinsically owned. Entrance. Therefore, the activities (coupons or free shipping) that are applicable to all the intrinsic entrances will become applicable to all the stores. On the other hand, in the participation form of each product, some of the products displayed in the store are selected and can be accessed from the intrinsic entrance. At this time, even if the activity applied to the entire intrinsic entrance is a product or the like that has already been registered to a part of the intrinsic entrance. In such a large-scale store that displays a plurality of products, it is not possible to participate in a store that has an intrinsic entrance, and it is also possible to participate in a product unit.

In S703, the shop PC 102 displays the unique entry participation screen provided from the management server 101 in the web browser, and receives input of information of the unique entry (segment) of the participation target from the store. Thereafter, the store PC 102 transmits the information of the selected unique portal to the management server 101. Further, in the selection of the section, the unique entry (segment) that cannot be participated can be displayed without being displayed from the beginning, and the display control of the UI screen can be performed. The intrinsic entry that cannot be joined is that the store or the product displayed in the store does not have an intrinsic entry to the attributes of the section to which the intrinsic entry is established. In this case, it is preferable that the store department excludes from the option that it is not eligible to participate in the inherent entrance. Alternatively, it may be included in the list display in order to give an incentive to participate in the future, but it may be grayed out or the like and excluded from the selection target.

Next, in S704, the management server 101, upon receiving the selection of the unique entry from the store PC 102, performs approval determination and authentication as to whether or not the store can participate in the selected intrinsic entry. once When it is permitted to participate in S704, the information of the section that is the intrinsic entrance that has been permitted is registered in the participation section of FIG. 4B, and the information of the store is registered in the participating store shown in FIG. 4C.

The details of the process of the determination and the authentication in S704 are made after the registration request has been made on the management server 101 side after having the participation request from the store PC 102 side to the unique entry. In the approval determination at this time, for example, the authority on the store side (the utilization plan of the infrastructure service made by the store) or the regulation, the section to which the intrinsic entrance is established, the attribute of the store, or the store The correspondence between the attributes of the displayed products and the like.

Then, in the approval determination, as a condition for participating in the intrinsic entry, it is also possible to request a transaction performance with a customer user who has already registered in the intrinsic portal, or to request that the evaluation of the store has obtained a certain evaluation or more. The presence or absence of the transaction performance can be determined by referring to the transaction information of FIG. 4F. As for the presence or absence of the actual performance, the threshold value may be set in accordance with the number of customer users who have already registered in the intrinsic entrance, and the intrinsic entrance to the number of participating users may be used as a store. The more the transaction results are required to participate in the conditions. Alternatively, the inherent entry of the number of customer users is a condition for relaxing the performance of the transaction and setting a lower threshold. On the other hand, for the newly established intrinsic entry, the condition is set to the attribute of the segment. The actual sales of goods or services, or the performance of transactions with customers who have such attributes, are more frequent.

In S705, the management server 101 transmits a notification of completion of the participation processing of the unique entry to the store PC 102.

In S706, the store PC 102 receives the notification of completion of the participation processing of the unique portal from the management server 101, and displays the intention. Thereafter, the processing flow is ended.

(section registration processing)

In FIG. 7, although the process of the shop application to participate in the established entry is described, the process of newly setting a section by the store and opening the intrinsic entrance is described below. FIG. 8 is a flow chart showing the processing flow when the shop user accesses the management server 101 from the store PC 102 and registers the session. The management server 101 side performs the present process by the store management unit 302, the segment management unit 303, the UI control unit 304, the shop authentication unit 306, and the search unit 307 shown in FIG.

This processing flow is realized by reading and executing a program stored in the HDD or the like by the CPU of each of the management server 101 and the shop PC 102. Further, the store PC 102 has a web browser (not shown), accesses the management server 101 via a 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 a zone registration. At this time, assuming that the store has been registered to the management server 101, authentication using a password or the like has been completed.

In S802, the management server 101 provides a segment registration screen as a response to the segment registration request from the store PC 102 (FIG. 11E). FIG. 11E is a diagram corresponding to the receipt from the store PC 102. An example of the configuration of the section registration screen when the section is registered is requested. The customer user can enter the name of the section, the attribute, and the possibility of merging. The section name, attribute, and mergeability that have been input are managed as the section name, merge possibility, and section attribute registered in the table shown in FIG. 4C after the section has been set. Further, in FIG. 11E, although the attributes are set and summarized, the attributes may be set for each category such as a store, a customer, and a product.

In S803, the shop PC 102 displays the section registration screen provided from the management server 101 on the web browser.

In S804, the store PC 102 accepts input of various section information from the store user. At this time, the store PC 102 accepts the input of the attribute corresponding to the section. Thereafter, the store PC 102 transmits the information of the accepted 1 or plural attribute to the management server 101.

In S805, the management server 101 searches and extracts the information of the customer user corresponding to the combination of the attributes based on the combination of the received attributes. Here, the information of the extracted customer user is equivalent to, for example, the total number of customer users, but may be other information. For example, the customer users who have been drawn may also be classified according to age, gender, occupation, origin, location, interest object, etc., and the number of customer users for each category is provided. Alternatively, it may be the number of customer users who have purchased the performance of the product associated with the property. These conditions can also be entered by the customer user along with the attributes in S804. In addition, customer information is equivalent to personal information, and it is generally intended to be managed. There are strict restrictions, so detailed information such as the customer's personal name or address may not be output. Moreover, if the complex attribute has been input by the shop user, the AND condition of the attribute may be used for the search, or the OR condition may be used for the search. Further, the number of attributes that can be input by the shop user may be set as the upper limit number/lower limit number depending on the search result. After the search is completed, the management server 101 notifies the store PC 102 of the search result.

Further, the attribute that can be input by the shop user in S805 may be the same as the attribute of the shop user's store or the person associated with the attribute (included by the attribute range). Regarding the relevance or range of the attribute, in the present embodiment, the attributes can be hierarchically set as the upper concept, the median concept, and the lower concept. The subordinate concept is covered by the upper concept and the median concept, and the median concept is covered by the scope of the upper concept. For example, the concept of the upper concept of clothing includes the median concept of suits and kimonos, and the concept of suits and lowers includes suits, jackets, and pants. Therefore, if this attribute of "clothing" is selected, the suit or jacket is associated with the attribute and is included in its scope. By limiting the attributes that can be input in this way, it is possible to prevent the setting of a section that is not related to the store.

In S806, the shop PC 102 receives the information transmitted from the management server 101 and displays the information. Based on the search result, the store PC 102 receives an instruction from the store user whether or not to register in the content of the section information.

In S807, the store PC 102 determines whether or not the registration instruction has been received from the store user. If the login instructions have been accepted (YES in S807) Proceed to S808. If the instruction to change the input attribute has been accepted (NO in S807), the process proceeds to S804, and the process is repeated. By referring to the search results, the shop user can determine whether the set attributes are properly captured and should be used as customer customers of the store's potential customers. If the shop user does not get the expected search result, the attribute can be reset and the above process can be repeated. In this way, the store user can establish an intrinsic entry that can efficiently capture potential customer users.

In S808, the shop PC 102 transmits an instruction to register from the shop user and the segment information that has been input to the management server 101.

In S809, the management server 101 issues information such as the segment ID once the segment information is received from the store PC 102, and registers the segment information in the table shown in FIG. 4C. In this case, it may be configured such that the shop in which the section is created participates at the beginning, and the created shop can be selected. Here, the management server 101 may be configured to reject the creation of a segment that does not exceed the predetermined threshold or the number of customers based on the number of stores corresponding to the segment information or the number of customers. In addition, it is also possible to consider the presence or absence of a transaction performance (sales performance) of a customer user corresponding to the attributes included in the section information. For example, it is possible to design a store that does not have a sales performance with the customer user or a store that does not have a certain number of sales performances, and does not recognize the creation right of the section, and refuses to apply.

In S810, the management server 101 transmits a notification of completion of registration to the store PC 102.

In S811, the store PC 102 receives the notification of completion of the registration and receives it from the management server 101, and displays the intention. Thereafter, the processing flow is ended.

In addition, although the flow of the process of generating and registering a new section is shown in FIG. 8, the same flow is performed also when editing the content of the section which has already been registered. As the main editing content, there are additions, corrections, deletions, and the like of attributes corresponding to the section creation. In the case of editing, the change request is transmitted in the items S801 to S803, and the section to be edited is selected in the edit screen obtained as the response.

(active login processing)

Fig. 9 is a flow chart showing the activity registration processing described in the embodiment. The management server 101 side performs the present process by the store management unit 302, the segment management unit 303, the UI control unit 304, the shop authentication unit 306, and the activity management unit 309 shown in FIG.

This processing flow is realized by reading and executing a program stored in the HDD or the like by the CPU of each of the management server 101 and the shop PC 102. Further, the store PC 102 has a web browser (not shown), accesses the management server 101 via a web browser, and displays various UI screens provided by the management server 101. In addition, the process of displaying or notifying the activity registered here will be described later using FIG.

In S901, the store PC 102 is based on the use from the store. The user's instruction is to access the management server 101 and perform an activity registration request. At this time, it is assumed that the shop has been registered to the management server 101, and the authentication by the shop authentication unit 306 using a password or the like has been completed. Further, in the registration of the event, the upper limit of the number of registrations may be set for each store, or the registration may be determined depending on the content of the event. At this time, it is assumed that, upon request registration from the store PC 102, the management server 101 side controls the approval process (not shown) for performing the event registration.

In S902, the management server 101 provides an activity registration screen as a response to the event registration request from the store PC 102 (FIG. 11F). FIG. 11F is a diagram showing an example of a configuration of an event registration screen when an event is registered in response to a request received from the store PC 102. For shop users, you can enter information about the event name, section ID, notification period, and activity content. The information that has been input is managed as information on the activity name, the section ID, the notification period, and the activity content registered in the table shown in FIG. 4E. In addition, when making a selection from a section that has already been registered, it is also possible to display a list of sections that can be selected.

In S903, the shop PC 102 displays the event registration screen provided from the management server 101 on the web browser.

In S904, the store PC 102 accepts input of various event information from the store user. At this time, the selection of the section corresponding to the activity is accepted. Here, the section that the store user can select is equivalent to the section corresponding to the unique entrance to which the store participates. In the selection of the section, the section preset that cannot be registered may not be displayed or may not be selected to perform display control of the UI screen. Again, if not It is an activity limited to the intrinsic entrance, but an activity carried out at the general entrance, and the selection of the section is not performed, and the object is set as a general entrance. In addition, new sections can be generated in this project. Thereafter, the store PC 102 transmits the received event information to the management server 101. By selecting the target section (customer user) from the store side as the setting of various event information, it is possible to clearly specify the other party who wants to be the target of the login activity (the section and the intrinsic entrance to which the association is established) ). In addition, even if the store does not participate in the intrinsic entrance, it is possible to attribute the attribute of the product to the attribute to be registered in the section to be registered. It is the same, it is licensed to log in. Further, when the section is selected, the number of customer users who are notified of the event may be displayed.

In S905, the management server 101, when receiving the event information from the store PC 102, issues information such as the event ID by the event management unit 309, and registers the event information in the table shown in FIG. 4E. In addition, it is also possible to set a composition that can be additionally applied/approved, or authenticated in the login. For example, after the information of the activity is input from the store PC 102 side in the project of S904, the input of the input content (automatic determination or determination by the manager) is performed on the management server 101 side. Log in. The confirmation at this time is, for example, based on the authority on the store side (the utilization plan of the infrastructure service made by the store) or the stipulations.

In S906, the management server 101 transmits a notification of completion of registration to the store PC 102.

In S907, the shop PC102 is the one that completes the login. It is known that it is received from the management server 101 and the intention is displayed. Thereafter, the processing flow is ended.

In the descriptions of FIGS. 5 to 9 above, the processing of registration of customer users, stores, products, events, sections, and the like has been described. However, for example, when the information has been registered, the same procedure can be used. Carry it out. In this case, in response to a request from each PC, a UI screen for editing (not shown) is supplied from the management server 101 to each PC, and is edited through the UI screen.

(activity notification processing)

The notification method of the activity described in the embodiment will be described below. In the present embodiment, after the customer user has performed the user registration, by logging in to the service website provided by the management server 101, the user can migrate to the unique access point that can be accessed. In the intrinsic portal site, the content (activity) displayed along with the corresponding section is different. Specifically, as described above, an intrinsic entry is established for each of the sections, and an activity for registering the intrinsic entry is displayed. Similarly, when accessing a general portal is registered as an activity specific to the general portal, it is notified. In accordance with the attribute information of the customer user, the portal (inherent entrance) that the customer user can access may vary.

Fig. 10 is a flowchart showing the processing of the notification of the activity described in the embodiment. This processing flow is realized by reading and executing a program stored in a memory unit such as an HDD by the CPU of the management server 101. On the side of the management server 101, the customer user tube shown in FIG. The management unit 301, the UI control unit 304, the customer user authentication unit 305, and the activity management unit 309 perform the present process by functioning.

In S1001, the management server 101 receives the login request from the customer user through the client PC 103. At this time, the management server 101 accepts the user ID and the password together and performs authentication processing. Here, it is assumed that the authentication is successful and the process proceeds.

In S1002, the management server 101 refers to the customer information of the authenticated customer user, and determines whether or not there is a section that is registered as a participant. If there is a zone that can participate (YES in S1002), the process proceeds to S1003, and if there is no zone that can participate (NO in S1002), the process flow ends.

In S1003, the management server 101, for the logged-in customer user, grants access to the intrinsic portal corresponding to the zone that has been and can participate.

In S1004, the management server 101 controls to display the activity corresponding to the section based on the table of FIG. 4E when the customer user accesses the unique entry that has been permitted to be accessed in S1003 ( Figure 11G). FIG. 11G is a diagram showing an example of a configuration of a notification screen of an activity displayed when a customer user accesses a web page having an intrinsic entrance. Here, when the customer user accesses the unique entry that can be accessed, the activity involved in the unique entry is displayed. In the example of FIG. 11G, the event is displayed in a list form, but is not limited thereto. For example, it may be displayed at every other time in the field for displaying the activity in the web page. Thereafter, the processing flow is ended.

In addition, in the present embodiment, although it is shown, An example of displaying and notifying the intrinsic access of the access is not limited thereto, and other notification methods may be used.

[Effect of this embodiment]

According to the present embodiment described above, among the customer users registered in the portal (general portal) provided by the management server, only the customer users associated with the specific attributes can be targeted. Provide an intrinsic entry. The intrinsic entry is in a store that has already been registered in the general entrance, and only a specific store that satisfies the conditions related to the specific attribute mentioned above can participate. In other words, the intrinsic portal is an portal that is provided as a place for a store that associates a specific attribute with a customer, and from the standpoint of the customer, it is efficient to participate in the intrinsic entrance. By finding out the goods or services you need, you can save money on the procedures or burdens of finding the goods or stores you need from most stores or products. In addition, from the standpoint of the store, customers who have the need (demand) for the products and services displayed in the store can be provided, and the customers and users can efficiently provide goods and services, thereby making the store operations change. Be efficient. In particular, instead of selling to a specific number of customers in a general entrance, it is better to link them to sales more reliably, and to increase sales performance more efficiently.

In addition, the intrinsic entry of the present embodiment is set up by setting a condition for a store or a customer who can participate in the management server, and it is possible to store a shop or a customer who is not related to the product or service displayed in the intrinsic entrance. Stores with low sales or low evaluations are excluded. Take this From the standpoint of the guest users, it is only necessary to participate in the intrinsic entrance, which saves the trouble of filtering the shops that display the products they need, even those that have not been traded in the past can be easily found. Moreover, if the intrinsic entrance is accessed, the information on the activity of the store in which the intrinsic entrance is made can be surely obtained, so that the event information can be prevented from being missed. On the other hand, from the standpoint of the store, for the customer users who need their own goods or services, the event notifications and the like can be made effective, so that not only the customer users who have conducted the transaction, but also the purchases have not been made so far. Potential customers such as resumes can still be effectively directed to the store.

<Second embodiment>

This embodiment is an embodiment in which the sections set by the store user are combined (integrated) with the similarity. When a store user generates a plurality of sections, it is expected that a similar section will be generated. In this case, the management of the sections is facilitated by merging the sections. In the case of similar sections, the same will be similar, even if the merger is not a problem. On the other hand, sections that do not want to be merged are also present. In consideration of these, in the present embodiment, the merging process of the segments is performed.

First, in the present embodiment, it is assumed that the store user receives a setting for permitting the merge in the registration/editing screen of the session.

(combination of sections)

Fig. 13 is a view showing a flow of processing for integrating segments in the management server 101 according to the present embodiment. This processing flow is realized by reading and executing the program stored in the HDD or the like by the CPU of the management server 101. The execution sequence of the processing flow may be executed at a predetermined date and time, or when the number of segments having the same or similar attributes exceeds the fixed number, or the number of segments made by a certain store exceeds the predetermined number. Only when executed.

In S1301, the management server 101 acquires the segment information that has been generated by referring to the table of FIG. 4C. At this time, the section is retrieved by using the shop ID as a search key.

In S1302, the management server 101 removes the information of the section that is prohibited from being merged from the acquired section information. The section that is prohibited from being merged here can be set by the shop user, and specifically, it is judged with the setting of "merger or not" in FIG. 4C.

In S1303, the management server 101 derives the similarity between the segments based on the respective attributes of the segment information. The method of deriving the degree of similarity herein is not particularly limited, but may be, for example, a ratio of the number of identical attributes to the number of types of attributes of the two sections between two sections, or a uniform attribute The value of the weighted addition of the number and the number of inconsistent attributes can be calculated by these methods. After calculating the similarity to the combination of all the sections, the management server 101 sorts the order of similarity by the combination of high and low.

In S1304, the management server 101 is among the combinations of the already sorted sections, and determines whether the similarity of the combination with the highest similarity is Above the threshold specified. The predetermined threshold value here is assumed to be set in advance and is held in the memory area of the HDD or the like. When the similarity of the combination of the sections having the highest degree of similarity is equal to or greater than the predetermined threshold (YES in S1304), the process proceeds to S1305, and when it is less than the threshold (NO in S1304), the processing flow is ended.

In S1305, the management server 101 merges the sections with the highest similarity with each other. The so-called merging here is to newly create a section, and associate an attribute associated with a section that is considered to be similar, and establish a relationship with the new section. Thereby, the intrinsic entries corresponding to the merged segments are respectively established, and are also integrated into one. Then, the segments that are considered similar are deleted. Further, in the table of FIG. 4C, regarding the segments generated by the merge, a flag may be set to let people know the intention. Moreover, the section before the merger may not be deleted, but the information is managed as a section before the merger. After the merging process of S1305 is completed, the process returns to S1303, and the combination of the new segments is again added to calculate the similarity.

As described above, according to the present embodiment, similar sections can be automatically merged on the management server side when similar sections are increased. Moreover, the state can be maintained for a specific section that does not want to be merged.

Although the above description shows an example in which the sections generated in the same store are merged, similar sections may be merged between different shops.

<Third embodiment>

This embodiment shows a notification about the activity of the customer user. The method is an example different from the first embodiment. The intrinsic entry described in the first and second embodiments above is accessible only to a customer user having a specific attribute, and the customer user has a potential need for a product or the like displayed on the store. However, from the perspective of each store, not all of the stores have a transaction performance with all the customers, and it is not difficult to imagine that there will be a customer who has not had a transaction performance with the store. Then, in the first and second embodiments described above, an invention in which a new transaction performance can be generated with such a customer user has been described. On the other hand, it is also considered that, with the store, there is a case where it is desired to limit the activity of the customer who has only the transaction performance. Therefore, in the present embodiment, a method of giving priority to an activity notification to a customer user who has a transaction performance is described.

Fig. 14 is a flow chart showing the processing of the notification of the activity described in the embodiment. This processing flow is realized by reading and executing a program stored in a memory unit such as an HDD by the CPU of the management server 101. The management server 101 side performs the present process by the function of the customer user management unit 301, the UI control unit 304, the customer user authentication unit 305, the activity management unit 309, and the transaction management unit 310 shown in FIG. S1401 to S1403 in Fig. 14 are the same as S1001 to S1003 in Fig. 10 described in the first embodiment, and thus the description thereof is omitted.

After S1403, in S1404, the management server 101 refers to various forms and determines whether there is an activity registered by the shopper who has already logged in in the store where the purchase procedure has been performed in the past. Specifically, the table shown in FIG. 4E and FIG. 4F managed by the transaction management unit 310 will used. If there is no activity registered by the store having the purchase history (NO in S1404), the process proceeds to S1406, and if yes (YES in S1404), the process proceeds to S1405.

In S1405, the management server 101 controls the display of the matching section based on the table of FIG. 4E and FIG. 4F when the customer user accesses the unique entry that has been permitted to be accessed in S1403. And the activities corresponding to the store. Thereafter, the processing flow is ended.

As described above, according to the present embodiment, it is possible to control whether or not to notify the event in accordance with the past purchase history of the customer user.

In the above description, it is described that only the event notification of the store where the actual performance is purchased is displayed for each customer user, but the embodiment of the invention is not limited to the notification method. For example, when the event registration is performed on the store side of FIG. 11F, the event notification event can be set to all customer users participating in the intrinsic portal, or only to the customer user who has the transaction performance. In this way, the activity notified in the intrinsic portal includes an activity (normal activity) in which all participants of the intrinsic entry are notified, and a notification of the notification to the store. 2 types of activities (limited activities) of customer users. At this time, the customer user A who has a transaction performance with the store A is displayed for the limited activity notified by the store A, and the customer user B who has no transaction performance with the store A is stored. Take the intrinsic entry and it will still not be displayed. On the other hand, the general activity notified by the store A is displayed whenever the customer user A and the customer user B access the intrinsic entrance. Then, when customer user A accesses the intrinsic entrance, the activity is limited. Both sides of the general event will be displayed, and the limited activities can be displayed in a way that can be distinguished from the general activities. For example, the notification of the limited activity may be set as a group to give a display indicating that this is a limited activity (a title surrounded by a box, or a title indicating that it is a limited activity, etc.). Alternatively, the notification of the limited event may be set in preference to the display order of the notification of the general event.

Further, the limited activity may be set to only a part of the notification period set in FIG. 11F, and the remaining period may be switched to the general activity. For example, if the notification period is one week, the first two days are notified only for the customer who has the transaction performance as the limited activity, and the remaining five days are switched to the general activity and are accessible. All customer users of the portal are notified.

As described above, according to the present embodiment, it is possible to control the activity in the intrinsic entrance of the store and control the presence or absence of the transaction with the store, thereby more effectively performing the event notification to the customer.

<Other Embodiments>

In addition, the above-mentioned inherent inlet may also have a function of specializing the section. For example, it is also possible to provide only the function of the activity or the store in which the section corresponding to the unique entry is registered on the unique entrance. In addition, it is also possible to register an activity that can be utilized only at the intrinsic entrance. Further, it is also possible to allow the customer user to search for the store from the product having the attribute associated with the segment.

Further, it is also possible to request registration of an activity from the customer side to the store side having the predetermined attribute through the unique entrance. It is even possible to configure that a section having a predetermined attribute can be registered from the customer user side.

The present invention is not limited to the embodiments described above, and various modifications and changes can be made without departing from the spirit and scope of the invention. Therefore, in order to disclose the scope of the invention, the following claims are attached. Further, the information processing device according to the present invention can be realized by causing one or more computers to function as the information processing device. The program can be provided/distributed by being recorded on a computer readable recording medium or via a telecommunication communication line.

101‧‧‧Management Server

102‧‧‧Store PC

Claims (17)

A management server is a first portal website for online shopping that provides access to a virtual store before reciprocating; and an access to a virtual store that provides a part of a specific attribute among the plurality of virtual stores. The management server of the second portal of the specific attribute is characterized by: management means: management information including information on the attributes of the virtual store having the preceding virtual number, and the second entry website having the pre-record The website information of the information on the attribute of the specific attribute; and the first acceptance means are applications for receiving and providing access, and are used to request any of the virtual stores from the previous virtual store to be recorded in the second entry site. In the case where the first access means receives the application for the advance access request, the method of determining the access to the virtual store determines the pre-recorded information based on the pre-store information and the pre-book information managed by the pre-recording means. Whether the virtual store that provides the application has the attribute specified in the pre-recording; In the case where the virtual store that provides the application for the application has the attributes specified in the pre-recording, the pre-recording management means updates the store information of the virtual shop in which the application is provided for the pre-recording, and the second entry site is provided to the virtual Access to the store. The management server described in claim 1, wherein the pre-stored store information includes the product displayed in the pre-record virtual store. The pre-recording means is based on whether or not the attribute of the pre-recorded item displayed on the virtual shop in which the pre-recorded access request is provided has a pre-recorded attribute, and whether the virtual shop that has made the pre-record access request has the pre-record Specific attributes. The management server according to claim 1, wherein the pre-store information includes information on the attributes of the products displayed in the virtual store; and the first acceptance means is to provide an application for the advance access, and the application is performed according to the application. Each of the products displayed in the virtual store is accepted; the pre-determination means is based on whether or not the attribute of the pre-recorded product that has received the application for the pre-record access has the attributes specified in the pre-recording, and determines the virtual shop in which the application for the pre-record access is provided. Whether or not the pre-recording means determines that the virtual shop that has made the application for the pre-recording access has the attributes specified in the pre-recording, and the pre-recording means is the virtual shop that has made the application for the pre-recording access. The store information is updated to indicate that the second entry site provides access to the products that have been applied for in the virtual store. The management server according to any one of claims 1 to 3, wherein the pre-recording management means further manages: a customer user who can access the virtual store through the first entry website and the second entry website User information containing information about the attributes of the customer user; Among the customer users who can access the virtual store through the first portal site, only the customer who has the attribute specified in the previous entry can access the virtual store through the second entry site. The management server according to claim 4, further comprising: a second receiving means for accepting an access permission request for requesting access to the virtual store from the first entry site The user's user's permission to access the virtual store through the second entry site; in the case where the second access means receives the pre-registration permission request, the pre-determination means is based on the pre-recording managed by the pre-recording means. The user information determines whether the customer user who has made the pre-registration permission application has the attribute specified in the pre-record, and the pre-determination determining means determines that the customer user who has made the pre-registration permission application has the attribute specified in the pre-recording, The pre-recording management means updates the user information of the customer user who has made the pre-registration permission application to indicate that the customer user can access the virtual store through the pre-recorded second portal. The management server according to claim 4, wherein the pre-recording management means further manages the information of the transaction history of the pre-recorded virtual store; the pre-determination means further determines based on the information of the pre-recorded transaction history, and performs the pre-recording access provision application. Whether the virtual store has a transaction performance with a customer who can access the virtual store through the second portal; In the case where the pre-recording determination means determines that the virtual shop that has made the application for the pre-recording access has the attribute of the pre-recording and the performance of the pre-recording, the pre-recording means is the shop of the virtual shop that has made the application for the pre-recording access. The information is updated to indicate that the second entry site provides access to the virtual store. The management server described in the claim 6, wherein the pre-determination determining means determines whether or not there is a number of customer users who can access the virtual store through the pre-recording second portal site in the determination of whether or not the pre-recorded transaction performance is present. Corresponding to the fixed number of transactions. The management server according to claim 4, further comprising: a third receiving means for receiving the virtual store before the access is provided from the second portal site, and passing the second entry in the second entry site of the preceding entry An application for a customer-specific event that accesses a virtual store on the website. The management server according to claim 8, wherein the pre-recording activity is to access the virtual store only through the pre-recorded second portal site by the customer user who has a transaction with the virtual store that has applied for the activity. The customer user is the object. The management server according to claim 8, wherein the pre-recording activity system is provided with a period in which the activity is performed in the second entry website; the pre-record activity is a period during which part of the pre-recording period is only The customer who has applied for the activity has a customer who has a transaction performance and is a customer who can access the virtual store through the second entry site. The remaining period in the pre-recording period is All customer users who can access the virtual store through the second entry site are targeted. The management server according to claim 4, further comprising: a fourth receiving means for accepting a setting request of a new second portal site from any of the plurality of virtual stores; and providing means In the case where the pre-recording request is accepted, the customer who has the attribute associated with the property of the new second portal site, and which is accessible to the virtual store through the first portal site The information is provided to the pre-record virtual store. The management server according to claim 11, wherein the pre-recording providing means provides the information of the pre-recorded customer user by the information of the number of users of each attribute of the customer user. The management server according to claim 12, wherein the attribute of the pre-recorded customer user includes at least one of age, age, gender, origin, location, home address, company address, occupation, and interest object. The management server described in the claim 11, wherein the pre-recording receiving means is only accepted, and has a setting request of the second portal site that is related to the attribute of the virtual store required to perform the pre-recording setting. The management server according to any one of the items 1 to 3, further comprising: an integration determination means for determining whether or not the second entry site exists before the plural attribute having the attribute specified in the foregoing is common The second portal site is integrated. A management method for managing a server, managed by: providing access The first entry site of the online shopping for accessing the plurality of virtual stores; and the management of the second portal site having access to the virtual store having a certain attribute to the virtual store in the virtual store The server control method is characterized in that it has an acceptance request, and is an application for accepting an access request, and is for requesting one of the virtual stores from the previous virtual store, and the second entry site In the case of the pre-recorded first access means, the store information of the information including the attribute of the pre-record virtual store, and the second entry of the pre-recorded second entry The website has information on the website that has previously recorded the specific attribute information, and determines whether the virtual shop that has made the application for the pre-record access has the attribute specified in the pre-record; and the update project is determined in the pre-determination project, and the pre-record is performed. In the case where the virtual store providing the application has the attributes specified in the pre-record, the application for the pre-record access will be provided. Virtual shop store information, updated to indicate Hutchison second portal system before providing access to the virtual shop of access. A computer program is a means for causing a computer to function as a management server as recited in any one of claims 1 to 15.