JP2011123820A - Information processor, information processing method and computer program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable schedule data registered in an inhouse private scheduler which is not disclosed from the outside and which is to be confirmed from a network environment, incapable of being connected to the private scheduler. <P>SOLUTION: A private scheduler and a popularly public scheduler for performing synchronous processing, when the private scheduler changes are associated with each other. Data composition of data to be transmitted in registering schedule information in the private scheduler and data composition of data to be transmitted in registering the schedule information in the public scheduler are stored. When schedule registration data is transmitted to the private scheduler, the schedule information acquired from the registration data and transmission data to the public scheduler is created, and is transmitted to the public scheduler. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a communication control method for registering information registered in a certain web electronic schedule service in another web electronic schedule service associated with the web electronic schedule service.

  With the development of network technology, it is possible to share information very easily and efficiently. In organizations such as companies, schedule management using groupware or an intranet system is widely performed in order to manage and share information such as conference schedules and business trip schedules. By using these, schedule management and sharing can be performed easily. However, as a security measure against information leakage, etc., it can be applied to groupware and intranet systems set in computer networks in organizations such as companies. In general, a firewall or the like prevents direct connection from the external Internet.

  Of course, there is also a demand for confirming the schedule via the Internet from a business trip destination or a place to go. In order to respond to such a request, it is necessary to open a server that provides a web electronic schedule service connected to a computer network in the organization to the outside. For this purpose, for example, a device such as a reverse proxy device is required. It becomes. For this reason, the cost and management load associated with the operation are increased, and the server is disclosed to the outside, which may increase the risk of information leakage.

  On the other hand, there are many web electronic schedule services published on the Internet. There are paid and free services, but any service can be easily used with a web browser application if it is connected to the Internet. In other words, it is convenient because it can be used from a computer network in an organization such as a company, as long as the computer is connected to the Internet, whether on a business trip or on the go. However, unlike an electronic schedule service in which data is managed in a company, a schedule must be registered in an external server, which causes a problem of risk of information leakage. Also, unlike the electronic schedule service systematically operated within the company, the organization-specific organization information is not managed, so only the web electronic schedule service published on the Internet can share information between groups within the company. It is difficult to use for such purposes.

  Patent Document 1 discloses an invention in which a user's schedule data managed by different schedule registration devices is synchronized using electronic mail. In the present invention, information is exchanged between two schedule registration apparatuses having different management systems by an e-mail created based on a unified rule, so that the schedule data registered in one schedule registration apparatus is transferred to the other schedule. It is possible to register with a registration device.

JP 2003-256623 A

  However, many service providers that provide electronic schedule services perform data operations such as adding, deleting, and changing schedule data according to their own rules, and multiple service providers are based on uniform rules. I'm not going. Therefore, the schedule data managed by the schedule management system used in the company and the schedule data for the web electronic schedule service currently widely used are synchronized by the technique disclosed in Patent Document 1. It is not realistic to do.

  Furthermore, the invention disclosed in Patent Document 1 is limited to sharing schedule data, and no consideration is given to information leakage due to schedule data registered in an external server that provides a schedule service.

  Therefore, the present invention is registered even between schedule servers that do not have a common data operation method, such as a server device used in an in-house schedule management system and an external server that provides a schedule service. It is a first object to enable synchronization processing of scheduled data.

  In addition to the first object, the present invention further provides information when registering information registered in an internal schedule server for synchronization processing of schedule data with an external server that provides a web electronic schedule service. A second object is to make it possible to reduce the risk of leakage.

In order to achieve the first object, the information processing apparatus of the present invention has the following configuration. That is,
An information processing apparatus capable of communicating with an HTTP server that provides a schedule management service using an HTTP protocol,
First identification information for identifying the HTTP server, and a first HTTP server that is an HTTP server installed in an internal network, or an HTTP server installed in an external network First storage means for storing service management information, including second specifying information for specifying which of the two HTTP servers, and at least the first HTTP server stored in the first storage means For the first definition information defining the structure of transmission data transmitted to the first HTTP server, and at least the second HTTP server stored in the first storage means, Second storage means for storing second definition information defining a structure of transmission data transmitted to the second HTTP server When,
First determination means for determining whether transmission data generated by the browser application and transmitted to the external terminal is transmission data for any of the first HTTP servers stored in the first storage means. When,
When the first determination means determines that the data is transmission data to the first HTTP server, it is transmitted to the first HTTP server according to the structure of transmission data defined by the first definition information. First acquisition means for acquiring data contents from the transmitted data;
Generating means for generating transmission data to be transmitted to the second HTTP server according to the data content acquired by the first acquisition means and the second definition information;
Transmitting means for transmitting the transmission data generated by the generating means to the second HTTP server;
It is characterized by providing.

In order to achieve the second object, the information processing apparatus of the present invention further comprises the following configuration. That is,
Of the character string information included in the transmission data transmitted to the first HTTP server, the character string that is subjected to character string conversion when the transmission data transmitted to the second HTTP server is created by the generating means And a fifth storage means for storing the pre-conversion character string and the post-conversion character string that is the post-conversion character string in association with each other,
The generation unit includes a character string that matches the pre-conversion character string stored in the fifth storage unit in the data content of the data transmitted to the first HTTP server acquired by the first acquisition unit. In this case, transmission data to be transmitted to the second HTTP server is generated using the post-conversion character string associated with the pre-conversion character string.

In order to achieve the first object, the information processing method of the present invention has the following configuration. That is,
First identification information for identifying an HTTP server and a first HTTP server that is an HTTP server installed in the internal network or a second HTTP server installed in an external network First storage means for storing service management information including second specifying information for specifying which one of the HTTP servers, and at least the first HTTP server stored in the first storage means For the first definition information defining the structure of transmission data transmitted to the first HTTP server, and at least the second HTTP server stored in the first storage means, Second storage means for storing second definition information defining a structure of transmission data transmitted to the second HTTP server; The provided an information processing method performed by an information processing apparatus capable of communicating with the HTTP server which provides a schedule management service using the HTTP protocol,
First determination step of determining whether transmission data generated by a browser application and transmitted to an external terminal is transmission data for any of the first HTTP servers stored in the first storage unit When,
When it is determined in the first determination step that the data is transmission data to the first HTTP server, the data is transmitted to the first HTTP server according to the structure of transmission data defined by the first definition information. A first acquisition step of acquiring data content from the transmitted data;
A generation step of generating transmission data to be transmitted to the second HTTP server according to the data content acquired in the first acquisition step and the second definition information;
A transmission step of transmitting the transmission data generated by the generation means to the second HTTP server;
It is characterized by providing.

In order to achieve the second object, the information processing method of the present invention further comprises the following configuration. That is,
The information processing apparatus further creates a transmission data to be transmitted to the second HTTP server by the generation unit, out of character string information included in the transmission data transmitted to the first HTTP server. Third storage means for storing a pre-conversion character string that is a character string for character string conversion and a post-conversion character string that is a character string after the conversion in association with each other,
The generation step includes a character string that matches the pre-conversion character string stored in the third storage means in the data content of the data transmitted to the first HTTP server acquired in the first acquisition step. In this case, transmission data to be transmitted to the second HTTP server is generated using the post-conversion character string associated with the pre-conversion character string.

  According to the present invention, it becomes necessary for request information for data from a request information for an electronic schedule service installed in a computer network in an organization such as a company to a web electronic schedule service disclosed and provided on the external Internet. Since information is acquired, data for the external web electronic schedule service is generated according to the acquired information, and information of the external web electronic schedule service is updated, information on the internal electronic schedule service and the external web electronic schedule service can be easily Synchronization processing can be performed.

In addition, if a specific keyword appears when data is rewritten, the data is replaced according to a preset rule, reducing the leakage of information due to schedule data synchronization processing. It becomes possible to do.

It is a block diagram which shows an example of the information processing system structure of this invention. FIG. 2 is a block diagram illustrating an example of a hardware configuration of a client apparatus 101 in FIG. 1. FIG. 2 is a schematic diagram illustrating an example of a functional configuration of a client apparatus 101 in FIG. 1. 6 is a flowchart showing processing at the time of starting an extended function 112 installed in the client apparatus 101. 2 is a sequence diagram illustrating an example of communication and processing order among a web browser 111, an extended function 112, an internal HTTP server 102, and an external HTTP server 105. FIG. It is a schematic diagram which shows an example of the screen of the web browser 111. FIG. It is a schematic diagram which shows an example of the screen of the web browser 111. FIG. It is a flowchart which shows an example of the procedure of an external schedule service cooperation process. It is a flowchart which shows the detail of the event recording process of step S806 of FIG. It is a flowchart which shows the detail of the schedule addition / change process of step S809 of FIG. It is a flowchart which shows the detail of the schedule deletion process of step S811 of FIG. It is a flowchart which shows the detail of the external event search process of step S1008 of FIG. It is a flowchart which shows the detail of the event LIST acquisition process of step S1207 of FIG. It is a flowchart which shows an example of an external service synchronous process. It is a figure which shows an example of a structure of the input screen of schedule service definition information. It is a figure which shows an example of a structure of the input screen of request definition information. It is a figure which shows an example of a structure of the input screen of a rewriting rule. It is a figure which shows an example of a structure of a schedule service definition information table. It is a figure which shows an example of a structure of a request definition information table (internal schedule service). It is a figure which shows an example of a structure of a request definition information table (external schedule service). It is a figure which shows an example of a structure of a rewriting rule table. It is a figure which shows an example of a structure of a schedule event table.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a diagram illustrating an example of a system configuration according to an embodiment of the present invention. Note that the configurations of the various terminals shown in FIG. 1 are merely examples, and it goes without saying that there are various configuration examples depending on the purpose and application.

  As shown in FIG. 1, the intranet 100 of the information processing system according to the present embodiment includes client apparatuses 101-1 to 101-3 (hereinafter collectively referred to as the client apparatus 101) and an internal HTTP server 102. These terminals are connected via a local area network (LAN) 103 so that they can communicate with each other.

  Further, the client apparatus 101 is connected to the external HTTP servers 105-1 to 105-3 (hereinafter collectively referred to as the external HTTP server 105) via the wide area network 104 so as to be able to communicate with each other. In addition, a firewall device (not shown) is installed between the LAN 103 and the wide area network 104, and a communication control process according to a predetermined rule is performed.

  As shown in FIG. 1, each client device 101 includes a web browser application 111 (hereinafter referred to as a web browser 111) and an extended function application 112 (hereinafter referred to as a function extension) that is an application for extending the function of the web browser 111. 112) is installed. The client device 101 is connected to the internal HTTP server 102, the external HTTP server 105, and the like by the function of the web browser 111. Further, the extended function 112 monitors input / output of data by the web browser 111, specifies communication contents with the internal HTTP server, and performs various processes described later according to the communication contents.

  The internal HTTP server 102 is a server device for providing a web electronic schedule service (hereinafter referred to as “internal schedule service”) to a user who uses the client device 101, a meeting or the like in response to a request from the client device 101. Registration, modification, deletion, browsing process, etc.

  The external HTTP server 105 is a web server provided in a general service provider. Like the internal HTTP server, the external HTTP server 105 performs a conference or the like in response to a request from the client apparatus 101 accessed via the wide area network 104. Provides a schedule service (hereinafter referred to as an external schedule service) that performs schedule registration, correction, deletion, browsing processing, and the like. At this time, the HTTP request data according to the data structure of the HTTP request data defined by each external HTTP server 105 is transmitted from the client apparatus 101 to the external HTTP server 105. As an electronic schedule service provided on the Internet, for example, Google Calendar of Google Corporation in the United States is available.

  FIG. 2 is a block diagram illustrating an example of a hardware configuration of the client apparatus 101 illustrated in FIG.

  In FIG. 2, the CPU 201 comprehensively controls various devices and controllers connected to the system bus 204. Further, the ROM 203 or the external memory 211 has a BIOS (Basic Input / Output System) or an operating system program (hereinafter referred to as an OS) that is a control program of the CPU 201, and various types for the client device 101 to execute various processes. The program is stored.

  The RAM 202 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 loads programs and data necessary for execution of processing into the RAM 202 and executes the programs to realize various operations described below.

  An input controller (input C) 205 controls input from a pointing device such as a keyboard 209 or a mouse (not shown). A video controller (VC) 206 controls display on a display device such as the display device 210. The display device 210 is composed of, for example, a CRT, a liquid crystal display, or the like. These are for use by the administrator as needed. In addition, the CPU 201 enables display on the display device 210 by executing outline font rasterization processing on a display information area in the RAM 202, for example.

  The memory controller (MC) 207 is an adapter to a hard disk (HD) or floppy disk (registered trademark FD) or PCMCIA card slot for storing a boot program, OS, various applications, font data, user files, editing files, various data, and the like. Controls access to an external memory 211 such as a compact flash memory connected via the. The web browser 111 and the function extension 112 for realizing the present invention are stored in the external memory 211 and executed by the CPU 201 by being loaded into the RAM 202 as necessary. Definition information and various information tables used by the web browser 111 and the extended function 112 according to the present invention are stored in the external memory 211. A detailed description thereof will be described later.

  A communication I / F (interface) controller (communication I / FC) 208 is for connecting and communicating with an external device via a network such as the LAN 103 or the wide area network 104, and executes communication control processing in the network. . For example, Internet communication using TCP / IP is possible.

  FIG. 3 is a schematic diagram illustrating a functional configuration of the client apparatus 101. As shown in FIG. 3, the client apparatus 101 includes a schedule service definition information setting unit 311, a request definition information setting unit 312, a definition information management unit 310 including a rewrite rule setting unit 313, a schedule service request acquisition unit 321, a request analysis. External schedule service cooperation unit 320 including means 322, external request generation / transmission means 323, synchronization state confirmation means 331, internal / external schedule acquisition means 332, schedule difference analysis means 333, external including external request generation / transmission means 334 A schedule service synchronization unit 330 is provided.

  The schedule service definition information setting unit 311 accepts input of schedule service definition information such as an access destination of web electronic schedule service and authentication information (details will be described later with reference to FIGS. 15 and 18), and is set in the schedule service definition information table 341 ( Register, modify, delete, etc.)

  In order to accept input of schedule service definition information, the schedule service definition information setting unit 311 displays, for example, a schedule service definition information input screen 1500 as shown in FIG.

  FIG. 15 is a diagram illustrating an example of an input screen for schedule service definition information displayed on the display device 210 of the client device 101.

  In the input screen 1500 shown in FIG. 15, as the schedule service definition information, the name and URL indicating the schedule service to be accessed and whether an HTTP server providing the schedule service is installed in the intranet 100 (whether it is the internal HTTP server 102) ) Or “internal” or “external” location classification information indicating whether it is installed in the wide area network 104 such as the Internet (external HTTP server 105), or authentication information when using the schedule service. A control for accepting input of items such as a certain account name and password is prepared, and the client apparatus 101 accepts various data input via the input screen 1500 as schedule service definition information. That.

  In the figure, reference numeral 1501 denotes a schedule service selection field in which already registered schedule services are set to be selectable. When the user corrects or deletes already registered schedule service definition information, Select the schedule service to be deleted in this selection field. Reference numeral 1502 denotes a control for inputting and displaying the name of the schedule service. Reference numeral 1503 denotes a control for inputting and displaying a URL indicating an access destination of an HTTP server that provides a schedule service.

  Reference numeral 1504 denotes a radio button for setting the classification information (“internal” or “external”) of the location of the HTTP server that provides the schedule service. In the authentication information 1505, an account name input field 1505-1 and a password input field 1505-2 used when using the schedule service are set. An add button 1506 is used to add a new schedule service, an edit button 1507 is used to modify the contents of a registered schedule service, and a delete button 1508 is used to delete a registered schedule service. Button.

  The schedule service definition information received from the user via the input screen 1500 is registered in the schedule service definition information table 341 shown in FIG.

  FIG. 18 is a diagram showing an example of the schedule service definition information table 341 used in the present invention. As shown in FIG. 18, the schedule service definition information table 341 includes an ID 1801 for uniquely identifying the schedule service, and a service name 1802, URL 1803, internal or external corresponding to the schedule service specified by the ID. A set of a location 1804 indicating classification information, an account name 1805 used as authentication information when using the schedule service, and a password 1806 are recorded.

  For example, the schedule service with ID 1801 is “Office Schedule” for the service name 1802, “http://o-schedule.cgn.aaa.co.jp/s.cgi” for the URL 1803, “internal” for the location 1804, It can be understood that “username” is set in the account name 1805 and “password” is set in the password 1806.

  Returning to the description of FIG. The request definition information setting means 312 shown in FIG. 3 is a parameter that indicates the structure of HTTP request data for operating (adding / modifying / deleting) schedule data managed by the schedule service for each schedule service, and data contents. Information (details will be described later with reference to FIGS. 16 and 19) is received, and the received information is set in the request definition information table 342. In order to receive the request definition information, the request definition information setting unit 312 displays a request definition information input screen 1600 as shown in FIG.

  FIG. 16 is a diagram illustrating an example of an input screen for request definition information displayed on the display device 210 of the client device 101.

  The input screen 1600 shown in FIG. 16 includes, as request definition information, a service name indicating a service defined by the schedule service definition information setting unit, an URL, an action indicating an operation type, a condition for specifying the action, a request parameter And control to accept input of items such as correspondence between response data and event items, name of service to be synchronized, and whether to rewrite event contents during synchronization. Then, the request definition information input via the input screen 1600 is registered in the request definition information table 342 shown in FIG.

  In the figure, reference numeral 1601 denotes a control for selecting a schedule service for setting request definition information. Reference numeral 1602 denotes a display field for displaying the location of the HTTP server that provides the schedule service selected by the control 1601. The internal HTTP in the case of the internal HTTP server 102, and “external” in the case of the external HTTP server 105. Will be displayed.

  An add button 1603 is used to add new request definition information, an edit button 1604 is used to modify the contents of registered request definition information, and a delete button 1605 is used to delete already registered request definition information. Button.

  Reference numeral 1606 denotes a URL display field, which is a display field for displaying the URL of the HTTP server that provides the schedule service selected by the control 1601.

  Reference numeral 1607 denotes an action designation field, which is a control for designating a data operation for the schedule service. Reference numeral 1608 denotes a control for inputting / displaying a condition for specifying data communication of an HTTP request corresponding to the action designated in 1607. Reference numeral 1609 denotes a control for inputting and displaying event parameters in which values corresponding to various event items are set. Event items include, for example, start year, start month, start date, start time, start minute, end year, end month, end date, end time, end minute, scheduled subject, detailed contents, etc. This is a control for inputting information as to which parameter in the HTTP request the corresponding value is set.

  Reference numeral 1610 denotes a control for designating an external schedule service that performs synchronization processing with the schedule service when an internal schedule service is selected in the control 1601. Reference numeral 1611 denotes a check box for designating whether to perform data conversion according to a rewrite rule described later in the data synchronization processing to the external HTTP server 105. Reference numeral 1612 denotes a button used for causing the display device 210 to display an input screen (not shown) for inputting response data definition information received from the HTTP server after transmitting an HTTP request related to the action to the HTTP server. It is.

  19A and 19B are diagrams illustrating an example of a request definition information table used in the present invention. 19-1 and 19-2, the request definition information table 342 includes a schedule service ID 1902, an action 1903, a request condition 1904, a request parameter definition 1905, a response data definition 1906, and a process definition 1907 corresponding to each ID 1901. Is set.

  In the request ID 1901, identification information for uniquely identifying the request definition information is set. The service ID 1902 is set with a service ID for uniquely identifying the corresponding schedule service. In the action 1903, an operation requested to the schedule service is set. For example, ADD that is an operation for adding new schedule data, DELETE that requests deletion of a registered schedule, and the like are set.

  In the request parameter definition, it is set to which parameter variable of the HTTP request transmitted to the HTTP server the event items such as the start year, the start date, the end year, the end date, and the contents. For example, if the request ID in FIG. 19-1 is data of 1, this means that the start year is set to startyear, the start month is set to startmonth,... Yes.

  In response data 1906, as a result of the transmission of the HTTP request to the HTTP server, the data structure of the response data transmitted from the HTTP server is set. In the process definition 1907, the service ID of the external schedule service that is synchronized when the schedule information managed by the internal schedule service is changed, the execution action, and information on whether to rewrite the contents are set.

  FIG. 19A shows request definition information of an internal schedule service. For example, when the request ID 1901 is 1, the corresponding schedule service ID 1902 is 1 (the Office Schedule shown in FIG. 18), and the request condition 1903 is a URL. Matches http://o-schedule.cgn.aaa.co.jp, and the parameter value page == scheduleadd and _Submit == 'add' is set in the request parameter definition 1904. , Start month = startmanth,... Content = Detail, other = Other, “None” in the response data definition 1906, 2 synchronization service in the process definition 1907, ADD action as an execution action, and synchronous processing Is set to perform string conversion according to the rewrite rules.

  FIG. 19-2 shows request definition information of the external schedule service, and the same data as in the case of the internal schedule service is set. The request definition information 342 according to FIGS. 19A and 19B is used when the external schedule service cooperation unit 320 and the external schedule service synchronization processing unit 330 perform processing.

  Returning to the description of FIG. The rewrite rule setting unit 313 accepts input of a rewrite rule for a character string used when setting (registering / modifying, etc.) the schedule data specified by the request analysis unit 322, which will be described later, for another external schedule service, This is set in the rewrite rule table 343.

  The rewrite rule setting unit 313 displays, for example, a rewrite rule input screen 1700 as shown in FIG. 17 on the display device 210 of the client device 101 in order to accept the input of the rewrite rule.

  FIG. 17 is a diagram illustrating an example of a rewrite rule input screen displayed on the display device 210 of the client device 101.

  In the input screen 1700 shown in FIG. 17, an ID that uniquely indicates a rewrite rule as a rewrite rule, a keyword condition to be rewritten, a keyword inclusion condition, a rewrite character string that matches the condition, and a case that does not match the set rule Default control designation, and various controls for inputting a rewrite character string when rewriting is designated in the default processing. Then, the rewrite rule input via the input screen 1700 is registered in the rewrite rule table 343 shown in FIG.

  In the figure, reference numeral 1701 denotes a control for displaying a rule ID for uniquely identifying a rewrite rule. 1702 is a keyword condition input field, and 1703 is a keyword inclusion condition input field. When a keyword is included in what kind of keyword (keyword condition) and in what form, character string conversion is performed according to the rewrite rule. This is a control for inputting the condition (keyword inclusion condition) of whether or not to perform. Reference numeral 1704 denotes a control for inputting character string information used when setting a schedule service that matches the keyword condition and the keyword inclusion condition in the schedule service provided by the external HTTP server 105.

  FIG. 20 is a diagram showing an example of a rewrite rule table used in the present invention. As shown in FIG. 20, the rewrite rule table 343 records a set of a keyword (keyword condition) 2002, a condition (keyword inclusion condition) 2003, and a rewrite character string 2004 corresponding to each rule ID 2001. For example, in rule ID = 1, “confidential” is associated with the keyword, “includes” is included in the condition, and “***” is associated with the rewritten character string as a set.

  Returning to the description of FIG. The schedule service request acquisition unit 321 shown in FIG. 3 is set by the schedule service definition information setting unit 311 and the communication contents corresponding to the use of the internal schedule service from the web browser 111 according to the definition information registered in the schedule service definition information table 341. Is identified. Here, it is determined whether the request URL included in the HTTP request data matches the URL set in the request condition, and whether the parameter value set in the request condition is set in the HTTP request data. As a result, it is specified which schedule service definition information corresponds.

  The request analysis unit 322 includes a management ID of the schedule event information included in the communication for using the internal schedule service specified by the schedule service request acquisition unit 321, a start year, a start month, a start time,. Information such as contents is acquired according to the request definition information corresponding to the internal schedule service set in the request definition information table 342, and the acquired schedule event information is set in the schedule event table 344. The schedule event table will be described with reference to FIG.

  FIG. 21 is a diagram showing an example of a schedule event table used in the present invention. As shown in FIG. 21, the schedule event table includes internal / external, service ID, management ID, start year, start month, start date, start time, start minute, end year, end month, corresponding to each event ID. End date, end time, end minute, contents, and internal / external correspondence are associated as a set.

  The external request generation / transmission unit 323 is transmitted from the web browser 111 to the external HTTP server when the processing definition 1907 of the request definition information that matches the HTTP request data acquired by the schedule service request acquisition unit 321 is set. HTTP request data for schedule data operation for the external schedule service to be synchronized is acquired by the request analysis unit 322, and the schedule data set in the schedule event table 344 and the same action of the corresponding external schedule service HTTP request data for the external HTTP server 105 is generated and transmitted according to the request definition information. At that time, if event content rewriting is set, after performing character string conversion according to the rewriting rules set in the rewriting rule table, HTTP request data to be transmitted to the external HTTP server 105 is generated. Will do.

  The synchronization status confirmation unit 331 is registered by the user operating the client apparatus 101 with the schedule information of the user registered in the schedule service provided by the internal HTTP server 104 and the external schedule service to be synchronized. The input of the execution instruction of the synchronous processing with the data is received.

  The internal / external schedule acquisition unit 332 follows the information registered in the schedule service definition information table 341 and the request definition information table 342, and sends an event acquisition request (the action set in the request definition information table) to the internal schedule service and the external schedule service. Transmits a request corresponding to the request definition information of LIST), and registers the acquired event in the schedule event table 344.

  The schedule difference analysis means 333 extracts the difference between the schedule information set in the internal schedule service registered in the schedule event table 344 and the schedule information set in the external schedule service to be synchronized.

  The internal / external request generation / transmission means registers an event (difference event) that is registered only in the internal schedule service and not registered in the external schedule service in order to eliminate the difference extracted by the schedule difference analysis means 333. In order to register with the schedule service, HTTP request data is generated and transmitted to the external HTTP server 105. Specifically, HTTP request data is generated by the same method as the external request generation / transmission means 323 and is transmitted to the corresponding external HTTP server 105.

  When synchronous processing is performed by deleting a difference event, HTTP request data for requesting deletion of the difference event registered in the internal schedule service is generated and transmitted to the internal HTTP server 102. It will be. The creation of HTTP request data for the internal HTTP server 102 is performed in the same manner as when HTTP request data for the external schedule service is generated except that the request definition information of the internal schedule service is referred to.

  Next, processing for extending the function of the web browser 111, which is performed when the extended function 112 installed in the client apparatus 101 is started, will be described with reference to FIG. This process is a process performed by the CPU 201 of the client apparatus 101.

  First, the web browser 111 installed in the external memory 211 of the client device 101 is activated in accordance with a user instruction or the like, and the extended function 112 is also activated to perform initialization processing of the extended function 112 (step S401). ). Thereafter, event listener registration is performed to supplement the communication processing of the web browser 111 in order to monitor the communication content of the web browser 111 (step S402). And the extended function 112 can acquire the communication content transmitted / received between the web browser 111 and the internal HTTP server 102 through this event listener. An example of a web browser to which such an extended function can be added is FireFox.

  FIG. 5 is a sequence diagram illustrating an example of the order of communication and processing among the web browser 111, the extended function 112, the internal HTTP server 102, and the external HTTP server 105.

  When the web browser 111 is activated on the client device 101, the extended function 112 is also activated accordingly, and initialization processing is performed (step S501). This process corresponds to the process of step S401 in FIG. Thereafter, an event listener registration process for supplementing the communication content of the web browser is performed (step S502). This process corresponds to the process of step S402 in FIG.

  Thereafter, in order to start using the internal schedule service, authentication information for identifying the user is transmitted to the internal HTTP server 102 (login: step S503). Usually, a user account name and a password are used. When the user can be specified by the authentication process (which may be performed by another authentication device) by the internal HTTP server 102, a screen as shown in FIG. 6 is displayed on the display device 210 of the client device 101. The internal HTTP server 102 transmits screen information including the user's schedule information to the client apparatus 101 (step S504). The client apparatus 101 that has acquired the screen information displays a screen as shown in FIG. 6 based on the screen information.

  FIG. 6 is a schematic diagram illustrating an example of a screen of the web browser 111 displayed on the display device 210 of the client device 101 after the authentication process in the internal HTTP server 102. In the calendar format as shown in the figure, the screen allows you to check the schedule information that has already been registered. Then, by clicking a link to the schedule information (601 in the figure), HTTP request data for event acquisition is transmitted to the internal HTTP server 102 (step S505). The extended function 112 supplements the HTTP request data and analyzes the HTTP request data (step S506). Thereafter, response data from the internal HTTP server 102 to the HTTP request data is transmitted to the internal HTTP server 102 (more specifically, the web browser 111 of the internal HTTP server 102) (step S507). Supplements the response data (step S508), analyzes the event information, and records the information in the schedule event table.

  As shown in FIG. 7, the web browser 111 that has received the response data sends detailed information such as start date / time / date, end date / time / date, schedule content, location, and the like, which are detailed information of the event, to the web browser 111. In the display area. When the user clicks on 602 (link for which no schedule is registered) in FIG. 6, only the start date and the end date are displayed as initial data in FIG.

  When the client device 101 in which the web browser 111 is executed receives a request for operation of schedule information such as addition of schedule information, change of schedule information, deletion of schedule information based on a user operation, in response to the request, The web browser 111 generates HTTP request data for the operation content (addition, change, deletion, etc.) and transmits it to the internal HTTP server 102 (step S509). The extended function 112 acquires and analyzes the HTTP request data, and registers the analysis result in the schedule event table 344 (step S510).

  Then, response data for the HTTP request data transmitted to the internal HTTP server 102 in the process of step S509 is accepted (step S511). If this request data is response data indicating successful processing, the extended function 112 sets an external schedule service that synchronizes with the internal schedule service that has issued an operation instruction such as addition, change, or deletion of schedule information. Account 1805 of the schedule service definition information of the external schedule service corresponding to the case (if the synchronization service is set in the process definition 1907 of the request definition information corresponding to the action corresponding to the internal schedule service and the operation content) Then, a request for login processing to the external schedule service is made using the information set in the password 1806 (step S512). When the response data indicating that the login is successful is acquired as a result of the login processing request (step S513), the extended function 112 schedules the external schedule service according to the operation content for the internal schedule service registered in the schedule event table 342. In order to operate the information, HTTP request data for the external schedule service is generated (step S514), and the HTTP request data is transmitted to the external HTTP server 105 (step S515). In step S514, when creating the HTTP request data for the external schedule service, the extension function 112 creates HTTP request data according to the request definition information of the external schedule service.

  Next, an example of the procedure of the external schedule service cooperation process performed by the CPU 201 of the client apparatus 101 will be described with reference to FIG. This process is performed by the external schedule service cooperation unit 320. This function is provided by the extended function 112. At the time when the processing according to FIG. 8 is started, the client apparatus 101 has already accessed the web page provided by the internal schedule service, and is in a state where instructions such as acquisition, addition, modification, and deletion of events are possible.

  First, the CPU 201 supplements HTTP request data generated by the web browser 111 and transmitted to the internal HTTP server 102 (step S801). When the HTTP request data is supplemented in step S801, the schedule service definition information table 341 is searched to determine whether the request URL set in the HTTP request data matches any of the schedule service definition information URLs 1803. Thus, it is determined whether the HTTP communication is for the schedule service (step S803).

  If the CPU 201 determines that the HTTP communication is for the schedule service (YES in step S803), the process proceeds to step S804. If the CPU 201 determines that it is not for the schedule service (NO in step S803), the process is performed. The process proceeds to step S801.

  When it is determined YES in the determination process in step S803, the CPU 201 performs an analysis process on the acquired HTTP request data (step S804). In that case, the HTTP request data acquired in step S801 is further decomposed into constituent elements (elements to be referred to in the subsequent processing). That is, for example, the request parameter value is decomposed into tokens using an ampersand symbol as a delimiter, and each token is further decomposed into name-value pairs using = as a delimiter. If there is external transmission data, the request body content is also analyzed based on the content of the Content-Type header, Content-Length, or Transfer-Encoding header, and decomposed into components.

  After that, based on the constituent elements of the HTTP request data analyzed in step S804, the HTTP request data matches the GET action condition of the internal schedule service specified in step S802 set in the request definition information table 342. It is determined whether or not there is (step S805). If the CPU 201 determines YES in step S805, the process proceeds to step S806 to perform event recording processing (details are shown in FIG. 9). On the other hand, if it is determined that the GET action condition is not met (NO in step S805), the process proceeds to the next step S807.

  In step S807, the CPU 201 determines whether the HTTP request data matches the ADD action condition of the internal schedule service. If the CPU 201 determines YES in step S807, the process proceeds to step S809, and schedule addition / change processing (details are shown in FIG. 10) is performed. On the other hand, if it is determined that the ADD action condition is not met (NO in step S807), the process proceeds to the next step S808.

  In step S808, the CPU 201 determines whether the HTTP request data matches the EDIT action condition of the internal schedule service. If the CPU 201 determines YES in step S808, the process proceeds to step S809, and schedule addition / change processing (details are shown in FIG. 10) is performed. On the other hand, if it is determined that the EDIT action condition is not met (NO in step S808), the process proceeds to the next step S810.

  In step S810, the CPU 201 determines whether or not the HTTP request data matches the DELETE action condition of the internal schedule service. If the CPU 201 determines YES in step S810, the process proceeds to step S811, and schedule deletion processing (details are shown in FIG. 11) is performed. On the other hand, if it is determined that the EDIT action condition is not met (NO in step S810), the process proceeds to the next step S812.

  The above processing is repeated until it is determined that the web browser 111 has been terminated (YES in step S812). The above is an example of the procedure of the external schedule service cooperation process performed by the CPU 201 of the client apparatus 101.

  Next, details of the event recording process in step S806 in FIG. 8 will be described with reference to FIG.

  FIG. 9 is a flowchart illustrating an example of an event recording process performed by the CPU 201 of the client apparatus 101. First, in step S901, the CPU 201 extracts a management ID (for example, sid = E111) from the HTTP request data components obtained as a result of the HTTP request data analysis processing in step S804 in FIG. Goes to step S902.

  Thereafter, the response data is kept waiting until it is determined that the response data for the HTTP request data is received (YES in step S903) (step S902).

  When response data is received from the internal HTTP server 102 (YES in step S903), request definition information corresponding to the GET action of the internal schedule service is acquired (step S904).

  After that, the CPU 201 decomposes the response data indicating the event content determined to have been acquired in step S903 into HTML DOM elements, and starts and ends the schedule event start date / month date and time according to the request definition information acquired in step S904. Get data corresponding to schedule event items such as minutes and schedule contents. For example, when the start year of the schedule event is set in the HTML text display area “id = startyear”, the value of the DOM element is associated with the start year of the schedule event item. Depending on the schedule service, the start year may be set as a partial character string such as “YYYY / MM / DD” in one DOM element. In such a case, the part of the corresponding DOM element is set. The response data definition of the response data definition information may be set so that a column (for example, two characters from the first digit) can be acquired as the start year.

  Next, in step S906, it is searched whether there is schedule event data having the same contents in the schedule event table 344 (shown in FIG. 21) (step S906). As a result of the search, if it is determined that there is no identical schedule event data, that is, it is a new schedule event, the process proceeds to step S908, the schedule event data is added to the schedule event table 344, and this process is performed. finish. If it is determined NO in step S907 (not a new schedule event), the process ends without performing the schedule event addition process in step S908. The above is the detailed description of the event recording process in step S806 in FIG.

  Next, details of the schedule addition / change process in step S809 of FIG. 8 will be described with reference to FIG.

  FIG. 10 is a flowchart illustrating details of the schedule addition / change process performed by the CPU 201 of the client apparatus 101. First, in step S1001, the CPU 201 extracts a management ID (for example, sid = E111) from the HTTP request data components obtained as a result of the HTTP request data analysis processing in step S804 in FIG. The process proceeds to step S1002.

  Thereafter, the response data wait state is continued until it is determined that the response data for the HTTP request data is received (YES in step S1003) (step S1002).

  When response data indicating the normal end of the schedule operation is received from the internal HTTP server 102 (YES in step S1003), the request definition information corresponding to the action (ADD or EDIT) corresponding to the internal schedule service is acquired, and the request definition information In accordance with the request parameter definition 1905, the schedule event data corresponding to the schedule event items such as the start date, the end date, the end date, the schedule content, and the like of the schedule event data from the constituent elements of the HTTP request data analyzed in step S804 of FIG. Data is acquired (step S1004). Depending on the schedule service, the start year may be specified as a partial character string such as “YYYY / MM / DD” in one request parameter value. In such a case, a request parameter definition condition may be set so that a substring (for example, two characters from the first digit) of the corresponding parameter value can be acquired as a start year.

  Thereafter, it is searched whether the schedule event data generated in step S1004 is already registered in the schedule event table (step S1005). As a result of the search, if it is determined that the same schedule event table is not registered, that is, it is new schedule event data (YES in step S1006), the process proceeds to step S1007, and the schedule event data is transferred to the schedule event. Register in the table 344.

  After the process of step S1007 is completed or after NO is determined in step S1006, the CPU 201 advances the process to step S1008 and performs a corresponding external event search process. Details of this processing will be described later with reference to FIG.

  After completion of the corresponding external event search process in step S1008, the CPU 201 determines whether schedule event data corresponding to the schedule event data is registered in the external schedule service (whether there is a corresponding event) (step S1009). If it is determined in the determination process of step S1008 that there is a corresponding event (YES in step S1009), the process proceeds to step S1010, and the request definition information of the EDIT action is acquired from the request definition information of the external schedule service to be synchronized. . On the other hand, if NO is determined in the determination process of step S1009 (no corresponding event), the process proceeds to step S1011 to acquire the request definition information of the ADD action among the request definition information of the external schedule service to be synchronized.

  After that, when it is set to rewrite the schedule contents, a character string conversion process according to the rewrite rule is performed (step S1012). If it is set not to perform the rewrite process according to the rewrite rule, this process is not performed.

  After the process of step S1012, the external HTTP request data used for the operation of the schedule information of the external schedule service is generated according to the request condition of the request definition information acquired in step S1010 or S1011 (step S1013), and the external schedule service Is transmitted to the external HTTP server that provides (step S1014).

  After that, when response data indicating successful processing is acquired from the external HTTP server 105 (YES in step S1015: success), the process proceeds to step S1016, and the fact that the HTTP request data is transmitted to the external schedule service in step S1014 is external. A schedule event registered in the schedule service is added to or updated in the event table (update corresponding entry). The above is the details of the schedule addition / change process in step S809 of FIG.

  Next, details of the schedule deletion process in step S811 of FIG. 8 will be described with reference to FIG.

  FIG. 11 is a flowchart illustrating an example of a schedule deletion process performed by the CPU 201 of the client apparatus 101. First, in step S1101, the CPU 201 extracts a management ID (for example, sid = E111) from the HTTP request data components obtained as a result of the HTTP request data analysis processing in step S804 in FIG. The process proceeds to step S1102.

  Thereafter, the response data wait state is continued until it is determined that the response data for the HTTP request data has been received (YES in step S1103).

  When response data indicating the normal end of the schedule operation is received from the internal HTTP server 102 (YES in step S1103), the schedule event table 342 is searched using the management ID acquired in step S1101 (step S1104). Then, it is determined whether the schedule event data is a new event (step S1105). If the schedule event data is a new event (YES in step S1105), the process ends.

  If it is determined in step S1105 that the event is not a new event, the process proceeds to step S1106 to perform a corresponding external event search process. Details of this processing will be described later with reference to FIG.

  If the CPU 201 determines that there is a corresponding external event after the processing of step S1106 is completed (YES in step S1107), the request definition information of the DELETE action of the corresponding external schedule service is acquired from the request definition information table 342 (step S1108). ). Then, HTTP request data for deleting the schedule information managed by the external schedule service is generated according to the request condition 1904 of the acquired request definition information (step S1109), and the generated HTTP data is sent to the external HTTP server 105. (Step S1110).

  Then, when response data indicating that the deletion process is completed is acquired (YES in step S1111), the process proceeds to step S1112 and the schedule event deleted from the external schedule service is deleted from the schedule event table (step S1112). The above is the detailed description of the schedule deletion process in step S811 of FIG.

  Next, details of the corresponding external event search process in step S1008 in FIG. 10 and step S1106 in FIG. 11 will be described with reference to FIG.

  FIG. 12 is a flowchart illustrating an example of a corresponding external event search process performed by the CPU 201 of the client apparatus 101. First, the CPU 201 determines whether an external event has already been acquired (step S1201). If it is determined that it has already been acquired, this process ends without performing the process described later.

  On the other hand, if it is determined in step S1201 that the external event has not been acquired (that is, the external event has not been acquired: NO), the process proceeds to step S1202, and it is determined whether the external schedule service has already been logged in. If it is determined that the user has already logged in to the external schedule service (YES in step S1202), the process proceeds to step S1207. On the other hand, if it is determined that the user has not logged in yet (NO in step S1202), the process proceeds to step S1203, and authentication information (account name 1805, password) of the external schedule service definition information from the schedule service definition information table 341 is obtained. 1806). Thereafter, HTTP request data (authentication information) used for user authentication is generated using the acquired authentication information, and the generated authentication information is transmitted to the external HTTP server 105 (step S1204).

  Thereafter, it is determined whether or not the login is successful (step S1205). If the login is unsuccessful (NO in step S1205), the process proceeds to step S1206, and error information is output to the display device 210. Exit. On the other hand, if the login is successful (YES in step S1205), the process proceeds to step S1207, and an event LIST acquisition process is performed. Details of this processing will be described later with reference to FIG.

  After the event LIST acquisition process in step S1207 ends, the processes in steps S1208 to S1212 are performed on the external schedule event data registered in the schedule event table in the LIST acquisition process in step S1207. First, in step S1209, one piece of external schedule event information is acquired. Then, it is determined whether there is internal schedule event data that matches the start year / month / day / hour / minute and the end year / month / day / hour / minute of the external schedule event data acquired in step S1209 (step S1210). When it is determined that there is internal schedule event data, the external schedule event data acquired in step S1209 and the internal schedule event data having the same start / end date / time and date / time are associated with the external schedule event data. The event ID of the schedule event corresponding to the corresponding event item of each record is set (step S1211). Then, this process is performed for all external schedule event data. The above is the details of the corresponding external event search process. By performing this process, it is possible to associate the internal schedule event data and the external schedule event data registered in the schedule event table shown in FIG.

  Next, the details of the event LIST acquisition process in step S1207 in FIG. 12 will be described with reference to FIG.

  FIG. 13 is a flowchart illustrating an example of event list processing performed by the CPU 201 of the client apparatus 101. First, in step S1301, the CPU 201 acquires request definition information corresponding to the LIST action for the external schedule service from the request definition information table 342. Then, an event acquisition request for N months set in advance from the current month of LIST acquisition is transmitted, the process proceeds to step S1303, and response data is awaited.

  In step S1303, for example, as shown in FIG. 6, HTML response data in which event information for one month is displayed in a table format is obtained. If only one month of data can be displayed on one page, processing may be configured to repeat this N times to obtain N months of data. If there is a page in which event data for a specified period can be acquired in a list format such as CSV, request definition information that transmits request data to the page may be set.

If the CPU 201 determines in step S1304 that the response data has been successfully acquired (YES in step S1304), the process proceeds to step S1305. On the other hand, if it is determined in step S1304 that the process has not succeeded (that is, failed: NO), the process ends without performing the process described later.

  Thereafter, the CPU 201 repeats the processes of S1305 to S1314 for each piece of event information of the acquired response data. If the acquired response data is in the HTML format as shown in FIG. 6, for example, a link to detailed information of each schedule event is included. When the link is clicked, detailed information is displayed as shown in FIG. 7, for example. When the acquired response data is in the CSV format, detailed information on the event is included for each line.

In step S1306, a request similar to clicking on the link of each event on the HTML to obtain detailed information on each event is sent to the HTTP server (internal HTTP server 102 or external HTTP server 105). Request definition information corresponding to the GET action of the schedule service to be processed is acquired from the request definition information table 342. After extracting the management ID (for example, sid = E111) from the request parameter included in the link information, the process proceeds to step S1307 to generate an HTTP request for performing a GET action, and transmit to the HTTP server.

  If request data is transmitted in step S1307, the process proceeds to step S1308 to wait for response data from the HTTP server. The response data is obtained, for example, as HTML as shown in FIG.

In step S1309, the CPU 201 determines whether response data has been successfully acquired. If response data is normally obtained, that is, if “YES” in the step S1309, the process proceeds to the next step S1310. On the other hand, for example, when an error response from the HTTP server or a timeout with no response for a certain time occurs, That is, if “NO” in the step S1310, the present process is ended.

In step S1310, the data corresponding to the event item such as the start date, the end date, the end date of the event information, and the event content are acquired from the request component analyzed in step S1308. For example, when the start year is associated with the startyear value of the request parameter, the value is associated with the start year of the event item. Depending on the Web electronic schedule service, the start year may be specified as a partial character string, such as “YYYY / MM / DD”, in one request parameter value. In such a case, the request parameter in the request definition information may be set so that a substring (for example, two characters from the first digit) of the corresponding parameter value can be acquired as the start year.

  In step S1311, the schedule event table 344 is searched, and the process proceeds to step S1312. If it is determined that the event is a new event that does not match the event already registered in the schedule event table 344, that is, if it is determined YES in step S1312, the process proceeds to step S1313, and the schedule event table 344 stores the new schedule event. Register as data. On the other hand, if NO in step S1312, the CPU 201 determines that the process proceeds to step S1314, and the processes in steps S1305 to S1314 are repeated for each schedule event information of the acquired response data.

In step S1314, the process ends when the repetition of all the acquired events is completed. The above is the description of the event LIST acquisition process.

Finally, the external service synchronization processing in the present invention will be described with reference to FIG. This external service synchronization process eliminates the discrepancy in event information between these services when the external schedule service is updated directly or when only the internal schedule service is updated without relying on the external service linkage process described above. Means.

  FIG. 14 is a flowchart illustrating an example of external service synchronization processing performed by the CPU 201 of the client apparatus 101. At the time of starting the processing according to the flowchart of FIG. 9, the web browser 111 of the client apparatus 101 is accessing the web electronic schedule service page of the internal HTTP server 102 and instructs acquisition, update, deletion, etc. of the event. It is in a possible state.

  First, in step S1401, the CPU 201 waits for a synchronization execution instruction from a user who operates the client apparatus 101. A synchronous execution instruction can be given to the extended function 112 by, for example, instructing to click on the menu of the web browser on the display apparatus 210 of the client apparatus 101. When the extended function 112 receives the synchronization execution instruction, the process proceeds to step S1402.

  In step S1402, the LIST action for the internal schedule service is searched from the request definition information table 342, and the HTTP request data according to the request parameter definition 1905 obtained as a result of the search is transmitted to the internal HTTP server 102 to obtain the event list. And register it in the schedule event table. Note that the event LIST acquisition method is performed for the internal HTTP server 102 in the procedure described with reference to FIG.

  Next, in step S1403, in order to detect a mismatch event for the external HTTP server 105, the corresponding external event search process described in FIG. 12 is performed, and the schedule event registered in the internal schedule service and the external schedule service are registered. Is associated with the scheduled event.

  Thereafter, the CPU 201 repeats the processes of steps S1404 to S1420 for each schedule event data registered in the schedule event table 344.

  In step S1405, the CPU 201 determines whether there is a corresponding event according to the corresponding event data in the schedule event table 344. If it is determined that there is a corresponding event (YES in step S1405), the process proceeds to step S1420, and this process is repeated for the next schedule event data in the schedule event table. On the other hand, if it is determined that there is no corresponding event (NO in step S1405), the process proceeds to step S1406.

  In step S <b> 1406, a screen (not shown) that accepts the mismatch schedule event information and synchronization or deletion instruction input is displayed on the display device 210 of the client device 101. For example, schedule event data that exists in the external schedule service but does not exist in the internal schedule service, or conversely, schedule event data that exists in the internal schedule service but does not exist in the external schedule service is displayed.

  Thereafter, in step S1407, a solution instruction is waited to accept the user's solution. The user can instruct synchronization to add an event that exists only on one side to the other. Alternatively, it can be instructed to delete an event that exists only on one side. Although it is possible to select the user's solution method instruction for such a mismatch event one by one, it is also possible to determine a solution method in advance and check only the mismatch event. If confirmation is not required, it is of course possible to process all inconsistent schedule events in a batch using a predetermined solution without receiving a solution instruction.

  Next, the CPU 201 determines whether or not the solution instruction received from the user is synchronous (step S1408). If it is determined that the instruction is a synchronization instruction (YES in step S1408), the process proceeds to step S1415. On the other hand, if the CPU 201 determines NO in step S1408, the process proceeds to step S1409.

  If the CPU 201 determines NO in step S1408, it determines whether the solution instruction is deletion in step S1409. If it is determined that the received solution instruction is deletion (YES in step S1409), the process proceeds to step S1410. On the other hand, if NO is determined in step S1409, the process proceeds to step S1420, and the processes in steps S1404 to S1420 are repeated for each event in the event table.

  In the processing after step S1410, deletion processing for the mismatch event is performed. In step S1410, the DELETE request definition information is acquired with reference to the request definition information table 342 for the service ID holding the mismatched event.

  In step S1411, the management ID of the mismatched event information is set as a parameter of the DELETE request, and in step S1412, HTTP request data is transmitted to the HTTP server.

  If the request succeeds in step S1413, that is, if “YES” in step S1413, the process proceeds to step S1414, and the corresponding mismatch event information is deleted from the schedule event table 344. On the other hand, if “NO” in the step S1413, the processes in the steps S1404 to S1420 are repeated.

  In step S1415 and subsequent steps, a synchronization process for the mismatch event is performed. In step S1415, the request definition information table 342 for the service ID holding the mismatched event is referred to, and the ADD request definition information of the synchronization target service ID which is the other service is acquired.

  In step S1416, event item values such as the start year and start month of the mismatched event information are set as parameters of the ADD request, and in step S1417, the HTTP request data is transmitted to the HTTP server. At the time of this event transmission, the event contents may be rewritten as in step S1012 of FIG.

  Next, if the request is successful in step S1418, that is, if “YES” in step S1418, the process proceeds to step S1419, and the event information transmitted in the request is added to the event table. On the other hand, if “NO” in the step S1418, the processes of the steps S1404 to S1420 are repeated.

  Although the embodiments have been described in detail above, the present invention can take an embodiment as, for example, a system, an apparatus, a method, a program, or a storage medium, and specifically includes a plurality of devices. The present invention may be applied to a system that is configured, or may be applied to an apparatus that includes a single device.

  In the present invention, a software program (in the embodiment, a program corresponding to the flowchart shown in the figure) that realizes the functions of the above-described embodiment is directly or remotely supplied to the system or apparatus, and the computer of the system or apparatus Is also achieved by reading and executing the supplied program code.

  Accordingly, since the functions of the present invention are implemented by computer, the program code installed in the computer also implements the present invention. In other words, the present invention includes a computer program itself for realizing the functional processing of the present invention.

  In that case, as long as it has the function of a program, it may be in the form of object code, a program executed by an interpreter, script data supplied to the OS, or the like.

  As a recording medium for supplying the program, for example, floppy (registered trademark) disk, hard disk, optical disk, magneto-optical disk, MO, CD-ROM, CD-R, CD-RW, magnetic tape, nonvolatile memory card ROM, DVD (DVD-ROM, DVD-R) and the like.

  As another program supply method, a client computer browser is used to connect to an Internet homepage, and the computer program of the present invention itself or a compressed file including an automatic installation function is downloaded from the homepage to a recording medium such as a hard disk. Can also be supplied. It can also be realized by dividing the program code constituting the program of the present invention into a plurality of files and downloading each file from a different homepage. That is, a WWW server that allows a plurality of users to download a program file for realizing the functional processing of the present invention on a computer is also included in the present invention.

  In addition, the program of the present invention is encrypted, stored in a storage medium such as a CD-ROM, distributed to users, and key information for decryption is downloaded from a homepage via the Internet to users who have cleared predetermined conditions. It is also possible to execute the encrypted program by using the key information and install the program on a computer.

  In addition to the functions of the above-described embodiments being realized by the computer executing the read program, the OS running on the computer based on the instruction of the program is a part of the actual processing. Alternatively, the functions of the above-described embodiment can be realized by performing all of the processes.

  Furthermore, after the program read from the recording medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function expansion board or The CPU or the like provided in the function expansion unit performs part or all of the actual processing, and the functions of the above-described embodiments are realized by the processing.

100 Intranet
101-1 to 101-3 Client apparatus 102 Internal HTTP server 103 Local area network (LAN)
104 Wide area network 105-1 to 105-3 External HTTP server 111 Web browser application 112 Extended function application 201 CPU
202 RAM
203 ROM
204 System Bus 205 Input Controller 206 Video Controller 207 Memory Controller 208 Communication I / F (Interface) Controller 209 Keyboard 210 Display Device 211 External Memory

Claims (11)

An information processing apparatus capable of communicating with an HTTP server that provides a schedule management service using an HTTP protocol,
First identification information for identifying the HTTP server, and a first HTTP server that is an HTTP server installed in an internal network, or an HTTP server installed in an external network First storage means for storing service management information, including second specifying information for specifying which of the two HTTP servers, and at least the first HTTP server stored in the first storage means For the first definition information defining the structure of transmission data transmitted to the first HTTP server, and at least the second HTTP server stored in the first storage means, Second storage means for storing second definition information defining a structure of transmission data transmitted to the second HTTP server When,
First determination means for determining whether transmission data generated by the browser application and transmitted to the external terminal is transmission data for any of the first HTTP servers stored in the first storage means. When,
When the first determination means determines that the data is transmission data to the first HTTP server, it is transmitted to the first HTTP server according to the structure of transmission data defined by the first definition information. First acquisition means for acquiring data contents from the transmitted data;
Generating means for generating transmission data to be transmitted to the second HTTP server according to the data content acquired by the first acquisition means and the second definition information;
Transmitting means for transmitting the transmission data generated by the generating means to the second HTTP server;
An information processing apparatus comprising: In each of the first definition information and the second definition information, a structure of the transmission data is defined for each data operation event with respect to the HTTP server for the HTTP server,
The first determination means further determines which data operation event for the first HTTP server is in accordance with the first definition information,
The first acquisition unit includes the first HTTP server according to the definition information corresponding to the data operation event of the first HTTP server determined by the first determination unit among the first definition information. Data content is acquired from the transmission data transmitted to
The transmission unit generates transmission data for the second HTTP server according to the second definition information corresponding to the data operation event determined by the first determination unit. Information processing device. The data manipulation event includes editing and deletion of schedule information,
Third storage means for storing a correspondence relationship between schedule information managed by the first HTTP server and schedule information managed by the second HTTP server;
After the first determination means determines that the data operation event corresponds to the editing or deletion of the schedule information, the first corresponding to the schedule information managed by the first HTTP server that is the target of the data operation event. Second determination means for determining whether schedule information of the HTTP server of 2 is stored in the third storage means;
Further comprising
When it is determined that the second determination unit stores the data, the generation unit determines whether the second server is in accordance with the second definition information corresponding to the data operation event determined by the first determination unit. The information processing apparatus according to claim 2, wherein transmission data for data operation on the schedule information is generated. The first determination unit determines that the data operation is editing of schedule information, and the second determination unit manages the schedule managed by the first HTTP server that is the target of the data operation event. If it is determined that the schedule information of the second HTTP server corresponding to the information is not stored in the third storage means,
The information processing apparatus according to claim 3, wherein the generation unit generates transmission data for registering new data with respect to the second HTTP server. Definition information related to a data acquisition event for the first HTTP server and the second HTTP server, and response data transmitted from the first HTTP server and the second HTTP server in response to the data acquisition event Fourth storage means for storing third definition information defining the structure;
Second acquisition means for acquiring schedule information managed by the first HTTP server and the second HTTP server;
Acquire schedule information managed by the first HTTP server and the second HTTP server according to the structure of response data stored in the third definition information stored in the fourth storage means. And an association means for associating each acquired schedule information,
The third storage unit stores a correspondence relationship between the schedule information managed by the first HTTP server and the schedule information managed by the second HTTP server associated with each other by the association unit. The information processing apparatus according to claim 3, wherein the information processing apparatus is an information processing apparatus. Of the character string information included in the transmission data transmitted to the first HTTP server, the character string that is subjected to character string conversion when the transmission data transmitted to the second HTTP server is created by the generating means And a fifth storage means for storing the pre-conversion character string and the post-conversion character string that is the post-conversion character string in association with each other,
The generation unit includes a character string that matches the pre-conversion character string stored in the fifth storage unit in the data content of the data transmitted to the first HTTP server acquired by the first acquisition unit. The transmission data to be transmitted to the second HTTP server is generated using the post-conversion character string that is associated with the pre-conversion character string. The information processing apparatus according to claim 1. A fifth storage means for storing authentication information used when accessing the second HTTP server;
The transmission means transmits the transmission data generated by the generation means to the HTTP server after accessing the second HTTP server using the authentication information and accepting the authentication. The information processing apparatus according to any one of 1 to 6. First identification information for identifying an HTTP server and a first HTTP server that is an HTTP server installed in the internal network or a second HTTP server installed in an external network First storage means for storing service management information including second specifying information for specifying which one of the HTTP servers, and at least the first HTTP server stored in the first storage means For the first definition information defining the structure of transmission data transmitted to the first HTTP server, and at least the second HTTP server stored in the first storage means, Second storage means for storing second definition information defining a structure of transmission data transmitted to the second HTTP server; An information processing method performed by an information processing apparatus capable of communicating with the HTTP server that provides a schedule management service using an HTTP protocol,
First determination step of determining whether transmission data generated by a browser application and transmitted to an external terminal is transmission data for any of the first HTTP servers stored in the first storage unit When,
When it is determined in the first determination step that the data is transmission data to the first HTTP server, the data is transmitted to the first HTTP server according to the structure of transmission data defined by the first definition information. A first acquisition step of acquiring data content from the transmitted data;
A generation step of generating transmission data to be transmitted to the second HTTP server according to the data content acquired in the first acquisition step and the second definition information;
A transmission step of transmitting the transmission data generated by the generation means to the second HTTP server;
An information processing method comprising: The information processing apparatus further creates a transmission data to be transmitted to the second HTTP server by the generation unit, out of character string information included in the transmission data transmitted to the first HTTP server. Third storage means for storing a pre-conversion character string that is a character string for character string conversion and a post-conversion character string that is a character string after the conversion in association with each other,
The generation step includes a character string that matches the pre-conversion character string stored in the third storage means in the data content of the data transmitted to the first HTTP server acquired in the first acquisition step. The transmission data to be transmitted to the second HTTP server is generated using the post-conversion character string associated with the pre-conversion character string when the data is converted. Processing method. First identification information for identifying an HTTP server and a first HTTP server that is an HTTP server installed in the internal network or a second HTTP server installed in an external network First storage means for storing service management information including second specifying information for specifying which one of the HTTP servers, and at least the first HTTP server stored in the first storage means For the first definition information defining the structure of transmission data transmitted to the first HTTP server, and at least the second HTTP server stored in the first storage means, Second storage means for storing second definition information defining a structure of transmission data transmitted to the second HTTP server; , A computer program for causing a computer to function as an information processing apparatus capable of communicating with the HTTP server that provides a schedule management service using an HTTP protocol,
First determination means for determining whether transmission data generated by the browser application and transmitted to the external terminal is transmission data for any of the first HTTP servers stored in the first storage means. When,
When the first determination means determines that the data is transmission data to the first HTTP server, it is transmitted to the first HTTP server according to the structure of transmission data defined by the first definition information. First acquisition means for acquiring data contents from the transmitted data;
Generating means for generating transmission data to be transmitted to the second HTTP server according to the data content acquired by the first acquisition means and the second definition information;
A computer program that causes transmission data generated by the generation unit to function as a transmission unit that transmits the transmission data to the second HTTP server. The computer further generates a character string when creating the transmission data to be transmitted to the second HTTP server by the generation unit, out of the character string information included in the transmission data to be transmitted to the first HTTP server. A third storage means for storing a pre-conversion character string that is a character string to be converted and a post-conversion character string that is a character string after the conversion in association with each other;
The generation unit includes a character string that matches the pre-conversion character string stored in the third storage unit in the data content of the data transmitted to the first HTTP server acquired by the first acquisition unit. The transmission data to be transmitted to the second HTTP server is generated using the post-conversion character string associated with the pre-conversion character string. program.

Images