JP2011060094A - Message board function providing system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily provide a message board function in pages of various services and to allow a user to use a message board of each service without being conscious of a service in use. <P>SOLUTION: A message board function providing system includes: a message board front-end part for receiving at least a topic registration request, a message posting request and a message retrieving request from each of a plurality of service providing parts for providing services on a web, and transmitting a processed result as a response; a topic/message registration processing part for registering topic data and message data for a message storage according to a request from one service providing part received in the message board front-end part; and a message reference processing part for retrieving and referring to the registered data for the message storage, according to a request from another service providing part received in the message board front-end part. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a technique for posting and referring to a message board (electronic bulletin board) via a network such as the Internet.

  In a web system such as a large-scale (huge) portal site, various services such as shopping, auctions, encounters, babies, and moving images are developed on different pages. The functions on each service page are developed and operated independently for each service in principle, except for basic functions such as user ID management.

  On the other hand, there is a message board function as means for communication between users (see, for example, Patent Document 1), but this message board function is also constructed independently for each service.

JP 2009-151776 A

  As described above, since the conventional message board function is constructed independently for each service, it has not been a system that cooperates with message boards in other services. For this reason, there is a bad usability that it is necessary to use a message board in consideration of the service currently used.

  The present invention has been proposed in view of the above-described conventional problems, and the object of the present invention is to easily implement a message board function on various service pages, and to provide services currently used. The object is to provide a message board function providing system that can use the message board of each service without being conscious of it.

  In order to solve the above problems, according to the present invention, as described in claim 1, at least a topic registration request, a message posting request, and a message are received from each of a plurality of service providing units that provide services on the Web. A message board front-end unit that receives a search request and returns a processing result as a response, and registration of topic data and message data in the message storage in response to a request from one service providing unit received by the message board front-end unit In response to a request from the topic / message registration processing unit that performs the above-described processing and the other service providing unit received by the message board front-end unit, a message that performs processing for searching and referring to registration data for the message storage The message board function providing system and a di reference processing unit is a gist.

  Further, as described in claim 2, in the message board function providing system according to claim 1, the topic / message registration processing unit sets the message storage firmware so that the number of topics allocated is flattened. Assignment and topic data and message data registration processing can be performed for the corresponding farm.

  In addition, as described in claim 3, receiving at least a topic registration request, a message posting request, and a message search request from each of a plurality of service providing units that provide a service on the Web, and the received one service A process of registering topic data and message data in the message storage in response to a request from the providing unit, and a process of searching and referring to the registered data in the message storage in response to the received request from another service providing unit And a message board function providing method including a step of returning a processing result as a response to the service providing unit.

  In the message board function providing system of the present invention, the message board function can be easily realized on various service pages, and the message board of each service is used without being conscious of the service currently used. be able to.

It is a figure which shows the structural example of the system concerning one Embodiment of this invention. It is a figure which shows the example of a data structure of message storage and replica storage. It is a figure which shows the data structure example of index storage. It is a figure which shows the hardware structural example of a composite service provision system. It is a sequence diagram (the 1) which shows the process example of embodiment. FIG. 10 is a first diagram illustrating an exemplary screen immediately after access; It is a figure which shows the example of a screen after completion of topic registration. It is a sequence diagram (the 2) which shows the process example of embodiment. It is a figure which shows the example of a screen after completion of message posting. It is a sequence diagram (the 3) which shows the process example of embodiment. It is a figure (the 2) which shows the example of a screen immediately after access. It is a figure which shows the example of a screen after a search.

  Hereinafter, preferred embodiments of the present invention will be described.

<Configuration>
FIG. 1 is a diagram showing a configuration example of a system according to an embodiment of the present invention.

  In FIG. 1, a user terminal 2A, 2B,..., Such as a PC (Personal Computer), a mobile phone, and a PDA (Personal Digital Assistants) operated by a user is connected to a network 1 such as the Internet. The user terminals 2A, 2B,... Have general browsers (Web browsers) 21A, 21B,. The browsers 21A, 21B,... Request / acquire / display page data and form data written in a language such as HTML (Hyper Text Markup Language) according to HTTP (Hyper Text Transfer Protocol), which is a standard protocol of the Internet. It has a function to transmit.

  On the other hand, a composite service providing system 3 that can be accessed from the browsers 21A, 21B,... Of user terminals 2A, 2B,.

  The composite service providing system 3 includes service providing units 31X, 31Y,... That provide individual services, and message board function providing units (messages) that provide message board functions to the service providing units 31X, 31Y,. Board platform) 32.

  The service providing units 31X, 31Y,... Function as page data generation units 311X, 311Y, .., page data transmission units 312X, 312Y,..., And user operation reception units 313X, 313Y,. , Message board posting units 314X, 314Y,... And message board reference units 315X, 315Y,. These functional units are realized by a computer program executed on hardware resources such as a CPU (Central Processing Unit), a ROM (Read Only Memory), and a RAM (Random Access Memory) of the computer constituting the composite service providing system 3. It is what is done. These functional units do not need to be arranged on a single computer, and may be distributed as necessary.

  The page data generation units 311X, 311Y,... Have a function of generating page data to be transmitted to the browsers 21A, 21B,.

  The page data transmitters 312X, 312Y,... Transmit the page data generated by the page data generators 311X, 311Y,... To the browsers 21A, 21B,. It has a function.

  The user operation receiving units 313X, 313Y,... Have a function of receiving operation contents such as mouse clicks and keyboard inputs from the browsers 21A, 21B,.

  The message board posting units 314X, 314Y,... Send the message board function providing unit 32 when the user operation content received by the user operation receiving units 313X, 313Y,. It has a function to request message board posting.

  The message board reference units 315X, 315Y,... Send the message board function providing unit 32 when the user operation content received by the user operation reception units 313X, 313Y,. It has a function to request message board reference.

  On the other hand, the message board function providing unit 32 includes, as function units, a message board front-end unit (interface unit) 321, a topic / message registration processing unit 322, an ID assignment processing unit 323, a replication processing unit 325, and an index creation processing unit 327. And a message reference processing unit 329. These functional units are realized by a computer program executed on hardware resources such as a CPU, a ROM, and a RAM of a computer constituting the composite service providing system 3. These functional units do not need to be arranged on a single computer, and may be distributed as necessary.

  The message board function providing unit 32 includes a message storage 324, a replica storage 326, and an index storage 328 as data storage. These data storages systematically hold predetermined data on a storage medium such as an HDD (Hard Disk Drive) in a computer constituting the composite service providing system 3.

  The message board front end unit 321 is a part that interfaces with the service providing units 31X, 31Y,..., Receives requests from the service providing units 31X, 31Y,. It has a function to return a response.

  The topic / message registration processing unit 322 has a function of performing processing for registering a topic or message in the message storage 324 in response to a request from the message board front end unit 321. That is, when a topic registration request or a message registration request is received, a new topic ID or message ID is acquired from the ID assignment processing unit 323 and registered in the message storage 324. When registering a topic in the message storage 324, registration is performed in the firmware indicated by the firmware ID included in the topic ID. When registering a message, the message is registered in the farm where the topic to which the message belongs is stored.

  The ID assignment processing unit 323 has a function of issuing a new topic ID or message ID in response to a request from the topic / message registration processing unit 322. The topic ID is obtained by adding a farm ID to serial numbers of all topics not related to the service. The farm ID is an identifier for identifying a farm, which is preferentially allocated from a farm having a small number of topic ID allocations. The ID assignment processing unit 323 internally manages the farm ID and the number of topics allocated. The message ID is a serial number of all messages not related to the service.

  The replication processing unit 325 has a function of copying the registration contents performed in the message storage 324 to the replica storage 326.

  The index creation processing unit 327 has a function of creating an index for searching topics and messages for registered contents that have been replicated. The created index is stored in the index storage 328.

  The message reference processing unit 329 has a function of acquiring an index from the index storage 328 in response to a request from the message board front end unit 321, executing a search, and acquiring a desired topic or message from the replica storage 326. Yes.

  FIG. 2 is a diagram illustrating an example of the data structure of the message storage 324 and the replica storage 326.

  The topic data includes items such as “topic ID”, “service type”, “topic title”, “topic text”, “creator ID”, “creator display name”, and “creation date / time”. “Topic ID” is an identifier that identifies a topic. “Service type” is an identifier for identifying a service. “Topic title” is a character string of a topic title. The “topic text” is a character string or the like that briefly explains the purpose of the topic. “Creator ID” is an identifier that identifies the creator of the topic. “Creator display name” is a character string of the name on the display of the creator of the topic. “Creation date” is a topic creation date (registration date).

  The message data includes items such as “message ID”, “affiliation topic ID”, “message title”, “message text”, “creator ID”, “creator display name”, and “creation date”. “Message ID” is an identifier for identifying a message. “Affiliation topic ID” is the topic ID of the topic to which the message belongs. “Message title” is a character string of the title of the message. The “message body” is a character string, an image, or the like that becomes a message body. “Creator ID” is an identifier that identifies the creator of the message. “Creator display name” is a character string of the name on the display of the creator of the message. “Creation date” is a message creation date (registration date).

  FIG. 3 shows an example of the data structure of the index storage 328, which includes a topic index and a message index. Both the topic index and the message index are searchable items “Creator ID”, “Creator Display Name”, “Topic ID”, “Message ID”, “Service Type”, “Topic Title / Topic Body”, and “Message Title”. For each “/ message body”, the sorted contents are associated with the corresponding topic or message storage address.

  FIG. 4 is a diagram illustrating a hardware configuration example of the composite service providing system 3.

  4, the composite service providing system 3 is connected to a CPU 3002, ROM 3003, RAM 3004, NVRAM (Non-Volatile Random Access Memory) 3005, I / F (Interface) 3006, and I / F 3006 connected to a system bus 3001. Also provided are an I / O (Input / Output Device) 3007 such as a keyboard, mouse, monitor, CD / DVD (Compact Disk / Digital Versatile Disk) drive, HDD 3008, NIC (Network Interface Card) 3009, and the like. M is a medium (recording medium) such as a CD / DVD in which a program or data is stored.

<Operation>
FIG. 5 is a sequence diagram showing a processing example of the above-described embodiment, and shows a processing example when the user instructs topic creation (topic registration).

  In FIG. 5, when the user of the user terminal 2A tries to browse a page of a service (for example, “baby” service) provided by the service providing unit 31X of the composite service providing system 3 from the browser 21A, the service providing unit is displayed from the browser 21A. A page request is transmitted to the 31X page data generation unit 311X (step S101). This is performed by directly inputting a URL (Uniform Resource Locator) of the service providing unit 31X or pressing a link button to the service providing unit 31X displayed on another page in the browser 21A. The page request is made by transmitting a message including a GET method according to HTTP, which is a standard protocol of the Internet, a request URI (Uniform Resource Identifier), and the like from the browser 21A to the page data generation unit 311X.

  The page data generation unit 311X that has received the page request generates page data to be provided to the browser 21A depending on whether the previously stored page data is acquired or the page data is dynamically generated (step S102). At this time, a screen area in which a user operation for the message function provided by the message board function providing unit 32 can be performed is included in the page data.

  The page data generation unit 311X transmits the generated page data to the page data transmission unit 312X (step S103). Since the communication between the page data generation unit 311X and the page data transmission unit 312X is communication within the service providing unit 31X, it can be in any format. The page data transmission unit 312X that has received the page data transmits the page data to the browser 21A (step S104). The page data is transmitted from the page data transmission unit 312X to the browser 21A according to an HTTP response or the like.

  The browser 21A that has received the page data displays a page screen (step S105). FIG. 6 shows an example of a page screen displayed on the browser 21A. Here, it is assumed that the service providing unit 31X provides the “baby” service. In this page screen, in addition to the contents of the normal service “baby”, a screen area is provided in which a user operation for the message function can be performed. In this screen area, buttons such as “search”, “create topic”, and “post a message” are provided.

  Returning to FIG. 5, when the user of the user terminal 2A performs a topic setting instruction operation from the page screen displayed on the browser 21A (step S106), the operation content is transmitted from the browser 21A to the user operation receiving unit 313X of the service providing unit 31X. It is transmitted (step S107). The operation content is transmitted from the browser 21A to the user operation reception unit 313X as data such as HTML added to the HTTP POST method or PUT method, or as a parameter added to the GET method. For example, a topic creation instruction is performed by pressing a “create topic” button in FIG. 6 and then inputting a topic title and a topic text and then pressing a confirmation button or the like.

  Returning to FIG. 5, the user operation receiving unit 313X that has received the operation content transmits the operation content to the message board posting unit 314X (step S108). Since the communication between the user operation receiving unit 313X and the message board posting unit 314X is communication within the service providing unit 31X, it can be in any format.

  The message board posting unit 314X that has received the operation content transmits a topic registration request to the message board front end unit 321 of the message board function providing unit 32 (step S109). Since the communication between the message board posting unit 314X and the message board front end unit 321 is communication in the composite service providing system 3, it can be in any format.

  The message board front end unit 321 that has received the topic registration request transmits the topic registration request to the topic / message registration processing unit 322 (step S110). Since communication between the message board front end unit 321 and the topic / message registration processing unit 322 is communication within the message board function providing unit 32, it can be in any format.

  The topic / message registration processing unit 322 that has received the topic registration request communicates with the ID assignment processing unit 323 to acquire the topic ID (step S111). Since communication between the topic / message registration processing unit 322 and the ID assignment processing unit 323 is communication within the message board function providing unit 32, it can be in any format.

  Next, the topic / message registration processing unit 322 registers the topic data in the farm (for example, the farm 324i) in the message storage 324 indicated by the firm ID included in the topic ID (step S112). The topic / message registration processing unit 322 notifies the replication processing unit 325 of the completion of topic data registration. Since communication between the topic / message registration processing unit 322 and the replication processing unit 325 is communication within the message board function providing unit 32, it can be in any format.

  The replication processing unit 325 acquires the registration contents performed in the message storage 324 by the topic / message registration processing unit 322, and registers a copy in the replica storage 326 as a replication process (step S113). The replication processing unit 325 notifies the completion of replication to the index creation processing unit 327. Since the communication between the replication processing unit 325 and the index creation processing unit 327 is communication within the message board function providing unit 32, it can be in any format.

  The index creation processing unit 327 creates a search index based on the registered content that has been replicated by the replication processing unit 325 and registers it in the index storage 328 (step S114). Completion of index creation by the index creation processing unit 327 is performed by the message board front-end unit from the index creation processing unit 327 via the replication processing unit 325 and the topic / message registration processing unit 322 or directly from the index creation processing unit 327. 321 is transmitted (step S115).

  Next, the message board front end unit 321 transmits a topic acquisition request for the topic for which registration has been completed to the message reference processing unit 329 (step S116). Since the communication between the message board front end unit 321 and the message reference processing unit 329 is communication within the message board function providing unit 32, it can be in any format.

  The message reference processing unit 329 that has received the topic acquisition request acquires an index from the index storage 328 (step S117), performs a search based on the acquired index, and acquires an address where desired topic data is registered ( Step S118).

  Then, the message reference processing unit 329 refers to the topic data from the replica storage 326 based on the acquired address (step S119), and transmits the topic data to the message board front end unit 321 (step S120).

  The message board front end unit 321 transmits the topic data to the message board posting unit 314X of the service providing unit 31X (step S121), and the message board posting unit 314X transmits the topic data to the page data generation unit 311X (step S122).

  The page data generation unit 311X that has received the topic data generates page data based on the topic data (step S123), and transmits the generated page data to the page data transmission unit 312X (step S124).

  The page data transmission unit 312X that has received the page data transmits the page data to the browser 21A (step S125).

  The browser 21A that has received the page data displays a page screen (step S126). FIG. 7 shows an example of the page screen of the browser 21A. Under the buttons such as “Search”, “Create topic”, “Post message”, etc., the topic title “Would you like to speak casually? "And the topic text" Would you like to speak casually? Anything is fine ... "is displayed.

  FIG. 8 is a sequence diagram showing another processing example of the above-described embodiment, and is a processing example when the user instructs message posting.

  In FIG. 8, when the user of the user terminal 2A operates a message posting instruction from the page screen displayed on the browser 21A (step S131), the operation content is transmitted from the browser 21A to the user operation receiving unit 313X of the service providing unit 31X. (Step S132). The message posting instruction is performed, for example, by pressing the “post message” button in FIG. 7 and then pressing the confirmation button or the like after inputting the message title and message body. The topic to which the message is posted may be the topic currently displayed, or may be selected when posting the message.

  Returning to FIG. 8, the user operation receiving unit 313X that has received the operation content transmits the operation content to the message board posting unit 314X (step S133).

  The message board posting unit 314X that has received the operation content transmits a message posting request to the message board front end unit 321 of the message board function providing unit 32 (step S134). The message posting request includes “affiliation topic ID”, “message title”, “message body”, “creator ID”, “creator display name”, and the like.

  The message board front end unit 321 that has received the message posting request transmits the message posting request to the topic / message registration processing unit 322 (step S135).

  The topic / message registration processing unit 322 that has received the message posting request communicates with the ID assignment processing unit 323 to acquire the message ID (step S136).

  Next, the topic / message registration processing unit 322 registers the message data in the firm (for example, the farm 324i) in the message storage 324 indicated by the firm ID included in the affiliated topic ID (step S137). The topic / message registration processing unit 322 notifies the replication processing unit 325 that message data registration has been completed.

  The replication processing unit 325 acquires the registration contents performed in the message storage 324 by the topic / message registration processing unit 322, and registers a copy in the replica storage 326 as a replication process (step S138). The replication processing unit 325 notifies the completion of replication to the index creation processing unit 327.

  The index creation processing unit 327 creates a search index based on the registration content that has been replicated by the replication processing unit 325 and registers it in the index storage 328 (step S139). Completion of index creation by the index creation processing unit 327 is performed by the message board front-end unit from the index creation processing unit 327 via the replication processing unit 325 and the topic / message registration processing unit 322 or directly from the index creation processing unit 327. 321 (step S140).

  Next, the message board front end unit 321 transmits a message acquisition request for the topic for which registration has been completed to the message reference processing unit 329 (step S141).

  The message reference processing unit 329 that has received the message acquisition request acquires an index from the index storage 328 (step S142), performs a search based on the acquired index, and acquires an address where desired message data is registered ( Step S143).

  Then, the message reference processing unit 329 refers to the topic data and message data from the replica storage 326 based on the acquired address (step S144), and transmits the topic data and message data to the message board front end unit 321 (step S145). ).

  The message board front end unit 321 transmits the topic data and the message data to the message board posting unit 314X of the service providing unit 31X (step S146), and the message board posting unit 314X transmits the topic data and the message data to the page data generation unit 311X. (Step S147).

  The page data generation unit 311X that has received the topic data and the message data generates page data based on the topic data and the message data (step S148), and transmits the generated page data to the page data transmission unit 312X (step S149). .

  The page data transmission unit 312X that has received the page data transmits the page data to the browser 21A (step S150).

  The browser 21A that has received the page data displays a page screen (step S151). FIG. 9 shows an example of the page screen of the browser 21A. Under the buttons such as “search”, “create topic”, and “post message”, the topic title “Would you like to speak casually? "And the topic text" Would you like to speak casually? Anything is fine ... "followed by the message text" Self introduction ... "is displayed.

  FIG. 10 is a sequence diagram showing another processing example of the above-described embodiment, and shows a processing example when the user refers to a message by instructing a message search.

  In FIG. 10, when the user of the user terminal 2B tries to browse a page of a service (for example, “shopping” service) provided by the service providing unit 31Y of the composite service providing system 3 from the browser 21B, the service providing unit is displayed from the browser 21B. A page request is transmitted to the page data generation unit 311Y of 31Y (step S201). This is performed by directly inputting the URL of the service providing unit 31Y in the browser 21B or pressing a link button to the service providing unit 31Y displayed on another page. The page request is made by transmitting a message including a GET method according to HTTP, which is a standard protocol of the Internet, a request URI, and the like from the browser 21B to the page data generating unit 311Y.

  The page data generation unit 311Y that has received the page request generates page data to be provided to the browser 21B depending on whether to acquire previously stored page data or to dynamically generate page data (step S202). At this time, a screen area in which a user operation for the message function provided by the message board function providing unit 32 can be performed is included in the page data.

  The page data generation unit 311Y transmits the generated page data to the page data transmission unit 312Y (step S203). Since the communication between the page data generation unit 311Y and the page data transmission unit 312Y is communication within the service providing unit 31Y, it can be in any format. The page data transmission unit 312Y that has received the page data transmits the page data to the browser 21B (step S204). The page data is transmitted from the page data transmission unit 312Y to the browser 21B according to an HTTP response or the like.

  The browser 21B that has received the page data displays a page screen (step S205). FIG. 11 shows an example of a page screen displayed on the browser 21B. Here, it is assumed that the service providing unit 31Y provides a “shopping” service. In this page screen, in addition to the contents of the normal service “shopping”, a screen area in which a user operation for the message function can be performed is provided. In this screen area, buttons such as “search”, “create topic”, and “post a message” are provided.

  Returning to FIG. 10, when the user of the user terminal 2B performs a message search instruction operation from the page screen displayed on the browser 21B (step S206), the operation content is displayed from the browser 21B to the user operation receiving unit 313Y of the service providing unit 31Y. It is transmitted (step S207). The operation content is transmitted from the browser 21B to the user operation reception unit 313Y as a parameter added to data such as HTML added to the HTTP POST method or PUT method or the GET method. For example, the topic search instruction is operated by selecting a bulletin board target from the leftmost slot among the slots on the left side of the “search” button in FIG. 11 and inputting a desired keyword in the next slot. This is done by pressing the "" button. The bulletin board target to be selected from the leftmost slot includes services such as “baby” and “video” that indicate services, and more detailed targets (for example, “pregnancy, childbirth”, “childcare, Osewa "etc.).

  Returning to FIG. 10, the user operation reception unit 313Y that has received the operation content transmits the operation content to the message board reference unit 315Y (step S208). Since the communication between the user operation receiving unit 313Y and the message board reference unit 315Y is communication within the service providing unit 31Y, it can be in any format.

  The message board reference unit 315Y that has received the operation content transmits a message search request to the message board front end unit 321 of the message board function providing unit 32 (step S209). Since communication between the message board reference unit 315Y and the message board front end unit 321 is communication in the composite service providing system 3, it can be in any format.

  The message board front end unit 321 that has received the message search request transmits the message search request to the message reference processing unit 329 (step S210).

  The message reference processing unit 329 that has received the message search request acquires an index from the index storage 328 (step S211), performs a search based on the acquired index, and acquires an address where desired message data is registered ( Step S212).

  Then, the message reference processing unit 329 refers to the topic data and message data from the replica storage 326 based on the acquired address (step S213), and transmits the topic data and message data to the message board front end unit 321 (step S214). ).

  The message board front end unit 321 transmits the topic data and message data to the message board reference unit 315Y of the service providing unit 31Y (step S215), and the message board reference unit 315Y transmits the topic data and message data to the page data generation unit 311Y. (Step S216).

  The page data generation unit 311Y that has received the topic data and the message data generates page data based on the topic data and the message data (step S217), and transmits the generated page data to the page data transmission unit 312Y (step S218). .

  The page data transmission unit 312Y that has received the page data transmits the page data to the browser 21B (step S219).

  The browser 21B that has received the page data displays a page screen (step S220). FIG. 12 shows an example of the page screen of the browser 21B. The contents of the message board of the “shopping” service are displayed under buttons such as “search”, “create topic”, and “post message”. The topic title “Would you like to speak casually ...” and the topic text “Would you like to speak casually? Show.

<Summary>
As described above, according to the present embodiment, the message board function can be easily realized on the individual service pages in the service providing units 31X, 31Y,... By the function provided by the message board function providing unit 32. There is an advantage that the message board of each service can be used without being conscious of the service currently used.

  The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

DESCRIPTION OF SYMBOLS 1 Network 2A, 2B User terminal 21A, 21B Browser 3 Complex service provision system 31X, 31Y Service provision part 311X, 311Y Page data generation part 312X, 312Y Page data transmission part 313X, 313Y User operation reception part 314X, 314Y Message board contribution part 315X, 315Y Message board reference section 32 Message board function providing section 321 Message board front end section 322 Topic / message registration processing section 323 ID assignment processing section 324 Message storage 324i farm 325 Replication processing section 326 Replica storage 326i farm 327 Index creation processing section 328 Index storage 329 Message reference processing unit

Claims (3)

A message board front-end unit that receives at least a topic registration request, a message posting request, and a message search request from each of a plurality of service providing units that provide services on the Web, and returns a processing result as a response;
A topic / message registration processing unit for processing topic data and message data for message storage in response to a request from the one service providing unit received by the message board front end unit;
A message board function provided, comprising: a message reference processing unit for searching and referring to registration data for message storage in response to a request from another service providing unit received by the message board front end unit system. In the message board function providing system according to claim 1,
The topic / message registration processing unit allocates the message storage firmware so that the number of allocated topics is flattened, and performs topic data and message data registration processing for the corresponding firmware. Board function providing system. Receiving at least a topic registration request, a message posting request, and a message search request from each of a plurality of service providing units that provide services on the Web;
In response to the received request from one service providing unit, a process of registering topic data and message data for message storage;
In response to a request from another service providing unit received, a process of searching and referring to registration data for the message storage;
A message board function providing method comprising: a step of returning a processing result as a response to the service providing unit.

Images