Patent information
IP India · live recordAbstract
Safety is further improved in a report inquiry system 500 that provides slip data to a mobile terminal 31. A mobile terminal management server 10 includes a business information temporary storage DB 16 for storing slip data to be provided to the mobile terminal 31; acquires the latest slip data from a slip data management server; updates the slip data stored in the business information temporary storage DB 16 by storing the acquired slip data in the business information temporary storage DB 16; determines whether to permit log-in of mobile terminals 31 to 3N or not when there is a log-in request from the mobile terminals 31 to 3N; carries outalog-in process in the case where it is determined to permit the log-in; receives a view request (provision request, search request) of slip data from the mobile terminals 31 to 3N of a log-in state for which the log-in process is carried out; and provides the slip data stored in the business information temporary storage DB 16 to the mobile terminals 31 to 3N in accordance with the received view request.
Applicants
1Inventors
1Specification
Show full textCollapse
DESCRIPTION MOBILE TERMINAL MANAGEMENT SERVER, AND MOBILE TERMINAL MANAGEMENT PROGRAM Technical Field
OOOl
The present invention relates to a mobile terminal management server that acquires slip data from a slip data management server, which manages the slip data generated for every business unit in a business process and provides the slip data via a communication network in response to a request from a mobile terminal used by a user, and to a mobile terminal management program mounted on the mobile terminal management server. Background Art [0002 ] Heretofore, one so-called ERP (Enterprise Resource Planning) has become mainstream as package software for establishing a core business system for a company. In a core business systemin which this ERPis contained, it is most often constructed on a relational database, and design of an application program that focuses on business processes is mostly made. Thus, it is often operated without focusing on a report output.
[0003] F o r t h e p u r p o s e o f p r o c e s s i n g t h e l a r g e a m o u n t o f b u s i n e s s data at a high speed, analyzing the business data from various angles, and outputting reports under such a situation, various data warehouse systems that undertake a complementary role to the core business system have been provided (see Patent L i t e r a t u r e 1) .
[0004] I Inreportinquirysystemsintendedto s u c h a r e p o r t output, one t h a t provides information such as a r e p o r t t o a mobile communication terminal has been proposed (see Patent L i t e r a t u r e s 2 and 3 ) . P r i o r A r t L i t e r a t u r e Patent L i t e r a t u r e
[0005] Patent L i t e r a t u r e 1: Japanese P a t e n t Application Publication No. 2002-312208 Patent L i t e r a t u r e 2: Japanese P a t e n t Application Publication No. 2003-323582 Patent L i t e r a t u r e 3: Japanese P a t e n t Application Publication No. 2007-200136 Summary of the Invention Problems t o be solved by the Invention
[0006] I n t h e r e p o r t inquiry system t h a t provides information suchas a r e p o r t t o amobile communicationterminal as described above, t h e r e is convenience t h a t is capable of acquiring i n f o r m a t i o n e v e n a t an outside l o c a t i o n o r inmotion. However, therehasbeenaprogramthatariskofleakageoftheinformation is increased. Therefore, i n the r e p o r t i n q u i r y system f o r providinginformationsuchas a report a n d t h e l i k e t o t h e m o b i l e communication terminal, one with high s a f e t y is required.
[0007] It is an o b j e c t of the p r e s e n t i n v e n t i o n t o resolve the problems described above and t o improve s a f e t y f u r t h e r i n a business systemforprovidinginformationonreportstoamobile communication terminal. Means f o r Solving the Problems
[0008] A mobile terminal management server according t o the present invention is a mobile terminal management server f o r acquiring s l i p data from a s l i p data management server and providingthe slipdatatoamobileterminalviaa communication network i n response t o a request from the mobile terminal used b y a u s e r , the s l i p d a t a b e i n g generated f o r everybusiness u n i t i n a b u s i n e s s process, the slipdatamanagement servermanaging the s l i p d a t a , themobileterminalmanagementserverincluding: a s l i p d a t a storage section f o r s t o r i n g s l i p d a t a t o b e provided t o the mobile terminal; a s l i p data acquiring s e c t i o n f o r acquiring the l a t e s t s l i p data from the s l i p data management server; a s l i p data updating section f o r updating the s l i p data s t o r e d i n t h e s l i p d a t a storage s e c t i o n b y s t o r i n g t h e s l i p d a t a acquired by the s l i p data acquiring section i n the s l i p data s t o r a g e s e c t i o n ; a log-in determining section f o r determining whether t o permit log-in of the mobile terminal when t h e r e is a log-in request from the mobile terminal; a log-in processing section f o r carrying out a log-in process i n the case where the log-in determining section determines t o permit the log-in; a view request receiving section f o r receiving a view request of s l i p data from the mobile terminal of a log-in s t a t e f o r which the log-in processing section c a r r i e s out the log-in process; and a s l i p data providing section f o r providing the s l i p data stored i n the s l i p data storage section t o the mobile terminal inaccordancewiththeviewrequestreceivedbytheviewrequest receiving s e c t i o n .
[0009] By configuring it as described above, it is possible t o improve safety further in a business system that provides information regarding reports to a mobile communication terminal. [00101 The mobile terminal management server may be configured so as to further include: an update request receiving section for receiving an update request of slip data from the mobile terminal of the log-in state; a log-in requesting section for carryingoutalog-in requesttothe slipdatamanagement server bypresentingterminal information in the case where the update request receiving section receives the update request, the terminal information indicating the mobile terminal; and an update requesting section for carrying out the update request received by the update request receiving section to the slip data management server in the case where the slip data management server permits the log-in in response to the log-in request by the log-in requesting section. [00111 The mobile terminal management server may be configured so as to further include: an update request receiving section for receiving an update request of slip data from the mobile terminal of the log-in state; an update related information accumulating section for accumulating update related information, the update related information containing the update content of the update request receive by the update request receiving section and terminal information indicating the mobile terminal that carried out the update request; and an update requesting section for transmitting, when it becomes predetermined timing, the update related information accumulated by the update related information accumulating section to the slip data management server in a lump and for carrying out the update request received by the update request receiving section in a lump.
[0012] The mobile terminal management server may be configured so that the mobile terminal includes a log-in determining section that permits log-in only in the case where a regular log-in operation defined in advance is received.
[0013] The mobile terminal management server may be configured so as to further include: a log-out processing section for carrying out a log-out process in the case where there is the log-outrequestfromthemobileterminal, the log-instatebeing cancelled in the log-out process; and a history information deletion requesting section for requestingthe mobile terminal to delete communication history information regarding provision of the slip data in the case where the log-out processing section carries out the log-out process.
[0014] The mobile terminal management server may be configured soas to further include: atimemeasuring section formeasuring a period of time for which exchange of information with the mobile terminal of the log-in state has not been carried out; and a history information deletion requesting section for requestingthemobileterminalto delete communication history information regardingprovisionofthe slipdata ina case where the period of time measured by the time measuring section reaches a predetermined period of time.
[0015] Further, amobileterminalmanagementprogramis amobile terminal management program for causing a mobile terminal management server to carry out a process to acquire slip data from a slip data management server and a process to provide the slip data to a mobile terminal via a communication network in response to a request from the mobile terminal used by a user, the mobile terminal management server managing the slip data generated for every business unit in a business process, the mobileterminalmanagementserverincludinga slip data storage section for storing the slip data to be provided to the mobile terminal, the mobile terminal management program causing the mobile terminal management server to execute: a slip data acquire process to acquire the latest slip data from the slip data management server; a slip data update process to update the slipdata storedinthe slipdata storage sectionby storing the slip data acquired in the slip data storage section in the slip data acquire process; a log-in determination process to determine whether to permit log-in of the mobile terminal when there is a log-in request from the mobile terminal; a log-in process to carry out a process for log-in in the case where it is determined in the log-in determination process to permit the log-in; a view request receiving process to receive a view request of slip data from the mobile terminal of a log-in state for which the log-in process is carried out; and a slip data providing process to provide the slip data stored in the slip data storage section to the mobile terminal in accordance with theviewrequestreceivedintheviewrequestreceivingprocess. Effects of the Invention
[0016] According to the present invention, it becomes possible to improve safety further in a business system that provides information on reports to a mobile communication terminal. Brief Description of the Drawings
[0017] F I G . 1 is ablockdiagramshowinga configuration example of a report inquiry system according to one embodiment of the present invention. F I G . 2 is ablockdiagramshowinga configuration example of a mobile terminal management server. F I G . 3 is an explanatory drawing for explaining a process to update business data. F I G . 4 is a flowchart showing an example of a business data providing process. F I G . 5 is an explanatory drawing showing an example of a data search screen. F I G . 6 is an explanatory drawing showing an example of a search result display screen. F I G . 7 is a flowchart showing an example of a business data updating process. F I G . 8 is an explanatory drawing showing an example of an editing screen. Mode for Carrying out the Invention
[0018] Hereinafter, an example of one embodiment according to the present invention will be described with reference to the drawings.
[0019] F I G . 1is ablockdiagramshowinga configuration example of a report inquiry system 500 according to one embodiment of the present invention. As shown in F I G . 1, the report inquiry system 500 includes a mobile terminal management server 10, a relay apparatus 20, a plurality of mobile terminals 31 to 3N ("N" is an arbitrary positive number), and an integrated core business system 100. Themobile terminalmanagement server 10 is connected to each of the mobile terminals 31 to 3N via a communication network 40, such as the Internet, and the relay apparatus 20. The mobile terminal management server 10 is connected to the integrated core business system 100 via a communication network such as an LAN (Local Area Network), dedicated communication line and the like.
[0020] The integrated core business system 100 includes a core business server 110, a data warehouse server (DWH server) 120, and a business information DB 101. In this regard, the core business server 110 is connected to the DWH server 120 via a dedicated communication line.
[0021] The core business server110is a servermanagedbyadata collectorwho is acollectingtargetofreportdata, for example, and has various kinds of functions for managing report information on various kinds of businesses. The core business server 110 is configured by a general information-processing apparatus provided with an OS (Operating System) and a relational DB. In this regard, the report is the general term of books and a type of slip. Further, the books denote one in whichmatters concerningaccounts ofmoney or goods are filled, and the slipdenotes data that become abasis for creatingbooks and constitute evidence of transactions and the like on a business. In the present embodiment, the case where the core business server110 deals withonlythe slipdata as report data will be described as an example.
[0022] The core business server 110 carries out various kinds of processes in accordance withbusiness application programs. There are a salesbusinessmanagement program, a sales business management program, a production management program, a financial accounting management program, a managerial accounting management program and the like as the business application programs, for example.
[0023] The DWH server120 is a servermanagedbya systemmanager of the present system, for example, and has various kinds of functions for realizing a data warehouse. Here, the data warehouse denotes a system to analyze the association among the individual items from among business data such as report data accumulated in time series. Further, the DWH server 120 has a function to register various kinds of data in a predetermined storage region (a business related data DB 101b, which will be described later) by converting a file with a CSV format transferred from the core business server 110 into a predetermined data format and the like. In this regard, the DWH server 120 may be configured to extract data according to the respective storage regions from a state of the CSV format without carrying out conversion of the data format. [ 0 02 4 ] The business information DB 101 includes a slip data DB 101a managed by the core business server 110 and a business related data DB 101b managed by the DWH server 120.
[0025] The slip data DB 101a is a storage medium for storing various kinds of slip data collected and marshaled by means of various kinds of information processing using various kinds of business application programs. In the slip data DB lola, for example, receivedorderslipheaderinformation, receivedorder slip description information, delivery date schedules and the like are associated with slip data corresponding to a received order slip, and they are stored in a structure capable of retrieving them on the basis of a key, such as a slip number. Inthis regard, the slipnumber includes a receivedordernumber, a purchase order number, a shipment number, an acceptance or delivery number, a bill reference, a billing number, an accounting number and the like.
[0026] The core business server 110 has a function to convert various kinds of data (slip data) stored in the slip data DB lOla into a CSV (Comma Separated Values) format in accordance with a predetermined extracting condition and a function to transmit the converted data to the mobile terminal management server 10. In this regard, in the present embodiment, the core business server 110 transfers the data file converted into the CSV format to the mobile terminal management server 10 by means of an FTP (File Transfer Protocol) .
[0027] The mobile terminal management server 10 is configured by an information-processing apparatus such as a WWW server, for example, and is managed by a system manager of the present system500. Themobile terminalmanagement server10 includes: a slip data managing section 11 that carries out a process regarding management of slip data; a log-in managing section 12 that carries out a process regarding management of log-in; a slip data provision processing section 13 that carries out a process to provide the slip data to the mobile terminals 31 to 3N; a slip data update processing section 14 that carries out a process to update the slip data in response to a request from the mobile terminals 31 to 3N; a customer information managing section 15 that carries out a process regarding management of customer information; anda business information temporary storage DB 16, for example, as shown in FIG. 2.
[0028] The business information temporary storage DB 16 is a storage medium for temporarily storing business data such as slip data acquired from the integrated core business system 100 side. The business data, such as the slip data, stored in the business information temporary storage DB 16 are updated at regular intervals (every day, every three days, every twelve hours or the like), for example.
[0029] Each of the mobile terminals 31 to 3N is an information-processing apparatus including a CPU (Central Processing Unit), a ROM, a RAM, a display section and the like, such as an Ipad (registered trademark), for example. In the present embodiment, each of the mobile terminals 31 to 3N has various kinds of applications available to deal with the report data, suchas awebbrowser. Further, inthe present embodiment, each of the mobile terminals 31 to 3N has a function to define a query (a search item, a search key, an extract key and the like) for acquiring necessary report data from the mobile terminal management server 10 in response to an operation input by a user, for example, and a function to transmit the defined query to the mobile terminal management server 10.
[0030] In the present embodiment, each of the mobile terminals 31 to 3N has a function to communicate with the mobile terminal management server 10 via the relay apparatus 20 and the communication network 40, and a function to output the data acquired from the mobile terminal management server 10 to the display section by means of a function of software such as a predetermined Web application (Web browser), for example.
[0031] Here, a process to update business data such as the slip data stored in the business information temporary storage DB 16 will be described. FIG. 3 is an explanatory drawing for explaining a process to update business data. As shown in FIG. 3, when it becomes timing of data update (for example, a predetermined time defined in advance (2 a.m. o r the l i k e ) in the case where they are updated every day), a f i l e outputting section 111 in the core business server 110 reads out s l i p data (which become the l a t e s t data) stored in the s l i p data DB 101a with which the core business server 110 is provided, and t r a n s f e r s t h e read-outslipdata to a f i l e transferring section 112. Further, when it becomes a predetermined time defined in advance, the DWH server 120 similarly reads out the business data (which become the l a t e s t data) stored in the business related data DB 101b with which the DWH server 120 is provided, a n d t r a n s f e r s t h e b u s i n e s s d a t a t o t h e f i l e t r a n s f e r r i n g section 112 with which the core business server 110 is provided. In t h i s regard, as shown in FIG. 3, there are item goods data, business partner data, definition data, inventory data, received order data, credit data, BI original data and the l i k e in the s l i p data stored in the s l i p data DB lola, for example. Further, as shown in FIG. 3, there a r e s a l e s performance information on individual customers and individual item goods, hot-sellinginformationandthelikeinthebusinessdata stored in the business related data DB 101b, for example.
[0032] The f i l e transferring section 112 included in the core business server 110 transmits the business data respectively received fromthe f i l e outputting s e c t i o n l l l a n d t h e DWH server 1 2 0 t o t h e m o b i l e t e r m i n a l m a n a g e m e n t s e r v e r 1 0 . Whenbusiness data (batch f i l e l l a ) are received, a f i l e retrieving section l l b of the s l i p data managing section 11 in the mobile terminal management server 10 stores (newly saves or overwrite saves) the received business data in a predetermined storage region of the business information temporary storage DB 16, and the f i l e retrieving section l l b thereby updates the information storedinthebusiness information temporary storage DB16. In this way, the information stored in the business information temporary storage DB 16 is updated by the batch process.
[0033] Next, an operation of the report inquiry system 500 according to the present embodiment will be described with reference to the drawings. In this regard, the content of operations and processes with no relationship to the present invention particularly may be omitted.
[0034] FIG. 4 is a flowchart showing an example of a business data providing process carried out by the mobile terminal management server 10 and the like in the report inquiry system 500 according to the present embodiment. Here, the case where business data are provided in response to a request from the mobile terminal 31 used by a user X will be described as an example.
[0035] In the business data providing process, the mobile terminal31firstreceives alog-in request bymeans ofalog-in operation of the user X (Step S101). For example, an input operation of a personal identification number setup in advance is thought as this log-in operation. When log-in to the mobile terminal 31 is permitted, it is allowed to carry out various kinds of operations for utilizing various kinds of functions mounted on the mobile terminal 31.
[0036] In the case where a predetermined log-in operation is carried out by the user X when to log in the mobile terminal 31, the mobile terminal 31 accesses to the mobile terminal management server 10 to carry out a log-in request (Step S102). This log-in request is carried out by presenting predetermined information used for log-in determination defined in advance (for example, electronic certificate issued tothe user X), for example.
[0037] When the log-in request is received, the log-in managing section 12 of the mobile terminal management server 10 determines whether to permit log-in or not (Step S103). This determination may be carried out by means of an ID, a password, electronic certificate or the like, for example.
[0038] In the case where it is determined to permit the log-in ("Yes" at Step S103), the log-in managing section 12 sets up the mobile terminal 31 to a log-in state. When it is set up tothe log-in state, the slipdata provision processing section 13 of the mobile terminal management server 10 transmits data search screen information indicating a data search screen to the mobile terminal 31 (Step S104) . In this regard, in the case where it is determined not to permit the log-in ("No" at Step S103), the log-in managing section 12 terminates the process without setting up the log-in state. In this regard, in the case where it is determined not to permit the log-in, the log-in managing section 12 carries out a process to notify that effect of the mobile terminal 31.
[0039] When the data search screen information is received, the mobile terminal 31 displays the data search screen indicated by the received the data search screen information on a display section included in the mobile terminal 31 itself (Step S105). FIG. 5 is an explanatory drawing showing an example of the data search screen. As shown in FIG. 5, a search item input region 601forinputtinganitem (searchitem) thatisatargetofsearch, a search word input region 602 for inputting a keyword (search word) used when t o s e a r c h , a r e t u r n button B1 t o be pressed when t o r e t u r n t o a previous screen, and a search button B2 t o be pressed when t o carry out the search are provided on the data search screen.
[0040] Onthedatasearchscreen,theuserXoperatesanoperating s e c t i o n included i n the mobile terminal 31 ( f o r example, a keyboarddisplayedonthedisplaysectioninwhichatouchpanel is arranged) t o input a search item and a search word and t o p r e s s t h e search button B2. Items such as received order s l i p , i n v e n t o r y , business p a r t n e r s , t r a d e names or the l i k e a r e i n p u t t e d a s t h e searchitem, f o r example. Names o f t h e b u s i n e s s p a r t n e r s , names of goods or the l i k e are inputted as the search word.
[0041] When a search item and a search word are inputted and the s e a r c h b u t t o n B2 is then pressed, the mobile terminal 31 presents the inputted search item and search word t o the mobile terminalmanagement server 10 as s e a r c h c o n d i t i o n s , a n d c a r r i e s out a p r o v i s i o n r e q u e s t of business data (Step S106). In t h i s regard, the search conditions described above a r e one example, a n d t h e y m a y b e a n y o t h e r c o n d i t i o n s o l o n g a s t h e y a r e searchable condition.
[0042] When the provision request of the business data is received, the mobile terminal management s e r v e r 1 0 r e f e r s t o the business information temporary storage DB 16, and searches the business data i n accordance with the p r e s e n t e d s e a r c h conditions (Step S107).
[0043] When the business data a r e searched i n accordance with the search conditions, the mobile terminal management s e r v e r 10 transmits, to the mobile terminal 31, search result screen information indicating a search result screen for displaying the searched business data as a search result (Step S108).
[0044] When the search result screen information is received, the mobile terminal 31 displays the search result screen indicated by the received search result screen information on the display section included in the mobile terminal 31 itself (Step S109). FIG. 6 is an explanatory drawing showing an example of the search result screen. As shown in FIG. 6, a display region 603 for displaying the search result, a return button B1 to be pressed when to return to a previous screen, a n d a n e d i t i n g b u t t o n B 3 t o b e p r e s s e d w h e n e d i t i n g o f t h e search result is carried out are provided in the search result screen.
[0045] Then, in the case where an operation to terminate the access, such as an operation to terminate a browser by the user X, is made ("Yes" at Step S110) , the mobile terminal 31 carries out a log-out request to the mobile terminal management server 10 (Step S111). In this regard, in the case where an operation to continue the access, such as pressing of the return button B1, is made ("No" at Step SllO), the mobile terminal 31 shifts to the process at Step S105 to display the data search screen.
[0046] When the search result screen information is transmitted at Step S108, the log-in managing section 12 starts to measure a period of time (waiting time) for which exchange of information with the mobile terminal 31 is not carried out, and monitors whether a predetermined period of time (for example, five minutes, ten minutes, thirty minutes or the like) elapses as this waiting time (it reaches the predetermined period of time) or not (Step S112).
[0047] When the log-out request is received during measurement of the waiting time ("Yes" at Step S113), the log-in managing section 12 suspends measurement of the waiting time, carries out an erasing request of history information (communication history information, operation history information and the like) by this communication with the mobile terminal 31 (Step S114), and carries out a log-out process to cancel the log-in state (Step S115).
[0048] Further, in the case where it is determined that the predetermined period of time elapses as the waitingtime ("Yes" at Step S112), the log-in managing section 12 terminates the measurementofthewaitingtime, carries out the erasing request ofthehistory information (communicationhistory information, operation history information and the like) by this communication with the mobile terminal 31 (Step S114), and carries out thelog-out processtocancelthelog-in state (Step S115).
[0049] Then, when the erasing request ofthe history information is received, the mobile terminal 31 carries out a process to erasethehistoryinformationaccumulatedbythis communication with the mobile terminal management server 10 (Step S116).
[0050] As described above, the process to determine whether to permit the log-in to the mobile terminal management server 10 in response to the log-in request from the mobile terminal 31 that becomes operable by means of the log-in process; the process to receive the provision request of the business data in the case of permission; and the process to provide the business data in accordance with the request are carried out. [00511 By carrying out the process to provide the business data as described above, it is possible to carry out authentication doubly at Step SlOl and Step S103. Further, it is possible to eliminate necessity to access to the integrated core business system 100. For this reason, it is possible to improve safety when to provide the business data to the mobile terminal 31. [00521 FIG. 7 is a flowchart showing an example of a business data updating process carried out by the core business server 110, the mobile terminal management server 10 and the mobile terminal 31. Here, the case where business data are updated in response to a request from the mobile terminal 31 used by the user X will be described as an example. [00531 Processes at Steps S201 to S209 in the business data updating process are similar to the processes at Steps SlOl to S109 in the business data providing process described above, andprocesses at Steps S 2 1 9 t o S 2 2 5 i n t h e b u s i n e s s d a t a u p d a t i n g process are similar to the processes at Steps SllO to S116 in the business data providing process described above. Forthis reason, detailed explanation of Steps S201 to S209 and S219 to S225 in the business data updating process is omitted. [00541 When pressing of the editing button B3 is received after the search result screen indicated by the search result screen information (see FIG. 6) is displayed on the display section included in the mobile terminal 31 at Step S209 in the business data updating process, the mobile terminal 31 displays an editing screen in which the search result displayed in the display region 603 can be edited. FIG. 8 is an explanatory drawing showing an example of the editing screen. As shown in F I G . 8, a n e d i t i n g r e g i o n 604 foreditablydisplayingthe search r e s u l t ; a r e t u r n button B1 t o be pressed when t o r e t u r n t o a previous screen; and an update button B4 t o be pressed when t o r e f l e c t the e d i t e d r e s u l t t o the business data saved a t the servers 1 0 , 110 s i d e s are provided on t h e e d i t i n g screen.
[0055] The user X operates the mobile terminal 31 t o carry out an operation t o e d i t the business data displayed as the search r e s u l t by adding ( f o r example, new r e g i s t r a t i o n of a s l i p ) , e r a s i n g , or c h a n g i n g t h e b u s i n e s s d a t a d i s p l a y e d i n t h e e d i t i n g region 604 on t h e e d i t i n g screen. Then, i n the case where the e d i t e d r e s u l t is r e f l e c t e d t o the business data saved a t the servers 10, 110 s i d e s a f t e r t h e e d i t i n g o p e r a t i o n i s terminated, the user X operates the mobile terminal 31 t o press the update button B4.
[0056] In the case where pressing of the update button B4 is received, the mobile terminal 31 c a r r i e s out an information rewritingrequestforrequestingthemobileterminalmanagement server 10 t o r e f l e c t the e d i t e d r e s u l t (Step S210) . The e d i t e d content, mobile terminal management s e r v e r information r e g a r d i n g t h e m o b i l e terminalmanagement s e r v e r 1 0 (forexample, electroniccertificateissuedtothemobileterminalmanagement s e r v e r l o ) , user information regarding the userX ( f o r example, e l e c t r o n i c c e r t i f i c a t e issued t o the user X, or the l i k e ) and the l i k e a r e presented i n t h i s request.
[0057] When the information r e w r i t i n g request is received, the mobile terminal management server 10 c a r r i e s o u t a c c e s s t o the corebusiness server110, a n d c a r r i e s outalog-in request (Step S211). This log-in request is c a r r i e d out by presenting predetermined information defined i n advance and used f o r the log-in determination (for example, electronic certificate issued to the mobile terminal management server 10, electronic certificate issued to the user X, and the like), for example.
[0058] When the log-in request is received, the core business server 110 determines whether to permit the log-in or not (Step S212). This determination may be carried out by means of an ID, apassword, electroniccertificate orthe like, for example.
[0059] In the case where the core business server 110 determines to permit the log-in, the core business server 110 sets up the mobile terminal management server 10 to a log-in state with respect to receiving of information from the mobile terminal 31 (Step S213). When it is set up to the log-in state, the core business server 110 carries out a process to rewrite the corresponding business data saved in the business information DB 101 in accordance with the edited content inputted from the mobile terminal 31 via the mobile terminal management server 10 (Step S214). The core business server 110 then transmits rewriting notification for notifying rewriting in accordance withtheeditedcontenttothemobileterminalmanagementserver 10 (Step S215) . The core business server 110 then carries out a log-out process.
[0060] When the rewriting notification is received, the mobile terminal management server 10 carries out a process to rewrite the corresponding business data stored in the business information temporary storage DB 16 in accordance with the edited content inputted from the mobile terminal 31, as well as the core business server 110 (Step S216). The mobile terminal management server 10 then transmits rewriting notification fornotifyingthe rewriting inaccordance with the edited content to the mobile terminal 31 (Step S217).
[0061] When the rewriting notification is received, the mobile terminal 31 displays rewriting reflection notification for informing the user X that the mobile terminal 31 reflects the edited result to a predetermined region of the editing screen (Step S218).
[0062] Then, the processes after Step S219 are carried out as well as the business data providing process described above.
[0063] As described above, it is determined whether to permit the log-in to the mobile terminal management server 10 or not in response to the log-in request from the mobile terminal 31 that becomes operable by the log-in process; the rewriting request for the business data is received in the case of permission; the log-in request is carried out to the core business server 110 in the case where the rewriting request is received; the process to rewrite the business data is carried out in the core business server 110 in the case of permission; and the process to rewrite the business data is also similarly carried out in the mobile terminal management server 10.
[0064] B y c a r r y i n g o u t t h e r e w r i t i n g p r o c e s s o f t h e b u s i n e s s d a t a as described above, it is possible to carry out authentication trebly at Step S201, Step S203 and Step S212. Further, it is possible to prohibit direct access from the mobile terminal 31 to the integrated core business system 100. For this reason, it is possible to improve safety when to update the business data in response to the request from the mobile terminal 31. [00651 In the embodiment described above, the mobile terminal management server 10 is configured sothat: themobile terminal management server 10 carries out a log-in request to the core business server 110 whenever a rewriting request is received from the mobile terminal 31; and the core business server 110 carries out the process to rewrite the business data. However, the mobile terminal management server 10 may be configured so as to: accumulate information (information necessary for authentication) regarding the mobile terminals 31 to 3N each of which becomes a requester for the edited content and rewriting in the case where the rewriting request is received from the mobile terminals 31 to 3N; and carry out the rewriting request to the core business server 110 by a batch process at predetermined timing (for example, at 11 p.m. every day, or the like). In this case, the log-in request may be carried out at predetermined timing by presenting the information regarding each of the mobile terminals 31 to 3N that becomes a requester for rewriting, and only the edited content for which a terminal device whose log-in is permitted is a requester for rewriting maybereflectedtothebusinessdatainthe corebusiness server 110.
[0066] Namely, the mobile terminal management server 10 may be configuredsoasto: receive the update request ofthe slipdata from the mobile terminal 31 to 3N in a log-in state; accumulate update related information containing the received update content of the update request (the edited content) and the terminal information indicating the mobile terminal 31 to 3N thatcarriedouttheupdaterequest (forexample, theelectronic certificate) (for example, accumulate them in the storage medium with which the mobile terminal management server 10 is provided); transmit, when it becomes predeterminedtiming (for example, at 11 p.m. every day, or the like), the accumulated update r e l a t e d information t o the s l i p data management s e r v e r ( f o r example, the c o r e business server 110) i n a lump; and carry out the update r e q u e s t received from each of the mobile terminals 31 t o 3N t h a t is i n a log-in s t a t e i n a lump. By configuring it i n t h i s manner, it becomes possible t o reduce the number of accesses t o the core business s e r v e r 110 d r a s t i c a l l y , and it becomes p o s s i b l e t o i m p r o v e s a f e t y f u r t h e r .
[0067] As explained above, i n the embodiment described above, themobile terminalmanagement s e r v e r 1 0 f o r acquiring s l i p d a t a from the s l i p data management s e r v e r ( f o r example, the core business server 110) and providing the s l i p data t o the mobile terminals 3 1 t o 3N v i a t h e communication network 40 i n response t o a request from the mobile terminals 31 t o 3N r e s p e c t i v e l y u s e d b y t h e u s e r s , inwhich the s l i p d a t a are generated f o r e v e r y business u n i t i n a b u s i n e s s process a n d t h e slipdatamanagement server manages the s l i p data, the mobile terminal management server 10 is configured so as t o : include the business information temporary storage DB 16 f o r s t o r i n g s l i p data t o be p r o v i d e d t o t h e m o b i l e terminals 3 1 t o 3N; acquire the l a t e s t s l i p data from the s l i p data management server; update the s l i p data stored i n the business information temporary storage DB 1 6 b y s t o r i n g t h e a c q u i r e d s l i p d a t a i n t h e b u s i n e s s i n f o r m a t i o n temporary storage DB 16; determine whether t o permit log-in of the mobile terminals 31 t o 3N when t h e r e is a log-in request from the mobile terminals 31 t o 3N; carry out a l o g - i n process i n the case where it is determined topermitthelog-in; receive a view request (a provision request, a search r e q u e s t ) of the s l i p data from the mobile terminals 31 t o 3N of the log-in s t a t e f o r which the l o g - i n process is c a r r i e d out; anti provide the s l i p data s t o r e d i n t h e business information temporary storage DB16tothemobileterminals 3 1 t o 3 N i n r e s p o n s e t o t h e received view request. Therefore, in the business system (the report inquiry system500) that provide st he information (for example, the slipdata) regardingthe reportstothemobilecomrnunication terminal (the mobile terminals 31 to 3N), it becomes possible to improve safety further.
[0068] Namely, the mobile terminal management server 10 is configured so as to: transfer the slip data to the mobile terminalmanagement server10 fromthecorebusiness server110; and provide the slip data to the mobile terminals 31 to 3N each of which is permittedtologinthis mobile terminal management server 10. Therefore, it becomes possible to provide the slip data fromthemobileterminalmanagementserver10tothemobile terminals 31 to 3N authenticated by the mobile terminal management server 10 without accessing to the core business server 110, and it becomes possible to improve safety when to provide the business data to the mobile terminals 31 to 3N.
[0069] Further, in the embodiment described above, the mobile terminal management server 10 is configured so as to: receive an update request of slip data from the mobile terminals 31 to 3N of the log-in state; carry out a log-in request to the slip data management server (for example, the core business server 110) by presenting terminal information (for example, electronic certificate issued for a terminal or user) in the case where the update request is received, the terminal information indicatingthemobile terminals 31to 3N; and carry out the update request to the slip data management server in the case where the slip data management server permits the log-ininresponsetothe log-inrequest. Therefore, itbecomes possible to improve safety when to update the business data in response to the request from the mobile terminals 31 to 3N. Namely, the mobile terminal management server 10 is configured so as topermitthe update ofthebusiness data in the case where double authentication is obtained by the mobile terminal management server10 andthe slipdatamanagement serverwithout direct access tothe slip datamanagement server fromthemobile terminals 31 to 3N. Therefore, it becomes possible to improve safety when to update business data.
[0070] Further, in the embodiment described above, the mobile terminal management server 10 is configured so that the log-in is permitted in the case where the mobile terminals 31 to 3N receive a regular log-in operation defined in advance. Therefore, it is possible to require authentication at the mobile terminals 31 to 3N, and it is thus possible to require double or triple authentication. This makes it possible to heighten safety further.
[0071] Further, in the embodiment described above, the mobile terminal management server 10 is configured so as to: carry out case where there is the log-out request from the mobile terminals 31 to 3N; and request the mobile terminals 31 to 3N to delete the communication history information regarding provision of the slip data in the case where the log-out process is carried out. Therefore, it becomes possible to erase the communication history information, and this makes it possible to prevent the information from being leaked due to loss of the mobile terminals 31 to 3N and the like.
[0072] Further, in the embodiment described above, the mobile terminal management server 10 is configured so as to: measure a period of time for which exchange of information with the mobile terminals 31 to 3N of the log-in state is not carried out; and request the mobile terminals 31 to 3N to delete the communication history information regarding provision of the slip data in the case where the measured period of time reaches the predetermined period of time. Therefore, it becomes possible to erase the communication history information, and this makes it possible to prevent the information from being leakeddue to loss ofthemobile terminals 31to 3N and the like. 100731 In this regard, although it has not been mentioned in the embodiment described above, the mobile terminal management server 10 carries out each of the processes (see FIG. 4 and FIG. 7) in accordance with processing programs (the mobile terminal management program) stored in a storage medium included in the mobile terminal management server 10 itself. Industrial Applicability
[0074] According to the present invention, it is useful to improve safety in a business system that provides information on reports to a mobile communication terminal. Explanation of Reference numerals 10 mobile terminal management server 20 relay apparatus 31 to 3N mobile terminal 40 communication network 50 communication network 100 integrated core business system 110 core business server 120 DWH server 500 report inquiry system
CLAIMS 1. A mobile terminal management server f o r acquiring s l i p data from a s l i p data management server and providing the s l i p data t o a mobile terminal via a communication network i n response t o a request from the mobile terminal used by a user, the s l i p data being generated f o r every business u n i t i n a business process, the s l i p datamanagement servermanagingthe s l i p data, the mobile terminal management server comprising: a s l i p data storage section f o r s t o r i n g s l i p data t o be provided t o the mobile terminal; a s l i p data acquiring section f o r acquiring the l a t e s t s l i p data from the s l i p data management server; a s l i p data updating section f o r updating the s l i p data s t o r e d i n t h e s l i p data storage s e c t i o n b y s t o r i n g t h e s l i p d a t a acquired by the s l i p data acquiring section i n the s l i p data s t o r a g e s e c t i o n ; a log-in determining section f o r determining whether t o p'ermit log-in of the mobile terminal when t h e r e is a log-in request from the mobile terminal; a log-in processing section f o r c a r r y i n g o u t a log-in process i n the case where the log-in determining s e c t i o n determines t o permit the log-in; a view r e q u e s t receiving section f o r receiving a view request of s l i p data from the mobile terminal of a log-in s t a t e f o r which the log-in processing section c a r r i e s out the log-in process; and a s l i p d a t a providing section f o r p r o v i d i n g t h e s l i p d a t a stored i n the s l i p data storage section t o the mobile terminal inaccordancewiththeviewrequestreceivedbytheviewrequest r e c e i v i n g s e c t i o n . 2. The mobile terminal management server according to claim 1, further comprising: an update request receiving section for receiving an update request of slip data from the mobile terminal of the log-in state; a log-in requesting section for carrying out a log-in request to the slip data management server by presenting terminal information in the case where the update request receiving section receives the update request, the terminal information indicating the mobile terminal; and an update requesting section for carrying out the update requestreceivedbythe update request receiving section tothe slip data management server in the case where the slip data management server permits the log-in in response to the log-in request by the log-in requesting section. 3 . Themobile terminalmanagement server according to claim 1, further comprising: an update request receiving section for receiving an update request of slip data from the mobile terminal of the log-in state; an update related information accumulating section for accumulating update related information, the update related informationcontainingthe update content ofthe update request receive by the update request receiving section and terminal informationindicatingthemobileterminalthatcarriedoutthe update request; and an update requesting section for transmitting, when it becomes predetermined timing, the update related information accumulated by the update related information accumulating section to the slip data management server in a lump and for carrying out the update request received by the update request receiving section in a lump. 4. The mobile terminal management server according to any one of claims 1 to 3, wherein the mobile terminal includes a log-in determining section that permits log-in only in the case wherearegularlog-inoperationdefinedinadvanceis received. 5. The mobile terminal management server according to any one of claims 1 to 4, further comprising: a log-out processing section for carrying out a log-out process in the case where there is the log-out request from the m o b i l e t e r m i n a l , t h e l o g - i n s t a t e b e i n g c a n c e l l e d i n t h e l o g - o u t process; and a history information deletion requesting section for requestingthe mobile terminal to delete communication history information regarding provision of the slip data in the case where the log-out processing section carries out the log-out process. 6. The mobile terminal management server according to any one of claims 1 to 5, further comprising: a time measuring section for measuring a period of time for which exchange of information with the mobile terminal of the log-in state has not been carried out; and a history information deletion requesting section for requestingthe mobile terminal to delete communication history information regardingprovisionofthe slipdata ina casewhere the period of time measured by the time measuring section reaches a predetermined period of time. 7 . Amobile terminalmanagement program for causing amobile terminal management server to carry out a process to acquire s l i p data from a s l i p data management server and a process t o provide the s l i p data t o a mobile terminal via a communication network i n response t o a request from the mobile terminal used by a user, the mobile terminal management s e r v e r managing the s l i p data generated f o r every business u n i t i n a business process, the mobile terminal management s e r v e r comprising a s l i p data storage s e c t i o n f o r s t o r i n g t h e s l i p data t o be providedtothemobileterminal, themobile terminalmanagement program causing the mobile terminal management s e r v e r t o execute : a s l i p data acquire process t o acquire the l a t e s t s l i p data from the s l i p data management s e r v e r ; a s l i p data update process t o update the s l i p d a t a s t o r e d i n the s l i p data storage s e c t i o n by s t o r i n g the s l i p data acquired i n the s l i p d a t a s t o r a g e s e c t i o n i n the s l i p data acquire process; a l o g - i n determination process t o determine whether t o permit log-in of the mobile terminal when t h e r e is a log-in request from the mobile terminal; a l o g - i n process t o c a r r y o u t a process f o r log-in i n the case where it is t o permit the log-in; aviewrequestreceivingprocesstoreceiveaviewrequest of s l i p d a t a fromthemobileterminalofalog-in s t a t e forwhich the l o g - i n process is c a r r i e d out; and a s l i p data providing process t o provide the s l i p data s t o r e d i n the s l i p data storage s e c t i o n t o the mobile terminal inaccordance with t h e v i e w r e q u e s t receiving process. Dated this 1 2d~ay of July 2012 V Of Anand and Anand Advocates Agents for the Applicant