WO2014002138A1 - Serveur de gestion de terminal mobile et programme de gestion de terminal mobile - Google Patents

Serveur de gestion de terminal mobile et programme de gestion de terminal mobile Download PDF

Info

Publication number
WO2014002138A1
WO2014002138A1 PCT/JP2012/004178 JP2012004178W WO2014002138A1 WO 2014002138 A1 WO2014002138 A1 WO 2014002138A1 JP 2012004178 W JP2012004178 W JP 2012004178W WO 2014002138 A1 WO2014002138 A1 WO 2014002138A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile terminal
user
login
data
process flow
Prior art date
Application number
PCT/JP2012/004178
Other languages
English (en)
Japanese (ja)
Inventor
敏文 秋田
Original Assignee
株式会社アイ・ピー・エス
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社アイ・ピー・エス filed Critical 株式会社アイ・ピー・エス
Priority to PCT/JP2012/004178 priority Critical patent/WO2014002138A1/fr
Priority to JP2013529474A priority patent/JPWO2014002138A1/ja
Publication of WO2014002138A1 publication Critical patent/WO2014002138A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Definitions

  • the present invention is a server on which an ERP operates, a portable terminal management server that provides various data via a communication network in response to a request from a portable terminal used by a user, and a portable terminal mounted on the portable terminal management server. It relates to a terminal management program.
  • ERP Enterprise Resource Planning
  • the mission-critical business system integrated mission-critical business system, ERP system
  • application programs that focus on business processing are designed.
  • the form output is operated without any focus.
  • the basic information management system that provides information such as forms to mobile communication terminals as described above has the convenience of being able to acquire information while away from home or on the move, but there is a risk of information leakage There was a problem of increasing the nature. Therefore, a basic information management system that provides information such as a form to a mobile communication terminal is required to have high safety.
  • a license is given to the user side, and only the licensee is allowed to use the system.
  • whether or not the user is a registered user is managed by the license.
  • an unauthorized use such as using one license by a plurality of users may be performed.
  • unauthorized data is included in the registered data of the registered user.
  • the present invention solves the above-described problems, can prevent fraudulent acts due to fraudulent licenses in a business system (ERP system) that provides information related to forms to mobile communication terminals, and can improve system safety. At the same time, it is an object to be able to protect the system administrator and the user.
  • ERP system business system
  • the mobile terminal management server of the present invention is a server on which ERP operates, and is a mobile terminal management server that provides various data via a communication network in response to a request from a mobile terminal used by a user.
  • Process flow data storage means for storing process flow data including various data related to a process flow including a business process so that the mobile terminal can be referred to, and a server administrator of the mobile terminal management server issued to the user Login determination that determines whether or not to allow login to the portable terminal based on the presented user license information when there is a login request from the portable terminal that presents the user license information that is the license information And when the login determination unit determines that login is permitted.
  • Login processing means for performing login processing, processing request reception means for receiving various processing requests from the portable terminal in the login state for which login processing has been executed by the login processing means, and processing received by the processing request reception means
  • Processing execution means for executing a predetermined process in response to a request, and the processing execution means performs processing for the integrated core business system that performs a function by communicating with the mobile terminal management server as the predetermined processing.
  • server license information that is license information issued to the server administrator, presenting the server license information that can uniquely identify the user license information, and submitting the processing request. It is characterized by performing.
  • the server license information is used as the user license information, and the login determination unit determines whether or not the user is a registered user based on the server license information presented as the user license information. You may be set as the structure which determines whether login is permitted with respect to a portable terminal.
  • One piece of user license information can be issued with respect to one piece of server license information, and is associated with one piece of server license information.
  • the process execution unit includes the user license information used by the login determination unit and The server license information associated in one-to-one correspondence may be presented and the processing request may be made to the integrated core business system.
  • the user ID and password may be used as the license information.
  • the mobile terminal management program of the present invention operates the ERP, and makes the mobile terminal management server execute processing for providing various data via a communication network in response to a request from the mobile terminal used by the user.
  • the portable terminal management server comprising process flow data storage means for storing process flow data including various data relating to a process flow including a plurality of business processes so that the portable terminal can be referred to the portable terminal management server.
  • Login determination to determine whether to allow login to the terminal And login processing execution processing for performing login processing when it is determined that login is permitted in the login determination processing, and various processing from the portable terminal in the login state in which login processing is executed in the login processing execution processing
  • a process request receiving process for receiving a request and a predetermined process executing process for executing a predetermined process in response to the process request received in the process request receiving process.
  • Server license information that is license information issued to the server administrator when performing a processing request to an integrated mission-critical system that performs functions by communicating with a mobile terminal management server, Present the server license information that can uniquely identify the user license information, and execute the process to request the process It is intended for.
  • FIG. 1 is a block diagram showing a configuration example of a basic information management system 500 according to an embodiment of the present invention.
  • the basic information management system 500 includes a mobile terminal management server 10, a relay device 20, a plurality of mobile terminals 31 to 3N (N is an arbitrary positive integer), an integrated core business system 100, The integrated core business system 200 and the integrated core business system 300 are included.
  • the mobile terminal management server 10 and the mobile terminals 31 to 3N are connected to each other via a communication network 40 such as the Internet and the relay device 20, respectively.
  • the mobile terminal management server 10 is connected to the integrated core business system 100, the integrated core business system 200, and the integrated core business system 300 via communication networks 51, 52, and 53 such as a LAN (Local Area Network) and a dedicated communication line, respectively. Is done. In addition, it is good also as a structure which can communicate between portable terminals and integrated core business systems via a portable terminal management server, and is good also as a structure which cannot communicate.
  • communication networks 51, 52, and 53 such as a LAN (Local Area Network) and a dedicated communication line, respectively. Is done.
  • LAN Local Area Network
  • the integrated core business system 100 includes a core business server 110, a data warehouse server (DWH server) 120, and a process flow DB 101.
  • the integrated core business system 200 includes a DWH server 220 and a process flow DB 201.
  • the integrated core business system 300 includes a core business server 310 and a process flow DB 301.
  • a plurality of integrated core business systems 100, 200, and 300 having different configurations are integrated by performing communication (transmission and reception of various types of information) with the mobile terminal management server 10 as necessary (that is, according to the functions of each). Demonstrate functions as a core business system. That is, in the basic information management system 500, even if the system 200 does not have a basic business server or the system 300 does not have a DWH server, by performing communication with the mobile terminal management server 10, integrated basic business Can function as a system. Although not shown, even a system that does not have a process flow DB can exhibit functions as an integrated core business system by storing process flow data in the mobile terminal management server 10. Since a well-known technique is used for the core business server provided in each core business system, the integrated core business system 100 will be described below as an example.
  • the core business server 110 is a server managed by an administrator of the core information management system 500, for example, and has various functions for managing form information related to various businesses (for example, creation, update, storage, etc. of information). Have.
  • the core business server 110 is configured by a general information processing apparatus including an OS (Operating System) and a relational DB.
  • “Here,“ form ” is a general term for books and slips.
  • the “book” is used to fill in items related to the receipt and payment of money and goods
  • the “slip” is the data used as the basis for creating the book and provides evidence of business transactions. Is. In this example, the case where the core business server 110 handles process data (data regarding each business process) indicating only slip data as form data will be described as an example.
  • the core business server 110 executes various processes according to the business application program.
  • Examples of the business application program include a sales business management program, a sales business management program, a production management program, a financial accounting management program, and a management accounting management program.
  • the DWH server 120 is a server managed by a system administrator of this system, for example, and has various functions for realizing a data warehouse.
  • the “data warehouse” refers to a system that analyzes the relationship between items from business data such as form data accumulated in time series.
  • the DWH server 120 has a function of registering various data in a predetermined storage area by converting a CSV (Comma-Separated Value) format file transferred from the core business server 110 into a predetermined data format.
  • CSV Common-Separated Value
  • the DWH server 120 may be configured to extract data corresponding to each storage area from the CSV format state without converting the data format.
  • the process flow DB 101 includes various process data (or form data) collected and organized by various information processing using various programs stored in the business application program DB (not shown) of the core business server 110. This is a storage medium for storing process flow data. The process flow data will be described later in detail.
  • the integrated core business system 100 includes a business related data DB (not shown) managed by the DWH server 120, and the core business server 110 stores process data stored in the process flow DB 101, According to a predetermined extraction condition, it has a function of converting to the CSV format and transmitting it to the mobile terminal management server 10.
  • the core business server 110 transfers a data file in CSV format by FTP (File Transfer Protocol) to the mobile terminal management server 10.
  • FTP File Transfer Protocol
  • the mobile terminal management server 10 is a server on which ERP operates, and is a server that provides various data via a communication network in response to a request from a mobile terminal used by a user.
  • the mobile terminal management server 10 is configured by an information processing apparatus such as a WWW server, for example, and manages the mobile terminal management server 10 different from the system administrator of the basic information management system 500 or the system administrator of the basic information management system 500. Managed by a person.
  • FIG. 2 is a block diagram illustrating a configuration example of the mobile terminal management server 10.
  • the mobile terminal management server 10 includes a process flow data management unit 11 that performs processing related to process flow data management, a login management unit 12 that performs processing related to login management, and mobile terminals 31 to 3N.
  • a process flow data provision processing unit 13 that executes processing for providing process flow data
  • a process flow data update processing unit 14 that executes processing for updating process flow data in response to a request from the mobile terminals 31 to 3N, and the like.
  • a customer information management unit 15 that performs processing related to the management of customer information, a business application program DB 17, a process flow DB 18, and various data necessary for realizing a function as a general core business server (for example, business application Various programs stored in the program DB 17 And a other DB19 storing the usage data).
  • the other DB 19 is a part not particularly related to the present invention, and a detailed description thereof will be omitted.
  • the business application program DB 17 is a storage medium that stores programs used for various businesses. Programs stored in the business application program DB 17 include a sales business management program, a purchasing business management program, a production management program, a financial accounting management program, and a management accounting management program.
  • the process flow DB 18 is a storage medium that stores process flow data including various process data (or form data) collected and organized by various information processing using various programs stored in the business application program DB 17. is there.
  • process flow data including various data related to a process flow (business flow) including a plurality of business processes is stored in the process flow table PT in the process flow DB 18.
  • the mobile terminal management server 10 centrally manages process flow data generated for each process flow using one process flow table PT.
  • the process flow data includes generally used slip data (for example, for the slip data corresponding to the order slip, the order slip header information, the order slip detail information, the delivery date schedule, etc. Is stored in a structure that can be searched based on the key such as the slip number, etc.
  • the slip number includes the order number, order number, shipping number, entry / exit number, invoice inquiry, billing number, Account number etc. are included)).
  • the mobile terminal management server 10 manages the process flow data in a plurality of tables, for example, for each type described later, or for each piece of common data (for example, an order recipient) described later. It is good also as composition to do.
  • FIG. 3 is an explanatory diagram showing an example of the storage state of process flow data in the process flow DB 18.
  • the process flow data in this example includes a main key part, a reference key part, a type part, a status part, a common data part, and a process specific data part.
  • Each item corresponding to each part of the process flow data indicates the type of process data constituting the process flow data.
  • data relating to each business process constituting the process flow is allocated and stored in each part constituting the process flow data.
  • process data relating to a process flow related to a series of operations is stored in the same entry (that is, the same line in the process table PT) in the process flow table PT. Is done. With such a configuration, it is possible to define the correspondence between the process data.
  • the “primary key part” is a part in which primary key data, which is data for uniquely identifying the process flow data, is stored in the process flow data.
  • the main key part is composed of a process flow number and a process flow detail number. That is, in this example, a combination of a process flow number and a process flow detail number becomes an identifier (ID) of each process flow data.
  • the main key part is updated when the process flow data is registered for the first time.
  • “when first registering process flow data” means that when an entry (data row) is added to the process flow data, for example, process data belonging to a certain process flow and corresponding other processes It shall mean the time when unregistered process data is registered.
  • the “update” here includes addition of data.
  • the “process flow number” is an identifier for specifying one process flow data (that is, one column in the process flow table PT shown in FIG. 3).
  • the process flow number is assigned to each process data having the same predetermined item.
  • the same number is assigned to the process flow number of the process flow number that has the same type and the order-receiving party in the process flow data.
  • the “process flow detail number” is an identifier for identifying specific process flow data from among the process flow data assigned with the same process flow number. That is, for example, the process flow table PT shown in FIG. 3 indicates that the business process “order received” in the process flow type “inventory sales” has received orders for the amounts “1200” and “2600” from the order recipient “T001”.
  • the process flow data including the process data to be shown can be uniquely identified by the combination of the process flow number “000001” and the process flow detail number “0010” or “0020”, respectively.
  • the “reference key part” is data for specifying other process flow data (or other process data) related to the process flow, such as the original transaction for sales returns, among the process flow data. This is the part where key data is stored.
  • the reference key part is composed of a reference number and a reference specification number. The reference key part is updated when the process flow data is registered for the first time.
  • the process number and process flow detail number of other process flows related to the process flow are stored in the reference number and the reference detail number, respectively.
  • the reference key portion contains data indicating the same value as the primary key portion of the same entry (that is, the reference number is a process)
  • a flow number is stored, and a process flow item number is stored in the reference item number.
  • the reference key part indicates other process data related to the process flow, the reference key part is further provided with data for specifying the type of the process data.
  • the “type part” is a part in which type data that is a type of process flow, such as inventory sales and sample shipment, is stored in the process flow data.
  • the type part is updated when the process flow data is registered for the first time.
  • the type of process flow is not limited to inventory sales or sample shipment. Also, it is assumed that which process is required for each type of process flow is determined in advance (that is, the type and number of business processes included in each type of process flow are different).
  • the “status part” stores status data that is data indicating the progress of the process flow (that is, data indicating the progress of each of a plurality of business processes included in the process flow) among the process flow data.
  • the status data indicates the progress of each business process by setting “0” for the unfinished business process and “1” for the completed business process for the business process required by the process flow. Show. That is, for example, as shown in FIG. 3, the process flow of “inventory sales”, and the business processes included in the process flow are “order receipt”, “shipment”, “shipping”, “shipping inspection”, and “sales”. In this case, it is assumed that process specific data (for example, order date) related to the business process “order received” is registered. In this case, in the status data, the portion corresponding to “sales” is “1”, and the other portions remain in the initial state (ie, the state in which “0” is set).
  • the status part in this example is updated for each business process.
  • the status part is updated when process-specific data to be described later is input, specifically, when it is determined that each business process is completed because a predetermined status change condition is satisfied.
  • the status change condition is not particularly limited, in this example, “all process specific data corresponding to one business process is input” is stored in a predetermined storage area of the mobile terminal management server 10 as a status change condition. It shall be remembered.
  • a part of the items (column items) constituting the table stores unnecessary process data in a specific process flow.
  • a part for storing unnecessary process data is empty data, and “0” is stored in status data corresponding to the empty data.
  • the “common data part” is data that does not depend on the business process such as the order receiving party and the shipping destination among the process flow data (that is, common data between business processes included in the same process flow). This is the part where data is stored. The common data part is updated when the process flow data is registered for the first time.
  • process specific data part is a text that indicates precautions such as the order date and data registered in each business process in the process flow data (for example, “delivery deadline” and “breaker”) Data), etc., is a part in which process-specific data that is data unique to each business process included in the same process flow is stored.
  • the process specific data part is updated for each business process. Therefore, in this example, it can be said that the process flow data based on the business process is “process-specific data” and the data not based on the business process is “common data”.
  • order received means a state in which an order is received from a customer and a contract with the customer is concluded.
  • shipment instruction means a state in which an instruction to ship a product is given to a warehouse company or a logistics person.
  • shipment means a state in which goods are shipped from the warehouse and movement is started.
  • Inspection means a state in which the inspection of the customer is completed and the ownership of the product is transferred to the customer.
  • the process flow DB 18 is provided with an update condition table UT in which update condition data indicating an update condition of the process flow data (or process flow table PT) is registered.
  • FIG. 4 is an explanatory diagram showing an example of the storage state of the update condition data stored in the update condition table UT in the process flow DB 18.
  • the update condition data in this example includes a business process name, a process flow type, and a process flow data update condition.
  • the “process flow data update condition” indicates the process data registration condition corresponding to the process flow type.
  • the process flow data update condition is defined as the type of process data that the process flow data should have as a prerequisite when process data related to a certain business process is added to the process flow data (that is, in the process flow). Indicates the type of business process that should be completed). That is, when the update condition table UT is as shown in FIG.
  • the update condition table UT may be configured by an administrator of the basic information management system 500, or may be configured by a user of the mobile terminals 31 to 3N.
  • the mobile terminal management server 10 stores various data stored in the process flow DB 18 and other DBs 19 in response to requests from predetermined external devices, in this example, the mobile terminals 31 to 3N and the integrated core business system 100, 200, 300. Have the function to provide. That is, the mobile terminal management server 10 has a function as a core business server. In other words, the mobile terminal management server 10 includes an ERP engine.
  • the mobile terminal management server 10 has a function as a DWH server having various functions for realizing a data warehouse.
  • the mobile terminal management server 10 includes an ERP engine and a configuration for functioning as a DWH server, so that integrated core business systems having different configurations (for example, integrated core business having both of the core business server and the DWH server)
  • integrated core business systems having different configurations for example, integrated core business having both of the core business server and the DWH server
  • the system 100, the integrated core business system 200 having only the DWH server, and the integrated core business system 300 having only the DWH server can be provided with information required for the integrated core business system. become.
  • Each of the mobile terminals 31 to 3N is an information processing apparatus such as Ipad (registered trademark) including a CPU (Central Processing Unit), a ROM, a RAM, and a display unit.
  • Ipad registered trademark
  • each of the mobile terminals 31 to 3N has various applications that can be used for handling form data, such as a Web browser.
  • each of the mobile terminals 31 to 3N receives, for example, a query for acquiring necessary form data (process flow data in this example) from the mobile terminal management server 10 in response to an operation input by the user. (Search items, search keys, extraction keys, etc.) are defined and transmitted to the mobile terminal management server 10.
  • each of the mobile terminals 31 to 3N communicates with the mobile terminal management server 10 via the relay device 20 and the communication network 40, and the data acquired from the mobile terminal management server 10 is transferred to, for example, a predetermined Web application (Web browser). ) Etc., and the function of outputting to the display unit.
  • a predetermined Web application Web browser
  • FIG. 5 is a flowchart showing an example of process flow data provision processing executed by the mobile terminal management server 10 or the like in the basic information management system 500 of this example.
  • the mobile terminal management server 10 provides process flow data in response to a request from the mobile terminal 31 used by the user X will be described as an example.
  • the mobile terminal 31 receives a login request by the login operation of the user X (step S101).
  • a login operation for example, a password input operation set in advance may be considered.
  • various operations for using various functions installed in the mobile terminal 31 are allowed.
  • Step S102 This login request is made, for example, by presenting predetermined information (for example, an electronic certificate issued to the user X, a user ID, a password, etc.) used for predetermined login determination.
  • predetermined information for example, an electronic certificate issued to the user X, a user ID, a password, etc.
  • the login management unit 12 of the mobile terminal management server 10 When receiving the login request, the login management unit 12 of the mobile terminal management server 10 performs an authentication process for determining whether or not to permit the login (step S103a). This authentication process may be performed using a user ID, a password, an electronic certificate, or the like, for example.
  • the login management unit 12 determines that the login is permitted (Y in step S103b)
  • the login management unit 12 sets the portable terminal 31 to the login state.
  • the login state of the portable terminal 31 means that the software application used for handling the form data installed in the portable terminal 31 is made valid (usable state).
  • the process flow data provision processing unit 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). If it is determined that login is not permitted (N in step S103b), the login management unit 12 ends the process flow data providing process without setting the mobile terminal 31 to the login state. If it is determined that login is not permitted, the login management unit 12 performs a process of notifying the mobile terminal 31 to that effect.
  • the mobile terminal 31 displays the data search screen indicated by the received data search screen information on the display unit included in the mobile terminal 31 (step S105).
  • FIG. 6 is an explanatory diagram showing an example of a data search screen.
  • the user X operates an operation unit (for example, a keyboard displayed on a display unit provided with a touch panel) provided in the mobile terminal 31, inputs a search item and a search word, and clicks a search button B2. Press.
  • Items for example, order slips, inventory, business partners, product names
  • search word a character string related to the process flow data (for example, a supplier name or a product name) is input.
  • step S106 When the search button B2 is pressed while the search item and the search word are input, the mobile terminal 31 presents the input search item and the search word as a search condition to the mobile terminal management server 10, A process flow data provision request is made (step S106).
  • search condition is an example, and any other condition may be used as long as it can search for arbitrary process flow data (or process data constituting the process flow data).
  • the mobile terminal management server 10 When the mobile terminal management server 10 receives the process flow data provision request, the mobile terminal management server 10 refers to the process flow DB 18 and searches the process flow data according to the search condition presented by the accepted provision request (step S107). If the corresponding data does not exist in the process flow DB 18, the mobile terminal management server 10 issues an acquisition request for the corresponding data to the general core business system 100, 200, 300 in step S 107, and performs the general core business. Corresponding data is acquired from the systems 100, 200, and 300.
  • the mobile terminal management server 10 transmits search result screen information indicating a search result screen for displaying the searched process flow data as a search result to the mobile terminal 31 (step S108).
  • the mobile terminal 31 displays the search result screen indicated by the received search result screen information on the display unit included in the mobile terminal 31 (step S109).
  • FIG. 7 is an explanatory diagram showing an example of a search result screen.
  • the search result screen includes a display area 701 for displaying the search result, a return button B1 that is pressed when returning to the previous screen, and an edit button that is pressed when editing the search result. B3 is provided.
  • the portable terminal 31 makes a logout request to the portable terminal management server 10 ( Step S111). If an operation for continuing access such as pressing the return button B1 is performed (N in step S110), the portable terminal 31 proceeds to the process in step S105 and displays the data search screen (see FIG. 6). indicate.
  • the login management unit 12 starts measuring the time (waiting time) during which no information is exchanged with the mobile terminal 31, and this waiting time is a predetermined time (for example, It is monitored whether or not 5 minutes, 10 minutes, 30 minutes, etc.) have elapsed (reached a predetermined time) (step S112).
  • a predetermined time for example, It is monitored whether or not 5 minutes, 10 minutes, 30 minutes, etc.
  • the login management unit 12 When a logout request is received during the measurement of the standby time (Y in step S113), the login management unit 12 stops the measurement of the standby time, and the history information (communication history information, operation by the current communication) with respect to the portable terminal 31. A request for erasing the history information or the like is issued (step S114), and a logout process for canceling the login state is performed (step S115).
  • step S112 If it is determined that the predetermined time has elapsed (Y in step S112), the login management unit 12 ends the measurement of the standby time, and the mobile terminal 31 performs history information ( A request to delete communication history information, operation history information, etc. is issued (step S114), and a logout process for canceling the login state is performed (step S115).
  • the portable terminal 31 when the portable terminal 31 receives a request for deleting history information, the portable terminal 31 performs a process of deleting the history information accumulated by the current communication with the portable terminal management server 10 (step S116).
  • FIG. 8 is a flowchart illustrating an example of the authentication process in step S103a.
  • FIG. 9 is a time chart for explaining the contents of the authentication process.
  • a user ID (ERP user ID) issued to the user X by the system administrator Y of the basic information management system 500 via the server administrator Z of the mobile terminal management server 10
  • the basic information management system 500 It is assumed that authentication processing using a password (ERP password) assigned to the user X via the server administrator Z of the mobile terminal management server 10 is performed by the system administrator Y.
  • the ERP user ID and the ERP password are given to the user X from the system administrator Y via the server administrator Z of the mobile terminal management server 10. Therefore, the general core business systems 100, 200, 300 and the mobile terminal management server 10 each hold an ERP user ID and an ERP password assigned to the user of the system 500.
  • authentication processing is performed using the ERP user ID and ERP password of user X issued as a license of the integrated core business system 100.
  • step S1001 When the login request presenting the ERP user ID and ERP password from the portable terminal 31 is received (step S1001), the login management unit 12 of the portable terminal management server 10 first performs the ERP presented from the portable terminal 31 in the authentication process. Authentication request information including a user ID and an ERP password is transmitted to the integrated core business system 100 to request authentication of the user X (step S501, step S1002).
  • the integrated core business system 100 Upon receiving the request for authentication, the integrated core business system 100 refers to the user information (in this case, the information associated with the ERP user ID, ERP password, etc. for each user) stored in its own database, Based on the ERP user ID and ERP password received from the mobile terminal management server 10, an authentication process for determining whether or not the user is a registered user is performed, and the result of the authentication is notified to the mobile terminal management server 10 (step) S1003).
  • the user information in this case, the information associated with the ERP user ID, ERP password, etc. for each user
  • the mobile terminal management server 10 Upon receiving the notification about the authentication result (step S502), the mobile terminal management server 10 determines whether or not to allow login according to the received notification (step S503). Login of the portable terminal 31 is permitted (step S1004).
  • the mobile terminal management server 10 After permitting login, the mobile terminal management server 10 performs various processes in response to a request from the mobile terminal 31 (step S1005).
  • processing processing such as search, information provision, information registration, etc.
  • the ERP presented from the mobile terminal 31.
  • a processing request is made by presenting the user ID and ERP password (step S1006).
  • the integrated core business system 100 determines that the user is a registered user based on the presented ERP user ID and ERP password, it executes the requested processing.
  • the mobile terminal management server 10 managed by the server administrator Z uses the ERP user ID and ERP password issued by the system administrator Y of the basic information management system 500 as described above, In the basic information management system 500 that provides information related to the form to the terminal 31, it is possible to prevent fraudulent acts due to fraudulent licenses, improve the safety of the system, and protect the system administrator Y and the user X. Will be able to.
  • FIG. 10 is a flowchart illustrating another example of the authentication process in step S103a.
  • FIG. 11 is an explanatory diagram showing an example of user information used in this example.
  • FIG. 12 is a time chart for explaining other contents of the authentication processing.
  • the user ID (ERP user ID) issued to the mobile terminal management server 10 by the system administrator Y of the basic information management system 500 and the mobile terminal management server by the system administrator Y of the basic information management system 500 10
  • a user ID issued to the user by the server administrator Z of the mobile terminal management server 10 a user ID issued to the user by the server administrator Z of the mobile terminal management server 10
  • a user by the server administrator Z of the mobile terminal management server 10 It is assumed that the authentication process using the password given is performed.
  • the ERP user ID and ERP password are assigned from the system administrator Y to the server administrator Z of the mobile terminal management server 10, and the user ID and password are assigned to the user X from the server administrator Z.
  • the general core business systems 100, 200, 300 and the mobile terminal management server 10 hold the ERP user ID and ERP password assigned to the server administrator Z of the system 500, respectively.
  • the ERP user ID and ERP password issued as the license of the integrated core business system 100, and the ERP user ID and ERP password associated with the user ID assigned to the user X from the server administrator Z An example in which authentication processing is performed using the user ID and password assigned to the user X from the server administrator Z will be described.
  • the ERP user ID and ERP password are associated with the user ID and password in a one-to-one relationship. That is, the server administrator Z issues one license (one set of user ID and password) to the user for one license (one set of ERP user ID and ERP password) given by the system administrator Y. It shall be.
  • the login management unit 12 of the mobile terminal management server 10 Upon receiving a login request that presents the user ID and password from the mobile terminal 31 (step S1011), the login management unit 12 of the mobile terminal management server 10 first stores the user stored in its own database in the authentication process. Whether the user is a registered user registered by the server administrator Z with the user ID and password presented from the portable terminal 31 with reference to information (here, information in which a user ID or password for each user is associated) (Step S511).
  • the mobile terminal management server 10 determines whether or not to allow login according to the determination result (step S503). Login of the terminal 31 is permitted (step S1012).
  • the mobile terminal management server 10 After permitting login, the mobile terminal management server 10 performs various processes in response to a request from the mobile terminal 31 (step S1013).
  • the mobile terminal management server 10 requests processing (search, information provision, information registration, etc.) from the general core business system 100, the mobile terminal management server 10 is stored in its own database.
  • the ERP user ID and ERP password associated with the user ID presented from the mobile terminal 31 are identified, and the identified ERP user ID and ERP password are presented.
  • a processing request is made (step S1014).
  • the integrated core business system 100 determines that the user is a registered user based on the presented ERP user ID and ERP password, it executes the requested processing.
  • the ERP user ID and ERP password issued by the system administrator Y of the basic information management system 500, and the user ID issued by the server administrator Z in association with the ERP user ID and ERP password uniquely. Since the mobile terminal management server 10 managed by the server administrator Z authenticates using the password, the core information management system 500 that provides information related to the form to the mobile terminal 31 prevents unauthorized acts due to unauthorized licenses. It is possible to improve the security of the system, and to protect the system administrator Y and the user X.
  • FIG. 13 is a flowchart showing an example of process flow data update processing executed by the mobile terminal management server 10 and the mobile terminal 31.
  • process flow data is updated in response to a request from the mobile terminal 31 used by the user X.
  • Steps S201 to S209 (including steps S103a and S103b) in the process flow data update process are the same as steps S101 to S109 (see FIG. 5: including steps S103a and S103b) in the process flow data providing process described above.
  • Steps S218 to S224 in the business data update process are the same as steps S110 to S116 (see FIG. 5) in the process flow data provision process described above, and therefore, steps S201 to S209 and S218 to S224 in the business data update process are described. Detailed description is omitted.
  • FIG. 14 is an explanatory diagram illustrating an example of an editing screen. As shown in FIG. 14, in the edit screen, an edit area 901 for displaying the search result in an editable manner, a return button B1 to be pressed when returning to the previous screen, and the edit result are stored on the mobile terminal management server 10 side. And an update button B4 that is pressed when reflecting in the processed process flow data.
  • the user X operates the mobile terminal 31 to display the search result by adding (for example, newly registering a slip), deleting, or changing the process flow data displayed in the editing area 604. Work to edit the process flow data. Then, after finishing the editing work, when the editing result is reflected in the process flow data stored on the mobile terminal management server 10 side, the user X operates the mobile terminal 31 and presses the update button B4. To do.
  • the mobile terminal 31 makes an information rewrite request for requesting the mobile terminal management server 10 to reflect the edited result (step S210).
  • the editing content for example, the mobile terminal management server information related to the mobile terminal management server 10 (for example, the electronic certificate issued to the mobile terminal management server 10), the user information related to the user X (for example, to the user X) For example, an electronic certificate issued).
  • the mobile terminal management server 10 accesses the process flow DB 18 and performs a predetermined process before login (pre-login process) (step S211).
  • pre-login process the mobile terminal management server 10 uses predetermined information (login determination information used for login determination, for example, an electronic certificate issued to the mobile terminal management server 10, a user X Processing for confirming the electronic certificate issued to the other).
  • the mobile terminal management server 10 determines whether or not to permit login (step S212). This determination may be made based on, for example, an ID, a password, or an electronic certificate.
  • the mobile terminal management server 10 sets the mobile terminal 31 to a login state (here, access to the process flow DB 18 is permitted) with respect to acceptance of information from the mobile terminal 31. (Step S213).
  • the portable terminal management server 10 When the portable terminal 31 is set in the login state (that is, when login is permitted), the portable terminal management server 10 corresponds to the information stored in the process data DB 18 according to the information rewrite request from the portable terminal 31 set in the login state. The process of rewriting the process flow data to be executed is executed (step S214). Then, the mobile terminal management server 10 transmits a rewrite notification for notifying the integrated core business system 100, 200, 300 that the rewriting has been performed according to the edited content (step S215). Thereafter, each integrated core business system 100, 200, 300 updates the process flow DB 101, 201, 301 included in itself according to the received rewrite notification. Each process flow DB 18, 101, 201, 301 may be configured to store the content rewritten in response to an information rewrite request from the mobile terminal 31. That is, it may be configured to record who rewrites process flow data and when.
  • the mobile terminal management server 10 transmits a rewrite notification for notifying the mobile terminal 31 that it has been rewritten according to the edited content (step S216).
  • the mobile terminal 31 Upon receiving the rewrite notification, the mobile terminal 31 displays a rewrite reflection notification for notifying the user X that the editing result has been reflected in a predetermined area of the editing screen (step S217).
  • step S218 is executed in the same manner as the above-described process flow data provision processing (see FIG. 5).
  • step S103a it is determined whether or not to permit the login to the portable terminal management server 10 in response to the login request from the portable terminal 31 that can be operated by the login process.
  • a process of accepting a data rewrite request step S210), performing a pre-login process on the process flow DB 18 when a rewrite request is accepted (step S211), and rewriting the process flow data in the process flow DB 18 if permitted. Is performed (step S214).
  • step S201 By performing the process flow data rewriting process as described above, it is possible to perform triple authentication in step S201, step S103a, and step S212, so that the process flow data is received in response to a request from the portable terminal 31. It is possible to improve safety when updating.
  • rewriting information data
  • the process flow DB 18 performs login determination, and when login is permitted, the process of rewriting data is performed.
  • the mobile terminal management server 10 receives a rewrite request from the mobile terminals 31 to 3N, it stores the editing contents and information (information necessary for authentication) regarding the mobile terminals 31 to 3N that are the source of the rewrite request.
  • the process flow DB 18 may be rewritten by batch processing at a predetermined timing (for example, every day at 23:00).
  • the mobile terminal management server 10 receives an update request (information rewrite request) for process flow data from a mobile terminal in a logged-in state, the update content (edit content) of the received update request, and the mobile that made the update request.
  • Update related information including terminal information (for example, an electronic certificate) indicating the terminal is stored (for example, stored in a storage medium included in the mobile terminal management server 10), and a predetermined timing (for example, every day at 23:00) is reached.
  • Update the process flow data in batches using the update related information accumulated, and batch update processing (information rewriting) in response to the update requests received from each mobile terminal that was in the login state It is good also as a structure to perform. With this configuration, the number of accesses to the process flow DB 18 can be greatly reduced, and safety can be further improved.
  • FIG. 15 is a flowchart illustrating an example of database update processing executed by the mobile terminal management server 10.
  • a process for updating the process flow data stored in the process flow DB 18 is executed by the mobile terminal management server 10.
  • the mobile terminal management server 10 uses various process data and process flow data collected and organized by various information processing using various programs stored in the business application program DB 17 at a predetermined timing.
  • the database update process described below is different from the case of updating in response to an update request from the mobile terminals 31 to 3N (for example, the process flow data update process described above, see FIG. 13).
  • the mobile terminal management server 10 determines whether or not new process flow data (new process flow data) has been acquired (step S301). If it is determined that new process flow data has not been acquired (N in step S301), the mobile terminal management server 10 proceeds to the process in step S303 described later.
  • the mobile terminal management server 10 registers the acquired process flow data in the process flow table PT (step S302).
  • the mobile terminal management server 10 determines whether or not process data corresponding to the registered process flow data (that is, data relating to a business process constituting the process flow) has been acquired (step S303).
  • process data acquired by the mobile terminal management server 10 is registered process data is determined based on whether the process flow data having a combination of the process flow number and the process flow detail number included in the acquired data is a process flow. This is done by determining whether or not it is stored in the table PT. Therefore, in this example, the data (that is, the process that forms the main key part) in the data (data input by the business executor or data created by the business application program) acquired by the mobile terminal management server 10. (Flow number and process flow detail number) are required to be included.
  • step S303 If it is determined that the process data corresponding to the registered process flow data has not been acquired (N in step S303), the mobile terminal management server 10 refers to the other DB 19 and stores the storage area corresponding to the acquired data. The acquired data is registered (step S304), and the process proceeds to step S301.
  • the mobile terminal management server 10 refers to the update condition table UT corresponding to the acquired process data and acquires the process data.
  • the update condition data corresponding to the processed process data is specified (step S305).
  • the mobile terminal management server 10 specifies update condition data based on the business process type and process flow identification information (that is, the process flow number and the process flow detail number) indicated by the process data.
  • the mobile terminal management server 10 determines whether or not the process flow data satisfies the update condition indicated by the specified update condition data (step S306). That is, the mobile terminal management server 10 determines whether or not to register the acquired process data as part of the process flow data in the process flow table PT based on the process flow data and the update condition data. In this example, the mobile terminal management server 10 compares the status part of the process flow data corresponding to the acquired process data with the update condition data, and the business process for which “1” is set in the update condition data is in the status. If all of the sections are set to “1”, it is determined that the process flow data satisfies the update condition.
  • step S307 If it is determined that the process flow data does not satisfy the update condition indicated by the specified update condition data (N in step S306), the mobile terminal management server 10 executes a predetermined error process (step S307), The process proceeds to step S301.
  • the “error processing” is not particularly limited as long as the process flow data is not updated. For example, even if the process data is temporarily stored in a predetermined storage area until the update condition is satisfied, Yes, processing to investigate the cause of acquiring process data that does not satisfy the update conditions (that is, the process of notifying the administrator of the error or the contents of the update condition that is not satisfied) Or the like).
  • the mobile terminal management server 10 updates the process flow data registered in the process flow table PT. (Step S308). That is, the mobile terminal management server 10 registers the acquired process data in the process flow table PT.
  • the mobile terminal management server 10 determines whether or not a predetermined status change condition related to the process flow data is satisfied by updating the process flow data (step S309). If it is determined that the predetermined status change condition is not satisfied in response to the process flow data being updated (N in step S309), the mobile terminal management server 10 proceeds to step S301.
  • the mobile terminal management server 10 determines the process flow based on the satisfied status change condition.
  • the status data included in the data is updated (step S310), and the process proceeds to step S301.
  • the database update process in this example is terminated by an end operation by the administrator of the mobile terminal management server 10, for example.
  • the database update process may be a process executed in real time, or may be a batch process executed every specific unit time.
  • a process having a part of real time property such as performing a real time process only for a specified period may be used.
  • FIG. 16 is a flowchart illustrating an example of a form output process executed by the mobile terminal management server 10 and the mobile terminal 31.
  • the mobile terminal management server 10 provides process flow data (a part or all of the process flow data) to the mobile terminal 31 to display the form on the display screen of the mobile terminal 31. Processing is executed.
  • the login management is the same as the process flow data providing process (see FIG. 5) described above, and thus the description thereof is omitted here.
  • the form output process is different from the process flow data providing process in that a form in a predetermined format is output.
  • the process flow DB 18 update process described here is an example of the database update process (see FIG. 15).
  • the mobile terminal 31 transmits a process flow data update request input screen request to the mobile terminal management server 10 in response to, for example, an operation input by the user X of the mobile terminal 31 (step S501).
  • the mobile terminal management server 10 When receiving the process flow data update request input screen request, the mobile terminal management server 10 transmits a process flow data update request input screen corresponding to the received process flow data update request input screen request (step S401).
  • the portable terminal 31 displays the process flow data update request input screen on the display screen of the display unit included in the mobile terminal 31 (step S502).
  • FIG. 17 is an explanatory diagram showing an example of a process flow data update request input screen.
  • the process flow data update request input screen includes identification information to be updated (in this example, data corresponding to the main key portion of the process flow data. That is, the process flow number and the process flow detail number). .)), A business process input area 1202 for receiving an input of the type of the business process indicated by the process data by the user X, and a detailed data input area for receiving the input of the contents of other process data.
  • a return button 1204 for accepting a request to switch the display screen output to the display unit to another display screen, and each input area (in this example, the main key data input area 1201, the business process input area 1202, the detailed data) Process based on the content entered in the input area 1203.)
  • the update button 1205 is provided to accept the update request of flow data.
  • the user X operates an operation unit (for example, a display area or a button displayed on the display unit on which the touch panel is arranged) included in the mobile terminal 31. That is, for example, when each input area is pressed by the finger of the user X, the portable terminal 31 starts accepting input of text data (including numbers and characters) for the pressed input area. And the portable terminal 31 displays a keyboard (not shown) on the display part in which the touch panel is arrange
  • an operation unit for example, a display area or a button displayed on the display unit on which the touch panel is arranged
  • the portable terminal 31 when receiving the selection of the business process input area 1202, the portable terminal 31 displays a predetermined business process name in a pull-down format so that it can be selected.
  • the method of accepting input of process data is not limited to this, and for example, the portable terminal 31 may accept a plurality of process data collected in a predetermined data format at a time.
  • the portable terminal 31 determines that it has accepted an update request for process flow data based on process data constituted by data input to each input area (step S503).
  • the mobile terminal 31 transmits the received update request to the mobile terminal management server 10 (step S504).
  • the mobile terminal management server 10 acquires process flow data corresponding to the received update request among the process flow data registered in the process flow table PT (step S402). At this time, the mobile terminal management server 10 updates the process flow data including the primary key data indicated by the update request (that is, data input to the primary key data input area 1201) as an update request (that is, received process data). Acquired as process flow data according to Further, “acquisition” here means temporarily storing the process flow data and the update condition data in a predetermined storage area in order to compare the process flow data with the update condition data.
  • the mobile terminal management server 10 acquires the update condition data corresponding to the update request (step S403).
  • the update condition data corresponding to the update request is the business process indicated by the update request and the type of the process flow data (that is, the business process input to the business process input area 1202 and the processing in step S402. This means update condition data that can be specified by the type indicated by the process flow data (see FIG. 4).
  • the mobile terminal management server 10 compares the acquired process flow data with the update condition data (step S404) and determines whether or not the process flow data update condition is satisfied (step S405). ).
  • the update condition of the process flow data is satisfied because one or more of the items set to “1” in the update condition data is not set to “1” in the status part of the process flow data. If it is determined that there is no change (N in step S405), the mobile terminal management server 10 creates an update error notification and transmits it to the mobile terminal 31 (step S406), and ends the processing here.
  • the mobile terminal 31 displays the update error notification display screen on the display screen of the display unit included in the mobile terminal 31 based on the received update error notification (step S506).
  • FIG. 18 is an explanatory diagram showing an example of an update error notification display screen.
  • the update error notification display screen is provided with an update error notification display area 1301 that is displayed superimposed on the process flow data update request input screen.
  • the update error notification display area 1301 in addition to the standard text for notifying the user X of the update error, a detail display button 1302 for receiving a request to display details of the update condition, A close button 1303 for receiving a request for deleting the update error notification display area 1301 from the display screen is provided.
  • the mobile terminal 31 can recognize, for example, the comparison result between the process flow data and the update condition data in the mobile terminal management server 10 (see FIG. For example, a comparison table indicating the status part of the process flow data and the process flow data update condition of the update condition data is displayed.
  • step S405 Y the mobile terminal management server 10 adds the process data indicated by the update request to the process flow data and updates the process flow data (step S407).
  • the mobile terminal management server 10 transmits the updated process flow data to the mobile terminal 31 (step S408), and ends the processing here.
  • the mobile terminal 31 displays a form display screen on the display screen of the display unit included in the mobile terminal 31 based on the received process flow data (step S507).
  • FIG. 19 is an explanatory diagram showing an example of a form display screen.
  • the form display screen includes a form display area 1401 for displaying a form based on the process flow data, a form status display area 1402, a return button 1403, and a change button 1404.
  • the mobile terminal 31 changes the scale of the form displayed in the form display area 1401 in accordance with, for example, an operation of a keyboard or the like provided in the mobile terminal 31.
  • part or all of the process flow data is displayed in a predetermined display form in the form display area 1401.
  • information for displaying a part or all of the process flow data in a predetermined display form is created by the mobile terminal management server 10 and, for example, at the timing of step S408 in the form output process, It is assumed that it is transmitted to the terminal 31.
  • the portable terminal 31 may be configured to display a part or all of the received process flow data in the form display area 1401 in a predetermined display format based on information stored in a storage device included in the mobile terminal 31.
  • the form status display area 1402 is an area for displaying the type (or status, hereinafter referred to as status) of the form displayed in the form display area 1401.
  • status As the status of the form, various forms such as an order slip, a delivery slip, an inspection slip, and an invoice can be considered.
  • the return button 1403 is a button for accepting a request to return the display screen to the process flow data update request input screen.
  • the mobile terminal 31 In response to the selection of the return button 1403 by the user X, the mobile terminal 31 not only returns the display screen to the process flow data update request input screen but also sends an update request to the mobile terminal management server 10. A request for canceling the update of the process flow data based on the above may be transmitted.
  • the portable terminal 31 is input to each input area (in this example, the primary key data input area 1201, the business process input area 1202, and the detailed data input area 1203) according to the selection of the return button 33.
  • the process flow data update request input screen may be displayed in a state indicating the text data (the business process selected in the business process input area 1202). With such a configuration, it is possible to easily confirm the input content by the user X.
  • the change button 1404 is a button for accepting a request to change the display contents of the form display area 1401.
  • a process for changing the display contents of the form display area 1401 will be described.
  • the mobile terminal 31 determines whether a form status change request from the user X has been received (step S508).
  • the mobile terminal 31 first accepts selection of the form status display area 1402 by the user X.
  • the portable terminal 31 displays a list of form status names indicating the forms of the forms that can be displayed, for example, in a pull-down manner.
  • the mobile terminal management server 10 inputs data relating to the form form (form form data) and process flow data stored in a predetermined storage area in advance (that is, each column item of the process flow table PT). Based on the status, a form status name indicating the form of the form that can be displayed is specified. That is, for example, when the type of process flow data transmitted to the mobile terminal 31 is “stock sales” and only process data related to the business process “order received” is registered in the process specific data section, the mobile terminal management server 10 , Specify only "order receipt” as the form status name. If process data related to the business process “issue” is registered in addition to the process data related to the business process “order received”, the mobile terminal management server 10 sets “order receipt slip” and “issue slip” as the form status names. Is identified.
  • FIG. 20 is an explanatory diagram for explaining the transition of the form status based on the state of the process flow data.
  • images 1501 to 1504 are in the form of forms (specifically slips) that can be displayed in the form display area 1401 based on the process flow data.
  • the images 1501 to 1504 are explanatory diagrams for explaining the transition of the form status, and do not show specific description examples for playing a role as various forms.
  • an area 1511 indicates a form status name
  • an area 1512 indicates a process flow type
  • an area 1513 indicates a business process name of process data included in the process flow data. It is assumed that it is an area to be shown (in this example, a character string display area).
  • the form status name corresponding to the type of process data included in the process flow data is displayed in the area 1511.
  • the form status name (that is, the process The types of forms that can be displayed based on flow data will increase. This is not "whether or not there is the next type of form", but "the form status increases according to the state of the process flow data (that is, the types of forms that can be displayed increase)" means.
  • the portable terminal 31 receives process flow data including business processes “orders”, “shipping instructions”, “shipping”, and “shipping inspection” before the processing of step S507 in the form output processing.
  • the portable terminal 31 includes the business process “order received”, “shipment instruction”, “shipping”, “shipping inspection” in the process flow indicated by the received process flow data.
  • the form corresponding to the form status name “order received slip” corresponding to the business process “order received” positioned at the top is displayed in the form display area 1401 (see FIG. 19).
  • the mobile terminal 31 may be configured to display a form corresponding to the business process according to the process data newly added to the process flow data in the process of step S407 in the form display area 1401.
  • step S508 If it is determined in the document status change request acceptance determination process (step S508) that the form status change request by the user X is not accepted (N in step S508), the portable terminal 31 proceeds to the process of step S510 described later.
  • the portable terminal 31 displays a form corresponding to the received change request in the form display area 1401 (step S509).
  • the mobile terminal 31 accepts the selection of the form status name “issue slip” corresponding to the business process “issue” by the user X, and displays the form (issue slip) corresponding to the business process “issue”. It is assumed that it is displayed in the area 1401. In this case, the mobile terminal 31 displays the form status name “issue slip” in the form status display area 1402.
  • the mobile terminal 31 determines whether or not to end the form output process (step S510). If it is determined that the form output process is not to be ended (N in step S510), the portable terminal 31 proceeds to the process in step S508.
  • the portable terminal 31 ends the process here.
  • the mobile terminal management server 10 is a server on which an ERP operates and provides various data via a communication network in response to a request from a mobile terminal used by a user.
  • the user license information for example, user ID, password
  • the login process is performed, various process requests are received from the logged-in portable terminal 31 where the login process has been executed, and predetermined processes (for example, inquiry of form data, registration of form data, etc., according to the received process request,
  • predetermined processes for example, inquiry of form data, registration of form data, etc., according to the received process request
  • server license information for example, ERP user ID, ERP password
  • the server license information itself is used as the user license information.
  • Server license information is presented and a processing request is made, so that a business system (for example, a core information management system) that provides information related to the form to the portable terminal 31 500), it is possible to prevent fraudulent acts due to fraudulent licenses, increase the safety of the system, and protect the system administrator and the user.
  • a business system for example, a core information management system
  • the mobile terminal management server 10 determines whether or not to permit the mobile terminal 31 to log in based on the user license information issued to the user X from the server administrator Z, and the mobile terminal 31 in the login state.
  • server license information that is license information issued to the server administrator Z
  • the user license information is uniquely assigned. Since the server license information that can be specified is presented and the processing request is made, it is determined whether or not the mobile terminal 31 is permitted to log in based on the user license information that can be uniquely specified by the server license information. And can prevent fraudulent acts such as unauthorized use of user license information. Can, it is possible to increase the security of the system, it is possible to protect the system administrator and the user.
  • server license information is used as the user license information
  • the mobile terminal management server 10 determines whether or not the user X is a registered user based on the server license information presented as the user license information. If it is configured to determine whether or not to allow login to the mobile terminal 31 by determining, whether or not to log in to the mobile terminal 31 based on user license information using the server license information itself. It is possible to determine whether the user license information is illegally used, to prevent illegal acts, to improve the safety of the system, and to protect the system administrator and the user. become able to.
  • one piece of user license information can be issued for one piece of server license information, and is license information associated with one piece of server license information. Then, by determining whether or not the user is a registered user based on the presented user license information, it is determined whether or not the mobile terminal 31 is permitted to log in, and the user license information used for the login determination and 1
  • the server license information associated with one-to-one is presented and the processing request is made to the integrated core business system 100
  • the user license associated with the server license information one-to-one It is possible to determine whether or not to allow the mobile terminal 31 to log in based on the information.
  • Sense information can be prevented abuse such as unauthorized use, it is possible to increase the security of the system, it is possible to protect the system administrator and the user.
  • the mobile terminals 31 to 3N are configured to permit login only when a predetermined regular login operation is accepted, authentication with the mobile terminals 31 to 3N is also required. And it is possible to require double or triple authentication, and it is possible to further enhance safety.
  • the mobile terminal management server 10 performs logout processing for releasing the login state in response to a logout request from the mobile terminals 31 to 3N, and the logout processing is executed.
  • the mobile terminal 31 to 3N is configured to request the communication history information related to the provision of slip data to be deleted (for example, step SS114; see FIG. 5). It becomes possible to prevent information leakage due to loss of the portable terminals 31 to 3N.
  • the mobile terminal management server 10 measures the time during which information is not exchanged with the mobile terminals 31 to 3N in the login state, and the measured time reaches a predetermined time. (For example, step S112, refer to FIG. 5.) Since the mobile terminal 31 to 3N are requested to delete the communication history information related to the provision of the process flow data, the communication history information can be deleted. Thus, it is possible to prevent information from leaking due to loss of the mobile terminals 31 to 3N.
  • FIG. 21 is a block diagram showing a configuration example of the basic information management system 501 according to the embodiment of the present invention.
  • the basic information management system 501 includes a mobile terminal management server 10, a data synchronization server 60, a relay device 20, a plurality of mobile terminals 31 to 3N (N is an arbitrary positive integer),
  • the integrated core business system 100, the integrated core business system 200, and the integrated core business system 300 are included.
  • the mobile terminal management server 10 and the mobile terminals 31 to 3N are connected to each other via a data synchronization server 60, a communication network 40 such as the Internet, and the repeater 20.
  • the mobile terminal management server 10 is connected to the integrated backbone business system 100, the integrated backbone business system 200, and the integrated backbone business system 300 via communication networks 51, 52, and 53 such as a LAN and a dedicated communication line, respectively. In addition, it is good also as a structure which can communicate between portable terminals and integrated core business systems via a portable terminal management server, and is good also as a structure which cannot communicate.
  • the mobile terminal management server 10 is connected to the data synchronization server 60 via a communication network such as a LAN or a dedicated communication line.
  • the data synchronization server 60 is interposed between the mobile terminal management server 10 and the mobile terminals 31 to 3N, and stores process data stored in the mobile terminals 31 to 3N and process data stored in its own DB. Is synchronized according to a predetermined synchronization rule (for example, a rule for synchronizing only specific data).
  • the data synchronization server 60 is configured by an information processing apparatus such as a WWW server, for example, and is managed by a system administrator of the basic information management system 501.
  • step S103a the above-described authentication process (step S103a) or the like is not executed, and the authentication process is similarly executed by the data synchronization server 60.
  • FIG. 22 is a flowchart showing an example of authentication processing executed by the data synchronization server 60.
  • FIG. 23 is an explanatory diagram showing an example of user information used in this example.
  • FIG. 24 is a time chart for explaining still another content of the authentication processing.
  • the user ID (ERP user ID) given to the mobile terminal management server 10 by the system administrator YY of the basic information management system 501 and the mobile terminal management server 10 by the system administrator YY of the basic information management system 501 A password (ERP password), a user ID (DDS user ID) given to the user X by the server administrator ZZ of the data synchronization server 60, and a user X by the server administrator ZZ of the data synchronization server 60 It is assumed that authentication processing using a password (DDS password) given to the user is performed.
  • DDS password password
  • the user information including the ERP user ID, the ERP password, the DDS user ID, and the DDS password is synchronized in the data synchronization server 60 and the mobile terminal management server 10 respectively.
  • the data synchronization server 60 and the mobile terminal management server 10 It is assumed that common user information is held respectively.
  • a case where authentication processing is performed using an ERP user ID and an ERP password issued as a license of the integrated core business system 100 will be described as an example.
  • the ERP user ID and ERP password are associated with the DDS user ID and DDS password on a one-to-one basis. That is, the server administrator ZZ gives one license (one set of DDS user ID and DDS password) to the user for one license (one set of ERP user ID and ERP password) given by the system administrator YY. Shall be issued.
  • the data synchronization server 60 Upon receiving a login request that presents the DDS user ID and DDS password from the mobile terminal 31 (step S1021), the data synchronization server 60 first performs user information stored in its own database (here, the authentication process). Whether or not the registered user is registered by the server administrator ZZ with the DDS user ID and the DDS password presented from the mobile terminal 31 with reference to the DDS user ID and DDS password associated with each user) (Step S521).
  • the data synchronization server 60 refers to the user information (see FIG. 23) stored in its own database and associates it with the DDS user ID presented from the mobile terminal 31.
  • the specified ERP user ID and ERP password are specified, and authentication request information including the specified ERP user ID and ERP password is transmitted to the integrated core business system 100 to request authentication of the user X (step S522, step S1022). ).
  • the integrated core business system 100 Upon receiving the request for authentication, the integrated core business system 100 refers to the user information (in this case, the information associated with the ERP user ID, ERP password, etc. for each user) stored in its own database, Based on the ERP user ID and ERP password received from the data synchronization server 60, an authentication process for determining whether or not the user is a registered user is performed, and the authentication result is notified to the data synchronization server 60 (step S1023).
  • the data synchronization server 60 Upon receiving the notification about the authentication result (step S523), the data synchronization server 60 determines whether or not to allow login according to the received notification (step S524). Login of the terminal 31 to the mobile terminal management server 10 is permitted (step S1024).
  • the mobile terminal management server 10 After permitting login, the mobile terminal management server 10 performs various processes in response to a request from the mobile terminal 31 (step S1025).
  • the mobile terminal management server 10 requests processing (search, information provision, information registration, etc.) from the general core business system 100
  • the mobile terminal management server 10 is stored in its own database.
  • the ERP user ID and ERP password associated with the DDS user ID presented from the mobile terminal 31 are specified with reference to the user information (see FIG. 23: the same as that held by the data synchronization server 60). Then, the specified ERP user ID and ERP password are presented and a processing request is made (step S1026).
  • the integrated core business system 100 determines that the user is a registered user based on the presented ERP user ID and ERP password, it executes the requested processing.
  • the mobile terminal management server 10 performs each of the above-described processes (FIG. 5, FIG. 5) according to a processing program (mobile terminal management program) stored in a storage medium included in the mobile terminal management server 10. 8, 10, 13, 15, and 16).
  • a business system in particular, an ERP system
  • an ERP system that provides information related to a form to a mobile communication terminal

Abstract

La présente invention concerne l'empêchement de l'utilisation frauduleuse d'une licence frauduleuse, et la protection de gestionnaires et d'utilisateurs de système d'un système professionnel contre une fourniture d'informations associées à des formulaires commerciaux à un terminal de communication mobile. Selon l'invention, un serveur de gestion de terminal mobile (10) exploité par un ERP détermine s'il faut autoriser, ou non, une ouverture de session pour un terminal mobile (31) sur la base des informations de licence d'utilisateur délivrées à un utilisateur (X) à partir d'un gestionnaire de serveur (Z), et présente des informations de licence de serveur, qui permettent d'identifier de manière unique des informations de licence d'utilisateur, lorsqu'une requête de traitement est faite à un système de planification de ressources d'entreprise (100) conformément à une requête de traitement du terminal mobile (31) dans un état de session ouverte, les informations de licence de serveur étant des informations de licence fournies au gestionnaire de serveur (Z). La requête de traitement est ensuite exécutée.
PCT/JP2012/004178 2012-06-27 2012-06-27 Serveur de gestion de terminal mobile et programme de gestion de terminal mobile WO2014002138A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2012/004178 WO2014002138A1 (fr) 2012-06-27 2012-06-27 Serveur de gestion de terminal mobile et programme de gestion de terminal mobile
JP2013529474A JPWO2014002138A1 (ja) 2012-06-27 2012-06-27 携帯端末管理サーバ、および携帯端末管理プログラム

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2012/004178 WO2014002138A1 (fr) 2012-06-27 2012-06-27 Serveur de gestion de terminal mobile et programme de gestion de terminal mobile

Publications (1)

Publication Number Publication Date
WO2014002138A1 true WO2014002138A1 (fr) 2014-01-03

Family

ID=49782380

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2012/004178 WO2014002138A1 (fr) 2012-06-27 2012-06-27 Serveur de gestion de terminal mobile et programme de gestion de terminal mobile

Country Status (2)

Country Link
JP (1) JPWO2014002138A1 (fr)
WO (1) WO2014002138A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104361468A (zh) * 2014-11-27 2015-02-18 成都博高科技有限责任公司 一种基于emerp系统的现场设备收集自动统计工作量的方法
US20170134953A1 (en) * 2014-06-05 2017-05-11 Orange Securing an entry in a user database
KR102486646B1 (ko) * 2022-06-28 2023-01-10 주식회사 윈테크솔루션 소프트웨어 자산 관리서비스 제공 장치 및 방법

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002157219A (ja) * 2000-11-16 2002-05-31 Nec Software Chubu Ltd 既存オンラインアプリケーションのインターネット端末対応方法及びシステム並びにサーバ装置と記録媒体
JP2002312208A (ja) 2001-04-11 2002-10-25 Mitsubishi Electric Corp データウェアハウスシステム
JP2003323582A (ja) 2002-04-30 2003-11-14 Nec System Technologies Ltd 携帯電話を使用した電子帳票システム
JP2004334413A (ja) * 2003-05-06 2004-11-25 Taisei Corp 業務選択システム
JP2007200136A (ja) 2006-01-27 2007-08-09 Fuji Xerox Co Ltd 業務支援システム、業務支援プログラムおよび業務支援方法
JP2008217712A (ja) * 2007-03-07 2008-09-18 Nec Networks & System Integration Corp メールサーバアクセス方法及び電子メールシステム

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002163196A (ja) * 2000-11-29 2002-06-07 Ntt Data Corp 端末入力支援装置、携帯端末総合支援システム、及び端末入力支援プログラムを記録した記録媒体
JP2004133804A (ja) * 2002-10-11 2004-04-30 Kyuden Joho Service Kk リモートアクセス方法及びリモートアクセスシステム

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002157219A (ja) * 2000-11-16 2002-05-31 Nec Software Chubu Ltd 既存オンラインアプリケーションのインターネット端末対応方法及びシステム並びにサーバ装置と記録媒体
JP2002312208A (ja) 2001-04-11 2002-10-25 Mitsubishi Electric Corp データウェアハウスシステム
JP2003323582A (ja) 2002-04-30 2003-11-14 Nec System Technologies Ltd 携帯電話を使用した電子帳票システム
JP2004334413A (ja) * 2003-05-06 2004-11-25 Taisei Corp 業務選択システム
JP2007200136A (ja) 2006-01-27 2007-08-09 Fuji Xerox Co Ltd 業務支援システム、業務支援プログラムおよび業務支援方法
JP2008217712A (ja) * 2007-03-07 2008-09-18 Nec Networks & System Integration Corp メールサーバアクセス方法及び電子メールシステム

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170134953A1 (en) * 2014-06-05 2017-05-11 Orange Securing an entry in a user database
US11978030B2 (en) * 2014-06-05 2024-05-07 Orange Securing an entry in a user database
CN104361468A (zh) * 2014-11-27 2015-02-18 成都博高科技有限责任公司 一种基于emerp系统的现场设备收集自动统计工作量的方法
KR102486646B1 (ko) * 2022-06-28 2023-01-10 주식회사 윈테크솔루션 소프트웨어 자산 관리서비스 제공 장치 및 방법

Also Published As

Publication number Publication date
JPWO2014002138A1 (ja) 2016-05-26

Similar Documents

Publication Publication Date Title
JP5386639B2 (ja) データベース、データ管理サーバ、およびデータ管理プログラム
RU2700395C2 (ru) Система для гарантирования подлинности брендовых товаров
US20210256491A1 (en) System and method for remote management of sale transaction data
WO2013114440A1 (fr) Serveur de gestion de terminal mobile, et programme de gestion de terminal mobile
US9922369B2 (en) Transaction account interface
WO2013114442A1 (fr) Serveur de gestion de terminal mobile, et programme de gestion de terminal mobile
WO2014002138A1 (fr) Serveur de gestion de terminal mobile et programme de gestion de terminal mobile
KR20000024506A (ko) 가발권을 이용한 티켓 발매 방법 및 그 시스템
JP7306910B2 (ja) アプリケーション販売管理サーバシステム、アプリケーション販売管理システム、管理制御装置及び配信制御装置
WO2013114441A1 (fr) Serveur de gestion de terminal mobile, et programme de gestion de terminal mobile
CN111667277A (zh) 对应海外应用程序销售管理服务器系统
JP5597769B2 (ja) 携帯端末管理サーバ、および携帯端末管理プログラム
WO2013114449A1 (fr) Serveur de gestion de terminal mobile, et programme de gestion de terminal mobile
JP4754505B2 (ja) 商品取引仲介システム、商品取引仲介方法、コンピュータプログラム
KR101662707B1 (ko) 중고 물품 관리 시스템 및 이를 이용한 중고 물품의 거래 시스템
JP5558571B2 (ja) 携帯端末管理サーバ、および携帯端末管理プログラム
US20080243707A1 (en) Equipment management system, equipment management apparatus, equipment management method, and computer readable storage medium
US20160104230A1 (en) Cooperation server, non-transitory computer-readable storage medium storing cooperation program, and ec system
JP6789869B2 (ja) 取引情報照合システム
CN111667332A (zh) 对应海外应用程序销售管理系统
JP2016099952A (ja) 帳票データ管理装置、帳票データ管理プログラム、および帳票データ管理方法
WO2013114438A1 (fr) Serveur de gestion de terminal mobile, et programme de gestion de terminal mobile
WO2012086096A1 (fr) Base de données, serveur de gestion de données et programme de gestion de données
KR20200079931A (ko) 블록체인 네트워크를 활용한 전자티켓 발권 검증 방법
JP2002041741A (ja) ビジネスプロセス管理システム

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2013529474

Country of ref document: JP

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12876589

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE