Ignition control device, ignition control method, ignition control program, client terminal, and ignition control system

Abstract

According to an ignition control device of the present invention, when a URL of a Web page is specified and a request is transmitted from a client terminal 90, a response is returned to the client terminal 90 and an ignition control function 10A is executed. The ignition control function 10A includes: a status acquisition unit 11 that acquires a status from the client terminal 90; and a tag control unit 12 that enables a tag in the Web page specified by the request according to the status. Accordingly, only a tag for which consent is confirmed from the status stored in the client terminal 90 is enabled, and a tag of a non-consented service can be reliably prevented from using personal information such as cookie.

Description

Ignition control device, ignition control method, ignition control program, client terminal, and ignition control system

[0001] The present invention relates to an ignition control device, an ignition control method, an ignition control program, a client terminal, and an ignition control system.

[0002] Information processing devices are known that are configured to not accept operations on operation screens provided on a domain until consent for the use of cookies requested in response to access to the domain is obtained (see, for example, Patent Document 1). However, such information processing devices merely do not accept operations; the script is loaded when the response is received, so there is a risk that the tag will fire between the time of receipt and the time of user consent, and the cookie will be used before consent is given. [Prior Art Documents] [Patent Documents] [Patent Document 1] Japanese Patent Application Publication No. 2023-170155 General disclosure

[0003] (Item 1) The ignition control device may be an ignition control device that, when a request is sent from a client terminal specifying the URL of a web page, sends a response back to the client terminal and executes an ignition control function. The ignition control device may include a status acquisition unit that acquires a status from the client terminal. The ignition control device may include a tag control unit that activates the tags in the web page specified by the request according to the status. (Item 2) The status may be information that associates service identification information with whether or not the use of the service is permitted. (Item 3) The tag control unit may query a tag information database with the service identification information for which use is permitted, acquire the tag identification information corresponding to the service for which use is permitted, and activate the tag identified by the tag identification information. (Item 4) The ignition control device may further include a tag information management unit that manages the tag information database. (Item 5) The tags may be disabled by default. (Item 6) The tag control unit may activate the tags by editing the attributes of the tags.

[0004] (Item 7) The client terminal may implement a firing control function. The client terminal may include a status acquisition unit that acquires the status of the client terminal when receiving a response from the server. The client terminal may include a tag control unit that enables tags in a Web page within the response according to the status.

[0005] (Item 8) The firing control system may include the firing control device according to any one of Items 1 to 6, and the client terminal according to Item 7, which receives and executes a firing control program from the firing control device to execute a firing control function.

[0006] (Item 9) The firing control method may be executed by one or more computers. The firing control method may include a step of acquiring the status of the client terminal when receiving a response from the server. The firing control method may include a step of enabling tags in a Web page within the response according to the status. (Item 10) The status may be information associating specific information of a service with the presence or absence of permission to use the service. (Item 11) In the enabling step, the tag information database may be queried with the specific information of the service permitted to be used to obtain the specific information of the tag corresponding to the service permitted to be used, and the tag specified by the specific information of the tag may be enabled. (Item 12) The tag may be disabled by default. (Item 13) In the enabling step, the tag may be enabled by editing the attribute of the tag.

[0007] (Item 14) The firing control program may cause a computer to execute the firing control method according to any one of Items 9 to 13.

[0008] (Item 15) The firing control system may include a firing control device that, when a request is sent from a client terminal specifying the URL of a web page, sends a response back to the client terminal and executes the firing control function. The firing control system may include a client terminal that executes the firing control function by receiving and executing a firing control program from the firing control device. The firing control function may include a status acquisition function that acquires a status from the client terminal, and a tag control function that activates the tags in the web page specified by the request according to the status. (Item 16) The status may be information that associates service identification information with whether or not the use of the service is permitted. (Item 17) The tag control function may query a tag information database with the service identification information for which use is permitted, acquire the tag identification information corresponding to the service for which use is permitted, and activate the tag identified by the tag identification information. (Item 18) The tag may be disabled by default. (Item 19) The tag control function may activate the tag by editing the attributes of the tag.

[0009] (Item 20) The ignition control method may include a step in which the ignition control device receives a request from a client terminal specifying the URL of a web page, and in response to the client terminal, sends a response to the client terminal to execute the ignition control function. The ignition control method may also include a step in which the client terminal executes the ignition control function by receiving and executing an ignition control program from the ignition control device. The ignition control function may include a status acquisition function that acquires a status from the client terminal, and a tag control function that activates the tags in the web page specified by the request according to the status.

[0010] (Item 21) The program may cause the computer to execute a procedure to send a response back to the client terminal and execute a firing control function in response to receiving a request from the client terminal specifying the URL of a web page. The firing control function may include a status acquisition function that obtains a status from the client terminal, and a tag control function that enables the tags in the web page specified by the request according to the status.

[0011] (Item 22) The firing control program may cause the computer to perform a procedure to obtain the status of the client terminal when it receives a response from the server. Depending on the status, the computer may perform a procedure to enable tags in the web page in the response.

[0012] It should be noted that the above summary of the invention does not enumerate all of its features. Furthermore, subcombinations of these features may also constitute an invention.

[0013] This document outlines the configuration of the ignition control system according to this embodiment. It also shows the functional configuration of the ignition control device, an example of registered information in the tag information database, an example of a disabled tag, another example of a disabled tag, yet another example of a disabled tag, another example of a disabled tag, an example of an enabled tag, the ignition control flow, and an example of the computer configuration.

[0014] The present invention will be described below through embodiments, but these embodiments are not intended to limit the scope of the claims. Furthermore, not all combinations of features described in the embodiments are necessarily essential to the solution of the invention.

[0015] Figure 1 shows a schematic configuration of the fire control system 1 according to this embodiment. The fire control system 1 (also simply called system 1) is a network system for activating invalidated tags in the response sent back from the server 50 to the client terminal 90 according to the user status obtained from the client terminal 90. System 1 includes a fire control device 10. System 1 may further include a tag information database (DB) 20. These are connected to each other so as to be able to communicate via the network 99. Although the fire control device 10 is shown as part of the server 50, as will be described later, at least a part of the functional unit of the fire control device 10 (fire control function 10A) is transmitted to the client terminal 90 and executed on the client terminal 90. The database is also referred to as DB.

[0016] Network 99 is a communication network that connects the ignition control device 10 and various databases such as the tag information database 20 in a manner that enables them to communicate with each other. Network 99 is, for example, the Internet, but is not limited to this. Any communication network that enables communication between these devices and databases may be used, such as a local area network or telephone line, or a network in which multiple communication networks coexist.

[0017] The server 50 is a server that operates the website accessed by the client terminal 90. The server 50 may include all or part of the ignition control device 10, which will be described later.

[0018] The client terminal 90 is, for example, a terminal device used by a user. The terminal device may be a computer terminal such as a personal computer, or a mobile terminal such as a smartphone or tablet computer. The client terminal 90 has a central processing unit (CPU) and a communication device (neither of which are shown). The CPU receives a response from the server 50 and executes the ignition control program (script) contained therein, thereby allowing the client terminal 90 to perform some or all of the functions of the ignition control device 10. The communication device is capable of communicating with the server 50 and various databases via a network 99, either by wired or wireless communication, and can, for example, communicate using a protocol such as TCP / IP. The client terminal 90 is equipped with a display 91 such as a liquid crystal display and functions as a client terminal that communicates with the server 50 to display web pages, etc., on the display 91. Multiple client terminals 90, each owned by multiple users, may be included in the system 1, allowing multiple users to utilize the system 1.

[0019] The fire control device 10 is a computer device that, when a request is sent from the client terminal 90 specifying a web page URL, sends a response back to the client terminal 90 and executes the fire control function 10A. The fire control device 10 has a central processing unit (CPU) and a communication device (neither of which are shown in the diagram). The fire control device 10 may also be implemented using a cloud (multiple distributed servers or multiple subsystems, etc.). When the CPU receives a request from the client terminal 90, it executes a dedicated program and sends a response containing a fire control program (script) to the client terminal 90, causing the client terminal 90 to execute it and thereby activate the fire control function 10A. The functional configuration of the fire control device 10 will be described later. The dedicated program may be stored in ROM (not shown) and read by the CPU, or stored in a storage medium such as a CD-ROM and read by the CPU using a reader (not shown) to activate it. The ignition control program can be read from ROM (not shown) or the like, sent to the client terminal 90, and loaded into RAM, thereby being started on the client terminal 90. The ignition control program may be a script such as JavaScript (registered trademark) included in a web page. The communication device is a device that can communicate with the server 50, the client terminal 90, and various databases via wired or wireless communication over the network 99, and can communicate using protocols such as TCP / IP as an example.

[0020] Figure 2 shows the functional configuration of the ignition control device 10. The ignition control device 10 comprises a status acquisition unit 11, a tag control unit 12, and a tag information management unit 13. Of these functional units, the status acquisition unit 11 and the tag control unit 12 are also referred to as the ignition control function 10A. The ignition control function 10A is transmitted from the server 50 to the client terminal 90 and executed on the client terminal 90. For example, the ignition control function 10A is implemented as a script, embedded in a web page, and included in the response from the server 50 and transmitted to the client terminal 90. Executing the ignition control function 10A on the client terminal 90 can reduce the load on the server 50, but it is also possible to configure the ignition control device 10 (server 50) to execute part or all of the ignition control function 10A, i.e., to execute the ignition control function 10A on multiple devices including the ignition control device 10 (server 50) and the client terminal 90.

[0021] The status acquisition unit 11 acquires the status from the storage of the client terminal 90. The status is information that associates service-specific information with whether or not the user has permission to use the service. The status may also include information such as the scope of the permission to use and its expiration date. The status is set by the user via a consent confirmation screen (so-called cookie banner, etc.) and stored in the storage of the client terminal 90. Note that the storage referred to here includes cookies, web storage, etc.

[0022] Cookies are data stored by browsers, and there are two types: persistent cookies and session cookies. Persistent cookies are stored in the storage of the device on which the browser is running for a specified period even after the browser is closed, and are used to retain information such as the contents of the user's shopping cart and language settings. Session cookies are temporary cookies that exist only during the session period and are automatically deleted when the browser is closed, and are used to retain login information when the user moves between pages. Cookies have attributes such as the Name attribute, which is an identifier such as the userPref attribute, the Domain attribute, which manages the domain on which the cookie is valid, the Path attribute, which manages the path on which the cookie is valid, and the Expires / Max-Age attribute, which manages the expiration date (deletion time) of the cookie.

[0023] Web storage refers to APIs for saving data in a browser, and there are two types: local storage and session storage. Local storage is an API for saving data until it is explicitly deleted within the browser. The data is stored in the browser's data storage area and can be retained even if the browser is closed. Data stored in local storage is shared within the same origin. Session storage is an API for saving data within the browser only for the duration of a single session. The data is stored in the memory area allocated by the browser and is deleted when the browser tab is closed. Note that data stored in web storage is also simply referred to as web storage.

[0024] As an example of a status, suppose the client terminal 90 has a cookie with the status "abn_consent=yes; expires=Fri, 22 Oct 2024 12:00:00 UTC; path= / ; domain=example.com". This cookie means that the use of the service identified by the cookie name "abn_consent" is permitted (yes) for the entire site of the domain "example.com" (path= / ), and this permission is valid until 12:00 on October 22, 2024.

[0025] The tag control unit 12 activates the tags in the web page specified by the request, depending on the status. Activating a tag is also referred to as firing the tag. Activation is performed by editing the tag's attributes. Tags that perform external communication in the response received by the client terminal 90, that is, tags in the web page accessed by the user, are disabled by default when the client terminal 90 receives the response. Tags are disabled in a manner that allows them to be activated by editing their attributes; for example, they may be assigned an attribute to disable them. The attribute to disable a tag may be set independently, or existing attributes such as the type attribute may be used. For example, a tag can be disabled by setting the value of the tag's type attribute to a non-standard MIME type such as "text / plain".

[0026] The tag control unit 12 queries the tag information database 20 with the service identification information of the authorized service to obtain the tag identification information corresponding to the authorized service. For example, according to the status obtained by the status acquisition unit 11, "abn_consent=yes; expires=Fri, 22 Oct 2024 12:00:00 UTC; path= / ; domain=example.com", the service identified by "abn_consent" is authorized. The tag information database 20 is then queried with this service identification information.

[0027] Figure 3 shows an example of the registered information in the tag information database 20. The tag information database 20 stores information that associates service identification information (identifier) ​​and service name (service) with the identification information of the tag that calls this service, i.e., the domain where the service is published (domain) and the format information of the unique ID that the service issues to individual sites (extraction_target). For example, if you query the tag information database 20 with the service identification information "abn_consent", the data in the first row, i.e., the identification information of the tag that calls the service named "AB Analytics", is extracted, which is the domain "abtagmanager.com" and the format information of the unique ID "id=ABN-XXXXXXXXXX". Note that X is any alphanumeric character. This makes it possible to identify a unique ID even if it is written in various formats within the tag.

[0028] The tag information management unit 13 manages the tag information database 20. For example, the tag information database 20 is managed by an administrator operating the ignition control device 10 registering, updating, and deleting tag information in response to operations performed through its interface. Service identification information simplifies responses such as updating tag information when the identification information of the tag calling the service is changed on the service side, or adding new services.

[0029] The tag control unit 12 extracts tags from HTML that match the tag identification information, which includes domain and unique ID format information. This allows for tag firing control based on the availability of each service, even when multiple services are published under the same domain, such as the data in the first and second rows, and the third and fourth rows of the tag information database 20 (see Figure 3). Furthermore, not only when multiple services are published under the same domain, but also when a single service changes its operation according to user attributes, etc., by setting categories for each user attribute and assigning an ID to each category, tag firing control can be performed for each category. User attributes, etc., include, for example, age.

[0030] Figure 4 shows an example of a disabled tag. In this example, the script tag is disabled by specifying text / plain for the type attribute 201. The external domain specified by the URL information 202 in the tag's src attribute is "abtagmanager.com", and the site-specific ID information 203 is in the format "id=ABN-XXXXXXXXXX". Therefore, the tag control unit 12 extracts this tag as a target to be enabled (fired) based on the status "abn_consent=yes; expires=Fri, 22 Oct 2024 12:00:00 UTC; path= / ; domain=example.com".

[0031] Figure 5 shows another example of a disabled tag. In this example, the script tag is disabled by specifying text / plain for the type attribute 205. The external domain specified by the URL information 206 is "connect.cd.net", and the site-specific ID information 207 is in the format "cbq('init', 'XXXXXXXXXX')". Therefore, if the status obtained by the status acquisition unit 11 is "cdp_consent=yes; expires=Fri, 22 Oct 2024 12:00:00 UTC; path= / ; domain=example.com", the tag control unit 12 extracts the tag identification information from the third line of the tag information database 20 (see Figure 3) and extracts the script tag in this example as a tag that matches this.

[0032] Figure 6 shows another example of a disabled tag. In this example, the script tag is disabled by specifying text / plain for the type attribute 208. The external domain specified by the URL information 209 is "connect.cd.net", and the site-specific ID information 210 is in the format that matches "appid : 'XXXXXXXXXX'). Therefore, if the status obtained by the status acquisition unit 11 is "cds_consent=yes; expires=Fri, 22 Oct 2024 12:00:00 UTC; path= / ; domain=example.com", the tag control unit 12 extracts the tag identification information from the fourth line of the tag information database 20 (see Figure 3) and extracts the script tag in this example as a tag that matches it.

[0033] Figure 7 shows another example of a disabled tag. In this example, the script tag is disabled by specifying text / plain for the type attribute 211. The external domain specified by the URL information 212 is "tracking.efclarity.com", and the site-specific ID information 213 is in the format "window, document, "efclarity", "script", "XXXXXXXXXX"". Therefore, if the status obtained by the status acquisition unit 11 is "efc_consent=yes; expires=Fri, 22 Oct 2024 12:00:00 UTC; path= / ; domain=example.com", the tag control unit 12 extracts the tag identification information from the 5th line of the tag information database 20 (see Figure 3) and extracts the script tag in this example as a tag that matches this.

[0034] The tag control unit 12 activates the tag identified by the specific information of the acquired tag. For example, if a tag is disabled by setting the value of the type attribute to a non-standard MIME type (see Figure 4), the tag control unit 12 can activate the tag by changing the value of the tag's type attribute to the standard MIME type, "text / javascript (registered trademark)".

[0035] Figure 8 shows an example of an enabled tag. In this example, the disabled script tag (see Figure 4) is enabled by changing the type attribute 204 to text / javascript (registered trademark). This enables the tag, which is disabled by default, only when consent to use the service called by the tag is confirmed, allowing the script within the tag to send cookie information and other data to this service. As a result, it is possible to reliably prevent tags of services to which consent has not been given from using personal information such as cookies.

[0036] According to the ignition control device 10 of this embodiment, when a request is sent from the client terminal 90 specifying the URL of a web page, a response is sent back to the client terminal 90 to execute the ignition control function 10A. The ignition control function 10A includes a status acquisition unit 11 that acquires the status from the client terminal 90, and a tag control unit 12 that activates the tags in the web page specified by the request according to the status. As a result, only tags for which consent has been confirmed from the status stored in the client terminal 90 are activated, and it is possible to reliably prevent tags of services for which consent has not been given from using personal information such as cookies.

[0037] Furthermore, causing the client terminal 90 to execute the ignition control function 10A can be interpreted as the client terminal 90 executing the ignition control program, thereby causing the status acquisition function of the status acquisition unit 11 and the tag control function of the tag control unit 12 to be executed, or the client terminal 90 executing the ignition control program, thereby causing the status acquisition unit 11 and the tag control unit 12 to be implemented in the client terminal 90 and to activate their respective status acquisition and tag control functions.

[0038] In addition, when a user accesses a web page on the client terminal 90, the client terminal 90 sends a request to the server 50 specifying the URL of the web page, the server 50 sends a response back to the client terminal 90, and the client terminal 90 executes the firing control program (script) included in the response, thereby enabling the client terminal 90 to implement some or all of the functions of the firing control device 10 (i.e., the firing control function 10A). In this way, the client terminal includes a status acquisition unit 11 that acquires the status of the client terminal 90 when it receives a response, and a tag control unit 12 that activates the tags in the web page specified by the request according to the status. Receiving a response means, in other words, when the web page is loaded. In addition, when the firing control function 10A is executed on the server 50, the status acquisition unit 11 may acquire the status when the client terminal 90 sends the request.

[0039] The fire control system 1 according to this embodiment comprises a fire control device 10 and a client terminal 90, which receives and executes a fire control program from the fire control device 10 (server 50) to perform the fire control function 10A.

[0040] Figure 9 shows the fire control flow executed by the fire control device 10. The fire control flow is initiated when a user accesses a web page on the client terminal 90, the client terminal 90 sends a request to the server 50 specifying the URL of the web page, the server 50 sends a response back to the client terminal 90, and the client terminal 90 executes the script included in the response, i.e., the fire control function 10A.

[0041] This flow assumes that the status of whether or not the client terminal user allows the service is pre-stored in storage via a consent confirmation screen (a so-called cookie banner). Furthermore, tags that use user information from the site accessed in this flow (generally script tags that perform external communication) are disabled by default.

[0042] In step S11, the ignition control device 10 (status acquisition unit 11) receives a response from the server 50 and acquires the status of the client terminal 90 when loading the page. The status is information that associates service identification information with whether or not permission to use the service is granted. For example, the status acquisition unit 11 acquires the status "abn_consent=yes; expires=Fri, 22 Oct 2024 12:00:00 UTC; path= / ; domain=example.com" from the client terminal 90's cookie because the tag is disabled. Details are as described above.

[0043] In step S12, the ignition control device 10 (tag control unit 12) queries the tag information database 20 with the specific information of the service for which use is permitted, obtains the specific information of the tag corresponding to the service for which use is permitted, and specifies the tag to be activated in the web page based on this specific information. For example, the tag control unit 12 queries the tag information database 20 (see FIG. 3) with the service specific information "abn_consent" obtained from the status "abn_consent=yes; expires=Fri, 22 Oct 2024 12:00:00 UTC; path= / ; domain=example.com", and extracts the domain "abtagmanager.com" and the specific information of the format of the unique ID "id=ABN-XXXXXXXXXX", which is the specific information of the tag for calling the "AB Analytics" service. The ignition control function 10A (tag control unit 12) specifies the tag (see the script tag in FIG. 4) in the web page that matches this specific information, that is, the tag whose URL information 202 includes the domain "abtagmanager.com" and the format of the unique ID information 203 matches the format information "id=ABN-XXXXXXXXXX". The details are as described above.

[0044] In step S13, the ignition control device 10 (tag control unit 12) activates the tag in the web page specified by the request according to the status. The activation is performed by editing the attributes of the tag. For example, as shown in FIG. 8, the tag control unit 12 activates this tag by changing the type attribute of the tag specified in step S12 to text / javascript (registered trademark). The details are as described above. The tag can use cookies, etc. only after being activated by the user's consent. This can reliably prevent the use of personal information such as cookies by the site before consent.

[0045] The trigger control method of this embodiment, which is executed by one or more computers, includes the steps of: obtaining the status of the client terminal 90 when receiving a response from the server 50 and loading the page; and activating the tags in the web page specified by the request according to the status. This ensures that only tags for which consent has been confirmed from the status stored in the client terminal 90 are activated, thereby reliably preventing tags of services for which consent has not been given from using personal information such as cookies.

[0046] Various embodiments of the present invention may be described with reference to flowcharts and block diagrams, where a block may represent (1) a stage in a process in which an operation is performed, or (2) a section of a device having the role of performing the operation. Specific stages and sections may be implemented by dedicated circuits, programmable circuits supplied with computer-readable instructions stored on a computer-readable medium, and / or processors supplied with computer-readable instructions stored on a computer-readable medium. Dedicated circuits may include digital and / or analog hardware circuits, and may include integrated circuits (ICs) and / or discrete circuits. Programmable circuits may include reconfigurable hardware circuits, including logical AND, logical OR, logical XOR, logical NAND, logical NOR, and other logic operations, flip-flops, registers, memory elements such as field-programmable gate arrays (FPGAs), programmable logic arrays (PLAs), etc.

[0047] A computer-readable medium may include any tangible device that can store instructions executable by a suitable device. As a result, a computer-readable medium having instructions stored therein will comprise a product that includes instructions that can be executed to create means for performing the operations specified in a flowchart or block diagram. Examples of computer-readable media may include electronic memory media, magnetic memory media, optical memory media, electromagnetic memory media, semiconductor memory media, and the like. More specific examples of computer-readable media may include floppy (registered trademark) disks, diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), electrically erasable programmable read-only memory (EEPROM), static random access memory (SRAM), compact disc read-only memory (CD-ROM), digital versatile disc (DVD), Blu-ray (registered trademark) disc, memory stick, integrated circuit card, and the like.

[0048] Computer-readable instructions may include any combination of one or more programming languages, including assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, or source code or object code written in any combination of object-oriented programming languages such as Smalltalk (registered trademark), JAVA (registered trademark), C++ and the like, and conventional procedural programming languages such as the "C" programming language or similar programming languages.

[0049] Computer-readable instructions are provided locally or via a wide area network (WAN) such as a local area network (LAN) or the internet to the processor or programmable circuit of a programmable data processing device such as a computer, and may be executed to create means for performing operations specified in a flowchart or block diagram. Here, the computer may be a PC (personal computer), tablet computer, smartphone, workstation, server computer, general-purpose computer, or special-purpose computer, and may also be a computer system in which multiple computers are connected. Such a computer system in which multiple computers are connected is also called a distributed computing system and is a computer in a broad sense. In a distributed computing system, multiple computers execute a program collectively by each computer executing a part of the program and passing data during program execution between computers as needed.

[0050] Examples of processors include computer processors, central processing units (CPUs), processing units, microprocessors, digital signal processors, controllers, and microcontrollers. A computer may have one or more processors. In a multiprocessor system with multiple processors, each processor executes a portion of the program, and the processors collectively execute the program by passing program execution data between them as needed. For example, in the execution of multitasks, each of the multiple processors may execute a portion of each task in small chunks by switching tasks at each time slice. In this case, which part of a program each processor executes changes dynamically. Which part of a program each of the multiple processors executes may also be statically determined by multiprocessor-aware programming.

[0051] Figure 10 shows an example of a computer 1200 in which multiple aspects of the present invention may be embodied in whole or in part. A program installed on the computer 1200 can cause the computer 1200 to function as an operation or one or more sections of an apparatus according to an embodiment of the present invention, or to execute such operation or one or more sections, and / or to cause the computer 1200 to execute a process or a stage of such process according to an embodiment of the present invention. Such a program may be executed by the CPU 1212 to cause the computer 1200 to perform a particular operation associated with some or all of the blocks in the flowcharts and block diagrams described herein.

[0052] The computer 1200 according to this embodiment includes a CPU 1212, RAM 1214, a graphics controller 1216, and a display device 1218, which are interconnected by a host controller 1210. The computer 1200 also includes input / output units such as a communication interface 1222, a storage device 1224 such as a hard disk drive, a DVD-ROM drive 1226, and an IC card drive, which are connected to the host controller 1210 via an input / output controller 1220. The computer also includes legacy input / output units such as a ROM 1230 and a keyboard 1242, which are connected to the input / output controller 1220 via an input / output chip 1240.

[0053] The CPU 1212 operates according to programs stored in the ROM 1230 and RAM 1214, thereby controlling each unit. The graphics controller 1216 acquires image data generated by the CPU 1212 from the frame buffer provided in RAM 1214 or from itself, and displays the image data on the display device 1218.

[0054] The communication interface 1222 communicates with other electronic devices via a network. The storage device 1224 stores programs and data used by the CPU 1212 in the computer 1200. The DVD-ROM drive 1226 reads programs or data from the DVD-ROM 1227 and provides them to the storage device 1224 via the RAM 1214. The IC card drive reads programs and data from the IC card and / or writes programs and data to the IC card.

[0055] The ROM 1230 stores boot programs and / or programs that depend on the computer 1200's hardware, which are executed by the computer 1200 when activated. The input / output chip 1240 may also connect various input / output units to the input / output controller 1220 via parallel ports, serial ports, keyboard ports, mouse ports, etc.

[0056] The program is provided on a computer-readable medium such as a DVD-ROM 1227 or an IC card. The program is read from the computer-readable medium and installed on a storage device 1224, RAM 1214, or ROM 1230, which are examples of computer-readable mediums, and executed by the CPU 1212. The information processing described within these programs is read by the computer 1200, resulting in coordination between the program and the various types of hardware resources described above. The apparatus or method may be configured to realize the manipulation or processing of information in accordance with the use of the computer 1200.

[0057] For example, when communication is performed between a computer 1200 and an external device, the CPU 1212 may execute a communication program loaded into the RAM 1214 and, based on the processing described in the communication program, instruct the communication interface 1222 to perform communication processing. Under the control of the CPU 1212, the communication interface 1222 reads transmission data stored in a transmission buffer processing area provided in a recording medium such as the RAM 1214, storage device 1224, DVD-ROM 1227, or IC card, transmits the read transmission data to the network, or writes received data received from the network to a receive buffer processing area provided on the recording medium.

[0058] Furthermore, the CPU 1212 may read all or necessary parts of a file or database stored on an external recording medium such as a storage device 1224, a DVD-ROM drive 1226 (DVD-ROM 1227), or an IC card into the RAM 1214, and perform various types of processing on the data in the RAM 1214. The CPU 1212 then writes the processed data back to the external recording medium.

[0059] Various types of information, such as various types of programs, data, tables, and databases, may be stored on the recording medium and subjected to information processing. The CPU 1212 may perform various types of processing on the data read from the RAM 1214, including various types of operations, information processing, conditional judgments, conditional branching, unconditional branching, information retrieval / replacement, etc., as described throughout this disclosure and specified by the program instruction sequence, and write the results back to the RAM 1214. The CPU 1212 may also retrieve information in files, databases, etc., within the recording medium. For example, if a plurality of entries having attribute values ​​of a first attribute, each associated with an attribute value of a second attribute, are stored in the recording medium, the CPU 1212 may search among the plurality of entries for an entry that matches the condition for which the attribute value of the first attribute is specified, read the attribute value of the second attribute stored in that entry, and thereby obtain the attribute value of the second attribute associated with the first attribute that satisfies a predetermined condition.

[0060] The program or software module described above may be stored on or near the computer 1200 on a computer-readable medium. Alternatively, a recording medium such as a hard disk or RAM provided within a server system connected to a dedicated communication network or the Internet can be used as a computer-readable medium, thereby providing the program to the computer 1200 via the network.

[0061] Although the present invention has been described above using embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments. It will be apparent to those skilled in the art that various modifications or improvements can be made to the above embodiments. It will be clear from the claims that such modified or improved forms may also be included in the technical scope of the present invention.

[0062] It should be noted that the execution order of operations, procedures, steps, and stages in the devices, systems, programs, and methods shown in the claims, specifications, and drawings is not explicitly stated as "before," "prior to," etc., and that these can be performed in any order unless the output of a previous process is used in a later process. Even if the operation flow in the claims, specifications, and drawings is described using phrases such as "first," "next," etc. for convenience, this does not mean that it is mandatory to perform the operations in that order.

[0063] This specification also discloses the configurations described in the following items: (Item 1) A fire control device that, when a request is sent from a client terminal specifying the URL of a web page, sends a response back to the client terminal and executes a fire control function, wherein the fire control function comprises: a status acquisition unit that acquires a status from the client terminal; and a tag control unit that activates a tag in the web page specified by the request according to the status. (Item 2) The fire control device according to Item 1, wherein the status is information that associates service identification information with whether or not the use of the service is permitted. (Item 3) The fire control device according to Item 2, wherein the tag control unit queries a tag information database with the service identification information for which use is permitted, acquires tag identification information corresponding to the service for which use is permitted, and activates the tag identified by the tag identification information. (Item 4) The fire control device according to Item 3, further comprising a tag information management unit that manages the tag information database. (Item 5) The fire control device according to Item 1, wherein the tag is disabled by default. (Item 6) The ignition control device according to Item 1, wherein the tag control unit enables the tag by editing the attributes of the tag. (Item 7) A client terminal implementing an ignition control function, comprising: a status acquisition unit that acquires the status of the client terminal when receiving a response from a server; and a tag control unit that enables the tags in the web page in the response according to the status. (Item 8) An ignition control system comprising: an ignition control device according to any one of Items 1 to 6; and a client terminal according to Item 7, which executes the ignition control function by receiving and executing an ignition control program from the ignition control device. (Item 9) An ignition control method executed by one or more computers, comprising: a step of acquiring the status of the client terminal when receiving a response from a server; and a step of enabling the tags in the web page in the response according to the status.(Item 10) The firing control method described in Item 9, wherein the status is information that associates service identification information with whether or not permission to use the service is granted. (Item 11) The firing control method described in Item 10, wherein in the activation stage, the tag information database is queried using the service identification information for which use is permitted, the tag identification information corresponding to the service for which use is permitted is obtained, and the tag identified by the tag identification information is activated. (Item 12) The firing control method described in Item 9, wherein the tag is disabled by default. (Item 13) The firing control method described in Item 10, wherein in the activation stage, the tag is activated by editing the attributes of the tag. (Item 14) A firing control program that causes a computer to execute the firing control method described in any one of Items 9 to 13. (Item 15) A fire control system comprising: a fire control device that sends a response back to the client terminal and executes a fire control function when a request is sent from the client terminal specifying the URL of a web page; and a client terminal that executes a fire control function by receiving and executing a fire control program from the fire control device, wherein the fire control function includes a status acquisition function that acquires a status from the client terminal, and a tag control function that activates the tags in the web page specified by the request according to the status. (Item 16) The fire control system according to Item 15, wherein the status is information that associates service identification information with whether or not the use of the service is permitted. (Item 17) The fire control system according to Item 16, wherein the tag control function queries a tag information database with the service identification information for which use is permitted, acquires the tag identification information corresponding to the service for which use is permitted, and activates the tag identified by the tag identification information. (Item 18) The fire control system according to Item 15, wherein the tags are disabled by default. (Item 19) The ignition control system described in Item 15, wherein the tag is activated by editing the attributes of the tag using the tag control function.(Item 20) A fire control method comprising the steps of: (1) When a fire control device receives a request from a client terminal specifying a URL of a web page, it sends a response back to the client terminal to execute a fire control function; and (2) The client terminal receives and executes a fire control program from the fire control device to execute a fire control function, wherein the fire control function includes a status acquisition function for acquiring a status from the client terminal, and a tag control function for enabling tags in the web page specified by the request according to the status. (Item 21) A program which causes a computer to execute a procedure for sending a response back to the client terminal to execute a fire control function in response to receiving a request from a client terminal specifying a URL of a web page, wherein the fire control function includes a status acquisition function for acquiring a status from the client terminal, and a tag control function for enabling tags in the web page specified by the request according to the status. (Item 22) A trigger control program that causes a computer to execute a procedure for obtaining the status of a client terminal when receiving a response from a server, and a procedure for enabling tags in the web page within the response according to the status.

[0064] 1...Ignition control system (system), 10...Ignition control device, 10A...Ignition control function, 11...Status acquisition unit, 12...Tag control unit, 13...Tag information management unit, 20...Tag information database, 50...Server, 90...Client terminal, 91...Display, 99...Network, 201...type attribute, 202...URL information, 203...ID information, 204...type attribute, 205...type attribute, 206...URL information, 207...ID information, 208...type attribute, 209...URL information, 210...ID information, 211...type attribute, 212...URL information, 213...ID information.

Claims

1. A fire control device that, when a request is sent from a client terminal specifying the URL of a web page, sends a response back to the client terminal and executes a fire control function, wherein the fire control function comprises: a status acquisition unit that acquires a status from the client terminal; and a tag control unit that activates tags in the web page specified by the request according to the status.

2. The fire control device according to claim 1, wherein the status is information that associates service identification information with whether or not permission to use the service is granted.

3. The ignition control device according to claim 2, wherein the tag control unit queries a tag information database with the specific information of the service for which use is permitted, obtains specific information of the tag corresponding to the service for which use is permitted, and activates the tag identified by the specific information of the tag.

4. The ignition control device according to claim 3, further comprising a tag information management unit for managing the tag information database.

5. The ignition control device according to claim 1, wherein the tag is disabled by default.

6. The ignition control device according to claim 1, wherein the tag control unit activates the tag by editing the attributes of the tag.

7. A client terminal that implements a fire control function, comprising: a status acquisition unit that acquires the status of the client terminal when it receives a response from a server; and a tag control unit that activates tags in the web page in the response according to the status.

8. A fire control system comprising: a fire control device according to any one of claims 1 to 6; and a client terminal according to claim 7, which performs a fire control function by receiving and executing a fire control program from the fire control device.

9. A fire control method performed by one or more computers, comprising the steps of: obtaining the status of a client terminal when receiving a response from a server; and enabling tags in a web page within the response according to the status.

10. The ignition control method according to claim 9, wherein the status is information that associates service identification information with whether or not permission to use the service is granted.

11. The ignition control method according to claim 10, wherein in the activation stage, the tag information database is queried with the specific information of the service for which use is permitted, the specific information of the tag corresponding to the service for which use is permitted is obtained, and the tag identified by the specific information of the tag is activated.

12. The ignition control method according to claim 9, wherein the tag is disabled by default.

13. The ignition control method according to claim 10, wherein the activation step involves activating the tag by editing the attributes of the tag.

14. A fire control program that causes a computer to execute the fire control method described in any one of claims 9 to 13.

Images