JP5408101B2 - Information processing apparatus and information processing method - Google Patents

Description

  The present invention makes it possible to inherit the type of a terminal that is accessed even during page transitions across Web applications, and appropriate information corresponding to the screen display area of the terminal without impairing the user's convenience during page transitions An information processing apparatus having a plurality of Web applications that can be provided is provided.

  In recent years, information provision using the Internet has expanded not only to client PCs (Personal Computers) but also to mobile terminals such as mobile phones and PDA (Personal Digital Assistants) terminals, and the information provision methods have become diversified. Have been doing.

  In order to provide information according to the size of the display screen on the terminal side such as a client PC, a mobile phone, and a PDA terminal, a terminal is provided for HTML (HyperText Markup Language) data prepared for information provision in advance. It has been proposed to generate display contents according to the type of the document (for example, see Patent Document 1). Alternatively, a gateway server that mediates between a Web server that provides information and a terminal that requests information requests information provided from the Web server in response to an information request from the terminal depending on the type of the terminal. It has been proposed to perform additional work such as color attribute adjustment work (see, for example, Patent Document 2).

  On the other hand, in recent years, a data processing apparatus having a Web server function capable of providing information related to image formation has been proposed (see, for example, Patent Document 3). With this data processing apparatus, a user can be provided with information related to a device that performs image forming processing provided in the data processing apparatus only via the Internet.

  In addition, even when a page transition is performed on the client PC side in providing information composed of a plurality of pages, information input by the user using the client PC is stored in a predetermined area, and the page transitions thereafter. A data inheritance method has been proposed in which input information is inherited and information is provided by using the input information (see, for example, Patent Document 4).

  However, the conventional information providing method has the following problems.

  In a Web server having a Web server function capable of providing information relating to image formation, in the case of providing, as information, the state of a device such as a plotter controlled by an image forming process or a Web server that performs the image forming process, Since this is the state at the time, HTML data cannot be prepared in advance. Therefore, the method proposed in Patent Document 1 cannot be applied. Moreover, in patent document 2, the expense, maintenance, etc. for providing a gateway server will start.

  The data processing apparatus proposed in Patent Document 3 cannot provide information according to the size of the display screen on the terminal side such as a client PC, a mobile phone, and a PDA terminal.

  Furthermore, in the data inheritance method proposed in Patent Document 4, a page for inputting information related to the user is required, or the user must explicitly input the page. In addition, information to be inherited for each user must be managed while connected to the network. Therefore, it is not possible to automatically provide information according to the size of the display screen.

  Therefore, an object of the present invention is to enable inheritance of the terminal type that is accessed even during page transitions across Web applications, and according to the screen display area of the terminal without impairing the user's convenience during page transitions. It is another object of the present invention to provide an information processing apparatus having a plurality of Web applications that can provide appropriate information.

In order to solve the above-described problem, an information processing apparatus according to the present invention is included in the connection information and communication means for receiving connection information from a terminal connected via a network, as described in claim 1. When the URL is composed of common path information including terminal type information of the terminal and relative path information designating processing for obtaining predetermined information following the common path information, the URL relates to a plotter, a scanner, and a network. among a plurality of functions for performing processing, by calling the function corresponding to said relative path information to execute the processing, generates a Web page with the processing result obtained by the processing is output based on the common path information And a Web page generation means.

  In such an information processing apparatus, a function is executed in association with relative path information in a URL, so that it is not necessary to develop a function of the number of combinations of common path information and relative path information. In addition, the common path information located before the relative path information in the URL includes information indicating the terminal type, profile, etc. of the terminal, so that the same common path information as the previous request can be acquired. The common path information can be inherited between Web pages to be generated without specifying such information for each request.

  The information processing apparatus according to the present invention is characterized in that, as described in claim 2, the information processing apparatus specifies attribute information indicating an attribute related to a usage mode of a display screen of the terminal from the connection information, and If the request includes URL creation means for creating the URL by setting the information as the common path information of the URL, and the URL included in the connection information does not include the common path information used for the function corresponding to the relative path information The URL creation means may identify the attribute information from the connection information, set it as common path information of the URL, and allow the terminal to access the set URL.

  In such an information processing apparatus, when a request for which the URL does not include common path information is received, information indicating the terminal type and profile of the terminal is specified, and the terminal is made to access the URL set in the common path information. Thus, common path information can be inherited between Web pages generated thereafter.

  Furthermore, the information processing apparatus according to the present invention is further characterized in that the information processing apparatus further includes at least one of the plurality of functions and performs the processing related to the hardware resource. The relative path information is composed of application ID information for specifying the application and page information for specifying the function in the specified application. When generating link information across other applications, the link information is configured with static relative path information so that the terminal can access the URL including the common path information and the relative path information. May be.

  In such an information processing apparatus, link information is statically generated with relative path information composed of application ID information and page information.

  In addition, as described in claim 4, the information processing apparatus according to the present invention refers to the page information of the URL by referring to the first correspondence list in which the page information is associated with the function name to be called. A plurality of handler means for calling the function with a corresponding function name using the common path information; the plurality of handler means are provided corresponding to each of the plurality of applications; By calling the handler means with the handler name corresponding to the application ID information of the URL by referring to the second correspondence list in which the application ID information and the handler name that identifies the handler means are associated with each other, The called handler means refers to the first correspondence list and adds the page information of the URL to the page information. It can be a function name to respond configured to call the function.

  Furthermore, as means for solving the above-described problems, the present invention may be an information processing method for causing a computer to perform the processing in the information processing apparatus.

  According to the present invention, the URL is composed of common path information and relative path information following the common path information, and the terminal type of the terminal is set as a part of the URL as common path information. Even when a page transition occurs, information corresponding to the same terminal type can always be provided to the Web browser of the terminal. In addition, the description of the processing result in XML and the process of determining the terminal type and converting from XML to HTML can be configured separately from a plurality of Web applications.

It is a block diagram which shows the hardware constitutions of the information processing apparatus which concerns on one Example of this invention. It is a block diagram which shows the function structure of information processing apparatus. It is a figure which shows URL structure. It is a block diagram for demonstrating execution of a Web application. FIG. 5 is a diagram showing a hash list. default. It is a figure which shows the processing flow by cgi. default. It is a figure which shows the processing flow by cgi. It is a flowchart figure for demonstrating the analysis process of terminal information. It is a figure which shows the data structure of HTTP connection information. It is a figure which shows the data structure of HTTP request information. It is a figure which shows a header information list. It is a figure which shows a web browser classification-terminal classification correspondence table. It is a figure which shows Web browser OS-terminal classification correspondence table. It is a figure which shows the example of a default HTML output. mainFrame. It is a figure which shows the processing flow by cgi. mainFrame. It is a figure which shows the processing flow by cgi. It is a figure which shows the example of the mainframe HTML for PCs. topPage. It is a figure which shows the processing flow by cgi. topPage. It is a figure which shows the processing flow by cgi. A topPage written in XML. It is a figure which shows the example of the process result by cgi. It is a figure which shows the example of description of XSL for converting a process result from XML to HTML. topPage. It is a figure which shows the example of description of HTML for PC which shows the process result of cgi. It is a figure which shows the example of a system status display with a client PC. topPage. It is a figure which shows the example of description of HTML for PDA terminals which shows the processing result of cgi. It is a figure which shows the example of a system status display with a PDA terminal. It is a figure which shows the example of a display of the network setting in a PDA terminal. It is a figure which shows the example which displayed the page for general PCs on the PDA terminal as it is.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  An information processing apparatus according to an embodiment of the present invention has at least one of a plurality of different image forming functions such as a printer, a FAX, and a copy, and provides information related to image formation by a plurality of Web applications. In this embodiment, for convenience of explanation, a case where information relating to a printing process or a plotter that performs printing is mainly provided will be described.

  FIG. 1 is a block diagram showing a hardware configuration of an information processing apparatus according to an embodiment of the present invention. In FIG. 1, an information processing apparatus 100 is an apparatus controlled by a computer, and includes a CPU (Central Processing Unit) 11, a ROM (Read-Only Memory) 12, a RAM (Random Access Memory) 13, and a nonvolatile memory. RAM (non-volatile random access memory) 14, real-time clock 15, Ethernet (registered trademark) I / F (Ethernet (registered trademark) Interface) 21, USB (Universal Serial Bus) 22, IEEE (Institute of Electrical and Electronics Engineers) 1284 23, a hard disk I / F 24, an engine I / F 25, and an RS-232C I / F 26, which are connected to the system bus B.

  The CPU 11 controls the information processing apparatus 100 according to a program stored in the ROM 12. In the RAM 13, for example, areas are allocated to resources connected to the interfaces 21 to 26. The nonvolatile RAM 14 stores information necessary for processing by the CPU 11 to control the information processing apparatus 100. The real-time clock 15 measures the current time and is used by the CPU 11 to synchronize processing.

  An Ethernet (registered trademark) interface cable such as 10BASE-T or 100BASE-TX is connected to the Ethernet (registered trademark) I / F 21. A USB interface cable is connected to the USB 22. An IEEE1284 interface cable is connected to the IEEE1284 23.

  A hard disk 34 is connected to the hard disk I / F 24, and document data of a document to be printed or image data after print processing transmitted via the network is stored in the hard disk 34 via the hard disk I / F 24. . Connected to the engine I / F 25 are a plotter 35-1 for printing on a predetermined medium based on document data, a scanner 35-2 for capturing image data, and the like. An operation panel 36 is connected to the RS-232C I / F 26 to display information to the user and acquire input information or setting information from the user.

  Next, a functional configuration of the information processing apparatus 100 having a hardware configuration as shown in FIG. 1, enabling a plurality of different image forming processes, and having a plurality of Web applications will be described.

  FIG. 2 is a block diagram illustrating a functional configuration of the information processing apparatus. In FIG. 2, the information processing apparatus 100 can be connected via the Internet 16 to terminals 40 such as a client PC 41, a mobile phone 42, and a PDA (Personal Digital Assistants) terminal 43 having different display screen usage modes. The computer provides information in response to a request from the terminal 40 as a response to the request.

  The information processing apparatus 100 mainly includes a network control unit 101, a sequence control library 110, a web application distribution common library 120, a web page handler 200, a SOAP (Simple Object Access Protocol) library 201, and an XML (eXtensible). It has a Markup Language) library 203, an XSLT (XSL Transformations) processor 205, a Web page function (WPF) 300, a printer control unit 103, and a scanner control unit 105.

  The network control unit 101 has an HTTP daemon 2 that performs communication control using at least HTTP (Hyper Text Transfer Protocol), receives a request from the terminal 40 according to HTTP, and provides information according to the request as a response to the request. .

  When the HTTP daemon 2 receives a request from the terminal 40, the plurality of Web applications 301 are configured to have a predetermined attribute information indicating an attribute relating to a usage pattern on the display screen of the terminal 40 even when a page is changed. In order to execute the process, temporary common path information, a Web application ID for executing the predetermined process, and a CGI (Common Gateway Interface) are added to a URL (Uniform Resource Locator) specified by the request. The page transition refers to displaying another Web page linked to the Web page from the displayed Web page.

  The HTTP daemon 2 adds necessary information and creates a URL as shown in FIG. FIG. 3 is a diagram showing a URL configuration. In FIG. 3, the URL is largely composed of common path information 60a and relative path information 60b. When the HTTP daemon 2 receives the first page request from the terminal 40, for example, only “http: // AAA” is specified as the URL, and the HTTP daemon 2 responds to the predetermined “ /TERMINAL/PROFILE/LANG/webDefaultApl/defaul.cgi ”is added.

  The URL configured in this way includes, for example, a protocol type 61 for specifying an access means such as “http”, an IP address 62 indicated by “AAA”, terminal type information 63a indicated by “TERMINAL”, It has profile information 63b indicated by “PROFILE”, language information 63c indicated by “LANG”, Web application ID 64 indicated by “webDefaultApl”, and page information 65 indicated by “default.cgi”.

  Then, the protocol type 61, the IP address 62, the terminal type information 63a, the profile information 63b, and the language information 63c are inherited in the subsequent page transition as the common path information 60a, and the Web application 301 straddling the page transition. Referenced between. The Web application ID 64 and the page information 65 constitute relative path information 60b.

  Returning to FIG. 2, the description of the processing unit will be continued.

  The sequence control library 110 absorbs a difference between a data transmission / reception processing sequence performed via the Internet 16 and a data transmission / reception processing sequence with each Web application 301 by a predetermined sequence control processing. Is a common processing unit.

  The web application distribution common library 120 is a processing unit that analyzes a request from the terminal 40 and generates a response to the terminal 40 and is common to the plurality of web applications 301. The Web application distribution common library 120 converts the response described in XML by the Web page handler 200 into a display format by HTML (HyperText Markup Language) corresponding to the terminal type of each terminal 40 by the XSLT processor 205.

  The web page handler 200 is a processing unit that performs conversion between a processing language that can be interpreted by the web application 301 and a processing language that is interpreted by communication control based on a request and a response that are performed between the terminal 40 and the terminal 40. The web page handler 200 calls a function of the web application 301 corresponding to the request via the CGI. Further, the Web page handler 200 sends a processing result data serialization request to the SOAP library 201 in order to describe the processing result data notified from the Web page function 300 in XML.

  The SOAP library 201 performs data conversion and serialization by describing the processing result data given as a C language variable in XML. In this embodiment, serializing means describing a processing result notified from the Web page function 300 by XML.

  The XML library 203 serializes the processing result in XML by being used by the SOAP library 201. Further, the XML library 203 is used by the XSLT processor 205 to generate HTML indicating the processing result.

  The XSLT processor 205 converts the processing result described in XML into an HTML description by using the XML library 203 based on XSL (eXtensible Stylesheet Language) corresponding to the Web application 301 specified by the request of the terminal 40. To do.

  When the web page function 300 is called by the web page handler 200, for example, an API (Application Program Interface) 17 is provided to the printer control unit 103 or the scanner control unit 105 that controls image formation provided in the information processing apparatus 100. To obtain information indicating the state of the plotter 35-1 or the state of the scanner 35-2, and return the information to the Web page handler 200. Similarly, the Web page function 300 returns information acquired by making an inquiry to the network control unit 101 via the API 17 to the Web page handler 200.

  Next, a detailed configuration for using a Web application will be described with reference to FIGS. FIG. 4 is a block diagram for explaining the execution of the Web application. FIG. 5 is a diagram showing a hash list. 4, the web page handler 200 includes a default handler 210 that is executed at the time of the initial request from the terminal 40 and a terminal 40 so that information can be provided based on the URL configuration as shown in FIG. Network setting handler 220 executed by page transition in response to the above instruction, system configuration information providing handler 230 executed by page transition, and the like.

  The web page function 300 includes a plurality of web applications 301 such as a web default application 310, a web network setting application 320, and a web system configuration information providing application 330 corresponding to each handler of the web page handler 200.

  Until the initial screen is displayed on the terminal 40, the default handler 210 sequentially selects “default.cgi”, “mainFrame.cgi”, “page” based on the page information 65 specified according to the URL format shown in FIG. A function call is made to the web default application 310 via “menuPage.cgi”, “topPage.cgi”, and “headerPage.cgi”. As a result, for example, the state of a device such as the plotter 35-1 or the scanner 35-2 mounted on the information processing apparatus 100 is displayed on the terminal 40.

  The network setting handler 220 makes a function call to the Web network setting application 320 for setting the network setting information input by the user of the terminal 40 in the information processing apparatus 100. The system configuration information providing handler 230 obtains system configuration information formed by the information processing apparatus 100 in response to a request from the terminal 40 by making a function call to the Web system configuration information providing application 330.

  The web application distribution common library 120 acquires the web application ID 64 from the URL, and refers to the hash list 50a shown in FIG. 5A, and when the web application ID 64 indicates “webDefaultApl”, sets “default_handler”. Run. Similarly, when the Web application ID 64 indicates another Web application ID, the handler corresponding to the Web application to be executed is executed with reference to the hash list 50a.

  Each handler 210, 220, and 230 of the Web page handler 200 acquires the page information 65 from the specified URL, and calls the corresponding function with reference to the hash list 50b shown in FIG. 5B. . For example, when the page information 65 indicates “topPage.cgi”, “topPage ()” is acquired from the hash list 50 b as a function to be called. Similarly, when the page information 65 indicates another CGI, the function to be called is acquired with reference to the hash list 50b.

  Further, the Web application distribution common library 120 makes page information 65 from the URL specified as the Web page function ID in order to make an XSL conversion request for converting the processing result described in XML to the XSLT processor 205 into HTML. And a corresponding style sheet is obtained with reference to the hash list 50b shown in FIG. For example, when the page information 65 indicates “topPage.cgi”, the Web application distribution common library 120 acquires “topPage.xsl” from the hash list 50b as a style sheet necessary for XSL conversion. Similarly, when the page information 65 indicates another CGI, the style sheet necessary for the XSL conversion is acquired with reference to the hash list 50b.

  4 and 5B, when the page information 65 of the URL as the Web page function ID is “default.cgi”, the default () function is executed, the terminal type of the terminal 40 is determined, and the HTTP daemon An initial screen is created in which the determined terminal type is set in the terminal type information of the URL created temporarily in step 2.

  When the page information 65 is “mainFrame.cgi”, the mainFrame () function is executed, and a predetermined CGI to be called is set for each frame constituting the initial screen. For example, the mainFrame () function generates information such as a frame for displaying a menu page, a frame for displaying a top page, and a frame for displaying a header page.

  When the page information 65 is “menuPage.cgi”, the menuPage () function is executed, and information for creating a menu page is generated. When the page information 65 is “topPage.cgi”, the topPage () function is executed, and for example, information for creating a top page that displays the state of the plotter 35-1 as the state of the printer is generated. When the page information 65 is “headerPage.cgi”, the headerPage () function is executed, and information for creating a header page is generated.

  When the page information 65 is “netsetting.cgi”, the setting () function is executed, and information for creating a page for performing system settings is generated. When the page information 65 is “sysconfig.cgi”, the config () function is executed, and information indicating the system configuration is generated.

  For convenience of explanation, the name of the Web application ID and the name of the Web page handler are unified, but the name is not limited to such a name, and the association is made by the hash list 50a as shown in FIG. It only has to be done. Similarly, the Web page function ID, the function, and the name of the style sheet are unified, but the name is not limited to such a name, and the association is made by the hash list 50b as shown in FIG. It only has to be done.

  Next, a processing flow until information is provided for the first request from the terminal 40 will be described. 6 and 7 show default. It is a figure which shows the processing flow by cgi.

  In FIG. 6, the terminal 40 makes a request with user agent information added using the HTTP GET method (step S11). The terminal 40 makes the request by designating the URL “http: // AAA”, for example.

  The HTTP daemon 2 of the information processing apparatus 100 that has received this request includes the terminal type information 63a, the profile information 63b, the language information 63c, the Web application ID 64, and the page information 65 in the URL “http: // AAA”. In addition, this request is notified to the sequence control library 110 (step S12). For example, the HTTP daemon 2 sets “TERMINAL” as the terminal type information 63a, “PROFILE” as the profile information 63b, “LANG” as the language information 63c, “webDefaultApl” as the web application ID 64, and “default.cgi” as the page information 65. It is added to the URL “http: // AAA”, and “http: //AAA/TERMINAL/PROFILE/LANG/webDefaultApl/default.cgi” is configured as the URL.

  The sequence control library 110 calls the web application distribution common library 120 (step S13). At this time, the sequence control library 110 sets, as arguments, HTTP connection information indicating information related to the connection with the terminal 40 and hash lists 50a and 50b (hereinafter, the hash lists 50a and 50b are collectively referred to as a hash list). To do. This HTTP connection information uniquely identifies the connection with the terminal 40 until the connection is disconnected.

  Based on the URL generated by the HTTP daemon 2, the Web application distribution common library 120 serves as the Web page handler 200 corresponding to the Web application ID 64 indicating “webDefaultApl” from the hash list 50 a to the default handler 210 (“default_handler”). Is specified and called (step S14).

  In the Web page handler 200, the default handler 210 acquires page information 65 indicating “default.cgi” from the URL, and the default () function from the hash list 50 b as the Web page function 300 corresponding to the “default.cgi”. Is specified and called (step S15). At this time, HTTP connection information is set as an argument. For example, when the web page function 300 is developed in C language, the web page handler 200 converts to a C language processing type and calls the default () function.

  By executing the default () function, the terminal information is analyzed based on the HTTP connection information, and a URL for calling the initial screen is created using the determined common path information 60a (step S16). The processing result data including the URL is notified to the default handler 210 in the Web page handler 200 (step S17). In the process using default.cgi, the common path information 60a is determined, and the URL is set by the determined common path information 60a and the relative path information 60b for determining the frame configuration of the initial screen. For example, “/ pc / admin / ja” is determined as the common path information 60a, and “/webDefaultApl/mainFrame.cgi” that divides the initial screen into several display areas by frames is set as the relative path information 60b.

  The default handler 210 makes a serialization request to the SOAP library 201 in order to describe the processing result data in XML (step S18). The SOAP library 201 creates a DOM (Document Object Model) based on, for example, processing result data represented by a C language structure, adds necessary elements and attributes (step S19), and the XML library 203 The processing result data is described in XML (step S20). The processing result data described in XML is notified to the default handler 210 as a serialization result by the SOAP library 203 (step S21). In the Web page handler 200, the default handler 210 notifies the Web application distribution common library 120 of the notified serialization result as display data “Response DOM” to be displayed on the terminal 40 (step S22).

  The web application distribution common library 120 refers to the hash list 50b and displays “default.cgi” page information in order to convert the display data described in XML into an HTML description corresponding to the type of the terminal 40. The style sheet “default.xsl” corresponding to 56 is acquired, and an XSL conversion request is made to the XSLT processor 205 (step S23). At this time, the display data “Response DOM” and the style sheet “default.xsl” are set as arguments.

  The XSLT processor 205 that has received the XSL conversion request analyzes the syntax of the display data “Response DOM” described in XML by executing the style sheet “default.xsl” specified by the argument (XML parsing), A DOM is created, elements and attributes are added (step S24), and converted to an HTML description by the XML library 203 (step S25). The XSLT processor 205 notifies the Web application distribution common library 120 of the converted HTML description as an XSL conversion result (step S26).

  Thus, the processing result described in HTML by the Web page function 300 when the page information 65 is “default.cgi” is output to the Web application distribution common library 120 as the default HTML. In the default HTML, it is described that “mainFrame.cgi” is called in the HTML, and is output as a default HTML response.

  The default HTML response is sequentially notified from the web application distribution common library 120 to the sequence control library 110 (step S27), and is notified from the sequence control library 110 to the HTTP daemon 2 (step S28). Then, the HTTP daemon 2 transmits a default HTML response as a response to the request of the terminal 40 in step S11 according to HTTP (step S29), and the processing flow for executing the web default application 310 by default.cgi is ended.

  In step S17, only the common path information 60a is determined and the determined common path information 60a is only added to the relative path information 60b. Therefore, the processing result is described in HTML in the Web default application 310, and is described in the HTML. The processing result may be output, and steps S18 to S26 may be omitted.

  Next, the terminal information analysis processing executed by calling the default () function in step S16 in FIG. 6 will be described in detail with reference to FIGS. FIG. 8 is a flowchart for explaining the terminal information analysis processing. FIG. 9 is a diagram showing a data structure of HTTP connection information. FIG. 10 is a diagram showing the data structure of HTTP request information. FIG. 11 is a diagram illustrating a header information list. The data structure shown in FIGS. 9 to 11 is a data structure referred to in the terminal information analysis process shown in FIG.

  Before describing the analysis processing in FIG. 8, each data structure shown in FIGS. 9 to 11 will be described. In FIG. 9, HTTP connection information 340 is information generated for each connection, and a description 346 indicated by “HTTP_REQUEST_INFO * request” indicates a pointer to the content of the request from the terminal 40, and “HTTP_RESPONSE_INFO * response” "347 indicates a pointer to the content of the response to the terminal 40. At the end of the pointer specified by the description 346, HTTP request information is stored as shown in FIG.

  10, HTTP request information 350 includes a remote address 351 indicating the address of the requesting terminal 40, a local address 352 indicating the host address receiving the request, and a request method 353 such as POST or GET. A request URL 354 indicating the URL of the request, an HTTP version 355 of the request, a header information list 360, and an encoded information list 357.

  In the request URL 354, a URL composed of common path information 60 a and relative path information 60 b as shown in FIG. 3 is set by the sequence control library 110. The HTTP request information 350 is notified simultaneously when the HTTP connection information 340 is notified to the Web page handler 200 and the Web page function 300. Therefore, each Web page handler 200 and each Web application 301 can refer to the common path information 60a.

  The header information list 360 is configured by information as shown in FIG. 11, for example. 11, the header information list 360 includes user agent information 365 represented by “User-Agent: Mozilla / 4.0 {compatible; MSIE 6.0; Windows NT 5.0; Q312461; NET CLR 1.0.3705}. The information 365 indicates the type of the terminal 40, and information can be provided according to the display screen on the terminal 40 by analyzing this description.

  In FIG. 8, the web default application 310 acquires the HTTP request information 350 from the HTTP connection information 340 by calling the default () function (step S1). Further, the web default application 310 acquires the user agent information 365 from the HTTP request information 350 (step S2). Then, the Web default application 310 identifies the terminal type of the terminal 40 with reference to the Web browser type-terminal type correspondence table (FIG. 12) based on the Web browser type of the user agent information 365 (step S3).

  The web default application 310 determines whether the terminal type can be determined based on the Web browser type (step S4). If it can be determined, the process proceeds to step S38. If it cannot be determined, the terminal type of the terminal 40 is specified by referring to the Web browser OS-terminal type correspondence table based on the Web browser OS of the user agent information 365 (step S5).

  The web default application 310 determines whether the terminal type has been determined by the web browser OS (step S6). If it cannot be determined, error information indicating that it is not supported is output (step S7), and the terminal information analysis process is terminated. In step S7, the Web default application 310 may set a predetermined terminal type as the terminal type of the terminal 40, instead of outputting error information indicating that it is not supported, and may proceed to step S8.

  On the other hand, if the terminal type can be determined in step S4 or S6, the web default application 310 sets the terminal type in the terminal type information 63a of the URL (step S8), and ends the terminal information analysis process.

  FIG. 12 is a diagram showing a Web browser type-terminal type correspondence table. In FIG. 12, a Web browser type-terminal type correspondence table 370 includes items such as a Web browser type and a terminal type, and the terminal type corresponding to the Web browser type is managed.

  As the Web browser type, for example, “DOCOMO (registered trademark)”, “xino (registered trademark)”, “MSPIE (registered trademark)”, “HandHTTP (registered trademark)”, “MSIE (registered trademark)”, “Mozilla ( “Registered trademark)”, “mozilla / 5 (registered trademark)”, “Netscape6 (registered trademark)”, and the like are managed.

  As terminal types, there are “IMODE (registered trademark)”, “PDA”, “0”, “PC”, and the like. The terminal type corresponding to the web browser type “DOCOMO (registered trademark)” is “IMODE (registered trademark)”, and the web browser types “xino (registered trademark)”, “MSPIE (registered trademark)”, “HandHTTP (registered trademark)”. The terminal type corresponding to “)” is “PDA”, and the web browser types “Mozilla (registered trademark)”, “Mozilla (registered trademark)”, “mozilla / 5 (registered trademark)”, and “Netscape 6 (registered trademark)”. The terminal type corresponding to is “PC”. The terminal type is not limited to the above, and there may be more types.

  The terminal type “0” indicates that the terminal type cannot be specified. This corresponds to the case where determination is not possible in the determination process in step S4 of FIG. For example, in the case of a request from Internet Explorer (registered trademark), normally, when the terminal type is “PDA”, the Web browser type “MSPIE” is set in the user agent information 365, and when the terminal type is “PC”. In the user agent information 365, the Web browser type “MSIE” is set. However, even when the terminal type is “PDA”, the Web browser type “MSIE” may be set in the user agent information 365. Therefore, since the terminal type corresponding to the Web browser type “MSIE” cannot be specified in advance, “0” is set.

  When the terminal type cannot be specified in this way, a correspondence table as shown in FIG. 13 is referred to. FIG. 13 is a diagram showing a Web browser OS-terminal type correspondence table. In FIG. 13, the Web browser OS-terminal type correspondence table 380 includes items such as the Web browser OS and the terminal type, and the terminal type corresponding to the Web browser OS is managed.

  As the Web browser OS, for example, “Windows 3.1 (registered trademark)”, “Windows 95 (registered trademark)”, “Windows 98 (registered trademark)”, “Windows ME (registered trademark)”, “Windows NT (registered trademark)”, “ "Windows 2000 (registered trademark)", "Windows XP (registered trademark)", "Mac 68K (registered trademark)", "Mac PowerPC (registered trademark)", "Solaris (registered trademark)", "Linux (registered trademark)", " FreeBSD (registered trademark), AIX (registered trademark), IRIX (registered trademark), HP (registered trademark), OS / 2 (registered trademark), Windows CE (registered trademark), etc. Managed.

  Terminal types include “PDA” and “PC”. The mobile phone 42 is included in the terminal type “PDA”. In the Web browser OS-terminal type correspondence table 380 shown in FIG. 13, the terminal type corresponding to the Web browser OS “Windows 3.1 (registered trademark)” to “OS / 2 (registered trademark)” is “PC”. The terminal type corresponding to the browser OS “Windows CE (registered trademark)” is “PDA”.

  Thus, the terminal type can be specified by the Web browser type-terminal type correspondence table 370 and the Web browser OS-terminal type correspondence table 380.

  default. The default HTML output by cgi will be described with reference to FIG. FIG. 14 is a diagram illustrating an example of default HTML output. In FIG. 14, the default HTML 400 is not displayed on the terminal 40, and a script for calling the top page is executed according to the description 401 of JavaScript (registered trademark).

  According to the description 402 indicated by “self.document.cookie =” cookieOnOffchecker = on; path = / ””, information on the Web browser of the terminal 40 is acquired by cookie, and “self.location.pathname =” / pc / admin / The web default application 310 of the web page function 300 is executed by inheriting the terminal type “PC” by the description 403 indicated by “en / webDefaultApl / mainframe.cgi” ”, that is, the mainframe is created by“ mainframe.cgi ”. Request HTML. The description 403 indicates that an absolute path serving as a reference for the relative path specified by the <a href> tag is specified in a series of page transitions performed by the user thereafter.

  When information is provided to the client PC 41 via the Internet 16, the screen is often divided into a plurality of frames. FIG. 14 shows an example of default HTML output in such a case. On the other hand, when the initial screen is displayed without dividing the screen by the frame, for example, the description 403 is described as “self.location.pathname =" / pc / admin / ja / webDefaultApl / topPage.cgi "”. The top page for displaying the information to be provided is set to be called directly.

  Hereinafter, a process of providing information according to the terminal type of the terminal 40 when the screen is divided by frames will be described.

  Thereafter, when page transition is performed, only the relative path information 60b is specified, and therefore the terminal type “PC” included in the common path information 60a is always inherited. That is, a plurality of Web applications 301 refer to the same common path information 60a.

  15 and 16 show mainFrame. It is a figure which shows the processing flow by cgi. In FIG. 15, the terminal 40 requests a main frame HTML (main frame HTML request) (step S31). “/Pc/admin/ja/webDefaultApl/mainFrame.cgi” is designated, and a mainframe HTML request is made by the GET method to which form data is attached.

  The HTTP daemon 2 of the information processing device 100 notifies the sequence control library 110 of the HTTP connection information 340 and the hash list (step S32).

  In this case, “GET” is set in the request method of the HTTP request information 350 associated with the HTTP connection information 340 by the HTTP daemon 2, and “/pc/admin/ja/webDefaultApl/mainFrame.cgi” is set in the URL 354 of the request. Is specified. With this designation, when a request is received from the terminal 40 by a relative path thereafter, the common path information 60a indicating “/ pc / admin / ja” can be referred to. Therefore, it can be seen that the terminal type of the terminal 40 is “PC”. Further, the received form data is set in the hash list by the HTTP daemon 2.

  The sequence control library 110 calls the web application distribution common library 120 (step S33). At this time, the sequence control library 110 sets HTTP connection information indicating information related to connection with the terminal 40 and a hash list as arguments.

  Based on the URL, the web application distribution common library 120 specifies and calls the default handler 210 (“default_handler”) from the hash list 50a as the web page handler 200 corresponding to the web application ID 64 indicating “webDefaultApl” (step) S34).

  In the Web page handler 200, the default handler 210 acquires the page information 65 indicating “mainFrame.cgi” from the URL, and the mainframe () function from the hash list 50b as the Web page function 300 corresponding to the “mainFrame.cgi”. Is specified and called (step S35). At this time, HTTP connection information is set as an argument. For example, when the web page function 300 is developed in C language, the web page handler 200 converts to a C language processing type and calls the mainFrame () function.

  By executing the mainFrame () function, frame information constituting the initial screen (topPage.cgi) is created (step S36). The frame information is notified as processing result data to the default handler 210 in the Web page handler 200 (step S37).

  Hereinafter, the serialization process described in XML in steps S38, S39, S40, S41, and S42 is the same as the process in steps S18, S19, S20, S21, and S22, and thus description thereof is omitted.

  The web application distribution common library 120 refers to the hash list 50b and displays “mainFrame.cgi” page information in order to convert display data described in XML into HTML description corresponding to the type of the terminal 40. The style sheet “mainFrame.xsl” corresponding to 56 is acquired, and an XSL conversion request is made to the XSLT processor 205 (step S43). At this time, the display data “Response DOM” and the style sheet “mainFrame.xsl” are set as arguments.

  Upon receiving the XSL conversion request, the XSLT processor 205 executes the style sheet “mainFrame.xsl” specified by the argument, selects a template according to the terminal type from the description of the style sheet, and displays the description described in XML. The syntax of the data “Response DOM” is analyzed (XML parsing), a DOM is created, elements and attributes are added (step S44), and converted into an HTML description by the XML library (step S45). When the terminal type information 63a indicates “PC”, HTML that divides the screen into a plurality of screens by a frame is output. On the other hand, when the terminal type information 63a indicates “PDA”, HTML in which JavaScript (registered trademark) for directly calling the top page is described is output.

  The XSLT processor 205 notifies the Web application distribution common library 120 of the converted HTML description as an XSL conversion result (step S46).

  The processing result described in HTML by the Web page function 300 when the page information 65 is “mainFrame.cgi” is output to the Web application distribution common library 120 as the main frame HTML. In mainframe HTML, “menuPage.cgi” is called from the frame constituting the menu page, “topPage.cgi” is called from the frame constituting the top page, and “headerPage.cgi” is called from the frame constituting the header page. Is written in HTML so that “

  The mainframe HTML response is sequentially notified from the web application distribution common library 120 to the sequence control library 110 (step S47), and is notified from the sequence control library 110 to the HTTP daemon 2 (step S48). Then, the HTTP daemon 2 transmits a main frame HTML response as a response to the request of the terminal 40 in step S31 according to HTTP (step S49), and the processing flow executed by mainFrame.cgi is terminated.

  MainFrame. When the terminal 40 is the client PC 41. The main frame HTML output by cgi will be described with reference to FIG. FIG. 17 is a diagram illustrating an example of mainframe HTML output for a PC. In FIG. 17, the main frame HTML 410 creates three frames on the Web browser of the terminal 40 based on the description 411, and calls a page from each <frame> tag with CGI.

The description 412 indicated by <frame noresize src = "/ webDefaultApl / headerPage.cgi" name = "header" marginheight = "0" marginwidth = "0" scrolling = "no"> displays the header page in the frame. According to the description 413 indicated by “/webDefaultApl/headerPage.cgi”,
The default handler 210 is executed based on “webDefaultApl”, the headerPage () function of the web default application 310 is executed based on “headerPage.cgi”, and the header page is displayed in the frame.

  The description 414 indicated by <frame src = "/ webDefaultApl / menuPage.cgi" name = "menu" marginheight = "0" marginwidth = "0" scrolling = "auto"> displays a menu page in the frame. According to the description 415 indicated by “/webDefaultApl/menuPage.cgi”, the default handler 210 is executed based on “webDefaultApl”, the menuPage () function of the Web default application 310 is executed based on “menuPage.cgi”, and the menu page Is displayed in the frame.

  Further, description 416 indicated by <frame src = "/ webDefaultApl / topPage.cgi" name = "top" marginheight = "0" marginwidth = "0" scrolling = "auto"> displays the top page in the frame. . According to the description 417 indicated by “/webDefaultApl/topPage.cgi”, the default handler 210 is executed based on “webDefaultApl”, the topPage () function of the Web default application 310 is executed based on “topPage.cgi”, and the top The page is displayed in the frame.

  Since the descriptions 412, 414, and 416 only specify the relative path information 60b, the common path information 60a is specified by the URL.

  In FIG. 17, when the terminal 40 is the cellular phone 42 or the PDA terminal 43, the topPage. It is configured to call only cgi. For example, the description of HTML is the same as the default HTML output shown in FIG. 14, but instead of jumpToMainFrame () Direct topPage. A jumpToTopPage () that calls cgi is used.

  18 and 19 show topPage. It is a figure which shows the processing flow by cgi. 18, the terminal 40 requests HTML for displaying the status of the plotter 35-1 or the scanner 35-2 provided in the information processing apparatus 100 (top page HTML request) (step S51). “TopPage.cgi” is designated, and a top page HTML request is made by the GET method to which form data is attached.

  The HTTP daemon 2 of the information processing device 100 notifies the sequence control library 110 of the HTTP connection information 340 and the hash list (step S52). In this case, “GET” is set in the request method of the HTTP request information 350 associated with the HTTP connection information 340 by the HTTP daemon 2, and “topPage.cgi” is specified in the URL of the request. The HTTP daemon 2 sets the received form data in the hash list.

  The sequence control library 110 calls the web application distribution common library 120 (step S53). At this time, the sequence control library 110 sets HTTP connection information 340 indicating information related to the connection with the terminal 40 and a hash list as arguments.

  Based on the URL, the Web application distribution common library 120 specifies and calls the default handler 210 (“default_handler”) from the hash list 50a as the Web page handler 200 corresponding to the Web application ID 64 indicating “webDefaultApl” (step) S54).

  In the Web page handler 200, the default handler 210 acquires the page information 65 indicating “topPage.cgi” from the URL, and the topPage () function from the hash list 50 b as the Web page function 300 corresponding to the “topPage.cgi”. Is specified and called (step S55). At this time, HTTP connection information 340 is set as an argument. For example, when the web page function 300 is developed in C language, the web page handler 200 converts to a C language processing type and calls the topPage () function.

  By executing the topPage () function, the Web default application 310 displays the status of the device (for example, the plotter 35-1 as a printer) on the initial screen (topPage.cgi), via the network control unit 101 via the API 17. In response to the request, information such as a device name and a comment is requested (step S56-2). In response to the request, the network control unit 101 notifies information such as a device name and a comment (step S56-4).

  The web default application 310 of the web page function 300 requests, for example, the printer status to the printer control unit 103 via the API 17 (printer status request) (step S56-6). The printer control unit 103 notifies the web default application 310 of the state of the plotter 35-1 as a printer status (step S56-8).

  Then, the Web default application 310 uses the printer status, the request type URL 345 of the HTTP request information 350, the terminal type information 63a, the profile information 63b, and the language information 63c as processing result data as defaults in the Web page handler 200. The handler 210 is notified (step S57).

  Hereinafter, the serialization processing described in XML in steps S58, S59, S60, S61, and S62 is the same as the processing in steps S18, S19, S20, S21, and S22, and thus description thereof is omitted.

  The web application distribution common library 120 refers to the hash list 50b and displays “topPage.cgi” page information in order to convert display data described in XML into HTML description corresponding to the type of the terminal 40. The style sheet “topPage.xsl” corresponding to 56 is acquired, and an XSL conversion request is made to the XSLT processor 205 (step S63). At this time, the display data “Response DOM” and the style sheet “topPage.xsl” are set as arguments.

  Upon receiving the XSL conversion request, the XSLT processor 205 executes the style sheet “topPage.xsl” specified by the argument to select a template corresponding to the terminal type from the description of the style sheet, and displays the description described in XML The syntax of the data “Response DOM” is analyzed (XML parsing), a DOM is created, elements and attributes are added (step S64), and converted into an HTML description by the XML library (step S65).

  The XSLT processor 205 notifies the Web application distribution common library 120 of the converted HTML description as an XSL conversion result (step S66).

  The processing result described in HTML by the Web page function 300 when the page information 65 is “topPage.cgi” is output to the Web application distribution common library 120 as the top page HTML. In the top page HTML, information related to the state of the plotter 35-1 is described in HTML.

  The top page HTML response is notified from the web application distribution common library 120 to the sequence control library 110 (step S67), and is notified from the sequence control library 110 to the HTTP daemon 2 (step S68). Then, the HTTP daemon 2 transmits a top page HTML response as a response to the request from the terminal 40 in step S51 in accordance with HTTP (step S69), and the processing flow executed by topPage.cgi ends.

  When the terminal 40 is the client PC 41, similarly to the above, processing by HeaderPage.cgi and menuPage.cgi called from each frame is executed, and a screen divided by the frame is displayed on the Web browser of the client PC 41. On the other hand, when the terminal 40 is the mobile phone 42 or the PDA terminal 43, since the screen is not divided by the frame, only the top page is displayed on one screen.

  A processing result described in XML will be described. FIG. 20 shows topPage. It is a figure which shows the example of the process result by cgi.

  In the XML 420 shown in FIG. 20, the processing result by the topPage () function of the Web default application 310 is shown by a description 421 shown from <networkResponse> to </ networkResponse>. A description 422 indicated by <terminal> pc </ terminal> indicates that the terminal 40 is the client PC 41, and a description 423 indicated by <language> ja </ language> indicates that the language of the Web browser of the terminal 40 is Japanese. The description 424 indicated by <profile> admin </ profile> indicates that the user of the terminal 40 is an administrator. Descriptions 422 to 424 are information based on the terminal type information 63a, the profile information 63b, and the language information 63c of the URL common path information 60a.

  A description 425 indicated by <deviceName> Printer 1 </ deviceName> indicates that the device name is “Printer 1”. A description 426 indicated by <comment> XXXXXXXXX </ comment> indicates that the comment regarding “Printer 1” is “XXXXXXXXX”. A description 427 indicated by <status> Ready </ status> indicates that the status of “Printer 1” is “normal”.

  Since the web page handler 200 has a function to describe and serialize processing result data by the web page function 300 in XML, each web application 301 of the web page function 300 needs to have a processing unit corresponding to each terminal type. There is no.

  A style sheet for converting the serialized processing result data described in XML into HTML based on the terminal type will be described with reference to FIG. FIG. 21 is a diagram illustrating a description example of XSL for converting the processing result from XML to HTML.

  In the XSL 430 shown in FIG. 21, whether or not the character string “pda” is included in the element enclosed by the <terminal> tag shown in the description 422 of the XML 420 in FIG. It is determined whether or not the processing result is for a PDA terminal. When the character string “pda” is included, the template for the PDA terminal is applied according to the description 432, and when the character string “pda” is not included, the template for the general PC is applied according to the description 433. . A description 434 describes a template for a PDA terminal, and a description 435 describes a template for a general PC. Each template is not described in detail in the figure.

  For example, in the description 434 describing the template for the PDA terminal, a font size smaller than that of the PC is specified in consideration of the display screen size of the cellular phone 42 or the PDA terminal 43, and the image displayed for the PC is not displayed. To specify the number of characters smaller than that of the PC.

  Since the Web application distribution common library 120 has a function of converting XML into HTML by XSL, it is possible to create HTML according to the terminal type in a unified manner. Therefore, each Web application 301 in the Web page function 300 does not need to have a processing unit corresponding to the terminal type.

  In this way, by preparing XSL for converting from XML to HTML according to each Web application 301 in advance, HTML indicating each processing result is provided to the terminal 40, and the processing result is displayed by the Web browser of the terminal 40. Is displayed.

  When the terminal 40 is the client PC 41, HTML indicating the processing result of the topPage () function of the Web default application 310 is described as shown in FIG. 22, for example. FIG. 22 shows topPage. It is a figure which shows the example of description of HTML for PC which shows the process result of cgi. In FIG. 22, the PC HTML 440 is provided when the terminal 40 is the client PC 41, and the processing result of the topPage () function of the Web default application 310 is displayed on the Web browser of the client PC 41 by the description 441.

  A description 442 indicating <font size = "4"> system status </ font> indicates that "system status" is displayed in font size 4. A description 443 indicating <img src = "printer.gif"> indicates that an image is displayed. A description 445 indicating <p> system name: Printer 1 </ p> indicates that “system name: Printer 1” is displayed, and a description 446 indicating <p> comment: XXXXXXXXX </ p> is “comment : XXXXXXXXX ”is displayed, and a description 447 indicating <p> system state: normal </ p> indicates that“ system state: normal ”is displayed.

  Such a PC HTML 440 displays a screen as shown in FIG. 23 on the Web browser of the client PC 41. FIG. 23 is a diagram showing a display example of the system status on the client PC. In FIG. 23, mainFrame. The screen 450 is composed of three frames by cgi, and each page includes headerPage. cgi displays the header page, menuPage. The menu page is displayed by cgi, and topPage. The top page is displayed by cgi.

  On the top page, a text 452 indicating “system status” is displayed by the description 442 of HTML 240 shown in FIG. 22, an image 454 is displayed by the description 444, and a text 455 indicating “system name: Printer 1” is displayed by the description 445. The text 456 indicating “comment: XXXXXXXXX” is displayed by the description 446, and the text 457 indicating “system state: normal” is displayed by the description 447.

  In addition, in the frame for displaying the header page, for example, information as a header such as “AAAAAAA” is displayed. In the frame that displays the menu page, for example, text 459 such as “system status”, “network setting”, and “apparatus configuration information” is displayed as selectable menu items.

  The HTML description of “network setting” is described as, for example, <p> <a href="../webNetsettingApl/netsetting.cgi" target="top"> network setting </a> </ p> The Since only the relative path information 60b is set in this URL, the common path information 60a is inherited as it is, and information related to “network setting” is displayed on the top page for the PC. That is, “webNetsettingApl” indicating the Web application ID is set as a relative path, and the current terminal type information 53a is inherited by the description of “../”. In addition, information regarding “network setting” is displayed on the top page for the PC by the description of “target =“ top ””.

  Similarly, HTML description of “device configuration information” is as follows: <p> <a href="../webSysconfigApl/sysconfig.cgi" target="top"> device configuration information </a> </ p> Described in Therefore, since only the relative path information 60b is set in this URL, the common path information 60a is inherited as it is, and information related to “device configuration information” is displayed on the top page for the PC.

  When the client PC 41 requests information from the information processing apparatus 100 according to the present invention, a screen 450 is displayed. When the mobile phone 42 or the PDA terminal 43 requests the same information, it is shown in FIG. Such an HTML for a PDA terminal is created, and a screen as shown in FIG. 25 is displayed on the PDA terminal 43.

  FIG. 24 shows topPage. It is a figure which shows the example of description of HTML for PDA terminals which shows the processing result of cgi. In FIG. 24, the HTML 440a for the PDA terminal is provided when the terminal 40 is the PDA terminal 43, and the processing result of the topPage () function of the Web default application 310 is displayed on the Web browser of the PDA terminal 43 by the description 441a.

  A description 442a indicating <font size = "3"> system status </ font> indicates that "system status" is displayed in font size 3. In the description 442a, a small character font is set for the PDA terminal 43.

  There is no description corresponding to the description 443 of the HTML 440 for the PC in the HTML 440a for the PDA terminal.

  Similar to the descriptions 445 and 446 of the HTML 440 for PC, the description 445a indicating <p> system name: Printer 1 </ p> indicates that “system name: Printer 1” is displayed, and <p> comment: A description 446 a indicating XXXXXXXXX </ p> indicates that “comment: XXXXXXXXX” is displayed.

  The PDA terminal 43 having a display area smaller than that of the client PC 41 displays, for example, “status: normal” instead of “system status: normal” in the description 447a corresponding to the description 447 of the HTML 440 for PC. Display with fewer display characters.

  Further, since it is not appropriate to divide the screen into a plurality of frames in the PDA terminal 43, it is necessary to display information displayed in other frames in the client PC 41 in one screen (page) in the PDA terminal 43. . The description 448a is described in HTML for displaying a menu page for a PC. In the HTML 440a for a PDA terminal, <p> <a href="../webNetsettingApl/netsetting.cgi"> network setting <// a> </ p> and <p> <a href="../webSysconfigApl/sysconfig.cgi"> Device configuration information </a> </ p> and displayed on the menu page of the client PC 41 Of the selectable items, “network setting” and “device configuration information” are displayed. In the description 448a, in the PC HTML 440, the frame to be displayed is specified by target = "top", but the description is deleted.

  With such an HTML 440a for PDA terminals, a screen as shown in FIG. 25 is displayed on the Web browser of the PDA terminal 43. FIG. 25 is a diagram showing a display example of the system status on the PDA. In FIG. 25, a screen 450a is composed of one screen that is not divided by frames.

  On the screen 450a, the text 452a indicating "system status" is displayed by the description 442a of the HTML 240a shown in FIG. Is displayed. The description 446a displays the text 456a indicating “comment: XXXXXXXXX”, and the description 447a displays the text 457a indicating “status: normal” with fewer characters than the client PC 41.

  In the client PC 41, selectable “network settings” and “device configuration information” displayed on the menu page are displayed as text 458a indicating “network settings” and “device configuration information” that can be selected by the description 448a.

  When the user of the PDA terminal 43 selects “network setting” while the screen 450a is displayed on the mobile terminal 42 or the PDA terminal 43, the common path information 60a is inherited and only the relative path information 60b indicates “network setting”. Since the URL is changed, a screen as shown in FIG. 26 is displayed on the portable terminal 42 or the PDA terminal 43. FIG. 26 is a diagram showing a display example of network settings on the PDA terminal.

  In FIG. 26, a screen 460a is a screen that is displayed after a page transition from the screen 450a, and since the common path information 60a is inherited at the time of the page transition, according to the size of the display screen of the mobile terminal 42 or the PDA terminal 43. The “Network Settings” page will be displayed. The user of the portable terminal 42 or the PDA terminal 43 does not make any setting for displaying the “network setting” page according to the size of the display screen.

  When a page transition is performed on an information processing apparatus in which the terminal type of the terminal 40 is not identified, a display corresponding to the size of the display screen on the client PC 41 is performed. It will be offered. Since the terminal type information 53a is not inherited, the terminal type information 53a is not displayed in too large characters, and information suitable for the display screen of the mobile terminal 42 or the PDA terminal 43 cannot be provided.

  According to the present invention, when the HTTP daemon 2 receives the first request from the terminal 40, the default. In order to construct the URL to call cgi, default. The URL having the common path information 60a can be automatically set by the information processing apparatus 100 by cgi. Therefore, the user of the terminal 40 does not need to input information with the display screen in mind.

  Since the common path information 60a is configured before the relative path information 60b, the link from the page only needs to specify the relative path, and the creation of HTML can be facilitated.

  Further, the information processing apparatus 100 performs conversion from XML to HTML based on the terminal type information 53a of the common path information 60a using the style sheet. Therefore, in the information processing apparatus 100, the developer of the Web application 301 does not need to develop an application in consideration of the terminal type, and the burden on the developer can be reduced. That is, each Web application 301 can output a unified processing result without depending on a difference in terminal type. For example, the difference in the size of the display screen, the division of the display screen by frames, and the like do not affect the development of the Web application 301.

  In the above embodiment, the client PC 41 is classified as “PC” and the mobile phone 42 and the PDA terminal 43 are classified as “PDA” as the terminal type. However, it is only necessary to be able to classify according to the display screen. In addition to “PDA”, there may be more terminal types. Further, the classification may be any classification according to the characteristics of the display screen.

  The present invention can also be applied to a case where a huge screen is connected to the information processing apparatus 100 as the terminal 40. That is, according to a huge screen, it is possible to change the characters greatly, or to increase the amount of information by increasing the number of characters. In addition, a larger image or a plurality of images can be displayed to effectively provide information.

  In order to provide such information according to the terminal 40, the information processing apparatus 100 according to the present invention uses the template according to the terminal type of each style sheet 430 to display the processing result provided from the Web page function 300. The display format is adjusted and images are added.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims.

2 HTTP daemon 16 Internet 17 API
40 terminals 41 client PC
42 Cellular phone 43 PDA
DESCRIPTION OF SYMBOLS 100 Information processing apparatus 101 Network control part 103 Printer control part 105 Scanner control part 110 Sequence control library 120 Web application distribution common library 200 Web page handler 201 SOAP library 203 XML library 205 XSLT processor 300 Web page function (WPF)

Japanese Patent Laid-Open No. 11-175515 JP 2002-23108 A JP 2002-7095 A JP-A-11-306070

Claims (5)

A communication means for receiving connection information from a terminal connected via a network;
If the URL included in the connection information is composed of common path information including the terminal type information of the terminal and relative path information designating processing for obtaining predetermined information following the common path information, , the scanner, and then calls the function corresponding to said relative path information by executing the processing among a plurality of functions for processing related to network, a processing result obtained by the processing is output based on the common path information Web page generation means for generating a generated Web page;
An information processing apparatus comprising: The information processing apparatus includes URL creation means for identifying information for creating common path information from the connection information, setting information for creating the common path information in the common path information of the URL, and creating a URL.
If the URL included in the connection information is a request that does not include common path information used for the function corresponding to the relative path information, the URL creation means specifies information for creating common path information from the connection information. 2. The information processing apparatus according to claim 1, wherein the URL is set in the common path information of the URL, and the terminal is made to access the set URL. The information processing apparatus further includes a plurality of applications having at least one of the plurality of functions and performing the processing relating to the plotter, scanner, and network ,
The relative path information includes application ID information for specifying the application and page information for specifying the function in the specified application.
When the Web page generation unit generates link information across other applications on the Web page to be created, the Web page generation unit configures the link information with static relative path information, thereby the common path information and the relative path information. The information processing apparatus according to claim 1, wherein the terminal is made to access a URL consisting of: A plurality of handler means for calling the function with the function name corresponding to the page information of the URL by referring to the first correspondence list in which the page information and the function name to be called are associated with each other. With
The plurality of handler means are provided corresponding to each of the plurality of applications,
The Web page generation means refers to the second correspondence list in which the application ID information and the handler name that identifies the handler means are associated with each other, so that the handler name is the handler name corresponding to the application ID information of the URL. 4. The information processing apparatus according to claim 3, wherein said means is called using said common path information. An information processing method in an information processing apparatus for providing a Web page to a terminal in response to a request from a terminal connected via a network,
The information processing apparatus is
A communication procedure for receiving connection information from a terminal connected via a network;
If the URL included in the connection information is composed of common path information including the terminal type information of the terminal and relative path information designating processing for obtaining predetermined information following the common path information, , the scanner, and among the plurality of functions for processing related to network, by calling the function corresponding to said relative path information to execute the processing, outputting a processing result obtained by the processing based on the common path information A Web page generation procedure for generating the Web page,
The information processing method characterized by performing.

Images